manuc66
commented
7 months ago Hi,
The reason it fails is that your printer is not supported because there is no WalkupScanToCompManifestURI or WalkupScanManifestURI in the DiscoveryTree. That's why you can also read Unknown device! (see https://github.com/manuc66/node-hp-scan-to/blob/043466417ed3e198c5e0d338e718d17c005a3054/src/readDeviceCapabilities.ts#L31)
These allow the application to register a computer as a target.
I don't know how the - Scan to Computer - feature works on this device. Without a complete record of the communication under Windows using the original hp software with the device, it's impossible to do the retro-engineering to make this device work in this project.
hydrocontica
Hello - I'm attempting to set this up as a container in Docker on Unraid (version 6.12.8), but as soon as I specify the printer IP as an environment variable (per the configuration instructions) it results in the container crashing and restarting rapidly until eventually the system kills it altogether. The container's log indicates that the issue is that the printer is an "unknown device", and with the container generating a 404 not found error after trying to initiate connection.
Device is a HP Color LaserJet MFP M283fdw, tested as working with scan to computer on a Windows PC (Windows 10), with firmware revision dated 2020-06-03. Note that I cannot update the firmware as HP removed scan to computer from this printer model with later revisions for some reason, however scan to computer does still work with the most recent version of HP software.
Here is my docker run (though no errors occur unless the IP address of the printer is specified, the container appears to start correctly otherwise but ofc is not detectable by the printer without that IP address being set):
And here are my logs (they repeat exactly 50 times once the container is started until the container is killed entirely):
I'm aware that using macvlan and specifying the printer's name is an alternative configuration method, but unfortunately macvlan was removed from recent versions of Unraid. My suspicion is that there is an incompatibility between Unraid's new Docker networking approach and node-hp-scan-to, but I'm not sure of the exact culprit.