Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[Gábor Szabados]

Where did you get those values from?

EN 50549-1:2019 far more permissive than you stated.

Here is Fronius' conformity certificate:

https://www.fronius.com/~/downloads/Solar%20Energy/Certificates/SE_CER_Conformity_EN50549_Sweden_Fronius_Inverters_EN.pdf

Or a link to the Hungarian EON's network quality statement (sorry, but this
one is in Hungarian)

https://www.eon.hu/pestmegyeihalozat/tudnivalok/energiakozeli-informaciok/halozatuzemeltetes.html

On Fri, 17 May 2024, 15:06 Karen K,  wrote:

> Gábor Szabados schrieb am Freitag, 17. Mai 2024 um 14:46:55 UTC+2:
>
> As I remember the EU specs is 50Hz +/-1%, so all those look good to me.
>
>
> No. The tolerance is much smaller. +-0.02 Hz (0.04%) is the normal
> operation range. Up to +-0.2 Hz (0.4%) the European electicity
> administration uses standardized and automated processes to stabilize the
> frequency. Outside that range the situation is considered dangerous. Real
> people get involved. Below 49 Hz they start switching off load. Above 50.2
> Hz private photovolatics inverters start reducing power output.
>
>
> --
> 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/HBDfW-ayRyI/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/56185fef-3051-4370-9d19-7b2afabe5ac1n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/56185fef-3051-4370-9d19-7b2afabe5ac1n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAEx3znJs%2BsebxJFu2a26-n4xg9oemkGyjGAKN7YMh5C58qknTQ%40mail.gmail.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[Gábor Szabados]

As I remember the EU specs is 50Hz +/-1%, so all those look good to me.

Regarding the battery and backup socket, I guess that must be a Fronius
Gen24 Plus with a BYD battery, and the socket would be the PV Point. As
just a note, if you don't know it yet, the PV Point socket and the Full
Backup operates at 54Hz. It is not really advertised, but the point of it,
to knock out any other Inverters as they would detect an out-of-spec line
frequency and would shut down.

And if you consider the Enwitec backup box, which as you stated would be
more than a 1000 with installation, there is a cheaper box also on the
market by Keno the SH-GEN24-SZR, but still around 1000 without
installation.

I have one, but have not installed it yet, and felt the need recently when
the operator did a 3+ hours maintenance and all the UPS depleted in the
house.

On Thu, 16 May 2024, 16:56 Karen K,  wrote:

> michael.k...@gmx.at schrieb am Donnerstag, 16. Mai 2024 um 15:46:28 UTC+2:
>
> Since the (public) power grid is part of the hardware your local weewx
> installation is running on, this is far from being off-topic.
>
>
> There are 3 types of UPS available: off-line, stand-by, and on-line. The
> first one is off as long as grid power is available and starts when the
> grid power goes off. The second one is similar, but it is in stand-by. So
> it start faster than the first one. The on-line one separates the grid and
> the output entirely. They are connected by DC only. So this type can
> additionally filter surges etc. The output frequency for the on-line type
> only depends on the internal circuit, while for the off-line and stand-by
> type the output frequency is always the same as the grid frequency.
>
> I use an on-line UPS and hope that will result in less damage in case of
> over-voltage, surges, and lightning strokes.
>
> To compare to Cameron's histogram I did one myself, based on 5 minutes
> averages of the grid frequency (NOT the UPS output frequency):
>
> [image: netzfrequenzhistogramm.png]
>
> This one has the peak at 50.00 Hz.
>
> --
> 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/HBDfW-ayRyI/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/78c65e41-5ac1-4e13-9644-e46beb078147n%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/CAEx3znKcqtDgEtSV%3DFepT-tWLXJO613reTgGx6rfL1hQgPJRqQ%40mail.gmail.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[Gábor Szabados]

Shamefully, running a bit old version of WeeWX, from 2019, on a Raspberry 
Pi Zero W, which has Raspbian and mainly default settings WeeWX. The same 
SD card since. The Pi operates in an interceptor way, it creates a hotspot 
for the weather station which sends all information to WU, WeeWX with 
Interceptor intercepts it, meanwhile the Pi connects to the local network 
by Wifi as well. A bit over complicated, but it was before the FineOffset 
clones were offering a custom URL option in their firmware.

It was a minimum budget project, still runs without any issues. (Knock on 
wood.)

Graham Knights a következőt írta (2024. február 23., péntek, 19:43:49 
UTC+1):

