Problèmes de fonctionnement

m.georgein · Juillet 20, 2023, 1:24

Bonjour
Je suis en Jeedom V 4.4.0

J’essaye de basculer mes infos modbus de l’onduleur solaire du plugin ‹ myModbus › vers ‹ modbus2mqtt ›

Ci après les paramètres de myModbus :

Pour tester j’utilise une valeur 16bit :

Les paramètrages de mqtt2modbus :

le registre :

Les commandes :

Le statut remonte bien (y compris dans mqttExplorer :

le log :

0081|[2023-07-20 15:11:05]WARNING : Failed to read 10 holding table registers starting from 32060: Modbus Error: [Input/Output] No Response received from the remote unit/Unable to decode response
0082|[2023-07-20 15:11:16]WARNING : Failed to read 10 holding table registers starting from 32060: Modbus Error: [Input/Output] No Response received from the remote unit/Unable to decode response
0083|[2023-07-20 15:11:38]WARNING : Failed to read 10 holding table registers starting from 32060: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)

Mais rien dans le plugin , Une idée de ce que je fait mal ???

Question subsidiaire : quid des données 32 bits ???

Mips · Juillet 20, 2023, 1:34

Salut,

le « statut » remonte mais pas les infos, il n’a pas su se connecter sur ton device => tu es sur de la config: ip, port, les adresses etc? tu es sur que tu peux lire plusieurs adresses en même temps? tu as configuré 10 ici, pourquoi au fait puisqu’en fait tu ne lis qu’un seul registre?

je n’en avais pas besoin donc comme dit dans la doc « évolution à envisager selon les demandes. »

m.georgein · Juillet 20, 2023, 1:45

Tout fonctionne nickel via myModbus, pour ça que je t’ai mis les screen de ses paramétrages, donc IP et autres pas de soucis

Pour la longueur de 10, j’ai bétement laissé la valeur par defaut

Petite remarque l’onduleur Sun2000 apparemment demande une tempo avant la première lecture :

Et maintenant ? tu envisage de faire évoluer ??

Mips · Juillet 20, 2023, 2:07

Essaye 1 déjà ou d’autres valeurs
honnetement je ne comprend pas trop pq certains devices veulent que tu lises plusieurs à la fois, certains si tu en lis trop ca plante, d’autres il en faut qu’un seul… c’est un peu le bo… modbus

oui mais ca sera pas tout de suite, je pars dans 2 jours en congés pour plusieurs semaines

Mips · Août 17, 2023, 8:26

Concernant la lecture, c’est réglé? ou tu n’as plus besoin?
si toujours besoin d’aide, peux-tu me donner capture page santé jeedom + logs dépendances

Mips · Octobre 3, 2023, 3:53

toujours pas de réaction… heureusement que je n’en fais pas autant lorsqu’il y a une question qui m’est adressée…

tu es pourtant actif sur d’autres sujets…

m.georgein · Octobre 3, 2023, 8:05

Pas faux,

je sort la tête de l’eau et je rouvre le dossier du plugin dans les jours à venir.

m.georgein · Octobre 17, 2023, 11:24

Je redémarre dans la mise en oeuvre du plugin …

Contexte : Jeedom 4.4.0, VM proxmox sous debian 10

J’ai une install de lecture de mon onduleur avec MyModbus qui fonctionne nickel.
Le but serai de normaliser modbus vers le mqtt comme mes autres protocoles
Toutes l’install à eu lieu sans problème.

Le paramètrage :

J’ai créé 2 registres test, 1 en 16 bit l’autre en 32 en image de ce que j’ai sur MyModbus qui fonctionne :

un extrait du log :

