follower wrote:Yeah, I can confirm this is the case for me as well. Which doesn't make it less odd. It seems to be failing at very first attempt to enter command mode.luwii wrote:If you modify the subsections of of switchToCommandMode, more specifically WiFlyDevice::attemptSwitchToCommandMode() in WiFly.cpp then I don't seem to be able to connect to the WiFi network (Not too worried why)Do you mean if you make the change in 'attemptSwitchToCommandMode' rather than client close it doesn't work? Odd.
After looking into it more I think I'm going to try a different approach to library startup. The combination of board versions, firmware versions, possible configurations, module state and timing means it's non-trivial to handle every possible startup state--especially for the older boards that don't have hardware reset functionality.