I recently replaced a Sonos Connect in my living room with two Sonos Era 100 speakers. These speakers are paired together in Sonos, but show up in Hubitat as two seperate devices. I am unable to communicate with either of them via my Hubitat. They work fine outside of Hubitat. The log file indicates there is "No route to host". It's like they are powered off. I verified their IP addresses in Sonos, and reserved the IP's in my Linksys router. I've deleted the devices and readded them to no avail. I also cycled power to the speakers. All of my other Sonos devices which are working.
I'm attempted to remove the Amazon Echo Skill and re-install it, but that would result in a lot of broken rules and a lot of work. Maybe there is a compatibility issue with the newer Era 100 speakers?
The IP addresses of these two speakers - based on the Sonos app or your router (the addresses are non-routable, being within your LAN, so there's no security risk in posting them).
The device network ID (DNI) for the two speakers. For eg, here's the DNI for one of my speakers:
I factory reset the two Sonos Era 100 speakers and readded them to Sonos and removed all references to the former living room speakers from Hubitat, Sonos, and my router. They were assigned the 1.41 and 1.80 addresses shown below. I then created a stereo pair named Living Room and tested in the Sonos Android app and desktop app. Also, I reserved these two IP addresses in my router.
Then I attempted to add these speakers to the Hubitat Sonos Integration. Instead of adding the Living Room pair, it added two separate Living Room devices (again):
The IP addresses assigned by the Sonos Integration do not match what they actually are in my network. Based on the DNI values the IP addresses do not match anything on my network. Which explains the "No route to host" errors:
I have other Sonos 1 speakers in pairs which are processed by the Sonos Integration correctly. It is only the new Era 100 speakers which do not work. This appears to be a compatibility issue between the Sonos Era 100 speakers and the Sonos Integration software.
The Sonos integration running on Hubitat isn’t really assigning any IP addresses, AFAIK.
It’s only listening for the IP addresses that the Sonos devices themselves are broadcasting while the integration on the hub is in discovery mode.
That’s possible. Sonos devices generally create a secondary network for use amongst themselves that’s supposed to be invisible to the user. Perhaps these IP addresses on the Era speakers are part of that so-called SonosNet and the Hubitat integration is getting confused.
But sometimes posts just don’t get a reply for a few days.
In that case, you can simply create another post in your own thread (also objective evidence that a thread hasn’t been closed, btw) and “bump” it back to the top of the “latest topics” list and perhaps get more attention that way.
Not only is the IP address an issue, but Sonos Integration is not grouping the speakers together in my living room with Era 100 speakers. In my office I have two Sonos 1 speakers grouped, and Sonos Integration creates one device Sonos Office.
I can see events in the Living Room Sonos device but of course cannot hear audio. The log file is filled with "No route to host" errors because of the incorrect IP addresses.
I actually came up with a partial workaround. I took the IP addresses in Hubitat based on the DNI ID's, and changed IP address to what Hubitat was expecting and it worked! I didn't expect Sonos to continue working after I changed the IP's but it did. Also I get sound out of both speakers if I select both devices in a rule action (See below). I just played an mp3 file as a test and got sound out of both speakers.
UPDATE: By changing the Sonos living room IP addresses in my Linksys router to match the DNI in the 'Living Room" devices created by the Sonos Integration, I was also able to get Sonos Favorites Support working using these devices. Cool!
