Fibar Group Keyfob : FGKF-601 (no node.xml)

Baltazar72 · April 3, 2017, 7:52pm

Hi

I am struggeling with this keyfob. It will not initialize, and no node.xml get generated. Also I can se a java exception in the logfile. Im using the experimenal z-wave binding (http://www.cd-jackson.com/downloads/openhab2/org.openhab.binding.zwave-2.1.0-SNAPSHOT.jar).

I do not know where to go from here. If anybody could give me any pointer I’d appreatiate it.

The keyfob is coming in as node5 in the logs, but no xml is appearing in userdata/zwave/

And if I press any keys on the keyfob … nothing happens in the openhab.log file …

Enclosing a logfile.

openhab2.log-fgkf-601.txt.xml (391.9 KB)

Thank you
Torstein

nokyyz · April 3, 2017, 8:41pm

Hi @Baltazar72,

Have you try to wake up the Keyfob close to your zwave controller ? http://manuals.fibaro.com/keyfob/#post-2615

Baltazar72 · April 3, 2017, 8:50pm

No, I did not …

But doing that solved it …
Thank you for reminding me to RTFM !!

Best Regards
Torstein

daunjo · April 11, 2017, 3:55pm

Hi,
Does your keyfob work ok now with OpenHAB, I get 2 channels: Scene number and battery, and these never change regardless wich button is pressed on the fob.

Baltazar72 · April 11, 2017, 7:46pm

Hi.

Yes it does.
Scene numbers 1.0 to 6.0 and battery. Although battery does not show in all
gui’s eg not in Android ( where I am now)
Trick I found to be good, was set inclusion time to 60 sec, and wake the
key fob up several times immediately after inclusion. Then delete it, and
rescan.
I currently use the experimental binding which supports security and
snapshot 2.1

Baltazar72 · April 11, 2017, 7:48pm

Clarification … It’s 2 channels. Scene and battery. The scene channel
changes from 1.0 to 6.0…

Br
Torstein

daunjo · April 11, 2017, 9:24pm

Thanks, I got it to work with your tip.

/Jonas

xsherlock · April 19, 2017, 7:36pm

what OH2 snapshot # do you use? I’m strugling to get it work, I can add it as a thing but it is device uknown" with no options at all."

Baltazar72 · April 20, 2017, 4:18pm

2.1.0-SNAPSHOT
Build #858
openhab> system:version
4.0.8
I use the experiemental binding … Not sure about version on that one feature:info openhab-binding-zwave
Feature openhab-binding-zwave 2.1.0.SNAPSHOT
Description:
Z-Wave Binding
Feature has no configuration
Feature has no configuration files
Feature depends on:
openhab-runtime-base 0.0.0
openhab-transport-serial 0.0.0
Feature contains followed bundles:
mvn:org.openhab.binding/org.openhab.binding.zwave/2.1.0-SNAPSHOT start-level=80
Feature has no conditionals.

-Torstein

daunjo · April 20, 2017, 6:16pm

I think that the most important part is to wake the device several times close to the controller.

/Jonas

Mohamed_Negm · May 29, 2017, 9:14pm

Have you guys manage to enable the key lock pattern?

I configure it via habmin but the fob never goes to the lock mode…

Mohamed_Negm · June 29, 2017, 7:09pm

Ok, it looks like i can’t configure any type of patterns neither for the scenes nor for locking the device.

Any help would be appreciated.

norbert_jordan · July 10, 2017, 3:26pm

hm,…i’m happy owner of the KeyFOB since today…on OH1.83 with Binding 1.11 Snapshot but the RemoteControl is not recognized by the system…only named "Fibaro Systems ID:1000 Type 1001). Also i cannot see any configuration items…so its empty.

Any Idea? I already woke up the keyfob several times…nothing…i’m rather close to the controller…about 3 meters.

chimera · July 10, 2017, 8:51pm

Upgrade to 2.1. I had the same issues with OH1.9, and logged a ticket - but rightly so, cd-jackson doesn’t want to spend time working on the zwave database for older versions of OH. I upgraded and still have issue with OH2.1, so have just updated the database with the new device id. So hoping this will be fixed for me soon.

chris · July 10, 2017, 8:55pm

If someone wants to create a PR for the database, then it’s fine to add it to OH1 of course

brononius · July 12, 2017, 3:57pm

For me, it’s working fine in OH2, out of the box…

I just can’t get the locking method to work.
What I’ve done so far:

Through HABmin, I’ve put parameter 1 to 54 (= 2 times button X)
Parameter 2 to 1546 (= 10 seconds and button X).
HABmin is now ‘waiting’
I wake up the device (button 0 and X)
The status HABmin ‘waiting’ goes away (after refresh browser)

But no luck, the locking scene isn’t working.

ps The guy that sold me this told me that he did succesfully configured on a demo device the lock function through the ‘fibaro home center’. So he thought the problem could be in the configuration way? So before we start to debug: did anybody got this lock config working?

For reference, my items, rules…
And with following item&rule:

item:

Number  Sch_Remote  "Remote 1"  <contact>  { channel="zwave:device:30038385:nod
e91:scene_number" }
Number  Sch_Remote_Bat    "Remote 1 [%s %%]"   <battery>     (ALL_bat,)     { channel="zwave:device:30038385:nod
e91:battery-level" }

rule:

rule "remote"
        when
                Item Sch_Remote received update
        then
                if (Sch_Remote.state == 1.0) {
                        logInfo("Remotes", "Remote nr 1 push")
                       sendCommand( Light1, ON )
                        Thread::sleep(2000)
                       sendCommand( Light1, OFF )
                }
                if (Sch_Remote.state == 2.0) {
                        logInfo("Remotes", "Remote nr 2 push")
                }
...

chimera · July 20, 2017, 10:18am

Locking method? You mean locking “something” based on a keypress? For example, I did mine like this:

items:

/* Key fob */
Number          keyFobKeyScene                  "Keyfob Button"                      <button>                                    { channel="zwave:device:fbcf2efa:node9:scene_number" }
Number          keyFobKeyBattery                "Keyfob Battery [%d %%]"             <battery>                                   { channel="zwave:device:fbcf2efa:node9:battery-level" }

Rules:

rule "Keyfob button press"
when
	Item keyFobKeyScene changed
then
	logInfo("keyfob", "Keyfob button press detected")
	switch (keyFobKeyScene.state) {
		case 1.0: {
            sendCommand(doWhatEverForSceneOne, ON)
			logInfo("keyfob", "Keyfob 1 pressed")
        }
		case 2.0:
			logInfo("keyfob", "Keyfob 2 pressed")
		case 3.0:
			logInfo("keyfob", "Keyfob 3 pressed")
		case 4.0:
			logInfo("keyfob", "Keyfob 4 pressed")
		case 5.0:
			logInfo("keyfob", "Keyfob 5 pressed")
		case 6.0:
			logInfo("keyfob", "Keyfob 6 pressed")
		default:
			logInfo("keyfob", "Other combination: " + keyFobKeyScene.state)
	}
end

Alter or add to the case statements to, for example, 1.2 = “key 1 pressed and held” and 1.1 = “key 1 released” etc.

brononius · July 20, 2017, 3:02pm

The keyfob can’t be configured to avoid unwanted key press.
You need to push a certain key combination before the actual key push will be forwarded to the zwave network.
For this, you need to put parameter 1 to a certain value (in my example 54).
But when I try to configure this parameter, it’s like the keyfob doesn’t pick up the value from openhab.

markus7017 · August 6, 2017, 2:41pm

Hi,

I was able to include the KeyFob and define the channels. I’m receiving battery updates, but not the button clicks (scene ids). I did several wakeups, but no change. Pressing a button is not reported to openhab even the led didn’t blink. Any idea?

using 2.1-SNAPSHOT buld 1033

Best regards, Markus

markus7017 · August 6, 2017, 3:53pm

2.1 stable shows the same behaviour: I see the wakeup in the logs, OH shows the battery state, but when pressing a key everything stays silent. It feels like the knob is in locking mode, but parameter 1,2 have been set to 0/0 (default was 0/60)