Third question...this time serious Sonoff Dongle-E and Zigbee2Mqtt

Installation
21

Disabled should be sufficient. I disable/enable to switch between zha/z2m.

22

Thank again for help. Removing ZHA was a solution. In my case simple disabling it didn’t work. Now I start “unfortunately” :slight_smile: rebuild ZB network but luckily only few devices.

1 Like
23

Guys, I have to ask you for help again. Using above advise i managed to run Z2MQTT. It worked and it probably would work still but I did something stupid. Using this tutorial (https://smarthomescene.com/guides/how-to-enable-thread-and-matter-support-on-sonoff-zbdongle-e/) I tried to turn on Thread on Sonoff Dongle. Now my Z2MQTT stoped to work. Device is not bricked. Steps which went OK was:

  1. Flashing firmware
  2. Starting Silicon Labs Multiprotocol Zigbee and OpenThread add on

Device is not bricked because after few attempts I reinstalled ZHA. Dongle works fine I can add zigbee device and it works. Fullstop. Thread integration sees Dongle as a Border Device. Fullstop. So I removed ZHA restarted again server , again tried with Z2MQTT. No luck.

Log looks like

[21:48:59] INFO: Preparing to start...
[21:49:00] INFO: Socat not enabled
[21:49:00] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2024-01-12 21:49:01: Logging to console and directory: '/config/zigbee2mqtt/log/2024-01-12.21-49-01' filename: log.txt
Zigbee2MQTT:info  2024-01-12 21:49:01: Starting Zigbee2MQTT version 1.35.1 (commit #unknown)
Zigbee2MQTT:info  2024-01-12 21:49:01: Starting zigbee-herdsman (0.30.0)
Assertion failed: Command (setConfigurationValue) returned unexpected state: [object Object]
Assertion failed: Command (setValue) returned unexpected state: 55
Error: {"address":0,"clusterId":32770,"sequence":2} after 10000ms
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35)
    at listOnTimeout (node:internal/timers:569:17)
    at processTimers (node:internal/timers:512:7)

Configuration looks now like that:

data_path: /config/zigbee2mqtt
socat:
  enabled: false
  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
mqtt:
  server: mqtt://core-mosquitto:1883
  user: mqtt_user
  password: xxx
serial:
  port: tcp://core-silabs-multiprotocol:9999
  adapter: ezsp
zigbee_herdsman_debug: false

What do you think. Did I mess completely up or there is some kind of solution?
Of course I know that i would need to rebuild Zigbee network but I have only 10 devices so it is not a problem.

25

Don’t.

If you want to use Thread don’t use that. The (Thread) devs recommend against it and instead recommend to use Apple or Google devices (depending on whether you’re an Apple or Google house).

The latest version of that add-on also has known problems with Z2M.

26

THX. Luckily I managed revert old firmware on ZB Dongle and magically all my devices started working again (except this one used to tests) . I resigned from Thread as of now. Only device with thread is Amazon Echo but there is no way to push HA and AMZN Echo work together in this topic. After number of attempts i managed to add sensor to Echo and it shows statuses and somehow I managed to show this sensor in HA but never managed to make status change (open/close) visible in HA. I will wait for other reasonable solution , maybe another cheap dongle only for thread.