Replies: 6 comments 17 replies
-
|
Hi @widert The reason it's Initialising, is due to the fact some of your devices are not "Ready" To get a thumbs For Battery operated Device
For Mains powered devices
How are you restarting Node RED? - as if you restarted it during a write operation - the file storage may have become corrupted = corrupted Interview data, if this is happening often, check that your storage isn't playing up (especially if using an SD card) To get back up and running. For Battery operated Device
For Mains powered devices
Example, your group that are in "Stue" show nothing is responding - are they being blocked by a metallic material?, as most are mains powered, and should be responding. In essence, the Driver is Ready when
It seems the storage has lost interview data, or some other thing has screwed around with Interview data = Bad Storage. As for the Mains devices, ensure they are not in a bad location, as they should be responding to a ping. The Editor (Node RED UI) may have also crashed - try refreshing You can also turn on logging (file) set to debug, as that will show you what is happening |
Beta Was this translation helpful? Give feedback.
-
|
I have a backup system. Is there a file that can be restored if this is the case?
|
Beta Was this translation helpful? Give feedback.
-
|
Hmm, did some logging: |
Beta Was this translation helpful? Give feedback.
-
|
That's nothing to do with ZWave? ZWave has its own Log file.... You need to enable logging on the controller Node |
Beta Was this translation helpful? Give feedback.
-
|
Here is the first part of the log: |
Beta Was this translation helpful? Give feedback.
-
|
What exactly did you update? Which is quite old in terms of Driver progress The module currently uses It seems whatever update has been done, wasn't against this module? and has wiped out the interview data (and its trying to re-interview all yours Nodes) - which is what will happen, if no cache (or its folder) has been deleted ( This folder, contains ALL interview data (once devices are interviewed - Thumbs up), and is critical to operation. @AlCalzone There may also be massive interference, as the Driver has found the devices in the config - if I am not mistaken, or are device fingerprints saved in the controller? Just strange Battery devices aren't ready? @widert |
Beta Was this translation helpful? Give feedback.
-
Using module 8.0.0. of node-red-contrib-zwave-js. Has been working flawlessly for some years...😊
It was a system update, running Ubuntu 22.04.5 LTS. So I have backup of the files in zwave-js-cache, shall I restore them?
Most of the battery devices are running on USB power
Yes, you are right, no the folder structure has not been messed with, must have happened something during Ubuntu system update then...? |
Beta Was this translation helpful? Give feedback.
-
|
I think some battery devices can be powered by USB - But still sleep, if that makes sense If a device can sleep, it's not expected to respond to a ping - but at least it must have been interviewed fully to be in a Ready state. A ready device (Thumbs up) MUST
I would maybe update the module before doing anything... |
Beta Was this translation helpful? Give feedback.
-
|
I'm a bit unsure what you mean now, this is what I have on my system: Ubuntu is 22.04.5 LTS Is it the last one I should update? |
Beta Was this translation helpful? Give feedback.
-
|
I would update to the latest version of the Module (9.1.3), which requires Node JS >= 18 BUT..... an upcoming update (v10) will require Node JS version 20. Note; If updating Node JS, you will need to the following after
Updating Node JS will require native modules to be re-built (Node RED uses a few) You can skip all of this of course if you want to skip updating to the latest module, but you might be missing out on some important bug fixes, and may become harder the longer it is left |
Beta Was this translation helpful? Give feedback.
-
|
OMG, now I'm in trouble... |
Beta Was this translation helpful? Give feedback.
-
|
So you have Node 20 right? if so, |
Beta Was this translation helpful? Give feedback.
-
|
Yes |
Beta Was this translation helpful? Give feedback.
-
|
can you paste whats in .node-red/package.json |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Sorry also delete |
Beta Was this translation helpful? Give feedback.
-
|
Ok, so that got it up and running again. But still issue with nodes not connecting... |
Beta Was this translation helpful? Give feedback.
-
|
ok - so now include a full (Zwave JS) log file run, from the start... Attach it as a file.... (no sensitive data is included) - so no need to worry |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
OK... So this is what I am seeing. You should be seeing There is something going on. Can you.
It seems the controller isn't happy about something. |
Beta Was this translation helpful? Give feedback.
-
|
Allright, back up again now 😊 |
Beta Was this translation helpful? Give feedback.
-
|
OK... Seems the hardware controller got really p**sed of with the OS getting updated - not sure why It should (potentially a couple of reboots got in the way maybe) But seems the controller needed to have 5 minutes away. Still - you got 9.1.3 in doing so 😉 |
Beta Was this translation helpful? Give feedback.
-
|
(and disable logging - it will grow!!) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Did some updates to my system yesterday, and now the Z-Wave JS Controller is stuck on "Initialising network..."
Seems like connection to a lot of the nodes are lost...
Any suggestions?
Beta Was this translation helpful? Give feedback.
All reactions