-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
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
ZHA: Offline devices recognized as on every 4 hours #80519
Comments
Hey there @dmulcahey, @Adminiuga, @puddly, mind taking a look at this issue as it has been labeled with an integration ( zha documentation |
Can you enable full debug logging (instructions in the zha docs) and capture logs. Please share them without filtering them in any way. |
Here are the logs from today, which were already recorded with my current log settings (didn't checked how to enable full debug logging until now). I hope that they are also helpful. The IKEA bulb was offline all the time. The affected device is:
|
There's no homeassistant.core module logging present. Can tell the status of the device, other than zha failed to read that device. Is the log from a HACore restart? |
I have enabled homeassistant.core debug logging and restarted. |
What is your logging configuration? |
Now it is:
Correct? By the way: The Zigbee setting "consider device as unavailable after ..." is set to 60 seconds. Maybe this is causing a timing issue with other components.. |
Here is more. "Lampe Bad" changed from unavailable to on at 03:16:14.
|
I need unfiltered logs. Can you share the entire HA log file ? |
Just for completeness — this seems to be the same issue as: |
The logfile is currently bigger than 50 MB and honestly I'm a bit concerned that sensitive information (MAC addresses, credentials,...) could be leaked by some of the integrations. Do you need logs from a larger timeframe? Are the log settings as seen in my earlier post sufficient? |
Send link to logs directly to devs then. From the earlier logs, how long after restart was the 03:16:09.359 time? Looks like the device changes the state right after all async_initialize attempts fail. @steffen890 you are saying the device goes online every 4 hours (while physically offline) do you see attempts to do "async_initialize" for that device every 4 hours? Question: does "device" availability takes precedence over entity's availability? In other words, when the device is marked unavailable, but the entity still tries to "initialize" in the background, fails to initialize but returns the "cashed" state. Would it mess up the "state" machine in the core? |
Yes, every 4 hours:
|
The problem
Hi,
I have a few IKEA bulbs which switches from unavilable to on every 4 hours, while they are still turned off by the wall switch. This happens simultanously for all unavailable devices. After five minutes they switch back to unavailable.
I would like to resolve issue this since I use this event (unavailable / on) for triggering other lights.
Thanks
Steffen
What version of Home Assistant Core has the issue?
core-2022.10.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
ZHA
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
Zigbee coordinator is "Texas Instruments Z-Stack ZNP protocol: CC253x, CC26x2, CC13x2".
The text was updated successfully, but these errors were encountered: