Tested models

[MultiMote]

There is a list of tested models. If your model is not listed here, it does not mean that it is not supported.
If you own other model or you have issues with model listed here, please write a comment.
You can test your model with the niimblue project.

My printers, fully supported:

Model	FW	HW	Print task	Notes
D110	13.14	13.10	D110	Сan print without RFID tag with this firmware version.
B1	5.14	5.10	B1
B21_C2B (ID 775) CN	40.23 40.30(factory)	40.10	B1	USB not working on windows if serial port uses NIIMBOT driver.
B21_PRO	3.06	3.01	D110M_V4

Tested by other people:

⚠D110M: Several reports of spontaneous bricking have been received. Avoid using this printer with NiimBlue, I do not want to take responsibility for damaging the device even if the problem is not NiimBlue.

Model	FW	HW	Print task	Notes	Reference
B1	3.03	3.01	B1		#1 (comment)
B1	3.07		B1
B1	5.18	5.10	B1		#1 (comment)
B1_PRO	2.09	2.01	D110M_V4		#1 (comment)
B21_C2B (ID 771)			B21_V1		MultiMote/niimblue#34 (comment)
B21_PRO	2.21	2.01	D110M_V4		MultiMote/niimblue#86 (comment)
B3S ❌				Does not work. UUIDs are uncommon. Maybe android app or usb connection will work.	#1 (comment)
B3S	37.07	37.01		Only USB connection tested.	MultiMote/niimblue#138
B3S_P	3.10	3.01	B1 / B21_V1		#1 (comment)
D101	9.06	9.10	B1		#1 (comment)
D101			D110M_V4		#1 (comment)
D11	21.12	21.01	D110		#1 (comment)
D11 ⚠️	3.60	3.01	D11_V1	Unable to fetch MAC address, printing is fine only when first heartbeat packet is sent before print	#1 (comment)
D110M	4.10	4.01	B1		MultiMote/niimblue#33 (comment)
D110M	4.13	4.01	B1		#1 (comment)
D110M ☠️	4.10			Bricking reported. Looks like software/hardware issue with outdated version. Update firmware first.
D110M	4.23	4.01		Does not print at all without RFID tag	MultiMote/niimblue#81
D110M	4.25	4.01	D110M_v4		#1 (comment)
D11H	4.18	4.01	B1
D11H	4.22	4.01	B1		#1 (comment)
M2 (2024)	1.17	1.01	B1	A valid RFID tag must be near/inside the printer.	#1 (comment)
N1	3.09	3.10	B1

[f870103]

D11 tested on:

• Hardware Version: 21.01
• Firmware Version: 21.12

Please let me know if you need any additional information or specific details about this model.

[nyarau]

D11 tested on Android.
While it shows an error after clicking Print, it prints just fine.
The hardware and firmware version must be very old since I bought it around 2020 and didn't use it for a long time.

Thank you so much for the work!

[MultiMote]

@nyarau That's very odd. It seems like the client is not even able to get the printer information.
What is your printer's hardware and firmware version (you can see it in official NIIMBOT app)?
Can you try it on PC (connect with USB cable if printer supports it or use BLE adapter if you have it) and send browser logs (usually press F12, console tab)?
Alternatively you can copy logs on Android browser supports DevTools (Kiwi Browser for example).

[nyarau]

Firmware 3.60
Hardware 3.01
Judging by the number it's probably too old.
It's printing just fine so I don't plan to update anything, bigger chance they get something locked down in a new version than giving me any meaningful improvement.
Here's browser log

[MultiMote]

@nyarau it's useful information. Looks like response for PrinterInfo packet is not same as in other models. I'll try to figure out how to handle it.
Can you also print some label and check logs again? I need to know how your model respond to PrintStatus packet.

[nyarau]

There you go
logs-print.txt

[MultiMote]

Pushed some changes. Model detection should work at least (if other info packets are not have different format, let me know if there is some other errors in the browser logs after printer connection).
Also added error codes (you receiving "Printer Busy" for some reason).

It would be very useful if you can record packet dump of successful print with the official app. Method may vary between ROMs, but generally it is:

• Turn on development settings
• Enable Bluetooth HCI Snoop Log
• Maybe reboot device
• Turn bluetooth off and on
• Print any label with Niimbot app
• Run adb bugreport somefilename on PC
• You should find btsnoop_hci.log in the archive

[nyarau]

I tried the new version, still can't get device info:

new NiimbotBluetoothClient
index-m_AmWyhH.js:33 >> 03 55 55 c1 01 01 c1 aa aa (Connect)
index-m_AmWyhH.js:33 << 55 55 c2 01 01 c2 aa aa (In_Connect)
index-m_AmWyhH.js:33 >> 55 55 40 01 08 49 aa aa (PrinterInfo)
index-m_AmWyhH.js:33 << 55 55 48 01 02 4b aa aa (In_PrinterInfoPrinterCode)
index-m_AmWyhH.js:33 Unable to fetch printer info.
connect @ index-m_AmWyhH.js:33
await in connect
h @ index-m_AmWyhH.js:74
index-m_AmWyhH.js:33 Error: Array length must be 2
    at yl.u8ArrayLengthEquals (index-m_AmWyhH.js:33:12632)
    at Vi.bytesToI16 (index-m_AmWyhH.js:33:12076)
    at s.getPrinterModel (index-m_AmWyhH.js:33:24979)
    at async o.fetchPrinterInfo (index-m_AmWyhH.js:33:74568)
    at async o.connect (index-m_AmWyhH.js:33:68768)
    at async HTMLButtonElement.h (index-m_AmWyhH.js:74:3642)
connect @ index-m_AmWyhH.js:33
await in connect
h @ index-m_AmWyhH.js:74
index-m_AmWyhH.js:33 onConnect

Error message when printing is now:
Error: Print error (In_PrintError packet received, code is 9 - PRINTER_BUSY)

Official Android app refused to run because my device is rooted, unfortunately.
I may find a way to dump the packets in the future but don't count on me.

[MultiMote]

I tried the new version, still can't get device info:

Copy-paste mistake, sorry. Fixed.

Official Android app refused to run because my device is rooted, unfortunately.

If your device rooted with Magisk, you can add NIIMBOT to DenyList. My device is rooted too and I can run app without problems with Zygisk&DenyList.

I may find a way to dump the packets in the future but don't count on me.

No problem, I don't want to bother you.

[nyarau]

new NiimbotBluetoothClient
index-B2UsUqlZ.js:33 >> 03 55 55 c1 01 01 c1 aa aa (Connect)
index-B2UsUqlZ.js:33 << 55 55 c2 01 01 c2 aa aa (In_Connect)
index-B2UsUqlZ.js:33 >> 55 55 40 01 08 49 aa aa (PrinterInfo)
index-B2UsUqlZ.js:33 << 55 55 48 01 02 4b aa aa (In_PrinterInfoPrinterCode)
index-B2UsUqlZ.js:33 >> 55 55 40 01 0b 4a aa aa (PrinterInfo)
index-B2UsUqlZ.js:33 << 55 55 4b 05 c3 ******* aa aa (In_PrinterInfoSerialNumber)
index-B2UsUqlZ.js:33 >> 55 55 40 01 0d 4c aa aa (PrinterInfo)
index-B2UsUqlZ.js:33 Unable to fetch printer info.
connect @ index-B2UsUqlZ.js:33
index-B2UsUqlZ.js:33 Error: Timeout waiting response (waited for 4f, 47, 4d, 4a, 41, 4c, 43, 46, 48, 4b, 49, 42)
    at index-B2UsUqlZ.js:33:69554
connect @ index-B2UsUqlZ.js:33

index-B2UsUqlZ.js:33 onConnect

And print

...
>> 55 55 83 10 00 7b 00 00 05 02 00 2b 00 2c 00 2d 00 3e 00 3f c4 aa aa (PrintBitmapRowIndexed)
index-B2UsUqlZ.js:33 >> 55 55 84 03 00 7d 33 c9 aa aa (PrintEmptyRow)
index-B2UsUqlZ.js:33 >> 55 55 e3 01 01 e3 aa aa (PageEnd)
index-B2UsUqlZ.js:33 << 55 55 e4 01 01 e4 aa aa (In_PageEnd)
index-B2UsUqlZ.js:33 << 55 55 db 01 09 d3 aa aa (In_PrintError)
index-B2UsUqlZ.js:33 >> 55 55 a3 01 01 a3 aa aa (PrintStatus)
index-B2UsUqlZ.js:33 << 55 55 e0 02 00 01 e3 aa aa (In_PrinterPageIndex)
index-B2UsUqlZ.js:70 Error: Timeout waiting response (waited for b3, db)
    at index-B2UsUqlZ.js:33:69554
$ @ index-B2UsUqlZ.js:70
await in $
(anonymous) @ index-B2UsUqlZ.js:70
await in (anonymous)
hl @ index-B2UsUqlZ.js:33
(anonymous) @ index-B2UsUqlZ.js:33
vl @ index-B2UsUqlZ.js:33
Promise.then
uu @ index-B2UsUqlZ.js:33
pu @ index-B2UsUqlZ.js:33
(anonymous) @ index-B2UsUqlZ.js:33
P @ index-B2UsUqlZ.js:70
10index-B2UsUqlZ.js:33 >> 55 55 a3 01 01 a3 aa aa (PrintStatus)
index-B2UsUqlZ.js:33 >> 55 55 f3 01 01 f3 aa aa (PrintEnd)
index-B2UsUqlZ.js:33 << 55 55 f4 01 01 f4 aa aa (In_PrintEnd)

[nyarau]

I managed to dump the packets from iOS app with the this method: https://novelbits.io/debugging-sniffing-secure-ble-ios/ (no Apple developer account required, any iCloud account works)
I added annotations myself according to your code.

[MultiMote]

Nice! Can you send a text version please?

[nyarau]

Long packets in txt export are truncated
dump.txt