update plan

Author: tyeth

testplan.md

@@ -9,6 +9,9 @@ Cleanup eraseCPFS and retest with full file system and no secrets + different bo
 
 Add boot reason detection for brownouts, if so and corrupt secrets/FS then fsHalt with appropriate message for 30s then reboot
 
+As part of boot protection add message when write or erase attempt and suggest user manually perform action.
+ Secondly consider moving all serial debug output to after usb reattach so user sees it, or at least repeat?
+
 
 then add the metro-s3
 Update step images in ws_boards for metro-s3
@@ -18,4 +21,13 @@ then add FT usb-to-gpio to ws_python
 
 Test ws_boards c6-aVref branch (esp32 aref=1.1 instead of 3.3, and C6 from 1.1 to 2.5v)
 
-Fix pin numbers + names for Metro S2 (all digital etc, tx/rx and D1 [etc] seem wrong, analog5 is wrong etc)
+Fix pin numbers + names for Metro S2 (all digital etc, tx/rx and D1 [etc] seem wrong, analog5 is wrong etc)
+Add guide pages for wippersnapper on metro s2
+Add guide pages for WS on C6
+
+Check in on Marty's code / local mqtt issue.
+Look at exception handling in mqtt library which seems biggest user hurdle
+- consider capturing OSError etc and return mqtt exception?
+- look at how IO fails too
+- catch gai dns errors
+- see what happens when no response / waiting message during loop call (people report exception but actually valid to have empty response)