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 Official
[App] Fibaro by Athom (v1.5.18)
This discussion has been closed.
Comments
But it doesn't state what.
@KeepT
It does have a small "glitch" with the "long press released", it can trigger twice, need to fix this still.
but for the rest it does trigger properly with all other presses.
(i'm using it myself with 2 buttons at the moment)
i have the binary sensor myself but thanks for the info though
the reason why it isn't implemented yet is because i came into some issues that i needed to think about before i'm able to add it and it working properly.
But i have some new ways/information now that i want to try this weekend to be able to add, so a little patience please
Small Edit: it still won't have the temperature sensor's being able to read out, this is still impossible without a change in the Z-Wave Driver/Z-wave Core
They all seem to be working for now (except my motion sensor, same problem as the first one, no updates...)
But... there is a lot of inconsistency in:
More specific (but not very because I forgot the details per device ):
I'm running the appstore version of the app, is this something that has to be streamlined by Athom, or is it up to the community?
Dimmer = in the class of "Light" because dimmers are 99% of the time a light anyway. So no option for choosing is needed.
The Relays/Switches = class of "Socket" because that is the only class where all capabilities being used are supported, and they are not always being used for lights.
but still light is select able, so it will switch with the default speech triggers in homey.
If i would use the "other" class i will need to add all mobile cards and all the triggers, actions and conditions cards myself. + no build in option for being able to select light.
the roller shutter = probably a mistake made in the icon of the device (i did not check this since it's not my driver)
the animation.. well that is what you get when different people start creating drivers.
But to answer your real question, it's probably up to the community to "streamline", if you want to wait for athom it will be probably be next year. and how do you want it to "streamline" it, all the same? then you will need to change ALL devices not just the fibaro app, you really need to see every individual fibaro device as a real different device.
But then it should surely be the icon of a bulb instead of the module itself
Wouldn't it be logical that it's streamlined for every device, no matter what brand? You'll get a jungle of methods and appearances in the end otherwise...
I can't seem to control my lights with the device cards. I was wrong at first, I tried turning on the lights with the S1, but then I remembered you have to use the main node for S1.
But it still doesn't work. The light doesn't turn on (don't hear the relay click either) when the slider moves.
When I close and reopen the card, the slider is back in the off-position.
When I control the light with the physical switch while the card is open, the slider moves to the correct position...
Same problem when using the main, S1 or S2 cards.
Is it possible I selected the wrong device when adding? I have all FGS-212 or FGS-222. Those are (Double) Relais 2, right?
Never mind, it started working some time after a reboot. Hope it stays stable.
Any status update on the fact that the main node has to be used to switch the S1/Q1?
Cards get updated when I use the switches, but I can't control any device anymore through Homey.
Relay, dimmer, rollers, nothing...
I'm posting it here since it's all Fibaro, but probably it's more of a generic Homey problem I guess.
Rinse, repeat. Grr.
https://github.com/athombv/homey/issues/847
It's not a Fibaro specific issue but a zwave issue in general.
Thanks!
Did you reset the FGS-222 itself as well? or just homey
I found that with Homey I need to be way closer than with my other controller.
It feels not entirely right that my Kaku devices perform much, much better at half their cost
I have a couple of FGS-222's too. I have added one of theses successfully by doing the 3x press on the actual wall switch (momentary type). That paired instantly with Homey. The distance was approx. 1,5 m.
I tried to add a second 222, by moving Homey to the second floor. Distance to the relay is 50 cm. Tried multiple times... It does not pair. I am sure it was removed from my Domoticz setup (as was the other 222). It just won't pair.
I gave up and hope the firmware and App updates will solve this issue.
Just go to the z-wzve settings and do a 'remove device'.
This will reset it correctly.
Try again after that.
Thanks
I tried to create a driver for the binary sensor, but have not been successful to get it working properly without having to poll it every 10 seconds (because short input signals definitely possible).
And that is way too much!
Maybe athom (@Robin) can be more helpful to this.
Since last update (few minutes ago) it will.
@ everyone
My pull request just got merged and published.! (v1.0.10)
This means the new way for relays/switches (only 2 devices).
You will need to re-pair them to have just 2 devices,
but it will still work with 3 devices, so it's not necessary to re-pair