Missing 1 required positional argument: 'callback_api_version'

Plugins Passerelle domotique
1

Bonjour,

j’ai le démon de MerosSync qui est arrêté, impossible de le démarrer malgré une relance de la dépendance.

[2024-03-07 21:55:08] DEBUG  : 21031633392407290d4848e1e962a50c = action: off_5 - params {"background":"0"}
[2024-03-07 21:55:08] DEBUG  : callMeross setOff Array (     [0] => 21031633392407290d4848e1e962a50c     [1] => 5 )
[2024-03-07 21:55:08] DEBUG  : Socket unix:///tmp/jeedom/MerosSync/daemon.sock
[2024-03-07 21:55:08] INFO  : noStreamSocket 111 - Connection refused
[2024-03-07 21:55:08] ERROR  : Merci de démarrer le démon !
[2024-03-07 21:55:08] DEBUG  : result callMeross
[2024-03-07 21:55:08] DEBUG  : setOff: ""
[2024-03-07 21:55:08] DEBUG  : mise à jour état
[2024-03-07 21:56:04] DEBUG  : 21031633392407290d4848e1e962a50c = action: off_5 - params {"background":"0"}
[2024-03-07 21:56:04] DEBUG  : callMeross setOff Array (     [0] => 21031633392407290d4848e1e962a50c     [1] => 5 )
[2024-03-07 21:56:04] DEBUG  : Socket unix:///tmp/jeedom/MerosSync/daemon.sock
[2024-03-07 21:56:04] INFO  : noStreamSocket 111 - Connection refused
[2024-03-07 21:56:04] ERROR  : Merci de démarrer le démon !
[2024-03-07 21:56:04] DEBUG  : result callMeross
[2024-03-07 21:56:04] DEBUG  : setOff: ""
[2024-03-07 21:56:04] DEBUG  : mise à jour état
[2024-03-07 21:56:24] INFO  : Lancement démon meross : /usr/bin/python3 /var/www/html/plugins/MerosSync/resources/MerossIOTd/MerossIOTd.py --muser "xxx" --mpswd "xxx" --callback http://127.0.0.1:80/plugins/MerosSync/core/php/jeeMerosSync.php --apikey KlpPmUy80NbVqkTqaeEnrEh3rJ2cfZkJ0wRSLHvVIUTZCiuLl0wNTrJvIU4lpMWB --loglevel debug --pid /tmp/jeedom/MerosSync/daemon.pid --errorfile /tmp/jeedom/MerosSync/errordaemon.pid --socket /tmp/jeedom/MerosSync/daemon.sock --logfile /var/www/html/core/class/../../log/MerosSync
[2024-03-07 20:56:26] DEBUG [meross_iot] : Test logger merossIOT
[2024-03-07 20:56:26] INFO [DemonPython] : Current version is : 0.4.6.2
[2024-03-07 20:56:26] INFO [DemonPython] : Start MerossIOTd
[2024-03-07 20:56:26] INFO [DemonPython] : Log level : debug
[2024-03-07 20:56:26] INFO [DemonPython] : Socket : /tmp/jeedom/MerosSync/daemon.sock
[2024-03-07 20:56:26] INFO [DemonPython] : PID file : /tmp/jeedom/MerosSync/daemon.pid
[2024-03-07 20:56:26] INFO [DemonPython] : Error file : /tmp/jeedom/MerosSync/errordaemon.pid
[2024-03-07 20:56:26] INFO [DemonPython] : Apikey : KlpPmUy80NbVqkTqaeEnrEh3rJ2cfZkJ0wRSLHvVIUTZCiuLl0wNTrJvIU4lpMWB
[2024-03-07 20:56:26] INFO [DemonPython] : Callback : http://127.0.0.1:80/plugins/MerosSync/core/php/jeeMerosSync.php
[2024-03-07 20:56:26] INFO [DemonPython] : Python version : 3.9.2 (default, Feb 28 2021, 17:03:44)
[GCC 10.2.1 20210110]
[2024-03-07 20:56:26] DEBUG [DemonPython] : Mise en place signal
[2024-03-07 20:56:26] DEBUG [DemonPython] : Test Callback
[2024-03-07 20:56:26] DEBUG [DemonPython] : Envoi un test à jeedom
[2024-03-07 20:56:26] DEBUG [DemonPython] : Envoie à jeedom :  {'action': 'test'}
[2024-03-07 21:56:26] DEBUG  : Array (     [action] => test )
[2024-03-07 20:56:26] DEBUG [DemonPython] : Réponse de jeedom :  {'success': True}
[2024-03-07 20:56:26] DEBUG [DemonPython] : Démarrage socket
[2024-03-07 20:56:26] DEBUG [DemonPython] : Test connection Meross
[2024-03-07 20:56:26] DEBUG [DemonPython] : Connecting with user *****@gmail.com - ********* => *********
[2024-03-07 20:56:26] DEBUG [meross_iot.http_api] : Logging in with email: *****@gmail.com, password: XXXXX
[2024-03-07 20:56:26] DEBUG [meross_iot.http_api] : Performing HTTP request against https://iotx-eu.meross.com/v1/Auth/signIn, headers: {'AppVersion': '0.4.6.2', 'Authorization': 'Basic', 'vender': 'meross', 'AppType': 'MerossIOT', 'AppLanguage': 'EN', 'User-Agent': 'MerossIOT/0.4.6.2', 'Content-Type': 'application/json'}, post data: {'params': 'eyJlbWFpbCI6ICJ2aW52aW5zeWx2YWluLnNyQGdtYWlsLmNvbSIsICJwYXNzd29yZCI6ICI3MmJlOWNiOGE1ZjI2NzMwYTViNmRhNTQ5ZDQ4YmFlMyIsICJhY2NvdW50Q291bnRyeUNvZGUiOiAidXMiLCAiZW5jcnlwdGlvbiI6IDEsICJhZ3JlZSI6IDAsICJtb2JpbGVJbmZvIjogeyJkZXZpY2VNb2RlbCI6ICJhYXJjaDY0IiwgIm1vYmlsZU9zVmVyc2lvbiI6ICIjMTAxIFNNUCBXZWQgU2VwIDE0IDAxOjQ5OjIzIFVUQyAyMDIyIiwgIm1vYmlsZU9zIjogIkxpbnV4IiwgInV1aWQiOiAiMWUyNTA3NTg4OWU1NGI0ZWI3ODdmYTY0MTlkZWU4YWI4NjYyZWItNTAxZi00NjFlLWEwMTMtMzUwZjljOTE4NjM0IiwgImNhcnJpZXIiOiAiIn19', 'sign': '19ad83b68bb8ebe103cbc1e2fb73a7ba', 'timestamp': 1709844986863, 'nonce': 'O8NUHKEBCVOF7GZS'}
[2024-03-07 20:56:27] DEBUG [meross_iot.http_api] : Response Status Code: 200
[2024-03-07 20:56:27] INFO [meross_iot.http_api] : Login successful against https://iotx-eu.meross.com
[2024-03-07 20:56:27] DEBUG [meross_iot.http_api] : Performing HTTP request against https://iotx-eu.meross.com/v1/log/user, headers: {'AppVersion': '0.4.6.2', 'Authorization': 'Basic 6430dc1d865f7b499a184ec0519ed8894446a606a11449df86dbf8c53dd49134', 'vender': 'meross', 'AppType': 'MerossIOT', 'AppLanguage': 'EN', 'User-Agent': 'MerossIOT/0.4.6.2', 'Content-Type': 'application/json'}, post data: {'params': 'eyJzeXN0ZW0iOiAiTGludXgiLCAidmVuZG9yIjogIm1lcm9zcyIsICJ1dWlkIjogIjFlMjUwNzU4ODllNTRiNGViNzg3ZmE2NDE5ZGVlOGFiODY2MmViLTUwMWYtNDYxZS1hMDEzLTM1MGY5YzkxODYzNCIsICJleHRyYSI6ICIiLCAibW9kZWwiOiAiYWFyY2g2NCIsICJ2ZXJzaW9uIjogIiMxMDEgU01QIFdlZCBTZXAgMTQgMDE6NDk6MjMgVVRDIDIwMjIifQ==', 'sign': '77fd3519aef515da4ac92d1cf8131960', 'timestamp': 1709844987211, 'nonce': 'L5M8YSMOPFMC6HKU'}
[2024-03-07 20:56:27] DEBUG [meross_iot.http_api] : Response Status Code: 200
[2024-03-07 20:56:27] DEBUG [meross_iot.http_api] : Login successful!
[2024-03-07 20:56:27] DEBUG [DemonPython] : Connected with user *****@gmail.com
[2024-03-07 20:56:27] INFO [meross_iot.manager] :
------- Triggering Manager Discovery, filter_device: [None] -------
[2024-03-07 20:56:27] DEBUG [meross_iot.http_api] : Performing HTTP request against https://iotx-eu.meross.com/v1/Device/devList, headers: {'AppVersion': '0.4.6.2', 'Authorization': 'Basic 6430dc1d865f7b499a184ec0519ed8894446a606a11449df86dbf8c53dd49134', 'vender': 'meross', 'AppType': 'MerossIOT', 'AppLanguage': 'EN', 'User-Agent': 'MerossIOT/0.4.6.2', 'Content-Type': 'application/json'}, post data: {'params': 'e30=', 'sign': '12f32233a01a756e3d9d7e453b4fcfe4', 'timestamp': 1709844987540, 'nonce': 'AO7LOYQA3URNR3HX'}
[2024-03-07 20:56:27] DEBUG [meross_iot.http_api] : Response Status Code: 200
[2024-03-07 20:56:27] DEBUG [meross_iot.manager] : The following devices were already known to me: {}
[2024-03-07 20:56:27] DEBUG [meross_iot.manager] : The following devices are new to me: [{"uuid": "21031633392407290d4848e1e962a50c", "online_status": "ONLINE", "dev_name": "multiprise", "dev_icon_id": "device020_fr", "bind_time": "2023-12-20T22:04:12", "device_type": "mss425f", "sub_type": "fr", "channels": [{}, {"type": "Switch", "devName": "t\u00e9l\u00e9vision", "devIconId": "device001"}, {"type": "Switch", "devName": "wii", "devIconId": "device001"}, {"type": "Switch", "devName": "dvd", "devIconId": "device001"}, {"type": "Switch", "devName": "lampe plante", "devIconId": "device001"}, {"type": "USB", "devName": "camera", "devIconId": "device001"}], "region": "eu", "fmware_version": "3.1.4", "hdware_version": "3.0.0", "user_dev_icon": "", "icon_type": 1, "skill_number": null, "domain": "mqtt-eu.meross.com", "reserved_domain": "mqtt-eu.meross.com"}]
[2024-03-07 20:56:27] DEBUG [meross_iot.manager] : Sending GET-Namespace.SYSTEM_ABILITY command via MQTT to 21031633392407290d4848e1e962a50c via mqtt-eu.meross.com:443
[2024-03-07 20:56:27] INFO [meross_iot.manager] : Allocating new mqtt client for mqtt-eu.meross.com:443...
Exception ignored in: <function Client.__del__ at 0x7f835abee0>
Traceback (most recent call last):
File "/usr/local/lib/python3.9/dist-packages/paho/mqtt/client.py", line 874, in __del__
self._reset_sockets()
File "/usr/local/lib/python3.9/dist-packages/paho/mqtt/client.py", line 1133, in _reset_sockets
self._sock_close()
File "/usr/local/lib/python3.9/dist-packages/paho/mqtt/client.py", line 1119, in _sock_close
if not self._sock:
AttributeError: 'Client' object has no attribute '_sock'
[2024-03-07 20:56:27] ERROR [DemonPython] : __init__() missing 1 required positional argument: 'callback_api_version'
[2024-03-07 20:56:27] DEBUG [DemonPython] : Ecriture du PID 22508 dans /tmp/jeedom/MerosSync/errordaemon.pid
__init__() missing 1 required positional argument: 'callback_api_version'
[2024-03-07 21:56:29] ERROR  : Impossible de lancer le démon meross, vérifiez la log

