Zigbee2MQTT 2.0.0-1 Lost Connection To ZBT-1

I sussed that and another error so it is now:

homeassistant:
  enabled: true
advanced:
  network_key:
    - 116
    - 96
    - 201
    - 167
    - 99
    - 168
    - 147
    - 53
    - 228
    - 247
    - 32
    - 178
    - 20
    - 205
    - 156
    - 210
  pan_id: 2108
  ext_pan_id:
    - 161
    - 35
    - 112
    - 39
    - 164
    - 70
    - 52
    - 249
serial:
  port: /dev/ttyUSB1
  adapter: zstack
homeassistant_legacy_entity_attributes: false
homeassistant_legacy_triggers: false
legacy_api: false
legacy_availability_payload: false
legacy: false

But I get the same error

It was ember and worked preiously set to that but if I use that then I get this error:

tarting Zigbee2MQTT without watchdog.
[2025-01-04 13:15:02] info: 	z2m: Logging to console, file (filename: log.log)
[2025-01-04 13:15:02] info: 	z2m: Starting Zigbee2MQTT version 2.0.0 (commit #unknown)
[2025-01-04 13:15:02] info: 	z2m: Starting zigbee-herdsman (3.2.1)
[2025-01-04 13:15:02] info: 	zh:adapter:discovery: Matched adapter: {"path":"/dev/ttyUSB1","manufacturer":"Nabu Casa","serialNumber":"6aca14c4533aef11a3352b1455516304","pnpId":"usb-Nabu_Casa_Home_Assistant_Connect_ZBT-1_6aca14c4533aef11a3352b1455516304-if00-port0","vendorId":"10c4","productId":"ea60"} => ember: 2
[2025-01-04 13:15:02] info: 	zh:ember: Using default stack config.
[2025-01-04 13:15:03] info: 	zh:ember: ======== Ember Adapter Starting ========
[2025-01-04 13:15:03] info: 	zh:ember:ezsp: ======== EZSP starting ========
[2025-01-04 13:15:03] info: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-01-04 13:15:03] info: 	zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2025-01-04 13:15:03] info: 	zh:ember:uart:ash: Serial port opened
[2025-01-04 13:15:03] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-01-04 13:15:04] info: 	zh:ember:uart:ash: ======== ASH connected ========
[2025-01-04 13:15:04] info: 	zh:ember:uart:ash: ======== ASH started ========
[2025-01-04 13:15:04] info: 	zh:ember:ezsp: ======== EZSP started ========
[2025-01-04 13:15:04] error: 	z2m: Error while starting zigbee-herdsman
[2025-01-04 13:15:04] error: 	z2m: Failed to start zigbee-herdsman
[2025-01-04 13:15:04] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-01-04 13:15:04] error: 	z2m: Exiting...
[2025-01-04 13:15:04] error: 	z2m: Error: Adapter EZSP protocol version (9) is not supported by Host [13-16].
    at EmberAdapter.emberVersion (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1403:19)
    at EmberAdapter.initEzsp (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:674:9)
    at EmberAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1533:24)
    at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:136:29)
    at Zigbee.start (/app/lib/zigbee.ts:69:27)
    at Controller.start (/app/lib/controller.ts:142:13)
    at start (/app/index.js:161:5)

Still you have wrong adapter

I understand that but cannot work out why as it was ember and set to that I get the error above.

Set to zstack I get the error previous to that.

It’s a Nabu Casa ZBT-1 I am using.

adapter: ezsp
2 Likes

Home Assistant Connect ZBT-1

Model No. NC-ZBT-9710

Radio Chipset Silicon Labs Multiprotocol EFR32MG21

Based on specification it’s Silicon Labs

EmberZNet adapters (Silicon Labs)

Perfect, many, many thanks as that solved it along with a restart. :smiley:

For anyone that gets the same or similar error, what I did was put this at the top of the Z2M config:

serial:
  port: #your apapter port info from hardware>connect
  adapter: ezsp
homeassistant_legacy_entity_attributes: false
homeassistant_legacy_triggers: false
legacy_api: false
legacy_availability_payload: false
legacy: false

And in the UI of MQTT add-on>config this:

serial:
  adapter: ezsp

Once that was done and HA restarted all came back as normal with no issues I can see.

Thanks again guys, appreciate the help.

1 Like

What’s interesting is that adapter option isn’t listed in the z2m documentation. https://www.zigbee2mqtt.io/guide/configuration/adapter-settings.html

  # Adapter type, allowed values: `zstack`, `ember`, `deconz`, `zigate` or `zboss`

I found it here: Home Assistant Connect ZBT-1

Yeah, I noticed that as well and thought it odd. I wasn’t sure if the ember and ezsp were the same thing or not a I’m really not familiar enough to think any differently.

But, it’s all working fine now and I cannot find any errors anywhere using ezsp as the adapter.

still not working with me, I restored to previous version, and it work normally.

FWIW, ezsp was deprecated in favor of ember (several months ago).

Reference

The second TIP box here:

Yet when I used ember it didnt work, used ezsp and it does. Seems very odd.

Can you confirm there were no other factors during the test that would have affected the result?

It seems pretty cut and dry from Ken’s posts above.

Which leads to either:

  1. The dongle needs a firmware update, or

  2. There’s a bug that needs reporting.

No, none.

All I changed was the adaptor and nothing else, when I changed it from zstack or ember to ezsp it just sparked to life and worked.

1 Like

You may wish to report it as a bug in Zigbee2MQTT’s Github repository. If the coordinator hardware is from Silicon Labs, it should work with ember.

I did look at the firmware update but, following the advice on that page I thought it best to follow the recommendation not to do that, apart from which, updating firmware always makes me jittery unless there’s good reasons to do that.

If Nabu Casa update it and the adapter needs changed to being ember that’s fine, it’s no big deal to sort that out as long as people know to do it.

What irked me a bit, though it’s really nobody’s fault, is that ezsp wasn’t even listed or so much as mentioned and yet, it appears to be what’s needed in this instance. Causing me to be bugging al you guys about it when it should have been easily sorted by myself.

Looks like this is a similar enough issue: EZSP to EMBER: TRADFRI E1745 unresponsive ¡ Issue #25283 ¡ Koenkk/zigbee2mqtt ¡ GitHub

Post your error message when you used adapter: ember then note that it only works with the depreciated ezsp option.

No problem, I have done that.

On second thought it might be best to create a new issue.