Home Assistent Yellow - Z2m

Installation
,
1

Just got my new yellow and wanted to run Z2M instead of ZHA. So I uninstalled ZHA, But I keep getting issues.
Any ideas?

[01:46:52] INFO: Preparing to start…
[01:46:53] INFO: Socat not enabled
[01:46:56] INFO: Starting Zigbee2MQTT…
Zigbee2MQTT:info 2023-08-03 01:47:02: Logging to console and directory: ‘/config/zigbee2mqtt/log/2023-08-03.01-47-02’ filename: log.txt
Zigbee2MQTT:info 2023-08-03 01:47:02: Starting Zigbee2MQTT version 1.32.2 (commit #unknown)
Zigbee2MQTT:info 2023-08-03 01:47:02: Starting zigbee-herdsman (0.17.2)
Zigbee2MQTT:error 2023-08-03 01:47:22: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-08-03 01:47:22: Failed to start zigbee
Zigbee2MQTT:error 2023-08-03 01:47:22: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions
Zigbee2MQTT:error 2023-08-03 01:47:22: Exiting…
Zigbee2MQTT:error 2023-08-03 01:47:23: Error: Connection not initialized
at Ezsp.execCommand (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:551:19)
at Ezsp.version (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:349:35)
at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:141:25)
at EZSPAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/adapter/ezspAdapter.ts:165:16)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
at Zigbee.start (/app/lib/zigbee.ts:59:27)
at Controller.start (/app/lib/controller.ts:101:27)
at start (/app/index.js:107:5)