Informations Jeedom Luna

Core : 4.4.2 (beta)
DNS Jeedom Luna : oui

Plugin : MerosSync
Version : 2024-02-19 09:50:59 (stable)
Statut Démon : Stoppé - (2024-03-07 21:51:44)
2

Bonjour,

L’erreur que vous avez maintenant est là parce que vous avez relancé le dépendances…
Problème connu avec la lib paho.mqtt, une mise à jour du plugin est nécessaire.
Voir les autres sujets sur community.

3

Bonjour @vinvinsylvain ,

C’est effectivement surprenant car la version que vous avez corrige le problème mentionné par Mips de paho.mqtt (voir Plugin ne synchronise pas)

Donc je dirais que le plus simple est de mettre à jour les dépendances puis nous transmettre les logs et ensuite lancer le démon.

Cela devrait normalement corriger le problème.

Bonne journée
Jérôme

4

c’est la mise a jour du pluning ? j’ai relancer aussi la dépendance, puis installer la version beta puis la version stable, toujours le même problème de demon ne veux pas se lancer

[2024-03-08 09:03:03] DEBUG  : 21031633392407290d4848e1e962a50c = action: on_5 - params {"background":"0"}
[2024-03-08 09:03:03] DEBUG  : callMeross setOn Array (     [0] => 21031633392407290d4848e1e962a50c     [1] => 5 )
[2024-03-08 09:03:03] DEBUG  : Socket unix:///tmp/jeedom/MerosSync/daemon.sock
[2024-03-08 09:03:03] INFO  : noStreamSocket 111 - Connection refused
[2024-03-08 09:03:03] ERROR  : Merci de démarrer le démon !
[2024-03-08 09:03:03] DEBUG  : result callMeross
[2024-03-08 09:03:03] DEBUG  : setOn: ""
[2024-03-08 09:03:03] DEBUG  : mise à jour état
5

