Tried the volume manager rule again that was confirmed working. I’m finding that when the sonos stops and I run the rule manually it works however it won’t trigger rule machine automatically if I let the rule do its thing. Any ideas?
Using webCoRE, what is the proper command format to execute the speak command on a Group Device? I assumed it would be:
But that doesn't work and throws a 408 error.
ETA: It appears to be failing only on the Group Coordinator. It is playing elsewhere.
Bleh, more fallout from my attempt to trim down the device data section a bit. Guess I had even more code-reuse between the player devices and group devices than I thought. I'l just leave groupId, isGroupCoordinator, and groupCoordinatorId on the player devices data section. Makes things a lot simpler, at the expense of the tiniest bit extra load on HE.
0.3.22 out with fix for that.
Do we need to "initialize" player devices again after this patch?
After a fresh NEW install of Sonos Advanced Controller 3.22:
HPM View Apps and Drivers
- Sonos Advanced Controller
- Sonos Advanced Controller v0.3.22 (app)
- Sonos Advanced Battery Status v0.3.22 (driver)
- Sonos Advanced Group v0.3.22 (driver)
- Sonos Advanced Player v0.3.22 (driver)
- Sonos Advanced Snapshot v0.3.22 (driver)
I cannot get the Sonos Advanced Controller App to create the discovered virtual player devices.
After runnig discovery, when i select each discovered player in the enum checkbox, the selected players disappear, and create players does not create any.
I've got lots of errors at the moment, was on .18 and just updated to .22 and it's the same. I clicked Initialize on each device after update.
Pressing play gives me this
979 is the Sonos Advanced App, all buttons are raising errors
I only see this on the device
I've tried deleting a player and re-adding it but 'Create Players' isn't working. When you choose a player like this
It loses the selection when you click away
Ah, also mentioned above by @KurtSanders
Looking at the logs I seem to have 2 versions of the app running at the same time, both producing logs
I think I'm going to wipe everything, clear logs, and start from scratch
Update: After wiping everything I can't add devices as above
1 Like
Just the once. It’s only needed to add the new subscription.
1 Like
Looking into device creation first thing today.
2 Likes
New version on HPM.
OK, device creation should be fixed... try to fix it for one person, break it for others.
I think I'll leave a day or two between updates from here on out so I have enough time to see errors pop up on my C7. It was a relatively minor tweak to the device creation selection page that cause it to reset the selected items each time you selected one, making it impossible to select anything.
3 Likes
Thanks, mine works now. Re-installed everything and now have the 5 sids on each device. I did notice this in the logs initially though, before device creation
New release worked like a charm for device creation and groups! Nice!
Ah sorry, is this correct?
1 device did have sid3 initially, but all now just have 1,2,4,5
Should have 2, 3, 4, 5, and sometimes 1 if it's currently a coordinator (which is the case for a stand-alone player too).
3 is ZoneGroupTopology which for whatever reason seems to like to fail to subscribe occasionally, especially on my Sonos Roam. It almost always picks it up on the second attempt 1 minute later.
All have 5 now 
All seems to be working fine!
I did notice on device creation that debug logging was enabled by default btw
It's odd that initialize() would cause any excessive load. It's not doing anything on a newly created device:
Initialize() just calls configure(), which has a bunch of stuff to create child devices, but since those all default to off in the settings, it doesn't create them and those methods should just return super fast. secondaryConfiguration has some load to it, but it's called in a runIn specifically so configure() can complete pretty quickly.
I'll toss a quick if(createCrossfadeChildDevice) { ... } on each of those lines, so they spend even less time running. But really, configure() (on a new device where it's not making all these children) shouldn't take more than a millisecond or two to run.
There's a scheduled task to turn it off after 30 minutes on everything I write. It's part of my library code.
2 Likes
Feedback request:
Presently, the volume up/down and group volume up/down function thusly:
If set to 5%, each volume up press increases volume by 5%. So if volume is 10, it's 15 after. Next press it's 20. Simple, but I'm finding it not meeting my needs very well.
I've got one of these fantastic Ikea button controllers. With the default 5% setting, changing the volume with up/down doesn't really work that great. For 'moderate' levels it gives an OK amount of adjustment. But when listening at lower levels, 5% is way too much jump.
If I change the setting to 2% or something, then at lower levels it works better, but at higher levels I have to press the button multiple times to have a noticeable amount of change.
So I'm thinking of changing it to some sort of relative adjustment. My thought is, using 5% as an example, for levels 21-100, keep things the same, 5% per "volume up" press. For 11-20, halving the setting, rounded down. So for 5% it would do 2%. For 10% it would do 5%. Then for 0-10 quartering the setting, rounded down, with 1% as the minimum. So if it's set to 5%, each volume up/down between 1-10 would adjust it 1%. If you have it set to 10% it would do 2%.
I could also make it "5% more/less of current level" but that would mean most people would probably want to change away from the default setting of 5%. If it's based on a % of current level, then at a setting of 5% everything 1-20 would be 1% jumps, 21-40 would be 2%, 41-60 would be 3% and so on. I think that might be a bit too low of a change at higher volumes. So I'm leaning toward the above change.
I could also just toss on another setting toggle for "use lower % change for volume up/down at lower volume levels" and make it optional, too. So is there anyone here that actually like it being 5% across the 0-100 range, and would object to having it be 1% from 0-10, 2% from 11-20, and 5% above 20? I could make every last thing 'optional', but each thing that's optional adds clutter to the device settings.
I have the same controller and yes it's difficult to adjust at lower volume. I think your 2% between 0-20 and 5% between 21-100 would be good. Maybe both of those being a setting too so if people like it as-is they can set both to 5.
Ah, yeah, I could just add a "Volume up/down Adjust (0-10)" and "Volume up/down Adjust (11-20)", then everyone can set them as they see fit.
1 Like
