Fibaro Keyfob (FGKF-601) all presses work (1x, 2x 3x press, hold, release)

Blueprints Exchange
, , ,
1

This is my first plan, I haven’t had any problems yet but if anyone encounters a problem or has an idea for improvement let me know.

Properties

A basic plan that gives you the ability to assign actions to all possible types of keystrokes. Each button (square, circle, cross, triangle, minus, plus) has assignable actions for the following presses …

with a single press
double press
triple press
hold (long press)
release (triggered after holding)

Requires

Z-Wave donage (tested with Z ‐ Stick Gen5 USB Controller from AEON Labs ZW090)
ZWaveJS integration (tested with ZWaveJS2MQTT)
Fibaro Keyfob FGKF 601

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

Only one press works in the factory setting in the Fibaro Keyfob
Enable pressing 2x and 3x must be changed parameters 21 to 26 to value 15 in the Fibaro Keyfob configuration.

1 Like
2

Cant get started with this due to the automation cant find the ZWaveJS Device in the first step?
Trying with “Keyfob”, 3967639279, b3695e9cf694233b63066a0d5808b952…?

Please advise.

event_type: zwave_js_value_notification
data:
  domain: zwave_js
  node_id: 35
  home_id: 3967639279
  endpoint: 0
  device_id: b3695e9cf694233b63066a0d5808b952
  command_class: 91
  command_class_name: Central Scene
  label: Scene 005
  property: scene
  property_name: scene
  property_key: "005"
  property_key_name: "005"
  value: KeyPressed
  value_raw: 0
origin: LOCAL
time_fired: "2023-06-03T13:37:49.261693+00:00"
context:
  id: 01H20QN06DV5CAV7D3H36YPB7K
  parent_id: null
  user_id: null

Home Assistant 2023.5.4
Supervisor 2023.04.1
Operating System 10.2
Frontend 20230503.3 - latest

3

image
image1426×1853 147 KB

Try removing your Keyfob from the Z-Wave JS network and adding it again. I use two of these devices and I don’t have a problem

4

Hi. Feb 2024 here. Got the keyfob today and imported your blueprint. Works perfect, now have 2x, 3x, etc actions.

1 Like
5

I have recently bought the FGKF-601 as well. The label of the package box states “ZW5 v3.2” in addition.

I successfully added the Keyfob to my Z-Wave. Following that, it is visible as a Z-Wave device in HA. However I suspect, that there is something fundamentally wrong, since

  • in the device list, manufacturer and model are shown as “unknown”, and the name is shown as “Node 15”,
  • trying to configure the device, no configurable parameters are shown,
  • using this blueprint, no device can be selected.

Pressing a button on the keyfob while observing the Z-Wave JS protocol (debug level), I see e.g. the following:

2024-09-07T15:01:11.374Z SERIAL « 0x010b0004000f055b0305800225                                        (13 bytes)
2024-09-07T15:01:11.375Z SERIAL » [ACK]                                                                   (0x06)
2024-09-07T15:01:11.378Z DRIVER « [Node 015] [REQ] [ApplicationCommand]
                                  └─[CentralSceneCCNotification]
                                      sequence number: 5
                                      key attribute:   KeyPressed
                                      scene number:    2
2024-09-07T15:01:11.379Z CNTRLR   [Node 015] [!] [Central Scene] scene[002]: 0
2024-09-07T15:01:11.379Z CNTRLR « [Node 015] received CentralScene notification {
                                      "nodeId": 15,
                                      "ccId": "Central Scene",
                                      "ccCommand": "0x03",
                                      "payload": "0x058002"
                                  }

Does this demonstrate, that the low level communication works as expected?

I have already excluded the keyfob from the Z-Wave controller and included it again. However this does not change anything (except that the device was first named “Node 14”, and now “Node 15”).

Other Z-Wave devices (I have a bunch of roller shutter Fibaro FGR223) are fully functional.

I am using

  • HAOS with installed version 2024.9.0
  • Z-Wave JS, as integrated in HA: driver version 12.11.2 and server version 1.36.0,
  • AEON Labs USB stick ZW090 with Firmware 1.1
  • latest version of this blueprint

What should I do to further debug the setup?

First additional question: one of the requirements is “ZWaveJS integration (tested with ZWaveJS2MQTT)”. Do I need to setup MQTT for this blueprint!? If yes, why?

Second additional question: is this a bug within Z-Wave JS?

Thanks, Urmel42

6

Fiddling around with the blueprint, it became clear, that the Blueprint selects the Fibaro Keyfob:

selector:
        device:
          integration: zwave_js
          manufacturer: Fibargroup
          model: FGKF601
          multiple: false

If no such device is detected, one cannot select the keyfob.

My conclusion: I should not “blame” the blueprint, but the z-wave integration.

7

Very strange. After fiddling around some more time, the Keyfob is now recognized, and the blueprint works as expected. I have now clue, what has happened.

No doubt: the blueprint is OK and works as expected, once the keyfob is “completely recognized”. No doubt: the root cause is either within the z-wave network itself, or within the integration.

I have a second keyfob, which is currently unconfigured. Let’s see, what I can find out with that device.

After a night and a new look I have got it now :slight_smile:

Pairing a second fresh keyfob (after the success with the first one), this keyfob was also not completely visible.

Watching the z-wave protocol log, I could see, that the keyfob though operated as expected.

I started a new interview with the keyfob several times. This brought the resolution: the second keyfob is now available for the blueprint, and all entities are available.

Long story short: the keyfob obviously needs some additional “kicks in the ass” to become operational.

Thanks for this great blueprint!