Try adding the fingerprint section, so it will pick it up when it pairs, then reset and re-pair. I believe the security part has to be done during the commissioning process.
Success! Result just had to be initialized. Now we have results when the buttons are pressed. I have to run out, but I’ll take a stab later at parsing what is sent when a key is pressed (looks like only 3 of the 4 buttons actually work - the 4th may just be for reset/program)
"Right now it looks like only 3 buttons on the remote function. According to Securifi the keyfob will have its own UI in the future- hopefully making the other options available as well.
So, the three buttons work great with the almond+ rules at the moment. However it would be nice if it had a little more functionality. I’ll review again when/if Securifi updates the firmware to support additional buttons/key combinations."
I am happy to report I have it working. I want to thank everyone for their help, especially @Sticks18 and @JohnR. I would not have been able to figure this out on my own.
I used @thegibertchan’s device code for the zigbee three button wireless switch to help finalize the device code. I welcome any suggestions for improvement.
One Note, the buttons are numbered in the order they are numbered from the device
1st - Unlock
2nd - Home
3rd - Lock
Thank you @kevintierney and everyone that helped. I just ordered one for my wife. She will be able to disable the Smart Alarm with out the Hated phone app(Not Wife approved!)
Are the dimensions really 2" x 1.5" ? With four buttons? That’s tiny! My car fob is bigger than that.
The Aeon zwave fob is almost twice that size.
One more thought about the Securifi fob: the product description says Internet connection is not required for it to work. Technically true, but not true when used with SmartThings, because the ST hub processes commands in the cloud.
The buttons are pretty small. If you want something to keep on your nightstand or coffee table, I’d probably spend the extra 10$ and buy the aeon minimote. This works well to keep on your keys or in your car (if it’s in a garage) to trigger things. I’m going to give my pet sitter one as well so she can turn the lights on and off easily.
I’ve given up on Ubi, the presence sensors aren’t great, especially living in and apartment, so this is an easy way to call the home/away HH actions without having to pull out your phone
That’s exactly the point. I will sell my SmartSense Presence Sensor, and will give this
to my wife as she Hates using her phone as HA control. Wife Acceptance A++!
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
#35
If someone would like to test this with my beta “Buttons As PIN” SmartApp, I would super appreciate it.
I may have to make some code modifications; but one step that would help is if you please define an ad hoc Attribute: numButtons string and set the value to “3” in the Device Handler.
Why bother?
Well… By using my SmartApp (and I’m still open to new features…), a single button press will not activate the function (such as changing mode to disarmed). Instead, a short or long sequence of presses is required. The result?: 2-Factor Authentication (something you have, the fob, and something you know; the PIN / button sequence).
It could probably done with a smart app and a virtual presence sensor. The app would monitor for a button press and toggle the virtual presence
1 Like
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
#39
Or just add Capability Presence Sensor to the Device Type for the fob, and an appropriate Attribute and some code around a particular button events to fire off the Presence Event.
Challenge… When do you reset to “not present”? Use another Button? Toggle is dangerous… Too easy to accidentally hit.
How do you get these to join your network? I followed the instructions hit * and the arm all, but i’m not getting anything? any ideas or tricks to this?