betted troubleshooting with udevadm

[Xophe92]

I wanted to mention that if you add the -p flag in the command line you obtain a much more detailed vision on the events helping to adjust the rule accordingly

sudo udevadm monitor -p --subsystem-match=usb

gave me this, when I pluged my printer

UDEV [560190.524530] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2 (usb)
ACTION=add
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/001/038
DEVTYPE=usb_device
PRODUCT=1d50/614e/100
TYPE=2/0/0
BUSNUM=001
DEVNUM=038
SEQNUM=1848
USEC_INITIALIZED=560190519647
ID_VENDOR=Klipper
ID_VENDOR_ENC=Klipper
ID_VENDOR_ID=1d50
ID_MODEL=stm32f103xe
ID_MODEL_ENC=stm32f103xe
ID_MODEL_ID=614e
ID_REVISION=0100
ID_SERIAL=Klipper_stm32f103xe_33FFD4054242363223780357
ID_SERIAL_SHORT=33FFD4054242363223780357
ID_BUS=usb
ID_USB_INTERFACES=:020201:0a0000:
ID_VENDOR_FROM_DATABASE=OpenMoko, Inc.
DRIVER=usb
MAJOR=189
MINOR=37

[skorokithakis]

This is very helpful, can it be added to the docs?