MQTT AD Dimmer switches issue in beta 17003

[hjzwiers]

I am using MQTT Auto Discovery

I have some problems in 17003 with Dimmer switches, they don't turn off anymore ..... Also tried to switch from the Domoticz UI and it fails. Its local to Domoticz, i tried in Z-wave JS and it works fine.

error: Error sending switch command, check device/hardware (idx=930) !

Could it be that it has anything to do with the update of Zwave JS ??

I now also have errors connecting with zigbee devices ....., and no errors in Zigbee2MQTT it seems like there is a problem with (some) devices connecting

I tried to downgrade to an older version, but the statement is that i cant downgrade to an older database

[hjzwiers]

Ok, i got it solved.

It was a very strange way of doing things. Because I had errors in both Zwave-JS-UI and Ziggbee2mqtt I reset both, set Domoticz to use the previous version 16997. I reset the switches in Zwave-JS, and refreshed them, and restarted the application several times. All of a sudden the lamp could be triggered from the Domoticz UI. With the Ziggbee2mqtt switches i did the same restarted several times, reset the cleared the browsing data in the app and all of a sudden the signals registered again.

All very strange and I dont know why all this is necessary ..... Anyway all is us and running again!

[hjzwiers]

Had an incident again.

Reverted back to Domoticz version 16997 and reset the whole PC which has it running ..... And now it all works. Did something change?

[hjzwiers]

Does anyone know why i need to restart Domoticz server to get it to see Zigbee2MQTT and Z-wave JS UI?
Otherwise Domoticz runs but is does not update any swiches.

[waltervl]

Does anyone know why i need to restart Domoticz server to get it to see Zigbee2MQTT and Z-wave JS UI?
Otherwise Domoticz runs but is does not update any swiches.

In what situation do you need to restart? After a reboot of the system eg RPi?

[hjzwiers]

After loading a fresh release

[waltervl]

So you use docker?
How do you update Domoticz?

[hjzwiers]

I use Dockge, so I update in the Dockge application. Within Dockge I have Domoticz, zwave-js-ui, zigbee2mqtt, nefiteasy-http-server, modbusproxy, eclipse-mosquitto and ebusd

It went fine upto around 16997, I updated the beta and I refreased the program. I had problems with the versions after that, until i discovered it went well if I restarted the server. Something has changed.

[waltervl]

Hopefully someone can help you, I dont use docker, MQTT , Zigbee2MQTT, Zwave-JS-UI nor dockge so no idea what has been changed in this context.

[gizmocuz]

No issues here, and the code has been stale for quite some time.
Best to report this issue in GitHub.
Also see our wiki for how to report MQTT-AD issues (topics payloads)

Also make sure you have the latest version of Zigbee2MQTT and don't get other devices for your switches/dimmers
There has been made some patches over a month ago

Edit:
Under Zigbee2MQTT->Settings->HASS, make sure you did not enable 'legacy_action_sensor' (disabled by default)

https://wiki.domoticz.com/MQTT_AD_Report_Problems

[hjzwiers]

I checked the Zigbee2MQTT parameter and it is set right. Ive downloaded my setup file in Dockge:

services:
domoticz:
image: domoticz/domoticz:2025-beta.16997
#image: domoticz/domoticz:beta
container_name: domoticz
restart: unless-stopped
ports:
- 8080:8080
- 8443:443
- 6144:6144
volumes:
- ./config:/opt/domoticz/userdata
- ./config/www/templates:/opt/domoticz/www/templates
environment:
- TZ=Europe/Amsterdam
- WWW_PORT=8080
- SSL_PORT=443
- LOG_PATH=/opt/domoticz/userdata/domoticz.log
networks: {}

I'm currently running in 16997 (the last stable option), @gizmocuz do you see anything wrong? I am running the last versions of both Zigbee2MQTT and Z-wave JS UI

I ran it today 17056, and it worked? I will leave and that, but I wonder what is going on

[gizmocuz]

With 'Set Right' you mean, it is not checked (= disabled) ?

I am quite sure that all your other devices work correctly, so what device is not working?

I have given a link above to our wiki, you need to create a github issue and provide all details otherwise we are not able to help

(config topic + payload, and if possible also status topic + payload)