Any chance that someone will fix the FIbaro 6 key fob button driver?

RSLaufer · December 11, 2023, 6:28pm

I recently bought a Fibaro 6 key fob button controller. A driver written in 2017 was able to use all 30 button/sequences. That broke and was never update. the generic Z-Wave Plus button controller can only provide 12 button/sequences.

It would be great to have some of those 18 other button/sequences to use.

I have written all the forum entries on this device.

Any way I can motivate someone to offer this very useful button controller driver?

I doubt that I am the only person somewhat greedy for key fob drivers.

Roy

jtp10181 · December 11, 2023, 6:37pm

Sounds pretty easy, do you have a link for the old broken one?

I have a 4-button Z-Wave remote thing I could use for some basic testing, and would just need support for all the extra buttons you have. I am using the generic system driver right now.

bertabcd1234 · December 11, 2023, 6:40pm

Doesn't sound like a Hubitat driver, then.

But yes, someone could probably figure something out if you share what you have...

RSLaufer · December 11, 2023, 6:55pm

The link is:

github.com

inpier/hubitat/blob/master/Fibaro Keyfob (30 Buttons)

                        /**
 *  Fibaro KeyFob
 *
 *  Copyright 2017 Artur Draga
 *	
 *	Special thanks to Eric "erocm123" Maycock for help with the code.
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *	  http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 * Version 1.0.2h 2018-05-14 Force SecureMessagingEncapsulation
 */
