Niimbot
eigger/hass-niimbot · v4.3.0
Niimbot Label Printer Home Assistant Integration
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
button | Button (as a switch) | |
select | Mode picker (as switches) |
What people report
Local Bluetooth integration for Niimbot label printers; B1 Pro added, RFCOMM-only models are unsupported, and some adapters fail discovery.
- Works1
- Partly works1
- Won’t be supported1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Niimbot B1 Pro | Works Local | Support added in 2026Saved copyThis pull request adds support for a new printer model, `B1_PRO`, to the `niimprint` module. The changes ensure the new model is recognized and its properties are properly defined. New printer model support: * Added `B1_PRO` to the `PrinterModel` enum in `model.py`, allowing it to be referenced throughout the codebase. * Defined the metadata for the `B1_PRO` model in the `PrinterModelMeta` list, including its ID, DPI, print direction, printhead pixels, and supported paper types. Note that this requires the dimensions: 567x354 due to the 300 DPI Excerpt saved from GitHub on 2026-10-23. | PR #47 · 2026-03 | |
| Niimbot D110 | Partly works Local | Not found through Shelly Bluetooth adapter; no local name seenSaved copy… possible to use the shelly devices for your integration as well? Right now when I try to add the integration in HA it only says "no device found". Have a new D110 and it is on and works with the Niibot App on the phone. Thanks in advance. Excerpt saved from GitHub on 2026-10-23. | Issue #43 · 2026-02 | |
| Niimbot B21 | Won’t be supported Local | Device that supports only RFCOMM is not supportedSaved copyI get the error that the Characteristic was not found, it also seems to not read any data. Probably for my device the Uids are different: Excerpt saved from GitHub on 2026-10-23. | Issue #101 · 2026-08 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local polling
Talks to the device on your network, asking it for updates every so often.
Found automatically over
- Bluetooth
Details
| Installs (analytics) | 172 (0.02%) |
|---|---|
| GitHub stars | 126 |
| Latest version | 4.3.0 (2026-10-23) |
| Set up in the UI | Yes |
| Maintainers | @eigger |
| License | MIT |
Notable forks
Forks with stars, or with code pushed at least 90 days after the original’s last push. Useful when the original goes quiet.
| Fork | Stars | Last push | Description |
|---|---|---|---|
| Rudd-O/hass-simple-image-raster | ★ 3 | 2026-04-09 | Generate pictures on the fly to print or update ePaper displays. Simple image rasterizer based on PIL / Pillow (derived from Niimbot Label Printer Home Assistant Integration). |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
Sources
- Documentation: https://github.com/eigger/hass-niimbot
- Source code: https://github.com/eigger/hass-niimbot
- Issues: https://github.com/eigger/hass-niimbot/issues
- HACS: https://hacs.xyz
