Page 2 of 2

Re: Cannot get zigbee running

Posted: Friday 07 February 2025 19:50
by hjzwiers
I tested with the new plugs (contact must be made to the Sonoff) ..... no contact is made

I deleted the added plugin from domoticz (did a full restart of the PC) and reset installed the zigbee2MQTT plug in. I need the basics to work.

I see now in the logging that the application cannot make a connection to the Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2, although I see it listed in the devices.

I have filled the connections properly and now I am checking if I as a user can access the Sonoff, or I must flash the Sonoff

Re: Cannot get zigbee running

Posted: Friday 07 February 2025 21:05
by waltervl
Ah just read this, your fourth topic about not being able to get zigbee running...

Re: Cannot get zigbee running

Posted: Friday 07 February 2025 22:12
by Xenomes
hjzwiers wrote: Tuesday 04 February 2025 12:52 server: mqtt://192.168.2.71:1883
I have in my config of zigbee2mqtt the IP of the container running mqtt.

Code: Select all

mqtt://172.17.0.*

Re: Cannot get zigbee running

Posted: Saturday 08 February 2025 13:29
by jannl
You should use the ip of the pi. The ip of the container is nornally only visible from within the container.

Re: Cannot get zigbee running

Posted: Sunday 09 February 2025 10:56
by hjzwiers
Got it all working, the main issue was I had a wrong firmware on my Sonoff, so I made the move to a different computer, and had to flash a few times.

It does het a bit frustrating sometimes, when things go wrong somewhere in the chain ....

Thanks for all the help!

Re: Cannot get zigbee running

Posted: Sunday 09 February 2025 11:29
by jannl
Don't change too many things at once, makes debugging a lot more difficult if something fails.

Re: Cannot get zigbee running

Posted: Tuesday 18 March 2025 12:03
by alkempter
Hi,
defining a "MQTT Client Gateway with LAN interface" is not enough, you also need a "MQTT Auto Discover Client Gateway with LAN interface"
Make sure to create in Domoticz hardware a "MQTT Auto Discover Client Gateway with LAN interface" wich has a discovery topic that ist different from your Gateway prefix.
There should also be a line (I have it below the homeassistant: in configuration.yaml) that says
discovery_topic: .......
which corresponds the discovery topic in your "MQTT Auto Discover Client Gateway with LAN interface"
If you are trying with the new version 2, you also need to specify in configuration.yaml the protocol your USB dongle uses. e.g.
serial:
adapter: zstack
(this is right if you are using the ZBDongle-P dongle)
or
serial:
adapter: ember
(in case you are using the ZBDongle-E dongle)

My output of sudo ls -l /dev/serial/by-id is
total 0
lrwxrwxrwx 1 root root 13 Mar 17 16:06 usb-0658_0200-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Mar 17 16:01 usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 -> ../../ttyUSB0

(I have also an adapter for zWave).

My working (docker) adapter for the ZBDongle-P definitions are different (I add only parts of the files).
docker-compose.yml
devices:
# Make sure this matched your adapter location
# - /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018ED3DDF-if00:/dev/ttyACM0
- dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0:/dev/zigbee

configuration.yaml
homeassistant:
enabled: true
discovery_topic: domoadzigbee
mqtt:
base_topic: domozigbee
server: http://192.168.0.103:1883

Not sure if 'if enabled: true' is right, but it works.

Cheers
Al