[TS0205 (TS0205_smoke_2) / _TZ3210_up3pngle] ???
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 have 2 and for the last couple of months, EVERY day they go "Offline" having to resort to manual pairing.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
2.13.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 Thu Jul 30 12:31:10 UTC 2026 - 6.18.39-haos - x64
node: v24.18.1
ha: true
Device database.db entry
No response
Debug log
No response
Notes
Device
definition: TS0205_smoke_2 - Tuya (v0.0.0)
software_build_id: undefined
date_code: ``
endpoints:
{"1":{"bindings":[{"cluster":"genPowerCfg","target":{"endpoint":1,"ieee_address":"0xe0798dfffefeea88","type":"endpoint"}}],"clusters":{"input":["genBasic","genGroups","genScenes","genPowerCfg","ssIasZone"],"output":["genIdentify","genGroups","genOnOff","touchlink","genTime","genOta"]},"configured_reportings":[{"attribute":"batteryPercentageRemaining","cluster":"genPowerCfg","maximum_report_interval":65000,"minimum_report_interval":3600,"reportable_change":0}],"scenes":[]}}
Health
time: Wed Aug 12 2026 06:10:00 GMT+0200 (hora de verano de Europa central)
os.load_average: 1.93, 1.69, 1.69
os.memory_percent: 76.8553
process.memory_percent: 4.1973
process.uptime_sec: 4230
{}
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 with the TS0205_smoke_2 device definition and collect the missing database.db entry and debug log while reproducing the daily offline transition. Compare the device's EmberZNet setup and reporting details with the observed disconnect, then document a reproducible cause and verify that the device remains online without manual pairing.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100