The account linking used Oauth protocol. When you use Oauth, you need to provide some key and secret to the 3rd party (for Alexa case, it’s Amazon. Amazon will keep our key and secret and it will make sure this pair is not exposed to anyone else). For SmartThings, we would expect them to keep the secret pair, however, now they don’t allow the integration and therefore they won’t hold the pair for us.
Sounds like there is no way around it too bad smartthings
Makes complete sense. Thanks for explaining. We’re all keen to see this get approved!
I will contact them again for the integration, hopefully we will make it.
I’ve post in a couple of places on their community forum - linked to Yeelight queries. Hopefully generates enough interest that it’s reviewed. There is definitely interest from users. Thanks again!
1 个赞
Weiwei I tried to use ifttt and smartthings together it kind of works as a virtual switch for Yeelight I don’t expect any good news from smartthings for official integration
Weiwei any progress with smartthings? Thanks
We have finished our side but SmartThings suspended all the 3rd-party integration request, so we are just waiting for their update.
I think this question isn’t SmartThings related but not sure where else to ask it. Is there any plans to set up a integration with the Wink hub?
If we set our bulbs to developer mode, then surely we can create a smartthings device handler to control? We would not need to contact the cloud? I am trying to cobble this together, however, I am far from an accomplished developer. Is there any decent code that you can point me at to use as a starting point. I am most keen to ensure the interaction is two way. (ie get the device properties available in smartthings)
I set up node-red and successfully controlled a light using the npm published yeelight nodes. So I am pretty sure this is feasible.
I have also posted this in smartthings
So. First challenge, The Yeelight uses 239.255.255.250:1982 for discovery. Smartthings expects port 1900. I cant see anyway to override this in Smarthings,
Anyone have any clever suggestions? or pointers?
Could the yeelight make this port configurable for developer mode>
We have investigated the local integration method, however, Smarthings require a standard Upnp and Soap afterwards, this means we need to upgrade all our firmware to support the heavy protocol. However, for some resource constrained device, it’s impossible to achieve that.
I have been trying to have response from smartthings about the approval but there is no reply so far don’t understand why they not allow it
Ok Understand. Thanks for your time…I will pursue a node.js bridge type solution.
Ideally, I would prefer to use any code that you may have to handle the Yeelight interactions commands. So any non-secret code you can point me at would be very appreciated
If you want to use a node.js bridge, please check out homebridge-yeelight plugin written for homebridge.
Hi there, Does this work with Smarthings yet?
Unfortunately no and smartthings has been silent about the approval, very disappointing
Ok…I have a working set up…it is probably not robust, but if anyone would like to try it
Needs a nodejs server running and at the moment, probably wont work on nodejs on windows.(ie you will need a Linux box eg pi)…if anyone needs it to work on windows, Let me know
Thanks for that thinking of getting a raspberry pi for that though I may try it on my NAS first
Anyone got it working on Pi 3? My test on NAS failed due to some missing command in QTS