Sorry been a bit busy today fitting a new loft hatch / ladder, I’m not sure why you don’t get any devices using the Auto option, are you seeing everything you have added when you use the plugin ? Yes, thanks, I now have all (two, so far) Zigbee devices working within Domoticz, and also the z2m fro ...

No MQTT Auto Disc instances are enabled for zigbee2mqtt. I may have been wrong about that part, i.e. that devices are enumerated without this. The Custom/Zigbee2MQTT page appears to have a tendency to 'go away' and/or need refreshing, to show devices. Setting MQTT Auto Disc.. enabled again appeared ...

This is odd. I installed Zigbee2MQTT Python plugin. Now I can find Zigbee devices in Domoticz, in the Custom/Zigbee2MQTT page. BUT only if zigbee2mqtt service (installed above) is *also* running. No MQTT Auto Disc instances are enabled for zigbee2mqtt. I can also use the devices from the Zigbee2MQTT ...

This is my configuration.yaml : homeassistant: false discovery_topic: zigbee2mqtt frontend: port: 8099 host: 0.0.0.0 permit_join: true mqtt: base_topic: zigbee2mqtt server: mqtt://localhost serial: port: /dev/ttyUSB0 advanced: network_key: ..... BTW, I don't know what the difference between ...

If you have left the rest of the zigbe2mqtt values as default in the z2m front end settings then I believe this should be fine, have you tried a reboot of the pi completely ? Yes, I've even shutdown and restarted, and I'm now running z2m as a service. For zwavejsmqtt I have: MQTT Auto Discovery ...

Dave21w wrote: ↑Friday 20 January 2023 22:31 what do you have in the auto discovery prefix in domoticz ?

'zigbee2mqtt'

Use the "MQTT Auto Discovery Client Gateway with LAN interface" and make sure you have the IP set for the machine where your MQTT server is (probably the same one as the rest I know) and the port is set correctly, after this if you don't see anything highlight the MQTT Auto option and click the ...

I have finally got this working. Just as I was beginning to think I might need to (re-)flash the Dongle.. Turns out there was a conflict with the RFXtrx433e on ttyUSB0. I didn't see anything in dmesg or ls-l ... to indicate this, but then I noticed that the Domoticz log was saying that it was on ...

Well without this bit frontend: port: 8099 host: 192.168.*.* where the host has to be your IP you will not get the z2m front end anyway Yes, I did try putting that in, but still couldn't get the front end from a browser on 192.168.*.* I'll try it again, though. Should Zigbee2MQTT actually be ...

from the cmd line on the pi type dmesg, you'l probably have to search a bit in the list you'll get but check to make sure the dongle is using USB0, mine shows like this usb 1-1.3.1: ch341-uart converter now attached to ttyUSB0 start of your yaml should look some thing like this homeassistant ...

Further to above: I have checked the Dongle, and I do have:
Zigbee 3.0 USB Dongle Plus / Model ZB dongle-P, with TI C2652P+CP2102N, and Coordinator firmware.

Well this is probably part of your problem, if you follow the instructions for installing zigbee2mqtt they are required, go back to this page https://www.zigbee2mqtt.io/guide/installation/01_linux.html And follow the instructions to the letter, your reference to installing the zigbee2mqtt plugin ...

Well this is probably part of your problem, if you follow the instructions for installing zigbee2mqtt they are required, go back to this page https://www.zigbee2mqtt.io/guide/installation/01_linux.html And follow the instructions to the letter, your reference to installing the zigbee2mqtt plugin ...

Have you followed the full install instructions and have node and npm installed too ? I did this: "Alternative 2: Install the Domoticz Zigbee2MQTT Python plugin Clone repository into your domoticz plugins folder cd domoticz/plugins git clone https://github.com/stas-demydiuk/domoticz-zigbee2mqtt ...

You can setup a second MQTT Autodiscover gateway to differ from the ZWave-JS-UI. If you want that you have to change in Zigbee2MQTT HomeAssistant_discovery_topic to something like "Zigbee" (instead of homeassistant) and use the same topic name as discovery topic in your Domoticz MQTT Autodiscover ...

This is some debug info. from the log: 2023-01-19 09:04:29.191 Zigbee2MQTT: [API] Request: [1] config_get({}) 2023-01-19 09:04:29.191 Zigbee2MQTT: [API] Response: [1] 2023-01-19 09:04:29.307 Zigbee2MQTT: [API] Request: [2] bridge_getstatus({}) 2023-01-19 09:04:29.307 Zigbee2MQTT: [API] Response: [2 ...

waltervl wrote: ↑Wednesday 18 January 2023 17:35 I am sorry I do not use Zigbee2MQTT but check the documentation and logging of it : https://www.zigbee2mqtt.io/guide/gettin ... stallation

Thanks but, unfortunately, my installation/configuration does not resemble that described in the link, e.g. I do not have a configuration.yaml.

waltervl wrote: ↑Wednesday 18 January 2023 16:23 Then something is wrong in Zigbee2MQTT

Any idea what? Could there be some more configuration to do, that I haven't done?
Or something more I should do to configure the dongle?

You can setup a second MQTT Autodiscover gateway to differ from the ZWave-JS-UI. If you want that you have to change in Zigbee2MQTT HomeAssistant_discovery_topic to something like "Zigbee" (instead of homeassistant) and use the same topic name as discovery topic in your Domoticz MQTT Autodiscover ...

You can use the Zigbee for Domoticz plugin which doesn't bring any additional layer https://github.com/zigbeefordomoticz/Domoticz-Zigbee and you can check the Wiki for installation here: https://zigbeefordomoticz.github.io/wiki/en-eng/Plugin_Installation.html Thanks, but unfortunately this didn't ...