# Homey pro 2019-2023 migration failing

**URL:** <https://community.homey.app/t/homey-pro-2019-2023-migration-failing/143782>\
**Category:** Questions & Help\
**Tags:** z-wave, homey-pro, homey-pro-2023, homey-pro-2016-19\
**Created:** [October 5, 2025, 9:09am UTC](https://community.homey.app/t/homey-pro-2019-2023-migration-failing/143782 "2025-10-05T09:09:19Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bas/32/12539_2.png) [@Bas](https://community.homey.app/u/Bas)\
**Post date:** [October 5, 2025, 9:09am UTC](https://community.homey.app/t/homey-pro-2019-2023-migration-failing/143782/1 "2025-10-05T09:09:19Z")

</div>

I know the topic title is nog new on this forum, but I started a new topic since solutions did not fit my case and posts are quite old.

Today I migrated my Homey 2016-2019 to a Homey pro 2023, following the steps lined out in the instructions. After connecting the 2023, I downloaded the latest backup from my 2016-2019. Backup was installed correctly, but I ran into the Fibaro z-wave“ no valid node ID” issue that came across this forum before. The issue is that solutions point to re-installing a backup from the old Homey, or reference to a specific old version that is no longer available (most topics date back tot 2023-2024). But my issue exists after installing the backup. So I am kind of stuck. Hopefully it can de fixed without resetting devices, since there are mostly build-in dimmers.

---

<div class="post-metadata">

**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:** [October 6, 2025, 1:02am UTC](https://community.homey.app/t/homey-pro-2019-2023-migration-failing/143782/2 "2025-10-06T01:02:37Z")

</div>

Most migrations took place since the introduction of Pro 2023, so I don’t get the fact why you describe 2023/2024 posts, and possible fixes, as old / obsolete. Nothing’s changed right? Not Homey 2019, not Pro 2023.

Because z-wave “should just work”, in other words, it’s not mentioned here:  
([https://support.homey.app/hc/en-us/articles/9302284997660-Migrating-data-from-Homey-Pro-2016-2019-to-Homey-Pro-Early-2023](https://support.homey.app/hc/en-us/articles/9302284997660-Migrating-data-from-Homey-Pro-2016-2019-to-Homey-Pro-Early-2023))  
you should contact Athom support imho:

> **[Support | Homey](https://homey.app/en-us/support/)**

---

<div class="post-metadata">

**Author:** ![Bas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bas/32/12539_2.png) [@Bas](https://community.homey.app/u/Bas)\
**Post date:** [October 6, 2025, 3:15pm UTC](https://community.homey.app/t/homey-pro-2019-2023-migration-failing/143782/3 "2025-10-06T15:15:28Z")

</div>

Because I could not find if any (firmware) updates since 2023 might have fixed the problem. And there have been updates te past 19 months…

---

<div class="post-metadata">

**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:** [October 6, 2025, 6:17pm UTC](https://community.homey.app/t/homey-pro-2019-2023-migration-failing/143782/4 "2025-10-06T18:17:16Z")

</div>

Got a response from Support?

.

> [@Bas](#):
>
> solutions point to re-installing a backup from the old Homey, or reference to a specific old version that is no longer available (most topics date back tot 2023-2024).

I wondered what you mean by “specific old version”?  
Firmware? \> this doesn’t get included in the cloud backup system.  
Backup? \> I can’t see how that would be related.

Maybe a link to these post(s) mentioning that possible fix can help clarify a bit.  
Searching on your error description did not return useful results:  
[https://community.homey.app/search?q=fibaro%20no%20valid%20node%20ID%20order%3Alatest](https://community.homey.app/search?q=fibaro%20no%20valid%20node%20ID%20order%253Alatest)

---

<div class="post-metadata">

**Author:** ![Bas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bas/32/12539_2.png) [@Bas](https://community.homey.app/u/Bas)\
**Post date:** [October 12, 2025, 7:13am UTC](https://community.homey.app/t/homey-pro-2019-2023-migration-failing/143782/5 "2025-10-12T07:13:42Z")

</div>

Resolved by athom support

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [October 12, 2025, 7:27am UTC](https://community.homey.app/t/homey-pro-2019-2023-migration-failing/143782/6 "2025-10-12T07:27:22Z")

</div>

Can you share the solution or fix?

---

<div class="post-metadata">

**Author:** ![Bas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bas/32/12539_2.png) [@Bas](https://community.homey.app/u/Bas)\
**Post date:** [October 12, 2025, 7:39am UTC](https://community.homey.app/t/homey-pro-2019-2023-migration-failing/143782/7 "2025-10-12T07:39:37Z")

</div>

A regular factory reset did not work. However, resetting via usb.homey.app did the trick
