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
Version 0.8.27
This discussion has been closed.
Comments
2. homey turns his white light on some times like he's thinking. But I dont do a thing
While watching TV homey recognized every 3 minutes "ie"/"ey" as a hit, and he starts listening. (did some voicetraining..)
but it only works when i ( er nogal kort opzit )
The ok homey trigger works like a mother*cker!
I can trigger homey from 6 meters away, even from the toilet
But homey doesn’t hear anything when he’s listening.
/manager/speech-input/ stays empty…
Using homey in dutch by the way.
Even with a distance of two meters, I can give commands. Sometimes the voice stutters. But after the last two dreadful months, who cares?
removeing the Door alarm and re-adding did it, but not for a normal remote.
LuukVisscher said: same with my AYCT-102
https://github.com/athombv/homey/issues/392
- OK Homey trigger seems to work reasonably well, about the same as 0.8.24 since it already worked reasonably for me. Still seeying false positives though.
- Oops I could not reach the server is still an issue.
- Zwave stability is still really bad, maybe even worse then on 0.8.24. The z-wave devices list is empty most of the time. Restarting the zwave network helps sometimes but a power cycle is need sometimes as well. Devices still time out if farther away then a couple of meters (my guess is there is something wrong with the routing / explorer frames in Homey). Refreshing a zwave device can make Homey crash sometimes.
- Homey still becomes unreachable because it crashes, also on 0.8.27. As far as I can tell it can still be pinged most of the times but the webinterface and app dont work no more and a power cycle is needed.
- Not sure in sunset/sunrise works now.
For me this update hasnt really added to a better experience. Patiently awaiting the next one and I'm gonna see if I can update some issues on GitHub with my latest experiences ...Around 09:00 most of The Netherlands were covered in clouds...
- OK Homey trigger is still bad; but retraining was with some background noise, so that might be a local issue
- Oops I couldn't reach the server also still an issue
- Zwave stability at least as bad as 0.8.24 ; I have one device (230V powered) that keeps Error TxStatus undefined, even when I switch it locally on/off. No issues that I had ( stability + parameters not being sent to device ) are solved.
- KaKu remote doesn't work anymore, Kaku outlet switches itself still work
- BetterLogic variables are gone, impacting the flows that are using them. I cannot add variables anymore. Reboot sometimes works to get the variables back
It does work, but looks to be a factor 10 off. So the range is 0-10 instead of 0-100.
Z-wave seems more stable; although I have been changing the polling settings of my powernodes and motion sensor... which might have been improving the stability (overload) of the z-wave network,
False triggering is a serious issue. This morning, while standing next to the footbal field, I recieved a message (complaint) that Homey started to play (loud) music without a trigger / command.
Stop command directly or via speech-input did not work; had to reboot Homey
Since both voice triggering is too sensitive and remote / wallswitch triggering is not working...
0.8.27 is for me a step back.
In order to prevent false triggering / spontaneous loud music, I would need to disable the microphone.
Yet, with no remote / wallswitch triggering, the majority of my flows are useless.....
Like z-wave wall switches?
Logitech harmony app stopped working.
IR still not working
Oops constantly (much more than before)
Voice is stuttering (it was fine before)
Besides the ok homey trigger working better, this firmware breaks more than it fixes
All my flows with zwave devices have completely stopped working. On the previous firmware version the zwave devices timed out and the zwave devices list was empty but the devices still switched on and off from flows. Now this has stopped working as well and the zwave network crashes about five minutes after a fresh boot and the zwave network chip needs to be restarted. Next to that a lot of the community apps stopped working because of an incompatible change in this firmware. As I use better logic for pretty much everything all my other flows are dead as well. And the oops I could not reach the server is driving my family nuts.
All in all this has reduced the WAF below acceptance level and I'm forced to pull the plug until some stuff is working again.
If so:
Said it before: how could is it possible all these problems and showstoppers reached a firmware? These problems should popup in tests....
I'm very curious what's going to happen with the shipment....