zwavejsUI, domoticz, mosquitto in docker

[pgas37]

Hi,
normally i had domoticz, zwavejsui and mosquitto running on a raspberrypi. Due to trouble upgrading to version 2025.2 I made docker containers for Zwave-js-ui, mosquitto and domoticz.
For the Domoticz hardware setup MQTT Client Gateway with Lan interface i took the configuratie from the old Pi setup. The ZwaveJSUi configuratie is also the same (same authkeys, etc) The controlpanel from Zwave js says: driver is running, controller is idle, connected and I have a home ID. number.
In the MQTT explorer I have a zwave topic publishing all the nodes.

Whats the problem:
In zwavejsui control panel some nodes are marked with 'unknow manufacturerxxx',
from 4 of the 6 nodes the protocolinfo is still (after hours) unknown, the other are 'completed'.

I restored a backup in domoticz in the conbtainerized Domoticz, so all the old nodes/sensors are visible (RFXCOM sensors working), but e.g. an on/off command of a zwave-sensor results in an error e.g. "Error sending switch command, check device/hardware (idx=10497) !". None of the zwave-sensors working in Domoticz.

Can anyone help me to solve this problem?

Thanks
Paul

[jannl]

You should use the auto discovery mqtt hardware.

And givve it some time. For zwave you may need to trigger the sensors and devices

[waltervl]

And also take care of IP adresses linking Domoticz and Zwave-JS-UI to MQTT docker. Due to docker restrictions adresses like localhost and 127.0.0.1 are not working (they are linking to inside the container). You have to use the IP adress of your host (eg RPi)

[pgas37]

I use the MQTT autodiscovery and yes
I also use everywhere the full ip adres of the RPI and port 1883.

The same prefix in zwavejsui and in domoticz (zwave).

I read somewhere it is not possible that domoticz en zwavejsui in container could communicatiedienst which each other ( ofcourse mosquitto is installeer) due to a bug and that you have to use nodered. Is that correct?

Problaby the configuratie is not correct: is na example for containerized domoticz and swavejsui available?

Thanks

[waltervl]

The domoticz wiki on Zwave-JS-UI is clear how to install it. The way how Domoticz is installed does not matter.
Communication always goes over mqtt. There is no direct communication with Zwave-JS-UI and Domoticz
https://wiki.domoticz.com/Zwave-JS-UI

[pgas37]

Thanks for the link to the wiki. It works, but unfortunately only partially.
The original configuration was a PI with Domoticz, OpenZwave converted to Zwavejsui (the controller is an Aeon Zwave USB stick), and RFxCom. The Zwave USB controller managed 8 nodes. Everything worked fine (see screenshots of the original setup).
Current configuration: Pi with Docker containers for domoticz, mosquitto, nodered, and Zwave JS-UI (and portainer). I removed the Z-stick from the old configuration and placed it in the new one. All 8 Zwave nodes are visible in the ZwaveJS-UI control panel (see screenshot), but some of them have unknown manufacturers data (xxxx) and product codes.
- All sensors from node 10 (multisensor) are being passed to domoticz.
- 3 nodes (20, 21, 26, motion sensors) are still not being recorded.
- Node 22 (motion sensor) is completed and recorded as connected in the network graph,, but the sensor is not being passed to domoticz.
- Node 48 (kickspace) is completed and recorded as connected in the network graph, but no sensors are being detected in domoticz, which should be 8.
- The temperature sensor from node 49 is also completed and recorded (kruipruimte), but is not being passed to domoticz.

In summary: all nodes are visible, but the sensors for some of them aren't being passed on to Domoticz.

What's going wrong here?

[pgas37]

network gragp missing

[pgas37]

I tampered the motion switches (nodes 20,21,22,26). They are visible now in domoticz

Nodes 48 en 49: i unplugged the power en plugged in again. No changes (zwavejsui status for alle node completed,but no sensors in domoticz (see printscreen MQTT-explorer.)

Any expert that can help?

[waltervl]

I see you changed the MQTT discovery topic in Zwave-JS-ui from homeassistant to domoticz.
That is not advised. Better leave it homeassistant. Now on every MQTT message in domoticz the MQTT AD system has to check for new devices....
Also change it back to homeassistant in Domoticz MQTT AD configuration.
Or if you do not want to use the word homeassistant use something like DomoticzAD. Also do not use the name zwave as that is used for the zwave-js-ui state topics.

[pgas37]

changed zwavejsui Homne Assitant discovery prefix to homeassistant and
changed the domticz MQTT AD prefix in homeassitant.

Unplugged en plugged the power of node 48 (kickspace); No results

[waltervl]

There should a config topic in homeassistant be created for node 48. I have no idea what node 48 is, perhaps check status in Zwave-Js-UI?

[pgas37]

Hi,

I do not know how to create a "config topic"

Node 48 is a quibino flush on/of thermostatic switch. in the old configuration it looked like this:

[jannl]

What do you see in the webinterface of zwavejs? Check if the port is forwarded to the zwave docker. Default port is 8091

Also re-adding may help. Set the enable in the zwave js to on

[pgas37]

default port is 8091. that works because the nodes 10, 13, 20,21,22,,26 are visible in domoticz and mqtt explorer.

you suggest a re-adding: i do not dare to do that. Why? the old configuration is still up and running. If i replace the usb controller again in the old configuration everything works. I do not known what happens if a do a re-adding in the new configuration (an exclusion first will be necessery first) ; mayby it does not work AND maybe it effects the old configuration to.

[jannl]

The worst thing that can happen when you re-add is a duplicate device in Domoticz, that is solvable.

Not sure if you need the enable the 'allow new hardware' when you re-add.

And make a database backup when trying these things.

[pgas37]

Backups seems not to be compatible: In the past I made a zwavejsui backup from the old configuration but you cannot restore that one in the new zwavejsui in docker

[pgas37]

found a solution:

in the old zwavejsui configuration i made a backup of the "store".
after a docker stop for zwavejsui i copied the old configuration in the "store" location of the zwavejsui in docker. Adjusted the ip and homeassistant-prefix in zwavejsui-settings

In domoticz (container) i restored a backup of the old configuration. adjusted some settings and dozen of sensors and switches are working again!

Next problem is the missing Solaredge Modbus TCP plugin in the domoticz hardware..............................??

[jannl]

That should not be that hard.

Install the plugin in the plugins directory and de modbus libraries in the docker container. And resd about customstart.sh for automating this.

[pgas37]

Sorry, but your suggestion is not very clear to.

Could you be a more specific? Somewhere a step by step guide?
Thanks

[jannl]

It is quite clearly explained on the wiki page. I will see if I csn write something down about installing the solaredge. Also read the forum.

Using opensource software like Domoticz requires at least some Linux knowledge. What helps is buying a second pi to test new things besides the production system. Or start a second docker with different ports, works on a pi 3b