Fibaro Keyfob detect kepress

Hans2004 · September 30, 2017, 12:17pm

If have a Fibaro FGKF-601 keyfob paired to my system.

I am trying to make make the keyfob do something from home assistant, but nothing happens. This is what I have about it in my config.yaml:

automation 6:

alias: ‘Key Pressed’
trigger:
platform: event
event_type: zwave.scene_activated
event_data:
object_id: zwave.keyfob
scene_id: 1
action:
- service: media_player.volume_set
  entity_id: media_player.squeezebox_radio
  data:
  volume_level: 0.99
- service: tts.google_say
  entity_id: media_player.squeezebox_radio
  data:
  message: ‘Keyfob Button 1 pressed’

Pressing a key shows the following in the OZV_log.txt:

2017-09-30 12:07:48.165 Info, Node008, Received Central Scene set from node 8: scene id=1 in 7680 seconds. Sending event notification.
2017-09-30 12:07:48.165 Warning, Node008, No ValueID created for Scene 1

The states panel shows the following in about the keyfob:
is_awake: false
is_failed: false
sentTS: 2017-09-30 12:04:36:292
averageRequestRTT: 0
max_baud_rate: 40000
sentFailed: 0
wake_up_interval: 0
sentCnt: 2
lastRequestRTT: 0
node_id: 8
is_ready: false
retries: 0
manufacturer_name: FIBARO System
product_name: FGKF601 Keyfob
receivedUnsolicited: 0
query_stage: CacheLoad
averageResponseRTT: 0
is_info_received: true
battery_level: 95
new_entity_id: zwave.keyfob
old_entity_id: zwave.keyfob_8
receivedCnt: 0
receivedTS: 2017-09-30 12:04:21:180
is_zwave_plus: true
capabilities: beaming,routing
friendly_name: keyfob
lastResponseRTT: 0
node_name: keyfob
receivedDups: 0

Hans2004 · October 1, 2017, 1:18pm

I made it work!

I had to add the buttons that I wanted to use to my Aeotec ZW090 Z-Stick Gen5 EU from the Node Group Associations in the home assistant z-wave node management. Next I changed Node Config Options for the devide, parameter “10: Single button associations - operating mode” to “Single press turns on, double press turns off”.
I use the square key. But for every key, you can set a value that is sent in Node Config Options,parameter “11: Value sent to square associations group”.

Then, in automation:

alias: ‘Alarm Arm key Pressed’
trigger:
platform: event
event_type: zwave.node_event
event_data:
entity_id: zwave.keyfob
basic_level: 255
action:
- service: media_player.volume_set
  entity_id: media_player.squeezebox_radio
  data:
  volume_level: 0.6
- service: tts.google_say
  entity_id: media_player.squeezebox_radio
  data:
  message: ‘Arming Alarm System’
- service: alarm_control_panel.alarm_arm_away
  data:
  entity_id: alarm_control_panel.home_alarm
alias: ‘Alarm Disarm key Pressed’
trigger:
platform: event
event_type: zwave.node_event
event_data:
entity_id: zwave.keyfob
basic_level: 0
action:
- service: media_player.volume_set
  entity_id: media_player.squeezebox_radio
  data:
  volume_level: 0.6
- service: tts.google_say
  entity_id: media_player.squeezebox_radio
  data:
  message: ‘Disarming Alarm System’
- service: alarm_control_panel.alarm_disarm
  data:
  entity_id: alarm_control_panel.home_alarm

Now works like a charm. Hopes this helps anyone else.

lurv · October 14, 2017, 4:11pm

Thank you for sharing this, I have now set up my Fibaro FGKF-601 keyfob with Aeotec ZW090 Z-Stick Gen5 EU similar to your configuration. And I am able to use your example to trigger an automation.

So far all OK. However, when I press a button that I have assigned with Node Group Associations to the Z-stick it seems to trigger the sequence mode in which the keyfob is waiting for other keypresses with a 10 second timeout (in my case lowered to 5sec with parameter 9). During this timeout, no other key press is registered in the OZW log.

Is this a default configuration that can be changed to not use the sequence function? Have you found any setting for this? It is possible that I have accidentally enabled this during my testing, but I am unable to find a way to disable this.

Also, which group are you using with Node Group Associations ? “2: Square - On/Of” or “3: Square - Multilevel”?

Hans2004 · October 15, 2017, 8:17am

So far all OK. However, when I press a button that I have assigned with Node Group Associations to the Z-stick it seems to trigger the sequence mode in which the keyfob is waiting for other keypresses with a 10 second timeout (in my case lowered to 5sec with parameter 9). During this timeout, no other key press is registered in the OZW log.

I do not see the timeout behaviour that you describe.

Also, which group are you using with Node Group Associations ? “2: Square - On/Of” or “3: Square - Multilevel”?

I have only set the On/Off associations. When I set the Multilevel, it did not work anymore in the way I wanted to (can’t remember what happened then). Further I have set “Config parameter 10: Single button associations - Operating mode” to “Single press turns on - Double press turns off”.

Hope this helps.

lurv · October 23, 2017, 7:51pm

I managed to get rid of the timeout issue, somehow.
I think the problem was that I only used Node Group Associations for the square key, leaving the rest of the buttons in some default mode. I have now removed all Associations and added the on/off for all buttons to my Aeotec Z-Stick and it works great now

charlieball · November 22, 2017, 7:26am

@Hans2004 what does your OZW log look like when you press a button? I followed your steps, but I just can’t get it to work. I don’t understand what I’m doing wrong.

After I have done the steps you specify, I just keep getting the same “Central Scene… bla bla bla and No Valueid”. The only thing different is that my keyfob blinks yellow 3 times, then 1 red, after I press a button.

charlieball · November 22, 2017, 2:59pm

Found the problem. I had hidden my Z-Wave stick from the frontend and I kept associating the keys to the keyfob itself… Stupid mistake.

I readded the keyfob several times, but didn’t read what I was actually associating the buttons with.

thundergreen · December 26, 2017, 8:23am

Tried adding my keyfob yesterday but it would shie this:

{
“query_stage”: “Probe”,
“receivedDups”: 0,
“product_name”: “”,
“is_awake”: false,
“friendly_name”: “Keyfob Thorsten”,
“location”: “Mobile”,
“sentCnt”: 1,
“lastRequestRTT”: 0,
“sentFailed”: 1,
“is_failed”: false,
“wake_up_interval”: 3600,
“capabilities”: [
“routing”,
“beaming”
],
“receivedCnt”: 0,
“max_baud_rate”: 40000,
“node_id”: 31,
“new_entity_id”: “zwave.keyfob_thorsten”,
“manufacturer_name”: “”,
“old_entity_id”: “zwave.keyfob_thorsten_31”,
“node_name”: “Keyfob Thorsten”,
“retries”: 0,
“receivedUnsolicited”: 0,
“is_ready”: false,
“lastResponseRTT”: 0,
“sentTS”: "2017-12-26 00:26:48:580 ",
“averageRequestRTT”: 0,
“is_info_received”: false,
“receivedTS”: "2017-12-26 00:18:09:962 ",
“averageResponseRTT”: 0,
“is_zwave_plus”: false
}

I think it was not reakky discovers by openzwave. I added it as secured node but its not as shown above .will re add it and will see.

thundergreen · December 26, 2017, 10:03pm

could u please precise how wou got it work. just got my keyfob… which steps are neccesarly?

thundergreen · December 26, 2017, 10:44pm

can u please exactly tell the steps… my keyfob now blinks just red when i push the button. i tried to remove but it failes… here last lines of the log

2017-12-26 23:33:50.973 Info, Node032, Received Central Scene set from node 32: scene id=3 in 7680 seconds. Sending event notification.
2017-12-26 23:33:50.973 Warning, Node032, No ValueID created for Scene 3
2017-12-26 23:33:51.313 Detail, Node032,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x20, 0x02, 0x98, 0x40, 0x09
2017-12-26 23:33:51.314 Info, Node032, Received SecurityCmd_NonceGet from node 32
2017-12-26 23:33:51.318 Info, Node032, Sending (Poll) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x20, 0x0a, 0x98, 0x80, 0xc9, 0x7f, 0xf9, 0x51, 0xcb, 0x2a, 0xfc, 0xfe, 0x05, 0x01, 0x36:
2017-12-26 23:33:51.364 Detail, Node032,   Received: 0x01, 0x1f, 0x00, 0x04, 0x00, 0x20, 0x19, 0x98, 0x81, 0x6d, 0xad, 0xcf, 0x44, 0xa8, 0x7a, 0xd4, 0x70, 0xb8, 0x92, 0x20, 0xe8, 0x85, 0x7f, 0xc9, 0x4c, 0xc4, 0xd6, 0xb4, 0x13, 0x62, 0x73, 0x62, 0xa2
2017-12-26 23:33:51.366 Detail, Node032, Decrypted Packet: 0x00, 0x5b, 0x03, 0x83, 0x80, 0x04
2017-12-26 23:33:51.367 Info, Node032, Received Central Scene set from node 32: scene id=4 in 7680 seconds. Sending event notification.
2017-12-26 23:33:51.367 Warning, Node032, No ValueID created for Scene 4
2017-12-26 23:33:51.992 Detail, Node032,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x20, 0x02, 0x98, 0x40, 0x09
2017-12-26 23:33:51.993 Info, Node032, Received SecurityCmd_NonceGet from node 32
2017-12-26 23:33:51.997 Info, Node032, Sending (Poll) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x20, 0x0a, 0x98, 0x80, 0x6d, 0x26, 0xa1, 0x90, 0xb4, 0x35, 0xbc, 0xdc, 0x05, 0x01, 0x50:
2017-12-26 23:33:52.043 Detail, Node032,   Received: 0x01, 0x1f, 0x00, 0x04, 0x00, 0x20, 0x19, 0x98, 0x81, 0xad, 0x5b, 0x5a, 0xf0, 0x46, 0x99, 0x3e, 0x70, 0xb5, 0xd7, 0x2c, 0x93, 0x69, 0x87, 0x6d, 0x4a, 0x4f, 0x59, 0xaf, 0x49, 0xf1, 0x6e, 0x43, 0x31
2017-12-26 23:33:52.045 Detail, Node032, Decrypted Packet: 0x00, 0x5b, 0x03, 0x84, 0x80, 0x01
2017-12-26 23:33:52.046 Info, Node032, Received Central Scene set from node 32: scene id=1 in 7680 seconds. Sending event notification.
2017-12-26 23:33:52.046 Warning, Node032, No ValueID created for Scene 1
2017-12-26 23:38:00.700 Detail, Node032,   Received: 0x01, 0x08, 0x00, 0x04, 0x10, 0x20, 0x02, 0x98, 0x40, 0x19
2017-12-26 23:38:00.701 Info, Node032, Received SecurityCmd_NonceGet from node 32
2017-12-26 23:38:00.706 Info, Node032, Sending (Command) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x20, 0x0a, 0x98, 0x80, 0x5f, 0x74, 0xbe, 0xab, 0xbc, 0x26, 0x3c, 0xc0, 0x05, 0x01, 0x93:
2017-12-26 23:38:00.842 Detail, Node032,   Received: 0x01, 0x08, 0x00, 0x04, 0x10, 0x20, 0x02, 0x98, 0x40, 0x19
2017-12-26 23:38:00.844 Info, Node032, Received SecurityCmd_NonceGet from node 32
2017-12-26 23:38:00.848 Info, Node032, Sending (Command) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x20, 0x0a, 0x98, 0x80, 0xab, 0x84, 0x90, 0x53, 0x9d, 0x91, 0xe4, 0x66, 0x05, 0x01, 0xa9:
2017-12-26 23:38:00.853 Detail, Node032,   Received: 0x01, 0x08, 0x00, 0x04, 0x10, 0x20, 0x02, 0x98, 0x40, 0x19
2017-12-26 23:38:00.854 Info, Node032, Received SecurityCmd_NonceGet from node 32
2017-12-26 23:38:00.861 Info, Node032, Sending (Command) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x20, 0x0a, 0x98, 0x80, 0x11, 0xde, 0xb8, 0xdb, 0x08, 0xb4, 0xda, 0x75, 0x05, 0x01, 0x74:
2017-12-26 23:38:00.941 Detail, Node032,   Received: 0x01, 0x08, 0x00, 0x04, 0x10, 0x20, 0x02, 0x98, 0x40, 0x19
2017-12-26 23:38:00.942 Info, Node032, Received SecurityCmd_NonceGet from node 32
2017-12-26 23:38:00.948 Info, Node032, Sending (Command) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x20, 0x0a, 0x98, 0x80, 0xdb, 0x7b, 0x05, 0x8f, 0xb1, 0xc2, 0x6c, 0x10, 0x05, 0x01, 0xee:
2017-12-26 23:38:00.988 Detail, Node032,   Received: 0x01, 0x08, 0x00, 0x04, 0x10, 0x20, 0x02, 0x98, 0x40, 0x19
2017-12-26 23:38:00.989 Info, Node032, Received SecurityCmd_NonceGet from node 32
2017-12-26 23:38:00.994 Info, Node032, Sending (Command) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x20, 0x0a, 0x98, 0x80, 0x37, 0x2b, 0xbb, 0xf3, 0x52, 0xf8, 0xb3, 0xfd, 0x05, 0x01, 0x7b:
2017-12-26 23:38:01.075 Detail, Node032,   Received: 0x01, 0x08, 0x00, 0x04, 0x10, 0x20, 0x02, 0x98, 0x40, 0x19
2017-12-26 23:38:01.077 Info, Node032, Received SecurityCmd_NonceGet from node 32
2017-12-26 23:38:01.081 Info, Node032, Sending (Command) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x20, 0x0a, 0x98, 0x80, 0x7d, 0x43, 0x51, 0x19, 0xd5, 0x35, 0x80, 0xe5, 0x05, 0x01, 0x38:
2017-12-26 23:38:01.134 Detail, Node032,   Received: 0x01, 0x08, 0x00, 0x04, 0x10, 0x20, 0x02, 0x98, 0x40, 0x19
2017-12-26 23:38:01.135 Info, Node032, Received SecurityCmd_NonceGet from node 32
2017-12-26 23:38:01.140 Info, Node032, Sending (Command) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x20, 0x0a, 0x98, 0x80, 0x15, 0x38, 0xc0, 0x1c, 0xed, 0x9b, 0x91, 0xc8, 0x05, 0x01, 0x15:
2017-12-26 23:38:01.179 Detail, Node032,   Received: 0x01, 0x08, 0x00, 0x04, 0x10, 0x20, 0x02, 0x98, 0x40, 0x19
2017-12-26 23:38:01.180 Info, Node032, Received SecurityCmd_NonceGet from node 32
2017-12-26 23:38:01.186 Info, Node032, Sending (Command) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x20, 0x0a, 0x98, 0x80, 0x17, 0x97, 0x58, 0xc7, 0x59, 0xc5, 0xd7, 0x90, 0x05, 0x01, 0x0f:
2017-12-26 23:38:03.254 Detail, Node032,   Received: 0x01, 0x1c, 0x00, 0x04, 0x10, 0x20, 0x16, 0x98, 0x81, 0xcf, 0xa8, 0xde, 0x46, 0x74, 0xbc, 0x3e, 0x11, 0x37, 0x31, 0xc4, 0x5f, 0x64, 0x41, 0x4a, 0xaf, 0xce, 0xef, 0x27, 0x25, 0xbe
2017-12-26 23:38:03.256 Detail, Node032, Decrypted Packet: 0x00, 0x5a, 0x01
2017-12-26 23:38:03.258 Info, Node032, Received Device Reset Locally from node 32
2017-12-26 23:38:03.259 Info, Node032, NoOperation::Set - Routing=true
2017-12-26 23:38:03.261 Detail, Node032, Queuing (Controller) Remove Device
2017-12-26 23:38:03.262 Detail, Node032, Queuing (Controller) Has Node Failed
2017-12-26 23:38:03.271 Warning, Node032, Received reply to FUNC_ID_ZW_IS_FAILED_NODE_ID - node 32 has not failed
2017-12-26 23:38:03.272 Error, Node032, WARNING: node revived
2017-12-26 23:38:03.272 Detail, Node032, AdvanceQueries queryPending=1 queryRetries=0 queryStage=CacheLoad live=1

2017-12-26 23:38:03.382 Info, Node032, Received Device Reset Locally from node 32
2017-12-26 23:38:03.383 Info, Node032, NoOperation::Set - Routing=true
2017-12-26 23:38:03.384 Detail, Node032, Queuing (WakeUp) NoOperation_Set (Node=32): 0x01, 0x09, 0x00, 0x13, 0x20, 0x02, 0x00, 0x00, 0x25, 0x52, 0xb0
2017-12-26 23:38:03.385 Detail, Node032, Queuing (Controller) Has Node Failed
2017-12-26 23:38:03.445 Detail, Node032,   Received: 0x01, 0x1c, 0x00, 0x04, 0x10, 0x20, 0x16, 0x98, 0x81, 0xcf, 0xa8, 0xde, 0x46, 0x74, 0xbc, 0x3e, 0x11, 0x37, 0x31, 0xc4, 0x5f, 0x64, 0x41, 0x4a, 0xaf, 0xce, 0xef, 0x27, 0x25, 0xbe
2017-12-26 23:38:03.447 Detail, Node032, Decrypted Packet: 0x00, 0x5a, 0x01
2017-12-26 23:38:03.448 Info, Node032, Received Device Reset Locally from node 32
2017-12-26 23:38:03.449 Info, Node032, NoOperation::Set - Routing=true
2017-12-26 23:38:03.451 Detail, Node032, Queuing (WakeUp) NoOperation_Set (Node=32): 0x01, 0x09, 0x00, 0x13, 0x20, 0x02, 0x00, 0x00, 0x25, 0x53, 0xb1
2017-12-26 23:38:03.452 Detail, Node032, Queuing (Controller) Has Node Failed
2017-12-26 23:38:03.481 Detail, Node032,   Received: 0x01, 0x1c, 0x00, 0x04, 0x10, 0x20, 0x16, 0x98, 0x81, 0xcf, 0xa8, 0xde, 0x46, 0x74, 0xbc, 0x3e, 0x11, 0x37, 0x31, 0xc4, 0x5f, 0x64, 0x41, 0x4a, 0xaf, 0xce, 0xef, 0x27, 0x25, 0xbe
2017-12-26 23:38:03.483 Detail, Node032, Decrypted Packet: 0x00, 0x5a, 0x01
2017-12-26 23:38:03.485 Info, Node032, Received Device Reset Locally from node 32
2017-12-26 23:38:03.485 Info, Node032, NoOperation::Set - Routing=true
2017-12-26 23:38:03.487 Detail, Node032, Queuing (WakeUp) NoOperation_Set (Node=32): 0x01, 0x09, 0x00, 0x13, 0x20, 0x02, 0x00, 0x00, 0x25, 0x54, 0xb6
2017-12-26 23:38:03.488 Detail, Node032, Queuing (Controller) Has Node Failed
2017-12-26 23:38:03.678 Detail, Node032,   Received: 0x01, 0x1c, 0x00, 0x04, 0x10, 0x20, 0x16, 0x98, 0x81, 0xcf, 0xa8, 0xde, 0x46, 0x74, 0xbc, 0x3e, 0x11, 0x37, 0x31, 0xc4, 0x5f, 0x64, 0x41, 0x4a, 0xaf, 0xce, 0xef, 0x27, 0x25, 0xbe
2017-12-26 23:38:03.680 Detail, Node032, Decrypted Packet: 0x00, 0x5a, 0x01
2017-12-26 23:38:03.682 Info, Node032, Received Device Reset Locally from node 32
2017-12-26 23:38:03.682 Info, Node032, NoOperation::Set - Routing=true
2017-12-26 23:38:03.683 Detail, Node032, Queuing (WakeUp) NoOperation_Set (Node=32): 0x01, 0x09, 0x00, 0x13, 0x20, 0x02, 0x00, 0x00, 0x25, 0x55, 0xb7
2017-12-26 23:38:03.684 Detail, Node032, Queuing (Controller) Has Node Failed
2017-12-26 23:38:03.692 Detail, Node032,   Received: 0x01, 0x1c, 0x00, 0x04, 0x10, 0x20, 0x16, 0x98, 0x81, 0xcf, 0xa8, 0xde, 0x46, 0x74, 0xbc, 0x3e, 0x11, 0x37, 0x31, 0xc4, 0x5f, 0x64, 0x41, 0x4a, 0xaf, 0xce, 0xef, 0x27, 0x25, 0xbe
2017-12-26 23:38:03.694 Detail, Node032, Decrypted Packet: 0x00, 0x5a, 0x01
2017-12-26 23:38:03.695 Info, Node032, Received Device Reset Locally from node 32
2017-12-26 23:38:03.696 Info, Node032, NoOperation::Set - Routing=true
2017-12-26 23:38:03.697 Detail, Node032, Queuing (WakeUp) NoOperation_Set (Node=32): 0x01, 0x09, 0x00, 0x13, 0x20, 0x02, 0x00, 0x00, 0x25, 0x56, 0xb4
2017-12-26 23:38:03.698 Detail, Node032, Queuing (Controller) Has Node Failed
2017-12-26 23:38:03.960 Detail, Node032,   Received: 0x01, 0x1c, 0x00, 0x04, 0x10, 0x20, 0x16, 0x98, 0x81, 0xcf, 0xa8, 0xde, 0x46, 0x74, 0xbc, 0x3e, 0x11, 0x37, 0x31, 0xc4, 0x5f, 0x64, 0x41, 0x4a, 0xaf, 0xce, 0xef, 0x27, 0x25, 0xbe
2017-12-26 23:38:03.962 Detail, Node032, Decrypted Packet: 0x00, 0x5a, 0x01
2017-12-26 23:38:03.963 Info, Node032, Received Device Reset Locally from node 32
2017-12-26 23:38:03.964 Info, Node032, NoOperation::Set - Routing=true
2017-12-26 23:38:03.965 Detail, Node032, Queuing (WakeUp) NoOperation_Set (Node=32): 0x01, 0x09, 0x00, 0x13, 0x20, 0x02, 0x00, 0x00, 0x25, 0x57, 0xb5
2017-12-26 23:38:03.966 Detail, Node032, Queuing (Controller) Has Node Failed
2017-12-26 23:38:04.055 Warning, Node032, Received reply to FUNC_ID_ZW_IS_FAILED_NODE_ID - node 32 has not failed
2017-12-26 23:38:04.055 Error, Node032, WARNING: node revived
2017-12-26 23:38:04.056 Detail, Node032, AdvanceQueries queryPending=1 queryRetries=0 queryStage=CacheLoad live=1
2017-12-26 23:38:04.060 Detail, Node032, Notification: Notification - Node Alive
2017-12-26 23:38:04.070 Warning, Node032, Received reply to FUNC_ID_ZW_IS_FAILED_NODE_ID - node 32 has not failed
2017-12-26 23:38:04.070 Error, Node032, WARNING: node revived
2017-12-26 23:38:04.071 Detail, Node032, AdvanceQueries queryPending=1 queryRetries=0 queryStage=CacheLoad live=1
2017-12-26 23:38:04.074 Detail, Node032, Notification: Notification - Node Alive
2017-12-26 23:38:04.085 Warning, Node032, Received reply to FUNC_ID_ZW_IS_FAILED_NODE_ID - node 32 has not failed
2017-12-26 23:38:04.086 Error, Node032, WARNING: node revived
2017-12-26 23:38:04.088 Detail, Node032, AdvanceQueries queryPending=1 queryRetries=0 queryStage=CacheLoad live=1
2017-12-26 23:38:04.089 Detail, Node032, Notification: Notification - Node Alive
2017-12-26 23:38:04.102 Warning, Node032, Received reply to FUNC_ID_ZW_IS_FAILED_NODE_ID - node 32 has not failed
2017-12-26 23:38:04.102 Error, Node032, WARNING: node revived
2017-12-26 23:38:04.104 Detail, Node032, AdvanceQueries queryPending=1 queryRetries=0 queryStage=CacheLoad live=1
2017-12-26 23:38:04.106 Detail, Node032, Notification: Notification - Node Alive
2017-12-26 23:38:04.115 Warning, Node032, Received reply to FUNC_ID_ZW_IS_FAILED_NODE_ID - node 32 has not failed
2017-12-26 23:38:04.115 Error, Node032, WARNING: node revived
2017-12-26 23:38:04.115 Detail, Node032, AdvanceQueries queryPending=1 queryRetries=0 queryStage=CacheLoad live=1
2017-12-26 23:38:04.118 Detail, Node032, Notification: Notification - Node Alive
2017-12-26 23:38:04.127 Warning, Node032, Received reply to FUNC_ID_ZW_IS_FAILED_NODE_ID - node 32 has not failed
2017-12-26 23:38:04.127 Error, Node032, WARNING: node revived
2017-12-26 23:38:04.129 Detail, Node032, AdvanceQueries queryPending=1 queryRetries=0 queryStage=CacheLoad live=1
2017-12-26 23:38:04.132 Detail, Node032, Notification: Notification - Node Alive