0184|File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 185, in _scan_value_range
0185|raise ValueError("Failed to read {} {} table registers starting from {}: {}".format(count, table, start, result))
0186|ValueError: Failed to read 1 holding table registers starting from 37023: Exception Response(131, 3, IllegalAddress)
0187|[2023-10-18 01:13:12]WARNING : Couldn't get value from register 37023 in table holding
0188|[2023-10-18 01:13:12]WARNING : Couldn't get value from register 32065 in table holding
0189|[2023-10-18 01:13:22]DEBUG : Current transaction state - TRANSACTION_COMPLETE
0190|[2023-10-18 01:13:22]DEBUG : Running transaction 7
0191|[2023-10-18 01:13:22]DEBUG : SEND: 0x0 0x7 0x0 0x0 0x0 0x6 0x1 0x3 0x7d 0x41 0x0 0x1
0192|[2023-10-18 01:13:22]DEBUG : New Transaction state 'SENDING'
0193|[2023-10-18 01:13:22]DEBUG : Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
0194|[2023-10-18 01:13:22]WARNING : Failed to poll modbus device, attempting to reconnect: Modbus Error: [Connection] ModbusTcpClient(192.168.2.139:502): Connection unexpectedly closed 0.000007 seconds into read of 8 bytes without response from unit before it closed connection
0195|[2023-10-18 01:13:22]DEBUG : Connection to Modbus server established. Socket ('192.168.2.196', 53697)
0196|[2023-10-18 01:13:32]DEBUG : Current transaction state - IDLE
0197|[2023-10-18 01:13:32]DEBUG : Running transaction 1
0198|[2023-10-18 01:13:32]DEBUG : SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x1 0x3 0x7d 0x41 0x0 0x1
0199|[2023-10-18 01:13:32]DEBUG : New Transaction state 'SENDING'
0200|[2023-10-18 01:13:32]DEBUG : Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
0201|[2023-10-18 01:13:32]DEBUG : Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
0202|[2023-10-18 01:13:32]DEBUG : RECV: 0x0 0x1 0x0 0x0 0x0 0x3 0x1 0x83 0x2
0203|[2023-10-18 01:13:32]DEBUG : Processing: 0x0 0x1 0x0 0x0 0x0 0x3 0x1 0x83 0x2
0204|[2023-10-18 01:13:32]DEBUG : Factory Response[131]
0205|[2023-10-18 01:13:32]DEBUG : Adding transaction 1
0206|[2023-10-18 01:13:32]DEBUG : Getting transaction 1
0207|[2023-10-18 01:13:32]DEBUG : Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
0208|[2023-10-18 01:13:32]ERROR : Failed to read 1 holding table registers starting from 32065: Exception Response(131, 3, IllegalAddress)
0209|Traceback (most recent call last):
0210|File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 182, in _scan_value_range
0211|return result.registers
0212|AttributeError: 'ExceptionResponse' object has no attribute 'registers'
0213|During handling of the above exception, another exception occurred:
0214|Traceback (most recent call last):
0215|File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 89, in poll
0216|values = self._scan_value_range(table, group, self._scan_batching)
0217|File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 185, in _scan_value_range
0218|raise ValueError("Failed to read {} {} table registers starting from {}: {}".format(count, table, start, result))
0219|ValueError: Failed to read 1 holding table registers starting from 32065: Exception Response(131, 3, IllegalAddress)
0220|[2023-10-18 01:13:32]DEBUG : Current transaction state - TRANSACTION_COMPLETE
0221|[2023-10-18 01:13:32]DEBUG : Running transaction 2
0222|[2023-10-18 01:13:32]DEBUG : SEND: 0x0 0x2 0x0 0x0 0x0 0x6 0x1 0x3 0x7d 0x42 0x0 0x1
0223|[2023-10-18 01:13:32]DEBUG : New Transaction state 'SENDING'
0224|[2023-10-18 01:13:32]DEBUG : Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
0225|[2023-10-18 01:13:32]DEBUG : Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
0226|[2023-10-18 01:13:32]DEBUG : RECV: 0x0 0x2 0x0 0x0 0x0 0x5 0x1 0x3 0x2 0x9 0x8e
0227|[2023-10-18 01:13:32]DEBUG : Processing: 0x0 0x2 0x0 0x0 0x0 0x5 0x1 0x3 0x2 0x9 0x8e
0228|[2023-10-18 01:13:32]DEBUG : Factory Response[ReadHoldingRegistersResponse: 3]
0229|[2023-10-18 01:13:32]DEBUG : Adding transaction 2
0230|[2023-10-18 01:13:32]DEBUG : Getting transaction 2
0231|[2023-10-18 01:13:32]DEBUG : Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
0232|[2023-10-18 01:13:33]DEBUG : Current transaction state - TRANSACTION_COMPLETE
0233|[2023-10-18 01:13:33]DEBUG : Running transaction 3
0234|[2023-10-18 01:13:33]DEBUG : SEND: 0x0 0x3 0x0 0x0 0x0 0x6 0x1 0x3 0x90 0x9f 0x0 0x1
0235|[2023-10-18 01:13:33]DEBUG : New Transaction state 'SENDING'
0236|[2023-10-18 01:13:33]DEBUG : Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
0237|[2023-10-18 01:13:33]DEBUG : Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
0238|[2023-10-18 01:13:33]DEBUG : RECV: 0x0 0x3 0x0 0x0 0x0 0x3 0x1 0x83 0x2
0239|[2023-10-18 01:13:33]DEBUG : Processing: 0x0 0x3 0x0 0x0 0x0 0x3 0x1 0x83 0x2
0240|[2023-10-18 01:13:33]DEBUG : Factory Response[131]
0241|[2023-10-18 01:13:33]DEBUG : Adding transaction 3
0242|[2023-10-18 01:13:33]DEBUG : Getting transaction 3
0243|[2023-10-18 01:13:33]DEBUG : Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
0244|[2023-10-18 01:13:33]ERROR : Failed to read 1 holding table registers starting from 37023: Exception Response(131, 3, IllegalAddress)
0245|Traceback (most recent call last):
0246|File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 182, in _scan_value_range
0247|return result.registers
0248|AttributeError: 'ExceptionResponse' object has no attribute 'registers'
0249|During handling of the above exception, another exception occurred:
0250|Traceback (most recent call last):
0251|File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 89, in poll
0252|values = self._scan_value_range(table, group, self._scan_batching)
0253|File "/var/www/html/plugins/modbus2mqtt/resources/modbus2mqttd/modbus4mqtt/modbus_interface.py", line 185, in _scan_value_range
0254|raise ValueError("Failed to read {} {} table registers starting from {}: {}".format(count, table, start, result))
0255|ValueError: Failed to read 1 holding table registers starting from 37023: Exception Response(131, 3, IllegalAddress)
0256|[2023-10-18 01:13:33]WARNING : Couldn't get value from register 37023 in table holding
0257|[2023-10-18 01:13:33]WARNING : Couldn't get value from register 32065 in table holding

Mips · Octobre 18, 2023, 5:01

Merci pour le log mais peux-tu aussi décrire le problème? Rien ne remonte ou partiellement ou…?
Je peux voir le log des dépendances aussi? Il va falloir vérifier qu’il n’y a pas un conflit avec mymodbus

Et tu confirmes que mymodbus est coupé? Tu n’as qu’un des deux qui se connecte à ton onduleur à la fois? Y compris modbusdoctor
Car certains devices n’aime pas si plusieurs client se connecte

m.georgein · Octobre 18, 2023, 10:19

Pour les retours, le 16bit retourne toujours -1, le 32bit reste vide

Pour les tests je désactive toujours le plugin myModbus par sécurité

Petite remarque : apparemment l’onduleur Sun2000 demande une tempo avant la première lecture.
sur myModbus on a :

le log des dépendances

0000|+ echo '*******************Begin of package installation******************'
0001|*******************Begin of package installation******************
0002|+ touch /tmp/jeedom_install_in_progress_modbus2mqtt
0003|+ echo 1
0004|+ echo 2
0005|+ sudo apt update
0006|WARNING apt does not have a stable CLI interface. Use with caution in scripts.
0007|Hit:1 http://deb.debian.org/debian buster InRelease
0008|Get:2 http://security.debian.org/debian-security buster/updates InRelease [34.8 kB]
0009|Get:3 https://download.docker.com/linux/debian buster InRelease [54.0 kB]
0010|Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
0011|Get:5 http://security.debian.org/debian-security buster/updates/main Sources [352 kB]
0012|Get:6 http://security.debian.org/debian-security buster/updates/main Translation-en [300 kB]
0013|Fetched 740 kB in 0s (1753 kB/s)
0014|Reading package lists...
0015|Building dependency tree...
0016|Reading state information...
0017|27 packages can be upgraded. Run 'apt list --upgradable' to see them.
0018|+ echo 3
0019|+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3-dev
0020|WARNING apt does not have a stable CLI interface. Use with caution in scripts.
0021|Reading package lists...
0022|Building dependency tree...
0023|Reading state information...
0024|python3-dev is already the newest version (3.7.3-1).
0025|The following packages were automatically installed and are no longer required:
0026|ipset libipset11 python3-decorator python3-selinux python3-slip
0027|python3-slip-dbus
0028|Use 'sudo apt autoremove' to remove them.
0029|0 upgraded, 0 newly installed, 0 to remove and 27 not upgraded.
0030|+ echo 4
0031|++ awk '$1 <= 4'
0032|++ cut -f 2-
0033|++ find /usr/local/lib/python2.7/dist-packages/ /usr/local/lib/python3.7/dist-packages/ -mindepth 1 -maxdepth 1 -type d -exec du -ks '{}' +
0034|+ RESULTTODELETE=
0035|++ echo ''
0036|++ sed 's, ,\ ,g'
0037|+ RESULTTODELETE2=
0038|+ xargs rm -rf
0039|+ echo ''
0040|+ echo 5
0041|+ sudo pip3 cache purge
0042|Files removed: 124
0043|+ echo 6
0044|+ sudo pip3 install --upgrade pip
0045|Requirement already satisfied: pip in /usr/local/lib/python3.7/dist-packages (23.3)
0046|DEPRECATION: reportbug 7.5.3-deb10u1 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 reportbug 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
0047|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
0048|WARNING There was an error checking the latest version of pip.
0049|+ echo 7
0050|+ sudo pip3 install --force-reinstall --upgrade requests
0051|Collecting requests
0052|Downloading requests-2.31.0-py3-none-any.whl.metadata (4.6 kB)
0053|Collecting charset-normalizer<4,>=2 (from requests)
0054|Downloading charset_normalizer-3.3.0-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (32 kB)
0055|Collecting idna<4,>=2.5 (from requests)
0056|Downloading idna-3.4-py3-none-any.whl (61 kB)
0057|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.5/61.5 kB 3.8 MB/s eta 0:00:00
0058|Collecting urllib3<3,>=1.21.1 (from requests)
0059|Downloading urllib3-2.0.7-py3-none-any.whl.metadata (6.6 kB)
0060|Collecting certifi>=2017.4.17 (from requests)
0061|Downloading certifi-2023.7.22-py3-none-any.whl.metadata (2.2 kB)
0062|Downloading requests-2.31.0-py3-none-any.whl (62 kB)
0063|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 62.6/62.6 kB 4.4 MB/s eta 0:00:00
0064|Downloading certifi-2023.7.22-py3-none-any.whl (158 kB)
0065|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 158.3/158.3 kB 5.6 MB/s eta 0:00:00
0066|Downloading charset_normalizer-3.3.0-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (133 kB)
0067|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 133.7/133.7 kB 5.8 MB/s eta 0:00:00
0068|Downloading urllib3-2.0.7-py3-none-any.whl (124 kB)
0069|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 124.2/124.2 kB 6.1 MB/s eta 0:00:00
0070|DEPRECATION: reportbug 7.5.3-deb10u1 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 reportbug 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
0071|Installing collected packages: urllib3, idna, charset-normalizer, certifi, requests
0072|Attempting uninstall: urllib3
0073|Found existing installation: urllib3 2.0.7
0074|Uninstalling urllib3-2.0.7:
0075|Successfully uninstalled urllib3-2.0.7
0076|Attempting uninstall: idna
0077|Found existing installation: idna 3.4
0078|Uninstalling idna-3.4:
0079|Successfully uninstalled idna-3.4
0080|Attempting uninstall: charset-normalizer
0081|Found existing installation: charset-normalizer 3.3.0
0082|Uninstalling charset-normalizer-3.3.0:
0083|Successfully uninstalled charset-normalizer-3.3.0
0084|Attempting uninstall: certifi
0085|Found existing installation: certifi 2023.7.22
0086|Uninstalling certifi-2023.7.22:
0087|Successfully uninstalled certifi-2023.7.22
0088|Attempting uninstall: requests
0089|Found existing installation: requests 2.31.0
0090|Uninstalling requests-2.31.0:
0091|Successfully uninstalled requests-2.31.0
0092|Successfully installed certifi-2023.7.22 charset-normalizer-3.3.0 idna-3.4 requests-2.31.0 urllib3-2.0.7
0093|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
0094|WARNING There was an error checking the latest version of pip.
0095|+ echo 8
0096|+ sudo pip3 install --force-reinstall --upgrade pymodbus
0097|Collecting pymodbus
0098|Downloading pymodbus-2.5.3-py2.py3-none-any.whl (154 kB)
0099|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 154.5/154.5 kB 2.9 MB/s eta 0:00:00
0100|Collecting six>=1.15.0 (from pymodbus)
0101|Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
0102|Collecting pyserial>=3.4 (from pymodbus)
0103|Downloading pyserial-3.5-py2.py3-none-any.whl (90 kB)
0104|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 90.6/90.6 kB 3.6 MB/s eta 0:00:00
0105|DEPRECATION: reportbug 7.5.3-deb10u1 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 reportbug 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
0106|Installing collected packages: pyserial, six, pymodbus
0107|Attempting uninstall: pyserial
0108|Found existing installation: pyserial 3.5
0109|Uninstalling pyserial-3.5:
0110|Successfully uninstalled pyserial-3.5
0111|Attempting uninstall: six
0112|Found existing installation: six 1.16.0
0113|Uninstalling six-1.16.0:
0114|Successfully uninstalled six-1.16.0
0115|Attempting uninstall: pymodbus
0116|Found existing installation: pymodbus 2.5.3
0117|Uninstalling pymodbus-2.5.3:
0118|Successfully uninstalled pymodbus-2.5.3
0119|Successfully installed pymodbus-2.5.3 pyserial-3.5 six-1.16.0
0120|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
0121|WARNING There was an error checking the latest version of pip.
0122|+ echo 9
0123|+ sudo pip3 install --force-reinstall --upgrade setuptools
0124|Collecting setuptools
0125|Downloading setuptools-68.0.0-py3-none-any.whl.metadata (6.4 kB)
0126|Downloading setuptools-68.0.0-py3-none-any.whl (804 kB)
0127|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 804.0/804.0 kB 8.4 MB/s eta 0:00:00
0128|DEPRECATION: reportbug 7.5.3-deb10u1 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 reportbug 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
0129|Installing collected packages: setuptools
0130|Attempting uninstall: setuptools
0131|Found existing installation: setuptools 68.0.0
0132|Uninstalling setuptools-68.0.0:
0133|Successfully uninstalled setuptools-68.0.0
0134|Successfully installed setuptools-68.0.0
0135|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
0136|WARNING There was an error checking the latest version of pip.
0137|+ echo 10
0138|+ sudo pip3 install --force-reinstall --upgrade wheel
0139|Collecting wheel
0140|Downloading wheel-0.41.2-py3-none-any.whl.metadata (2.2 kB)
0141|Downloading wheel-0.41.2-py3-none-any.whl (64 kB)
0142|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 64.8/64.8 kB 6.2 MB/s eta 0:00:00
0143|DEPRECATION: reportbug 7.5.3-deb10u1 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 reportbug 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
0144|Installing collected packages: wheel
0145|Attempting uninstall: wheel
0146|Found existing installation: wheel 0.41.2
0147|Uninstalling wheel-0.41.2:
0148|Successfully uninstalled wheel-0.41.2
0149|Successfully installed wheel-0.41.2
0150|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
0151|WARNING There was an error checking the latest version of pip.
0152|+ echo 11
0153|+ sudo pip3 install --force-reinstall --upgrade ruamel.yaml
0154|Collecting ruamel.yaml
0155|Downloading ruamel.yaml-0.17.35-py3-none-any.whl.metadata (18 kB)
0156|Collecting ruamel.yaml.clib>=0.2.7 (from ruamel.yaml)
0157|Downloading ruamel.yaml.clib-0.2.8-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl.metadata (2.2 kB)
0158|Downloading ruamel.yaml-0.17.35-py3-none-any.whl (112 kB)
0159|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 112.9/112.9 kB 7.2 MB/s eta 0:00:00
0160|Downloading ruamel.yaml.clib-0.2.8-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl (551 kB)
0161|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 551.1/551.1 kB 10.4 MB/s eta 0:00:00
0162|DEPRECATION: reportbug 7.5.3-deb10u1 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 reportbug 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
0163|Installing collected packages: ruamel.yaml.clib, ruamel.yaml
0164|Attempting uninstall: ruamel.yaml.clib
0165|Found existing installation: ruamel.yaml.clib 0.2.8
0166|Uninstalling ruamel.yaml.clib-0.2.8:
0167|Successfully uninstalled ruamel.yaml.clib-0.2.8
0168|Attempting uninstall: ruamel.yaml
0169|Found existing installation: ruamel.yaml 0.17.35
0170|Uninstalling ruamel.yaml-0.17.35:
0171|Successfully uninstalled ruamel.yaml-0.17.35
0172|Successfully installed ruamel.yaml-0.17.35 ruamel.yaml.clib-0.2.8
0173|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
0174|WARNING There was an error checking the latest version of pip.
0175|+ echo 12
0176|+ sudo pip3 install --force-reinstall --upgrade paho-mqtt
0177|Collecting paho-mqtt
0178|Downloading paho-mqtt-1.6.1.tar.gz (99 kB)
0179|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 99.4/99.4 kB 5.9 MB/s eta 0:00:00
0180|Preparing metadata (setup.py): started
0181|Preparing metadata (setup.py): finished with status 'done'
0182|Building wheels for collected packages: paho-mqtt
0183|Building wheel for paho-mqtt (setup.py): started
0184|Building wheel for paho-mqtt (setup.py): finished with status 'done'
0185|Created wheel for paho-mqtt: filename=paho_mqtt-1.6.1-py3-none-any.whl size=62118 sha256=78769a8c10eaa48b3a5e3e3e2f73c37d2afe945568cae3f262c5f6a3904c6bbb
0186|Stored in directory: /root/.cache/pip/wheels/d0/bf/ac/2b3f43f8c6fcd0f4ba5395397458c521eb0b52d33b574a5a40
0187|Successfully built paho-mqtt
0188|DEPRECATION: reportbug 7.5.3-deb10u1 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 reportbug 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
0189|Installing collected packages: paho-mqtt
0190|Attempting uninstall: paho-mqtt
0191|Found existing installation: paho-mqtt 1.6.1
0192|Uninstalling paho-mqtt-1.6.1:
0193|Successfully uninstalled paho-mqtt-1.6.1
0194|Successfully installed paho-mqtt-1.6.1
0195|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
0196|WARNING There was an error checking the latest version of pip.
0197|+ echo 13
0198|+ sudo pip3 install --force-reinstall --upgrade aiohttp
0199|Collecting aiohttp
0200|Downloading aiohttp-3.8.6-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (7.7 kB)
0201|Collecting attrs>=17.3.0 (from aiohttp)
0202|Downloading attrs-23.1.0-py3-none-any.whl (61 kB)
0203|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.2/61.2 kB 4.0 MB/s eta 0:00:00
0204|Collecting charset-normalizer<4.0,>=2.0 (from aiohttp)
0205|Using cached charset_normalizer-3.3.0-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (32 kB)
0206|Collecting multidict<7.0,>=4.5 (from aiohttp)
0207|Downloading multidict-6.0.4-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (94 kB)
0208|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 94.8/94.8 kB 8.3 MB/s eta 0:00:00
0209|Collecting async-timeout<5.0,>=4.0.0a3 (from aiohttp)
0210|Downloading async_timeout-4.0.3-py3-none-any.whl.metadata (4.2 kB)
0211|Collecting yarl<2.0,>=1.0 (from aiohttp)
0212|Downloading yarl-1.9.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (236 kB)
0213|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 236.2/236.2 kB 10.6 MB/s eta 0:00:00
0214|Collecting frozenlist>=1.1.1 (from aiohttp)
0215|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)
0216|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 148.0/148.0 kB 10.7 MB/s eta 0:00:00
0217|Collecting aiosignal>=1.1.2 (from aiohttp)
0218|Downloading aiosignal-1.3.1-py3-none-any.whl (7.6 kB)
0219|Collecting asynctest==0.13.0 (from aiohttp)
0220|Downloading asynctest-0.13.0-py3-none-any.whl (26 kB)
0221|Collecting typing-extensions>=3.7.4 (from aiohttp)
0222|Downloading typing_extensions-4.7.1-py3-none-any.whl.metadata (3.1 kB)
0223|Collecting importlib-metadata (from attrs>=17.3.0->aiohttp)
0224|Downloading importlib_metadata-6.7.0-py3-none-any.whl.metadata (4.9 kB)
0225|Collecting idna>=2.0 (from yarl<2.0,>=1.0->aiohttp)
0226|Using cached idna-3.4-py3-none-any.whl (61 kB)
0227|Collecting zipp>=0.5 (from importlib-metadata->attrs>=17.3.0->aiohttp)
0228|Downloading zipp-3.15.0-py3-none-any.whl (6.8 kB)
0229|Downloading aiohttp-3.8.6-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (987 kB)
0230|━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 988.0/988.0 kB 10.0 MB/s eta 0:00:00
0231|Downloading async_timeout-4.0.3-py3-none-any.whl (5.7 kB)
0232|Using cached charset_normalizer-3.3.0-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (133 kB)
0233|Downloading typing_extensions-4.7.1-py3-none-any.whl (33 kB)
0234|Downloading importlib_metadata-6.7.0-py3-none-any.whl (22 kB)
0235|DEPRECATION: reportbug 7.5.3-deb10u1 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 reportbug 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
0236|Installing collected packages: zipp, typing-extensions, multidict, idna, frozenlist, charset-normalizer, asynctest, yarl, importlib-metadata, async-timeout, aiosignal, attrs, aiohttp
0237|Attempting uninstall: zipp
0238|Found existing installation: zipp 3.15.0
0239|Uninstalling zipp-3.15.0:
0240|Successfully uninstalled zipp-3.15.0
0241|Attempting uninstall: typing-extensions
0242|Found existing installation: typing_extensions 4.7.1
0243|Uninstalling typing_extensions-4.7.1:
0244|Successfully uninstalled typing_extensions-4.7.1
0245|Attempting uninstall: multidict
0246|Found existing installation: multidict 6.0.4
0247|Uninstalling multidict-6.0.4:
0248|Successfully uninstalled multidict-6.0.4
0249|Attempting uninstall: idna
0250|Found existing installation: idna 3.4
0251|Uninstalling idna-3.4:
0252|Successfully uninstalled idna-3.4
0253|Attempting uninstall: frozenlist
0254|Found existing installation: frozenlist 1.3.3
0255|Uninstalling frozenlist-1.3.3:
0256|Successfully uninstalled frozenlist-1.3.3
0257|Attempting uninstall: charset-normalizer
0258|Found existing installation: charset-normalizer 3.3.0
0259|Uninstalling charset-normalizer-3.3.0:
0260|Successfully uninstalled charset-normalizer-3.3.0
0261|Attempting uninstall: asynctest
0262|Found existing installation: asynctest 0.13.0
0263|Uninstalling asynctest-0.13.0:
0264|Successfully uninstalled asynctest-0.13.0
0265|Attempting uninstall: yarl
0266|Found existing installation: yarl 1.9.2
0267|Uninstalling yarl-1.9.2:
0268|Successfully uninstalled yarl-1.9.2
0269|Attempting uninstall: importlib-metadata
0270|Found existing installation: importlib-metadata 6.7.0
0271|Uninstalling importlib-metadata-6.7.0:
0272|Successfully uninstalled importlib-metadata-6.7.0
0273|Attempting uninstall: async-timeout
0274|Found existing installation: async-timeout 4.0.3
0275|Uninstalling async-timeout-4.0.3:
0276|Successfully uninstalled async-timeout-4.0.3
0277|Attempting uninstall: aiosignal
0278|Found existing installation: aiosignal 1.3.1
0279|Uninstalling aiosignal-1.3.1:
0280|Successfully uninstalled aiosignal-1.3.1
0281|Attempting uninstall: attrs
0282|Found existing installation: attrs 23.1.0
0283|Uninstalling attrs-23.1.0:
0284|Successfully uninstalled attrs-23.1.0
0285|Attempting uninstall: aiohttp
0286|Found existing installation: aiohttp 3.8.6
0287|Uninstalling aiohttp-3.8.6:
0288|Successfully uninstalled aiohttp-3.8.6
0289|Successfully installed aiohttp-3.8.6 aiosignal-1.3.1 async-timeout-4.0.3 asynctest-0.13.0 attrs-23.1.0 charset-normalizer-3.3.0 frozenlist-1.3.3 idna-3.4 importlib-metadata-6.7.0 multidict-6.0.4 typing-extensions-4.7.1 yarl-1.9.2 zipp-3.15.0
0290|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
0291|WARNING There was an error checking the latest version of pip.
0292|+ echo 14
0293|+ php /var/www/html/core/class/../php/jeecli.php plugin install mqtt2
0294|warning: commands will be executed using /bin/sh
0295|job 37 at Wed Oct 18 12:08:00 2023
0296|+ echo 15
0297|+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end modbus2mqtt
0298|+ rm /tmp/jeedom_install_in_progress_modbus2mqtt
0299|+ echo '*******************End of package installation******************'
0300|*******************End of package installation******************

