[weewx-user] Re: ecowitt extra sensor data parameters

[Paul Ward]

Ah no thanks - dunno why that didn't pop up in a search - thanks I'll look 
into it

On Wednesday, October 7, 2020 at 5:13:57 AM UTC+1 gert.a...@gmail.com wrote:

> Hi
>
> Have You seen this 
> 
> ?
>
> Gert
> On Wednesday, October 7, 2020 at 12:57:53 AM UTC+2 ward...@gmail.com 
> wrote:
>
>> HI forum! I'm running 4.1.1 on a Pi connecting directly to a HP2551 with 
>> sensors of WS80 ultrasonic, WH40 rain, WH31 indoor, WH41 pm2.5 AQ, WH51 
>> soil, WH57 lightning (from Froggit in UK). It's using weewx-interceptor in 
>> ecowitt-client mode, default config. It seems to find most of the sensors 
>> but it's not recognising the lighting detector os some of the battery info. 
>> Does anyone know how I can add this, do I need to modify the interceptor 
>> and/or weewx.conf somehow? Also where can I find to display all the extra 
>> sensor data? I'm new to the weewx infrastructure but proficient in 
>> unix/code in general. Have read basics in wiki. Thank you! Paul
>>
>> /var/log/syslog entries below, only these, repeated:
>>
>> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
>> unrecognized parameter wh40batt=1.6
>> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
>> unrecognized parameter lightning_time=
>> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
>> unrecognized parameter wh80batt=3.28
>> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
>> unrecognized parameter lightning_num=0
>> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
>> unrecognized parameter wh57batt=5
>> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
>> unrecognized parameter lightning=
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/991e160f-50c6-4ed3-8542-71d287706943n%40googlegroups.com.

Re: [weewx-user] ecowitt extra sensor data parameters

[Paul Ward]

Do you think that would work even direct from the HP2551? If I'd understood 
it right the GW1000 driver uses an API that the consoles don't support 
directly but the GW1000 does.

On Wednesday, October 7, 2020 at 5:52:33 AM UTC+1 ti...@skybase.net wrote:

> Hi Paul,
>
> You could try swapping from the Interceptor plugin to the GW1000 driver 
> which captures more of the data than the Interceptor does rather than 
> trying to modify things to fit.
>
> https://github.com/gjr80/weewx-gw1000
>
> cheers
>
> Tim
> On 7/10/20 9:57 am, Paul Ward wrote:
>
> HI forum! I'm running 4.1.1 on a Pi connecting directly to a HP2551 with 
> sensors of WS80 ultrasonic, WH40 rain, WH31 indoor, WH41 pm2.5 AQ, WH51 
> soil, WH57 lightning (from Froggit in UK). It's using weewx-interceptor in 
> ecowitt-client mode, default config. It seems to find most of the sensors 
> but it's not recognising the lighting detector os some of the battery info. 
> Does anyone know how I can add this, do I need to modify the interceptor 
> and/or weewx.conf somehow? Also where can I find to display all the extra 
> sensor data? I'm new to the weewx infrastructure but proficient in 
> unix/code in general. Have read basics in wiki. Thank you! Paul 
>
> /var/log/syslog entries below, only these, repeated:
>
> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
> unrecognized parameter wh40batt=1.6
> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
> unrecognized parameter lightning_time=
> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
> unrecognized parameter wh80batt=3.28
> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
> unrecognized parameter lightning_num=0
> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
> unrecognized parameter wh57batt=5
> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
> unrecognized parameter lightning=
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/7ceefed8-5aa4-4d51-be21-3b03bb256522n%40googlegroups.com
>  
> 
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3261017b-4d22-455a-945d-c43f5b98744en%40googlegroups.com.

[weewx-user] My "rain" field adds up

[Sébastien F4GQK]

Hello,

 I have a WALDBECK Halley WHT3 weather station I use a home automation 
system where I receive information from the station and via a php file, I 
have the possibility of exporting to Weewx a txt file with the different 
fields recognized by weewx (currently every minute)

 In this file, the x server resets a value to zero: dailyrainin every 
day at midnight I added the "rain" field in my generated file "Today's 
Rain" is no longer at zero but every 10 minutes weewx adds my dailyrain. 
Currently 300 mm today !!! 


 It is the PWS server which gives me my dailyrain.  

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/cbf11875-0d56-4839-8c4f-f1a1ec77ca96n%40googlegroups.com.

Re: [weewx-user] ecowitt extra sensor data parameters

[gert.a...@gmail.com]

Hi
No API support from the HP2551.

The GW1000 driver supports a local configuration, server and GW1000/DP1500 
on the same network. 

In my case I'm running the weewx on at remote server and therefore I need 
the Interceptor for the Custom Server upload. You can upload from the 
DP1500/GW1000 or the HP2551 console. I have done that and it's working 
flawlessly. Now I'm using Olivers FOSHKplugin to upload to different 
domains. Using Oliver plugin, you just need 1 device(GW1000/DP1500 or a 
console)

Gert
On Wednesday, October 7, 2020 at 10:30:37 AM UTC+2 ward...@gmail.com wrote:

> Do you think that would work even direct from the HP2551? If I'd 
> understood it right the GW1000 driver uses an API that the consoles don't 
> support directly but the GW1000 does.
>
> On Wednesday, October 7, 2020 at 5:52:33 AM UTC+1 ti...@skybase.net wrote:
>
>> Hi Paul,
>>
>> You could try swapping from the Interceptor plugin to the GW1000 driver 
>> which captures more of the data than the Interceptor does rather than 
>> trying to modify things to fit.
>>
>> https://github.com/gjr80/weewx-gw1000
>>
>> cheers
>>
>> Tim
>> On 7/10/20 9:57 am, Paul Ward wrote:
>>
>> HI forum! I'm running 4.1.1 on a Pi connecting directly to a HP2551 with 
>> sensors of WS80 ultrasonic, WH40 rain, WH31 indoor, WH41 pm2.5 AQ, WH51 
>> soil, WH57 lightning (from Froggit in UK). It's using weewx-interceptor in 
>> ecowitt-client mode, default config. It seems to find most of the sensors 
>> but it's not recognising the lighting detector os some of the battery info. 
>> Does anyone know how I can add this, do I need to modify the interceptor 
>> and/or weewx.conf somehow? Also where can I find to display all the extra 
>> sensor data? I'm new to the weewx infrastructure but proficient in 
>> unix/code in general. Have read basics in wiki. Thank you! Paul 
>>
>> /var/log/syslog entries below, only these, repeated:
>>
>> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
>> unrecognized parameter wh40batt=1.6
>> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
>> unrecognized parameter lightning_time=
>> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
>> unrecognized parameter wh80batt=3.28
>> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
>> unrecognized parameter lightning_num=0
>> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
>> unrecognized parameter wh57batt=5
>> Oct  6 23:31:43 blueberrypi weewx[2710] INFO user.interceptor: 
>> unrecognized parameter lightning=
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/7ceefed8-5aa4-4d51-be21-3b03bb256522n%40googlegroups.com
>>  
>> 
>> .
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a32f5571-190d-42f4-8b6d-eb23f1a9533en%40googlegroups.com.

