NUT with Riello Sentinel Pro 2200 USB connection cant make it work

No i have not sorted it out with pfsense at all. Still have exactly same issue. It would be really nice if someone who is involved with UPS plugin to explain how to connect (if it is even possible) UPS devices with PRTK identifiers.
Sadly i had to sort out ancient HP thin client with winxp just to monitor UPS so i have any kind of its status. I have couple of them and this is really bad issue because original app is really really outdated and buggy.
Not even sure is it working with win10 without java. Dont take me on word for that.

So yeah, this looks as really consistent either issue or lack of documentation. If anyone who stumble on this know whats problem, please share.

Thank you in advance 2 years later :)

Unoptanio · Nov 8, 2023, 3:11 PM

@ha11oga11o
Most users use APC UPS and it seems to work with these

Unoptanio · Nov 8, 2023, 3:22 PM

@ha11oga11o

I also tried with different USB cables, even short ones, but it doesn't work

look here too

https://blog.victormendonca.com/2020/10/28/how-to-setup-ups-on-pfsense/t

Oct 31, 2023: NUT 2.8.1 released

🔒 Log in to view

ha11oga11o · Nov 8, 2023, 4:02 PM

I can confirm that APC works. I manage to sort those in no time. But Riello with PRTK does not work. maybe some additional driver commands needs to be in place. But there sno docs that i found which explain that.

dennypage · Nov 8, 2023, 7:05 PM

@Unoptanio You might look in the NUT package support thread. There are a lot of USB issues with NUT 2.8.0.

ha11oga11o · Nov 8, 2023, 7:48 PM

@dennypage

I doubt its actual USB problem. More like configuration issue or its not supported. I have this problem since:

2.5.0-RELEASE (amd64)
built on Tue Feb 16 08:56:29 EST 2021
FreeBSD 12.2-STABLE

nut sysutils 2.7.4_8

Two years i tried many things to make it work. I read so many threads, and just gave up. Today i got notification someone else have same problem, so i cherish hope it might be seen by right eyes to explain whats in stake.

As far i can understand original programs MUST have type in that famous PRTK code which is written on back of UPS on small sticker to actually recognize it. So, im kinda sure its same thing here, but have no idea how to do it, since GUI does not ask for it, except additional driver parameters which i dont know how to format.

Its stated here:

What is PRTK code

""It is a code inherent to the UPS communication protocol and can be found either on the plate on the back of the UPS itself or, for large UPS, inside the door of the UPS.

This code is essential to identify and associate the UPS or ATS/STS with our software, such as the PowerShield3, as well as connectivity devices like Netman 204.

Only with the correct PRTK code is communication between the two elements possible. ""

Cheers!

dennypage · Nov 8, 2023, 8:11 PM

@ha11oga11o Ah yes. My bad. I did a little quick reading....

It looks like Riello purposefully does not implement the USB HID Power device protocol. It appears that they want to force users to use Riello software to manage the units. Kinda sad.

Unoptanio · Nov 9, 2023, 9:50 AM

@dennypage
@ha11oga11o

On the official NUT website they write that the RIELLOs work with the USB and SERIAL drivers

To write this I hope they have tested them

Is there anyone on the Nut development team who can take this to heart this problem with Riello UPS?

I am Italian and in Italy Riello UPSs are very popular

https://networkupstools.org/stable-hcl.html

🔒 Log in to view

Can we try writing here? to see if they help us solve the problem

https://github.com/networkupstools/nut/issues

I have open this ticket:
https://github.com/networkupstools/nut/issues/2159t

Unoptanio · Nov 9, 2023, 2:42 PM

@ha11oga11o
@dennypage
@ha11oga11o

Response from team Nut

Looking at screenshot, maybe the problem is with driver name: in NUT there are riello_ser and riello_usb respectively for different media, not one riello. 
I doubt that pfSense undertook an effort to merge them into one, although maybe they "hide" it behind selection of "UPS Type" (Local USB)?
Even that would not be easy, as different drivers follow different naming patterns (and some are dual-capability). 
So the first thing to check would be typing riello_usb there.

Looking at source history, initial driver codebase was in fact contributed by a person from Riello, so at least as of ~2014 it should have "officially" supported the contemporary protocol.
I do not know if their newer devices follow some unrelated protocol or are still compatible, though.

You might try to bump driver debug verbosity, if you can see its logs - maybe that would expose how it tries to find the device and what exactly fails. 
With NUT v2.8.0+ it may suffice to add a debug_min = 6 to the "Extra arguments" while you are troubleshooting.

Can someone from the pfsense team help us? Thank you

Unoptanio · Nov 9, 2023, 3:23 PM

https://docs.netgate.com/pfsense/en/latest/packages/nut.html#troubleshooting

🔒 Log in to view

Unoptanio · Nov 9, 2023, 3:54 PM

🔒 Log in to view

dennypage · Nov 9, 2023, 3:55 PM

@Unoptanio "failed to detach kernel driver" indicates that there is not a USB quirk registered to prevent the kernel from attaching a default driver. In other words, the kernel does not know that it is a UPS.

You will either need to determine and register the correct quirk, or run as root. See this thread for a recent discussion about developing a quirk.

Unoptanio · Nov 9, 2023, 4:13 PM

Problem solved but there is still work to do for the pfsense team.

follow the solution on:

https://github.com/networkupstools/nut/issues/2159

https://github.com/networkupstools/nut/wiki/NUT-on-pfSense

🔒 Log in to view

Wow
🔒 Log in to view

dennypage · Nov 9, 2023, 4:35 PM

@Unoptanio said in NUT with Riello Sentinel Pro 2200 USB connection cant make it work:

Problem solved but there is still work to do for the pfsense team.

follow the solution on:

https://github.com/networkupstools/nut/issues/2159

This is the quirk issue I mentioned in the prior post. It is actually not pfSense, but upstream FreeBSD that manages the default quirks.

You will have to develop and test a quirk. It cannot be done without possession of the physical UPS. After you have developed the quirk, we can file a ticket with upstream to request that it added to FreeBSD.

Unoptanio · Nov 9, 2023, 5:49 PM

@dennypage

you could involve Riello technical support because I believe the problem is with all Riello UPS models.
Once the quirk has been developed on a specific Riello UPS model, does it then work with all Riello models? or should a quirk be developed for each model?

dennypage · Nov 9, 2023, 7:09 PM

@Unoptanio Depends upon the manufacturer. For most, I think it is for a series of UPSs. APC for instance has only had 3 of them.

See this post for detailed information.

ha11oga11o · Nov 10, 2023, 9:35 AM

Hello all,

i can confirm that like this works on mine side too with rather old SEP2200. All it needed is extra argument user = root.

So, NUT package needs some tweaking not to work at root privileges i guess?

At least we manage to connect UPS to device. many thnx! Finally some progress on this subject.

Cheers!