Music Assistant
Cannot group musiccast receiver as slave to other musiccast speakers. #5560
-
|
Wondering if this is what is referred to in the documentation, or whether there are any workouts to prevent this issue: "The main zone cannot be successfuly joined to a non-main zone. Attempting to do so will result in unexpected behaviour". When grouping the main zone from a HTR-4072 musiccast receiver to any of the other musiccast speakers - with the main zone from the receiver being a slave and not the master - the logs show the following error message: 2026-05-31 13:37:33.564 WARNING (MainThread) [music_assistant.MusicCast] It is impossible to join as a normal zone to another zone of the same device. Only joining to main is possible. Please refer to the docs. For completeness sake: i'm only using the main zone of the receiver, zone B isn't even configured. When grouping using the main zone as the master, everything works accordingly. Interestingly, using the musiccast app it doens't matter whether the receiver is a master or slave. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Beta Was this translation helpful? Give feedback.
-
|
You should be able to join a main zone (and also any other zone) as a member to another group leader of another device. The doc's refer to the same device, you cannot make a zone a leader and join main as a member if they are on the same device. If you are not using the zone at all, could you try disabling it in Music Assistant and try again. On which version of MA you? In our most recent betas, there are some changes to the zone handling, so you could try a version before beta 14. Remember to take a backup. |
Beta Was this translation helpful? Give feedback.
-
|
thanks for the quick reply. disabling the zone B speaker does not solve it, unfortunately. i'm running 2.8.8, (so i'm guessing i don't need to revert to a previous version as i'm not running beta?). Any other suggestions? |
Beta Was this translation helpful? Give feedback.
-
|
Then the suggestion would be the other way round - try the most recent beta and see if that helps. If you are using MA as an HA add on, you can just stop your stable instance, install beta in parallel, and give it a go. They are independent from each other. Just make sure, that you don't have both running at the same time. |
Beta Was this translation helpful? Give feedback.
-
|
Works with the beta! I'll wait for the stable release, it's not a big issue. Many thanks |
Beta Was this translation helpful? Give feedback.
Then the suggestion would be the other way round - try the most recent beta and see if that helps. If you are using MA as an HA add on, you can just stop your stable instance, install beta in parallel, and give it a go. They are independent from each other. Just make sure, that you don't have both running at the same time.