[Nearing Release] Sonos Advanced Controller

[marc8]

By the sounds of it, this is a phenomenal app and I'm so envious of everyone that has gotten it to work for them. I have been trying unsuccessfully for weeks to get the app to find my Sonos devices. I have reviewed the pages and pages of notes here and have seen others occasionally run into what I'm seeing, but haven't found a solution. Here's a summary...

I've installed the app in HPM (v0.7.4) and added it as a User App. But when it launches and I start a Discovery to find my devices, of which I have 13 (10 Ports, 1 Amp, 1 Bean (and associated Sub), and 1 One), it only finds one of the devices. I have tried this over and over always with the same results. I have turned on logging and believe I see the problem - it appears to be checking a bunch of my devices on my network and (correctly) determining they are not Sonos devices. But only once did it check the IP address of a device that actually was a Sonos. Anyone know where the app is getting its list of IP addresses to check? Seems like whatever is providing the list of IP addresses is not up to date and maybe giving old IP addresses for my Sonos devices.

Although my Sonos devices do not have static IP addresses, they rarely change. I've gone into the Sonos app on my iPhone and put in a spreadsheet the IP address (and MAC address) of each of the Sonos devices. With the exception of just a couple devices (Beam/Amp, One), they are all hardwired to the main switch. I'm running on a Ruckus Unleashed Router through a Ruckus IPX7450 switch.

Here is an excerpt from my log (bottom up):

[Actually I tried embedding a screenshot but it says I'm not allowed to do that. I'll keep working on trying to get it posted.]

I am running on a C-8 Pro with 2.4.0.151 firmware. FWIW, I first installed the built-in Sonos Integration and that did find all the Sonos devices. But actually I just went back to try it again and it too only finds the one device. I went into my Sonos App on my iPhone and it still works just fine with all 13 devices.

Any help from experts on this forum would be greatly appreciated. I can't wait to finally be able to use some of the great features @daniel.winks created, especially being able to join Sonos devices together, which I've never been able to do with my Lutron (RadioRa2) system.

Thanks in advance!

Marc

[marc8]

Just a quick follow-up. I rebooted my Windows machine that I'm using to run the Hubitat UI. I then downloaded the Sonos App onto the machine to see if it could find the devices. It first needed permission to update the firewall settings, so I thought that would be good news, but it then said it didn't actually need to update it. When I told it to find my Sonos devices, right away it showed me all 13. So then I went back to the Sonos Advanced Controller and told it to discover my devices. Same result as before... Just the one device and a whole bunch of checks on IP addresses not belonging to Sonos devices. So I'm still stuck...

[DGBQ]

@marc8

Just the one device

Hope this helps...

@DGBQ

Unfortunately, the developer of this app has been unresponsive since April 2024. I encountered a similar issue when uninstalled, deleted, re-installed and re-setup all my players. My setup was a bit chaotic, as I had helped with a lot of the initial testing.

What worked for me was running the full setup process repeatedly for each of my devices—just the setup, not the installation. Eventually, all the players showed up as Devices. I hope this approach helps you too.

Hopefully, the developer will return to this project soon.

[JamesTX10]

@marc8

Although my Sonos devices do not have static IP addresses, they rarely change.

I am pretty sure you are going to want to reserve the IPs in DHCP so they always get the same IP. Once you have it working you are not going to want issues because the IP changed.

[mluck]

Does anyone have any insight into using this app to queue TTS messages so that they don't interrupt or step on each other if they are issued in quick succession? Really struggling with this....

[marc8]

Thanks @DGBQ and @JamesTX10. That's the area I'm focusing on, fixing the IP addresses. That brought up a different issue, which I'll deal with separately and probably on a different topic (Hubitat won't let me assign its IP address as 192.168.0.50 with my router and gateway at 192.168.1.1 even though my subnet mask throughout is 255.255.254.0). I will assign IP addresses for each of the Sonos devices within DHCP. But I still need a way to get Hubitat, or whoever is remembering, to forget what it currently thinks the IP addresses are for the Sonos devices. I'll probably flush the ARP and try a few other network tricks.

(Two days goes by...)

OK, I've spent the last two days trying to work around my issues. I'm pretty convinced it has to do with my network setup. First of all, I'm running Ruckus Unleashed (R610) WAPs (12 of them), all hardwired back to my switch (non-mesh). From what I've seen, Ruckus WAPs interfere with Multicast that I believe is necessary for discovery of the Sonos devices. However all my Sonos devices are hardwired, through a local hub and then over to my Ruckus (Brocade) ICX-7450-48 switch. Apparently this is another device that doesn't play well with Sonos / Multicast. I spent (way too much) time messing around through the management port on the switch trying to setup Multicast and IGMP on the switch, but in the end had to throw in the towel. I have also reserved IP addresses for my (13) Sonos devices, rebooted them all, and they are all nicely using their assigned addresses. But still, nothing is discovered in the app (OK, occasionally one Sonos is discovered). I even moved the Hubitat over to the hub where all the Sonos devices are connected, but no difference.

