Page 1 of 1
Low battery alarms
Posted: Mon 14 Mar 2022 8:01 am
by freddie
I have had three well-spaced low battery alarm emails since Saturday night. The text of the email says "A low battery condition has been detected". Looking in the MXdiags, I can't see which battery is low. Any ideas? I have four batteries to consider: Davis console (unlikely as the mains adaptor is plugged in), Davis ISS, and two Ecowitt temperature sensors.
Re: Low battery alarms
Posted: Mon 14 Mar 2022 11:24 am
by mcrossley
To check your Davis batteries you could use the local API...
http://<IP_ADDRESS>:8998/api/tags/process.json?battery&txbattery
For Ecowitt, it is a check of WSView app I'm afraid.
Debug logging "should" show the affected battery for Ecowitt in the debug SensorInfo dumped every 20 minutes, but MX does not keep track of which one, just the fact that a low condition occurred.
Re: Low battery alarms
Posted: Mon 14 Mar 2022 11:41 am
by freddie
mcrossley wrote: ↑Mon 14 Mar 2022 11:24 am
To check your Davis batteries you could use the local API...
http://<IP_ADDRESS>:8998/api/tags/process.json?battery&txbattery
For Ecowitt, it is a check of WSView app I'm afraid.
Debug logging "should" show the affected battery for Ecowitt in the debug SensorInfo dumped every 20 minutes, but MX does not keep track of which one, just the fact that a low condition occurred.
Thanks Mark. Davis shows {"battery":"4.68","txbattery":"1-ok 2-ok 3-ok 4-ok 5-ok 6-ok 7-ok 8-ok"}. Ecowitt via the app - grass temperature says battery is "Normal"; depth temperature gives me a graphic that shows 2 out of 5 "bars" for the battery.
I guess I'm just going to have to monitor....
Re: Low battery alarms
Posted: Sat 26 Mar 2022 3:33 pm
by freddie
mcrossley wrote: ↑Mon 14 Mar 2022 11:24 am
Debug logging "should" show the affected battery for Ecowitt in the debug SensorInfo dumped every 20 minutes, but MX does not keep track of which one, just the fact that a low condition occurred.
I'm still getting these alarms - usually 3-4 and all between midnight and sunrise. I see this in the diags file:
Code: Select all
2022-03-26 06:37:09.023 ProcessExtraData: Processing posted data
2022-03-26 06:37:09.023 ProcessExtraData: Payload = PASSKEY=<PassKey>&stationtype=GW1100A_V2.0.2&dateutc=2022-03-26+06:35:52&tempinf=59.4&humidityin=41&baromrelin=30.546&baromabsin=30.053&temp1f=28.6&tf_ch1=46.9&batt1=0&tf_batt1=1.20&freq=868M&model=GW1100A
2022-03-26 06:37:09.024 SendEmail: Waiting for lock...
2022-03-26 06:37:09.024 SendEmail: Has the lock
2022-03-26 06:37:09.024 SendEmail: Sending email, to [niall@hosiene.co.uk], subject [Cumulus MX Alarm], body ["A Cumulus MX alarm has been triggered.\r\nA low battery condition has been detected" +
"."]...
2022-03-26 06:37:09.025 ProcessExtraData: Complete
I can see two potential battery readings in the payload from my GW1100 - batt1 and tf_batt1. I don't know which sensors they refer to - is there a decode available?
Re: Low battery alarms
Posted: Sat 26 Mar 2022 6:20 pm
by mcrossley
batt[1-8] sends 0 for good, 1 for low. I believe this is the extra T/H sensor
tf_batt[1-8] sends the voltage, with <= 1.2 being considered low. I believe this is the WN34 Soil sensor.
Re: Low battery alarms
Posted: Sat 26 Mar 2022 8:00 pm
by freddie
mcrossley wrote: ↑Sat 26 Mar 2022 6:20 pm
batt[1-8] sends 0 for good, 1 for low. I believe this is the extra T/H sensor
tf_batt[1-8] sends the voltage, with <= 1.2 being considered low. I believe this is the WN34 Soil sensor.
Thanks @mcrossley looks like I need to change the soil sensor battery - I'll do that tomorrow.