-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
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
Shelly Motion sensors unavailable while CoAP messages are coming in #117734
Comments
Hey there @balloob, @bieniu, @thecode, @chemelli74, @bdraco, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) shelly documentation |
@rhoddan by similar I assume you checked the logs and saw that CoAP packets arrive correctly? can you share the log and diagnostics? @PimDoos can you retest with core 2024.5.5, it should resolve this issue - #116975 (comment) |
Same issue with a Shelly Motion Sensor, deleting and reinstalling this from the integration fixes it for an hour or so, rebooting HA makes it work for around a day. The sensor uses a fixed IP 192.168.178.xxx:5683, CoLot is enabled, MQTT is Clean Session enabled, Max QoS=1 Rebooting the device has no effect, the device functions normally via http btw this is with Core 2024.5.5 |
After upgrading to 2024.5.5, the issue persists for me.
|
Having similar issue with my TRVs. COAP messages arrive.
|
Ironically, since I posted this I restarted HA once and did not have any issues with any of my battery powered Shelly devices since. |
Today I performed a 12-hour Shelly Motion test. Device entities in HA were available all the time. We suspect that the problem may be caused by blocking the event loop by another integration (probably custom one). The CoIoT packet with status reaches the HA server but cannot be processed correctly. |
I've run HA with debug mode enabled for just over a day, and this one stands out: I'll disable entsoe and see if that fixes the issue. Looks like the issue has already been reported with the custom integration. JaccoR/hass-entso-e#156 |
The problem
My Shelly Motion sensors (gen 1, SHMOS-01 and SHMOS-02) become unavailable within about 1 hour 15 minutes after startup.
After restarting Home Assistant or reloading the Shelly integration, the sensors work fine for just over 1 hour. After this, they become unavailable.
I have enabled debug logging (see attached files) for
aioshelly
andhomeassistant.components.shelly
. In the logs I see two things happening:aioshelly
shows the devices are sending periodic CoAP messages every 30 minutes, as they shouldshelly
component logsError fetching <device name> data: Sleeping device did not update within 3600 seconds interval
What version of Home Assistant Core has the issue?
core-2024.5.4
What was the last working version of Home Assistant Core?
core-2024.4.4
What type of installation are you running?
Home Assistant OS
Integration causing the issue
shelly
Link to integration documentation on our website
https://www.home-assistant.io/integrations/shelly/
Diagnostics information
shelly-overloop.log
shelly-toilet.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
State history for the 'Toilet Motion' and and 'Overloop Motion' sensors during the log snippets.
The text was updated successfully, but these errors were encountered: