-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot bind or unbind Aqara MCCGQ11LM door sensor #3159
Comments
More specifically, the idea was to test it with a bulb first... then to link it to a TRV |
AFAIK these devices don't support binding. |
I guess we should at least log a message then? Doesn't look like z2m even attempted to bind though. Also do you know of any that do support binding? |
Can you confirm if it works as expected? |
Error log is working, but they are not yet 100% correct:
This should say 'Nothing to unbind' instead of 'Nothing to bind' |
It's a super simple fix: PR #3172 |
thanks, merged! 😄 |
Bug Report
What happened
Doesn't seem to do anything, when I try to bind a group (or device)
It has the same effect, nothing is logged at all with log level set to debug?
What did you expect to happen
The device seems to send message to the genOnOff cluster
So I was expecting to be able to unbind it from the coordiantor, and then bind it to a group of devices... e.g. bulbs, so they would go off or on depending on the state.
How to reproduce it (minimal and precise)
Pair a Aqara MCCGQ11LM, try to (un)bind a device or group from it... It's odd nothing is logged at all, at minimal I would expect a 'not support' or something message to be logged.
Debug Info
zigbee2mqtt version:
1.12.0-dev (commit #ac8a84f)
CC253X firmware version:
{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190608}}
The text was updated successfully, but these errors were encountered: