-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Temperature stuck due to dead sensor but no indication of sensor being dead #248
Comments
Unsure what the expected action is wrt to software changes sorry. |
This happens when the sensor battery dies - it's actually quite a good indicator when it suddenly spikes to a large negative number. Can we please hold off working on this for now as there are many higher priority issues than this we could work on. @louisaw123 - can you remove the client details from this ticket (this is a public repo so anyone on the internet can read) - cheers! |
removed! thanks! |
Thanks @louisaw123 :)) |
perhaps not an issue with the longer battery life? |
Describe the bug
Blue Maestro small sensor stuck at -39 degrees and continued recording this temperature (screenshot). Battery sensor at the time 32%. On replacing the battery the sensor went back to normal.
History of Battery sensor %:
18/08/23: 44%
[unable to get recordings in between this time due to no sync]
23/08/23: 36%
24/08.23: 32%
: Yep, they usually die around 32%. I was expecting it to go. When the battery dies, sometimes the data goes haywire & sometimes they just stop recording or transmitting or both.
To Reproduce
?when battery sensor reaches 32% - although this may be variable as sensors have been working at less than this
Expected behavior
If the sensor is dead it should be dead and not able to record any data. However, this sensor is transmitting false temperature readings to the server and the battery % is still at 32% and so is not necessarily dead from a user perspective. If the sensor is dead it should stop transmitting any data and the battery should be 0%.
The text was updated successfully, but these errors were encountered: