Riello IDG400 wrong values & not powering off #530

latimeria68 · 2018-02-25T17:06:13Z

Hello,
I just changed my old UPS with a new Riello IDG400:
1: it shows battery charge 255% - battery.runtime 3932100 - Runtime (H:M:S): 1092:15:00
is this an hardware problem or something on Nut side?
2: I use a raspberry as nut server to shutdown all lan clients after 180 seconds without main power; the old ups was also powered off after FINALDELAY 5 seconds while the Riello keeps staying on battery; is this something related to the first problem?
Thanks

jimklimov · 2018-02-25T22:17:58Z

Is this model on HCL? If yes, might it be that the vendor changed specs/protocol keeping same model name?

Beside a possible issue with this piece of hardware, this might be a NUT problem at least in way of not having the driver support for this model/update of the device. Or a vendor's one, requiring new ways to communicate where old ways don't suffice. Rolling back to the NUT problem. Maybe some other NUT driver or sub-driver already supports the needed protocol?

As for UPS poweroff - this as well may be a HW issue (e.g. not everyone has such feature at all), or likely that your current driver can't tell the UPS what it wants in a way that both sides understand.

latimeria68 · 2018-02-25T22:56:37Z

Yes IDG 400 is listed in HCL but really do not know what to say about the rest. Maybe calling the Cypress subdriver and Mustek protocol

clepple · 2018-02-26T14:03:19Z

From http://lists.alioth.debian.org/pipermail/nut-upsdev/2018-February/007373.html :

this type of UPS doesn't support realtime autonomy calculation, instead a fixed countdown must be used.

Note that we have a pending update to the HCL (5 star -> 4 star) because the IDG400 was not in the protocol documents. http://new.networkupstools.org/stable-hcl.html?manufacturer=Riello

latimeria68 · 2018-02-26T17:43:23Z

well, apparently replacing my old UPS with this one was not a good choice. Even if I won't care about realtime autonomy calculation (and this is what I do as I set the nut server to shutdown everything after 180 seconds on battery) I can't believe that a recent brand ups won't respect the power off and re-start when mains back.
Thanks a lot for your comments and great work

clepple · 2018-03-01T13:58:17Z

I can't believe that a recent brand ups won't respect the power off and re-start when mains back.

You may want to check out the reply (and patch) on the nut-upsdev thread:

- small changes in riello_usb.c and riello_ser that solved problem with UPS that not support realtime autonomy calculation (and also internal temperature); - the second problem I think is related to the first because the shutdown command that I sent to UPS by NUT monitor works without problems;

http://lists.alioth.debian.org/pipermail/nut-upsdev/2018-February/007374.html

latimeria68 · 2018-03-01T17:44:12Z

yes.....an help to apply the patch and test it please?

clepple · 2018-03-02T03:40:21Z

sure - OS details please?

latimeria68 · 2018-03-02T06:39:43Z

Raspbian Stretch so basically Debian

clepple · 2018-03-05T03:35:53Z

make sure you have "deb-src" lines to match the "deb" lines in /etc/apt/sources
run "sudo apt-get update" if you had to change anything
run "sudo apt-get build-dep nut"
3.5) optional: remove "asciidoc" (or install the build-deps manually, and omit asciidoc) to save a bit of build time
run "sudo apt-get -y install git" if you do not already have Git installed
clone the source to your working directory: "git clone https://github.com/networkupstools/nut.git"
5.5) "cd nut", apply the patch downloaded from the URL above: "zcat path/to/attachment.bin | patch -p0"
run this mega-command:

./configure --includedir=/usr/include --mandir=/usr/share/man \
--infodir=/usr/share/info --sysconfdir=/etc/nut --localstatedir=/var \
--libexecdir=/usr/lib/nut --srcdir=. --enable-maintainer-mode \
--disable-silent-rules --libdir=/usr/lib/arm-linux-gnueabihf \
--with-ssl --with-nss --with-cgi --with-dev --enable-static \
--with-statepath=/var/run/nut --with-altpidpath=/var/run/nut \
--with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut \
--with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut \
--datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/arm-linux-gnueabihf/pkgconfig \
--with-user=nut --with-group=nut --with-udev-dir=/lib/udev \
--with-systemdsystemunitdir=/lib/systemd/system

run "make"

Edit, 2019-07-18: there should be a single backslash at the end of each line of the ./configure... command except for the last line, in order to join the lines into a single command.

latimeria68 · 2018-03-05T10:26:21Z

Ok I will purge remove nut installed from standard raspbian packages and test the patch. Keep you posted.
Many thanks

clepple · 2018-03-05T12:10:53Z

not necessary to purge the packages - the configuration I suggested lets you use all of the startup scripts and other NUT binaries as-is.

latimeria68 · 2018-03-06T22:11:40Z

I have applied the patch, wrong values disappeared but ups keeps staying on battery when main power off, so nothing changed on this side

CentroricercheRPS · 2018-03-13T16:09:28Z

Hi,
we are the mantainer of riello drivers.
When main power off, NUT wait the battery low signals before send a shutdown command to the ups.
From what we understood you have a fixed time to shutdown the ups after main power off. Is this right?
In every case please could you post your NUT configuration (the main parameters of ups.conf, upsmon.conf etc...) so we try to solve your issue?

latimeria68 · 2018-03-13T18:04:31Z

Hi,
zip file with confs attached.
nutconfig.zip
my config tells the nut server (a Raspberry with Raspbian Stretch installed) to shutdown server and clients after 3 minutes working on battery. This was working with my old UPS (an EQ Power LN651T)managed through the blazer_usb driver; after FINALDELAY the UPS put itself down too. This is not happening with the Riello IDG400 so I'm wondering if /lib/systemd/system-shutdown/nutshutdown works with the IDG and expecially if the IDG will return on when main power is back again.
Thanks

ulesin · 2018-03-21T21:02:28Z

Hello everyone! Any news? I am very interested in this topic because I have an UPS IDG 800 and I have the same problems with 255 values. Is there another form to patch It? I don't know the exactly commands I have to put from point 5.5, It doesn't work for me. Thank you very much!

autofrank · 2019-07-17T20:34:06Z

make sure you have "deb-src" lines to match the "deb" lines in /etc/apt/sources

run "sudo apt-get update" if you had to change anything

run "sudo apt-get build-dep nut"
3.5) optional: remove "asciidoc" (or install the build-deps manually, and omit asciidoc) to save a bit of build time

run "sudo apt-get -y install git" if you do not already have Git installed

clone the source to your working directory: "git clone https://github.com/networkupstools/nut.git"
5.5) "cd nut", apply the patch downloaded from the URL above: "zcat path/to/attachment.bin | patch -p0"

run this mega-command:

./configure --includedir=/usr/include --mandir=/usr/share/man
--infodir=/usr/share/info --sysconfdir=/etc/nut --localstatedir=/var
--libexecdir=/usr/lib/nut --srcdir=. --enable-maintainer-mode
--disable-silent-rules --libdir=/usr/lib/arm-linux-gnueabihf
--with-ssl --with-nss --with-cgi --with-dev --enable-static
--with-statepath=/var/run/nut --with-altpidpath=/var/run/nut
--with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut
--with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut
--datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/arm-linux-gnueabihf/pkgconfig
--with-user=nut --with-group=nut --with-udev-dir=/lib/udev
--with-systemdsystemunitdir=/lib/systemd/system

run "make"

HI @clepple
okay - got step 5.5 running but now the ./configure won't run
I'm running raspian jessi lite

I'm not terribly familiar with the raspian commands so any help really appreciated

Thanks

autofrank · 2019-07-17T20:34:40Z

Hello everyone! Any news? I am very interested in this topic because I have an UPS IDG 800 and I have the same problems with 255 values. Is there another form to patch It? I don't know the exactly commands I have to put from point 5.5, It doesn't work for me. Thank you very much!

Hi @ulesin
Did you manage to resolve ?

Thanks

clepple · 2019-07-18T02:02:21Z

@autofrank I think I was referring to this patch from this message to nut-upsdev: http://lists.alioth.debian.org/pipermail/nut-upsdev/2018-February/007374.html It’s the link below this: “Desc: riello.diff.gz”

autofrank · 2019-07-18T06:40:05Z

@clepple Thanks Charles..I located the patch and applied it. I'm trying to run the mega "./ configure....." command you suggest but all the combinations I try don't work. It seems like the command is not supported. I can only find a configure.au file on the pi and I'm also not sure if the command should be run as a single long string or a set of separate commands Any help appreciated.. .Thanks

…

-------- Original message --------From: Charles Lepple <notifications@github.com> Date: 18/07/2019 03:02 (GMT+00:00) To: networkupstools/nut <nut@noreply.github.com> Cc: autofrank <frank.tp.smith@gmail.com>, Mention <mention@noreply.github.com> Subject: Re: [networkupstools/nut] Riello IDG400 wrong values & not powering off (#530) @autofrank I think I was referring to this patch from this message to nut-upsdev: http://lists.alioth.debian.org/pipermail/nut-upsdev/2018-February/007374.html It’s the link below this: “Desc: riello.diff.gz” —You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread. [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "#530?email_source=notifications\u0026email_token=AE3NARJEMFUPPTHVMMHNI2DP77FK7A5CNFSM4ESJPNSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2HC6SQ#issuecomment-512634698", "url": "#530?email_source=notifications\u0026email_token=AE3NARJEMFUPPTHVMMHNI2DP77FK7A5CNFSM4ESJPNSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2HC6SQ#issuecomment-512634698", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

clepple · 2019-07-18T11:00:37Z

Hmm, it looks like the backslashes got stripped out. It should look like the `./configure" line (step 7) on this page: https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu

The backslashes make it all one command. It would need to be run from within the "nut" directory created by git clone.

Also, I must have dropped the step that says to run "./autogen.sh", which creates the configure script from configure.ac.

autofrank · 2019-07-18T12:30:39Z

Hmm, it looks like the backslashes got stripped out. It should look like the `./configure" line (step 7) on this page: https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu

The backslashes make it all one command. It would need to be run from within the "nut" directory created by git clone.

Also, I must have dropped the step that says to run "./autogen.sh", which creates the configure script from configure.ac.

Thanks @clepple
I'll give that a go this evening ...
Just so I'm clear - the command in your post appears over several lines. I assume I don't need to sequence that into one string. The reason I ask is because the Pi wouldn't accept it last night as it tried to execute the parts at the start. It sounds like that is because the backslashes were missing ....

clepple · 2019-07-18T12:34:26Z

Yes, use backslashes to join all of the lines into one command, as shown in the wiki page. (I will try to edit the comment in this issue, but no promises, since there are backslashes in the raw text already.)

autofrank · 2019-07-18T13:14:03Z

Yes, use backslashes to join all of the lines into one command, as shown in the wiki page. (I will try to edit the comment in this issue, but no promises, since there are backslashes in the raw text already.)

Perfect @clepple
It looks like I should run it as attached

clepple · 2019-07-18T19:06:44Z

In general, either use backslashes and multiple lines, or no backslashes and all on one line. (They might not be a problem in this case- hard to see on a small screen. )

autofrank · 2019-07-18T19:09:20Z

In general, either use backslashes and multiple lines, or no backslashes and all on one line. (They might not be a problem in this case- hard to see on a small screen. )

Thanks @clepple
I got that part to work earlier but the "make"command won't work
I've decided to start from scratch and see if'll work from a fresh raspbian buster image

autofrank · 2019-07-18T20:00:36Z

@clepple

make still not working

sequence of events as follows..

login as: pi
pi@192.168.1.239's password:
Linux raspberrypi 4.19.57+ #1244 Thu Jul 4 18:42:50 BST 2019 armv6l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

SSH is enabled and the default password for the 'pi' user has not been changed.
This is a security risk - please login as the 'pi' user and type 'passwd' to set a new password.

pi@raspberrypi:~ $ sudo apt-get update
Get:1 http://archive.raspberrypi.org/debian buster InRelease [25.1 kB]
Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Get:3 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB]
Get:4 http://archive.raspberrypi.org/debian buster/main armhf Packages [205 kB]
Fetched 13.2 MB in 39s (339 kB/s)
Reading package lists... Done
pi@raspberrypi:~ $ sudo apt-get build-dep nut
Reading package lists... Done
E: You must put some 'source' URIs in your sources.list
pi@raspberrypi:~ $ sudo nano /etc/apt/source.list
pi@raspberrypi:~ $ sudo nano /etc/apt/sources
pi@raspberrypi:~ $ ls
pi@raspberrypi:~ $ ls
pi@raspberrypi:~ $ ls -l
total 0
pi@raspberrypi:~ $ sudo apt-get -y install git
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
git-man libcurl3-gnutls liberror-perl
Suggested packages:
git-daemon-run | git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-cvs git-mediawiki git-svn
The following NEW packages will be installed:
git git-man libcurl3-gnutls liberror-perl
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 6,144 kB of archives.
After this operation, 32.8 MB of additional disk space will be used.
Get:1 http://ftp.heanet.ie/mirrors/raspbian/raspbian buster/main armhf libcurl3-gnutls armhf 7.64.0-4 [291 kB]
Get:2 http://ftp.heanet.ie/mirrors/raspbian/raspbian buster/main armhf liberror-perl all 0.17027-2 [30.9 kB]
Get:3 http://ftp.heanet.ie/mirrors/raspbian/raspbian buster/main armhf git-man all 1:2.20.1-2 [1,619 kB]
Get:4 http://ftp.heanet.ie/mirrors/raspbian/raspbian buster/main armhf git armhf 1:2.20.1-2 [4,202 kB]
Fetched 6,144 kB in 3s (2,207 kB/s)
Selecting previously unselected package libcurl3-gnutls:armhf.
(Reading database ... 37620 files and directories currently installed.)
Preparing to unpack .../libcurl3-gnutls_7.64.0-4_armhf.deb ...
Unpacking libcurl3-gnutls:armhf (7.64.0-4) ...
Selecting previously unselected package liberror-perl.
Preparing to unpack .../liberror-perl_0.17027-2_all.deb ...
Unpacking liberror-perl (0.17027-2) ...
Selecting previously unselected package git-man.
Preparing to unpack .../git-man_1%3a2.20.1-2_all.deb ...
Unpacking git-man (1:2.20.1-2) ...
Selecting previously unselected package git.
Preparing to unpack .../git_1%3a2.20.1-2_armhf.deb ...
Unpacking git (1:2.20.1-2) ...
Setting up libcurl3-gnutls:armhf (7.64.0-4) ...
Setting up liberror-perl (0.17027-2) ...
Setting up git-man (1:2.20.1-2) ...
Setting up git (1:2.20.1-2) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
pi@raspberrypi:~ $ git clone https://github.com/networkupstools/nut.git
Cloning into 'nut'...
remote: Enumerating objects: 54, done.
remote: Counting objects: 100% (54/54), done.
remote: Compressing objects: 100% (50/50), done.
remote: Total 40384 (delta 14), reused 16 (delta 4), pack-reused 40330
Receiving objects: 100% (40384/40384), 67.82 MiB | 835.00 KiB/s, done.
Resolving deltas: 100% (29594/29594), done.
Checking out files: 100% (706/706), done.
pi@raspberrypi:~ $ zcat patch/attachment.bin | patch -p0
gzip: patch/attachment.bin.gz: No such file or directory
pi@raspberrypi:~ $ ls
nut
pi@raspberrypi:~ $ cd nut
pi@raspberrypi:/nut $ zcat patch/attachment.bin | patch -p0
patching file drivers/riello_ser.c
patching file drivers/riello_usb.c
pi@raspberrypi:/nut $ ./configure --includedir=/usr/include --mandir=/usr/share/man \

--infodir=/usr/share/info --sysconfdir=/etc/nut --localstatedir=/var
--libexecdir=/usr/lib/nut --srcdir=. --enable-maintainer-mode
--disable-silent-rules --libdir=/usr/lib/arm-linux-gnueabihf
--with-ssl --with-nss --with-cgi --with-dev --enable-static
--with-statepath=/var/run/nut --with-altpidpath=/var/run/nut
--with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut
--with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut
--datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/arm-linux-gnueabihf/pkgconfig
--with-user=nut --with-group=nut --with-udev-dir=/lib/udev
--with-systemdsystemunitdir=/lib/systemd/system
-bash: ./configure: No such file or directory
pi@raspberrypi:/nut $ ./autogen.sh
Regenerating Augeas ups.conf lens...
Regenerating the USB helper files...
Calling autoreconf...
./autogen.sh: 44: ./autogen.sh: autoreconf: not found
pi@raspberrypi:/nut $ sudo apt-get install autoconf
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
automake autotools-dev libsigsegv2 m4
Suggested packages:
autoconf-archive gnu-standards autoconf-doc libtool gettext m4-doc
The following NEW packages will be installed:
autoconf automake autotools-dev libsigsegv2 m4
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,407 kB of archives.
After this operation, 4,276 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.heanet.ie/mirrors/raspbian/raspbian buster/main armhf libsigsegv2 armhf 2.12-2 [32.3 kB]
Get:2 http://ftp.heanet.ie/mirrors/raspbian/raspbian buster/main armhf m4 armhf 1.4.18-2 [185 kB]
Get:3 http://ftp.heanet.ie/mirrors/raspbian/raspbian buster/main armhf autoconf all 2.69-11 [341 kB]
Get:4 http://ftp.heanet.ie/mirrors/raspbian/raspbian buster/main armhf autotools-dev all 20180224.1 [77.0 kB]
Get:5 http://ftp.heanet.ie/mirrors/raspbian/raspbian buster/main armhf automake all 1:1.16.1-4 [771 kB]
Fetched 1,407 kB in 1s (1,137 kB/s)
Selecting previously unselected package libsigsegv2:armhf.
(Reading database ... 38556 files and directories currently installed.)
Preparing to unpack .../libsigsegv2_2.12-2_armhf.deb ...
Unpacking libsigsegv2:armhf (2.12-2) ...
Selecting previously unselected package m4.
Preparing to unpack .../archives/m4_1.4.18-2_armhf.deb ...
Unpacking m4 (1.4.18-2) ...
Selecting previously unselected package autoconf.
Preparing to unpack .../autoconf_2.69-11_all.deb ...
Unpacking autoconf (2.69-11) ...
Selecting previously unselected package autotools-dev.
Preparing to unpack .../autotools-dev_20180224.1_all.deb ...
Unpacking autotools-dev (20180224.1) ...
Selecting previously unselected package automake.
Preparing to unpack .../automake_1%3a1.16.1-4_all.deb ...
Unpacking automake (1:1.16.1-4) ...
Setting up autotools-dev (20180224.1) ...
Setting up libsigsegv2:armhf (2.12-2) ...
Setting up m4 (1.4.18-2) ...
Setting up autoconf (2.69-11) ...
Setting up automake (1:1.16.1-4) ...
update-alternatives: using /usr/bin/automake-1.16 to provide /usr/bin/automake (automake) in auto mode
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
pi@raspberrypi:/nut $ ./autogen.sh
Calling autoreconf...
configure.ac:135: error: possibly undefined macro: AC_PROG_LIBTOOL
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:904: error: possibly undefined macro: AC_DISABLE_STATIC
autoreconf: /usr/bin/autoconf failed with exit status: 1
pi@raspberrypi:/nut $ sudo apt-get install libtool
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libltdl-dev libltdl7
Suggested packages:
libtool-doc gfortran | fortran95-compiler gcj-jdk
The following NEW packages will be installed:
libltdl-dev libltdl7 libtool
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,093 kB of archives.
After this operation, 2,606 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.heanet.ie/mirrors/raspbian/raspbian buster/main armhf libltdl7 armhf 2.4.6-9 [387 kB]
Get:2 http://ftp.heanet.ie/mirrors/raspbian/raspbian buster/main armhf libltdl-dev armhf 2.4.6-9 [159 kB]
Get:3 http://ftp.heanet.ie/mirrors/raspbian/raspbian buster/main armhf libtool all 2.4.6-9 [547 kB]
Fetched 1,093 kB in 1s (1,162 kB/s)
Selecting previously unselected package libltdl7:armhf.
(Reading database ... 38851 files and directories currently installed.)
Preparing to unpack .../libltdl7_2.4.6-9_armhf.deb ...
Unpacking libltdl7:armhf (2.4.6-9) ...
Selecting previously unselected package libltdl-dev:armhf.
Preparing to unpack .../libltdl-dev_2.4.6-9_armhf.deb ...
Unpacking libltdl-dev:armhf (2.4.6-9) ...
Selecting previously unselected package libtool.
Preparing to unpack .../libtool_2.4.6-9_all.deb ...
Unpacking libtool (2.4.6-9) ...
Setting up libtool (2.4.6-9) ...
Setting up libltdl7:armhf (2.4.6-9) ...
Setting up libltdl-dev:armhf (2.4.6-9) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
pi@raspberrypi:/nut $ ./autogen.sh
Calling autoreconf...
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/ltobsolete.m4'
configure.ac:11: installing './config.guess'
configure.ac:11: installing './config.sub'
configure.ac:15: installing './install-sh'
configure.ac:15: installing './missing'
Makefile.am: installing './INSTALL'
clients/Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
pi@raspberrypi:/nut $ ./configure --includedir=/usr/include --mandir=/usr/share/man
--infodir=/usr/share/info --sysconfdir=/etc/nut --localstatedir=/var
--libexecdir=/usr/lib/nut --srcdir=. --enable-maintainer-mode
--disable-silent-rules --libdir=/usr/lib/gcc -print-multiarch
--with-ssl --with-nss --with-cgi --with-dev --enable-static
--with-statepath=/var/run/nut --with-altpidpath=/var/run/nut
--with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut
--with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut
--datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/gcc -print-multiarch/pkgconfig
--with-user=nut --with-group=nut --with-udev-dir=/lib/udev
--with-systemdsystemunitdir=/lib/systemd/system
Network UPS Tools version 2.7.4.1
checking build system type... armv6l-unknown-linux-gnueabihf
checking host system type... armv6l-unknown-linux-gnueabihf
checking target system type... armv6l-unknown-linux-gnueabihf
checking for host system name... debian
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for autoconf macro to enable system extensions... yes
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define EXTENSIONS... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking for pkg-config... /usr/bin/pkg-config
configure: checking for autoconf macro support of pkg-config
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
configure: checking for autoconf macro support of pkg-config module checker
checking for dummy_PKG_CONFIG... yes
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking for gcc option to accept ISO C99... none needed
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether g++ understands -c and -o together... yes
checking whether ln -s works... yes
checking for egrep... (cached) /bin/grep -E
checking for ar... /usr/bin/ar
checking for ranlib... ranlib
checking whether byte ordering is bigendian... no
checking for inline... inline
checking for flexible array members... yes
checking for variable-length arrays... yes
checking for flock... yes
checking for lockf... yes
checking for fcvt... yes
checking for fcvtl... no
checking for pow10... no
checking for round... no
checking for abs_val... no
checking for cfsetispeed... yes
checking for tcsendbreak... yes
checking for seteuid... yes
checking for setsid... yes
checking for getpassphrase... no
checking for on_exit... yes
checking for strptime... yes
checking for setlogmask... yes
checking whether LOG_UPTO is declared... yes
checking whether ln -sr works... yes
checking for unsigned long long int... yes
checking for vsnprintf... yes
checking for snprintf... yes
checking for setenv... yes
checking for strerror... yes
checking for atexit... yes
checking whether optind is declared... yes
checking for getopt.h... yes
checking for getopt_long... yes
checking whether uu_lock is declared... no
checking whether func is declared... yes
checking for library containing gethostbyname... none required
checking for library containing connect... none required
checking whether time.h and sys/time.h may both be included... yes
checking for sys/modem.h... no
checking for stdarg.h... yes
checking for varargs.h... no
checking for sys/termios.h... yes
checking for sys/time.h... yes
checking for library containing pthread_create... -lpthread
checking for socklen_t... yes
checking for --with-all... not given
checking for Net-SNMP version via net-snmp-config... none found
checking for Net-SNMP cflags...
checking for Net-SNMP libs...
checking for net-snmp/net-snmp-config.h... no
checking for init_snmp... no
checking for libusb version via pkg-config... checking via libusb-config... none found
checking for libusb cflags...
checking for libusb ldflags... -lusb
checking for usb.h... no
checking for usb_init... no
checking for libneon version via pkg-config (0.25.0 minimum required)... none found
configure: WARNING: could not get pkg-config information for libneon version, using fallback defaults
checking for libneon cflags... -I/usr/include/neon
configure: WARNING: could not get pkg-config information for libneon cflags, using fallback defaults
checking for libneon ldflags... -lneon
configure: WARNING: could not get pkg-config information for libneon libs, using fallback defaults
checking for ne_xmlreq.h... no
checking for ne_xml_dispatch_request... no
checking for libpowerman cflags...
checking for libpowerman libs...
checking for libpowerman.h... no
checking for pm_connect... no
checking for libmodbus version via pkg-config... none found
checking for libmodbus cflags... -I/usr/include/modbus
checking for libmodbus ldflags... -lmodbus
checking for modbus.h... no
checking for modbus_new_rtu... no
checking for modbus_new_tcp... no
checking for avahi-core version via pkg-config (0.6.30 minimum required)... none found
checking for avahi-client version via pkg-config (0.6.30 minimum required)... none found
checking for avahi cflags...
checking for avahi ldflags...
checking for avahi-common/malloc.h... no
checking for avahi_free... no
checking whether to build serial drivers... yes
checking whether to build USB drivers... no
checking whether to build neon based XML driver... no
checking whether to enable Avahi support... no
checking whether to build Powerman PDU client driver... no
checking whether to build Modbus driver... no
checking for FreeIPMI version via pkg-config... none found
checking for FreeIPMI cflags...
checking for FreeIPMI ldflags... -lfreeipmi -lipmimonitoring
checking for freeipmi/freeipmi.h... no
checking for ipmi_monitoring.h... no
checking for library containing ipmi_ctx_create... no
checking for library containing ipmi_ctx_find_inband... no
checking for library containing ipmi_monitoring_init... no
checking for library containing ipmi_monitoring_sensor_read_record_id... no
checking for library containing ipmi_sdr_cache_ctx_destroy... no
checking for library containing ipmi_sdr_ctx_destroy... no
checking whether to build IPMI driver... no
checking whether to build Mac OS X meta-driver... no
checking whether i2c_smbus_read_word_data is declared... no
checking whether i2c_smbus_write_word_data is declared... no
checking whether i2c_smbus_read_block_data is declared... no
checking whether to build i2c based drivers... no
checking for Mozilla NSS version via pkg-config... none found
checking for Mozilla NSS cflags...
checking for Mozilla NSS ldflags... -lnss3 -lnssutil3 -lsmime3 -lssl3 -lplds4 -lplc4 -lnspr4
checking for NSS_Init... no
checking for nss.h... yes
checking for ssl.h... no
configure: error: Mozilla NSS not found (required for SSL support)
pi@raspberrypi:/nut $ make
make: *** No targets specified and no makefile found. Stop.
pi@raspberrypi:~/nut $

