Domoticz

pffffffffff i finished the zwave js ui migration for 80 devices... a lot of work, took me 2 days!

on the bright side though...: my zwave network is much more responsive now! so happy i did it!

i am trying to get my zwave up and running again using the instructions.

but somehow mqtt is not coming up on 192.168.0.115:1881

and "MQTT Auto Discovery hardware" is not showing in domoticz

what is going on?

Port should be 1883

nothing on port 1883 allso

And your MQTT Explorer shows also nothing?

ah yes...now with port 1883 i can see stuff...

i am sorry...i am an averige computer user...this is getting pretty complicated

is "mqtt auto discovery client gateway with lan interfase" same as "MQTT Auto Discovery hardware" named in the instructions?

You need two things in the hardware section of Domoticz that is the MQTT Broker: MQTT Client Gateway with LAN interface and for the client Zwavejs: MQTT Auto discovery Client Gateway with LAN interface

ok thanks.

following problem is that ls /dev/serial/by-id is giving: ls: cannot access '/dev/serial/by-id': No such file or directory

zwave dongle is connected via usb hub becouse it is a pi-4

Did you follow the instruction to determ the port of your usb Zwave stick?
command: ls /dev/serial/by-id in your terminal?

cannot access '/dev/serial/by-id': No such file or directory

this is coming up

i have a rfxcom connected allso but not showing

Oke, is possible that there are more usb devices connected to the Raspberry for example a Zigbee stick or P1 serial to usb? In that case you can try another usb port on the Raspberry and then renew the command ls /dev................

@tiga When ls /dev/serial/by-id is not working you are probably on an old OS? What OS do you use?

Does ls /dev/tty* showing your USB devices eg /dev/ttyACM0 or /dev/ttyUSB0 ?

no not working....i only can chose "by-path"

is there an other option?
i know it is /dev/ttyACM0 i had that in the hardware setup for the stick in domoticz


i have this os:
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian

I also have problems with that, I also have the Z-wave dongle connected to dev/ttyACM0, and JS UI can't connect tro it as well.
I run buster on a rpi 3b+

You can use /dev/ttyACM0, no problem. Only when using multiple USB sticks it could lead to unwanted switching of names.
You have to find out why by-id is not working as i think it should work on bullseye.

@WalterVL
In several posts you mentioned the fact that you have delete your old OZW stuff. Is deleting in the hardware section of Domomticz sufficient or do we have more deleting/uninstalling to do?
Grz Piet

Seems to be a common issue that by-id has dissapeared: https://forums.raspberrypi.com/viewtopic.php?t=351113

Bospieper wrote: ↑Thursday 04 January 2024 19:28 @WalterVL
In several posts you mentioned the fact that you have delete your old OZW stuff. Is deleting in the hardware section of Domomticz sufficient or do we have more deleting/uninstalling to do?
Grz Piet

Deleting from the setup-hardware page should be enough. Only now Domoticz has already removed the OZW hardware this seems somewhat troublesome as mentioned by other users.

my docker-compose.yml looks like this:

version: "3.7"
services:
zwave-js-ui:
container_name: zwave-js-ui
image: zwavejs/zwave-js-ui:latest
restart: unless-stopped
tty: true
stop_signal: SIGINT
environment:
- SESSION_SECRET=mySecretSession
- TZ=Europe/Amsterdam
devices:
- '/dev/ttyACM0:/dev/zwave'
volumes:
- ./store:/usr/src/app/store
ports:
- "8091:8091" # port for web interface
- "3000:3000" # port for Z-Wave JS websocket server


worked once but after reboot nothing