News for hackers. Stuff that matters.

A comment on IoT garage door opener maker disables customer’s service after bad review. Parent comment

Re:IoT garage door opener maker disables customer’s service ... by leoedin on Wednesday April 05, 2017 @08:55AM (#14041708)
This doesn't work on corporate networks, or with ISPs who put their users behind a NAT (common for cellular modems). It also doesn't really fix the discovery problem - how does the client running on a different network know what dynamic DNS domain to look up? The easiest method is to use a hosted service to coordinate the two. Then you're back to the same problem.

I'm not aware of a robust solution for IoT device discovery that doesn't use a cloud based system of some sort. All the alternatives are fiddly or vulnerable to weird router/ISP configurations. Not ideal when you want your product to be seamless.

[ Parent | on HN ]
Re:IoT garage door opener maker disables customer’s service ... by pythonaut_16 on Wednesday April 05, 2017 @10:00AM (#14042108)
Really it sounds like a good situation for a federated service/protocol.

Let IoT developers develop against the protocol and then consumers can pick a provider to run their IoT hub.

i.e. I go to my garage app and plugin iot://firstname_lastname@iot_hub_provider.com and then that does the heavy lifting of cloud connecting the device and allowing the app to communicate with it.

[ Parent | on HN ]
Re:IoT garage door opener maker disables customer’s service ... by PaulRobinson on Wednesday April 05, 2017 @09:21AM (#14041857)
You know, IPv6 fixes a lot of this...
[ Parent | on HN ]