Iris Smart Fob 3450L (2nd generation)

got it working, button 2, 3 and 4 work…button 1 does not.

I think it might be a bad fob. It lights up on all presses except button 1

I’m using these keyfobs and new Centralite buttons with a custom HA controller. Do they flash red when sending on SmartThings too? I’m wondering if the keyfob expects some sort of response. The flashing is just a cosmetic issue, but there is a 1-2 second delay before I can send another button press and that may be because the keyfob is not getting the expected reply. The button has the same issue.

1 Like

I’ve seen the same thing and unfortunately I can’t think of a good workaround (other than local processing). This is likely caused by delays either on the way to or within the ST cloud. There’s another issue of commands arriving out of sequence, but that one’s a bit more rare.

Yes, I have noticed this as well. I believe there are 3 red flashes after you press a button. It will not send another push button event until after the flashes are complete (ie, if I press one button, starts the flashing…then immediately press another button, button two press will never happen). At least that is what it’s looking like to me.

1 Like

Does anyone who has one of these want to help test presence sensing?

Count me in. I need an excuse to use this Fob and this is the perfect one :relieved:

Here you go: https://gist.github.com/mitchpond/99d0df7d3ebce733ee30

This isn’t the final code. There are some other refinements that I want to add before publishing to my Github repository. Let me know how it works for you!

Edit: I would probably reset the fob and re-add after changing the device type. Otherwise, the new reporting configuration might not get sent.

2 Likes

Thanks Mitch. I’ll be testing this starting tonight and will let you know.
Note - Now I know why you were asking about the “zigbee.configureReporting” command :slight_smile:

I have one and will also do some testing with the new code.

First thing is the code is missing the first line to start the comment section, you will need to add the line with /* which I am guessing was just missed during a copy/paste.

That said initial testing looks good, I was able to pair and it is reporting presence in the Live Logging in the IDE as shown below. I will let you know after I am able to test leaving and coming back several times to ensure that part is working correctly.

6f366daa-f546-477f-907d-c8058fb5c61b 6:10:22 PM: debug Battery level at 88
6f366daa-f546-477f-907d-c8058fb5c61b 6:10:22 PM: debug Creating presence event: [name:presence, value:present, linkText:Iris Smart Fob - Jeremy, descriptionText:Iris Smart Fob - Jeremy has arrived]
6f366daa-f546-477f-907d-c8058fb5c61b 6:10:22 PM: debug lastCheckin = 1457485822010
6f366daa-f546-477f-907d-c8058fb5c61b 6:10:21 PM: debug Sensor checked in 19.638 seconds ago

2 Likes

org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
script14574860834541324142513.groovy: 1: unexpected token: * @ line 1, column 2.

  • Iris Smart Fob
    ^

1 error

@plantucha, please see my reply above, just need to fix the comment section at the top.

silly me. /*
now it works

@mitchp

Update after first trip with presence enabled. Something does not seem quite right, the presence took way too long to be recognized for some reason. Below is a copy of the logs from when I left and came back as well as a log from my android presence (based on geofence presence). When I left it seems that the device type eventually quit checking for the presence of the sensor which may be normal but when I arrived it took a good 3 minutes before the sensor was detected as being present and an error was reported at the same time that it came back. Seems that it is not connecting back to the mesh to report its presence very quickly. Other than that it seems to be working and is reporting presence status every 20 seconds, not sure if there is a way to adjust that to maybe save battery power or if that is even a concern.

7f602e15-fe4f-44a4-9edb-72093672374f 6:59:13 PM: debug Parse returned Personal Android has arrived

6f366daa-f546-477f-907d-c8058fb5c61b 7:03:31 PM: debug Creating presence event: [name:presence, value:present, linkText:Iris Smart Fob - Jeremy, descriptionText:Iris Smart Fob - Jeremy has arrived]
6f366daa-f546-477f-907d-c8058fb5c61b 7:03:31 PM: debug lastCheckin = 1457489011296
6f366daa-f546-477f-907d-c8058fb5c61b 7:03:24 PM: debug Battery level at 88
6f366daa-f546-477f-907d-c8058fb5c61b 7:03:24 PM: debug Creating presence event: [name:presence, value:present, linkText:Iris Smart Fob - Jeremy, descriptionText:Iris Smart Fob - Jeremy has arrived]
6f366daa-f546-477f-907d-c8058fb5c61b 7:03:09 PM: debug Scheduling periodic timer
6f366daa-f546-477f-907d-c8058fb5c61b 7:03:09 PM: debug Sensor is present
6f366daa-f546-477f-907d-c8058fb5c61b 7:03:09 PM: debug lastCheckin = 1457488989841
6f366daa-f546-477f-907d-c8058fb5c61b 7:03:16 PM: error java.util.concurrent.TimeoutException: Execution time exceeded 20 app execution seconds: 866726781559 @ line 105
6f366daa-f546-477f-907d-c8058fb5c61b 7:03:03 PM: debug Creating presence event: [name:presence, value:present, linkText:Iris Smart Fob - Jeremy, descriptionText:Iris Smart Fob - Jeremy has arrived]
6f366daa-f546-477f-907d-c8058fb5c61b 7:02:49 PM: debug Scheduling periodic timer
6f366daa-f546-477f-907d-c8058fb5c61b 7:02:49 PM: debug Sensor is present
6f366daa-f546-477f-907d-c8058fb5c61b 7:02:49 PM: debug lastCheckin = 1457488969046
6f366daa-f546-477f-907d-c8058fb5c61b 6:42:00 PM: debug Sensor checked in 113.152 seconds ago
6f366daa-f546-477f-907d-c8058fb5c61b 6:41:00 PM: debug Sensor checked in 53.361 seconds ago
6f366daa-f546-477f-907d-c8058fb5c61b 6:40:07 PM: debug Sensor checked in 0.815 seconds ago
6f366daa-f546-477f-907d-c8058fb5c61b 6:40:06 PM: debug Battery level at 88
6f366daa-f546-477f-907d-c8058fb5c61b 6:40:06 PM: debug Creating presence event: [name:presence, value:present, linkText:Iris Smart Fob - Jeremy, descriptionText:Iris Smart Fob - Jeremy has arrived]
6f366daa-f546-477f-907d-c8058fb5c61b 6:40:06 PM: debug lastCheckin = 1457487606891

Ugh…copy/paste error that I thought I fixed. Must not have hit save :-/ fixed now. Thanks.

I’m using the code that ST wrote for their arrival sensor and I set the reporting interval to the same 20 sec. Not sure what kind of effect this will have on battery life at this point.

Mine worked when it came to detecting that I was gone, but it never rejoined the mesh. I reset the fob and will be trying it again tomorrow.

I just updated my device type and it is reporting presence. I did not re-pair the device instead I edited the device and saved it again.
I’ll post my findings when I leave today.
Thanks for the work on this.
Cheers,
Scott

Hi @mitchp, here is my first feedback.
I’ve tested this now for 2 days (4 instances of Departure and Arrival) and so far everything is working as expected “under normal circumstances” (I’ll explain later)
Note - I’m using some minor changes to the Device Handler. The buttons 3 and 4 mapping is inverted and I’m using 60 seconds to report Battery, and for Departure timeout I’m using 5 minutes.

The Departure (Not Present) is detected as expected and the Arrival (Present) is working better then I expected for this specific device. It always detected that the Device was Present before I would get to my Front Door (without pressing any button). The device seems to be more responsive now when getting close to home. Pressing a button before sometime would fail 1 or 2 times before it would connect to the mesh and respond to a command, so this update is already making this deve more reliable to me.

BUT, last night I ran into a snag:
I was trying to pair 2 new ZigBee devices, so the while the Hub is in discovery mode it seems that it does not send or receive commands from the devices.
While I was pairing the first new device the Key Fob DH timed out and considered the device Not Present. After around 1 minute (the Pairing was already complete) the Key Fob sent a report an was Present again.
Now, while I was pairing the second new device the Key Fob was considered Not Present (as expected if more then 5 minutes without a report) but even when the Hub was back to normal operation (Discovery was complete) the Key Fob did not report anymore. I’ve noticed this 45 minutes after the fact and just pressed one button on the Key Fob and everything went back to normal and it’s working fine again until now.
Note - I’ve checked my ST Arrival Sensor and this same behavior did not happen.

So, I’m really happy with the new Presence Sensor capability added to this device and tonight I’ll add the device to my Presence Sensors group that I use for several Routines and this will give me more experience with the behavior of the new Presence report.

That’s good to know. I had some initial problems where the fob fell off the mesh (as expected when leaving the house), but did not re-join when arriving. From what I can tell, the fob did attempt to re-join. There was a “join” event in my location event log, but not the usual listing of endpoints. So it seems as if sometimes the join does not complete. Either an issue with how ST is handling re-joins or perhaps the fob is not responding correctly. This is lower-level than a device handler can deal with. No useful logs of what is actually happening at that level either :confused: I don’t really know who at ST to tag regarding that.

If I tossed the fob back in my makeshift faraday cage to simulate leaving, then brought it back out a minute or two later, it would attempt to re-join again and maybe 9 times out of 10 would be successful (“join” event in the logs, followed by endpoint listing). Sometimes pressing a button can kickstart the joining, but sometimes it gets in what seems like a half-joined state where it needs to be isolated/taken out of range and brought back before it tries again.

I’m probably going to add the presence capability to the GitHub version, perhaps with an on/off switch in the settings to turn off the increased reporting for those that don’t want to use it for presence.

I would bet that they do some magic behind the scenes for their devices that we just don’t have access to. I would really love to get shell access to this hub like I have with Wink to see what’s actually going on.

2 Likes

Any updates? I have 2 of these fobs for 2 separate locations and am looking forward to presence :slight_smile: