Add the HP MFP 137fnw to the HPLIP

Give the outputs from

  avahi-browse -rt _ipp._tcp
  avahi-browse -rt _uscan._tcp
  driverless

Run both commands. But they did return nothing.
The MFP has been turned on

root@hp:~# avahi-browse --all
+ br0 IPv6 HP Device Info local
+ br0 IPv6 HP Microsoft Windows Network local
+ br0 IPv4 HP Device Info local
+ br0 IPv4 HP Microsoft Windows Network local
+ lo IPv4 HP Device Info local
+ lo IPv4 HP Microsoft Windows Network local
+ br0 IPv4 zhimi-airpurifier-ma2_miio94023556 _miio._udp local

The 'HP MFP 137fnw' has been connected locally to the USB port.

> Run both commands. But they did return nothing.

That is not good.

Provide the output of

  lsusb
  lsusb -v | grep -A 3 bInterfaceClass.*7

root@hp:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 012: ID 03f0:f22a HP, Inc HP Laser MFP 137fnw
Bus 001 Device 003: ID 09da:3519 A4Tech Co., Ltd. A4Tech OpticalMouse
Bus 001 Device 002: ID 0951:16d2 Kingston Technology HX-KB4BL1-US [HYPERX Alloy FPS Pro]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

root@hp:~# lsusb -v | grep -A 3 bInterfaceClass.*7
      bInterfaceClass 7 Printer
      bInterfaceSubClass 1 Printer
      bInterfaceProtocol 4
      iInterface 0
--
      bInterfaceClass 7 Printer
      bInterfaceSubClass 1 Printer
      bInterfaceProtocol 2 Bidirectional
      iInterface 0
--
      bInterfaceClass 7 Printer
      bInterfaceSubClass 1 Printer
      bInterfaceProtocol 4
      iInterface 0
--
      bInterfaceClass 7 Printer
      bInterfaceSubClass 1 Printer
      bInterfaceProtocol 4
      iInterface 0

> bInterfaceClass 7 Printer
> bInterfaceSubClass 1 Printer
> bInterfaceProtocol 4
> iInterface 0

These stanzas indicate that the 137fnw can use IPP-over-USB. Therefore,
'avahi-browse -rt _ipp._tcp' should give an output. When the printer is plugged
nto USB the ipp-usb daemon should become active. What is given by

  systemctl status ipp-usb ?

root@hp:~# systemctl status ipp-usb
● ipp-usb.service - Daemon for IPP over USB printer support
     Loaded: loaded (/lib/systemd/system/ipp-usb.service; static)
     Active: active (running) since Thu 2023-04-20 20:31:06 +06; 19h ago
       Docs: man:ipp-usb(8)
   Main PID: 152886 (ipp-usb)
      Tasks: 16 (limit: 76365)
     Memory: 8.5M
        CPU: 2min 28.213s
     CGroup: /system.slice/ipp-usb.service
             └─152886 /sbin/ipp-usb udev

Apr 20 20:31:06 hp.home.local systemd[1]: Started Daemon for IPP over USB printer support.
root@hp:~# avahi-browse -rt _ipp._tcp (launched again but return nothing)
root@hp:~#

> Active: active (running) since Thu 2023-04-20 20:31:06 +06; 19h ago

ipp-usb is operating.

Set up this queue:

  lpadmin -p 137fnw -v ipp://127.0.0.1:60000/ipp/print -E -m everywhere

Test with

  lp -d 137fnw /etc/nsswitch.conf

root@hp:~# lpadmin -p 137fnw -v ipp://127.0.0.1:60000/ipp/print -E -m everywhere

Tried to print the /etc/nsswitch.conf but this attempt was unsuccessful.
root@hp:~# lp -d 137fnw /etc/nsswitch.conf
request id is 137fnw-127 (1 file(s))
root@hp:~#

Additionally, I have created a 'test.txt' text file with one word in it and tried to print it using 'lp -d 137fnw /tmp/test.txt' but unsuccessfully. It is still in the queue for the 137fnw. We can see it in '137fnw - Active jobs'.

The USB printer is definitely on localhost (127.0.0.1) at port 60000. The
resource ipp/print is a bit of a guess but most printers these days use it.
avahi-browse would confirm (or not). Consult an error_log.

  sudo cuosctl --debug-logging

'avahi-browse -a' shows

  + lo IPv4 HP Device Info local

What does this resolve to with

  avahi-browse -ar' ?

root@hp:~# cupsctl --debug-logging
root@hp:~# (returned nothing)

root@hp:~# avahi-browse -ar
+ vnet1 IPv6 HP Microsoft Windows Network local
+ br0 IPv6 HP Microsoft Windows Network local
+ br0 IPv4 HP Microsoft Windows Network local
+ lo IPv4 HP Microsoft Windows Network local
+ vnet1 IPv6 HP Device Info local
+ br0 IPv6 HP Device Info local
+ br0 IPv4 HP Device Info local
+ lo IPv4 HP Device Info local
= vnet1 IPv6 HP Device Info local
   hostname = [hp.local]
   address = [fe80::fc54:ff:fe75:9433]
   port = [0]
   txt = ["model=MacSamba"]
= vnet1 IPv6 HP Microsoft Windows Network local
   hostname = [hp.local]
   address = [fe80::fc54:ff:fe75:9433]
   port = [445]
   txt = []
= br0 IPv6 HP Device Info local
   hostname = [hp.local]
   address = [fe80::7cdf:41ff:fe25:732a]
   port = [0]
   txt = ["model=MacSamba"]
= br0 IPv6 HP Microsoft Windows Network local
   hostname = [hp.local]
   address = [fe80::7cdf:41ff:fe25:732a]
   port = [445]
   txt = []
= br0 IPv4 HP Device Info local
   hostname = [hp.local]
   address = [192.168.31.50]
   port = [0]
   txt = ["model=MacSamba"]
= br0 IPv4 HP Microsoft Windows Network local
   hostname = [hp.local]
   address = [192.168.31.50]
   port = [445]
   txt = []
= lo IPv4 HP Device Info local
   hostname = [hp.local]
   address = [127.0.0.1]
   port = [0]
   txt = ["model=MacSamba"]
= lo IPv4 HP Microsoft Windows Network local
   hostname = [hp.local]
   address = [127.0.0.1]
   port = [445]
   txt = []
+ br0 IPv4 zhimi-airpurifier-ma2_miio94023556 _miio._udp local
= br0 IPv4 zhimi-airpurifier-ma2_miio94023556 _miio._udp local
   hostname = [zhimi-airpurifier-ma2_miio94023556.local]
   address = [192.168.31.100]
   port = [54321]
   txt = ["mac=7c49eb852557" "epoch=1"

root@hp:~# netstat -lpntu | grep 127
tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 8192/qemu-system-x8
tcp 0 0 127.0.0.1:5939 0.0.0.0:* LISTEN 2428/teamviewerd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 12472/cupsd
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 820/systemd-resolve
tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN 1630/tor
tcp6 0 0 127.0.0.1:13579 :::* LISTEN 3605/java
udp 0 0 127.0.0.53:53 0.0.0.0:* 820/systemd-resolve
udp 0 0 127.0.0.1:896 0.0.0.0:* 2416/rpc.statd
root@hp:~#

> = lo IPv4 HP Device Info local
> hostname = [hp.local]
> address = [127.0.0.1]
> port = [0]
> txt = ["model=MacSamba"]

This is not your printer. I haven't any idea why it is not discovered and do
not know what MacSamba is.

The lpadmin command was successful. This means CUPS was able to query
the printer over IPP. The file /etc/cups/ppd/137fnw.ppd should exist.

root@hp:~# ll /etc/cups/ppd/137fnw.ppd
ls: cannot access '/etc/cups/ppd/137fnw.ppd': No such file or directory
root@hp:~#

Let me ask If there is a driver for HP Laser MFP 135 why we cannot add it (the 'HP Laser MFP 135') to HPLIP ?

Thanks brian_p, that solved my question.

> et me ask If there is a driver for HP Laser MFP 135 why we cannot add it
> (the 'HP Laser MFP 135') to HPLIP ?

My records have an avahi-browse entry (from a wireless connection) for this device:

  pdl=application/octet-stream,application/x-QPDL,image/urf,application/PCLm

These are the languages the HP Laser MFP 135 understands. application/x-QPDL
is used with Samsung's ULD, not with HPLIP. For HPLIP, one pdl that is understood
is application/vnd.hp-PC. That would have to be added to the printer's firmware
and, IMO, is unlikely to be done by HP. Neither of these pdl is a driverless pdl.