Connection refused depuis mise à jour Debian bullseye

belgotux · Janvier 23, 2024, 5:53

Hello,

Depuis la mise à jour vers Debian 11 depuis l’iso x64 officielle (j’étais en Debian 10 toujours…), je n’ai plus de remontée depuis mon solaredge.
Je n’avais pas encore eu le temps de l’analyser, mais voilà ce que je constate dans les logs :

[2024-01-23 17:53:53][ERROR] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
Traceback (most recent call last):
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 89, in poll
values = self._scan_value_range(table, group, self._scan_batching)
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 186, in _scan_value_range
raise ValueError("Failed to read {} {} table registers starting from {}: {}".format(count, table, start, result))
ValueError: Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-23 17:53:53][ERROR] : Connection to (192.168.9.136, 1502) failed: [Errno 111] Connection refused
[2024-01-23 17:53:53][ERROR] : Connection to (192.168.9.136, 1502) failed: [Errno 111] Connection refused

Je suis passé par la case réinstallation des dépendances, restart du daemon et même reboot de la machine, c’est la même chose

Vu le nom de l’erreur, j’ai dans le doute de mon réseau mis la machine jeedom et le solaredge sur le même réseau ce soir via un bête switch et j’ai également le problème de connection refused. Rien n’avait changé de toute façon.

J’ai arrêté le daemon et je me suis connecté depuis mon pc avec modbus client X et cela fonctionne parfaitement pour une adresse seule ou un start sur la 40050 et un nombre de 30 adresses :

Et voici le log du daemon en mode debug :

[2024-01-23 18:50:48][DEBUG] : Connection to Modbus server established. Socket ('192.168.9.11', 48950)
[2024-01-23 18:50:48][DEBUG] : Current transaction state - IDLE
[2024-01-23 18:50:48][DEBUG] : Running transaction 1
[2024-01-23 18:50:48][DEBUG] : SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x0 0x3 0x9c 0x72 0x0 0x1e
[2024-01-23 18:50:48][DEBUG] : New Transaction state "SENDING"
[2024-01-23 18:50:48][DEBUG] : Changing transaction state from "SENDING" to "WAITING FOR REPLY"
[2024-01-23 18:50:50][DEBUG] : Transaction failed. (Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received))
[2024-01-23 18:50:50][DEBUG] : Processing:
[2024-01-23 18:50:50][DEBUG] : Frame check failed, ignoring!!
[2024-01-23 18:50:50][DEBUG] : Getting transaction 1
[2024-01-23 18:50:50][DEBUG] : Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
[2024-01-23 18:50:50][ERROR] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
Traceback (most recent call last):
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 89, in poll
values = self._scan_value_range(table, group, self._scan_batching)
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 186, in _scan_value_range
raise ValueError("Failed to read {} {} table registers starting from {}: {}".format(count, table, start, result))
ValueError: Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-23 18:50:50][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-23 18:50:50][WARNING] : Failed to poll modbus device, attempting to reconnect: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.11.13:1502)]
[2024-01-23 18:50:50][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-25 08:03:25][DEBUG] : Received {"action":"start","eqLogicId":"448","topic":"solaredge","apikey":"hGyLjnXUuuCiOkUwCb7sAkB8Fv62uVEZ7ixuLu9YLrxJnEXOZndeNSWLQAdniEGV"} from ('127.0.0.1', 42330)
[2024-01-25 08:03:25][DEBUG] : Close connection
[2024-01-25 08:03:25][INFO] : Starting modbus4mqtt for 448 and topic solaredge
[2024-01-25 08:03:25][DEBUG] : connect mqtt to 127.0.0.1 on 1883 with user jeedom
[2024-01-25 08:03:25][DEBUG] : will publish to modbus/solaredge
[2024-01-25 08:03:25][DEBUG] : Connection to Modbus server established. Socket ('192.168.9.11', 34256)
[2024-01-25 08:03:25][INFO] : Start polling...
[2024-01-25 08:03:25][INFO] : Connected to MQTT.
[2024-01-25 08:03:35][DEBUG] : Current transaction state - IDLE
[2024-01-25 08:03:35][DEBUG] : Running transaction 1
[2024-01-25 08:03:35][DEBUG] : SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x0 0x3 0x9c 0x72 0x0 0x1e
[2024-01-25 08:03:35][DEBUG] : New Transaction state "SENDING"
[2024-01-25 08:03:35][DEBUG] : Changing transaction state from "SENDING" to "WAITING FOR REPLY"
[2024-01-25 08:03:37][DEBUG] : Transaction failed. (Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received))
[2024-01-25 08:03:37][DEBUG] : Processing:
[2024-01-25 08:03:37][DEBUG] : Frame check failed, ignoring!!
[2024-01-25 08:03:37][DEBUG] : Getting transaction 1
[2024-01-25 08:03:37][DEBUG] : Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
[2024-01-25 08:03:37][ERROR] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
Traceback (most recent call last):
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 89, in poll
values = self._scan_value_range(table, group, self._scan_batching)
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 186, in _scan_value_range
raise ValueError("Failed to read {} {} table registers starting from {}: {}".format(count, table, start, result))
ValueError: Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-25 08:03:37][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-25 08:03:37][WARNING] : Failed to poll modbus device, attempting to reconnect: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.11.13:1502)]

Merci et bonne soirée

anon53349806 · Janvier 23, 2024, 6:05

Voir la config pourrait aider ?
L’etat de mqtt manager ?

la doc dit

4.1) Paramètres de connexion modbus
IP et Port de votre équipement modbus TCP
Actualisation: délai en secondes entre chaque opérations de lecture/écriture sur l’équipement modbus
Offset décalage à appliquer sur les adresses des registres
Longueur du batch: nombre de registres contigus à lire lors de chaque opération de lecture (entre 1 et 100 inclus). Si 1 alors chaque registre sera lû séparément.
Ordre des mots: Uniquement pour les nombres sur 32-bit ou 64-bit, choix entre Big-endian (le défaut) et Little-endian

Mips · Janvier 23, 2024, 6:17

Bonjour,

Et page santé + page config du plugin (au moins pour avoir les versions) + log des dépendances du coup; bref tout ce qui est demandé dans la doc

Pcq en principe la version stable contient ce qu’il faut pour que ca tourne sur debian 11 et suivant.

Et je suis sur debian 11 sur ma prod avec le plugin qui tourne

belgotux · Janvier 25, 2024, 7:05

Meaculpa j’en oublie les bases… Et merci pour votre réactivité, c’est moi qui assure pas du coup

Jeedom v4.3.22 en x64 sous le dernier Debian Officiel Bullseyes tous les plugins en stable sauf modbus2mqtt
Plugin modbus2mqtt beta pour l’integer 32bits du solaredge : version 2023-11-03 01:02:24
mqttmanager est up & running : j’ai aussi jeezzigbee et z-wave js qui tournent et sont ok
mosquitto est ok aussi

Page santé :

Configuration du plugin :

Configuration du solaredge :

Configuration de mqtt manager (mosquitto installé via jmqtt pour des besoins de mqtts et certificat pour mes esp32 sous Tasmota) :

Rien n’a changé au niveau de la configuration de jeedom entre le backup sous Debian 10, installation de Debian11 et restauration du backup.

J’avais plus de log d’installation, j’ai relancé l’installation des dépendances pour en avoir un mais j’ai rien dans Modbus2mqtt_packages

Vous savez quels deb sont nécessaires histoire de faire un dpkg -l pour voir si le problème n’est pas côté installation de dépendances ?

Mips · Janvier 25, 2024, 7:17

Avant de faire des actions manuelles, je peux avoir les logs?

et l’erreur revient en boucle? pcq ce n’est pas impossible qu’il y ai eu un glitch et qu’ensuite ca passe
car sur ta capture le démon tourne

belgotux · Janvier 25, 2024, 7:35

Si je ne me trompe pas, les logs des dépendances sont dans Mobus2mqtt_packages normalement ? Ici il est vide :

Dans /var/log/dpkg.log aucun log d’installation aujourd’hui, les derniers sont ceux du système :

2024-01-24 06:52:17 status unpacked xvfb:amd64 2:1.20.11-1+deb11u11
2024-01-24 06:52:17 status half-configured xvfb:amd64 2:1.20.11-1+deb11u11
2024-01-24 06:52:17 status installed xvfb:amd64 2:1.20.11-1+deb11u11
2024-01-24 06:52:17 trigproc man-db:amd64 2.9.4-2 <none>
2024-01-24 06:52:17 status half-configured man-db:amd64 2.9.4-2
2024-01-24 06:52:22 status installed man-db:amd64 2.9.4-2

Idem dans /var/log/apt/history.log

Start-Date: 2024-01-24  06:52:15
Commandline: /usr/bin/unattended-upgrade
Upgrade: xserver-common:amd64 (2:1.20.11-1+deb11u10, 2:1.20.11-1+deb11u11), xvfb:amd64 (2:1.20.11-1+deb11u10, 2:1.20.11-1+deb11u11)
End-Date: 2024-01-24  06:52:23

Mips · Janvier 25, 2024, 7:37

Donc tu as installé un jeedom vierge en debian 11 et restauré un backup et jamais installé les dépendances?

as-tu essayé de les relancer malgré tout?

belgotux · Janvier 25, 2024, 12:46

