Hm I am also having issues with the speed here… I noticed it works a lot better though when I disable the Bermuda BLE and Passive BLE Tracker integrations (that I was not using for the most part anyway…) I also disabled active scanning there…
performance settings to tweak how HA talks to the printer and make it go faster
a “last label made” image entity that you can place on your dashboard
preview-only mode for when you want to design a label using the niimbot.print service call but you don’t want to waste paper; complements last label made image very well
multiline labels with auto-fit line width
It’s looking good! Thanks to eigger for prompt PR reviews.
This should be fixable with the new config settings (you can test them via the service call, but to make them permanent you have to delete and readd the config entry).
I have never gotten that notification. If my printer is offline, instead of getting a notification like that, I get an error in the trace of the automation or script that ran the service call.
By the way, the combination of Grocy (the Inventory for Personal Homes app), its support for label making via JSON and HTTP REST endpoint, and Home Assistant with the Niimbot is PHENOMENAL.
SUP FOLKS MEGA HEADS UP FOR ALL NIIMBOT PRINTER USERS:
If you are using Bluetooth proxies to print labels with this integration (almost certain many of you are), update your Bluetooth proxies to ESPHome 2025.11.2 right now.
Prints that would take 20-30 seconds before now come out in a flash. It’s almost instantaneous.
Reliability of prints is also enormously improved. I used to see refusal to print (until the integration was reloaded) every 3 out of 10 labels. Now it works errytiem always.
Seriously, leap into the latest ESPHome ASAP.
The main technical reason for this improvement is that, whereas before, every line sent to the printer would wait for an acknowledgement up to 16 milliseconds in the event loop of the Bluetooth proxy device, now these GATT acknowledgments are received instantaneously and processed using a loopback process inside of the ESP device. In previous iterations of the integration, I added a feature that would allow BT proxies to relay a configurable number of print lines without waiting for acknowledgments, but relying on that usually came at the cost of reliability. Now that acknowledgments are lightning fast, this does not need to be enabled, although you still might see some tiny improvement in print speed compared to the baseline configuration. It should also be possible to configure a lower time to wait between print lines being sent, and gain performance this way.
OP you may want to update the README to mention this development.