Shelly BLU Motion ZB (SBMO-103Z) cannot join with ConBee III (deconz adapter) - "unsupported source address mode: 3"
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- networking
Research direction
The errors come from the deconz frame parser, logged as zh:deconz:frameparser, on APS-DATA.indication frames: "unsupported source address mode: 3" and "Unsupported response reading for cluster ID '2'" (ZDO Node Descriptor). Start by finding where the source address mode is read and where ZDO responses are parsed in the zigbee-herdsman deconz adapter. Done means the join succeeds and the device is interviewed, which needs a reproduction with the SBMO-103Z or a captured frame to confirm the expected format.
Written by the indexing model from the issue text.
Description
What happened?
The Shelly BLU Motion ZB (SBMO-103Z) cannot join the network when using a ConBee III coordinator (deconz adapter).
The sensor is in Zigbee pairing mode (LED flashing purple), permit join is enabled, and the sensor is placed directly next to the coordinator (LQI 223). The device reaches the coordinator, but the deconz frame parser fails on every attempt with:
- "unsupported source address mode: 3"
- "Unsupported response reading for cluster ID '2'" (ZDO Node Descriptor request from the device)
The device retries about every 23 seconds (5 attempts) and then gives up. No "device joined" or "device announce" is ever logged.
Additional info: the same sensor also cannot be paired with a ConBee II in deCONZ/Phoscon.
All other 32 devices in the network work fine.
What did you expect to happen?
The device should join and be interviewed, as it is listed as supported (SBMO-103Z).
How to reproduce it (minimal and precise)
- Zigbee2MQTT 2.14.3 with ConBee III (deconz adapter)
- Enable permit join
- Press the button on the Shelly BLU Motion ZB 5 times (LED flashes purple)
- Device fails to join, errors appear in debug log
Zigbee2MQTT version
2.14.3
Adapter firmware version
0x26510900
Adapter
ConBee III
Setup
Proxmox LXC (Debian trixie), Node.js 24.22.3, zigbee-herdsman 11.2.0, zigbee-herdsman-converters 26.125.0
Device database.db entry
No response
Debug log
[2026-11-13 17:17:50] info: z2m: Zigbee: allowing new devices to join.
[2026-11-13 17:17:50] debug: zh:deconz: Permit joining on coordinator for 254 sec.
[2026-11-13 17:18:12] debug: zh:deconz:frameparser: Response APS-DATA.indication error: Error: unsupported source address mode: 3
[2026-11-13 17:18:15] debug: zh:deconz:frameparser: Response APS-DATA.indication seq: 52 srcAddr: 0x6fe1 destAddr: 0x0 profile id: 0x0000 cluster id: 0x0002 lqi: 223
[2026-11-13 17:18:15] debug: zh:deconz:frameparser: Response APS-DATA.indication error: Error: Unsupported response reading for cluster ID '2'.
[2026-11-13 17:18:35] debug: zh:deconz:frameparser: Response APS-DATA.indication error: Error: unsupported source address mode: 3
[2026-11-13 17:18:39] debug: zh:deconz:frameparser: Response APS-DATA.indication seq: 37 srcAddr: 0x6fe1 destAddr: 0x0 profile id: 0x0000 cluster id: 0x0002 lqi: 223
[2026-11-13 17:18:39] debug: zh:deconz:frameparser: Response APS-DATA.indication error: Error: Unsupported response reading for cluster ID '2'.
[2026-11-13 17:18:59] debug: zh:deconz:frameparser: Response APS-DATA.indication error: Error: unsupported source address mode: 3
[2026-11-13 17:19:02] debug: zh:deconz:frameparser: Response APS-DATA.indication seq: 24 srcAddr: 0x6fe1 destAddr: 0x0 profile id: 0x0000 cluster id: 0x0002 lqi: 223
[2026-11-13 17:19:02] debug: zh:deconz:frameparser: Response APS-DATA.indication error: Error: Unsupported response reading for cluster ID '2'.
[2026-11-13 17:19:22] debug: zh:deconz:frameparser: Response APS-DATA.indication error: Error: unsupported source address mode: 3
[2026-11-13 17:19:25] debug: zh:deconz:frameparser: Response APS-DATA.indication seq: 2 srcAddr: 0x6fe1 destAddr: 0x0 profile id: 0x0000 cluster id: 0x0002 lqi: 223
[2026-11-13 17:19:25] debug: zh:deconz:frameparser: Response APS-DATA.indication error: Error: Unsupported response reading for cluster ID '2'.
[2026-11-13 17:19:45] debug: zh:deconz:frameparser: Response APS-DATA.indication error: Error: unsupported source address mode: 3
[2026-11-13 17:19:47] debug: zh:deconz:frameparser: Response APS-DATA.indication seq: 223 srcAddr: 0x6fe1 destAddr: 0x0 profile id: 0x0000 cluster id: 0x0002 lqi: 223
[2026-11-13 17:19:47] debug: zh:deconz:frameparser: Response APS-DATA.indication error: Error: Unsupported response reading for cluster ID '2'.
Notes
No response
- Dominant language
- TypeScript
- Stars
- 15.8k
- Forks
- 2.1k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 38
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Koenkk/zigbee2mqtt
-
[Feature request]: OTA for generated definitions of devices with an OTA client clusterPossibly taken @jabla claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Koenkk/zigbee2mqtt#33684 · 1 comment ·
Maintainers usually reply within 1 day
-
new device support
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Koenkk/zigbee2mqtt#33674 · 1 comment ·
Maintainers usually reply within 1 day
-
[Feature request]: Support espzb adapter (ESP Zigbee SDK v2, ESP32-S31)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Koenkk/zigbee2mqtt#33668 ·
Maintainers usually reply within 1 day
-
problem
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Koenkk/zigbee2mqtt#33645 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Koenkk/zigbee2mqtt#33613 · 2 comments ·
Maintainers usually reply within 1 day
All issues in Koenkk/zigbee2mqtt
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/ui#540 ·
Maintainers usually reply within 1 day
-
accepted ai-dev ai-implementing
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
livesport/homer#218 · 1 comment ·
Maintainers usually reply within 1 day
-
normalizePropName strips `#` characters from Figma property names instead of only the `#id` suffixOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
figma/code-connect#419 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Negative values skip k/M abbreviation and medium decimal format on line, stacked-area, and tooltipOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
britecharts/britecharts#1255 ·
Maintainers usually reply within 1 day