Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

nut-scanner generated conf can cause device-name collisions #2243

Closed
aquette opened this issue Dec 22, 2023 · 1 comment · Fixed by #2247
Closed

nut-scanner generated conf can cause device-name collisions #2243

aquette opened this issue Dec 22, 2023 · 1 comment · Fixed by #2247
Labels
nut-scanner SmartNUT Multi-backend extension of NUT for smart home integrations

Comments

@aquette
Copy link
Member

aquette commented Dec 22, 2023 •
edited
Loading

When nut-scanner is called separately, to scan different busses, it will generate similar names for each of these:

  • USB scan

[nutdev1]
...

  • NUT scan

[nutdev1]
...

  • ...

As a result, one can't just redirect nut-scanner outputs directly to ups.conf, without a 'sed' hack workaround.

Solution: simply refine the device names, like "nutdev-[method][id]".
Examples: nutdev-usb1, nutdev-usb2, nutdev-nut1, nutdev-snmp1, ...
@jimklimov jimklimov added nut-scanner SmartNUT Multi-backend extension of NUT for smart home integrations labels Jan 20, 2024
@jimklimov
Copy link
Member

Fixed by #2247

This was referenced Feb 19, 2024
Merged
Merged
@github-project-automation github-project-automation bot moved this to Done in SmartNUT Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
nut-scanner SmartNUT Multi-backend extension of NUT for smart home integrations
Projects
SmartNUT
Status: Done
Milestone
No milestone
2 participants
@aquette @jimklimov