Actually I've just set this up myself and can get the same thing to happen. Sorry about that.
Looks like it is a software bug - not sure how that crept in, unless the fix didn't make it into 1v72 after all. It seems like it might be to do with the recent change which allows the real-time clock to keep track of time between resets.
It seems that if you completely power down Espruino so the RTC loses all of its state then it should work. However if you reset Espruino then its RTC remembers the last time and everything breaks.
Looks like just adding even setTime(0) is probably enough to fix it in 1v72, but I'll make sure I get this fixed properly for 1v73 (which it looks like I'll be releasing quite soon!).
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.
Actually I've just set this up myself and can get the same thing to happen. Sorry about that.
Looks like it is a software bug - not sure how that crept in, unless the fix didn't make it into 1v72 after all. It seems like it might be to do with the recent change which allows the real-time clock to keep track of time between resets.
It seems that if you completely power down Espruino so the RTC loses all of its state then it should work. However if you reset Espruino then its RTC remembers the last time and everything breaks.
Looks like just adding even
setTime(0)
is probably enough to fix it in 1v72, but I'll make sure I get this fixed properly for 1v73 (which it looks like I'll be releasing quite soon!).