New Fibaro Switch FGS-223 is driving me nuts

chris · December 28, 2016, 11:02am

Should this be command=METER?

ewgor · December 28, 2016, 11:43am

Thanks

ossostborn · December 30, 2016, 9:56pm

FGS-223 and FGS-213 should have the same parameters.

Parameter 30 (35) must have an range from 0 to 15 (like 28 and 29)
in HABmin I can set parameter 28 to 15 but 29 is only selectable (OH2)
in OH2 I can only select. combinations are not possible
FGS 213: Missing all the parameters > 33
to write the changes to the unit I’ve to restart OH2. All the parameters I did change are marked with the yellow label that the changes will be writen to the unit.

If you need an log I’ll add.

sihui · December 31, 2016, 7:09am

The changes to the database where made three days ago, you might need to wait until the changes make it into the binding.
Then you need to uninstall the binding, wait a short while (a minute or so) and install it again.
Then delete the thing and add it again and you will see the newly added/changed parameters.

Although this won’t help you with the FGS213 parameters > 33: nobody added those into the database yet.
If you want to add them read:
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide
Would be great to have one more user who performs regularly updates on devices

ossostborn · January 1, 2017, 10:58am

I did ask already for the right some weeks before… until now I can’t.

I can’t see in the database:
http://cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/423
It ends at 33.

sihui · January 1, 2017, 11:25am

If you have succesfully registered on the website email chris at chris@cd-jackson.com to ask for edit rights. Don’t forget to mention your username (website username) in that email.
It’s always best that users who own that specific device make database additions …

sihui · January 1, 2017, 11:40am

Then we should ping @chris if he is able to find that email …

chris · January 1, 2017, 11:46am

As far as I can tell, you should have edit access

What actually “ends at 33”? The database has something like 450 entries, so I’m not sure why you would only see 33 of them. Even without edit access, you should still be able to see everything…

ossostborn · January 1, 2017, 12:17pm

Both Fibaro FGS-223 and FGS-213 has the same parametes.

I can see all the parameters for the FGS-223 device. FDS-213 ends with parameter 33 in data base. Until I can make changes … I must hope someone has to muich time

chris · January 1, 2017, 12:24pm

Ok - sorry. I misunderstood what you meant.

Please can you let me know what user name you are using so I can give you access. There is a user with your name in the user list, and I gave that user edit rights some time ago. If that is not you, then I need to look at what is happening.

chris · January 1, 2017, 12:39pm

Maybe the issue is your username here is ossostborn and on the database site it’s ossiostborn? I’m not sure if that’s on purpose or a typo?

ossostborn · January 1, 2017, 1:00pm

you are right Chris.

smee204 · January 5, 2017, 6:43pm

Did you manage to get it working on OH1?

I have a FGS-223 (double switch 2) and openhab is not updating the status of the switches. In the debug log I get messages such as:

NODE 6: No item bound for event, endpoint = 0, command class = BASIC, value = 255, ignoring.

Looking at the code the calls to “zwaveCommandClass.handleApplicationCommandRequest” are hard-coded with the endpoint set to 0. Is this because it is not implemented in OH1?

chris · January 5, 2017, 6:47pm

No - it’s because that’s the way zwave works. All command classes received at this level are for endpoint 0.

You don’t provide a lot of information about your configuration, but are you handling the basic command class in your item configurations?

smee204 · January 5, 2017, 7:12pm

I believe I am handling the basic command class. I have the following in my items file:

Switch	outsideLight	"Outside Light"	<light>	(LIGHTS)		{ zwave="6:1:command=switch_binary,respond_to_basic=true" }
Switch	hallLight	"HallLight"	<light>	(LIGHTS)		{ zwave="6:2:command=switch_binary,respond_to_basic=true" }

Here is the full log of what happens when I press one of the physical light switches:

