Owntone: Server unavailable

[00lex]

The problem

Hi since first release of 2022.11.0 till today owntone server (v28.5) is unavailable.

my workaround is to copy forked_daapd files from HA 2022.10.5 to my updated version of HA 2022.11.4

https://github.com/home-assistant/core/tree/2022.10.5/homeassistant/components/forked_daapd

What version of Home Assistant Core has the issue?

2022.11.0-2022.11.4

What was the last working version of Home Assistant Core?

2022.10.5

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Owntone / forked_daapd

Link to integration documentation on our website

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

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 @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` Change the title of 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)}}

[uvjustin]

I am unable to replicate this on my end. Is it possible that you have a copy of forked_daapd in custom_components?

[00lex]

Do you mean /home/homeassistant/.homeassistant/custom_components/ ? no I even don’t have this folder.

Tried a fresh install of 2022.11.0+ and removing/ adding the integration. Same. Speakers are ok, only the server is unavailable. I only can Test now what happens if I start ha without my backup. Fresh. Stange

[uvjustin]

If you remove and readd the integration, the entity name will probably change since the default name has now changed from forked_daapd to owntone. You'll need to update your frontend to point to the new entity.

[00lex]

Yes I saw that. But I am looking at the entities direct over the integration of owntone.

just two questions. Could there be more dependencies than in /custom_components/ inside the home folder? Maybe inside the .storage folder 👉

core.config core.config_entries core.device_registry core.entity_registry

I’m on the road and limited to check. Just have ssh and my smartphone.

do you running a official HA Version or your own dev version?

[00lex]

Now I tried from scratch. fresh install and no recovery of my setup. server is unavailable. im done for now.

my last request is, if you ever find the time, please install an official Home Assistant and report back with the results.

for me, this is a dead end. if a complete fresh install not work but the last HA version 2022.10 with forked_daapd before renaming works, what can I do?

If someone has same issues and stumbles upon this, take the old forked_daapd integration: https://github.com/home-assistant/core/tree/2022.10.5/homeassistant/components/forked_daapd

[uvjustin]

I am using Home Assistant Container 2022.11.2. Are you able to use Home Assistant Container? Home Assistant Core is really not recommended and can be hard to troubleshoot.

[00lex]

for me it was important to know you have a stable version of HA running. core is core no matter if docker container or HA-OS. now test again if it behaves differently with docker would be a homeopathic solution approach :) anyway. It seems its a very personal problem. my update script includes meanwhile a part which replaces the forked_daapd integration with the old one. that's ok for me. btw. I just moved to HA 7 weeks ago and I am still not aware why core might be the wrong base. I can very easy cp, mv or tar a installation before update and like in this case modify the installation.

I'll be in touch if I ever find out what was going on. thank you for your time

[uvjustin]

Actually it does make a difference. HA OS and HA Container are much more consistent in the environment they set up, so there are less problems that arise, and it's also easier to reproduce/troubleshoot/fix issues when they do arise. That's why those are the two recommended install types.

[00lex]

Puhh then I will fire a VM to test a docker container too. I don’t like unnecessary stuff/ additional layers on my pi. See you 🥴

[00lex]

I did not try the docker image but the ready haos_ova-9.3.vdi and it works. I tried core on a Debian x86 vm and its the same as my rpi. not working. core seems to be the problem. but how can it be that a simple name change has such consequences?

i'm not a programmer myself and i don't know anymore. is there any further change you introduced with the renaming? again, the old integration is fully functional in a current home assistant.

i can very well imagine the whole thing getting annoying. i will end the whole conversation immediately if you say own tone will not run in home assistant core in the future.

[uvjustin]

I would say it's probably not the renaming, but more likely something to do with updating the packages from PyPI (the packages forked_daapd uses were updated between 2022.10 and 2022.11). However, I don't see why this should be a problem with a normal install - the packages used are simple Python packages, architecture independent, with no C extensions. Owntone should run under Home Assistant Core, but Core is an advanced installation type, and there are a lot of potential issues with user setups that can pop up that we can't troubleshoot or fix. I highly recommend using Home Assistant Container on Docker - it will reduce the number of issues you encounter and make maintenance/upgrades easier, while still avoiding the unnecessary overhead of a VM.

[00lex]

hi! thanks for your explanation. I'm a bit tired from moving to home assistant to take this step. i'll stick with my setup for now and switch to docker on occasion or when unrecoverable problems occur.

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