4 ms·

Those IoT devices are getting more and more computing power. They can run the server software (like Web UI) on the device itself. For example, they can serve st

Those IoT devices are getting more and more computing power. They can run the server software (like Web UI) on the device itself. For example, they can serve static SPA that would connect back to the device via Websocket. So you don't need a sophisticated web server and can do most computations in a browser.

jjeaff 9y ago
But then it can either only be accessed within the same subnet, or you are going to have to do some port forwarding. Which is too much to ask for 99% of users.
zdragnar 9y ago
It's not terribly useful for each fish tank thermometer (or whatever) to run its own server and webui, since what you're probably interested in is "are all of my things behaving as expected". Having that data be centralized- on site or off- is where a web UI can be most useful. A friend of mine rolled his own version of this for his house, helping him optimize how the furnace / ac units operate, etc. It would've been way more painful to go to each devices UI individually.
- Spooky23 9y ago
  Why not? That server could have an api for a management device to discover and manage it as well.
  - jsjohnst 9y ago
    Especially if it’s a SPA, the same API (with minimal changes) that drives the web UI could be available to others on the network.
  - zdragnar 9y ago
    That does make sense, http or otherwise. And yes, technically feasible for each devices to serve up their own SPA, though I still fail to see why one would want to go to individual sites when a centralized interface for looking at the units both individually and as a group would be more efficient. To each their own, I guess.
    - Spooky23 9y ago
      Right now you are beholden to the Amazon, Apple or vertically integrated solution to access your IoT devices. My thermostat cost $10 75 years ago. I would prefer that a $200 thermostat have a life longer than the technology platform.

jjeaff 9y ago

But then it can either only be accessed within the same subnet, or you are going to have to do some port forwarding. Which is too much to ask for 99% of users.

zdragnar 9y ago

It's not terribly useful for each fish tank thermometer (or whatever) to run its own server and webui, since what you're probably interested in is "are all of my things behaving as expected". Having that data be centralized- on site or off- is where a web UI can be most useful. A friend of mine rolled his own version of this for his house, helping him optimize how the furnace / ac units operate, etc. It would've been way more painful to go to each devices UI individually.

Spooky23 9y ago
Why not? That server could have an api for a management device to discover and manage it as well.
- jsjohnst 9y ago
  Especially if it’s a SPA, the same API (with minimal changes) that drives the web UI could be available to others on the network.
- zdragnar 9y ago
  That does make sense, http or otherwise. And yes, technically feasible for each devices to serve up their own SPA, though I still fail to see why one would want to go to individual sites when a centralized interface for looking at the units both individually and as a group would be more efficient. To each their own, I guess.
  - Spooky23 9y ago
    Right now you are beholden to the Amazon, Apple or vertically integrated solution to access your IoT devices. My thermostat cost $10 75 years ago. I would prefer that a $200 thermostat have a life longer than the technology platform.