Yes I'm aware of the WH26/WH32 issue, I have a WH32 myself. Interestingly the GW1000 API does not mention the term 'WH32' anywhere.In fact, to date I have not seen 'WH32' mentioned anywhere on the Ecowitt.net display/dashboard nor anywhere in the WS View app. The closet I have seen WH32 being 'mentioned' is the device icons that appear when you go to 'Sensors ID' in the WS View app - the icon appears to be a WH32 (but then I have never unknowingly seen a WH26 either). Bottom line is the GW1000 API lists the bit concerned in the battery state API response as WH26 battery state so that is what the driver passes it through as. If I could find something somewhere that discriminates between the two I would use that to change the field name accordingly (there actually is a bit in one of the API responses that discriminates between a connected WH24 or WH65, but there nothing along those lines for WH26/WH32). I have toyed with adding a config option in the driver stanza that would solely be used to set the name of that battery state field, just haven't gotten around to it yet plus WeeWX gives the user the ability to map wh26_batt to a field name of the users choice anyway.
Gary On Sunday, 20 December 2020 at 12:33:38 UTC+10 vince wrote: > Gary - this thread got me thinking of adding battery status to my minimal > EcoWitt skin (GitHub link) > <https://github.com/vinceskahan/weewx-ecowitt-skin> > > I have a GW1000 and a WH32 outdoor sensor and run weewx 4.2.0 dpkg raspi > using 0.1.0b12 of your driver. > > pi@pi3jr:~ $ PYTHONPATH=/usr/share/weewx python3 -m user.gw1000 > --live-data > Using configuration file /etc/weewx/weewx.conf > Interrogating GW1000 at 192.168.2.20:45000 > GW1000 live sensor data: absbarometer: 1002.8, datetime: 1608426650, > inhumid: 43, intemp: 21.8, outhumid: 97, outtemp: 7.7, relbarometer: > 1014.3, wh26_batt: 0 > > What's interesting is that you report this as a wh26 when the EcoWitt app > (and my Amazon receipt) show it as a WH32. > > A little research says that the WH32 seems to be a later model of the WH26 > so I'm guessing/hoping it doesn't matter much, but I thought I'd mention it > to you. You do have a comment in decode_batt() with a question mark about > it, so I guess the answer there is 'yes it seems to be the same'. > > Thanks again for a great driver. Looking forward to buying more sensors. > > FWIW, I also added a screenshot > <https://github.com/vinceskahan/weewx-ecowitt-skin/blob/main/ecowitt-skin-example.png> > and > the cheetah-fu and description of how I added battery status to the skin is > here > <https://github.com/vinceskahan/weewx-ecowitt-skin/blob/main/skins/ecowitt/index.html.tmpl> > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/f4fe12ad-3deb-4d07-8510-f965260c5b5cn%40googlegroups.com.
