¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Crestron
  2. Topics

Sonos muting

 

Hey guys,

Our customer has a simple sounding request but never having worked with Sonos before I am not sure how to accomplish this.

All they want to do is mute all Sonos players if they get an alarm in.

I have added a Sonos Device Module v3.2.0 for each Sonos.? All have the default parameters except for the player name.

On the module inputs I have only Restart and MutePlayer connected.? Every other connection is commented out.? On the outputs I have Offline connected for debugging.

What makes this extra fun is the Crestron traffic and Sonos traffic are on different VLans, but our IT group can take care of that if necessary.

If I run the code I get:

? 1. Notice: SimplPlus[App01] # 2023-10-14 04:02:55 # CRPCConnectionHelper - Created CIP Transport for ipaddress: 192.168.69.70, port: 41798, adapterID: 0
? 2. Notice: SimplPlus[App01] # 2023-10-14 04:02:55 # Sonos - Multicast discovery started.
? 3. Notice: SimplPlus[App01] # 2023-10-14 04:02:55 # Sonos - The system state changed to "Connecting to Primary Device".
? 4. Notice: SimplPlus[App01] # 2023-10-14 04:03:25 # Sonos - Discovery state changed to idle.
? 5. Notice: SimplPlus[App01] # 2023-10-14 04:03:25 # Sonos - Multicast discovery result: no devices found.
? 6. Notice: SimplPlus[App01] # 2023-10-14 04:03:25 # Sonos - The system connection failure reason changed to "No Devices Found".
? 7. Notice: SimplPlus[App01] # 2023-10-14 04:03:25 # Sonos - Discovery mode changed to "broadcast".
? 8. Notice: SimplPlus[App01] # 2023-10-14 04:03:25 # Sonos - Broadcast discovery started.

In the error log.? This sounds like VLan issue.

I guess my question is am I doing this correctly, or do I need a full CRPC type connection to get this to work?? Is there an easier way?

Do I need to Restart every device or is one enough?

Thanks
 

Crestron and Sonos must be on the same network.
Simply won't work if they are not.
 

¿ªÔÆÌåÓý

I've never seen a Sonos device let alone tried to control one, but from the error log "Multicast" and "Broadcast" device discovery strongly suggest that the module is expecting to find Sonos on the same broadcast domain (i.e. subnet) as the processor?

Multicast routing between subnets/vlans is conceptually possible but I would be surprised if Sonos or the module have been tested in such a scenario... As it is one of my colleagues is battling a "foxed again, broke again, fixed again, broke again" issue with multicast on the 4-series firmware, but I believe that only affects processors with an internal router (CP4N, PRO4, AV4)

Get

From: [email protected] <[email protected]> on behalf of Devin Cook <devin.cook@...>
Sent: Saturday, October 14, 2023 4:42:10 AM
To: [email protected] <[email protected]>
Subject: [crestron] Sonos muting
?

Hey guys,

Our customer has a simple sounding request but never having worked with Sonos before I am not sure how to accomplish this.

All they want to do is mute all Sonos players if they get an alarm in.

I have added a Sonos Device Module v3.2.0 for each Sonos.? All have the default parameters except for the player name.

On the module inputs I have only Restart and MutePlayer connected.? Every other connection is commented out.? On the outputs I have Offline connected for debugging.

What makes this extra fun is the Crestron traffic and Sonos traffic are on different VLans, but our IT group can take care of that if necessary.

If I run the code I get:

? 1. Notice: SimplPlus[App01] # 2023-10-14 04:02:55 # CRPCConnectionHelper - Created CIP Transport for ipaddress: 192.168.69.70, port: 41798, adapterID: 0
? 2. Notice: SimplPlus[App01] # 2023-10-14 04:02:55 # Sonos - Multicast discovery started.
? 3. Notice: SimplPlus[App01] # 2023-10-14 04:02:55 # Sonos - The system state changed to "Connecting to Primary Device".
? 4. Notice: SimplPlus[App01] # 2023-10-14 04:03:25 # Sonos - Discovery state changed to idle.
? 5. Notice: SimplPlus[App01] # 2023-10-14 04:03:25 # Sonos - Multicast discovery result: no devices found.
? 6. Notice: SimplPlus[App01] # 2023-10-14 04:03:25 # Sonos - The system connection failure reason changed to "No Devices Found".
? 7. Notice: SimplPlus[App01] # 2023-10-14 04:03:25 # Sonos - Discovery mode changed to "broadcast".
? 8. Notice: SimplPlus[App01] # 2023-10-14 04:03:25 # Sonos - Broadcast discovery started.

In the error log.? This sounds like VLan issue.

I guess my question is am I doing this correctly, or do I need a full CRPC type connection to get this to work?? Is there an easier way?

Do I need to Restart every device or is one enough?

Thanks
 

I am controlling a Sonos Sound Bar with the same Crestron logic you described and it works fine. I would also guess your issue is a network one.
 

I have gotten Sonos to work across subnets with Crestron on one subnet and Sonos on another subnet.? However you need a router that can support an mdns repeater and igmp-proxy functions.? I know it works with the Series 3 processor however I cannot speak for the series 4. It is usually more trouble than it is worth so I normally put Sonos on the same subnet as Crestron.
 

Though I agree that you can definitely get this to work,
Why not just switch your audio Switcher to an unused input or something like that, until the condition resolves...
 

We don't have any audio switcher in front of these boxes.? Usually people Airplay to them.

By the way, is there a need to hit restart on each player or is one enough?
 

You shouldn't ever need to hit restart. Since the module loses connection every few months, I now hit restart every morning
 

Eric,
Have you found the 'Restart' to reliably restart communications on a single player that has gone off-line? I assume that you have some logic to pulse RESTART when the unit registers OFFline status?

My issue with the Sonos integration for years now is that the whole 'SYSTEM' will go offline, requiring a program slot restart. I'm not sure that the player 'restart' command would resolve this...
The SonosSystem module has an 'Initialize' input but my experience is that retriggering this does not restart the communications (I've asked Crestron to *Fix* this for 4+ years...)
I have built a whole separate slot program for Sonos equipment with specific online/offline logic just to be able to restart it when things go south, without having to 'Reboot the whole house!'...

Any add'l insights would be welcome
 

The project I did this on has only been running for a few weeks. It has not been long enough to tell if it actually fixed anything.
 

Just a note for anyone searching for answers in the future.

It turns out that the Sonos Device Module is not enough.

After talking to Crestron I needed to add a Sonos System Module as well, and let it initialize the system.? Takes a while to start up but so far so good.? When the Device Module only was used the results we all over the place.? It would talk for a while, then stop talking etc.
 

It was my understanding you ALWAYS have to have the Sonos System module in the program for anything Sonos to even work. And it has to be placed above the individual Sonos Device Module(s)??
 

Agreed!? I'm shocked that it worked at all...

1 - 13 of 13