Thats really weird. Honestly, I don't think it's the weather.json...
@Gordon Could it be that an exception is thrown in the "on exit" event and then the firmware calls "on exit" again which again raises an exception such that it is stuck in a loop (on exit -> exception -> on exit -> exception -> ...)? I could easily refactor this to save settings whenever something is changed rather than "on exit" in case this could be the problem and also try catch on exit which would probably a good idea in general... Otherwise I honestly have no idea how this could happen...
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.
Thats really weird. Honestly, I don't think it's the weather.json...
@Gordon Could it be that an exception is thrown in the "on exit" event and then the firmware calls "on exit" again which again raises an exception such that it is stuck in a loop (on exit -> exception -> on exit -> exception -> ...)? I could easily refactor this to save settings whenever something is changed rather than "on exit" in case this could be the problem and also try catch on exit which would probably a good idea in general... Otherwise I honestly have no idea how this could happen...