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
Let me know.
in a quick view i saw that u use miio libary version 12, i don't know if 13 fixed things?
Great job!! I just added my yeelights, peace of cake now
Will play with it more tomorrow but for now THANK YOU!
2017-07-10 -- v2.1.1
[quick code look]
if i look into the code, i see 2 things that match that outcome: 120000 or 120 packet.js (handshake) and token.js(MAX_STALE_TIME) in the mii folder
But... give someone a finger.... what I like to accomplish seems simple at first but turns out to be somewhat more complicated. Some explanation.
When an alarm is activated I would like the Yeelight to do:
- save the current state as in current scenario it is in.
- start a new scenario (which I would like to define...?)
- return to the saved scenario.
Sounds simple? Suggestions are welcome
The timeout issue seems to mainly occur since firmware version 3.3.9_003077 which still hasnt rolled out to my robot (and I dont feel like switching to Mainland China in the Mi Home app again). I'm not a power user myself (just scheduled an start cleaning flow based on some conditions) and this has not happened to my yet which makes it hard to troubleshoot.
@Robiebab , thanks for thinking along. Not sure if those time settings are related. But the issue is for sure related to the miio library used in this app. I might submit an issue there once I'm able to reproduce.
@RuudvB , perhaps in the future but dont count on it. That's way beyond the default device support.
Still i'm hoping there are some guys around with clever idea's that have some (partly) solutions.
As for testing I just added some tasks for the same light about 1 second apart. This results in an push message error stating "Syntax error Unexpected token at O" (the rest is off screen) Not sure what causes this. Below a simple flow just for testing.
>>The guys at Athom must be going nuts over all these app approvals .. :-)<<
They better not complain; they should have done the job....
But now I am wondering if the Yeelight RGB is known to Homey as a RGB light. Yesterday I asked Homey to turn the 'schemerlamp' to blue, but Homey told me it couldn't find any lights with changable colors.
I wonder how homey would know what type of blue you want, since there is a large pallet of blue shades possible. If possible, can we also use this in flows?
BTW, I have ordered more Yeelights yesterday. They will replace some WEMO lights that I found not to be reliable. There is _ALWAYS_ another update in the app, lights keep disappearing from the app, lights stay off or on because homey cannot make a connection.
If someone is interested in the WEMO's just drop me a pm
2017-07-11 -- v2.1.2
Found any good deals ? Now that the app for yeelight is working good im ready to expand.
€15 euro for E27 color lamps
Does someone has any advice?
All working perfectly now, thanks!!
I do already save the current state of the device within the app and I could probably go back to the last state but it seems like a lot of work for a small userbase. I'd rather focus on stablizing the support for the Robot Vacuum Cleaner first (and even that will probably have to wait until after my vacation).