[TS0601 (ZG-102ZM) / _TZE200_jfw0a4aa] ???
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.7k
- Forks
- 2k
- Avg merge
- 18h 55m
- Merged PRs (30d)
- 35
Description
What happened?
I`ve added 4 of this ZG-103ZL sensors. All four were incorrectly identified as ZG-102ZM devices.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
2.12.1 (unknown)
Adapter firmware version
{"build":0,"ezsp":13,"major":7,"minor":5,"patch":1,"revision":"7.5.1 [GA]","special":0,"type":170}
Adapter
EmberZNet
Setup
os: #1 SMP PREEMPT_DYNAMIC Wed Jul 1 07:35:33 UTC 2026 - 6.18.37-haos - x64
node: v22.23.0
ha: true
Device database.db entry
No response
Debug log
No response
Notes
Device
definition: ZG-102ZM - HOBEIAN (v0.0.0)
software_build_id: 0104012026
date_code: undefined
endpoints:
{"1":{"bindings":[],"clusters":{"input":["genBasic","genIdentify","ssIasZone","manuSpecificTuya","genPowerCfg"],"output":[]},"configured_reportings":[],"scenes":[]}}
Health
time: Thu Jul 16 2026 22:16:21 GMT+0200 (Mitteleuropäische Sommerzeit)
os.load_average: 0.38, 0.41, 0.37
os.memory_percent: 38.5045
process.memory_percent: 4.269
process.uptime_sec: 47449
{"leave_count":0,"messages":42,"messages_per_sec":0.0009,"network_address_changes":0}
Contributor 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.
Research direction
Start by comparing the reported ZG-103ZL sensors with the ZG-102ZM device definition and the identification data available for the devices. Check the database.db entry and collect a debug log, since both are absent from the report. Done means these sensors are identified as ZG-103ZL rather than ZG-102ZM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100