search

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.94k stars 30.99k forks source link

Denon integration detects Home speaker but fails to add it #125048

Open sellison2 opened 2 months ago

sellison2 commented 2 months ago

The problem

I recently purchased a Denon Home 150 NV. Any time it connects to my network, HA finds it and offers to add it as a new device. When I click Confirm to add it, it immediately fails instead. I turned on debug logging one of the times I tried it, see attached. My Denon AVR works fine so the integration itself is otherwise working normally, and the Heos app finds and controls it just fine as well so it's not a networking issue or issue with the device. Behavior is the same on both wifi and ethernet.

The speaker isn't on the integration's list of compatible devices, so I'm not surprised it doesn't work. I'm not sure if the speaker uses a different API than the AVR, or if there's some other reason that makes it incompatible. If nothing else, HA should be smart enough to not offer to add the speaker until a better fix is implemented. Whenever I power on the speaker, HA asks me multiple times if I want to add it, so getting notified about a new device when it's un-addable is almost as annoying as not being able to add it in the first place.

What version of Home Assistant Core has the issue?

core-2024.8.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

Denon AVR Network Receivers

Link to integration documentation on our website

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

Diagnostics information

home-assistant_denonavr_2024-09-02T01-05-10.316Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 2 months ago

Hey there @ol-iver, @starkillerog, mind taking a look at this issue as it has been labeled with an integration (denonavr) you are listed as a code owner for? Thanks!

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

denonavr documentation denonavr source (message by IssueLinks)

Sausmaster commented 1 month ago

I am having exactly this issue. With some 6 speakers, this is quite annoying... HA keeps discovering them even though they have already been picked up by the DENON HEOS integration and cannot be actually added by this integration.

Thus, error messages keep flooding back every time. Would be great if @starkillerOG or someone could fix this...

marcoryba commented 1 month ago

Hi, yes, I also have this problem. I managed to manually add the Denon Home 150 NV to HA, just by adding a device, entering the speaker's IP, and everything went smoothly. The only issue is that the window for adding the device keeps popping up. Even after clicking "Ignore."