An API is pretty straightforward/normal IoT...

An API is pretty straightforward/normal IoT platform feature these days. But most of the time it’s more about a legacy machine’s capability to be externally controlled by API (i.e. being able to be switch on/off by an external command etc). I’d reckon most buildings Ohm would be going into would have relatively old HVAC infrastructure.

The bigger issue with externally ‘controlling’ devices seems to be security. There are a vast number of surveys which suggest IoT security is perceived as a key business risk; and there’s plenty of articles published on the risk of IoT hackers. The upshot being: if Ohm were to ‘control’ machines  (or say electricity supply to a building), security may present itself as a significant barrier in the B2B sales process. I’ve seen energy management solutions with remote control features; however, I’ve only seen them implemented on in-house intranet-type networks. I haven’t seen any Cloud based IoT  solution which controls machines getting massive market traction.

When it comes to B2C (and our LIFX opportunity), consumers are bigger risk takers. But even then, I’ve heard plenty of people express their concern about Cloud-based security cameras being hacked.