ZBT-2 issues with Z2M

Configuration Zigbee
,
1

Hi,

I think i need some help, i used to have the Skyconnect adapter, which worked fine, but i decided to try to upgrade to the ZBT2.
I managed to get pretty much everything back after a long and hard struggle.

However it seems to keep crashing my Z2M

z2m: Failed to ping ‘Udenfor-Væglampe-Garage-Højre’ (attempt 1/1, ZCL command 0x00178801067f1499/11 genBasic.read([“zclVersion”], {“timeout”:10000,“disableResponse”:false,“disableRecovery”:true,“disableDefaultResponse”:true,“direction”:0,“reservedBits”:0,“writeUndiv”:false}) failed (sendZclFrameToEndpointInternal error))

zh:ezsp:uart: → Error: Error: {“sequence”:-1} after 10000ms

zh:ezsp:uart: Failed to reset on Error Frame: Error: Reset error: Error: {“sequence”:-1} after 10000ms

zh:ezsp:uart: → Error: Error: {“sequence”:1} after 4000ms

zh:ezsp:uart: -!- break waiting (1)

It seems to keep flipping my Z2M with restarts.

I have tried several firmware 7.4.4.3, 7.4.4.5 and 7.4.4.6 (current)
My Z2M version is 2.6.3

Im using EZSP v13
adapter: ezsp
baudrate: 460800
disabled_led: true
port: my device :wink:
rtscts: true

When i look into Nabu Casa’s documentation i seem stumble upon that they’re recommending the ember adapter, but i simply cant make it work properly since it spams this in the logs

Nov 28 16:35:23 MO-Zigbee2MQTT pnpm[968]: [2025-11-28 16:35:23] info: zh:ember:ezsp: Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for “0”. Nov 28 16:35:23 MO-Zigbee2MQTT pnpm[968]: [2025-11-28 16:35:23] info: zh:ember:ezsp: Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for “0”. Nov 28 16:35:23 MO-Zigbee2MQTT pnpm[968]: [2025-11-28 16:35:23] info: zh:ember:ezsp: Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for “0”. Nov 28 16:35:23 MO-Zigbee2MQTT pnpm[968]: [2025-11-28 16:35:23] info: zh:ember:ezsp: Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for “0”. Nov 28 16:35:23 MO-Zigbee2MQTT pnpm[968]: [2025-11-28 16:35:23] info: zh:ember:ezsp: Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for “0”. Nov 28 16:35:23 MO-Zigbee2MQTT pnpm[968]: [2025-11-28 16:35:23] info: zh:ember:ezsp: Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for “0”.

I have probed with the universal-silabs-flasher both outside my LXC in Proxmox and inside my LXC and it works fine.

What am i doing wrong?

It also seems to have a distaste for the Hue Appear outdoor lamps.

2

When I see route error and you know there was a major disruption in the force, I would be tempted to wait and see if it settles, or power down all the routing devices and once all were down, turn them back on to pick new routes starting closer to the ZBT-2 and working out.
¯\(ツ)/¯

3

Are you using a combination of DHCP dynamic and static IP addresses? Any non-standard network configurations such as VPN etc? Not enough info.
A full power down sound like a good idea to refresh everything.

4

Those are zigbee route errors from a usb coordinator. No IP involvement at all.

5

For ZBT-2, its should be set to ember.

Also, just an FYI:

6

If i start using the ember adapter it complains about the route errors - also my devices become unusually unstable

I changed back now to ZBT-1 - everything just works instantly… both with ember and ezsp - the ZBT-2 is very unstable for me - what firmware are you using ?

7

Really glad to see I’m not the only one not that impressed with ZBT-2!

Performs in quite a similar way here - not that stable. ZBT-1 has been solid up until now, and after switching to ZBT-2 the signal to many of the devices feels not as good.
One thing I do notice: the LQIs reported right now don’t seem to be accurate. There are some switches that I use and are reporting 40-60 (so they should be unreachable), but respond very snappy despite that.
Will give it a day or two to see how things settle. If it doesn’t change much - I might go back to ZBT-1.

8

i would very much like to hear what your experience is :slight_smile:

I must say - after plugging in the ZBT-1 everything just seems calm and stable - im very dissapointed with the new antenna

9

My god I’ve been pulling my hair out with this damn thing … tried every option and tried letting the network settle for days but wow I’ve never had so many issue : (