-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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 Plus H&T constantly raising error "Sleeping device did not update within 7200 seconds interval" #85563
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 |
@MacrosorcH can you download diagnostics from the device card in Home Assistant and attach in a comment? Thanks |
@thecode Many thanks for the quick reply! Here is the diagnostics file: |
Can you please add the following to logger:
default: info
logs:
aioshelly: debug
homeassistant.components.shelly: debug Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub. Thanks |
There is a bug where we try to stop the ble scanner because it is disabled. We should not do this on sleepy devices. Its only now apparent because the lib used to swallow the exception |
Also opened home-assistant-libs/aioshelly#330 to fix the |
The problem
Every time it wakes up to report new temperature/humidity values, the Shelly Plus H&T triggers a "Sleeping device did not update within 7200 seconds interval" error in the logs. See logs below.
What version of Home Assistant Core has the issue?
2023.1.2
What was the last working version of Home Assistant Core?
2022.12.x
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
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: