0.11.0 - the device becomes its own certificate authority
A self-signed certificate gets you a warning page you can click through. That is fine for a settings page and useless for the interesting parts: a browser will not open a WebSocket or hand video to a hardware decoder over a connection it does not trust. So the click-through cost H.264 and, in some browsers, the keyboard.
The device now generates a small certificate authority of its own, once, and keeps it. That authority signs the certificate the console is served with. You can download the authority from Settings, or from /cert.pem, and import it into your machine's trust store - and from then on the device is genuinely trusted, warning gone, H.264 and the control channel working.
The important part is that this survives change. When the hostname or a static address changes, the device re-issues its own certificate under the same authority. The import you did once is still good.
This release also fixes something embarrassing that had been broken since 0.9.0: the web server's routing table had one slot too few, and the two WebSocket routes were registered last, so they were the ones that silently disappeared. Every ordinary page still answered, which is why it looked like a browser problem. H.264 video, keyboard and mouse are back.