Zwave JS issue after migration from raspberry pi 3 to 4

Configuration
1

Hi.

My configuration was running fine on RP3, but now I’'ve restored on a RP4 and got this error:

Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed (‘172.30.33.3’, 3000)]

I’ve reconnected the USB Zwave module and it is running fine:.
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/config.sh
[18:28:55] INFO: Both ‘network_key’ and ‘s0_legacy_key’ are set and match. All ok.
[18:28:57] INFO: Virtual Machine not detected, enabling soft-reset
cont-init: info: /etc/cont-init.d/config.sh exited 0
cont-init: info: running /etc/cont-init.d/structure.sh
cont-init: info: /etc/cont-init.d/structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun zwave_js (no readiness notification)
s6-rc: info: service legacy-services successfully started
[18:28:58] INFO: Successfully send discovery information to Home Assistant.
2022-07-06T16:29:01.014Z DRIVER

The same configuration run correctly in a VMware VM…

So why does it not run on my raspberry 4 ??

Any help welcome.

Z-Wave JS : Current version: 0.1.64

Configuration of the zwave device on my RP3 :

/dev/serial/by-id/usb-0658_0200-if00

Configuration RP4:

device: /dev/ttyAMA0
log_level: info
s0_legacy_key: 6291E1D5C5F***************
s2_access_control_key: E07**********
s2_authenticated_key: C4******************
s2_unauthenticated_key: 5D4***************
network_key: 6291E1D************************

Home Assistant Core 2022.6.7
Home Assistant Supervisor 2022.06.2
Home Assistant OS 8.2

2

Do you have an Aeotec Gen5 stick (not Gen5+)? Then you need a USB hub.

3

Yes, a Gen5. Is it due to an USB power output of the RP4 ??

4

It’s a problem with the USB designs of the Gen5 and RPi4. You’ll find numerous discussions here and elsewhere about the problem.

5

USB hub is an option. The second, cheaper option is USB extension cable. It just seems necessary to have the the stick physically separated from the Pi, at least 50cm. Its all about radio-graphic interference.

6

USB extension does not help with the Gen5 and RPi4 issue. Only a hub.

7

Many thanks for the replies. I will try with an USB hub asap. But still, I did not get the point about how this “behaviour” as to do with the fact about the connection issue on port 3000… :face_with_raised_eyebrow:

8

Because your USB stick isn’t working, it prevents the driver and server from starting…

9

I’ve orderd an USB hub and USb extension cables. Let’s test them asap.

10

Hi,

So thank you @freshcoast, I confirm that using an USB hub and USB extension cables solved the issue.

Thank you again :slight_smile:
D.