Hi @aric , thanks for sharing your enthusiasm. Welcome to SavaPage!
Proxy Printers are picked up from CUPS. Note that printers that advertise themselves via DNS-SD / Bonjour / Zeroconf (like your HP printers) are not automatically part of CUPS. You can easily check: printer devices that show up with the lpinfo -v command do not show up as printer with the lpstat -v command.
Add your DNS-SD printers in CUPS by selecting them there from the list of “Discovered Network Printers”. Make sure to select a Model that uses CUPS filtering and is compatible with your printer. Do not select an IPP Everywhere variant as Model, as this will give you an unusable “Local Raw Printer” throughput without filtering and print job options, which is unusable for SavaPage.
After you add/delete/modify CUPS printers you need to sync them with SavaPage: simply push the Synchronize button at the top of the Proxy Printers list of the Admin Web App.
Now that your CUPS printers are visible in SavaPage as Proxy Printer, you must first configure their Media Sources and Costs before they can be selected for print jobs.
There is another issue you need to be aware of. SavaPage is standardized on IANA Registered IPP Attributes and uses the CUPS IPP interface to retrieve printer capabilities. Since vendor specific PPD option keywords are generally not mapped to IPP attributes by CUPS, make sure that each vendor specific PPD option is mapped to its IPP counterpart. You can read all about this in the User Manual PPD Extensions Appendix. Please consult and reply to this post if you have any questions about PPDE files.
Indeed, placing your DNS-SD printers in a VLAN, which only the SavaPage server can access, prevents these printers from advertising themselves on user devices. This forces all users to use DNS-SD printers only from the SavaPage User Web app.