Impossible de faire fontionner Onduleur APC UPS

Bonjour, j’ai fait l’acquisition d’un onduleur APC Back-UPS ES - BE700G-FR.

Je l’ai branché, branché le câble data sur l’onduleur et l’usb sur ma jeedom smart.

J’ai ça dans les logs Apcups_dep

Reading package lists…
Building dependency tree…
Reading state information…
Suggested packages:
apcupsd-cgi
Recommended packages:
apcupsd-doc s-nail | mailx
The following NEW packages will be installed:
apcupsd
0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded.
1 not fully installed or removed.
Need to get 243 kB of archives.
After this operation, 848 kB of additional disk space will be used.
Get:1 Index of /debian stretch/main arm64 apcupsd arm64 3.14.14-0.3 [243 kB]
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 243 kB in 0s (1829 kB/s)
Selecting previously unselected package apcupsd.
(Reading database …
(Reading database … 5%
(Reading database … 10%
(Reading database … 15%
(Reading database … 20%
(Reading database … 25%
(Reading database … 30%
(Reading database … 35%
(Reading database … 40%
(Reading database … 45%
(Reading database … 50%
(Reading database … 55%
(Reading database … 60%
(Reading database … 65%
(Reading database … 70%
(Reading database … 75%
(Reading database … 80%
(Reading database … 85%
(Reading database … 90%
(Reading database … 95%
(Reading database … 100%
(Reading database … 56906 files and directories currently installed.)
Preparing to unpack …/apcupsd_3.14.14-0.3_arm64.deb …
Unpacking apcupsd (3.14.14-0.3) …
Setting up setup-odroid (0.0.1-51) …
cat: /boot/boot.ini: No such file or directory
sed: invalid option – ‹ 1 ›
Usage: sed [OPTION]… {script-only-if-no-other-script} [input-file]…
-n, --quiet, --silent
suppress automatic printing of pattern space
-e script, --expression=script
add the script to the commands to be executed
-f script-file, --file=script-file
add the contents of script-file to the commands to be executed
–follow-symlinks
follow symlinks when processing in place
-i[SUFFIX], --in-place[=SUFFIX]
edit files in place (makes backup if SUFFIX supplied)
-l N, --line-length=N
specify the desired line-wrap length for the l' command --posix disable all GNU extensions. -E, -r, --regexp-extended use extended regular expressions in the script (for portability use POSIX -E). -s, --separate consider files as separate rather than as a single, continuous long stream. --sandbox operate in sandbox mode. -u, --unbuffered load minimal amounts of data from the input files and flush the output buffers more often -z, --null-data separate lines by NUL characters --help display this help and exit --version output version information and exit If no -e, --expression, -f, or --file option is given, then the first non-option argument is taken as the sed script to interpret. All remaining arguments are names of input files; if no input files are specified, then the standard input is read. GNU sed home page: <http://www.gnu.org/software/sed/>. General help using GNU software: <http://www.gnu.org/gethelp/>. sed: invalid option -- '1' Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]... -n, --quiet, --silent suppress automatic printing of pattern space -e script, --expression=script add the script to the commands to be executed -f script-file, --file=script-file add the contents of script-file to the commands to be executed --follow-symlinks follow symlinks when processing in place -i[SUFFIX], --in-place[=SUFFIX] edit files in place (makes backup if SUFFIX supplied) -l N, --line-length=N specify the desired line-wrap length for the l’ command
–posix
disable all GNU extensions.
-E, -r, --regexp-extended
use extended regular expressions in the script
(for portability use POSIX -E).
-s, --separate
consider files as separate rather than as a single,
continuous long stream.
–sandbox
operate in sandbox mode.
-u, --unbuffered
load minimal amounts of data from the input files and flush
the output buffers more often
-z, --null-data
separate lines by NUL characters
–help display this help and exit
–version output version information and exit
If no -e, --expression, -f, or --file option is given, then the first
non-option argument is taken as the sed script to interpret. All
remaining arguments are names of input files; if no input files are
specified, then the standard input is read.
GNU sed home page: http://www.gnu.org/software/sed/.
General help using GNU software: http://www.gnu.org/gethelp/.
cat: /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
sed: can’t read /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
/var/lib/dpkg/info/setup-odroid.postinst: line 228: [: -lt: unary operator expected
grep: /boot/boot.ini: No such file or directory
can’t find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:

|diff --git a/boot.ini b/boot.ini
|index 1bfe00b…97c5ba1 100755
|— a/boot.ini 2016-03-19 13:37:36.000000000 +0100

+++ b/boot.ini 2016-05-06 19:46:52.966733237 +0200

File to patch:

Et ça dans les logs Apcups
[ERROR] : Erreur sur la fonction cron du plugin : The command /sbin/apcaccess status 127.0.0.1:3551 has failed or not returned any string.

Je ne sais pas quoi faire.

Pouvez vous m’aider svp?

Merci

Bonsoir,
Essayez la même commande en ouvrant une console ssh
les commandes:
apcaccess
ou /sbin/apcaccess status 127.0.0.1:3551
doivent donner en réponse, quelque chose comme:

APC : 001,034,0850
DATE : 2020-02-25 19:44:20 +0000
HOSTNAME : raspberrypi
VERSION : 3.14.14 (31 May 2016) debian
UPSNAME : jeedom UPS_IDEN
CABLE : USB Cable
DRIVER : USB UPS Driver
UPSMODE : Stand Alone
STARTTIME: 2020-02-22 21:09:09 +0000
MODEL : Back-UPS ES 550G
STATUS : ONLINE
LINEV : 236.0 Volts
LOADPCT : 1.0 Percent
BCHARGE : 100.0 Percent
TIMELEFT : 40.6 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME : 0 Seconds
SENSE : Medium
LOTRANS : 180.0 Volts
HITRANS : 266.0 Volts
ALARMDEL : 30 Seconds
BATTV : 13.6 Volts
LASTXFER : Unacceptable line voltage changes
NUMXFERS : 0
TONBATT : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
STATFLAG : 0x05000008
SERIALNO : 5B1825T25904
BATTDATE : 2018-06-23
NOMINV : 230 Volts
NOMBATTV : 12.0 Volts
FIRMWARE : 870.O4 .I USB FW:O4
END APC : 2020-02-25 19:44:48 +0000

Cela prouvera déjà que l’UPS communique bien

Bonjour,

j’ai comme réponse a /sbin/apcaccess status 127.0.0.1:3551
Error contacting apcupsd @ 127.0.0.1:3551: Connection refused

Y’a un problème quelque part :neutral_face:

Vérifie si l’UPS est bien présente dans la site des périphériques usb
lsusb

Bus 001 Device 005: ID 0658:0200 Sigma Designs, Inc.
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 008: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 001 Device 007: ID 04e8:8001 Samsung Electronics Co., Ltd Handheld

Il est bien reconnu.

Bus 001 Device 008: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle ( HCI mode)
Bus 001 Device 007: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 001 Device 009: ID 1cf1:0030 Dresden Elektronik
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub

C’est déjà une bonne chose

Merci Christian

Du coup il est reconnu par la smart, mais pourquoi jeedom n’arrive pas a le trouver.

J’ai toujours ça dan mes logs

E: dpkg was interrupted, you must manually run ‹ sudo dpkg --configure -a › to correct the problem.
cp: cannot stat ‹ /etc/apcupsd/apcupsd.conf ›: No such file or directory
sed: can’t read /etc/apcupsd/apcupsd.conf: No such file or directory
sed: can’t read /etc/apcupsd/apcupsd.conf: No such file or directory
sed: can’t read /etc/apcupsd/apcupsd.conf: No such file or directory
sed: can’t read /etc/apcupsd/apcupsd.conf: No such file or directory
Fichier de conf modifié
sed: can’t read /etc/default/apcupsd: No such file or directory
cp: cannot stat ‹ /etc/apcupsd/apccontrol ›: No such file or directory
Job for apcupsd.service failed because the control process exited with error code.
See « systemctl status apcupsd.service » and « journalctl -xe » for details.

:neutral_face:

Et quand je tape sudo dpkg --configure -a en ssh

ça fini par « File to patch: »
et attend une action de ma part.

Je ne sais pas quoi faire.

Merci encore

Vu ton premier log, le plugin n’y est pour rien
Ton système est dans un état qu’il faut corriger avant de pouvoir installer n’importe quelle dépendance de n’importe quel plugin

C’est ca qui passe pas :

Setting up setup-odroid (0.0.1-51) …

Si t’es sur smart, le mieux est un ticket au support

Ticket ouvert ce matin
Réponse en début de journée.

Problème résolu :grin:

Vous êtes au top :+1:

MERCI