Maybe someone can port the new updated 2019 Smartthings driver to Hubitat.
The updated driver is said to remove disconnect issues. I would love to do it, but don't have the coding capabilities... 
Just when I thought we could tap into the trove of Swann One used equipment hitting Gumtree from people frustrated with the stinking POS they had been trying to get to work reliably. Yet again, they disappoint. I've been trawling around trying to find a fob or presence sensor that might work well with HE to arm/disarm security devices. I saw a thread about using phones to do it. Have you played around with anything else successfully?
I know... Gumtree great for that.
I would recommend taking a look at the Life360 app and the HE driver and app.
Works quite well in Oz with free version and not too hard on battery
Thanks. Shall do.
I'm at work right now but I'm pretty sure the driver code I used was the latest and was ported by the great @ogiewon
If so, then what I reported is how it is. 
1 Like
I've got my houses iphones working HSM (arm/disarm) perfectly via iphone Presence + Locative + Wifi.
So much so the wall mounted keypad is now used only by visitors.
This is an interesting THREAD as I've been wanting to get a presence sensor for the cars.
I've now got one of the @iharyadi sensors which I've yet to find time to play with.
Thanks for that. We're a mixed family - wife has an iPhone and I have an Android phone. I've got some research to do.
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"
