Domoticz

Posted: **Sunday 04 January 2026 23:07**

this my docker compose yaml
I double checked correct 'ID' of zwave stick
it throws warnings causing noy usable :

zwave-js-ui | 2026-01-04 23:02:00.463 INFO APP: Version: 11.9.1.38aff57
zwave-js-ui | 2026-01-04 23:02:00.476 INFO APP: Application path:/usr/src/app
zwave-js-ui | 2026-01-04 23:02:00.477 INFO APP: Store path:/usr/src/app/store
zwave-js-ui | ______ __ __ _ _____ _ _ _____
zwave-js-ui | |___ / \ \ / / | |/ ____| | | | |_ _|
zwave-js-ui | / /____\ \ /\ / /_ ___ _____ | | (___ | | | | | |
zwave-js-ui | / /______\ \/ \/ / _' \ \ / / _ \ _ | |\___ \ | | | | | |
zwave-js-ui | / /__ \ /\ / (_| |\ V / __/ | |__| |____) | | |__| |_| |_
zwave-js-ui | /_____| \/ \/ \__,_| \_/ \___| \____/|_____/ \____/|_____|
zwave-js-ui |
zwave-js-ui | 2026-01-04 23:02:00.520 WARN STORE: scenes.json not found
zwave-js-ui | 2026-01-04 23:02:00.525 WARN STORE: nodes.json not found
zwave-js-ui | 2026-01-04 23:02:00.551 INFO APP: Listening on port 8091 protocol HTTP
zwave-js-ui | 2026-01-04 23:02:00.569 WARN BACKUP: Store backup is disabled
zwave-js-ui | 2026-01-04 23:02:00.571 WARN BACKUP: Nvm backup is disabled
zwave-js-ui | 2026-01-04 23:02:00.576 WARN Z-WAVE: Z-Wave driver not inited, no port configured

Code: Select all

version: '3.7'
services:
    zwave-js-ui:
        container_name: zwave-js-ui
        image: zwavejs/zwave-js-ui:latest
        restart: always
        tty: true
        stop_signal: SIGINT
        environment:
            - SESSION_SECRET=mysupersecretkey
            - ZWAVEJS_EXTERNAL_CONFIG=/usr/src/app/store/.config-db
            # Change if you want log times and dates to match your timezone 
            # Available at https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
            - TZ=Europe/Amsterdam
        networks:
            - zwave
        devices:
            # Do not use /dev/ttyUSBX serial devices, as those mappings can change over time.
            # Instead, use the /dev/serial/by-id/X serial device for your Z-Wave stick.
            - '/dev/serial/by-id/usb-0658_0200-if00:/dev/zwave'
        volumes:
            - zwave-config:/usr/src/app/store
        # Or by using local folder
        # - ./store:/usr/src/app/store
        ports:
            - '8091:8091' # port for web interface
            - '3000:3000' # port for Z-Wave JS websocket server
networks:
    zwave:
volumes:
    zwave-config:
        name: zwave-config
        external: true

Any help is appreciated.
Thanks
Bart

Posted: **Monday 05 January 2026 10:16**

Looks like a problem with the USB stick. What does de webinterface on port 8091 say?

Posted: **Monday 05 January 2026 10:43**

No controller is reported. But the linux command (from top of my head) ls /dev/serial/by-device shows the zwave stick

Posted: **Monday 05 January 2026 12:26**

In zwave-js-ui configuration on port 8091 you should use /dev/zwave as the USB controller port as that is configured in your docker compose yaml.

Posted: **Monday 05 January 2026 14:08**

thanks Walter, while checking I came to the mqtt part which I overlooked
Soo fixed, the mqtt-part settings still hold localhost setting iso 192.168.2.100

Posted: **Monday 05 January 2026 14:28**

OK so a misleading warning from Zwave-JS-UI?
WARN Z-WAVE: Z-Wave driver not inited, no port configured
could mean:
MQTT server not correctly defined/reached......?

Posted: **Monday 05 January 2026 15:25**

BartSr wrote: Monday 05 January 2026 14:08 thanks Walter, while checking I came to the mqtt part which I overlooked
Soo fixed, the mqtt-part settings still hold localhost setting iso 192.168.2.100

Localhost inside a docker container is the docker container itself.

Hosturl in the zwave container for the MQTT server should most likely be anything else then localhost/127.0.0.1, unless MQTT runs in the same container.

Or do I read your post wrong.

Posted: **Monday 05 January 2026 19:57**

That's correct. Just updated the ip# of the broker solved my problem.

Domoticz

problem zwave2mqtt

problem zwave2mqtt

Re: problem zwave2mqtt

Re: problem zwave2mqtt

Re: problem zwave2mqtt

Re: problem zwave2mqtt

Re: problem zwave2mqtt

Re: problem zwave2mqtt

Re: problem zwave2mqtt