Closed BenS89 closed 1 year ago
Can you please adjust the subject of this issue to be meaningful? Thanks 👍
../Frenck
Hey there @uvjustin, mind taking a look at this issue as it has been labeled with an integration (forked_daapd
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
forked_daapd documentation forked_daapd source (message by IssueLinks)
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.
The problem
The problem described in #60724 still exists on newest HAOS. After a VM restart, the integration tries to connect for one time and throws the following error since not all ad-ons are ready. The current fix is to restart the core (Supervisor -> System -> Core -> Core restart). After the core is restarted, the integration works as expected.
@a-marcel
What version of Home Assistant Core has the issue?
Home Assistant 2023.2.5
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
No response
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