Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detected that integration 'fritz' calls device_registry.async_get_or_create referencing a non existing via_device #134269

Open
NorbertHD opened this issue Dec 30, 2024 · 3 comments

Comments

@NorbertHD
Copy link

The problem

Detected that integration 'fritz' calls device_registry.async_get_or_create referencing a non existing via_device is shown in logs on startup.

What version of Home Assistant Core has the issue?

core-2025.1.0b3

What was the last working version of Home Assistant Core?

core-2024.12.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Fritz

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?

2024-12-30 09:14:13.039 WARNING (MainThread) [homeassistant.helpers.frame] Detected that integration 'fritz' calls `device_registry.async_get_or_create` referencing a non existing `via_device` ('fritz', '60B58D0B980F'), with device info: {'connections': {('mac', '02:18:5D:xx:xx:xx')}, 'default_manufacturer': 'AVM', 'default_model': 'FRITZ!Box Tracked device', 'default_name': 'homeassistant', 'via_device': ('fritz', '60B58D0B980F')} at homeassistant/components/fritz/button.py, line 86: async_add_entities(entities_list). This will stop working in Home Assistant 2025.12.0, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+fritz%22

Additional information

No response

@home-assistant
Copy link

Hey there @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 mib1185 added this to the 2025.1.0 milestone Jan 1, 2025
@mib1185
Copy link
Contributor

mib1185 commented Jan 1, 2025

Hi @

please enable debug logging, restart the integration and download and provide the log file after the issue occur again.

Further please download and provide the diagnostics data for this integration.

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.

thx 👍

@mib1185
Copy link
Contributor

mib1185 commented Jan 1, 2025

Further question - is this the only occurrence of a "referencing a non existing via_device" message for the fritz integration, or are there more?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants