search for: apcupskeld

...uot; ATTR{idVendor}=="051d", ATTR{idProduct}=="0004", MODE="664", GROUP="nut" ``` 3. I believe I commented these away? Are you suggesting I change something? 4. ``` erik at MinipcLG2:/usr/lib/udev/rules.d$ systemctl status nut-driver at apcupskelder.service ? nut-driver at apcupskelder.service - Network UPS Tools - device driver for NUT device 'apcupskelder' Loaded: loaded (/usr/lib/systemd/system/nut-driver at .service; enabled; preset: enabled) Drop-In: /etc/systemd/system/nut-driver at apcupskelder.service....

...ns bus, device, busport can depend on topology and enumeration of connected devices; it may be wise to comment them away. Later NUT versions already do not default to offering them in `nut-scanner` output, to minimize run-time surprises. 4) See if you already have a service instance `nut-driver at apcupskelder.service` defined and running, since NUT v2.8.0 https://github.com/networkupstools/nut/wiki/nut%E2%80%90driver%E2%80%90enumerator-(NDE) could have created it - but the older blogs/videos do not reflect this facility. The "terminating other driver" seems to be a clue in that direction. Ma...

...ch? Thanks in advance for anyone's help! Kind regards, Erik PS. I also created a GitHub issue ( https://github.com/networkupstools/nut/issues/2666). Maybe doing that AND mailing this, is not the correct procedure? In that case, I apologize. ``` erik at MinipcLG2:/$ sudo upsdrvctl shutdown apcupskelder Network UPS Tools - UPS driver controller 2.8.1 Network UPS Tools - Generic HID driver 0.52 (2.8.1) USB communication driver (libusb 1.0) 0.46 select with socket: Invalid argument Can't claim USB device [051d:0002]@0/0: Entity not found upsnotify: failed to notify about state 4: no notificati...