Skip to content
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

Closed
sjorge opened this issue Mar 20, 2020 · 7 comments
Closed

Cannot bind or unbind Aqara MCCGQ11LM door sensor #3159

sjorge opened this issue Mar 20, 2020 · 7 comments

Comments

@sjorge
Copy link
Sponsor Contributor

sjorge commented Mar 20, 2020

Bug Report

What happened

mosquitto_pub -h localhost -p 1883 -t zigbee2mqtt/bridge/unbind/0x00158d00044faf3e -m 'coordinator'

Doesn't seem to do anything, when I try to bind a group (or device)

mosquitto_pub -h localhost -p 1883 -t zigbee2mqtt/bridge/bind/0x00158d00044faf3e -m 'bedroom/desk_lamp'

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

zigbee2mqtt:debug 2020-03-20 12:12:08: Received Zigbee message from '0x00158d00044faf3e', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 1 with groupID 0
zigbee2mqtt:debug 2020-03-20 12:12:10: Received Zigbee message from '0x00158d00044faf3e', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0

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}}

@sjorge
Copy link
Sponsor Contributor Author

sjorge commented Mar 20, 2020

More specifically, the idea was to test it with a bulb first... then to link it to a TRV

@Koenkk
Copy link
Owner

Koenkk commented Mar 20, 2020

AFAIK these devices don't support binding.

@sjorge
Copy link
Sponsor Contributor Author

sjorge commented Mar 20, 2020

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?

@Koenkk
Copy link
Owner

Koenkk commented Mar 20, 2020

Can you confirm if it works as expected?

@sjorge
Copy link
Sponsor Contributor Author

sjorge commented Mar 21, 2020

Error log is working, but they are not yet 100% correct:

zigbee2mqtt:debug 2020-03-21 20:29:02: Received MQTT message on 'zigbee2mqtt/bridge/unbind/0x00158d00044faf3e' with data 'coordinator'
zigbee2mqtt:error 2020-03-21 20:29:02: Nothing to bind from '0x00158d00044faf3e' to 'Coordinator'

This should say 'Nothing to unbind' instead of 'Nothing to bind'

sjorge added a commit to sjorge/zigbee2mqtt that referenced this issue Mar 21, 2020
@sjorge
Copy link
Sponsor Contributor Author

sjorge commented Mar 21, 2020

It's a super simple fix: PR #3172

Koenkk pushed a commit that referenced this issue Mar 21, 2020
@Koenkk
Copy link
Owner

Koenkk commented Mar 21, 2020

thanks, merged! 😄

@sjorge sjorge closed this as completed Mar 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants