AVM FRITZ!Box Tools: Setup not successful; no devices found

[Rexaris]

The problem

After update of my homeassistant core installation on my Raspberry Pi, i noticed, that the device-tracker by the fritzbox integration does not work anymore. No devices were found.

In the Integration panel the following error is shown:

Translation: retry Setup; check the logs

I already reinstalled the integration. The login to the Fritzbox works, but the error remains.

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 Core

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?

In the logs i just found some warnings regarding my Caldav-Configuration and the following entries:
Detected integration that accessed discovery_info.__contains__('ssdp_location') instead of discovery_info.upnp.__contains__('ssdp_location') or discovery_info.ssdp_headers.__contains__('ssdp_location'); this will fail in version 2022.6. Please report issue for upnp using this method at homeassistant/components/upnp/device.py, line 78: if ssdp.ATTR_SSDP_LOCATION not in headers:

Detected integration that accessed discovery_info['ssdp_location'] instead of discovery_info.ssdp_location, discovery_info.upnp['ssdp_location'] or discovery_info.ssdp_headers['ssdp_location']; this will fail in version 2022.6. Please report issue for upnp using this method at homeassistant/components/upnp/device.py, line 81: location = headers[ssdp.ATTR_SSDP_LOCATION]

I tired to dig a bit deeper and activated the debug logs for fritzconnection:
After a wall of Text it ends with a "response status: 500"

2022-02-03 07:34:44 DEBUG (SyncWorker_4)
http://192.168.179.1:49000/upnp/control/hosts
2022-02-03 07:34:44 DEBUG (SyncWorker_4) [fritzconnection] b'<s:Envelope s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><u:GetGenericHostEntry xmlns:u="urn:dslforum-org:service:Hosts:1">20</u:GetGenericHostEntry></s:Body></s:Envelope>'
2022-02-03 07:34:44 DEBUG (SyncWorker_4) [fritzconnection] response status: 500
2022-02-03 07:34:44 DEBUG (SyncWorker_4) [fritzconnection]
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<s:Body>
<s:Fault>
s:Client
UPnPError


713
SpecifiedArrayIndexInvalid


</s:Fault>
</s:Body>
</s:Envelope>
2022-02-03 07:34:44 DEBUG (MainThread) [homeassistant.components.fritz.common] Finished fetching fritz-192.168.179.1-coordinator data in 3.411 seconds (success: False)

Additional information

FRITZ!OS: 07.13

[probot-home-assistant]

fritz documentation
fritz source
_{^{(message by IssueLinks)}}

[probot-home-assistant]

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!
_{^{(message by CodeOwnersMention)}}

[gzxto1]

Looks I have the same Issue with Fritzbox 7582 OS 7.16 not working since 2022.2.0. Deleted the integration, after reboot the inegration was found but setup failed.

[chemelli74]

@Rexaris, @gzxto1 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.

EDIT: Please also add diagnostics (menu configuration -> integration -> fritz tools -> download diagnostics )

[Rexaris]

now i created a logfile with fritzconnection: info, which is much more readable:
logfile.txt

Regarding the diagnostics:
For the Fritzbox Tools integration there is no download diagnostics button. But it is available for Fritzbox SmartHome integration.

[gzxto1]

HA_Fritz_Tools_setup_failure.log
Here the Log, as mentioned there is no Diag for this integration

[chemelli74]

Regarding the diagnostics: For the Fritzbox Tools integration there is no download diagnostics button. But it is available for Fritzbox SmartHome integration.

Are you sure you are running 2022.02.0 ?

Simone

[Rexaris]

I copied the System Health from the Info site, which states it is 2022.2.0, maybe there was an error during update process?:

System Health

version	core-2022.2.0
installation_type	Home Assistant Core
dev	false
hassio	false
docker	false
user	homeassistant
virtualenv	true
python_version	3.9.2
os_name	Linux
os_version	5.10.92-v8+
arch	aarch64
timezone	Europe/Berlin

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Lovelace

dashboards	1
resources	0
views	5
mode	storage

Spotify

api_endpoint_reachable	ok

[gzxto1]

I'm also defenitely running 2022.02.0 and there are no diags for the Call Monitor + Tools integrations. I don't use the Smarthome integration. I see diags it for some other integrations but not all. Using HA OS on Raspi 4

[chemelli74]

Please try hard deleting the browser cache, it's definitively there.

Simone

[gzxto1]

I've logged in via Chrome Ikonito, so they also should no interference with any extension... no success

[Rexaris]

I deleted all cache data from google chrome and installed a clean firefox.
Same result as before for both browsers: no diagnostics.
Same in the mobile app.

[ludeeus]

If you do not have default_config: in your configuration, you need to add diagnostics: to it manually for diagnostics to work.

