We are building some related home control products and have forgone radio level integrations instead favoring integrating with anyone over http, providing an op

We are building some related home control products and have forgone radio level integrations instead favoring integrating with anyone over http, providing an open api, and shortly after launch an sdk. Radio integrations in theory are fine but in practice it's a matter of picking sides, allowing third party devices to dictate your access to the Internet and interop, for a few features, offline (local http should be an option with any hub, nest etc but isnt) and lower latency operation as probably the biggest features. Not controlling your own products' access to the Internet is a scary proposition not to mention range/interference issues with 2.4ghz if you don't have aa critical mass. Building IoTs right now is as much an alignment excercise as a technical one and while it's a bummer that they have chosen to remove/prevent compatibility, consumers aren't really choosing subscription models for devices and cloud backed services hence the economics of customer acquisition, support, margins etc aren't realities that can be wished away.