After hitting Save, you fairly quickly need to simultaneously press the - and O on the KeyFob.
You should get a white light. (if not cycle through with X until you do)
While the white light is on, press + to confirm wake-up. New settings should be transferred.
I had to try twice to get it to work.
Full manual here
Note: 1xclick, holdDown & release are defaults, assuring very quick 1x response.
Enabling 2xclick and/or 3xclick introduces a delayed 1xclick response (obviously )
Edit: I have not played around with the sequences yet …
this thing drives me crazy. The reason it took me so long to get back to you since you wrote is that I am “working” "on it.
The point is
When I saved the parameters 15 the keyfob did not send any events anymore at all.
Because I thought I had maybe pressed something wrong (even un unintential exclusion of the device), I looked at the network viewer and from then my node24 was red.
Finally I decided to exclude it from the network
I then tried (for almost) an hour to reinclude it again but when press + for inclusion, even though the device’s battery is out, the node24 reappears in openhab.
I deleted the node, it comes back.
Finally I decided to do an exclusion with the mechanism described in the manual and that at least excluded the hardware. (however, whatever I do the node24 always reappears, even if I delete the cache from openhab and restart openhab)
I resetted the device to factory defaults
I then did an inclusion again and it detects the device as a new node but it shows up as “not in the database”
and I tried and tried again… it took me ages to find out that after the device gets found unrecognized in the database, I then have to wait quite some minutes, then delete it through habmin and then start the inclusion process again in habmin. Then it finds the node25 (btw, still node24 as well). I then add Node25 and this it knows what the device is.
Then, I am not really sure what it - so after basically doing that several time, suddenly the keyfob was sending keystrokes again.
Happy as I was, I went to habmin and set the parameters to 15 and … from then on, nothing.
Since then, I am stuck with a keyfob that is not sending anything anymore, even though I did a factory reset, a new inclusion, a wake, almost everything I can think off…
… I keep you posted as soon as soon as I have device running again…
meanwhile if you have an idea how to get rid with the old nodes forever let me know…
don’t be farther away from your Z-Stick than 1-2m (ideally even closer)
enable zwave debug logging in the karaf console. Might give you a clue.
after hours of pressing keys, check that you battery is not (temporarily) flat.
Ikea Trådfri remotes have this problem. Check with a voltmeter.
After the key-pressing is mostly done, the battery recovers, but you might have a dud.
Just for info: I use OH2 snapshot from just a few days ago and the Z-Wave development binding
When deleting items in PaperUi or HABmin that does not remove it from the stick. It pops right back after a new inbox scan. This is as expected.
for a tru exclusion, the device must be properly included and working and the exclusion procedure must be done both in OH2 and on the device.
if you no longer have the device OnLine, devices must be removed using a Z-Stick vendor utility.
My 2 cent are that you might try to update new parameters when too far from the stick.
Thanks, Ole for keep posting (!) and all in the above checklist - I make sure all of it is followed.
Ok, then I should probably go to the latest zwave addon. I wanted to do this anyway because with the current version there is actually an issue when inverting rollershutter values (gives 1 instead of 0). Only downside, I need to recreate all things…
I am so stupid. I didn’t understand that I had to update the file in what you described above (and now that I am aware of it, I even see that in your writing)
The called the “deb” (which is actually not a command).
It’s been a long day and I can finally go to bed and have at least some good news:
I was able to update to 2.3.0 which actually was pretty smooth. The “serial” was part of it, even after I uninstalled the z-wave binding.
I was then able to update z-wave 2.3.0-snapshot. Interestingly enough it seemed to come along with OH 2.3 already. Anyways, I dropped/uninstalled that one and added the downloaded file, so I have control over it.
I deleted all things and readded them. Unfortunately 1 of around 20 are not communicating anymore with the controller at the moment. I will take a look at them tomorrow (worst case I may have to re-include them to the network again…)
EDIT/UPDATE: By using the node once it became visible in the network again and has now been adopted. Everything works well now.
Good news though: All of a sudden the keyfob has been detected again. and I get key-changes
Time-wise I don’t dare to apply your above config changes tonight. That needs to wait until tomorrow…
I’ll keep you posted what my experience are (and for all others who might run into similar issues).
Still this device keeps me puzzled. All of a sudden it wasn’t sending keystrokes anymore (without your proposed changes applied), so it took me hours to get it working again. Still I see a lot of logs of the device (e.g. I can updated the config or see the device being woken up) but not sending anything.
I now have filed a bug with Fibaro and have provided the configuration of the device.
To all of those who have that problem and want to at least fix it
Remove the device from the controller (in habmin and then confirm with the right keystrokes on the device)
Reset to factory defaults
Re-include the device into the network
After that it works and send keystrokes (1.0, 2.0…)
I will wait now until Fibaro comes back to me and after that, I try setting the 15s liked described at the very beginning of our thread.
OK, but since you have had trouble and probably strained the battery, I would have tried with a fresh one before pursuing the matter further with Fibaro.
In any case, telling them you have inserted a fresh battery will strengthen your case should it turn out to be a HW problem.
I wrote to support but they more or less told me to change the battery (…surprise ) but of course I did not have one by that time.
I again reset and tried to include it several times and after some tries it finally came back into the network. Now the battery says it is on 52% (even though “above” I have written 27% …) . The wake up time is on 0 and polling period is 1 day.
Even your triple-click settings could now be applied (=15), so I started implementing the following rule together with my son who is using the keyfob for his room.
Here is an excerpt of the rule that controls lights and the rollershutter (we used “if’s” because it is easier for my son to understand than “switch / case”):
Note that the triangle and the plus sign are pretty intuitive for using them with a rollershutter and using the same button for stopping, while the shutter is moving, saves an additional stop button.
Funnily enough we are not using double clicks or triple clicks at the moment but the idea will be that double clicking the rollershutter or light would send the commands to the whole group of that room at once (hence switching off all lights or closing all shutters at once).
rule "remote"
when
// Remote_Selection is the item that receives the id of the button
Item Remote_Selection received update
then
logInfo("remote","State {}", Remote_Selection.state)
if (Remote_Selection.state == 2.0) {
if (F2_KidRoom1_Light1_F2R.state ==OFF ) {
sendCommand(F2_KidRoom1_Light1_F2R,ON)
} else {
sendCommand(F2_KidRoom1_Light1_F2R,OFF)
}
}
// ... other lights on different buttons here
// Rollershutter DOWN or Stop
if (Remote_Selection.state == 3.0) {
// rollershutter on 100 or 0 means that it is currently moving
if (F2_Kidrooms1_shutter_front.state==100 || F2_Kidrooms1_shutter_front==0) {
sendCommand(F2_Kidrooms1_shutter_front,STOP)
} else {
sendCommand(F2_Kidrooms1_shutter_front,DOWN)
}
}
// Rollershutter UP or Stop
if (Remote_Selection.state == 4.0) {
if (F2_Kidrooms1_shutter_front.state==100 || F2_Kidrooms1_shutter_front==0) {
sendCommand(F2_Kidrooms1_shutter_front,STOP)
} else {
sendCommand(F2_Kidrooms1_shutter_front,UP)
}
}
end
To sum up:
Inclusion of the keyfob is a pain but once it is done it is a really cool and comparably cheap device to control many functions at once. I wished Fibaro had a similar device that could be mounted to a wall…
Hello Stefan,
i had the same problem with the KeyFob.
My Solution at the end:
Change the “Scene activation for □ button” Number 9 to 15 and pull the switch “reinitialise the device” to on, save the Thing configuration and wake up the KeyFob many time (i think more then ten times) up and then the magic happens, the KeyFob can do the 1,2 and 3 times click.
With an old Battery (40%)!
I don’t dare to apply your above config changes tonight. That needs to wait until tomorrow…