I could be wrong here, but I think that when the app connects it runs some magic command on the Smartibot (it may just end up being smarti = require("Smartibot"); or something like that).
You'd have to ask Smartibot what the actual command is (or maybe disconnect the app, open the web IDE, and try using up-arrow to look back in the command history).
Either way if you ran reset() it'd blow away the result of running that command, which may be why the dpad no longer works?
I guess looking at what you're doing, just calling stopWallAvoid() and not reset() might be enough? Although possibly calling load() to run your code might have removed the code the app uploaded too...
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 could be wrong here, but I think that when the app connects it runs some magic command on the Smartibot (it may just end up being
smarti = require("Smartibot");
or something like that).You'd have to ask Smartibot what the actual command is (or maybe disconnect the app, open the web IDE, and try using up-arrow to look back in the command history).
Either way if you ran
reset()
it'd blow away the result of running that command, which may be why the dpad no longer works?I guess looking at what you're doing, just calling
stopWallAvoid()
and notreset()
might be enough? Although possibly callingload()
to run your code might have removed the code the app uploaded too...