Je ne sais pas ce que j’ai encore foutu mais mon plugin est KO. Mon Jeedom est sur une VM ainsi que la clé GCE:
J’ai refait l’install et voici les logs:
[2024-05-21 10:10:37]INFO : Compression du dossier local:'/var/www/html/plugins/vmczehnder/core/class/../../resources/zehnder2mqtt/
[2024-05-21 10:10:37]INFO : Envoi du fichier /tmp/jeedom/vmczehnder/folder-zehnder2mqtt.tar.gz
[2024-05-21 10:10:37]DEBUG : send file to 127.0.0.1
[2024-05-21 10:10:37]INFO : Décompression
[2024-05-21 10:10:38]DEBUG : SSH exec:mkdir /home => mkdir: cannot create directory ‘/home’: File exists
[2024-05-21 10:10:38]DEBUG : SSH exec:mkdir /home/jc => mkdir: cannot create directory ‘/home/jc’: File exists
[2024-05-21 10:10:38]DEBUG : SSH exec:rm -R /home/jc/zehnder2mqtt =>
[2024-05-21 10:10:38]DEBUG : SSH exec:mkdir /home/jc/zehnder2mqtt =>
[2024-05-21 10:10:38]DEBUG : SSH exec:tar -zxf /home/jc/folder-zehnder2mqtt.tar.gz -C /home/jc/zehnder2mqtt =>
[2024-05-21 10:10:38]DEBUG : SSH exec:rm /home/jc/folder-zehnder2mqtt.tar.gz =>
[2024-05-21 10:10:38]INFO : Installation des dépendances
[2024-05-21 10:10:38]DEBUG : SSH exec:sudo rm /tmp/vmcd_update =>
[2024-05-21 10:10:40]DEBUG : SSH exec:bash /home/jc/zehnder2mqtt/install.bash >> /tmp/vmcd_update 2>&1 =>
[2024-05-21 10:10:40]INFO : Envoi de la configuration
[2024-05-21 10:10:40]DEBUG : mqtt2 info:{"ip":"192.168.1.12","port":"1883","user":"jeedom","password":"xxx"}
[2024-05-21 10:10:40]DEBUG : Remote config: {"serial_port":"\/dev\/ttyUSB1","mqtt_server":"192.168.1.12","mqtt_port":1883,"mqtt_username":"jeedom","mqtt_password":"xxx","mqtt_qos":1,"mqtt_retain":false,"mqtt_base_topic":"zehnder2mqtt","mqtt_hrv_topic":"461","log_level":"INFO"}
[2024-05-21 10:10:41]DEBUG : send file to 127.0.0.1
[2024-05-21 10:10:41]DEBUG : SSH exec:cd /home/jc/zehnder2mqtt/; sudo make install => zehnder2mqtt is installed and enabled as a systemd service, start it with the command 'sudo systemctl start zehnder2mqtt.service'
[2024-05-21 10:10:41]INFO : Récupération du log...
[2024-05-21 10:10:41]DEBUG : getRemoteLog: /tmp/vmcd_update to /var/www/html/core/class/../../log/vmczehnder_VMC_update
[2024-05-21 10:10:41]DEBUG : get file from 127.0.0.1
[2024-05-21 10:10:41]INFO : (Re)starting remote service...
[2024-05-21 10:10:41]DEBUG : Listening to topic:'zehnder2mqtt'
[2024-05-21 10:10:41]DEBUG : SSH exec:sudo systemctl restart zehnder2mqtt.service =>
[2024-05-21 10:10:41]INFO : start successfully executed, wait 1s
[2024-05-21 10:10:42]INFO : Récupération du log du service distant
[2024-05-21 10:10:43]DEBUG : getRemoteLog: /tmp/zehnder2mqtt.log to /var/www/html/core/class/../../log/vmczehnder_VMC
[2024-05-21 10:10:43]DEBUG : get file from 127.0.0.1
Les logs d’install:
[2024-05-21 10:10:38] *********************************
[2024-05-21 10:10:38] * update all packages on the pi *
[2024-05-21 10:10:38] *********************************
[2024-05-21 10:10:38] Hit:1 http://deb.debian.org/debian bullseye InRelease
[2024-05-21 10:10:38] Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
[2024-05-21 10:10:38] Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
[2024-05-21 10:10:38] Hit:4 http://phoscon.de/apt/deconz bullseye InRelease
[2024-05-21 10:10:38] Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease
[2024-05-21 10:10:39] Reading package lists...
[2024-05-21 10:10:39] ***********************************
[2024-05-21 10:10:39] * install dependencies if needed *
[2024-05-21 10:10:39] ***********************************
[2024-05-21 10:10:39] Reading package lists...
[2024-05-21 10:10:39] Building dependency tree...
[2024-05-21 10:10:39] Reading state information...
[2024-05-21 10:10:40] python3-serial is already the newest version (3.5~b0-1).
[2024-05-21 10:10:40] python3-pip is already the newest version (20.3.4-4+deb11u1).
[2024-05-21 10:10:40] python3-yaml is already the newest version (5.3.1-5).
[2024-05-21 10:10:40] 0 upgraded, 0 newly installed, 0 to remove and 63 not upgraded.
[2024-05-21 10:10:40] Collecting paho-mqtt>=2.0.0 (from -r requirements.txt (line 1))
[2024-05-21 10:10:40] Using cached paho_mqtt-2.1.0-py3-none-any.whl.metadata (23 kB)
[2024-05-21 10:10:40] Requirement already satisfied: pyserial==3.5 in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 2)) (3.5)
[2024-05-21 10:10:40] Collecting pyyaml==6.0.1 (from -r requirements.txt (line 3))
[2024-05-21 10:10:40] Using cached PyYAML-6.0.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.1 kB)
[2024-05-21 10:10:40] Using cached PyYAML-6.0.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (738 kB)
[2024-05-21 10:10:40] Using cached paho_mqtt-2.1.0-py3-none-any.whl (67 kB)
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.0 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of gpg or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at https://github.com/pypa/pip/issues/12063
[2024-05-21 10:10:40] Installing collected packages: pyyaml, paho-mqtt
ERROR: Cannot uninstall 'PyYAML'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.
[2024-05-21 10:10:40] Attempting uninstall: pyyaml
[2024-05-21 10:10:40] Found existing installation: PyYAML 5.3.1
[notice] A new release of pip is available: 23.3.1 -> 24.0
[notice] To update, run: python3 -m pip install --upgrade pip
[2024-05-21 10:10:40] ********************
[2024-05-21 10:10:40] * install finished *
[2024-05-21 10:10:40] ********************
J’arrive bien à me connecter en SSH avec le user jc
Le device est le 067b:2303 mais ce que je ne sais pas c’est si il est en USB0 ou USB1. J’ai testé les 2 sans succès:
Pour les logs j’ai que cela en mode debug, rien dans ;
Pour l’USB j’ai débranché et j’ai conservé celui présent pour le mettre dans la conf.
Ce que je voulais dire, est parfois lorsque j’ai les 2 branchés le dernier digit de l’USBx s’inverse.
root@jeedom:~# lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 006: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port / Mobile Action MA-8910P
C’est pourquoi, quand cela est possible, il vaut mieux passer par l’ID.
Sinon, sur pi tu peux fixer le port usb, cela doit aussi etre possible sur ta machine mais cela dépasse mes compétences.
yep mais là en fait c’est le plugin qui récupère la liste des devices usb sur un pi en principe en remote car il faut un pi branché physiquement à la vmc qui n’est pas forcément dans le même local que la machine jeedom et je n’ai pas encore modifié la logique pour passer par le serial-by-id; faut que je change ça
(ici j’ai l’impression que tout est installé en local mais ce n’est pas vmt prévu par le plugin)
Toujours a tenter de trouver pourquoi le plugin ne veut plus marcher.
Je suis repartis de 0 avec l’installation du plugin:
[2024-06-11 16:38:03] ***********************************
[2024-06-11 16:38:03] Reading package lists...
[2024-06-11 16:38:03] Building dependency tree...
[2024-06-11 16:38:03] Reading state information...
[2024-06-11 16:38:03] python3-serial is already the newest version (3.5~b0-1).
[2024-06-11 16:38:03] python3-pip is already the newest version (20.3.4-4+deb11u1).
[2024-06-11 16:38:03] python3-yaml is already the newest version (5.3.1-5).
[2024-06-11 16:38:03] 0 upgraded, 0 newly installed, 0 to remove and 65 not upgraded.
[2024-06-11 16:38:04] Collecting paho-mqtt>=2.0.0 (from -r requirements.txt (line 1))
[2024-06-11 16:38:04] Using cached paho_mqtt-2.1.0-py3-none-any.whl.metadata (23 kB)
[2024-06-11 16:38:04] Requirement already satisfied: pyserial==3.5 in /usr/local/lib/python3.9/dist-packages (from -r requirements.txt (line 2)) (3.5)
[2024-06-11 16:38:04] Collecting pyyaml==6.0.1 (from -r requirements.txt (line 3))
[2024-06-11 16:38:04] Using cached PyYAML-6.0.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.1 kB)
[2024-06-11 16:38:04] Using cached PyYAML-6.0.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (738 kB)
[2024-06-11 16:38:04] Using cached paho_mqtt-2.1.0-py3-none-any.whl (67 kB)
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of gpg or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at https://github.com/pypa/pip/issues/12063
[2024-06-11 16:38:04] Installing collected packages: pyyaml, paho-mqtt
ERROR: Cannot uninstall 'PyYAML'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.
[2024-06-11 16:38:04] Attempting uninstall: pyyaml
[2024-06-11 16:38:04] Found existing installation: PyYAML 5.3.1
[2024-06-11 16:38:04] ********************
[2024-06-11 16:38:04] * install finished *
[2024-06-11 16:38:04] ********************
Premier pb:
ERROR: Cannot uninstall ‹ PyYAML ›. mais j’ai Found existing installation: PyYAML 5.3.
Faut il comprendre que l’installation est quand meme OK ?
Le Statut du service lui est toujours KO.
Pour info Jeedom est sur la meme VM que l’install coté VMC.
la dernière version installe le service « distant » dans un environnement virtuel (requis pour debian12) et du coup toutes les dépendances lui sont propres sans interférences tierces.
Donc tu avais probablement qlqch qui s’est installé sur ton jeedom et qui a cassé les dépendances de ce service.
Je n’avais pas compris jusque hier que c’était installé sur la même machine que jeedom, ce qui est déconseillé, cela m’aurait p-e mis sur la voie plus rapidement.
