I have not observed that but I only open the Sonos app to make favorites.
I use my MagicCube to control my Sonos and play/stop my favorite stations and control volume
I finally removed the Sonos App from HE. Now I have a virtual button which sends an HTTP GET http://IP_address:5005/pauseall and that stops things. I'm really loving the Node API solution. Well done.
Excuse my ignorance here but to run the "node-sonos-http-api" server you need a separate device to host it correct? Like a RSPi connected to the network somewhere?
Apologies for reviving this thread, but didn't want to start a new one since there's a lot of info here that's relevant to what I'm trying to do. Also, the question isn't entirely about HE, but I gather some people in this thread may have gone through a similar setup and be able to help me.
I have managed to get the sonos http api working thanks to the great info and tips in this thread.
I am now wanting to host that node.js server in a Synology NAS, for convenience. I have found versions of that api wrapped on a docker image, and it is working so far, but I have no idea where to place the presets and setting files when using a docker image.
I see I can define and mount volumes in the Synology docker app, but not sure what my mount point should be so that the sonos api can find them.
Cool, I'm going to follow your posts about NAS/docker configuration, because I have been considering moving to docker from my nodejs installation on a vanilla Raspberry Pi OS installation.
In case it is useful to anyone else, I just posted by Sonos node-sonos-http-api drivers here and added them to my HPM repo.
These drivers give a lightweight abstraction of grouping/ungrouping and album or track art for display on dashboards. They also give the ability to create custom commands for the node-sonos-http-api and expose them through numbered button pushes. I found this easier than assembling a bunch of HTTP queries in RM rules and other virtual devices.
I guess I'm not going to hold my breath for native support of Sonos groups, since this feature request has been pending for quite some time. Looks like I'll have to go the node.js route. Can somebody inform me whether it can do what I want though? I want to be able to dynamically choose how to group sonos speakers, on the fly, just like in the sonos mobile app (or spotify app). So, I come home, press play on my dashboard, and then use my dashboard to choose which speakers to group for playing that. Doable with the node.js solution or can you only set more or less static groups?
Dunno about node.js but you can do that in Node Red. I do it now. I use node-red-contrib-sonos-plus and this my Node Red dashboard. It's pretty simple, as I've just been forcibly removed due cancellation from Google play music and transitioning to Amazon streaming.
There are join and leave commands. With join, you also supply the name of the zone to join. If you specify yourself, it's a noop (which simplifies some logic). For an existing group, you can use the name of any member in the group. Leave is just leave, and the rest of the group status intact regardless of whether you were the first member or not.
Yes, you can do that with Jishi's Node.js app for Sonos... but it's all REST requests, so you'll have to script them together into the routines you want.