At wits end, I finally decided to get intimate with ChatGPT and attempted to modify the discovery code in the Sonos Advanced Controller app to draw from a list of fixed IP addresses instead of using the results of Discovery. But as I've learned over the past year, ChatGPT will always get you 75% of the way there and then just go round and round in circles until you have lost your voice yelling at it.

So at this point, after spending ~20 hours going back and forth with Julie (that's what I call ChatGPT), I quit! And all I really wanted was for a way to have button 3 on a Pico merge and unmerge two Sonos devices (so my wife could easily have the Great Room Sonos Beam play out the Kitchen Sonos).

Maybe someday I'll rip apart my network and figure out a way to put it all together where Discovery of Sonos devices can work within Hubitat. But then again, I love the network the way I have it setup.

Unfortunately my experiences probably don't help anyone else. Until I get it working, I'll continue to dream about someday getting Sonos Advanced Controller working with my setup.

Thanks for the help!

Marc

[ogiewon]

@mluck

Does anyone have any insight into using this app to queue TTS messages so that they don't interrupt or step on each other if they are issued in quick succession? Really struggling with this

Looks like the author is still working on getting queued TTS sorted out.

[Nearing Release] Sonos Advanced Controller

0.7.4 Out with only a tiny change, fixing 'MRVAT_ should be MRRC_' on resubscribeToMrRcEvents(). There's probably a fair number that have this already changed in their local copy, but at least anyone coming in new will get it with a working version. No other changes at the moment. Once I wrap up a few things on the Shelly Webhook/Websocket 'MQTT-free' drivers I've been working on for a bit here and get a release out on that, I'll be back over here to tighten up some code on Sonos Advanced, put …

[user5728]

Hello. Awesome at first but now no bueno. I went through the process of removing the default sonos integration prior to setting this one up and everything was good. Weeks later, the devices are no longer working (unresponsive). I really do not want to mess with the associated apps that include certain sonos speakers if I uninstall and reinstall. Any suggestions to get it responsive and more reliable?

[DGBQ]

@user5728

Hello. Awesome at first but now no bueno. I went through the process of removing the default sonos integration prior to setting this one up and everything was good. Weeks later, the devices are no longer working (unresponsive). I really do not want to mess with the associated apps that include certain sonos speakers if I uninstall and reinstall. Any suggestions to get it responsive and more reliable?

Troubleshooting Sonos Connectivity Issues

Without more details, it's difficult to pinpoint the exact cause of your issue. However, the key is to review your logs and identify what might be disrupting communication or connection.

Step 1: Assign Static IPs

Before doing anything else, ensure that all your Sonos players have static IPs—this can be set within your router. Once assigned, reboot all Sonos players and confirm they are working with the Sonos app.

Step 2: Check for Issues After Updates

Sometimes, Sonos updates can cause unexpected issues. While I can’t guarantee this will resolve your problem, the following steps are worth a try.

Step 3: Run the Sonos Advanced Controller in Hubitat

1. Open two instances of the Hubitat web app in a browser:

• One for Live Logs
• One for the Sonos Advanced Controller

2. In the Sonos Advanced Controller, select the Sonos Virtual Player Devices button and let it discover all your players.
3. Once the discovery process is complete, press Next (this may take some time).
4. In the Select Sonos field, if you see "X newly found primaries," you will need to re-add them.
5. Press Create Players and verify that every player is listed.
6. If any are missing, reselect them in the dropdown list, then proceed by clicking Next and finally Done.

Step 4: Monitor Logs for Errors

As you run the discovery process, keep an eye on the logs—any errors reported during this stage could provide clues to the issue.

Step 5: Test Playback

1. Open the Sonos app and try playing something, then stop playback.
2. Open a second Live Logs window and attempt to play Sonos through Hubitat.
3. If playback fails, check the logs for any errors or warnings that might point to the root cause.

Hopefully, these steps should help you identify and resolve any connection issues with Sonos in Hubitat.

[styxman]

None of my Sonos devices have anywhere near the correct IP address (found by converting the Device Network ID from hex). Im getting 55.249.78.248....should something like 192.168.1.xxx.

Any advice on getting this working?

Thanks

[DGBQ]

@styxman

None of my Sonos devices have anywhere near the correct IP address (found by converting the Device Network ID from hex). Im getting 55.249.78.248....should something like 192.168.1.xxx.

Any advice on getting this working?

Thanks

Hey there @styxman! It sounds like you’re encountering some puzzling IP address issues with your Sonos devices. Providing more detail will help the community determine how they should respond. Let’s break things down step by step:

1. What’s Your End Goal?

• Clarify Your Objective: Are you installing a new integration, running specific commands, or troubleshooting a network mapping issue? Knowing exactly what you’re trying to achieve will help pinpoint the best solution.

2. Log File Details

• Share the Logs: It would be really useful to see what you’re getting in the logs. Are there any error messages, warnings, or patterns that might suggest where the mismatch is coming from? Log details can offer valuable clues to diagnose the issue.

3. Static IP Addresses

• Set Static IPs: One of the most effective steps is to assign static IP addresses to your Sonos devices. With static IPs, you ensure that each player consistently falls within your expected range (like 192.168.1.xxx). This minimizes conflicts and makes troubleshooting a lot easier.
• Have You Tried It Yet? If you haven’t set static IPs on your router for your Sonos devices, it might be a good idea to start there.

4. Network Configuration Check

• Double-Check Your Subnets: Make sure that both your Hubitat hub and your Sonos players are on the same subnet. If they’re separated by different VLANs or subnets, network translation or routing issues might cause the devices to display unexpected IP addresses.

Next Steps:

• Clarify Your Goal: Let us know exactly what you’re aiming to do so that the community can offer targeted advice.
• Share Log Details: Any specific errors or entries from your logs will be helpful for diagnosing the issue.
• Consider Static IPs: If you haven’t done so already, assign static IP addresses to your Sonos devices to help prevent these kinds of issues.

I hope this points you in the right direction! Feel free to share more details or ask for further guidance—just keep in mind that the developer of this integration is on break for a while, so members of this forum try to help out as best they can.

[styxman]

Hi @DGBQ and thanks for the response. I already followed your i structions above, without success.

1. I'm just trying to get 1 of my Sonos Play:5s to work at the moment. Eventually i'll add others.
2. Heres the log for when i added the player from Sonos Advanced App.
   app:7132025-03-25 06:59:40.412 PM

info

Sonos Advanced Controller: Updating player info with latest info from discovery...

app:7132025-03-25 06:59:40.406 PM

info

Sonos Advanced Controller: Sonos Advanced Controller updated

app:7132025-03-25 06:59:37.524 PM

error

java.net.UnknownHostException: null: Name or service not known on line 946 (method appButtonHandler) (library dwinks.UtilitiesAndLoggingLibrary, line 26)

app:7132025-03-25 06:59:37.112 PM

info

Sonos Advanced Controller: Creating Sonos Advanced Player device for Bedroom

app:7132025-03-25 06:59:30.276 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.103:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.263 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.103:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.250 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.20:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.238 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.1:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.225 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.1:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.213 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.110:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.200 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.20:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.188 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.1:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.176 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.1:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.161 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.1:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.125 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.1:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.111 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.103:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.097 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.103:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.084 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.58:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.071 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.20:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.059 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.1:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.047 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.103:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.034 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.1:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.021 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.1:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:30.009 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.58:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:29.995 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.110:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:29.982 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.20:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:29.420 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.1:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:27.765 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.103:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:25.574 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.102:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:25.562 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.102:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:25.369 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.103:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:25.356 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.103:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:23.893 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.58:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:23.874 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.1:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:23.797 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.1:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

app:7132025-03-25 06:59:23.780 PM

info

Sonos Advanced Controller: Could not connect to: 192.168.1.58:1443. If this is a Sonos player, please report an issue. Note that RIGHT channel speakers on a stereo pair, subwoofers, or rear channel speakers this is expected. Only LEFT channel in stereo pairs (or Arc/Beam in a center + rear setup) will respond.

3. IP is static, Subnets not an issue.

Thanks for the help.

[DGBQ]

@styxman

I'm just trying to get 1 of my Sonos Play:5s to work at the moment. Eventually i'll add others.

Just a couple of thoughts—hopefully, other community members can chime in with suggestions to try. Otherwise, you may need to wait until @daniel.winks returns from his break.

1. Are You Using Sonos S1 or S2?

This integration was designed with Sonos S2 in mind, so if you're using S1, that could be a factor. I recall Daniel mentioning this in the past, but I’m not sure if a resolution was ever found. Since I’m running S2, I can’t personally test this, but hopefully, another community member using S1 can share their experience.

2. Does Your Sonos Play:5 Show Up in Discovery?

When you run a discovery scan, does your Play:5 appear? If not, it’s possible that UPnP is blocked by your router. This has been a known issue for some users, so you might want to check your router settings or search the forum for similar cases.

3. Are You Using UniFi Network Gear?

Some users with UniFi networking gear have run into issues with Sonos device discovery. Daniel has mentioned this before in the forum, though I’m not sure if a definitive fix was found. A forum search might reveal potential workarounds that others have tried. If you’re using UniFi, that could be something worth investigating.

If you followed my previous posts and this did not help hopefully, someone with a similar setup can share their experience and help troubleshoot.

[styxman]

Hi there....

1. All my Sonos products are S1. So that may be a factor, as you say. FWIW, the HE Sonos integration works correctly, but doesnt support grouping like SAC.
2. Yes, all the devices show up in discovery. The only oddity is that i gave a stereo pair that only shows up as 1 speaker, where in the HE integration both sepakers appear
3. I dont use a Unifi network.

I appreciate your time and help. Hopefully theres someone here that has managed to get S1 products working.

Thanks again.

[DGBQ]

Hey @styxman,

Just a few more thoughts.

@styxman

All my Sonos products are S1. So that may be a factor, as you say. FWIW, the HE Sonos integration works correctly, but doesn’t support grouping like SAC.

Yeah, I remember Daniel built this app using only S2, so that could definitely be a factor. Also, keep in mind the Hubitat version and the Sonos Advanced Controller (SAC) version are completely different beasts—they use entirely different frameworks and connection methods. If I recall correctly, HE’s integration is cloud-based, while SAC is local.

And I couldn't agree more—grouping is the best part along with using favorites! That’s why when Daniel started this project, I jumped right in to help test it. Oh, and by the way, you shouldn’t be running both versions at the same time, if you are. If I remember right, they can chew through a lot of system resources together.

@styxman

Yes, all the devices show up in discovery. The only oddity is that I have a stereo pair that only shows up as one speaker, whereas in the HE integration, both speakers appear.

Yep, that’s expected. In SAC, stereo pairs show up as a single player—same goes for surround sound setups. I have both, and honestly, I prefer it that way. It means you only have to manage one volume control instead of tweaking multiple ones and risking an accidental sound imbalance (because nothing says "immersion" like your left speaker whispering while your right one is screaming).

@styxman

I don’t use a Unifi network.

Well, that’s good news! One less thing to troubleshoot.

So, at this point, I think I may have jumped to the conclusion that you couldn’t discover any of your players—but it sounds (pun absolutely intended) like you can. My memory isn’t what it used to be, so help me out—what’s the exact issue you’re running into again?

[bertabcd1234]

@DGBQ

If I recall correctly, HE’s integration is cloud-based

This would be incorrect; Hubitat's integration uses the local UPnP API (unofficial but their only supported option appears to be the cloud API that new Sonos app users don't seem to love ).

