Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

My apologies for not publishing b5 earlier, I had some documentation issues I wished to fix first but a lack of spare time prevented that. In any case I have released v0.5.0b5 this morning. b5 addresses two main issues. Firstly it removes the the internal driver field t_rainhour from the

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

FYI... I edited v0.5.0b4 driver and remarked-out the line "t_rainhour" from the default field map and this has stopped the erroneous reading. It's a temporary fix until b5 becomes available. Sorry for being impatient but I hated to see that value being reported to CWOP. Does anyone have ties to

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

I found this thread after investigating the hourly rain problem with my CWOP readings. I attempted to download the b5 version using: wget -P /var/tmp https://github.com/gjr80/weewx-gw1000/releases/download/v0.5.0b5/gw1000-0.5.0b5.tar.gz But I get a 404 error. Is version v0.5.0b5 available

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

Thanks Gary. You mentioned WU earlier. I looked at the data of my station on the WU website and it seems to me that it matches the data on the Ecowitt dashoard. Tomek środa, 1 czerwca 2022 o 14:01:13 UTC+2 gjr80 napisał(a): > Tomek, > > The interceptor driver ignores the hour rain field from

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

Tomek, The interceptor driver ignores the hour rain field from the GW device and consequently the CWOP uploader falls back to obtaining (valid) hour rain data from the database. Whereas the Ecowitt Gateway (GW1000) driver passes the erroneous hour rain field through and it is used by the CWOP

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

Hi Gary, thank you for your reply. It's very interesting what you wrote. It looks like I will have to wait for your driver or firmware to be updated. Before, I used the weewx-interceptor . Today I discovered that the problem came after changing

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

One thing I forgot. You will not see any hour rain data in the --get-all-rain-data output as the --get-all-rain-data output mimics the 'More', 'Rain Totals' screen in the WSView Plus app. Gary On Wednesday, 1 June 2022 at 08:40:37 UTC+10 gjr80 wrote: > Hi Tomek, > > Short answer is I believe

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

Hi Tomek, Short answer is I believe it is a device API error. What I suspect is going on is that the Ecowitt gateway device API is returning 10.0mm for what the API documentation refers to as 'ITEM_RAINHOUR' (described as 'Rain hour (mm)'). The driver passes this value through to the WeeWX

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

...and after a short rain as I wrote the above post: PYTHONPATH=/usr/share/weewx python -m user.gw1000 --get-all-rain-data Using configuration file /etc/weewx/weewx.conf Interrogating GW1100 at 192.168.x.x:45000 Traditional rain data: Rain rate: 0.0mm/hr (0.0in/hr))

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

Hi Gary. GW1100A_V2.1.4 / WH40 *PYTHONPATH=/usr/share/weewx python -m user.gw1000 --live-data* GW1100 live sensor data (2022-05-31 21:59:38 CEST (1654027178)): [...]* 't_rainhour': '1.00'*, [...] *PYTHONPATH=/usr/share/weewx python -m user.gw1000 --test-driver* 2022-05-31 21:34:53 CEST

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

Latest beta working good on my gw1000 with the latest firmware (1.7.2) 2022-05-04 10:08:46 EDT (1651673326): 'dateTime': '1651673326', 'daymaxwind': '3.1', 'dayRain': '1.7', 'extraHumid1': '60', 'extraTemp1': '14.9', 'hourRain': '10.0', 'inHumidity': '46', 'inTemp': '21.4',

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

My apologies, I should have also included the output from the syslog... May 2 12:55:30 weewx weewx[2263] DEBUG user.gw1000: Parsed data: {'intemp': 16.6, 'inhumid': 61, 'absbarometer': 1020.9, 'relbarometer': 1020.9, 'outtemp': 15.7, 'outhumid': 78, 'winddir': 359, 'windspeed': 1.3,

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

Looking good on my test server: May 2 12:50:47 weewx weewx[2263] INFO user.gw1000: GatewayDriver: Packet 2022-05-02 12:50:47 BST (1651492247): {'dateTime': '1651492247', 'daymaxwind': '4.3', 'dayRain': '0.6', 'extraHumid1': '53', 'extraHumid2': '56', 'extraTemp1': '19.9', 'extraTemp2':

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

That is good, we will see how b4 goes. Test data is from various sources; some live captures, some WSView Plus settings, some reverse calculated. Gary On Monday, 2 May 2022 at 17:21:17 UTC+10 lang@googlemail.com wrote: > Gary, > you made it. Now it runs properly with my two rain gauges,

Re: [weewx-user] Ecowitt Gateway (formerly GW1000) driver v0.5.0b4 release [5]

Gary, you made it. Now it runs properly with my two rain gauges, traditional and piezo.  I guess you also used some fake test data for daily, weekly and monthly rain and also rain rate. As I did now - setting some fake rain totals in the WS View Plus app. The CMD_READ_RAIN is now properly