[weewx-user] Re: Upgrade PWS- WLL or WiFiLogger2?

[mh081...@gmail.com]

Yes, works with the script from my above reply with curl on raspberry 
pi4 debian 10 






jerry...@gmail.com schrieb am Dienstag, 6. Oktober 2020 um 21:01:31 UTC+2:

> I'm curious if the curl command works to restart WiFiLogger2.  I first 
> tried using the lynx command line browser and it did not resolve the page 
> correctly and didn't restart.  I assumed that was because the restart page 
> contains some javascript and lynx doesn't support javascript.  I then 
> switched to Safari, which has the downside of needing a GUI.  
>
> So does curl work in the terminal script?  That's a better solution if it 
> works.
>
> On Tuesday, October 6, 2020 at 6:37:57 AM UTC-7 gary@gmail.com wrote:
>
>> Thanks for the Linux version of the script.
>>
>> On Tuesday, October 6, 2020 at 4:33:35 AM UTC-4 mh081...@gmail.com wrote:
>>
>>> Thanks for the script. I changed it to be runnable from raspberry pi 
>>> (Debian 10.4)
>>>
>>> #!/bin/sh
>>> # Shell script to restart the weatherLogger wifi device in the Davis 
>>> Vantage Pro 2 in the Harbormaster Building
>>> # The weather logger tends to disconnect from network every 4 days 
>>> causing weewx to crash in a waiting state
>>> # Currently set to run by rycweather as a cron job once a day at 8:07 am.
>>> # check to see if weatherLogger is connected on Harbormaster vlan
>>> /bin/ping -c 1 WiFiLogger.fritz.box
>>> if [ "$?" = "0" ]; then
>>> weatherLoggerStatus="weatherLogger is online"
>>> #   Using curl
>>> curl --connect-timeout 5 --fail 
>>> http://WiFiLogger.fritz.box/admin/restart
>>> #   wait to launch and load javascript function of URL
>>> sleep 30
>>> else
>>> weatherLoggerStatus="weatherLogger is OFFLINE"
>>> fi
>>> # Check weatherLogger is connected again
>>> /bin/ping -c 1 WiFiLogger.fritz.box
>>> if [ "$?" = "0" ]; then
>>> newWeatherLoggerStatus="weatherlogger is back online"
>>> else
>>> newWeatherLoggerStatus="weatherLogger is OFFLINE after restart"
>>> fi
>>> echo "$weatherLoggerStatus and after restart $newWeatherLoggerStatus" | 
>>> sendemail -f mailadr...@mail.com -t mailad...@mail.com -u "WifiLogger 
>>> Restart" -s mailserver.mail.com -xu "username" -xp "password" -o 
>>> tls=yes -o message-content-type=auto
>>> exit
>>>
>>>
>>> jerry...@gmail.com schrieb am Dienstag, 6. Oktober 2020 um 09:36:22 
>>> UTC+2:
>>>
 WifiLogger2 doesn't have an ssh port open, but it does respond on port 
 80 to a restart command from http.  Under macOS I use the shell script 
 command to open the Safair browser to the restart javascript command.
 #!/bin/sh
 # Shell script to restart the weatherLogger wifi device in the Davis 
 Vantage Pro 2 in the Harbormaster Building
 # The weather logger tends to disconnect from network every 4 days 
 causing weewx to crash in a waiting state
 # Currently set to run by rycweather as a cron job once a day at 8:07 
 am.
 # check to see if weatherLogger is connected on Harbormaster vlan
 /sbin/ping -c 1 192.168.145.106
 if [[ "$?" == "0" ]]; then
 weatherLoggerStatus="weatherLogger is online"
 #   Using Safari browser
 open -a Safari http://192.168.145.106/admin/restart
 #   wait for Safari to launch and load javascript function of URL
 sleep 60
 #   close Safari
 killall Safari
 else
 weatherLoggerStatus="weatherLogger is OFFLINE"
 fi
 # Check weatherLogger is connected again
 /sbin/ping -c 1 192.168.145.106
 if [[ "$?" == "0" ]]; then
 newWeatherLoggerStatus="weatherlogger is back online"
 else
 newWeatherLoggerStatus="weatherLogger is OFFLINE after restart"
 fi
 echo "$weatherLoggerStatus and after restart $newWeatherLoggerStatus" | 
 mail -s "weatherLogger restart" xxx
 exit


 On Tuesday, October 6, 2020 at 12:23:03 AM UTC-7 mh081...@gmail.com 
 wrote:

> Hi,
>
> can you provide me this shell script to restart  WifiLogger2  by cron? 
> How did you connect to WifiLogger2 remotely? I have the same problem that 
> WifiLogger2 disconnects from wlan after several days.
>
> jerry...@gmail.com schrieb am Dienstag, 6. Oktober 2020 um 09:15:11 
> UTC+2:
>
>> I recently switched from a 3 hop retransmit across 1000 ft by 
>> multiple Davis Vantage Pro2 links to WiFiLogger2 across an AirMax 
>> backhaul 
>> and the weewx server has been running well for several months.  I had 
>> one 
>> problem with the WiFiLogger2.  It seemed to disconnect from its vLAN 
>> network every 4 days or so, which caused weewx to going into a waiting 
>> mode 
>> and not reconnect.  WiFiLogger2 eventually reconnects after about 2 
>> hours, 
>> but weewx needs to be restarted after that.  I fixed this problem by 
>> running a short shell script as a cron job once a day to restart 
>> WiFiLogger2.  WifiLogger2 has been stable if restarted once a day.  
>>
>> WifiLog

[weewx-user] Re: Can't tell if I'm posting soilTemp1, soilMoist1 and leafWet1 to WU

['quantum.m...@googlemail.com' via weewx-user]

Just a quick update - I received quick responses back, and as suspected, 
they both receive the data, but report they do not display the data. This 
makes sense to me, as the various combinations of Soil Moisture / Temp / 
Leaf would make it a nightmare to configure.

So from my perspective, as stated before, WeeWx does an incredible job with 
a myriad of different devices to allow weather to displayed in a variety 
incredible ways. IMHO I do not think that this warrants any further work, 
as the site providers will not support it anyway.

Many, many thanks Gary, and of course Tom Keffer, for a brilliant suite of 
software that is WeeWx!

On Monday, 5 October 2020 at 08:32:26 UTC+1 quantum.m...@googlemail.com 
wrote:

> Thank you for this. Looking at WOW, it does appear they do accept all the 
> data: https://wow.metoffice.gov.uk/support/dataformats 
> Looking at the WOW map there are many stations reporting Soil Moisture.
>
> Thanks for 'kicking me' into action - outputs (redacted) for PWS, AWEKAS, 
> WOW, WeatherCloud:
>
> PWS Wx
>
> Ambient: url: 
> http://www.pwsweather.com/pwsupdate/pwsupdate.php?action=updateraw&ID=XXX&PASSWORD=XXX&softwaretype=weewx-4.1.1&baromin=29.386&dateutc=2020-10-05%2007%3A00%3A00&dailyrainin=0.00&dewptf=49.1&rainin=0.00&leafwetness=002&humidity=095&tempf=50.5&solarradiation=30.00&soilmoisture=003&soiltempf=53.0&soiltemp2f=48.0&soiltemp3f=50.0&UV=0.00&winddir=202&windgustmph=4.0&windspeedmph=1.0
>
> AWEKAS
>
> url: 
> http://data.awekas.at/eingabe_pruefung.php?val=XXX;XXX;05.10.2020;07:00;10.3;95;995.124;0.00;1.6;202de;;6.4;30.00;0.000.00;weewx_4.1.1;xxx,xxx
>
> WOW
>
> url: 
> http://wow.metoffice.gov.uk/automaticreading?action=updateraw&siteid=xxx&siteAuthenticationKey=XXX&softwaretype=weewx-4.1.1&dateutc=2020-10-05+07%3A00%3A00&baromin=29.386&tempf=50.5&humidity=95&windspeedmph=1&winddir=202&windgustmph=4&windgustdir=248&dewptf=49.1&rainin=0.00&dailyrainin=0.00
>
> WeatherCloud
>
>
> http://api.weathercloud.net/v01/set?ver=4.1.1&type=251&wid=xxx&key=XXX&time=0700&date=20201005&temp=103&hum=95&wdir=202&wspd=4&bar=9951&rain=0&rainrate=0&tempin=236&humin=45&uvi=0&solarrad=300&et=0&chill=103&heat=103&dew=95&battery=455&temp01=111&temp04=117&temp05=89&temp06=117&temp07=89&temp08=100&leafwet01=2&soilmoist01=3&wspdhi=18&wspdavg=4&wdiravg=169&heatin=236&dewin=109&battery01=1
> Interestingly WeatherCloud is receiving, but you guessed it, it's not 
> showing - I'll email them, same with PWS.
>
> However, I am thinking this is a whole can of worms, by virtue of the many 
> different possible configurations Soil/Temp/Leaf etc., that really doesn't 
> warrant wasting yours or Tom's time.
>
> Bottom line to me, WeeWx does an incredible job, merging hundreds of 
> different Weather Station types of kit, with all manner of different 
> outputs - it is simply brilliant, and IMHO adding support for different 
> Soil / Leaf combinations is not really what WeeWx is about. 
>
> I'll see if I get a response back from either of the two sites it is going 
> to, and let you know. 
>
> Once again, many thanks
>
> On Sunday, 4 October 2020 at 21:49:26 UTC+1 gjr80 wrote:
>
>> Setting debug = 2 will show the same level of detail for posts to WOW and 
>> AWEKAS so you can see exactly what is being posted. As it turns out the WOW 
>> and AWEKAS uploaders don’t post soil temperature, soil moisture or leaf 
>> wetness to WOW or AWEKAS. I don’t use either of those services so I am 
>> unaware whether they accept those extra obs, though looking at the AWEKAS 
>> uploader I see a comment in the uploader code that position 21 is soil 
>> temperature. Not sure if that is correct or not or if it is why soil 
>> temperature is not uploaded. I will look into that but if there is any 
>> evidence that WOW accepts these extra obs please let us know.
>>
>> Gary
>>
>> On Monday, 5 October 2020 at 00:23:45 UTC+10 quantum.m...@googlemail.com 
>> wrote:
>>
>>> Following on from this, does the WeeWx Restx send Soil Temp and Moisture 
>>> to UK WOW and AWEKAS? Looking at the code, I am not sure, and it certainly 
>>> isn't appearing at either, for me on DVP2 with Soil/Moisture Station - all 
>>> showing on WLL, but that's a different story. 
>>>
>>> FWIW - it doesn't show for me either on WU, but I too can see the data 
>>> going to WU, but as you say Gary, WU problems are not uncommon. Would have 
>>> been nice to see it on WOW and AWEKAS etc.
>>>
>>> It's really not serious, but as the topic has been raised, I thought I 
>>> would ask?
>>>
>>> On Saturday, 3 October 2020 at 19:44:30 UTC+1 gjr80 wrote:
>>>
 Yes, WU problems are not uncommon.

 Gary

 On Sunday, 4 October 2020 at 04:38:17 UTC+10 dua...@gmail.com wrote:

>
> Gary, Worked. I was going to try that but didn't know enough yet.
>
> At least I know the problem is at Wunderground now. So nothing for me 
> to do other than wait.
>
> Thanks so much for your assistance.
>
> baromin=30.091&
> 

[weewx-user] Re: Can't tell if I'm posting soilTemp1, soilMoist1 and leafWet1 to WU

['quantum.m...@googlemail.com' via weewx-user]

 Just a quick update - I received quick responses back, and as suspected, 
they both receive the data, but report they do not display the data. This 
makes sense to me, as the various combinations of Soil Moisture / Temp / 
Leaf would make it a nightmare to configure.

So from my perspective, as stated before, WeeWx does an incredible job with 
a myriad of different devices to allow weather to displayed in a variety of 
incredible ways. IMHO I do not think that this warrants any further work, 
as the site providers will not support it anyway.

Many, many thanks Gary, and of course Tom Keffer, for a brilliant suite of 
software that is WeeWx!


On Monday, 5 October 2020 at 08:32:26 UTC+1 quantum.m...@googlemail.com 
wrote:

