Regardless of IP defined in env it is searching for scanners
Regardless of IP defined in env it is searching for scanners using Bonjour.
This doesn't work, so the container restarts.
Originally posted by @domse in https://github.com/manuc66/node-hp-scan-to/issues/1464#issuecomment-3577047606
@manuc66 I'm using v1.9.6 without Docker but when I pass the IP address with the --address flag, the app still gets stuck on the Searching device... step and doesn't detect the ADF load in adf-autoscan mode.
@gy-mate I tried to reproduce but didn't managed, I'm getting this on my side:
$ npx [email protected] --address 192.168.1.53
Current commit ID: 1c4ef6f4f400c8ea501eaded52e9758e1d2c3d69
Using device ip: 192.168.1.53
Target folder: /tmp/scan-to-pcyu3SSo
Temp folder: /tmp/scan-to-pcW9k8zE
Running iteration: 1 - errorCount: 0
Hmm—thanks for checking! Here are the detailed reproduction steps:
- Install node
v25.2.1on macOS26.1 - Install pnpm
v10.12.4 - Install node-hp-scan-to
v1.9.6:
pnpm install -g node-hp-scan-to
- Run the app:
node-hp-scan-to adf-autoscan --address 192.168.████ --width 2450 --directory ~/Downloads -D
- It gets stuck here:
WARNING: No configurations found in configuration directory:/Users/████/config
WARNING: To disable this warning set SUPPRESS_NO_CONFIG_WARNING in the environment.
Running with Git commit ID: 6b48b6270c32458597c71ef7bb12b99f29be155f
Searching device...
.
Device: HP DeskJet Ink Advantage 3775 All-in-One
@gy-mate Seems to be an issue with npm publish (not yet fully solved), can you test the version 1.9.8 ?
It works now, thank you very much!! :)