Cannot specify TCP connection as serial connection about node-zwave-js

[robertsLando]

I cannot reproduce this, did you tried to simply write that in the input? It suggests you available ports but you can write on it everything you want

[elronzo]

I cannot reproduce this, did you tried to simply write that in the input? It suggests you available ports but you can write on it everything you want

Having the zwave stick exposed over the network using TCP works for years now using FHEM. But as I want to migrate zwave to Home Assistant I need zwave-js-ui to be able to connect that way...

[robertsLando]

@elronzo What I mean is to write tcp://host:port in the settings input:

It just works on my side. Please try and let me know

[elronzo]

Interesting...

Socat exposes the actual device with this line
ExecStart=/usr/bin/socat TCP4-LISTEN:3000,fork,reuseaddr /dev/serial/by-id/usb-0658_0200-if00,raw,echo=0,b115200

Connection attempts from zwave-js-ui show up on the socat side with:
Jun 03 15:25:19 somehost socat[234]: 2024/06/03 15:25:19 socat[14729] E write(6, 0x11b180, 21): Broken pipe

I thought maybe FHEM must not be connected to the stick at the same time. Tried that. Got this error:
2024/06/03 15:33:50 socat[14980] E open("/dev/serial/by-id/usb-0658_0200-if00", 0102, 0666): No such file or directory

[robertsLando]

Did you typed the tcp address correctly in the Serial Port input above? Does it has the tcp:// prefix? Did you hit Save button at the end?

If so please make a driver log, loglevel debug and attach it here as a file (drag & drop into the text field).

[elronzo]

2024-06-03T13:34:03.230Z DRIVER   starting driver...
2024-06-03T13:34:03.231Z DRIVER   opening serial port tcp://somehost.lan:3000
2024-06-03T13:34:03.239Z DRIVER   serial port opened
2024-06-03T13:34:03.239Z SERIAL » 0x15                                                                 (1 bytes)
2024-06-03T13:34:04.241Z DRIVER   loading configuration...
2024-06-03T13:34:04.243Z CONFIG   Using external configuration dir /usr/src/app/store/.config-db
2024-06-03T13:34:04.244Z CONFIG   version 12.9.1
2024-06-03T13:34:04.580Z DRIVER   destroying driver instance...
2024-06-03T13:34:04.581Z DRIVER   driver instance destroyed

















2024-06-03T13:45:30.652Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2024-06-03T13:45:30.652Z DRIVER   version 12.9.1
2024-06-03T13:45:30.652Z DRIVER   
2024-06-03T13:45:30.652Z DRIVER   starting driver...
2024-06-03T13:45:30.652Z DRIVER   opening serial port tcp://hmlangw03.lan:3000
2024-06-03T13:45:30.661Z DRIVER   serial port opened
2024-06-03T13:45:30.662Z SERIAL » 0x15                                                                 (1 bytes)
2024-06-03T13:45:31.666Z DRIVER   loading configuration...
2024-06-03T13:45:31.669Z CONFIG   Using external configuration dir /usr/src/app/store/.config-db
2024-06-03T13:45:31.669Z CONFIG   version 12.9.1
2024-06-03T13:45:32.491Z DRIVER   beginning interview...
2024-06-03T13:45:32.492Z DRIVER   added request handler for AddNodeToNetwork (0x4a)...
                                  1 registered
2024-06-03T13:45:32.492Z DRIVER   added request handler for RemoveNodeFromNetwork (0x4b)...
                                  1 registered
2024-06-03T13:45:32.492Z DRIVER   added request handler for ReplaceFailedNode (0x63)...
                                  1 registered
2024-06-03T13:45:32.492Z DRIVER   added request handler for SerialAPIStarted (0x0a)...
                                  1 registered
2024-06-03T13:45:32.492Z CNTRLR   querying Serial API capabilities...
2024-06-03T13:45:32.495Z SERIAL » 0x01030007fb                                                         (5 bytes)
2024-06-03T13:45:32.495Z DRIVER » [REQ] [GetSerialApiCapabilities]
2024-06-03T13:45:33.498Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2024-06-03T13:45:33.599Z DRIVER » [REQ] [GetSerialApiCapabilities]
2024-06-03T13:45:33.599Z SERIAL » 0x01030007fb                                                         (5 bytes)
2024-06-03T13:45:33.606Z SERIAL « [DISCARDED] invalid data 0xfe81ff884f1f0000fb9f7da06700008000808600 (33 bytes)
                                  0000e87300000e0000600000fa
2024-06-03T13:45:34.602Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2024-06-03T13:45:34.613Z SERIAL « 0x012b0107010100860001005afe81ff884f1f0000fb9f7da067000080008086012 (45 bytes)
                                  b0107010100860001005afe81
2024-06-03T13:45:34.614Z SERIAL « [DISCARDED] invalid data 0xff884f1f0000fb9f7da067000080008086000000 (31 bytes)
                                  e87300000e0000600000fa
2024-06-03T13:45:34.614Z DRIVER   Dropping message because it contains invalid data
2024-06-03T13:45:34.615Z SERIAL » [NAK]                                                                   (0x15)
2024-06-03T13:45:35.703Z DRIVER » [REQ] [GetSerialApiCapabilities]
2024-06-03T13:48:06.750Z DRIVER   Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK 
                                  from the controller (ZW0200)
                                      at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/D
                                  river.ts:5349:23)
                                      at ZWaveController.queryCapabilities (/usr/src/app/node_modules/zwave-js/s
                                  rc/lib/controller/Controller.ts:970:37)
                                      at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js
                                  /src/lib/driver/Driver.ts:1458:46)
                                      at Immediate.<anonymous> (/usr/src/app/node_modules/zwave-js/src/lib/drive
                                  r/Driver.ts:1259:16)
2024-06-03T13:48:06.751Z DRIVER   destroying driver instance...
2024-06-03T13:48:06.752Z DRIVER   all queues idle
2024-06-03T13:48:06.752Z DRIVER   driver instance destroyed

[elronzo]

OK. I see... 0x01030007fb seems to be invalid. This should most likely be replaced with what is called ZWave HomeId in FHEM... Where can I set this?

[robertsLando]

@elronzo You shouldn't set the homeId manually, Let me move this to driver issues and wait for @AlCalzone response

[elronzo]

Problem is that I have set a homeID in FHEM already and included several zwave nodes. In order to migrate zwave from FHEM to zwave-js-ui I will probably need a way to set this particular homeId in zwave-js-ui...

(But I am glad that this has nothing to do with using the zwave stick over a TCP connection...)

[AlCalzone]

I think there's some misconception here. You do not set the home ID yourself, it is stored on the stick.

The logs above don't look like you're talking to a Z-Wave stick, or the serial-over-TCP tunnel is configured incorrectly.
Can you try ser2net instead of socat? This should work, since I use it all the time.
https://zwave-js.github.io/node-zwave-js/#/usage/tcp-connection?id=remote-serial-port-over-tcp documents the setup.

[elronzo]

I think there's some misconception here. You do not set the home ID yourself, it is stored on the stick.

The logs above don't look like you're talking to a Z-Wave stick, or the serial-over-TCP tunnel is configured incorrectly. Can you try ser2net instead of socat? This should work, since I use it all the time. https://zwave-js.github.io/node-zwave-js/#/usage/tcp-connection?id=remote-serial-port-over-tcp documents the setup.

Honestly I doubt that it would make much of a difference as socat does not operate in a different way. (and FHEM can use the stick exposed over TCP without any problems) I am pretty sure the problem lies somewhere else...

[AlCalzone]

Good luck then