Zigbee2mqtt not communicating

Configuration
1

I tried to install a Sonoff Zigbee dongle and use the Zigbee2mqtt service but it doesn’t seem to be working:

image
image882×666 39.3 KB

The configuration page http://192.168.3.2:12000/ is also unavailable…

What can I do?

2

docker logs gladys-z2m-zigbee2mqtt

[2024-08-02 14:09:01] info:     z2m: Logging to console, file (filename: log.log)
[2024-08-02 14:09:01] info:     z2m: Starting Zigbee2MQTT version 1.39.1 (commit #e132316)
[2024-08-02 14:09:01] info:     z2m: Starting zigbee-herdsman (0.55.3)
[2024-08-02 14:09:03] warning:  zh:ezsp: Deprecated driver 'ezsp' currently in use, 'ember' will become the officially supported EmberZNet driver in next release. If using Zigbee2MQTT see https://github.com/Koenkk/zigbee2mqtt/discussions/21462
[2024-08-02 14:09:03] error:    zh:ezsp:uart: Error: <-- CRC error: bf7e|bf|ffff
[2024-08-02 14:09:03] error:    zh:ezsp:uart: Error while parsing to NpiFrame 'Error: <-- CRC error: bf7e|bf|ffff
    at Frame.checkCRC (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/frame.ts:87:19)
    at SerialDriver.onParsed (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:167:19)
    at Parser.emit (node:events:517:28)
    at Parser._transform (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/parser.ts:50:26)
    at Parser.Transform._write (node:internal/streams/transform:175:8)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Parser.Writable.write (node:internal/streams/writable:337:10)
    at SerialPort.ondata (node:internal/streams/readable:809:22)
    at SerialPort.emit (node:events:517:28)'
[2024-08-02 14:09:07] info:     z2m: zigbee-herdsman started (resumed)
[2024-08-02 14:09:07] info:     z2m: Coordinator firmware version: '{"meta":{"maintrel":"3 ","majorrel":"6","minorrel":"10","product":8,"revision":"6.10.3.0 build 297"},"type":"EZSP v8"}'
[2024-08-02 14:09:07] info:     z2m: Currently 0 devices are joined:
[2024-08-02 14:09:07] info:     z2m: Zigbee: disabling joining new devices.
[2024-08-02 14:09:08] info:     z2m: Connecting to MQTT server at mqtt://localhost:1884
[2024-08-02 14:09:08] error:    z2m: MQTT error: Connection refused: Not authorized
[2024-08-02 14:09:08] error:    z2m: MQTT failed to connect, exiting...
[2024-08-02 14:09:08] info:     z2m: Stopping zigbee-herdsman...
[2024-08-02 14:09:09] info:     zh:controller: Wrote coordinator backup to '/app/data/coordinator_backup.json'
[2024-08-02 14:09:09] info:     z2m: Stopped zigbee-herdsman
Using '/app/data' as data directory
Starting Zigbee2MQTT without watchdog.
3

docker logs gladys-z2m-mqtt


1722607922: New connection from ::1:59344 on port 1884.
1722607922: Client gladys-main-instance-816862 disconnected, not authorised.
1722607924: New connection from ::1:59346 on port 1884.
1722607924: Client mqttjs_e19f996c disconnected, not authorised.
4

@Xenicle Hello !

The error is here :

[quote=« Xenicle, post:2, topic:9027 »]
` zh

1 Like
5

Hello @pierre-gilles !
The dongle is out of the box, I haven’t touched the firmware…

Do I need to update it?

(Otherwise I had chosen the wrong dongle at first; I chose the P and switched to the E which is the right one…)

6

That might be a lead ^^

The Zigbee2mqtt website can be a good source of advice: https://www.zigbee2mqtt.io/

Their forum too: Koenkk/zigbee2mqtt · Discussions · GitHub

The GitHub issues: GitHub · Where software is built

Which hardware are you on otherwise?

The USB port needs to be properly powered (Pi ports are sometimes underpowered, for example)

7

Ah! There’s a good chance that’s it — I’m on a Raspberry Pi 3…

8

You have all of Zigbee2mqtt’s advice on this page:

https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html

You have, in particular, this advice for Raspberry Pi:

Screenshot 2024-08-02 at 17.40.15
Screenshot 2024-08-02 at 17.40.152078×700 83.5 KB

9

dmesg | grep volt doesn’t return anything for me…

10

Some things to try:

  • Try another USB port
  • Use a USB extension cable or, better, a powered USB hub
  • Update the dongle’s firmware
11

OK I’ll look into that, thanks!

By the way, is it normal to have the « unauthorised connection » entries in the different logs?

12

Ah, you’re right, I hadn’t gone further than the first issue!

In fact that might be the problem, it looks a lot like another recent issue I saw here:

You may have put Zigbee2mqtt into an unstable state by selecting the wrong dongle, maybe purging everything to start from scratch would be wiser:

1 Like
13

Ok thanks, I’m on it ^^

1 Like
14

That was it! :
![image|690x190](upload://xq9BntsYXtQVigfmGMS0QlN

2 Likes
15

Excellent! Nice setup!

16

@pierre-gilles Maybe that should be added to the docs?
Or something to change in the integration. It seems the dongle change isn’t being taken into account…

17

I think it’s indeed a bug in the integration; since the new UI the cleanup isn’t performed properly when the integration is disabled.

I created an issue:

2 Likes
18

Indeed, there was a bug in the current integration — I can reproduce it on my end!

I’ve created a PR to fix the issue.

@cicoub13 @AlexTrovato if you have time to take a look :wink:

2 Likes