Two or more "Fritzbox" Devices are created by Fritzbox Tools.

[christschnman]

The problem

The integration creates 2 or more devices with the same name for the Fritzbox itself. Immediately after resetting the integration, two “Fritz!box 7530” devices are available, with different entities being displayed in both devices. Initially only the "connected devices" are displayed in one device, with all the controls for e.g. wifi, restart, etc. in the second device. Later, all entities appear to appear in one of the two devices. I have already tried to deactivate the device, which then remains without entities, but it has also happened that the entities then "jump" into this device and are therefore also deactivated. I currently have 3 devices again, one with no entities, one with the device tracker (of itself?) and the "configuration" controls (cleanup, restart, etc.) and one device with all other information (download speed, etc.)

What version of Home Assistant Core has the issue?

2024.4.0

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]

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

[mib1185]

Hi @christschnman

please

1. remove the integration at all
2. enable debug logging by adding the following to your configuration.yaml (needs a restart of HA)

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

3. re-add the integration and wait 5 minutes
4. download and provide the diagnostics data
5. finally provide the full home-assistant.log

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.

[christschnman]

I'm driving crazy, the problem seems to have just solved itself, even though I've probably re-set up the integration 5 times. Maybe a caching problem.
Another reason could be that I installed the "nmap tracker" integration and it originally found the fritzbox under its IP itself and, interestingly, also a fritzbox device with the IP of Wireguard access. Maybe the devices got mixed up here, even though the Fritz-related entities were split between two devices.

If it happens again in the next few days, I'll let you know