> I've been running weewx on a RPi 3B+ for just over 5 years, but after a 
> couple of other pi's died for various reasons (SD card being one of them), 
> I've moved it to a debian install on a VM in a Windows 10 Pro machine (runs 
> my automation server).  Hardware is a Lenovo ThinkCentre M700 Tiny which I 
> find perfect for running a couple of small linux VM's on it.  Low power, 
> tiny, quiet, and versatile, and Lenovo hardware has been good to me over 
> the years. Machines are cheap to find on ebay/amazon, probably less than a 
> new Pi by the time you add all the parts.
>
> On Friday, February 23, 2024 at 9:46:42 AM UTC-8 vince wrote:
>
>> If I was starting clean 'today', I would probably just throw $125 at it 
>> and get one of those little beelink boxes amazon sells and toss linux on it.
>>
>> But to answer - currently on a 4GB pi4 to sd card for 2+ years with no 
>> issues.
>>
>> Stability issues on a pi are almost always bad power supply these days. 
>>  I've never had a micro-sd fail on a pi3, 3+, 4, or pi5.  Never.   I did 
>> burn a 'lot' of big sd cards on the old modelB over the years but again 
>> that was related to either (a) cheapo cards or (b) cheapo power adaptors 
>> not on surge suppressors.  My one remaining modelB is still happily 
>> shooting my timelapse snaps for over a decade now.
>>
>> I do make one change to the pi setups to protect the sd card.  I mount 
>> some filesystems as tmpfs so the sd can't be hammered by log writes by 
>> appending this to /etc/stab
>>
>> # put logs and tmp dirs in ramdisk too ---
>> tmpfs   /tmptmpfs   
>> defaults,nosuid,mode=0755,nodev,noatime   0   0
>> tmpfs   /var/logtmpfs   
>> defaults,nosuid,mode=0755,nodev,noatime   0   0
>> tmpfs   /var/tmptmpfs   
>> defaults,nosuid,mode=0755,nodev,noatime   0   0
>> #-
>>
>> Yes - if I reboot I lose the system logs.  But I basically never reboot.
>>
>> I might add that I do install rsyslog and the matching logrotate.d and 
>> rsyslog.d files from util/ to my v5 setup, so weewx logs to under 
>> /var/log/weewx in that tmpfs partition, so I just run debug=1 here because 
>> it's not going to touch the actual sd card.  Super stable.
>>
>>

-- 
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/86c8becf-edfb-4264-b93f-2626ed9adfacn%40googlegroups.com.

[weewx-user] Connecting Froggit WH2600SE to Weewx - Setup always fails :(

[Gábor Szabados]

Hi,

Try to remove address = 192.168.1.122. If it is still not working, then set the 
observerIP back to the default port and remove the port settings from the weewx 
config too.

If you read the interceptor manuals, you can see that interceptor can be run 
without weewx for testing too. Then you can see what is the right settings. 
https://github.com/matthewwall/weewx-interceptor/blob/master/readme

I guess you have installed interceptor and not just weewx.

Otherwise the wifi and ethernet config is the same. Both uses the same network 
protocol TCP/IP. No difference. You can read those topics.

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/8bc7c970-cd82-49b5-b6fa-159de59fcf30%40googlegroups.com.

Re: [weewx-user] Re: Ambient WS-2000 + ATMOCOM weewx rain way too high

[Gábor Szabados]

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
>> <https://groups.google.com/d/msgid/weewx-user/f9f3fc89-4b12-44fb-aff0-b34f1bb48f88%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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

[Gábor Szabados]

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

[Gábor Szabados]

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] Ventus W830

[Gábor Szabados]

Hi Martin,

If this model is a FineOffset clone with a wifi connected console, as it looks 
like, you need to set up interceptor to receive the packages what the console 
would send to one of the providers (ie.: WU).

I don't know that this console can be programmed for specific address like the 
ObserverIPs, but if not then you need to define a rule in your router to 
reroute the traffic to your weewx. There are plenty descriptions of this, how 
to do it with some router firmwares.

I personally have a Eurochron Efws2900, and a Raspberry Pi. The Pi creates an 
AP where the console connects, and routes the data to WU. The Weewx runs with 
interceptor set to sniffer mode.

The rest of it is a different story and the previous commenter can help you 
with that.

I hope it helps!

Gabor 

-- 
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/72a552e2-b6cf-4eb6-9c4f-8eb95c5e642c%40googlegroups.com.

[weewx-user] Re: Connect Froggit WH3000SE weatherstation to weewx

[Gábor Szabados]

Hello Rainer,

I've used this instruction, as I can remember, to set up the RPi as an AP 
(repeater).

https://raspberrypi.stackexchange.com/questions/89803/access-point-as-wifi-router-repeater-optional-with-bridge/89804#89804

There are other instructions too, but none of the others was working for me.

