This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Closed Official
[APP] Xiaomi Mi Home (supports Yeelights and Mi Home WiFi devices)
This discussion has been closed.
Comments
I do use BetterLogic in several other situations. At this time I just don't see how to transfer color, hue etc. to a variable... Any suggestions for this? I don't think that "BL-var1 = Yeelight color" would work? The real question is how to access the Yeelight parameters as a variable I guess.
If you already saved the current state of the devices, would it be possible to share that state as some kind of variable or parameter?
I understand your priorities and don't want to be in the way of your vacation
Is this something you can look into or do I need to check Slask or Github?
The Yeelights have been working fine using your app, but now I ran into an issue that does not resolve.
The other day I had to switch of one of the Yeelights using the physical switch. The device disappeared from the Xiaomi app and also from homey (device not available). After switching the light back on the Xiaomi app found the light again and the control works fine again.
Only homey still sees the device as not available. I have restarted the homey app, without success. Any ideas on how to resolve this? Besides of course deleting the device and then re-pairing it again. I expect this would break up all existing flows since the device will probably get another node ID?
What works for me to get my Yeelight color enabled again is kill the power of the light, restart the app and than power on the light again. Do you have a color or a white?
(and yes, re-pairing means editing all your flows)
[EDIT] i need to do more testing but last evening it was working fine again while I hardly touched the code. So I'm not sure if I fixed it or it's not an actual issue. I was thinking, could it be your Yeelight received a different IP address from your router?
I there a difference in how the light responds to commands like 'Turn on' and 'Change color' or 'Change brightness'? In my flows I just use 'Turn on' and 'Turn off'. Maybe that causes the light to not be in color mode?
Via the official Yeelight app I can decrease the brightness level to a really low level while this is not possible via the homey app. The lowest brightness level is around 50% compared to the brightness level of the official app.
Is this something you can easily solve (after your holidays of course:) ) ?
The lights haven't changed IP-addresses.
What could be causing Homey to loose connection to the lights?
Although I cannot explain it, but I first guessed it had something to do with my internet connection dropping out for 15-20 minutes yesterday afternoon. Last night nothing worked to get the light back working with the homey app. I just checked, and now it IS working again....?
Another thought, after the initial pairing there is no way to see what IP the light uses (except checking in your routers dhcp table). A settings/node information page could be useful for a device.
The app checks if it can set up a socket with the bulb, if it cant for some reason it will set the light as Offline assuming it has been powered off by a switch. But I can imagine this sometimes happens when the bulb is actually online. Either my code is not bulletproof (which I can very well imagine) or there was a hickup with the connection or something. Toggling the power of the bulb should fix it. If I can ever get my head around the SDK2 I'll give this some extra love.
I also could not find anything in the coding of my app that could explain this, the dim level gets set correctly. I have asked on Slack if the issue with setting the dim levels through the mobile app is a known issue.
[EDIT]
I have just submitted a new version of the Xiaomi Mi Home app to the beta channel. It will be available in a few days but I'm looking for beta testers. Here is the change log.