Battery status on different devices: https://www.wxforum.net/index.php?topic=37373.msg408190#msg408190
Matthias Am Dienstag, 28. Juli 2020 18:34:34 UTC+2 schrieb NanoG5Kite: > > Regarding Evowitt Battery Status. There are new Sensors like the WH 57 > which report the battery status from 0-5 (5=fully charged), but former > sensors like the 7in1 with 0 or 1 (1=empty, to be replaced asap). There was > a useful threat in the wxforum.net telleing which sensors show which kind > of level, but can‘t find it back currently... > > Am Dienstag, 28. Juli 2020 18:04:55 UTC+2 schrieb Paul Anderson: >> >> Gary >> First just a note that I was running v0.1.0b6 as a service and my GW1000 >> lost it's WIFI connection. Actual dropped WIFI connecting by the GW1000. >> Looking at the log I see that the driver worked perfectly, it logged a >> connection failure after 3 attempts, but weewx itself kept running so that >> only the supplemental data from the GW1000 was lost. Once I relocated the >> GW1000 to a better location , without restarting WeeWX, the GW1000 data >> started flowing again. Perfect just the behavior I would want. >> >> Just updated to v0.1.0b7 here is what is returned for battery status: >> wh31_ch2_batt: 0, wh31_ch4_batt: 0, wh31_ch5_batt: 0, wh31_ch7_batt: 0, >> wh57_batt: 5 >> So all sensors recognized, not sure of the meaning of "0" and "5" and why >> wh57 returns "5" All sensors installed with new batteries 3 days ago . >> >> On Tue, Jul 28, 2020 at 9:52 AM gjr80 <gjrod...@gmail.com> wrote: >> >>> I have released v0.1.0b7 on Github >>> <https://github.com/gjr80/weewx-gw1000/releases>. b7 adds the battery >>> states to the default field map which should see battery states appear in >>> the loop packets. I expect there will still be some naming issues, >>> especially with WH65 and WH32. b7 also fixes a n issue where wind direction >>> was wrongly decoded.. >>> >>> Those that have already installed the driver can download and install >>> v0.1.0b7 using the following commands depending on your WeeWX install type: >>> >>> for setup.py installs: >>> >>> $ sudo mv /home/weewx/bin/user/gw1000.py /home/weewx/bin/user/ >>> gw1000_orig.py >>> $ sudo wget -P /home/weewx/bin/user https:// >>> raw.githubusercontent.com/gjr80/weewx-gw1000/v0.1.0b7/bin/user/gw1000.py >>> <http://raw.githubusercontent.com/gjr80/weewx-gw1000/v0.1.0b6/bin/user/gw1000.py> >>> >>> for package installs: >>> >>> $ sudo mv /usr/share/weewx/user/gw1000.py /usr/share/weewx/user/ >>> gw1000_orig.py >>> $ sudo wget -P /usr/share/weewx/user https:// >>> raw.githubusercontent.com/gjr80/weewx-gw1000/v0.1.0b7/bin/user/gw1000.py >>> <http://raw.githubusercontent.com/gjr80/weewx-gw1000/v0.1.0b6/bin/user/gw1000.py> >>> >>> There has been no change to the [GW1000] structure so you can just >>> restart WeeWX/run v0.1.0b7 directly without further changes. >>> >>> 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...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/4636d1ee-f397-4679-907c-45981a165199o%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/4636d1ee-f397-4679-907c-45981a165199o%40googlegroups.com?utm_medium=email&utm_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/3a110944-2de1-4c17-8fec-df056ddfd6ffo%40googlegroups.com.
