[TS0601 (TOQCB2-80-2P) / _TZE284_mrffaamu] Exposures
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 a TS0601 - TOQCB2-80-1P and the power, voltage and current always read N/A while the Power A, Voltage A and Current A read OK. Temperature and Energy are OK as well. This becomes a problem because when interfaced to Homey only the common power, voltage and current are displayed which always show "Last value unknown".
What did you expect to happen?
I would expect that all exposures are sent to Homey rather than the common power, voltage and current which appear to do nothing.
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
2.13.0 (fcbb7ff4)
Adapter firmware version
{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20260310,"transportrev":2}
Adapter
ZStack3x0
Setup
os: Windows 11 Pro - 10.0.26200 - x64
node: v24.13.0
ha: false
Device database.db entry
No response
Debug log
No response
Notes
Device
definition: TOQCB2-80-2P - Tongou (v0.0.0)
software_build_id: undefined
date_code: ``
endpoints:
{"1":{"bindings":[],"clusters":{"input":["genBasic","genGroups","genScenes","manuSpecificTuya","genBasic","60672"],"output":["genOta","genTime"]},"configured_reportings":[],"scenes":[]}}
Health
time: Thu Aug 06 2026 13:29:51 GMT+1000 (Australian Eastern Standard Time)
os.load_average: 0, 0, 0
os.memory_percent: 52.289
process.memory_percent: 1.717
process.uptime_sec: 157212
{"leave_count":0,"messages":21500,"messages_per_sec":0.1368,"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 at the TOQCB2-80-2P device definition and inspect how the common power, voltage, and current exposures relate to the working A variants. Reproduce with the reported device data if available; done means the Homey-facing exposures provide the device's available readings. No debug log or database entry is provided, so the exact code path still needs locating.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100