Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heos Integration unvailable needs to be reloaded #117719

Open
kruzgix opened this issue May 19, 2024 · 7 comments
Open

Heos Integration unvailable needs to be reloaded #117719

kruzgix opened this issue May 19, 2024 · 7 comments
Assignees

Comments

@kruzgix
Copy link

kruzgix commented May 19, 2024

The problem

The integration becomes unavailable until the integration is reloaded

This issue has already been described: #86475 (comment)

What version of Home Assistant Core has the issue?

core-2024.4.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Heos

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?

There is no active log when the integration becomes unavailable. Only if you want to use the device there is an error that the device is unavailable.

Additional information

No response

@kruzgix
Copy link
Author

kruzgix commented May 19, 2024

Link to integration documentation: https://www.home-assistant.io/integrations/heos/

@home-assistant
Copy link

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)

@Clooos
Copy link

Clooos commented May 24, 2024

Hi, I have this issue too. It's working for 4 or 5 days then it stops working, sometimes an HA reboot is not enough and I have to reboot my Denon AVR as well.

@kruzgix
Copy link
Author

kruzgix commented May 27, 2024

This weekend I realized that Home Assistant Supervisor is supporting Debian 12 "bookworm". I still had Debian 11 "bullseye"... so I noted more and more bugs.... heos, protocol of add-ons not accessible, etc.
-> I updated to Debian 12, now all is running again.... at least for a few days :-)
I will wait for at least 1 week, because Heos crashed always earlier, if everithing is fine, I will close this issue.

@ndarilek
Copy link

@kruzgix Please don't close this. I'm having it too on a fully supervised OS installation with the exact same symptoms. My integration became unavailable with nothing in the logs. The controller IP was still valid, it just stopped controlling the device. Clicking the "Known issues" link on the integration brought me straight here and showed me a workaround. If it's Debian-specific, it's on about the happiest path possible, and should remain open so folks know how to fix it.

Also, thanks for filing this. Had to rebuild my home lab from scratch for reasons, and wasn't looking forward to having to figure this one out myself.

@kruzgix
Copy link
Author

kruzgix commented Jun 1, 2024

After 1 week, home assistant 2024.5.5 with supervisor 2024.05.1 on debian bookworm is running and humming :-)

But the heos integration still crashes after some days and must be reloaded to work again. So I have to keep this issue.

@davey400
Copy link

davey400 commented Jun 8, 2024

Same issue here.
Problem occured a few weeks ago for the first time; have not been able to solve it after several retries and choosing several different 'masters'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants