Possible Solution for Sonos Things going into OFFLINE - Communication_Error
I have been having lots of troubling keeping my 13 Sonos devices “ONLINE” within OH 2.4 consistently for over 11 months. I’ve tried Sonos binding versions 2.4m1 - 7 and 2.5m1 and I keep seeing the same results of them going into “OFFLINE - Communication_Error” states. Sometimes they go back online but mostly what happens is one goes offline then the rest will slowly follow so all of them are in “OFFLINE - Communication_Error” state. Only way I found to get them back online with OH is to restart OH.
Lots of talk about JUPNP being the problem. I’m running these UPNP versions:
openhab> list -s | grep upnp
212 │ Active │ 80 │ 2.5.2 │ org.jupnp
218 │ Active │ 80 │ 0.11.0.oh250M1 │ org.eclipse.smarthome.config.discovery.upnp
296 │ Active │ 80 │ 0.11.0.oh250M1 │ org.eclipse.smarthome.io.transport.upnp
Current Sonos Binding:
openhab> list -s | grep sonos
300 │ Active │ 80 │ 0.10.0.oh240M6 │ org.eclipse.smarthome.binding.sonos
This is from someone on a Sonos support community board which got me thinking:
"So I have been having same issues for months after over a year of zero issues. Same network nothing changed except SONOS began to not work. Tried almost all the answers here - reboot reboot —sounds like my IT here at work. Usually, the issues arise whenever we involve ALEXA. Even if you dont use it. I was in my Amazon account and ended up finding my way to Alexa settings and noticed my registered sonos devices. I just deregistered all of them . . . "
I have numerous Sonos devices connected via Alexa via OH HUE Emulation tied to Switches. I’m not using the Sonos Skill with Alexa so the actual Sonos devices are not listed as a device for me BUT
I ended up going into the Alexa Mobile App into devices and disabled ALL Sonos related devices that Alexa had linked up as a device from an OH perspective. It’s been 24 hours and NONE of my Sonos devices have fallen off OH since I did this. I have pushed rule policies at least 3 times and started/stopped OH also during this time period which sometimes starts to cause the issue with Sonos.
It’s my belief that Alexa/Amazon is scanning all devices for states and it causing the Sonos devices to fall off of OH. I’m not sure if this has anything to do with Sonos natively OR its tied to the HUE Emulation piece of it?
Can someone else having this Sonos issue please try what I did to help validate it?
Best, Jay