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
Device trackers unavailable for few minutes almost every day #72375
Comments
fritz documentation |
Hey there @mammuth, @AaronDavidSchneider, @chemelli74, @mib1185, mind taking a look at this issue as it has been labeled with an integration ( |
Hi @FabioEight, please add the following to 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. |
config_entry-fritz-b0aa7442c46c1690e8c52b4bce5a518a.json.txt |
Hi @FabioEight please provide the home-assistant.log as requested by @chemelli74 in #72375 (comment) |
home-assistant.zip |
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. |
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
The text was updated successfully, but these errors were encountered: