Can't get ZBT-2 working

Configuration Zigbee
,
1

From many years with Hubitat, I’m trying to get HA working on a BeeLink Ser5 mini PC.
I bought a ZBT-2 thinking it would be straight forward to setup. Apparently not.
HA has setup okay and is at version 17.0.

When I click the ‘Open Web UI’ on zigbee2mqtt it always opens the Onboarding page. From reading many articles, it should open a page where I can pair devices.

HA detected the ZBT-2 and I clicked add which installed the zigbee firmware.
The ZBT-2 has a blue slow pulsing led.
I’ve tried install Mosquitto first and then zigbee2mqqt. uninstalled and then tried the other way round. Neither have worked.
I’ve tried plugging it into different usb ports - no different.
It is on the supplied 1.2m lead to get it away from the Beelink Ser5.

One thing I’ve read somewhere was about it having trouble with blue usb ports (3.0?) The Beelink only has blue USb ports!

I’ve tried using chatGPT to solve the problem, but that just leads me round and round in circles for hours and gets nowhere fast.

How can I start to debug the issue?

2

Have you filled in all the fields in the Onboarding page? Unless you do that, Z2M won’t start up because it has no idea what adapter you’re using or the IP address of your MQTT broker.

3

If Z2M is a bit more complication than you need, try ZHA. It’s a bit more built in and makes less assumptions about what you know or don’t know. There are HA Docs to get you going.

4

In the video/instructions I’ve found they said to leave the defaults, so all I’ve selected is the only device with ZBT-2 in its name, and zstack for the coordinator…

The user and password are greyed out, but I managed to enter them into the yaml file.

These are the values. I’ve had to take links out because they cause an error on this page.

Found Devices

usb-Nabu_Casa_ZBT-2_DCB4D90CA9B8-if00 (Nabu Casa), /dev/ttyACM0, unknown
Optionally allows to configure coordinator port and type (if known) automatically.

Coordinator/Adapter Port/Path
/dev/ttyACM0
Coordinator/Adapter Type/Stack/Driver

zstack
Coordinator/Adapter Baudrate

115200
Can be ignored for networked coordinators (TCP).
Coordinator/Adapter Hardware Flow Control (“rtscts: true”)

Can be ignored for networked coordinators (TCP).

Closest WiFi Channel
0
Optionally set to your closest WiFi channel to pick the best value for “Network channel” below.
Network Channel
11

Generate network?
Network Key
77,26,207,12,8,152,219,78,125,28,56,210,88,105,169,197
Network PAN ID
33896
Network Extended PAN ID
114,57,63,110,76,83,75,50

MQTT Base Topic
zigbee2mqtt
MQTT Server
mqtt://core-mosquitto:1883
MQTT User
addons
Optional. Set only if using authentication.
MQTT Password
••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
Optional. Set only if using authentication.

Frontend enabled?
Frontend Port
8099

Home Assistant enabled?

Log Level

debug

5

I had thought of doing that just to get me going, but I got zigbee2mqtt working on a RPI a couple of years ago so thought I should be able to get it working on here.

I’d like to persist if anyone has the patience to help, but failing that, I’ll revert to ZHA.
I just prefer the addition ‘element’? you get with mqtt.

1 Like
6

Just an update for anyone having the same trouble.

Three things were causing the problem

  1. The baud rate has to be set to Baudrate: 460800.
    The advice I found about leaving fields as default meant that the baud rate was 115200

  2. rtscts: must be checked/enabled
    I think I may have unticked this whilst messing about with the field values

  3. I had made a simple mistype causing a mismatch with user name between zigbee2mqtt and Mosquitto.

The blue led on top of the ZBT-2 is no longer pulsing and Open web UI now opens the zigbee2mqtt dashboard.

Happy days

2 Likes