[TS0601 (TS0601_fancoil_8scene) / _TZE284_yp1m0fla] ???
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.7k
- Forks
- 2k
- Avg merge
- 18h 55m
- Merged PRs (30d)
- 35
Description
What happened?
Please add new device support TS0601 _TZE284_yp1m0fla into Zigbee2MQTT.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
2.14.1 (unknown)
Adapter firmware version
{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20240909,"transportrev":2}
Adapter
ZStack3x0
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: TS0601_fancoil_8scene - Tuya (v0.0.0)
software_build_id: undefined
date_code: ``
endpoints:
{"1":{"bindings":[],"clusters":{"input":["genBasic","genGroups","genScenes","manuSpecificTuya","60672"],"output":["genOta","genTime"]},"configured_reportings":[],"scenes":[]}}
Health
time: Sun Sep 06 2026 22:29:00 GMT+0500 (Казахстан)
os.load_average: 0.98, 2.34, 2.56
os.memory_percent: 44.4807
process.memory_percent: 3.0503
process.uptime_sec: 117031
{"leave_count":0,"messages":999,"messages_per_sec":0.0085,"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
The report identifies the TS0601_fancoil_8scene device and model _TZE284_yp1m0fla, but names no files or tests and provides no database entry or debug log. Start by locating the existing TS0601_fancoil_8scene device definition and its related tests; the work is done when the reported device is recognized with its supported behavior verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100