Bas ic information
KNX Sonos -Gateway
MR-SONOS-REG
© 2019 Albrecht J ung GmbH & Co. KG
p. 31 / 118
Cas e s tudy – continuation 2:
•
You now activate Sonos devices 3 and 10 as s laves in mas ter-s lave group 4.
•
Res ult: No changes . Why?
Sonos device 4 continues as a s lave and therefore does not have its full mas ter functions to add an-
other Sonos device as a s lave to a group. Us ing a mas ter function does not neces sarily automatically
mean that the Sonos device switches to the mas ter role. You can only us e mas ter functions to a lim-
ited extent (also see
Table 5: Overview of a Sonos device's behaviour in the role of a s lave in mas -
until you releas e it us ing the <<Exit s lave mode>> communication object. It continues
to play the mus ic of its master, Sonos device 1. The <<general err>> error is trans mitted on the
<<Sys tem s tatus >> communication object s ince the s laves cannot be activated. The mas ter-s lave
group 4 s laves remain inactive.
Things to remember
A slave belongs to the master for which it was last activated.
If a Sonos device had the status "Master" before it was activated as a slave, it loses its status as
a master.
A Sonos device remains a slave until you do the following:
•
You can use another master-slave group master's <<Exit slave mode>> communication
object to remove the device from the group if the said Sonos device is configured as a mas-
ter there.
•
You use the slave's communication object <<Slave 1/2/3/4/5 – Switch group association>>
to remove the device from the master-slave group where it is active as a slave.
•
You can remove the Sonos device from the Sonos group in the Sonos software.
