# \[FeatureRequest\] Replace a device **URL:** \ **Category:** Ideas & Suggestions\ **Tags:** flow, featurerequest\ **Created:** [May 20, 2024, 5:18pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185 "2024-05-20T17:18:05Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![macfreek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/macfreek/32/176862_2.png) [@macfreek](https://community.homey.app/u/macfreek)\ **Post date:** [May 20, 2024, 5:18pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/1 "2024-05-20T17:18:05Z")
In the (almost) 6 years I own a Homey, one of the most tedious activities is replacing a device with a new device of the same type. This happens rather frequently, especially for some brands (Quibino, I’m looking at you!). It would be awesome if there was a feature to replace a device, or replace all flows and variables from one device (which may not longer be responding, and perhaps is not even present anymore in the device list), with another device that is either to be added, or is already added, but does not yet have any flows attached. ---
**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\ **Post date:** [May 20, 2024, 5:25pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/2 "2024-05-20T17:25:22Z")
Agree, something like [[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) but just in the WebApp or Mobile app with device Selection (also for removed devices with Cards in flows.) Send Martijn a Cake! 🎂 ---
**Author:** ![Rrrr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rrrr/32/629_2.png) [@Rrrr](https://community.homey.app/u/Rrrr)\ **Post date:** [May 20, 2024, 5:47pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/3 "2024-05-20T17:47:33Z")
Sorry that’s way too technical for me. I prefer to design flows in a way that devices don’t / hardly need to be replaced. Virtual devices in [device capabilities](https://homey.app/en-us/app/nl.qluster-it.DeviceCapabilities/Device-Capabilities/) goes a long way. Use zones (activities, lights). Maybe \< groups \> in certain places (still requires some replacing) ---
**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\ **Post date:** [May 20, 2024, 8:07pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/4 "2024-05-20T20:07:21Z")
Perhaps you should take a look at the script and thread @Dijker mentioned. The device ID can also be found at [Homey Developer Tools](https://tools.developer.homey.app/tools/devices). From there on it is not very much more than adding the old and new device ID in the script, run under [Homey Developer Tools](https://tools.developer.homey.app/tools/api-playground) The script in the first post of the link @Dijker mentioned has been constantly updated, so don’t get afarid of all the posts following the first post. 😉 I agree that the how-to in the thread is a bit “clogged”, but once you get the hang of it it can save you a lot of time and effort! 🙂 ---
**Author:** ![Helene](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/helene/32/110169_2.png) [@Helene](https://community.homey.app/u/Helene)\ **Post date:** [August 1, 2024, 7:55am UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/5 "2024-08-01T07:55:54Z")
I would like the possibility to exchange units, for example if a unit breaks down, and in the process adopt all connections in flows ---
**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\ **Post date:** [August 1, 2024, 8:14am UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/6 "2024-08-01T08:14:26Z")
Good point, I would say not only in the flows but also keeping the insights. For Flows there is a workaround with a Script to fix them after you added a new device . For fe zigbee devices that loose their connection there is a workaround to repair them by adding it and restarting the Homey App. But I want to make this a FeatureRequest but see it is already. Therefore moved to [[FeatureRequest] Replace a device](https://community.homey.app/t/featurerequest-replace-a-device/110185) ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [August 1, 2024, 3:11pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/7 "2024-08-01T15:11:47Z")
I’d like to point out, for contact and motion sensors it’s already in place, if you solely use “Zone is active” and “Zone is inactive” in the flows for the zones the sensors are in. You can add, replace, remove sensors (not the last one of course) from zones, without having to fix flows. Brands and models are redeemable. ---
**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\ **Post date:** [August 1, 2024, 5:14pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/8 "2024-08-01T17:14:34Z")
> [@Peter\_Kawa](#): > > for contact and motion sensors it’s already in place, if you solely use “Zone is active” and “Zone is inactive” in the flows for the zones the sensors No it is not in place for contract and motion sensors but icm zone activity you dont need it… Still the device history ( insights ) are lost and there are plenty usecases even icm zone activity where you also use fe contractsensors in flows. The request for replacing devices is just a valid feature request. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [August 1, 2024, 6:53pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/10 "2024-08-01T18:53:57Z")
Noooo I certainly did not mean, and I wasn’t saying at all it is not a valid request. Because contact and motion sensors are just a very small part of everything you can connect with Homey. ---
**Author:** ![Raita\_Kallio](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/raita_kallio/32/113863_2.png) [@Raita\_Kallio](https://community.homey.app/u/Raita_Kallio)\ **Post date:** [January 16, 2026, 10:24am UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/11 "2026-01-16T10:24:38Z")
I’d like to revive this older thread, as the need for a proper _ **device replacement** _ feature in Homey has become even more relevant than before. Currently, when a device needs to be replaced (for example due to hardware failure), the workflow is very manual: - Add the new device to Homey - Then replace it **one by one** in Groups, Flows, Advanced Flows, Dashboards, Modes, etc. In larger setups this quickly becomes very time‑consuming and error‑prone, especially when the device is used across many automations and views. With **Thread becoming a major successor to Zigbee** , this issue is only going to grow. We already see this transition happening with vendors like **IKEA** , where new product lines are Thread‑based instead of Zigbee. Building a stable Thread mesh often requires replacing multiple devices at once to achieve sufficient coverage and routing quality. Using the current replacement process in these scenarios is extremely tedious. ### Suggested solution A simple, clear system-level feature such as: 1. **“Replace device”** 2. **Select the device to be replaced** 3. **Select the new device that should take its place** 4. Homey automatically swaps the device in **all locations** where the original device was used (Flows, Advanced Flows, Groups, Dashboards, Modes, etc.) This would greatly reduce migration effort, minimize human error and encourage users to modernize their networks (Thread adoption) I believe this would be a hugely valuable quality‑of‑life improvement and increasingly essential as device churn grows with Thread-based ecosystems. ---
**Author:** ![PoJa84](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/poja84/32/114582_2.png) [@PoJa84](https://community.homey.app/u/PoJa84)\ **Post date:** [March 3, 2026, 8:18am UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/12 "2026-03-03T08:18:17Z")
I don’t see a ‘upvote’ button, so count this as my upvote. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [March 3, 2026, 5:53pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/13 "2026-03-03T17:53:01Z")
Ticking the ❤ is the usual upvote way > ![Screenshot_20260303_185157_Ecosia](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/a/1ad638c57fdb11fe21bb933e586e0bb64959fee8.jpeg) ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [March 3, 2026, 5:58pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/14 "2026-03-03T17:58:55Z")
> [@Raita\_Kallio](#): > > Then replace it **one by one** in … Flows, Advanced Flows, … 100% Agreed to the fact an onboard “replace tool” should be available, but where would Homey be without the community; Here’s a brilliant script to fix your flows dead easy: > [@\[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): > > rotating_lightwarning Use at own risk! warning rotating_light If you have a broken device which you want to replace or you have to fix flows for your device I made a script which can help with this. Instructions: Device ID you would like to update - - Go to the Homey web app - Devices - Right click on the device to show context menu - Hold down Alt / option key on keyboard - Select “Copy ID”. Write down the Device ID Remove the Device Re-add the Device Get the Device ID of… And in case of zone activating sensors: when you use zone activity in flows, you can replace sensors, add, or even remove surplus sensors without having to fix flows. ---
**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\ **Post date:** [March 3, 2026, 9:54pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/15 "2026-03-03T21:54:51Z")
There seems to be some movement on this, if I am interpreting the latest changelog correctly: ![IMG_1042](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/d/2d7ee23d09be7bffbd771d1d81bccc33ab5d8a14.jpeg) ---
**Author:** ![Raita\_Kallio](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/raita_kallio/32/113863_2.png) [@Raita\_Kallio](https://community.homey.app/u/Raita_Kallio)\ **Post date:** [March 9, 2026, 5:05pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/16 "2026-03-09T17:05:38Z")
Well, demand for same model and manufacturer is quite limiting. Especially now when thread devices will start replacing zigbee devices. I landed to Homey from Hubitat, and it didn’t have such limitations. Just select a replacement device and that’s it, if the new device just did same job than the old one. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [March 9, 2026, 7:17pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/17 "2026-03-09T19:17:16Z")
How does Thread relate to zigbee? Who is replacing zigbee devices by Thread? Or is that just your assumption? I mean, you can’t replace a zigbee device by a Matter-over-Thread device without starting from scratch ---
**Author:** ![macfreek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/macfreek/32/176862_2.png) [@macfreek](https://community.homey.app/u/macfreek)\ **Post date:** [August 18, 2026, 3:37pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/18 "2026-08-18T15:37:48Z")
How many people are specifically replacing a Zigbee device by a Thread device, I do not know. I guess at least 1: @Raita_Kallio 🙂. That said, it is not uncommon to replace one device with the same type of device from a different manufacturer. I’ve done it at least 10 times now. For example, I have replaced broken some onoff switches by onoff switches from a different brand, simply because the original device is no longer being made. And yes, in some cases it used a different protocol (e.g. from Z-Wave to Zigbee). And the point of this feature request is that this process should NOT be “you have to start from scratch”, but a smooth process that copies/replaces the name and flows of the old device to the new device. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [August 18, 2026, 6:51pm UTC](https://community.homey.app/t/featurerequest-replace-a-device/110185/19 "2026-08-18T18:51:06Z")
The script I mentioned before is now available as app + multiple improvements. It’s quite easy to use, “dry runs” are possible. and replacing an ‘old’ Y protocol device with a new Z protocol device is no problem; all related flows get repaired, and afterwards you can simply remove the ‘old’ device: > [@\[APP\]\[Pro\]Flow Converter](https://community.homey.app/t/app-pro-flow-converter/154906): > > Hi everyone, First.. A special thank to [Martijn Poppen](https://homey.app/en-no/apps/author/5e2daad2e3e0da0ca754b6a8/page/0/)! Then to repeat what he said in his [API Playground script](https://community.homey.app/t/how-to-pro-cloud-tool-to-fix-advanced-flows-after-removing-and-re-adding-devices/65018) that made this app possible. rotating_light warning Use at own risk! warning rotating_light I built Flow Converter to solve a common Homey headache: after replacing or re-pairing a device, Flows and Advanced Flows can still point to the old device ID and stop working. This app helps you remap old references to the new device safely, directly from the app settings page, so …