marioh · December 22, 2018, 11:01am

Hi, I just got a KeyFob myself and found this thread. Since my solution is a bit different, I though I share it with you.

First of all, I noticed that changes in the Z-Wave options only take effect after waking up the up. For this, “O” and “+” have to be pushed (at the same time) on the KeyFob.

My goal was not to use the “10: Single button associations - operating mode” option, but the “scene activation” which are also the default config. As written above, this results in the error message “Warning, Node0XX, No ValueID created for Scene 1”.

The solution can be found here: https://www.home-assistant.io/docs/z-wave/device-specific/#fibaro-keyfob-fgkf-601

This means, save Z-Wave config. Shut down Z-Wave network, change XML as described in the link, (i.e., replace the ’ CommandClass id=“91” name=“COMMAND_CLASS_CENTRAL_SCENE” ’ tag for the KeyFob node) and restart the network.

Now I used app daemon for automations:

class KeyFob(hass.Hass):
    def initialize(self):
        self.listen_event(self.hallo, "zwave.scene_activated")
            
    def hallo(self, event_name, data, kwargs):
        self.log("/// [EVENT] event_name: {}, data: {}".format(event_name, data))

But I guess this also works with regular automations. Note that the code is just an initial test, I guess one should also set the entity_id in listen_event.

Now I can trigger trigger different actions for short and long keypress. In the Z-Wave options, this can also be changed to other patterns, e.g., double klicks and even sequences (see manual: https://manuals.fibaro.com/content/manuals/en/FGKF-601/FGKF-601-EN-T-v1.1.pdf)

Hope this helps someone.