Bonjour j’aurais besoin de votre aide car j’ai acheté un deshumidificateur comfee le modèle connecté 20m2.
Sur l’application téléphonique midea air bien reconnu.
Par contre sur midea wifi (jeedom) non reconnu.
Quelqu’un aurait il la solution ?
Merci d’avance.
Bonjour,
merci de donner quelques précisions
Vous utilisez la version stable ou beta du plugin? il faut la beta pour les déshumidificateurs de mémoire
Ensuite: logs en debug et donnez le résultat du scan trouvé dans les logs
merci
Bonjour j’utilise la version beta
[2024-05-10 23:41:36][DEBUG] : MsmartHome: n
[2024-05-10 23:41:39][DEBUG] : [ENDPOINT] /discover : { "latency": 2.373, "response": "no response from cmd", "status": "nok" }
[2024-05-10 23:41:39][DEBUG] : ============================ DISCOVER ============================
[2024-05-10 23:42:32][DEBUG] : Can't update , missing:<br/> Either => credentials + ip <br/> Either => token + key + ip
[2024-05-10 23:43:02][DEBUG] : Can't update , missing:<br/> Either => credentials + ip <br/> Either => token + key + ip
[2024-05-10 23:43:04][DEBUG] : Can't update , missing:<br/> Either => credentials + ip <br/> Either => token + key + ip
[2024-05-10 23:43:59][DEBUG] : [ENDPOINT] /appliance_status_with_account
[2024-05-10 23:44:01][DEBUG] : [GET STATUS] { "latency": 2.054, "response": "no response from cmd", "status": "nok" }
[2024-05-10 23:44:01][DEBUG] : Error while updating : Midea cloud not responding or error
[2024-05-10 23:51:02][DEBUG] : [DOCKER2] Build cmd: sudo docker build --tag midea-beautiful-air -f /var/www/html/plugins/mideawifi/core/ajax/../../resources/containerDocker/armDockerfile /var/www/html/plugins/mideawifi/core/ajax/../../resources/containerDocker
[2024-05-10 23:51:11][DEBUG] : [DOCKER2] :
[2024-05-10 23:53:14][DEBUG] : MsmartHome: n
[2024-05-10 23:53:17][DEBUG] : [ENDPOINT] /discover : { "latency": 2.344, "response": "no response from cmd", "status": "nok" }
[2024-05-10 23:53:17][DEBUG] : ============================ DISCOVER ============================
[2024-05-10 23:55:58][DEBUG] : [ENDPOINT] /appliance_status_with_account
[2024-05-10 23:56:00][DEBUG] : [GET STATUS] { "latency": 2.296, "response": "no response from cmd", "status": "nok" }
[2024-05-10 23:56:00][DEBUG] : Error while updating : Midea cloud not responding or error
[2024-05-10 23:56:04][DEBUG] : [ENDPOINT] /appliance_status_with_account
[2024-05-10 23:56:06][DEBUG] : [GET STATUS] { "latency": 2.067, "response": "no response from cmd", "status": "nok" }
[2024-05-10 23:56:06][DEBUG] : Error while updating : Midea cloud not responding or error
[2024-05-10 23:57:04][DEBUG] : [ENDPOINT] /appliance_status_with_account
[2024-05-10 23:57:07][DEBUG] : [GET STATUS] { "latency": 3.239, "response": "no response from cmd", "status": "nok" }
[2024-05-10 23:57:07][DEBUG] : Error while updating : Midea cloud not responding or error
[2024-05-10 23:58:04][DEBUG] : [ENDPOINT] /appliance_status_with_account
[2024-05-10 23:58:06][DEBUG] : [GET STATUS] { "latency": 2.052, "response": "no response from cmd", "status": "nok" }
[2024-05-10 23:58:06][DEBUG] : Error while updating : Midea cloud not responding or error
[2024-05-10 23:59:05][DEBUG] : [ENDPOINT] /appliance_status_with_account
[2024-05-10 23:59:07][DEBUG] : [GET STATUS] { "latency": 2.158, "response": "no response from cmd", "status": "nok" }
[2024-05-10 23:59:07][DEBUG] : Error while updating : Midea cloud not responding or error
[2024-05-10 23:59:31][DEBUG] : MsmartHome: n
[2024-05-10 23:59:31][DEBUG] : [ENDPOINT] /discover :
[2024-05-10 23:59:31][DEBUG] : ============================ DISCOVER ============================
[2024-05-10 23:59:31][DEBUG] : [DISCOVER] 0 equipments detected.
[2024-05-10 23:59:33][DEBUG] : MsmartHome: n
[2024-05-10 23:59:33][DEBUG] : [ENDPOINT] /discover :
[2024-05-10 23:59:33][DEBUG] : ============================ DISCOVER ============================
[2024-05-10 23:59:33][DEBUG] : [DISCOVER] 0 equipments detected.
[2024-05-11 00:00:14][ERROR] : Erreur sur mideawifi::pull() : Erreur d'exécution de la commande : sudo docker start 190a21f7b58b415d3398349487d2ede891afa31546a0c48f0df72a90e38ace15 2>&1 (1) => ["Error response from daemon: No such container: 190a21f7b58b415d3398349487d2ede891afa31546a0c48f0df72a90e38ace15","Error: failed to start containers: 190a21f7b58b415d3398349487d2ede891afa31546a0c48f0df72a90e38ace15"]
Euh comment dire, en fait c’était mon mdp que j’avais mal rentré
Problème résolu.
Merci
1 « J'aime »
Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.