[DGBQ]

@bertabcd1234

This would be incorrect; Hubitat's integration uses the local UPnP API (unofficial but their only supported option appears to be the cloud API that new Sonos app users don't seem to love ).

"Well, of course, everything looks bad if you remember it!" – Homer Simpson

You're right, I messed that up. Hubitat’s integration does use the local UPnP API. I was thinking about the officially supported options, which seem to be cloud-based. Thanks for the correction!

[styxman]

@DGBQ .... the issue for me is that SAC is assigning totally weird Ip.....55.249.78.248. Where is it getting that from??? Lol

I can change the IP, but it still doesnt play, so must be related to my devices being S1. Bummer.

Thanks again.

[DGBQ]

@styxman

@DGBQ .... the issue for me is that SAC is assigning totally weird Ip.....55.249.78.248. Where is it getting that from??? Lol

I can change the IP, but it still doesnt play, so must be related to my devices being S1. Bummer.

Thanks again.

That’s really interesting! I don’t remember Daniel mentioning that when I tested the app early in development. I’d like to explore this some more—how did you come to this conclusion, and where are you seeing the IP change?

[styxman]

I go through the discovery process in SAC, select one speaker and create the device. Under the Device Info tab, i looked at the Device Network ID, which i understand is the IP of the player in hex. The id is: B8E937F94EF8, which translates to 55.249.78.248. I then converted the correct IP into hex and put it in the Network ID and clicked save. Still nothing playing.

Take a look at the log file you resquested a few posts back. Whrn i installed the Play:5, I found it odd that it was try to connect to all these different devices...one was Roku, another was my Tv and numerous hits on my gateway and various other IPs. Doesnt seem right to me.

Thanks again.