-
-
Notifications
You must be signed in to change notification settings - Fork 566
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
How to deal with getDeviceWifi().subscribe #528
Comments
Do you have any idea how the subscribe works? Can you give it an URL that gets pinged in case an event happens? |
Currently, I can't. I can give you logs from the doorbell. Unfortunately, I flashed the ESP on it, and now I cannot flash back the factory firmware. |
`| | ||| ||| || 08:00:03.750 [D] tou: recv=get_down 08:00:04.980 [I] miio_net: Wifi event[4] 08:00:06.730 [D] tou: recv=get_down 08:00:06.890 [I] httpc: Content-Length 216 |
My doorbell is working, if you help me, what need to do, i really would like to help! |
The subscribe is likely used for the cloud communication notifications, and thus out of scope for this project. |
I'm trying to reverse engineer the communication protocol of the Xiaomi Linptech doorbell, and I'm stuck with this subscribe thing. I don't know how to deal with this. I can use the methods to control the device, but for data feedback, it uses this subscribe method, which is not familiar to me. Please help me figure out what to do with that.
https://github.com/MiEcosystem/miot-plugin-sdk/blob/38905bbe8452cf46bf1e9ba22879495423a1eff8/miot-sdk/Device.js#L24
The text was updated successfully, but these errors were encountered: