OpenAgricultureFoundation / openag-device-software

Software for running controlled grow environments on Linux / OSX machines and embedded linux devices such as Beaglebones and Raspberry Pis.

GNU General Public License v3.0

192 stars 50 forks source link

Simplify & improve the provision / registration process #145

Closed rbaynes closed 5 years ago

rbaynes commented 5 years ago

New S/N format and central ID storage

We will use a single number for everything the user sees. It will be a serial number in this format: "PFC_EDU-XXXX" where the XXXX is the 4 digit BBB access point code (if on eth, use eeprom code).
Store provisioned IDs in /etc/openagbrain/serial_number.json
- "AP_number": "XXXX"
- "eeprom": "ABCDEF123" (perhaps don't use for serveo/ngrok link? use shorter AP code?)
- "serial_number": "PFC_EDU-XXXX" (XXXX is AP_number)
- "deviceID": "EDU-$CKSUM-$MAC" (from the IoT reg script)

Create a new Provision page (in the provision drop menu)

Page checks if device is online, if not, prompt user to go to (link) Connect page and hide everything.
There is a one time use "Provision this device" button that is shown if there is no /etc/openagbrain/serial_number.json file.
Provision button creates /etc/openagbrain/serial_number.json and does the public IoT reg (runs the script).
Page shows the generated info when done for information only (for us).

New single number (S/N) procedures

We now label the EDU with a single number, just the S/N described above.
In the header (or footer) of the device UI, we show the S/N and the debian package version (for quick and easy support)

Change default BBBs AP name and password

In our flasher image, change the default BBBw AP name to our S/N, password to openag
Should the Change password page also change the AP password?

Password protected OpenAg only ngrok paid client provision step

Rob has to play with ngrok link and get some answers from them about how their auth step works.
This will fix #125

rbaynes commented 5 years ago

Need to save this big enhancement (may also involve cloud UI for vcode device reg) for after Nov. 21 pilot test.

rbaynes commented 5 years ago

figure out what the XXXX code is in the BBBw AP

How is it generated? 4 hex digits is only 65536 unique numbers.

Should we use the (shortened) eeprom or mac?

jakerye commented 5 years ago

this is no longer pertinent. upon the next production roll out, the provisioning and registration flow should be re-examined to support a platform agnostic flow