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.20
This discussion has been closed.
Comments
And thats another confirm over here too. First night i did not do lots of reboots because it was movie night and not Homey night.
Flows did notwork. only once maybee twice when it was based on RF.
Hue and My IRobot flow still responded on Test.
Zwave i could not test because non of my zwave devices are suported yet by Homey
But it looks like is just RF thats haging after 1 , 2 commands
Kaku as wel as somfy RTS no response
IR Remote
Finding (automatically) remote of my panasonic tv worked at ones YEEHHHH
Learning (manual) remote keys for curtains also worked at ones
Voice training
OK Homey = not working (managed to get 2 greens out of over arround 100 tries
OK = working (strange 5 out of 7 times)
Ahhummm clearing throat (5 of 10 times)
Very responsive for every sound went over after some reboot(s)
Flow
Using microphone = Not working SNIK
Sending learned remote keys from homey to curtains = not working (it worked 3 times out of over 100)
Receiving discovered remote keys from remote to homey = working (it looked like it was slowly getting better and better - now 8 out of 10 have to do a firm press)
Addons
IFTTT = working (only did what was mentioned in instuction movie)
Harmony activities = working
Soundcloud = working (but who wants to listen to music from a poor speaker)
Homey
Reboot = working with no errors
Dim homey's lights = working
Will keep you guys informed!!! for the good and the bad
- Action switches will not always switch off when activated via a flow. Via "Devices" it works 100 %, but when a flow switches the device off, it is registered in Homey, but the signal isn't actually send to the device.
- Memory (freemem, show stuff for geeks) slowly decreases, to a point where it is so low (17965056) that I suspect the HomeyOS starts swapping; load increases to 1.7 and the Homey webpage starts failing to response in time. This was after 11 hours of uptime (and lots of testing).
After a power down/power up, freemem was OK again (75583488) , but 12 hours later (of minimal activity), it is down again (37878908) and decreases steadily over time.
They worked fine in 0.8.17 ; and setting them manually via the 'Devices' tab is no issues. Just when powering down via a flow, they will not respond 60 % of the time. In Devices, it is registered that there is a powerdown, but the actual 433Mhz command isn't sent (properly).
I didn't try Kaku switches yet, to see if they have the same issue, to pinpoint it to generic 433Mhz or to the Action Eurodomeest driver specifically.
When you let Homey react by sending directly to a device, it can be inter-fear that signal.
Here are KaKu devices in use. In 0.8.17 Athon have make a delay in sending to more devices at once by a flow.
Hopefully they have that not turn back in 0.8.20.
I read it often on the Forum that Homey works again after a reboot. I think they need to find out who is doing the leaking.
@taco ; As asked the info. I Have the Aeotec Multisensor 6 Gen 5
Missing lots of sensors , also the most important the motion sensor.
In Homey Device manager after discovery it shows Generic Alarm (Its never getting triggerd) Luminance, Temperature and Battery.
It has: Motion, Temperature, Luminance, Humidity, Vibration and UV Sensor
Specs : http://aeotec.com/z-wave-sensor
I Also have the AEOTEC Recessed Door Sensor Gen 5. Nifty door sensor like how they all should be. Battery powered, small and you can drill them in the door. (So you dont have those ugly sensors on top of the door)
Specs: http://aeotec.com/hidden-z-wave-door-sensor
Homey detects it as a sensor with the options alarm and battery.
But no matter what, Homey Always has a red blinking Alarm. A flow doesnt give anything alarm or no alarm.
If you want info on the devices, access to my homey , anything else but my whole bankaccount just let me know.
The 'Manufacturer Provided Product Manual' will provide a lot of information.
I am able to type via speech-input, which was not possible after the first upgrade.
But homey is not reacting on my voice / voice training will result in endless red rings (see Voice trainer goes bezerk).
You were able to complete the voice training successfully, or did Homey respond to "ok homey" without voice training?
For the Door Sensor configuration parameter 121 has to be set to 16 To to let the sensor send Binary Switch frames.
For the Multisensor enter "5,1,2" and for the Door Sensor "121,4,16" in the Configuration Data field in the device settings.
I was just reading true the zwave for dummy manuals for about 45 minutes and was almost getting the parm options. Will try right away.
Any way to get uv and humidity in the reports ? or does homey not yet support these?
Maybee it would be handydandy to setup a zwavecode.athom.com site with a database of codes, or are you going to implement some kind of database for home to autodetect the device codes and fill in these parms by default ?
I.e. http://products.z-wavealliance.org/products/1184/embedconfigs
Directly after a full reset (without voice training), Homey was not listening to me (reacting on "ok homey" or " hey homey"...
So I switched to the Dutch language (with recommended reboot)... still not listening...
Switched back to English language (with reboot)... still not listening
Started voice training and was expecting multiple red rings...
but Homey recognised my "hey Homey" pretty good... I think I only saw 2 red rings...
Now Homey is listening again! Switching back and forth the language might have done the trick for me...
I should give this a try at home... perhaps the kids will now also start listening
It's not the switching of languages (and thus the possible update of the corresponding settings), but the reboot after the full reset (part of the change of language routine) that solved my issue (unable to complete voice training).
I'm able to get good response if the following steps are taken:
1. Full reset (clear all data) by turning Homey up-side-down
2. Wait until the voice has been downloaded (blue ring is off and verify in settings)
3. Reboot Homey (Settings > system > stuff for geeks > reboot).
4. Then do the voice training... I only needed 6 attempts to complete the training with "Hey Homey"
So in addition to the suggestion @Panda made also apply a reboot after the full reset.
Hope this is solving more issues with voice training / recognition.
After a full reset, it still wasn't working. Then somebody on Tweakers told me he noticed his homey listened much better in a smaller room so I moved mine to the bedroom (thus unplugging/rebooting it).
Both the smaller room and the reboot didn't change anything.
The first time I did the full reset and tried the voice training, it looked oversensitive (continuous red rings).
I was not able to recover from it. So I unplugged, restarted, re-tried same issue. Rebooted/ downloaded new voices/ tried voice training several times, all not successful.
After my first success, I reproduced that if after a reset (clear all data) the voice training is executed (without reboot), the voice training will not be successful. Following above sequence... again successful.
For the record: at around 2 meters distance like @JohanKuster mentions, in a fairly large (70 m2) room.
I'm trying it again right now, about 3m from Homey, different volumes, all red rings
The training should maybe give more feedback about what was wrong with the sample...
Also I manage to get allot of green lights by only saying OK. It makes me lose the faith in the system (snik)