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.48k stars 30.7k forks source link

Denon AVR Network integration network error after reboot #88149

Closed dabbler68 closed 6 months ago

dabbler68 commented 1 year ago

The problem

If I turn off (Standby) or power off the AVR, home assistant has no problem. But if I reboot HA while the AVR is not actually ON, the Denon integration card is outlined in red with the message: Retrying setup: NetworkError: All connection attempts failed

It cycles from Initializing to displaying the red outline and error message on about a 1 minute cycle.

Once I switch the AVR on, the device is automatically detected and the error message stops. It stays off until the next HA reboot. My Denon AVR-X3400H is in the list of supported devices. It is connected via Wifi.

What version of Home Assistant Core has the issue?

2023.2.4

What was the last working version of Home Assistant Core?

This same issue was in previous HA versions although I did not try the integration before December.

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Denon AVR Network Receiver

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?

At boot, there is a single line recorded in the logfile: Config entry 'Denon AVR-X3400H' for denonavr integration not ready yet: TimeoutException: ; Retrying in background,

Then a few minutes later: Config entry 'Denon AVR-X3400H' for denonavr integration not ready yet: NetworkError: All connection attempts failed; Retrying in background

Additional information

I wanted to see if it behaved the same way with the IP address allocated in the router. So after doing so I deleted the integration and set it up again, but this time it did not ask for the IP address. I could not see how to get that field back. A separate issue no doubt.

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` Change the title of 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)

dabbler68 commented 1 year ago

Update: I am thinking this may be an issue with the core as the Tapo and Wiz integrations act similarly .... not identically. The common behaviour is the display on the integration card. Identical for all three.

Reboot HA when devices are offline. All show "retrying", Take devices offline after reboot, none show anything wrong on the integration card.

For the logfile they act differently with Denon and Wiz generating 1 or 2 messages. Tapo reports about every minute, but only if disconnected when HA rebooted.

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

dabbler68 commented 1 year ago

The issue is still there with current versions but there has been a change in logfile reporting.

Just updated to: HAOS generic on Intel. Version 10.1. Core to 2023.5.3.

The Denon integration card shows the error as before. Turn off the AVR and no error is reported. The integration card shows it normally. But reboot HA when the AVR is off, the card then gets outlined in red with message "Retrying setup: NetworkError: All connection attempts failed". Every minute it displays "Initializing" for a few seconds before reverting to the error message.

The difference from when I raised this in February is that no entries are made to the logfile.

ol-iver commented 1 year ago

You could enable the networking of your receiver while it is on standby in its settings to avoid this error.

dabbler68 commented 1 year ago

Yes, when I first reported this I did not have networking activated, which I do now. So the problem is partly solved. If the AVR is on standby HA is happy and finds the AVR again on reboot.

But I still want to turn the AVR fully off when not using it. My Denon and connected devices (TV, antenna amp, 3 media players and BluRay) all run off the same powerboard which is connected to a smart switch. An automation detects the reduced watts when on standby and automatically turns everything off..

All those devices on standby comsume about 30 watts. Not a whole lot, but with say 150 hours a week of being on standby that would add up to around $100 per year wasted. And when storms are about I want it and the others off anyway,

As I said before, if HA is rebooted while the AVR is on (or now in standby), all is OK. The integration works fine. But reboot while the AVR is off and HA keeps trying to connect at least every minute with message "Failed setup". It should just show "Unavailable" as it does when the AVR is switched off but no HA reboot.

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

dabbler68 commented 1 year ago

The problem is still evident with current versions (OS 11.0 and Core 2023.10.5).

Cut the power to AVR without rebooting HA there is no problem. HA and integration deals with it as expected. I have it off (not standby) 95% of the time.

But if the Denon AVR is already powered off when HA is rebooted, the integration shows "Failed setup" and tries constantly to establish connection. When AVR has power again HA reconnects fine.

So the problem occurs on HA reboot.

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

dabbler68 commented 9 months ago

The problem is still evident with current versions (Intel Generic OS 11.4 and Core 2024.1.5).

Cut the power to AVR without rebooting HA there is no problem. HA and integration deals with it as expected. I have it off (not standby) 95% of the time.

But if the Denon AVR is already powered off when HA is rebooted, the integration shows "Failed setup" and tries constantly to establish connection. When AVR has power again HA reconnects fine.

So the problem occurs on HA reboot. Constantly failing and retrying is a waste of resources and does not meet integration guidelines. There are no messages in the Logfile.

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