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
What could be the reason that I have no Left/Right Switch-triggers for S1/S2 (like the FGS-213) for either of the 2 channels?
I only have 'Turned on' and 'Turned off' for both.
The FGS-223 has momentary switches, also changed to that in the setting, still don't get any more options.
Just added a couple of Fibaro devices but before I had installed:
Dimmer 2, firmware v3.5 - 5x
Motion Sensor (z-wave plus), firmware v3.2 - 2x
Tonight I added:
Dimmer 2, firmware v3.5 - 3x
Motion Sensor (z-wave plus), firmware v3.2 - 1x
Fibaro devices are not responding constantly. All the other devices (e.g. NEO Coolcam, Greenwave, etc.) are working just fine. Rebooting the Fibaro app doesn't change a thing but when I reboot Homey, FIbaro devices are working again for a bit less than 5 minutes. After that, it stops working until I reboot Homey again and so on.
I have a box with unpacked Fibaro devices. Including the previous installs I'm going to instal 52 Fibaro modules but it has lost stability after having less than 10 devices connected to Homey.
Homey is running in firmware version v1.5.3 and Fibaro devices are not responding trough the Desktop app, mobile app, mobile beta app, homeydash, homeyda.sh, Home Kit and S2 switches. So I've tried everything
Also the Homey Bèta app (v1.1.105) is unable to reach Homey quite often (as well before and after the Fibaro issues) but when the app is connected and I want to switch/dim Fibaro devices since these issues, I receive ''Something went wrong addressing device ''....'' (Network request failed'.
Anyone else experiencing similar issues or does anyone know what's going on?
I don't mind reinstalling the FIbaro app but I probably have to add every single device again, don't I?
Really hope someone can help me out since I cannot control anything in my house right now and the misses is getting upset too
Update:
Removed all devices and flows I added tonight but still the same issues and Homey goed offline all the time...?
I had also a lot of issues with Fibaro running under 1.5.3. like you mentioned. Suddenly Fibaro devices didn't work anymore without changing anything. After a PtP it was back running again for less then an hour. Because of that I decided to go to experimental. Now running 1.5.6rc8
Zwave (Including Fibaro) is now running stable.
Zigbee is not running stable.I need to reset my Homey by Candy every night to keep Zigbee running.
So if you only running Z-wave devices, it is maybe an idea to go over to experimental. (Be carefull you can not go back to stable anymore!!!!)
Sounds like a perfect tip but really don't want to go experimental.
I deleted every app accept for Fibaro and a few other apps I can't work without. After deleting HomeyKit and HomeKit, everything looked stable again but that only lasted for a couple of hours.
So now I need to reboot Homey every 1 to 5 hours to keep everything working. Very very enjoying.
I'll contact Athom to see if they can help me.
But since I have deleted and re added my device and deleted and re installed the Fibaro app v 1.5.17 (this is a stable version) the motion sensor is working again. At least for the past 24 hours now.
Then adding it to homey, (FGS-223 Double Switch 2) do not select it as a light switch. Let it stay as undefined or whatever the default is. Then the 2-click etc works OK.
Have it set up now so the FGS-223 controls ceiling (S1) and a window (S2) light, double-click on the S2 also activates a flow that shuts down all lights in the house that should so during the night, also pauses SONOS etc.
Then you double-click on a FGS-223, the light that is connected to that particular switch is also reacting. Is there a way to configure it, so it does not react to this? Probably with a small delay then for normal operation for it to see if there's a normal click or 2/3-click or hold before it changes state.
Tripple-click or hold on the FGS-223 is even worse because then you also reverse the previously state of the light.
This could be fixed with a couple and/or statements so it goes back to as it was. But the light still blinks or shuts off momentarily. Should be a more elegant solution.
I have the same problem with fibaro. seems to have stared with the latest Fibaro app version. All other Zwave devices work fine. Did you get an answer from Athom?
right now there is a bug in homey itself that sometimes settings (not default for the device, but for workings in homey) during pairing are not send (which happend in your case), so you need to de-activate the setting "scene activation", save, then activate it again and save.
is the bug i mentioned known? I see on the forum here and on the Dutch tweakers forum I am not the only one.
It is know, and should "already" be fixed in the upcoming experimental update 1.5.6 RC9
Ok but this only helps if i go the experimental route.... it WAS working on 1.5.3 so the new app version broke it and now normal users have no other option to wait (for how long??) or go to an unstable experimental release path.. Does not seem the way for a company who wants to attract normal users and not "tweakers".
it is not caused by the app update, it was already there way before the app updated (as in 1.5.3 has it... way before last app's update), as i said before, it is an homey issue, and not an app issue.
it is just in certain situations, and also not all devices (that need to have a setting send during inclusion (not that many)) have it, so it just won't happen every time, also the reason why it took about 5-6 weeks to even discover the issue.
and tell me how many times do you think those "non tweakers" will pair a z-wave device that needs to send a setting during inclusion (fibaro only has 3).
this is only the 6th or 7th message i see, both github and forum taken into account, that have a device with this, (which is easy fixable manually btw, even for the non tweakers) in the time that 1.5.3 is out until now, which is 2,5 months.
BTW, hope you don't put all bugs under the same thing, as there are multiple issues regarding zwave, not just this one.
Hi Caseda,
Thanks for your reply. I tried it, but no effect. I checked the associations, but there was only 1 group which had value. So I added my homey's node number to all the other groups (2 till 5), and now it works.
Ok I linked it to the last app update as it started after i updated, and I've seen more reports lately. Good that the solution has been found. The device i have is a simple double switch, not something uncommon for a home automation system, even for people who are not "tweakers".
This is the first issue i have encountered. Of course i will try to identify the separate issues. The tone of your message seems hostile. It was not my intention to be negative about the work the Athom team already has done..
Offtopic question. If i go experimental now. Does it keep all my devices and settings? And is it possible to upgrade to 1.5.6 stable with settings when its available? Thank you.
Edit: After re-adding the motion sensor everything is working fine.
Group 3 was already at 1.
I did register it at github again:
https://github.com/athombv/homey/issues/2479
It is anoing.