Tagged video
all 74hardware 30console 22video 22update 15network 13diagnostics 11input 11storage 10security 8display 7media 6community 4home-assistant 4screen-text 4mobile 3vpn 3boards 2power 2api 1dashcam 1demo 1explainer 1hdmi 1m5stack 1notifications 1ota 1recording 1tailscale 1terminal 1
-
0.65.0 - video over Tailscale that keeps up
Frame acks, so a slow link shows the newest frame instead of a queue of old ones, and a run of Tailscale fixes that took video between two ESP32-P4 devices from 1-3 fps to 11-14.
-
0.62.0 - 155 ms from your mouse to the picture, and twice the free memory
H.264 in the browser lost 170 ms of delay, a button measures the whole round trip, video adapts to a slow link, task stacks were cut to what they use, and a restart no longer signs anyone out.
-
0.56.2 - Wi-Fi that holds a stream
Over Wi-Fi the P4 ran out of internal RAM as soon as the console loaded. Two buffers moved to PSRAM, and a FireBeetle 2 that stalled now streams without a break.
-
0.54.0 - exFAT cards, all keys in full screen, and a picture that left the device twice
A microSD card straight out of the packet works now, even above 32 GB. The console can send Alt+Tab and the Windows key to the target. And every frame had been leaving the device twice.
-
0.52.2 - Fixed: no picture on the M5Stack PoE-P4 after the target switches to a text console
The picture vanished when the target switched to a text console, and the firmware had an answer for exactly that - behind a check the board could never pass.
-
0.52.1 - Fixed: after an update the device rolled back to the old version
An update would install, reboot, and come back as the old version. The new image was never the problem - it never ran. The firmware on its way out broke the boot behind it.
-
0.52.0 - Support for the M5Stack Unit PoE-P4 with the Display In module
A whole IP-KVM the size of a matchbox. Its capture module uses a chip this firmware had never driven, and getting a picture out of it took a week - in which I was wrong three times and the chip was innocent every time.
-
0.51.0 - Recording the screen to microSD: videos, screenshots, dashcam, timelapse
A car dashcam records the road nobody is watching and keeps the minutes before the crash. This release gives a server the same thing: the screen goes to the device's own microSD card, the last minutes are held and saved when something happens, and the console plays it all back - with what was typed as subtitles, and search over what the screen said.
-
0.50.0 - swap the card while it runs, and a picture that keeps up
The microSD card can go in and out without a restart, even in the middle of a copy. And on a still screen the MJPEG picture no longer shows the screen as it was before your last key.
-
0.48.0 - microSD and WiFi at the same time
0.48.0 lets the microSD card and WiFi run together, keeps the video alive when the HDMI signal comes back, lets H.264 be switched on after boot, and adds a Sign out button.
-
Compiled for a debugger all along
0.46.2 is the first build at -O2. Also why a device with 314 KB of free RAM could not find 155 KB of it, and a watchdog that now reboots instead of writing a warning.
-
Twelve minutes of blocks, then twelve minutes of fine
The still-screen fault was an int32 overflow in the H.264 rate controller. Why raising the bitrate made it worse, how the arithmetic was checked on hardware, and why the fix is a one-line version bump.
-
Two more boards, and a watchdog for a picture that breaks into blocks
0.46.0 adds the Waveshare ESP32-P4-NANO-WIFI6-DB and the VIEWE ESP32-P4-Pi, and ships a guard for the still-screen fault where the picture goes blocky and heals itself.
-
0.42.0 - two things can no longer share a pin
A settings write that would put two things on one GPIO is refused, a capture driver announces itself instead of being called by name, and a keyboard the target has forgotten can be re-plugged from the console.
-
0.41.1 - a fix that was there and did nothing
I shipped a WiFi fix and never called the function. The person who reported the bug found the missing line himself. While checking that release I found a crash that had been hiding behind three different symptoms.
-
0.37.0 - the screen as two kilobytes
Work a machine over a phone tether by sending the characters instead of the video, hand a dashboard a view-only token, and go back to any published release.
-
0.28.0 - reading the screen as text, and watching it while you are away
Select and copy the words off a BIOS screen instead of typing them out, and let the device raise an alert when a phrase you care about appears.
-
0.24.0 - point a phone at the screen to get in
The round LCD shows the rescue hotspot as a QR code, the certificate finally names the address DHCP gave the device, and the reset button shows that it heard you.
-
0.22.0 - two firmware slots, and a way back
The firmware panel shows both slots and can boot the other one, so going back to a build that worked needs no cable.
-
0.17.0 - WiFi, and a hotspot for when it fails
On boards with an ESP32-C6 the KVM can run over WiFi, put up its own hotspot when the network is gone, and open the console on your phone by itself.
-
0.11.0 - the device becomes its own certificate authority
Import one small certificate once and the browser trusts the device for good - which is also what unlocks H.264 and the keyboard channel.
-
0.1.2 - the first working KVM
The first tagged builds. HDMI capture, a keyboard and mouse the target cannot tell from real ones, a web console over HTTPS, and updates over the network.
