[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
FYI, there is a detailed explanation of the various rain measurements and why the default sensor map value was chosen in the weewx-atmocom-udp station driver's README file: https://github.com/captain-coredump/weewx-atmocom-udp/blob/master/README Rain Delta Calculations: Weewx likes its "rain" value passed from station drivers to be the amount of rain counted since the last LOOP packet was received. Weather Underground (and clones) receives one or more rainfall totals, based on fixed time periods: rainin dailyrainin weeklyrainin monthlyrainin yearlyrainin While one would hope that "rainin" would be the total since the last packet (like weewx needs), we would not be so lucky. There is actually conflicting information on the web, with some saying that "rainin" is the rain total for the past hour and others saying that it is rain total for the last 60 minutes. Yes, there are 60 minutes in an hour, but saying it is the last 60 minutes implies a sliding time window...and not from when the big hand is on the 12 until it returns to the 12. If that's not confusing enough, the Weather Underground protocol also allows for specifying observation time as "now" for stations without a clock. I'm going to stop here, and take some aspirin to numb the headache I'm getting just thinking about how the station knows when a day/month/year starts with no clock. To give a no-code option for everyone, I have parsed every single rain figure into separate delta variables in the returned LOOP packet: rainindelta dailyrainindelta weeklyrainindelta monthlyrainindelta yearlyrainindelta The default sensor_map entry is created as follows: rain = rainindelta.WUStationID Because of the sliding time window ambiguity with rainin, I strongly suggest editing weewx.conf and mapping rain to yearlyrainindelta or whatever is the longest time period observation your station is sending. I would really, really, really like to set the default as yearlyrainindelta, but fear that there is a station out there without a clock that does not send anything but rainin...and hopefully not as a sliding 60-minute time window! On Sunday, December 15, 2019 at 3:36:19 PM UTC-5, gjr80 wrote: > > I should have clarified, Gabor is exactly right, you originally had the > following in your sensor map: > > rain = rainindelta.ITEHKUMM2 > > this uses a synthetic rainindelta field created by the driver based on the > WU rainin. You need use a similar synthetic field based on dailyrainin (or > some other cumulative rain field). Such a map would be: > > rain = dailyrainindelta.ITEHKUMM2 > > Gary > > -- 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/696853be-fa73-4824-b5e2-1f12a3019e8f%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
I should have clarified, Gabor is exactly right, you originally had the following in your sensor map: rain = rainindelta.ITEHKUMM2 this uses a synthetic rainindelta field created by the driver based on the WU rainin. You need use a similar synthetic field based on dailyrainin (or some other cumulative rain field). Such a map would be: rain = dailyrainindelta.ITEHKUMM2 Gary -- 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/88b354fa-d61b-4e84-963d-94eb0aff07a7%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Thanks for spending all this time in looking at this issue.
As mentioned to Gabor, dailyrainin may have created a phantom rain event so
I am trying dailyrainindelta.
This looks promising as I did another experiment and dumped water in the
rain gauge to simulate a rain event. and weewx reported 1 mm (Rain Today)
I'll try doing another simulated rainfall except it is -6C at the moment!
--
On Sunday, December 15, 2019 at 1:44:29 AM UTC-5, gjr80 wrote:
>
> Glenn,
>
> I've spent some time working through the atmocom driver and I think I have
> a basic understanding of it now. You are correct in that you need to map
> run to dailyrainin (or one of the other cumulative rain fields).
>
> Your sensor map is using fields from the WU posts so you can ignore the
> Ambient posts (whether you continue to allow your station to post to
> Ambient is up to you, in your current config WeeWX will do nothing with the
> Ambient data). As far as WU is concerned rainin is the rainfall occurring
> in the last hour, you could consider this to be the rain rate. When mapping
> rainin to WeeWX field rain the atmocom driver attempts to take the delta
> between successive rainin values to determine the rainfall in the period.
> This works fine for a source data field that holds the cumulative rain such
> as a daily or yearly rain total but the problem with using rainin as a
> source is that since it is rainfall over the last hour you have rainfall
> dropping off because it fell over an hour ago and rainfall being added that
> just fell in the last period. It is impossible to tell the rainfall in the
> last period without some complexing processing. If you did use rainin
> everything would be fine while there is no rain but once it does start
> raining you will see your rain data going all over the place, certainly not
> something that can be fixed by a simple scaling factor (as you found out).
>
> Try changing you sensor map, restart WeeWX and then either manually
> stimulate your rain gauge or wait for some rain.
>
> One you get some consistent/explainable rain data you may well still have
> a units problem (reading the driver code it is not very units aware) but
> hopefully this will only be a display issue rather than an underlying data
> issue.
>
> Gary
>
> On Sunday, 15 December 2019 13:43:39 UTC+10, Glenn Szlagowski wrote:
>>
>> Success!
>> Thanks for your help-greatly appreciated!
>>
>> There are two types of packets..looks like one goes to ambient weather
>> and the other one goes to WU. Interestingly only every fourth packet goes
>> to ambient.
>>
>> Note that the ambient packet contains extra fields.
>>
>> Here are some samples (sans passwords):
>>
>> Dec 14 21:54:54 glenn weewx[5373]: atmocomudp: MainThread: raw packet:
>> ('passkey=xx=0x2E708=/weatherstation/updateweatherstation.php?ID=ITEHKUMM2=xx=70.5=32.0=29.7=32.0=50=91=1.3=2.2=210=28.84=29.50=0.00=0.04=1.24=1.32=38.87=0.00=0=2019-12-15%202:54:44=AMBWeatherV4.0.2=updateraw=1=5
>>
>> ', ('192.168.1.8', 12000))
>>
>> Dec 14 21:55:33 glenn weewx[5373]: atmocomudp: MainThread: raw packet:
>> ('passkey=xx=0x2E708=/endpoint?stationtype=AMBWeatherV4.0.2=xx=2019-12-15+02:55:32=330=1.3=2.2=11.4=32.0=0.00=0.04=0.04=1.24=1.32=38.87=29.51=28.85=92=70.5=50=0=0.00
>>
>> ', ('192.168.1.8', 12000))
>>
>> If I change the ATMOCOM sensor mapping to dailyrainin, would that work?
>>
>> ---
>>
>>
>> On Saturday, December 14, 2019 at 7:17:57 PM UTC-5, gjr80 wrote:
>>>
>>> Glenn,
>>>
>>> Ok, I see the raw packet issue (should have seen it before actually).
>>> Are you up for making a slight change to atmocomudp.py? If so first make a
>>> backup copy of /usr/share/weewx/user/atmocomudp.py then open
>>> /usr/share/weewx/user/atmocomudp.py in a text editor and change line 283
>>> from:
>>>
>>> loginf('raw packet: %s' % m)
>>>
>>> to
>>>
>>> loginf('raw packet: %s' % (m,))
>>>
>>> Save atmocomudp.py, set log_raw_packets = True in weeewx.conf and
>>> restart WeeWX. Check your log.
>>>
>>> Gary
>>>
>>>
>>>
--
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/9e8439ed-a557-43ff-8501-63c40bc6a3f8%40googlegroups.com.
Re: [weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Thanks Gabor for your help on this.
The ATMOCOM driver allows you to use WU sensor mapping or the Ambient
mapping if you have a Fine Offset or clone weather station ( but not both)
so I should be OK.
dailyrainin created a 2 separate hourly unrealistic high rainfall> 200mm
just before midnight last night so something went awry there. My other
machine recorded no such rain event. I will try the dailyrainindelta as you
have suggested.
The ATMOCOM hardware device inventor supports a custom weather34 weather
template that works pretty good but he does not specialize in anything
related to weewx.
I may have to contact the developer of the ATMOCOM weewx udp driver (he's
on gitHub) if we can't figure things out here.
---
--
On Sunday, December 15, 2019 at 1:00:42 AM UTC-5, Gábor Szabados wrote:
>
> Hi Glenn,
>
> I would uses the dailyrainin. I had an issue once during a storm, when a
> power outage occurred, that the internal unit forgot the yearlyrainin value
> and set it back not to 0 but some earlier state of the week/month. I could
> work, but if the two packets has different values that can cause different
> issues, similar what I have explained before.
>
> Probably your best solution is to turn off one of your services in the
> weather station. (WU or Ambient) Do a run for a short time and see what
> happens then when you do the same test.
>
> Or you can send a mail to the guy who developed ATMOCOM, asking what is
> the solution for this problem. It really should interpret only one of the
> packets and not both. Probaly WU is the better choice.
>
> Best Regards,
>
> Gabor Szabados
>
> Glenn Szlagowski > ezt írta (időpont:
> 2019. dec. 15., Vas 4:43):
>
>> Success!
>> Thanks for your help-greatly appreciated!
>>
>> There are two types of packets..looks like one goes to ambient weather
>> and the other one goes to WU. Interestingly only every fourth packet goes
>> to ambient.
>>
>> Note that the ambient packet contains extra fields.
>>
>> Here are some samples (sans passwords):
>>
>> Dec 14 21:54:54 glenn weewx[5373]: atmocomudp: MainThread: raw packet:
>> ('passkey=xx=0x2E708=/weatherstation/updateweatherstation.php?ID=ITEHKUMM2=xx=70.5=32.0=29.7=32.0=50=91=1.3=2.2=210=28.84=29.50=0.00=0.04=1.24=1.32=38.87=0.00=0=2019-12-15%202:54:44=AMBWeatherV4.0.2=updateraw=1=5
>>
>> ', ('192.168.1.8', 12000))
>>
>> Dec 14 21:55:33 glenn weewx[5373]: atmocomudp: MainThread: raw packet:
>> ('passkey=xx=0x2E708=/endpoint?stationtype=AMBWeatherV4.0.2=xx=2019-12-15+02:55:32=330=1.3=2.2=11.4=32.0=0.00=0.04=0.04=1.24=1.32=38.87=29.51=28.85=92=70.5=50=0=0.00
>>
>> ', ('192.168.1.8', 12000))
>>
>> If I change the ATMOCOM sensor mapping to dailyrainin, would that work?
>>
>> ---
>>
>>
>> On Saturday, December 14, 2019 at 7:17:57 PM UTC-5, gjr80 wrote:
>>>
>>> Glenn,
>>>
>>> Ok, I see the raw packet issue (should have seen it before actually).
>>> Are you up for making a slight change to atmocomudp.py? If so first make a
>>> backup copy of /usr/share/weewx/user/atmocomudp.py then open
>>> /usr/share/weewx/user/atmocomudp.py in a text editor and change line 283
>>> from:
>>>
>>> loginf('raw packet: %s' % m)
>>>
>>> to
>>>
>>> loginf('raw packet: %s' % (m,))
>>>
>>> Save atmocomudp.py, set log_raw_packets = True in weeewx.conf and
>>> restart WeeWX. Check your log.
>>>
>>> Gary
>>>
>>>
>>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/3f3zakgAEOc/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx...@googlegroups.com .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/f9f3fc89-4b12-44fb-aff0-b34f1bb48f88%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/096eba32-1817-471c-9e5e-d97c12eab571%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Glenn,
I've spent some time working through the atmocom driver and I think I have
a basic understanding of it now. You are correct in that you need to map
run to dailyrainin (or one of the other cumulative rain fields).
Your sensor map is using fields from the WU posts so you can ignore the
Ambient posts (whether you continue to allow your station to post to
Ambient is up to you, in your current config WeeWX will do nothing with the
Ambient data). As far as WU is concerned rainin is the rainfall occurring
in the last hour, you could consider this to be the rain rate. When mapping
rainin to WeeWX field rain the atmocom driver attempts to take the delta
between successive rainin values to determine the rainfall in the period.
This works fine for a source data field that holds the cumulative rain such
as a daily or yearly rain total but the problem with using rainin as a
source is that since it is rainfall over the last hour you have rainfall
dropping off because it fell over an hour ago and rainfall being added that
just fell in the last period. It is impossible to tell the rainfall in the
last period without some complexing processing. If you did use rainin
everything would be fine while there is no rain but once it does start
raining you will see your rain data going all over the place, certainly not
something that can be fixed by a simple scaling factor (as you found out).
Try changing you sensor map, restart WeeWX and then either manually
stimulate your rain gauge or wait for some rain.
One you get some consistent/explainable rain data you may well still have a
units problem (reading the driver code it is not very units aware) but
hopefully this will only be a display issue rather than an underlying data
issue.
Gary
On Sunday, 15 December 2019 13:43:39 UTC+10, Glenn Szlagowski wrote:
>
> Success!
> Thanks for your help-greatly appreciated!
>
> There are two types of packets..looks like one goes to ambient weather and
> the other one goes to WU. Interestingly only every fourth packet goes to
> ambient.
>
> Note that the ambient packet contains extra fields.
>
> Here are some samples (sans passwords):
>
> Dec 14 21:54:54 glenn weewx[5373]: atmocomudp: MainThread: raw packet:
> ('passkey=xx=0x2E708=/weatherstation/updateweatherstation.php?ID=ITEHKUMM2=xx=70.5=32.0=29.7=32.0=50=91=1.3=2.2=210=28.84=29.50=0.00=0.04=1.24=1.32=38.87=0.00=0=2019-12-15%202:54:44=AMBWeatherV4.0.2=updateraw=1=5
>
> ', ('192.168.1.8', 12000))
>
> Dec 14 21:55:33 glenn weewx[5373]: atmocomudp: MainThread: raw packet:
> ('passkey=xx=0x2E708=/endpoint?stationtype=AMBWeatherV4.0.2=xx=2019-12-15+02:55:32=330=1.3=2.2=11.4=32.0=0.00=0.04=0.04=1.24=1.32=38.87=29.51=28.85=92=70.5=50=0=0.00
>
> ', ('192.168.1.8', 12000))
>
> If I change the ATMOCOM sensor mapping to dailyrainin, would that work?
>
> ---
>
>
> On Saturday, December 14, 2019 at 7:17:57 PM UTC-5, gjr80 wrote:
>>
>> Glenn,
>>
>> Ok, I see the raw packet issue (should have seen it before actually).
>> Are you up for making a slight change to atmocomudp.py? If so first make a
>> backup copy of /usr/share/weewx/user/atmocomudp.py then open
>> /usr/share/weewx/user/atmocomudp.py in a text editor and change line 283
>> from:
>>
>> loginf('raw packet: %s' % m)
>>
>> to
>>
>> loginf('raw packet: %s' % (m,))
>>
>> Save atmocomudp.py, set log_raw_packets = True in weeewx.conf and restart
>> WeeWX. Check your log.
>>
>> Gary
>>
>>
>>
--
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/dc566dbb-7b97-41a0-9e0a-95146384237d%40googlegroups.com.
Re: [weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Glenn,
It should be dailyrainindelta.
Best Regards,
Gabor
Gábor Szabados ezt írta (időpont: 2019.
dec. 15., Vas 7:00):
> Hi Glenn,
>
> I would uses the dailyrainin. I had an issue once during a storm, when a
> power outage occurred, that the internal unit forgot the yearlyrainin value
> and set it back not to 0 but some earlier state of the week/month. I could
> work, but if the two packets has different values that can cause different
> issues, similar what I have explained before.
>
> Probably your best solution is to turn off one of your services in the
> weather station. (WU or Ambient) Do a run for a short time and see what
> happens then when you do the same test.
>
> Or you can send a mail to the guy who developed ATMOCOM, asking what is
> the solution for this problem. It really should interpret only one of the
> packets and not both. Probaly WU is the better choice.
>
> Best Regards,
>
> Gabor Szabados
>
> Glenn Szlagowski ezt írta (időpont: 2019. dec.
> 15., Vas 4:43):
>
>> Success!
>> Thanks for your help-greatly appreciated!
>>
>> There are two types of packets..looks like one goes to ambient weather
>> and the other one goes to WU. Interestingly only every fourth packet goes
>> to ambient.
>>
>> Note that the ambient packet contains extra fields.
>>
>> Here are some samples (sans passwords):
>>
>> Dec 14 21:54:54 glenn weewx[5373]: atmocomudp: MainThread: raw packet:
>> ('passkey=xx=0x2E708=/weatherstation/updateweatherstation.php?ID=ITEHKUMM2=xx=70.5=32.0=29.7=32.0=50=91=1.3=2.2=210=28.84=29.50=0.00=0.04=1.24=1.32=38.87=0.00=0=2019-12-15%202:54:44=AMBWeatherV4.0.2=updateraw=1=5
>> ', ('192.168.1.8', 12000))
>>
>> Dec 14 21:55:33 glenn weewx[5373]: atmocomudp: MainThread: raw packet:
>> ('passkey=xx=0x2E708=/endpoint?stationtype=AMBWeatherV4.0.2=xx=2019-12-15+02:55:32=330=1.3=2.2=11.4=32.0=0.00=0.04=0.04=1.24=1.32=38.87=29.51=28.85=92=70.5=50=0=0.00
>> ', ('192.168.1.8', 12000))
>>
>> If I change the ATMOCOM sensor mapping to dailyrainin, would that work?
>>
>> ---
>>
>>
>> On Saturday, December 14, 2019 at 7:17:57 PM UTC-5, gjr80 wrote:
>>>
>>> Glenn,
>>>
>>> Ok, I see the raw packet issue (should have seen it before actually).
>>> Are you up for making a slight change to atmocomudp.py? If so first make a
>>> backup copy of /usr/share/weewx/user/atmocomudp.py then open
>>> /usr/share/weewx/user/atmocomudp.py in a text editor and change line 283
>>> from:
>>>
>>> loginf('raw packet: %s' % m)
>>>
>>> to
>>>
>>> loginf('raw packet: %s' % (m,))
>>>
>>> Save atmocomudp.py, set log_raw_packets = True in weeewx.conf and
>>> restart WeeWX. Check your log.
>>>
>>> Gary
>>>
>>>
>>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/3f3zakgAEOc/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/f9f3fc89-4b12-44fb-aff0-b34f1bb48f88%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/CAEx3znLNDbhti8svmND4OEST22aM9E-686_NHktfJO%3DySqqFnQ%40mail.gmail.com.
Re: [weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Hi Glenn,
I would uses the dailyrainin. I had an issue once during a storm, when a
power outage occurred, that the internal unit forgot the yearlyrainin value
and set it back not to 0 but some earlier state of the week/month. I could
work, but if the two packets has different values that can cause different
issues, similar what I have explained before.
Probably your best solution is to turn off one of your services in the
weather station. (WU or Ambient) Do a run for a short time and see what
happens then when you do the same test.
Or you can send a mail to the guy who developed ATMOCOM, asking what is the
solution for this problem. It really should interpret only one of the
packets and not both. Probaly WU is the better choice.
Best Regards,
Gabor Szabados
Glenn Szlagowski ezt írta (időpont: 2019. dec. 15.,
Vas 4:43):
> Success!
> Thanks for your help-greatly appreciated!
>
> There are two types of packets..looks like one goes to ambient weather and
> the other one goes to WU. Interestingly only every fourth packet goes to
> ambient.
>
> Note that the ambient packet contains extra fields.
>
> Here are some samples (sans passwords):
>
> Dec 14 21:54:54 glenn weewx[5373]: atmocomudp: MainThread: raw packet:
> ('passkey=xx=0x2E708=/weatherstation/updateweatherstation.php?ID=ITEHKUMM2=xx=70.5=32.0=29.7=32.0=50=91=1.3=2.2=210=28.84=29.50=0.00=0.04=1.24=1.32=38.87=0.00=0=2019-12-15%202:54:44=AMBWeatherV4.0.2=updateraw=1=5
> ', ('192.168.1.8', 12000))
>
> Dec 14 21:55:33 glenn weewx[5373]: atmocomudp: MainThread: raw packet:
> ('passkey=xx=0x2E708=/endpoint?stationtype=AMBWeatherV4.0.2=xx=2019-12-15+02:55:32=330=1.3=2.2=11.4=32.0=0.00=0.04=0.04=1.24=1.32=38.87=29.51=28.85=92=70.5=50=0=0.00
> ', ('192.168.1.8', 12000))
>
> If I change the ATMOCOM sensor mapping to dailyrainin, would that work?
>
> ---
>
>
> On Saturday, December 14, 2019 at 7:17:57 PM UTC-5, gjr80 wrote:
>>
>> Glenn,
>>
>> Ok, I see the raw packet issue (should have seen it before actually).
>> Are you up for making a slight change to atmocomudp.py? If so first make a
>> backup copy of /usr/share/weewx/user/atmocomudp.py then open
>> /usr/share/weewx/user/atmocomudp.py in a text editor and change line 283
>> from:
>>
>> loginf('raw packet: %s' % m)
>>
>> to
>>
>> loginf('raw packet: %s' % (m,))
>>
>> Save atmocomudp.py, set log_raw_packets = True in weeewx.conf and restart
>> WeeWX. Check your log.
>>
>> Gary
>>
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/3f3zakgAEOc/unsubscribe.
> To unsubscribe from this group and all its topics, 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/f9f3fc89-4b12-44fb-aff0-b34f1bb48f88%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/CAEx3zn%2BKfH065qhPMGf1Kf9MPP_3418LeKYPhk5_zzMNwRiVmA%40mail.gmail.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Success!
Thanks for your help-greatly appreciated!
There are two types of packets..looks like one goes to ambient weather and
the other one goes to WU. Interestingly only every fourth packet goes to
ambient.
Note that the ambient packet contains extra fields.
Here are some samples (sans passwords):
Dec 14 21:54:54 glenn weewx[5373]: atmocomudp: MainThread: raw packet:
('passkey=xx=0x2E708=/weatherstation/updateweatherstation.php?ID=ITEHKUMM2=xx=70.5=32.0=29.7=32.0=50=91=1.3=2.2=210=28.84=29.50=0.00=0.04=1.24=1.32=38.87=0.00=0=2019-12-15%202:54:44=AMBWeatherV4.0.2=updateraw=1=5
', ('192.168.1.8', 12000))
Dec 14 21:55:33 glenn weewx[5373]: atmocomudp: MainThread: raw packet:
('passkey=xx=0x2E708=/endpoint?stationtype=AMBWeatherV4.0.2=xx=2019-12-15+02:55:32=330=1.3=2.2=11.4=32.0=0.00=0.04=0.04=1.24=1.32=38.87=29.51=28.85=92=70.5=50=0=0.00
', ('192.168.1.8', 12000))
If I change the ATMOCOM sensor mapping to dailyrainin, would that work?
---
On Saturday, December 14, 2019 at 7:17:57 PM UTC-5, gjr80 wrote:
>
> Glenn,
>
> Ok, I see the raw packet issue (should have seen it before actually). Are
> you up for making a slight change to atmocomudp.py? If so first make a
> backup copy of /usr/share/weewx/user/atmocomudp.py then open
> /usr/share/weewx/user/atmocomudp.py in a text editor and change line 283
> from:
>
> loginf('raw packet: %s' % m)
>
> to
>
> loginf('raw packet: %s' % (m,))
>
> Save atmocomudp.py, set log_raw_packets = True in weeewx.conf and restart
> WeeWX. Check your log.
>
> Gary
>
>
>
--
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/f9f3fc89-4b12-44fb-aff0-b34f1bb48f88%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Glenn,
Ok, I see the raw packet issue (should have seen it before actually). Are you
up for making a slight change to atmocomudp.py? If so first make a backup copy
of /usr/share/weewx/user/atmocomudp.py then open
/usr/share/weewx/user/atmocomudp.py in a text editor and change line 283 from:
loginf('raw packet: %s' % m)
to
loginf('raw packet: %s' % (m,))
Save atmocomudp.py, set log_raw_packets = True in weeewx.conf and restart
WeeWX. Check your log.
Gary
--
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/ab3729f2-9f8c-4835-8ac3-9a17cc2effad%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
I ran the ATMOCOM data logger/parser and this is what it is seeing.(see
below)
This should be in WU format and it looks like it is in all US units.
The 0.04 inches of rain is about 1 mm which is what I dumped into the rain
gauge this morning.
I have edited things for readability.
('192.168.1.8', 12000) b'passkey=xx&
rev=0x2E708&
data=/weatherstation/updateweatherstation.php?ID=ITEHKUMM2&
PASSWORD=xx&
indoortempf=72.1&
tempf=34.2&
dewptf=33.8&
windchillf=34.2&
indoorhumidity=49&
humidity=99&
windspeedmph=0.2&
windgustmph=1.1&
winddir=56&
absbaromin=28.92&
baromin=29.58&
rainin=0.00&
dailyrainin=0.04&
weeklyrainin=1.24&
monthlyrainin=1.32&
yearlyrainin=38.87&
solarradiation=73.65&
UV=0&
dateutc=2019-12-14%2016:45:2&
softwaretype=AMBWeatherV4.0.2&
action=updateraw&
realtime=1&
rtfreq=5 '
On Saturday, December 14, 2019 at 3:44:17 PM UTC-5, gjr80 wrote:
>
> Hi,
>
> I think you are going to need to see those raw packets to fix this. I just
> looked at the driver code and the log raw packets code is pretty basic.
> When you set log_raw_packets = True what do you see in the log? This part
> should be easy to fix.
>
> When posting the log make sure you include from WeeWX startup through
> until the error hits.
>
> Gary
>
>
--
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/c97cd089-21fd-46cf-a9e4-4141e877e53b%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Hi Gary,
Thanks for your help.
Getting the log entries was hard fought as the usual sudo tail -f
/var/log/syslog was stopped dead in its tracks.
I managed to get the following from Ubuntu:
6:09:18 glenn weewx[1134]: engine: Main loop exiting. Shutting engine down.
Dec 14 16:09:18 glenn weewx[1134]: engine: Caught unrecoverable exception in
engine:
Dec 14 16:09:18 glenn weewx[1134]: not all arguments converted during
string formatting
Dec 14 16:09:18 glenn weewx[1134]: Traceback (most recent call last):
Dec 14 16:09:18 glenn weewx[1134]: File
"/usr/share/weewx/weewx/engine.py", line 894, in main
Dec 14 16:09:18 glenn weewx[1134]: engine.run()
Dec 14 16:09:18 glenn weewx[1134]: File
"/usr/share/weewx/weewx/engine.py", line 188, in run
Dec 14 16:09:18 glenn weewx[1134]: for packet in
self.console.genLoopPackets():
Dec 14 16:09:18 glenn weewx[1134]: File
"/usr/share/weewx/user/atmocomudp.py", line 283, in genLoopPackets
Dec 14 16:09:18 glenn weewx[1134]: loginf('raw packet: %s' % m)
Dec 14 16:09:18 glenn weewx[1134]: TypeError: not all arguments
converted during string formatting
Dec 14 16:09:18 glenn weewx[1134]: Exiting.
---
On Saturday, December 14, 2019 at 3:44:17 PM UTC-5, gjr80 wrote:
>
> Hi,
>
> I think you are going to need to see those raw packets to fix this. I just
> looked at the driver code and the log raw packets code is pretty basic.
> When you set log_raw_packets = True what do you see in the log? This part
> should be easy to fix.
>
> When posting the log make sure you include from WeeWX startup through
> until the error hits.
>
> Gary
>
>
--
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/cab1cb56-4988-4c77-a6e1-34e9e4b6fec7%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Hi, I think you are going to need to see those raw packets to fix this. I just looked at the driver code and the log raw packets code is pretty basic. When you set log_raw_packets = True what do you see in the log? This part should be easy to fix. When posting the log make sure you include from WeeWX startup through until the error hits. Gary -- 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/23787fac-fffd-4197-8203-e69f4bdc1b64%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Hi Gabor Thanks for your help. I just came in from outside after tipping about a 1 ml of water into my rain gauge as an experiment. I wanted to see what my test bed weewx would report. On the rpi it shows 6.1 mm and on my old linux notebook it showed the identical 6.1 mm rain...a fail once again.. Considering that my weather station is 3m above the ground, I taped a measuring cup onto a long pole and tipped the water in. You mentioned that there was a possibility of an extended rain event that might alter the rain data so I checked out one of my weather templates. Charting is done by WU: [image: Capture.PNG] Note on the chart that rain is 1 ml and rain rate is 6.1 mm. Could it be that weewx is reporting *rain rate* instead of *daily rain*? [image: weewx capture.PNG] We can assume WU is correct because it corresponds to what my weather station display console is showing. Here is the ATMOCOM driver in weewx_conf: AtmocomUDP] driver = user.atmocomudp udp_address = 0.0.0.0 udp_port = 12000 udp_timeout = 90 share_socket = True station_units = weewx.US log_raw_packets = False [[sensor_map]] outTemp = tempf.ITEHKUMM2 outHumidity = humidity.ITEHKUMM2 UV = UV.ITEHKUMM2 radiation = solarradiation.ITEHKUMM2 *rain = rainindelta.ITEHKUMM2* windDir = winddir.ITEHKUMM2 pressure = absbaromin.ITEHKUMM2 windSpeed = windspeedmph.ITEHKUMM2 inHumidity = indoorhumidity.ITEHKUMM2 inTemp = indoortempf.ITEHKUMM2 windGust = windgustmph.ITEHKUMM2 Unfortunately when I try to enable log raw packets weewx crashes so I can't determine the correct header for daily rain or total rain. --- On Saturday, December 14, 2019 at 10:08:02 AM UTC-5, Gábor Szabados wrote: > > Hi, > > Look at the days when you see rain. Does it distribute the same way on > WeeWX and WU? > > Let's say WU is correct and the ATMOCOM driver has an issue. So WeeWX > receives a wrong value or amount of values. > > I have seen before with interceptor, that it has received old packets for > some reason. It caused the daily total rain value to jump let's say from > 0.3 to 0.2 what shouldn't happen in reality. The Interceptor driver was > written to handle it as a change of day or change of year, it wasn't > expecting similar in any other case. The worst part was that when from 0.2 > it received a 0.3 value, so it has triggered another +0.1 for WeeWX's daily > count. It caused the WeeWX values to increase/change in a different way > than the WU values. > WU showed the rain stopped at 10AM, meanwhile WeeWX showed rain all day > long. > > Solution in my case was to add an extra line to the interceptor to check > time stamps of the packets and refuse the old ones to be processed. > > Best Regards, > > Gabor Szabados > > -- 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/1876fb7c-ff38-4180-8337-e2ceaf919ad3%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Hi, Look at the days when you see rain. Does it distribute the same way on WeeWX and WU? Let's say WU is correct and the ATMOCOM driver has an issue. So WeeWX receives a wrong value or amount of values. I have seen before with interceptor, that it has received old packets for some reason. It caused the daily total rain value to jump let's say from 0.3 to 0.2 what shouldn't happen in reality. The Interceptor driver was written to handle it as a change of day or change of year, it wasn't expecting similar in any other case. The worst part was that when from 0.2 it received a 0.3 value, so it has triggered another +0.1 for WeeWX's daily count. It caused the WeeWX values to increase/change in a different way than the WU values. WU showed the rain stopped at 10AM, meanwhile WeeWX showed rain all day long. Solution in my case was to add an extra line to the interceptor to check time stamps of the packets and refuse the old ones to be processed. Best Regards, Gabor Szabados -- 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/b8ae24e5-0303-4dc0-b458-1fa066c026e9%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
.Already have done a fresh install on the rpi..a few times, and the result is the same - rain is way too high.. I do have my old test bed weewx 3.9.1 running on another machine under Ubuntu 18.04. I have disabled ftp uploads to my web host and there is just the ATMOCOM driver running locally. It will be difficult to get some liquid water to test as we are solidly in winter now. Might get some snowmelt in the rain gauge today if I'm lucky. Will report back. -- On Wednesday, December 11, 2019 at 11:52:04 PM UTC-5, Michi Kaa wrote: > > And: only th Pi should query the station in this test period, no other > applicaton or service. > -- 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/7ee855d7-96d2-4af5-bfa3-e80e2a67e506%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
And: only th Pi should query the station in this test period, no other applicaton or service. -- 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/7a4cf088-6cbb-4918-8c57-bb56ab117dbd%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Given the clarification that all data is from the same source, my first approach is invalid. The next thing to try is to run the station from a fresh vanilla weewx installation without anything else and sie what happens. With a (second) raspberryPi (who doesn't have at least half a dozwn raspberries at home? ;) ) thats a matter of minutes (ok, an hour or so) -- 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/aa97e33e-75c3-4bf9-a225-85d4175e56b5%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
A word of advice, be very, very careful if taking this approach to correct an apparently wrong observation. Whilst the resulting number may be correct for that particular observation such a correction may well result in errors being introduced elsewhere. If a driver is reporting an incorrectly converted or scaled observation the correct (and safe) solution is to fix the driver. Gary On Wednesday, 11 December 2019 18:26:32 UTC+10, Michi Kaa wrote: > Take your and the other Measurements (which, I suppose, are measure on > another place nearby, where the real amount of rainfall may vary to your > place more or less) yout measurements are off with ~factor 10. > > so you could configure: > > [StdCalibrate] > > [[Corrections]] > > rain = rain / 10 > > -- 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/9e945990-1f50-4557-96ca-514236b6912d%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Uploading to WU and Ambient is done directly from the Ambient WS-2000 hardware console/display. Uploading to Windy and AWEKAS is done through weewx. Weewx also uploads to some of my weather34 templates so if weewx is not reporting rain correctly, any template using weewx is also incorrect. The only accurate template is Ken True's Cumulus template but that one is a special ATMOCOM version. -- On Wednesday, December 11, 2019 at 11:28:48 AM UTC-5, Michi Kaa wrote: > > Ok, so all readings are from the same source. Howare you uploading to WU > an AW? Using weewx? > -- 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/3221b39d-9002-47cb-8f84-50541672e560%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Ok, so all readings are from the same source. Howare you uploading to WU an AW? Using weewx? -- 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/f82abddb-df73-4855-baf3-eb36e3386c49%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Thanks Michi for your help. Good tip for verifying the accuracy of a rain gauge. As a relatively new weewx user (several months), I was wondering how to implement a conversion factor in the config file. My weather station uploads simultaneously to Ambient weather and Weather Underground. Those are the "actual numbers" that I mentioned in my post. Those numbers correspond to what I am seeing on my Ambient Ws-2000 display console. However, i must be overlooking something regarding conversion factors. For instance in the last 3 rain events here is what I got: Ambient Weewxconversion DateRain mm*Rain mmfactor 2019-12-0925.9 352.813.62162162 2019-12-081.810.9 6.05556 2019-12-042.012.2 6.1 * as reported by ambientweather.net The conversion factors are all different so if I put in a conversion factor of 10 what would happen to the weewx reported numbers? Thanks..Glenn -- On Wednesday, December 11, 2019 at 3:26:32 AM UTC-5, Michi Kaa wrote: > > Take your and the other Measurements (which, I suppose, are measure on > another place nearby, where the real amount of rainfall may vary to your > place more or less) yout measurements are off with ~factor 10. > > so you could configure: > > [StdCalibrate] > > [[Corrections]] > > rain = rain / 10 > > > If it is really off by a certain factor, you could do so. > > To check that, place a bucket near the rain sensor, then compare your > measure value to the value your sensor delivers. The amount of mm is the > amount of water in liters divided by the area of the opening of the bucket > in square meters. Or the amount of water in kilograms divided by the is the > area of the opening of the bucket in m². > > Am Dienstag, 10. Dezember 2019 14:06:55 UTC+1 schrieb Glenn Szlagowski: >> >> >> comparison of a few weeks rainfall data in Oct 2019: >> >> WEEWXACTUAL >> RAIN RAIN >> --- >> 1.30.25 >> 4.80.76 >> 40.65.84 >> 23.63.05 >> 52.85.33 >> 120.68.64 >> 81.59.14 >> 102.69.14 >> 254.514.48 >> 719.135.81 >> 24.42.54 >> 77.26.86 >> 55.44.32 >> --- >> > -- 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/112964d7-db62-4902-a72d-38e6d63115c2%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Take your and the other Measurements (which, I suppose, are measure on another place nearby, where the real amount of rainfall may vary to your place more or less) yout measurements are off with ~factor 10. so you could configure: [StdCalibrate] [[Corrections]] rain = rain / 10 If it is really off by a certain factor, you could do so. To check that, place a bucket near the rain sensor, then compare your measure value to the value your sensor delivers. The amount of mm is the amount of water in liters divided by the area of the opening of the bucket in square meters. Or the amount of water in kilograms divided by the is the area of the opening of the bucket in m². Am Dienstag, 10. Dezember 2019 14:06:55 UTC+1 schrieb Glenn Szlagowski: > > > comparison of a few weeks rainfall data in Oct 2019: > > WEEWXACTUAL > RAIN RAIN > --- > 1.30.25 > 4.80.76 > 40.65.84 > 23.63.05 > 52.85.33 > 120.68.64 > 81.59.14 > 102.69.14 > 254.514.48 > 719.135.81 > 24.42.54 > 77.26.86 > 55.44.32 > --- > -- 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/81288d12-b42f-44b0-9de6-133613447442%40googlegroups.com.
[weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high
Take your and the other Measurements (which, I suppose, are measure on another place nearby, where the real amount of rainfall may vary to your place more or less) yout measurements are off with ~factor 10. so you could configure: [StdCalibrate] [[Corrections]] rain = rain / 10 If it is really off by a certain factor, you could do so. To check that, place a bucket near the rain sensor, the compare your measure value to the value your sensor delivers. The amount of mm amount of water in liters divided by the is the area of the opening of the bucket in square meters. Or the amount of water in kilograms divided by the is the area of the opening of the bucket in m². Am Dienstag, 10. Dezember 2019 14:06:55 UTC+1 schrieb Glenn Szlagowski: > > > comparison of a few weeks rainfall data in Oct 2019: > > WEEWXACTUAL > RAIN RAIN > --- > 1.30.25 > 4.80.76 > 40.65.84 > 23.63.05 > 52.85.33 > 120.68.64 > 81.59.14 > 102.69.14 > 254.514.48 > 719.135.81 > 24.42.54 > 77.26.86 > 55.44.32 > --- > -- 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/f6e5704b-b83e-478f-998f-db3ca923c55d%40googlegroups.com.
