# Invalid node id after migrating

**URL:** <https://community.homey.app/t/invalid-node-id-after-migrating/94891>\
**Category:** Questions & Help\
**Created:** [November 17, 2023, 10:39am UTC](https://community.homey.app/t/invalid-node-id-after-migrating/94891 "2023-11-17T10:39:35Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stian89](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stian89/32/32082_2.png) [@Stian89](https://community.homey.app/u/Stian89)\
**Post date:** [November 17, 2023, 10:39am UTC](https://community.homey.app/t/invalid-node-id-after-migrating/94891/1 "2023-11-17T10:39:35Z")

</div>

Hi! Just migrated from 2019 to 2023 Homey through a backup.  
Everything seems to be transfered OK, but there is an issue with all my Fibaro devices.

If I try to trigger a fibaro unit, I get the error: Invalid node id. Any suggestions on how to fix it?

---

<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:** [November 18, 2023, 2:48am UTC](https://community.homey.app/t/invalid-node-id-after-migrating/94891/2 "2023-11-18T02:48:08Z")

</div>

Can [this](https://community.homey.app/t/all-z-wave-devices-are-gone-after-latest-firmware-update-to-10-1-0-on-h23/94736/27) be related, Stian

---

<div class="post-metadata">

**Author:** ![Jan\_Spruit](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan_spruit/32/82940_2.png) [@Jan\_Spruit](https://community.homey.app/u/Jan_Spruit)\
**Post date:** [November 18, 2023, 10:56am UTC](https://community.homey.app/t/invalid-node-id-after-migrating/94891/3 "2023-11-18T10:56:46Z")

</div>

Hi,

i got same issue after migration 2016 to 2023.  
waited more then an hour after restore. then after restart apps were started but when i try to use zwave device I also get invalid node id

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [November 18, 2023, 11:12am UTC](https://community.homey.app/t/invalid-node-id-after-migrating/94891/4 "2023-11-18T11:12:09Z")

</div>

Please do contact Athom on their [support form](https://support.athom.com/hc/requests/new), they might read these messages, but there is also a big chance they _wont_.

And lets not try to combine all issues that seem the same, to also be the same.  
It could be related, but that doesn’t necessarily makes them the same.

---

<div class="post-metadata">

**Author:** ![Jan\_Spruit](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan_spruit/32/82940_2.png) [@Jan\_Spruit](https://community.homey.app/u/Jan_Spruit)\
**Post date:** [November 20, 2023, 12:14pm UTC](https://community.homey.app/t/invalid-node-id-after-migrating/94891/5 "2023-11-20T12:14:15Z")

</div>

Hi,

Athom support adviced me to install latest experimental update and do restore of a pre 10.0.1.0 backup. Then they would remotely run some scripts to do a fix. Since I only had a homey2016 backup i restored this one again to homey2023 with the experimental update. After restore my zwave devices were working again, without need of Athom support to run scripts.

---

<div class="post-metadata">

**Author:** ![Ruud\_Gakes](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ruud_gakes/32/79108_2.png) [@Ruud\_Gakes](https://community.homey.app/u/Ruud_Gakes)\
**Post date:** [April 23, 2024, 6:24pm UTC](https://community.homey.app/t/invalid-node-id-after-migrating/94891/6 "2024-04-23T18:24:29Z")

</div>

Hello,  
Last weekend I installed a new Homey 2023, because I couldn’t reach the Homey 2019 anymore. Placed the back ups frome the old one and have the same troubles with the Z-wave devices . Does it have to be specificaly the 10.0.1.0 back up or does anyone have another option?

---

<div class="post-metadata">

**Author:** ![Jan\_Spruit](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan_spruit/32/82940_2.png) [@Jan\_Spruit](https://community.homey.app/u/Jan_Spruit)\
**Post date:** [April 23, 2024, 7:50pm UTC](https://community.homey.app/t/invalid-node-id-after-migrating/94891/7 "2024-04-23T19:50:43Z")

</div>

Hi,

you should be able to use backup made with latest stable firmware. Restore and the rebuilding all devices takes quite some time. Have you tried reset the 2023 and do a restore from 2019 again?

---

<div class="post-metadata">

**Author:** ![Ruud\_Gakes](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ruud_gakes/32/79108_2.png) [@Ruud\_Gakes](https://community.homey.app/u/Ruud_Gakes)\
**Post date:** [April 23, 2024, 8:23pm UTC](https://community.homey.app/t/invalid-node-id-after-migrating/94891/8 "2024-04-23T20:23:11Z")

</div>

Hello Jan,  
Thanks for your quick reply.  
I shall try to restore to an earlier updat/back up than latest.  
Could make sense, the 2019 had problems with latest one.  
I’ll try it tomorrow.  
Thanks, will get back to you.

---

<div class="post-metadata">

**Author:** ![Ruud\_Gakes](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ruud_gakes/32/79108_2.png) [@Ruud\_Gakes](https://community.homey.app/u/Ruud_Gakes)\
**Post date:** [April 28, 2024, 5:30pm UTC](https://community.homey.app/t/invalid-node-id-after-migrating/94891/9 "2024-04-28T17:30:04Z")

</div>

Hello Jan,  
Sorry for my late reply.  
I re-installed the homey with an older version, that worked on the ‘19’ , now it works.  
Hue gave some problems, re-installed them to and now it’s fine.  
Thanks for your help.