Quand il restaure il va chercher les dépendances de tous les plugins, ça a vraiment été du plug&play pour zigbee, zwave, unifi et j’en passe, pas de raison que modbus2mqtt ca ne l’ait pas fait.

Si j’avais relancé les dépendances le 23 janvier durant mes tests, et il me retourne qu’il les a faites sur le bouton orange « Relancer » après quelques secondes. Je m’étais pas encore aperçu qu’il n’avais pas bien fait ou rien fait.

Ce matin quand j’ai répondu, je les ai relancé de nouveau pour avoir des logs, et c’est là que je m’aperçois qu’il y a rien dans les logs, ce qui n’est pas normal. Surtout quand sur la page de config il dit que tout se passe bien. Je vais tester de mettre la version stable et relancer les dépendances, on sait jamais.

Mips · Janvier 25, 2024, 12:51

c’est le core qui gère les dépendances pour ce plugin (comme zigbee & zwave)
c’est qu’il considère qu’il n’y a rien à installer

tu peux faire un pip3 freeze et me donner le résultat?

belgotux · Janvier 25, 2024, 1:11

aiohttp==3.9.1
aiosignal==1.3.1
aiosqlite==0.19.0
async-timeout==4.0.3
attrs==23.2.0
bellows==0.33.1
certifi==2023.11.17
cffi==1.16.0
chardet==4.0.0
charset-normalizer==2.0.12
click==8.1.7
click-log==0.4.0
coloredlogs==15.0.1
colorzero==2.0
crccheck==1.3.0
cryptography==41.0.7
cupshelpers==1.0
dbus-python==1.2.16
distro-info==1.0
fail2ban==0.11.2
frozenlist==1.4.1
gpg===1.14.0-unknown
gpiozero==2.0
humanfriendly==10.0
idna==3.6
iotop==0.6
jsonschema==4.20.0
jsonschema-specifications==2023.12.1
multidict==6.0.4
paho-mqtt==1.6.1
pure-pcapy3==1.0.1
pycairo==1.16.2
pycparser==2.21
pycrypto==2.6.1
pycups==2.0.1
pycurl==7.43.0.6
PyGObject==3.38.0
pyinotify==0.9.6
pymodbus==3.6.3
pyserial==3.5
pyserial-asyncio==0.6
pysmbc==1.0.23
python-apt==2.2.1
pyudev==0.24.1
pyusb==1.2.1
referencing==0.32.1
requests==2.31.0
rpds-py==0.16.2
ruamel.yaml==0.18.5
ruamel.yaml.clib==0.2.8
six==1.16.0
systemd-python==234
tornado==6.4
typing_extensions==4.9.0
unattended-upgrades==0.1
urllib3==2.1.0
voluptuous==0.14.1
xmodem==0.4.7
yarl==1.4.2
zha-quirks==0.0.80
zigpy==0.50.3
zigpy-deconz==0.18.1
zigpy-xbee==0.15.0
zigpy-zigate==0.9.2
zigpy-znp==0.8.2

Et l’installe des dépendances en plugin stable n’a rien donné

Mips · Janvier 25, 2024, 1:27

au fait tu n’as pas répondu à ça

belgotux · Janvier 25, 2024, 1:50

Oui ca reste sur des erreurs en boucle.

Ici j’ai essayé de désactiver le plugin, le supprimer, le réinstaller (stable toujours), il ne me dit rien pour les dépendances. Je fait quand même un relancer les dépendances, c’est très rapide 10sec, je configure le topic et je démarre le daemon.

J’ai créé un device solaredge et un seul registre 40083 en signed 16bits, j’ai toujours la même erreur en tournant 10min :

[2024-01-25 14:31:37][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-25 14:31:37][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-25 14:31:37][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-25 14:31:49][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-25 14:32:01][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:32:13][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:32:25][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:32:37][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:32:49][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:33:01][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:33:13][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:33:25][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:33:37][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:34:01][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:34:13][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:34:25][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:34:37][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:34:49][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:35:01][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:35:13][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:35:25][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:35:37][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:35:49][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:36:01][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:36:13][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:36:25][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:36:37][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:36:49][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:37:01][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:37:13][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:37:25][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:37:37][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:37:49][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:38:01][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:38:13][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:38:25][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:38:37][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:38:49][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:39:01][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:39:13][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:39:25][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:39:37][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:39:49][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:40:01][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:40:13][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:40:25][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:40:37][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:40:49][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:41:01][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:41:14][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:41:26][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:41:38][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:41:50][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:42:02][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:42:14][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:42:26][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:42:38][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:42:50][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:43:02][WARNING] : Failed to read 30 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response
[2024-01-25 14:43:06][WARNING] : Failed to read 10 holding table registers starting from 40080: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-25 14:43:18][WARNING] : Failed to read 10 holding table registers starting from 40080: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response

Mips · Janvier 25, 2024, 2:42

c’est normal que l’ip cible change?

dans le premier log c’était 192.168.9.136
dans le 2eme 192.168.9.11
dans ta capture d’écran c’est 192.168.11.13
et finalement le dernier log c’est la même ip

t’es sur de ta config?

belgotux · Janvier 25, 2024, 3:55

Le 192.168.9.11 c’est jeedom, ça ne change pas.
Le 192.168.11.13 c’est l’ip de solaredge dans son réseau de base pour les produits domotique ayant besoin d’un accès internet.
192.168.9.136 c’est quand j’ai mis le solaredge dans le même range pour faire un test et exclure un problème réseau

EDIT : J’ai regardé un peu aussi dans les erreur il y a question d’une clé api,
Elle correspond bien à cella dans la configuration, mais je vois que la case Accès restreint est cochée par rapport aux autres plugins :

Mais décocher et relancer le daemon ne change rien

Mips · Janvier 25, 2024, 4:44

oui, c’est moi qui force cette configuration

c’était pas vraiment lié mais je devais revoir la façon d’installer les dépendances pour la compatibilité debian 12; du coup j’ai fait ca plus tôt que prévu et une nouvelle beta est dispo (et compatible debian 12 du coup)
essayes celle là, il faudra relancer les dépendances et le log sera dans le fichier xxx_update
le fichier xxx_packages peut être supprimé.

belgotux · Janvier 25, 2024, 8:15

Là j’ai bien eu une installation en cours en cliquant sur relancer

Le log des dépendances :

======================================================================
== 25/01/2024 18:15:52 == Dependencies installation for modbus2mqtt
======================================================================
[  5% ] : Clean apt...
[  9% ] : Clean apt : [  OK  ]
[ 10% ] : Update apt...
[ 19% ] : Update apt : [  OK  ]
[ 20% ] : Install apt packages...
[ 39% ] : Install apt packages : [  OK  ]
[ 40% ] : Creating python 3 virtual environment...
[ 49% ] : Creating python 3 virtual environment : [  OK  ]
[ 50% ] : Setting up virtual environment...
[ 69% ] : Setting up virtual environment : [  OK  ]
[ 70% ] : Install the required python packages...
[ 89% ] : Install the required python packages : [  OK  ]
[ 90% ] : Summary of installed packages...
aiohttp==3.9.1
aiosignal==1.3.1
async-timeout==4.0.3
attrs==23.2.0
certifi==2023.11.17
charset-normalizer==3.3.2
frozenlist==1.4.1
idna==3.6
multidict==6.0.4
paho-mqtt==1.6.1
pkg_resources==0.0.0
pymodbus==3.6.3
requests==2.31.0
ruamel.yaml==0.18.5
ruamel.yaml.clib==0.2.8
urllib3==2.1.0
yarl==1.9.4
[ 99% ] : Summary of installed packages : [  OK  ]
[100% ] : Finished !
======================================================================
== OK == Installation Successful
======================================================================

J’ai redémarré le daemon et puis réactivé le solaredge, mais toujours le souci :

[2024-01-25 20:59:30][ERROR] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
Traceback (most recent call last):
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 89, in poll
values = self._scan_value_range(table, group, self._scan_batching)
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 186, in _scan_value_range
raise ValueError("Failed to read {} {} table registers starting from {}: {}".format(count, table, start, result))
ValueError: Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-25 20:59:30][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-25 20:59:30][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-25 20:59:42][ERROR] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
Traceback (most recent call last):
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 89, in poll
values = self._scan_value_range(table, group, self._scan_batching)
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 186, in _scan_value_range
raise ValueError("Failed to read {} {} table registers starting from {}: {}".format(count, table, start, result))
ValueError: Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-25 20:59:42][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-25 20:59:42][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused

En redémarrant en debug et quelques tours :

[2024-01-25 21:05:46][INFO] : Starting daemon
[2024-01-25 21:05:46][INFO] : Log level: debug
[2024-01-25 21:05:46][DEBUG] : Socket port: 55071
[2024-01-25 21:05:46][DEBUG] : Writing PID 3003132 to /tmp/jeedom/modbus2mqtt/daemon.pid
[2024-01-25 21:05:46][INFO] : Listening on 127.0.0.1:55071
[2024-01-25 21:05:47][INFO] : Signal 15 caught, exiting...
[2024-01-25 21:05:47][INFO] : Listening cancelled
[2024-01-25 21:05:47][INFO] : Ready
[2024-01-25 21:05:52][INFO] : Starting daemon
[2024-01-25 21:05:52][INFO] : Log level: debug
[2024-01-25 21:05:52][DEBUG] : Socket port: 55071
[2024-01-25 21:05:52][DEBUG] : Writing PID 3003193 to /tmp/jeedom/modbus2mqtt/daemon.pid
[2024-01-25 21:05:52][INFO] : Listening on 127.0.0.1:55071
[2024-01-25 21:05:53][INFO] : Ready
[2024-01-25 21:06:12][DEBUG] : Received {"action":"start","eqLogicId":"448","topic":"solaredge","apikey":"bQh1utprub2cwTygjcqCXkmUBTYFsFXlpKM2hsaZBw2U9OtTUbxXZFd0M9KKrGst"} from ('127.0.0.1', 54000)
[2024-01-25 21:06:12][DEBUG] : Close connection
[2024-01-25 21:06:12][INFO] : Starting modbus4mqtt for 448 and topic solaredge
[2024-01-25 21:06:12][DEBUG] : connect mqtt to 127.0.0.1 on 1883 with user jeedom
[2024-01-25 21:06:12][DEBUG] : will publish to modbus/solaredge
[2024-01-25 21:06:12][DEBUG] : Connection to Modbus server established. Socket ('192.168.9.11', 52498)
[2024-01-25 21:06:12][INFO] : Start polling...
[2024-01-25 21:06:12][INFO] : Connected to MQTT.
[2024-01-25 21:06:22][DEBUG] : Current transaction state - IDLE
[2024-01-25 21:06:22][DEBUG] : Running transaction 1
[2024-01-25 21:06:22][DEBUG] : SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x0 0x3 0x9c 0x72 0x0 0x1e
[2024-01-25 21:06:22][DEBUG] : New Transaction state "SENDING"
[2024-01-25 21:06:22][DEBUG] : Changing transaction state from "SENDING" to "WAITING FOR REPLY"
[2024-01-25 21:06:24][DEBUG] : Transaction failed. (Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received))
[2024-01-25 21:06:24][DEBUG] : Processing:
[2024-01-25 21:06:24][DEBUG] : Frame check failed, ignoring!!
[2024-01-25 21:06:24][DEBUG] : Getting transaction 1
[2024-01-25 21:06:24][DEBUG] : Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
[2024-01-25 21:06:24][ERROR] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
Traceback (most recent call last):
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 89, in poll
values = self._scan_value_range(table, group, self._scan_batching)
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 186, in _scan_value_range
raise ValueError("Failed to read {} {} table registers starting from {}: {}".format(count, table, start, result))
ValueError: Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-25 21:06:24][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-25 21:06:24][WARNING] : Failed to poll modbus device, attempting to reconnect: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.11.13:1502)]
[2024-01-25 21:06:24][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-25 21:06:34][DEBUG] : Connection to Modbus server established. Socket ('192.168.9.11', 34170)
[2024-01-25 21:06:34][DEBUG] : Current transaction state - IDLE
[2024-01-25 21:06:34][DEBUG] : Running transaction 1
[2024-01-25 21:06:34][DEBUG] : SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x0 0x3 0x9c 0x72 0x0 0x1e
[2024-01-25 21:06:34][DEBUG] : New Transaction state "SENDING"
[2024-01-25 21:06:34][DEBUG] : Changing transaction state from "SENDING" to "WAITING FOR REPLY"
[2024-01-25 21:06:36][DEBUG] : Transaction failed. (Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received))
[2024-01-25 21:06:36][DEBUG] : Processing:
[2024-01-25 21:06:36][DEBUG] : Frame check failed, ignoring!!
[2024-01-25 21:06:36][DEBUG] : Getting transaction 1
[2024-01-25 21:06:36][DEBUG] : Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
[2024-01-25 21:06:36][ERROR] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
Traceback (most recent call last):
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 89, in poll
values = self._scan_value_range(table, group, self._scan_batching)
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 186, in _scan_value_range
raise ValueError("Failed to read {} {} table registers starting from {}: {}".format(count, table, start, result))
ValueError: Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-25 21:06:36][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-25 21:06:36][WARNING] : Failed to poll modbus device, attempting to reconnect: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.11.13:1502)]
[2024-01-25 21:06:36][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-25 21:06:46][DEBUG] : Connection to Modbus server established. Socket ('192.168.9.11', 36148)
[2024-01-25 21:06:46][DEBUG] : Current transaction state - IDLE
[2024-01-25 21:06:46][DEBUG] : Running transaction 1
[2024-01-25 21:06:46][DEBUG] : SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x0 0x3 0x9c 0x72 0x0 0x1e
[2024-01-25 21:06:46][DEBUG] : New Transaction state "SENDING"
[2024-01-25 21:06:46][DEBUG] : Changing transaction state from "SENDING" to "WAITING FOR REPLY"
[2024-01-25 21:06:48][DEBUG] : Transaction failed. (Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received))
[2024-01-25 21:06:48][DEBUG] : Processing:
[2024-01-25 21:06:48][DEBUG] : Frame check failed, ignoring!!
[2024-01-25 21:06:48][DEBUG] : Getting transaction 1
[2024-01-25 21:06:48][DEBUG] : Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
[2024-01-25 21:06:48][ERROR] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
Traceback (most recent call last):
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 89, in poll
values = self._scan_value_range(table, group, self._scan_batching)
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 186, in _scan_value_range
raise ValueError("Failed to read {} {} table registers starting from {}: {}".format(count, table, start, result))
ValueError: Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-25 21:06:48][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-25 21:06:48][WARNING] : Failed to poll modbus device, attempting to reconnect: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.11.13:1502)]
[2024-01-25 21:06:48][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused

En tout cas merci déjà pour ta percévérance!

Je tenterai bien ce weekend une restauration de mon cpio sur une vm de test, si ça peut aider à comprendre, voir un from scratch sur l’ancienne iso deb10 pour voir si même phénomène

belgotux · Janvier 27, 2024, 1:08

Hello @Mips je reviens avec mes tests, en résumé sur une fresh install debian 11 ça ne fonctionne pas. Je te livre ici mes tests en deb10 et deb11 :

Debian 11 from scratch + Market modbus manager (mêmes options et topic) stable et modbus2mqtt stable :

log l’install des dépendances :

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_modbus2mqtt
+ echo 1
+ echo 2
++ find /usr/local/lib/python3.9/dist-packages/ -mindepth 1 -maxdepth 1 -type d -exec du -ks '{}' +
++ awk '$1 <= 4'
++ cut -f 2-
+ RESULTTODELETE=
++ echo ''
++ sed 's, ,\ ,g'
+ RESULTTODELETE2=
+ echo ''
+ xargs rm -rf
+ echo 3
+ sudo pip3 cache purge
ERROR: No matching packages
+ echo 4
+ sudo pip3 install --upgrade pip
Requirement already satisfied: pip in /usr/lib/python3/dist-packages (20.3.4)
Collecting pip
Downloading pip-23.3.2-py3-none-any.whl (2.1 MB)
Installing collected packages: pip
Attempting uninstall: pip
Found existing installation: pip 20.3.4
Not uninstalling pip at /usr/lib/python3/dist-packages, outside environment /usr
Can't uninstall 'pip'. No files were found to uninstall.
Successfully installed pip-23.3.2
+ echo 5
+ sudo pip3 install --force-reinstall --upgrade pymodbus
Collecting pymodbus
Downloading pymodbus-3.6.3-py3-none-any.whl.metadata (14 kB)
Downloading pymodbus-3.6.3-py3-none-any.whl (205 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 205.2/205.2 kB 3.4 MB/s eta 0:00:00
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
Installing collected packages: pymodbus
Successfully installed pymodbus-3.6.3
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
+ echo 6
+ sudo pip3 install --force-reinstall --upgrade ruamel.yaml
Collecting ruamel.yaml
Downloading ruamel.yaml-0.18.5-py3-none-any.whl.metadata (23 kB)
Collecting ruamel.yaml.clib>=0.2.7 (from ruamel.yaml)
Downloading ruamel.yaml.clib-0.2.8-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.whl.metadata (2.2 kB)
Downloading ruamel.yaml-0.18.5-py3-none-any.whl (116 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 116.4/116.4 kB 4.1 MB/s eta 0:00:00
Downloading ruamel.yaml.clib-0.2.8-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.whl (562 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 562.1/562.1 kB 13.0 MB/s eta 0:00:00
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
Installing collected packages: ruamel.yaml.clib, ruamel.yaml
Successfully installed ruamel.yaml-0.18.5 ruamel.yaml.clib-0.2.8
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
+ echo 7
+ sudo pip3 install --force-reinstall --upgrade paho-mqtt
Collecting paho-mqtt
Downloading paho-mqtt-1.6.1.tar.gz (99 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 99.4/99.4 kB 2.5 MB/s eta 0:00:00
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Building wheels for collected packages: paho-mqtt
Building wheel for paho-mqtt (setup.py): started
Building wheel for paho-mqtt (setup.py): finished with status 'done'
Created wheel for paho-mqtt: filename=paho_mqtt-1.6.1-py3-none-any.whl size=62114 sha256=2a59b6a5a89291cb7b0868e5369863ee34ffcd33166cfad4c0cdb8b87553ebdd
Stored in directory: /root/.cache/pip/wheels/0f/90/29/db29bb8ddc98ec5f2363b959130c9ddbcf5cfdb4a00b6184dd
Successfully built paho-mqtt
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
Installing collected packages: paho-mqtt
Successfully installed paho-mqtt-1.6.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
+ echo 8
+ sudo pip3 install --force-reinstall --upgrade aiohttp
Collecting aiohttp
Downloading aiohttp-3.9.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (7.4 kB)
Collecting attrs>=17.3.0 (from aiohttp)
Downloading attrs-23.2.0-py3-none-any.whl.metadata (9.5 kB)
Collecting multidict<7.0,>=4.5 (from aiohttp)
Downloading multidict-6.0.4-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (114 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 114.2/114.2 kB 2.7 MB/s eta 0:00:00
Collecting yarl<2.0,>=1.0 (from aiohttp)
Downloading yarl-1.9.4-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (31 kB)
Collecting frozenlist>=1.1.1 (from aiohttp)
Downloading frozenlist-1.4.1-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (12 kB)
Collecting aiosignal>=1.1.2 (from aiohttp)
Downloading aiosignal-1.3.1-py3-none-any.whl (7.6 kB)
Collecting async-timeout<5.0,>=4.0 (from aiohttp)
Downloading async_timeout-4.0.3-py3-none-any.whl.metadata (4.2 kB)
Collecting idna>=2.0 (from yarl<2.0,>=1.0->aiohttp)
Downloading idna-3.6-py3-none-any.whl.metadata (9.9 kB)
Downloading aiohttp-3.9.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.2 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 14.9 MB/s eta 0:00:00
Downloading async_timeout-4.0.3-py3-none-any.whl (5.7 kB)
Downloading attrs-23.2.0-py3-none-any.whl (60 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 60.8/60.8 kB 6.3 MB/s eta 0:00:00
Downloading frozenlist-1.4.1-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (240 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 240.7/240.7 kB 17.2 MB/s eta 0:00:00
Downloading yarl-1.9.4-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (304 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 304.3/304.3 kB 14.0 MB/s eta 0:00:00
Downloading idna-3.6-py3-none-any.whl (61 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.6/61.6 kB 6.7 MB/s eta 0:00:00
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
Installing collected packages: multidict, idna, frozenlist, attrs, async-timeout, yarl, aiosignal, aiohttp
Attempting uninstall: idna
Found existing installation: idna 2.10
Uninstalling idna-2.10:
Successfully uninstalled idna-2.10
Successfully installed aiohttp-3.9.1 aiosignal-1.3.1 async-timeout-4.0.3 attrs-23.2.0 frozenlist-1.4.1 idna-3.6 multidict-6.0.4 yarl-1.9.4
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
+ echo 9
+ php /var/www/html/core/class/../php/jeecli.php plugin install mqtt2
warning: commands will be executed using /bin/sh
job 2 at Sat Jan 27 11:57:00 2024
+ echo 10
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end modbus2mqtt
+ rm /tmp/jeedom_install_in_progress_modbus2mqtt
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Log au démarrage après la création du device solaredge :

[2024-01-27 12:07:32][INFO] : Starting daemon
[2024-01-27 12:07:32][INFO] : Log level: debug
[2024-01-27 12:07:32][DEBUG] : Socket port: 55071
[2024-01-27 12:07:32][DEBUG] : PID file: /tmp/jeedom/modbus2mqtt/daemon.pid
[2024-01-27 12:07:32][INFO] : Start listening
[2024-01-27 12:07:33][DEBUG] : Message received in socket JEEDOM_SOCKET_MESSAGE
[2024-01-27 12:07:33][INFO] : Starting modbus4mqtt for 1 and topic solaredge
[2024-01-27 12:07:33][DEBUG] : connect mqtt to 127.0.0.1 on 1883 with user jeedom
[2024-01-27 12:07:33][DEBUG] : will publish to modbus/solaredge
[2024-01-27 12:07:33][INFO] : Start polling...
[2024-01-27 12:07:33][INFO] : Connected to MQTT.
[2024-01-27 12:07:35][WARNING] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-27 12:07:35][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-27 12:07:35][WARNING] : Failed to poll modbus device, attempting to reconnect: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.11.13:1502)]
[2024-01-27 12:07:35][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-27 12:07:47][WARNING] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-27 12:07:47][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-27 12:07:47][WARNING] : Failed to poll modbus device, attempting to reconnect: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.11.13:1502)]
[2024-01-27 12:07:47][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-27 12:07:59][WARNING] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-27 12:07:59][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-27 12:07:59][WARNING] : Failed to poll modbus device, attempting to reconnect: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.11.13:1502)]
[2024-01-27 12:07:59][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-27 12:08:11][WARNING] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-27 12:08:11][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-27 12:08:11][WARNING] : Failed to poll modbus device, attempting to reconnect: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.11.13:1502)]
[2024-01-27 12:08:11][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused

Debian 11 from scratch + Market modbus manager (mêmes options et topic) stable et modbus2mqtt BETA (installation + relance dépendance sur la stable)

log dépendances :

======================================================================
== 27/01/2024 12:11:21 == Dependencies installation for modbus2mqtt
======================================================================
[  5% ] : Clean apt...
[  9% ] : Clean apt : [  OK  ]
[ 10% ] : Update apt...
[ 19% ] : Update apt : [  OK  ]
[ 20% ] : Install apt packages...
[ 39% ] : Install apt packages : [  OK  ]
[ 40% ] : Creating python 3 virtual environment...
[ 49% ] : Creating python 3 virtual environment : [  OK  ]
[ 50% ] : Setting up virtual environment...
[ 69% ] : Setting up virtual environment : [  OK  ]
[ 70% ] : Install the required python packages...
[ 89% ] : Install the required python packages : [  OK  ]
[ 90% ] : Summary of installed packages...
aiohttp==3.9.1
aiosignal==1.3.1
async-timeout==4.0.3
attrs==23.2.0
certifi==2023.11.17
charset-normalizer==3.3.2
frozenlist==1.4.1
idna==3.6
multidict==6.0.4
paho-mqtt==1.6.1
pkg_resources==0.0.0
pymodbus==3.6.3
requests==2.31.0
ruamel.yaml==0.18.5
ruamel.yaml.clib==0.2.8
urllib3==2.1.0
yarl==1.9.4
[ 99% ] : Summary of installed packages : [  OK  ]
[100% ] : Finished !
======================================================================
== OK == Installation Successful
======================================================================

Log du daemon

[2024-01-27 12:11:46][INFO] : Starting daemon
[2024-01-27 12:11:46][INFO] : Log level: debug
[2024-01-27 12:11:46][DEBUG] : Socket port: 55071
[2024-01-27 12:11:46][DEBUG] : Writing PID 12973 to /tmp/jeedom/modbus2mqtt/daemon.pid
[2024-01-27 12:11:46][INFO] : Listening on 127.0.0.1:55071
[2024-01-27 12:11:47][DEBUG] : Received {"action":"start","eqLogicId":"1","topic":"solaredge","apikey":"QuCKhJUAaL5EtLr1KBOXU7BNnGGHUnWTDeMA8Ch2bJR6pYhU1ixX5UV0U7rUXYaI"} from ('127.0.0.1', 40374)
[2024-01-27 12:11:47][DEBUG] : Close connection
[2024-01-27 12:11:47][INFO] : Starting modbus4mqtt for 1 and topic solaredge
[2024-01-27 12:11:47][DEBUG] : connect mqtt to 127.0.0.1 on 1883 with user jeedom
[2024-01-27 12:11:47][DEBUG] : will publish to modbus2mqtt/solaredge
[2024-01-27 12:11:47][DEBUG] : Connection to Modbus server established. Socket ('192.168.9.137', 34836)
[2024-01-27 12:11:47][INFO] : Connected to MQTT.
[2024-01-27 12:11:47][INFO] : Start polling...
[2024-01-27 12:11:47][INFO] : Ready
[2024-01-27 12:11:57][DEBUG] : Current transaction state - IDLE
[2024-01-27 12:11:57][DEBUG] : Running transaction 1
[2024-01-27 12:11:57][DEBUG] : SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x0 0x3 0x9c 0x72 0x0 0x1e
[2024-01-27 12:11:57][DEBUG] : New Transaction state "SENDING"
[2024-01-27 12:11:57][DEBUG] : Changing transaction state from "SENDING" to "WAITING FOR REPLY"
[2024-01-27 12:11:59][DEBUG] : Transaction failed. (Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received))
[2024-01-27 12:11:59][DEBUG] : Processing:
[2024-01-27 12:11:59][DEBUG] : Frame check failed, ignoring!!
[2024-01-27 12:11:59][DEBUG] : Getting transaction 1
[2024-01-27 12:11:59][DEBUG] : Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
[2024-01-27 12:11:59][ERROR] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
Traceback (most recent call last):
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 89, in poll
values = self._scan_value_range(table, group, self._scan_batching)
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 186, in _scan_value_range
raise ValueError("Failed to read {} {} table registers starting from {}: {}".format(count, table, start, result))
ValueError: Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-27 12:11:59][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-27 12:11:59][WARNING] : Failed to poll modbus device, attempting to reconnect: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.11.13:1502)]
[2024-01-27 12:11:59][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-27 12:12:09][DEBUG] : Connection to Modbus server established. Socket ('192.168.9.137', 60628)
[2024-01-27 12:12:09][DEBUG] : Current transaction state - IDLE
[2024-01-27 12:12:09][DEBUG] : Running transaction 1
[2024-01-27 12:12:09][DEBUG] : SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x0 0x3 0x9c 0x72 0x0 0x1e
[2024-01-27 12:12:09][DEBUG] : New Transaction state "SENDING"
[2024-01-27 12:12:09][DEBUG] : Changing transaction state from "SENDING" to "WAITING FOR REPLY"
[2024-01-27 12:12:11][DEBUG] : Transaction failed. (Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received))
[2024-01-27 12:12:11][DEBUG] : Processing:
[2024-01-27 12:12:11][DEBUG] : Frame check failed, ignoring!!
[2024-01-27 12:12:11][DEBUG] : Getting transaction 1
[2024-01-27 12:12:11][DEBUG] : Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
[2024-01-27 12:12:11][ERROR] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
Traceback (most recent call last):
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 89, in poll
values = self._scan_value_range(table, group, self._scan_batching)
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 186, in _scan_value_range
raise ValueError("Failed to read {} {} table registers starting from {}: {}".format(count, table, start, result))
ValueError: Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-27 12:12:11][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-27 12:12:11][WARNING] : Failed to poll modbus device, attempting to reconnect: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.11.13:1502)]
[2024-01-27 12:12:11][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-27 12:12:21][DEBUG] : Connection to Modbus server established. Socket ('192.168.9.137', 49648)
[2024-01-27 12:12:21][DEBUG] : Current transaction state - IDLE
[2024-01-27 12:12:21][DEBUG] : Running transaction 1
[2024-01-27 12:12:21][DEBUG] : SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x0 0x3 0x9c 0x72 0x0 0x1e
[2024-01-27 12:12:21][DEBUG] : New Transaction state "SENDING"
[2024-01-27 12:12:21][DEBUG] : Changing transaction state from "SENDING" to "WAITING FOR REPLY"
[2024-01-27 12:12:23][DEBUG] : Transaction failed. (Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received))
[2024-01-27 12:12:23][DEBUG] : Processing:
[2024-01-27 12:12:23][DEBUG] : Frame check failed, ignoring!!
[2024-01-27 12:12:23][DEBUG] : Getting transaction 1
[2024-01-27 12:12:23][DEBUG] : Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
[2024-01-27 12:12:23][ERROR] : Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
Traceback (most recent call last):
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 89, in poll
values = self._scan_value_range(table, group, self._scan_batching)
File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 186, in _scan_value_range
raise ValueError("Failed to read {} {} table registers starting from {}: {}".format(count, table, start, result))
ValueError: Failed to read 30 holding table registers starting from 40050: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)
[2024-01-27 12:12:23][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-27 12:12:23][WARNING] : Failed to poll modbus device, attempting to reconnect: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.11.13:1502)]
[2024-01-27 12:12:23][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused

Debian 10 from scratch + Market modbus manager (mêmes options et topic) stable et modbus2mqtt stable :

La version jeedom de l’iso est 4.2.21

Log d’installation :

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_modbus2mqtt
+ echo 1
+ echo 2
++ awk '$1 <= 4'
++ cut -f 2-
++ find /usr/local/lib/python3.7/dist-packages/ -mindepth 1 -maxdepth 1 -type d -exec du -ks '{}' +
+ RESULTTODELETE=
++ echo ''
++ sed 's, ,\ ,g'
+ RESULTTODELETE2=
+ echo ''
+ xargs rm -rf
+ echo 3
+ sudo pip3 install --upgrade pip
Collecting pip
Downloading https://files.pythonhosted.org/packages/15/aa/3f4c7bcee2057a76562a5b33ecbd199be08cdb4443a02e26bd2c3cf6fc39/pip-23.3.2-py3-none-any.whl (2.1MB)
Installing collected packages: pip
Found existing installation: pip 18.1
Not uninstalling pip at /usr/lib/python3/dist-packages, outside environment /usr
Can't uninstall 'pip'. No files were found to uninstall.
Successfully installed pip-23.3.2
+ echo 4
+ sudo pip3 install --no-cache-dir --force-reinstall --upgrade requests
Collecting requests
Downloading requests-2.31.0-py3-none-any.whl.metadata (4.6 kB)
Collecting charset-normalizer<4,>=2 (from requests)
Downloading charset_normalizer-3.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (33 kB)
Collecting idna<4,>=2.5 (from requests)
Downloading idna-3.6-py3-none-any.whl.metadata (9.9 kB)
Collecting urllib3<3,>=1.21.1 (from requests)
Downloading urllib3-2.0.7-py3-none-any.whl.metadata (6.6 kB)
Collecting certifi>=2017.4.17 (from requests)
Downloading certifi-2023.11.17-py3-none-any.whl.metadata (2.2 kB)
Downloading requests-2.31.0-py3-none-any.whl (62 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 62.6/62.6 kB 8.9 MB/s eta 0:00:00
Downloading certifi-2023.11.17-py3-none-any.whl (162 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 162.5/162.5 kB 15.3 MB/s eta 0:00:00
Downloading charset_normalizer-3.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (136 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 136.8/136.8 kB 58.5 MB/s eta 0:00:00
Downloading idna-3.6-py3-none-any.whl (61 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.6/61.6 kB 274.4 MB/s eta 0:00:00
Downloading urllib3-2.0.7-py3-none-any.whl (124 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 124.2/124.2 kB 29.2 MB/s eta 0:00:00
Installing collected packages: urllib3, idna, charset-normalizer, certifi, requests
Successfully installed certifi-2023.11.17 charset-normalizer-3.3.2 idna-3.6 requests-2.31.0 urllib3-2.0.7
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
+ echo 5
+ sudo pip3 install --no-cache-dir --force-reinstall --upgrade pymodbus
Collecting pymodbus
Downloading pymodbus-2.5.3-py2.py3-none-any.whl (154 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 154.5/154.5 kB 3.8 MB/s eta 0:00:00
Collecting six>=1.15.0 (from pymodbus)
Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting pyserial>=3.4 (from pymodbus)
Downloading pyserial-3.5-py2.py3-none-any.whl (90 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 90.6/90.6 kB 18.6 MB/s eta 0:00:00
Installing collected packages: pyserial, six, pymodbus
Attempting uninstall: six
Found existing installation: six 1.12.0
Uninstalling six-1.12.0:
Successfully uninstalled six-1.12.0
Successfully installed pymodbus-2.5.3 pyserial-3.5 six-1.16.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
+ echo 6
+ sudo pip3 install --no-cache-dir --force-reinstall --upgrade ruamel.yaml
Collecting ruamel.yaml
Downloading ruamel.yaml-0.18.5-py3-none-any.whl.metadata (23 kB)
Collecting ruamel.yaml.clib>=0.2.7 (from ruamel.yaml)
Downloading ruamel.yaml.clib-0.2.8-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl.metadata (2.2 kB)
Downloading ruamel.yaml-0.18.5-py3-none-any.whl (116 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 116.4/116.4 kB 5.5 MB/s eta 0:00:00
Downloading ruamel.yaml.clib-0.2.8-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl (551 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 551.1/551.1 kB 17.0 MB/s eta 0:00:00
Installing collected packages: ruamel.yaml.clib, ruamel.yaml
Successfully installed ruamel.yaml-0.18.5 ruamel.yaml.clib-0.2.8
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
+ echo 7
+ sudo pip3 install --no-cache-dir --force-reinstall --upgrade paho-mqtt
Collecting paho-mqtt
Downloading paho-mqtt-1.6.1.tar.gz (99 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 99.4/99.4 kB 3.7 MB/s eta 0:00:00
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Building wheels for collected packages: paho-mqtt
Building wheel for paho-mqtt (setup.py): started
Building wheel for paho-mqtt (setup.py): finished with status 'done'
Created wheel for paho-mqtt: filename=paho_mqtt-1.6.1-py3-none-any.whl size=62116 sha256=08bc2884e27055b75795ca2aac2978adbe558d45dbb224b51db588bad6bdf9aa
Stored in directory: /tmp/pip-ephem-wheel-cache-zt19jgau/wheels/d0/bf/ac/2b3f43f8c6fcd0f4ba5395397458c521eb0b52d33b574a5a40
Successfully built paho-mqtt
Installing collected packages: paho-mqtt
Successfully installed paho-mqtt-1.6.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
+ echo 8
+ sudo pip3 install --no-cache-dir --force-reinstall --upgrade aiohttp
Collecting aiohttp
Downloading aiohttp-3.8.6-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (7.7 kB)
Collecting attrs>=17.3.0 (from aiohttp)
Downloading attrs-23.2.0-py3-none-any.whl.metadata (9.5 kB)
Collecting charset-normalizer<4.0,>=2.0 (from aiohttp)
Downloading charset_normalizer-3.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (33 kB)
Collecting multidict<7.0,>=4.5 (from aiohttp)
Downloading multidict-6.0.4-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (94 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 94.8/94.8 kB 6.0 MB/s eta 0:00:00
Collecting async-timeout<5.0,>=4.0.0a3 (from aiohttp)
Downloading async_timeout-4.0.3-py3-none-any.whl.metadata (4.2 kB)
Collecting yarl<2.0,>=1.0 (from aiohttp)
Downloading yarl-1.9.4-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (31 kB)
Collecting frozenlist>=1.1.1 (from aiohttp)
Downloading frozenlist-1.3.3-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (148 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 148.0/148.0 kB 10.7 MB/s eta 0:00:00
Collecting aiosignal>=1.1.2 (from aiohttp)
Downloading aiosignal-1.3.1-py3-none-any.whl (7.6 kB)
Collecting asynctest==0.13.0 (from aiohttp)
Downloading asynctest-0.13.0-py3-none-any.whl (26 kB)
Collecting typing-extensions>=3.7.4 (from aiohttp)
Downloading typing_extensions-4.7.1-py3-none-any.whl.metadata (3.1 kB)
Collecting importlib-metadata (from attrs>=17.3.0->aiohttp)
Downloading importlib_metadata-6.7.0-py3-none-any.whl.metadata (4.9 kB)
Collecting idna>=2.0 (from yarl<2.0,>=1.0->aiohttp)
Downloading idna-3.6-py3-none-any.whl.metadata (9.9 kB)
Collecting zipp>=0.5 (from importlib-metadata->attrs>=17.3.0->aiohttp)
Downloading zipp-3.15.0-py3-none-any.whl (6.8 kB)
Downloading aiohttp-3.8.6-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (987 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 988.0/988.0 kB 22.3 MB/s eta 0:00:00
Downloading async_timeout-4.0.3-py3-none-any.whl (5.7 kB)
Downloading attrs-23.2.0-py3-none-any.whl (60 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 60.8/60.8 kB 37.7 MB/s eta 0:00:00
Downloading charset_normalizer-3.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (136 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 136.8/136.8 kB 54.9 MB/s eta 0:00:00
Downloading typing_extensions-4.7.1-py3-none-any.whl (33 kB)
Downloading yarl-1.9.4-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (289 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 289.8/289.8 kB 26.3 MB/s eta 0:00:00
Downloading idna-3.6-py3-none-any.whl (61 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.6/61.6 kB 186.6 MB/s eta 0:00:00
Downloading importlib_metadata-6.7.0-py3-none-any.whl (22 kB)
Installing collected packages: zipp, typing-extensions, multidict, idna, frozenlist, charset-normalizer, asynctest, yarl, importlib-metadata, async-timeout, aiosignal, attrs, aiohttp
Attempting uninstall: idna
Found existing installation: idna 3.6
Uninstalling idna-3.6:
Successfully uninstalled idna-3.6
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
Successfully installed aiohttp-3.8.6 aiosignal-1.3.1 async-timeout-4.0.3 asynctest-0.13.0 attrs-23.2.0 charset-normalizer-3.3.2 frozenlist-1.3.3 idna-3.6 importlib-metadata-6.7.0 multidict-6.0.4 typing-extensions-4.7.1 yarl-1.9.4 zipp-3.15.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
+ echo 9
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end modbus2mqtt
+ rm /tmp/jeedom_install_in_progress_modbus2mqtt
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Log du daemon

[2024-01-27 12:40:51][INFO] : Starting daemon
[2024-01-27 12:40:51][INFO] : Log level: debug
[2024-01-27 12:40:51][DEBUG] : Socket port: 55071
[2024-01-27 12:40:51][DEBUG] : PID file: /tmp/jeedom/modbus2mqtt/daemon.pid
[2024-01-27 12:40:51][INFO] : Start listening
[2024-01-27 12:40:52][DEBUG] : Message received in socket JEEDOM_SOCKET_MESSAGE
[2024-01-27 12:40:52][INFO] : Starting modbus4mqtt for 1 and topic solaredge
[2024-01-27 12:40:52][DEBUG] : connect mqtt to 127.0.0.1 on 1883 with user jeedom
[2024-01-27 12:40:52][DEBUG] : will publish to modbus2mqtt/solaredge
[2024-01-27 12:40:52][INFO] : Start polling...
[2024-01-27 12:40:52][INFO] : Connected to MQTT.
[2024-01-27 12:40:52][DEBUG] : Publish 283 to modbus2mqtt/solaredge/AC_current_value
[2024-01-27 12:40:52][DEBUG] : Publish 50011 to modbus2mqtt/solaredge/AC_frequency
[2024-01-27 12:40:52][DEBUG] : Publish 6661 to modbus2mqtt/solaredge/DC_power
[2024-01-27 12:40:52][DEBUG] : Publish 6561 to modbus2mqtt/solaredge/AC_power
[2024-01-27 12:41:02][DEBUG] : Publish 282 to modbus2mqtt/solaredge/AC_current_value
[2024-01-27 12:41:02][DEBUG] : Publish 50002 to modbus2mqtt/solaredge/AC_frequency
[2024-01-27 12:41:02][DEBUG] : Publish 6646 to modbus2mqtt/solaredge/DC_power
[2024-01-27 12:41:02][DEBUG] : Publish 6546 to modbus2mqtt/solaredge/AC_power

C’est fonctionnel en debian 10 donc !
Je fais la mise à jour vers Jeedom 4.3.22, je reboot et cela fonctionne toujours.

belgotux · Janvier 27, 2024, 1:09

J’ai atteins la limite de caractères

Debian 10 from scratch + Market modbus manager (mêmes options et topic) stable et modbus2mqtt BETA :

Dans le doute, j’ai aussi tenté la beta en debian 10 et il y a des dépendances non satisfaisantes pour les utilisateurs qui seraient encore en debian 10, ça t’aide pour avancer sur ton plugin beta au moins ^^’

======================================================================
== 27/01/2024 13:44:51 == Dependencies installation for modbus2mqtt
======================================================================
[  5% ] : Clean apt...
[  9% ] : Clean apt : [  OK  ]
[ 10% ] : Update apt...
[ 19% ] : Update apt : [  OK  ]
[ 20% ] : Install apt packages...
[ 39% ] : Install apt packages : [  OK  ]
[ 40% ] : Creating python 3 virtual environment...
[ 49% ] : Creating python 3 virtual environment : [  OK  ]
[ 50% ] : Setting up virtual environment...
[ 69% ] : Setting up virtual environment : [  OK  ]
[ 70% ] : Install the required python packages...
[ 99% ] : Install the required python packages : ERROR
[100% ] : Finished !
======================================================================
== KO == Installation Error
======================================================================
== ANALYSING ERRORS...
== NO KNOWN ERROR DETECTED
== Error in step : Install the required python packages
== Line 158
== Command `/var/www/html/plugins/modbus2mqtt/resources/venv/bin/python3 -m pip install --no-cache-dir -r requirements.txt' have an issue
== Return code is 1
== Error message :
Collecting requests>=2.25.1 (from -r requirements.txt (line 1))
Downloading requests-2.31.0-py3-none-any.whl.metadata (4.6 kB)
ERROR: Ignored the following versions that require a different python version: 3.0.0 Requires-Python >=3.8.0; 3.0.0.dev4 Requires-Python >=3.8.0; 3.0.0.dev5 Requires-Python >=3.8.0; 3.0.0rc1 Requires-Python >=3.8.0; 3.0.1 Requires-Python >=3.8.0; 3.0.2 Requires-Python >=3.8.0; 3.1.0 Requires-Python >=3.8.0; 3.1.1 Requires-Python >=3.8.0; 3.1.2 Requires-Python >=3.8.0; 3.1.3 Requires-Python >=3.8.0; 3.2.0 Requires-Python >=3.8.0; 3.2.1 Requires-Python >=3.8.0; 3.2.2 Requires-Python >=3.8.0; 3.3.0 Requires-Python >=3.8.0; 3.3.1 Requires-Python >=3.8.0; 3.3.2 Requires-Python >=3.8.0; 3.4.0 Requires-Python >=3.8.0; 3.4.1 Requires-Python >=3.8.0; 3.5.0 Requires-Python >=3.8.0; 3.5.1 Requires-Python >=3.8.0; 3.5.2 Requires-Python >=3.8.0; 3.5.3 Requires-Python >=3.8.0; 3.5.4 Requires-Python >=3.8.0; 3.6.1 Requires-Python >=3.8.0; 3.6.2 Requires-Python >=3.8.0; 3.6.3 Requires-Python >=3.8.0
ERROR: Could not find a version that satisfies the requirement pymodbus>=3.4.0 (from versions: 0.9.0, 1.0.0, 1.1.0, 1.2.0, 1.3.0rc1, 1.3.0rc2, 1.3.1, 1.3.2, 1.4.0rc3, 1.4.0, 1.5.0, 1.5.1, 1.5.2, 2.0.0, 2.0.1, 2.1.0, 2.2.0rc1, 2.2.0rc2, 2.2.0rc3, 2.2.0rc4, 2.2.0, 2.3.0rc1, 2.3.0, 2.4.0rc1, 2.4.0, 2.5.0rc1, 2.5.0rc2, 2.5.0, 2.5.1rc1, 2.5.1, 2.5.2, 2.5.3rc1, 2.5.3, 3.0.0.dev2, 3.0.0.dev3)
ERROR: No matching distribution found for pymodbus>=3.4.0
======================================================================

EDIT: je viens de testé le plugin mymodbus (désolé de mon infidélité ) sur la debian11 de test et j’ai exactement le même souci de connection refused!

Ce serait plutôt une erreur de librairie commune ou configuration de l’OS ?

[2024-01-27 14:20:47][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
[2024-01-27 14:20:47][ERROR] : Connection to (192.168.11.13, 1502) failed: [Errno 111] Connection refused
Exception in thread Thread-2:
Traceback (most recent call last):
File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
self.run()
File "/usr/lib/python3.9/threading.py", line 892, in run
self._target(*self._args, **self._kwargs)
File "/var/www/html/plugins/mymodbus/ressources/mymodbus_demond.py", line 177, in polling_thread
rr = client.read_holding_registers(int(hreg_first),i,unit=args.unid)
File "/usr/local/lib/python3.9/dist-packages/pymodbus/client/common.py", line 114, in read_holding_registers
return self.execute(request)
File "/usr/local/lib/python3.9/dist-packages/pymodbus/client/sync.py", line 108, in execute
raise ConnectionException("Failed to connect[%s]" % (self.__str__()))
pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.11.13:1502)]

J’ai trouvé un sujet a ce propos : [Errno 111] Connection refused · Issue #614 · pymodbus-dev/pymodbus · GitHub

Sous debian 10 :

Sous debian 11 :

EDIT2 : avec le script de test du lien, j’ai des erreurs en pymodbus-3.6.3 et plus en 2.5.3 :

jeedom@jeedom:~$ mkdir test && cd test/
jeedom@jeedom:~/test$ virtualenv venv
created virtual environment CPython3.9.2.final.0-64 in 2748ms
  creator CPython3Posix(dest=/home/jeedom/test/venv, clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/jeedom/.local/share/virtualenv)
    added seed packages: pip==23.3.1, setuptools==69.0.2, wheel==0.42.0
  activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
jeedom@jeedom:~/test$ source venv/bin/activate
(venv) jeedom@jeedom:~/test$ pip install pymodbus
Collecting pymodbus
  Downloading pymodbus-3.6.3-py3-none-any.whl.metadata (14 kB)
Downloading pymodbus-3.6.3-py3-none-any.whl (205 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 205.2/205.2 kB 1.7 MB/s eta 0:00:00
Installing collected packages: pymodbus
Successfully installed pymodbus-3.6.3

[notice] A new release of pip is available: 23.3.1 -> 23.3.2
[notice] To update, run: pip install --upgrade pip


(venv) jeedom@jeedom:~/test$ python test2.py
Traceback (most recent call last):
  File "/home/jeedom/test/test2.py", line 5, in <module>
    from pymodbus.client.sync import ModbusTcpClient
ModuleNotFoundError: No module named 'pymodbus.client.sync'
(venv) jeedom@jeedom:~/test$ vim test.py ^C
(venv) jeedom@jeedom:~/test$ pip install pymodbus==2.5.3
Collecting pymodbus==2.5.3
  Downloading pymodbus-2.5.3-py2.py3-none-any.whl (154 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 154.5/154.5 kB 1.4 MB/s eta 0:00:00
Collecting six>=1.15.0 (from pymodbus==2.5.3)
  Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting pyserial>=3.4 (from pymodbus==2.5.3)
  Downloading pyserial-3.5-py2.py3-none-any.whl (90 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 90.6/90.6 kB 3.2 MB/s eta 0:00:00
Installing collected packages: pyserial, six, pymodbus
  Attempting uninstall: pymodbus
    Found existing installation: pymodbus 3.6.3
    Uninstalling pymodbus-3.6.3:
      Successfully uninstalled pymodbus-3.6.3
Successfully installed pymodbus-2.5.3 pyserial-3.5 six-1.16.0
(venv) jeedom@jeedom:~/test$ python test2.py
2024-01-27 15:13:47,888 [__main__    ] DEBUG    b'SunS\x00\x01\x00ASolarEdge \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00SE4000H-RW000BEN4\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x000004.0018.0032\x00\x0075033FCF\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01'
2024-01-27 15:13:47,927 [__main__    ] DEBUG    b'\x00e\x002\x00\xc8\x00\xc8\xff\xff\xff\xff\xff\xfe\t\x02\xff\xff\xff\xff\t\x02\xff\xff\xff\xff\xff\xff\x11\xe8\xff\xff\xc3=\xff\xfd\x12\x10\xff\xff\x17\xbd\xff\xfe&\xb9\xff\xfe\x00\x0e\xf4\xbb\x00\x001\x1f\xff\xfc\x0et\xff\xff\x12-\xff\xff\x80\x00\x0b\xe3\x80\x00\x80\x00\xff\xfe\x00\x04\x00\x00\xff\xff\xff\xff\xff\xff\xff\xff\x00\x00\x00\x00\xff\xff\xff\xff\xff\xff\xff\xff\x00\x00\x00\x00'

Mips · Janvier 27, 2024, 2:25

Je ne sais pas pq cela cause autant de problème avec ton onduleur, pour bien faire faudrait tester chez toi avec un autre « serveur » modbus voir si le même problème se pose car chez moi je ne reproduis pas ca fonctionne (je test avec 2 serveurs différents)

Mais en attendant j’ai fait un revert sur la version 2.5, de toute façon c’est requis pour garder la compatibilité avec debian 10;
heureusement cette version est encore dispo sous debian 12, pour l’instant.

peux-tu essayer la nouvelle beta?

belgotux · Janvier 27, 2024, 2:55

Je me demande si c’est pas le cas du github que ce device est stricte, je lis qu’entre la 2.4.0 et la 2.5.1 il y a eu un bug. Il y a peut-être eu régression quelque part entre la 2.5.3 et le 3.6.3 ?

En tout cas je viens de tester sur la vm deb11 et cela fonctionne! un grand merci à toi pour le suivi!
C’était bien sur cette lib le souci, mais à voir si seul le solaredge est touché ou non

Log install

======================================================================
== 27/01/2024 15:35:37 == Dependencies installation for modbus2mqtt
======================================================================
[  5% ] : Clean apt...
[  9% ] : Clean apt : [  OK  ]
[ 10% ] : Update apt...
[ 19% ] : Update apt : [  OK  ]
[ 20% ] : Install apt packages...
[ 39% ] : Install apt packages : [  OK  ]
[ 40% ] : Creating python 3 virtual environment...
[ 49% ] : Creating python 3 virtual environment : [  OK  ]
[ 50% ] : Setting up virtual environment...
[ 69% ] : Setting up virtual environment : [  OK  ]
[ 70% ] : Install the required python packages...
[ 89% ] : Install the required python packages : [  OK  ]
[ 90% ] : Summary of installed packages...
aiohttp==3.9.1
aiosignal==1.3.1
async-timeout==4.0.3
attrs==23.2.0
certifi==2023.11.17
charset-normalizer==3.3.2
frozenlist==1.4.1
idna==3.6
multidict==6.0.4
paho-mqtt==1.6.1
pkg_resources==0.0.0
pymodbus==2.5.3
pyserial==3.5
requests==2.31.0
ruamel.yaml==0.18.5
ruamel.yaml.clib==0.2.8
six==1.16.0
urllib3==2.1.0
yarl==1.9.4
[ 99% ] : Summary of installed packages : [  OK  ]
[100% ] : Finished !
======================================================================
== OK == Installation Successful
======================================================================

Log daemon

[2024-01-27 15:36:11][INFO] : Starting daemon
[2024-01-27 15:36:11][INFO] : Log level: debug
[2024-01-27 15:36:11][DEBUG] : Socket port: 55071
[2024-01-27 15:36:11][DEBUG] : Writing PID 3379 to /tmp/jeedom/modbus2mqtt/daemon.pid
[2024-01-27 15:36:11][INFO] : Listening on 127.0.0.1:55071
[2024-01-27 15:36:12][INFO] : Ready
[2024-01-27 15:36:12][DEBUG] : Received {"action":"start","eqLogicId":"1","topic":"solaredge","apikey":"AdPcwN0EjOve521NapkSF2UCduPJXQV88hrAO3yhb52YLMZ6lARH1RJ8NSEOCnNx"} from ('127.0.0.1', 34402)
[2024-01-27 15:36:12][DEBUG] : Close connection
[2024-01-27 15:36:12][INFO] : Starting modbus4mqtt for 1 and topic solaredge
[2024-01-27 15:36:12][DEBUG] : connect mqtt to 127.0.0.1 on 1883 with user jeedom
[2024-01-27 15:36:12][DEBUG] : will publish to modbus2mqtt/solaredge
[2024-01-27 15:36:12][DEBUG] : Connection to Modbus server established. Socket ('192.168.9.137', 41867)
[2024-01-27 15:36:12][INFO] : Start polling...
[2024-01-27 15:36:12][INFO] : Connected to MQTT.
[2024-01-27 15:36:22][DEBUG] : Current transaction state - IDLE
[2024-01-27 15:36:22][DEBUG] : Running transaction 1
[2024-01-27 15:36:22][DEBUG] : SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x1 0x3 0x9c 0x72 0x0 0x1e
[2024-01-27 15:36:22][DEBUG] : New Transaction state 'SENDING'
[2024-01-27 15:36:22][DEBUG] : Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
[2024-01-27 15:36:22][DEBUG] : Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
[2024-01-27 15:36:22][DEBUG] : RECV: 0x0 0x1 0x0 0x0 0x0 0x3f 0x1 0x3 0x3c 0x33 0x32 0x0 0x0 0x37 0x35 0x30 0x33 0x33 0x46 0x43 0x46 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x1 0x0 0x65 0x0 0x32 0x0 0xe5 0x0 0xe5 0xff 0xff 0xff 0xff 0xff 0xfe 0x9 0x13 0xff 0xff 0xff 0xff 0x9 0x13
[2024-01-27 15:36:22][DEBUG] : Processing: 0x0 0x1 0x0 0x0 0x0 0x3f 0x1 0x3 0x3c 0x33 0x32 0x0 0x0 0x37 0x35 0x30 0x33 0x33 0x46 0x43 0x46 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x1 0x0 0x65 0x0 0x32 0x0 0xe5 0x0 0xe5 0xff 0xff 0xff 0xff 0xff 0xfe 0x9 0x13 0xff 0xff 0xff 0xff 0x9 0x13
[2024-01-27 15:36:22][DEBUG] : Factory Response[ReadHoldingRegistersResponse: 3]
[2024-01-27 15:36:22][DEBUG] : Adding transaction 1
[2024-01-27 15:36:22][DEBUG] : Getting transaction 1
[2024-01-27 15:36:22][DEBUG] : Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
[2024-01-27 15:36:22][DEBUG] : Current transaction state - TRANSACTION_COMPLETE
[2024-01-27 15:36:22][DEBUG] : Running transaction 2
[2024-01-27 15:36:22][DEBUG] : SEND: 0x0 0x2 0x0 0x0 0x0 0x6 0x1 0x3 0x9c 0x90 0x0 0x1e
[2024-01-27 15:36:22][DEBUG] : New Transaction state 'SENDING'
[2024-01-27 15:36:22][DEBUG] : Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
[2024-01-27 15:36:22][DEBUG] : Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
[2024-01-27 15:36:22][DEBUG] : RECV: 0x0 0x2 0x0 0x0 0x0 0x3f 0x1 0x3 0x3c 0xff 0xff 0xff 0xff 0xff 0xff 0x14 0xad 0xff 0xff 0xc3 0x34 0xff 0xfd 0x14 0xca 0xff 0xff 0x15 0xa5 0xff 0xfe 0x26 0xd9 0xff 0xfe 0x0 0xe 0xf5 0x7a 0x0 0x0 0x38 0xc0 0xff 0xfc 0xe 0x73 0xff 0xff 0x14 0xfe 0xff 0xff 0x80 0x0 0xb 0xdf 0x80 0x0 0x80 0x0 0xff 0xfe 0x0 0x4 0x0 0x0 0xff 0xff
[2024-01-27 15:36:22][DEBUG] : Processing: 0x0 0x2 0x0 0x0 0x0 0x3f 0x1 0x3 0x3c 0xff 0xff 0xff 0xff 0xff 0xff 0x14 0xad 0xff 0xff 0xc3 0x34 0xff 0xfd 0x14 0xca 0xff 0xff 0x15 0xa5 0xff 0xfe 0x26 0xd9 0xff 0xfe 0x0 0xe 0xf5 0x7a 0x0 0x0 0x38 0xc0 0xff 0xfc 0xe 0x73 0xff 0xff 0x14 0xfe 0xff 0xff 0x80 0x0 0xb 0xdf 0x80 0x0 0x80 0x0 0xff 0xfe 0x0 0x4 0x0 0x0 0xff 0xff
[2024-01-27 15:36:22][DEBUG] : Factory Response[ReadHoldingRegistersResponse: 3]
[2024-01-27 15:36:22][DEBUG] : Adding transaction 2
[2024-01-27 15:36:22][DEBUG] : Getting transaction 2
[2024-01-27 15:36:22][DEBUG] : Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
[2024-01-27 15:36:22][DEBUG] : Publish 229 to modbus2mqtt/solaredge/AC_current_value
[2024-01-27 15:36:22][DEBUG] : Publish 49972 to modbus2mqtt/solaredge/AC_frequency
[2024-01-27 15:36:22][DEBUG] : Publish 5374 to modbus2mqtt/solaredge/DC_power
[2024-01-27 15:36:22][DEBUG] : Publish 5293 to modbus2mqtt/solaredge/AC_power
[2024-01-27 15:36:32][DEBUG] : Current transaction state - TRANSACTION_COMPLETE
[2024-01-27 15:36:32][DEBUG] : Running transaction 3
[2024-01-27 15:36:32][DEBUG] : SEND: 0x0 0x3 0x0 0x0 0x0 0x6 0x1 0x3 0x9c 0x72 0x0 0x1e
[2024-01-27 15:36:32][DEBUG] : New Transaction state 'SENDING'
[2024-01-27 15:36:32][DEBUG] : Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
[2024-01-27 15:36:32][DEBUG] : Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
[2024-01-27 15:36:32][DEBUG] : RECV: 0x0 0x3 0x0 0x0 0x0 0x3f 0x1 0x3 0x3c 0x33 0x32 0x0 0x0 0x37 0x35 0x30 0x33 0x33 0x46 0x43 0x46 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x1 0x0 0x65 0x0 0x32 0x0 0xe5 0x0 0xe5 0xff 0xff 0xff 0xff 0xff 0xfe 0x9 0x20 0xff 0xff 0xff 0xff 0x9 0x20
[2024-01-27 15:36:32][DEBUG] : Processing: 0x0 0x3 0x0 0x0 0x0 0x3f 0x1 0x3 0x3c 0x33 0x32 0x0 0x0 0x37 0x35 0x30 0x33 0x33 0x46 0x43 0x46 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x1 0x0 0x65 0x0 0x32 0x0 0xe5 0x0 0xe5 0xff 0xff 0xff 0xff 0xff 0xfe 0x9 0x20 0xff 0xff 0xff 0xff 0x9 0x20
[2024-01-27 15:36:32][DEBUG] : Factory Response[ReadHoldingRegistersResponse: 3]
[2024-01-27 15:36:32][DEBUG] : Adding transaction 3
[2024-01-27 15:36:32][DEBUG] : Getting transaction 3
[2024-01-27 15:36:32][DEBUG] : Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
[2024-01-27 15:36:32][DEBUG] : Current transaction state - TRANSACTION_COMPLETE
[2024-01-27 15:36:32][DEBUG] : Running transaction 4
[2024-01-27 15:36:32][DEBUG] : SEND: 0x0 0x4 0x0 0x0 0x0 0x6 0x1 0x3 0x9c 0x90 0x0 0x1e
[2024-01-27 15:36:32][DEBUG] : New Transaction state 'SENDING'
[2024-01-27 15:36:32][DEBUG] : Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
[2024-01-27 15:36:32][DEBUG] : Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
[2024-01-27 15:36:32][DEBUG] : RECV: 0x0 0x4 0x0 0x0 0x0 0x3f 0x1 0x3 0x3c 0xff 0xff 0xff 0xff 0xff 0xff 0x14 0xdb 0xff 0xff 0xc3 0x3d 0xff 0xfd 0x14 0xf8 0xff 0xff 0x16 0x12 0xff 0xfe 0x26 0xd8 0xff 0xfe 0x0 0xe 0xf5 0x7b 0x0 0x0 0x39 0x34 0xff 0xfc 0xe 0x75 0xff 0xff 0x15 0x2c 0xff 0xff 0x80 0x0 0xb 0xe0 0x80 0x0 0x80 0x0 0xff 0xfe 0x0 0x4 0x0 0x0 0xff 0xff
[2024-01-27 15:36:32][DEBUG] : Processing: 0x0 0x4 0x0 0x0 0x0 0x3f 0x1 0x3 0x3c 0xff 0xff 0xff 0xff 0xff 0xff 0x14 0xdb 0xff 0xff 0xc3 0x3d 0xff 0xfd 0x14 0xf8 0xff 0xff 0x16 0x12 0xff 0xfe 0x26 0xd8 0xff 0xfe 0x0 0xe 0xf5 0x7b 0x0 0x0 0x39 0x34 0xff 0xfc 0xe 0x75 0xff 0xff 0x15 0x2c 0xff 0xff 0x80 0x0 0xb 0xe0 0x80 0x0 0x80 0x0 0xff 0xfe 0x0 0x4 0x0 0x0 0xff 0xff
[2024-01-27 15:36:32][DEBUG] : Factory Response[ReadHoldingRegistersResponse: 3]
[2024-01-27 15:36:32][DEBUG] : Adding transaction 4
[2024-01-27 15:36:32][DEBUG] : Getting transaction 4
[2024-01-27 15:36:32][DEBUG] : Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
[2024-01-27 15:36:32][DEBUG] : Publish 49981 to modbus2mqtt/solaredge/AC_frequency
[2024-01-27 15:36:32][DEBUG] : Publish 5420 to modbus2mqtt/solaredge/DC_power
[2024-01-27 15:36:32][DEBUG] : Publish 5339 to modbus2mqtt/solaredge/AC_power

Et pour l’autre device :
Je n’ai pas d’autre modbus tcp facilement accessible, maintenant s’il y a un docker dummy pour faire les tests, je peux installer. Je peux aussi regardé côté de la vmc mais je pense que c’est modbus serie et pas tcp/ip, en tout cas je viens d’essayer avec modbusclientx sur son ip et port 502 et j’ai rien