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
Tried to move the Hue light to different zones, remove/pair them, but nothing seems to help.
Anybody here with the same issue?
I use the internal command to switch on my Hue Lights, and a flow to change color, and all is working fine. I’m on .39. During all updates my lights keep on working fine.
KaKu are working (switches, contact sensor, doorbell)
also all my Smartwares (switches, contact sensor).
The only problem I have is the garden light, It should switch of at 2300 but only the slider is off, the light itself not.
FW. 0.8.39
KaKu app 1.1.6
I'm using Hue and as far as i know the old bridge is on the most recent firmware.
Just got my first z-wave device's today. After installing them they do not get trigger in a flow.
Strange thing is KaKu can trigger z-wave but not the other way around.
PTP(™), box your Homey, have a nice beer, spent some quality time with your wife, gear up the WAF and wait patiently on the soon(™) be available update with a lot of awesome(™) new features that will make or ..... your Homey to a awesome device!
Here Homey does 2 (ok 3 things);
1. standing in corner (verdom hoekje)
2. randomly shouting "MarcoF came/left home" (he, to frustation of the wife, forgets the Wife)
3. On sunset switching 3 Hue lights
- Sunset/sunrise triggering Hues
- Kodi turns on/off lights when movie starts/stops and announces the name of the movie
- Voice trigger turns off Hues and audio/video devices (through Harmony) when I say I'm going to bed
- Limited z-wave devices seem to be reachable most of the time
But I'm still on .38 by the way, didn't upgrade because I saw the stability/trigger problems
- 2 kaku sockets
- 2 greenwave power node 6
- 1 greenwave power node 1
- 1 Lifx light
- sunset triggered flows
- report my solar panel generation (through http app)
- report my appointments (iCalendar app)
- report incoming emails
- completely control all my A/V devices (through Harmony app)
- do all sorts of stuff based on Kodi events
- tell me when it is going to rain (buienradar app)
- tell me when a new download has started on sabnzbd
What isn't working:
- 1 fibaro wall plug (pairing never worked, awaits zwave rewrite)
- speech to text recognition (not misinterpretation but just a white ring)
- presence detection, it's to flaky to rely on it
- report current power usage of sockets of the greenwave power node devices (only reports totals, awaits the zwave rewrite)
- 3 Hue Lights
- 1 KAKU doorbell
- 1 z-wave sensor (not used for triggering atm.)
- 1 Camera with Synology NAS.
- 2 Elro Sockets
What is not working:
- 4 Milight bulbs. (they stop working after a while. Have to do a reinstall and than check again).
The KAKU doorbell stopped working as well but after pairing it again it's working without any problems.
KAKU, Hue, NFC, Chromecast and infrared are still working fine.
The only thing that still isn't working is the 'OK Homey' trigger.
But a lot of people,mostly impatient postmen, push the doorbell multiple times in a row OR push the button for 1-5 secs. The result is a load of triggers, the soundboard ringtone go mad and emails keep filling the mailbox.
So for now I disconnected the doorbell from Homey and it would be great if a user can set the debouncer threshold per device.
If doorbell is pressed set variable "doorbell" at true.
If variable "doorbell" is changed and is true, say there is someone at the door and set variable to false after 10 sec.
Bought recently some z-wave to overcome this problem, sadly z-wave doens't work either. In one sentence "my homey is crap" and i'm slowly gettting the feeling to sell this troublemaker.
The only thing to fix this problem is to add the sensor as a socket and reset the device yourself.
@Rocodamelshe
I think the most simplistic doorbel flow with a debouncer: