New Fibaro switches FGS-213/223

Hi again if anyone sees this.
Here are the details from this Fibaro FGS-223 when NULL appears -

Hi There

I am trying to resolve the issue with Switch endpoint 2 reporting NULL from a Fibaro FGS-223 Dual Switch 2.
Do you have any ideas given you are the expert?

So I turned the Physical Switch 1 on and then Physical switch 2 on, then both off.
Here is the Log from this.
Any ideas what is causing the NULL status?

5037fc93-7535-4df6-9364-837f7469f4eb 7:27:21 PM: debug Parsed SecurityMessageEncapsulation(commandByte: [2, 1, 37, 3, 0], commandClassIdentifier: 96, commandIdentifier: 13, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [['name':switch2, 'value':'off', 'isStateChange':true, 'displayed':true, 'linkText':'KitchenS1', 'descriptionText':KitchenS1 switch2 is off], ['name':'switch', 'value':'off', 'isStateChange':false, 'displayed':false, 'linkText':'KitchenS1', 'descriptionText':KitchenS1 switch is off]]

5037fc93-7535-4df6-9364-837f7469f4eb 7:27:21 PM: debug MultiChannelCmdEncap MultiChannelCmdEncap(bitAddress: false, command: 3, commandClass: 37, destinationEndPoint: 1, parameter: [0], sourceEndPoint: 2)
5037fc93-7535-4df6-9364-837f7469f4eb 7:27:20 PM: debug Parsed SecurityMessageEncapsulation(commandByte: [1, 1, 37, 3, 0], commandClassIdentifier: 96, commandIdentifier: 13, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘name’:switch1, ‘value’:‘off’, ‘isStateChange’:true, ‘displayed’:true, ‘linkText’:‘KitchenS1’, ‘descriptionText’:KitchenS1 switch1 is off]]
5037fc93-7535-4df6-9364-837f7469f4eb 7:27:20 PM: debug MultiChannelCmdEncap MultiChannelCmdEncap(bitAddress: false, command: 3, commandClass: 37, destinationEndPoint: 1, parameter: [0], sourceEndPoint: 1)
5037fc93-7535-4df6-9364-837f7469f4eb 7:27:07 PM: debug Parsed SecurityMessageEncapsulation(commandByte: [2, 0, 38, 1, 0, 0], commandClassIdentifier: 96, commandIdentifier: 13, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘name’:switch2, ‘isStateChange’:true, ‘displayed’:true, ‘linkText’:‘KitchenS1’]]
5037fc93-7535-4df6-9364-837f7469f4eb 7:27:07 PM: debug MultiChannelCmdEncap MultiChannelCmdEncap(bitAddress: false, command: 1, commandClass: 38, destinationEndPoint: 0, parameter: [0, 0], sourceEndPoint: 2)
5037fc93-7535-4df6-9364-837f7469f4eb 7:27:07 PM: debug Parsed SecurityMessageEncapsulation(commandByte: [2, 0, 32, 1, 0], commandClassIdentifier: 96, commandIdentifier: 13, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘name’:switch2, ‘value’:‘off’, ‘isStateChange’:true, ‘displayed’:true, ‘linkText’:‘KitchenS1’, ‘descriptionText’:KitchenS1 switch2 is off]]
5037fc93-7535-4df6-9364-837f7469f4eb 7:27:07 PM: debug MultiChannelCmdEncap MultiChannelCmdEncap(bitAddress: false, command: 1, commandClass: 32, destinationEndPoint: 0, parameter: [0], sourceEndPoint: 2)
5037fc93-7535-4df6-9364-837f7469f4eb 7:27:01 PM: debug Parsed SecurityMessageEncapsulation(commandByte: [2, 0, 38, 1, 255, 0], commandClassIdentifier: 96, commandIdentifier: 13, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘name’:switch2, ‘isStateChange’:true, ‘displayed’:true, ‘linkText’:‘KitchenS1’]]
5037fc93-7535-4df6-9364-837f7469f4eb 7:27:01 PM: debug MultiChannelCmdEncap MultiChannelCmdEncap(bitAddress: false, command: 1, commandClass: 38, destinationEndPoint: 0, parameter: [255, 0], sourceEndPoint: 2)
5037fc93-7535-4df6-9364-837f7469f4eb 7:27:00 PM: debug Parsed SecurityMessageEncapsulation(commandByte: [2, 0, 32, 1, 255], commandClassIdentifier: 96, commandIdentifier: 13, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘name’:switch2, ‘value’:‘on’, ‘isStateChange’:true, ‘displayed’:true, ‘linkText’:‘KitchenS1’, ‘descriptionText’:KitchenS1 switch2 is on], [‘name’:‘switch’, ‘value’:‘on’, ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘KitchenS1’, ‘descriptionText’:KitchenS1 switch is on]]
5037fc93-7535-4df6-9364-837f7469f4eb 7:27:00 PM: debug MultiChannelCmdEncap MultiChannelCmdEncap(bitAddress: false, command: 1, commandClass: 32, destinationEndPoint: 0, parameter: [255], sourceEndPoint: 2)
5037fc93-7535-4df6-9364-837f7469f4eb 7:26:54 PM: debug Parsed Crc16Encap(checksum: 128, command: 2, commandClass: 50, data: [33, 50, 0, 216, 0, 0, 167]) to [[‘descriptionText’:KitchenS1: Crc16Encap(checksum: 128, command: 2, commandClass: 50, data: [33, 50, 0, 216, 0, 0, 167]), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘KitchenS1’]]
5037fc93-7535-4df6-9364-837f7469f4eb 7:26:54 PM: debug Unhandled event Crc16Encap(checksum: 128, command: 2, commandClass: 50, data: [33, 50, 0, 216, 0, 0, 167])
5037fc93-7535-4df6-9364-837f7469f4eb 7:26:53 PM: debug Parsed SecurityMessageEncapsulation(commandByte: [1, 1, 37, 3, 255], commandClassIdentifier: 96, commandIdentifier: 13, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘name’:switch1, ‘value’:‘on’, ‘isStateChange’:true, ‘displayed’:true, ‘linkText’:‘KitchenS1’, ‘descriptionText’:KitchenS1 switch1 is on], [‘name’:‘switch’, ‘value’:‘on’, ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘KitchenS1’, ‘descriptionText’:KitchenS1 switch is on]]
5037fc93-7535-4df6-9364-837f7469f4eb 7:26:53 PM: debug MultiChannelCmdEncap MultiChannelCmdEncap(bitAddress: false, command: 3, commandClass: 37, destinationEndPoint: 1, parameter: [255], sourceEndPoint: 1)
5037fc93-7535-4df6-9364-837f7469f4eb 7:26:51 PM: debug Parsed SecurityMessageEncapsulation(commandByte: [255], commandClassIdentifier: 37, commandIdentifier: 3, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [physicalgraph.device.HubMultiAction@77cd47a1]
5037fc93-7535-4df6-9364-837f7469f4eb 7:26:51 PM: debug SwitchBinaryReport SwitchBinaryReport(value: 255)

Here is the Logs as I hit the Configure button -
5037fc93-7535-4df6-9364-837f7469f4eb 7:12:31 PM: debug Parsed SecurityMessageEncapsulation(commandByte: [5, 5, 0, 1], commandClassIdentifier: 133, commandIdentifier: 3, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [1]
5037fc93-7535-4df6-9364-837f7469f4eb 7:12:31 PM: debug AssociationReport AssociationReport(groupingIdentifier: 5, maxNodesSupported: 5, nodeId: [1], reportsToFollow: 0)
5037fc93-7535-4df6-9364-837f7469f4eb 7:12:27 PM: debug Parsed SecurityMessageEncapsulation(commandByte: [4, 5, 0, 1], commandClassIdentifier: 133, commandIdentifier: 3, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [1]
5037fc93-7535-4df6-9364-837f7469f4eb 7:12:27 PM: debug AssociationReport AssociationReport(groupingIdentifier: 4, maxNodesSupported: 5, nodeId: [1], reportsToFollow: 0)
5037fc93-7535-4df6-9364-837f7469f4eb 7:12:25 PM: debug Setting association group 5
5037fc93-7535-4df6-9364-837f7469f4eb 7:12:25 PM: debug Setting association group 4
5037fc93-7535-4df6-9364-837f7469f4eb 7:12:25 PM: debug configure() called

Hi Nigel I am new to this and experimenting with the fibario 223. I have loaded the handlers erocm123. How do I create the virtual switches and link them to fibario 223?

This is a great tool:

1 Like

Create 2x Virtual Switches using erocm123 Virtual Switch device, then use his SmartApp Virtual /Physical Switch Sync to link the Physical Switch with the 2 Virtual switches

1 Like

Thank you for the reply I have done the following so far

  1. I have loaded the handler ercom123
  2. I have created the smartapp sync to link the physical switches
    3 I have created two virtual switches using simulated switch handler

From this point I am stuck the physical switch is recognised as a dimmer (I pressed the S1 three times and got the hub to recognise it as a Z wave device multichannel) I presume this is the physical switch you are referring to. when I try to link the physical switch to the virtual switch it comes up as Device Handler Z-wave Multichannel detected number of end points 0 virtual switch type dimmer.

How do I get this to use the ercom123 dual device relay handler

thanks for your help

Go to IDE and My Devices.

Find your device and click on it

At the bottom click Edit, then change “Type” to the new handler

@erocm1231 I have installed the latest version of this handler. I have tested with a toggle switch and it works well, status is updated correctly for both switches. But I want to use a momentary switch. Any way to change the config parameter? I see there is something in the code with setting switch type, but its not activated

I managed to enable it my self, just had to change the config parameter to from 3 to 20 also.

I can now change switch type from the app, and I can get it to work with both type of switches.
Status is also updated correctly in the app when using the wall switch.

1 Like

The big on/off tile is not doing anything for me. It updates correct status, but do not turn anything on or off when pressing it.

Any plans to add power meter reports? Then this handler would be complete :slight_smile:

I have managed to change the handler to erocm 123 however as soon as i did that the switch stops working. if i revert back to the original handler it works am i missing a step? please help

@cscheiene Yeah, I’ll add power and energy. I posted an update that enables some configuration options. There is supposedly scene ID reports for double click, triple click, press & hold, but no documentation of what they are. You can enable them in the preferences, try them out, and post the logs.

@irfsay From the SmartThings app if you tap on switch 1 and switch 2 it does not control the lights? Please post the logs when doing so.

Take it easy on me, I’ve developed this handler without having the device. :wink: Wish they would release it in the US.

1 Like

Thanks again for doing this. I have installed the latest handler and here are some findings:

On the main page of the device it always says "Pending"
Here are the logs from when i press “Done” in the configuration page

f705e370-1091-4840-a15f-1e313eed516a 08.48.18 CEST: debug Parsed SecurityMessageEncapsulation(commandByte: [29, 1, 0], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘descriptionText’:Fibaro Relay: ConfigurationReport(configurationValue: [0], parameterNumber: 29, reserved11: 0, size: 1), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Fibaro Relay’]]
f705e370-1091-4840-a15f-1e313eed516a 08.48.18 CEST: debug Unhandled event ConfigurationReport(configurationValue: [0], parameterNumber: 29, reserved11: 0, size: 1)
f705e370-1091-4840-a15f-1e313eed516a 08.48.18 CEST: debug Parsed SecurityMessageEncapsulation(commandByte: [28, 1, 0], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘descriptionText’:Fibaro Relay: ConfigurationReport(configurationValue: [0], parameterNumber: 28, reserved11: 0, size: 1), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Fibaro Relay’]]
f705e370-1091-4840-a15f-1e313eed516a 08.48.18 CEST: debug Unhandled event ConfigurationReport(configurationValue: [0], parameterNumber: 28, reserved11: 0, size: 1)
f705e370-1091-4840-a15f-1e313eed516a 08.48.15 CEST: debug Parsed SecurityMessageEncapsulation(commandByte: [59, 2, 14, 16], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘descriptionText’:Fibaro Relay: ConfigurationReport(configurationValue: [14, 16], parameterNumber: 59, reserved11: 0, size: 2), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Fibaro Relay’]]
f705e370-1091-4840-a15f-1e313eed516a 08.48.15 CEST: debug Unhandled event ConfigurationReport(configurationValue: [14, 16], parameterNumber: 59, reserved11: 0, size: 2)
f705e370-1091-4840-a15f-1e313eed516a 08.48.15 CEST: debug Parsed SecurityMessageEncapsulation(commandByte: [58, 2, 14, 16], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘descriptionText’:Fibaro Relay: ConfigurationReport(configurationValue: [14, 16], parameterNumber: 58, reserved11: 0, size: 2), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Fibaro Relay’]]
f705e370-1091-4840-a15f-1e313eed516a 08.48.15 CEST: debug Unhandled event ConfigurationReport(configurationValue: [14, 16], parameterNumber: 58, reserved11: 0, size: 2)
f705e370-1091-4840-a15f-1e313eed516a 08.48.12 CEST: debug Parsed SecurityMessageEncapsulation(commandByte: [57, 2, 0, 100], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘descriptionText’:Fibaro Relay: ConfigurationReport(configurationValue: [0, 100], parameterNumber: 57, reserved11: 0, size: 2), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Fibaro Relay’]]
f705e370-1091-4840-a15f-1e313eed516a 08.48.12 CEST: debug Unhandled event ConfigurationReport(configurationValue: [0, 100], parameterNumber: 57, reserved11: 0, size: 2)
f705e370-1091-4840-a15f-1e313eed516a 08.48.12 CEST: debug Parsed SecurityMessageEncapsulation(commandByte: [55, 1, 10], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘descriptionText’:Fibaro Relay: ConfigurationReport(configurationValue: [10], parameterNumber: 55, reserved11: 0, size: 1), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Fibaro Relay’]]
f705e370-1091-4840-a15f-1e313eed516a 08.48.12 CEST: debug Unhandled event ConfigurationReport(configurationValue: [10], parameterNumber: 55, reserved11: 0, size: 1)
f705e370-1091-4840-a15f-1e313eed516a 08.48.09 CEST: debug Parsed SecurityMessageEncapsulation(commandByte: [54, 1, 20], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘descriptionText’:Fibaro Relay: ConfigurationReport(configurationValue: [20], parameterNumber: 54, reserved11: 0, size: 1), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Fibaro Relay’]]
f705e370-1091-4840-a15f-1e313eed516a 08.48.09 CEST: debug Unhandled event ConfigurationReport(configurationValue: [20], parameterNumber: 54, reserved11: 0, size: 1)
f705e370-1091-4840-a15f-1e313eed516a 08.48.09 CEST: debug Parsed SecurityMessageEncapsulation(commandByte: [53, 2, 0, 100], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘descriptionText’:Fibaro Relay: ConfigurationReport(configurationValue: [0, 100], parameterNumber: 53, reserved11: 0, size: 2), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Fibaro Relay’]]
f705e370-1091-4840-a15f-1e313eed516a 08.48.09 CEST: debug Unhandled event ConfigurationReport(configurationValue: [0, 100], parameterNumber: 53, reserved11: 0, size: 2)
f705e370-1091-4840-a15f-1e313eed516a 08.48.06 CEST: debug Parsed SecurityMessageEncapsulation(commandByte: [51, 1, 10], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘descriptionText’:Fibaro Relay: ConfigurationReport(configurationValue: [10], parameterNumber: 51, reserved11: 0, size: 1), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Fibaro Relay’]]
f705e370-1091-4840-a15f-1e313eed516a 08.48.06 CEST: debug Unhandled event ConfigurationReport(configurationValue: [10], parameterNumber: 51, reserved11: 0, size: 1)
f705e370-1091-4840-a15f-1e313eed516a 08.48.06 CEST: debug Parsed SecurityMessageEncapsulation(commandByte: [50, 1, 20], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘descriptionText’:Fibaro Relay: ConfigurationReport(configurationValue: [20], parameterNumber: 50, reserved11: 0, size: 1), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Fibaro Relay’]]
f705e370-1091-4840-a15f-1e313eed516a 08.48.06 CEST: debug Unhandled event ConfigurationReport(configurationValue: [20], parameterNumber: 50, reserved11: 0, size: 1)
f705e370-1091-4840-a15f-1e313eed516a 08.48.03 CEST: debug Parsed SecurityMessageEncapsulation(commandByte: [20, 1, 0], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘descriptionText’:Fibaro Relay: ConfigurationReport(configurationValue: [0], parameterNumber: 20, reserved11: 0, size: 1), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Fibaro Relay’]]
f705e370-1091-4840-a15f-1e313eed516a 08.48.03 CEST: debug Unhandled event ConfigurationReport(configurationValue: [0], parameterNumber: 20, reserved11: 0, size: 1)
f705e370-1091-4840-a15f-1e313eed516a 08.48.02 CEST: debug Parsed SecurityMessageEncapsulation(commandByte: [9, 1, 1], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false) to [[‘descriptionText’:Fibaro Relay: ConfigurationReport(configurationValue: [1], parameterNumber: 9, reserved11: 0, size: 1), ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Fibaro Relay’]]
f705e370-1091-4840-a15f-1e313eed516a 08.48.02 CEST: debug Unhandled event ConfigurationReport(configurationValue: [1], parameterNumber: 9, reserved11: 0, size: 1)
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 29 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 28 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 59 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 58 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 57 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 55 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 54 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 53 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 51 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 50 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 20 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 9 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug updated() is being called
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug 15
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 29 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 28 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 59 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 58 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 57 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 55 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 54 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 53 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 51 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 50 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 20 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug Current value of parameter 9 is unknown
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug updated() is being called
f705e370-1091-4840-a15f-1e313eed516a 08.48.01 CEST: debug 15

