Addon_core_zwave_js cpu usage

Hi Gurus,

I recently fried my rpi3B+ where I was having hassio installed.
I decided to change platform and to install the supervised ha in a linux machine.
So far so good, all my zwave devises are connected and functionning.

However, I realised (docker stats) that the core_wave_js addon is using a lot of CPU.

$docker stats
CONTAINER ID   NAME                          CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O         PIDS
68f51562ae7b   addon_core_zwave_js           136.13%   55.14MiB / 3.679GiB   1.46%     154kB / 152kB     47.3MB / 3.07MB   11

I was wondering if this is normal (I don’t recall such behaviour with my pi)? So I guess that there is something under the hood that is not working fine.

I have activated the low level logs and looked at them (docker logs). Except the message (Error: Invalid networkKey defined) which I believe is not meaning full I see nothing wrong:

$docker logs -f addon_core_zwave_js
[cont-init.d] structure.sh: executing... 
[cont-init.d] structure.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[11:56:09] INFO: Successfully send discovery information to Home Assistant.
Error: Invalid networkKey defined
[11:56:12] INFO: Successfully send discovery information to Home Assistant.
Error: Invalid networkKey defined
[11:56:14] INFO: Successfully send discovery information to Home Assistant.
Error: Invalid networkKey defined

Can someone be kind enough to give me road of investigation.
Now, I can stop the docker with the supervised menu and everything is working fine up to the next boot.

Cheers

I have the same issue. No errors on log, but the CPU is overwhelmed.