Closed derekatkins closed 2 years ago
forked_daapd documentation forked_daapd source (message by IssueLinks)
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)
Sorry, I was out of the country without my laptop during the "stale" period. @uvjustin any chance you could have a look at this?
The problem
I have a server running multiple instances of Owntone on different ports. Owntone is quite happy to do this, and it works fine by the Owntone WebUI. However, even though Home Assistant will see all the instances, it will only let me configure one. Once I have one configured, any additional configuration says "Device is already configured". Moreover, when it sees the ZeroConf message from another instance (on a different port) it will update the name. So instead of saying "Basement - owntone.local" it will change it to "Main Level - owntone.local" --- which is certainly incorrect.
To test this, run two instances of owntone on the same machine. You will need to duplicate owntone.conf into another file (owntown-zone.conf), you will need to uncomment and change the three "port" definitions, and change the two database definitions, and then you can run owntone -c owntone-zone.conf. Then go to HA Configuration -> Integrations and try to configure both instances of owntone. It'll let you do the first, but wont let you do the second.. And if you restart HA it may change the name of the configured instance.
What version of Home Assistant Core has the issue?
2021.11.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
forked_dappd
Link to integration documentation on our website
https://www.home-assistant.io/integrations/forked_daapd/
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response