Just to clarify - I removed all of this from the initialisation to keep the initialisation traffic to a minimum to try and speed up the initialisation. On large networks, this can take a long time, so first time around, youâve got to wait for the healâŠ
(if itâs not working again tomorrow, then let me know )
Just competed the update and everything went through fine, only have one device missing which is a secure door lock. Will I need to re-do this, securely?, or should it heal overnight?
Cheers
If you were using the secure binding already, then it should sort itself out - so long as you did not loose the key . The key is stored in the controller âthingâ so it should not get lost if you didnât delete this.
If youâve lost the key, youâd need to exclude and re-include.
Well that explains why my locks are not giving me any status updates. I deleted the original âthingâ and kept the new âthingâ lol⊠Will need to reinclude them tonight.
Edit: Found a backup of the old Thing json and receovered the key. If I input that into the new âthingâ I assume my locks will start functioning again without the need to reinclude them?
Thanks. Also, I have over 100 devices so instead of deleting and recreating them all, re-lilnking, etc, I instead went and modified the jsondb files and updated all their device IDs. Everything seems to work okay, except for the locks which I now have an explanation for.
I have 76 nodes (many mains). On a reboot some devices get stuck at âREQUEST NIFâ.
I would assume a host with a higher spec (currenlty Pi2) would improve things for me to get all devices going on a reboot/restart?
Yep, works, that seems to be the only way to update.
I tried PaperUI again but no luck.
The update problem is not zwave related, I tried other bindings too, no update through PaperUI possible.
I didnât investigate as you did, but this will also at least depend on your UI setting whether to use the online repo or .kar, and the versions of installed addons packages.
Thatâs possibly why. .kar contents is cached and cache contents is properly deleted/replaced during addon package upgrade process. Wouldnât bet on this to happen for the online repo version, and not to forget about connectivity caused problems there (or key or location changes you donât notice).