Denonavr intégration log issue every 20sec with powered-off ACRs

[amg0]

The problem

My logs are filled in with error like this. When the AVR is powered on, it worked, but when I switch it off completely ( really completely so with a zwave power plug ), then my logs gets filled every 20 sec with these =>

2024-02-15 19:33:05.686 ERROR (MainThread) [homeassistant.components.denonavr.media_player] Error Power attribute of zone Main not found on update occurred in method async_update for Denon AVR receiver
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/denonavr/media_player.py", line 181, in wrapper
    return await func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/denonavr/media_player.py", line 323, in async_update
    await receiver.async_update()
  File "/usr/local/lib/python3.12/site-packages/denonavr/denonavr.py", line 180, in async_update
    await self._device.async_update(global_update=True, cache_id=cache_id)
  File "/usr/local/lib/python3.12/site-packages/denonavr/foundation.py", line 178, in async_update
    await self.async_update_power(global_update=global_update, cache_id=cache_id)
  File "/usr/local/lib/python3.12/site-packages/denonavr/foundation.py", line 431, in async_update_power
    await self.async_update_power_status_xml(cache_id=cache_id)
  File "/usr/local/lib/python3.12/site-packages/denonavr/foundation.py", line 494, in async_update_power_status_xml
    raise AvrProcessingError(
denonavr.exceptions.AvrProcessingError: Power attribute of zone Main not found on update

What version of Home Assistant Core has the issue?

2024.2.1

What was the last working version of Home Assistant Core?

n/a

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

DenonAVR

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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)}}

[ol-iver]

You might have something in the network which responds on the device's behalf when it is powered off. Usually, the connections should time out which makes HA marking the receivers as unavailable.

[issue-triage-workflows[bot]]

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.