I may have incorrect docs, will look later. I replaced the "connected" event by, what i think is a more accurate "associated" event, and the "got_ip" by "connected". Part of the reason was that once someone adds static IP support the got_ip doesn't make much sense anymore, but getting "associated" and "connected" still does. So you can trigger off "connected" whether you have a static IP or a dynamic one.
WRT probe_recv, you probably have the AP on. When you flash blank.bin the default is to have the AP on, which makes sense going forward because it will allow for serial-less operation.
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.
I may have incorrect docs, will look later. I replaced the "connected" event by, what i think is a more accurate "associated" event, and the "got_ip" by "connected". Part of the reason was that once someone adds static IP support the got_ip doesn't make much sense anymore, but getting "associated" and "connected" still does. So you can trigger off "connected" whether you have a static IP or a dynamic one.
WRT probe_recv, you probably have the AP on. When you flash blank.bin the default is to have the AP on, which makes sense going forward because it will allow for serial-less operation.
I'll fix the docs WRT callbacks.