Domoticz, Zwave-JS-UI, RPI5 and Bookwork compatibility

[elzorrovega]

Hello All,
Plan to use Domoticz in our family home abroad. Decided to invest in recent hardware so as to have reliable remote monitoring.
Purchased:

Code: Select all

Raspberry Pi 5 16 Go PCIe M.2 NVMe – Kit | Metal casing| Active Cooler |  M.2 NVMe SSD PCIe Card Adapter | Official RPI USB-C 27 W Power Supply| 64 GB SD Card | Micro HDMI 4K 

Crucial P3 Plus SSD 500Go PCIe Gen4 NVMe M.2 SSD ,  up to 4.700Mb/s, Compatible with Portable and Desktop, SSD Hard disk - CT500P3PSSD8

AEOTEC ZW090-C(Plus Version) Z-Stick Gen5 Plus, Z-Wave Plus USB for Z-Wave bridge, Zwave Controller Hub Pro 2020 

Hardware/Software Configuration:

Code: Select all

• Installed latest official image of RPI OS 64-bit Bookwork PI Desktop.
• Installed Mosquitto
• Installed Docker
• Installed/configured zwave-js-ui: 10.3.3.3331be3, zwave-js: 15.1.3
• Installed Version Domoticz Version: 2024.7
• Installed NodeRED V4.0.9
• 64 GB USB Memory Stick is connected to RPI5 USB3 port
• AEOTEC ZW90 is connected to RPI5 USB3 port 

This motley crew seems to get along with exception of intermittent WIFI reconnections. Other RPIs in same LAN do not have these issues so I assumed either hardware or software as the source. Digging into RPI forum, found some mention of concurrent network managers application.
Using command journalctl -b | grep -E "NetworkManager|wlan0" gave some funny activities related to wlan0 port.

By default Bookwork comes with Network Manager but at the same time SYSTEMD has own service. Posts suggested to disable concurrent Network Manager software. Disable service at start-up: sudo systemctl disable systemd-networkd

WIFI was still not robust after rebooting. In another RPI forum post there was a mention of potential issues with metallic case: Faraday cage. I removed RPI’s top metallic cover and voila: WIFI reception is now at 63% and at boot DHCP Server assigns WIFI IP address. After four reboots, IP address attribution is properly done during start-up.

Saw that latest version of Domoticz came today. So decided to upgrade it. For the few hours running, all appears good. Thank you team!!

[gizmocuz]

Are you using an official power supply? If not, make sure to use a good one that can handle enough amps (or try to replace it with another one)
I had some funky errors that were caused by a cheap insufficient power supply

I hope that you installed docker (compose) first, and then installed everything via docker (compose) ? (zwavejs/nodered)

[elzorrovega]

Hello Gizmocuz,

Good to hear from you and let me take this opportunity to thank you and team behind Domoticz!

Yup, power supply is the 27W official one. Maybe it manufactured by the same Chinese company as others but it has the raspberry stamp. Originally,I bought a USB2 hub 4xports to install Z-Wave controller for this is my RPI4 setup. I decided to be brave and tried using USB3 ports. It works!

RPI5 booting procedure favours USB2 before USB3 ports.

As for the software, I installed docker compose and then zwave-js-ui container. I am still old fashioned kind of guy and hesitate to put docker containers of mosquitto, nodered, etc. I guess that with docker application specific updates should be easier to maintain.

As for my motley crew, they seem to be getting along. For the moment there is only one slave attached to controller but more will come. I have dummy devices following cpu load, cpu temperature and ram use. They seem stable over the past week.

Regards,

Elzorro

[elzorrovega]

Migrated Domoticz to Bookwork release on a RPI4b. Docker now runs containers for both mosquitto and zwavejs-ui. Had some issues with locale bookwork locale settings. Be careful with any bash scripts which you are using to put or extract information from field devices. If you are setting LC_ALL=C for say decimal separator as I was doing in Bullseye, your scripts will not work properly. I did not take the time to read the differences between the two major releases but I can tell you that you will face challenges.

Another item to keep in mind is mosquitto. If instance is running as container, then subscribe/publish command will now look differently. Below are some examples of what I came-up with. There are probably a simpler json commands which avoids dealing directly with MQTT broker. I am all ears!

Code: Select all

sudo docker exec -it mosquitto-mosquitto-1 mosquitto_sub -h 192.168.1.44 -p 1883 -t 'zwave/Living_Motion_Sensor/configuration/endpoint_0/Motion_Day-Night_Mode' -C 1 -W 1 | awk -F ',' '/time/ {printf ("%1.0f",substr($2,9,length($2)))} END {print("")}'

sudo docker exec -it mosquitto-mosquitto-1 mosquitto_pub -h ' .. lhost .. ' -p ' .. lport .. ' -t '  .. "'" .. MQTTTopic .. "'" .. ' -m ' .. "'" .. message .."'"