[TS0210 / _TZ32101000000_5oy7cysk] ???
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.7k
- Forks
- 2k
- Avg merge
- 18h 55m
- Merged PRs (30d)
- 35
Description
What happened?
No corresponde el sensor con el que tengo físicamente. Tampoco recibo nada, lo reconoce pero cuando vibra no recibo nada en z2mqtt, ni el estado de batería, absolutamente nada
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
2.12.0 (unknown)
Adapter firmware version
{"build":0,"ezsp":13,"major":7,"minor":4,"patch":5,"revision":"7.4.5 [GA]","special":0,"type":170}
Adapter
EmberZNet
Setup
os: #1 SMP PREEMPT_DYNAMIC PMX 7.0.6-2 (2026-05-29T11:08Z) - 7.0.6-2-pve - x64
node: v24.13.0
ha: true
Device database.db entry
No response
Debug log
No response
Notes
Device
definition: TS0210 - Tuya (v0.0.0)
software_build_id: undefined
date_code: ``
endpoints:
{"1":{"bindings":[],"clusters":{"input":["genBasic","57344","genIdentify","genPowerCfg","ssIasZone","57346","manuSpecificTuya"],"output":["genTime","genOta"]},"configured_reportings":[],"scenes":[]}}
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 reviewing the TS0210 Tuya device definition and collecting the missing database.db entry and debug log while the sensor vibrates. Compare the reported endpoints and clusters with the physical device; done means the correct sensor is identified and vibration and battery state are received in Zigbee2MQTT.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100