[BUG] Battery operated devices appears as "unavailable after some time
See original GitHub issueEnvironment
- ShellyForHASS release with the issue: 0.1.9
- Last working ShellyForHASS release (if known): I guess ~ 0.1.6
- Home Assistant Core release with the issue: 0.112 - 0.113
- Operating environment (Home Assistant/Supervised/Docker/venv): HASSIO - Home Assistant
Describe the bug
Sometimes it happens, that one or multiple Door / Window Sensors appear as “unavailable”. When i check the details, one sensor change the status from “Closed” to “Unavailabe” 10 hours ago, another one 3 hours ago. I never saw this before, only when the batteries are empty and the device is dead. If i force the sensor waking up (e.g. open / closed the window/door) than its “alive” again. This happens not only for specific sensors, it happens randomly for mostly every of my D/W sensor at no specific time
Steps to Reproduce
Unfortunately there is no way to reproduce, it simply happens randomly
Expected behavior
It should stay with the last status. Maybe only mark them as “unavailable” when it doesn’t update for over 72 hours
Screenshots
Traceback/Error logs
Additional context
Issue Analytics
- State:
- Created 3 years ago
- Comments:20 (4 by maintainers)
Top Results From Across the Web
7 Ways to Fix the “No Battery Is Detected” Error on Windows
So, let's take a look at how you can restart the battery drivers: Press Win + X and select Device Manager from the...
Read more >Conbee 2 devices not available after HA shutdown
I have waited quite a while after I turned on HA again but all entities remain unavailable, battery powered and mains powered. If...
Read more >How to Fix 'No Battery Is Detected' on Your Laptop - Lifewire
Update the battery's device drivers. Open Device Manager, then select Batteries > your laptop's battery name > Driver > Update Driver > Search ......
Read more >ZIGBEE Devices going Unavailable / Unable to add
Try turning off the unavailable feature and see if the sensor work. There is an issue with this new feature. Couple of mines...
Read more >Common Android 12 problems and how to fix them
1. Go to Settings, then select Developer options. 2. Select Bluetooth PBAP, then choose Bluetooth BPAP version. 3. Select PBAP 1.1, then choose...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I had overlooked one very useful feature in the Shelly DW2. This was disabled by default:
I enabled it, and ever since my Shelly DW2 has been waking up throughout the day to report illuminance and temperature values. This is the illuminance history:
I’m very happy with these results, hopefully it will last.
As for the Shelly Motion, it has a bug that causes it to never wake up from low power mode if it doesn’t detect any motion for a long time. It has been reported and the devs are working on it: https://www.shelly-support.eu/forum/index.php?thread/8921-device-is-offline/ https://www.shelly-support.eu/forum/index.php?thread/8905-wifi-re-connect/
@rousveiga
No, actually I’m the one still learning things: I was oblivious to that setting in the Shellys! Thanks for the share, and I again hope you can figure it out.