I have created a scene that is triggered by a switch.
When the switch is turned ON, other lights need to be turned on for which the scene has been created.
Similar approach for turning OFF the lights.
What happens:
I manually activate the switch,
only the physically attached light is turned ON.
after some time (minutes) the other lights are turned ON.
Same with turning OFF lights
I am using the Fibaro double switch with 2 virtual devices and one z-wave root device, so the double switch appears as 3 devices in VERA.
It used to work.
I may have used the root device in the past as a trigger and not the virtual device connected to the physical switches so maybe this is the cause but I like to understand.
When tapping the switch, does it get reported to Vera right away or is there a delay? Load up the web interface and tap the switch to see if it gets reported right away. It sounds like the status is not being reported right away and Vera is polling the switch. In which could cause the delay.
As @garrettwp said, it sounds like Vera may not instantly get the status from the switch, so you have to rely on polling. I’ve been curious about the FGS-221, as it does not seem to give you a scene controller and two switches. What is your scene trigger? A [tt]device is turned on/off[/tt], or [tt]a scene is activated[/tt]?
My trigger is a the virtual device being switched on. So NOT a scene being activated.
This can be done by changing the bistable state of the physical switch or on the Dasboard.
The Fibaro’s are known to report status.
When I use the physical switch, I can see on the Dashboard that the root device is activated (lights up green and shows new status) and within parts of a second the virtual device is turned on on the Dashboard too.
It is almost instantaneous but not entirely.
Same experience looking at the lights, almost instantanous.
Striking is that it seems to have solved itself now.
(And the only thing I have been doing is working on my other issue with the Remotec as scene controller by taking it out of the network and putting it back in and put back in all the scenes where it is used.)
To me, it seems a Fibaro-issue. I also have some Fibaro’s triggering scene’s. I also have Fibaro modules associated. After a while (days or weeks, it seems depending on the # of switches made), the Fibaro modules stop sending state changes. Then, the only way for Vera to now that a state changed, is after polling (which can take up to some minutes…).
The only way to solve this for me is to switch off the mains supply of the Fibaro’s. After switching on they start reporting status changes again.
I’ve sent Fibaro an email today, asking for some help. I did not have an answer yet.
Vera Lite (UI5, firmware 1.5.346)
5xFGS-221 (Vera reports firmware version 3,3,20,1,4)
2xFDS-211
Some Fibaros stop sending status updates after a while. Same is true for the new Duewi wall switches with enhanced firmware. Both companies have stated that the underlying issue is the Zensys firmware in the Z-wave chips; there’s a memory or buffer overrun apparently.
Sometimes Vera (UI5 on Vera 3) takes ages to execute a scene; when triggered from a state change (Fibaro) or a scene controller (MiniMote, HSM). Either the scene takes a very long time to start, or the scene starts quickly but takes a long time to execute, with half a minute between each light turning on.
I am having the same problem with the fibaro relay switches.
After a while (days, sometimes weeks) status updates from the switch to Veralite are delayed (seconds, minutes).
Is there already more info (possible solutions) about this problem?
@fbodewes, you mentioned sending an e-mail to Fibaro about this, did you already get an answer?
I can confirm the behaviour described above. I also wanted to use an FGS211 as switch and scene controller.
When I tested this setup it used to be quite responsive, it would take less than a minute, and often much less to respond. Now it takes minutes. The reporting of the switch state now definitely depends on polling of the device and it can take a long time before it is polled depending on the polling settings and the network size.
What I am wondering now: is there another method (other than polling) for the fibaros to report their status to the vera instantly?
I have the same issue, but with Fibaro FGS221 switches. I noticed that the root device changes state immediately, but the actual switches (e1 and e2) can take up to minutes to change. The poll setting for the root device is 60 and blank for the e1 and e2 switches. I tried playing with those, but it doesn’t seem to help.
Do you think it would somehow be possible to have the trigger act on the root device state change (instead of e1 or e2_ and then somehow actively polling from a script or something like that whether it was e1 or e2 that caused the trigger in order to determine whether the scene should be executed?