ShellyForHASS: [BUG] Battery operated devices appears as "unavailable after some time
Environment
- 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
About this issue
- Original URL
- State: open
- Created 4 years ago
- Comments: 20 (4 by maintainers)
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.
@rousveiga I hope you can figure it out.
One thing though: whatever you’re doing in the network to configure things as unicast, I’m not sure that will improve things.
My understanding is that for Shelly CoAP to function properly, it requires multicast to be working with no hiccups. Configuring the network to expressly use only unicast might actually compound on any issues that were already present.
Try to check the mdns is working correctly on openwrt I had to load some extra modules to get multi cast to work correctly. Search Google for how to test multicast on your system. Remember to check on your machine that is running home assistant as can be a internal problem very hard to give instructions on how to do as some many different ways of doing things