# Official Sonos app gave up, after provider change

**URL:** <https://community.homey.app/t/official-sonos-app-gave-up-after-provider-change/154201>\
**Category:** Apps\
**Tags:** sonos\
**Created:** [April 25, 2026, 8:58pm UTC](https://community.homey.app/t/official-sonos-app-gave-up-after-provider-change/154201 "2026-04-25T20:58:40Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ralf\_Huelsmann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ralf_huelsmann/32/159889_2.png) [@Ralf\_Huelsmann](https://community.homey.app/u/Ralf_Huelsmann)\
**Post date:** [April 25, 2026, 8:58pm UTC](https://community.homey.app/t/official-sonos-app-gave-up-after-provider-change/154201/1 "2026-04-25T20:58:40Z")

</div>

Hi there,

I was using the official sonos app with no trouble.

After changing myp ISP and by that my Sonos configuration, my sonos App and thd the Sonos WebUI work great again.

Homey however gave up (can´t find devices / groups).  
Repair process with no error, but does not solve the problem.  
Restart of app and/or Homey does not do anything, as well.  
Homey and Sonos in same IP Subnet (now) - while I guess this is irrelavant, becaus I expect the official (in contrast to the community) app, to make use of a Sonos cloud API.

Any better way to repair?

Cheers,  
Ralf

---

<div class="post-metadata">

**Author:** ![Patrick\_Van\_Deursen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/patrick_van_deursen/32/56539_2.png) [@Patrick\_Van\_Deursen](https://community.homey.app/u/Patrick_Van_Deursen)\
**Post date:** [April 26, 2026, 9:22am UTC](https://community.homey.app/t/official-sonos-app-gave-up-after-provider-change/154201/2 "2026-04-26T09:22:08Z")

</div>

In my case the IP addresses changed (though some still had the same) and I needed to re-add all the sonos unit, and rebuild all the flows…

---

<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:** [April 26, 2026, 10:19am UTC](https://community.homey.app/t/official-sonos-app-gave-up-after-provider-change/154201/3 "2026-04-26T10:19:38Z")

</div>

> [@Patrick\_Van\_Deursen](#):
>
> rebuild all the flows

For future reference, assuming you are not using Homey Cloud, to make that somewhat less of a burden:

- Before you delete the non-functional Sonos devices, open the [Homey Developer Tools](https://tools.developer.homey.app/), go to the Devices section and note/write down the Device ID of each Sonos speaker;
- After removing and re-pairing the devices, the Sonos speakers will have a new device ID, rendering your flows non-functional;
- Replace the new IDs with the prior one by using this script provided and explained in this topic: [[HOW-TO][Pro][Cloud] - Tool to FIX (advanced) flows after removing and re-adding devices](https://community.homey.app/t/how-to-pro-cloud-tool-to-fix-advanced-flows-after-removing-and-re-adding-devices/65018) . After updating all IDs your existing flow should work again.

---

<div class="post-metadata">

**Author:** ![Ralf\_Huelsmann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ralf_huelsmann/32/159889_2.png) [@Ralf\_Huelsmann](https://community.homey.app/u/Ralf_Huelsmann)\
**Post date:** [May 4, 2026, 7:23pm UTC](https://community.homey.app/t/official-sonos-app-gave-up-after-provider-change/154201/4 "2026-05-04T19:23:53Z")

</div>

That would be a horrible downgrade from the Magenta Home I used before.  
Devices have unique ID´s, e.g. based on MAC etc. I would assume re-pairing. 🙂  
However, thanks for the feedback. Did prevent me from to fast steps. 😉

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [May 4, 2026, 7:49pm UTC](https://community.homey.app/t/official-sonos-app-gave-up-after-provider-change/154201/5 "2026-05-04T19:49:09Z")

</div>

The Sonos app communicates via the cloud, so this means IP changes aren’t relevant here.

Did you reset your Sonos device itself? In that case, the ID might have changed, which means that you do need to remove and re-pair the device with Homey.

---

<div class="post-metadata">

**Author:** ![Ralf\_Huelsmann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ralf_huelsmann/32/159889_2.png) [@Ralf\_Huelsmann](https://community.homey.app/u/Ralf_Huelsmann)\
**Post date:** [May 4, 2026, 8:29pm UTC](https://community.homey.app/t/official-sonos-app-gave-up-after-provider-change/154201/6 "2026-05-04T20:29:05Z")

</div>

Will check at the weekend.

Thanks.

---

<div class="post-metadata">

**Author:** ![Ralf\_Huelsmann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ralf_huelsmann/32/159889_2.png) [@Ralf\_Huelsmann](https://community.homey.app/u/Ralf_Huelsmann)\
**Post date:** [May 16, 2026, 9:51pm UTC](https://community.homey.app/t/official-sonos-app-gave-up-after-provider-change/154201/7 "2026-05-16T21:51:43Z")

</div>

I get the approach.  
Pretty sure (you never know) I did follow the rules.  
No errors (..request took xy ms).

No success.  
Homey Pro (2026)  
Version 13.1.5

However, maybe a Version specific thing.

Scrolling in the feed, I saw [[APP][Pro]Flow Converter - Apps - Homey Community Forum](https://community.homey.app/t/app-pro-flow-converter/154906) - which did it with not trouble.

Can only thank both authors and @smarthomesven for the hint.

Cheers,  
Ralf
