Mon Roborock est bien reconnu mais les commandes ne remontent pas

ninori · Janvier 31, 2024, 5:36

Bonjour,

Suite à un crash de mon ESXi j’ai remonté une VM en Debian 10 (la version de mon ESXi nécessite un upgrade pour passer en version 11 ou 12) et depuis j’ai des soucis pour faire remonter les infos de mon roborock S7… je ne comprend bien d’où cela peut bien venir le robot est bien détecté mais aucune commande ne remonte… (je précise que ça fonctionnait au poil avant mon crash).
Voici les lois à toutes fins utiles :

[2024-01-31 18:26:15][DEBUG] : ============================ DISCOVER ============================
[2024-01-31 18:26:16][DEBUG] : ["[{\"did\": \"535464230\", \"token\": \"xxxxx\", \"longitude\": \"0.0\", \"latitude\": \"0.0\", \"name\": \"Roborock S7 MaxV\", \"pid\": \"0\", \"localip\": \"192.168.15.20\", \"mac\": \"B0:4A:39:48:CA:26\", \"ssid\": \"OrbiLab\", \"bssid\": \"0E:36:C9:1E:BC:2E\", \"parent_id\": \"\", \"parent_model\": \"\", \"show_mode\": 1, \"model\": \"roborock.vacuum.a27\", \"adminFlag\": 1, \"shareFlag\": 0, \"permitLevel\": 16, \"isOnline\": true, \"desc\": \"Device online \", \"extra\": {\"isSetPincode\": 0, \"pincodeType\": 0, \"fw_version\": \"4.3.5_5840\", \"needVerifyCode\": 0, \"isPasswordEncrypt\": 0}, \"uid\": 8185725052, \"pd_id\": 72166, \"password\": \"\", \"p2p_id\": \"\", \"rssi\": -55, \"family_id\": 0, \"reset_flag\": 0}]"]
[2024-01-31 18:26:16][DEBUG] : [{"did":"535464230","token":"xxxxx","longitude":"0.0","latitude":"0.0","name":"Roborock S7 MaxV","pid":"0","localip":"192.168.15.20","mac":"B0:4A:39:48:CA:26","ssid":"OrbiLab","bssid":"0E:36:C9:1E:BC:2E","parent_id":"","parent_model":"","show_mode":1,"model":"roborock.vacuum.a27","adminFlag":1,"shareFlag":0,"permitLevel":16,"isOnline":true,"desc":"Device online ","extra":{"isSetPincode":0,"pincodeType":0,"fw_version":"4.3.5_5840","needVerifyCode":0,"isPasswordEncrypt":0},"uid":8185725052,"pd_id":72166,"password":"","p2p_id":"","rssi":-55,"family_id":0,"reset_flag":0}]
[2024-01-31 18:26:16][DEBUG] : Nouvel Equipement, ajout en cours.
[2024-01-31 18:26:16][DEBUG] : ============================ CREATING CMD ============================
[2024-01-31 18:26:16][DEBUG] : GENERATE CMD FROM CONFIG FILE : /var/www/html/plugins/mirobot/core/class/../conf/genericmiot.json
[2024-01-31 18:26:16][DEBUG] : CMD BY genericmiot => sudo  /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty genericmiot --ip 192.168.15.20 --token xxxxx status  >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_4238.txt
[2024-01-31 18:26:16][DEBUG] : CMD result null
[2024-01-31 18:26:32][DEBUG] : removing all commands
[2024-01-31 18:26:32][DEBUG] : ============================ CREATING CMD ============================
[2024-01-31 18:26:32][DEBUG] : GENERATE CMD FROM CONFIG FILE : /var/www/html/plugins/mirobot/core/class/../conf/roborockvacuum.json
[2024-01-31 18:26:32][DEBUG] : CMD BY roborockvacuum => sudo  /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.15.20 --token xxxxx status  >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_4238.txt
[2024-01-31 18:26:33][DEBUG] : CMD result null
[2024-01-31 18:26:33][DEBUG] : CMD BY roborockvacuum => sudo  /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.15.20 --token xxxxx get_room_mapping  >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_4238.txt
[2024-01-31 18:26:33][DEBUG] : CMD result null
[2024-01-31 18:27:02][DEBUG] : ============================ UPDATING CMD ============================
[2024-01-31 18:27:02][DEBUG] : GENERATE CMD FROM CONFIG FILE : /var/www/html/plugins/mirobot/core/class/../conf/roborockvacuum.json
[2024-01-31 18:27:02][DEBUG] : CMD BY roborockvacuum => sudo  /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.15.20 --token xxxxx status  >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_4238.txt
[2024-01-31 18:27:03][DEBUG] : CMD result null
[2024-01-31 18:28:01][DEBUG] : ============================ UPDATING CMD ============================
[2024-01-31 18:28:01][DEBUG] : GENERATE CMD FROM CONFIG FILE : /var/www/html/plugins/mirobot/core/class/../conf/roborockvacuum.json
[2024-01-31 18:28:01][DEBUG] : CMD BY roborockvacuum => sudo  /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.15.20 --token xxxxx status  >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_4238.txt
[2024-01-31 18:28:02][DEBUG] : CMD result null
[2024-01-31 18:29:02][DEBUG] : ============================ UPDATING CMD ============================
[2024-01-31 18:29:02][DEBUG] : GENERATE CMD FROM CONFIG FILE : /var/www/html/plugins/mirobot/core/class/../conf/roborockvacuum.json
[2024-01-31 18:29:02][DEBUG] : CMD BY roborockvacuum => sudo  /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.15.20 --token xxxxx status  >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_4238.txt
[2024-01-31 18:29:02][DEBUG] : CMD result null
[2024-01-31 18:30:46][DEBUG] : ============================ UPDATING CMD ============================
[2024-01-31 18:30:46][DEBUG] : GENERATE CMD FROM CONFIG FILE : /var/www/html/plugins/mirobot/core/class/../conf/roborockvacuum.json
[2024-01-31 18:30:46][DEBUG] : CMD BY roborockvacuum => sudo  /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.15.20 --token xxxxx status  >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_4238.txt
[2024-01-31 18:30:47][DEBUG] : CMD result null

Le fichier d’erreur

Traceback (most recent call last):
  File "/var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli", line 5, in <module>
    from miio.cli import create_cli
  File "/var/www/html/plugins/mirobot/resources/venv/lib/python3.8/site-packages/miio/__init__.py", line 96, in <module>
    from miio.discovery import Discovery
  File "/var/www/html/plugins/mirobot/resources/venv/lib/python3.8/site-packages/miio/discovery.py", line 6, in <module>
    import zeroconf
  File "/var/www/html/plugins/mirobot/resources/venv/lib/python3.8/site-packages/zeroconf/__init__.py", line 25, in <module>
    from ._cache import DNSCache  # noqa # import needed for backwards compat
  File "src/zeroconf/_cache.py", line 1, in init zeroconf._cache
  File "src/zeroconf/_protocol/incoming.py", line 1, in init zeroconf._protocol.incoming
  File "src/zeroconf/_protocol/outgoing.py", line 1, in init zeroconf._protocol.outgoing
  File "src/zeroconf/_dns.py", line 28, in init zeroconf._dns
  File "/var/www/html/plugins/mirobot/resources/venv/lib/python3.8/site-packages/zeroconf/_utils/net.py", line 31, in <module>
    import ifaddr
  File "/var/www/html/plugins/mirobot/resources/venv/lib/python3.8/site-packages/ifaddr/__init__.py", line 24, in <module>
    from ifaddr._shared import Adapter, IP
  File "/var/www/html/plugins/mirobot/resources/venv/lib/python3.8/site-packages/ifaddr/_shared.py", line 22, in <module>
    import ctypes
  File "/usr/local/lib/python3.8/ctypes/__init__.py", line 7, in <module>
    from _ctypes import Union, Structure, Array
ModuleNotFoundError: No module named '_ctypes'

Si quelqu’un a la solution je suis preneur!! Merci

Bison · Janvier 31, 2024, 6:03

Bonsoir,

As-tu bien relancé les dépendances après la restauration de la sauvegarde Jeedom ? Quels sont les logs de ces installations ?

ninori · Janvier 31, 2024, 6:17

Oui je l’avais bien fait mais depuis j’ai installé et supprimé le plugin plusieurs fois et là pour une nouvelle installation j’ai les dépendances ko, c’est à n’y rien comprendre…Je viens de tester sur ma jeedom de test remontée à l’identique de celle de prod et les commande du roborock sont bien présentes

Voici les long d’installation de mon jeedom de prod ou le plugin pose problème :

Wed Jan 31 19:15:24 CET 2024
********************************************
***************** PARAM ********************
********************************************
VENV_DIR          => /var/www/html/plugins/mirobot/core/class/../../resources/venv/
PROGRESS_FILE     => /tmp/jeedom/mirobot/dependency
PYTHON_VERSION    => 3.8.2
********************************************
***** Revert Last Dependencies Install *****
********************************************
Not uninstalling pip at /usr/lib/python3/dist-packages, outside environment /usr
Can't uninstall 'pip'. No files were found to uninstall.
Reading package lists...
Building dependency tree...
Reading state information...
The following package was automatically installed and is no longer required:
linux-image-4.19.0-16-amd64
Use 'sudo apt autoremove' to remove it.
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/171 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 81427 files and directories currently installed.)
Preparing to unpack .../python3-pip_18.1-5_all.deb ...
Unpacking python3-pip (18.1-5) over (18.1-5) ...
Setting up python3-pip (18.1-5) ...
Processing triggers for man-db (2.8.5-2) ...
***************************************************
***** Launch pre-install of miio dependency *****
***************************************************
<span class='label label-xs label-success'>Python 3.8.2 already existing</span>
*************************
***** Install VENV ******
*************************
Reading package lists...
Building dependency tree...
Reading state information...
python3-pip is already the newest version (18.1-5).
python3 is already the newest version (3.7.3-1).
python3-venv is already the newest version (3.7.3-1).
The following package was automatically installed and is no longer required:
linux-image-4.19.0-16-amd64
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Requirement already satisfied: pip in /var/www/html/plugins/mirobot/resources/venv/lib/python3.8/site-packages (23.3.2)
Requirement already satisfied: wheel in /var/www/html/plugins/mirobot/resources/venv/lib/python3.8/site-packages (0.42.0)
*********************************************************
***** Installing python-miio from git master branch *****
*********************************************************
Reading package lists...
Building dependency tree...
Reading state information...
git is already the newest version (1:2.20.1-2+deb10u8).
The following package was automatically installed and is no longer required:
linux-image-4.19.0-16-amd64
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Looking in links: /tmp/tmp_ijp8367
Requirement already satisfied: setuptools in /var/www/html/plugins/mirobot/resources/venv/lib/python3.8/site-packages (41.2.0)
Requirement already satisfied: pip in /var/www/html/plugins/mirobot/resources/venv/lib/python3.8/site-packages (23.3.2)
Collecting git+https://github.com/rytilahti/python-miio.git@master
Cloning https://github.com/rytilahti/python-miio.git (to revision master) to /tmp/pip-req-build-mjcr6unq
Running command git clone --filter=blob:none --quiet https://github.com/rytilahti/python-miio.git /tmp/pip-req-build-mjcr6unq
Resolved https://github.com/rytilahti/python-miio.git to commit 658ee2e82e54233372f19e4f67bbf055b60eaee4
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Collecting PyYAML<7,>=5 (from python-miio==0.6.0.dev0)
Using cached PyYAML-6.0.1-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.1 kB)
Collecting appdirs<2,>=1 (from python-miio==0.6.0.dev0)
Using cached appdirs-1.4.4-py2.py3-none-any.whl (9.6 kB)
Collecting attrs (from python-miio==0.6.0.dev0)
Using cached attrs-23.2.0-py3-none-any.whl.metadata (9.5 kB)
Collecting click>=8 (from python-miio==0.6.0.dev0)
Using cached click-8.1.7-py3-none-any.whl.metadata (3.0 kB)
Collecting construct<3.0.0,>=2.10.56 (from python-miio==0.6.0.dev0)
Using cached construct-2.10.70-py3-none-any.whl.metadata (4.2 kB)
Collecting croniter>=1 (from python-miio==0.6.0.dev0)
Using cached croniter-2.0.1-py2.py3-none-any.whl.metadata (24 kB)
Collecting cryptography>=35 (from python-miio==0.6.0.dev0)
Using cached cryptography-42.0.2-cp37-abi3-manylinux_2_28_x86_64.whl.metadata (5.3 kB)
Collecting defusedxml<1,>=0 (from python-miio==0.6.0.dev0)
Using cached defusedxml-0.7.1-py2.py3-none-any.whl (25 kB)
Collecting micloud>=0.6 (from python-miio==0.6.0.dev0)
Using cached micloud-0.6.tar.gz (9.4 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'error'
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [1 lines of output]
ERROR: Can not execute `setup.py` since setuptools is not available in the build environment.
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
Requirement already satisfied: pycryptodome in /var/www/html/plugins/mirobot/resources/venv/lib/python3.8/site-packages (3.20.0)
Collecting micloud
Using cached micloud-0.6.tar.gz (9.4 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'error'
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [1 lines of output]
ERROR: Can not execute `setup.py` since setuptools is not available in the build environment.
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
Wed Jan 31 19:15:38 CET 2024
***************************
*      Install ended      *
***************************

ninori · Janvier 31, 2024, 8:07

Aux grands maux… nouvelle VM créée et réinstall de jeedom, restauration de la dernière sauvegarde… et tout roule

anon53349806 · Janvier 31, 2024, 8:11

Je ne pense pas !
Si pour ta vm tu choisis debian 10 en système hôte, rien n’empêche d’installer un debian 11 ou 12 !

ninori · Janvier 31, 2024, 8:19

Ah? Nickel merci, très bon tips

system · Février 1, 2024, 8:19

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