Domoticz

solarboy wrote: Monday 25 November 2024 18:53 Re: Get ZWave devices visible in Domoticz (Zwave JS UI / MQTT)Quote solarboy
by solarboy » Monday 25 November 2024 18:53

Thanks, I will try the different suggestions.
My guess is that from within Docker the different containers have a problem to connect to each other by their real ip-adress and port.
I will also change the prefix to zwave.
At the moment I'm focussing on Docker network settings.

solarboy wrote: Monday 25 November 2024 18:53 So I would check that you have the correct port, name and username for mosquitto in zwavejsUI and that you have made those ports available to both docker containers. I use "host.docker.internal" as the host url in zwavejsUI and the prefix "zwave" (not the discovery topic) so all my devices appear under the subheading "zwave" when I view mosquitto with MQTT Explorer. I don't use any authorisation so I have "auth" turned off. Perhaps you could try running your mosquitto without requiring authentication until you resolve the problem.

Thanks for the suggestions. I have tried several and have succeeded .

1) was a change in the domoticz docker-compose.yml for the USB-id (I thought I needed to add a port number by adding -port0 to the USB-id): usb-0658_0200-if00-port0 into usb-0658_0200-if00 (without the -port0)
2) was a change in Z-Wave JS UI MQTT Gateway setting, because I had enabled security by setting allow_anonymous false in the mosquitto.conf.
I had to enable Auth and fill in Username and Password I used for Mosquitto.
After saving these the devices started filling in Domoticz immediately. Also in MQTT Explorer I now saw the devices.

It was not necessary to use "host.docker.internal". I used the dedicated ip-address with the right ports and that worked fine.

Now onwards to the steps of migrating Domoticz from Synology to Raspberry!

Hello, I seem to have the same issue: due to OpenZwave being deprecated in domoticz, I have been requested to migrate to zwave-js-UI and MQTT.

To that end, I have installed both on my Raspberry Pi3 b+, however NOT using docker-compose because this tutorial https://wiki.domoticz.com/Zwave-JS-UI did not work for me regarding Mosquitto for some reason I still can't figure-out, so I installed mosquitto simply using apt-get install mosquitto (and kept docker for zwave-js-ui).
The mosquitto broker service seems to work (service status showing as "active", MQTT-explorer showing the tree of devices) and so does Zwave JS UI at 192.168.1.xx:8091 (e.g. showing the connectivity of devices with proper names, and all devices are reported as "alive").

In Domoticz, I have installed the "MQTT Auto Discovery Client Gateway with LAN interface" hardware under "setup - H/W". The H/W is "enabled" and if I click "setup" next to this H/W, I see a bunch of nodes (that have no sensible names).

Now, and this is the problem, if I go to the "device" section of domoticz, I can't see any new device that is attached to a Zwave controller. So in effect I can't use the devices...
I spent the entire day trying to figure-out to no avail, however I must confess I'm not used to managing this environment.
I'm not sure if this is a Domoticz issue or a MQTT issue, or more likely just a configuration that I mismanaged while installing those applications and services. Please note that I did enable MQTT gateway in Zwave-js-ui, and I double checked the local host IP address, discovery prefixes, port numbers, etc.

I would be happy to receive some help here. Maybe it's something obvious !
Thanks a lot,
Manu

in MQTT explorer do you see a homeassistant topic with subtopics like sensor, switch, light?
If not you have to enable Homeassistant Autodiscover in Zwave-JS-UI.

But you see devices in the Setup Button of your " MQTT Auto Discovery Client Gateway with LAN interface" you should also see devices related to the " MQTT Auto Discovery Client Gateway with LAN interface" hardware in Domoticz menu Setup-Devices together with all the rest of your devices.
In Domoticz they are now related to MQTT-AD, not to the old zwave controller.

Version: 2025.1 (build 16767)
Platform: Docker domoticz/domoticz:latest
Plugin/Hardware: MQTT Auto Discovery Client Gateway with LAN / ZWaveJS-UI with MQTT
Description: Last seen not updated on Zwave devices battery only

Hello,

Since August 15th, Zwave devices are still working with Domoticz (switches, temp sensor, ...), but battery level of all ZWave devices are no more updated on Domoticz.
With MQTT explorer I can see the messages sent by ZWaveJS-UI, well received by Domoticz, however last seen is not updated. See below example:

MQTT explorer message captured:
{"value_template":"{{ value_json.value }}","unit_of_measurement":"%","device_class":"battery","state_topic":"zwave/Fibaro_Walli/128/0/level","availability":[{"payload_available":"true","payload_not_available":"false","topic":"zwave/Fibaro_Walli/status","value_template":"{{'true' if value_json.value else 'false'}}"},{"topic":"zwave/_CLIENTS/ZWAVE_GATEWAY-zwave-js-ui/status","value_template":"{{'online' if value_json.value else 'offline'}}"},{"payload_available":"true","payload_not_available":"false","topic":"zwave/driver/status"}],"availability_mode":"all","json_attributes_topic":"zwave/Fibaro_Walli/128/0/level","device":{"identifiers":["zwavejs2mqtt_0xedfc8921_node30"],"manufacturer":"Fibargroup","model":"Walli Controller (FGWCEU-201)","name":"Fibaro Walli","sw_version":"7.0"},"name":"Fibaro Walli_battery_level","unique_id":"zwavejs2mqtt_0xedfc8921_30-128-0-level"}

Received by Domoticz:
2025-08-23 17:45:33.898 Status: ZWave JS UI: Discovered: Fibaro Walli (Fibaro Walli_battery_level)/Fibaro Walli (Fibaro Walli_battery_level) (unique_id: zwavejs2mqtt_0xedfc8921_30-128-0-level)

However associated device "last seen" is not updates. Thus, device is red.

Any idea or additional test/investigation I could perform?