[weewx-user] Re: GW-1000 API battery reading issues with GW1000 V1.6.6

Ah Gary I now realise this is a known change in the API for v1.6.6... Happy to beta test any updated driver s/w on my setup if you want, let me know... Not the end of the world as the Ecowitt.net sees the levels anyway correctly. On Monday, March 15, 2021 at 8:09:34 PM UTC Paul Ward wrote

[weewx-user] GW-1000 API battery reading issues with GW1000 V1.6.6

Hi @gjr80 I think I have a problem with the battery level extraction since the GW1000 updated firmware to V1.6.6... Everything was working fine beforehand and I can see the battery levels in the Weewx loop data and use it downstream. Since V1.6.6 the battery statuses seem to have vanished from

[weewx-user] GW1000 poll interval settings / limitations

Question about shortening the poll interval an implications / recommendations... My setup is I’ve got 2x GW1000’s both reading lots of “shared” sensors but one reading at WS80 and one reading a WS68. I then have 2x Raspberry Pi’s concurrently, both running the API in driver mode and receiving

[weewx-user] Re: GW1000 driver v0.2.0 release

I've just got my WH45 and its working great with new driver thanks Gary. I've noticed that the CO2 internal temp & humidity are coming through as the curiously named "extraTemp17" and "extraHumid17" does that sound right? Also FYI at some point wiki sensor map page will need updating :-) On

Re: [weewx-user] Re: weewx crashed - issue with gw1000.py when Ecowitt WH45 5-in-1 combo sensor gets activated (5= T+PM2.5+PM10) [2b]

Gary I have a WH45 on order so subject to shipping delays I’m happy to test the code too in couple of weeks when I get it, if you don’t release beforehand. On Friday, January 1, 2021 at 1:26:45 AM UTC gjr80 wrote: > WH45 support was coded some time ago though of course not tested with an >

Re: [weewx-user] GW1000 output and database

Thanks Gary and others on this thread - I'm using the GW1000 API driver mode and have re-purposed one of my internal multi-channel WH31 sensors for main outdoor temp/humidity use temporarily (whilst I await return of WS80). Very simple once I'd figured out I needed to use the

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

ping from the Interceptor plugin to the GW1000 driver > which captures more of the data than the Interceptor does rather than > trying to modify things to fit. > > https://github.com/gjr80/weewx-gw1000 > > cheers > > Tim > On 7/10/20 9:57 am, Paul Ward wrote: >

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

Ah no thanks - dunno why that didn't pop up in a search - thanks I'll look into it On Wednesday, October 7, 2020 at 5:13:57 AM UTC+1 gert.a...@gmail.com wrote: > Hi > > Have You seen this > > ? >

[weewx-user] ecowitt extra sensor data parameters

HI forum! I'm running 4.1.1 on a Pi connecting directly to a HP2551 with sensors of WS80 ultrasonic, WH40 rain, WH31 indoor, WH41 pm2.5 AQ, WH51 soil, WH57 lightning (from Froggit in UK). It's using weewx-interceptor in ecowitt-client mode, default config. It seems to find most of the sensors

Re: [weewx-user] How to display pm2.5 & lightning graphs?

Hi I'm a bit new to this and have similar setup except like your originally did Andy without a DP1500 (GW1000) gateway just using the HP2551 with weewx-interceptor in ecowitt-client mode. I've got a lightning detector (wh57), pm2.5 detector (wh41) also soil moisture detector. From the syslogs