Domoticz

Posted: **Friday 29 November 2019 10:05**

Hi all,

Yesterday I managed to get my S2 button on the Fibaro Dimmer 2 (FGD-212) recognized in Domoticz.
I have got it connect to a Gira double push button (Sx goes to L, L is bridge from one side to the other, S1 goes to 14, S2 goes to 24, if anyone might be interested).
After trying different connections to the Gira button and measuring with a resistance meter I still couldn't figure out why I wouldn't work.
It appears that you have to enable the scene activation functionality under hardware, then the switch and under option 28 set to 'functionality activated'.
Now that's passed, I could move on.

When pressing the button that connects to S2, the log shows that the button is pushed, so that seems to be working just fine.

Now, what I want to do is use this button to switch 3 other switches on or off.
I think there are three possibilities (and couldn't get any of them to work):
1. Create a group of devices and add the 3 switches there. Then set the activation device to be the S2 button. However, when I want to include the device as an activation device, it doesn't detect the button push, although I do see it in the logging. How do I add the S2 as an activation device?
And how can I make it to turn off if the lights are already on?
2. Alternative to option one, I could create a device that's triggered when the button is pushed twice and then activates a 'turn lights off group'. But how can I add a new device that should trigger when I push the button twice?
3. Create a script (either LUA or Blockly) and use a variable to track status and do:
- when status is on and button is pushed, turn lights off
- when status is off and button is pushed, turn lights on
But when I do that, the status of the variable doesn't change.

Can someone push me in the right direction? Or have a real world sample? I have browsed the forum for quite some time, but could't figure it out.
Main points are:
- how to add the device as an activator for a group or scene?
- how to add a new device as 'double click' device?

Thanks a lot!

Posted: **Sunday 01 December 2019 20:01**

i think option 1 in the way to go.

i checked out my settings and i have added the activation device to the group.

i noticed that there is a difference how you use the activation device

when you use it as a virtual switch(which is visible in the domoticz gui) you can problably not use it as an activation device but only in a script

so please try to remove the activation device(go to setup-devices and press the blue arrow on the right of the device
The device will still be there but you can not use it from the gui (but you can as a trigger device)

regarding a double click device.
i think you need to set domoticz to accept new devices
then when you click 1x a device is created
the same for double click, tripple click and click and hold

: triggers.JPG (88.7 KiB) Viewed 2509 times

to use it as a toggle device there are several ways
the easiest is this way.

add the trigger device to a group

put this in both the on and off action of that group
change the ip address, port and idx to the ones you use.
now when you click the activation device it uses the toggle command and when you hit it again it again used the toggle device

Code: Select all

http://192.168.1.50:8084/json.htm?type=command&param=switchlight&idx=77&switchcmd=Toggle

Posted: **Sunday 01 December 2019 23:03**

Thanks. I'll give it a try tomorrow evening and let you know the outcome.

Posted: **Wednesday 04 December 2019 8:20**

I tried this yesterday. Without success...

I have removed the device (with the blue arrow).
Now when I want to add it as an activation device to the group I receive a timeout.
The switch press is however logged:

2019-12-03 07:43:31.533 (Aeotec ) Light/Switch (Knop Alle Lampen Keuken)

So, that doesn't appear to work.

Also, I have enabled Domoticz to accept new devices and when I double press the switch, nothing happens, although it is logged again:

2019-12-03 07:43:34.421 Status: New sensors allowed for 5 minutes...
2019-12-03 07:43:40.810 (Aeotec ) Light/Switch (Knop Alle Lampen Keuken)
2019-12-03 07:43:40.955 (Aeotec ) Light/Switch (Knop Alle Lampen Keuken)

I must apparently be doing something wrong here...

Any other clues?

Posted: **Wednesday 04 December 2019 9:56**

strange.
i assume you are running the latest domoticz version which uses the zw1.6 implementation?
you should have devices like the screenshot i showed.

i renamed them so that i can recognize what is what.
is S2 set correctly in the dimmer (as a push button or a toggle switch)
scene activation was activated.

if you never cleared out you zwave cache file that might be the problem.
the FGD212 devices might need to be recreated in the cache file.

let me know wat your setup is and how long it has been this way.

if all things are in place it should work like i said
1 click, device is made (rename to S2 1 click)
2 clicks, device is made (rename to S2 2 clicks)
3 clicks, device is made(rename to S2 3 clicks)

if this is not working now i suspect the device was added a long time ago and needs to be re added in the cache file
if this is the case i can tell you how to do things

Posted: **Monday 09 December 2019 20:09**

Indeed run the latest version: V4.10717.

The device is shown like this:

: domoticz.jpg (133.48 KiB) Viewed 2464 times

I have started with Domoticz a couple of weeks ago.
So, I guess my cache is pretty clean.
And, as you might have guessed, my Domoticz knowledge is nearly 0...

Where's this cache file?

Posted: **Wednesday 11 December 2019 19:16**

v4.10717 is a really old version which works with openzwave 1.4
that being said that version is very stable and should work with scene activation
the last version i used with open zwave v1.4 was 4.10734
there was a version which had a bug in it which caused the scene activation not to work but i do not know if this was the one.
i looked at my copies and v717 and 734 are 2 days behind so it could be that you need to upgrade to v4.10734

what system do you have, how do you install domoticz?

going to a newer version with openzwave v 1.6 might y cause more problems because it took a lot of time to get v1.6 stable and working again.

ask on the forum if it is save to go from your version to the latest version and how you should do this

current version is V4.11762 and i believe upgrading from 1.4 to 1.6 without you knowing how things work is a serious risk

then again you are just starting out so maybee the risk is not that big

look at my device list.

all those 801 devices you see should be there in your setup as well
they are created the moment they are activated

in my setup
801 1 is the S1 switch which controls the dimmer
801 1 is a kWh meter

when you goto the setup of the FGD212(setup-hardware-zwave setup)
what do you see in all the registers

20 should be set to correct input button (do you push(click-click) or do you have a regular switch
23 should be disable double click (because we want scenes to do that)
26 3 way switch should be disabled
28 scene activation should be enabled
29 standard mode

here is my setup

1. Minimum brightness level:
10
(%) (actual: 10)

Parameter is set automatically during the calibration process. Options for changing parameter 1-98. Default 1.
Last Update: 2019-12-11 18:56:43

2. Maximum brightness level:
58
(%) (actual: 58)

Parameter is set automatically during the calibration process. Options for changing parameter 2-99. Default 99.
Last Update: 2019-12-11 18:56:43

3. Incandescence level of dimmable compact fluorescent lamps:
1
(%) (actual: 1)

Virtual value set as a percentage level between parameters MIN (1%) and MAX. (99%). The Dimmer will set to this value after first switch on. It is required for warming up and switching dimmable compact fluorescent lamps and certain types of light sources. Options for changing parameter 1-99. Default 1.
Last Update: 2019-12-11 18:56:43

4. Incandescence time of dimmable compact fluorescent lamps:
0
(sec) (actual: 0)

This parameter determines the time required for switching compact fluorescent lamps and certain types of light sources. Setting this parameter to 0 will disable the incandescence functionality. Available settings: 0-255 (0s - 25,5s)
Last Update: 2019-12-11 18:56:43

5. The percentage of a dimming step at automatic control:
1
(%) (actual: 1)

Available settings: 1-99 Default: 1
Last Update: 2019-12-11 18:56:43

6. Time of a dimming step at automatic control:
2
(sec) (actual: 2)

Available settings: 0-255 (0s - 2,55s) Default setting: 1
Last Update: 2019-12-11 18:56:43

7. The percentage of a dimming step at manual control:
1
(%) (actual: 1)

Available settings: 1-99 Default: 1
Last Update: 2019-12-11 18:56:43

8. Time of a dimming step at manual control:
5
(sec) (actual: 5)

Available settings: 0-255 (0s - 2,55s) Default setting: 1
Last Update: 2019-12-11 18:56:43

9. Saving state before power failure:

Saving state before power failure. Default 1.
Last Update: 2019-12-11 18:56:43

10. Timer functionality (auto - off):
0
(sec) (actual: 0)

Available settings: 0 - Function disabled; 1-32767 - time to turn off measured in seconds (1s - 9,1h) Default setting: 0
Last Update: 2019-12-11 18:56:43

11. Enable/Disable ALL ON/OFF:

Enable/Disable ALL ON/OFF. Default 255.
Last Update: 2019-12-11 18:56:43

13. Force auto-calibration:

Changing value of this parameter will force the calibration process.
Last Update: 2019-12-11 18:56:43

15. Burnt out bulb detection:
0
(%) (actual: 0)

Function based on the sudden power variation of a specific value, interpreted as a LOAD ERROR. Available settings: 0 - function disabled; 1-99 - percentage value of power variation, compared to standard power consumption, measured during the calibration procedure (to be interpreted as load error/burnt out bulb) Default setting: 30
Last Update: 2019-12-11 18:56:43

16. Time delay of a burnt out bulb:
0
(%) (actual: 0)

Time of delay (in seconds) for power variation detection, interpreted as a LOAD ERROR or OVERLOAD detection (too much power connected to the Dimmer). Available settings: 0 - detection of a burnt out bulb disabled; 1-255 - delay time in seconds; Default setting: 5
Last Update: 2019-12-11 18:56:43

19. Forced switch on brightness level:
0
(%) (actual: 0)

If the parameter is active, switching on the Dimmer (S1 single click) will always set this brightness level. Available settings: 0 - function disabled; 1-99 - percentage level of brightness; Default setting: 0
Last Update: 2019-12-11 18:56:43

20. Inputs Button/Switch configuration:

Binary inputs type configuration. Default 0.
Last Update: 2019-12-11 18:56:43

21. The value sent to associated devices on single click:

The value sent to associated devices on single click.
Last Update: 2019-12-11 18:56:43

22. Assign toggle switch status to the device status:

Last Update: 2019-12-11 18:56:43

23. Double click option:

Double-click set lighting at 100%. Default 1.
Last Update: 2019-12-11 18:56:43

24. Command frames sent in 2-nd and 3-rd association groups (S1 associations):
0
(actual: 0)

Parameter determines, which actions will not result in sending frames to association groups. Parameter values may be combined, e.g. 1+2=3 means that associations on switching on or off the Dimmer (single click) will not be sent. Available settings: 0-31 0 - all actions send to association groups; 1 - do not send when switching on the Dimmer (single click); 2 - do not send when switching off the Dimmer (single click); 4 - do not send when changing dimming level (holding and releasing); 8 - do not send on double click; 16 - send 0xFF value on double click; Default setting: 0
Last Update: 2019-12-11 18:56:43

25. Command frames sent in 4-th and 5-th association groups (S2 associations):
0
(actual: 0)

Parameter determines, which actions will not result in sending frames to association groups. Parameter values may be combined, e.g. 1+2=3 means that associations on switching on or off the Dimmer (single click) will not be sent. Available settings: 0-31 0 - all actions send to association groups; 1 - do not send when switching on the Dimmer (single click); 2 - do not send when switching off the Dimmer (single click); 4 - do not send when changing dimming level (holding and releasing); 8 - do not send on double click; 16 - send 0xFF value on double click; Default setting: 0
Last Update: 2019-12-11 18:56:43

26. The function of 3-way switch:

Switch no. 2 controls the Dimmer additionally (in 3-way switch mode). Function disabled for parameter 20 set to 2 (roller blind switch)
Last Update: 2019-12-11 18:56:43

27. Associations in Z-Wave network security mode:
15
(actual: 15)

This parameter defines how commands are sent in specified association groups: as secure or non-secure. Parameter is active only in Z-Wave network security mode. It does not apply to 1st Lifeline group. Parameter values may be combined, e.g. 1+2=3 means that 2nd & 3rd group are sent as secure. Available settings: 0-15 0 - all groups (II-V) sent as non-secure; 1 - 2nd group sent as secure; 2 - 3rd group sent as secure; 4 - 4th group sent as secure; 8 - 5th group sent as secure; 15 - all groups (II-V) sent as secure; Default setting: 15
Last Update: 2019-12-11 18:56:43

28. Scene activation functionality:

SCENE ID depends on the switch type configurations. Default 0.
Last Update: 2019-12-11 18:56:43

29. Switch functionality of S1 and S2:

Last Update: 2019-12-11 18:56:43

30. Load control mode:

Forced auto-calibration will set this parameter value to 2.
Last Update: 2019-12-11 18:56:43

32. On/Off mode:

This mode is necessary while connecting non-dimmable light sources. Setting this parameter to 1 automatically ignores brightening/dimming time settings. Forced auto-calibration will set this parameter’s value to 2
Last Update: 2019-12-11 18:56:43

34. Soft-Start functionality:

Time required to warm up the filament of halogen bulb.
Last Update: 2019-12-11 18:56:43

35. Auto-calibration after power on:

This parameter determines the trigger of auto-calibration procedure, e.g. power on, load error, etc.
Last Update: 2019-12-11 18:56:43

37. Behaviour of the Dimmer after OVERCURRENT or SURGE:

Behaviour of the Dimmer after OVERCURRENT or SURGE
Last Update: 2019-12-11 18:56:43

38. Brightness level correction for flickering loads:
255
(actual: 255)

Correction reduces spontaneous flickering of some capacitive load (e.g. dimmable lEDs) at certain brightness levels in 2-wire installation. In countries using ripple-control, correction may cause changes in brightness. In this case it is necessary to disable correction or adjust time of correction for flickering loads. Available settings: 0 - automatic correction disabled 1-254 - duration of correction in seconds 255 - automatic correction always enabled Default setting: 255
Last Update: 2019-12-11 18:56:43

39. Power limit - OVERLOAD:
250
(Watt) (actual: 250)

Reaching the defined value will result in turning off the load. Additional apparent power limit of 350VA is active by default. Available settings: 0 - functionality disabled; 1-350 - 1W-350W; Default setting: 250
Last Update: 2019-12-11 18:56:43

40. Response to General Purpose Alarm:

Response to General Purpose Alarm; Default 3.
Last Update: 2019-12-11 18:56:43

41. Response to Water Flooding Alarm:

Response to Water Flooding Alarm; Default 2.
Last Update: 2019-12-11 18:56:43

42. Response to Smoke, CO or CO2 Alarm:

Response to Smoke, CO or CO2 Alarm; Default 3.
Last Update: 2019-12-11 18:56:43

43. Response to Temperature Alarm:

Response to Temperature Alarm; Default 1.
Last Update: 2019-12-11 18:56:43

44. Time of alarm state:
600
(sec) (actual: 600)

Alarm state may be cancelled earlier, as a result of pressing the switches or sending the Z-Wave command frame.
Last Update: 2019-12-11 18:56:43

45. OVERLOAD alarm report:

OVERLOAD alarm report (load power consumption too high)
Last Update: 2019-12-11 18:56:43

46. LOAD ERROR alarm report:

LOAD ERROR alarm report (no load, load failure, burnt out bulb)
Last Update: 2019-12-11 18:56:43

47. OVERCURRENT alarm report:

OVERCURRENT alarm report (short circuit, burnt out bulb causing overcurrent)
Last Update: 2019-12-11 18:56:43

48. SURGE alarm report:

SURGE alarm report (Dimmer output overvoltage)
Last Update: 2019-12-11 18:56:43

49. OVERHEAT and VOLTAGE DROP alarm report:

OVERHEAT (critical temperature) and VOLTAGE DROP (low voltage) alarm report
Last Update: 2019-12-11 18:56:43

50. Active power reports:
1
(%) (actual: 1)

The parameter defines the power level change that will result in a new power report being sent. The value is a percentage of the previous report. Available settings: 0 - power reports disabled; 1-100 (1-100%) - power report threshold; Default setting: 10 (10%)
Last Update: 2019-12-11 18:56:43

52. Periodic active power and energy reports:
0
(sec) (actual: 0)

Parameter 52 defines a time period between consecutive reports. Timer is reset and counted from zero after each report. Available settings: 0 - periodic reports disabled; 1-32767 (1-32767 seconds); Default setting: 3600 (3600s)
Last Update: 2019-12-11 18:56:43

53. Energy reports:
0
(kWh) (actual: 0)

Energy level change which will result in sending a new energy report. Available settings: 0 - energy reports disabled; 1-255 (0,01 - 2,55 kWh) - report triggering threshold; Default setting: 10 (0,1 kWh)
Last Update: 2019-12-11 18:56:43

54. Self-measurement:

The Dimmer may include active power and energy consumed by itself in reports sent to the main controller.
Last Update: 2019-12-11 18:56:43

58. Method of calculating the active power:

This parameter defines how to calculate active power. This parameter is useful in a case of 2-wire connection with light sources other than resistive. The parameter is set to 0 after forced auto-calibration.
Last Update: 2019-12-11 18:56:43

59. Approximated power at the maximum brightness level:
0
(Watt) (actual: 0)

This parameter determines the approximate value of the power that will be reported by the device at its maximum brightness level. This parameter works only when parameter 58 has a value other than 0. Available settings: 0-500 (0-500W) - power consumed by the load at the maximum brightness level. Default setting: 0
Last Update: 2019-12-11 18:56:43

3001. Protection:

Protect a device against unintentional control

Posted: **Sunday 15 December 2019 21:42**

I used this method, as mentioned in the installation wiki: curl -L https://install.domoticz.com | bash
It was a couple of weeks ago and it gave me that version. Installed on a Raspberry Pi 2.

The setup for options 20 to 29 is:

20. Inputs Button/Switch configuration:
Mono-stable input (button)

Binary inputs type configuration. Default 0.
Last Update: 2019-12-08 15:12:47

21. The value sent to associated devices on single click:
0xFF value is sent.

The value sent to associated devices on single click.
Last Update: 2019-12-08 15:12:47

22. Assign toggle switch status to the device status:
Device changes status on switch status change

Last Update: 2019-12-08 15:12:47

23. Double click option:
Enable double click

Double-click set lighting at 100%. Default 1.
Last Update: 2019-12-08 15:12:47

24. Command frames sent in 2-nd and 3-rd association groups (S1 associations):
0
(actual: 0)

Parameter determines, which actions will not result in sending frames to association groups. Parameter values may be combined, e.g. 1+2=3 means that associations on switching on or off the Dimmer (single click) will not be sent. Available settings: 0-31 0 - all actions send to association groups; 1 - do not send when switching on the Dimmer (single click); 2 - do not send when switching off the Dimmer (single click); 4 - do not send when changing dimming level (holding and releasing); 8 - do not send on double click; 16 - send 0xFF value on double click; Default setting: 0
Last Update: 2019-12-08 15:12:47

25. Command frames sent in 4-th and 5-th association groups (S2 associations):
0
(actual: 0)

Parameter determines, which actions will not result in sending frames to association groups. Parameter values may be combined, e.g. 1+2=3 means that associations on switching on or off the Dimmer (single click) will not be sent. Available settings: 0-31 0 - all actions send to association groups; 1 - do not send when switching on the Dimmer (single click); 2 - do not send when switching off the Dimmer (single click); 4 - do not send when changing dimming level (holding and releasing); 8 - do not send on double click; 16 - send 0xFF value on double click; Default setting: 0
Last Update: 2019-12-08 15:12:47

26. The function of 3-way switch:
3-way switch function for s2 disabled

Switch no. 2 controls the Dimmer additionally (in 3-way switch mode). Function disabled for parameter 20 set to 2 (roller blind switch)
Last Update: 2019-12-08 15:12:47

27. Associations in Z-Wave network security mode:
15
(actual: 15)

This parameter defines how commands are sent in specified association groups: as secure or non-secure. Parameter is active only in Z-Wave network security mode. It does not apply to 1st Lifeline group. Parameter values may be combined, e.g. 1+2=3 means that 2nd & 3rd group are sent as secure. Available settings: 0-15 0 - all groups (II-V) sent as non-secure; 1 - 2nd group sent as secure; 2 - 3rd group sent as secure; 4 - 4th group sent as secure; 8 - 5th group sent as secure; 15 - all groups (II-V) sent as secure; Default setting: 15
Last Update: 2019-12-08 15:12:47

28. Scene activation functionality:
Function activated

SCENE ID depends on the switch type configurations. Default 0.
Last Update: 2019-12-08 15:12:47

29. Switch functionality of S1 and S2:
standard mode

Last Update: 2019-12-08 15:12:47

So I modified the option 23 to 'disabled'.

It might be worth mentioning that I have walked through our house with the Aeotec stick to associate the devices and experimented on Windows a bit before connecting the stick to the Raspberry Pi. Could that have done something wrong with the ZWave configuration?

Posted: **Monday 16 December 2019 8:53**

no i do not think so.

somehow the FGD212 is not generating new devices when you click the buttons.

maybee it is a good idea to install winscp on your pc and try to make a connection with the pi.

if you are able to browse through the files i can tell you how to delete the cache file.(make a copy to be save)
This resets the devices and domoticz will add then automatically to the system.

when you first installed domoticz and had the ACCEPT NEW HARDWARE DEVICES set to on it discovers each device and puts them in a file called zwcfg_0xxxxxxx.xml
this file is in the domoticz/var directory.

when you delete this file, stop domoticz and start it up again in collects all the devices again.
i think something went wrong in there.

Posted: **Monday 16 December 2019 22:45**

I found the file here: /home/pi/domoticz/Config.
I assume that's the correct one?

Posted: **Tuesday 17 December 2019 8:19**

yes.

just one check to know for sure the FGD212 is set correctly
go to setup hardware-zwave setup
select the fgd212
press the request current values from device
press ok
select the fgd212
press the request current values from device
press ok
select the fgd212

go to register 28
is the scene functionality enabled?

sometimes what you see on the screen in not what is actual in the device(hence the request values twice)

make a backup from the zw file(rename it with the .org extention) just in case

delete the original file (keep the backup)
make sure the ACCEPT NEW HARDWARE DEVICES option is set to ON in the domoticz settings

stop domoticz
start domoticz

if you look in the log after starting up domoticz you see that it discovers all the devices again.
if you have devices with batteries this will take longer(or you need to press the wake up button)

if this does not solve he problem then my only guess is the 717 verion is the one in which the scenes are deactivated

in case things go wrong
stop domoticz
restore the old cache file
start domoticz

Posted: **Tuesday 17 December 2019 22:36**

Thanks a lot for helping me out here!

I just did that procedure to get the stored values from the device and option 28 remains on 'functionality enabled'.

So, remove the config file, restart domoticz and indeed all devices are discovered again.

Then, the magic moment and the button is now recognized as a scene activator!

Very grateful!

Posted: **Wednesday 18 December 2019 8:14**

glad i could help You out.

You can now also create the other scenes (double click, triple click, clikc and hold)
click and hold is my favorite, i use it to turn of all my lights.

sometimes when there are a lot of changes regarding zwave functionality(changes in device configs) it is always good to do this procedure.

i think your stable version still works with zwave v1.4

newer builds(anything newer then v4.10734) use zw1.6
this change initially caused a lot of problems with devicefiles needed to be changed.
We have had al that and also that version is running very stable.

fyi, the cache file in those versions is called ozwcachexxxx

same procedure applies whenever you need to refresh domoticz

Posted: **Wednesday 18 December 2019 16:02**

Yes, that also works fine now. I was thinking about a toggle switch, but as not all lights might be on or off, that would make things not work as expcted (e.g. 1 out of 3 lights is on, I click the button once and what should it do? turn everything on or off). So this is definitely a better solution.

I don't understand why I got this old version if I installed via the recommended method (domoticz.sh).

Posted: **Wednesday 18 December 2019 16:19**

toggle switch is easy but like you said all the lights need to be either on or off

of course if this is not the case you can still toggle but the lights on will go off and the lights off will go on

first i did toggle by using a toggle script.

now i found an easier solution

let's say you have a light or group with idx 99 which you would like to toggle

make a new scene and give it the name lights-Toggle
add the right activation device to this scene (eg double click or clik and hold)
now go to the on /off actions of that scene and put in(change ip adrees and port to your setup)

on action :http://192.168.1.50:8084/json.htm?type= ... cmd=Toggle
off action:http://192.168.1.50:8084/json.htm?type= ... cmd=Toggle

now whenever you press the activation device it toggles the light or group you put in the on/off action field

ofcourse this is a workaround but until native support comes along this is the way to go.

if you really only want to toggle the lights which are on you need to do this in dzvents and write a script.
is not thatr difficult i think (and i am a noob with dzvents)

Domoticz

Fibaro FGD212 S2 button as activator / deactivator

Fibaro FGD212 S2 button as activator / deactivator

Re: Fibaro FGD212 S2 button as activator / deactivator

Re: Fibaro FGD212 S2 button as activator / deactivator

Re: Fibaro FGD212 S2 button as activator / deactivator

Re: Fibaro FGD212 S2 button as activator / deactivator

Re: Fibaro FGD212 S2 button as activator / deactivator

Re: Fibaro FGD212 S2 button as activator / deactivator

Re: Fibaro FGD212 S2 button as activator / deactivator

Re: Fibaro FGD212 S2 button as activator / deactivator

Re: Fibaro FGD212 S2 button as activator / deactivator

Re: Fibaro FGD212 S2 button as activator / deactivator

Re: Fibaro FGD212 S2 button as activator / deactivator

Re: Fibaro FGD212 S2 button as activator / deactivator

Re: Fibaro FGD212 S2 button as activator / deactivator

Re: Fibaro FGD212 S2 button as activator / deactivator