Closed coen1111 closed 4 weeks ago
@SantiagoSotoC
It's the first beta you've used and this appeared in the last one? Or first time you create a Sync group ?
Can't recreate this. I have a group sitting there for a few hours?
I used to run into this issue a lot, but it’s been pretty stable for me since version 2.2.0. What worked for me before was deleting the sync group and recreating it, which would keep things stable for a few hours. But ever since the 2.2.0 update, I haven’t seen the problem come back.
I replaced my MA by 2.2.0 and recreated the Sync Group, I will try to see if that works out.
Well the beta should be better. So if this works with 2.2.0 then revert again to the beta and see what happens (after recreating the group in the beta server)
This morning with 2.2.0 the Sync Group has become unavailable again, I also noted that you are not able to configure it once unavailable.
I disabled 2.2.0 and have installed the latest beta add-on. I there recreated the Sync Group, I will update here what will happen.
I encounter the same issue in 2.3.0b29. This morning a big part of my Snapcast players and the Sync Group where unavailable.
What seems to help is restarting the add-on (the Facility room: Stereo is really powered off with a plug, so shall be unavailable)
So something over time happens which makes Snapcast players unavailable.
Do you anything unusual about your network setup? Anything at all that someone may consider non standard with your install. I have a Snapcast group sitting happily on my instance for days now.
The Snapcast players are all Rpi+Hifiboards, which are connected to old stereo players. Since these stereo players have good audio, but terrible stand-by use (typically 20 W or more) I have a power plug to turn everything on/off. This did not give issues before with my Snapcast setup, but it might cause issues for the beta.
How is the disable state for a player or Sync Group determined now?
The Snapcast players are all Rpi+Hifiboards, which are connected to old stereo players. Since these stereo players have good audio, but terrible stand-by use (typically 20 W or more) I have a power plug to turn everything on/off. This did not give issues before with my Snapcast setup, but it might cause issues for the beta.
How is the disable state for a player or Sync Group determined now?
Do you turn off the Raspberry pi ?
This issue is stale because it has been open 7 days with no activity after asking for more info. Comment or this will be closed in 3 days.
This issue was closed because it has been stalled for 10 days with no activity. This can be reopened if additional information is provided.
What version of Music Assistant has the issue?
2.3.0b27
What version of the Home Assistant Integration have you got installed?
2024.9.1
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?
The problem
I created a Sync Group of several Snapcast players. Initially they work fine, however after some time the Sync Group becomes Unavailable, while the Players within this Sync Group are available. See the attached screenshots.
How to reproduce
Music Providers
All
Player Providers
Snapcast
Full log output
music-assistant.log
Additional information
No response
What version of Home Assistant Core are your running
2024.9.3
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Raspberry Pi