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
72.76k stars 30.47k forks source link

Denon AVR integration appears to cause AVR to power on with no audio #94837

Closed jjross closed 9 months ago

jjross commented 1 year ago

The problem

I am using an AVR-X1700H which I have owned since March with the Home Assistant integration connected to the AVR for as long as I have owned it.

Over the past few days / weeks I've noticed that the AVR will power on and will not have any audio. If I power off the AVR and then back on again the audio will work as normal but if I power it off a 3rd time the audio will go back to being broken.

After messing around for a long time I believe I have narrowed this down to the Home Assistant Denon integration running in Telnet mode as everything behaves as expected when I turn off telnet mode.

Not sure what about Telnet mode would cause the AVR to start with no audio on first boot but wanted to make the team aware and provide anything I can to help narrow the issue down. Also, I'm wondering if something changed in the integration or the Denon firmware because I'm sure this was all working normally until recently.

What version of Home Assistant Core has the issue?

core-2023.6.2

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

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Not that I noticed

Additional information

No response

home-assistant[bot] commented 1 year 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.

(message by CodeOwnersMention)

denonavr documentation denonavr source (message by IssueLinks)

parabiosis commented 1 year ago

I have the same issue on 2023.6.2 with my Marantz Cinema 50. I recently upgraded from a Denon AVR-X1500H which was working fine on 2023.6 as was the Marantz until updating to 2023.6.2. My experience is essentially identical and everything works fine without the Telnet connection being used but when I turn it on again I get the volume set to 0 issue.

I also have issues on 2023.6.2 with media_player.set_volume not working in my automations. I can call the service outside of automations just fine but they just aren't working within. When the Telnet connection is off this works fine again leading me to believe there is more to this Telnet issue than just the volume getting set to 0.

@jjross are you able to test to see if that is also an issue on your end?

ol-iver commented 1 year ago

Both volume issues are weird.

I never experienced the issue that the receiver start without volume. I'm even not entirely sure what this means. Is the volume set to 0 and you can simply increase it again or is it entirely broken and there is no sound until you power off and on again?

For changing any value the integration is sending HTTP requests no matter if telnet is activated or not. I don't know why media_player.set_volume is working without telnet only.

delibird commented 1 year ago

For me, the receiver will turn on and set to 0.0 volume but I can adjust it both on the receiver and through HA and it will be fine once adjusted to an appropriate level. For reference, I have my receiver set to use the last volume level on power on and then an automation in HA to set the volume level depending on the source when either the source changes or the state of the entity changes to 'on'.

I left the Telnet connection unchecked and updated to 2023.7.0 . After the update I was having the issue again and had to check the Telnet option, and then uncheck it again for things to go back to normal behavior. I tested a bit today on 2023.7.1 (same issue present) and found that if I disabled any automation that calls media_player.volume_set I get the expected behavior and the receiver turns on with the last volume level it had when it was powered off. But when I turn the Telnet connection back on, the receiver will turn on with volume level 0.0. I tried to recreate my automation from scratch and the behavior remains the same. The automation I created is very simple and I don't believe is the cause but here is an excerpt of the code (I only removed a few options that are identical except the source in the condition):

alias: "AVR: Set Volume Based on Source"
description: ""
trigger:
  - platform: state
    entity_id:
      - media_player.home_theater
    attribute: source
  - platform: state
    entity_id:
      - media_player.home_theater
    to: "on"
condition: []
action:
  - choose:
      - conditions:
          - condition: state
            entity_id: media_player.home_theater
            attribute: source
            state: Shield
        sequence:
          - service: media_player.volume_set
            data:
              volume_level: 0.52
            target:
              entity_id: media_player.home_theater
      - conditions:
          - condition: state
            entity_id: media_player.home_theater
            attribute: source
            state: Switch
        sequence:
          - service: media_player.volume_set
            data:
              volume_level: 0.58
            target:
              entity_id: media_player.home_theater
mode: restart

Anyway, in my case it seems like setting the volume in an automation whilst using the Telnet connection is an issue. I tried to disable just the receiver state is on trigger and it still happens. I took a look at the code and I have no clue what could be causing that but nothing on my end has changed in terms of HA besides the updates.

jjross commented 1 year ago

The volume doesn’t work at all and it looks like the receiver doesn’t “initialize” as the indicators for the sound format never show up. It’s as though the receiver fails to fully boot. It’s just such a strange issue. If I power off the receiver and turn it back on then things initialize and it works perfectly. On Jul 8, 2023, at 11:02 AM, Oliver @.***> wrote: Both volume issues are weird. I never experienced the issue that the receiver start without volume. I'm even not entirely sure what this means. Is the volume set to 0 and you can simply increase it again or is it entirely broken and there is no sound until you power off and on again? For changing any value the integration is sending HTTP requests no matter if telnet is activated or not. I don't know why media_player.set_volume is working without telnet only.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

jjross commented 1 year ago

I never use HA to set the volume so that doesn’t have an impact on my situation. Like I mentioned, it really seems to me like the receiver doesn’t full POST. I can’t change inputs and everything and there’s no audio. It doesn’t make sense. On Jul 8, 2023, at 10:41 PM, Gary @.***> wrote: For me, the receiver will turn on and set to 0.0 volume but I can adjust it both on the receiver and through HA and it will be fine once adjusted to an appropriate level. For reference, I have my receiver set to use the last volume level on power on and then an automation in HA to set the volume level depending on the source when either the source changes or the state of the entity changes to 'on'. I left the Telnet connection unchecked and updated to 2023.7.0 . After the update I was having the issue again and had to check the Telnet option, and then uncheck it again for things to go back to normal behavior. I tested a bit today on 2023.7.1 (same issue present) and found that if I disabled any automation that calls media_player.volume_set I get the expected behavior and the receiver turns on with the last volume level it had when it was powered off. But when I turn the Telnet connection back on, the receiver will turn on with volume level 0.0. I tried to recreate my automation from scratch and the behavior remains the same. The automation I created is very simple and I don't believe is the cause but here is an excerpt of the code (I only removed a few options that are identical except the source in the condition): alias: "AVR: Set Volume Based on Source" description: "" trigger:

Anyway, in my case it seems like setting the volume in an automation whilst using the Telnet connection is an issue. I tried to disable just the receiver state is on trigger and it still happens. I took a look at the code and I have no clue what could be causing that but nothing on my end has changed in terms of HA besides the updates.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

ol-iver commented 1 year ago

A couple of weeks ago, I had the volume issue on my receiver too. It happened several time in a row until I unplugged and plugged the receiver. Since then the issue never appeared again. Thus, it might be a firmware bug.

Did you try to unplug your receiver? Just switching it off is not enough to reboot it.

jjross commented 1 year ago

I did. In the end turning off the telnet option appeared to fix the issues. On Sep 30, 2023, at 5:24 AM, Oliver @.***> wrote: A couple of weeks ago, I had the volume issue on my receiver too. It happened several time in a row until I unplugged and plugged the receiver. Since then the issue never appeared again. Thus, it might be a firmware bug. Did you try to unplug your receiver? Just switching it off is not enough to reboot it.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

issue-triage-workflows[bot] commented 10 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.