Probleme installation dependances plugin solarman

Bonjour à tous,

Je cherche à installer le plugin Solarman.
Les dépendances semblent s’installer correctement mais le statut reste NOK.
Ma version jeedom est 4.4.7.
Je suis un novice complet, je suis incapable d’interpréter les problemes dans le LOG. Si quelqu’un peut m’éclairer ?
Merci d’avance

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_solarman
+ echo 1
+ echo 2
++ cut -f 2-
++ find /usr/local/lib/python2.7/dist-packages/ /usr/local/lib/python3.9/dist-packages/ -mindepth 1 -maxdepth 1 -type d -exec du -ks '{}' +
++ awk '$1 <= 4'
+ RESULTTODELETE=
++ echo ''
++ sed 's, ,\ ,g'
+ RESULTTODELETE2=
+ echo ''
+ xargs rm -rf
+ echo 3
+ sudo pip3 cache purge
Files removed: 74
+ echo 4
+ sudo pip3 install --upgrade pip
Requirement already satisfied: pip in /usr/local/lib/python3.9/dist-packages (24.1.2)
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead:  Use the --root-user-action option if you know what you are doing and want to suppress this warning.
+ echo 5
+ sudo python3 -m pip install --force-reinstall --upgrade pyyaml
Collecting pyyaml
Downloading PyYAML-6.0.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (2.1 kB)
Downloading PyYAML-6.0.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (731 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 731.8/731.8 kB 1.6 MB/s eta 0:00:00
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
Installing collected packages: pyyaml
Attempting uninstall: pyyaml
Found existing installation: PyYAML 6.0.1
Uninstalling PyYAML-6.0.1:
Successfully uninstalled PyYAML-6.0.1
Successfully installed pyyaml-6.0.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: htps://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
+ echo 6
+ sudo python3 -m pip install --force-reinstall --upgrade pyudev
Collecting pyudev
Downloading pyudev-0.24.3-py3-none-any.whl.metadata (4.6 kB)
Downloading pyudev-0.24.3-py3-none-any.whl (62 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 62.7/62.7 kB 1.1 MB/s eta 0:00:00
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
Installing collected packages: pyudev
Attempting uninstall: pyudev
Found existing installation: pyudev 0.24.3
Uninstalling pyudev-0.24.3:
Successfully uninstalled pyudev-0.24.3
Successfully installed pyudev-0.24.3
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
+ echo 7
+ sudo python3 -m pip install --force-reinstall --upgrade serial
Collecting serial
Downloading serial-0.0.97-py2.py3-none-any.whl.metadata (889 bytes)
Collecting future>=0.17.1 (from serial)
Downloading future-1.0.0-py3-none-any.whl.metadata (4.0 kB)
Collecting pyyaml>=3.13 (from serial)
Using cached PyYAML-6.0.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (2.1 kB)
Collecting iso8601>=0.1.12 (from serial)
Downloading iso8601-2.1.0-py3-none-any.whl.metadata (3.7 kB)
Downloading serial-0.0.97-py2.py3-none-any.whl (40 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 40.9/40.9 kB 836.3 kB/s eta 0:00:00
Downloading future-1.0.0-py3-none-any.whl (491 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 491.3/491.3 kB 2.9 MB/s eta 0:00:00
Downloading iso8601-2.1.0-py3-none-any.whl (7.5 kB)
Using cached PyYAML-6.0.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (731 kB)
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
Installing collected packages: pyyaml, iso8601, future, serial
Attempting uninstall: pyyaml
Found existing installation: PyYAML 6.0.1
Uninstalling PyYAML-6.0.1:
Successfully uninstalled PyYAML-6.0.1
Attempting uninstall: iso8601
Found existing installation: iso8601 2.1.0
Uninstalling iso8601-2.1.0:
Successfully uninstalled iso8601-2.1.0
Attempting uninstall: future
Found existing installation: future 1.0.0
Uninstalling future-1.0.0:
Successfully uninstalled future-1.0.0
Attempting uninstall: serial
Found existing installation: serial 0.0.97
Uninstalling serial-0.0.97:
Successfully uninstalled serial-0.0.97
Successfully installed future-1.0.0 iso8601-2.1.0 pyyaml-6.0.1 serial-0.0.97
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: htps://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
+ echo 8
+ sudo python3 -m pip install --force-reinstall --upgrade requests
Collecting requests
Downloading requests-2.32.3-py3-none-any.whl.metadata (4.6 kB)
Collecting charset-normalizer<4,>=2 (from requests)
Downloading charset_normalizer-3.3.2-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (33 kB)
Collecting idna<4,>=2.5 (from requests)
Downloading idna-3.7-py3-none-any.whl.metadata (9.9 kB)
Collecting urllib3<3,>=1.21.1 (from requests)
Downloading urllib3-2.2.2-py3-none-any.whl.metadata (6.4 kB)
Collecting certifi>=2017.4.17 (from requests)
Downloading certifi-2024.7.4-py3-none-any.whl.metadata (2.2 kB)
Downloading requests-2.32.3-py3-none-any.whl (64 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 64.9/64.9 kB 1.5 MB/s eta 0:00:00
Downloading certifi-2024.7.4-py3-none-any.whl (162 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 163.0/163.0 kB 2.1 MB/s eta 0:00:00
Downloading charset_normalizer-3.3.2-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (138 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 138.3/138.3 kB 2.0 MB/s eta 0:00:00
Downloading idna-3.7-py3-none-any.whl (66 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 66.8/66.8 kB 1.2 MB/s eta 0:00:00
Downloading urllib3-2.2.2-py3-none-any.whl (121 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 121.4/121.4 kB 2.3 MB/s eta 0:00:00
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
Installing collected packages: urllib3, idna, charset-normalizer, certifi, requests
Attempting uninstall: urllib3
Found existing installation: urllib3 2.2.2
Uninstalling urllib3-2.2.2:
Successfully uninstalled urllib3-2.2.2
Attempting uninstall: idna
Found existing installation: idna 3.7
Uninstalling idna-3.7:
Successfully uninstalled idna-3.7
Attempting uninstall: charset-normalizer
Found existing installation: charset-normalizer 3.3.2
Uninstalling charset-normalizer-3.3.2:
Successfully uninstalled charset-normalizer-3.3.2
Attempting uninstall: certifi
Found existing installation: certifi 2024.7.4
Uninstalling certifi-2024.7.4:
Successfully uninstalled certifi-2024.7.4
Attempting uninstall: requests
Found existing installation: requests 2.32.3
Uninstalling requests-2.32.3:
Successfully uninstalled requests-2.32.3
Successfully installed certifi-2024.7.4 charset-normalizer-3.3.2 idna-3.7 requests-2.32.3 urllib3-2.2.2
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: htps://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
+ echo 9
+ sudo python3 -m pip install --force-reinstall --upgrade umodbus
Collecting umodbus
Downloading uModbus-1.0.4-py2.py3-none-any.whl.metadata (5.2 kB)
Collecting pyserial~=3.4 (from umodbus)
Downloading pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB)
Downloading uModbus-1.0.4-py2.py3-none-any.whl (31 kB)
Downloading pyserial-3.5-py2.py3-none-any.whl (90 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 90.6/90.6 kB 1.6 MB/s eta 0:00:00
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
Installing collected packages: pyserial, umodbus
Attempting uninstall: pyserial
Found existing installation: pyserial 3.5
Uninstalling pyserial-3.5:
Successfully uninstalled pyserial-3.5
Attempting uninstall: umodbus
Found existing installation: uModbus 1.0.4
Uninstalling uModbus-1.0.4:
Successfully uninstalled uModbus-1.0.4
Successfully installed pyserial-3.5 umodbus-1.0.4
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: htps://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
+ echo 10
+ sudo systemctl restart apache2
+ echo 11
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end solarman
+ echo 12
+ rm /tmp/jeedom_install_in_progress_solarman
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Informations Jeedom Luna

Core : 4.4.7 (V4-stable)
DNS Jeedom Luna : oui

Plugin : Solarman
Version : 2024-07-13 10:21:16 (stable)

Informations complémentaires
OS: debian 11 on Luna ; PHP: 7.4.33 ; Python: 3.9.2
Solarman: v unknown ; cmds: 0

Bonjour,

Les dépendances n’ont aucun soucis, tout est installé.

Mettez à jour jeedom core, cela fonctionnera après.
Pour les détails du pourquoi, cherchez sur l’erreur. Il y a un post sur community qui explique en détail: « Error parsing dependencies of gpg: Invalid version »

Edit: le voici

C’est toujours utile de d’abord chercher le message d’erreur sur community avant de poser la question
De même que mettre à jour en dernière version pour s’assurer que le soucis n’est pas déjà réglé.

1 « J'aime »

Bonjour,

Oui j’avais bien trouvé ce post et bien fouillé sur le forum avant de poser ma question. Mais je ne comprends pas tout => D’ou le gros doute.
J’avais un autre problème pour la mise a jours du core que j’ai résolu => j’ai finalement pu mettre a jour le core et tout est rentré dans l’ordre.
En tout cas, merci beaucoup pour votre retour très rapide qui m’a permis d’avancer.
Bonne journée

Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.