Closed jf-64 closed 1 hour ago
Hey there @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)
fritz documentation fritz source (message by IssueLinks)
Hi @jf-64 please provide a debug log as described in the troubleshooting section of the integrations documentation, thx :+1:
Sorry, I cannot provide debug log.
The problem
Since the FritzOS 8.0 I get frequently incorrect values for device_tracker:
not_home
if the device is still online (the device is still reachable by other tools).home
, if e.g. the device´s switch entity is unavailable, because the device is offline (as e.g. said by the Smart Life app for a Tuya device). Thus, now I'm monitoring for a device beside the device_tracker's entity value also the state of the switch's entity (if any) and the combination of both of them gives the online/offline information.The monitoring and power resets are done by Node RED/MQTT.
What version of Home Assistant Core has the issue?
2024.11.1
What was the last working version of Home Assistant Core?
2024.11.1
What type of installation are you running?
Home Assistant OS
Integration causing the issue
AVM FRITZ!Box Tools
Link to integration documentation on our website
https://www.home-assistant.io/integrations/fritz
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
I have 8 FritzBox routers in a Mesh and over 100 IoT devices. I let automatically monitor the most important devices and by automatically initiated power off and on (of the device) I let them reset if they're loosing the WIFI connection.
The number of power resets increased dramatically since the upgrade to Fritz OS 8.0. Actually, I'm not quite sure whether it is because of
Points 1. + 2. are there for sure, ergo, also 3.