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
0.8.34
This discussion has been closed.
Comments
Note: The issue seems only to affect the LED-Indicator. The voicerecognition is working fine. I can ask homey something right after the trigger and it understands it without showing the indicator.
Even dead simple things like "test" are not recognized..
somfy also for me not working anymore, tried everyting reboot reinstall putting homey next to the blinds, powering off.
had it from 0.8.32 somfy dead
The only thing is that my fibaro motion sensor v3.2 has a continously generic alarm. Furthermore, I'm not able to change the settings (association group, z-wave wake up time etc) for the fibaro motion sensor. Anyone else experiencing the same problems with the fibaro motionsensor?
Love the new dimmer slider in the app.
Updated to 0.8.34 en both KAKU and Hue not working. I tried the following:
- removing en reinstalling apps
- Homey restart
- unplugged the power cord for half an hour
- Complete reset en setup of homey
After the reset it was not possible to add sockets or remotes. Also adding the HUE lights was not possible
Any suggestions?
Note1: I could re-add the Somfy blinds but it controls only one of them. After reboot not even that works.
Note2: The flow list has a scroll bar but it is hard to get rid of that drop down list (which you wish to do if you need the card underneath the list).
This one is definitely not a stable firmware. If you haven`t installed it and you are indecisive, than don`t do install it, no major visible improvements.
You are able to change the parameters with flows, they will not show up inside the configuration popup, but will be saved in the device.
(even if you delete the flow afterward)
little bit cumbersome, but atleast it works until fixed
can you give an example of changing the setting in a flow?
New to me.....
The time trigger is just a place holder so you can click the test button.
In this example i'm changing the parameter 42 (lux time threshold) to 300 seconds of my fibaro motion sensor
(doing this to see if the byteflip bug has been fixed, will tell more when results are in
You can add multiple parameters by just adding more cards, or just change the parameter in 1 card.
Then just press the "Test" button, and wake up your device to speed up the configuration.
Tested with parameter 6 (fibaro motion sensor v2.7) to 20 seconds and the alarm turns off properly after these 20 seconds (instead of the default 30 seconds).
Now just testing with the other parameters to be sure if logging is affected as well.
I'm trying to get it to work...
AEOTEC is next... Had to reset it and it is now in his box to "cool down"
It will give the console error "invalid_type_for_capability_light_mode" if you try to open the config popup and the colormode of that bulb is in xy colormode.
(there are 3 modes, xy (Coordinate Color Value), ct (Color Temperature = Warm white <-> Cold White) and hs (Hue and Saturation).
So i think Athom forgot one of the colormode options in the hue app. (homey hue app only uses hs and ct colormodes itself)
It is fixable by changing the colormode with the hue app on your phone/tablet by change color to either a Color Temperature or using the Hue and Saturation way to change color (which is the NOT the default way the official hue app changes color, it uses xy)
When I open the card for one of my LivingWhites plugs, I get 'invalid_type_for_capability_dim'
When I open the card for my Fibaro Smoke sensor, I get 'invalid_type_for_capability_alarm_smoke'
When I open the card for my Fibaro Relay, I get 'taskfailed_for_capability_onoff'
I see a pattern here