# \[APP\]\[Pro\] Sonos (LocalAPI) **URL:** \ **Category:** Apps\ **Tags:** app, homey-pro\ **Created:** [December 28, 2025, 12:48pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985 "2025-12-28T12:48:49Z")\ **Posts on this page:** 20\ **Page:** 5
**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\ **Post date:** [January 11, 2026, 9:04am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/83 "2026-01-11T09:04:25Z")
@xiutit > [@xiutit](#): > > What do you mean with this? If you change it in Homey it doesn’t update in the Sonos app? It sometimes takes a few minutes to update there. > [@xiutit](#): > > Is this still the case with v1.6.0? I think there is a limitation on the number of settings within a certain time, which may be a Sonos thing. Sometimes the switches are synced within a second, and sometimes they indeed take a few minutes (same switches). > [@xiutit](#): > > Is this still the case? Repeat and shuffle settings possible issue not reproducible anymore in v1.6.0 ---
**Author:** ![AlexRedwood](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/alexredwood/32/34032_2.png) [@AlexRedwood](https://community.homey.app/u/AlexRedwood)\ **Post date:** [January 11, 2026, 12:12pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/84 "2026-01-11T12:12:46Z")
App versie is ineens 1.3 en speakers werken niet meer op APP. Opnieuw installeren verandert niets. ---
**Author:** ![xiutit](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/xiutit/32/175860_2.png) [@xiutit](https://community.homey.app/u/xiutit)\ **Post date:** [January 11, 2026, 12:17pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/85 "2026-01-11T12:17:04Z")
This topic should stay in English. v1.3.0 is the Live version. To install v1.6.0 you have to use this link (add /test at the end of the live app): > **[Sonos (LocalAPI) | Homey](https://homey.app/nl-nl/app/nl.xiut.sonoslocal/Sonos-(LocalAPI)/test/)** > > Locally control your Sonos system ---
**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\ **Post date:** [January 11, 2026, 1:54pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/86 "2026-01-11T13:54:27Z")
It seems that when the artist name contains a hyphen (`-`) the artist name is split across the artist and track tags. See below the example of artist ‘Di-Rect’. Not sure whether this also applies when other special characters are used. ![IMG_2405.PNG](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/4/4436bd2bbf4acb2f715ab30bb744ecb0b60be1f0.jpeg) ---
**Author:** ![Geronimo206](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/geronimo206/32/29921_2.png) [@Geronimo206](https://community.homey.app/u/Geronimo206)\ **Post date:** [January 13, 2026, 12:00pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/87 "2026-01-13T12:00:42Z")
Hi @xiutit ! Slight warning up front: I’m really not sure how difficult this is to implement, so please don’t hate me for suggesting it 😅 . In trying to migrate to your app I came to the (admittedly very late) realisation that I’m missing a crucial feature from the older Homey app: group states for every speaker! See: ![Schermafbeelding 2026-01-13 om 12.19.45](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/3/f321691713bd807fbb8df330dfcacb5925c631d1.png) I am using this to dynamically determine pre-set “states” of where Sonos is playing exactly. For example: when the kids are asleep Sonos can only play downstairs, and a bunch of flows are adjusted based on that specific grouped state. Just to give you a sense of what this (sorry, it’s a mess) looks like in advanced flow, see: ![Schermafbeelding 2026-01-13 om 12.21.17](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/a/da1f571ff4a9500e123c4b95bb806883228c5219.jpeg) The groups I’m trying to determine trough the above flow currently are: - Downstairs - Downstairs + upstairs - Downstairs + outside - Downstairs + upstairs + outside I asked ChatGPT and he’s sure there is a way to read speaker grouped states in Home Assistant also, so I’m hopeful it’s at the very least “technically” possible: ![Schermafbeelding 2026-01-13 om 12.25.07](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/9/f9774f88c92e81b3846da229aa59dfe308008c1e.jpeg) Only thing I’m wondering is: what would be the best way to implement this? The older Homey app is a bit weird in that it does not show exactly what each speaker is grouped with, just that it is grouped with an amount of speakers (which makes me have to jump trough some hoops flow-wise). Home Assistant apparently show EXACTLY which speakers are grouped to which speaker. I’m just spewing out random ideas right now so bear with me but: in an ideal world your app could have some sort of “group function”, where you could predetermine groups based on what speakers should be in it (in the settings or something?), so that whenever the speakers are grouped in a certain way, a tag on the speakers (“grouped to Downstairs” for example?) would turn to “Yes”. This might be totally overkill but I’m just trying to think about the most user-friendly way to go about this. At the very least an implementation in line with the older Homey Sonos app would be needed for me to switch fully to your app 🤓 . I’d love to hear your feedback on this! ---
**Author:** ![xiutit](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/xiutit/32/175860_2.png) [@xiutit](https://community.homey.app/u/xiutit)\ **Post date:** [January 13, 2026, 12:13pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/88 "2026-01-13T12:13:01Z")
> [@SunBeech](#): > > It seems that when the artist name contains a hyphen (`-`) the artist name is split across the artist and track tags. That’s because those stations don’t provide separate artist and track information 😅 I’m currently splitting them by a hyphen, but I hadn’t considered this edge case yet. > [@Geronimo206](#): > > Slight warning up front: I’m really not sure how difficult this is to implement, so please don’t hate me for suggesting it 😅 . This information should be available, so I should be able to expose this as a sensor. I will look into this 🙂 ---
**Author:** ![Friedhofsblond](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/friedhofsblond/32/93838_2.png) [@Friedhofsblond](https://community.homey.app/u/Friedhofsblond)\ **Post date:** [January 13, 2026, 7:20pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/89 "2026-01-13T19:20:59Z")
Hi xiutit, I just stumbled across your app and was delighted to find it. I’m in the process of migrating my apps to the Homey Home Server (SHS). I’ve had a Sonos API server running on Debian for a while now. It’s the same Debian server where the Homey SHS is installed. My old Sonos API is running at: [http://192.168.115.29:5005/](http://192.168.115.29:5005/) Homey SHS is running at: [http://192.168.115.29:4859/](http://192.168.115.29:4859/) Will there be any problems if I install your Sonos app on the SHS? Currently, the Sonos AFlows are still running with a link on port 5005. Or would it be better to install your app only after I’ve also migrated the old AFlows to the SHS? Cheers ![Screenshot 2026-01-13 200913](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/9/791ba913ccc51c999aafb9474a8a3de2083670ea.png) ![Screenshot 2026-01-13 202242](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/2/a2472b11598522c126ecea9261f5139b5c5d2d70.png) ---
**Author:** ![xiutit](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/xiutit/32/175860_2.png) [@xiutit](https://community.homey.app/u/xiutit)\ **Post date:** [January 13, 2026, 7:36pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/90 "2026-01-13T19:36:58Z")
> [@Friedhofsblond](#): > > Will there be any problems if I install your Sonos app on the SHS? > Currently, the Sonos AFlows are still running with a link on port 5005. It should work just fine, but we’ve seen that Sonos speakers can get a bit “overwhelmed” when multiple apps are sending commands and requesting data at the same time. Ideally you’d end up using just one app, but for testing purposes this shouldn’t cause any issues. ---
**Author:** ![synnc](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/synnc/32/86011_2.png) [@synnc](https://community.homey.app/u/synnc)\ **Post date:** [January 14, 2026, 9:56am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/91 "2026-01-14T09:56:47Z")
![imagem](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/8/e8bf0e52836d1d9effccf776e9b8265c834a6667.jpeg) ![imagem](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/2/328ef190a6fabf77cb6672fd0fa29ae5a03bd9da.jpeg) Is it possible to remove the toggle selection and instead have a single panel with four buttons? I’d like it to look similar to the screen with two buttons, but showing four buttons and no selection box. ---
**Author:** ![Friedhofsblond](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/friedhofsblond/32/93838_2.png) [@Friedhofsblond](https://community.homey.app/u/Friedhofsblond)\ **Post date:** [January 14, 2026, 10:21am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/92 "2026-01-14T10:21:20Z")
Okay, when the time comes, I’ll stop the old API service. I miss the playlist feature. 😉 ---
**Author:** ![xiutit](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/xiutit/32/175860_2.png) [@xiutit](https://community.homey.app/u/xiutit)\ **Post date:** [January 14, 2026, 3:56pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/93 "2026-01-14T15:56:18Z")
> [@Geronimo206](#): > > The groups I’m trying to determine trough the above flow currently are: > > - Downstairs > - Downstairs + upstairs > - Downstairs + outside > - Downstairs + upstairs + outside In v1.7.0 I have added a sensor that shows the group members. Can you try it out? > [@Friedhofsblond](#): > > I miss the playlist feature. 😉 **Play (Playlist)** is added in v1.7.0 ---
**Author:** ![Friedhofsblond](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/friedhofsblond/32/93838_2.png) [@Friedhofsblond](https://community.homey.app/u/Friedhofsblond)\ **Post date:** [January 14, 2026, 5:04pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/94 "2026-01-14T17:04:39Z")
Oh, you’re fast! 👍🏻 😉 ---
**Author:** ![Michael\_Edholm](https://avatars.discourse-cdn.com/v4/letter/m/bc79bd/32.png) [@Michael\_Edholm](https://community.homey.app/u/Michael_Edholm)\ **Post date:** [January 14, 2026, 6:43pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/95 "2026-01-14T18:43:03Z")
Nothing big but if two speakers are group only the main will be detected by the discovery API. ---
**Author:** ![Geronimo206](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/geronimo206/32/29921_2.png) [@Geronimo206](https://community.homey.app/u/Geronimo206)\ **Post date:** [January 14, 2026, 10:46pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/96 "2026-01-14T22:46:28Z")
Wow, nice! First impressions: way more usable for my flows than the older Homey Sonos app, that’s for sure, thank you! I’m still building flows with it so I’ll let you know if I come across any issues. One thing that I already see now is that I’m missing a trigger, like you added for audio output format: ![Schermafbeelding 2026-01-14 om 23.40.20](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/2/c2e4379250ac569b45e85d1bb1af6d9878bf7d0b.png) Would be super handy for Sonos group related flows to be able to use a “Groepsleden gewijzigd” trigger (if at all possible to implement) to verify instantly if the speaker grouping has changed. Thanks again for the very fast updates! ---
**Author:** ![Joka](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@Joka](https://community.homey.app/u/Joka)\ **Post date:** [January 15, 2026, 10:13am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/97 "2026-01-15T10:13:14Z")
> [@\[APP\]\[Pro\] Sonos (LocalAPI)](https://community.homey.app/t/app-pro-sonos-localapi/147985/50): > > It is not possible to select a group coordinator in the group card. The field remains empty even if you enter the correct name of another player. I have to mention that I use only S1 Sonos devices. I would like to come back to this topic again. node-sonos should be able to handle grouping for S1 and S2, but you can’t mix them. Would it be possible to implement grouping for S1 devices as well? ---
**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\ **Post date:** [January 15, 2026, 2:54pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/98 "2026-01-15T14:54:02Z")
Is it possible to make dropdowns like the Sonos cards “Play Favorite” and “Play Playlist” dynamic, so that the list name is provided as a tag? Case: I’d like to use the Sonos app to select one of dozens of lists to play. The list name is provided via a webhook. ---
**Author:** ![synnc](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/synnc/32/86011_2.png) [@synnc](https://community.homey.app/u/synnc)\ **Post date:** [January 16, 2026, 9:29am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/99 "2026-01-16T09:29:31Z")
is this possible @xiutit ? Thank you 🙌 ---
**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\ **Post date:** [January 16, 2026, 11:22am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/100 "2026-01-16T11:22:25Z")
The speaker\_playing capability reacts differently on the Sonos Playbar than on the Era 100. In Homey Development Tools: - Playbar: set speaker\_playing from true to false; after 1 second of play, it returns to false. - Era 100: works as expected. This does work for the Playbar in the official Sonos app. Similar experience with the “play favorite” and “play playlist” cards. Has anyone had a similar experience with the Playbar, which is a bit older device, but doesn’t react the same as a newer Sonos device? How to solve (except “use the official app”)? ---
**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\ **Post date:** [January 16, 2026, 1:31pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/101 "2026-01-16T13:31:44Z")
> [@Amersfoort](#): > > Playbar: set speaker\_playing from true to false; after 1 second of play, it returns to false. Not sure whether I understand you correctly. I assume you are talking about this capability: ![Sonos speaker_playing](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/b/2b20037ccf29265530eb1f870467e63851b8c558.png) I also have ‘older’ Sonos speakers. When I start playing music on my system that includes the Playbar (via flowcard, speaker widget or the device tile) the value changes from `false` to `true` and v.v. when I pause playback. If I use the SET button in Developer Tools, and set it to `false` then playback pauses (and remains paused). If i then set it to `true`, then my Playbar starts playing again. I did note that, at least for radio stations, when I start playback the value changes to true, it then loads the steam, the value changes briefly to false and when the stream actually starts playing it changes back to true again. ---
**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\ **Post date:** [January 16, 2026, 3:12pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/103 "2026-01-16T15:12:08Z")
Yes, that’s what I mean. Thanks for testing. How to reproduce: Use the Sonos (LocalAPI) Play Favorite card in the advanced flow and start/execute this card. If Sonos was already playing another favorite, the new favorite will be loaded on the Playbar but not played. If Sonos wasn’t playing yet, the new favorite will be applied and played. Pausing works fine (in Developer Tools, as a card, and in the app player interface (under album art), but restarting playback afterward is impossible. [Previous page](https://community.homey.app/t/app-pro-sonos-localapi/147985.md?page=4) [Next page](https://community.homey.app/t/app-pro-sonos-localapi/147985.md?page=6)