metadata {
	definition (name: "Fibaro KeyFob(HE)", namespace: "ClassicGOD", author: "Artur Draga") {

This file has been truncated. show original

Roy

jtp10181 · December 11, 2023, 7:01pm

Wow there is a LOT going on in that driver, but it looks like it uses the Central Scene for the button presses which I can work with. Everything else is just fluff. I just posted my ZEN37 driver which it should be very similar to.

What is broken on this driver exactly so I know what to look for?
Also can you post the full info from the "data" section of the device page so I can look up the specs and settings for it.

RSLaufer · December 11, 2023, 7:29pm

According to forum entries, Hubitat changed how it dealt with Z-Wave and this “broke” that driver. The button controller recommended since then has been Generic Z-WavePlus Button Controller, which only implements “press”, “release”, and “long press”.

I’m kinda new to Hubitat, so I am not sure about the data section, but I think this might be it:

deviceId: 8192
deviceType: 4097
inClusters: 0x5E,0x59,0x80,0x56,0x7A,0x73,0x98,0x22
manufacturer: 271
S2: 128
secureInClusters: 0x85,0x5B,0x70,0x5A,0x72,0x8E,0x86,0x84,0x75
zwaveSecurePairingComplete: true
zwNodeInfo: 53 9C 80 04 18 01 5E 59 80 56 7A 73 98 22 68 23 F1 00 85 5C 5B 70 5A 72 8E 86 84 75

Thanks!

RSLaufer · December 11, 2023, 7:35pm

BTW, previous forum discussions listed this source for Fibaro 6 info:

https://manuals.fibaro.com/keyfob/

jtp10181 · December 11, 2023, 8:18pm

Ok that gives me enough to work with.
With any luck I may have something to test later tonight.

Found some parameter info: Z-Wave JS Config DB Browser
Manual direct link: https://manuals.fibaro.com/content/manuals/en/FGKF-601/FGKF-601-EN-T-v1.1.pdf

RSLaufer · December 11, 2023, 9:03pm

Thanks!

It would be great to be able to increase the Fibaro’s functionality!

jtp10181 · December 12, 2023, 2:13am

Do you have a preference on how the buttons are numbered. The old driver you linked to had this:

1-6		Single Presses
7-12	Double Presses
13-18	Tripple Presses
19-24	Held Buttons
25-30	Sequences

I would actually prefer to do it like this:

1-6 = Pushed / Held / Released / DoubleTapped
7-12 - Sequences
13-18 = Triple Taps

You get separate events for the pushed, held, released and dt events, this is the way it is supposed to be. There is no need for all those extra button numbers it just makes creating rules more confusing.

In fact it is so easy to make this from my existing driver it is just about done. I just need to add all the settings for the sequences so they can be configured.

RSLaufer · December 12, 2023, 3:09am

Your way is fine!
I really appreciate your help.
I am not quite sure what the “sequences” are.
I think the original driver had a series of quadruple pressed events.

jtp10181 · December 12, 2023, 3:17am

Check the manual on the sequences, you can program a sequence of up to 6 button presses which will then activate a virtual button press. It gives you 6 extra button actions.

You could program each one to be a 4x button press of the different buttons if desired. I could make that the default setting if desired.

RSLaufer · December 12, 2023, 3:17am

Never mind about the quadruple press. I must have misread something earlier.
Thank you for your help.

jtp10181 · December 12, 2023, 3:32am

Try this out. If it gives you any problems enable the Trace logging, try whatever it was again, and post some log screenshots.

Tip Jar (Anything or nothing is OK)

UPDATE 12/12/2023 Confirmed to be working!

Online Manual, also has sequence code builders: KeyFob - FIBARO Manuals
Found some other parameter info: Z-Wave JS Config DB Browser

gist.github.com

https://gist.github.com/jtp10181/a4ba1225e4c9d9144a0a3903f990dca6

fibaro-keyfob.groovy

/*
 *  FIBARO 6-Button Keyfob
*    - Model: FGKF-601
 *
 *  For Support, Information, and Updates:
 *  https://community.hubitat.com/u/jtp10181/
 *  https://github.com/jtp10181/Hubitat
 *

Changelog:

This file has been truncated. show original

cwwilson08 · December 12, 2023, 3:48am

Wow @jtp10181 you are amazing. Ive been hoping someone would pick this up for a long time. These are pretty nifty little button devices.

Many thanks for doing this. When i have a few minutes ill grab your driver and test as well.

I wish i could like your post many times over!

RSLaufer · December 12, 2023, 4:32am

I haven’t gotten it to work, past the original press once or hold.
Double and triple clicking seem to be recognized as a single click.

The log reports:
dev:1232023-12-11 11:29:22.371 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:29:21.485 PMinfoKey Fob: button 1 released

dev:1232023-12-11 11:29:20.933 PMinfoKey Fob: button 1 held

dev:1232023-12-11 11:29:19.199 PMinfoKey Fob: button 1 released

dev:1232023-12-11 11:29:18.710 PMinfoKey Fob: button 1 held

dev:1232023-12-11 11:29:16.011 PMinfoKey Fob: button 1 released

dev:1232023-12-11 11:29:15.581 PMinfoKey Fob: button 1 held

dev:1232023-12-11 11:29:11.737 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:29:11.508 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:29:11.302 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:29:08.214 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:29:07.920 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:29:07.753 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:24:54.882 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:24:53.117 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:24:52.918 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:24:46.579 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:24:46.284 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:24:46.099 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:19:07.091 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:19:06.810 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:19:06.589 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:18:18.590 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:18:18.370 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:18:18.161 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:18:06.114 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:18:05.912 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:16:19.007 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:16:18.699 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:16:18.483 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:12:05.072 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:12:04.851 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:12:00.888 PMinfoKey Fob: button 1 released

dev:1232023-12-11 11:12:00.272 PMinfoKey Fob: button 1 held

dev:1232023-12-11 11:11:56.631 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:11:53.518 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:11:53.248 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:11:53.015 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:11:45.872 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:11:45.582 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:11:45.337 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:10:03.949 PMinfoKey Fob: button 1 released

dev:1232023-12-11 11:10:03.419 PMinfoKey Fob: button 1 held

dev:1232023-12-11 11:09:53.889 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:09:53.584 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:09:49.997 PMinfoKey Fob: button 1 released

dev:1232023-12-11 11:09:49.445 PMinfoKey Fob: button 1 held

dev:1232023-12-11 11:09:45.552 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:09:21.631 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:09:21.375 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:09:18.160 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:09:15.573 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:09:15.325 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:09:09.253 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:09:08.993 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:07:10.058 PMinfoKey Fob: button 1 held (digital)

dev:1232023-12-11 11:06:52.339 PMinfoKey Fob: button 1 doubleTapped (digital)

dev:1232023-12-11 11:05:55.357 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:05:55.127 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:05:50.763 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:05:50.445 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:05:47.547 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:05:47.331 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:05:45.697 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:05:45.406 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:05:41.010 PMinfoKey Fob: button 1 pushed

dev:1232023-12-11 11:05:06.749 PMdebugKey Fob: Update Params List

dev:1232023-12-11 11:05:06.746 PMdebugKey Fob: Set Device Info - Model: FGKF-601 | Firmware: 3.2

jtp10181 · December 12, 2023, 5:33pm

I need you to enable TRACE logging so I can see what is going on and use a screenshot please.

You will need to only do a few tests and tell me what button you pressed and how many times, for each attempt, so I can make sense out of the trace logs.

Its just a matter of figuring out how the device is sending the info over, must not be standard although it looked like I coded it similar to the old driver.

RSLaufer · December 12, 2023, 6:16pm

Okay, here is the results of pressing "1" once:
dev:1232023-12-12 01:10:22.689 PMinfoKey Fob: button 1 pushed

Here is the results of pressing "1" twice:
dev:1232023-12-12 01:12:26.519 PMinfoKey Fob: button 1 pushed
dev:1232023-12-12 01:12:26.308 PMinfoKey Fob: button 1 pushed

and here is pressing "1" three times:
dev:1232023-12-12 01:14:04.244 PMinfoKey Fob: button 1 pushed
dev:1232023-12-12 01:14:04.166 PMinfoKey Fob: button 1 pushed
dev:1232023-12-12 01:14:03.936 PMinfoKey Fob: button 1 pushed

The driver doesn't seem to recognize multiple presses and just treats it as a single press.

Here is when i press "5" three times:
dev:1232023-12-12 01:15:32.769 PMinfoKey Fob: button 5 pushed
dev:1232023-12-12 01:15:32.379 PMinfoKey Fob: button 5 pushed
dev:1232023-12-12 01:15:32.086 PMinfoKey Fob: button 5 pushed

I tried pressing faster and slower but multiple presses don't seem to be recognized.

Is this sufficient?

Thanks!

jtp10181 · December 12, 2023, 7:28pm

You did not enable Trace logging as requested (it is a setting on the device page from my driver)....
Also please use screenshots of the logs, it is much easier for me to read.

But this is more clear and it seems that the device itself is only recognizing single presses. I will have to look over all of the settings, there might be something I need to expose so that it will wait for multiple presses before sending the events.

cwwilson08 · December 12, 2023, 7:40pm

If im not mistaken the device behaves differently based on the option selected. I believe the timing is adjusted depending on if you want to use key combinations as a single event?

This device would be fairly decent as a keypad device for arming disarming requiring knowing the proper sequences to fire the events.

I dont know if any of thats helpful. I will try to test after work tonight. 12 hour shifts boo.

Also if i remember properly when the driver first got ported it was modified to spoof s2 check as it was giving trouble or some such Details are likely in the original thread.