For the past day, operating my Fibaro light switches and screen switches has been giving an “Unvalid Node ID: ” error message.
Already tried/checked:
- Restart Fibaro app
- Restart Homey
- Fibaro devices are present and don’t display an exclamation mark
- I can’t find any repair options for the devices.
The Homey developer tools indicate that all Z-Wave nodes have disappeared, with only the Homey node still visible. I have quite a few advanced flows using the devices. Because the switches are all built-in and a Z-Wave reinstall requires pressing the button on the Fibaro switch itself to enter pair mode, I’m trying to find alternative ways to restore the nodes to my Homey Pro 2023.
Any help is appreciated.
Maybe obvious, but did you try restoring a backup?
Of course this isn’t of any use if it’s a hardware issue, but this is still unknown…
1 Like
I restored the backup successfully. Now I have 1010 (token is expired) error with all Tuya devices, which is maybe not that surprising.
Do you use the ‘official’ Tuya app or the Tuya Cloud community app?
I use the Tuya Cloud app.
Because my Tuya devices stopped working after restoring the backup and restarting the app, I uninstalled the original app and reinstalled it. After configuring the app, a message appeared, when adding devices, that the app needed to be configured first (but I had already done that).
Further investigation revealed that the Tuya API license had expired over a year ago, but it had always worked until now. After renewing the API for six months, the Tuya devices became visible again, and everything started working again.
1 Like
I had a new (first) Homey that didn’t allow me to perform a restore of a backup that I had made locally. It didn’t allow me to perform a restore to factory settings either. It was extremely difficult with the usb-c wire for making a backup in the first place… it certainly didn’t accept the cable that came with the Homey. In short: it was bricked. So I sent it back.
Ordered a 2nd Homey, hoping that the first one was a one off ‘lemon’.
So when I received the 2nd Homey, the first thing I did was test restore the one backup I had made of the first Homey. That didn’t work very well… all the devices I had at that time were basically non functional. (a few z-wave, one klik-aan, klik-uit… luckily I was just starting and there wasn’t much there.)… but the list of z-wave nodes in the developer tools was almost empty.
First conclusion: this is not a complete restore!
With the experience I had with the first Homey, I felt that testing backup/restore AND reset to factory settings was the most important thing I needed to check extensively. Trusting a lot of Domotica programming to Homey is really only sensible if those basic functionalities can be relied upon.
So I did this:
- reset to factory setting (that worked! So one step forward compared to Homey #1)
- re-add 2 z-wave devices (Eurotronic Radiator Thermostats) + one klik-aan, klik-uit (switch)
- make a backup (again: yes!)
- restore the backup (erm… no.)
Sadly, the conclusion must be: the restore (or backup) functionality doesn’t work AT ALL.
Only the KAKU still worked. All Z-wave nodes were missing in the Developer Tools… and gave ‘invalid Node ID” errors when trying to access them (against better judgement) from Homey where they still lingered as dummies.
I understand from the posts above that this happens with other z-wave technology too so it isn’t just a problem of one z-wave app.
So this is extremely bad news. I have to think in the next few days if I should keep the Homey. Or stick to Homeseer (which is very stable and has been for more than a decade). Which is extremely bad news as the way Homey works and especially the advanced Flow technology is brilliant.
A side complaint is (coming from Homeseer) that Homey doesn’t seem to allow a ‘re-scan’ of a z-wave device. That could have saved some bother… but that is small in comparison to the above.
Do you have something “non restoreable” in your backup? It sounds really weird…
