We moved to a new flat. I am not sure how this is all related to the issues that I am about to explain, but let's go.
So moved all our stuff over to the new flat. As one of the last steps I grabbed all the smart bulbs and switches, and twisted them in.
Started up my vm (home01) and all the buttons worked. This was the setup at that time:
I suddenly realised that sometimes the zigbee2mqtt serive is loosing connection with the SLZB06. I had to re-start z2m. I then looked at the web interface of the coordinator, and started flasing new firmwares. I ended up flashing the latest firmwares:
- Coordinator (CC2652P): 20240710
- I used this version because the newer ones were marked as "Dev firmware".
- SLZB OS: v3.3.1
But I still encountered restarts, and also seen all my devices lost.
So then I decided to use a USB plug to power SLZB06:
But I think I still need to deal with lost devices. So first I will want to re-create the internal DB. But before that, let's see what I have if I started the z2m service:
May 02 08:57:14 home01 systemd[1]: Started zigbee2mqtt.
May 02 08:57:14 home01 node[7389]: Starting Zigbee2MQTT without watchdog.
May 02 08:57:14 home01 node[7389]: Zigbee2MQTT requires node version ^20.15.0 || ^22.2.0 || ^24, you are running v25.9.0!
May 02 08:57:15 home01 node[7389]: [2026-05-02 08:57:15] info: z2m: Logging to console, file (filename: log.log)
May 02 08:57:15 home01 node[7389]: [2026-05-02 08:57:15] info: z2m: Starting Zigbee2MQTT version 2.9.2 (commit #
May 02 08:57:15 home01 node[7389]: )
May 02 08:57:15 home01 node[7389]: [2026-05-02 08:57:15] info: z2m: Starting zigbee-herdsman (10.0.5)
May 02 08:57:15 home01 node[7389]: [2026-05-02 08:57:15] info: zh:zstack:znp: Opening TCP socket with 192.168.0.220:6638
May 02 08:57:15 home01 node[7389]: [2026-05-02 08:57:15] info: zh:zstack:znp: Socket connected
May 02 08:57:15 home01 node[7389]: [2026-05-02 08:57:15] info: zh:zstack:znp: Socket ready
May 02 08:57:15 home01 node[7389]: [2026-05-02 08:57:15] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
May 02 08:57:16 home01 node[7389]: [2026-05-02 08:57:16] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
May 02 08:58:08 home01 node[7389]: [2026-05-02 08:58:08] info: z2m: zigbee-herdsman started (restored)
May 02 08:58:08 home01 node[7389]: [2026-05-02 08:58:08] info: z2m: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20240710,"transportrev":2},"type":"ZStack3x0"}'
May 02 08:58:08 home01 node[7389]: [2026-05-02 08:58:08] info: z2m: bathroom-switch (0x8c65a3fffe982251): Not supported (Unknown)
May 02 08:58:08 home01 node[7389]: [2026-05-02 08:58:08] info: z2m: Currently 1 devices are joined.
May 02 08:58:08 home01 node[7389]: [2026-05-02 08:58:08] info: z2m: Connecting to MQTT server at mqtt://localhost
May 02 08:58:08 home01 node[7389]: [2026-05-02 08:58:08] info: z2m: Connected to MQTT server
May 02 08:58:08 home01 node[7389]: [2026-05-02 08:58:08] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
May 02 08:58:08 home01 node[7389]: [2026-05-02 08:58:08] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bathroom-switch', payload '{"battery":100,"update_available":true}'
May 02 08:58:08 home01 node[7389]: [2026-05-02 08:58:08] info: z2m: Zigbee2MQTT started!
And tbh, it took a lot of time to start.
Couple of warnings: - I am not running the correct node version (25 looks too much)
Now I will try to check what could be wrong:
First, I am doing a coordinator check as recommended
[matelakat@home01 ~]$ mosquitto_pub -t 'zigbee2mqtt/bridge/request/coordinator_check' -m '{}'
Response (from logs)
May 02 09:02:16 home01 node[7389]: [2026-05-02 09:02:16] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/coordinator_check', payload '{"data":{"missing_routers":[]},"status":"ok"}'
Ok, that's good. Now I will try to re-set the db.
Files live under /var/lib/zigbee2mqtt/
[root@home01 /]# cd
[root@home01 ~]# pwd
/root
[root@home01 ~]# mkdir backup
[root@home01 ~]# cd backup/
[root@home01 backup]# mv /var/lib/zigbee2mqtt/database.db ./
[root@home01 backup]# mv /var/lib/zigbee2mqtt/coordinator_backup.json ./
[root@home01 backup]# mv /var/lib/zigbee2mqtt/state.json ./
Then started the service:
May 02 09:17:51 home01 systemd[1]: Started zigbee2mqtt.
May 02 09:17:51 home01 node[7663]: Starting Zigbee2MQTT without watchdog.
May 02 09:17:51 home01 node[7663]: Zigbee2MQTT requires node version ^20.15.0 || ^22.2.0 || ^24, you are running v25.9.0!
May 02 09:17:52 home01 node[7663]: [2026-05-02 09:17:52] info: z2m: Logging to console, file (filename: log.log)
May 02 09:17:52 home01 node[7663]: [2026-05-02 09:17:52] info: z2m: Starting Zigbee2MQTT version 2.9.2 (commit #
May 02 09:17:52 home01 node[7663]: )
May 02 09:17:52 home01 node[7663]: [2026-05-02 09:17:52] info: z2m: Starting zigbee-herdsman (10.0.5)
May 02 09:17:52 home01 node[7663]: [2026-05-02 09:17:52] info: zh:zstack:znp: Opening TCP socket with 192.168.0.220:6638
May 02 09:17:52 home01 node[7663]: [2026-05-02 09:17:52] info: zh:zstack:znp: Socket connected
May 02 09:17:52 home01 node[7663]: [2026-05-02 09:17:52] info: zh:zstack:znp: Socket ready
May 02 09:17:52 home01 node[7663]: [2026-05-02 09:17:52] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
May 02 09:17:53 home01 node[7663]: [2026-05-02 09:17:53] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
May 02 09:18:13 home01 node[7663]: [2026-05-02 09:18:13] info: zh:controller: Wrote coordinator backup to '/var/lib/zigbee2mqtt/coordinator_backup.json'
May 02 09:18:14 home01 node[7663]: [2026-05-02 09:18:14] info: z2m: zigbee-herdsman started (resumed)
May 02 09:18:14 home01 node[7663]: [2026-05-02 09:18:14] info: z2m: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20240710,"transportrev":2},"type":"ZStack3x0"}'
May 02 09:18:14 home01 node[7663]: [2026-05-02 09:18:14] info: z2m: Currently 0 devices are joined.
May 02 09:18:14 home01 node[7663]: [2026-05-02 09:18:14] info: z2m: Connecting to MQTT server at mqtt://localhost
May 02 09:18:14 home01 node[7663]: [2026-05-02 09:18:14] info: z2m: Connected to MQTT server
May 02 09:18:14 home01 node[7663]: [2026-05-02 09:18:14] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
May 02 09:18:14 home01 node[7663]: [2026-05-02 09:18:14] info: z2m: Zigbee2MQTT started!
Now I will allow devices to join:
[matelakat@home01 ~]$ mosquitto_pub -t 'zigbee2mqtt/bridge/request/permit_join' -m '{"time": 254, "device": "bathroom-switch"}'
May 02 09:20:37 home01 node[7663]: [2026-05-02 09:20:37] error: z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'Device 'bathroom-switch' does not exist'
May 02 09:20:37 home01 node[7663]: [2026-05-02 09:20:37] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"Device 'bathroom-switch' does not exist","status":"error"}'
Ok, trying it without friendly name
[matelakat@home01 ~]$ mosquitto_pub -t 'zigbee2mqtt/bridge/request/permit_join' -m '{"time": 254}'
And after that, I pushed a button on the ikea switch, and also on the sonoff buttons.
I got them paired.
Ok, let me try vallhorn. Clanker says that I need to push the pairing button 4 times within 5 seconds. then red light indicates pairing mode. That went well:
May 02 15:51:21 home01 node[7663]: [2026-05-02 15:51:21] info: zh:controller: Succesfully interviewed '0xf84477fffe7df6d3'
May 02 15:51:21 home01 node[7663]: [2026-05-02 15:51:21] info: z2m: Successfully interviewed 'corridor_motion_sensor', device has successfully been paired
Now the lights.
I will need to turn them on and off 6 times. Let me try doing that. Worked. Basically I always need to make sure I enter the system to pairing mode.
The other smart bulbs went on and off as well.