I would ask in some of the Mimolite threads to see if you can figure out whatâs going on there.
As far as the Aeotec contact device, it reports as an open/close binary sensor so it can definitely be used with SmartThings as a generic door sensor.
There are some community members who have customized the device type handler to reverse what is reported as âopenâ. You can see that work in the following thread (this is a clickable link)
It works well. I am using them for to read a old alarm system with relay, a yard light with a relay and a heating boiler with a relay. So I have 3 at each of two locations. Set up is under open /closed sensors is this weeks version of Smart things as a Aeotec Dor/Window Sensor (Gen 5) mostly all z wave things work but only one function. Also using 4 Fibaro Door Window sensors which have connections so it can be used a a dry contact sensor and is much smaller FGK 101 -107. I use the Mimolite for a momentary switch on a garage door and a automatic Gate but use a dry contact sensor with a garage door armored door magnetic switch to sensor the gate and on the Garage door I use the positon function on a Smart things door switch and that shows up as a garage door in the APP. Anything not a Samsung part takes some messing around and when setting thing up you do it and walk away wait a few hours and the server will figure it out. The Z wave things are funny about getting them to join. I am up to 87 Devices on 2 hubs in 2 countries
I have an iDevices outdoor 2 outlet plug that I would love to have available within Smartthings but I havenât seen any integration yet. It does have Homekit compatibility but I donât use that much.
edit: @JDRoberts correctly pointed out that Aeon doesnât recommend using the Gen5 MultiSensor as an outdoor motion sensor. Due to the way that PIR sensors work theyâre inherently poor at detecting motion in outdoor environments. If you were to use it you might see lots of false positives. If you have an outdoor area thatâs sectioned off you may find some use in it, but otherwise we canât recommend any outdoor motion sensors at this time.
Hi @Tyler, do you anticipate any updates on whether weâll have official support for the centralite keypad (or any other) in the near future? Itâs been about a year since you mentioned this was in progress (in another thread). Thanks.
Iâve seen that smartapp, thanks. I can use the keypad to arm/disarm SHM, it has a functioning device handler. But ST staff have said in the past they wonât roll out delayed arming of SHM until thereâs an officially supported keypad.
I wouldnât put too much weight on that. Regardless of broken promises in the past, this particular precedent doesnât even matter all that much, and are completely separate development teams.
If the SHM team is deferring entry/exit grace delays due to lack of hardware, thatâs just a convenient excuse. Thereâs absolutely no reason to believe if will suddenly increase in priority and resources after hardware is available.
Itâs pretty clear at this point itâs not a priority at all. But since theyâve made public statements in the past implying it could eventually happen, and since @Tyler engages with community members re: device certification from time to time, it seemed like it was worth a shot to ask. I will not be holding my breath until that response comes, however.
Yeah, I can provide an update, but itâs more like a non-update.
Weâve made no progress on integrating a security keypad. There is not any ongoing work to make this happen, and itâs not present on any current prioritization list.
Weâve also made no progress in adding entry/exit delays to Smart Home Monitor. There is no ongoing work slated to make this happen, and itâs not present on any current prioritization list.
To be clear, there is no âSmart Home Monitorâ team. We have a [pretty small] Works With SmartThings Engineering team that works across all solutions (Devices, SmartApps, partner integrations, submission review, general bug fixes, Samsung Connect, OCF, etc.). Smart Home Monitor hasnât been changed since the beginning of the year.
Iâm currently traveling, but will bring this up again with the team when I return to the office.
Thanks so much for the update, although thatâs pretty disappointing to hear. Delayed arming and disarming of SHM has been a very common feature request since SHM was released two years ago, and for good reason IMO. Itâs hard to understand why ST isnât interested in adding this functionality.
There are two community discussion threads on outdoor motion sensors which are worth looking at.
The first one is pretty short and basically just suggests putting a tube over the lens of a PIR motion sensor, any of them including the Aeon which at least does have a weatherproof case, which can reduce some of the false alarms just because you narrow the detection field. But it obviously wonât work for all use cases. Itâs most useful for use cases that involve small detection areas, like wanting the front lights to come on as you approach the front door. Not so useful if you want a security warning over a larger area.
The second is a long detailed discussion about the issues involved in using outdoor motion sensors and what some of the options are. There is some good information there, including suggestions from some of our UK members, but the short answer is to choose a device which is designed for outdoor sensing and then Wire it to something like the Aeotec Dry contact sensor (available in both the US and the UK) to have the reports sent to SmartThings. The thread discusses several different types of devices and different wiring methods, as well as the use of @Mike_Maxwell 's zone manager smartapp to combine several sensors into one zone. So different people will find different parts of thread helpful depending on the details of what you are trying to accomplish.
Still another option is to take advantage of motion sensors built into more expensive devices like the ring doorbell that @tyler mentioned or some of the outdoor cameras. These use a different technology than the simple PIR sensors and consequently have fewer false alerts outdoors. This option wonât work for everyone, but some people will find it useful. 
I really donât understand why there isnât a simple outdoors motion sensor⌠Settled on using Blink XTs for Back Door and Garage and Ring Pro for Front Door. However, these solutions are on the âcostlyâ side.
Physics. 
Cheap âmotionâ sensors are really PIR sensors, and that technology just doesnât work really well outdoors.
Thereâs a detailed discussion of this along with alternatives in the community FAQ:
But the short answer is that a reliable one cannot be made at the price point that people using DIY solutions typically want.
Your solution of using cameras with built in motion sensors is really the most cost-effective one for reliability right now.
Tyler,
Thanks for the response, although not exactly what most folks want to hear.
Since SHM is not a priority for the ST Engineering Team, why not Open Source the code so the community can take a crack at adding the entry/exit delays?
While Iâm not answering for Tyler or in any official capacity, I believe that a significant reason is that the code for SHM includes various internal (ie, unpublished) APIs or Methods not available or hidden from Community Developers.
For example, SHM:
Is a Dashboard Solution SmartApp (ie, appears oj the front-page of the SmartThings App).
Can post special notifications that have reminders and need to be âdismissedâ by the user: A function that ActionTiles Customers would love if we could access / integrate.
Can share notifications with specific monitoring Partners like Scout (previously announced âADT Canopyâ integration appears to have been abandoned or on hold).
Can automatically select âallâ Things of a particular Capability (e.g., All Smoke Detectors, All Motion SensorsâŚ).
Of course, all of the above APIs would be beneficial to Community Developers for various SmartApps (including CoRE), ⌠But SmartThings knows this already.
How well does your Blink XTâs PIR sensor work for you outdoors? Iâm running into sensitivity issues with mine (ie itâs too sensitive) and thereâs a pretty active topic in the Blink community forum on this since it seems to be a widespread problem.