Pb de ttyUSB

rjcb · Novembre 5, 2024, 10:52

Hello,

J’ai rajouté un device USB sur mon proxmox et depuis souci de communication avec la VMC:

root@jeedom:~# ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 Nov  5 11:44 usb-0658_0200-if00 -> ../../ttyACM1
lrwxrwxrwx 1 root root 13 Nov  5 11:43 usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2122345-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Nov  5 11:43 usb-FTDI_FT232R_USB_UART_A702OS2Y-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 Nov  5 11:43 usb-HUAWEI_Technology_HUAWEI_Mobile_1234567890ABCDEF-if00-port0 -> ../../ttyUSB1
lrwxrwxrwx 1 root root 13 Nov  5 11:43 usb-HUAWEI_Technology_HUAWEI_Mobile_1234567890ABCDEF-if02-port0 -> ../../ttyUSB3
lrwxrwxrwx 1 root root 13 Nov  5 11:43 usb-HUAWEI_Technology_HUAWEI_Mobile_1234567890ABCDEF-if03-port0 -> ../../ttyUSB4
lrwxrwxrwx 1 root root 13 Nov  5 11:43 usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0 -> ../../ttyUSB2
root@jeedom:~#

Ici pour la VMC c’est le USB0.
Dans les logs j’ai ceci:

[2024-11-05 11:47:29] DEBUG  : get Remote Serial Device...
[2024-11-05 11:47:30] DEBUG  : SSH exec:for sysdevpath in $(find /sys/bus/usb/devices/usb*/ -name dev); do syspath="${sysdevpath%/dev}"; devname="$(udevadm info -q name -p $syspath)"; [[ "$devname" == "bus/"* ]] && continue; echo "/dev/$devname;"; done => /dev/ttyACM0; /dev/ttyACM1; /dev/sg1; /dev/sr0; /dev/bsg/7:0:0:0; /dev/ttyUSB3; /dev/ttyUSB1; /dev/sg2; /dev/sdb; /dev/bsg/8:0:0:0; /dev/ttyUSB4; /dev/cdc-wdm0; /dev/ttyUSB0; /dev/gpiochip0; /dev/ttyUSB2; /dev/input/event3; /dev/input/mouse2; /dev/hidraw0;
[2024-11-05 11:47:30] DEBUG  : Devices:'/dev/ttyACM0;/dev/ttyACM1;/dev/sg1;/dev/sr0;/dev/bsg/7:0:0:0;/dev/ttyUSB3;/dev/ttyUSB1;/dev/sg2;/dev/sdb;/dev/bsg/8:0:0:0;/dev/ttyUSB4;/dev/cdc-wdm0;/dev/ttyUSB0;/dev/gpiochip0;/dev/ttyUSB2;/dev/input/event3;/dev/input/mouse2;/dev/hidraw0;'
[2024-11-05 11:47:30] INFO  : (Re)starting remote service...
[2024-11-05 11:47:30] DEBUG  : Listening to topic:'zehnder2mqtt'
[2024-11-05 11:47:31] DEBUG  : SSH exec:sudo systemctl restart zehnder2mqtt.service =>
[2024-11-05 11:47:31] INFO  : start successfully executed, wait 1s
[2024-11-05 11:47:31] DEBUG  : handle Mqtt Message:{"zehnder2mqtt":{"461":{"LWT":"online","config":{"version":"0.1","serial_port":"\/dev\/ttyUSB1","mqtt_qos":1,"mqtt_retain":false,"log_level":"INFO"}}}}
[2024-11-05 11:47:31] INFO  : LWT update:online
[2024-11-05 11:47:31] INFO  : config update:{"version":"0.1","serial_port":"\/dev\/ttyUSB1","mqtt_qos":1,"mqtt_retain":false,"log_level":"INFO"}
[2024-11-05 11:47:32] INFO  : Récupération du log du service distant
[2024-11-05 11:47:32] DEBUG  : getRemoteLog: /tmp/zehnder2mqtt.log to /var/www/html/core/class/../../log/vmczehnder_VMC
[2024-11-05 11:47:32] DEBUG  : get file from 192.168.1.12
[2024-11-05 11:50:02] INFO  : Récupération du log du service distant
[2024-11-05 11:50:02] DEBUG  : getRemoteLog: /tmp/zehnder2mqtt.log to /var/www/html/core/class/../../log/vmczehnder_VMC
[2024-11-05 11:50:02] DEBUG  : get file from 192.168.1.12

