Did you try rebooting your processor so see if the Sonos is
rediscovered?
Sounds like a Cloud problem to me.? Why else would everyone start
have issues.? That may be Crestron's fault or it may be a Sonos
cloud service problem.? The Reboot issue sounds like a bug in the
Sonos module where if it gets something unsuspected, the processor
reboots -- its not the first time I have seen something like this.
So far none of my clients have called me but for the most part, we
constructed our programs where is the Sonos module breaks, it the
Sonos will continue to work.
On 10/2/20 4:25 PM, ckangis via
groups.io wrote:
toggle quoted message
Show quoted text
Interestingly, I'm at a site with (2) PORTs (S2-12.1) and a
CP3/TSWx60 setup, and 'So Far' no problems!?
I'm running CP3 PUF v1.601.0050
I have disabled all the ENABLEFEATURE items, including
HYDROGENENABLE
My Friend is running a couple CONNECTs at his house with a CP3 set
to the same FW, etc. and he's having issues... So Weird!!
