Open jimbovp opened 6 months ago
Hey there @luar123, mind taking a look at this issue as it has been labeled with an integration (snapcast
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
snapcast documentation snapcast source (message by IssueLinks)
Confirming this issue as well. It defaults to:
service: snapcast.join
data:
master: media_player.<Master>
entity_id: <---
entity_id: media_player.<Subscriber>
It should present as:
service: snapcast.join
data:
master: media_player.<Master>
entity_id:
- media_player.<Subscriber>
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.
Not stale
The problem
When using the service snapcast.join in UI mode (in Developer tools or in a script), the service isn't working correctly. Switching to YAML mode shows that an "entity_id" is erroneously added in the service, which causes the service call to fail:
Correcting the YAML to the correct format as follows, the service can be called:
What version of Home Assistant Core has the issue?
core-2024.4.3
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
snapcast
Link to integration documentation on our website
https://www.home-assistant.io/integrations/snapcast/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
No response