Device trackers unavailable for few minutes almost every day

Question

Device trackers unavailable for few minutes almost every day

FabioEight opened this issue 2 years ago · comments

The problem

Since few weeks, at least once everyday, the FritzBox integration stop working: without any apparent reason, HA is detecting most of the device trackers as unavailable.
After few minutes, the entities are properly restored.
No actions are done to restore the correct operation of the entities.
I have a 7530 and 2 repeater 2400 but I have only configured the integration for the 7530.

Thanks!

What version of Home Assistant Core has the issue?

2022.5.5

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

fritz

Link to integration documentation on our website

https://www.home-assistant.io/integrations/fritz/

Diagnostics information

config_entry-fritz-b0aa7442c46c1690e8c52b4bce5a518a.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

probot-home-assistant · Answer 1 · Mon May 23 2022 23:53:05 GMT+0800 (China Standard Time)

fritz documentation
fritz source
_{^{(message by IssueLinks)}}

probot-home-assistant · Answer 2 · Mon May 23 2022 23:53:08 GMT+0800 (China Standard Time)

Hey there @mammuth, @AaronDavidSchneider, @chemelli74, @mib1185, mind taking a look at this issue as it has been labeled with an integration (fritz) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

Simone Chemelli · Answer 3 · Wed May 25 2022 21:26:28 GMT+0800 (China Standard Time)

Hi @FabioEight, please add the following to configuration.yaml , restart HA, and post the log:

logger:
  default: warning
  logs:
    homeassistant.components.fritz: debug
    fritzconnection: info

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.

Fabio Eight · Answer 4 · Thu May 26 2022 15:15:24 GMT+0800 (China Standard Time)

config_entry-fritz-b0aa7442c46c1690e8c52b4bce5a518a.json.txt
For example, I noticed the same behaviour for my device at 5.50 GMT+2

Michael · Answer 5 · Thu Jun 09 2022 06:01:17 GMT+0800 (China Standard Time)

Hi @FabioEight please provide the home-assistant.log as requested by @chemelli74 in #72375 (comment)

Fabio Eight · Answer 6 · Fri Jun 10 2022 22:58:09 GMT+0800 (China Standard Time)

home-assistant.zip
Hello, here in attachment the log requested. The issue happened at 16.49.
Thank you!

github-actions · Answer 7 · Fri Jun 24 2022 23:06:02 GMT+0800 (China Standard Time)

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.