Bonjour @vinvinsylvain ,

Est-ce possible d’avoir la log d’installation des dépendances ?
Merci

6

Voici le log d’installation je croix:

Installation des dépendances
Hit:1 https://deb.debian.org/debian bullseye InRelease
Get:2 https://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB]
Get:3 https://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Get:4 https://deb.debian.org/debian bullseye-backports InRelease [49.0 kB]
Hit:5 https://download.docker.com/linux/debian bullseye InRelease
Hit:6 https://deb.nodesource.com/node_18.x nodistro InRelease
Fetched 141 kB in 5s (26.0 kB/s)
Reading package lists...
Installation libffi-dev
Reading package lists...
Building dependency tree...
Reading state information...
libffi-dev is already the newest version (3.3-6).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Installation python3
Reading package lists...
Building dependency tree...
Reading state information...
python3 is already the newest version (3.9.2-3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Installation python3-pip
Reading package lists...
Building dependency tree...
Reading state information...
python3-pip is already the newest version (20.3.4-4+deb11u1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Installation python3-requests
Reading package lists...
Building dependency tree...
Reading state information...
python3-requests is already the newest version (2.25.1+dfsg-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Installation python3-setuptools
Reading package lists...
Building dependency tree...
Reading state information...
python3-setuptools is already the newest version (52.0.0-4).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Installation python3-dev
Reading package lists...
Building dependency tree...
Reading state information...
python3-dev is already the newest version (3.9.2-3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Empty cache
Files removed: 4
Installation upgrade pip
Requirement already satisfied: pip in /usr/local/lib/python3.9/dist-packages (24.0)
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of gpg or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at https://github.com/pypa/pip/issues/12063
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
Installation upgrade requests
Requirement already satisfied: requests in /usr/local/lib/python3.9/dist-packages (2.31.0)
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/local/lib/python3.9/dist-packages (from requests) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in /usr/lib/python3/dist-packages (from requests) (2.10)
Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/lib/python3/dist-packages (from requests) (1.26.5)
Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3/dist-packages (from requests) (2020.6.20)
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of gpg or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at https://github.com/pypa/pip/issues/12063
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
Installation upgrade merossiot
Requirement already satisfied: meross_iot==0.4.6.2 in /usr/local/lib/python3.9/dist-packages (0.4.6.2)
Requirement already satisfied: paho-mqtt<2.0.0,>=1.5.0 in /usr/local/lib/python3.9/dist-packages (from meross_iot==0.4.6.2) (1.6.1)
Requirement already satisfied: requests<3.0.0,>=2.19.1 in /usr/local/lib/python3.9/dist-packages (from meross_iot==0.4.6.2) (2.31.0)
Requirement already satisfied: aiohttp<4.0.0,>=3.7.4.post0 in /usr/local/lib/python3.9/dist-packages (from aiohttp[speedups]<4.0.0,>=3.7.4.post0->meross_iot==0.4.6.2) (3.9.3)
Requirement already satisfied: aiosignal>=1.1.2 in /usr/local/lib/python3.9/dist-packages (from aiohttp<4.0.0,>=3.7.4.post0->aiohttp[speedups]<4.0.0,>=3.7.4.post0->meross_iot==0.4.6.2) (1.3.1)
Requirement already satisfied: attrs>=17.3.0 in /usr/local/lib/python3.9/dist-packages (from aiohttp<4.0.0,>=3.7.4.post0->aiohttp[speedups]<4.0.0,>=3.7.4.post0->meross_iot==0.4.6.2) (23.2.0)
Requirement already satisfied: frozenlist>=1.1.1 in /usr/local/lib/python3.9/dist-packages (from aiohttp<4.0.0,>=3.7.4.post0->aiohttp[speedups]<4.0.0,>=3.7.4.post0->meross_iot==0.4.6.2) (1.4.1)
Requirement already satisfied: multidict<7.0,>=4.5 in /usr/local/lib/python3.9/dist-packages (from aiohttp<4.0.0,>=3.7.4.post0->aiohttp[speedups]<4.0.0,>=3.7.4.post0->meross_iot==0.4.6.2) (6.0.5)
Requirement already satisfied: yarl<2.0,>=1.0 in /usr/local/lib/python3.9/dist-packages (from aiohttp<4.0.0,>=3.7.4.post0->aiohttp[speedups]<4.0.0,>=3.7.4.post0->meross_iot==0.4.6.2) (1.9.4)
Requirement already satisfied: async-timeout<5.0,>=4.0 in /usr/local/lib/python3.9/dist-packages (from aiohttp<4.0.0,>=3.7.4.post0->aiohttp[speedups]<4.0.0,>=3.7.4.post0->meross_iot==0.4.6.2) (4.0.3)
Requirement already satisfied: Brotli in /usr/local/lib/python3.9/dist-packages (from aiohttp[speedups]<4.0.0,>=3.7.4.post0->meross_iot==0.4.6.2) (1.1.0)
Requirement already satisfied: aiodns in /usr/local/lib/python3.9/dist-packages (from aiohttp[speedups]<4.0.0,>=3.7.4.post0->meross_iot==0.4.6.2) (3.1.1)
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/local/lib/python3.9/dist-packages (from requests<3.0.0,>=2.19.1->meross_iot==0.4.6.2) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in /usr/lib/python3/dist-packages (from requests<3.0.0,>=2.19.1->meross_iot==0.4.6.2) (2.10)
Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/lib/python3/dist-packages (from requests<3.0.0,>=2.19.1->meross_iot==0.4.6.2) (1.26.5)
Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3/dist-packages (from requests<3.0.0,>=2.19.1->meross_iot==0.4.6.2) (2020.6.20)
Requirement already satisfied: pycares>=4.0.0 in /usr/local/lib/python3.9/dist-packages (from aiodns->aiohttp[speedups]<4.0.0,>=3.7.4.post0->meross_iot==0.4.6.2) (4.4.0)
Requirement already satisfied: cffi>=1.5.0 in /usr/local/lib/python3.9/dist-packages (from pycares>=4.0.0->aiodns->aiohttp[speedups]<4.0.0,>=3.7.4.post0->meross_iot==0.4.6.2) (1.16.0)
Requirement already satisfied: pycparser in /usr/local/lib/python3.9/dist-packages (from cffi>=1.5.0->pycares>=4.0.0->aiodns->aiohttp[speedups]<4.0.0,>=3.7.4.post0->meross_iot==0.4.6.2) (2.21)
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of gpg or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at https://github.com/pypa/pip/issues/12063
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
Installation des dépendances terminée !
7

quelqu’un aurait une solution ?

8

Bonjour @vinvinsylvain
Cette erreur est un peu bizarre :
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of gpg or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at Deprecate legacy versions and version specifiers · Issue #12063 · pypa/pip · GitHub

Va dans le centre de mise à jour

image
puis OS/package

image

Dans la colonne « Nom » saisi « gpg » et voit si une mise à jour est disponible. Cela vaudrait le coup de le faire…

9

Sinon voici les différences de version que l’on a

complément Jercle vinvinsylvain
paho-mqtt (1.6.1) (1.6.1)
requests (2.31.0) (2.31.0)
aiohttp (3.8.4) (3.9.3)
attrs (22.2.0) (23.2.0)
charset-normalizer (3.0.1) (3.3.2)
multidict (6.0.4) (6.0.5)
async-timeout (4.0.2) (4.0.3)
yarl (1.8.2) (1.9.4)
frozenlist (1.3.3) (1.4.1)
aiosignal (1.3.1) (1.3.1)
asynctest (0.13.0) absent
typing-extensions (4.5.0) absent
aiodns (3.0.0) (3.1.1)
Brotli (1.0.9) (1.1.0)
cchardet (2.1.7) absent
idna (2.6) (2.10)
urllib3 (1.24.1) (1.26.5)
certifi (2018.8.24) (2020.6.20)
pycares (4.3.0) (4.4.0)
cffi (1.15.1) (1.16.0)
pycparser (2.21) (2.21)

Je suis donc surpris de ne pas voir certaines versions…

Il faudra peut être lancer à la main l’installation type
sudo pip3 install --upgrade typing-extensions
sudo pip3 install --upgrade asynctest
sudo pip3 install --upgrade cchardet

10

bonsoir, je n’ai pas OS/package

image
image1119×184 9.66 KB

11

C’est toujours pas la bonne version de paho.mqtt qui est installée

Si ce plugin force une 1.6 et qu’un autre installe une 2.0 ca n’ira jamais et sur une lib telle que celle là on ne peut pas forcer une version inférieure, surtout en global, ca va impacter potentiellement tous les plugins.

Il faudrait aussi créer un venv pour éviter les conflits entre plugins

Normale sur une smart à priori

12

je fais comment ?

13

Comment mettre a jour la bonne version ?

14

si je réinstaller la dernière image de Jeedom luna, est ce que cela va résoudre mon problème ?

15

Non, cela n’aidera pas à résoudre le problème sur paho.mqtt

Voir le premier post cité ci-dessus, dans un des messages je donne la commande pour installer manuellement une version; mais je vous recommande de ne pas faire d’action manuelle.

Soit le plugin a besoin de la version 1.6.x soit 2.0;
mais le problème c’est (peut-être) qu’un autre plugin que vous avez installe lui aussi globalement sur le système une version différente de celui-ci. Dans ce cas il n’y a pas d’autre solution qu’une mise à jour des plugins.

16

@vinvinsylvain
Depuis quand le problème existe sur le plugin ? Si ce n’est que récemment : a voir si c’est lié à la mise à jour récente d’un plugin ou l’installation d’un nouveau.

17

depuis pas longtemps, a mes souvenirs aucunes mise a jours ressente.

18

toujours avec le problème , aucune solution ?

19

La solution que j’ai trouver, reflasher la box luna, remettre les bonnes versions:
Version : 4.3.23
Source : default
Branche : V4-stable

refaire les plunings un par un.

20

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