#ZAC93 800 GPIO Module Install on Pi5

1 messages · Page 1 of 1 (latest)

oak mauve
#

I had no issues installing this on the Pi4. But I'm having a hard time finding the location of the second config file for the Pi5.
Zooz says add dtoverlay=disable-bt
enable_uart=1 to the config file (boot/config.txt) which i had no problem but i cant find the boot/firmware config. You can follow the above instructions, but you will also need to add "dtparam=uart0" to the "/boot/firmware/config.txt" file to enable UART0/ttyAMA0 on GPIO 14 & 15.
You also need to omit "enable_uart=1" from the above directions as this does not apply to the Raspberry Pi 5.

I hooked a keyboard up directly and im on the pi and followed a post from 21. but firmware doesnt show up in any LS commands. Looking for some help. I'm running this on an nvme and it looks like after flashing the OS onto it windows no longer recognizes it as a drive so i cant browse the files using an external ssd shell like i have done in the past. Kind of a noob with cmd line so looking for any help.

Post from 21'
Using blkid gives available partitions, blkid | grep hassos-boot shows the partition number we´re looking for
So in my case mount -t vfat /dev/mmcblk0p1 /mnt/boot mounts the boot partition and…
…ls -lha /mnt/boot shows content, vi /mnt/boot/config.txt finally gives access to config.txt

broken vessel
#

The Home Assistant documentation for the Z-Wave integration includes the recommended config changes

#

It's different from Pi 4

haughty patio
#

boot partition is usually in a windows compatible format

oak mauve
#

Is that the boot config it's referencing when it says config. Txt for pi5?

haughty patio
#

AFAIK all RPis have /boot/config.txt

oak mauve
#

2024-10-12T19:35:18.446Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2024-10-12T19:35:18.448Z DRIVER version 13.3.1
2024-10-12T19:35:18.449Z DRIVER
2024-10-12T19:35:19.481Z CONFIG version 13.3.1
2024-10-12T19:35:19.942Z CNTRLR querying Serial API capabilities...
2024-10-12T19:35:21.120Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2024-10-12T19:35:22.225Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2024-10-12T19:35:24.335Z DRIVER Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK
from the controller (ZW0200)
at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Drive
r.ts:5816:23)
at ZWaveController.queryCapabilities (/usr/src/node_modules/zwave-js/src/l
ib/controller/Controller.ts:1134:37)
at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src
/lib/driver/Driver.ts:1523:46)
at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Dr
iver.ts:1324:16)
Error in driver ZWaveError: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)
at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5816:23)
at ZWaveController.queryCapabilities (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:1134:37)
at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1523:46)
at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1324:16) (ZW0100)
at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1344:6) {
code: 100,
context: undefined,
transactionSource: undefined
}
Shutting down

#

2024-10-12T19:44:11.857Z DRIVER Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK
from the controller (ZW0200)
at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts
:5816:23)
at ZWaveController.queryCapabilities (/opt/node_modules/zwave-js/src/lib/c
ontroller/Controller.ts:1142:37)
at Driver.initializeControllerAndNodes (/opt/node_modules/zwave-js/src/lib
/driver/Driver.ts:1523:46)
at Immediate.<anonymous> (/opt/node_modules/zwave-js/src/lib/driver/Driver
.ts:1324:16)
2024-10-12 14:44:11.858 INFO Z-WAVE: Restarting client in 15 seconds, retry 10

broken vessel
#

correct path configured?

oak mauve
#

i think so?

#

its failing in both zwave js and ui. only running one at a time.

#

im about ot give up on this hat.... and just redo it all via a stick

#

also weird to me i have this showing up in devices.

broken vessel
#

Hm, I think the configuration may still be wrong, but I'm not sure. I haven't tried with a Pi 5 yet

#

Can you check /boot/cmdline.txt too?

#

I remember that older Pis needed to have the console=serial0,115200 part removed from there aswell

oak mauve
#

Yeah I'll look here in a bit. I found another post. I followed their instructions but. I'm really wish the hat had a light out something so I knew it was working

oak mauve
#
oak mauve
#

gave up migrated to a usb stick 😦

cinder phoenix
#

is this the right channel to ask questions about a aeontec z-wave gen5 usb stick i have? after i added it in the zwave js ui add-on it comes back with the error: failed to initialize the driver: ZWaveError: Timeout while waiting for....

This is the entire message:
Driver: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:5907:23) at ZWaveController.queryCapabilities (/opt/node_modules/zwave-js/src/lib/controller/Controller.ts:1144:37) at Driver.initializeControllerAndNodes (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:1537:46) at Immediate.<anonymous> (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:1338:16) (ZW0100)

This is on a raspberry pi 4, 2gb with an aeontec Gen5 zwave USB stick

broken vessel