Page 4 of 4

Re: MQTT AD - Zigbee2MQTT

Posted: Thursday 02 May 2024 11:32
by nonolk
Hello,

I just want to share something, I found recently.

It looks at least in my case, that updating raspbian from Buster to Bullseye solved the issue (at least for now).
It can be done in place, just be carrefull with your network configuration (solution could be found here https://forums.raspberrypi.com/viewtopi ... 6&t=320383)

Maybe it could help someone else.

Re: MQTT AD - Zigbee2MQTT

Posted: Sunday 14 July 2024 22:02
by matekogon
Hello,
I have the same problem.The problem occurs after every Domoticz reset I need to rename the devices in Zigbee2mqtt and save. So that Domoticz can communicate with devices.The problem occurred after updating to 2024. I have Domoticz on Windows. Any suggestions?

Re: MQTT AD - Zigbee2MQTT

Posted: Monday 15 July 2024 7:21
by Kedi
Maybe you should 'retain' set to true in Zigbee2MQTT?

Re: MQTT AD - Zigbee2MQTT

Posted: Sunday 15 December 2024 10:32
by matekogon
Gentlemen, I'm back again with a problem. after setting "retain" the problem still occurs. Do you know where the problem is? In home assistant everything works fine after restart

Re: MQTT AD - Zigbee2MQTT

Posted: Monday 16 December 2024 16:30
by alkempter
Some time ago I tried to go from Zigbee2MQTT version 1.30.2 to version 1.41.0 without changing the working setup.

Docker container then keeps restarting with version 1.41.0 and also older versions (e.g. 1.36). No output in log.

Starting it with docker run ... shows following output:
docker run --name zigbee2mqtt --restart=unless-stopped --device=dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0:/dev/zigbee -p 8092:8092 -v /home/domopi3i/zigbeemq/data:/app/data -v /run/udev:/run/udev:ro -e TZ=Europe/Vienna koenkk/zigbee2mqtt
Using '/app/data' as data directory
Starting Zigbee2MQTT without watchdog.
[2024-11-13 19:31:39] info: z2m: Logging to console, file (filename: log.log)
Error: 'homeassistant.discovery_topic' cannot not be equal to the 'mqtt.base_topic' (got 'domozigbee')
at new HomeAssistant (/app/lib/extension/homeassistant.ts:470:19)
at new Controller (/app/lib/controller.ts:135:34)
at start (/app/index.js:152:18)

Finally found a hint in homeassistant community.

in configuration.yaml changed discovery Topic (now domoadzigbee)
homeassistant:
discovery_topic: domoadzigbee

and in Domoticz Auto Discovery Client Gateway Definition changed
Autodiscovery prefix to domoadzigbee

Did not Change in Domoticz Client Gateway the prefix definitions (domozigbee/in and domozigbee/out)

Seems to work now as before.

Interestingly in zWave MQTT interface the discovery topic and the client gatewa prefix definitions can have the same name.

Cheers
Al