[TS0601 (TS0601_TZE284_gnpflcoq) / _TZE284_gnpflcoq] Wrong "Fading time" mapping
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.7k
- Forks
- 2k
- Avg merge
- 18h 55m
- Merged PRs (30d)
- 35
Description
What happened?
When I increase the fading time value for the MM Wave Sensor, the reported temperature increases instead. A fading time of "1000 seconds" results in an increase in the reported temperature by about 21C (26.9 -> 48C). The actual fading time (time between the sensor no longer detecting motion and the state switching to "unoccupied" is unaffected by the setting
What did you expect to happen?
I expect that the setting for the fading time actually controls the fading time
How to reproduce it (minimal and precise)
1.) Increase the fading time to 1000
2.) Cause motion infront of the sensor (to instantly trigger a new reading of the reported values)
3.) Observe the reported temperature jumping up
4.) Reduce the fading time back to 0, trigger another sensor read, observe the temperature settling back to normal levels.
Zigbee2MQTT version
2.13.0 (unknown)
Adapter firmware version
{"build":397,"ezsp":14,"major":8,"minor":0,"patch":2,"revision":"8.0.2 [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: TS0601_TZE284_gnpflcoq - Tuya (v0.0.0)
software_build_id: undefined
date_code: ``
endpoints:
{"1":{"bindings":[],"clusters":{"input":["genGroups","genScenes","manuSpecificTuya","genBasic","60672"],"output":["genOta","genTime"]},"configured_reportings":[],"scenes":[]}}
Health
time: Tue Aug 04 2026 12:21:57 GMT+0200 (Central European Summer Time)
os.load_average: 0.03, 0.08, 0.04
os.memory_percent: 47.1719
process.memory_percent: 6.5474
process.uptime_sec: 56403
{"leave_count":0,"messages":1126,"messages_per_sec":0.02,"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 locating the TS0601_TZE284_gnpflcoq device definition and inspect how the "Fading time" setting and temperature are mapped. Reproduce with fading time set to 1000, trigger a sensor read, and compare it with the setting at 0. Done means fading time controls occupancy timing without changing the reported temperature.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100