After the battery voltage has dropped to some voltage (e.g. 2.9V), the readout always returns the same value for all following messages sent (hundreds) although the DMM measured battery voltage is much below the reported fixed value of 3280mV. Probably rather a HW problem. But the SW should not send wrong data. This makes the sensor useless.
22:30:571763
dev id:ttn-node-01payload:0CD0001008E9battery:3280event:"motion"light:16temperature:22.81
... hundreds of messages later..
11:26:122514
dev id:ttn-node-01payload:0CD6002908E3battery:3280event:"button"light:41temperature:22.75
actual DMM measured battery voltage: 2.0V
In this case the SW should somehow indicate in the message, that the data is invalid.
After the battery voltage has dropped to some voltage (e.g. 2.9V), the readout always returns the same value for all following messages sent (hundreds) although the DMM measured battery voltage is much below the reported fixed value of 3280mV. Probably rather a HW problem. But the SW should not send wrong data. This makes the sensor useless.
22:30:571763
dev id:ttn-node-01payload:0CD0001008E9battery:3280event:"motion"light:16temperature:22.81
... hundreds of messages later..
11:26:122514
dev id:ttn-node-01payload:0CD6002908E3battery:3280event:"button"light:41temperature:22.75
actual DMM measured battery voltage: 2.0V
In this case the SW should somehow indicate in the message, that the data is invalid.