Open gerasdf opened 4 years ago
a possibility is for the user to send a /allown <bssid>
or /own <bssid>
command, which could automatically own all un-configured devices connected to that bssid. Also /own <essid>
could work. Both can be faked, and essid
won't work for a fixed essid as in #28.
(It's not trivial for a user to know it's bssid, or is it?)
uhm... a possibility is to change #28 to allow the user to open a WiFi AP with any essid but a fixed (factory defined) password. The device could try to connect to all visible APs, with the known password. The one that works is the chosen one, and after that, the ESSID can be used as identification for the /own
commands
better: isntead of ANY network, the user should open an AP with ESSID "IoT:whatever", and fixed password. Whatever is used to identify the user for the /own
commands
this one I like better :-)
When the user first plugs in a device (or on missconfiguration or factory reset), there should be an easy setup procedure.
Internet access can be assumed (see #28 and as now implemented using AutoConnect portal)