3 ms·
If you're going to sell a consumer an internet connected device, they're probably going to assume that it'll work on its own and they can review and adjust thin
by inamberclad 9y ago
If you're going to sell a consumer an internet connected device, they're probably going to assume that it'll work on its own and they can review and adjust things on a website (that isn't a 192.0.0.*)
- fgonzag 9y agoSadly, thats the IoT world I want to live in. All the devices communicate only through the internal network. This increases security a ton by default. If you want to use it outside your network, then you do it the old fashioned way, by setting up a vpn to your router.
- ianhowson 9y agoI've shipped a few products that work like this, but the support burden is incredible. Practically no users are capable of configuring IP addresses or forwarding ports on their router. Config-by-phone or config-by-cloud is definitely the way to go for consumer gear -- see Roku or Chromecast for great examples.
- smcl 9y agoHm, I wonder if it is just the IP address people don't like to use? Like if it used Bonjour/Avahi and you could (after a bit of initial config) connect to your internet connected lightbulb via http://kitchen-lightbulb.local http://kitchen-lightbulb.local would that be better?