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.47k stars 30.69k forks source link

Fritzbox repeater 1200 discovered as new on every HA restart #107297

Closed mopahle closed 6 months ago

mopahle commented 10 months ago

The problem

Fritzbox repeater 1200 discovered as new on every HA restart

What version of Home Assistant Core has the issue?

2024.1.1

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

Link to integration documentation on our website

https://www.home-assistant.io/integrations/fritzbox

Diagnostics information

config_entry-fritzbox-06011d5c0b1675c754139846f1a6509d.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2024-01-05 21:15:18.308 INFO (SyncWorker_0) [fritzconnection] Unable to retrieve resource 'http://192.168.178.27:49000/igddesc.xml' from the device.
2024-01-05 21:15:18.327 INFO (SyncWorker_1) [fritzconnection] Unable to retrieve resource 'http://192.168.178.29:49000/igddesc.xml' from the device.

192.168.178.27 and 192.168.178.29 are the repeaters

Additional information

If I configure the repeater i see the following message: image After that the discovered repeater disappears until I restart HA

This seems to be related to https://github.com/home-assistant/core/issues/81741

home-assistant[bot] commented 10 months ago

Hey there @mib1185, @flabbamann, mind taking a look at this issue as it has been labeled with an integration (fritzbox) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `fritzbox` 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 fritzbox` 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)


fritzbox documentation fritzbox source (message by IssueLinks)

mib1185 commented 10 months ago

Hi @mopahle first the provided error log messages are related to the AVM FRITZ!Box Tools but not AVM FRITZ!SmartHome so we can ignore them in this case. When you say "discovered as new on every HA restart", i assume you already have tried to just ignore the discovered device?

mopahle commented 10 months ago

No, they only came up as new device if I configure them. If I ignore them they are kept as ignored devices.

mib1185 commented 10 months ago

ok, but than why not just ignore them, when they should not be configured even?

mopahle commented 10 months ago

Ignoring them looks like a workaround for me. My expectation is that either the devices should not come up if there is nothing to configure or they should not come up again after they were configured (even if they can not be used). Maybe a hint in the documentation will do it.

issue-triage-workflows[bot] commented 7 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.