> Thank you for this. Looking at WOW, it does appear they do accept all the 
> data: https://wow.metoffice.gov.uk/support/dataformats 
> Looking at the WOW map there are many stations reporting Soil Moisture.
>
> Thanks for 'kicking me' into action - outputs (redacted) for PWS, AWEKAS, 
> WOW, WeatherCloud:
>
> PWS Wx
>
> Ambient: url: 
> http://www.pwsweather.com/pwsupdate/pwsupdate.php?action=updateraw&ID=XXX&PASSWORD=XXX&softwaretype=weewx-4.1.1&baromin=29.386&dateutc=2020-10-05%2007%3A00%3A00&dailyrainin=0.00&dewptf=49.1&rainin=0.00&leafwetness=002&humidity=095&tempf=50.5&solarradiation=30.00&soilmoisture=003&soiltempf=53.0&soiltemp2f=48.0&soiltemp3f=50.0&UV=0.00&winddir=202&windgustmph=4.0&windspeedmph=1.0
>
> AWEKAS
>
> url: 
> http://data.awekas.at/eingabe_pruefung.php?val=XXX;XXX;05.10.2020;07:00;10.3;95;995.124;0.00;1.6;202de;;6.4;30.00;0.000.00;weewx_4.1.1;xxx,xxx
>
> WOW
>
> url: 
> http://wow.metoffice.gov.uk/automaticreading?action=updateraw&siteid=xxx&siteAuthenticationKey=XXX&softwaretype=weewx-4.1.1&dateutc=2020-10-05+07%3A00%3A00&baromin=29.386&tempf=50.5&humidity=95&windspeedmph=1&winddir=202&windgustmph=4&windgustdir=248&dewptf=49.1&rainin=0.00&dailyrainin=0.00
>
> WeatherCloud
>
>
> http://api.weathercloud.net/v01/set?ver=4.1.1&type=251&wid=xxx&key=XXX&time=0700&date=20201005&temp=103&hum=95&wdir=202&wspd=4&bar=9951&rain=0&rainrate=0&tempin=236&humin=45&uvi=0&solarrad=300&et=0&chill=103&heat=103&dew=95&battery=455&temp01=111&temp04=117&temp05=89&temp06=117&temp07=89&temp08=100&leafwet01=2&soilmoist01=3&wspdhi=18&wspdavg=4&wdiravg=169&heatin=236&dewin=109&battery01=1
> Interestingly WeatherCloud is receiving, but you guessed it, it's not 
> showing - I'll email them, same with PWS.
>
> However, I am thinking this is a whole can of worms, by virtue of the many 
> different possible configurations Soil/Temp/Leaf etc., that really doesn't 
> warrant wasting yours or Tom's time.
>
> Bottom line to me, WeeWx does an incredible job, merging hundreds of 
> different Weather Station types of kit, with all manner of different 
> outputs - it is simply brilliant, and IMHO adding support for different 
> Soil / Leaf combinations is not really what WeeWx is about. 
>
> I'll see if I get a response back from either of the two sites it is going 
> to, and let you know. 
>
> Once again, many thanks
>
> On Sunday, 4 October 2020 at 21:49:26 UTC+1 gjr80 wrote:
>
>> Setting debug = 2 will show the same level of detail for posts to WOW and 
>> AWEKAS so you can see exactly what is being posted. As it turns out the WOW 
>> and AWEKAS uploaders don’t post soil temperature, soil moisture or leaf 
>> wetness to WOW or AWEKAS. I don’t use either of those services so I am 
>> unaware whether they accept those extra obs, though looking at the AWEKAS 
>> uploader I see a comment in the uploader code that position 21 is soil 
>> temperature. Not sure if that is correct or not or if it is why soil 
>> temperature is not uploaded. I will look into that but if there is any 
>> evidence that WOW accepts these extra obs please let us know.
>>
>> Gary
>>
>> On Monday, 5 October 2020 at 00:23:45 UTC+10 quantum.m...@googlemail.com 
>> wrote:
>>
>>> Following on from this, does the WeeWx Restx send Soil Temp and Moisture 
>>> to UK WOW and AWEKAS? Looking at the code, I am not sure, and it certainly 
>>> isn't appearing at either, for me on DVP2 with Soil/Moisture Station - all 
>>> showing on WLL, but that's a different story. 
>>>
>>> FWIW - it doesn't show for me either on WU, but I too can see the data 
>>> going to WU, but as you say Gary, WU problems are not uncommon. Would have 
>>> been nice to see it on WOW and AWEKAS etc.
>>>
>>> It's really not serious, but as the topic has been raised, I thought I 
>>> would ask?
>>>
>>> On Saturday, 3 October 2020 at 19:44:30 UTC+1 gjr80 wrote:
>>>
 Yes, WU problems are not uncommon.

 Gary

 On Sunday, 4 October 2020 at 04:38:17 UTC+10 dua...@gmail.com wrote:

>
> Gary, Worked. I was going to try that but didn't know enough yet.
>
> At least I know the problem is at Wunderground now. So nothing for me 
> to do other than wait.
>
> Thanks so much for your assistance.
>
> baromin=30.091&
>

Re: [weewx-user] Register your WeeWX station!

[Tom Keffer]

Unfortunately, we have suspended preview snapshots. It was just taking too
much memory, which would cause weewx.com to hang. Maybe later!

On Tue, Oct 6, 2020 at 12:40 PM Vetti52  wrote:

> being registered, but...
> when opening the station on the map, there is no preview picture. I am
> afraid, that for URLs containing windy.com a preview is not available,
> right? I could establish another URL, which, however is only available per
> IPv6 (IPv4 access is locked by a firewall). Would this satisfy as source
> for a preview picture?
>
> Vetti52 schrieb am Dienstag, 6. Oktober 2020 um 10:49:19 UTC+2:
>
>> That's it!
>> thanks
>>
>> tke...@gmail.com schrieb am Montag, 5. Oktober 2020 um 23:26:19 UTC+2:
>>
>>> I'm seeing an error on the server end: "station_url cannot contain
>>> single quotes".
>>>
>>> Not exactly sure what that means. Try using the URL
>>> https://www.windy.com/station/pws-f069b42a, without any quotes.
>>>
>>> -tk
>>>
>>> On Mon, Oct 5, 2020 at 12:21 PM Vetti52  wrote:
>>>
 just registered today, due to the advise in this thread. However there
 is no map entry. I get this log:

 Oct  5 21:00:30 raspbee weewx[10983] ERROR weewx.restx:
 StationRegistry: Failed to publish record 2020-10-05 21:00:00 CEST
 (1601924400): Failed upload after 3 tries

 I am using Weewx 4.1.1. My URL at windy.com actually works fine:
 https://www.windy.com/station/pws-f069b42a?54.088,10.258,8
 What is wrong?

 gjr80 schrieb am Sonntag, 4. Oktober 2020 um 22:57:52 UTC+2:

> The only requirement of the URL is that it is unique in the station
> registry. So I guess if you are making up an arbitrary URL be creative. WU
> URLs are fine, they are used by numerous users in the station registry.
>
> Gary
>
> On Monday, 5 October 2020 at 06:11:06 UTC+10 maf@gmail.com wrote:
>
>> Tom:
>>
>> A question on 1. below. What if you do not have a web page or use any
>> other (e.g. Weather Underground) site? Are you saying that we can make up
>> any arbitrary URL as long as it is unique?
>>
>> Thanks.
>>
>> Mike
>>
>>
>> On 10/4/2020 1:41 PM, Tom Keffer wrote:
>>
>> While we don't require it, I strongly encourage you to register your
>> station. We use the registration information for statistical purposes to
>> figure out which stations to support, and which to drop. We are looking 
>> at
>> cutting a few stations in V4.2, so it's important we get an accurate
>> representation of what is getting used.
>>
>> It's as simple as no registrations = no support!
>>
>> You can see the results on the WeeWX map
>> .
>>
>> Registering your station is easy:
>>
>>1. In the [Station] section of weewx.conf, set a unique URL for
>>your station as option *station_url*. If you have a webpage, use
>>that. Or, if you upload to the Weather Underground or other site, use 
>> your
>>station URL. It doesn't really matter, provided that it is unique.
>>2. Turn on the station registry uploader. In weewx.conf, under
>>[[StationRegistry]], set option *register_this_station* to True.
>>3. Restart weewxd.
>>
>> That's it! Thanks for your help!
>>
>> -tk
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/544ee748-0449-4eac-aa21-7d01ba37fe2en%40googlegroups.com
>> 
>> .
>>
>> --
 You received this message because you are subscribed to the Google
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to weewx-user+...@googlegroups.com.

>>> To view this discussion on the web visit
 https://groups.google.com/d/msgid/weewx-user/e021c67e-c987-4e6a-b3c6-f793b56aaee3n%40googlegroups.com
 
 .

>>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/1e80a19c-0356-442b-a4b9-7a69c8bcdd58n%40googlegroups.com
> 

[weewx-user] Parsing some NWS Area Forecast Matrices fails

