Fibaro Switch FGS-213 and FGS-223 causing double events

[BakSeeDaa]

Hi there.

I'm on Domoticz V3.8702 on Raspberry Pi. Aeotec Z-Stick Gen5.

I recently installed 2 new Z-wave devices, a Fibaro Switch FGS-213 ZW5 and a a FGS-223 ZW5.

They are installed in my garden shed and they are connected to momentary wall switches.

My problems with these switches are that when I operate them by using a Lua script, double on events are created. Mostly, but not always.

double_events.png

That's annoying because my device triggered scripts will of course fire twice ...

It would be nice to know if someone else has similar problems (or not) with theses switches. Next step for trying to solve the issue is to try with a new fresh Domoticz DB. (Thanks @dannybloe for the tip). I will have some time for testing that in the next coming days.

If you think you have any idea on how to help to find out what's going on, your kind help will be very appreciated. Thanks.

[Amsterdam020]

Same here with the fgs-223


Date
Data
2017-11-08 19:25:40 On
2017-11-08 19:25:33 Off
2017-11-08 18:42:30 On
2017-11-08 17:27:31 On
2017-11-08 17:27:31 On
2017-11-08 17:27:24 Off
2017-11-08 17:27:00 On
2017-11-08 17:27:00 On
2017-11-08 17:26:35 Off
2017-11-08 17:26:25 On
2017-11-08 17:26:25 On
2017-11-08 17:26:18 Off
2017-11-08 17:26:11 On
2017-11-08 17:26:09 On
2017-11-08 17:26:09 On
2017-11-08 17:26:09 On
2017-11-08 17:24:55 Off
2017-11-08 15:46:15 On
2017-11-08 09:11:00 Off
2017-11-08 09:10:51 On
2017-11-08 09:10:14 Off
2017-11-08 08:57:45 On
2017-11-08 08:08:56 Off
2017-11-08 07:31:06 On
2017-11-07 22:41:25 Off

[BakSeeDaa]

Same here with the fgs-223
...

Thanks for sharing. At least I'm not alone with this problem then. Maybe after all there is nothing wrong with my Domoticz DB. It would be interesting to hear from more FGS-213 and FGS-223 owners.

Maybe all of us have the same problems with these switches?

[lost]

Had a similar issue with the wired relay control of a qubino smart-meter. On my side, I was mostly getting an off a few hundreds ms after an on event, so immediately reversing state witjout any action from me. But manual test sending back a on in a 1 to 3s time-frame appeared to lead to a stable state. Ticket to manufacturer was further sent to OZW, with no solution so far. Reason looked to be module confirming back state change quite late: Up to 7s! So fooling OZW.

IMO this was more a module FW problem than an OZW one, indeed, and a way for qubino not handling it. Try to open a ticket and see if Fibaro does a better job.

Would be a good idea to make a subforum section with metrics for manufacturers post sales service...

On my side, I made a device script to automate what was working by hand: If last command to switch was in last second time-frame, script send back reversed state.

As it's not a heavily used switch (just used to "filter" a relay command from my energy provider, triggering water tank heater during hours when energy cost less, to be able to control it remotely: The day before coming back from vacations, for instance, to have already hot water when back... plus some energy consumption limiting: water heater is stopped for 5 mn if current input power exceed 7kW, to avoid reaching 9kW limit if another heater switches on but the module handles this side automatically), this was not the best solution but at least I could use the module as there was no alternative.

[XerachCruz]

I just ordered the same modules and USB Stick, as soon as they reach me and I get them to work, I'll tell them if I have that same issue.

[BakSeeDaa]

I just ordered the same modules and USB Stick, as soon as they reach me and I get them to work, I'll tell them if I have that same issue.

Great! Thanks!

[BakSeeDaa]

Seems to be some problems with these switches discussed in thread Fibaro FGS223 is not working well

I has nothing to do with your HTTP call. My own Fibaro FGS223 switches show the same behaviour.



Doesn't matter if they are switched manually or by domoticz. My Qubino switches do not have this "problem".

However the topic is marked as "solved".

Reading that thread, I see that there has been problems with timeouts. I have seen some z-wave timeout messages for my two nodes as well.

[XerachCruz]

I have installed my first Fibaro 223 module and I have the same issue, when actionate them from Domoticz it causes double events.

For Q1: if I click ON the events show ON ON and with OFF shows OFF OFF.
But for Q2: if I click ON it shows ON ON... but if I click OFF it shows OFF ON, leaving the status of the bulb reverse.

Another issue is that S2 does not return the status to Domoticz, so when pressing the physical switch on the wall, the bulb changes its status, but the change is not reflected in domoticz. However, S1 return the status instantly

When activating the polling for the module, in the following check it changes to the correct state, but this can happen up to a minute later.

[BakSeeDaa]

I have installed my first Fibaro 223 module and I have the same issue, when actionate them from Domoticz it causes double events.

For Q1: if I click ON the events show ON ON and with OFF shows OFF OFF.
But for Q2: if I click ON it shows ON ON... but if I click OFF it shows OFF ON, leaving the status of the bulb reverse.

Another issue is that S2 does not return the status to Domoticz, so when pressing the physical switch on the wall, the bulb changes its status, but the change is not reflected in domoticz. However, S1 return the status instantly

When activating the polling for the module, in the following check it changes to the correct state, but this can happen up to a minute later.

Thanks!

I believe we should report this problem then.

Someone who knows where that should be done? I'm not even sure if it's a Domoticz issue or if it's an OpenZwave issue...

[BakSeeDaa]

Since I had no answers, I've now posted a formal Bug/Problem report.

[pigloox]

Hello,

Same problems for me with a FGS 223, with Q1 and Q2.
Domoticz beta
RPI3 Stretch
OZW : 1.4-2713-ge2021e46-dirty
Controller : Sigma Designs UZB Z-Wave USB Adapter

[XerachCruz]

I have excluded and included the modules again (this time using the Domoticz interface instead the button of Z-Stick) and the others issues have been solved, the issue with the double events persist.

[XerachCruz]

At the end, I returned the two Fibaro FGS-223 because in addition to the double events, with LED bulbs many times did not switch on/off using S1 or S2, when more Watios had the bulb, the problem occurred more often ... with only 20W in normal Led bulbs, the issue happed almost every day, with 8W it happened one time at week or less.

I searched the forums of Fibaro and it is a problem of building the module, they only work correctly with incandescent bulbs. Something inexplicable on 2017.

I have returned them and bought some Qubino ZMNHBD1 that work correctly for now.

[Grover01]

@gizmocuz, all,
I'm also experiencing double events with the Fibaro switches as well. I have been in contact with Fibaro support, replaced the switch with another one, and performed a fresh install of Domoticz. Until now I have no luck to get this resolved, is there any solution to this?
I'm currently running 3.9043

Many thanks in advance.

[guantolento]

the problem is solvedd or not ???

[Grover01]

Not that I'm aware of, I'm running the latest version (3.9317) which is still showing double events. It would be very helpfull if this can be sorted out. Please see also http://www.domoticz.com/forum/viewtopic ... 13#p177113 discusing similar topic.

[harrykausl]

Same issue here with the single switch and the double switch (FGS 213 and 223), Aeotec gen5 stick and latest stable version. Is there any solution?

[Amsterdam020]

Someone uses a 'two second rule'. If a switch is pressed two times within 2 seconds, the second command is ignored.
see: http://www.domoticz.com/forum/viewtopic ... e&start=20
the Post by ben53252642 » 25 Apr 2018 01:28

Perhaps this is a solution as well for the Fibaro Switch FGS-213 and FGS-223

What do you think about this solution?

[Amsterdam020]

This seems to work to get ride of the double commands

Code: Select all

-- living_room_wall_switch
-- living_room_wall_switch
t1 = os.time()
    devices = {
        "Eettafel_links", "Eettafel_rechts"
        }
    numdevices = 0 -- Count number of devices in the array
    for index in pairs(devices) do
        numdevices = numdevices + 1
    end
    for i = 1, numdevices do
    s = otherdevices_lastupdate[devices[i]]
    year = string.sub(s, 1, 4)
    month = string.sub(s, 6, 7)
    day = string.sub(s, 9, 10)
    hour = string.sub(s, 12, 13)
    minutes = string.sub(s, 15, 16)
    seconds = string.sub(s, 18, 19)
    t2 = os.time{year=year, month=month, day=day, hour=hour, min=minutes, sec=seconds}
    str = (devices[i] .. "LastUpdate")
    str = str:gsub("%s+", "")
    str = string.gsub(str, "%s+", "")
    _G[str] = (os.difftime (t1, t2))
    end


-- print('Last update eettafel_links: ' ..Eettafel_linksLastUpdate)
-- print('Last update eettafel_rechts: ' ..Eettafel_rechtsLastUpdate)

commandArray = {}

if (devicechanged["Eettafel_links"] == 'On' and Eettafel_linksLastUpdate > 2)  then commandArray['Eettafel'] = 'On'
    

end
if (devicechanged["Eettafel_links"] == 'Off' and Eettafel_linksLastUpdate > 2) then commandArray['Eettafel'] = 'Off' 
end

if (devicechanged["Eettafel_rechts"] == 'On' and Eettafel_rechtsLastUpdate > 2)  then commandArray['woonkamer_bank_gu10'] = 'On'
end
if (devicechanged["Eettafel_rechts"] == 'Off' and Eettafel_rechtsLastUpdate > 2) then commandArray['woonkamer_bank_gu10'] = 'Off' 
    
end

return commandArray

[Grover01]

After tweeking the script a bit to apply my switchname, I get a 3rd event on top of the double onces.