Open denveronly opened 9 months ago
Hello, can you try stopping the NUT programs and starting the drivers from command line in probe mode, e.g. nutdrv_qx -a myups -DDDDDD -d 1
so they would report in more detail what they tried and how that failed?
In the screenshot, "Mega" protocol is mentioned. I assume it means a variant of Megatec Qnutdrv_qx
should be a good match.
There were some fixes merged recently for this driver, to help it handle devices this played loose with the spec (e.g. ending some messages with zero-bytes instead of zero characters in a sort of flag bit map entry). I am not sure if that was done for a specific subdriver (IIRC Ablerex) or for the whole ecosystem, however.
If you have a chance to build NUT from git sources - it may be possible to see if the fix takes effect and helps with your device.
More details at https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests - note you do not have to replace a packaged NUT just to test the driver (can do from build workspace).
Hello, can you try stopping the NUT programs and starting the drivers from command line in probe mode, e.g.
nutdrv_qx -a myups -DDDDDD -d 1
so they would report in more detail what they tried and how that failed?
im not sure how to start it in probe mode, the only idea i tried is
In the screenshot, "Mega" protocol is mentioned. I assume it means a variant of Megatec Q protocol family, so generally
nutdrv_qx
should be a good match.There were some fixes merged recently for this driver, to help it handle devices this played loose with the spec (e.g. ending some messages with zero-bytes instead of zero characters in a sort of flag bit map entry). I am not sure if that was done for a specific subdriver (IIRC Ablerex) or for the whole ecosystem, however.
If you have a chance to build NUT from git sources - it may be possible to see if the fix takes effect and helps with your device.
More details at https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests - note you do not have to replace a packaged NUT just to test the driver (can do from build workspace).
Maybe it is easier just to replace the driver file from /usr/lib/nut , the file nutdrv_qx from other version?
rm file and cp from other location, stupid idea ?
In Unix/Linux, you have to provide a path to programs (if not in a PATH
listed location), e.g. ./nutdrv_qx -a myups -DDDDDD -d 1
(assuming myups
is the device configuration section name in your ups.conf
).
To "rm
and cp
" you have to build that newer driver program first :) And if after testing from the build workspace it behaves better, the make install
would do a better job to copy the new files into your system (the wiki article ends with this optional replacement step).
In Unix/Linux, you have to provide a path to programs (if not in a
PATH
listed location), e.g../nutdrv_qx -a myups -DDDDDD -d 1
(assumingmyups
is the device configuration section name in yourups.conf
).To "
rm
andcp
" you have to build that newer driver program first :) And if after testing from the build workspace it behaves better, themake install
would do a better job to copy the new files into your system (the wiki article ends with this optional replacement step).
oh i get, still learning. sorry. I tried the probe mode, but the info is not so informative changed in ups.conf the name.
Hm, I was under impression you had NUT 2.8.x, must have mistaken with another issue of the day. Probably have to build a new one or find packaged.
Any fix for this? I have the same problem in Homeassistant.
Any news about this ? Also struggling with a similar UPS
"Similar" being "2E" branded, or with ID 0000:0001 indicating that the vendor did not even bother to get an ID?
It is ID 0000:0001 with a "Fry's Electronics" vendor. It also works with the UPSmart with the Mega (USB) option as per the original post. I have tried the nutdrv_qx driver with megatec and megatec/old protocol and pretty much every subdriver but it always fails to start with Device not supported!
(It prints it 2 times).
Howdy!
Ive been struggling a full day to hook a Chineese UPS to a NUT server. Tried it on homeassistant and Unraid instances, just to make sure there is no USB driver issues. So i have a brand "2E" RE650VA UPS, which goes to a server 2u Rack. It is pretty neat, but lacks of NUT support. Unraid Monitor gave me a setup like this to try.
All are failing to start, but the original program that came on a CD UPSmart works.
Ubuntu VM with a nut-scanner proposed nutdrv_actl_usb
lsusb -v give such an answer on connected device