sytem start very slow upon startup (device was rebooted)

[zeev-mindali]

Dear all,

installed the zwave-js-ui via docker, and all works fine.
but when it's starting after reboot, the cpu is very high (100%) and it's takes up to an half an hour (10 devices) to start working.
i see the devices in the ui, but the status is in question mark.
how i can tell the system to save the info after first interview, and use it on next boot

[robertsLando]

Please share your docker-compose file or the command used to start zui and also attach driver log, loglevel debug and attach it here as a file (drag & drop into the text field).

[zeev-mindali]

docker command :
docker run --rm -it -p 8091:8091 -p 3000:3000 --name=zwave --device=/dev/ttymxc6:/dev/zwave -v $(pwd)/store:/usr/src/app/store zwavejs/zwave-js-ui:latest

zwave-js-ui-store.zip

[robertsLando]

cc @AlCalzone

@zeev-mindali where are you running ZUI? Can you give use some specifications? Like product/model RAM

[AlCalzone]

The log is showing some really weird pauses during startup, for example:

2023-09-20T13:19:44.672Z CNTRLR   [Node 053] The node is alive.
2023-09-20T13:28:03.896Z CNTRLR   Retrieving priority route to node 53...
2023-09-20T13:28:03.943Z CNTRLR   [Node 053] The node is ready to be used

I think the priority route stuff is initiated by Z-Wave JS UI as part of the "ready" callback, so something is blocking there for 8 minutes, before the driver can continue.

Also several serial messages are received multiple times. Not sure what could cause this, but it being on the OS/hardware side isn't entirely unlikely.

[zeev-mindali]

i using it on variscite som imx6ul-var-dart

product specefication data:
CPU NameNXP/Freescale iMX6UL / 6ULL / 6ULZ
CPU Type900MHz Cortex™-A7
Memory & Storage1 GB DDR3L, 128 GB eMMC
EthernetDual 10/100Mbps
WiFi/BT 802.11 ac/a/b/g/n, Bluetooth 5.2/BLE
Power consumptionUnder 5mA in suspend

[robertsLando]

@zeev-mindali Do you have locks devices?

[zeev-mindali]

nope, but i have glass9 from mcoHome (two of them),
once i removed it from the the zwave net, everything start to work faster...
node 53 that you mentaioned before.
my question, if the network and the node was already probe, why i need to wait again for probing after reboot,
does it not save the info to sqlite3 db file?

[robertsLando]

Does node 53 support schdule CC? @AlCalzone What I do in node ready is to also popolate schedule CC, BTW I fetch them from cache so that should not take this much....

@zeev-mindali Are you using latest version, right? I mean 8.25.1?

@AlCalzone I also noticed this in logs:

2023-09-20T13:19:34.029Z CNTRLR   [Node 048] No device config found
2023-09-20T13:19:34.117Z CNTRLR   [Node 049] No device config found
2023-09-20T13:19:34.232Z CNTRLR   [Node 050] No device config found
2023-09-20T13:19:34.361Z CNTRLR   [Node 051] No device config found
2023-09-20T13:19:34.415Z CNTRLR   [Node 052] No device config found
2023-09-20T13:19:34.459Z CNTRLR   [Node 053] No device config found
2023-09-20T13:19:34.562Z CNTRLR   [Node 054] No device config found
2023-09-20T13:19:34.593Z CNTRLR   [Node 055] No device config found

Could that be a problem?

[AlCalzone]

You mean Schedule Entry Lock CC.
Schedule CC is a different one that zwave-js doesn't support yet.

The missing device configs shouldn't cause this.

[robertsLando]

Yeah I mean Schedule Entry Lock CC.

So i have no clue what else could cause this sincerly

[AlCalzone]

Are there application logs that could give a hint what's happening in the time between the driver logs?

[robertsLando]

@AlCalzone could be.

@zeev-mindali Could you upload logs again but this time select application logs too?

[zeev-mindali]

sure, i will connect the glass9 again later on, and send the entire logs directory

thanks for the help :)

[zeev-mindali]

where i can find the appllication logs

[zeev-mindali]

zwavejs_current.log

[AlCalzone]

Application logs: https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=application-logs
Driver logs: https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=driver-logs

[zeev-mindali]

find the error, it's mcoHome glass 9 product, sending a lot of information and retiries, once i took it out, system started to work faster