autofrank · 2019-07-18T20:20:06Z

I think the issue is that i have a makefile.am and a makefile.in but no makefile
.. don;t know how to solve that one

clepple · 2019-07-19T02:42:00Z

Did you run sudo apt-get build-dep nut? That grabs the dependencies.

./configure needs to not error out, then it will create Makefiles. (You can remove some of the options like the SSL-related ones if you don't want to build those components.)

autofrank · 2019-07-20T14:52:39Z

@clepple
I finally got it working , thanks for the assistance.
The 255 reading s now gone but my battery capacity is showing as 7 (see below)

battery.capacity: 7
battery.voltage: 13.5
battery.voltage.nominal: 12
device.mfr: RPS S.p.a.
device.model: UNV1
device.serial:
device.type: ups
driver.name: riello_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.4-716-g0c48e7b2
driver.version.internal: 0.04
input.bypass.frequency: 409.50
input.bypass.voltage: 4095
input.frequency: 50.10
input.voltage: 241
output.frequency: 50.10
output.frequency.nominal: 50.0
output.L1.current: 0
output.L1.power: 0
output.L1.realpower: 0
output.L2.current: 0
output.L2.power: 0
output.L2.realpower: 0
output.L3.current: 0
output.L3.power: 0
output.L3.realpower: 0
output.power.percent: 0
output.voltage: 237
output.voltage.nominal: 230
ups.firmware: SWM038-01-02
ups.load: 0
ups.mfr: RPS S.p.a.
ups.model: UNV1
ups.power.nominal: 800
ups.productid: 5500
ups.realpower.nominal: 480
ups.serial:
ups.status: OL
ups.vendorid: 04b4

`
For the /etc/nut/ups.conf
Should I be using riello_usb.c instead of riello_usb
I tried this and it didn't start

I plugged out the UPS and checked it every 30/40 seconds
The ups.status seems to change but not much else (see seq attached)
riello IDG800.xlsx

Any thoughts

autofrank · 2019-07-20T15:29:59Z

I have applied the patch, wrong values disappeared but ups keeps staying on battery when main power off, so nothing changed on this side

@sgiannulli
Just wanted to check if you got the correct values
I applied the patch and no longer have 255 as battery charge but now I have 7
Is this what you are also seeing (IDG800)

battery.capacity: 7

battery.voltage: 13.5
battery.voltage.nominal: 12
device.mfr: RPS S.p.a.
device.model: UNV1
device.serial:
device.type: ups
driver.name: riello_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.4-716-g0c48e7b2
driver.version.internal: 0.04
input.bypass.frequency: 409.50
input.bypass.voltage: 4095
input.frequency: 50.10
input.voltage: 241
output.frequency: 50.10
output.frequency.nominal: 50.0
output.L1.current: 0
output.L1.power: 0
output.L1.realpower: 0
output.L2.current: 0
output.L2.power: 0
output.L2.realpower: 0
output.L3.current: 0
output.L3.power: 0
output.L3.realpower: 0
output.power.percent: 0
output.voltage: 237
output.voltage.nominal: 230
ups.firmware: SWM038-01-02
ups.load: 0
ups.mfr: RPS S.p.a.
ups.model: UNV1
ups.power.nominal: 800
ups.productid: 5500
ups.realpower.nominal: 480
ups.serial:
ups.status: OL
ups.vendorid: 04b4

autofrank · 2019-07-21T11:26:28Z

Hi,
we are the mantainer of riello drivers.
When main power off, NUT wait the battery low signals before send a shutdown command to the ups.
From what we understood you have a fixed time to shutdown the ups after main power off. Is this right?
In every case please could you post your NUT configuration (the main parameters of ups.conf, upsmon.conf etc...) so we try to solve your issue?

Hi @CentroricercheRPS
I installed the patched ups driver and the battery.charge and battery.runtime are missing
how can I calculate how much capacity I have left if power is being drawn from the UPS during an outage ?

clepple · 2019-07-21T11:36:46Z

@autofrank riello_usb is still the name to use in ups.conf. The riello_usb.c file is just the primary source file that is used to build the driver.

I must have been thinking of a different patch, though. All this one does is prevent battery.charge and battery.runtime from being displayed if the values correspond to 0xff. I assume this means that the UPS does not calculate these values.

autofrank · 2019-07-21T12:07:05Z

@autofrank riello_usb is still the name to use in ups.conf. The riello_usb.c file is just the primary source file that is used to build the driver.

I must have been thinking of a different patch, though. All this one does is prevent battery.charge and battery.runtime from being displayed if the values correspond to 0xff. I assume this means that the UPS does not calculate these values.

thanks @clepple
I'm in the process of running it down to see how long it lasts but it seems that even from the riello sw itself (power shield3) I can't seem to find the rundown time... may need to return it for another device...

CentroricercheRPS · 2019-08-28T09:57:52Z

Yes, as @clepple <https://github.com/clepple> sayd some devices do not provide the charge or authonomy indication. Il giorno dom 21 lug 2019 alle ore 14:07 autofrank <notifications@github.com> ha scritto:

…

@autofrank <https://github.com/autofrank> riello_usb is still the name to use in ups.conf. The riello_usb.c file is just the primary source file that is used to build the driver. I must have been thinking of a different patch, though. All this one does is prevent battery.charge and battery.runtime from being displayed if the values correspond to 0xff. I assume this means that the UPS does not calculate these values. thanks @clepple <https://github.com/clepple> I'm in the process of running it down to see how long it lasts but it seems that even from the riello sw itself (power shield3) I can't seem to find the rundown time... may need to return it for another device... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#530?email_source=notifications&email_token=AHQEA6IHS55JQAFWH6S34GTQARGO3A5CNFSM4ESJPNSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2OB5TY#issuecomment-513547983>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHQEA6KI2IRQDUS5I36HE3TQARGO3ANCNFSM4ESJPNSA> .

NilByte · 2020-12-12T15:49:42Z

I have the same problem with Riello IDG400 not accepting paramters offdelay, ondelay and lowbatt in ups.conf.

I tried to follow the git clone procedure to see if it would change but it didn't.

admin@raspberrypi:~ $ sudo service nut-client restart
admin@raspberrypi:~ $ sudo systemctl status nut-server
● nut-server.service - Network UPS Tools - power devices information server
   Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2020-12-12 15:11:02 GMT; 24s ago
  Process: 19988 ExecStart=/sbin/upsd (code=exited, status=0/SUCCESS)
 Main PID: 19993 (upsd)
    Tasks: 1 (limit: 4915)
   Memory: 480.0K
   CGroup: /system.slice/nut-server.service
           └─19993 /lib/nut/upsd

Dec 12 15:11:02 raspberrypi upsd[19988]: listening on 192.168.1.105 port 3493
Dec 12 15:11:02 raspberrypi upsd[19988]: listening on 127.0.0.1 port 3493
Dec 12 15:11:02 raspberrypi upsd[19988]: listening on 127.0.0.1 port 3493
Dec 12 15:11:02 raspberrypi upsd[19988]: Connected to UPS [UPS-1]: riello_usb-UPS-1
Dec 12 15:11:02 raspberrypi upsd[19988]: Connected to UPS [UPS-1]: riello_usb-UPS-1
Dec 12 15:11:02 raspberrypi upsd[19993]: Startup successful
Dec 12 15:11:02 raspberrypi systemd[1]: Started Network UPS Tools - power devices information server.
Dec 12 15:11:02 raspberrypi upsd[19993]: User upsmon@127.0.0.1 logged into UPS [UPS-1]
Dec 12 15:11:17 raspberrypi upsd[19993]: User upsmon@127.0.0.1 logged out from UPS [UPS-1]
Dec 12 15:11:17 raspberrypi upsd[19993]: User upsmon@127.0.0.1 logged into UPS [UPS-1]
admin@raspberrypi:~ $ upsc UPS-1
Init SSL without certificate database
battery.capacity: 7
battery.charge: 255
battery.runtime: 3932100
battery.voltage: 13.5
battery.voltage.nominal: 12
device.mfr: RPS S.p.a.
device.model: UNV1
device.serial:
device.type: ups
driver.name: riello_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.4-2050-gd90c5d30
driver.version.internal: 0.03
input.bypass.frequency: 409.50
input.bypass.voltage: 4095
input.frequency: 50.00
input.voltage: 228
output.frequency: 50.00
output.frequency.nominal: 50.0
output.L1.current: 0
output.L1.power: 0
output.L1.realpower: 0
output.L2.current: 0
output.L2.power: 0
output.L2.realpower: 0
output.L3.current: 0
output.L3.power: 0
output.L3.realpower: 0
output.power.percent: 0
output.voltage: 222
output.voltage.nominal: 230
ups.firmware: SWM038-01-02
ups.load: 0
ups.mfr: RPS S.p.a.
ups.model: UNV1
ups.power.nominal: 400
ups.productid: 5500
ups.realpower.nominal: 240
ups.serial:
ups.status: OL
ups.temperature: 255
ups.vendorid: 04b4
admin@raspberrypi:~ $ lsusb
Bus 002 Device 002: ID 2109:0715 VIA Labs, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232 Adapter
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It shows driver version 2.7.4-2050-gd90c5d30, but internal driver version is still 0.03.

Any ideas on how to set a timed offdelay to let the client shutdown before the UPS shuts down, that is not based on battery status?

The non opensource driver from Riello has this functionality working, so the riello_usb driver seems to miss this functionality.

The parameters that are missing are described in http://rogerprice.org/NUT/ConfigExamples.A5.pdf

72 # ups.conf, improved
73 [UPS-1]
74 driver = usbhid-ups
75 port = auto
76 desc = "Eaton ECO 1600"
77 offdelay = 60
78 ondelay = 70
79 lowbatt = 33

geoghegan · 2021-07-31T15:28:04Z

I've an IPG800 which is listed as a 4* driver. I am running nut on a Debian 10 rPi also. Here is the output from uspc (with the mains power killed)

Init SSL without certificate database
battery.capacity: 7
battery.charge: 255
battery.runtime: 3932100
battery.voltage: 12.3
battery.voltage.nominal: 12
device.mfr: RPS S.p.a.
device.model: USV5
device.serial:
device.type: ups
driver.name: riello_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.internal: 0.03
input.bypass.frequency: 409.50
input.bypass.voltage: 4095
input.frequency: 0.00
input.voltage: 4
output.frequency: 50.00
output.frequency.nominal: 50.0
output.L1.current: 0
output.L1.power: 0
output.L1.realpower: 0
output.L2.current: 0
output.L2.power: 0
output.L2.realpower: 0
output.L3.current: 0
output.L3.power: 0
output.L3.realpower: 0
output.power.percent: 0
output.voltage: 231
output.voltage.nominal: 230
ups.firmware: SWM036-01-04
ups.load: 0
ups.mfr: RPS S.p.a.
ups.model: USV5
ups.power.nominal: 800
ups.productid: 5500
ups.realpower.nominal: 480
ups.serial:
ups.status: OB
ups.temperature: 255
ups.vendorid: 04b4

The charge and runtime are obviously wrong.

@NilByte : Where did you find the non-FOSS driver?

NilByte · 2021-08-01T11:04:02Z

I'm using upsmon downloaded from Riello:

https://www.riello-ups.com/downloads/1-powershield-free

V.5.3 (Build: 000) for Linux Raspbian Raspberry Pi

https://www.riello-ups.com/uploads/file/402/1402/upsmon-5.3.0-linux-3.12-armhf.deb

There are versions for Debian listed as well.

NilByte · 2022-01-18T16:05:09Z

There is a mailing list here suggesting update of the riello_ser and riello_usb from the original driver author which could possibly fix some of the problems that are experienced.

@jimklimov : Would it be possible for one of the NUT devs to have a look at this?

https://www.mail-archive.com/nut-upsdev@alioth-lists.debian.net/msg00106.html

From one of the attachments riello.diff:

Index: drivers/riello_ser.c
===================================================================
--- drivers/riello_ser.c	(revisione 7681)
+++ drivers/riello_ser.c	(copia locale)
@@ -37,14 +37,17 @@
 #include "riello.h"
 
 #define DRIVER_NAME	"Riello serial driver"
-#define DRIVER_VERSION	"0.03"
+#define DRIVER_VERSION	"0.04"
 
+#define DEFAULT_OFFDELAY   5
+#define DEFAULT_BOOTDELAY  5
+
 /* driver description structure */
 upsdrv_info_t upsdrv_info = {
 	DRIVER_NAME,
 	DRIVER_VERSION,
 	"Elio Parisi <e.parisi@riello-ups.com>",
-	DRV_EXPERIMENTAL,
+	DRV_STABLE,
 	{ NULL }
 };
 
@@ -57,6 +60,9 @@
 uint8_t input_monophase;
 uint8_t output_monophase;
 
+static unsigned int offdelay = DEFAULT_OFFDELAY;
+static unsigned int bootdelay = DEFAULT_BOOTDELAY; 
+
 extern uint8_t commbyte;
 extern uint8_t wait_packet;
 extern uint8_t foundnak;
@@ -751,6 +757,13 @@
 	dstate_addcmd("shutdown.stop");
 	dstate_addcmd("test.battery.start");
 
+	dstate_setinfo("ups.delay.shutdown", "%d", offdelay);
+	dstate_setflags("ups.delay.shutdown", ST_FLAG_RW | ST_FLAG_STRING);
+	dstate_setaux("ups.delay.shutdown", 3);
+	dstate_setinfo("ups.delay.reboot", "%d", bootdelay);
+	dstate_setflags("ups.delay.reboot", ST_FLAG_RW | ST_FLAG_STRING);
+	dstate_setaux("ups.delay.reboot", 3);
+
 	if (typeRielloProtocol == DEV_RIELLOGPSER)
 		dstate_addcmd("test.panel.start");
 
@@ -803,9 +816,12 @@
 	dstate_setinfo("input.bypass.frequency", "%.2f", DevData.Fbypass/10.0);
 	dstate_setinfo("output.frequency", "%.2f", DevData.Fout/10.0);
 	dstate_setinfo("battery.voltage", "%.1f", DevData.Ubat/10.0);
-	dstate_setinfo("battery.charge", "%u", DevData.BatCap);
-	dstate_setinfo("battery.runtime", "%u", DevData.BatTime*60);
-	dstate_setinfo("ups.temperature", "%u", DevData.Tsystem);
+	if ((DevData.BatCap < 0xFFFF) &&  (DevData.BatTime < 0xFFFF)) {
+		dstate_setinfo("battery.charge", "%u", DevData.BatCap);
+		dstate_setinfo("battery.runtime", "%u", DevData.BatTime*60);
+	}
+	if (DevData.Tsystem < 0xFF)
+		dstate_setinfo("ups.temperature", "%u", DevData.Tsystem);
 
 	if (input_monophase) {
 		dstate_setinfo("input.voltage", "%u", DevData.Uinp1);
Index: drivers/riello_usb.c
===================================================================
--- drivers/riello_usb.c	(revisione 7681)
+++ drivers/riello_usb.c	(copia locale)
@@ -33,14 +33,17 @@
 #include "riello.h"
 
 #define DRIVER_NAME	"Riello USB driver"
-#define DRIVER_VERSION	"0.03"
+#define DRIVER_VERSION	"0.04"
 
+#define DEFAULT_OFFDELAY   5  /*!< seconds (max 0xFF) */
+#define DEFAULT_BOOTDELAY  5  /*!< seconds (max 0xFF) */
+
 /* driver description structure */
 upsdrv_info_t upsdrv_info = {
 	DRIVER_NAME,
 	DRIVER_VERSION,
 	"Elio Parisi <e.parisi@riello-ups.com>",
-	DRV_EXPERIMENTAL,
+	DRV_STABLE,
 	{ NULL }
 };
 
@@ -52,6 +55,10 @@
 uint8_t input_monophase;
 uint8_t output_monophase;
 
+/*! Time in seconds to delay before shutting down. */
+static unsigned int offdelay = DEFAULT_OFFDELAY;
+static unsigned int bootdelay = DEFAULT_BOOTDELAY; 
+
 extern uint8_t commbyte;
 extern uint8_t wait_packet;
 extern uint8_t foundnak;
@@ -929,6 +936,13 @@
 	dstate_addcmd("test.battery.start");
 	dstate_addcmd("test.panel.start");
 
+	dstate_setinfo("ups.delay.shutdown", "%d", offdelay);
+	dstate_setflags("ups.delay.shutdown", ST_FLAG_RW | ST_FLAG_STRING);
+	dstate_setaux("ups.delay.shutdown", 3);
+	dstate_setinfo("ups.delay.reboot", "%d", bootdelay);
+	dstate_setflags("ups.delay.reboot", ST_FLAG_RW | ST_FLAG_STRING);
+	dstate_setaux("ups.delay.reboot", 3);
+
 	/* install handlers */
 /*	upsh.setvar = hid_set_value; setvar; */
 
@@ -1012,9 +1026,12 @@
 	dstate_setinfo("input.bypass.frequency", "%.2f", DevData.Fbypass/10.0);
 	dstate_setinfo("output.frequency", "%.2f", DevData.Fout/10.0);
 	dstate_setinfo("battery.voltage", "%.1f", DevData.Ubat/10.0);
-	dstate_setinfo("battery.charge", "%u", DevData.BatCap);
-	dstate_setinfo("battery.runtime", "%u", DevData.BatTime*60);
-	dstate_setinfo("ups.temperature", "%u", DevData.Tsystem);
+	if ((DevData.BatCap < 0xFFFF) &&  (DevData.BatTime < 0xFFFF)) {
+		dstate_setinfo("battery.charge", "%u", DevData.BatCap);
+		dstate_setinfo("battery.runtime", "%u", DevData.BatTime*60);
+	}
+	if (DevData.Tsystem < 0xFF)
+		dstate_setinfo("ups.temperature", "%u", DevData.Tsystem);
 
 	if (input_monophase) {
 		dstate_setinfo("input.voltage", "%u", DevData.Uinp1);

geoghegan · 2022-02-09T22:59:15Z

@NilByte PR #1280 may be of help to you

jimklimov · 2022-02-10T10:56:46Z

Thanks for the PR, commented some bits there :)

As for the original issue, I think Riello devices use a variant of Megatec Qx protocols (sources mention "cypress"), so wondering if the newer nutdrv_qx (which consolidates many older drivers into same architecture) might handle them better?

geoghegan · 2022-02-10T18:38:41Z

Sadly it doesn't - at least not with this configuration in /etc/nut/ups.conf

[ups]
  driver = nutdrv_qx
  port = auto
  vendorid = 04b4
  productid = 5500
  subdriver = cypress

Error back is Device not supported!

geoghegan · 2022-02-11T20:15:57Z

The erroneous runtime, temp, and charge should be fixed for an IDG (1600). Shutdown and reboot delays should also be working. Both addressed in version 0.7 of the driver, merged as PR #1280 .

Edit: It appears that setting the reboot and shutdown delays (e.g. ./drivers/riello_usb -a ups -x override.ups.delay.reboot=10) does not persist if upsdrvctl is restarted. I doubt the IDG has non-volatile memory. These delays are set as 5 seconds in the code

NilByte · 2022-02-16T17:19:27Z

Finally I managed to get successful timed shutdown, ups powering off and powering up again when mains return.

NUT build from master driver.version: 2.7.4-4609-g61862059, driver.version.internal: 0.07 according to https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu

Configuration that worked for me:

        NUT configuration  2022-02-16 16:38:28 UTC

        ########### Operating system ###########
Kernel release 5.10.63-v8+ GNU/Linux
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_CODENAME=buster
Network UPS Tools upsd 2.7.4
Bash version 5.0.3(1)-release
User root
nut-report.sh version: 2020-08-07

        ########### /etc/nut/nut.conf ###########
MODE=standalone

        ########### /etc/nut/ups.conf ###########
pollinterval = 1
maxretry = 3
[UPS-1]
	driver = riello_usb
	port = auto
        desc = "Riello IDG400"
	override.ups.delay.shutdown = 14
	override.ups.delay.reboot = 7

        ########### /etc/nut/upsd.conf ###########
LISTEN 127.0.0.1 3493
LISTEN 192.168.1.105

        ########### /etc/nut/upsd.users ###########
[upsmaster]
	upsmon master
	password =  ****m**** 
	actions = SET FSD
	instcmds = ALL

        ########### /etc/nut/upsmon.conf ###########
RUN_AS_USER nut
MONITOR UPS-1@localhost 1 upsmaster  ****m****  master
MINSUPPLIES 1
SHUTDOWNCMD "/home/admin/config.scripts/custom.shutdown.sh"
NOTIFYCMD /sbin/upssched
POLLFREQ 2
POLLFREQALERT 1
HOSTSYNC 15
DEADTIME 15
POWERDOWNFLAG /etc/killpower
NOTIFYMSG ONLINE    "UPS %s on line power"
NOTIFYMSG ONBATT    "UPS %s on battery"
NOTIFYMSG LOWBATT   "UPS %s battery is low"
NOTIFYMSG FSD       "UPS %s: forced shutdown in progress"
NOTIFYMSG COMMOK    "Communications with UPS %s established"
NOTIFYMSG COMMBAD   "Communications with UPS %s lost"
NOTIFYMSG SHUTDOWN  "Auto logout and shutdown proceeding"
NOTIFYMSG REPLBATT  "UPS %s battery needs to be replaced"
NOTIFYMSG NOCOMM    "UPS %s is unavailable"
NOTIFYMSG NOPARENT  "upsmon parent process died - shutdown impossible"
NOTIFYFLAG ONLINE   SYSLOG+WALL+EXEC
NOTIFYFLAG ONBATT   SYSLOG+WALL+EXEC
NOTIFYFLAG LOWBATT  SYSLOG+WALL+EXEC
NOTIFYFLAG FSD      SYSLOG+WALL+EXEC
NOTIFYFLAG COMMOK   SYSLOG+WALL+EXEC
NOTIFYFLAG COMMBAD  SYSLOG+WALL+EXEC
NOTIFYFLAG SHUTDOWN SYSLOG+WALL+EXEC
NOTIFYFLAG REPLBATT SYSLOG+WALL+EXEC
NOTIFYFLAG NOCOMM   SYSLOG+WALL+EXEC
NOTIFYFLAG NOPARENT SYSLOG+WALL
RBWARNTIME 43200
NOCOMMWARNTIME 600
FINALDELAY 5

        ########### /etc/nut/upssched.conf ###########
CMDSCRIPT /bin/upssched-cmd
PIPEFN /etc/nut/upssched/upssched.pipe
LOCKFN /etc/nut/upssched/upssched.lock
AT COMMBAD * START-TIMER comms-bad 15
AT COMMOK * CANCEL-TIMER comms-bad
AT COMMOK * START-TIMER comms-ok 60
AT COMMBAD * CANCEL-TIMER comms-ok
AT ONBATT * START-TIMER on-batt 10
AT ONLINE * CANCEL-TIMER on-batt
AT ONLINE * EXECUTE on-mains
AT REPLBATT * EXECUTE replace-batt
AT FSD * EXECUTE forced-shutdown
AT LOWBATT * EXECUTE low-batt
AT NOCOMM * EXECUTE no-comms
AT SHUTDOWN * EXECUTE shutdown
AT ONBATT * START-TIMER early-shutdown 120
AT ONLINE * CANCEL-TIMER early-shutdown

        ########### /bin/upssched-cmd ###########
#!/bin/sh
case $1 in
    	no-comms)
                logger -t upssched-cmd "UPS no comms event triggered."
                ;;
        comms-bad)
                logger -t upssched-cmd "UPS comms bad state exceeded timer value."
                ;;
        comms-ok)
                logger -t upssched-cmd "UPS comms OK for at least timer value."
                ;;
        on-batt)
                logger -t upssched-cmd "UPS On Battery state exceeded timer value."
                ;;
        on-mains)
                logger -t upssched-cmd "UPS mains power has returned."
                upscmd -u upsmaster -p ****m**** UPS-1@localhost shutdown.stop
		;;
        early-shutdown)
                logger -t upssched-cmd "UPS On Battery state exceeded early Shutdown timer value."
		upscmd -u upsmaster -p ****m**** UPS-1@localhost shutdown.return
                ;;
        forced-shutdown)
                logger -t upssched-cmd "UPS force shutdown has been executed (ie upsmon -c fsd)."
                /usr/sbin/upsmon -c fsd
		;;
        shutdown)
                logger -t upssched-cmd "UPS - shutdown in progress."
                ;;
        low-batt)
                logger -t upssched-cmd "UPS Low Battery Warning."
                ;;
        replace-batt)
                logger -t upssched-cmd "UPS Replace Battery Warning."
                ;;
        *)
          	logger -t upssched-cmd "UPS Unrecognized event: $1"
                ;;
esac
exit 0

        ########### /etc/hosts.allow ###########

        ########### ps -eLf ###########
nut       1292     1  1292  0    1 17:13 ?        00:00:00 /lib/nut/upsd
root      1296     1  1296  0    1 17:13 ?        00:00:00 /lib/nut/upsmon
nut       1297  1296  1297  0    1 17:13 ?        00:00:00 /lib/nut/upsmon

        ########### Ownership and permissions of executables ###########
-rwxr-xr-x 1 root root   425 Jun  1  2018 /usr/sbin/upsd*
-rwxr-xr-x 1 root root 30672 Jun  1  2018 /usr/sbin/upsdrvctl*
-rwxr-xr-x 1 root root   429 Jun  1  2018 /usr/sbin/upsmon*
-rwxr-xr-x 1 root root 30664 Jun  1  2018 /usr/sbin/upssched*

        ########### Ownership and permissions of configuration files ###########
-rw-r----- 1 root nut  1112 Feb  4 20:12 /etc/nut/hosts.conf
-rw-r----- 1 root nut    16 Feb  3 21:09 /etc/nut/nut.conf
-rw-r----- 1 root nut  1538 Jun  1  2018 /etc/nut/nut.conf.dpkg-dist
-rw-r----- 1 root nut   647 Feb 16 17:00 /etc/nut/ups.conf
-rw-r----- 1 root nut  5522 Jun  1  2018 /etc/nut/ups.conf.dpkg-dist
-rw-r----- 1 root nut    43 Feb  3 22:39 /etc/nut/upsd.conf
-rw-r----- 1 root nut  4578 Jun  1  2018 /etc/nut/upsd.conf.dpkg-dist
-rw-r----- 1 root nut   358 Feb 10 18:00 /etc/nut/upsd.users
-rw-r----- 1 root nut  2131 Jun  1  2018 /etc/nut/upsd.users.dpkg-dist
-rw-r----- 1 root nut  1378 Feb 13 14:27 /etc/nut/upsmon.conf
-rw-r----- 1 root nut 15308 Jun  1  2018 /etc/nut/upsmon.conf.dpkg-dist
-rw-r----- 1 root nut  4815 Feb 15 21:51 /etc/nut/upssched.conf
-rw-r----- 1 root nut  3887 Jun  1  2018 /etc/nut/upssched.conf.dpkg-dist

/etc/nut/upssched:
total 8
drwxr-xr-x 2 nut  nut 4096 Feb 16 17:08 ./
drwxr-xr-x 3 root nut 4096 Feb 16 17:28 ../
srw-rw---- 1 nut  nut    0 Feb 16 17:08 upssched.pipe=

        ########### Custom NOTIFYCMD scheduler /sbin/upssched ###########
Custom NOTIFYCMD scheduler /sbin/upssched is not a script

        ########### nut-journal ###########

I believe that the issue on not powering off has also been solved by riello_usb driver version 0.7 #1280

ntd · 2024-03-07T07:19:45Z

Trying to summarize the current status (nut 2.8.1, riello_usb 0.11, UPS iDialog whatever): I'm able to shutdown if (and only if) the UPS is on battery and I send a shutdown command from software. Specifically I cannot:

shutdown when UPS is on power: it fails with instcmd: unknown command [shutdown.return] [(null)]
shutdown autonomously when power goes off

In my use case, 2 is especially important: if for some reason the software fails to send the shutdown (e.g. the PC is off), that thing stays on battery forever.

Is this correct?

clepple mentioned this issue Dec 18, 2019

Bad data from riello_usb driver for Riello Net Power NPW 800 #750

Open

geoghegan mentioned this issue Feb 9, 2022

Update riello (ser, usb) for shutdown/reboot delays (Fixes #530) #1280

Merged

jimklimov added raspberry USB labels Feb 10, 2022

jimklimov mentioned this issue Feb 22, 2022

riello IPG 800 serial. Serial-to-USB cable #1302

Open

PeteRager mentioned this issue Nov 11, 2022

Incorrect readings with NUT integration for UPS Riello IDG 600 home-assistant/core#79703

Closed

jimklimov added the Riello Riello UPS devices (serial, usb), usually with a variant of Qx protocol label Apr 3, 2023

jimklimov mentioned this issue Apr 3, 2023

Incorrect data from the **riello_usb** driver #1895

Closed

jimklimov added HCL DDL Shutdowns and overrides and battery level triggers Issues and PRs about system shutdown, especially if battery charge/runtime remaining is involved labels Aug 29, 2023

Riello IDG400 wrong values & not powering off #530

Riello IDG400 wrong values & not powering off #530

Comments

latimeria68 commented Feb 25, 2018

jimklimov commented Feb 25, 2018

latimeria68 commented Feb 25, 2018

clepple commented Feb 26, 2018

latimeria68 commented Feb 26, 2018

clepple commented Mar 1, 2018 via email

latimeria68 commented Mar 1, 2018

clepple commented Mar 2, 2018 via email

latimeria68 commented Mar 2, 2018

clepple commented Mar 5, 2018 • edited

latimeria68 commented Mar 5, 2018

clepple commented Mar 5, 2018 via email

latimeria68 commented Mar 6, 2018

CentroricercheRPS commented Mar 13, 2018

latimeria68 commented Mar 13, 2018

ulesin commented Mar 21, 2018 • edited

autofrank commented Jul 17, 2019 • edited

autofrank commented Jul 17, 2019

clepple commented Jul 18, 2019 via email

autofrank commented Jul 18, 2019 via email • edited

clepple commented Jul 18, 2019

autofrank commented Jul 18, 2019

clepple commented Jul 18, 2019

autofrank commented Jul 18, 2019

clepple commented Jul 18, 2019 via email

autofrank commented Jul 18, 2019

autofrank commented Jul 18, 2019

autofrank commented Jul 18, 2019

clepple commented Jul 19, 2019

autofrank commented Jul 20, 2019 • edited

@clepple I finally got it working , thanks for the assistance. The 255 reading s now gone but my battery capacity is showing as 7 (see below)

autofrank commented Jul 20, 2019

battery.capacity: 7

autofrank commented Jul 21, 2019

clepple commented Jul 21, 2019

autofrank commented Jul 21, 2019

CentroricercheRPS commented Aug 28, 2019 via email

NilByte commented Dec 12, 2020 • edited

geoghegan commented Jul 31, 2021 • edited

NilByte commented Aug 1, 2021

NilByte commented Jan 18, 2022 • edited

geoghegan commented Feb 9, 2022

jimklimov commented Feb 10, 2022

geoghegan commented Feb 10, 2022 • edited

geoghegan commented Feb 11, 2022 • edited

NilByte commented Feb 16, 2022

ntd commented Mar 7, 2024

clepple commented Mar 5, 2018 •

edited

ulesin commented Mar 21, 2018 •

edited

autofrank commented Jul 17, 2019 •

edited

autofrank commented Jul 18, 2019 via email •

edited

autofrank commented Jul 20, 2019 •

edited

@clepple
I finally got it working , thanks for the assistance.
The 255 reading s now gone but my battery capacity is showing as 7 (see below)

NilByte commented Dec 12, 2020 •

edited

geoghegan commented Jul 31, 2021 •

edited

NilByte commented Jan 18, 2022 •

edited

geoghegan commented Feb 10, 2022 •

edited

geoghegan commented Feb 11, 2022 •

edited