RaZberry2: Failed to initialize the driver on arm64 (bullseye)

[qaldak]

I moved my Raspberry from "stretch" to "bullseye". After new setup, zwabve-js-ui won't work anymore.
Reason: failed to initialze the driver.

2022-11-02T09:54:22.373Z DRIVER   ███████╗ ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗             ██╗ ███████╗
                                  ╚══███╔╝ ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝             ██║ ██╔════╝
                                    ███╔╝  ██║ █╗ ██║ ███████║ ██║   ██║ █████╗   █████╗      ██║ ███████╗
                                   ███╔╝   ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝   ╚════╝ ██   ██║ ╚════██║
                                  ███████╗ ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗        ╚█████╔╝ ███████║
                                  ╚══════╝  ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝         ╚════╝  ╚══════╝
2022-11-02T09:54:22.373Z DRIVER   version 10.3.0
2022-11-02T09:54:22.374Z DRIVER   
2022-11-02T09:54:22.374Z DRIVER   starting driver...
2022-11-02T09:54:22.381Z DRIVER   opening serial port /dev/zwave
2022-11-02T09:54:22.392Z DRIVER   serial port opened
2022-11-02T09:54:22.393Z SERIAL » [NAK]                                                                   (0x15)
2022-11-02T09:54:22.395Z DRIVER   loading configuration...
2022-11-02T09:54:22.400Z CONFIG   Using external configuration dir /usr/src/app/store/.config-db
2022-11-02T09:54:22.401Z CONFIG   version 10.3.0
2022-11-02T09:54:24.696Z DRIVER   beginning interview...
2022-11-02T09:54:24.696Z DRIVER   added request handler for AddNodeToNetwork (0x4a)...
                                  1 registered
2022-11-02T09:54:24.697Z DRIVER   added request handler for RemoveNodeFromNetwork (0x4b)...
                                  1 registered
2022-11-02T09:54:24.697Z DRIVER   added request handler for ReplaceFailedNode (0x63)...
                                  1 registered
2022-11-02T09:54:24.698Z CNTRLR   querying controller IDs...
2022-11-02T09:54:24.713Z SERIAL » 0x01030020dc                                                         (5 bytes)
2022-11-02T09:54:24.714Z DRIVER » [REQ] [GetControllerId]
2022-11-02T09:54:25.720Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-11-02T09:54:25.823Z SERIAL » 0x01030020dc                                                         (5 bytes)
2022-11-02T09:54:25.825Z DRIVER » [REQ] [GetControllerId]
2022-11-02T09:54:26.831Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2022-11-02T09:54:27.936Z SERIAL » 0x01030020dc                                                         (5 bytes)
2022-11-02T09:54:27.938Z DRIVER » [REQ] [GetControllerId]
2022-11-02T09:54:28.956Z 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:3990:23)
                                      at ZWaveController.identify (/usr/src/app/node_modules/zwave-js/src/lib/co
                                  ntroller/Controller.ts:713:33)
                                      at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js
                                  /src/lib/driver/Driver.ts:1208:26)
                                      at Immediate.<anonymous> (/usr/src/app/node_modules/zwave-js/src/lib/drive
                                  r/Driver.ts:1015:16)
2022-11-02T09:54:28.971Z DRIVER   destroying driver instance...
2022-11-02T09:54:28.978Z DRIVER   driver instance destroyed

my docker-compose config is still same as on "stretch":

version: "3.7"
services:
  zwave-js-ui:
    container_name: zwave-js-ui
    image: zwavejs/zwave-js-ui:8.2.2
    restart: unless-stopped
    tty: true
    stop_signal: SIGINT
    environment:
      - ZWAVEJS_EXTERNAL_CONFIG=/usr/src/app/store/.config-db
    networks:
      - zwave-js-ui
    devices:
      - '/dev/ttyAMA0:/dev/zwave'
    volumes:
      - zwave_data:/usr/src/app/store
    ports:
      - "8091:8091" # port for web interface

networks:
  zwave-js-ui:
    name: zwave-js-ui

volumes:
  zwave_data:
    name: zwave_data

raspi config should be ok. Device /dev/ttyAMA0 is availabe.
Any idea to solve this?

[robertsLando]

Try to disable soft reset using env var: ZWAVEJS_DISABLE_SOFT_RESET=true

[qaldak]

Still same. Disable soft reset didn't change anything.

[robertsLando]

Try replacing /dev/ttyACM0 with the one you find by following this: #2483 (and remove the previously added env var)

[qaldak]

ENV var removed.

Mhmmm... there is no ID_SERIAL for ttyAMA0.

➜ ~ /bin/udevadm info --name=/dev/ttyAMA0
P: /devices/platform/soc/3f201000.serial/tty/ttyAMA0
N: ttyAMA0
L: 0
S: serial0
E: DEVPATH=/devices/platform/soc/3f201000.serial/tty/ttyAMA0
E: DEVNAME=/dev/ttyAMA0
E: MAJOR=204
E: MINOR=64
E: SUBSYSTEM=tty
E: USEC_INITIALIZED=8219203
E: DEVLINKS=/dev/serial0
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

maybe because it's not an USB device, but an expansion board for RPi which uses gpio.

[robertsLando]

@qaldak Is there any fixed id path for that serial device? the problem is that using ttyACM0 could fail as zwave-js does a soft reset on startup and that could cause that id to change (for ex. ttyACM0 becomes ttyACM1). That's why we suggest to use that path instead, try to check in /dev/serial/by-path/

[jmgiaever]

Have you checked the config.txt and cmdline.txt files and verified the required changes there, and know that the board is working as expected?

[qaldak]

No, there is any fixed id path.

config.txt: uart, i2c and spi are enabled.
cmdline.txt: root=PARTUUID=8d0105b5-02 rootfstype=ext4 rootwait fsck.repair=yes net.ifnames=0 logo.nologo console=tty1 cgroup_enable=memory console=ttyAMA0,115200

What other way can I check if the device is working?

[jmgiaever]

I'm using the following:

# config.txt:
# Enable the serial pins
enable_uart=1
dtoverlay=miniuart-bt
core_freq=250

# cmdline.txt (you probably shouldn't just copy/paste this....)
dwc_otg.lpm_enable=0 rng_core.default_quality=700 vt.handoff=2 quiet splash

But I'm also using Ubuntu Core and the snap version, so I only have to connect the serial-port and it's automatically identified by ZUI. So I can't help you any futher.. I know @AlCalzone uses these boards too, and I guess under Debian based system (e.g rapsbian).

[AlCalzone]

console=ttyAMA0,115200

Delete that. You have a serial console on the GPIO, preventing communication with the zwave controller.

[qaldak]

Many thanks for all your inputs, guys.
I solved the problem!

Problem was: additionaly to enable_uart=1 (ttyS0 (mini UART device)), I had explicity ttyAMA0 console activated.

So I did following:
/boot/cmdline.txt removed
console=ttyAMA0,115200

/boot/config.txt set

enable_uart=1
dtoverlay=pi3-miniuart-bt

Now it works fine.

[jmgiaever]

Note: The answer applies to raspberry pi 3 models, either model should use miniuart-bthttps://github.com/raspberrypi/firmware/blob/f3db2058e9d 1f0cefb4c1aff5dbd9fd2d2749233/boot/overlays/README#L2980

[jmgiaever]

@AlCalzone you know the reason/benefit of setting the core_freq to 250?

[AlCalzone]

No