5 ms·
Can't help but quote: «“the "Internet of Things" won't work until the "Local Area Network of Things" works», seen here on HN [1]. There's significantly less mo
by nine_k 8y ago
Can't help but quote: «“the "Internet of Things" won't work until the "Local Area Network of Things" works», seen here on HN [1].
There's significantly less money in it, though, and more hassle. It's not going to become popular enough until people get burned enough with vendors going out of business, or just stopping support, and making their convenient $199 gadgets obsolete.
In a sense, a large company like Nest pulling his off is a good thing: it sends the signal.
[1]: https://news.ycombinator.com/item?id=15721911#15726960 https://news.ycombinator.com/item?id=15721911#15726960
- derefr 8y agoI would say that the Local Area Network of Things has existed for decades, but the intricacies of its deployment means that so far, it’s required a network admin to set up. The most classical example of such “things” are softphones. They need their own vxlan and switch QOS policies and so forth, to function the way people expect phones to work (rather than flaking out when someone is torrenting.) Softphone deployments exist in plenty of enterprises, but have you ever heard of a SOHO deployment of softphones (where the phones are PBX extensions and can call each-other over the LAN; not where the phones are distinct phone-company DIDs sending IP packets through the gateway, out over the internet, and to the the phone company’s PBX terminus, just to talk to one-another)? Until we get SOHO router-gateways smart enough to make such a SOHO softphone deployment “installation-free”, we’ll probably never see LANoT.
- nine_k 8y agoInternet routing in general used to require some solid engineering knowledge. Still, home routers that mostly work out of the box exist, and the learning curve is approachable for people with enough special needs not covered by the default settings. It took some protocols to be designed and widely deployed, from DHCP to mDNS and STUN. But this has been done, and it mostly works. Running a RAID array was once as enterprisey as it gets. Now you can buy a RAID-ready box (something like Synology) and have a reasonable default configuration, or configure to your taste if you have a general knowledge of what you're doing. I suppose that LANoT is going to develop eventually into something easy enough to deploy, too. Re softphones: since US cable providers effectively sell softphones as a part of the cable package, they have every incentive to prevent home routers from allowing to easily set it up for free. OTOH the QoS settings are there in the routers firmwares for that same reason, and desktop / mobile softphones (aka "internet messengers") can use that if they care enough.
- pjc50 8y agoThe home phone example is a good one, because as you say the softphones are too much hassle - but in this one case, because you're connecting to the real regulated phone system, the ""cloud"" solution of using your cellphone to make a call across the house Just Works (+). All of the anti-competitive nonsense about not interoperating with different phones or deliberately obsoleting the service goes away. The hardware manufacturer and the service provider are separated, and you can choose a new service provider by swapping the SIM. The tradeoff is that the quality is kind of bad and the ongoing fees comparatively high relative to IoT. There's even the old DECT phones, if anyone's still using those. (+ except where the internet companies have tried to break this by routing you through Hangouts or some other thing that isn't the phone system)
- donatj 8y agoLIFX bulbs work without the need to connect to the internet. They have a LAN protocol that's pretty easy to use.
- humblebee 8y agoI believe Philips Hue also does this correctly. I don't own any of the Hue products, last I looked (a few years ago) they had an open API. Currently it looks like you have to sign up for a developer account, I don't know if this is purely for email marketing or if they have know restricted API access. The downside to Hue was always the bridge, which is what exposed the http API. LIFX looks nice though. The UDP Lan protocol is really neat, and the documentation is better than I remember of Philips Hue.
- strange_quark 8y agoI have a Hue setup, and you only need to signup for a developer account to use their cloud API. If you're on your local network, the bridge has a REST API exposed and you can just start issuing requests to it without any signing up for anything.
- brachi 8y agoIn my experience, when I researched some of the official forums some time ago, there was no public documentation of the protocols. I still have to use the Android app to onboard a bulb (which will fail if you forget to deactivate mobile data on your phone). Then, I was pretty satisfied using lifxlan in Python (https://github.com/mclarkk/lifxlan https://github.com/mclarkk/lifxlan)
- donatj 8y agoThere is absolutely public documentation [1] and has been for years. I've used it extensively to help maintain a Go connector [2]. It's a binary protocol and it's just a matter of spraying your network with broadcast UDP packets. 1. https://lan.developer.lifx.com/ https://lan.developer.lifx.com/ 2. https://github.com/2tvenom/golifx https://github.com/2tvenom/golifx
- Bartweiss 8y agoIt's hard to decide which nickname is better between "the Internet of Things That Don't Work" and "the Internet of Someone Else's Things". I can see a half dozen solidly practical uses for a smart home setup, mostly scheduling tasks to be done while I'm sleeping or not at home. Beyond that, I'd have a lot of fun just building silly hobby projects with cheap sensors, wifi-controlled lighting, etc. But I'm not going to touch any of it until I can get a system that's happy to run locally, and only calls out to the rest of the world when it actually needs to. At this point, I'm even going to hold out for adaptable integrations; if some service I'm talking to shuts down, I should be able to substitute another one honoring the same API. Anything less looks like a privacy, security, and ownership nightmare.
- pygy_ 8y agohttps://twitter.com/internetofshit https://twitter.com/internetofshit ? "the Internet of bricks" succintly conveys your first suggestion. "Internet of taps" for the second?