flacon030 Posté(e) le 26 octobre Signaler Posté(e) le 26 octobre (modifié) bonjour Je viens de commander un nouveau ESP32 Tous la phase de test se passe bien avec le test.yaml Je peut faire un ping et quant je veux passer a la programmation avec le fichier Mitsubishi-emaes.yaml, j'ai ce message flacon030@Mac-mini-M2-Pro ESPHome % esphome run mitsubishi-emaes.yaml INFO ESPHome 2023.12.9 INFO Reading configuration mitsubishi-emaes.yaml... INFO Generating C++ source... Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/3.12/bin/esphome", line 8, in <module> sys.exit(main()) ^^^^^^ File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/esphome/__main__.py", line 1041, in main return run_esphome(sys.argv) ^^^^^^^^^^^^^^^^^^^^^ File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/esphome/__main__.py", line 1028, in run_esphome rc = POST_CONFIG_ACTIONS[args.command](args, config) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/esphome/__main__.py", line 458, in command_run exit_code = write_cpp(config) ^^^^^^^^^^^^^^^^^ File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/esphome/__main__.py", line 192, in write_cpp generate_cpp_contents(config) File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/esphome/__main__.py", line 204, in generate_cpp_contents CORE.flush_tasks() File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/esphome/core/__init__.py", line 679, in flush_tasks self.event_loop.flush_tasks() File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/esphome/coroutine.py", line 246, in flush_tasks next(task.iterator) File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/esphome/__main__.py", line 184, in wrapped await coro(conf) File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/esphome/coroutine.py", line 80, in coro ret = yield from _flatten_generator(gen) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/esphome/coroutine.py", line 118, in _flatten_generator val = gen.send(to_send) ^^^^^^^^^^^^^^^^^ File "/Users/flacon030/Documents/ESPHome/.esphome/external_components/3b4567cc/components/mitsubishi_heatpump/climate.py", line 101, in to_code serial = HARDWARE_UART_TO_SERIAL[PLATFORM_ESP8266][config[CONF_HARDWARE_UART]] ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^ KeyError: 'esp8266' flacon030@Mac-mini-M2-Pro ESPHome % Modifié le 26 octobre par flacon030
Lazer Posté(e) le 26 octobre Auteur Signaler Posté(e) le 26 octobre (modifié) Ouh là là, c'est du chinois tout ça Tu as dû avoir quelque chose qui s'est mal passé durant l'installation de la suite de compilation ESPHome. Essaye de tout effacer et reprendre au début, car là je n'ai aucune idée du problème. EDIT : c'est normal le KeyError: 'esp8266' tout en bas ? C'est de l'ESP32 qu'on utilise normalement... tu n'aurais pas juste une couille dans ton fichier de config YAML ? Modifié le 26 octobre par Lazer
flacon030 Posté(e) le 26 octobre Signaler Posté(e) le 26 octobre (modifié) comment vérifier le fichier de config YAML? Je viens de tous réinstaller python avec la dernière version ESPHOME, mais j'ai toujours le même message d'erreur Je me demande si j'ai la bonne carte hardware de ESP32 https://www.amazon.fr/dp/B08BTLYSTM?ref=ppx_yo2ov_dt_b_fed_asin_title Je pense que l’erreur viens de la plutot Modifié le 26 octobre par flacon030
Lazer Posté(e) le 26 octobre Auteur Signaler Posté(e) le 26 octobre C'est exactement le même microcontrôleur que j'ai commandé, donc ça devrait être bon. Dans ton fichier YAML, tu n'as pas une référence à esp8266 qui traine ? Si le test.yaml passe, je ne vois pas pourquoi ça ne passerait pas ensuite...
flacon030 Posté(e) le 26 octobre Signaler Posté(e) le 26 octobre cela avance un peut j'ai tous réinstaller sur une autre machine a présent j'ai ce message emaes@eMAES ESPHome % esphome run mitsubishi-emaes.yaml INFO ESPHome 2024.10.2 INFO Reading configuration mitsubishi-emaes.yaml... Failed config ota.unknown: [source mitsubishi-emaes.yaml:33] 'ota' requires a 'platform' key but it was not specified. password: !secret ota_password emaes@eMAES ESPHome %
Lazer Posté(e) le 26 octobre Auteur Signaler Posté(e) le 26 octobre Ah ça avance Là tu dois juste avoir un petit problème d'erreur de syntaxe dans ton fichier de configuration et/ou le fichier de mots de passes.
flacon030 Posté(e) le 26 octobre Signaler Posté(e) le 26 octobre en cherchant l'erreur il semble que je ne soit pas le seul https://next.esphome.io/components/ota/ 'ota' requires a 'platform' key but it was not specified.
Lazer Posté(e) le 26 octobre Auteur Signaler Posté(e) le 26 octobre (modifié) ça a peut être changé.... Je viens de regarder le fichier exemple de la page 1 contient à la fois ota, et à la fois platform, sauf que le platform est dans climate. La doc en ligne te donne les valeurs possibles pour le paramètre platform dans ota : esphome ou http_request... à tester. Sinon, tu peux essayer de virer complètement ota, tu ne pourras pas faire les mises à jour à distance par Wi-Fi, mais ce n'est pas nécessaire, au pire tu devras rebrancher le module en USB sur le PC (c'est d'ailleurs pour ça que j'avais anticipé, dans mon tuto, avec la "rallonge" permettant de déporter le module ESP de la carte mère du split pour le débrancher facilement) Modifié le 26 octobre par Lazer
flacon030 Posté(e) le 26 octobre Signaler Posté(e) le 26 octobre (modifié) j'ai essayer de supprimer la ligne OTA , la compilation commence et plante et j'ai la même chose en ajoutant ota: - platform: esphome password: !secret ota_password flacon030@Mac-mini-M2-Pro ESPHome % esphome run mitsubishi-room.yaml INFO ESPHome 2024.10.2 INFO Reading configuration mitsubishi-room.yaml... INFO Generating C++ source... INFO Core config, version or integrations changed, cleaning build files... INFO Deleting .esphome/build/mitsubishi-room/.pioenvs INFO Deleting .esphome/build/mitsubishi-room/.piolibdeps INFO Compiling app... Processing mitsubishi-room (board: wemos_d1_mini32; framework: arduino; platform: platformio/espressif32@5.4.0) ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Library Manager: Installing esphome/AsyncTCP-esphome @ 2.1.4 INFO Installing esphome/AsyncTCP-esphome @ 2.1.4 Unpacking [####################################] 100% Library Manager: AsyncTCP-esphome@2.1.4 has been installed! INFO AsyncTCP-esphome@2.1.4 has been installed! Library Manager: Installing esphome/ESPAsyncWebServer-esphome @ 3.2.2 INFO Installing esphome/ESPAsyncWebServer-esphome @ 3.2.2 Unpacking [####################################] 100% Library Manager: ESPAsyncWebServer-esphome@3.2.2 has been installed! INFO ESPAsyncWebServer-esphome@3.2.2 has been installed! Library Manager: Resolving dependencies... INFO Resolving dependencies... Library Manager: Installing bblanchon/ArduinoJson @ 6.18.5 INFO Installing bblanchon/ArduinoJson @ 6.18.5 Unpacking [####################################] 100% Library Manager: ArduinoJson@6.18.5 has been installed! INFO ArduinoJson@6.18.5 has been installed! Library Manager: Installing git+https://github.com/SwiCago/HeatPump#5d1e146771d2f458907a855bf9d5d4b9bf5ff033 INFO Installing git+https://github.com/SwiCago/HeatPump#5d1e146771d2f458907a855bf9d5d4b9bf5ff033 git version 2.39.5 (Apple Git-154) Cloning into '/Users/flacon030/.platformio/.cache/tmp/pkg-installing-afrp6viz'... remote: Enumerating objects: 1242, done. remote: Counting objects: 100% (111/111), done. remote: Compressing objects: 100% (75/75), done. remote: Total 1242 (delta 52), reused 82 (delta 36), pack-reused 1131 (from 1) Receiving objects: 100% (1242/1242), 460.21 KiB | 3.01 MiB/s, done. Resolving deltas: 100% (618/618), done. HEAD is now at 5d1e146 Merge pull request #209 from dzungpv/master Library Manager: HeatPump@1.0.0+sha.5d1e146 has been installed! INFO HeatPump@1.0.0+sha.5d1e146 has been installed! HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash - toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch5 Dependency Graph |-- AsyncTCP-esphome @ 2.1.4 |-- WiFi @ 2.0.0 |-- FS @ 2.0.0 |-- Update @ 2.0.0 |-- ESPAsyncWebServer-esphome @ 3.2.2 |-- DNSServer @ 2.0.0 |-- ESPmDNS @ 2.0.0 |-- ArduinoJson @ 6.18.5 |-- HeatPump @ 1.0.0+sha.5d1e146 Compiling .pioenvs/mitsubishi-room/src/esphome/components/api/api_connection.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/api/api_frame_helper.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/api/api_pb2.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/api/api_pb2_service.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/api/api_server.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/api/list_entities.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/api/proto.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/api/subscribe_state.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/api/user_services.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/captive_portal/captive_portal.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/climate/climate.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/climate/climate_mode.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/climate/climate_traits.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/esp32/core.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/esp32/gpio.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/esp32/preferences.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/json/json_util.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/logger/logger.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/logger/logger_esp32.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/logger/logger_esp8266.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/logger/logger_host.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/logger/logger_libretiny.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/logger/logger_rp2040.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/mdns/mdns_component.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/mdns/mdns_esp32.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/mdns/mdns_esp8266.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/mdns/mdns_host.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/mdns/mdns_libretiny.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/mdns/mdns_rp2040.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/mitsubishi_heatpump/espmhp.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/network/util.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/select/select.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/select/select_call.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/select/select_traits.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/socket/bsd_sockets_impl.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/socket/lwip_raw_tcp_impl.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/socket/lwip_sockets_impl.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/socket/socket.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/web_server/list_entities.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/web_server/web_server.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/web_server/web_server_v1.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/web_server_base/web_server_base.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/wifi/wifi_component.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/wifi/wifi_component_esp32_arduino.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/wifi/wifi_component_esp8266.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/wifi/wifi_component_esp_idf.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/wifi/wifi_component_libretiny.cpp.o Compiling .pioenvs/mitsubishi-room/src/esphome/components/wifi/wifi_component_pico_w.cpp.o In file included from src/esphome.h:26, from src/esphome/components/mitsubishi_heatpump/espmhp.h:20, from src/esphome/components/mitsubishi_heatpump/espmhp.cpp:21: src/esphome/components/mitsubishi_heatpump/espmhp.h:182:14: error: 'optional' in namespace 'std' does not name a template type std::optional<std::chrono::duration<long long, std::ratio<60>>> remote_operating_timeout_; ^~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:182:9: note: 'std::optional' is only available from C++17 onwards std::optional<std::chrono::duration<long long, std::ratio<60>>> remote_operating_timeout_; ^~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:183:14: error: 'optional' in namespace 'std' does not name a template type std::optional<std::chrono::duration<long long, std::ratio<60>>> remote_idle_timeout_; ^~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:183:9: note: 'std::optional' is only available from C++17 onwards std::optional<std::chrono::duration<long long, std::ratio<60>>> remote_idle_timeout_; ^~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:184:14: error: 'optional' in namespace 'std' does not name a template type std::optional<std::chrono::duration<long long, std::ratio<60>>> remote_ping_timeout_; ^~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:184:9: note: 'std::optional' is only available from C++17 onwards std::optional<std::chrono::duration<long long, std::ratio<60>>> remote_ping_timeout_; ^~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:185:14: error: 'optional' in namespace 'std' does not name a template type std::optional<std::chrono::time_point<std::chrono::steady_clock>> last_remote_temperature_sensor_update_; ^~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:185:9: note: 'std::optional' is only available from C++17 onwards std::optional<std::chrono::time_point<std::chrono::steady_clock>> last_remote_temperature_sensor_update_; ^~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:186:14: error: 'optional' in namespace 'std' does not name a template type std::optional<std::chrono::time_point<std::chrono::steady_clock>> last_ping_request_; ^~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:186:9: note: 'std::optional' is only available from C++17 onwards std::optional<std::chrono::time_point<std::chrono::steady_clock>> last_ping_request_; ^~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp: In member function 'virtual void MitsubishiHeatPump::control(const esphome::climate::ClimateCall&)': src/esphome/components/mitsubishi_heatpump/espmhp.cpp:252:9: error: 'last_remote_temperature_sensor_update_' was not declared in this scope if (last_remote_temperature_sensor_update_.has_value()) { ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:252:9: note: suggested alternative: 'enforce_remote_temperature_sensor_timeout' if (last_remote_temperature_sensor_update_.has_value()) { ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ enforce_remote_temperature_sensor_timeout src/esphome/components/mitsubishi_heatpump/espmhp.cpp: In member function 'void MitsubishiHeatPump::set_remote_temperature(float)': src/esphome/components/mitsubishi_heatpump/espmhp.cpp:625:9: error: 'last_remote_temperature_sensor_update_' was not declared in this scope last_remote_temperature_sensor_update_ = ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:625:9: note: suggested alternative: 'enforce_remote_temperature_sensor_timeout' last_remote_temperature_sensor_update_ = ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ enforce_remote_temperature_sensor_timeout src/esphome/components/mitsubishi_heatpump/espmhp.cpp:628:9: error: 'last_remote_temperature_sensor_update_' was not declared in this scope last_remote_temperature_sensor_update_.reset(); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:628:9: note: suggested alternative: 'enforce_remote_temperature_sensor_timeout' last_remote_temperature_sensor_update_.reset(); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ enforce_remote_temperature_sensor_timeout src/esphome/components/mitsubishi_heatpump/espmhp.cpp: In member function 'void MitsubishiHeatPump::ping()': src/esphome/components/mitsubishi_heatpump/espmhp.cpp:636:5: error: 'last_ping_request_' was not declared in this scope last_ping_request_ = std::chrono::steady_clock::now(); ^~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp: In member function 'void MitsubishiHeatPump::set_remote_operating_timeout_minutes(int)': src/esphome/components/mitsubishi_heatpump/espmhp.cpp:641:5: error: 'remote_operating_timeout_' was not declared in this scope remote_operating_timeout_ = std::chrono::minutes(minutes); ^~~~~~~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:641:5: note: suggested alternative: 'set_remote_operating_timeout_minutes' remote_operating_timeout_ = std::chrono::minutes(minutes); ^~~~~~~~~~~~~~~~~~~~~~~~~ set_remote_operating_timeout_minutes src/esphome/components/mitsubishi_heatpump/espmhp.cpp: In member function 'void MitsubishiHeatPump::set_remote_idle_timeout_minutes(int)': src/esphome/components/mitsubishi_heatpump/espmhp.cpp:646:5: error: 'remote_idle_timeout_' was not declared in this scope remote_idle_timeout_ = std::chrono::minutes(minutes); ^~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:646:5: note: suggested alternative: 'set_timeout' remote_idle_timeout_ = std::chrono::minutes(minutes); ^~~~~~~~~~~~~~~~~~~~ set_timeout src/esphome/components/mitsubishi_heatpump/espmhp.cpp: In member function 'void MitsubishiHeatPump::set_remote_ping_timeout_minutes(int)': src/esphome/components/mitsubishi_heatpump/espmhp.cpp:651:5: error: 'remote_ping_timeout_' was not declared in this scope remote_ping_timeout_ = std::chrono::minutes(minutes); ^~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:651:5: note: suggested alternative: 'set_timeout' remote_ping_timeout_ = std::chrono::minutes(minutes); ^~~~~~~~~~~~~~~~~~~~ set_timeout src/esphome/components/mitsubishi_heatpump/espmhp.cpp: In member function 'void MitsubishiHeatPump::enforce_remote_temperature_sensor_timeout()': src/esphome/components/mitsubishi_heatpump/espmhp.cpp:656:9: error: 'remote_ping_timeout_' was not declared in this scope if (remote_ping_timeout_.has_value() && last_ping_request_.has_value()) { ^~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:656:9: note: suggested alternative: 'set_timeout' if (remote_ping_timeout_.has_value() && last_ping_request_.has_value()) { ^~~~~~~~~~~~~~~~~~~~ set_timeout src/esphome/components/mitsubishi_heatpump/espmhp.cpp:656:45: error: 'last_ping_request_' was not declared in this scope if (remote_ping_timeout_.has_value() && last_ping_request_.has_value()) { ^~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:669:28: error: 'remote_operating_timeout_' was not declared in this scope this->operating_ ? remote_operating_timeout_ : remote_idle_timeout_; ^~~~~~~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:669:28: note: suggested alternative: 'set_remote_operating_timeout_minutes' this->operating_ ? remote_operating_timeout_ : remote_idle_timeout_; ^~~~~~~~~~~~~~~~~~~~~~~~~ set_remote_operating_timeout_minutes src/esphome/components/mitsubishi_heatpump/espmhp.cpp:669:56: error: 'remote_idle_timeout_' was not declared in this scope this->operating_ ? remote_operating_timeout_ : remote_idle_timeout_; ^~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:669:56: note: suggested alternative: 'set_timeout' this->operating_ ? remote_operating_timeout_ : remote_idle_timeout_; ^~~~~~~~~~~~~~~~~~~~ set_timeout src/esphome/components/mitsubishi_heatpump/espmhp.cpp:671:13: error: 'last_remote_temperature_sensor_update_' was not declared in this scope last_remote_temperature_sensor_update_.has_value()) { ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:671:13: note: suggested alternative: 'enforce_remote_temperature_sensor_timeout' last_remote_temperature_sensor_update_.has_value()) { ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ enforce_remote_temperature_sensor_timeout Compiling .pioenvs/mitsubishi-room/src/esphome/core/application.cpp.o *** [.pioenvs/mitsubishi-room/src/esphome/components/mitsubishi_heatpump/espmhp.cpp.o] Error 1 =================================================================================================== [FAILED] Took 5.84 seconds =================================================================================================== flacon030@Mac-mini-M2-Pro ESPHome % Modifié le 11 novembre par flacon030
flacon030 Posté(e) le 30 octobre Signaler Posté(e) le 30 octobre bonjour J'ai essayé a nouveau avec de nouvelles carte ESP32 j'ai toujours le même résultat comme ci dessus La différence que j'ai avec toi c'est que je suis pour "pip3 Install esphome" en Version: 2024.10.2 au lieu de 2022.11.5 pour toi et je suis en python 3.13 au lieu de 3.11 du coup je me demande si la version "pip installée esphome" 2024.10.2 n'aurait pas de modifications qui fait que ton fichier "mitsubishi-room.yaml" ne fonctionne plus? car le fichier test.yaml fonctionne comme il faut
Lazer Posté(e) le 30 octobre Auteur Signaler Posté(e) le 30 octobre Peut être, je ne sais pas du tout en fait. Mais je pense plutôt à une modification de la syntaxe du YAML comme je l'ai évoqué dans mon message précédent, as-tu essayé les modifications comme je l'ai suggéré ? Le 26/10/2024 à 15:27, Lazer a dit : ça a peut être changé.... Je viens de regarder le fichier exemple de la page 1 contient à la fois ota, et à la fois platform, sauf que le platform est dans climate. La doc en ligne te donne les valeurs possibles pour le paramètre platform dans ota : esphome ou http_request... à tester. Sinon, tu peux essayer de virer complètement ota, tu ne pourras pas faire les mises à jour à distance par Wi-Fi, mais ce n'est pas nécessaire, au pire tu devras rebrancher le module en USB sur le PC (c'est d'ailleurs pour ça que j'avais anticipé, dans mon tuto, avec la "rallonge" permettant de déporter le module ESP de la carte mère du split pour le débrancher facilement)
flacon030 Posté(e) le 11 novembre Signaler Posté(e) le 11 novembre oui j'ai supprimé la ligne ota mais cela donne toujours le même résultat
Lazer Posté(e) le 11 novembre Auteur Signaler Posté(e) le 11 novembre Dommage... Tu n'as pas un autre PC pour tester ? Je vois que tu es sous MacOS, peut être qu'avec Windows ou Linux le compilateur se comporte différemment ?
flacon030 Posté(e) le 11 novembre Signaler Posté(e) le 11 novembre (modifié) J'ai essayé sous unbuntu 22.03 et windows 11 et c'est toujours le même résultat flacon030@ubuntu-2204:~/Documents/ESPHome$ esphome run mitsubishi-emaes.yaml INFO ESPHome 2024.10.3 INFO Reading configuration mitsubishi-emaes.yaml... INFO Generating C++ source... INFO Core config, version or integrations changed, cleaning build files... INFO Compiling app... Processing mitsubishi-emaes (board: wemos_d1_mini32; framework: arduino; platform: platformio/espressif32@5.4.0) ---------------------------------------------------------------------------------------------------- Library Manager: Installing esphome/AsyncTCP-esphome @ 2.1.4 INFO Installing esphome/AsyncTCP-esphome @ 2.1.4 Unpacking [####################################] 100% Library Manager: AsyncTCP-esphome@2.1.4 has been installed! INFO AsyncTCP-esphome@2.1.4 has been installed! Library Manager: Installing esphome/ESPAsyncWebServer-esphome @ 3.2.2 INFO Installing esphome/ESPAsyncWebServer-esphome @ 3.2.2 Unpacking [####################################] 100% Library Manager: ESPAsyncWebServer-esphome@3.2.2 has been installed! INFO ESPAsyncWebServer-esphome@3.2.2 has been installed! Library Manager: Resolving dependencies... INFO Resolving dependencies... Library Manager: Installing bblanchon/ArduinoJson @ 6.18.5 INFO Installing bblanchon/ArduinoJson @ 6.18.5 Downloading [####################################] 100% Unpacking [####################################] 100% Library Manager: ArduinoJson@6.18.5 has been installed! INFO ArduinoJson@6.18.5 has been installed! Library Manager: Installing git+https://github.com/SwiCago/HeatPump#5d1e146771d2f458907a855bf9d5d4b9bf5ff033 INFO Installing git+https://github.com/SwiCago/HeatPump#5d1e146771d2f458907a855bf9d5d4b9bf5ff033 git version 2.34.1 Cloning into '/home/flacon030/.platformio/.cache/tmp/pkg-installing-454rino4'... remote: Enumerating objects: 1242, done. remote: Counting objects: 100% (111/111), done. remote: Compressing objects: 100% (75/75), done. remote: Total 1242 (delta 52), reused 82 (delta 36), pack-reused 1131 (from 1) Receiving objects: 100% (1242/1242), 460.21 KiB | 4.11 MiB/s, done. Resolving deltas: 100% (618/618), done. HEAD is now at 5d1e146 Merge pull request #209 from dzungpv/master Library Manager: HeatPump@1.0.0+sha.5d1e146 has been installed! INFO HeatPump@1.0.0+sha.5d1e146 has been installed! HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash - toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch5 Dependency Graph |-- AsyncTCP-esphome @ 2.1.4 |-- WiFi @ 2.0.0 |-- FS @ 2.0.0 |-- Update @ 2.0.0 |-- ESPAsyncWebServer-esphome @ 3.2.2 |-- DNSServer @ 2.0.0 |-- ESPmDNS @ 2.0.0 |-- ArduinoJson @ 6.18.5 |-- HeatPump @ 1.0.0+sha.5d1e146 Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/api/api_connection.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/api/api_frame_helper.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/api/api_pb2.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/api/api_pb2_service.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/api/api_server.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/api/list_entities.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/api/proto.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/api/subscribe_state.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/api/user_services.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/captive_portal/captive_portal.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/climate/climate.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/climate/climate_mode.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/climate/climate_traits.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/esp32/core.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/esp32/gpio.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/esp32/preferences.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/json/json_util.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/logger/logger.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/logger/logger_esp32.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/logger/logger_esp8266.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/logger/logger_host.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/logger/logger_libretiny.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/logger/logger_rp2040.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/mdns/mdns_component.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/mdns/mdns_esp32.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/mdns/mdns_esp8266.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/mdns/mdns_host.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/mdns/mdns_libretiny.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/mdns/mdns_rp2040.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/mitsubishi_heatpump/espmhp.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/network/util.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/select/select.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/select/select_call.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/select/select_traits.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/socket/bsd_sockets_impl.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/socket/lwip_raw_tcp_impl.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/socket/lwip_sockets_impl.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/socket/socket.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/web_server/list_entities.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/web_server/web_server.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/web_server/web_server_v1.cpp.o Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/web_server_base/web_server_base.cpp.o In file included from src/esphome.h:26, from src/esphome/components/mitsubishi_heatpump/espmhp.h:20, from src/esphome/components/mitsubishi_heatpump/espmhp.cpp:21: src/esphome/components/mitsubishi_heatpump/espmhp.h:182:14: error: 'optional' in namespace 'std' does not name a template type std::optional<std::chrono::duration<long long, std::ratio<60>>> remote_operating_timeout_; ^~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:182:9: note: 'std::optional' is only available from C++17 onwards std::optional<std::chrono::duration<long long, std::ratio<60>>> remote_operating_timeout_; ^~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:183:14: error: 'optional' in namespace 'std' does not name a template type std::optional<std::chrono::duration<long long, std::ratio<60>>> remote_idle_timeout_; ^~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:183:9: note: 'std::optional' is only available from C++17 onwards std::optional<std::chrono::duration<long long, std::ratio<60>>> remote_idle_timeout_; ^~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:184:14: error: 'optional' in namespace 'std' does not name a template type std::optional<std::chrono::duration<long long, std::ratio<60>>> remote_ping_timeout_; ^~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:184:9: note: 'std::optional' is only available from C++17 onwards std::optional<std::chrono::duration<long long, std::ratio<60>>> remote_ping_timeout_; ^~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:185:14: error: 'optional' in namespace 'std' does not name a template type std::optional<std::chrono::time_point<std::chrono::steady_clock>> last_remote_temperature_sensor_update_; ^~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:185:9: note: 'std::optional' is only available from C++17 onwards std::optional<std::chrono::time_point<std::chrono::steady_clock>> last_remote_temperature_sensor_update_; ^~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:186:14: error: 'optional' in namespace 'std' does not name a template type std::optional<std::chrono::time_point<std::chrono::steady_clock>> last_ping_request_; ^~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.h:186:9: note: 'std::optional' is only available from C++17 onwards std::optional<std::chrono::time_point<std::chrono::steady_clock>> last_ping_request_; ^~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp: In member function 'virtual void MitsubishiHeatPump::control(const esphome::climate::ClimateCall&)': src/esphome/components/mitsubishi_heatpump/espmhp.cpp:252:9: error: 'last_remote_temperature_sensor_update_' was not declared in this scope if (last_remote_temperature_sensor_update_.has_value()) { ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:252:9: note: suggested alternative: 'enforce_remote_temperature_sensor_timeout' if (last_remote_temperature_sensor_update_.has_value()) { ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ enforce_remote_temperature_sensor_timeout src/esphome/components/mitsubishi_heatpump/espmhp.cpp: In member function 'void MitsubishiHeatPump::set_remote_temperature(float)': src/esphome/components/mitsubishi_heatpump/espmhp.cpp:625:9: error: 'last_remote_temperature_sensor_update_' was not declared in this scope last_remote_temperature_sensor_update_ = ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/wifi/wifi_component.cpp.o src/esphome/components/mitsubishi_heatpump/espmhp.cpp:625:9: note: suggested alternative: 'enforce_remote_temperature_sensor_timeout' last_remote_temperature_sensor_update_ = ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ enforce_remote_temperature_sensor_timeout src/esphome/components/mitsubishi_heatpump/espmhp.cpp:628:9: error: 'last_remote_temperature_sensor_update_' was not declared in this scope last_remote_temperature_sensor_update_.reset(); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:628:9: note: suggested alternative: 'enforce_remote_temperature_sensor_timeout' last_remote_temperature_sensor_update_.reset(); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ enforce_remote_temperature_sensor_timeout src/esphome/components/mitsubishi_heatpump/espmhp.cpp: In member function 'void MitsubishiHeatPump::ping()': src/esphome/components/mitsubishi_heatpump/espmhp.cpp:636:5: error: 'last_ping_request_' was not declared in this scope last_ping_request_ = std::chrono::steady_clock::now(); ^~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp: In member function 'void MitsubishiHeatPump::set_remote_operating_timeout_minutes(int)': src/esphome/components/mitsubishi_heatpump/espmhp.cpp:641:5: error: 'remote_operating_timeout_' was not declared in this scope remote_operating_timeout_ = std::chrono::minutes(minutes); ^~~~~~~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:641:5: note: suggested alternative: 'set_remote_operating_timeout_minutes' remote_operating_timeout_ = std::chrono::minutes(minutes); ^~~~~~~~~~~~~~~~~~~~~~~~~ set_remote_operating_timeout_minutes src/esphome/components/mitsubishi_heatpump/espmhp.cpp: In member function 'void MitsubishiHeatPump::set_remote_idle_timeout_minutes(int)': src/esphome/components/mitsubishi_heatpump/espmhp.cpp:646:5: error: 'remote_idle_timeout_' was not declared in this scope remote_idle_timeout_ = std::chrono::minutes(minutes); ^~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:646:5: note: suggested alternative: 'set_timeout' remote_idle_timeout_ = std::chrono::minutes(minutes); ^~~~~~~~~~~~~~~~~~~~ set_timeout src/esphome/components/mitsubishi_heatpump/espmhp.cpp: In member function 'void MitsubishiHeatPump::set_remote_ping_timeout_minutes(int)': src/esphome/components/mitsubishi_heatpump/espmhp.cpp:651:5: error: 'remote_ping_timeout_' was not declared in this scope remote_ping_timeout_ = std::chrono::minutes(minutes); ^~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:651:5: note: suggested alternative: 'set_timeout' remote_ping_timeout_ = std::chrono::minutes(minutes); ^~~~~~~~~~~~~~~~~~~~ set_timeout src/esphome/components/mitsubishi_heatpump/espmhp.cpp: In member function 'void MitsubishiHeatPump::enforce_remote_temperature_sensor_timeout()': src/esphome/components/mitsubishi_heatpump/espmhp.cpp:656:9: error: 'remote_ping_timeout_' was not declared in this scope if (remote_ping_timeout_.has_value() && last_ping_request_.has_value()) { ^~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:656:9: note: suggested alternative: 'set_timeout' if (remote_ping_timeout_.has_value() && last_ping_request_.has_value()) { ^~~~~~~~~~~~~~~~~~~~ set_timeout src/esphome/components/mitsubishi_heatpump/espmhp.cpp:656:45: error: 'last_ping_request_' was not declared in this scope if (remote_ping_timeout_.has_value() && last_ping_request_.has_value()) { ^~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:669:28: error: 'remote_operating_timeout_' was not declared in this scope this->operating_ ? remote_operating_timeout_ : remote_idle_timeout_; ^~~~~~~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:669:28: note: suggested alternative: 'set_remote_operating_timeout_minutes' this->operating_ ? remote_operating_timeout_ : remote_idle_timeout_; ^~~~~~~~~~~~~~~~~~~~~~~~~ set_remote_operating_timeout_minutes src/esphome/components/mitsubishi_heatpump/espmhp.cpp:669:56: error: 'remote_idle_timeout_' was not declared in this scope this->operating_ ? remote_operating_timeout_ : remote_idle_timeout_; ^~~~~~~~~~~~~~~~~~~~ Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/wifi/wifi_component_esp32_arduino.cpp.o src/esphome/components/mitsubishi_heatpump/espmhp.cpp:669:56: note: suggested alternative: 'set_timeout' this->operating_ ? remote_operating_timeout_ : remote_idle_timeout_; ^~~~~~~~~~~~~~~~~~~~ set_timeout src/esphome/components/mitsubishi_heatpump/espmhp.cpp:671:13: error: 'last_remote_temperature_sensor_update_' was not declared in this scope last_remote_temperature_sensor_update_.has_value()) { ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/esphome/components/mitsubishi_heatpump/espmhp.cpp:671:13: note: suggested alternative: 'enforce_remote_temperature_sensor_timeout' last_remote_temperature_sensor_update_.has_value()) { ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ enforce_remote_temperature_sensor_timeout Compiling .pioenvs/mitsubishi-emaes/src/esphome/components/wifi/wifi_component_esp8266.cpp.o *** [.pioenvs/mitsubishi-emaes/src/esphome/components/mitsubishi_heatpump/espmhp.cpp.o] Error 1 =================================== [FAILED] Took 23.06 seconds =================================== flacon030@ubuntu-2204:~/Documents/ESPHome$ j'ai fait un essai sous unbuntu 22.04 et sous windows 11 et c'est toujours la même chose. Modifié le 11 novembre par flacon030
Lazer Posté(e) le 11 novembre Auteur Signaler Posté(e) le 11 novembre Apparemment c'est la version ESPHome de juin 2024 qui a tout pété : https://github.com/geoffdavis/esphome-mitsubishiheatpump/issues/152 Ils disent que la compilation crashe quand on utilise UART2, ce qui le cas dans notre montage... Il y a des solutions qui sont données, mais je n'ai ni le courage ni le temps de tester tout ça maintenant.... je me demande si en attendant, le mieux n'est pas de trouver un moyen de downgrader à la version précédente de ESPHome.
flacon030 Posté(e) le 12 novembre Signaler Posté(e) le 12 novembre déjà cela me rassure, cela ne viens pas de moi reste a voir comment downgrader esphome ou attendre une nouvelle version car l'hiver arrive et il me reste deux split a convertir en ESP32
flacon030 Posté(e) le 12 novembre Signaler Posté(e) le 12 novembre (modifié) bon j'ai downgrader esphome en version esphome 2023.7.1 je n'ai pas réussi a aller plus bas https://pypi.org/project/esphome/2023.7.1/ Mais cela ne fonctionne toujours pas j'ai aussi essayer de dowgrader wheel en 0.38.4 https://pypi.org/project/wheel/0.45.0/#history Je commence a en avoir marre... Si une âme charitable pouvait programmer mes deux ESP32 je lui en serais reconnaissant Je peut lui envoyer les deux cartes et je peut remunerer le travail si il le faut Merci d'avance au volontaire Modifié le 12 novembre par flacon030
Lazer Posté(e) le 12 novembre Auteur Signaler Posté(e) le 12 novembre ça m'inquiète cette histoire, car ça veut dire qu'on ne sait plus compiler les firmwares... Il faut que j'essaye de trouver du temps pour creuser le sujet, mais je ne garantie pas que ça soit tout de suite...
flacon030 Posté(e) le 13 novembre Signaler Posté(e) le 13 novembre (modifié) Merci je continue de mon coté pour essayer de trouver une solution Car en l'état actuel a mon avis ce QA ne peut plus être mis en place Modifié le 14 novembre par flacon030
flacon030 Posté(e) le 17 novembre Signaler Posté(e) le 17 novembre Pour info j'ai aussi installer esphome sous home assistant, et j'ai toujours le même message d'erreur
flacon030 Posté(e) le 17 novembre Signaler Posté(e) le 17 novembre (modifié) petite avancé je viens de réussir a compiler l'ESP32 que se soit avec python ou (esphome sous HA en ajoutant un nouvelle ESP32 pour avoir ota: password, api: key) - J'arrive a faire fonctionner la clim sur le connecteur CN105 mais pas sur le CN110 (cela ne m'arrange pas... mais cela fera l'affaire en attendant mieux) - cela ne fonctionne qu'avec l'ESP32 que j'ai acheter sur alixepress mais pas ceux de amazone https://fr.aliexpress.com/item/32858054775.html?spm=a2g0o.order_list.order_list_main.20.246f5e5bDE8bNB&gatewayAdapt=glo2fra - Je pense qu'il faut mettre tx_pin : 16, et rx_pin:17 (a essayer)et non 3 et 4 (j'ai du me tromper j'ai du inverser les fils pour que cela fonctionne donc c'est: tx_pin : 17, et rx_pin:16) - reste a essayer de lancer la mise en place du QA sous HC3 car l’interface web de l'esp32 n'est pas la même, il y a plus d'options Cela ne semble pas fonctionner?? https://forum.hacf.fr/t/piloter-sa-pompe-a-chaleur-mitsubishi-en-local-avec-une-sonde-deportee/8544/101 substitutions: name: clim-emaes friendly_name: clim-emaes esphome: name: ${name} platform: ESP32 board: wemos_d1_mini32 uart: id: HP_UART baud_rate: 2400 tx_pin: 17 rx_pin: 16 external_components: - source: github://echavet/MitsubishiCN105ESPHome ota: - platform: esphome password: "xxxxxxx" wifi: ssid: !secret wifi_ssid password: !secret wifi_password power_save_mode: none manual_ip: static_ip: 192.168.1.xxx gateway: 192.168.1.1 subnet: 255.255.255.0 # Enable fallback hotspot (captive portal) in case wifi connection fails ap: ssid: "${friendly_name} ESP Fallback Hotspot" password: "Killer060+" captive_portal: # Enable Web server. web_server: port: 80 # Enable logging logger: hardware_uart: UART1 level: INFO logs: EVT_SETS : INFO WIFI : INFO MQTT : INFO WRITE_SETTINGS : INFO SETTINGS : INFO STATUS : INFO CN105Climate: WARN CN105: INFO climate: WARN sensor: WARN chkSum : INFO WRITE : WARN READ : WARN Header: INFO Decoder : INFO CONTROL_WANTED_SETTINGS: INFO # level: DEBUG # logs: # EVT_SETS : DEBUG # WIFI : INFO # MQTT : INFO # WRITE_SETTINGS : DEBUG # SETTINGS : DEBUG # STATUS : INFO # CN105Climate: WARN # CN105: DEBUG # climate: WARN # sensor: WARN # chkSum : INFO # WRITE : WARN # READ : WARN # Header: INFO # Decoder : DEBUG # CONTROL_WANTED_SETTINGS: DEBUG # Sync time with Home Assistant. time: - platform: homeassistant id: homeassistant_time # Sensors with general information. sensor: # Uptime sensor. - platform: uptime name: ${name} Uptime # WiFi Signal sensor. - platform: wifi_signal name: ${name} WiFi Signal update_interval: 60s # Text sensors with general information. text_sensor: # Expose ESPHome version as sensor. - platform: version name: ${name} ESPHome Version # Expose WiFi information as sensors. - platform: wifi_info ip_address: name: ${name} IP ssid: name: ${name} SSID bssid: name: ${name} BSSID # Create a button to restart the unit from HomeAssistant. Rarely needed, but can be handy. button: - platform: restart name: "Restart ${friendly_name}" climate: - platform: cn105 id: hp name: "${friendly_name}" icon: mdi:heat-pump update_interval: 4s # Defaut 500ms visual: min_temperature: 15 max_temperature: 31 temperature_step: target_temperature: 0.5 current_temperature: 0.1 compressor_frequency_sensor: name: ${name} Compressor Frequency vertical_vane_select: name: ${name} Vertical Vane horizontal_vane_select: name: ${name} Horizontal Vane isee_sensor: name: ISEE Sensor # The remote_temperature_timeout setting allows the unit to revert back to the internal temperature measurement # if it does not receive an update in the specified time range (highly recommended if using remote temperature updates) remote_temperature_timeout: 30min # debounce_delay adds a small delay to the command processing to account for some HomeAssistant buttons that may send # repeat commands too quickly. A shorter value creates a more responsive UI, a longer value protects against repeat commands debounce_delay : 500ms # Enable Home Assistant API api: encryption: key: "xxxxxxxxx" services: # Ajouter une valeur de température comme si c'était un capteur externe # Créer une automatisation qui envoie la température d'un capteur # chaque fois qu'une nouvelle valeur est détectée - service: set_remote_temperature_clim_rdc variables: temperature: float then: # Select between the C version and the F version # Uncomment just ONE of the below lines. The top receives the temperature value in C, # the bottom receives the value in F, converting to C here. - lambda: 'id(hp).set_remote_temperature(temperature);' # - lambda: 'id(hp).set_remote_temperature((temperature - 32.0) * (5.0 / 9.0));' # Revenir à l'utilisation du capteur interne - service: use_internal_temperature_clim_rdc then: - lambda: 'id(hp).set_remote_temperature(0);' Modifié le 17 novembre par flacon030
flacon030 Posté(e) le 2 décembre Signaler Posté(e) le 2 décembre (modifié) Petit recap J'ai réussi a compilé l'ESP32 avec la config yaml ci dessus cela fonctionne avec l'adresse ip de l'ESP32 cela fonctionne avec ESP home sous home assistant je viens d'installer le QA avec le debug activé car il ne fonctionne pour avec la HC3 voici les logs Merci [02.12.2024] [18:21:47] [TRACE] [QA_MITSUBISHI_1077]: [02.12.2024] [18:21:47] [TRACE] [QA_MITSUBISHI_1077]: QuickApp Mitsubishi v2.00 - Initialization - Parent device [02.12.2024] [18:21:47] [TRACE] [QA_MITSUBISHI_1077]: [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: Using tools library v2.30 [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: Using ESPHome library v2.00 [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: Temperature device ID not defined, using internal temperature sensor [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure("tcp", "192.168.1.80", 6053) [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "HomeassistantServiceMap" => field "key" ignored [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "HomeassistantServiceMap" => field "value" ignored [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "ListEntitiesServicesArgument" => field "name" ignored [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "ListEntitiesServicesArgument" => field "type" ignored [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "ExecuteServiceArgument" => field "bool_" ignored [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "ExecuteServiceArgument" => field "legacy_int" ignored [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "ExecuteServiceArgument" => field "float_" ignored [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "ExecuteServiceArgument" => field "string_" ignored [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "ExecuteServiceArgument" => field "int_" ignored [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "ExecuteServiceArgument" => field "bool_array" ignored [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "ExecuteServiceArgument" => field "int_array" ignored [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "ExecuteServiceArgument" => field "float_array" ignored [02.12.2024] [18:21:47] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "ExecuteServiceArgument" => field "string_array" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothServiceData" => field "uuid" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothServiceData" => field "legacy_data" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothServiceData" => field "data" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothLERawAdvertisement" => field "address" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothLERawAdvertisement" => field "rssi" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothLERawAdvertisement" => field "address_type" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothLERawAdvertisement" => field "data" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothGATTDescriptor" => field "uuid" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothGATTDescriptor" => field "handle" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothGATTCharacteristic" => field "uuid" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothGATTCharacteristic" => field "handle" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothGATTCharacteristic" => field "properties" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothGATTCharacteristic" => field "descriptors" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothGATTService" => field "uuid" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothGATTService" => field "handle" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "BluetoothGATTService" => field "characteristics" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "VoiceAssistantAudioSettings" => field "noise_suppression_level" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "VoiceAssistantAudioSettings" => field "auto_gain" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "VoiceAssistantAudioSettings" => field "volume_multiplier" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "VoiceAssistantEventData" => field "name" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:configure() option message_id not found for message "VoiceAssistantEventData" => field "value" ignored [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome library v2.00 successfully initialized [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome URL : tcp://192.168.1.80:6053 [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: Refresh interval : 60 seconds [02.12.2024] [18:21:48] [DEBUG] [QA_MITSUBISHI_1077]: Using internal temperature sensor [02.12.2024] [18:21:51] [DEBUG] [QA_MITSUBISHI_1077]: loop(60) [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:setDeviceNotification() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:checkVG() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:setVG() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:iif() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:split() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:deepCompare() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:urlencode() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:distributeViewLayoutItems() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:isNil() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:getSlider() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:getDurationInString() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:searchViewLayoutItem() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:round() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:updateSlider() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:getDeviceNotification() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:saveViewLayout() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:addViewLayoutItem() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:getViewLayoutItemIndex() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:WOL() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:base64() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:isNotNil() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:isNumber() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:createVG() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:deleteVariable() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:removeViewLayoutItem() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:deepFilter() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:getDeviceIdByName() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: Optimize tools:optimize() [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: init(function()) [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:getDeviceInfo(table[2]) [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:nativeAPI("DeviceInfoRequest", {}, "DeviceInfoResponse", true, false, table[2])[02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:nativeAPI() New TCP connection [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:connect(table[2]) [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:connect() connect() success [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:nativeAPI("DeviceInfoRequest", {}, "DeviceInfoResponse", true, false, table[2])[02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:nativeAPI() New ESPHome login [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:login(table[2]) [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:nativeAPI("HelloRequest", {"client_info":"Fibaro HC3-00003815"}, "HelloResponse", true, false, table[2] [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:transmit("HelloRequest", {"client_info":"Fibaro HC3-00003815"}, table[2])[02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:buildPacket("HelloRequest", {"client_info":"Fibaro HC3-00003815"}) [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:buildPacket() message "HelloRequest" => id 1 [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:buildPacket() field name = "client_info" / field type = "string" / field value = "Fibaro HC3-00003815" [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:buildPacket() wire LEN id = 2 => "010" / field id = 1 => "00001" ==//==> tag = Hex "0a" => "00001010" [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:transmit() packet ASCII : .....Fibaro HC3-00003815 [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:transmit() packet HEX : 00 15 01 0a 13 46 69 62 61 72 6f 20 48 43 33 2d 30 30 30 30 33 38 31 35 [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:transmit() write() success [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:receive(table[2] [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:receive() read() success : 22 bytes [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:receive() packet ASCII : ....Bad indicator byte [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:receive() packet HEX : 01 00 13 01 42 61 64 20 69 6e 64 69 63 61 74 6f 72 20 62 79 74 65 [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:fetchResponse("Bad indicator byte") [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:fetchResponse() data size = 22 [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:fetchResponse() message_count = 0 - data_size = 22 - index = 1 [02.12.2024] [18:21:52] [WARNING] [QA_MITSUBISHI_1077]: ESPHome:fetchResponse() Invalid ESPHome packet [02.12.2024] [18:21:52] [ERROR] [QA_MITSUBISHI_1077]: ESPHome:receive() fetchResponse() failed : Invalid ESPHome packet [02.12.2024] [18:21:52] [ERROR] [QA_MITSUBISHI_1077]: ESPHome:nativeAPI() Receive failed : Invalid ESPHome packet [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:nativeAPI() request message "HelloRequest" removed from queue at index1 [02.12.2024] [18:21:52] [ERROR] [QA_MITSUBISHI_1077]: ESPHome:login() HelloRequest error() : Invalid ESPHome packet [02.12.2024] [18:21:52] [DEBUG] [QA_MITSUBISHI_1077]: ESPHome:disconnect() [02.12.2024] [18:21:52] [ERROR] [QA_MITSUBISHI_1077]: Can't get ESPHome device info : Invalid ESPHome packet [02.12.2024] [18:21:52] [TRACE] [QA_MITSUBISHI_1077]: Update label "LabelDebug" to "❌ Invalid ESPHome packet ❌" [02.12.2024] [18:21:52] [WARNING] [QA_MITSUBISHI_1077]: Mitsubishi virtuel / graph is now dead Modifié le 2 décembre par flacon030
Lazer Posté(e) le 2 décembre Auteur Signaler Posté(e) le 2 décembre Ouh là là, c'est pas bon ça, l'ESP32 qui répond un paquet inconnu, comme si le protocole avait changé.... Pas le choix pour l'instant, il va falloir trouver le moyen de downgrader pour revenir à l'ancienne version de ESPHome... parce que reprendre le développement du QA, ça ne risque pas d'arriver avant un bon moment... pas du tout le temps pour ça en ce moment, surtout que son code LUA est loin d'être simple...
Messages recommandés