Screenshots that show the firmware people actually download - #195
Merged
Conversation
The five generated dashboard images were captured on 2026-07-31 against 0.25.1. Three releases have shipped since, and the version string is printed in the header of every one of them -- so the first thing a reader saw was a build two minor versions behind the one they were about to flash. Recaptured from the production bridge, now running 0.27.2. The tabs themselves have not changed shape; what is different is the header, the counters, and a fixture that matches a firmware someone can actually get. discovery.png is untouched and stays dated 2026-07-26. It cannot be regenerated by this tool -- it needs a live bus mid-probe and a human clicking through the wizard -- which docs/README.md already records as the one image that ages without anyone noticing. Sanitisation verified rather than assumed: the fixture was diffed against what the bridge actually returns, for serial number, SSID, hostname, NTP server and bridge id. No live value survives into the committed file, which matters because both the fixture and the images are published. Dashboard layout check and all gates pass.
Timdebruijn
marked this pull request as ready for review
August 27, 2026 11:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The screenshots
The five generated dashboard images were captured on 2026-07-31 against 0.25.1. Three releases
have shipped since, and the version string is printed in the header of every image — so the first
thing a reader saw was a build two minor versions behind the one they were about to flash.
Recaptured from the production bridge, now on 0.27.2. The tabs have not changed shape; what is
different is the header, the counters, and a fixture matching a firmware someone can actually get.
discovery.pngis untouched and stays dated 2026-07-26 — it cannot be regenerated by this tool(it needs a live bus mid-probe and a human clicking the wizard), which
docs/README.mdalreadyrecords as the one image that ages without anyone noticing.
Sanitisation verified, not assumed. The fixture was diffed against what the bridge actually
returns for serial number, SSID, hostname, NTP server and bridge id. No live value survives into
the committed file — which matters because both the fixture and the images are published.
The README pass
Checked every factual claim against the code. Nothing needed changing, which is worth stating
because it was not true two weeks ago:
the path, which is the correction made in the last round
Verification
Dashboard layout check passes, all twelve layering checks pass.