Pourquoi il prend le USB1 ?

config update:{"version":"0.1","serial_port":"\/dev\/ttyUSB1","mqtt_qos":1,"mqtt_retain":false,"log_level":"INFO"

Merci

Mips · Novembre 5, 2024, 11:25

Bonjour,

parce que c’est ce qui est configuré.

rjcb · Novembre 5, 2024, 11:43

Mips · Novembre 5, 2024, 11:47

ca aide de voir la config

donc il ne suffit de choisir le port dans la liste s’il y a un changement à faire, il faut sauvegarder évidemment mais aussi envoyer la configuration en cliquant sur le bouton « configurer le service »

rjcb · Novembre 5, 2024, 12:52

yes.

J’avais oublié le « envoyer la configuration » et un souci du coup:

[2024-11-05 13:49:42] ERROR  : Impossible d'envoyer la configuration
[2024-11-05 13:49:46] DEBUG  : mqtt2 info:{"ip":"192.168.1.12","port":"1883","protocol":"mqtt","user":"jeedom","password":"xxx"}
[2024-11-05 13:49:46] DEBUG  : Remote config: {"serial_port":"\/dev\/ttyUSB0","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-11-05 13:49:46] DEBUG  : send file to 192.168.1.12
[2024-11-05 13:49:46] ERROR  : Impossible d'envoyer la configuration

Je suis pourtant certain du user et pwd. Le 192.168.1.12 est le jeedom lui même.
Quand je retire un device USB la com fonctionne, bizarre

Mips · Novembre 5, 2024, 1:12

c’est que l’utilisateur n’a pas les droits pour écrire dans /tmp/zehnder2mqtt/ alors.

je ne comprend pas ce que ca veut dire

rjcb · Novembre 5, 2024, 2:02

J’ai testé ceci :

Mais cela n’agit pas sur le rep du plugin, je vais le faire à la mano

rjcb · Novembre 5, 2024, 2:05

normal, pas de rep

root@jeedom:~# cd /tmp
root@jeedom:/tmp# ls
adb.0.log
jeedom
runtime-root
systemd-private-4ed15f5afa92400aad5c5ee9fb0be2d2-ModemManager.service-DDU9Fg
systemd-private-4ed15f5afa92400aad5c5ee9fb0be2d2-ntp.service-shrhFf
systemd-private-4ed15f5afa92400aad5c5ee9fb0be2d2-systemd-logind.service-zI2EJg
yarn--1730803481600-0.8616540044873899
zehnder2mqtt.log
root@jeedom:/tmp#

du coup un coup de bouton et le rep est créé, je vais tester

rjcb · Novembre 5, 2024, 2:11

je dois avoir un souci de com je pense, bizarre:

[2024-11-05 15:09:43]WARNING : Changing the ventilation to 3 went wrong, did not receive an ACK after the set command
[2024-11-05 15:09:45]WARNING : get_ventilation_status function could not get serial data
[2024-11-05 15:09:47]WARNING : get_temp function could not get serial data
[2024-11-05 15:09:49]WARNING : get_ventilation_status function could not get serial data
[2024-11-05 15:09:51]WARNING : get_filter_status function could not get serial data
[2024-11-05 15:09:53]WARNING : get_fan_status function could not get serial data
[2024-11-05 15:09:55]WARNING : get_bypass_control function could not get serial data
[2024-11-05 15:09:57]WARNING : get_valve_status function could not get serial data
[2024-11-05 15:09:58] INFO  : Successfully connected to MQTT server
[2024-11-05 15:09:58] INFO  : Successfully subscribed to the MQTT topics
[2024-11-05 15:09:59] INFO  : Refresh hrv config
[2024-11-05 15:10:01]WARNING : get_bootloader_data function could not get serial data

rjcb · Novembre 5, 2024, 3:55

cela progresse

[2024-11-05 16:54:52]WARNING : Checksum doesn't match (173 vs 128). Message ignored
[2024-11-05 16:54:52]WARNING : get_operating_hours function could not get serial data
[2024-11-05 16:54:59]WARNING : Checksum doesn't match (45 vs 0). Message ignored
[2024-11-05 16:54:59]WARNING : get_temp function could not get serial data
[2024-11-05 16:55:01]WARNING : Checksum doesn't match (173 vs 0). Message ignored
[2024-11-05 16:55:01]WARNING : get_ventilation_status function could not get serial data

rjcb · Novembre 6, 2024, 1:15

redémarrage de la VMC est tout est rentré dans l’ordre

rjcb · Novembre 7, 2024, 8:10

Je ne c’est pas si j’ouvre un nouveau sujet.
Je viens de remarquer que la commande vitesse lente ne fonctionne pas

La commande semble ne pas poser d’erreur, mais aucun impact sur la vitesse de la VMC

[2024-11-07 09:09:24] DEBUG  : handle Mqtt Message:{"zehnder2mqtt":{"461":{"values":{"fanSpeed":2,"intakeFanActive":"True"}}}}
[2024-11-07 09:09:25] INFO  : Changement de la vitesse de ventilation sur:1
[2024-11-07 09:09:26] DEBUG  : handle Mqtt Message:{"zehnder2mqtt":{"461":{"values":{"filterError":0}}}}
[2024-11-07 09:09:30] DEBUG  : handle Mqtt Message:{"zehnder2mqtt":{"461":{"values":{"extractLevel0":15,"extractLevel1":35,"extractLevel2":50}}}}
[2024-11-07 09:09:30] DEBUG  : Update config extractLevel0
[2024-11-07 09:09:30] DEBUG  : Update config extractLevel1
[2024-11-07 09:09:30] DEBUG  : Update config extractLevel2
[2024-11-07 09:09:30] DEBUG  : handle Mqtt Message:{"zehnder2mqtt":{"461":{"values":{"extractLevel3":70,"extractLevelCurrent":50,"supplyLevel0":15}}}}
[2024-11-07 09:09:30] DEBUG  : Update config extractLevel3
[2024-11-07 09:09:30] DEBUG  : Update config supplyLevel0
[2024-11-07 09:09:30] DEBUG  : handle Mqtt Message:{"zehnder2mqtt":{"461":{"values":{"supplyLevel1":35,"supplyLevel2":50,"supplyLevel3":70}}}}
[2024-11-07 09:09:30] DEBUG  : Update config supplyLevel1
[2024-11-07 09:09:30] DEBUG  : Update config supplyLevel2
[2024-11-07 09:09:30] DEBUG  : Update config supplyLevel3
[2024-11-07 09:09:31] DEBUG  : handle Mqtt Message:{"zehnder2mqtt":{"461":{"values":{"supplyLevelCurrent":50,"fanSpeed":2,"intakeFanActive":"True"}}}}
[2024-11-07 09:09:33] DEBUG  : handle Mqtt Message:{"zehnder2mqtt":{"461":{"values":{"fanInject":50}}}}
[2024-11-07 09:09:33] DEBUG  : handle Mqtt Message:{"zehnder2mqtt":{"461":{"values":{"fanExtract":50,"fanInjectRPM":1588,"fanExtractRPM":1665}}}}

Idem pour le mode absent. Avez-vous une idée ?

system · Novembre 8, 2024, 8:10

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