[aqara.feeder.acn001 (ZNCWWSQ01LM) / undefined] ???
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.7k
- Forks
- 2k
- Avg merge
- 18h 55m
- Merged PRs (30d)
- 35
Description
What happened?
Unable to pair. Interview keep failing.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
2.13.0 (fcbb7ff44bdc05a16e95d3472a81d110646cc17b
)
Adapter firmware version
{"maintrel":"3 ","majorrel":"7","minorrel":"4","product":13,"revision":"7.4.3.0 build 0"}
Adapter
EZSP v13
Setup
os: #515 SMP Sat May 23 05:35:03 UTC 2026 - 6.1.99-rk356x - arm64
node: v24.18.1
ha: true
Device database.db entry
No response
Debug log
No response
Notes
Device
definition: ZNCWWSQ01LM - Aqara (v0.0.0)
software_build_id: undefined
date_code: undefined
endpoints:
{"1":{"bindings":[],"clusters":{"input":["genBasic","genIdentify","genGroups","genScenes","genOnOff","manuSpecificLumi"],"output":["genIdentify","genOta"]},"configured_reportings":[],"scenes":[]},"242":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]}}
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 with the Aqara ZNCWWSQ01LM device definition and the reported endpoints. Reproduce the pairing failure while collecting the missing debug log and database.db entry; the report currently provides neither. Done means the cause of the failed interview is identified and pairing behavior for this device is verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100