Hey folks! Hope all is well out there. I am a pretty rundown with a flu-ish/head cold type bug and wanted to get an update out before my inventible crash in a couple of hours.

I am going to do a quick rundown through some of Mugsy’s first boot screens/steps. The brain is very clunky right now, so I’m not going to go into too much detail, but will add additional info in a future update (Tuesday/Wednesday).

First Boot: Wifi

After the initial boot splash and loading screens, you will be dropped into the First Boot set up process.

Mugsy will spin up an adhoc wifi network. This connection is temporary and will only be used to connect Mugsy to your actual local network wifi.

Mugsy will display a QR code that you will scan from a mobile device:

Open your mobile device’s camera app to scan the code. A button will pop up to Join MugsyWifi:

Once clicked, your phone will ask you if you would like to connect to Mugsy’s Wifi connection:

Once connected, you will be able to select your actual local Wifi network through your phone’s web browser:

First Boot: Initial User Creation

Next you will move on to creating your first user. All of the following configuration screens can be accessed from Mugsy’s screen or the mobile device you used in the previous step.

Please note that the first user must be an admin level user. In production, the admin toggle will be greyed out with a tooltip explaining this. Any additional users can be configured to have more limited or granular privileges.

First Boot: Basic Settings

Next you will configure some very basic privacy settings. I will go over all of these in more detail in the next update, but for now the basic gist is that online Cloud Control features are only meant to supplement Mugsy’s functionality and are in no way required for you to use Mugsy . You can pick and choose what Cloud Control features you want to allow or shut them all off. Please note that the following image does not show an exhaustive list of options, it’s just the very basic ones that will determine the initial DB seeders and access types. Further granularity will be available within the main settings options after the first boot process is completed.

First Boot: Everything Else

• Systems Check: Once steps 1-3 are completed. Mugsy will run a systems check to make sure all hardware is responding as expected. I have not created a front end interface for this step yet, so nothing to show at this point. The actual hardware scripts that runs the check is mostly completed. Only remaining thing is to integrate it in to the task management system.

• Ready to Brew: Once the systems check is completed, the system is ready to brew and you will be dropped into the main Mugsy interface.

Other Bits:

• Apologies for any typos or clunky wording in this update. The brain is super cloudy right now…

• In regards to the weekend todo list I posted in Friday’s update:

  • I completed the mongoDB shapes and got some of the commander.ino work done, but not all of it.

  • I have not touched the HTTPS and CAD tasks and do not expect to get to them today unless I start feeling better.

Ok, that is all for now. I will have another update out in 48-72 hours.

Thanks!