[gzxto1]

I have default_config: on top of configuration.yaml. Also I have other integration offering "Download Diagnostics" in the menu, but not both of my Fritzbox Integrations..

[Rexaris]

although I had the default_config: in my config. i added the diagnostics: with no changes regarding the diagnostics for the fritz-integration.

default_config:

diagnostics:

[ludeeus]

Yeah, did not look at the image properly, until the integration is set up there is not diagnostic.

[gzxto1]

Yeah, did not look at the image properly, until the integration is set up there is not diagnostic.

AVM FRITZ!Box Call Monitor is properly setup but has no diags, even Google Cast properly working
has no Diag, while e.g. HACS, Shelley, OpenUV have Diags.....

[ludeeus]

So far only about 60 integrations have diagnostics added so that is expected.

[gzxto1]

Frenck stated in the release party "over 60 ingrations support Diags" means obviously not all.....

[BebeMischa]

I suffer exactly the same issue on Fritz!Box 7581.

After the upgrade of core HA all entities of the box were dead.
Deleted the integration, restarted the HA server (yes, a cold restart) and after that tried to fresh install the integration of Fritz.
It has been auto-discovered, but integration fails to setup with this as result:

in the logs:

Logger: homeassistant.helpers.frame
Source: helpers/frame.py:103
First occurred: 17:25:08 (2 occurrences)
Last logged: 17:25:08

Detected integration that accessed discovery_info.__contains__('ssdp_location') instead of discovery_info.upnp.__contains__('ssdp_location') or discovery_info.ssdp_headers.__contains__('ssdp_location'); this will fail in version 2022.6. Please report issue for upnp using this method at homeassistant/components/upnp/device.py, line 78: if ssdp.ATTR_SSDP_LOCATION not in headers:
Detected integration that accessed discovery_info['ssdp_location'] instead of discovery_info.ssdp_location, discovery_info.upnp['ssdp_location'] or discovery_info.ssdp_headers['ssdp_location']; this will fail in version 2022.6. Please report issue for upnp using this method at homeassistant/components/upnp/device.py, line 81: location = headers[ssdp.ATTR_SSDP_LOCATION]

Running HA supervised on dedicated intel based PC. No other issues after the upgrade, this is the only one.
No other software on that machine.

[mib1185]

@Rexaris @BebeMischa @gzxto1
may I ask you to test the linked PR if this solves the issue for you?

[chemelli74]

Detected integration that accessed discovery_info.contains('ssdp_location') instead of discovery_info.upnp.contains('ssdp_location') or discovery_info.ssdp_headers.contains('ssdp_location'); this will fail in version 2022.6. Please report issue for upnp using this method at homeassistant/components/upnp/device.py, line 78: if ssdp.ATTR_SSDP_LOCATION not in headers:
Detected integration that accessed discovery_info['ssdp_location'] instead of discovery_info.ssdp_location, discovery_info.upnp['ssdp_location'] or discovery_info.ssdp_headers['ssdp_location']; this will fail in version 2022.6. Please report issue for upnp using this method at homeassistant/components/upnp/device.py, line 81: location = headers[ssdp.ATTR_SSDP_LOCATION]

Please open a issue for upnp integration.
Thx,

Simone

[BebeMischa]

@Rexaris @BebeMischa @gzxto1 may I ask you to test the linked PR if this solves the issue for you?

I would directly do that, if I had any clue, how to ;-)

[OldShaterhan]

Detected integration that accessed discovery_info.contains('ssdp_location') instead of discovery_info.upnp.contains('ssdp_location') or discovery_info.ssdp_headers.contains('ssdp_location'); this will fail in version 2022.6. Please report issue for upnp using this method at homeassistant/components/upnp/device.py, line 78: if ssdp.ATTR_SSDP_LOCATION not in headers:
Detected integration that accessed discovery_info['ssdp_location'] instead of discovery_info.ssdp_location, discovery_info.upnp['ssdp_location'] or discovery_info.ssdp_headers['ssdp_location']; this will fail in version 2022.6. Please report issue for upnp using this method at homeassistant/components/upnp/device.py, line 81: location = headers[ssdp.ATTR_SSDP_LOCATION]

Please open a issue for upnp integration. Thx,

Simone

#65540 already one exists.

[Rexaris]

I would directly do that, if I had any clue, how to ;-)

I think there is a more elegant way, but i just copied the file with the changes to my installation.

Looks like the integration works again for me. Good Job!
Diagnostics are now available too.

[gzxto1]

Installed 2022.2.1. I'ts working now again:-) I see the diag menu too
Great Job thank for all your efford to fix it.

[BebeMischa]

confirm. 2022.2.1 solved the issue. ;-) Thanks very much.