core
core copied to clipboard
Unable to provide credentials to Squeezebox / LMS integration
The problem
There is no provision for entering username and password for a Squeezebox / LMS server after turning them on.
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 OS
Integration causing the issue
Squeezebox
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
I found a workaround for my problem, but the interface should (IMO) provide a means of doing this - e.g. you want to change passwords. My workaround is this:
Manually edit /homeassistant/.storage/core.config_entries and add lines for username and password in the "domain": "squeezebox" section
Hey there @rajlaud, mind taking a look at this issue as it has been labeled with an integration (squeezebox) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of squeezebox can trigger bot actions by commenting:
@home-assistant closeCloses the issue.@home-assistant rename Awesome new titleRenames the issue.@home-assistant reopenReopen the issue.@home-assistant unassign squeezeboxRemoves the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-informationRemove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
squeezebox documentation squeezebox source (message by IssueLinks)
I'll look into adding this. In the meantime, you can simply delete and re-add the squeezebox server in the Integrations tab of settings.
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.