I am working on switching from the deprecated zwave integration to the Z-Wave JS integration.
I use home-assistant container running on a Raspberry Pi 3B+, and have zwavejs2mqtt as another container. (Side note: my docker containers are managed through balena, with a docker-compose file).
Iβve followed the instructions here Z-Wave - Home Assistant and here Z-Wave - Home Assistant following the recommended approach for users running HomeAssistant Container.
In testing the setup, I am using a fresh zwave controller and micro-ssd card. When I start the containers on a fresh installation, with neither home-assistant nor zwavejs2mqtt configured, I can navigate to the ZwaveJS Control panel, and configure the ZwaveJS instance to properly connect to the zwave controller and run the WS server on port 3000. Once done, it connects successfully to the controller, and works well.
However, as soon as I create my home-assistant login account, the ZwaveJS Control Panel reports that it is disconnected. This is with no zwave integration yet set up in HomeAssistant.
I can, at this point, successfully add the ZwaveJS integration via the HomeAssistant configuration/integration menu, and it does successfully connect, and find the zwave controller. However, any added devices report as unknown and do not add the expected entities. (If I add devices via the ZwaveJS Control Panel prior to creating a home-assistant login account, the paired devices show up correctly with appropriate entities created for them).
Iβd really like to be able to use the ZwaveJS Control Panel. I can, however, work with only the HomeAssistant ZwaveJS integration, if I can add devices in such a way that they have the expected device information and associated entities.
docker-compose.yml
version: '2.1'
volumes:
hass-config:
backup:
cgroup:
store:
zwave-config:
name: zwave-config
networks:
zwave:
services:
sh_homeassistant:
container_name: sh_homeassistant
build: ./sh_homeassistant
restart: unless-stopped
privileged: true
volumes:
- 'hass-config:/hass-config'
depends_on:
- sh_mosquitto
labels:
io.balena.features.supervisor-api: true
sh_nginx:
container_name: sh_nginx
build: ./sh_nginx
restart: always
privileged: true
labels:
io.balena.features.dbus: '1'
volumes:
- 'hass-config:/hass-config'
ports:
- 80:80
sh_mosquitto:
container_name: sh_mosquitto
build: ./sh_mosquitto
ports:
- 1883
restart: on-failure
volumes:
- 'hass-config:/hass-config'
zwavejs2mqtt:
container_name: zwavejs2mqtt
build: ./zwavejs2mqtt
restart: always
tty: true
stop_signal: SIGINT
environment:
- SESSION_SECRET=mysupersecretkey
devices:
- "/dev/serial/by-id/usb-0658_0200-if00:/dev/serial/by-id/usb-0658_0200-if00"
volumes:
- "store:/usr/src/app/store"
ports:
- '8091:8091' # port for web interface
- '3000:3000' # port for zwave-js websocket server
labels:
io.balena.features.supervisor-api: true
io.balena.features.dbus: true
io.balena.features.kernel-modules: true
io.balena.features.balena-socket: true
io.balena.features.sysfs: true
io.balena.features.procfs: true
io.balena.features.firmware: true
io.balena.features.balena-api: true
The container running home-assistantβs build is FROM ghcr.io/home-assistant/raspberrypi3-homeassistant:2021.7.4, and the container running zwavejs2mqtt is FROM zwavejs/zwavejs2mqtt:5.4.3
Image of disconnected ZwaveJS Control Panel (note the red icon at the top right)
Image of connected ZwaveJS Control Panel (prior to creating HomeAssistant login)
Iβve tried a variety of combinations of settings in the ZwaveJS Control Panel, with the MQTT Gateway enabled and disabled both.
The problem Iβm encountering does not seem related to the integration itself, but just having both HomeAssistant and ZWaveJS2MQTT both running in docker containers on the same hardware. As noted, the problem starts when I create my first login for HomeAssistant.
Since the ZwaveJS installation instructions Z-Wave - Home Assistant note
- The Z-Wave JS to MQTT Docker container
This is the recommended approach if youβre running Home Assistant Container.
The recommendation is to run them together, so there must be a way to do so successfully.
Iβd really appreciate any help in getting them working together.
