Key Fob

[jnowland]

Can someone please tell me how to use the Securifi Key Fob. I realize it is mainly for security systems however, the description states it can be set up via a Web browser interface to use for operating other devices.  I tried setting up rules to turn lights on or off, but the lights simply blink on and off continuously. Is there another Web browser interface to set the key fob up?

[mparadis]

I don't think that is working quite yet but I don't have one myself so you'd have to wait for others to comment. http://wiki.securifi.com/index.php?title=Securifi_SZ-KFB01

[bwainscott]

Can someone please tell me how to use the Securifi Key Fob. I realize it is mainly for security systems however, the description states it can be set up via a Web browser interface to use for operating other devices.  I tried setting up rules to turn lights on or off, but the lights simply blink on and off continuously. Is there another Web browser interface to set the key fob up?

Which firmware are you on, and how is your rule set up?  I had keyfob issues, but with R70as they have gone away.  I have 3 rules set up, using the "arm all" "disarm all" and "arm perimeter" buttons (simple things like "turn off the lights and lock the door" "turn off most lights, but set living room light to 20%" -- stuff like that).  They work fine.

[jnowland]

I was not aware of a Firmware update, so I just performed the update.  The way I was attempting to create a rule was using a single button to turn a light both on and off.  I set it up by creating one rule stating "IF Key Fob Arm All" then "turn light on".  Then I created another rule where "IF Light is ON AND Key Fob Arm ALL", then "Turn Light Off". 

In premise this should work.  However, when I press the "Arm All" button, the light blinks on and off.  I believe it is getting confused with the second rule.  With only 3 usable buttons on the Key Fob, it will make it ineeficient to use if I have to use 2 of the buttons to operate just one light. 

Did I make this clear?  I know this all can be confusing :-P

[bwainscott]

The way I was attempting to create a rule was using a single button to turn a light both on and off.  I set it up by creating one rule stating "IF Key Fob Arm All" then "turn light on".  Then I created another rule where "IF Light is ON AND Key Fob Arm ALL", then "Turn Light Off". 

I don't think you are going to be able to make that work.  I think what is happening is this:  you press the ARM button, the system sees that then checks all the rules it might trigger.  Sees the first rule and turns the light on.  Then checks the next rule and, since the light is on, turns the light off.  Changing the order of the rules won't help either, I expect.  What you want is "if I press ARM, toggle the light" and there is currently no action for that.

I keep suggesting that they make a script interface, so that we can write our own actions, in which case new stuff like this would be easy -- it would vastly expand the capabilities, far beyond anything they can ever have with a GUI built set of rules.  Hopefully they will do it some day...

[Mishakim]

Part of the problem you're having is that the fob "state" persists as whatever the last button press was until the next button press. Any time the rules are evaluated, the current state is read and any rules that trigger on that state are applied. That seems to happen on any state-change (did they fix the problem of unrelated rules also getting evaluated? I haven't updated to 70as yet), so you can't really use the same button press for two rules unless additional criteria (which aren't changed by the rule itself) assure no overlap in triggering conditions.

Using one button for on and off would need the rule to be based only on the fact that the button was just pressed, which isn't the way it works currently, as the rule evaluation is triggered by the press, but rule execution is based on the state, not the press.

[bwainscott]

Part of the problem you're having is that the fob "state" persists as whatever the last button press was until the next button press. Any time the rules are evaluated, the current state is read and any rules that trigger on that state are applied. That seems to happen on any state-change (did they fix the problem of unrelated rules also getting evaluated? I haven't updated to 70as yet)

Yes, they did.  I use my fob for a few things.  In R70, if I closed my front door, the rule corresponding to the current state of my fob would run.  Similarly, if I press the fob, the rule corresponding to the current state of my front door would run.  That doesn't happen with R70as.  So now, pressing the fob acts like a single event, and that rule doesn't get triggered again until I press the fob again, which is the way it should be.  My experience with R70as has been good -- rules act reasonably.

[chad.siegmann]

I was having problems with my key fob so I unpaired/removed it from my A+. I can't seem to get it to repair. I am sure it is because I have to actually unpair the key fob as well. Does anyone know what buttons to push to do this.

To securifi, have there been updated instructions released for the securifi sensors? I only see how to pair the key fob by pressing the lock button for less than a second.

[LGNilsson]

The instructions included are mostly correct. That said, as this is a ZigBee device, it doesn't have to be unpaired, but it has to be reset for it to be able to be paired again.

To reset the key fob, press and hold the star button, while it's being pressed, press the unlock/disarm button for 10 seconds. After 10 seconds, keep holding the star button pressed, but release the unlock/disarm button and the key fob will reset.

To pair the key fob, press the star button, then quickly press the lock/arm all button for less than 1 second and the key fob should go into pairing mode.

I've updated the instructions on the Wiki as well.