Most recent activity

Also, for the unhandled promise, can you try changing characteristic.writeValue(val); to return ?characteristic.writeValue(val);? I think that'll be the problem - looks like all Espruino's docs need updating as none of them mentioned that.

I have a piece of code with a for loop (loops only 10 times to get lower, avg and upper bounds of light) inside an interval that outputs to the console - see print screen. It keeps working if it's not printing anything, but sometimes I need to either re-upload or switch off the bulb and then back on. You can also see that there is also a promise that wasn't caught which should have been already caught.

I had a try with some code with an interval of 30 seconds and coded some behaviour that allows some light tolerance so that it does not change back and forth all the time. I noticed that sensing light has some variance and this can cause issues. One odd behaviour I notice from the Puck is that when viewing console output after some time, console looping stops and I need to reconnect again to the puck. Although I find that what works well is to switch the AWOX bulb off and then back on. Is this a sync issue?

So far, so good - the behaviour is much more stable, but I'm getting an "Out of memory while appending to array" warning as the interval keeps checking for light levels. Is there a way of doing this in JS or is it C level malloc stuff?

I have tested this over the few days and what I observed is that if there is a timeout error which is caught (sometimes weirdly it doesn't get caught) it will get into a busy state and nothing will happen. What I have to do (manually) is switch the light bulb off from the mains and then back on again and it will resume operation.