core: fritzbox after timeout entities are no longer available
The problem
For some time now, the entities in AVM Fritz!SmartHome are no longer available after a short time in use. A reload of the integration does not help.If you restart the core, the entities are available again and work as usual. Since I missed the exact time since it started, I can not say whether it started since the update of FritzOS to 7.28 or HomeAssistant. A new setup of the integration brought nothing. It works briefly, then again not. I have read through the issues concerning AVM here and the following logs: logs: homeassistant.components.fritz: debug fritzconnection: debug fritzprofiles: debug
I can only find the posted timeout though.
I am running a Fritzbox 7590 with a FritzRepeate 2400, different Fritz!Dect 301, Fritz!DECT 210 and two Fritz!Dect 440.
I don’t know if this helps, just as a little additional information: To help me temporarily, I run a parallel Hombridge with the following plugin https://github.com/SeydX/homebridge-fritz-platform#readme to access the devices in Homekit. Here the problem does not occur.
Translated with www.DeepL.com/Translator (free version)
What is version of Home Assistant Core has the issue?
core-2021.9.7
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
AVM FRITZ!SmartHome
Link to integration documentation on our website
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
2021-09-28 01:09:05 ERROR (MainThread) [homeassistant.components.fritzbox] Timeout fetching f3e8e043184b5baef08f0c5852c06a14 data
Additional information

About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 40 (12 by maintainers)
I already made similar observations, but in addition it seems that the API session gets invalid from Fritz!Box side, but integration does not renew the session … for that i’m already thinking about a fix …
This looks like a short DNS outage (the Fritz!Box usually works as DNS server) where the negative or non-existing answer gets cached by the core.
In other words: HA asks the DNS server every time it accesses the entities. But when it gets a timeout from DNS it never asks again until the core is restarted.
Thank you @mib1185 , I have added this and will report as soon as the error occurs again