[Michael Bruski]

Hi all,

First of all, I am running WeeWX 4.1.1 with forecast extension 3.4.0b10.

I had recently managed to use a Area Forecast Matrix for one location and 
that is working fine.   Recently I tried to setup a second location to use 
the AFM (different LID and FOID) and it fails to get a forecast even though 
I see it in the web browser using the URL that forecast.py uses.  After 
careful application of some trace print statements, I see the forecast is 
succesfully download from the FOID and that the forecast for the specified 
LID is also located and extracted but nothing gets parsed.  Below is a copy 
of my trace output from the log:

Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
forecast downloaded successfully from 
'http://forecast.weather.gov/product.php?site=NWS&product=AFM&format=txt&issuedby=LWX'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'MDZ005-072100-'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Carroll-'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Including the cities of Eldersburg and Westminster'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: '137 
PM EDT Wed Oct 7 2020'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Date Wed 10/07/20Thu 10/08/20Fri 
10/09/20'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'EDT 
3hrly 05 08 11 14 17 20 23 02 05 08 11 14 17 20 23 02 05 08 11 14 17 20'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'UTC 
3hrly 09 12 15 18 21 00 03 06 09 12 15 18 21 00 03 06 09 12 15 18 21 00'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Max/Min75 77 8047 48 5265 67 7042 44 4868 
70 73'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Temp   76 76 68 61 56 51 50 60 65 64 55 50 47 45 45 61 68 
67 59'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Dewpt  52 52 53 50 48 46 45 45 43 42 43 42 41 40 41 45 45 
46 47'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'RH 43 43 59 67 74 83 83 58 45 45 64 74 79 82 86 56 43 
47 64'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Wind dirW  W NW NW NW NW NW NW NW NW NW NW  W  W  W SW SW 
SW  S'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Wind spd   19 17 10  6  5  5  6 11 12 10  5  3  1  2  1  4  6  
8  4'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Wind gust  33 31'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Clouds CL CL SC FW FW CL CL FW CL CL CL CL FW FW FW FW FW 
FW SC'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'PoP 
12hr 20  20   0   0   0'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'QPF 
12hr  0   0   0   0   0'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Rain shwrs S  S'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Date  Sat 10/10/20  Sun 10/11/20  Mon 10/12/20  Tue 10/13/20'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'EDT 
6hrly 02 08 14 20   02 08 14 20   02 08 14 20   02 08 14 20'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'UTC 
6hrly 06 12 18 00   06 12 18 00   06 12 18 00   06 12 18 00'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Min/Max  5475  5669  5366  5468'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Temp  55 56 73 66   61 58 66 60   56 55 63 59   56 56 65 61'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Dewpt 50 54 59 60   59 56 55 54   54 53 56 56   56 56 58 57'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'PWind dir SSW  SWSE   E E   ESE'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
'Wind charLTGN  LTLT  GNGN  LTLT'
Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'Avg 
cloudsSC B1 B1 B1   B1 B1 B1 B1   B2 B2 B2 B2   B2 B2 B2 B1'
Oct  7 14:36:45 server weewx[3014] INFO user.

Re: [weewx-user] Parsing some NWS Area Forecast Matrices fails

[John Kline]

Perhaps Area Forecast Matrix responses can’t be treated just like Point 
Forecast Matrix responses.  AFMs are only supported to the extent that they 
provide an identically formatted response as the PFM response.

What do you know about AFMs and the differences between them and PFMs?

> On Oct 7, 2020, at 12:18 PM, Michael Bruski  wrote:
> 
> 
> 
> Hi all,
> 
> First of all, I am running WeeWX 4.1.1 with forecast extension 3.4.0b10.
> 
> I had recently managed to use a Area Forecast Matrix for one location and 
> that is working fine.   Recently I tried to setup a second location to use 
> the AFM (different LID and FOID) and it fails to get a forecast even though I 
> see it in the web browser using the URL that forecast.py uses.  After careful 
> application of some trace print statements, I see the forecast is succesfully 
> download from the FOID and that the forecast for the specified LID is also 
> located and extracted but nothing gets parsed.  Below is a copy of my trace 
> output from the log:
> 
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> forecast downloaded successfully from 
> 'http://forecast.weather.gov/product.php?site=NWS&product=AFM&format=txt&issuedby=LWX'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'MDZ005-072100-'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Carroll-'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Including the cities of Eldersburg and Westminster'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: '137 
> PM EDT Wed Oct 7 2020'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'Date  
>Wed 10/07/20Thu 10/08/20Fri 10/09/20'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'EDT 
> 3hrly 05 08 11 14 17 20 23 02 05 08 11 14 17 20 23 02 05 08 11 14 17 20'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'UTC 
> 3hrly 09 12 15 18 21 00 03 06 09 12 15 18 21 00 03 06 09 12 15 18 21 00'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Max/Min75 77 8047 48 5265 67 7042 44 4868 70 
> 73'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'Temp  
>  76 76 68 61 56 51 50 60 65 64 55 50 47 45 45 61 68 67 59'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'Dewpt 
>  52 52 53 50 48 46 45 45 43 42 43 42 41 40 41 45 45 46 47'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'RH
>  43 43 59 67 74 83 83 58 45 45 64 74 79 82 86 56 43 47 64'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'Wind 
> dirW  W NW NW NW NW NW NW NW NW NW NW  W  W  W SW SW SW  S'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'Wind 
> spd   19 17 10  6  5  5  6 11 12 10  5  3  1  2  1  4  6  8  4'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'Wind 
> gust  33 31'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Clouds CL CL SC FW FW CL CL FW CL CL CL CL FW FW FW FW FW FW 
> SC'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'PoP 
> 12hr 20  20   0   0   0'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'QPF 
> 12hr  0   0   0   0   0'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'Rain 
> shwrs S  S'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'Date  
> Sat 10/10/20  Sun 10/11/20  Mon 10/12/20  Tue 10/13/20'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'EDT 
> 6hrly 02 08 14 20   02 08 14 20   02 08 14 20   02 08 14 20'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'UTC 
> 6hrly 06 12 18 00   06 12 18 00   06 12 18 00   06 12 18 00'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Min/Max  5475  5669  5366  5468'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'Temp  
> 55 56 73 66   61 58 66 60   56 55 63 59   56 56 65 61'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'Dewpt 
> 50 54 59 60   59 56 55 54   54 53 56 56  

Re: [weewx-user] Cumulated bars

[Invisible Man]

Hmmm... looks like it doesn't change anything... ?

   [[[yearrain]]]
yscale = None, None, 0.02
plot_type = bar
rain
aggregate_type = cumulative
# aggregate_interval = 2629800 # Magic number: the length 
of a nominal month
aggregate_interval = 604800# == 1 week
label = Rain (weekly total)


On Wednesday, October 7, 2020 at 1:40:39 AM UTC+2 tke...@gmail.com wrote:

> Try 
>
>  aggregate_type = cumulative
>
>
>
>
> On Tue, Oct 6, 2020 at 11:49 AM Invisible Man  
> wrote:
>
>> Hello,
>>
>> In Weewx, is it possible to generate a graph with cumulated bars? For 
>> example, for year's rain, you'd see rain in January, then rain of January + 
>> February, then rain of January + February + March etc.
>>
>> In skin.conf,  I see this config. But tweaking the aggregate interval 
>> won't help me, because it won't sum the previous months... And plot_type 
>> only has bar, line or vector available.
>>
>> So, is this possible ?
>> Thanks
>>
>> [[[yearrain]]]
>> yscale = None, None, 0.02
>> plot_type = bar
>> rain
>> aggregate_type = sum
>> # aggregate_interval = 2629800 # Magic number: the length 
>> of a nominal month
>> aggregate_interval = 604800# == 1 week
>> label = Rain (weekly total)
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/4cd03028-e945-47b6-8b78-9cca1b22711fn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2b314311-1f5f-44e6-ae16-17a6cf6c313cn%40googlegroups.com.

Re: [weewx-user] Parsing some NWS Area Forecast Matrices fails

[Michael Bruski]

Hi John,

I've looked at several forecast matrices from my local and surrounding NWS 
forecast offices and haven't seen anything format wise that would lead me 
to think they would cause a problem for the forecast extension.  I have 
selected several different AFMs and see they parse fine.  But I ran into 
this issue with my local AFM and spent several hours trying to track down 
the cause.   The issue is not with the matrix itself but with text 
preceeding the DTG.   To test further, I put a cheap hack into the parse 
loop so that date2ts() isn't called if the first word in 'line' is 
'Including'.  This actually works (in this specific instance) and a valid 
forecast is produced.  What other lines of text might NWS put in the header 
preceeding the DTG, I just don't know.The URLs mentioned in forecast.py 
are dead links so I couldn't find any specifics on decoding the reports.

I'm not terribly comfortable programming in python so I'm not sure the best 
approach to work this issue but sending bad data to time.mktime() via 
date2ts() is probably bad unless there is a way to trap the error.  Not 
meant to criticize...  just my thoughts on how to make it better.

Mike/AJ9X

On Wednesday, October 7, 2020 at 4:24:56 PM UTC-4 jo...@johnkline.com wrote:

> Perhaps Area Forecast Matrix responses can’t be treated just like Point 
> Forecast Matrix responses.  AFMs are only supported to the extent that they 
> provide an identically formatted response as the PFM response.
>
> What do you know about AFMs and the differences between them and PFMs?
>
> On Oct 7, 2020, at 12:18 PM, Michael Bruski  wrote:
>
> 
>
>
> Hi all,
>
> First of all, I am running WeeWX 4.1.1 with forecast extension 3.4.0b10.
>
> I had recently managed to use a Area Forecast Matrix for one location and 
> that is working fine.   Recently I tried to setup a second location to use 
> the AFM (different LID and FOID) and it fails to get a forecast even though 
> I see it in the web browser using the URL that forecast.py uses.  After 
> careful application of some trace print statements, I see the forecast is 
> succesfully download from the FOID and that the forecast for the specified 
> LID is also located and extracted but nothing gets parsed.  Below is a copy 
> of my trace output from the log:
>
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> forecast downloaded successfully from '
> http://forecast.weather.gov/product.php?site=NWS&product=AFM&format=txt&issuedby=LWX
> '
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'MDZ005-072100-'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Carroll-'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Including the cities of Eldersburg and Westminster'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> '137 PM EDT Wed Oct 7 2020'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Date Wed 10/07/20Thu 10/08/20Fri 
> 10/09/20'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'EDT 3hrly 05 08 11 14 17 20 23 02 05 08 11 14 17 20 23 02 05 08 11 14 
> 17 20'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'UTC 3hrly 09 12 15 18 21 00 03 06 09 12 15 18 21 00 03 06 09 12 15 18 
> 21 00'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Max/Min75 77 8047 48 5265 67 7042 44 4868 
> 70 73'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Temp   76 76 68 61 56 51 50 60 65 64 55 50 47 45 45 61 68 
> 67 59'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Dewpt  52 52 53 50 48 46 45 45 43 42 43 42 41 40 41 45 45 
> 46 47'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'RH 43 43 59 67 74 83 83 58 45 45 64 74 79 82 86 56 43 
> 47 64'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Wind dirW  W NW NW NW NW NW NW NW NW NW NW  W  W  W SW SW 
> SW  S'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Wind spd   19 17 10  6  5  5  6 11 12 10  5  3  1  2  1  4  6  
> 8  4'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Wind gust  33 31'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'Clouds CL CL SC FW FW CL CL FW CL CL CL CL FW FW FW FW FW 
> FW SC'
> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
> 'PoP 12hr 20  20   0   
> 0   0'
> Oct  7 14:36:45 server weewx[3014] INFO user.fo

Re: [weewx-user] Parsing some NWS Area Forecast Matrices fails

[John Kline]

Absent a spec on area forecast matrices, and absent any problem reports on 
point forecast matrices, there isn’t much to go on here.

> On Oct 7, 2020, at 2:35 PM, Michael Bruski  wrote:
> 
> 
> Hi John,
> 
> I've looked at several forecast matrices from my local and surrounding NWS 
> forecast offices and haven't seen anything format wise that would lead me to 
> think they would cause a problem for the forecast extension.  I have selected 
> several different AFMs and see they parse fine.  But I ran into this issue 
> with my local AFM and spent several hours trying to track down the cause.   
> The issue is not with the matrix itself but with text preceeding the DTG.   
> To test further, I put a cheap hack into the parse loop so that date2ts() 
> isn't called if the first word in 'line' is 'Including'.  This actually works 
> (in this specific instance) and a valid forecast is produced.  What other 
> lines of text might NWS put in the header preceeding the DTG, I just don't 
> know.The URLs mentioned in forecast.py are dead links so I couldn't find 
> any specifics on decoding the reports.
> 
> I'm not terribly comfortable programming in python so I'm not sure the best 
> approach to work this issue but sending bad data to time.mktime() via 
> date2ts() is probably bad unless there is a way to trap the error.  Not meant 
> to criticize...  just my thoughts on how to make it better.
> 
> Mike/AJ9X
> 
>> On Wednesday, October 7, 2020 at 4:24:56 PM UTC-4 jo...@johnkline.com wrote:
>> Perhaps Area Forecast Matrix responses can’t be treated just like Point 
>> Forecast Matrix responses.  AFMs are only supported to the extent that they 
>> provide an identically formatted response as the PFM response.
>> 
>> What do you know about AFMs and the differences between them and PFMs?
>> 
 On Oct 7, 2020, at 12:18 PM, Michael Bruski  wrote:
 
>>> 
>> 
>>> 
>>> Hi all,
>>> 
>>> First of all, I am running WeeWX 4.1.1 with forecast extension 3.4.0b10.
>>> 
>>> I had recently managed to use a Area Forecast Matrix for one location and 
>>> that is working fine.   Recently I tried to setup a second location to use 
>>> the AFM (different LID and FOID) and it fails to get a forecast even though 
>>> I see it in the web browser using the URL that forecast.py uses.  After 
>>> careful application of some trace print statements, I see the forecast is 
>>> succesfully download from the FOID and that the forecast for the specified 
>>> LID is also located and extracted but nothing gets parsed.  Below is a copy 
>>> of my trace output from the log:
>>> 
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
>>> forecast downloaded successfully from 
>>> 'http://forecast.weather.gov/product.php?site=NWS&product=AFM&format=txt&issuedby=LWX'
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
>>> 'MDZ005-072100-'
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
>>> 'Carroll-'
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
>>> 'Including the cities of Eldersburg and Westminster'
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: '137 
>>> PM EDT Wed Oct 7 2020'
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
>>> 'Date Wed 10/07/20Thu 10/08/20Fri 
>>> 10/09/20'
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'EDT 
>>> 3hrly 05 08 11 14 17 20 23 02 05 08 11 14 17 20 23 02 05 08 11 14 17 20'
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'UTC 
>>> 3hrly 09 12 15 18 21 00 03 06 09 12 15 18 21 00 03 06 09 12 15 18 21 00'
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
>>> 'Max/Min75 77 8047 48 5265 67 7042 44 4868 
>>> 70 73'
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
>>> 'Temp   76 76 68 61 56 51 50 60 65 64 55 50 47 45 45 61 68 
>>> 67 59'
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
>>> 'Dewpt  52 52 53 50 48 46 45 45 43 42 43 42 41 40 41 45 45 
>>> 46 47'
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 'RH  
>>>43 43 59 67 74 83 83 58 45 45 64 74 79 82 86 56 43 47 64'
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
>>> 'Wind dirW  W NW NW NW NW NW NW NW NW NW NW  W  W  W SW SW 
>>> SW  S'
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
>>> 'Wind spd   19 17 10  6  5  5  6 11 12 10  5  3  1  2  1  4  6  
>>> 8  4'
>>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: 
>>> 'Wind gust  33 31'
>>> Oct  7 14:

Re: [weewx-user] Cumulated bars

[Tom Keffer]

Are you sure you are looking at a new image? Images do not get refreshed
any longer than their aggregation interval, which, in this case, would be
once a week.

Delete the image, wait for the next reporting cycle.

On Wed, Oct 7, 2020 at 1:42 PM Invisible Man 
wrote:

> Hmmm... looks like it doesn't change anything... ?
>
>[[[yearrain]]]
> yscale = None, None, 0.02
> plot_type = bar
> rain
> aggregate_type = cumulative
> # aggregate_interval = 2629800 # Magic number: the length
> of a nominal month
> aggregate_interval = 604800# == 1 week
> label = Rain (weekly total)
>
>
> On Wednesday, October 7, 2020 at 1:40:39 AM UTC+2 tke...@gmail.com wrote:
>
>> Try
>>
>>  aggregate_type = cumulative
>>
>>
>>
>>
>> On Tue, Oct 6, 2020 at 11:49 AM Invisible Man 
>> wrote:
>>
>>> Hello,
>>>
>>> In Weewx, is it possible to generate a graph with cumulated bars? For
>>> example, for year's rain, you'd see rain in January, then rain of January +
>>> February, then rain of January + February + March etc.
>>>
>>> In skin.conf,  I see this config. But tweaking the aggregate interval
>>> won't help me, because it won't sum the previous months... And plot_type
>>> only has bar, line or vector available.
>>>
>>> So, is this possible ?
>>> Thanks
>>>
>>> [[[yearrain]]]
>>> yscale = None, None, 0.02
>>> plot_type = bar
>>> rain
>>> aggregate_type = sum
>>> # aggregate_interval = 2629800 # Magic number: the
>>> length of a nominal month
>>> aggregate_interval = 604800# == 1 week
>>> label = Rain (weekly total)
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/4cd03028-e945-47b6-8b78-9cca1b22711fn%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/2b314311-1f5f-44e6-ae16-17a6cf6c313cn%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEB24%2BBPUW1DzZ5Pu1Te-63Zk05OiBJ0f86KfD%3D5gvj8EA%40mail.gmail.com.

[weewx-user] Re: Upgrade PWS- WLL or WiFiLogger2?

[jerry...@gmail.com]

Doh!  Didn't work on macOS because I forgot the -u username:password 
argument.  Safari used the login keychain so didn't need it.  Much better 
solution for a shell script.

On Wednesday, October 7, 2020 at 4:45:18 AM UTC-7 mh081...@gmail.com wrote:

> Yes, works with the script from my above reply with curl on raspberry 
> pi4 debian 10 
>
>
>
>
>
>
> jerry...@gmail.com schrieb am Dienstag, 6. Oktober 2020 um 21:01:31 UTC+2:
>
>> I'm curious if the curl command works to restart WiFiLogger2.  I first 
>> tried using the lynx command line browser and it did not resolve the page 
>> correctly and didn't restart.  I assumed that was because the restart page 
>> contains some javascript and lynx doesn't support javascript.  I then 
>> switched to Safari, which has the downside of needing a GUI.  
>>
>> So does curl work in the terminal script?  That's a better solution if it 
>> works.
>>
>> On Tuesday, October 6, 2020 at 6:37:57 AM UTC-7 gary@gmail.com wrote:
>>
>>> Thanks for the Linux version of the script.
>>>
>>> On Tuesday, October 6, 2020 at 4:33:35 AM UTC-4 mh081...@gmail.com 
>>> wrote:
>>>
 Thanks for the script. I changed it to be runnable from raspberry pi 
 (Debian 10.4)

 #!/bin/sh
 # Shell script to restart the weatherLogger wifi device in the Davis 
 Vantage Pro 2 in the Harbormaster Building
 # The weather logger tends to disconnect from network every 4 days 
 causing weewx to crash in a waiting state
 # Currently set to run by rycweather as a cron job once a day at 8:07 
 am.
 # check to see if weatherLogger is connected on Harbormaster vlan
 /bin/ping -c 1 WiFiLogger.fritz.box
 if [ "$?" = "0" ]; then
 weatherLoggerStatus="weatherLogger is online"
 #   Using curl
 curl --connect-timeout 5 --fail 
 http://WiFiLogger.fritz.box/admin/restart
 #   wait to launch and load javascript function of URL
 sleep 30
 else
 weatherLoggerStatus="weatherLogger is OFFLINE"
 fi
 # Check weatherLogger is connected again
 /bin/ping -c 1 WiFiLogger.fritz.box
 if [ "$?" = "0" ]; then
 newWeatherLoggerStatus="weatherlogger is back online"
 else
 newWeatherLoggerStatus="weatherLogger is OFFLINE after restart"
 fi
 echo "$weatherLoggerStatus and after restart $newWeatherLoggerStatus" | 
 sendemail -f mailadr...@mail.com -t mailad...@mail.com -u "WifiLogger 
 Restart" -s mailserver.mail.com -xu "username" -xp "password" -o 
 tls=yes -o message-content-type=auto
 exit


 jerry...@gmail.com schrieb am Dienstag, 6. Oktober 2020 um 09:36:22 
 UTC+2:

> WifiLogger2 doesn't have an ssh port open, but it does respond on port 
> 80 to a restart command from http.  Under macOS I use the shell script 
> command to open the Safair browser to the restart javascript command.
> #!/bin/sh
> # Shell script to restart the weatherLogger wifi device in the Davis 
> Vantage Pro 2 in the Harbormaster Building
> # The weather logger tends to disconnect from network every 4 days 
> causing weewx to crash in a waiting state
> # Currently set to run by rycweather as a cron job once a day at 8:07 
> am.
> # check to see if weatherLogger is connected on Harbormaster vlan
> /sbin/ping -c 1 192.168.145.106
> if [[ "$?" == "0" ]]; then
> weatherLoggerStatus="weatherLogger is online"
> #   Using Safari browser
> open -a Safari http://192.168.145.106/admin/restart
> #   wait for Safari to launch and load javascript function of URL
> sleep 60
> #   close Safari
> killall Safari
> else
> weatherLoggerStatus="weatherLogger is OFFLINE"
> fi
> # Check weatherLogger is connected again
> /sbin/ping -c 1 192.168.145.106
> if [[ "$?" == "0" ]]; then
> newWeatherLoggerStatus="weatherlogger is back online"
> else
> newWeatherLoggerStatus="weatherLogger is OFFLINE after restart"
> fi
> echo "$weatherLoggerStatus and after restart $newWeatherLoggerStatus" 
> | mail -s "weatherLogger restart" xxx
> exit
>
>
> On Tuesday, October 6, 2020 at 12:23:03 AM UTC-7 mh081...@gmail.com 
> wrote:
>
>> Hi,
>>
>> can you provide me this shell script to restart  WifiLogger2  by 
>> cron? How did you connect to WifiLogger2 remotely? I have the same 
>> problem 
>> that WifiLogger2 disconnects from wlan after several days.
>>
>> jerry...@gmail.com schrieb am Dienstag, 6. Oktober 2020 um 09:15:11 
>> UTC+2:
>>
>>> I recently switched from a 3 hop retransmit across 1000 ft by 
>>> multiple Davis Vantage Pro2 links to WiFiLogger2 across an AirMax 
>>> backhaul 
>>> and the weewx server has been running well for several months.  I had 
>>> one 
>>> problem with the WiFiLogger2.  It seemed to disconnect from its vLAN 
>>> network every 4 days or so, whic

Re: [weewx-user] Parsing some NWS Area Forecast Matrices fails

[Ernest Jillson]

Here is the spec on AFMs from the NWS:
https://www.weather.gov/media/notification/dir/AFM_Format.pdf


On Wed, Oct 7, 2020 at 5:57 PM John Kline  wrote:

> Absent a spec on area forecast matrices, and absent any problem reports on
> point forecast matrices, there isn’t much to go on here.
>
> On Oct 7, 2020, at 2:35 PM, Michael Bruski 
> wrote:
>
> 
> Hi John,
>
> I've looked at several forecast matrices from my local and surrounding NWS
> forecast offices and haven't seen anything format wise that would lead me
> to think they would cause a problem for the forecast extension.  I have
> selected several different AFMs and see they parse fine.  But I ran into
> this issue with my local AFM and spent several hours trying to track down
> the cause.   The issue is not with the matrix itself but with text
> preceeding the DTG.   To test further, I put a cheap hack into the parse
> loop so that date2ts() isn't called if the first word in 'line' is
> 'Including'.  This actually works (in this specific instance) and a valid
> forecast is produced.  What other lines of text might NWS put in the header
> preceeding the DTG, I just don't know.The URLs mentioned in forecast.py
> are dead links so I couldn't find any specifics on decoding the reports.
>
> I'm not terribly comfortable programming in python so I'm not sure the
> best approach to work this issue but sending bad data to time.mktime() via
> date2ts() is probably bad unless there is a way to trap the error.  Not
> meant to criticize...  just my thoughts on how to make it better.
>
> Mike/AJ9X
>
> On Wednesday, October 7, 2020 at 4:24:56 PM UTC-4 jo...@johnkline.com
> wrote:
>
>> Perhaps Area Forecast Matrix responses can’t be treated just like Point
>> Forecast Matrix responses.  AFMs are only supported to the extent that they
>> provide an identically formatted response as the PFM response.
>>
>> What do you know about AFMs and the differences between them and PFMs?
>>
>> On Oct 7, 2020, at 12:18 PM, Michael Bruski  wrote:
>>
>> 
>>
>>
>> Hi all,
>>
>> First of all, I am running WeeWX 4.1.1 with forecast extension 3.4.0b10.
>>
>> I had recently managed to use a Area Forecast Matrix for one location and
>> that is working fine.   Recently I tried to setup a second location to use
>> the AFM (different LID and FOID) and it fails to get a forecast even though
>> I see it in the web browser using the URL that forecast.py uses.  After
>> careful application of some trace print statements, I see the forecast is
>> succesfully download from the FOID and that the forecast for the specified
>> LID is also located and extracted but nothing gets parsed.  Below is a copy
>> of my trace output from the log:
>>
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS:
>> forecast downloaded successfully from '
>> http://forecast.weather.gov/product.php?site=NWS&product=AFM&format=txt&issuedby=LWX
>> '
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS:
>> 'MDZ005-072100-'
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS:
>> 'Carroll-'
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS:
>> 'Including the cities of Eldersburg and Westminster'
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS:
>> '137 PM EDT Wed Oct 7 2020'
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS:
>> 'Date Wed 10/07/20Thu 10/08/20Fri
>> 10/09/20'
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS:
>> 'EDT 3hrly 05 08 11 14 17 20 23 02 05 08 11 14 17 20 23 02 05 08 11 14
>> 17 20'
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS:
>> 'UTC 3hrly 09 12 15 18 21 00 03 06 09 12 15 18 21 00 03 06 09 12 15 18
>> 21 00'
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS: ''
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS:
>> 'Max/Min75 77 8047 48 5265 67 7042 44 4868
>> 70 73'
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS:
>> 'Temp   76 76 68 61 56 51 50 60 65 64 55 50 47 45 45 61 68
>> 67 59'
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS:
>> 'Dewpt  52 52 53 50 48 46 45 45 43 42 43 42 41 40 41 45 45
>> 46 47'
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS:
>> 'RH 43 43 59 67 74 83 83 58 45 45 64 74 79 82 86 56 43
>> 47 64'
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS:
>> 'Wind dirW  W NW NW NW NW NW NW NW NW NW NW  W  W  W SW SW
>> SW  S'
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWSThread: NWS:
>> 'Wind spd   19 17 10  6  5  5  6 11 12 10  5  3  1  2  1  4  6
>> 8  4'
>> Oct  7 14:36:45 server weewx[3014] INFO user.forecast: NWST

[weewx-user] Re: My "rain" field adds up

[Susan Mackay]

WeeWx expects the amount of rain since the last packet. Therefore you need 
to remember the last 'rain' value you sent and then subtract that from the 
current reading (and remember the new value for the next packet).
I know you are not using my driver but if you have a look at the HP1000 
driver python source you will see how I handle that for my weather station 
which does the same thing - reports the current daily total each time. 
There are probably many other drivers out there that do the same thing.
Susan

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/382dcf63-076f-4e0f-a37f-929279d54575o%40googlegroups.com.