Danfoss Ally thermostat - cannot read the diagnostic cluster 0x0B05
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.7k
- Forks
- 2k
- Avg merge
- 18h 55m
- Merged PRs (30d)
- 35
Description
What happened?
With reference to Danfoss zigbee cluster specification for the Ally thermostat it should be possible to read the motor step counter (0x0B05 0x4010 Motor step counter uint32). However, when the read is requested the reply is empty except for the model number. My Ally thermostats are integrated into HA via Z2M. All software is fully updated. Generally it seems that the diagnostic cluster 0xB05 cannot be read.
zigbee-herdsman-converters version 26.90.0
zigbee-herdsman version 10.8.0
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
2.13.0
Adapter firmware version
EmberZNet 0xe456acfffe6a30cc Revision: 7.5.1 [GA]
Adapter
ZBT-2 Coordinator EmberZNet 0xe456acfffe6a30cc Revision: 7.5.1 [GA]
Setup
Home assistant green
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 reproducing the diagnostic-cluster read against a Danfoss Ally thermostat, using the reported versions and adapter details. Investigate handling of cluster 0x0B05 and attribute 0x4010; done means the requested diagnostic value is returned rather than an empty reply.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100