Dymo Printmanager PnP

[X-Seti]

I have tried to run Labelle on Armbian arm64.
$uname -a
Linux purplepi 6.1.99-vendor-rk35xx #1 SMP Wed Mar 19 11:16:36 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux - Plasma 5.27.12 (Wayland - Xorg bridge)

OS: Armbian (25.2.3) aarch64
Host: Orange Pi 5 Plus
Kernel: 6.1.99-vendor-rk35xx
DE: Plasma 5.27.12 (Wayland) WM: kwin_wayland - Emerald)
WM Theme: Purple-Red-Shift-Fruit-Blur-Dark
Theme: [Plasma], Breeze [GTK3]
Icons: [Plasma], breeze-dark [GTK3]
Terminal: konsole
CPU: Cortex-A55 Cortex-A76 (8) @ 1.900GHz
GPU: Mali-G610 (Panfrost)
Memory: 6949MiB / 31778MiB

---

Installed package labelle 1.4.0, installed using Python 3.12.3.

I installed with pipx, added the rules to udev -> 91-labelle-1001.rules

Labelle can't see the printer?

$labelle "Hello world"
Error: No supported devices found

So is there something else missing from arm64 distro?

[maresb]

Do you mean the LabelManager?

If so, are you sure the device is powered on?

Do you see anything like the following in the output of lsusb?

Bus 001 Device 009: ID 0922:1001 Dymo-CoStar Corp. LabelManager PnP

[X-Seti]

lsusb
Bus 001 Device 011: ID 0922:1001 Dymo-CoStar Corp. LabelManager PnP
dmesg
[106831.414028] usb 1-1.4.3: new full-speed USB device number 11 using xhci-hcd
[106831.530091] usb 1-1.4.3: New USB device found, idVendor=0922, idProduct=1001, bcdDevice= 1.00
[106831.530948] usb 1-1.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[106831.531640] usb 1-1.4.3: Product: DYMO LabelManager PnP
[106831.532135] usb 1-1.4.3: Manufacturer: Dymo
[106831.532538] usb 1-1.4.3: SerialNumber: 05234404092020
[106831.613087] hid-generic 0003:0922:1001.0021: hiddev98,hidraw4: USB HID v1.11 Device [Dymo DYMO LabelManager PnP] on usb-xhci-hcd.12.auto-1.4.3/input0

[maresb]

Thanks a lot for the report and for the additional info. This is surprising since it's definitely visible with lsusb. Maybe something is messed up with the pyusb / libusb communication.

To get to the bottom of things, could you please let me know what you get with the following procedure?

First figure out the Python executable. Run cat $(which labelle), and look at the first line. Ignoring the #! prefix, this is the executable you need to run.

Run the Python executable and enter the following commands:

import usb

print(list(usb.core.find(find_all=True)))

I expect you to see a list of devices of the form [<DEVICE ID 1d6b:0003 on Bus 004 Address 001>, ... corresponding to the devices found by lsusb.

In particular, I expect one of the devices to have ID 0922:1001 corresponding to your LabelManager PnP.

To reproduce the code path taken by Labelle, you can run the following commands:

from labelle.lib.devices.usb_device import UsbDevice

print(UsbDevice.supported_devices())

An output of set() indicates the empty set, i.e. no devices found, so given the No supported devices found error message you're seeing, that's probably what you'll get.

The corresponding source code is here.

I'm not sure what's likely wrong, but I'd start by checking which libusb version is installed. I think you can check with a command similar to apt list --installed | grep libusb.

[X-Seti]

Lets start by;

import usb
print(list(usb.core.find(find_all=True)))
bash: syntax error near unexpected token `list'

apt list --installed | grep libusb.

libhidapi-libusb0/noble,now 0.14.0-1build1 arm64 [installed]
librust-libusb1-sys-dev/noble,now 0.6.4-1 arm64 [installed]
libusb-0.1-4/noble,now 2:0.1.12-35build1 arm64 [installed]
libusb-1.0-0-dev/noble,now 2:1.0.27-1 arm64 [installed]
libusb-1.0-0/noble,now 2:1.0.27-1 arm64 [installed]
libusb-1.0-doc/noble,now 2:1.0.27-1 all [installed]
libusb-dev/noble,now 2:0.1.12-35build1 arm64 [installed]
libusb-java-doc/noble,now 0.8+ztex20090101-9ubuntu1 all [installed]
libusb-java-lib/noble,now 0.8+ztex20090101-9ubuntu1 arm64 [installed]
libusb-java/noble,now 0.8+ztex20090101-9ubuntu1 all [installed]
libusb-libusb-perl/noble,now 0.09-2build6 arm64 [installed]
libusb-ocaml-dev/noble,now 1.3.1-5build2 arm64 [installed]
libusb-ocaml/noble,now 1.3.1-5build2 arm64 [installed]
libusb3380-0t64/noble,now 0.0.1+git20190125.c83d1e9-2.1build1 arm64 [installed]
libusb3380-dev/noble,now 0.0.1+git20190125.c83d1e9-2.1build1 arm64 [installed]
libusbauth-configparser-dev/noble,now 1.0.5-2 arm64 [installed]
libusbauth-configparser1/noble,now 1.0.5-2 arm64 [installed]
libusbguard-dev/noble,now 1.1.2+ds-6build2 arm64 [installed]
libusbguard1/noble,now 1.1.2+ds-6build2 arm64 [installed]
libusbgx-dev/noble,now 0.2.0-3.1build1 arm64 [installed]
libusbgx-doc/noble,now 0.2.0-3.1build1 all [installed]
libusbgx2t64/noble,now 0.2.0-3.1build1 arm64 [installed]
libusbmuxd-dev/noble,now 2.0.2-4build3 arm64 [installed]
libusbmuxd-tools/noble,now 2.0.2-4build3 arm64 [installed]
libusbmuxd6/noble,now 2.0.2-4build3 arm64 [installed]
libusbredirhost-dev/noble,now 0.13.0-2.1build1 arm64 [installed]
libusbredirhost1t64/noble,now 0.13.0-2.1build1 arm64 [installed]
libusbredirparser-dev/noble,now 0.13.0-2.1build1 arm64 [installed]
libusbredirparser1t64/noble,now 0.13.0-2.1build1 arm64 [installed]
python3-libusb1/noble,now 2.0.1+ds-1 all [installed]

now here is the strange thing, I installed labelle using pip instead of pipx, and it now works.

[X-Seti]

Thank you for your help. :) Much appreciated.

[maresb]

You're welcome. For the Python commands, it's incorrect to enter them in Bash, and that's why you're getting the syntax error. Instead, you need to enter them in Python after starting the Python executable. The Python executable must be determined following the instructions above based on the output of cat $(which labelle)