Mips · Octobre 27, 2023, 7:58

Dans les premières captures & log je vois que tu lisais l’adresse 32066 et là tu recois l’erreur : No Response received from the remote
mais ensuite tu essaies de lire le registre 32065 ou 37023 et là l’erreur est Exception Response(131, 3, IllegalAddress)
donc déjà c’est pas pareil dans tous les tests; es-tu sur de la config?

concernant le délai entre chaque lecture, c’est la config « actualisation »

je vois que tu as mis 10s aussi
effectivement il n’y a pas de délai entre le premier connect et le moment ou il commence à lire mais ensuite c’est le cas, y compris s’il doit se reconnecter et d’ailleurs on le voit dans ton log

m.georgein:

0195|[2023-10-18 01:13:22]DEBUG : Connection to Modbus server established. Socket ('192.168.2.196', 53697)
0196|[2023-10-18 01:13:32]DEBUG : Current transaction state - IDLE
0197|[2023-10-18 01:13:32]DEBUG : Running transaction 1
0198|[2023-10-18 01:13:32]DEBUG : SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x1 0x3 0x7d 0x41 0x0 0x1
0199|[2023-10-18 01:13:32]DEBUG : New Transaction state 'SENDING'

il y a bien eu 10s entre le connect et le read suivant

j’ai malgré tout mis à jour en beta pour attendre aussi avant la toute première lecture, au cas où…

ngm47 · Avril 11, 2024, 7:57

Bonsoir,

J’hésite également à remplacer mymodbus par Mqtt2modbus… mais la différence de performance ou de ressource est-elle significative ?

Merci

Mips · Avril 11, 2024, 9:27

Bonjour,

Je ne comprends pas le rapport avec le sujet, il y en a un?

ngm47 · Avril 12, 2024, 5:10

Bonjour,

Nous avons le même projet, remplacer mymodbus par modbus Mqtt.
Je ne voulais pas ouvrir un sujet uniquement pour ça…
De plus, j’ai pas mal d’équipement Modbus sur mon installation, je pouvais éventuellement essayé de reproduire son problème.

Mips · Avril 12, 2024, 6:03

Ok
Rapport à la consommation de ressources je ne vais pas me prononcer plus que ça.

Tout ce que je peux dire c’est qu’en 2022 j’avais testé mymodbus et je n’ai pas été satisfait par la consommation cpu et ram.
Je passe les détails des tentatives pour y remédier, j’ai finalement développé ce plugin ci.

Michel_F · Avril 12, 2024, 8:48

Bonjour,

Je m’immisce dans la conversation pour plussoyer et c’est la raison pour laquelle j’ai proposé fin 2022 à Bebel27, le propriétaire du plugin MyModbus, de réécrire le plugin. Donc je suis 100% d’accord avec Mips sur les performances de MyModbus version stable.

Sans faire de pub puisque je n'y gagne rien...

Je suis en train de revoir la version bêta pour respecter les principes proposés par Mips sur la gestion d’un démon avec asyncio, et j’en ai profité pour approfondir mes connaissances sur asyncio. Ca prend du temps, mais c’est en cours.

A+
Michel

Mips · Avril 12, 2024, 8:54

Oui bien sur, j’aurais du préciser qu’il y a manifestement eu un gros boulot de fait par @Michel_F (que je n’ai pas testé)

Du coup je dirais que si d’un point de vue fonctionnalité vous êtes satisfait par mymodbus, testez la beta de celui-ci, ca fera moins de boulot de migration je suppose

ngm47 · Avril 12, 2024, 11:02

Merci à vous pour votre point de vue, je reste en Beta Mymodbus en espérant une version stable courant de l’année.

Bonne journée