Skip to content
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

Enable old discovery method - what is the difference? #35840

Open
cguthardt opened this issue Nov 20, 2024 · 4 comments
Open

Enable old discovery method - what is the difference? #35840

cguthardt opened this issue Nov 20, 2024 · 4 comments
Assignees

Comments

@cguthardt
Copy link

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

@home-assistant
Copy link

Hey there @mammuth, @AaronDavidSchneider, @chemelli74, @mib1185, mind taking a look at this feedback as it has been labeled with an integration (fritz) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of fritz can trigger bot actions by commenting:

  • @home-assistant close Closes the feedback.
  • @home-assistant rename Awesome new title Renames the feedback.
  • @home-assistant reopen Reopen the feedback.
  • @home-assistant unassign fritz Removes the current integration label and assignees on the feedback, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

@cguthardt
Copy link
Author

I got to this because I am experiencing this problem with FritzOS 8.0

@mib1185
Copy link
Contributor

mib1185 commented Nov 20, 2024

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).

@cguthardt
Copy link
Author

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)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants