What the patch promises
niimbot targets the Niimbot B1 on firmware 5.22. Its README describes darker printing on third-party or untagged paper and a density setting that changes print energy. Those are upstream claims, not results from our sandbox.
The documented mapping runs from coefficient 270 at D1 to 400 at D5. The author describes D3 as the practical minimum on typical paper and D1 as suitable for more sensitive thermal stock. Paper-dependent results still need a physical check.
The README explicitly excludes other models and firmware versions. It warns that flashing across major versions, including 5.x and 6.x, will brick the device. Confirming the version is the first setup decision; a checksum cannot establish compatibility.
What our recorded run establishes
Our run took place on October 7, 2026, at commit 3c7a4894df186cf68fc338b93523f9638935ff25. The raw record marks the install step successful in 16,618 ms and the build step successful in 4,392 ms. The summary rounds these to 17 and 4 seconds and records 27 seconds for the overall harness run. Adding the rounded step times gives 21 seconds, not the overall run duration.
The harness recorded 35 dependencies and 37 MB of dependency installation space. Its checkout summary recorded 13 files, approximately 320 source lines and 0.3 MB. Detection recorded no CI workflows, Dockerfile or tests directory. These are dated parser observations, not an exhaustive repository audit.
The retained install output says only that it used a Python 3.12.12 environment. The build output is empty. Successful step statuses therefore do not show which dependencies were downloaded, that @mmote/niimblue-node was installed, or that the firmware was rebuilt. No installed-binary check or hardware workload is recorded.
Tests were skipped with reason "no script". That is not a failed test result and does not establish that no other testing method exists. The repository supplies five manual density print samples.
Pip-audit recorded 0 advisories. The record does not establish audit coverage, so this cannot support a claim that all dependencies were checked or that the firmware is safe.
Firmware files and the build evidence
The README identifies B1_5.22_density_coeff.bin as the density-controlled patch and gives its expected MD5 as 023ff56326fe8c65f01b68f32ebdba99. It describes B1_5.22_thirdparty_fullquality.bin as a fixed-darkness fallback without density control. Stock 5.22 firmware is not distributed here; the documentation directs readers to obtain it separately.
The reverse-engineering notes describe the density byte, scaling table, renderer detours and assembly/link procedure. They describe the density patch as 112 changed bytes on top of the fixed-darkness build. Commit 3c7a489 added the missing linker script, and its message reports that rebuilt sections matched the supplied firmware at four documented offsets. That is an upstream verification claim. Our empty build tail does not independently reproduce it or establish an end-to-end firmware build.
The notes provide material for a technical reader to inspect. Their energy-model argument is not a substitute for measured print-head behavior or hardware regression testing.
Flashing and print checks remain physical work
The README uses the separate @mmote/niimblue-node CLI to flash over USB serial and shows /dev/ttyACM0 as the Linux port. It says the printer powers off after flashing and must be turned back on. Our sandbox did not execute or verify that sequence.
The included src/niimbot_b1.py driver is documented for printing 384-pixel-wide images over USB. The suggested check is to print each supplied D1 through D5 image at its matching density and inspect the progression. That would check output on the particular printer and paper used; it would not establish compatibility with other firmware versions or guarantee recovery.
In the supplied RFID discussion, the maintainer reports full-darkness printing on third-party rolls without a Niimbot tag, using the project's USB driver on patched 5.22 firmware. They explicitly say they had not tested a genuine roll whose counter had run out. The same thread includes a report about firmware 6.19, which falls outside the supplied patch's stated target. Do not generalize the maintainer's result to the official app, exhausted genuine rolls or other firmware versions.
Recovery is unresolved evidence, not a guarantee
The supplied recovery discussion concerns a user's additional modifications to a 5.22 image. The user reported that printing and connections initially remained possible while normal reflashing failed. The maintainer suggested reflashing stock firmware and cutting power, and explained that the published images contain the application rather than the bootloader. A later user reply reported a command-line timeout and rejection by the official app. The supplied thread does not establish a successful recovery.
This is not evidence that either unmodified supplied binary caused that failure. It is a reason to avoid assuming that a responsive printer can always accept another image. The README's fallback instructions should be read as a procedure to investigate, not a recovery guarantee.
Choosing between a patch and a printing client
If the goal is label design and printing, start by checking the client requirements. niimblue's README describes a browser editor with Bluetooth and USB connections, but says there is no exact supported-model list. NiimPrintX's README describes Bluetooth printing with CLI and GUI applications and lists the B1 among its models. Neither supplied extract establishes that these clients reproduce this firmware patch's claimed darkness changes.
Choose the firmware project only when changing B1 firmware behavior is the actual goal and you can evaluate the documented edits and physical results. Our run supplies limited environment-step observations, not a validated printer upgrade.
How the scores were assigned
These are editorial readiness ratings, not measured performance or adoption scores. The rubric is 1 for experimental evidence with major validation gaps, 2 for a usable starting point requiring substantial manual investigation, 3 for a documented routine path with limited verification, 4 for detailed inspectable support within the stated scope, and 5 for broad, independently verified readiness. Each category uses only the supplied evidence; unknown compatibility or adoption earns no credit. Here, documentation earns more credit than operational maturity because the patch map is inspectable while hardware results remain upstream reports.