As I used a RPi Zero W, I've set up the device as a repeater, but if you 
used a RPi 3 or something which has eth connector, it is another story, 
because you can create and AP with the Wifi, and pass all data packets to 
the ethernet. With the RPi Zero W, it is an AP/Client setup.

In my setup all the data what passes through the RPi is sniffed by the 
interceptor, and it is passed to WU without modification. So, what you want 
that would work. Otherwise, if you set up WeeWX and interceptor, just to 
intercept/receive, then you can configure WeeWX to send the collected data 
to WU too, or any other web-service what is listed in the config, please 
see the wiki for that, if you need it.


Interceptor in sniffer more:

>From the interceptor.py (
https://github.com/matthewwall/weewx-interceptor/blob/master/bin/user/interceptor.py
)

SniffServer vs TCPServer
The driver can obtain packets by sniffing network traffic using pcap, or by
listening for TCP/IP requests. The pcap approach requires the python pypcap
module, which in turn requires libpcap. This means a separate installation
on most platforms.
https://github.com/pynetwork/pypcap
To run a listener, specify an address and port. This is the default mode.
For example:
[Interceptor]
mode = listen
address = localhost
port = 
To run a sniffer, specify an interface and filter. For example:
[Interceptor]
mode = sniff
iface = eth0
pcap_filter = src host 192.168.1.5 && dst port 80
"""
  
My weewx config looks like this for interceptor:

[Interceptor]
# This section is for the network traffic interceptor driver.

# The driver to use:
driver = user.interceptor

# Specify the hardware device to capture.  Options include:
#   acurite-bridge - acurite internet bridge, smarthub, or access
#   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
#   lw30x - oregon scientific LW301/LW302
#   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
#   wu-client - any hardware that uses the weather underground protocol
device_type = wu-client
mode = sniff
iface = ap0
pcap_filter = src 192.168.6.5 and dst port 80

In my case ap0 is the name of the network interface, and the weather 
station's console is 192.168.6.5, defined in the dnsmasq as I remember.

There are two/three issues what I have seen with my setup.

Rain is not logged correctly by weewx, but I think is mostly due to the RPi 
Zero W's speed capabilities. But I tried to fix for myself the 
interceptor.py.
Due to my Wifi network, and equipment, I have Wifi dropouts, which causes 
some issues by the AP (repeater) setup, I have a script added to chron to 
restart the Wifi connection and the AP, if something goes wrong.
It has happened twice so far, that Interceptor stopped sniffing, probably 
due to the previous issue and Wifi and AP restart. I might add another 
chron job later to restart weewx every X days or something. But the good 
thing, if the interceptor is not sniffing the packets are still passed 
through and reaches WU. 

I hope this helps! Let me know if you need any other info.

Best Regards,

Gábor Szabados

PS.: There is a device which does a similar thing out of the box, and 
passes data to your Raspberry Pi or whatever machine you want, 
http://astrogenic.com/shop/product_info.php?currency=USD_id=64

2019. július 5., péntek 13:58:19 UTC+2 időpontban Moose Man a következőt 
írta:
>
> Dear Gábor,
>
> I own a Froggit WH3000 PWS connected to my Router sending weather data to 
> WU <https://www.wunderground.com/dashboard/pws/IHERZBER23#history>. 
> Now I would like to connect it to Raspberry Pi 3+ via wifi using weewx.
> You mentioned a method to create a wifi access point with the Raspberry Pi 
> and then pass data to the network.
> I will try to do the same but I fear I've not enough experience to get 
> this working, i.e. what does it mean to set up *interceptor in sniffer 
> mode*.  :-) 
>
> However, do you know if it is possible to use weewx on raspberry Pi and 
> still passing data to Weather underground at the same time?
>
> Would be nice to hear from you.
> Thanks in advance.
>
> Best regards,
>
> Rainer
>
> Am Donnerstag, 20. Juni 2019 00:47:41 UTC+2 schrieb Gábor Szabados:
>>
>> Hello, 
>>
>> I have one of the Froggit (Fine Offset) clones from Conrad. 
>>
>> I have used a similar setup as it was described before, but the only 
>> difference, that I have used a wifi AP a way to pass packet through it. 
>>
>> I've done my whole project with a Raspberry Pi Zero W. There

[weewx-user] Re: Connect Froggit WH3000SE weatherstation to weewx

[Gábor Szabados]

Hello,

I have one of the Froggit (Fine Offset) clones from Conrad.

I have used a similar setup as it was described before, but the only 
difference, that I have used a wifi AP a way to pass packet through it.

I've done my whole project with a Raspberry Pi Zero W. There is a way to create 
a wifi access point with the Raspberry Pi and pass all data to your normal 
network. Then you set up interceptor in sniffer mode.

It decodes all the packets what is sent from the weather station to WU.

If you use a Raspberry Pi 3 or 3+ you can do the same by combining the wifi and 
the ethernet port. Wifi as AP and ethernet to your normal network. But an AP 
and Client combination works too the same way as on the Rpi0w.

In my setup there was no need to define iptables in the router (and change 
firmware on the router). The Raspberry Pi does everything. It runs WeeWX too.

Best Regards,

Gábor 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/9fe94f3b-133a-45db-bf72-56403a85a4da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: New to weewx need some help

[Gábor Szabados]

ad:
> unrecognized parameter uv=0
> May 22 16:04:39 UBUNTUMATE-1000H weewx[2069]: interceptor: MainThread:
> unrecognized parameter stationtype=EasyWeatherV1.3.2
> May 22 16:04:39 UBUNTUMATE-1000H weewx[2069]: interceptor: MainThread:
> unrecognized parameter weeklyrainin=0.000
>
>
> On Wednesday, May 22, 2019 at 2:46:57 PM UTC+10, gjr80 wrote:
>>
>> Hi,
>>
>> Not an interceptor or ECOWITT HP2551 user but looking at your log1.txt
>> log extract it appears that your station is sending both rapidfire as well
>> as normal (non-rapidfire) updates.
>>
>> Rapid fire:
>> May 22 07:40:02 UBUNTUMATE-1000H weewx[26366]: interceptor: ServerThread:
>> GET: ID=IVICTORI1768==71.1=54.3=
>> 47.7=54.3=52=78=6.9&
>> windgustmph=8.1=40=29.73=30.34=0.00&
>> dailyrainin=0.00=0.00=1.35=2.25&
>> solarradiation=16.88=0=2019-05-21%2021:40:01=
>> EasyWeatherV1.3.2=updateraw=1=5
>>
>> normal:
>> May 22 07:40:18 UBUNTUMATE-1000H weewx[26366]: interceptor: ServerThread:
>> POST: PASSKEY==EasyWeatherV1.3.2=2019-05-21+21:40
>> :17=71.4=52=30.34=29.73=
>> 54.3=78=18=5.4_avg10m=0.0&
>> windgustmph=6.9=15.9=0.000=0.000&
>> hourlyrainin=0.000=0.000=0.000=
>> 1.346=2.248=16.02=0
>>
>> This really shouldn't be an issue but if you have a look at the number of
>> decimal places used for each rain related observation in each you will see
>> the RF updates use 2 decimal places and the normal updates 3 decimal
>> places. Consequently, when you have normal after a RF you get a rain
>> counter wraparound detected and your rainfall has the wrapped around figure
>> added. If you have RF after normal you get 0.002 inches added. RF after RF
>> has no effect as both yearly rain fields are identical. I don't think using
>> any of the other rain fields will make a difference because the same
>> decimal places difference exist with both.
>>
>> Maybe less than ideal but can you turn off RF updates on your station,
>> that would at last show if that cures the issue or not. If so, maybe the
>> solution is to get the interceptor driver to ignore either the RF updates
>> or the normal updates. Not sure whether it can or not, probably one for
>> Matthew the author.
>>
>> Gary
>>
>> On Wednesday, 22 May 2019 14:13:03 UTC+10, Joe Santas wrote:
>>>
>>> Cleared the settings on the weatherstation.  Same issue again.
>>> Obviously something else is going on.  Also tried shutting down the weather
>>> station and deleting the weewx.sdb file so it re creates a new one but no
>>> joy so far.
>>> I have attached the latest copy of the log.
>>>
>>> Regards
>>>
>>>
>>>
>>> On Wednesday, May 22, 2019 at 2:22:50 AM UTC+10, Gábor Szabados wrote:
>>>>
>>>> Sounds like a plan. Let me know once you have done it.
>>>>
>>>> Interceptor should receive only the wu messages, then it should not
>>>> have any issue.
>>>>
>>>> Gabor
>>>>
>>>> Joe Santas  ezt írta (időpont: 2019. máj. 21., Ke
>>>> 17:41):
>>>>
>>>>> From what i have read they specify just the tcp to port 80 which i
>>>>> already have in place.  What i will do is deactivate the upload features 
>>>>> in
>>>>> the weatherstation its self and see if it makes a difference and leave the
>>>>> rules i currently have in place and see if this sorts it.
>>>>> Once this is done i will configure weewx config file to push the data
>>>>> up to wunderground and weathercloud any any other services i use.
>>>>>
>>>>> Regards
>>>>>
>>>>> On Wednesday, May 22, 2019 at 1:35:11 AM UTC+10, Gábor Szabados wrote:
>>>>>>
>>>>>> Read about how you can redirect only the traffic to WU servers to
>>>>>> your weewx server then you will be ok.
>>>>>>
>>>>>> I've seen some Merlin router firmware descriptions how it can be
>>>>>> done. Or DD-WRT descriptions are around the net too.
>>>>>>
>>>>>> Gabor
>>>>>>
>>>>>> Joe Santas  ezt írta (időpont: 2019. máj. 21., Ke
>>>>>> 16:22):
>>>>>>
>>>>>>> You may be onto something.  So i will have to turn off the non wu
>>>>>>> servers on the device its self.  Im unable to do this as i am at work 
>>>>>>> but i
>>>>&g

Re: [weewx-user] Re: New to weewx need some help

[Gábor Szabados]

Sounds like a plan. Let me know once you have done it.

Interceptor should receive only the wu messages, then it should not have
any issue.

Gabor

Joe Santas  ezt írta (időpont: 2019. máj. 21., Ke
17:41):

> From what i have read they specify just the tcp to port 80 which i already
> have in place.  What i will do is deactivate the upload features in the
> weatherstation its self and see if it makes a difference and leave the
> rules i currently have in place and see if this sorts it.
> Once this is done i will configure weewx config file to push the data up
> to wunderground and weathercloud any any other services i use.
>
> Regards
>
> On Wednesday, May 22, 2019 at 1:35:11 AM UTC+10, Gábor Szabados wrote:
>>
>> Read about how you can redirect only the traffic to WU servers to your
>> weewx server then you will be ok.
>>
>> I've seen some Merlin router firmware descriptions how it can be done. Or
>> DD-WRT descriptions are around the net too.
>>
>> Gabor
>>
>> Joe Santas  ezt írta (időpont: 2019. máj. 21., Ke
>> 16:22):
>>
>>> You may be onto something.  So i will have to turn off the non wu
>>> servers on the device its self.  Im unable to do this as i am at work but i
>>> can reconfigure my router remotely to route the correct traffic. I can try
>>> this from work.  Which protocol should i leave active?  At the moment i am
>>> forwarding all tcp traffic to my weewx server from the weather station.
>>>
>>> Regards
>>>
>>> On Wednesday, May 22, 2019 at 12:13:36 AM UTC+10, Gábor Szabados wrote:
>>>>
>>>> I can see more issues there, because I faced a similar one before.
>>>>
>>>> One of your issues, maybe the main one, that your weather station is
>>>> sending reports to multiple servers and all of them ia redirected to your
>>>> weewx. Interceptor tries to parse all the messages and faces a mixed state
>>>> with yearlyrainin and dailyrainin and some rounding issues.
>>>>
>>>> First try to turn off the reporting to the non-wu servers. Or set your
>>>> router to forward only the wu request to your weewx. Then the interceptor
>>>> will recieve and parse only one kind of messages.
>>>>
>>>> Gabor
>>>>
>>>> Joe Santas  ezt írta (időpont: 2019. máj. 21., Ke
>>>> 15:52):
>>>>
>>>>> wraparound detected in this log.
>>>>> After clearing the database rainfall graph has started to populate
>>>>> once again even though no rain lol.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tuesday, May 21, 2019 at 5:12:03 PM UTC+10, Gábor Szabados wrote:
>>>>>>
>>>>>> Hi Joe,
>>>>>>
>>>>>> Could you try to look for messages in the log, like interceptor:
>>>>>> MainThread: rain counter wraparound detected:
>>>>>>
>>>>>> I can see a rounding issue (maybe) at the yearly rain is once 2.248
>>>>>> the then 2.25, when no weekly rain change.
>>>>>>
>>>>>> May 21 02:53:17 UBUNTUMATE-1000H weewx[7192]: interceptor:
>>>>>> MainThread: raw data:
>>>>>> PASSKEY==EasyWeatherV1.3.2=2019-05-20+16:53:05=65.8=60=30.14=29.54=55.4=77=16=2.9_avg10m=0.0=3.4=8.1=0.000=0.000=0.000=0.000=0.000=1.346=2.248=0.00=0
>>>>>>
>>>>>> May 21 02:53:22 UBUNTUMATE-1000H weewx[7192]: interceptor:
>>>>>> ServerThread: GET:
>>>>>> ID=*==65.8=55.4=48.4=55.4=60=77=2.9=3.4=16=29.54=30.14=0.00=0.00=0.00=1.35=2.25=0.00=0=2019-05-20%2016:53:21=EasyWeatherV1.3.2=updateraw=1=5
>>>>>>
>>>>>> Look for wraparound events and check on your console too what is your
>>>>>> yearly value. Try to find places where the yearlyrainin changes and where
>>>>>> it calculates rain from the change then I can try to find you the logic
>>>>>> what goes wrong. Look for dateutc values too, is it incremental or 
>>>>>> changes
>>>>>> back time to time when wraparound happens, if happens.
>>>>>>
>>>>>> Best Regards,
>>>>>>
>>>>>> Gabor
>>>>>>
>>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "weewx-user" group.
>>>>> To unsubscribe from this group and stop receiving em

Re: [weewx-user] Re: New to weewx need some help

[Gábor Szabados]

Read about how you can redirect only the traffic to WU servers to your
weewx server then you will be ok.

I've seen some Merlin router firmware descriptions how it can be done. Or
DD-WRT descriptions are around the net too.

Gabor

Joe Santas  ezt írta (időpont: 2019. máj. 21., Ke
16:22):

> You may be onto something.  So i will have to turn off the non wu servers
> on the device its self.  Im unable to do this as i am at work but i can
> reconfigure my router remotely to route the correct traffic. I can try this
> from work.  Which protocol should i leave active?  At the moment i am
> forwarding all tcp traffic to my weewx server from the weather station.
>
> Regards
>
> On Wednesday, May 22, 2019 at 12:13:36 AM UTC+10, Gábor Szabados wrote:
>>
>> I can see more issues there, because I faced a similar one before.
>>
>> One of your issues, maybe the main one, that your weather station is
>> sending reports to multiple servers and all of them ia redirected to your
>> weewx. Interceptor tries to parse all the messages and faces a mixed state
>> with yearlyrainin and dailyrainin and some rounding issues.
>>
>> First try to turn off the reporting to the non-wu servers. Or set your
>> router to forward only the wu request to your weewx. Then the interceptor
>> will recieve and parse only one kind of messages.
>>
>> Gabor
>>
>> Joe Santas  ezt írta (időpont: 2019. máj. 21., Ke
>> 15:52):
>>
>>> wraparound detected in this log.
>>> After clearing the database rainfall graph has started to populate once
>>> again even though no rain lol.
>>>
>>>
>>>
>>>
>>> On Tuesday, May 21, 2019 at 5:12:03 PM UTC+10, Gábor Szabados wrote:
>>>>
>>>> Hi Joe,
>>>>
>>>> Could you try to look for messages in the log, like interceptor:
>>>> MainThread: rain counter wraparound detected:
>>>>
>>>> I can see a rounding issue (maybe) at the yearly rain is once 2.248 the
>>>> then 2.25, when no weekly rain change.
>>>>
>>>> May 21 02:53:17 UBUNTUMATE-1000H weewx[7192]: interceptor: MainThread:
>>>> raw data:
>>>> PASSKEY==EasyWeatherV1.3.2=2019-05-20+16:53:05=65.8=60=30.14=29.54=55.4=77=16=2.9_avg10m=0.0=3.4=8.1=0.000=0.000=0.000=0.000=0.000=1.346=2.248=0.00=0
>>>>
>>>> May 21 02:53:22 UBUNTUMATE-1000H weewx[7192]: interceptor:
>>>> ServerThread: GET:
>>>> ID=*==65.8=55.4=48.4=55.4=60=77=2.9=3.4=16=29.54=30.14=0.00=0.00=0.00=1.35=2.25=0.00=0=2019-05-20%2016:53:21=EasyWeatherV1.3.2=updateraw=1=5
>>>>
>>>> Look for wraparound events and check on your console too what is your
>>>> yearly value. Try to find places where the yearlyrainin changes and where
>>>> it calculates rain from the change then I can try to find you the logic
>>>> what goes wrong. Look for dateutc values too, is it incremental or changes
>>>> back time to time when wraparound happens, if happens.
>>>>
>>>> Best Regards,
>>>>
>>>> Gabor
>>>>
>>>> --
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/f4434e12-7ed4-4a60-bc6c-42ff8de0d5ee%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/f4434e12-7ed4-4a60-bc6c-42ff8de0d5ee%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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/lg4W_4qHTaQ/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/30272d74-fedd-46a6-9a0f-ba66112df697%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/30272d74-fedd-46a6-9a0f-ba66112df697%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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%2BwUz7F%3DUBokNSt25xv%2BNCUmYfrtjrhL1jjbCPQnOOtfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: New to weewx need some help

[Gábor Szabados]

I can see more issues there, because I faced a similar one before.

One of your issues, maybe the main one, that your weather station is
sending reports to multiple servers and all of them ia redirected to your
weewx. Interceptor tries to parse all the messages and faces a mixed state
with yearlyrainin and dailyrainin and some rounding issues.

First try to turn off the reporting to the non-wu servers. Or set your
router to forward only the wu request to your weewx. Then the interceptor
will recieve and parse only one kind of messages.

Gabor

Joe Santas  ezt írta (időpont: 2019. máj. 21., Ke
15:52):

> wraparound detected in this log.
> After clearing the database rainfall graph has started to populate once
> again even though no rain lol.
>
>
>
>
> On Tuesday, May 21, 2019 at 5:12:03 PM UTC+10, Gábor Szabados wrote:
>>
>> Hi Joe,
>>
>> Could you try to look for messages in the log, like interceptor:
>> MainThread: rain counter wraparound detected:
>>
>> I can see a rounding issue (maybe) at the yearly rain is once 2.248 the
>> then 2.25, when no weekly rain change.
>>
>> May 21 02:53:17 UBUNTUMATE-1000H weewx[7192]: interceptor: MainThread:
>> raw data:
>> PASSKEY==EasyWeatherV1.3.2=2019-05-20+16:53:05=65.8=60=30.14=29.54=55.4=77=16=2.9_avg10m=0.0=3.4=8.1=0.000=0.000=0.000=0.000=0.000=1.346=2.248=0.00=0
>>
>> May 21 02:53:22 UBUNTUMATE-1000H weewx[7192]: interceptor: ServerThread:
>> GET:
>> ID=*==65.8=55.4=48.4=55.4=60=77=2.9=3.4=16=29.54=30.14=0.00=0.00=0.00=1.35=2.25=0.00=0=2019-05-20%2016:53:21=EasyWeatherV1.3.2=updateraw=1=5
>>
>> Look for wraparound events and check on your console too what is your
>> yearly value. Try to find places where the yearlyrainin changes and where
>> it calculates rain from the change then I can try to find you the logic
>> what goes wrong. Look for dateutc values too, is it incremental or changes
>> back time to time when wraparound happens, if happens.
>>
>> Best Regards,
>>
>> Gabor
>>
>> --
> 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/f4434e12-7ed4-4a60-bc6c-42ff8de0d5ee%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/f4434e12-7ed4-4a60-bc6c-42ff8de0d5ee%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAEx3znKe5MncDFZQ6kzrnQdDy1F-ObXJcAJ0H_ZqKmdf90L1dQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: New to weewx need some help

[Gábor Szabados]

Hi Joe,

Could you try to look for messages in the log, like interceptor: MainThread: 
rain counter wraparound detected:

I can see a rounding issue (maybe) at the yearly rain is once 2.248 the then 
2.25, when no weekly rain change.

May 21 02:53:17 UBUNTUMATE-1000H weewx[7192]: interceptor: MainThread: raw 
data: 
PASSKEY==EasyWeatherV1.3.2=2019-05-20+16:53:05=65.8=60=30.14=29.54=55.4=77=16=2.9_avg10m=0.0=3.4=8.1=0.000=0.000=0.000=0.000=0.000=1.346=2.248=0.00=0

May 21 02:53:22 UBUNTUMATE-1000H weewx[7192]: interceptor: ServerThread: GET: 
ID=*==65.8=55.4=48.4=55.4=60=77=2.9=3.4=16=29.54=30.14=0.00=0.00=0.00=1.35=2.25=0.00=0=2019-05-20%2016:53:21=EasyWeatherV1.3.2=updateraw=1=5

Look for wraparound events and check on your console too what is your yearly 
value. Try to find places where the yearlyrainin changes and where it 
calculates rain from the change then I can try to find you the logic what goes 
wrong. Look for dateutc values too, is it incremental or changes back time to 
time when wraparound happens, if happens.

Best Regards,

Gabor

-- 
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/cc3e21d4-a783-47e8-a26f-c404d2ec7c57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: New to weewx need some help

[Gábor Szabados]

Hi Joe,

Could you please add some more of the log? I might have an idea, but I haven't 
seen a specific message in the snippet of your log yet.

Do you have any rain at all now? Is this station a Fine Offset clone too 
reporting to WU?

Best Regards,

Gábor

-- 
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/ef00afa5-d00c-4ec7-ba4a-0c3b36f4719c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WeeWX rain not matching console and WU

[Gábor Szabados]

It has turned out that the wraparound packets were from a previous time when I 
started inspect the dateTime of the messages. I've implemented a modification 
into my interceptor to check the time and don't let previous rain values to mix 
up things.

Can anyone tell me, when Interceptor passes the data to WeeWX, does the 
dateTime value from the messages are used? I am just worried about that these 
out of order messages can screw other things up too? I only guess that the 
console is resending some messages to WU when it has not confirmed received. 
That is may causing the disorder.

Thanks for any help!

Gábor 

-- 
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/25c08793-b49c-440e-9cf1-91c7dfa8ae96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WeeWX rain not matching console and WU

[Gábor Szabados]

Hi,

I've looked at the logs and this is what happens:

May 15 23:23:10 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter rainin=0.07
May 15 23:23:10 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter absbaromin=29.74
*May 15 23:23:10 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter monthlyrainin=1.34*
*May 15 23:23:10 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter weeklyrainin=0.82*
May 15 23:24:26 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter rainin=0.05
May 15 23:24:26 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter absbaromin=29.74
*May 15 23:24:26 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter monthlyrainin=1.33*
*May 15 23:24:26 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter weeklyrainin=0.81*
*May 15 23:24:26 WeeWX weewx[419]: interceptor: MainThread: rain counter 
wraparound detected: new=0.31 last=0.32*
May 15 23:24:27 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter rainin=0.07
May 15 23:24:27 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter absbaromin=29.74
*May 15 23:24:27 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter monthlyrainin=1.34*
*May 15 23:24:27 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter weeklyrainin=0.82*
May 15 23:24:46 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter rainin=0.07
May 15 23:24:46 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter absbaromin=29.74
May 15 23:24:46 WeeWX weewx[419]: interceptor: MainThread: unrecognized 
parameter monthlyrainin=1.34

All the wraparounds are causing the interceptor driver to set the last rain 
value to the new, and then a correct record comes again, which adds the 
same difference again and again. (If we are disregarding, that it really 
returns the new value as the amount of rain and that is even worse.)

I have still no idea why the messages are containing these values, and 
triggering the wraparound. Should this be reported as bug for Interceptor?

Thanks,

Gábor

-- 
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/178c8edc-0f59-43a5-954a-16be8c5c1dc3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] WeeWX rain not matching console and WU

[Gábor Szabados]

 see on the console and in 
WU, meanwhile WeeWX shows 0.32 inch. I have seen previously in the logged 
data that occasionally WeeWX is logging more rain then what what was 
reported by the station.

I don't know is it an Interceptor a WeeWX logging issue.

I am using WeeWX 3.9.1, and Interceptor 0.45.

I've attached the WeeWX configuration too.

I have a feeling that the interceptor's this section is causing the issue, 
when it logs the new value to rain:

def _delta_rain(rain, last_rain):
if last_rain is None:
loginf("skipping rain measurement of %s: no last rain" % rain)
return None
if rain < last_rain:
loginf("rain counter wraparound detected: new=%s last=%s" %
(rain, last_rain))
return rain
return rain - last_rain
 
Suddenly I have no idea why the values are wrapped around.

Thank you in advance for any help!

Best Regards,

Gábor 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/619cce49-f930-4888-aa84-a140612442bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 0

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.9.1

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Wschowa, Poland"

# Latitude and longitude in decimal degrees
latitude = 51.810
longitude = 16.322

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 135, meter

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be used.
station_type = Interceptor

# If you have a website, you may specify an URL
#station_url = http://www.example.com

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 0

##

[Interceptor]
# This section is for the network traffic interceptor driver.

# The driver to use:
driver = user.interceptor

# Specify the hardware device to capture.  Options include:
#   acurite-bridge - acurite internet bridge, smarthub, or access
#   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
#   lw30x - oregon scientific LW301/LW302
#   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
#   wu-client - any hardware that uses the weather underground protocol
device_type = wu-client
mode = sniff
iface = ap0
pcap_filter = src 192.168.6.5 and dst port 80

##

[Simulator]
# This section is for the weewx weather station simulator

# The time (in seconds) between LOOP packets.
loop_interval = 2.5

# The simulator mode can be either 'simulator' or 'generator'.
# Real-time simulator. Sleep between each LOOP packet.
mode = simulator
# Generator.  Emit LOOP packets as fast as possible (useful for testing).
#mode = generator

# The start time. Format is -mm-ddTHH:MM. If not specified, the default 
# is to use the present time.
#start = 2011-01-01T00:00

# The driver to use:
driver = weewx.drivers.simulator

##

#   This section is for uploading data to Internet sites

[StdRESTful]

[[StationRegistry]]
# To register this weather station with weewx, set this to true
register_this_station = false

[[AWEKAS]]
# This section is for configuring posts to AWEKAS.

# If you wish to do this, set the option 'enable' to true,
# and specify a username and password.
# To guard against