Domoticz

Dave21w wrote: ↑Friday 20 January 2023 17:14 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 running, after doing npm start, based on the output I've included below? The first three lines (after npm start) have the 'Zigbee2MQTT' in green, the remaining lines have it in red.

Zigbee2MQTT:info 2023-01-20 14:14:17: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2023-01-20.14-14-17' filename: log.txt
Zigbee2MQTT:info 2023-01-20 14:14:17: Starting Zigbee2MQTT version 1.29.2 (commit #bb3e8f6)
Zigbee2MQTT:info 2023-01-20 14:14:17: Starting zigbee-herdsman (0.14.83-hotfix.0)
Zigbee2MQTT:error 2023-01-20 14:14:38: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-01-20 14:14:38: Failed to start zigbee
Zigbee2MQTT:error 2023-01-20 14:14:38: Check https://www.zigbee2mqtt.io/guide/instal ... start.html for possible solutions
Zigbee2MQTT:error 2023-01-20 14:14:38: Exiting...
Zigbee2MQTT:error 2023-01-20 14:14:39: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:103:27)
at Controller.start (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
at Zigbee.start (/opt/zigbee2mqtt/lib/zigbee.ts:58:27)
at Controller.start (/opt/zigbee2mqtt/lib/controller.ts:101:27)
at start (/opt/zigbee2mqtt/index.js:107:5)

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 USB0 - even though I'd unplugged it some time ago. I deleted the Hardware for it, restarted, end then Zigbee2MQTT worked. I'm now able to run the front end, and join Zigbee devices and control them from there.

But... I can't (yet) see them in Domoticz, as Devices. Do I need to use either of the MQTT Client Gateway... Hardware? Or...?

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 update button, this will force a refresh and if there are any devices in the broker you should at least see them get detected in the Domoticz log

Dave21w wrote: ↑Friday 20 January 2023 20:41 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 update button, this will force a refresh and if there are any devices in the broker you should at least see them get detected in the Domoticz log

Odd. I've done that, using 'zigbee2mqtt' as the Auto Discovery Prefix, 'localhost' for the Remote Address (everything running on the same RPi3), and 1883 for the Port, but no Devices appear. Tried updating the Hardware, and also tried restarting Domoticz. All I'm (still) getting are zwavejs2mqtt Devices.

I can see stuff under the topic 'zigbee2mqtt' in MQTT Explorer, under sub-headings for 'Bridge' and the name of the device I'm hoping to see turn up in Domoticz devices.

what do you have in the auto discovery prefix in domoticz ?

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

'zigbee2mqtt'

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 ?

Dave21w wrote: ↑Saturday 21 January 2023 9:06 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 Client Gateway with LAN interface
MQTT Client Gateway with LAN interface
zwave devices are reported in both MQTT Explorer (under 'domoticz_zw') and Domoticz, with 'MQTT Auto Disc' in the 'Hardware' column of Devices page.

For zigbee2mqtt I have:
MQTT Auto Discovery Client Gateway with LAN interface (a second instance)
Two devices are now being reported in MQTT Explorer, under 'zigbee2mqtt'.
But I can't find these zigbee devices being reported in Domoticz/Devices.

I don't understand why I need both of the MQTT...LAN interface 'Hardware' for zwave (see above), or what the distinction is between them.
All of these are pointed at localhost:1883.
But, do I also need another instance of 'MQTT Client Gateway with LAN interface' for zigbee2mqtt? (actually, I've tried that, but it doesn't fix this).

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 'discovery_topic' and 'base_topic' is; what does 'base_topic' mean / in what way is it different to 'discovery_topic'?

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 front end.

I'm a bit confused.

Furry wrote: ↑Saturday 21 January 2023 14:58 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 to make this work again. TBH I'm not sure what is contributing and what isn't.

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 ?

Dave21w wrote: ↑Saturday 21 January 2023 22:51 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 front end.

But it seems to need *all* the things to work. I have:
Two instances of MQTT Auto Discovery Client Gateway with LAN Interface (one each for zwave and zigbee)
Two instances of MQTT Client Gateway with LAN Interface (one each for zwave and zigbee)
One instance of Zigbee2MQTT plugin (for zigbee)

If I disable any one of these, things stop working.

I haven't fully understood the hierarchy or 'wiring' between these various entities yet, or what each is actually doing.
E.g. if I have installed zigbee2mqtt, why do I then also need a zigbee2mqtt python plugin? Is the latter actually a 'gateway''?

Hi Guys! IS there a definite guide on what are the steps to get the flow zigbee to domoticz working?
I have hardware on my desk but a lot of confusion on different forum on how to make it working....
Thanks
Diego