AVM FRITZ!Box Tools - device tracker entities for the Fritz Box and all repeaters are not defined/created since 2022.2.0 #65541
Comments
|
fritz documentation |
|
Hey there @mammuth, @AaronDavidSchneider, @chemelli74, @mib1185, mind taking a look at this issue as it has been labeled with an integration ( |
|
Hi @browetd logger:
default: info
logs:
homeassistant.components.fritz: debug
fritzconnection: debugFurther please download and provide the diagnostics data for this integration if possible. 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. |
|
I'm digging into the same issue; so far I discovered that:
Simone |
|
I have the same Issuse. logfile |
|
@mib1185 Here is the logfile. My network: logfile |
|
I am very sorry but I have no Idea how to test the link, I am kinda lost |
|
I'm totaly new to this integration and I'm pretty sure I'm getting it wrong... Maybe you have to check this part now? " device tracker entities that match up with an existing - known by Home Assistant - device" Hope this helps... Please ignore if not ;-) |
|
I have the same problem. A lot of devices are detected correctly. But some are not. It feels like there is a system in int:
but on the other hand
It feels weird that it is consistent groups being present or not. There are no error logs at all. I've completely removed the integration and started from scratch - same result. |
That feels like something different. And something also broken. In my case, two raspis are detected. They were not previously knwon to HA. But the mobile devices are not detected, while they are all known through the companion app. |
|
I have the same issue lost all my device trackers from the fritzbox integration. |
|
Same on my system |
|
2022.2.1 does not seem to solve this |
This sounds to be related to the new device tracker handling 🤔 |
|
Totally broken. Again. Every release has a problem or has a braking change and we have to adjust things again and again and again. I really miss the old integration. It was rock solid, never never never had a problem nor a glitch. It simply worked as expected. Now I am not sure I had at least a couple of months troubles free. I lost all my mesh routers and repeaters, they are not created. Remove, reboot, add again from scratch the integration do not solve the problem. Fritz 7490. |
|
Problem still exist in 2022.2.2 |
|
I updated this morning and have the same or similar issue. All the device tracker entities I had are now unavailable. Tried reboots or HA and router and hasn’t helped. |
|
In my case, I have all the device trackers correctly created except the Fritz boxes and Fritz repeaters, |
|
@Smandurlo and all the others, we are working hard to achive 2 goals:
I think that we are now very close: firmware update, mesh management, details of each device tracker, set guest password, are all implemented. We just wait for QR code for Guest WIFI . About the second, unfortunately some API from AVM are broken on some devices, and we need to find different ways to achive the same result. We are also looking for an updated fritzconnection to get the last requested performance improvement; with that we will do 1 single call for all devices instead of 1 for each device! Please share an updated log and diagnostics from 2022.02.2 or later to help this process. Simone |
|
{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2022.2.2",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.9.7",
"docker": true,
"arch": "aarch64",
"timezone": "Europe/Berlin",
"os_name": "Linux",
"os_version": "5.10.63-v8",
"supervisor": "2022.01.1",
"host_os": "Home Assistant OS 7.2",
"docker_version": "20.10.9",
"chassis": "embedded",
"run_as_root": true
},
"custom_components": {
"hacs": {
"version": "1.21.0",
"requirements": [
"aiogithubapi>=21.11.0"
]
},
"rpi_gpio": {
"version": "2022.2.2",
"requirements": [
"RPi.GPIO==0.7.1a4"
]
},
"iq_notify": {
"version": "1.0.0",
"requirements": []
},
"dwd_weather": {
"version": "1.2.17",
"requirements": [
"simple_dwd_weatherforecast==1.1.1",
"markdownify==0.6.5"
]
},
"linkplay": {
"version": "2.0.43",
"requirements": [
"uPnPClient~=0.0",
"validators~=0.12",
"chardet>=4.0.0"
]
}
},
"integration_manifest": {
"domain": "fritz",
"name": "AVM FRITZ!Box Tools",
"documentation": "https://www.home-assistant.io/integrations/fritz",
"requirements": [
"fritzconnection==1.8.0",
"xmltodict==0.12.0"
],
"dependencies": [
"network"
],
"codeowners": [
***@***.***",
***@***.***",
***@***.***",
***@***.***"
],
"config_flow": true,
"ssdp": [
{
"st": "urn:schemas-upnp-org:device:fritzbox:1"
}
],
"iot_class": "local_polling",
"is_built_in": true
},
"data": {
"entry": {
"entry_id": "8168d17f0eddc8127e77662d1bac635c",
"version": 1,
"domain": "fritz",
"title": "FritzBox-UG",
"data": {
"host": "192.168.178.1",
"password": "**REDACTED**",
"port": 49000,
"username": "**REDACTED**"
},
"options": {
"consider_home": 180.0
},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "ssdp",
"unique_id": "123402409-bccb-40e7-8e6c-DC396F19A643",
"disabled_by": null
},
"device_info": {
"model": "FRITZ!Box 7590 (UI)",
"current_firmware": "154.07.29",
"latest_firmware": "",
"update_available": false,
"is_router": true,
"mesh_role": "master",
"last_update success": true,
"last_exception": null,
"discovered_services": [
"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",
"WLANConfiguration1",
"WLANConfiguration2",
"WLANConfiguration3",
"Hosts1",
"LANEthernetInterfaceConfig1",
"LANHostConfigManagement1",
"WANCommonInterfaceConfig1",
"WANDSLInterfaceConfig1",
"WANDSLLinkConfig1",
"WANEthernetLinkConfig1",
"WANPPPConnection1",
"WANIPConnection1"
],
"client_devices": [ **removed ** ],
"wan_link_properties": {
"NewWANAccessType": "DSL",
"NewLayer1UpstreamMaxBitRate": 38517000,
"NewLayer1DownstreamMaxBitRate": 128876000,
"NewPhysicalLinkStatus": "Up"
}
}
}
}
Am Sa., 5. Feb. 2022 um 11:22 Uhr schrieb Simone Chemelli <
***@***.***>:
… @Smandurlo <https://github.com/Smandurlo> and all the others, we are
working hard to achive 2 goals:
- all the requested features, scenarios covered
- improve performances, means less API call to the Fritz
I think that we are now very close: firmware update, mesh management,
details of each device tracker, set guest password, are all implemented. We
just wait for QR code for Guest WIFI
<#64176>.
The Team doesn't have anything left on the todo after that.
About the second, unfortunately some API from AVM are broken on some
devices, and we need to find different ways to achive the same result.
Luckily often there is more than 1 way to do it, so we are actively
looking into all issues to find a stable solution for you all.
We are also looking for an updated fritzconnection
<kbr/fritzconnection#134> to get the last
requested performance improvement; with that we will do 1 single call for
all devices instead of 1 for each device!
Please share an updated log and diagnostics from 2022.02.2 or later to
help this process.
Simone
—
Reply to this email directly, view it on GitHub
<#65541 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFIMPZ2SW7XCGZSSFEW6ZULUZT27DANCNFSM5NPCY7HQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
@Oxaluz, I miss the log ;-) Please don't send it via email, but drag and drop in a reply via web. Simone |
|
@chemelli74 Here is my last log... HA 2022.2.2... |
Your device says that WANCommonInterfaceConfig exist as a service, but once invoked it throws an error: Is your router coming from a ISP ? Simone |
chemelli74
changed the title
|
Just to add to the discussion that the integration (AVM Fritz!Box Tools) discovered my 4 repeaters... For each repeater, I have 4 button entities (cleanup, firmware update, reboot, reconnect), one sensor (device_uptime) and one binary_sensor(firmware update) but no device_tracker neither... Each repeater has an IP address... |
|
Into my integration, there is nothing related to the routers (connected
with ethernet) nor repeaters (wifi link).
Into another HA, I use a fritzbox 4040 (no mesh) and mobile phones and a
google assistant mini disappeared.
So, I don't think it is only related to the mesh network, but it is related
with 2022.2 upgrade. Everything works perfectly when downgrading to
2021.12. New way to discover devices is broken.
Il mer 9 feb 2022, 17:04 browetd ***@***.***> ha scritto:
… Just to add to the discussion that the integration (AVM Fritz!Box Tools)
discovered my 4 repeaters... For each repeater, I have 4 button entities
(cleanup, firmware update, reboot, reconnect), one sensor (device_uptime)
and one binary_sensor(firmware update) but no device_tracker neither...
Each repeater has an IP address...
—
Reply to this email directly, view it on GitHub
<#65541 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIXTCZLLU4G26MHIJWABKXDU2KGBRANCNFSM5NPCY7HQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
IF the repeater is part of a mesh network, then we add teh device trackers only to the master. Simone |
|
@chemelli74 My repeaters are part of a mesh... so as you mentionned, the trackers should then be created by the master... |
|
I am not sure I understood correctly, you mean that there will be no device
tracker for mesh slave?
Il gio 10 feb 2022, 08:35 browetd ***@***.***> ha scritto:
… @chemelli74 <https://github.com/chemelli74> My repeaters are part of a
mesh... so as you mentionned, the trackers should then be created by the
master...
—
Reply to this email directly, view it on GitHub
<#65541 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIXTCZIFTHQBERM2BALEFLLU2NTDDANCNFSM5NPCY7HQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@Smandurlo I understood that the trackers for mesh repeaters will be created at the master level so in my case at the level of my FritzBox 7590... not at the level of each repeater integration... |
|
Update: I had to switch off the electricity on a section of my house where there is a mesh repeater connected with ethernet. After some minutes, I got the notification of my offline devices as expected, PLUS my fritz mesh repeater that was not discovered anymore. Funny thing is, it works in reverse mode! HA lists it as home. When I switched back on the eletricity, the mesh repeater went not_home. Out of curiosity, I switched off again, and it went "home". Switched on electricity and "not_home". The other device trackers work as supposed to be. |
|
My two cents: I only have a FritzBox 5490 as a router, no mesh setup. |
They do it as far as I know. At least, it was this way. Now I see they are not created at all even if the Fritz has the ip reserved (second problem) and new devices create a device_tracker that is active despite the option not to track new device discovered (third problem). Are you sure they are unavailable? Because it will be another problem and in my opinion now there are too much problems to fix and it is better to revert back. |
Please don't mix up issues. You are reporting something different than the topic. Simone |
I checked against the todays release 2022.2.6 and the problem still persists. |
|
Still tracker entities for Fritz!Box, Fritz!Repeaters and devices not being connected recently are shown with entity state
|
|
The beta of 2022.3.0 (currently 2022.3.0b2) has a new integration system option:
Please enable it and report back if issue is fixed. Simone |
|
Thank you. Does "old integration option" mean |
@chemelli74 I can confirm that all of my devices showed up after using "Enable old discovery method" 🎉 Thanks for your work, Simone! |
Option A, back to the same code used for 2021.12.x Simone |
|
@browetd, can you please test latest release 2022.3.0 ? Simone |
|
my (last) test: #67543 |
|
I just tried it. Obviously, I deleted the "test" code from
The good news is: all entities come back once the switch for the old discovery option is enabled. The bad news is: the devices still have cumbersome names with the term |
|
I tried to test the new version as well. I removed the files inside the custom_component dir, removed the yaml code and restarted HA before configuring the gui integration. It didn't complain of custom_component, but it is still plenty of bugs: #67543 (but @chemelli74 closed it without a solution). Unfortunately I cannot continue to test the integration in a production environment. |
This might actually be related to something else on my setup. I'll take a deeper look into this and will report back here. Might actually not be a |
|
Ok, now the integration loads properly. Using the "old" discovery option, everything is detected. The cumbersome naming is gone as well. thanks! |
|
do you have working switches and binary_sensors as well? |
I've now spent quite a bit of time with the integration. Yes, the binary sensors and the switches seem to work as expected. All is well. Actually, @chemelli74 was very helpful with some debugging so we worked together on this via Discord. I first thought the integration was still bugged, but it turns out that I misconfigured something else (my shellies) which had the side effect of HA not starting properly, which again didn't load the new fritz integration properly. From my perspective, this can be closed now. Thanks to all those who worked on this integration! |
|
I am closing this issue ... If you have still specific problems please open a new issue... |
The problem
I am tracking the availability of all my network devices using device_tracker entities. Since I upgraded to version 2022.2.0 all the device trackers for the fritz box and all fritz repeaters are "unavailable" while other entities (button, switch, binary_sensors) for those equipments exist. All other devices I am tracking have been correctly created... No error message seems to be existent for that integration but I have the following error at startup (but this one was already there in 2021.12.x without creating any issues):
I have also the following error (a couple times at startup) but not sure if this is linked with Fritz Box integration:
What version of Home Assistant Core has the issue?
core-2022.2.0
What was the last working version of Home Assistant Core?
core-2021.12.x
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/
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: