SmartThings Hub Version 2.0

Does ADT use a presence sensor / tag?

I don’t under why folks here who are having alarm problems related to presence detection, don’t consider using a PIN entry instead, in the meantime.

Shameless plug for my “proof of concept” SmartApp in Beta…



I don’t know about ADT presence. I know one guy who uses ADT Pulse but I don’t think he has it. Our presence detection is two 1st gen ST detectors that I got with our starter kit.

I have our “alarm” set to trigger instantly – there is no delay, so I suppose I would have to tinker to implement a PIN. Still, I like the idea, so I’ll see if I can make it work.

1 Like

So… I am presuming that you and most everyone else uses a PIN pad to arm/disarm their traditional alarm company systems.

The Minimote PIN App lets you do similar with ST, though we could use a nice keypad. Might write one as a tile for, but a standalone hardware would be nice.


The SmartTiles aka the Web Dashboard will have a security pin access very soon. For those that have a tablet setup to control the house.

  1. Setup the dashboard to control the house.
  2. Setup the pin.
  3. Setup New version of Smart Alarm to Arm/Disarm from Hello Home frazes.
  4. Setup an entry delay for the purpose of disabling the Alarm when Entering the House.
  5. Mount the Tablet with in walking distance of the door for the Entry delay.

This is my current road map for the House Security and Keypad is for the Wife HA approval factor.

Alternative: All of the Android devices have a Keypad Lock Screen. And you can setup the SmartTiles to load on device boot via Taske.

1 Like

I use SmartAlarm so in my case my garage door is set as an Entry zone so if I open it I’ll set the alarm off. I have an entry delay at the max of 60 seconds which I don’t think is enough time to open the door, park, get out and type in a key plus on top of that I’m not sure I could sell it to my wife. There are a lot of reasons why someone couldn’t or wouldn’t want to park then jump out of their car to type in a key to disable an alarm. Since ST’s last app update the presence detection has gotten better but most of the time not at the Geofence border. Also seems like detecting us as leaving is better than detecting us as arriving for some reason. If an option became available to use a phone to type in a key I don’t think my wife nor I would be interested in that. The presence detection is really our best option so I’ll continue to hope it gets better in ST.

1 Like


1 Like

[quote=“hscox030, post:493, topic:5146”]
I use SmartAlarm so in my case my garage door is set as an Entry zone so if I open it I’ll set the alarm off.[/quote]

Yes … it certainly is an inconvenience to have to rush to input a PIN-code – my point was that traditional / legacy (and current!) major dedicated alarm company systems (ADT, etc., etc., etc.) have been using that paradigm (PIN entry required to disable alarm after breaching an armed zone) for decades, reliably, and the user’s have found this to be “acceptable” (even if a little annoying and requires a sufficiently long delay time to permit the disarm PIN-input procedure).

You have two options here:

  • Customize the Alarm App so that you can set a longer delay.
  • Place an Aeon Aeotec Minimote in the car so that you can enter the PIN (it could be as little as 1 or 2 digits), as soon as you are in Z-Wave range (i.e., no need to exit the car and run to a PIN pad placed at some difficult location inside the home).

The Buttons As PIN SmartApp is, in fact, 2-Factor authentication: You must have the exact Z-Wave registered device (the specific Aeon Minimote), and you must know the PIN to enter (which can be short or long, depending on the level of security desired).

This makes this alternative solution extra secure (much more secure than just a Presence Tag).

You can also, and this may just me being stupid, use IFTT’s new DO app to arm and disarm your system.Aalmost as simple as a mininmote.

I use the ifttt button all the time, but as written it can’t change a mode. It can only turn switches on and off or the other options available through the regular smart things channel on IFTTT.

You can use a virtual switch, and then the custom smart app “big switch for hello home actions” and use that to change the mode. But it does require some custom code.

its been 22 days since last word on progress… Is there any word on we might actually expect to see this product?

I don’t have an official information, but reiterate that I think the “July 1st” timeline is “technically” on schedule.

I would rather heartily recommend patience though, even after release: Don’t rush to be an “early adopter” of the new platform.

If you’ve got time to be a Beta tester (or post-Beta … Gamma (?!) tester), then early adoption is a great service to the Community and hopefully you have a smooth experience with personal benefits.

But there will be a period of time after Hub V2 is in the wild that it could be less stable than Hub V1 (gasp!). Existing Hub V1 customers will have to go through a migration process to Hub V2, and it would be sad to see a lot of folks jump into this and then a rash of Community postings saying “Help! I wish I could rollback!!!”.

SmartThings is surely doing their best to avoid that undesirable scenario with the extensive and progressive behind the scenes beta / burn-in period going on right now.

In other words: Try to look at any further Hub V2 delays as a good thing, because that means they’ve caught a bug that you would otherwise had to “live with” for an indeterminate amount of time and personal environment impact. :sunny:

Most likely Q3, also. :slight_smile:

1 Like

With the risk of being called “disingenuous”, I would interpret this as being the end of August. Yes?

Or no.

“Most likely Q3” also means “…but could be later.”

No guarantees on this one either way. I don’t think they know yet.

Please don’t release it until it is stable and fully functional. I won’t be able to resist the upgrade when it is available. I don’t want to suffer after upgrading. I might start whining in the forums again! :older_man:


That is highly subjective, unfortunately.

What’s your criteria?

1 Like

CTO Hagins’ definition of “stability” works for me:

We are working round the clock to get the experience to the point where it needs to be. From a customer experience perspective, my simple goal is that SmartThings should be the last thing you suspect as being the cause of a problem, not the first. We need to be more reliable than the devices that are connected to our platform, and we want our customers to expect that day after day, month after month, year after year.


That’s an absolutely admirable goal and disagreeing with it would be like saying I disagree with the goal of world peace and balanced budgets…

That is a very literal standard, and anyone who expects Hub V2 to meet that this year will likely be disappointed. I expect wonderful improvements from Hub V2, but let’s be realistic: For the first few months, Hub V2 (and/or the rest of the SmartThings Platform) will be the first thing I suspect when there is an issue.

Shaking out bugs and scale issues in a complex system converted from a cloud to hybrid architecture requires considerable time in the wild.

Furthermore, that literal standard not only requires excellent stability, but it requires time to establish trust in this stability in order to redirect “suspicion”.

As I wrote previously, the mixed-blessing case is what I’m optimistic will be averted: ie, Priority to avoid appearance that the benefits of the new architecture could be outweighed by the glitches that are inherent in a new product. The simple solution: patience. Wait to see others’ experiences before jumping in.

1 Like

My expectation is that launch criteria for hub v2 would be that it as reliable and perform as well as the current hub for all currently functioning device types and community smartapps. Migration from old to new hub should be tested and reliable (better testing than some recent mobile app revisions). And advertised new features should work most of the time.

New features or capabilities shouldn’t be announced or marketed until they actually work most of the time (see the 2014 ST Harmony integration announcement and user experience and months of “we’re still fixing/testing” for an example of how NOT to launch new features or integrations). It seems it always comes back to good testing processes… That’s always been the weakness. So take the time needed to test properly.


Are you saying hub v2 should never be released?