get_mesh_topology() does not get all hosts

[kongo09]

I'm not 100% familiar with the precise differences of the active hosts vs mesh nodes concept, but I noticed the following:

• Using fh.get_active_hosts() I correctly get all my hosts as I see them in the Fritz!Box interface
• Using fh.get_mesh_topology() I get a much shorter list of devices, notably missing those that are wired on the main network, while the guest network devices are present

Shouldn't the active hosts be part of the mesh topology? At least, that's how it is displayed in the Fritz!Box interface.

[kongo09]

I've now followed the code down to the actual X_AVM-DE_GetMeshListPath and manually called the URL of NewX_AVM-DE_MeshListPath for the lua script that is supposed to generate the mesh list.

The resulting json file is indeed incomplete. It does not contain all the active hosts that I see in my interface or that the get_active_hosts() function would produce.

That sounds to me like this is not a bug in the code, but a bug in the Fritz!Box itself - or are there good reasons why some active hosts should be left out of the mesh topology?

This is on a Fritz!Box 6660 Cable (retail version)

[kongo09]

I've contacted AVM to find out if this is a bug or a feature.

[kbr]

Thanks. If the json is incomplete then from our side it would just be guessing about.

[kongo09]

AVM acknowledged the receipt of my message, retrieved my diagnostic data and told me that they try to replicate it in their lab.

[mib1185]

this is a known bug with LLDP enabled LAN connected devices (see https://github.com/home-assistant/core/issues/66887#issuecomment-1051982504) AVM already confirmed it as a bug, which should be solved with next FritzOS planned for end of Q2/2022 (see https://github.com/home-assistant/core/issues/66887#issuecomment-1054313855)

[kbr]

As this is related to FritzOS I like to close the issue. Please feel free to reopen in case of need.

[kongo09]

That's fair. AVM never got back to me about this.