The auto-update process is quite memory intensive. If the update fails it's often the WebUI update that succeeds and the firmware update itself that fails. If the WebUI commit is on c37347aa7293cf9dddf5a78d8ac16469c7bc49bb you can just flash the firmware file itself. It should specify which firmware file you need to download from https://git.btclock.dev/btclock/btclock_v3/releases/tag/3.3.10 Just updating with the firmware file should bring the WebUI and firmware version in sync again. Alternatively just retrying the auto-update it again if it presents the option could also fix it. I had one Rev. A that had a successfully updated only after the 3rd try π