Zigbee2MQTT on another Rasberry PI than Domoticz

[Satellietje]

On a Raspberry PI 4 I have installed Domoticz with the Zigbee2MQTT plugin, I see the item Zigbee2MQTT in the hardware tab in Domoticz.

On another Raspberry Pi 4 I installed an MQTT server which also works in Domoticz.

On yet another Raspberry PI 4 I installed Zigbee2MQTT, how can I tell in Domoticz or in the Zigbee2MQTT plugin that Zigbee is not installed on domoticz but on another PI?
I only see the option to enter an MQTT server in the Zigbee hardware tab but not where Zigbee2MQTT is installed.

[heggink]

When you refer to the zigbee2mqtt plugin, are you referring to the autodiscovery function? That is now the default / preferred integration. You can tell it where your mqtt broker is installed.

Sent from my SM-G980F using Tapatalk

[Satellietje]

I can fill in the MQTT broker and it also works.

When I install Zigbee2MQTT on the same PI as Domoticz I see the Custom button where I can manage the zigbee devices.

Because I installed Zigbee2MQTT on another Raspberry PI, this button is not there and can't access the devices, and the network map.

I think I should be able to indicate somewhere that the Zigbee2MQTT is on another Pi, so that I get to see the management console of the Zigbee devices.

[Satellietje]

I found it
The api_transport must be added manually

[heggink]

I am confused. When you use zigbee2mqtt, there is no button in domoticz since the devices are managed from the zigbee2mqtt web interface. The earlier python plugin did have an interface but that plugin doesn't use zigbee2mqtt.

What button are you referring to?

Sent from my SM-G980F using Tapatalk

[Satellietje]

[heggink]

Ah so you are still using the python plugin. Domoticz note has native autodiscovery functionality built in so you don't need the plugin anymore.

Sent from my SM-G980F using Tapatalk

[Satellietje]

I'm always a bit behind

New options often have some problems.

[heggink]

Sure, sensible. But sometimes, new things get built because the old has issues. I was on the plugin long time ago and faced a bunch of issues (the original 256 device linit followed by the new plugin framework that now has some remaining memory issues that dnpwwo is still working on). I moved to the new, native function months ago and noticed that even the beta was already very good. It's now in the latest stable release and, so far, I see no issues being reported for close to a month now.
Anyways, food for thought. Have a great weekend.

Sent from my SM-G980F using Tapatalk