You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there @chishm, mind taking a look at this issue as it has been labeled with an integration (dlna_dmr) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of dlna_dmr 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 dlna_dmr 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.
This is an interesting bug. All entries for the dlna_dmr component should have a CONF_URL set, so my best guess is that non-dlna_dmr entries are getting checked. I'll put in a quick check to skip such entries.
The problem
After upgrade from 2024.5.3 to 2024.5.4
What version of Home Assistant Core has the issue?
core-2024.5.4
What was the last working version of Home Assistant Core?
core-2024.5.3
What type of installation are you running?
Home Assistant Container
Integration causing the issue
dlna_dmr
Link to integration documentation on our website
https://www.home-assistant.io/integrations/dlna_dmr/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
The text was updated successfully, but these errors were encountered: