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.
Comments
Beta
Beta, named after the second letter of the Greek alphabet, is the software development phase following alpha. Software in the beta stage is also known as betaware.[2] Beta phase generally begins when the software is feature complete but likely to contain a number of known or unknown bugs. Software in the beta phase will generally have many more bugs in it than completed software, as well as speed/performance issues and may still cause crashes or data loss. The focus of beta testing is reducing impacts to users, often incorporating usability testing. The process of delivering a beta version to the users is called beta releaseand this is typically the first time that the software is available outside of the organization that developed it. Beta version software is often useful for demonstrations and previews within an organization and to prospective customers. Some developers refer to this stage as a preview, preview release, prototype, technical preview / technology preview (TP),[3] or early access. Some software is kept in perpetual beta, where new features and functionality are continually added to the software without establishing a firm "final" release.
And yes I know that Gmail has had a beta-label even when it was fully functional, but they are an exception to the rule. The above description is pretty much what you can expect from Homey at this point in time. If you can't deal with this, then yes, to use your words: PTP. But keep it pulled until athom releases a 1.xx version
Bugs ok, but I asked why a beta system is marked as unstable/unreliable.
And these unpredictable issues could later have a great impact on the whole platform/acceptance/UX/etc.
And as said I keep it unplugged until the next big update loses its experimental tag.
A beta system is not by definition marked as unstable, but it's very common to see an unstable beta system.
Those unpredictable issues now will not have a big impact on the whole platform/acceptance/UX/etc. Google and Facebook were full of bugs in their first years after creation as well.
Athom is now learning how to do thing right and sometimes it needs an complete re-write (like Z-Wave and some 433 apps).
Plus these large companies have a team of tens, maybe even hundreds of testers which are using the beta or even alpha versions.
And still do these companies have bugs. Minor but still: bugs.
- time is set wrong, timezone is correct but system time is 2 hours early.
- i cannot get it to activate on my voice, except for when using mobile.
- i made a flow with an if "starts listening" and then led ring effect but nothing happens when using phone voice.
Also i have a question about the features. Will it be possible to control a philips livingcolors first edition? It is 2,4 ghz, so it should be possible right?
Thanks in advance. Nick
I decided to Power up homey again awaiting on the Kaku and major firmware update. This because the holiday started and I have some extra time. Also I'm very curious to see what's going to happen with and after the big update.
1. Time - I had the exact same issue for several weeks. Emailed support about it, but Athom didn't have a solution. Eventually, after pulling the plug on Homey and restarting it a couple of times, suddenly the time was correct.
2. Yeah, voice recognition isn't very good at the moment. Athom are aware of it and are working on improvements, but it may still take a while before anything is released in that field. Patience is the only option...
3. I don't think the "Homey starts listening" flow works (or is even intended to work) on the phone... because the status of "homey is listening" never really happens... it's the phone app that starts listening, and that sends the results to Homey.
As for the Philips LivingColors... see this thread for some additional info...
I hope that helps.
There should be a 'for humans' or something like that that shows it correctly.
[Edit] I just noticed that in my particular case, the problem is back, and it's worse than ever:
This screenshot was taken at 09:13 CET this morning (Wednesday, July 20, 2016 - and as you can see, my timezone says Europe/Amsterdam), but the time -and even the date- is completely off:
In his case its a difference of almost 2 months.
https://github.com/athombv/homey/issues/724
Do you know when Homey is supposed to react? do i need to say hey homey?
Thanks for your response!
You can check what homey heard @ ...local ip homey ..../manager/speech-input/
Does this help??
Google now has opened it's speech recognition API. Perhaps worth a look at because when I talk to my Android words come out right almmost all of the time. In contrast to Homey where it's wrong most of the times.
https://cloud.google.com/speech/
The Android App also uses the same Speech API/Service as Homey itself and the IOS App.
The reason that the Android app is getting better results is because the microphone of your Phone is much better calibrated then Homey's Mics(yes multiple).
About 2-3 month ago Athom stated the are looking at better mic calibration (background/noise cancelling/filtering), but until now its not working as expected (yes yes its beta so nothing to expect....Only after 2,5 years development I(!) was expecting a bit more of speech )
For the time problem I made a screenshot:
Also flows based on sunset, sunrise and buienradar do not work. But i will contact athom for these problems.
If it doesn't work contact Athom. Because to me it sounds like a hardware problem with the led ring. But that's just my 2 cents