I've found that if onInit immediately disconnects, it can confuse the IDE.
Yes, I can imagine :) However there should be no need to force a disconnect - I know you're trying to weed out potential issues, but in this case it might just be causing problems. I'd just call setServices direct on onInit, and then manually disconnect?
I'd be worried that after saving, if you then power on the device, 3 seconds is enough that the Mac might already have tried to connect to it, and is then disconnected in the middle of negotiation.
But yeah, if it works and it's a sleep/wake issue then it could be something else I guess.
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.
Yes, I can imagine :) However there should be no need to force a disconnect - I know you're trying to weed out potential issues, but in this case it might just be causing problems. I'd just call setServices direct on onInit, and then manually disconnect?
I'd be worried that after saving, if you then power on the device, 3 seconds is enough that the Mac might already have tried to connect to it, and is then disconnected in the middle of negotiation.
But yeah, if it works and it's a sleep/wake issue then it could be something else I guess.