@Dennis.... expected a disconnect as well... but if the CH_PD does kind of the same plus even more, it might be worth to sacrifice a pin to control that... from a 'comprehensive' software point of view a disconnect makes sense though... it could even be tied to a pin when passed on that pin on initialization ;-)... now I'm getting ahead of...
Furthermore - if it is easy to add 'custom' commands to wifi wrapping AT wrapping device, adding an at(atString, callback) could be the solution. The method would include the setup of the context and abstract callback handling. This method would Drawing a line for a standard what is included and what is not is a gray zone.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@Dennis.... expected a disconnect as well... but if the CH_PD does kind of the same plus even more, it might be worth to sacrifice a pin to control that... from a 'comprehensive' software point of view a disconnect makes sense though... it could even be tied to a pin when passed on that pin on initialization ;-)... now I'm getting ahead of...
Furthermore - if it is easy to add 'custom' commands to wifi wrapping AT wrapping device, adding an
at(atString, callback)
could be the solution. The method would include the setup of the context and abstract callback handling. This method would Drawing a line for a standard what is included and what is not is a gray zone.