# \[APP\]\[Pro\] Sonos (LocalAPI)

**URL:** <https://community.homey.app/t/app-pro-sonos-localapi/147985>\
**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:** 13

<div class="post-metadata">

**Author:** ![John\_William\_Brekke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_william_brekke/32/111887_2.png) [@John\_William\_Brekke](https://community.homey.app/u/John_William_Brekke)\
**Post date:** [May 16, 2026, 12:00pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/247 "2026-05-16T12:00:37Z")

</div>

Hmm, i don’t know yet. But would be cool to do something when the song is like 50% into the song. Or at X seconds. Also i like having all data in 1 place which your app is already good at! So adding these 3 as sensors, tags and flow cards would make your app much better.

---

<div class="post-metadata">

**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\
**Post date:** [May 16, 2026, 2:52pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/248 "2026-05-16T14:52:03Z")

</div>

> [@xiutit](#):
>
> Seeking flow card is now available in V2.2.0.

Thank you for the new Seeking card!

> [@xiutit](#):
>
> That data is already available and visible in the developer tools. What would you want to do with them? I could add them as a sensor.

I have created an extensive media player dashboard using your great Sonos app in combination with another very nice Homey app [Dashboard Studio](https://community.homey.app/t/app-pro-new-dashboard-studio-a-completely-free-form-dashboard-designer/151169).

I managed to display the lyrics at the right moment while Sonos is playing a Spotify song. However, it is annoying that the speaker\_position functionality updates every 15 seconds if you want to display the lyrics at the right moment.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/b/4b2a73657a8ea7976da3cda801024dd21feca304.jpeg)

Would it also be possible to jump to a specific number of seconds within the song, rather than using plus or minus x seconds?

---

<div class="post-metadata">

**Author:** ![John\_William\_Brekke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_william_brekke/32/111887_2.png) [@John\_William\_Brekke](https://community.homey.app/u/John_William_Brekke)\
**Post date:** [May 16, 2026, 7:25pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/249 "2026-05-16T19:25:21Z")

</div>

In addition to this request, could you take a look at the playing state not changing correctly? My Move 2 is playing, but it states as paused from your app. Song, artist and album still changes. But the playing state stays on paused, it does get fixed when restarting the app, but it has happened multiple times. Could you take a look at it?

16344584-bb90-49ae-8f37-1f6ead344e6d

---

<div class="post-metadata">

**Author:** ![LeonK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/leonk/32/121679_2.png) [@LeonK](https://community.homey.app/u/LeonK)\
**Post date:** [May 17, 2026, 7:46pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/250 "2026-05-17T19:46:17Z")

</div>

Audio books do indeed work now. One small thing I noticed is that when building the flow populating the [favorite] dropdown/selector occasionally stays empty. After a while it shows a [time out exception]. That exception persists. Only way to fix it is to refresh the flow page in the browser.

But, once configured, it works

---

<div class="post-metadata">

**Author:** ![Terry\_Hawkins](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/terry_hawkins/32/120934_2.png) [@Terry\_Hawkins](https://community.homey.app/u/Terry_Hawkins)\
**Post date:** [May 21, 2026, 10:27pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/251 "2026-05-21T22:27:10Z")

</div>

I have 4 Sonos Era 100s in my house which I’ve just added to homey.

3 of them show the icon which look like the Era, but one has an icon which just says sonos. Any idea why and any way to change it?

Also, any chance for an icon for the Sonos Play?

---

<div class="post-metadata">

**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:** [May 25, 2026, 3:33pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/252 "2026-05-25T15:33:47Z")

</div>

> [@xiutit](#):
>
> > [@SunBeech](#):
> >
> > - Is it possible to change the order of favorites?
> > - Is is possible to select only a specific set of favorites?
> 
> In v2.1.0 I have tried to add support for this, although there are some limitations in what the settings page currently allows.
> 
> I have added 12 configurable “slots” where you can select your Sonos Favorites. If all slots are left empty, the widget will show all favorites as before. Once you select favorites in one or more slots, the widget will only show those selected favorites, in the order you configured them.

Nice solution!

I did note that the favorites widget shows an error while the Sonos system is not powered on.

 ![IMG_2621.PNG](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/2/f2377abf6c6a1a134b039ba095201047eaf51413.jpeg)

Would be nice if the error description could be replaced by a more user-friendly text (e.g. “Favorites currently not available; turn on your Sonos system.”). Or, better: keep displaying the last know set of (configured) favorites (maybe in a dimmed format), but disable the tap action.

---

<div class="post-metadata">

**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:** [May 26, 2026, 9:07am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/253 "2026-05-26T09:07:56Z")

</div>

@xiutit: You recently added two flowcards regarding the Autoplay function on soundbars.

- One that enables or disables this option altogether:  
 ![Sonos TV Autoplay](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/c/2c4ae7b268caf5139c736fc5543575ad4336e814.png)
- One that enables or disables the ungrouping of speakers on Autoplay, which is a sub option of the prior one:  
 ![Sonos Ungroup on TV Autoplay](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/c/dcd57cb95c4b10b0d6a5f3df99cf822e8707cd0d.png)

The overall flowcard works just fine: Autoplay is enabled/disabled instantly when commanded via the respective flowcard: the change is reflected in the Sonos mobile app.

I am having issues with the second flowcard for enabling ungrouping of speakers on Autoplay. When using this flowcard to enable the said option, nothing seems to happen. The option is not being enabled; it stays disabled when checking in the Sonos mobile app.

Some further context. I have two flows:

- One that disables Autoplay. Sonos then also automatically disables the ungrouping option. So the flow only uses the first flowcard (`Set TV Autoplay to No`), which results in both option being disabled.
- One that enables Autoplay. Sonos does not automatically re-enable the ungrouping option. So I first use the first flowcard (`Set TV Autoplay to Yes`) and then the second one to enable the ungrouping option (`Set ungroup on TV Autoplay to Yes`).

As indicated, the second command does not seems to be processed by my Playbar. The flowcard does not result in an error (so it seems to have bee executed succesfully).

I first thought that I might have to wait a few seconds between running both commands, but to no avail.

If I manually run the `Set ungroup on TV Autoplay to Yes` flowcard then after several attempts the option is enabled. So it seems that the flowcard is able to send the command successfully at some time.

Any idea what could be causing this behavior and how to tackle it?

---

<div class="post-metadata">

**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:** [May 27, 2026, 10:36am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/254 "2026-05-27T10:36:39Z")

</div>

In V2.3.0 the app will now verify the setting after sending the command and retry it a few times if Sonos did not apply it yet. If it still fails, the flow will return an error instead of silently reporting success.

Also improved the widget offline handling. It will now dim and doesn’t respond to taps when the speaker is unavailable.

---

<div class="post-metadata">

**Author:** ![John\_William\_Brekke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_william_brekke/32/111887_2.png) [@John\_William\_Brekke](https://community.homey.app/u/John_William_Brekke)\
**Post date:** [May 27, 2026, 10:40am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/255 "2026-05-27T10:40:24Z")

</div>

Hi, could you implement duration (seconds), progress (%) and progress (seconds) as i mentioned? I sometimes find 1 part of the song too loud or too quiet. For example when progress (%) is at 50% then set volume to 75%. Also sometimes playing state shows wrong, for example: Move 2 playing but Sonos LocalAPI says it isn’t. Restarting the app fixes it.

---

<div class="post-metadata">

**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:** [May 27, 2026, 10:43am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/256 "2026-05-27T10:43:07Z")

</div>

This was already implemented but wasn’t in the live version yet.

Now v2.3.0 is live so that should make this available to everyone.

---

<div class="post-metadata">

**Author:** ![John\_William\_Brekke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_william_brekke/32/111887_2.png) [@John\_William\_Brekke](https://community.homey.app/u/John_William_Brekke)\
**Post date:** [May 27, 2026, 10:46am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/257 "2026-05-27T10:46:24Z")

</div>

Oh! I didn’t notice, thank you! I see them in tags, could you also put them in as sensors here?

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/f/3f7a25e872e349b5721b70eb73dbc09e650ca573.png)

Would be amazing! (and as **WHEN** cards?)

---

<div class="post-metadata">

**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:** [May 27, 2026, 10:54am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/258 "2026-05-27T10:54:44Z")

</div>

They should be there. Are you running v2.3.0?

> **[Sonos (LocalAPI) | Homey](https://homey.app/nl-nl/app/nl.xiut.sonoslocal/Sonos-(LocalAPI)/)**
>
> Locally control your Sonos system

---

<div class="post-metadata">

**Author:** ![John\_William\_Brekke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_william_brekke/32/111887_2.png) [@John\_William\_Brekke](https://community.homey.app/u/John_William_Brekke)\
**Post date:** [May 27, 2026, 10:55am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/259 "2026-05-27T10:55:26Z")

</div>

Yes, i am. I can try restarting the app? If not, then i might have to readd devices? (i’ll try installing again just to be safe)

---

<div class="post-metadata">

**Author:** ![John\_William\_Brekke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_william_brekke/32/111887_2.png) [@John\_William\_Brekke](https://community.homey.app/u/John_William_Brekke)\
**Post date:** [May 27, 2026, 10:57am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/260 "2026-05-27T10:57:15Z")

</div>

I reinstalled the app and found them! Thank you for this amazing app 😁 (also how often do the values update?)

---

<div class="post-metadata">

**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:** [May 27, 2026, 11:07am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/261 "2026-05-27T11:07:08Z")

</div>

For now, once every 15 seconds. I’m considering implementing some internal timer which would make it possible to update every second without having to poll the speakers every second, but that requires some work.

---

<div class="post-metadata">

**Author:** ![John\_William\_Brekke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_william_brekke/32/111887_2.png) [@John\_William\_Brekke](https://community.homey.app/u/John_William_Brekke)\
**Post date:** [May 27, 2026, 11:08am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/262 "2026-05-27T11:08:39Z")

</div>

Alright, thanks! Did you add **WHEN** cards for the duration and progress (both % and seconds)? I know i can make a workaround to do it myself, but it would be better in your app. I’m not sure if you did add it or not as i can’t see it.

---

<div class="post-metadata">

**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:** [May 27, 2026, 11:23am UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/263 "2026-05-27T11:23:07Z")

</div>

No, these are not yet implemented. Will add them to the wishlist.

---

<div class="post-metadata">

**Author:** ![BMT](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bmt/32/121140_2.png) [@BMT](https://community.homey.app/u/BMT)\
**Post date:** [May 28, 2026, 8:41pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/264 "2026-05-28T20:41:27Z")

</div>

Hello Xiutit, thanks for the app. I was wondering if automatic IP detection and update is also on your wishlist? Greetz!

---

<div class="post-metadata">

**Author:** ![John\_William\_Brekke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_william_brekke/32/111887_2.png) [@John\_William\_Brekke](https://community.homey.app/u/John_William_Brekke)\
**Post date:** [May 28, 2026, 8:42pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/265 "2026-05-28T20:42:08Z")

</div>

Automatic IP detection is already there.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/f/8f1e2a05229a8b09ba1ae300997617c094f7c3b4.png)

(But for surround speakers it’s manual)

---

<div class="post-metadata">

**Author:** ![BMT](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bmt/32/121140_2.png) [@BMT](https://community.homey.app/u/BMT)\
**Post date:** [May 29, 2026, 2:58pm UTC](https://community.homey.app/t/app-pro-sonos-localapi/147985/266 "2026-05-29T14:58:29Z")

</div>

Thx for your feedback. After a reboot of my modem, I lost connection and I had to update all IP’s manually to restore. Is it possible detection happens only when installing, but if IP changes afterwards you need to update manually?

[Previous page](https://community.homey.app/t/app-pro-sonos-localapi/147985.md?page=12)

[Next page](https://community.homey.app/t/app-pro-sonos-localapi/147985.md?page=14)
