FGPB-101 not recognized properly

brononius · October 19, 2016, 6:38pm

Hey,

For some reason, I’m not capable to get the Fibaror FGPB-101 in openhab2.
This is always seen as (010F:0F01:1000:3.2).

@chris, I’ve updated yesterday the xml on http://www.cd-jackson.com, and updated today my installtion (by apt-get upgrade). Not sure if this was necessary. Maybe it’s more an issue of my installation/configuration?
(I’ve also changed the descriptions today a bit on your side since some warnings were present due of long descriptions).

What else can I do to resolve this?

chris · October 21, 2016, 8:11am

I’m not sure if this is in the binding at the moment. Currently the builds seem to be broken, and as this was a new addition to the binding, I think it was added after the builds stopped (about a week ago).

chris · October 21, 2016, 10:24am

Cloudbees is now building again (they had a bug in their software) so I’ve just triggered a build - let’s see if it fixes your issue .

brononius · October 21, 2016, 4:59pm

And…

It’s recognized properly!!!

Thanks a lot!!!
One thing removed from the todo list.

Next step is figuring out how I can use this in rules (and items)…

brononius · October 22, 2016, 2:23pm

Hmmm, fail…
Any clue/example how I could use this button to activate a light (or whatever) when I push 1 time?
If possible with a rule, since today, I only use rules…

chris · October 22, 2016, 3:36pm

It should be simple.

Trigger the rule with the item (use the UPDATED trigger) and then send a command to turn on the light.

What doesn’t work?

brononius · October 22, 2016, 4:13pm

I can’t find out how how I should read the number of pushes (if so).
For the moment, I’m having in my items:

Number  Sch_Paddestoel                  "Paddestoel"                    <contact>                               { channel="zwave:device:ef2351c6:node85:scene_number" }
Contact Sch_Paddestoel_Alarm            "Paddestoel Alarm [%s]"         <alarm>         (ALL_Alarms)            { channel="zwave:device:ef2351c6:node85:alarm_general" }
Number  Sch_Paddestoel_Batterij         "Paddestoel [%s %%]"            <socket>        (ALL_bat,WO_bat)        { channel="zwave:device:ef2351c6:node85:battery-level" }

And my rule for the moment:

rule "Test Button"
when
  item Sch_Paddestoel received update
then
  logInfo("TEST","Paddestoel wijzigt")
end

When I push the button 1x, I’m getting following log entries. So I’m not 100% convinced that my setup is working properly. The button is nicely recognized as a thing in PaperUI. I’ve already excluded/included it, and it changed nicely from node84 to node85, with the proper db entry (FGPB101…).

2016-10-22 18:03:17.374 [ItemStateChangedEvent     ] - zwave_serial_zstick_ef2351c6_serial_sof changed from 1518 to 1519
2016-10-22 18:03:17.491 [ItemStateChangedEvent     ] - zwave_serial_zstick_ef2351c6_serial_sof changed from 1519 to 1520
2016-10-22 18:03:17.511 [ItemStateChangedEvent     ] - zwave_serial_zstick_ef2351c6_serial_ack changed from 560 to 561
2016-10-22 18:03:17.518 [ItemStateChangedEvent     ] - zwave_serial_zstick_ef2351c6_serial_sof changed from 1520 to 1521
2016-10-22 18:03:17.533 [ItemStateChangedEvent     ] - zwave_serial_zstick_ef2351c6_serial_sof changed from 1521 to 1522
2016-10-22 18:03:17.555 [ItemStateChangedEvent     ] - zwave_serial_zstick_ef2351c6_serial_sof changed from 1522 to 1523
2016-10-22 18:03:17.582 [ItemStateChangedEvent     ] - zwave_serial_zstick_ef2351c6_serial_ack changed from 561 to 562
2016-10-22 18:03:17.588 [ItemStateChangedEvent     ] - zwave_serial_zstick_ef2351c6_serial_sof changed from 1523 to 1524
...

chris · October 22, 2016, 4:23pm

The log entries aren’t anything to do with the device, although they indicate that the binding is receiving data from the button.

I would grab a debug log - although the fact that there’s no items being updated (other than the serial data) might mean there’s something wrong with the config somewhere…

I’m hoping to get hold of one of these next week (hopefully!) as Fibaro are kindly donating a few (various) devices for testing.

brononius · October 22, 2016, 4:46pm

I’ll try to find out how to enable the debug log.

I’ve seen some mentions about ‘karaf’, but it’s not clear to me how this all comes together. Or how I can enable this…

chris · October 22, 2016, 5:05pm

http://docs.openhab.org/administration/console.html

brononius · October 22, 2016, 5:06pm

OK, easier then I thought.