And here is from when I press the “Pending” tile:

f705e370-1091-4840-a15f-1e313eed516a 09.49.35 CEST: debug Current value of parameter 29 is unknown
f705e370-1091-4840-a15f-1e313eed516a 09.49.35 CEST: debug Current value of parameter 28 is unknown
f705e370-1091-4840-a15f-1e313eed516a 09.49.35 CEST: debug Current value of parameter 59 is unknown
f705e370-1091-4840-a15f-1e313eed516a 09.49.35 CEST: debug Current value of parameter 58 is unknown
f705e370-1091-4840-a15f-1e313eed516a 09.49.35 CEST: debug Current value of parameter 57 is unknown
f705e370-1091-4840-a15f-1e313eed516a 09.49.35 CEST: debug Current value of parameter 55 is unknown
f705e370-1091-4840-a15f-1e313eed516a 09.49.35 CEST: debug Current value of parameter 54 is unknown
f705e370-1091-4840-a15f-1e313eed516a 09.49.35 CEST: debug Current value of parameter 53 is unknown
f705e370-1091-4840-a15f-1e313eed516a 09.49.35 CEST: debug Current value of parameter 51 is unknown
f705e370-1091-4840-a15f-1e313eed516a 09.49.35 CEST: debug Current value of parameter 50 is unknown
f705e370-1091-4840-a15f-1e313eed516a 09.49.35 CEST: debug Current value of parameter 20 is unknown
f705e370-1091-4840-a15f-1e313eed516a 09.49.35 CEST: debug Current value of parameter 9 is unknown
f705e370-1091-4840-a15f-1e313eed516a 09.49.35 CEST: debug Configuring Device For SmartThings Use

I’ve uploaded a new version of the handler. Can you test the configuration again? If it works test the double and triple tap features. Also, if there are any energy reports coming in, post their logs as well. I’ll need those to add that functionality. If you want to PM me we can continue this and not add any more static to this thread.

Eric

Can you explain the double/triple tap feature please?
Is this the physical switch or the Device Handler?

Hi Nigel, the double & triple tap features allow you to create SmartThings automations based on those actions at the physical switch. When I am done with the handler, you will be able to double tap the light switch and it will send a button event. Then you can configure any automation to respond to that button event. For example, if I had the Fibaro Relay on a light switch that was at my front door, I could configure a triple tap to turn off all the lights in the house. That way, when I was on my way out of the house, a quick triple click could turn off everything. Does that make sense?

1 Like

just love the work you do on this @erocm1231 :slight_smile:

Is there any chance it will work for the single version FGS-213 as well?
I see that the testing is mostly done with the FGS-223.
You think I could test this one as it is?

Regards

I believe several functions won’t work. Z-wave handles multichannel devices (which is what the dual relays are) with a special set of commands. The framework is pretty much in place though, so we could just remove the unneeded tiles and change the zwave commands that get sent and parsed. I wouldn’t mind taking a look once the dual relay is finished.

1 Like