TS0301 from _TZE210_m6lwazh9 - Fix for Battery showing NA
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.7k
- Forks
- 2k
- Avg merge
- 18h 55m
- Merged PRs (30d)
- 35
Description
What happened?
What does/doesn't work with the external definition?
The battery was using tuya.valueConverter.raw, but the numbers coming back were
Received Zigbee message from 'zb_curtain_05', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,100],"type":"Buffer"},"datatype":2,"dp":13}],"seq":60421}' from endpoint 1 with groupID 0
data type 2 is number
[13, 'battery', tuya.valueConverter.number], this seems to fix it
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
2.12.1
Adapter firmware version
20210708
Adapter
ZStack3x0
Setup
Running in HA Zigbee2MQTT Addon/App
Device database.db entry
No response
Debug log
No response
Notes
No response
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 external device definition for TS0301 and inspect its battery converter entry. Compare the reported dp 13 data type with the configured converter, then verify that the battery value is no longer shown as NA using the supplied Zigbee message details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100