Start karaf: /usr/share/openhab2/runtime/karaf/bin/client
Start extra log (in karaf): log:set DEBUG org.openhab.binding.zwave
Check /var/log/openhab/* via another console

This is some debug logs:

2016-10-22 19:07:37.937 [ItemStateChangedEvent     ] - zwave_serial_zstick_ef2351c6_serial_sof changed from 1871 to 1872

==> logs/openhab.log <==
2016-10-22 19:07:37.951 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 55 03 80 03 64 43 
2016-10-22 19:07:37.954 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-10-22 19:07:37.954 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 55 03 80 03 64 43 
2016-10-22 19:07:37.954 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 55 03 80 03 64 43 
2016-10-22 19:07:37.954 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 55 03 80 03 64 
2016-10-22 19:07:37.954 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 85: Application Command Request (ALIVE:DONE)
2016-10-22 19:07:37.956 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 85: Starting initialisation from DONE
2016-10-22 19:07:37.956 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@5e8f64bf already registered
2016-10-22 19:07:37.956 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 85: Incoming command class BATTERY
2016-10-22 19:07:37.956 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 85: Received Battery Request
2016-10-22 19:07:37.956 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 85: Battery report value = 100
2016-10-22 19:07:37.956 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2016-10-22 19:07:37.957 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=85, callback=126, payload=55 02 84 08 
2016-10-22 19:07:37.957 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 55 03 80 03 64 
2016-10-22 19:07:37.957 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=126, expected=SendData, cancelled=false      MISMATCH

==> logs/events.log <==
2016-10-22 19:07:38.080 [ItemStateChangedEvent     ] - zwave_serial_zstick_ef2351c6_serial_sof changed from 1872 to 1873

==> logs/openhab.log <==
2016-10-22 19:07:38.094 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 55 03 80 03 64 43 
2016-10-22 19:07:38.096 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-10-22 19:07:38.096 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 55 03 80 03 64 43 
2016-10-22 19:07:38.096 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 55 03 80 03 64 43 
2016-10-22 19:07:38.096 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 55 03 80 03 64 
2016-10-22 19:07:38.096 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 85: Application Command Request (ALIVE:DONE)
2016-10-22 19:07:38.096 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 85: Starting initialisation from DONE
2016-10-22 19:07:38.096 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@5e8f64bf already registered
2016-10-22 19:07:38.096 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 85: Incoming command class BATTERY
2016-10-22 19:07:38.097 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 85: Received Battery Request
2016-10-22 19:07:38.097 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 85: Battery report value = 100
2016-10-22 19:07:38.097 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2016-10-22 19:07:38.097 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=85, callback=126, payload=55 02 84 08 
2016-10-22 19:07:38.097 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 55 03 80 03 64 
2016-10-22 19:07:38.097 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=126, expected=SendData, cancelled=false      MISMATCH

==> logs/events.log <==
2016-10-22 19:07:38.198 [ItemStateChangedEvent     ] - zwave_serial_zstick_ef2351c6_serial_sof changed from 1873 to 1874

==> logs/openhab.log <==
2016-10-22 19:07:38.209 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 04 55 02 84 07 23 
2016-10-22 19:07:38.211 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-10-22 19:07:38.211 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 04 04 55 02 84 07 23 
2016-10-22 19:07:38.211 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 08 00 04 04 55 02 84 07 23 
2016-10-22 19:07:38.212 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=04 55 02 84 07 
2016-10-22 19:07:38.212 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 85: Application Command Request (ALIVE:DONE)
2016-10-22 19:07:38.212 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 85: Starting initialisation from DONE
2016-10-22 19:07:38.212 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@5e8f64bf already registered
2016-10-22 19:07:38.212 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 85: Incoming command class WAKE_UP
2016-10-22 19:07:38.212 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 85: Received Wake Up Request
2016-10-22 19:07:38.212 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 85: Received WAKE_UP_NOTIFICATION
2016-10-22 19:07:38.212 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 85: Is awake with 0 messages in the wake-up queue.
2016-10-22 19:07:38.212 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
2016-10-22 19:07:38.212 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=85, callback=126, payload=55 02 84 08 
2016-10-22 19:07:38.213 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=04 55 02 84 07 
2016-10-22 19:07:38.213 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=126, expected=SendData, cancelled=true      MISMATCH
2016-10-22 19:07:39.213 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 85: No more messages, go back to sleep
2016-10-22 19:07:39.213 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 85: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2016-10-22 19:07:39.213 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2016-10-22 19:07:39.213 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2016-10-22 19:07:39.213 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 55 02 84 08 25 7F 64 
2016-10-22 19:07:39.213 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 85: Sending REQUEST Message = 01 09 00 13 55 02 84 08 25 7F 64 

==> logs/events.log <==
2016-10-22 19:07:39.216 [ItemStateChangedEvent     ] - zwave_serial_zstick_ef2351c6_serial_ack changed from 651 to 652
2016-10-22 19:07:39.222 [ItemStateChangedEvent     ] - zwave_serial_zstick_ef2351c6_serial_sof changed from 1874 to 1875

==> logs/openhab.log <==
2016-10-22 19:07:39.229 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
2016-10-22 19:07:39.230 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-10-22 19:07:39.230 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
2016-10-22 19:07:39.230 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
2016-10-22 19:07:39.230 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
2016-10-22 19:07:39.231 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 85: Sent Data successfully placed on stack.

==> logs/events.log <==
2016-10-22 19:07:39.238 [ItemStateChangedEvent     ] - zwave_serial_zstick_ef2351c6_serial_sof changed from 1875 to 1876

==> logs/openhab.log <==
2016-10-22 19:07:39.251 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 7F 00 00 02 96 
2016-10-22 19:07:39.254 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-10-22 19:07:39.255 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 7F 00 00 02 00 00 98 
2016-10-22 19:07:39.255 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 7F 00 00 02 00 00 98 
2016-10-22 19:07:39.255 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=7F 00 00 02 
2016-10-22 19:07:39.255 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 85: SendData Request. CallBack ID = 127, Status = Transmission complete and ACK received(0)
2016-10-22 19:07:39.255 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 85: Starting initialisation from DONE
2016-10-22 19:07:39.255 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@5e8f64bf already registered
2016-10-22 19:07:39.255 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=85, callback=127, payload=55 02 84 08 
2016-10-22 19:07:39.255 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=7F 00 00 02 
2016-10-22 19:07:39.255 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=127, expected=SendData, cancelled=false        transaction complete!
2016-10-22 19:07:39.255 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2016-10-22 19:07:39.255 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 85: Went to sleep
2016-10-22 19:07:39.255 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 85: Is sleeping
2016-10-22 19:07:39.256 [DEBUG] [curityCommandClassWithInitialization] - NODE 85: updating lastSentMessageTimestamp
2016-10-22 19:07:39.256 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 85: Response processed after 42ms/4842ms.

chris · October 22, 2016, 5:11pm

Unless I missed something, it doesn’t look like any data is being sent other than the battery state. This might indicate that something needs to be configured in the device parameters?

brononius · October 22, 2016, 5:15pm

No idea if I need to configure extra parameters. Would be a pitty for a ‘stupid’ push button.

When I push, sometimes I see a ‘scene’ passing by. But not always? Maybe there’s a kind of ‘time-out/sleep’ between pushes?

2016-10-22 19:13:05.340 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0B 00 04 00 55 05 5B 03 01 00 01 F8 
2016-10-22 19:13:05.343 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-10-22 19:13:05.343 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0B 00 04 00 55 05 5B 03 01 00 01 F8 
2016-10-22 19:13:05.343 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0B 00 04 00 55 05 5B 03 01 00 01 F8 
2016-10-22 19:13:05.343 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 55 05 5B 03 01 00 01 
2016-10-22 19:13:05.343 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 85: Application Command Request (ALIVE:DONE)
2016-10-22 19:13:05.343 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 85: Starting initialisation from DONE
2016-10-22 19:13:05.343 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@5e8f64bf already registered
2016-10-22 19:13:05.343 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 85: Incoming command class CENTRAL_SCENE
2016-10-22 19:13:05.343 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 85: Received CENTRAL_SCENE command V1
2016-10-22 19:13:05.344 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 85: Received scene 1 at time 0
2016-10-22 19:13:05.344 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2016-10-22 19:13:05.344 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=85, callback=134, payload=55 02 84 08 
2016-10-22 19:13:05.344 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 55 05 5B 03 01 00 01 
2016-10-22 19:13:05.344 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=134, expected=SendData, cancelled=false      MISMATCH

brononius · October 22, 2016, 5:17pm

And this is 1 push, 2 pushes, 3 pushes. So somewhere, there’s a difference.
Not sure where time1 and time2 went, but it’s always time0 for 1 push, time3 for 2 pushes…

tail -f openhab.log I grep “NODE 85”

2016-10-22 19:16:23.745 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 85: Application Command Request (ALIVE:DONE)
2016-10-22 19:16:23.745 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 85: Starting initialisation from DONE
2016-10-22 19:16:23.745 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 85: Incoming command class CENTRAL_SCENE
2016-10-22 19:16:23.745 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 85: Received CENTRAL_SCENE command V1
2016-10-22 19:16:23.745 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 85: Received scene 1 at time 0



2016-10-22 19:16:27.572 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 85: Application Command Request (ALIVE:DONE)
2016-10-22 19:16:27.572 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 85: Starting initialisation from DONE
2016-10-22 19:16:27.572 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 85: Incoming command class CENTRAL_SCENE
2016-10-22 19:16:27.572 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 85: Received CENTRAL_SCENE command V1
2016-10-22 19:16:27.572 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 85: Received scene 1 at time 3



2016-10-22 19:16:32.461 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 85: Application Command Request (ALIVE:DONE)
2016-10-22 19:16:32.461 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 85: Starting initialisation from DONE
2016-10-22 19:16:32.462 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 85: Incoming command class CENTRAL_SCENE
2016-10-22 19:16:32.462 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 85: Received CENTRAL_SCENE command V1
2016-10-22 19:16:32.462 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 85: Received scene 1 at time 4

chris · October 22, 2016, 5:27pm

It’s possible that this is logging incorrectly - I think this was a guess from before the ZWave docs were made public, and I think it might be incorrect.

Let me take a look at that (tomorrow) and see if it’s correct.

brononius · October 22, 2016, 5:28pm

Thanks already!!!
Let me know if I can test/do something…

Pierre_Cobbaert · October 24, 2016, 7:40pm

Hello,
I’ve the same kind of problem with The Button (FGPB-101).
I’ve tried all the possible actions (according to the specs) and I’ve extracted some part of the ZWave log (see below. I can provide more information if needed).
It is consistent with @brononius observations. So it seems that the action is identified by the 11th bytes in the message and logged as “time” information.

BUTTON PRESSED 1 TIME:
[ve.internal.protocol.ZWaveController] - Process Message = 01 0B 00 04 00 08 05 5B 03 02 00 01 A6
…
[dclass.ZWaveCentralSceneCommandClass] - NODE 8: Received CENTRAL_SCENE command V1
[dclass.ZWaveCentralSceneCommandClass] - NODE 8: Received scene 1 at time 0

BUTTON PRESSED 2 TIMES:
[ve.internal.protocol.ZWaveController] - Process Message = 01 0B 00 04 00 08 05 5B 03 03 03 01 A4
…
[dclass.ZWaveCentralSceneCommandClass] - NODE 8: Received CENTRAL_SCENE command V1
[dclass.ZWaveCentralSceneCommandClass] - NODE 8: Received scene 1 at time 3

BUTTON PRESSED 3 TIMES:
[ve.internal.protocol.ZWaveController] - Process Message = 01 0B 00 04 00 08 05 5B 03 04 04 01 A4
…
[dclass.ZWaveCentralSceneCommandClass] - NODE 8: Received CENTRAL_SCENE command V1
[dclass.ZWaveCentralSceneCommandClass] - NODE 8: Received scene 1 at time 4

BUTTON PRESSED 4 TIMES:
[ve.internal.protocol.ZWaveController] - Process Message = 01 0B 00 04 00 08 05 5B 03 05 05 01 A4
…
[dclass.ZWaveCentralSceneCommandClass] - NODE 8: Received CENTRAL_SCENE command V1
[dclass.ZWaveCentralSceneCommandClass] - NODE 8: Received scene 1 at time 5

BUTTON PRESSED 5 TIMES:
[ve.internal.protocol.ZWaveController] - Process Message = 01 0B 00 04 00 08 05 5B 03 03 06 01 A1
…
[dclass.ZWaveCentralSceneCommandClass] - NODE 8: Received CENTRAL_SCENE command V1
[dclass.ZWaveCentralSceneCommandClass] - NODE 8: Received scene 1 at time 6

BUTTON HELD DOWN (same kind of message is sent several times):
[ve.internal.protocol.ZWaveController] - Process Message = 01 0B 00 04 00 08 05 5B 03 06 02 01 A0
…
[dclass.ZWaveCentralSceneCommandClass] - NODE 8: Received CENTRAL_SCENE command V1
[dclass.ZWaveCentralSceneCommandClass] - NODE 8: Received scene 1 at time 2

BUTTON RELEASED (after button was held down for several seconds):
[ve.internal.protocol.ZWaveController] - Process Message = 01 0B 00 04 00 08 05 5B 03 09 01 01 AC
…
[dclass.ZWaveCentralSceneCommandClass] - NODE 8: Received CENTRAL_SCENE command V1
[dclass.ZWaveCentralSceneCommandClass] - NODE 8: Received scene 1 at time 1

brononius · November 1, 2016, 7:59am

Hey @chris,

Did you found the time to have a look a this button?
Or can we do anything to help you out?

chris · November 1, 2016, 9:08am

I’ll update this late today. The scene number will be a decimal value in the format “scene.key” where key is the following -:

0 - Single Press
1 - Key Released
2 - Key Held Down
3 - Single Press 2 times
4 - Single Press 3 times
5 - Single Press 4 times
6 - Single Press 5 times

brononius · November 1, 2016, 4:32pm

Thanks, I’ll have it a try tomorrow!

Does this mean that we’ll use items for each ‘push-combination’? Fe

Switch Push1_1     {channel="zwave:device:a968g96b:node1:1" }
Switch Push1_2     {channel="zwave:device:a968g96b:node1:2" }