In another thread @Ben said:
SmartThings doesn’t need to convince OEMs to play by any rules, we are building a platform that allows all those connections to happen without the OEM’s involvement.
SmartThings app experience establishes a single destination for smart home enthusiasts to create and customize a connected home that matches their needs. By embracing the innovative third-party applications and products on our open Platform, we hope to offer consumers greater flexibility and make it as easy as possible for anyone to create a smart home.
So here’s my silly question. To what extent SmartThings is open? To me “open” implies that I should be able to create a device (e.g. a temperature / humidity sensor) that can connect to the SmartThings cloud without requiring a proprietary piece of hardware (an ST hub). This is how other open device cloud services operate, for example ThingSpeak, Xively, Carriots and others. Also, this device must be a “first class citizen”, i.e. be able to send/receive all events without restriction.
Based on available documentation and forum discussions this does not seem to be the case. The only way a custom device can communicate with the SmartThings cloud is via REST end-point that have far too many restrictions imposed on it.
Any thoughts or comments?