0.25.0 - the device keeps its own log
When a device misbehaves and then reboots, the evidence normally goes with it, and the only way to have caught it was to have had a serial cable plugged in before it happened. Which nobody does.
The device now keeps a log in a small ring in memory that a restart does not clear. So after a boot that failed, you can come back on a working firmware and still read what the failed one said. Diagnostics, then "Download the log".
It holds no passwords or keys. It does name your network, your addresses and the MAC, and the console says so at the point where you download it, because that is a file people paste into issues.
The update shows itself on the little screen as well now: the percentage while the image arrives, then verifying, then restarting, and what went wrong if something did. An update is the longest thing the device does with nothing to show for it, and the console has just been asked to give up its video connection for the duration - so whoever is standing at the box has somewhere to look.
There is also a fix worth naming, because it is the second time the same thing bit us: adding one endpoint pushed the web server's route table past its end, and the route that fell off was the keyboard and mouse channel. Registration past the end used to fail silently. It says so in the log now.