2017-01-05 19:08:10.035 [DEBUG] [eController$ZWaveReceiveThread:1601]- Receive Message = 01 09 00 04 08 06 03 20 01 00 DE 
2017-01-05 19:08:10.036 [DEBUG] [eController$ZWaveReceiveThread:1517]- Receive queue ADD: Length=1
2017-01-05 19:08:10.036 [DEBUG] [b.z.i.protocol.ZWaveController:1244]- Receive queue TAKE: Length=0
2017-01-05 19:08:10.036 [DEBUG] [o.b.z.i.protocol.SerialMessage:255 ]- Assembled message buffer = 01 09 00 04 08 06 03 20 01 00 DE 
2017-01-05 19:08:10.036 [DEBUG] [b.z.i.protocol.ZWaveController:1245]- Process Message = 01 09 00 04 08 06 03 20 01 00 DE 
2017-01-05 19:08:10.036 [DEBUG] [b.z.i.protocol.ZWaveController:200 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 08 06 03 20 01 00 , callbackid = 0
2017-01-05 19:08:10.037 [DEBUG] [ApplicationCommandMessageClass:41  ]- NODE 6: Application Command Request (ALIVE:DONE)
2017-01-05 19:08:10.037 [DEBUG] [ApplicationCommandMessageClass:146 ]- NODE 6: Incoming command class BASIC (0x20)
2017-01-05 19:08:10.037 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:73  ]- NODE 6: Received Basic Request
2017-01-05 19:08:10.037 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:77  ]- NODE 6: Basic Set sent to the controller will be processed as Basic Report
2017-01-05 19:08:10.037 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:106 ]- NODE 6: Basic report, value = 0x00
2017-01-05 19:08:10.037 [DEBUG] [b.z.i.protocol.ZWaveController:668 ]- NODE 6: Notifying event listeners: ZWaveCommandClassValueEvent
2017-01-05 19:08:10.037 [DEBUG] [.z.internal.ZWaveActiveBinding:455 ]- ZwaveIncomingEvent
2017-01-05 19:08:10.037 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ]- NODE 6: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 0
2017-01-05 19:08:10.037 [WARN ] [.z.internal.ZWaveActiveBinding:491 ]- NODE 6: No item bound for event, endpoint = 0, command class = BASIC, value = 0, ignoring.
2017-01-05 19:08:10.037 [DEBUG] [ApplicationCommandMessageClass:122 ]- NODE 5: Transaction not completed: node address inconsistent.  lastSent=5, incoming=255
2017-01-05 19:08:10.050 [DEBUG] [eController$ZWaveReceiveThread:1601]- Receive Message = 01 09 00 04 00 06 03 20 01 00 D6 
2017-01-05 19:08:10.051 [DEBUG] [eController$ZWaveReceiveThread:1517]- Receive queue ADD: Length=1
2017-01-05 19:08:10.052 [DEBUG] [b.z.i.protocol.ZWaveController:1244]- Receive queue TAKE: Length=0
2017-01-05 19:08:10.052 [DEBUG] [o.b.z.i.protocol.SerialMessage:255 ]- Assembled message buffer = 01 09 00 04 00 06 03 20 01 00 D6 
2017-01-05 19:08:10.052 [DEBUG] [b.z.i.protocol.ZWaveController:1245]- Process Message = 01 09 00 04 00 06 03 20 01 00 D6 
2017-01-05 19:08:10.052 [DEBUG] [b.z.i.protocol.ZWaveController:200 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 06 03 20 01 00 , callbackid = 0
2017-01-05 19:08:10.052 [DEBUG] [ApplicationCommandMessageClass:41  ]- NODE 6: Application Command Request (ALIVE:DONE)
2017-01-05 19:08:10.052 [DEBUG] [ApplicationCommandMessageClass:146 ]- NODE 6: Incoming command class BASIC (0x20)
2017-01-05 19:08:10.052 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:73  ]- NODE 6: Received Basic Request
2017-01-05 19:08:10.052 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:77  ]- NODE 6: Basic Set sent to the controller will be processed as Basic Report
2017-01-05 19:08:10.052 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:106 ]- NODE 6: Basic report, value = 0x00
2017-01-05 19:08:10.052 [DEBUG] [b.z.i.protocol.ZWaveController:668 ]- NODE 6: Notifying event listeners: ZWaveCommandClassValueEvent
2017-01-05 19:08:10.052 [DEBUG] [.z.internal.ZWaveActiveBinding:455 ]- ZwaveIncomingEvent
2017-01-05 19:08:10.052 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ]- NODE 6: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 0
2017-01-05 19:08:10.053 [WARN ] [.z.internal.ZWaveActiveBinding:491 ]- NODE 6: No item bound for event, endpoint = 0, command class = BASIC, value = 0, ignoring.
2017-01-05 19:08:10.053 [DEBUG] [ApplicationCommandMessageClass:122 ]- NODE 5: Transaction not completed: node address inconsistent.  lastSent=5, incoming=255

I have the controller in the following association groups: Lifeline, ON/OFF (S1) and ON/OFF (S2).

chris · January 5, 2017, 7:15pm

Ok, but you don’t handle endpoint 0 like the error is saying ;)…

With some of the newer Fibaro devices, when you manually change the switch they don’t use the multi channel command class - they send from the root device. You therefore can’t use multi channel for switch 1 - you should use endpoint 0. That should solve the problem.

smee204 · January 5, 2017, 7:33pm

Ah I see. So it sends from the root device but does it specify which switch has changed?

I have changed it to:

Switch	outsideLight	"Outside Light"	<light>	(LIGHTS)		{ zwave="6:command=switch_binary,respond_to_basic=true" }
Switch	hallLight	"HallLight"	<light>	(LIGHTS)		{ zwave="6:2:command=switch_binary,respond_to_basic=true" }

Now the status is updated however the status of outsideLight is modified no matter which switch is pressed. Is there anyway to update the status of hallLight as well?

chris · January 5, 2017, 7:36pm

Hmm - I thought from previous experience with these switches that endpoint 0 was the same as endpoint 1 (this is also how it is written in the zwave standard). What happens when you press switch 2 - does it send exactly the same thing as switch 1 or is it MC encapsulated?

If it always sends the same thing, then this switch might now be using the same strategy as the new Qubino switches. Is this a new switch?

smee204 · January 5, 2017, 7:55pm

It looks like when I press switch2 exactly the same thing is sent so endpoint 0 is always updated.
This is a FGS-223 which is new.

chris · January 5, 2017, 7:56pm

Ok, then I guess Fibaro has updated their code to use the same concept as Qubino are using. The bad news is that this isn’t supported in OH1 - probably, if it’s the same issue as Qubino, then it should work in OH2.