search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.28k stars 30.6k forks source link

AVM FRITZ!Box Tools Internet Access Switch greyed out #104646

Closed evilmumi closed 8 months ago

evilmumi commented 11 months ago

The problem

If the device is offline i cant toggle Internet Access Switch because its greyed out

What version of Home Assistant Core has the issue?

2023.11.2

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!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

No response

home-assistant[bot] commented 11 months ago

Hey there @mammuth, @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!

Code owner commands Code owners of `fritz` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign fritz` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)

fritz documentation fritz source (message by IssueLinks)

chemelli74 commented 11 months ago

Hi, this is by design: if the device is not available, then the user cannot change the related settings.

evilmumi commented 11 months ago

Thanks - is it possible to change the design? in the fritzbox itself it is possible to do even if the device is offline.

chemelli74 commented 11 months ago

Thanks - is it possible to change the design? in the fritzbox itself it is possible to do even if the device is offline.

Offline is different than unavailable

evilmumi commented 11 months ago

It's a normal pc which is not powered on. So whats the difference between offline and unavailable

DEVIDTR commented 10 months ago

Hi, all of my internet access setting are disabled regardless of the device state! This behavior started in 2023.11.x

chemelli74 commented 10 months ago

Please add the following to configuration.yaml , restart HA, and post the log:

logger:
  default: warning
  logs:
    homeassistant.components.fritz: debug
    fritzconnection: info

Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub.

And add diagnostics (menu configuration -> integration -> fritz tools -> download diagnostics )

evilmumi commented 9 months ago

I still have problem of not switchable internet access because of that :

2024-01-19 01:00:00.278 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.pc_internet_access are missing or not currently available image greyed out

Migaddo commented 8 months ago

I have the same issue when in add my repeaters (3x), after 15 min alle the "Internet Access" become unavailable. if i delete the repeaters from the integration and reload the integration, they all come available again.

Fritz 7590 FRITZ!REPEATER 3000 AX 2x FRITZ!REPEATER 6000 1x

mib1185 commented 8 months ago

without logs and possible diagnostics data from https://github.com/home-assistant/core/issues/104646#issuecomment-1875869764 we can't analyse anything

evilmumi commented 8 months ago

what do you need exactly - how long the logs? just restarted HA with logger and PC still greyed out (offline since19 hours) image

mib1185 commented 8 months ago

everything between restart of HA (with enabled debug logging) and the time when the issue occur

evilmumi commented 8 months ago

I would like to cut unimportant stuff out because of "confidential" content.


2024-02-07 13:13:04.907 DEBUG (SyncWorker_8) [homeassistant.components.fritz.common] detected services on 192.168.0.1 ['any1', 'WANCommonIFC1', 'WANDSLLinkC1', 'WANIPConn1', 'WANIPv6Firewall1', 'DeviceInfo1', 'DeviceConfig1', 'Layer3Forwarding1', 'LANConfigSecurity1', 'ManagementServer1', 'Time1', 'UserInterface1', 'X_AVM-DE_Storage1', 'X_AVM-DE_WebDAVClient1', 'X_AVM-DE_UPnP1', 'X_AVM-DE_Speedtest1', 'X_AVM-DE_RemoteAccess1', 'X_AVM-DE_MyFritz1', 'X_VoIP1', 'X_AVM-DE_OnTel1', 'X_AVM-DE_Dect1', 'X_AVM-DE_TAM1', 'X_AVM-DE_AppSetup1', 'X_AVM-DE_Homeauto1', 'X_AVM-DE_Homeplug1', 'X_AVM-DE_Filelinks1', 'X_AVM-DE_Auth1', 'X_AVM-DE_HostFilter1', 'X_AVM-DE_Media1', 'X_AVM-DE_USPController1', 'WLANConfiguration1', 'WLANConfiguration2', 'WLANConfiguration3', 'Hosts1', 'LANEthernetInterfaceConfig1', 'LANHostConfigManagement1', 'WANCommonInterfaceConfig1', 'WANDSLInterfaceConfig1', 'X_AVM-DE_WANMobileConnection1', 'WANDSLLinkConfig1', 'WANEthernetLinkConfig1', 'WANPPPConnection1', 'WANIPConnection1']
2024-02-07 13:13:04.985 DEBUG (SyncWorker_8) [homeassistant.components.fritz.common] gathered device info of 192.168.0.1 {'manufacturer_name': 'AVM', 'manufacturer_oui': '00040E', 'model_name': 'FRITZ!Box 6590 Cable', 'description': 'FRITZ!Box 6590 Cable Release 148.07.57', 'product_class': 'FRITZ!Box', 'serial_number': 'SERIALNUMBER', 'software_version': '148.07.57', 'hardware_version': 'FRITZ!Box 6590 Cable', 'spec_version': '1.0', 'provisioning_code': '', 'up_time': 12718302, 'device_log': '', 'NewDeviceLog': '***omitted***', 'NewSerialNumber': '***omitted***'}
2024-02-07 13:13:05.354 DEBUG (MainThread) [homeassistant.components.fritz.common] Checking host info for FRITZ!Box device 192.168.0.1
2024-02-07 13:13:05.408 DEBUG (MainThread) [homeassistant.components.fritz.common] Checking devices for FRITZ!Box device 192.168.0.1

2024-02-07 13:13:11.614 DEBUG (MainThread) [homeassistant.components.fritz.common] Client dev_info: Device(connected=True, connected_to='fritz.repeater', connection_type='WLAN', ip_address='192.168.0.91', name='TimsFireTVStick', ssid='SSIDNAME', wan_access=True)

...ALOT WLAN DEVICES... NOT THE GREYED ONE

2024-02-07 13:13:11.688 DEBUG (MainThread) [homeassistant.components.fritz.common] enity_data: {'call_deflections': {}, 'entity_states': {}}
2024-02-07 13:13:11.688 DEBUG (MainThread) [homeassistant.components.fritz.common] Finished fetching fritz-192.168.0.1-coordinator data in 6.334 seconds (success: True)
2024-02-07 13:13:12.602 DEBUG (MainThread) [homeassistant.components.fritz.button] Setting up buttons
2024-02-07 13:13:12.605 DEBUG (MainThread) [homeassistant.components.fritz.binary_sensor] Setting up FRITZ!Box binary sensors
2024-02-07 13:13:12.609 DEBUG (MainThread) [homeassistant.components.fritz.device_tracker] Starting FRITZ!Box device tracker
2024-02-07 13:13:12.615 DEBUG (MainThread) [homeassistant.components.fritz.sensor] Setting up FRITZ!Box sensors
2024-02-07 13:13:12.661 DEBUG (MainThread) [homeassistant.components.fritz.switch] Setting up switches
2024-02-07 13:13:12.661 DEBUG (MainThread) [homeassistant.components.fritz.switch] Fritzbox services: {'any1': <fritzconnection.core.processor.Service object at 0x7fafe328e2d0>, 'WANCommonIFC1': <fritzconnection.core.processor.Service object at 0x7fafe32967d0>, 'WANDSLLinkC1': <fritzconnection.core.processor.Service object at 0x7fafe3296c90>, 'WANIPConn1': <fritzconnection.core.processor.Service object at 0x7fafe3296e50>, 'WANIPv6Firewall1': <fritzconnection.core.processor.Service object at 0x7fafe3296fd0>, 'DeviceInfo1': <fritzconnection.core.processor.Service object at 0x7fafe329ebd0>, 'DeviceConfig1': <fritzconnection.core.processor.Service object at 0x7fafe329ed50>, 'Layer3Forwarding1': <fritzconnection.core.processor.Service object at 0x7fafe329ee10>, 'LANConfigSecurity1': <fritzconnection.core.processor.Service object at 0x7fafe329eed0>, 'ManagementServer1': <fritzconnection.core.processor.Service object at 0x7fafe329ef50>, 'Time1': <fritzconnection.core.processor.Service object at 0x7fafe329f110>, 'UserInterface1': <fritzconnection.core.processor.Service object at 0x7fafe329f2d0>, 'X_AVM-DE_Storage1': <fritzconnection.core.processor.Service object at 0x7fafe329f490>, 'X_AVM-DE_WebDAVClient1': <fritzconnection.core.processor.Service object at 0x7fafe329f650>, 'X_AVM-DE_UPnP1': <fritzconnection.core.processor.Service object at 0x7fafe329f7d0>, 'X_AVM-DE_Speedtest1': <fritzconnection.core.processor.Service object at 0x7fafe329f990>, 'X_AVM-DE_RemoteAccess1': <fritzconnection.core.processor.Service object at 0x7fafe329fb10>, 'X_AVM-DE_MyFritz1': <fritzconnection.core.processor.Service object at 0x7fafe329fc90>, 'X_VoIP1': <fritzconnection.core.processor.Service object at 0x7fafe329fdd0>, 'X_AVM-DE_OnTel1': <fritzconnection.core.processor.Service object at 0x7fafe329ff90>, 'X_AVM-DE_Dect1': <fritzconnection.core.processor.Service object at 0x7fafe3298150>, 'X_AVM-DE_TAM1': <fritzconnection.core.processor.Service object at 0x7fafe3298310>, 'X_AVM-DE_AppSetup1': <fritzconnection.core.processor.Service object at 0x7fafe32984d0>, 'X_AVM-DE_Homeauto1': <fritzconnection.core.processor.Service object at 0x7fafe3298690>, 'X_AVM-DE_Homeplug1': <fritzconnection.core.processor.Service object at 0x7fafe3298850>, 'X_AVM-DE_Filelinks1': <fritzconnection.core.processor.Service object at 0x7fafe3298a10>, 'X_AVM-DE_Auth1': <fritzconnection.core.processor.Service object at 0x7fafe3298bd0>, 'X_AVM-DE_HostFilter1': <fritzconnection.core.processor.Service object at 0x7fafe3298d90>, 'X_AVM-DE_Media1': <fritzconnection.core.processor.Service object at 0x7fafe3298f50>, 'X_AVM-DE_USPController1': <fritzconnection.core.processor.Service object at 0x7fafe3299110>, 'WLANConfiguration1': <fritzconnection.core.processor.Service object at 0x7fafe3299650>, 'WLANConfiguration2': <fritzconnection.core.processor.Service object at 0x7fafe32997d0>, 'WLANConfiguration3': <fritzconnection.core.processor.Service object at 0x7fafe3299990>, 'Hosts1': <fritzconnection.core.processor.Service object at 0x7fafe3299b50>, 'LANEthernetInterfaceConfig1': <fritzconnection.core.processor.Service object at 0x7fafe327d910>, 'LANHostConfigManagement1': <fritzconnection.core.processor.Service object at 0x7fafe3299e50>, 'WANCommonInterfaceConfig1': <fritzconnection.core.processor.Service object at 0x7fafe671b890>, 'WANDSLInterfaceConfig1': <fritzconnection.core.processor.Service object at 0x7fafe329a2d0>, 'X_AVM-DE_WANMobileConnection1': <fritzconnection.core.processor.Service object at 0x7fafe329a610>, 'WANDSLLinkConfig1': <fritzconnection.core.processor.Service object at 0x7fafe329a790>, 'WANEthernetLinkConfig1': <fritzconnection.core.processor.Service object at 0x7fafe329a950>, 'WANPPPConnection1': <fritzconnection.core.processor.Service object at 0x7fafe329aa50>, 'WANIPConnection1': <fritzconnection.core.processor.Service object at 0x7fafe329ac10>}
2024-02-07 13:13:12.661 DEBUG (MainThread) [homeassistant.components.fritz.switch] Setting up CallDeflection switches
2024-02-07 13:13:12.661 DEBUG (MainThread) [homeassistant.components.fritz.switch] Setting up PortForward switches
2024-02-07 13:13:12.665 DEBUG (MainThread) [homeassistant.components.fritz.update] Setting up AVM FRITZ!Box update entities
2024-02-07 13:13:12.725 DEBUG (MainThread) [homeassistant.components.fritz.common] ConnectionInfo for FritzBox 192.168.0.1: ConnectionInfo(connection='x_avm-de_cable', mesh_role=<MeshRoles.MASTER: 'master'>, wan_enabled=True, ipv6_active=True)
2024-02-07 13:13:12.725 DEBUG (MainThread) [homeassistant.components.fritz.common] register entity is_connected for updates
2024-02-07 13:13:12.725 DEBUG (MainThread) [homeassistant.components.fritz.common] register entity is_linked for updates
2024-02-07 13:13:12.729 DEBUG (MainThread) [homeassistant.components.fritz.common] Checking host info for FRITZ!Box device 192.168.0.1
2024-02-07 13:13:12.827 DEBUG (MainThread) [homeassistant.components.fritz.common] Checking devices for FRITZ!Box device 192.168.0.1
2024-02-07 13:13:12.827 DEBUG (MainThread) [homeassistant.components.fritz.switch] Specific PortForward response: GetPortMappingNumberOfEntries=4
2024-02-07 13:13:12.827 DEBUG (MainThread) [homeassistant.components.fritz.switch] IP source for 192.168.0.1 is 192.168.0.148
2024-02-07 13:13:12.851 DEBUG (MainThread) [homeassistant.components.fritz.common] ConnectionInfo for FritzBox 192.168.0.1: ConnectionInfo(connection='x_avm-de_cable', mesh_role=<MeshRoles.MASTER: 'master'>, wan_enabled=True, ipv6_active=True)
2024-02-07 13:13:12.851 DEBUG (MainThread) [homeassistant.components.fritz.common] register entity external_ip for updates
2024-02-07 13:13:12.851 DEBUG (MainThread) [homeassistant.components.fritz.common] register entity external_ipv6 for updates
2024-02-07 13:13:12.851 DEBUG (MainThread) [homeassistant.components.fritz.common] register entity device_uptime for updates
2024-02-07 13:13:12.851 DEBUG (MainThread) [homeassistant.components.fritz.common] register entity connection_uptime for updates
2024-02-07 13:13:12.851 DEBUG (MainThread) [homeassistant.components.fritz.common] register entity kb_s_sent for updates
2024-02-07 13:13:12.851 DEBUG (MainThread) [homeassistant.components.fritz.common] register entity kb_s_received for updates
2024-02-07 13:13:12.851 DEBUG (MainThread) [homeassistant.components.fritz.common] register entity max_kb_s_sent for updates
2024-02-07 13:13:12.851 DEBUG (MainThread) [homeassistant.components.fritz.common] register entity max_kb_s_received for updates
2024-02-07 13:13:12.851 DEBUG (MainThread) [homeassistant.components.fritz.common] register entity gb_sent for updates
2024-02-07 13:13:12.852 DEBUG (MainThread) [homeassistant.components.fritz.common] register entity gb_received for updates
2024-02-07 13:13:12.852 DEBUG (MainThread) [homeassistant.components.fritz.common] register entity link_kb_s_sent for updates
2024-02-07 13:13:12.852 DEBUG (MainThread) [homeassistant.components.fritz.common] register entity link_kb_s_received for updates

... DELETE PORTFORWARD ....

2024-02-07 13:13:13.382 DEBUG (MainThread) [homeassistant.components.fritz.switch] Setting up WiFiNetwork switches
2024-02-07 13:13:13.382 DEBUG (MainThread) [homeassistant.components.fritz.switch] WiFi networks count: 3

...DELETE WLAN INFORMATION ....

2024-02-07 13:13:13.692 DEBUG (MainThread) [homeassistant.components.fritz.switch] Setting up Profile switches
2024-02-07 13:13:13.693 DEBUG (MainThread) [homeassistant.components.fritz.switch] Creating 106 profile switches

2024-02-07 13:13:17.634 DEBUG (MainThread) [homeassistant.components.fritz.common] Client dev_info: Device(connected=True, connected_to='fritz.repeater', connection_type='WLAN', ip_address='192.168.0.91', name='TimsFireTVStick', ssid='bigbossbgn', wan_access=True)

leave as an example

2024-02-07 13:13:17.636 DEBUG (MainThread) [homeassistant.components.fritz.common] update entity is_connected
2024-02-07 13:13:17.643 DEBUG (MainThread) [homeassistant.components.fritz.common] update entity is_linked
2024-02-07 13:13:17.683 DEBUG (MainThread) [homeassistant.components.fritz.common] update entity external_ip
2024-02-07 13:13:17.686 DEBUG (MainThread) [homeassistant.components.fritz.common] update entity external_ipv6
2024-02-07 13:13:17.725 DEBUG (MainThread) [homeassistant.components.fritz.common] update entity device_uptime
2024-02-07 13:13:17.771 DEBUG (MainThread) [homeassistant.components.fritz.common] update entity connection_uptime
2024-02-07 13:13:17.778 DEBUG (MainThread) [homeassistant.components.fritz.common] update entity kb_s_sent
2024-02-07 13:13:17.827 DEBUG (MainThread) [homeassistant.components.fritz.common] update entity kb_s_received
2024-02-07 13:13:17.874 DEBUG (MainThread) [homeassistant.components.fritz.common] update entity max_kb_s_sent
2024-02-07 13:13:17.907 DEBUG (MainThread) [homeassistant.components.fritz.common] update entity max_kb_s_received
2024-02-07 13:13:17.991 DEBUG (MainThread) [homeassistant.components.fritz.common] update entity gb_sent
2024-02-07 13:13:18.011 DEBUG (MainThread) [homeassistant.components.fritz.common] update entity gb_received
2024-02-07 13:13:18.055 DEBUG (MainThread) [homeassistant.components.fritz.common] update entity link_kb_s_sent
2024-02-07 13:13:18.083 DEBUG (MainThread) [homeassistant.components.fritz.common] update entity link_kb_s_received
2024-02-07 13:13:18.212 DEBUG (MainThread) [homeassistant.components.fritz.common] enity_data: {'call_deflections': {}, 'entity_states': {'is_connected': True, 'is_linked': True, 'external_ip': 'IPV4adress', 'external_ipv6': '::', 'device_uptime': datetime.datetime(2023, 9, 13, 7, 21, 22, 771334, tzinfo=datetime.timezone.utc), 'connection_uptime': datetime.datetime(2023, 12, 9, 0, 36, 35, 777895, tzinfo=datetime.timezone.utc), 'kb_s_sent': 176.7, 'kb_s_received': 8170.6, 'max_kb_s_sent': 6805.0, 'max_kb_s_received': 115000.0, 'gb_sent': 686.0, 'gb_received': 6959.4, 'link_kb_s_sent': 6805.0, 'link_kb_s_received': 115000.0}}
2024-02-07 13:13:18.212 DEBUG (MainThread) [homeassistant.components.fritz.common] Finished fetching fritz-192.168.0.1-coordinator data in 5.483 seconds (success: True)
2024-02-07 13:17:14.704 DEBUG (MainThread) [homeassistant.components.fritz.image] fetched 315 bytes
evilmumi commented 8 months ago 

<Item>
<Index>106</Index>
<IPAddress>192.168.0.154</IPAddress>
<MACAddress>04:42:1A:30:1C:AC</MACAddress>
<Active>0</Active>
<HostName>TimPC</HostName>
<InterfaceType />
<X_AVM-DE_Port>0</X_AVM-DE_Port>
<X_AVM-DE_Speed>0</X_AVM-DE_Speed>
<X_AVM-DE_UpdateAvailable>0</X_AVM-DE_UpdateAvailable>
<X_AVM-DE_UpdateSuccessful>unknown</X_AVM-DE_UpdateSuccessful>
<X_AVM-DE_InfoURL />
<X_AVM-DE_MACAddressList>04:42:1A:30:1C:AC</X_AVM-DE_MACAddressList>
<X_AVM-DE_Model />
<X_AVM-DE_URL />
<X_AVM-DE_Guest>0</X_AVM-DE_Guest>
<X_AVM-DE_RequestClient>0</X_AVM-DE_RequestClient>
<X_AVM-DE_VPN>0</X_AVM-DE_VPN>
<X_AVM-DE_WANAccess>denied</X_AVM-DE_WANAccess>
<X_AVM-DE_Disallow>1</X_AVM-DE_Disallow>
<X_AVM-DE_IsMeshable>0</X_AVM-DE_IsMeshable>
<X_AVM-DE_Priority>0</X_AVM-DE_Priority>
<X_AVM-DE_FriendlyName>TimPC</X_AVM-DE_FriendlyName>
<X_AVM-DE_FriendlyNameIsWriteable>1</X_AVM-DE_FriendlyNameIsWriteable>
</Item>

then i start the windows pc and switch is no longer greyed out


2024-02-07 13:20:46.842 DEBUG (MainThread) [homeassistant.components.fritz.common] Client dev_info: Device(connected=False, connected_to='routi', connection_type='LAN', ip_address='192.168.0.154', name='TimPC', ssid='', wan_access=False)

<Item>
<Index>106</Index>
<IPAddress>192.168.0.154</IPAddress>
<MACAddress>04:42:1A:30:1C:AC</MACAddress>
<Active>1</Active>
<HostName>TimPC</HostName>
<InterfaceType>Ethernet</InterfaceType>
<X_AVM-DE_Port>3</X_AVM-DE_Port>
<X_AVM-DE_Speed>1000</X_AVM-DE_Speed>
<X_AVM-DE_UpdateAvailable>0</X_AVM-DE_UpdateAvailable>
<X_AVM-DE_UpdateSuccessful>unknown</X_AVM-DE_UpdateSuccessful>
<X_AVM-DE_InfoURL />
<X_AVM-DE_MACAddressList>04:42:1A:30:1C:AC</X_AVM-DE_MACAddressList>
<X_AVM-DE_Model />
<X_AVM-DE_URL />
<X_AVM-DE_Guest>0</X_AVM-DE_Guest>
<X_AVM-DE_RequestClient>0</X_AVM-DE_RequestClient>
<X_AVM-DE_VPN>0</X_AVM-DE_VPN>
<X_AVM-DE_WANAccess>denied</X_AVM-DE_WANAccess>
<X_AVM-DE_Disallow>1</X_AVM-DE_Disallow>
<X_AVM-DE_IsMeshable>0</X_AVM-DE_IsMeshable>
<X_AVM-DE_Priority>0</X_AVM-DE_Priority>
<X_AVM-DE_FriendlyName>TimPC</X_AVM-DE_FriendlyName>
<X_AVM-DE_FriendlyNameIsWriteable>1</X_AVM-DE_FriendlyNameIsWriteable>
</Item>
mib1185 commented 8 months ago

mhhh ... it's hard to hunt the issue without complete logs (context around the log messages is needed), further please provide The diagnostics data as requested in https://github.com/home-assistant/core/issues/104646#issuecomment-1875869764. Feel free to contact me via discord to exchange possibly sensitive data

evilmumi commented 8 months ago

just for information @mib1185 and me are in exchange

evilmumi commented 8 months ago

@mib1185 recommended to turn on old detection method in integration - we will see if it will help

DEVIDTR commented 8 months ago

Just for your information, when I deaktivate all AVM repeaters in my settings, internet access button is back as usual. I assume the code is handling a repeater the same way as it handles the router. So it sets the device state in mesh scenarios to not available and disables the internet access button. The code should treat a mesh repeater different from non mesh. This would also explain why the old detection method brings back the setting in some cases.

Von: evilmumi @.> Gesendet: Friday, February 16, 2024 9:01:59 AM An: home-assistant/core @.> Cc: Comment @.***> Betreff: Re: [home-assistant/core] AVM FRITZ!Box Tools Internet Access Switch greyed out (Issue #104646)

@mib1185https://github.com/mib1185 recommended to turn on old detection method in integration - we will see if it will help

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/104646#issuecomment-1947918290 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK5OQHUBNBY5W4TMWNGB4K3YT4G7RBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIYTEOBSHA3DSMRXHCSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKBRGI4DQOBZHEZYFJDUPFYGLJLJONZXKZNFOZQWY5LFVIZDAMJUGYZTOOBRGCBKI5DZOBS2K3DBMJSWZJLWMFWHKZNKGEZDQMRYGY4TENZYU52HE2LHM5SXFJTDOJSWC5DF. You are receiving this email because you commented on the thread.

Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

evilmumi commented 8 months ago

That is also what I understood from @mib1185 . I hope someone could change this

mib1185 commented 8 months ago

The new discovery method (default) combines the new mesh topology and old host data of the Fritzbox to identify connected devices and their states. the mesh data are the primary data in this case (means if a device is not reported on mesh, it is ignored). This will bring additional information to the device tracker entities about their topology in your home network. But it might happen, that the Fritzbox does not provide possible existing devices in mesh topology data if they are connected via 3rd party devices like switches or other "non-avm-mesh" wifi repeaters. in this case you should try to enable the old discovery method, as mentioned in the docs

mib1185 commented 8 months ago

@evilmumi did the old discovery method worked for you?

evilmumi commented 8 months ago

Till now everything works fine

mib1185 commented 8 months ago

ok, than I'm going to close this issue