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.24
This discussion has been closed.
Comments
Luckily i'm not the only one.
- upgrading took some reboots and a power cycle even though automatic upgrades was ticked
- Homey does not crash anymore on first voice trigger
- speech recognition has decreased for me though, from a 70% hit ratio to a 15% hit ratio (I'm unable to finish the OK Homey learner) -> update: with adjusting my speech to a more phonetic kinda trigger sounding like okiyomi I'm back on track again with a succes rate of about 80%.
- z-wave sockets still time out
- refreshing z-wave nodes works again without throwing an error
- sometimes the list of z-wave devices on the z-wave settings page stays empty but it now shows loading ids (a reboot is needed to bring the list back)
- z-wave in general still works for me but sockets time out from time to time (see issue here)
- KAKU in general still works for me
- there are some 404 error on the settings pages here and there not loading an icon font
- issue with button for device settings not solved yet (see issue here and here)
- some small UI improvements
All in all, it doesnt break anything compared to 0.8.22 but it doesnt fix much either.The loud noise sound is gone, and can time, date etc. call via app on phone.
via speech input works okay.
The ok HOMEY trainer have to wait till tomorrow .
I have 0% success rate with the training.
I'm in a completely silent room, about 10m away (tried closer also) but I always get 'there is too much background noise', 'try talking less loudly' or 'try to articulate more clearly'
After discovering the ledring bug in .20, trigger was working fine. It broke in .22 and it appears worse now.
Was expecting some news about the "Oeps ikke ben te dom om de server nog te vinden meldingen"
@Emile al een idee wat het probleem is, want verder lijkt mijn Gody goed op spraak te reageren.
For all other people having issue's with speech commands, please check that you do not have more than 1 flow with a microphone in the "when" and than check if speech issues are resolved.
Is this a general problem, and if so, how did it get through testing?
@arjan, did you remove the flows? Or is just unchecking them enough?
Edit 1: In my case i replaced them with input of random IR Remote signals (IR is broken anyway) to test.
Edit 2: I'm currently still at work so i can't check voice input but i'm confident that this should fix the issue.
Damn, that was one tricky bug! Fixed it :-) Thanks for finding out when it was caused!
Have no flow with Mic because it didn't work before this version.. Well.. before...... Still haha
Issues with the ooooeps still in progress
What happens when you go to http://Homey's-ip/manager/speech-input and then type in a sentence like "What is the time" ? The sentence you entered should appear in the http://Homey's-ip/manager/speech-input screen and in the screen http://Homey's-ip/manager/speech-output the answer should be visible.
It pairs, but it doesn't register - all was fine on 0.8.22 with KaKu 1.0.15 even, but I had to do a full reset and now it's broken
Speaking of KaKu, the new pairing flows are a little broken graphically. When pairing a dimmer socket, it won't allow you to pick the device (so it stays a socket, instead of a lamp for example) and when you want to copy a remote signal, the wizard says "press a random key". That should be "press the key you use to control the socket".
Small regression perhaps?
Speech recon looks pretty good on my homey. He's just to stuppid to find the servers
I this something that is understandable for this update? or is it maybe something in a workflow.
Also triggers on sunset are not working.
to be clear microphone is off and there are no flows or any kind of speech related items.
Do you have Z-wave device's ? I Noticed this also when some of my defuct z-wave devices where configured
That Works for me, Input Bad Output visible and Homey unterstand correct what im writing,i dont want Do an hard reset because the Z-Wave Devices
Problem solved, made a new flow and add a volume control regulator, speech is normal again
Reading up on the last days, did not have much time.
My Homey looks like most of it is working after .24 update. Ok Homey works like a charm, even from the kitchen on the other side of the room.
However every voice command results in a Oeps could not find servers.
Punching in command as text in speech input page does not have this problem and results in time etc etc.
Am i not looking correct or did nobody at Homey respond yet with a sollution for this problem. Lot of people seem to have this problem.
It was a bug and is fixed now, so the next release should solve your problem.
In the meantime you can try removing (or just disabling, don't know if that works also) flow that use the microphone. That seems to get rid of the problem...
Thanks , did not see it was on slack.
Have no flows with mic / speech because it did not work before .24 on my homey. Double checked it.
So no resolution for me then (Maybee a restore to default but that will kill my flows again)