forked-daapd integration doesn't retry

[BenS89]

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.

2021-11-30 22:50:41 ERROR (MainThread) [pyforked_daapd] Can not get http://172.30.33.4:3689/api/config with params None
2021-11-30 22:50:42 ERROR (MainThread) [homeassistant.components.media_player] Error while setting up forked_daapd platform for media_player
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/src/homeassistant/homeassistant/components/forked_daapd/media_player.py", line 106, in async_setup_entry
    await forked_daapd_updater.async_init()
  File "/usr/src/homeassistant/homeassistant/components/forked_daapd/media_player.py", line 771, in async_init
    if websocket_port := server_config.get("websocket_port"):
AttributeError: 'NoneType' object has no attribute 'get'

@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

[frenck]

Can you please adjust the subject of this issue to be meaningful? Thanks 👍

../Frenck

[home-assistant[bot]]

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!

Code owner commands

Code owners of forked_daapd 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 forked_daapd Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[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.