So I typically have a rule setup to have Hubitat wake me up in the morning by playing a stream on my Sonos Speaker. This morning I woke to discover that my Hubitat is no longer controlling my Sonos. In my limited time this morning before leaving work. I confirmed through the Sonos app that the speakers are connected to the network and working. I ran the Sonos App and Hubitat sees both speakers but doesn't control them through the device handler (stop/play/tts/etc). Any thoughts? I'm lost.
I've had to remove and re-add my Sonos speakers and app 3 times so far because one speaker will drop off. All my speakers have static IP addresses, so it's not an IP issue. I can always tell when one drops off because the logs will start showing "no route to host" errors.
I was hoping that wasn't going to be the response, I have them included in about 15 different rules. Does that mean I have to recreate all the rules after I delete and re-add?
Yup. I feel your pain, trust me. You shouldn't have to delete the rules and recreate them, just go back in and set your speakers up in the Send or speak a message section.
However, until it gets fixed (if it gets fixed), I would use @Cobra's Speaker Central to control your speakers. It creates a Proxy Speaker Device. So, when something like this happens, all you have to do is re-add the Sonos back to Speaker Central and not have to fix 15+ announcement rules.
1 Like
I have the same issue. @mike.maxwell looks like I am not alone with the Sonos issues. When I see the errors (or lack of TTS playback) I first check the Sonos app to ensure the Sonos device is working properly. If no issues (which is the majority of the time) then a reboot of the HUB is usually required and most of the time removing the Sonos app, devices if still there and reinstalling. Has happened about 6-7 times this past month between 2 of my 4 Sonos devices.
1 Like
The thing that irks me is that it's only usually one speaker that drops off and just happens to be my only Sonos One. All my other speakers have been stable (4 Play-1 (gen 1) and 1 Play-5).
I only have two and both of them went MIA this morning. Up until this incident they've been solid for a couple months.
What model are they? I haven't been paying attention, but has Sonos put out a firmware update recently? I know they did one a few months ago.
I haven't noticed a new update recently. I thought Sonos required you to approve updates before installing? Regardless both of mine are Play-1's. Not sure what generation.
I have (2) 1’s, (1) 3 and a Play-1. The Sonos One is the ones dropping all the time. Just checked and sure enough it is gone again this morning.
Last update was back in January.
1 Like
You can set them to auto-update now. I never let mine, but I know some people do.
1 Like
So I did more research over the weekend and did find a support article about Sonos Play devices and router issues for DHCP and IPs. Basically, the Sonos device "spoofs" the router and does not ask for a renewal/extension of it's current DHCP reservation and just makes an assumption that it owns it. Crappy development by Sonos honestly. So when the router ages out the IP it will reassign the IP as available and of course then there will be issues. Hence a duplicate IP address assignment on the network on conflicts. Since I have a lot of guests in/out and devices on my network I have a DHCP lease period of 3 days. So this can make sense why I have been having issues.
I have an assigned a partial class B (10.0.x.x) for my home network so I can assign devices in different ip ranges. I decided to move ALL of my Sonos over to a 10.0.3.x where the IP range is beyond the number of reserved IP addresses being requested/used. After rebooting the Router the Sonos devices that dropped off came back on. Will see if this fixes the issue.
2 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
