Heos: "Command timed out" after reload of integration, entities unavailable

[danielschenk]

The problem

After reloading the Heos integration, I get an error in the UI about a command which timed out. It keeps retrying without success. Also, I enabled debug logging and I saw a really high-speed spam of connect/disconnect logging messages. I already tried the following without luck:

• delete configuration and re-add the controller
• reload integration
• restart HA completely
• power cycle all my Heos devices

What version of Home Assistant Core has the issue?

2024.10.3

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 Heos

Link to integration documentation on our website

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

Diagnostics information

home-assistant_heos_2024-11-15T10-05-29.153Z.zip

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

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

Code owner commands

Code owners of heos 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 heos 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)}}

---

heos documentation
heos source
_{^{(message by IssueLinks)}}

[danielschenk]

FYI, now with another reboot of HA itself after I already had power cycled the devices, it works again. It seems to have to do with the Heos side too, however, I still think that there's an issue in the integration here. Those rapidly repeated messages in the debug log just don't seem right. If my Heos is OK again this integration should be able to recover on its own, IMHO.

[andrewsayre]

Can you share the logs? There shouldn't be any high-speed spamming coming from HEOS. If it can't connect initially, it won't load the integration and ask HA to retry, which it does after a delay.

[danielschenk]

@andrewsayre I've uploaded a diagnostics file which has the logs, it's linked in the issue description.