Zigbee2MQTT - Revision history

Walter vl: /* Use Domoticz MQTT Autodiscover */

2025-12-01T14:21:46Z

Use Domoticz MQTT Autodiscover

← Older revision		Revision as of 14:21, 1 December 2025
Line 94:		Line 94:
	<br />		<br />

	*It advised to leave the the HomeAssistant_discovery_topic in menu Home Assistant Integration to default (<code>homeassistant</code>) . This also forces to create a second MQTT hardware gateway specially for Zigbee2MQTT.		*It advised to leave the the HomeAssistant_discovery_topic in frontend menu Home Assistant Integration to default (<code>homeassistant</code>) . This also forces to create a second MQTT hardware gateway specially for Zigbee2MQTT.
	**NOTE: Do not make the <code>discovery_topic</code> name the same as the normal base topic (default: <code>zigbee2mqtt</code> in menu MQTT) as that confuses Domoticz and other applications!		**NOTE: Do not make the <code>discovery_topic</code> name the same as the normal base topic (default: <code>zigbee2mqtt</code> in frontend menu MQTT) as that confuses Domoticz and other applications!
	*Make sure Zigbee2MQTT is connected to your MQTT broker. (You can test this with (for example) the great MQTT Explorer application (free)		*Make sure Zigbee2MQTT is connected to your MQTT broker. (You can test this with (for example) the great MQTT Explorer application (free)

Walter vl: /* Use Domoticz MQTT Autodiscover */

2025-12-01T14:20:14Z

Use Domoticz MQTT Autodiscover

← Older revision		Revision as of 14:20, 1 December 2025
Line 94:		Line 94:
	<br />		<br />

	*It advised to leave the the HomeAssistant_discovery_topic to default (homeassistant) . This also forces to create a second MQTT hardware gateway specially for Zigbee2MQTT.		*It advised to leave the the HomeAssistant_discovery_topic in menu Home Assistant Integration to default (<code>homeassistant</code>) . This also forces to create a second MQTT hardware gateway specially for Zigbee2MQTT.
	**NOTE: Do not make the <code>discovery_topic</code> name the same as the normal topic (default: zigbee2mqtt) as that confuses Domoticz and other applications!		**NOTE: Do not make the <code>discovery_topic</code> name the same as the normal base topic (default: <code>zigbee2mqtt</code> in menu MQTT) as that confuses Domoticz and other applications!
	*Make sure Zigbee2MQTT is connected to your MQTT broker. (You can test this with (for example) the great MQTT Explorer application (free)		*Make sure Zigbee2MQTT is connected to your MQTT broker. (You can test this with (for example) the great MQTT Explorer application (free)

Walter vl at 22:58, 19 November 2025

2025-11-19T22:58:29Z

← Older revision		Revision as of 22:58, 19 November 2025
Line 1:		Line 1:

	Open Source Zigbee Gateway with [https://www.zigbee2mqtt.io/ zigbee2mqtt]		Open Source Zigbee Gateway with [https://www.zigbee2mqtt.io/ zigbee2mqtt]

			Zigbee2MQTT (with Autodiscover enabled) communicates with Domoticz [[MQTT\|MQTT AD hardware gateway]] over an MQTT broker/server (like Mosquito) in your network.

			Zigbee2MQTT <---> MQTT <---> Domoticz

			With Autodiscover enabled all zigbee nodes in Zigbee2MQTT will result in related devices (sensors/switches) in Domoticz.

	==Buy Hardware==		==Buy Hardware==

Gizmocuz: /* Alternative 2: Install the Domoticz Zigbee2MQTT Python plugin (not maintained!) */

2025-10-25T07:22:33Z

Alternative 2: Install the Domoticz Zigbee2MQTT Python plugin (not maintained!)

Show changes

Walter vl: /* Alternative 2: Install the Domoticz Zigbee2MQTT Python plugin */

2025-02-08T17:03:32Z

Alternative 2: Install the Domoticz Zigbee2MQTT Python plugin

← Older revision		Revision as of 17:03, 8 February 2025
Line 79:		Line 79:
	==Domoticz and zigbee2mqtt==		==Domoticz and zigbee2mqtt==
	===Alternative 1: Use Domoticz MQTT Autodiscover===		===Alternative 1: Use Domoticz MQTT Autodiscover===
	~~Since~~ release 2022.1 MQTT Autodiscover is implemented in Domoticz.		The preferred method as since release 2022.1 MQTT Autodiscover is implemented in Domoticz.

	Setup:		Setup:
Line 134:		Line 134:
	<br />		<br />

	===Alternative 2: Install the Domoticz Zigbee2MQTT Python plugin===		===Alternative 2: Install the Domoticz Zigbee2MQTT Python plugin (not maintained!)===
			Warning: This method is not the prefereed method as the plugin is not maintained for 2 years (feb 2025)

	Clone repository into your domoticz plugins folder		Clone repository into your domoticz plugins folder
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">

Walter vl: /* MQTT Broker */

2025-01-07T15:14:18Z

MQTT Broker

← Older revision		Revision as of 15:14, 7 January 2025
Line 51:		Line 51:
	For more information have a look on [https://github.com/vvatelot/mosquitto-docker-compose this page]<br />		For more information have a look on [https://github.com/vvatelot/mosquitto-docker-compose this page]<br />

	There is one additional step we need to be doing, we want the MQTT broker to restart when the system starts.		There is one additional step we need to be doing, we want the MQTT broker to restart when the system starts or reboots.

	For this you have to edit the file <code>docker-compose.yaml</code> in <code>/opt/mosquitto</code> and add the following line underneath 'mosquitto:'		For this you have to edit the file <code>docker-compose.yaml</code> in <code>/opt/mosquitto</code> and add the following line underneath 'mosquitto:'

Walter vl: /* Installing docker compose */

2025-01-07T15:13:32Z

Installing docker compose

← Older revision		Revision as of 15:13, 7 January 2025
Line 24:		Line 24:
	This is because it runs in its separate system and can use certain system resources (like hdd, serial ports)		This is because it runs in its separate system and can use certain system resources (like hdd, serial ports)

	~~I advise~~ to install all docker compose containers in their own folder (I do this in the /opt folder, like /opt/domoticz)		It is advised to install all docker compose containers in their own folder (do this in the /opt folder, like /opt/domoticz or /opt/zigbee2mqtt)

	You want your settings/data folders on your local system, so you can map local folders/files to the docker container.		You want your settings/data folders on your local system, so you can map local folders/files to the docker container.
Line 31:		Line 31:

	This way it is easy to make backups, you just copy the folder.		This way it is easy to make backups, you just copy the folder.


	A quick tutorial, you start a docker compose container with		A quick tutorial, you start a docker compose container with

Walter vl: /* MQTT Broker */

2025-01-07T15:10:53Z

MQTT Broker

← Older revision		Revision as of 15:10, 7 January 2025
Line 39:		Line 39:

	===MQTT Broker===		===MQTT Broker===
	~~ZWaveJS-UI (like~~ Zigbee2MQTT) communicates via '''MQTT''' with Domoticz. (~~ZWaveJS-UI~~ <---> MQTT <---> Domoticz)		Zigbee2MQTT communicates via '''MQTT''' with Domoticz. (Zigbee2MQTT <---> MQTT <---> Domoticz)

	So, for this to work you need to have a MQTT broker up and running. And this is the hardest part in this setup process.		So, for this to work you need to have a MQTT broker up and running. And this is the hardest part in this setup process.

Walter vl: /* Install and run Zigbee2MQTT */

2025-01-07T15:09:03Z

Install and run Zigbee2MQTT

@@ Line 38: / Line 38: @@
 If you want to see what's going on you start the docker compose container without the -d flag, when done, press control-c to stop (the docker compose container is stopped)
-*Have a MQTT broker installed or install one using docker (compose) (https://github.com/vvatelot/mosquitto-docker-compose) See also wiki page [[MQTT]]
+===MQTT Broker===
 Next install the Zigbee2MQTT Docker image with the following instruction: https://www.zigbee2mqtt.io/guide/installation/02_docker.html#creating-the-initial-configuration

Walter vl: /* Install and run Zigbee2MQTT */

2025-01-07T15:07:19Z

Install and run Zigbee2MQTT

← Older revision		Revision as of 15:07, 7 January 2025
Line 8:		Line 8:

	==Install and run Zigbee2MQTT==		==Install and run Zigbee2MQTT==
	~~'''The recommended way to install Zigbee2MQTT is by using Docker (Docker Compose).'''~~		Prerequisites:

	~~For this to work you need to~~:

	===Installing docker compose===		===Installing docker compose===