# Issue Zwave migration Homey Pro 2019 to 2026 **URL:** \ **Category:** Questions & Help\ **Tags:** z-wave, homey-pro\ **Created:** [February 16, 2026, 12:59pm UTC](https://community.homey.app/t/issue-zwave-migration-homey-pro-2019-to-2026/151202 "2026-02-16T12:59:37Z")\ **Posts on this page:** 1\ **Showing post:** 9
**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:** [February 18, 2026, 8:21pm UTC](https://community.homey.app/t/issue-zwave-migration-homey-pro-2019-to-2026/151202/9 "2026-02-18T20:21:55Z")
If you can still gather the current device IDs of your Z-Wave devices, then there is an alternative that is less time consuming. After resetting your Z-Wave network and re-pairing the devices, your flows that contain Z-Wave devices will be broken, but there is a fix. This topic describes how you can update the old device references with the new ones based on an automated script: [[HOW-TO][Pro][Cloud] - Tool to FIX (advanced) flows after removing and re-adding devices - #246 by martijnpoppen](https://community.homey.app/t/how-to-pro-cloud-tool-to-fix-advanced-flows-after-removing-and-re-adding-devices/65018/246). You would need to gather all the current device ID’s (either on your old Homey or your new one based on a restored backup) and the new ones (on the new Homey, after re-pairing every device). This still requires manual effort, but it’s better than starting from scratch all together. --- _[View the full topic](https://community.homey.app/t/issue-zwave-migration-homey-pro-2019-to-2026/151202)._