Since SmartThings already has support for all of those devices, it’s hard as a SmartThings user to feel much about the announcement except it might make it easier to move to wink 2 if someone chose to do that. And I noticed they still aren’t supporting the accelerometer feature of the multi sensor.
I think pretty soon SmartThings does need to decide what they want to be as far as competing with Wink and HomeKit.
If they want to be a real security system, they need to add an entry/exit delay, an officially supported keypad, A way to arm/disarm the system locally, user management for nonadmin users, better camera support and cellular notifications.
If they want to be a plug-and-play home automation system to compete with HomeKit and wink, they need to have an official way to group lights, an easier and more intuitive rules engine, better stability, more local operation, a functioning Bluetooth radio, better camera support and an app that works with voiceover.
If they want to be a maker’s platform to compete with homeseer and Vera they need network mapping tools, better stability, more local operation, vastly improved hubaction options, the ability to add and manage secondary Z wave controllers, full exposure of Device parameters, stronger zigbee implementation including groupcasting, and better support for zwave central scene management.
If they want to be the glue for Samsung’s appliances IOT then they have a lot of work to do on both the television and the appliances side. And add a good rules engine and better stability.
Right now SmartThings is a little of all of these four but not really enough of any to be first in class in any of the categories. So it’s really impressive when you’re just reading the top level specs, but in practice, there are just these big gaps.
It’s hard to predict what their next iterations will be because it’s hard to tell which of these four markets they are aiming for.