Fibaro swipe support in the future?

Hardware Home Automation
,
41

Hi @chris

For fibaro swipe device ,

  1. OH version supported…?
  2. zwave binding version supported…?
42

I know from this thread that people are using it on OH2 - that’s all I know though as I don’t have this device.

43

Hi @Shrikant_Lahase, OH 2 latest version and latest zwave binding should work fine.

44

Hi Chris, I just received my Fibaro Swipe, but it doesn’t seam to work right on my OH2. I don’t found any documentation on how to set the device parameters. I’ve currently set the following:

Device Parameters:
5 = 4
6 = Standby Mode
10 = All commands enabled
11 = Security enabled for all gestures
12 = Toggle mode enabled for all gestures
13 = 255
20 = 255
21 = 0
22 = 255
23 = 0
24 = 255
25 = 0
26 = 255
27 = 0
28+ = 0

Association groups: Z-Stick is added as “Lifeline Controller”, everything else not set.

Item configuration

Number NUM_ZWAVE_Kitchen_Swipe_Scene "Swipe Kitchen [%d]" <movecontrol> (G_Kitchen) { channel="zwave:device:4c0da5c0:node29:scene_number" }

When swiping up I get the following logs with TRACE level:

2017-02-09 22:05:58.000 [Handler$ZWaveReceiveThread] - Received SOF
2017-02-09 22:05:58.012 [Handler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 1D 09 60 0D 00 00 5B 03 0E 00 01 DA 
2017-02-09 22:05:58.013 [SerialMessage             ] - NODE 255: Creating new SerialMessage from buffer = 01 0F 00 04 00 1D 09 60 0D 00 00 5B 03 0E 00 01 DA 
2017-02-09 22:05:58.014 [SerialMessage             ] - Calculated checksum = 0xDA
2017-02-09 22:05:58.015 [SerialMessage             ] - NODE 255: Checksum matched
2017-02-09 22:05:58.016 [SerialMessage             ] - NODE 255: Message payload = 00 1D 09 60 0D 00 00 5B 03 0E 00 01 
2017-02-09 22:05:58.017 [Handler$ZWaveReceiveThread] - Message is valid, sending ACK
2017-02-09 22:05:58.018 [Handler$ZWaveReceiveThread] - Response SENT
2017-02-09 22:05:58.019 [ZWaveController           ] - Receive queue TAKE: Length=0
2017-02-09 22:05:58.025 [SerialMessage             ] - Calculated checksum = 0xDA
2017-02-09 22:05:58.026 [SerialMessage             ] - Assembled message buffer = 01 0F 00 04 00 1D 09 60 0D 00 00 5B 03 0E 00 01 DA 
2017-02-09 22:05:58.027 [ZWaveController           ] - Process Message = 01 0F 00 04 00 1D 09 60 0D 00 00 5B 03 0E 00 01 DA 
2017-02-09 22:05:58.029 [ZWaveController           ] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 1D 09 60 0D 00 00 5B 03 0E 00 01 
2017-02-09 22:05:58.030 [ZWaveController           ] - Incoming Message type = REQUEST
2017-02-09 22:05:58.031 [icationCommandMessageClass] - Handle Message Application Command Request
2017-02-09 22:05:58.032 [icationCommandMessageClass] - NODE 29: Application Command Request (ALIVE:DONE)
2017-02-09 22:05:58.034 [ZWaveNodeInitStageAdvancer] - NODE 29: Starting initialisation from DONE
2017-02-09 22:05:58.036 [ZWaveController           ] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@11a005e already registered
2017-02-09 22:05:58.037 [icationCommandMessageClass] - NODE 29: Incoming command class MULTI_INSTANCE
2017-02-09 22:05:58.039 [icationCommandMessageClass] - NODE 29: Found Command Class MULTI_INSTANCE, passing to handleApplicationCommandRequest
2017-02-09 22:05:58.040 [eMultiInstanceCommandClass] - NODE 29: Received MULTI_INSTANCE command V0
2017-02-09 22:05:58.040 [eMultiInstanceCommandClass] - Process Multi-channel Encapsulation
2017-02-09 22:05:58.041 [eMultiInstanceCommandClass] - NODE 29: Requested Command Class = CENTRAL_SCENE (0x5b)
2017-02-09 22:05:58.042 [eMultiInstanceCommandClass] - NODE 29: Endpoint 0 not found. Cannot set command classes.
2017-02-09 22:05:58.043 [icationCommandMessageClass] - NODE 22: Transaction not completed: node address inconsistent.  lastSent=22, incoming=255

Here is the node.xml of the device:
node29.xml (17.7 KB)

If I set my Z-Stick on all association groups I get at least the on off values. (except for swipe up for some reason) But as far as I understand the device it should send a scene number as described in chapter 7 the manual.

Is maybe the “Endpoint 0 not found” error causing this problem?

45

I would try to delete the XML and restart to see if it solves the issue - it looks like it’s not read the configuration right.

46

Thanks for the quick answer. I’ve removed the thing, the node.xml, restarted and added the device again, but the error is still logged. Here is the new node.xml: node29.xml (17.1 KB)

Should I try to reset the device and add it again? And do I have to remove it from the controller first for this?

Edit: On the back of the device I found a device description: “FGCC - 001 White v3.2 EU”
Is this maybe a new version of the device that is not yet in the database?

47

Which version of the binding are you using?

I think I know what the issue is - it’s probably related to the way associations are now configured and it’s causing the device to send multi-channel encapsulated data. There was a fix for this issue recently (a few weeks ago) so I would have expected if you were using the latest binding it should be ok?

48

I’am using a slightly modified version of the 2.0.0 binding with added meter_reset channel for some devices. Tonight I will try if it works with the latest snapshot.

49

Thanks for the Tipp, the scene command is working with the latest zwave snapshot! But I had to make a small change to the device XML. I’ve added false to parameter 12 and 13 so that I can also set parameter combinations. (e.g. 0 to disable toggle mode for all gestures) Can you also add this for future versions?

50

What change did you make to the XML - can we look to do this in the database if needed?

Sorry - I’m a bit confused what you mean by this? Aren’t parameter 12 and 13 already in the file? They are in the database at least.

What does ‘false’ mean?

51

Sorry the xml I’ve attached got formatted, I’ve added this to the parameters 12 and 13:

<limitToOptions>false</limitToOptions>

With this option I was able to set the numbers of the parameters directly so I could disable toggle mode for all gestures.

52

Ah - ok - that makes more sense…

I’ve updated this in parameter 12 in the database.

1 Like
53

Thanks! I guess this option would also make sense on parameter 11. (Secure mode for every gesture) Can you add it there too?

54

Hi @chris, where can I download the latest zwave binding snapshot?

I’m having the same issue with “Endpoint 0 not found” using the stable 2.0 binding. I’m assuming the issue is still there in this version?

Do I have to update my whole OH2 install to snapshot version as I’m running the stable version now.

55

Hi @pa1

Im trying to get the circle gesture working with not much success.
I was wondering if you could share your setup for that

Matt

56

Hi guys,
I’m currently struggling to set up my Fibaro Swipe. It is my first Z-wave device and I’m using a Cyrus Z-wave Stick with OpenHAB 2. I tried to configure the Z-wave binding with default values (except for the part configuration obviously), but I can’t find the Fibaro Swipe no matter if I use the automatic search or the manual adding of things.
I powered the Swipe via USB and did the fancy activation gestures (hold for 3-4 secs, double beep, hold longer, beep-beep, beep, swipe upwards), but still no new thing turns up.

Any tips what I might be doing wrong? If I need to provide further infos, please tell me, as I’m really new to all of this. :sweat:

Thanks for your help!

57

Sorry to bother you again, but I solved it. Seems like the Fibaro Swipe has somehow been previously connected to a Z-Wave network (quality control perhaps?) and I had to restart the device (go into menu, three beeps and then confirm with swiping upwards). Afterwards it connected instantly. :+1: