Yes, i updated the esp and the atmega, reverting back to 353 solved the problem
Just to follow up... I was able to reproduce the problem here with Rev.2 V.355 when I loaded it on my Modular clock and WiFi module. It's a legit bug, the source of the problem has been located, and Ian tells me he's fixed it and will make it available very soon. Not sure if it will still be called 355 or rolled to 356.
Look into it later when the dust is clearing off the crater.