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

SJCGQ11LM (Xiaomi Water Leak Sensor) doesn't report immediately #17

Closed
Koenkk opened this issue May 4, 2018 · 10 comments
Closed

SJCGQ11LM (Xiaomi Water Leak Sensor) doesn't report immediately #17

Koenkk opened this issue May 4, 2018 · 10 comments
Labels
problem Something isn't working

Comments

@Koenkk
Copy link
Owner

Koenkk commented May 4, 2018

But does with the native gateway: https://www.youtube.com/watch?time_continue=149&v=8yGm2vH8HYQ

@Koenkk Koenkk added the problem Something isn't working label May 4, 2018
@starkun
Copy link

starkun commented May 4, 2018

Work prefect on cc stick.

@Koenkk
Copy link
Owner Author

Koenkk commented May 4, 2018

@starkun it reports immediately after you drop it into the water? What configuration do you have?

@tube0013
Copy link

tube0013 commented May 4, 2018

@Koenkk I'm who posted this in the HA forums. I just tried running cat /dev/ttyACM0 and immediately get feed back when I drop it into water, also get feedback as soon as I dry it off.

@kirovilya
Copy link
Contributor

You try to detect leak event with attReport message. But statusChange event is more good for this.
Look at https://github.com/kirovilya/ioBroker.zigbee/blob/master/main.js#L523

@ciotlosm
Copy link
Contributor

ciotlosm commented May 8, 2018

@kirovilya do you have a description between the differen attrReport, devChange, statusChange? Would be great when adding more devices.

@tb-killa
Copy link
Contributor

tb-killa commented May 8, 2018

@ciotlosm Look here: https://github.com/zigbeer/zigbee-shepherd/wiki#event-ind

  • 'ind'

devIncoming
devLeaving
devChange
devStatus
attReport

@kirovilya
Copy link
Contributor

@ciotlosm Unfortunately not know. These were obtained by experience and in google.
Different devices uses different message type.

@ciotlosm
Copy link
Contributor

ciotlosm commented May 8, 2018

Thanks @tb-killa. It seems based on the information there that we should never ignore devChanged. Maybe it's better to recevie two mqtt messages than miss 1 potential sensor message.

@kirovilya
Copy link
Contributor

You also need modification of zigbee-shepherd library with this events support.
Like commit in my fork kirovilya/zigbee-shepherd@77eee08 from not applied PR zigbeer/zigbee-shepherd#6

@Koenkk
Copy link
Owner Author

Koenkk commented May 8, 2018

Thank you very much @kirovilya, works perfect now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants