Closed SodaWithoutSparkles closed 10 hours 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!
(message by CodeOwnersMention)
denonavr documentation denonavr source (message by IssueLinks)
From my limited tests, I think the issue is incorrect mapping of NEURAL:X
to DOLBY DIGITAL
.
I will look through the code and see if I find anything
It seems that it was incorrectly mapped here. I can't find Dolby Neural:X on my unit, perhaps it would be unit-dependent?
Maybe it would be more approiate to check for NEURAL:X
instead of DTS NEURAL:X
?
Edit: sorry cant get the embedded code snippets to work
Further testing will be needed to see if this have been solved by #126703
We made the wrong assumption where NEURAL:X
belongs to 🙂
I fixed this with https://github.com/ol-iver/denonavr/pull/317.
The problem
When using the "Denon AVR network recievers" integration with my AVR_X1600H, I discovered the following issue:
Method to reproduce:
media_player.select_sound_mode
on the unit with "DOLBY DIGITAL" as sound mode, observe that the unit actually changed to DSUR modeWhat version of Home Assistant Core has the issue?
core-2024.7.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Denon AVR network recievers
Link to integration documentation on our website
https://www.home-assistant.io/integrations/denonavr/
Diagnostics information
It does not provide diagnostic
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
A reload does not fix the issue, so the 403 is likely not an issue.
Possibily related to #117255 , but I cannot find the relevant logs.
It is possible to transition from DTS-STEREO-DOLBY, but the sound mode is still wrong.
It is not possible to transition from DTS-DOLBY directly as it thinks it was in DOLBY already.