Seeking help with Not finding devices

[genem2]

Hello all. I hope this is the right place for this, rather than creating an issue.

This tool was working great until it was accidentally removed a few weeks back, and now I'm pulling my hair out, trying to figure out why I can't get it rerunning.

I'm running unRAID 7.0.0 and the resulting container start command is:

docker run
  -d
  --name='hp_scan_to'
  --net='host'
  --pids-limit 2048
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="ed800"
  -e HOST_CONTAINERNAME="hp_scan_to"
  -e 'IP'='192.168.0.45'
  -e 'RESOLUTION'='300'
  -e 'PATTERN'='yymmdd_hhMMss"-scan"'
  -e 'TZ'='America/Los_Angeles'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'LABEL'='Homeserver'
  -e 'NAME'='"HP ENVY 7640"'
  -e 'SUPPRESS_NO_CONFIG_WARNING'='false'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://homeassistant.genem.org/local/images/scanner.png'
  -v '/mnt/cache/HomeShare/':'/scan':'rw' 'docker.io/manuc66/node-hp-scan-to:master'

But this just terminates:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/10-adduser
cont-init: info: /etc/cont-init.d/10-adduser exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/node-config/node-config/wiki/Strict-Mode
error: too many arguments for 'listen'. Expected 0 arguments but got 2.
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

User uid:    99
User gid:    100

If I add:
Extra Parameters: --entrypoint /bin/sh
Post Arguments: -c "ln -s /bin/true /usr/bin/listen && node /app/index.js -D"

docker run
  -d
  --name='hp_scan_to'
  --net='host'
  --pids-limit 2048
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="ed800"
  -e HOST_CONTAINERNAME="hp_scan_to"
  -e 'IP'='192.168.0.45'
  -e 'RESOLUTION'='300'
  -e 'PATTERN'='yymmdd_hhMMss"-scan"'
  -e 'TZ'='America/Los_Angeles'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'LABEL'='Homeserver'
  -e 'NAME'='"HP ENVY 7640"'
  -e 'SUPPRESS_NO_CONFIG_WARNING'='false'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://homeassistant.genem.org/local/images/scanner.png'
  -v '/mnt/cache/HomeShare/':'/scan':'rw'
  --entrypoint /bin/sh 'docker.io/manuc66/node-hp-scan-to:master'
  -c "ln
  -s /bin/true /usr/bin/listen && node /app/index.js
  -D"

it runs, but isn't finding anything:

WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/node-config/node-config/wiki/Strict-Mode
Current commit ID: 4969a0a867d8fb962cb5dab54adab12b7fadbb93
Searching device...

From the container. I can ping the printer at that IP address. A packet capture is not suggesting any firewall blockage. Not sure where to proceed...

[genem2]

From #1073
manuc66 mentioned:

The first endpoint that is called is http://192.168.1.253/DevMgmt/DiscoveryTree.xml. This endpoint allows node-hp-scan-to to discover all the capabilities and routes of the device, enabling it to determine how to interact with it.

Wondering if that might give insight to my issue, I tried:
http://192.168.0.45/DevMgmt/DiscoveryTree.xml
and found these two entries that contained scan.

<ledm:SupportedIfc>
  <ledm:ManifestURI>/WalkupScanToComp/WalkupScanToCompManifest.xml</ledm:ManifestURI>
  <dd:ResourceType>ledm:hpLedmWalkupScanToCompManifest</dd:ResourceType>
  <dd:Revision>http://www.hp.com/schemas/imaging/con/ledm/manifest/2009/03/24</dd:Revision>
</ledm:SupportedIfc>
<ledm:SupportedIfc>
  <ledm:ManifestURI>/Scan/ScanJobManifest.xml</ledm:ManifestURI>
  <dd:ResourceType>ledm:hpLedmScanJobManifest</dd:ResourceType>
  <dd:Revision>http://www.hp.com/schemas/imaging/con/ledm/manifest/2009/03/24</dd:Revision>
</ledm:SupportedIfc>

I attached the local files, but the web-based manifest link is no longer on the hp site
Would that be a requirement?

WalkupScanToCompManifest.xml.txt
ledm_ManifestURI.xml.txt

[manuc66]

Hi @genem2,

I think your issue is the same as #1065

As you are using the IP of the device, you don't need to specify the name, could you try by removing that parameter ?

Best regards

[genem2]

Appreciate the suggestion. Unfortunately, no difference. Log file still shows Searching device…

docker run
  -d
  --name='hp_scan_to'
  --net='host'
  --pids-limit 2048
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="ed800"
  -e HOST_CONTAINERNAME="hp_scan_to"
  -e 'IP'='192.168.0.45'
  -e 'RESOLUTION'='300'
  -e 'PATTERN'='yymmdd_hhMMss"-scan"'
  -e 'TZ'='America/Los_Angeles'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'LABEL'='Homeserver'
  -e 'SUPPRESS_NO_CONFIG_WARNING'='false'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://homeassistant.genem.org/local/images/scanner.png'
  -v '/mnt/cache/HomeShare/':'/scan':'rw'
  --entrypoint /bin/sh 'docker.io/manuc66/node-hp-scan-to:master'
  -c "ln
  -s /bin/true /usr/bin/listen && node /app/index.js
  -D"
50395091cf020f9e4f55dcc1c60211b6cfa2aad2562cb61d2ab9cf651b32bd71

[manuc66]

I'm sorry but when the output indicates that it's searching for device

node-hp-scan-to/src/index.ts

Line 180 in aea0497

console.log("Searching device...");

it means that it looks the device by its name that is taken from the CLI's argument (or config file that you don't seem to look)

node-hp-scan-to/src/index.ts

Line 279 in aea0497

const name = options.name || getConfig("name");

Are you sure that you've looked at the correct logs ?

[manuc66]

The space argument should be fixed now

[genem2]

Perfect - your space argument fix got things running as they were before.

However, it appears the pdfs are always being deleted.
Given I'm on unRAID, I added -e 'CMDLINE'='-k --keep-files' hoping to prevent purging, but it's not working out

Results:

Scan event captured, saving scan #0
Waiting user input: 1/50
Selected shortcut: SavePDF
Scan will be converted to pdf, using /tmp/scan-to-pcHahAEB as temp scan output directory for individual pages
ScanPlexMode is : Simplex
Afd is : Empty
New job created: http://192.168.0.45:8080/Jobs/JobList/8
Ready to download page job page 1 at: /Scan/Jobs/8/Pages/1
Page downloaded to: /tmp/scan-to-pcHahAEB/250118_072318-scan.jpg
Job state: Completed, totalPages: 1:
Start listening for new ScanEvent
Scan of page(s) completed totalPages: 1:
The following page(s) have been rendered inside '/scan/250118_072313-scan.pdf': 
        - page   1 - 2550x3508
File /scan/250118_072313-scan.pdf has been removed from the filesystem
Running iteration: 2 - errorCount: 0
Host destinations fetched: HomeShare, Homeserver

[manuc66]

I will have a look at it this evening, my guess is that it have been introduced here: #1068 (comment)

[manuc66]

Should be fixed in v1.6.1

[genem2]

Sure is! Thank you. 🙏