You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Site tells you to enable the old discovery method in some cases. But I can't find any documentation on what the differences are between the old and new discovery methods. What disadvantages do I get by enabling the old method? There must be something, or it wouldn't have been replaced by a new method. Also, does changing the discovery method from new to old re-discover all devices, maybe ignoring name changes that I did and breaking automations?
The new (and default used) method is based on the mesh topology data of the fritzbox and has some advantages like you know via which mesh-device (fritzobx or repeater) your device is connected.
But this mesh topology data don't work correct on non-meshed setups or when there are 3rd party network devices involved (eq. switches or non-AVM access points).
Understood. So I have the choice of benefiting from this fix and being able to track the access point of my device, OR being able to have automations based on whether LAN devices are turned on or not.
Is it known if the fact that I have switches on my network will ruin the whole enter/leave detection of LAN devices or will it work as long as the LAN device is directly connected to a Fritzbox (or a secondary Fritzbox that is connected to the master via a switch)?
Feedback
Site tells you to enable the old discovery method in some cases. But I can't find any documentation on what the differences are between the old and new discovery methods. What disadvantages do I get by enabling the old method? There must be something, or it wouldn't have been replaced by a new method. Also, does changing the discovery method from new to old re-discover all devices, maybe ignoring name changes that I did and breaking automations?
URL
https://www.home-assistant.io/integrations/fritz/
Version
2024.11.2
Additional information
No response
The text was updated successfully, but these errors were encountered: