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

Unoptanio

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

ha11oga11o

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

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

ha11oga11o

@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

@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

@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

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

@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

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

Unoptanio

dennypage

@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

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

Wow

dennypage

@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

@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

@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

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!

ha11oga11o

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

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!

yeah, that was short live; I got initial data, an next refresh interval it says UPS need attention.

Nov 10 10:39:58 	upsmon 	20183 	Communications with UPS RielloSEP2200 established
Nov 10 10:39:58 	upsd 	33371 	User local-monitor@127.0.0.1 logged into UPS [RielloSEP2200]
Nov 10 10:39:55 	upsd 	33371 	Connected to UPS [RielloSEP2200]: riello_usb-RielloSEP2200
Nov 10 10:39:55 	riello_usb 	33500 	Startup successful
Nov 10 10:39:54 	upsd 	33371 	Startup successful
Nov 10 10:39:54 	upsd 	32400 	Can't connect to UPS [RielloSEP2200] (riello_usb-RielloSEP2200): No such file or directory
Nov 10 10:39:54 	upsd 	32400 	listening on 127.0.0.1 port 3493
Nov 10 10:39:54 	upsd 	32400 	listening on ::1 port 3493
Nov 10 10:39:53 	upsmon 	20183 	Communications with UPS RielloSEP2200 lost
Nov 10 10:39:53 	upsmon 	20183 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Nov 10 10:39:53 	upsmon 	19414 	Startup successful
Nov 10 10:39:53 	php-fpm 	50287 	/nut_settings.php: Starting service nut
Nov 10 10:39:53 	riello_usb 	58720 	Signal 15: exiting
Nov 10 10:39:53 	upsd 	28635 	Signal 15: exiting
Nov 10 10:39:53 	upsd 	28635 	mainloop: Interrupted system call
Nov 10 10:39:53 	upsd 	28635 	User local-monitor@127.0.0.1 logged out from UPS [RielloSEP2200]
Nov 10 10:39:53 	upsmon 	27914 	Signal 15: exiting
Nov 10 10:39:53 	php-fpm 	50287 	/nut_settings.php: Stopping service nut
Nov 10 10:39:53 	check_reload_status 	484 	Syncing firewall
Nov 10 10:39:53 	php-fpm 	50287 	/nut_settings.php: Configuration Change: admin@192.168.1.210 (Local Database): Updated UPS settings
Nov 10 10:37:41 	upsmon 	27914 	Communications with UPS RielloSEP2200 established
Nov 10 10:37:40 	upsd 	28635 	Connected to UPS [RielloSEP2200]: riello_usb-RielloSEP2200
Nov 10 10:37:38 	riello_usb 	58720 	Startup successful
Nov 10 10:37:36 	upsmon 	27914 	UPS RielloSEP2200 is unavailable
Nov 10 10:37:36 	upsmon 	27914 	Poll UPS [RielloSEP2200] failed - Driver not connected
Nov 10 10:37:36 	upsd 	28635 	User local-monitor@127.0.0.1 logged into UPS [RielloSEP2200]
Nov 10 10:37:32 	upsd 	28635 	Startup successful
Nov 10 10:37:32 	upsd 	28603 	Can't connect to UPS [RielloSEP2200] (riello_usb-RielloSEP2200): Connection refused
Nov 10 10:37:32 	upsd 	28603 	listening on 127.0.0.1 port 3493
Nov 10 10:37:32 	upsd 	28603 	listening on ::1 port 3493
Nov 10 10:37:30 	upsmon 	27914 	Communications with UPS RielloSEP2200 lost
Nov 10 10:37:30 	upsmon 	27914 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Nov 10 10:37:30 	upsmon 	27623 	Startup successful
Nov 10 10:37:30 	php-fpm 	50287 	/nut_settings.php: Starting service nut
Nov 10 10:37:30 	upsd 	13922 	Signal 15: exiting
Nov 10 10:37:30 	upsd 	13922 	mainloop: Interrupted system call
Nov 10 10:37:30 	upsd 	13922 	User local-monitor@127.0.0.1 logged out from UPS [RielloSEP2200]
Nov 10 10:37:30 	upsmon 	13197 	Signal 15: exiting
Nov 10 10:37:30 	php-fpm 	50287 	/nut_settings.php: Stopping service nut
Nov 10 10:37:30 	check_reload_status 	484 	Syncing firewall
Nov 10 10:37:30 	php-fpm 	50287 	/nut_settings.php: Configuration Change: admin@192.168.1.210 (Local Database): Updated UPS settings
Nov 10 10:37:01 	check_reload_status 	484 	Syncing firewall
Nov 10 10:37:01 	php-fpm 	97711 	/index.php: Configuration Change: admin@192.168.1.210 (Local Database): Widget configuration has been changed. (User admin)
Nov 10 10:37:00 	sshguard 	28889 	Now monitoring attacks.
Nov 10 10:37:00 	sshguard 	91620 	Exiting on signal.
Nov 10 10:36:48 	check_reload_status 	484 	Syncing firewall
Nov 10 10:36:48 	php-fpm 	83476 	/index.php: Configuration Change: admin@192.168.1.210 (Local Database): Widget configuration has been changed. (User admin)
Nov 10 10:32:58 	upsmon 	13197 	Communications with UPS RielloSEP2200 established
Nov 10 10:32:58 	upsd 	13922 	User local-monitor@127.0.0.1 logged into UPS [RielloSEP2200]
Nov 10 10:32:56 	upsd 	13922 	Connected to UPS [RielloSEP2200]: riello_usb-RielloSEP2200
Nov 10 10:32:56 	riello_usb 	13928 	Startup successful
Nov 10 10:32:54 	upsd 	13922 	Startup successful
Nov 10 10:32:54 	upsd 	13777 	Can't connect to UPS [RielloSEP2200] (riello_usb-RielloSEP2200): No such file or directory
Nov 10 10:32:54 	upsd 	13777 	listening on 127.0.0.1 port 3493
Nov 10 10:32:54 	kernel 		uhid0: detached
Nov 10 10:32:54 	kernel 		uhid0: at uhub3, port 1, addr 3 (disconnected)
Nov 10 10:32:54 	upsd 	13777 	listening on ::1 port 3493
Nov 10 10:32:53 	upsmon 	13197 	Communications with UPS RielloSEP2200 lost
Nov 10 10:32:53 	upsmon 	13197 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Nov 10 10:32:53 	upsmon 	12733 	Startup successful
Nov 10 10:32:53 	php-fpm 	86594 	/nut_settings.php: Starting service nut
Nov 10 10:32:53 	check_reload_status 	484 	Syncing firewall

It looks, for me, did it once and stopped. This log is since NUT is actually started. And its filling it constantly. But it looks that reading data because i see load changes.

UPS Status.png

I have multiple USB units and all of them acting totally same.

Anyone have any thoughts about this?

It looks it works, but that error bugs me. Is it conflicting maybe, dropping connection,... ?

Thanks in advance.

ha11oga11o

This is what im getting with debug mode 6:

Nov 10 10:54:00 	sshguard 	35724 	Now monitoring attacks.
Nov 10 10:54:00 	sshguard 	19247 	Exiting on signal.
Nov 10 10:51:29 	upsmon 	18266 	Communications with UPS RielloSEP2200 established
Nov 10 10:51:29 	upsd 	21661 	User local-monitor@127.0.0.1 logged into UPS [RielloSEP2200]
Nov 10 10:51:27 	upsd 	21661 	Connected to UPS [RielloSEP2200]: riello_usb-RielloSEP2200
Nov 10 10:51:27 	riello_usb 	27207 	Startup successful
Nov 10 10:51:25 	upsd 	21661 	Startup successful
Nov 10 10:51:25 	upsd 	21547 	Can't connect to UPS [RielloSEP2200] (riello_usb-RielloSEP2200): No such file or directory
Nov 10 10:51:25 	upsd 	21547 	listening on 127.0.0.1 port 3493
Nov 10 10:51:25 	upsd 	21547 	listening on ::1 port 3493
Nov 10 10:51:24 	upsmon 	18266 	Communications with UPS RielloSEP2200 lost
Nov 10 10:51:24 	upsmon 	18266 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Nov 10 10:51:24 	upsmon 	17701 	Startup successful
Nov 10 10:51:24 	php-fpm 	50287 	/nut_settings.php: Starting service nut
Nov 10 10:51:24 	riello_usb 	33500 	Signal 15: exiting
Nov 10 10:51:24 	upsd 	33371 	Signal 15: exiting
Nov 10 10:51:24 	upsd 	33371 	mainloop: Interrupted system call
Nov 10 10:51:24 	upsd 	33371 	User local-monitor@127.0.0.1 logged out from UPS [RielloSEP2200]
Nov 10 10:51:24 	upsmon 	20183 	Signal 15: exiting
Nov 10 10:51:24 	php-fpm 	50287 	/nut_settings.php: Stopping service nut
Nov 10 10:51:24 	check_reload_status 	484 	Syncing firewall

ha11oga11o

Sorry guys for spamming subject, but im trying to troubleshoot issue. I noticed that driver sees my ups in

Summary status: On line, Bypass, Charging

Is it possible that driver sees it as some sort of error because its in bypass mode and notifies about it?

And its not spamming disconnect in log anymore. But notice stays. Refreshing fine too. Actually it works, but notice is there and i dont dare to turn on mail notification in case of spamming error.

If more data is needed i will provide.

Thanks

Unoptanio

@ha11oga11o

hi,

i have generated a Quirk for Riello VST1100

https://forum.netgate.com/topic/183961/nut-package-2-8-1-and-above/15?_=1699613439488

I also own UPS Riello Sentinel Pro 2200 and Riello Sentinel Dual SDU 6Kw.

As soon as I have time I'll check if the quirk also applies to this other UPS or if it has a different one

Unoptanio

@Unoptanio

test in progress

I disconnected the USB cable from the Riello VST 1100 UPS and connected it to the USB port of the Riello Sentinel Pro 2200. On pfsense everything works in the UPS panel

Quirk for Riello VST1100 also works on Riello Sentinel Pro 2200

What parameter configuration do you recommend setting in the other text boxes?