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
Homey v0.10.0
This discussion has been closed.
Comments
Homey is useless after update, same here.
@johan_kreeft So at first you had the same issues as everyone else after updating to 0.10.0, but afterwards everything is now working? What did you do exactly and in what order?
Because you just might have the solution to the issues regarding 0.10.0...
And are you absolutely sure that the Dutch built in commands now work again? Could you test the following command: "OK Homey, wat voor dag is het vandaag?"
So I did not do anything. Just let the homey do it's thing and wait.
Although usually exit code 0 means all is well - it still has the orange triangle next to it and Kaku devices do not work.
Edit: #900! https://github.com/athombv/homey/issues/900
Legend! I've tried:
1. Reboot
2. Reinstalling the KaKa app.
What did work:
1. Disable all installed apps (already deleted the KaKu app, but disabled it once again)
2. Reboot
3. Powercycle
4. Enabled all apps
5. Could reconnect all KaKu devices.
Note: the AWMT-003 is beter recognized as APA2-2300R but that's an 'old' workaround
Thanks for the info about the powercycle and disabling
https://github.com/athombv/homey/issues/890#issuecomment-249662873
Your welcome.
Beta testing is in my DNA.
It took a bit of my time, but then it got me and my homey(s) a step further
My kaku 2.4.0 crashes as well (fw 0.10.0) but not on all devices. It crashes on e.g the doorbell. I can pair it up to Homey, the first trigger from the doorbell causes Homey to crash.
Work around (for now) is to reset the 433 microcontroller via a post command after the doorbell has been rang.
So maybe they changed something that makes it incompatible now...
Next stop: The cable box so I could actually see a channel. Took me 20 minutes to add all the buttons from the remote. Added a flow which 'sends' digit 1.....and all IR stuff stopped working. Great
Error: too_many_devices (yeah, cause 2 is a shitload.....)
So I removed the Samsung remote. For that one I can add within a minute. Down to 1 remote should do the trick right? Can't be too many...
Error: Cannot read property 'device' of undefined
For goodness sake.....I know it's in the unstable channel. But unstable usually means 'some things are working, some things are not'. Athom changed it too 'you might find something that works for a little while'
Athom, I know comments like these do not add to the motivation of the developers. But it's also unfair to hail and praise while actually it's a bit messed up. Please, please, please focus on getting the basic promises straight and stable for 90% of the population. Creating an in-house solution to also please the other 10% is really cool, but might result in a 100% fail of the product.
Minimal Viable Product....does it (led) ring a bell?
Will be fixed in 0.10.1.
Tried deleting the device and adding it again (didn't help, by the way), and I also got quite a few duplicates in the list.
I also found out why my hues aren't turned on in the morning anymore. The flow stops/hangs on the first dimmer card, so only the first light is turned on. Anyone else having this problem?
Can't find it on slack but if my memory serves me well it was labeled as a bug and will be fixed
https://github.com/athombv/homey/issues/893