Merci. Du coup je mets la même chose sur l’application xiaomi
Il faudra que je parametre le S5 sur le même serveur du coup
Et je n’ai pas réussi à comprendre comment on paramètre les pièces depuis le plugin.
J’ai bien vu la commande perso mais je ne sais pas quoi mettre dedans
J’ai compris pour les pièces.
Sur mon S5 elles ne remontent pas dans le plug in, par contre avdc le S8 j’ai directement les commandes.
Ca ne peut pas fonctionner avec le S5 ?
Je n’ai pas compris a quoi sert ou comment utiliser la commande perso.
Concernant le S8, on ne peut pas choisir uniquement aspiration, lavage ou les 2 ?
Merci
le S5 doit être enregistré en type « générique »
alors que le S8 doit être en « roborock »
pas pour le moment, il faut que je creuse le point …
Merci pour ton retour.
Je n’ai pas trouvé comment faire meme depuis l’application Mi home pour faire en sorte que le robot soit par défaut en mode aspiration uniquement.
Par défaut chez moi c’est lavage avec serpiere + aspiration. Il y a moyen de le bloquer en mode aspiration uniquement ?
Et j’ai vu dans un changelog que le plug in etait compatible avec jeedom connect, du coup ca se passe comment pour l’integrer ? Il faut choisir quel type de widget ?
J’ai contacté roborock pour savoir comment mettre par défaut le mode aspirateur voici la réponse :
Quant au mode aspirateur uniquement, nous vous recommandons fortement de connecter le robot via l’application Roborock pour de meilleures fonctionnalités.
Mais si appli roborock plus d’intégration jeedom …
si tu achetes une mercedes, ils t’encouragent rarement à aller faire les entretiens chez speedy …
Mais est ce que connecter Roborock est totalement différent que Xiaomi à intégrer ?
Il y a pas mal de Github dessus dont celui de HA : GitHub - humbertogontijo/homeassistant-roborock: Roborock integration for Home Assistant. This integration uses your devices from the Roborock App
faut pas hésiter à se lancer dans la création d’un plugin du coup ! 
j’ai cherché pas mal et je ne pense pas que ce soit possible de recuprer un token sur l’app roborock. Sur HA ils passent pas l’app roborock mais je n’ai pas l’impression que ca fonctionne en local
Bonjour,
Y a t’il une solution a mon problème de time out?
Bonsoir @tomitomas
je suis tombé sur ton post et plug in pour le roborock.
Je possède le S6.
Par contre l’installation des dépendances ne se fait pas cela tourne en rond et n’atteins jamais les 100 %:
et cela toute la journée, comme si l’opération ne se termine pas…
Néanmoins, j’ai bien l’icone d’un équipement qui apparait :
d’ailleurs à ce propos, l’équipement avait au début une image / icone qui correspondait à celle du plug in… et ca changé sans que je ne le vois en icone roborock.
su l’équipement, je vois bien le détail de l’appareil, avec le bon IP attribué et un token récupéré, que je vois par ailleurs dans les logs… :
log mi robot dep :
Wed 22 Nov 21:40:48 CET 2023
********************************************
***************** 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 packages were automatically installed and are no longer required:
chromium-common chromium-sandbox libimobiledevice6 libjsoncpp1 libminizip1
libplist3 libre2-5 libu2f-udev libupower-glib3 libusbmuxd4 libwebpdemux2
upower usbmuxd
Use 'sudo apt autoremove' to remove them.
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 43 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 ... 75588 files and directories currently installed.)
Preparing to unpack .../python3-pip_18.1-5+rpt1_all.deb ...
Unpacking python3-pip (18.1-5+rpt1) over (18.1-5+rpt1) ...
Setting up python3-pip (18.1-5+rpt1) ...
Processing triggers for man-db (2.8.5-2) ...
***************************************************
***** Launch pre-install of miio dependency *****
***************************************************
Python 3.8.2 already existing
*************************
***** Install VENV ******
*************************
Reading package lists...
Building dependency tree...
Reading state information...
python3 is already the newest version (3.7.3-1).
python3-venv is already the newest version (3.7.3-1).
python3-pip is already the newest version (18.1-5+rpt1).
The following packages were automatically installed and are no longer required:
chromium-common chromium-sandbox libimobiledevice6 libjsoncpp1 libminizip1
libplist3 libre2-5 libu2f-udev libupower-glib3 libusbmuxd4 libwebpdemux2
upower usbmuxd
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 43 not upgraded.
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: pip in ./html/plugins/mirobot/resources/venv/lib/python3.8/site-packages (23.3.1)
Requirement already satisfied: wheel in ./html/plugins/mirobot/resources/venv/lib/python3.8/site-packages (0.41.3)
*********************************************************
***** 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 packages were automatically installed and are no longer required:
chromium-common chromium-sandbox libimobiledevice6 libjsoncpp1 libminizip1
libplist3 libre2-5 libu2f-udev libupower-glib3 libusbmuxd4 libwebpdemux2
upower usbmuxd
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 43 not upgraded.
Looking in links: /tmp/tmpz9yf0k0d
Requirement already satisfied: setuptools in ./html/plugins/mirobot/resources/venv/lib/python3.8/site-packages (41.2.0)
Requirement already satisfied: pip in ./html/plugins/mirobot/resources/venv/lib/python3.8/site-packages (23.3.1)
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
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-c7xwpqos
Running command git clone --filter=blob:none --quiet https://github.com/rytilahti/python-miio.git /tmp/pip-req-build-c7xwpqos
Resolved https://github.com/rytilahti/python-miio.git to commit 9b17d906d3829dd861d4cb73982dad7d9a5a8e95
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-linux_armv7l.whl
Collecting appdirs<2,>=1 (from python-miio==0.6.0.dev0)
Using cached https://www.piwheels.org/simple/appdirs/appdirs-1.4.4-py2.py3-none-any.whl (9.6 kB)
Collecting attrs (from python-miio==0.6.0.dev0)
Using cached https://www.piwheels.org/simple/attrs/attrs-23.1.0-py3-none-any.whl (61 kB)
Requirement already satisfied: click>=8 in ./html/plugins/mirobot/resources/venv/lib/python3.8/site-packages (from python-miio==0.6.0.dev0) (8.1.7)
Collecting construct<3.0.0,>=2.10.56 (from python-miio==0.6.0.dev0)
Using cached https://www.piwheels.org/simple/construct/construct-2.10.69-py3-none-any.whl (62 kB)
Collecting croniter>=1 (from python-miio==0.6.0.dev0)
Using cached https://www.piwheels.org/simple/croniter/croniter-2.0.1-py2.py3-none-any.whl (19 kB)
Collecting cryptography>=35 (from python-miio==0.6.0.dev0)
Using cached cryptography-41.0.5.tar.gz (630 kB)
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 defusedxml<1,>=0 (from python-miio==0.6.0.dev0)
Using cached https://www.piwheels.org/simple/defusedxml/defusedxml-0.7.1-py2.py3-none-any.whl (25 kB)
Requirement already satisfied: micloud>=0.6 in ./html/plugins/mirobot/resources/venv/lib/python3.8/site-packages (from python-miio==0.6.0.dev0) (0.6)
Collecting pydantic<3,>=1 (from python-miio==0.6.0.dev0)
Using cached pydantic-2.5.2-py3-none-any.whl.metadata (65 kB)
Collecting pytz (from python-miio==0.6.0.dev0)
Using cached https://www.piwheels.org/simple/pytz/pytz-2023.3.post1-py3-none-any.whl (502 kB)
Collecting tqdm<5,>=4 (from python-miio==0.6.0.dev0)
Using cached https://www.piwheels.org/simple/tqdm/tqdm-4.66.1-py3-none-any.whl (78 kB)
Collecting zeroconf<1,>=0 (from python-miio==0.6.0.dev0)
Using cached zeroconf-0.127.0-cp38-cp38-manylinux_2_28_armv7l.whl
Log mi robot :
2023-11-22 20:31:10]DEBUG : GENERATE CMD FROM CONFIG FILE : /var/www/html/plugins/mirobot/core/class/../conf/roborockvacuum.json
[2023-11-22 20:31:10]DEBUG : CMD BY roborockvacuum => sudo /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.1.13 --token 44414a546e37347248384f41444c6e31 status >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_659.txt
[2023-11-22 20:31:10]DEBUG : CMD result null
[2023-11-22 20:32:10]DEBUG : ============================ UPDATING CMD ============================
[2023-11-22 20:32:10]DEBUG : GENERATE CMD FROM CONFIG FILE : /var/www/html/plugins/mirobot/core/class/../conf/roborockvacuum.json
[2023-11-22 20:32:11]DEBUG : CMD BY roborockvacuum => sudo /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.1.13 --token 44414a546e37347248384f41444c6e31 status >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_659.txt
[2023-11-22 20:32:11]DEBUG : CMD result null
[2023-11-22 20:33:10]DEBUG : ============================ UPDATING CMD ============================
[2023-11-22 20:33:10]DEBUG : GENERATE CMD FROM CONFIG FILE : /var/www/html/plugins/mirobot/core/class/../conf/roborockvacuum.json
[2023-11-22 20:33:10]DEBUG : CMD BY roborockvacuum => sudo /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.1.13 --token 44414a546e37347248384f41444c6e31 status >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_659.txt
[2023-11-22 20:33:10]DEBUG : CMD result null
[2023-11-22 20:34:10]DEBUG : ============================ UPDATING CMD ============================
[2023-11-22 20:34:10]DEBUG : GENERATE CMD FROM CONFIG FILE : /var/www/html/plugins/mirobot/core/class/../conf/roborockvacuum.json
[2023-11-22 20:34:10]DEBUG : CMD BY roborockvacuum => sudo /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.1.13 --token 44414a546e37347248384f41444c6e31 status >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_659.txt
[2023-11-22 20:34:10]DEBUG : CMD result null
Un début d’explication ?
Merci
Bonjour, En générique je n’ai pas de commandes. En roborock j’ai les ciommandes mais pas les pièces.
Peut etre qu avec des logs je pourrais (peut etre) aider, mais sans c est sur que je ne pourrais rien faire.
en tout cas sur mon S8, le nettoyage des pieces, c’est easy 
Oui sur le S8 ça fonctionne bien mais je suis passé sur l’application Roborock.
C’est pour le S5 que je voudrais faire la même chose. Des que je peux je t’envoie les logs.
En debug pendant la création des commandes c’est ça ?
tout à fait !
en ayant au préalable sélection « roborock » (et non générique) et fait une 1ere sauvegarde sur l’équipement.
1 « J'aime »
et voila :
[2023-11-27 08:24:33]DEBUG : removing all commands
[2023-11-27 08:24:33]DEBUG : ============================ CREATING CMD ============================
[2023-11-27 08:24:33]DEBUG : GENERATE CMD FROM CONFIG FILE : /var/www/html/plugins/mirobot/core/class/../conf/roborockvacuum.json
[2023-11-27 08:24:33]DEBUG : CMD BY roborockvacuum => sudo /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.18.6 --token 39415730784b6f4e6f57323854485755 status >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_1749.txt
[2023-11-27 08:24:40]DEBUG : CMD result {"msg_ver":3,"msg_seq":461,"state":8,"battery":100,"clean_time":52,"clean_area":367500,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":0,"map_status":3,"lock_status":0}
[2023-11-27 08:24:40]DEBUG : -- creating cmd Statut
[2023-11-27 08:24:40]DEBUG : -- creating cmd Etat
[2023-11-27 08:24:40]DEBUG : -- creating cmd Batterie
[2023-11-27 08:24:40]DEBUG : -- creating cmd Durée de nettoyage
[2023-11-27 08:24:40]DEBUG : -- creating cmd Surface Nettoyée
[2023-11-27 08:24:40]DEBUG : -- creating cmd Statut Compartiment Eau
[2023-11-27 08:24:40]DEBUG : -- creating cmd Nettoyage en cours
[2023-11-27 08:24:40]DEBUG : -- creating cmd Mode Ne Pas Déranger
[2023-11-27 08:24:40]DEBUG : -- creating cmd Code erreur
[2023-11-27 08:24:40]DEBUG : -- creating cmd Verrouillé
[2023-11-27 08:24:40]WARNING : -- skipping cmd Statut Niveau Eau
[2023-11-27 08:24:40]WARNING : -- skipping cmd Statut Tiroir Poussière
[2023-11-27 08:24:40]WARNING : -- skipping cmd En Charge
[2023-11-27 08:24:40]DEBUG : -- creating cmd Sécurité Enfant
[2023-11-27 08:24:40]WARNING : -- skipping cmd Taux Nettoyage Effectué
[2023-11-27 08:24:40]DEBUG : -- creating cmd Statut Carte
[2023-11-27 08:24:40]DEBUG : -- creating cmd Arreter
[2023-11-27 08:24:40]DEBUG : -- creating cmd Démarrer
[2023-11-27 08:24:40]DEBUG : -- creating cmd Pause
[2023-11-27 08:24:40]DEBUG : -- creating cmd Maison
[2023-11-27 08:24:40]DEBUG : -- creating cmd Joue un son
[2023-11-27 08:24:40]DEBUG : -- creating cmd Rafraichir
[2023-11-27 08:24:41]DEBUG : -- creating cmd Vitesse
[2023-11-27 08:24:41]DEBUG : -- creating cmd Mode Sécurité enfant
[2023-11-27 08:24:41]DEBUG : -- creating cmd Commande perso
[2023-11-27 08:24:41]DEBUG : CMD BY roborockvacuum => sudo /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.18.6 --token 39415730784b6f4e6f57323854485755 get_room_mapping >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_1749.txt
[2023-11-27 08:24:43]DEBUG : CMD result []
[2023-11-27 08:24:43]DEBUG : rooms => []
[2023-11-27 08:24:43]DEBUG : ============================ UPDATING CMD ============================
[2023-11-27 08:24:43]DEBUG : GENERATE CMD FROM CONFIG FILE : /var/www/html/plugins/mirobot/core/class/../conf/roborockvacuum.json
[2023-11-27 08:24:43]DEBUG : JSON {"msg_ver":3,"msg_seq":461,"state":8,"battery":100,"clean_time":52,"clean_area":367500,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":0,"map_status":3,"lock_status":0}
[2023-11-27 08:24:43]DEBUG : Updating [state] with value [8]
[2023-11-27 08:24:43]DEBUG : Updating [battery] with value [100]
[2023-11-27 08:24:43]DEBUG : Updating [clean_time] with value [52]
[2023-11-27 08:24:43]DEBUG : Updating [clean_area] with value [367500]
[2023-11-27 08:24:43]DEBUG : Updating [error_code] with value [0]
[2023-11-27 08:24:43]DEBUG : Updating [in_cleaning] with value [0]
[2023-11-27 08:24:43]DEBUG : Updating [water_box_status] with value [0]
[2023-11-27 08:24:44]DEBUG : Updating [dnd_enabled] with value [0]
[2023-11-27 08:24:44]DEBUG : Updating [map_status] with value [3]
[2023-11-27 08:24:44]DEBUG : Updating [lock_status] with value [0]
[2023-11-27 08:24:44]DEBUG : CMD BY roborockvacuum => sudo /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.18.6 --token 39415730784b6f4e6f57323854485755 child_lock >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_1749.txt
[2023-11-27 08:24:46]DEBUG : CMD result null
[2023-11-27 08:24:46]WARNING : ERROR:miio.click_common:Exception: Command get_child_lock_status is not supported by the device
[2023-11-27 08:25:05]DEBUG : ============================ UPDATING CMD ============================
[2023-11-27 08:25:05]DEBUG : GENERATE CMD FROM CONFIG FILE : /var/www/html/plugins/mirobot/core/class/../conf/roborockvacuum.json
[2023-11-27 08:25:05]DEBUG : CMD BY roborockvacuum => sudo /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.18.6 --token 39415730784b6f4e6f57323854485755 status >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_1749.txt
[2023-11-27 08:25:13]DEBUG : CMD result {"msg_ver":3,"msg_seq":464,"state":8,"battery":100,"clean_time":52,"clean_area":367500,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":0,"map_status":3,"lock_status":0}
[2023-11-27 08:25:13]DEBUG : JSON {"msg_ver":3,"msg_seq":464,"state":8,"battery":100,"clean_time":52,"clean_area":367500,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":0,"map_status":3,"lock_status":0}
[2023-11-27 08:25:13]DEBUG : Updating [state] with value [8]
[2023-11-27 08:25:13]DEBUG : Updating [battery] with value [100]
[2023-11-27 08:25:13]DEBUG : Updating [clean_time] with value [52]
[2023-11-27 08:25:13]DEBUG : Updating [clean_area] with value [367500]
[2023-11-27 08:25:13]DEBUG : Updating [error_code] with value [0]
[2023-11-27 08:25:13]DEBUG : Updating [in_cleaning] with value [0]
[2023-11-27 08:25:13]DEBUG : Updating [water_box_status] with value [0]
[2023-11-27 08:25:13]DEBUG : Updating [dnd_enabled] with value [0]
[2023-11-27 08:25:13]DEBUG : Updating [map_status] with value [3]
[2023-11-27 08:25:13]DEBUG : Updating [lock_status] with value [0]
[2023-11-27 08:25:13]DEBUG : CMD BY roborockvacuum => sudo /var/www/html/plugins/mirobot/core/class/../../resources/venv/bin/miiocli -o json_pretty roborockvacuum --ip 192.168.18.6 --token 39415730784b6f4e6f57323854485755 child_lock >&1 2>/var/www/html/plugins/mirobot/core/class/../../data/exec/error_1749.txt
[2023-11-27 08:25:15]DEBUG : CMD result null
[2023-11-27 08:25:15]WARNING : ERROR:miio.click_common:Exception: Command get_child_lock_status is not supported by the device
donc aucune pièce ne remonte, c’est pour ça qu’aucune commande n’est créée pour ça.
on peut voir comment elles sont définies dans l’app xiaomi ?
