Can I please get a hand installing & using my Sonoff Zigbee 3 Plus to work with Zigbee2MQTT?
I’ve got the firmware updated. I’ve got the dongle recognised in HA OS from my VM running from a Synology 920+ on DSM7x.
ZHA recognises it - but if I use that it instantly kills any hope of using Zigbee2MQTT. Thusly, I have not clicked on ‘configure’. If I try to set up Z2Mqtt (configure tab) it looks nothing alike to the ones shown in videos, so it seems I have a very different thing going, at least judging by the configuration tab.
Below is my hardware tab pertaining to my Dongle+
ttyUSB0/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_8882c180ba5fec118985365f25bfaa52-if00-port0
Subsystem:tty
Device path:
/dev/ttyUSB0
ID:
/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_8882c180ba5fec118985365f25bfaa52-if00-port0
Under Attributes: it states…
DEVLINKS: >-
/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_8882c180ba5fec118985365f25bfaa52-if00-port0
/dev/serial/by-path/pci-0000:00:05.0-usb-0:1:1.0-port0
DEVNAME: /dev/ttyUSB0
DEVPATH: /devices/pci0000:00/0000:00:05.0/usb2/2-1/2-1:1.0/ttyUSB0/tty/ttyUSB0
ID_BUS: usb
ID_MODEL: Sonoff_Zigbee_3.0_USB_Dongle_Plus
ID_MODEL_ENC: Sonoff\x20Zigbee\x203.0\x20USB\x20Dongle\x20Plus
ID_MODEL_ID: ea60
ID_PATH: pci-0000:00:05.0-usb-0:1:1.0
ID_PATH_TAG: pci-0000_00_05_0-usb-0_1_1_0
ID_REVISION: ‘0100’
ID_SERIAL: ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_8882c180ba5fec118985365f25bfaa52
ID_SERIAL_SHORT: 8882c180ba5fec118985365f25bfaa52
ID_TYPE: generic
ID_USB_DRIVER: cp210x
ID_USB_INTERFACES: ‘:ff0000:’
ID_USB_INTERFACE_NUM: ‘00’
ID_VENDOR: ITead
ID_VENDOR_ENC: ITead
ID_VENDOR_ID: 10c4
MAJOR: ‘188’
MINOR: ‘0’
SUBSYSTEM: tty
TAGS: ‘:systemd:’
USEC_INITIALIZED: ‘83284241532’
Now, as far as I can tell - the above is all good to go. But I will add, the dongle+ was not recognised for several days. It seems if I dare to unplug it, it loses everything and doesn’t come back for seemingly days… I have no idea why it doesn’t register for days and then suddenly, out of the blue, is recognised.
So moving on to ZHA (which I don’t want to use, as I want to start learning & using MQTT) it seems to have acknowledged the existence of the Dongle+ but I have not done anything with it as yet… (partly because I’m petrified of losing it for days on end again).
Moving on to MQTT…
I have set up a standard & local user for the broker.
The YAML for the Mosquitto broker reads as:
logins:
require_certificate: false
certfile: fullchain.pem
keyfile: privkey.pem
customize:
active: true
folder: mosquitto
The settings, under ‘Network’ (of mosquitto broker) are as follows:
- 1883 / tcp — “normal MQTT”
- 1884 / tcp — “MQTT over WebSocket”
- 8883 / tcp — “Normal MQTT with SSL”
- 8884 / tcp — “MQTT over WebSocket with SSL”
However, when I click on the ‘log’ tab, I am confronted with the following, which repeats over & over.
[13:13:42] INFO: Starting mosquitto MQTT broker…
1654172022: Error: Unable to open include_dir ‘/share/mosquitto’.
1654172022: Error found at /etc/mosquitto/mosquitto.conf:36.
[13:13:42] INFO: Successfully send discovery information to Home Assistant.
[13:13:42] INFO: Successfully send service information to the Supervisor.
[13:13:43] INFO: Starting mosquitto MQTT broker…
1654172023: Error: Unable to open include_dir ‘/share/mosquitto’.
1654172023: Error found at /etc/mosquitto/mosquitto.conf:36.
[13:13:43] INFO: Successfully send discovery information to Home Assistant.
I am aware there is an issue with it using the ‘include_dir/…’ but I am uncertain how to begin resolving this.
Moving on to the Zigbee2MQTT…
The initial Configuration tabs shows the config broken in to separate elements; socat, mqtt & serial.
SOCAT:
enabled: true
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: ‘-d -d’
log: false
frontend:
port: 8099
MQTT
base_topic: zigbee2mqtt
user: xxx
password: xxx
server: http://my.ip.add.ress:1883
SERIAL
port: /dev/ttyUSB0
The NETWORK tab of Zigbee2MQTT shows the following:
- 8485 / tcp — Socat tcp-listen port
The LOG tab for Zigbee2MQTT shows the following information, again, repeating over & over…
Zigbee2MQTT:info 2022-06-02 13:21:20: Stopped zigbee-herdsman
[13:21:22] INFO: Handing over control to Zigbee2mqtt Core …
[email protected] start
node index.js
Zigbee2MQTT:info 2022-06-02 13:21:27: Logging to console and directory: ‘/config/zigbee2mqtt/log/2022-06-02.13-21-27’ filename: log.txt
Zigbee2MQTT:info 2022-06-02 13:21:27: Starting Zigbee2MQTT version 1.25.2 (commit #unknown)
Zigbee2MQTT:info 2022-06-02 13:21:27: Starting zigbee-herdsman (0.14.34)
Zigbee2MQTT:info 2022-06-02 13:21:28: zigbee-herdsman started (resumed)
Zigbee2MQTT:info 2022-06-02 13:21:28: Coordinator firmware version: ‘{“meta”:{“maintrel”:1,“majorrel”:2,“minorrel”:7,“product”:1,“revision”:20220219,“transportrev”:2},“type”:“zStack3x0”}’
Zigbee2MQTT:info 2022-06-02 13:21:28: Currently 0 devices are joined:
Zigbee2MQTT:warn 2022-06-02 13:21:28:permit_joinset totruein configuration.yaml.
Zigbee2MQTT:warn 2022-06-02 13:21:28: Allowing new devices to join.
Zigbee2MQTT:warn 2022-06-02 13:21:28: Setpermit_jointofalseonce you joined all devices.
Zigbee2MQTT:info 2022-06-02 13:21:28: Zigbee: allowing new devices to join.
Zigbee2MQTT:info 2022-06-02 13:21:28: Connecting to MQTT server at http://192.168.0.61:1883
Zigbee2MQTT:error 2022-06-02 13:21:32: MQTT failed to connect: read ECONNRESET
Zigbee2MQTT:error 2022-06-02 13:21:32: Exiting…
Zigbee2MQTT:info 2022-06-02 13:21:32: Stopping zigbee-herdsman…
Zigbee2MQTT:info 2022-06-02 13:21:42: Stopped zigbee-herdsman
[13:21:43] INFO: Handing over control to Zigbee2mqtt Core …
[email protected] start
node index.js
Zigbee2MQTT:info 2022-06-02 13:21:48: Logging to console and directory: ‘/config/zigbee2mqtt/log/2022-06-02.13-21-48’ filename: log.txt
So, if anyone could kindly assist me in understanding & getting this working, I would be forever indebted to you 
