You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
4.3NOTIFICATION message
Whenever there is state change of smart LED, it will send a notification message to all connected 3rdparty devices. This is to make sure all 3rdparty devices will get the latest state of the smart LED in time without having to poll the status from time to time.
The notification messages schould look something like this acording to that document:
It looks like it is possible to get status notification pushes through this protecoll at least for yeelight bulbs.
I do not own yeelight bulbs, but do have a xiaomi gateway, it might be that the gateway also supports this same protecoll....
Would be awesom if someone could figure this out. Probably someone who owns a yeelight bulb to see if it works with that occording to this documentation, if so then maybe also look at diffrent devices.
Yust posting it for documentation and future refrence
The text was updated successfully, but these errors were encountered:
it's dev/lan mode for yeelight devices. old mi zigbee hub (lumi.gateway.v3) have something similar, but different api. all other devices notify to cloud only.
I was looking into if the Xiaomi miio protecol support push notifications instead of having to poll the devices all the time.
I found this document: https://www.yeelight.com/download/Yeelight_Inter-Operation_Spec.pdf
Which states at the very bottom:
The notification messages schould look something like this acording to that document:
It looks like it is possible to get status notification pushes through this protecoll at least for yeelight bulbs.
I do not own yeelight bulbs, but do have a xiaomi gateway, it might be that the gateway also supports this same protecoll....
Would be awesom if someone could figure this out. Probably someone who owns a yeelight bulb to see if it works with that occording to this documentation, if so then maybe also look at diffrent devices.
Yust posting it for documentation and future refrence
The text was updated successfully, but these errors were encountered: