4 ms·

How would you suggest getting that information (say, a fixed IP address and gateway) into a part that has no user interface and no removable storage? How about

How would you suggest getting that information (say, a fixed IP address and gateway) into a part that has no user interface and no removable storage? How about after deployment?

Animats 10y ago
The device here had to be configured with a URL for the user's web server. The real problem is, how do you securely introduce your home devices to each other? Various schemes have been tried - proximity, reading serial numbers off labels, and pushing the "pair" button at both ends at roughly the same time.
- deleted 10y ago
  [deleted]
laichzeit0 10y ago
Isn't the usual approach for these things to not use IP or wireless at all, but some other simple serial protocol like ZigBee and have them talk to a gateway "controller" that's connected to the outside world? The last time I played with wireless sensor networks that's how it worked, and they can actually form their own mesh network.
- jordz 10y ago
  That's still the case indeed.
Isamu 10y ago
Zeroconf networking? I've done a bit of that, both Bonjour (Apple) and UPnP (Microsoft). It is doable. I recognize that these things are tiny, but I've worked with extremely limited, real-time devices too - it can be done. https://en.wikipedia.org/wiki/Zero-configuration_networking https://en.wikipedia.org/wiki/Zero-configuration_networking
CountSessine 10y ago
So the fact that this isn't possible easily is the answer to Animat's question, "how did we screw up networking." As for how I would solve it, it seems like something like mDNS should be in the solution space. But I don't think consumer routers or operating systems make this easy enough.
Taniwha 10y ago
We have a similar device, using better sensors, runs off 2 AAs (the DH11 is cheap but us not very accurate) - we run in deep sleep to get good battery life - we'll open source it soon. We configure it by making the device an AP an offering up a list of local APs on a tiny web server

How would you suggest getting that information (say, a fixed IP address and gateway) into a part that has no user interface and no removable storage? How about after deployment?

Animats 10y ago

The device here had to be configured with a URL for the user's web server. The real problem is, how do you securely introduce your home devices to each other? Various schemes have been tried - proximity, reading serial numbers off labels, and pushing the "pair" button at both ends at roughly the same time.

deleted 10y ago
[deleted]

laichzeit0 10y ago

Isn't the usual approach for these things to not use IP or wireless at all, but some other simple serial protocol like ZigBee and have them talk to a gateway "controller" that's connected to the outside world? The last time I played with wireless sensor networks that's how it worked, and they can actually form their own mesh network.

jordz 10y ago
That's still the case indeed.

Isamu 10y ago

Zeroconf networking? I've done a bit of that, both Bonjour (Apple) and UPnP (Microsoft). It is doable. I recognize that these things are tiny, but I've worked with extremely limited, real-time devices too - it can be done. https://en.wikipedia.org/wiki/Zero-configuration_networking https://en.wikipedia.org/wiki/Zero-configuration_networking

CountSessine 10y ago

So the fact that this isn't possible easily is the answer to Animat's question, "how did we screw up networking." As for how I would solve it, it seems like something like mDNS should be in the solution space. But I don't think consumer routers or operating systems make this easy enough.

Taniwha 10y ago

We have a similar device, using better sensors, runs off 2 AAs (the DH11 is cheap but us not very accurate) - we run in deep sleep to get good battery life - we'll open source it soon. We configure it by making the device an AP an offering up a list of local APs on a tiny web server