PiBox » Iron Man » Monitor

This actually implies that pair mode is enabled at boot time. If it's not enabled at boot time, but is later enabled, that's okay. That's how Jarvis and IoT devices pair. The boot time pair enabled scenario is just used to configure the two networks (wifi client and AP).

This is actually a little different than what I thought and I've changed the title of the issue to reflect that. First, the code is working in S90imwww for the imwww server. It does what it's supposed to do at boot time for imwww. It does not (yet - see RM #637) start imrest (via NodeJS) at boot time if the button is not enabled.

1. It's not Pair Mode at boot time. It's Config Mode at power up because we're configuring the network interfaces via

   imwww

   .
2. Pair Mode is enabled if the button is enabled at run time.

The button serves a dual purpose. At power up it is a Config Mode button. At runtime it is a Pair Mode button.

This is the same design as imlightsw (the sample IoT device). But I need to make sure all documentation and code reflects this before I go further.

Then I need to add a new function to init.js. This gets called at the start of the registration functions to check if the button is enabled, meaning Pair Mode is enabled. If not, return an error code.

All code is implemented in the ironman www clone, but it's not tested or committed yet.

1. Verify server is running imwww at boot time with the Mode button enabled.
2. Verify server is running imrest in operational mode at boot time with the Mode button disabled.
3. Verify server is running imrest in Pair mode at run time with the Mode button enabled.

This requires setting up fake imgpio usage if not run on real hardware.

All scenarios verified. Monitor configures networks properly in Pair Mode at boot time. It handles IoT registration in Pair Mode at run time.

All changes committed and pushed.

Closing issue.