Bugger
I got it back in May/June. I believe it was from the last batch but I’ve been consumed by work and family life so haven’t had a good stretch of time to set it up.
Just so you know... I don’t have one of these devices. I simply helped tweak the driver to get it to compile on Hubitat. I have no idea what other changes may be necessary.
I hope you are able to get it working.
Hi Dan,
I gathered that from the earlier conversations and really appreciate the assistance you’ve provided . Thx 
1 Like
LOL - I am not a Zigbee driver expert, at all. I only made a few tweaks to resolve some errors due to porting from ST to HE.
I personally love my Pico remotes!
Just reporting in, that the weirdness continues with this Fob.
A quick double press of the Panic button registers this in HE logs;
Pressing Home, Away or Night buttons do nothing.
Pressing those 3 many times does nothing.
Holding those 3 does nothing.
Like I said weird because clearly the Fob has not "dropped off" the Mesh !
What I'd like to do is have the Fob send out Panic every 60sec or so so that then I could embed the fob into a "car presence sensor".
Hey @mike.maxwell, any tips on whether this would be possible with this Zigbee device and a pointer as to where to start ??
It probably can do this, configure the battery to report every 60 seconds, when the driver receives that fire a runIn with a delay value being your default presence timeout, the method called by the runin would send your departed event....
Thx Mike.
As an analogy of my abilities......I’m certainly not at base camp on the approach to Everest but I know how to save and I’ll get the flight ticket to Nepal. 
I believe there is a HW or Driver issue here.
I have tried again and noticed that I do not get execution on 3 (Home, Away and Night. No: 1,2,3) of the buttons in the events for a delay of 10-20 seconds
Where as, I press the "Panic" No: 4 Button and the action takes place instantly. ( can notice this also via the device led, which is instant with button 4 and the rest is delayed)
Would this be down to "If, If Else, If Else Again and Else" being used for button actions in Driver??
Usually If is fixed, Else If refers to actioning on the ground the "original If" is not correct. Else is a last resort???
Otherwise. Would it be a driver or HW delay for Buttons 1,2,3??
See below logs...
Enroll seems to be picked up instantly in logs. but action is delayed.
Which leads me to think it is a hardware delay... Hopefully someone can read this better than me 
Logs below
dev:7052019-09-12 16:46:19.813 debugParse returned null
dev:7052019-09-12 16:46:19.810 debugNight button Pushed
dev:7052019-09-12 16:46:19.798 debugSmartShield(text: null, manufacturerId: 0x0000, direction: 0x00, data: [0x02, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00], number: null, isManufacturerSpecific: false, messageType: 0x00, senderShortId: 0xa81f, isClusterSpecific: true, sourceEndpoint: 0x01, profileId: 0x0104, command: 0x00, clusterId: 0x0501, destinationEndpoint: 0x01, options: 0x0040)
dev:7052019-09-12 16:45:59.838 debugenroll response: [raw 0x500 {01 23 00 00 00}, delay 200, send 0xA81F null 1]
**
dev:7052019-09-12 16:47:46.665 debugParse returned null
dev:7052019-09-12 16:47:46.662 debugHome button Pushed
dev:7052019-09-12 16:47:46.649 debugSmartShield(text: null, manufacturerId: 0x0000, direction: 0x00, data: [0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00], number: null, isManufacturerSpecific: false, messageType: 0x00, senderShortId: 0xa81f, isClusterSpecific: true, sourceEndpoint: 0x01, profileId: 0x0104, command: 0x00, clusterId: 0x0501, destinationEndpoint: 0x01, options: 0x0040)
dev:7052019-09-12 16:47:26.666 debugenroll response: [raw 0x500 {01 23 00 00 00}, delay 200, send 0xA81F null 1]
dev:7052019-09-12 16:47:26.661 debugSending enroll response
**
dev:7052019-09-12 16:49:02.863 debugParse returned null
dev:7052019-09-12 16:49:02.860 debugAway button Pushed
dev:7052019-09-12 16:49:02.844 debugSmartShield(text: null, manufacturerId: 0x0000, direction: 0x00, data: [0x03, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00], number: null, isManufacturerSpecific: false, messageType: 0x00, senderShortId: 0xa81f, isClusterSpecific: true, sourceEndpoint: 0x01, profileId: 0x0104, command: 0x00, clusterId: 0x0501, destinationEndpoint: 0x01, options: 0x0040)
dev:7052019-09-12 16:48:42.886 debugenroll response: [raw 0x500 {01 23 00 00 00}, delay 200, send 0xA81F null 1]
dev:7052019-09-12 16:48:42.882 debugSending enroll response
**
Below is the Panic button 4 which actions instantly
dev:7052019-09-12 16:49:32.831 debugenroll response: [raw 0x500 {01 23 00 00 00}, delay 200, send 0xA81F null 1]
dev:7052019-09-12 16:49:32.828 debugParse returned null
dev:7052019-09-12 16:49:32.825 debugPanic button Pushed
dev:7052019-09-12 16:49:32.822 debugSending enroll response
dev:7052019-09-12 16:49:32.805 debugSmartShield(text: null, manufacturerId: 0x0000, direction: 0x00, data: , number: null, isManufacturerSpecific: false, messageType: 0x00, senderShortId: 0xa81f, isClusterSpecific: true, sourceEndpoint: 0x01, profileId: 0x0104, command: 0x04, clusterId: 0x0501, destinationEndpoint: 0x01, options: 0x0040)
FYI: That sounds just like I reported above (approx 10 days ago).
I've been trying to get Battery displayed - unsuccessfully !
But I did find that IF I use the Iris V2 Keypad driver I get the following functions being reported/acted through the logs.
note: ALL buttons must be double pressed
Star button (panic) - will toggle "Siren ON/OFF" function
Arm Home - will log "Invalid pin entered [] for arm command [disarm]"
Arm Away - will send "Armed Away"
Arm Night - will send "Armed Night"
@mike.maxwell,
hey mike, sorry if this is a stupid question but does a driver have to explicitly request what data gets displayed in the "Current State" area of the driver page ??
Reason I ask is I'm playing around with the SwannOne Fob and I've not found a single one that will to display anything like Battery info.
using the Iris v2 driver i can get the Fob to register some button presses but NOTHING about battery. All I get is...
Current States
- alarm : off
- armingIn : 0
- codeChanged : deleted
- codeLength : 4
- lockCodes : {}
- securityKeypad : armed night
How are you travelling with the fob? Have you made any headway?
Pretty much yes, virtually every zigbee button device requires a custom driver.
Hi @njanda
I have been playing around with it also.
Best case I got was pairing with ST driver. (Hold pair button till led flashes, then press the button every 1-2secs - While in Zig pairing)
Then change driver to Iris v2 driver and back to ST a short time later. Got more options with Iris, but armed, unarmed etc did not change on key presses
I can get key presses detected, but there is a strange delay on buttons 1-3 (home, away and night buttons) of about 15-20secs from time of pressing to device led flashing and action occurring on Hub. button 4 (gear icon) is instant led and action on Hub.
I can deal with the delay, if it is hard encoded in the HW.
But... I cannot get the device to stay connected or reconnect when out of range.
It just does not reconnect after between 1 and 4 days and you need to pair again to use. feel this may be the driver, as it works on ST.
Hey Gary,
Actually I loaded @ogiewon's driver from back up in the post HERE and it stays connected and each of the 4 buttons report, when double clicked BUT I was looking for a battery query which it doesn't appear to report, so no go for my use case.
I get a bunch of ..
State Variables
- delayExpire : 1568440710663
- bin : -1
- Driver : SecurifiKeyFob
- armingMode : 02
- entryDelay : 1
- PressType : Lock
- pendingRefresh : true
- updatedLastRanAt : 1568436237204
- armPending : false
- panic : inactive
- ButtonPresses : 1
- armNightDelay : 4
- Version : 0.3
- armMode : 02
- tempOffset : 0
- Asterisk : false
- lastRefreshAt : 2019-09-14 14:43:57
- exitDelay : 0
- lcData :
For those looking for a reliable zigbee key fob with a working driver: [Release] Heiman Zigbee Key Fob Driver
The buttons fire events instantly.
don't know if you're still using this key fob, but I love the form factor, and it looks like the manual states the 20 second delay is built in, but is configurable via the swann hub
are you or @ozsmarthome still using the key fob?
Excerpt from User Manual
The Key Fob works as a remote control within your Smart Home system, offering a quick and convenient way for you to activate a particular security mode whether you are staying, leaving or arriving home. Arming your system with the Key Fob Double-press the Away or Night button to arm your Smart Home system in Away or Night mode. The LED blinks green and then red twice for Night mode and thrice for Away mode as confirmation. There is a entry/exit delay period which allows you enter, leave or walk freely around the inside of the premises, before your system is active in Away or Night mode. The default entry/exit delay period is 20 seconds. You can easily configure the Entry/Exit Delay period from the Smart Home web portal via My Settings > Smart Hub. Disarming your system with the Key Fob Double-press the Home button to disarm your Smart Home system. The LED blinks green and then red as confirmation. Tip: Have a Smart Home Siren accessory connected?
Actually I gave up on the fob. There was some weird behavior that I could never come to grips with and as it turns out I’ve not needed such a device.
1 Like