Yaml file:
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:
base_topic: zigbee2mqtt
serial:
port: /dev/ttyAMA1
baudrate: 115200
rtscts: false
adapter: ezsp
`

2

That is not yaml formatted. But are you sure the device is /dev/ttyAMA1 ?

3

I am having the same issue.
I have a Home Assistant Yellow and have been struggling getting Z2M to work for me at all. It all seems like there is a missing connection between the z2m addon and the silabs-multiprotocol addon.
Home assistant Yellow uses /dev/ttyAMA1 for the zigbee coordinator. silabs-multiprotocol adds a socket://core-silabs-multiprotocol:9999 endpoint to connect z2m/zha to.

ZHA works fine. But Z2M will not work.

Here are both the z2m configurations I’ve tried, both give the same result:

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:
  base_topic: zigbee2mqtt
serial:
  port: /dev/ttyAMA1
  baudrate: 115200
  rtscts: false
  adapter: ezsp

Gives the following result:

[13:36:55] INFO: Preparing to start...
[13:36:55] INFO: Socat not enabled
[13:36:58] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-09-28 13:37:05: Logging to console and directory: '/config/zigbee2mqtt/log/2023-09-28.13-37-04' filename: log.txt
Zigbee2MQTT:info  2023-09-28 13:37:05: Starting Zigbee2MQTT version 1.33.0 (commit #unknown)
Zigbee2MQTT:info  2023-09-28 13:37:05: Starting zigbee-herdsman (0.18.5)
Zigbee2MQTT:error 2023-09-28 13:37:25: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-09-28 13:37:25: Failed to start zigbee
Zigbee2MQTT:error 2023-09-28 13:37:25: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-09-28 13:37:25: Exiting...
Zigbee2MQTT:error 2023-09-28 13:37:25: Error: Connection not initialized
    at Ezsp.execCommand (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:551:19)
    at Ezsp.version (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:349:35)
    at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:141:25)
    at EZSPAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/adapter/ezspAdapter.ts:165:16)
    at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
    at Zigbee.start (/app/lib/zigbee.ts:60:27)
    at Controller.start (/app/lib/controller.ts:101:27)
    at start (/app/index.js:107:5)

And using the silabs multiprotocol addon (it currently works correctly in ZHA):

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:
  base_topic: zigbee2mqtt
serial:
  port: socket://core-silabs-multiprotocol:9999
  adapter: ezsp

I get the following output in the logs:

[13:39:47] INFO: Preparing to start...
[13:39:47] INFO: Socat not enabled
[13:39:50] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-09-28 13:39:56: Logging to console and directory: '/config/zigbee2mqtt/log/2023-09-28.13-39-56' filename: log.txt
Zigbee2MQTT:info  2023-09-28 13:39:56: Starting Zigbee2MQTT version 1.33.0 (commit #unknown)
Zigbee2MQTT:info  2023-09-28 13:39:56: Starting zigbee-herdsman (0.18.5)
Zigbee2MQTT:error 2023-09-28 13:40:17: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-09-28 13:40:17: Failed to start zigbee
Zigbee2MQTT:error 2023-09-28 13:40:17: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-09-28 13:40:17: Exiting...
Zigbee2MQTT:error 2023-09-28 13:40:17: Error: Connection not initialized
    at Ezsp.execCommand (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:551:19)
    at Ezsp.version (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:349:35)
    at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:141:25)
    at EZSPAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/adapter/ezspAdapter.ts:165:16)
    at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
    at Zigbee.start (/app/lib/zigbee.ts:60:27)
    at Controller.start (/app/lib/controller.ts:101:27)
    at start (/app/index.js:107:5)

So, essentially zigbee2mqtt is not getting a connection to the zigbee coordinator at all in either case. My hunch is that this is an issue with the docker permissions not being properly set up in HAOS for the z2m addon. I’ve been overwhelmed just trying to brute force myself through this problem so I can’t tell for sure that this is the case.

4

I’ve somewhat reliably been able to generate the same type of log entries in the Silicon Labs Multiprotocol addon each time I restart Z2M:

Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b9:3fff:fee4:a928/veth3e7e90d/75
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b9:3fff:fee4:a928/veth3e7e90d/75
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b9:3fff:fee4:a928/veth3e7e90d/75
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b9:3fff:fee4:a928/veth3e7e90d/75
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b9:3fff:fee4:a928/veth3e7e90d/75
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b9:3fff:fee4:a928/veth3e7e90d/75

I’ll try disabling/stopping this addon and using /dev/ttyAMA1 directly but it’s not looking good…

5

Sorry for adding so much info… but i really am at my wits end with this.
I tried disabling the multiprotocol addon and connecting directly to /dev/ttyAMA1. With herdsman debugging enabled, I finally get a new error message that I haven’t seen before:

[13:52:13] INFO: Preparing to start...
[13:52:14] INFO: Socat not enabled
[13:52:14] INFO: Zigbee Herdsman debug logging enabled
[13:52:17] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:debug 2023-09-28 13:52:23: Loaded state from file /config/zigbee2mqtt/state.json
Zigbee2MQTT:info  2023-09-28 13:52:23: Logging to console and directory: '/config/zigbee2mqtt/log/2023-09-28.13-52-23' filename: log.txt
Zigbee2MQTT:debug 2023-09-28 13:52:23: Removing old log directory '/config/zigbee2mqtt/log/2023-09-27.23-54-30'
Zigbee2MQTT:info  2023-09-28 13:52:23: Starting Zigbee2MQTT version 1.33.0 (commit #unknown)
Zigbee2MQTT:info  2023-09-28 13:52:23: Starting zigbee-herdsman (0.18.5)
Zigbee2MQTT:debug 2023-09-28 13:52:23: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/config/zigbee2mqtt/coordinator_backup.json","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","databasePath":"/config/zigbee2mqtt/database.db","network":{"channelList":[11],"extendedPanID":[126,238,121,175,26,212,81,29],"networkKey":"HIDDEN","panID":15638},"serialPort":{"adapter":"ezsp","baudRate":115200,"path":"/dev/ttyAMA1","rtscts":false}}'
2023-09-28T11:52:24.013Z zigbee-herdsman:adapter Failed to validate path: 'Error: spawn udevadm ENOENT'
2023-09-28T11:52:24.017Z zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[9,69,234,13,225,167,192,187,155,4,106,174,151,246,102,36],"panID":15638,"extendedPanID":[126,238,121,175,26,212,81,29],"channelList":[11]},"serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/ttyAMA1","adapter":"ezsp"},"databasePath":"/config/zigbee2mqtt/database.db","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","backupPath":"/config/zigbee2mqtt/coordinator_backup.json","adapter":{"disableLED":false,"concurrent":null,"delay":null}}'
2023-09-28T11:52:24.022Z zigbee-herdsman:adapter:ezsp:uart Opening SerialPort with {"path":"/dev/ttyAMA1","baudRate":115200,"rtscts":false,"autoOpen":false}
2023-09-28T11:52:24.037Z zigbee-herdsman:adapter:ezsp:uart Serialport opened
2023-09-28T11:52:24.038Z zigbee-herdsman:adapter:ezsp:uart Uart reseting
2023-09-28T11:52:24.041Z zigbee-herdsman:adapter:ezsp:uart --> Write reset
2023-09-28T11:52:24.044Z zigbee-herdsman:adapter:ezsp:uart --> [1ac038bc7e]
2023-09-28T11:52:24.047Z zigbee-herdsman:adapter:ezsp:uart -?- waiting reset
2023-09-28T11:52:34.050Z zigbee-herdsman:adapter:ezsp:uart --> Error: Error: {"sequence":-1} after 10000ms
2023-09-28T11:52:34.052Z zigbee-herdsman:adapter:ezsp:driv Reset connection. Try 0
2023-09-28T11:52:34.053Z zigbee-herdsman:adapter:ezsp:driv Stop driver
2023-09-28T11:52:34.055Z zigbee-herdsman:adapter:ezsp:ezsp Stop ezsp
2023-09-28T11:52:34.057Z zigbee-herdsman:adapter:ezsp:ezsp Close ezsp
2023-09-28T11:52:34.060Z zigbee-herdsman:adapter:ezsp:driv Close driver
Error: Reset error: Error: {"sequence":-1} after 10000ms
    at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
    at Queue.executeNext (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
6

Do you try to use both ZHA and Z2M at the same time ?

7

Yes, I am not disabling ZHA while trying to get Z2M working. Is it common to not be able to use both?

8

You can’t use ZHA and Z2M at the same time using the same radio. If you want to run them at the same time, you will need a second radio, e.g. ZHA on the built-in radio and Z2M on a dongle.

9

I tried a new approach: I went ahead and uninstalled the multiprotocol firmware. After this, I restarted Z2M a couple times and now it finally runs!

[14:25:44] INFO: Preparing to start...
[14:25:45] INFO: Socat not enabled
[14:25:48] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-09-28 14:25:54: Logging to console and directory: '/config/zigbee2mqtt/log/2023-09-28.14-25-54' filename: log.txt
Zigbee2MQTT:info  2023-09-28 14:25:54: Starting Zigbee2MQTT version 1.33.0 (commit #unknown)
Zigbee2MQTT:info  2023-09-28 14:25:54: Starting zigbee-herdsman (0.18.5)
Assertion failed: Command (setConfigurationValue) returned unexpected state: [object Object]
Zigbee2MQTT:info  2023-09-28 14:25:58: zigbee-herdsman started (reset)
Zigbee2MQTT:info  2023-09-28 14:25:58: Coordinator firmware version: '{"meta":{"maintrel":"1 ","majorrel":"7","minorrel":"3","product":12,"revision":"7.3.1.0 build 176"},"type":"EZSP v12"}'
Zigbee2MQTT:info  2023-09-28 14:25:58: Currently 0 devices are joined:
Zigbee2MQTT:info  2023-09-28 14:25:58: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2023-09-28 14:25:59: Connecting to MQTT server at mqtt://core-mosquitto:1883
Zigbee2MQTT:info  2023-09-28 14:26:00: Connected to MQTT server
Zigbee2MQTT:info  2023-09-28 14:26:00: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
Zigbee2MQTT:info  2023-09-28 14:26:00: Started frontend on port 0.0.0.0:8099
Zigbee2MQTT:info  2023-09-28 14:26:00: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
Zigbee2MQTT:info  2023-09-28 14:26:00: Zigbee2MQTT started!
10

Thank you for clarifying this for me… What is the correct way of “disabling” ZHA?

edit: It seems like you are completely right. Z2M works as soon as I disable or reconfigure ZHA.

11

Choose disable in that menu

image
image982×446 27.1 KB

1 Like
12

Looking back, this seems so obvious. Thank you for explaining it. I must have missed the part about disabling ZHA when I researched the topic.

13

Is there any news?
I get Z2M running but not with the multiprotocol firmware, just with the regular Zigbee version.

Has anybody it running?

14

Have you read the thread?

Disable ZHA and try again.

15

Yes I read !
As I wrote I have it running !
Without multiprotcol firmware !

My question is if anybody has it running using the multi- protocol firmware (thread support) ( and not just the Zigbee firmware)

I‘m not speaking of zha, which must in all cases disabled

16

Hi alive1, i also have a HA Yellow and get the same error as you when trying to get Mqtt running. I tried disabling the ZHA integration but this has not fixed the issue for me.

Can i ask, did you need to uninstall the multi protocol firmware for your fix to work? Or was it simply disabling ZHA that fixed it for you?

Many Thanks Dan

17

I may be able to answer my own question! I just disabled it and then tried mqtt again and it started.

This is both great and annoying as i have matter devices that i would like to use as well as mqtt from my HA Yellow. Means i need to use something like my Apple Home Pod now as a thread router for my matter devices I think.

That said - massive thanks to this thread and to alive1.

I cant imagine there are many people using the HA yellows built in radio for z2mqtt if you need to figure this disabling / uninstalling multiprotocol firmware step out …