# \[APP\]\[Pro\] ESPhome - Control your ESP8266/ESP32 by simple configuration files **URL:** \ **Category:** Apps\ **Created:** [August 16, 2023, 7:17pm UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271 "2023-08-16T19:17:36Z")\ **Posts on this page:** 20\ **Page:** 8
**Author:** ![Ron\_Smith](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ron_smith/32/120735_2.png) [@Ron\_Smith](https://community.homey.app/u/Ron_Smith)\ **Post date:** [May 16, 2025, 4:59pm UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/142 "2025-05-16T16:59:10Z")
Thanks Baldhor. I’ll look into this. ---
**Author:** ![Baldhor](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/baldhor/32/27028_2.png) [@Baldhor](https://community.homey.app/u/Baldhor)\ **Post date:** [July 31, 2025, 1:58pm UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/143 "2025-07-31T13:58:20Z")
New test version available : [ESPhome | Homey](https://homey.app/fr-fr/app/nl.inversion.esphome/ESPhome/test/) The fix is proposed by [TDonselaar (Tim Donselaar) · GitHub](https://github.com/TDonselaar) , thank you for your pull request! _ **It should fix the device reconnection issue based on Tim tests!** _ I cannot test this version (I don’t have a Homey running anymore). I will publish it to live only if I get several positive feedbacks! ---
**Author:** ![Bas\_Nahuis](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bas_nahuis/32/19577_2.png) [@Bas\_Nahuis](https://community.homey.app/u/Bas_Nahuis)\ **Post date:** [August 2, 2025, 10:40pm UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/144 "2025-08-02T22:40:58Z")
I installed it and it works well so far. I’m going to do some more testing with it. Thank you for doing this! ---
**Author:** ![Baldhor](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/baldhor/32/27028_2.png) [@Baldhor](https://community.homey.app/u/Baldhor)\ **Post date:** [August 13, 2025, 8:42am UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/145 "2025-08-13T08:42:55Z")
I published latest version to live. Within 2 weeks, only 9 users used it, and there was no crash at all. Seems more stable than previous version. ---
**Author:** ![Doekse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doekse/32/109415_2.png) [@Doekse](https://community.homey.app/u/Doekse)\ **Post date:** [September 15, 2025, 11:18am UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/146 "2025-09-15T11:18:38Z")
Hi @Baldhor, thanks so much for all the work you’ve put into this app! At IFA I spoke with the Open Home Foundation team about the ESPHome integration you’ve built, and we’re all very interested in working together to make this an officially supported app. Since it looks like you might not be actively using Homey anymore, would you be open to discussing a possible transfer of the app, either to us at Athom or to the Open Home Foundation, depending on the path we choose? If you’re open to it, feel free to reach out to me at [partners@athom.com](mailto:partners@athom.com) 😉 ---
**Author:** ![Baldhor](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/baldhor/32/27028_2.png) [@Baldhor](https://community.homey.app/u/Baldhor)\ **Post date:** [September 16, 2025, 9:28am UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/148 "2025-09-16T09:28:09Z")
yes no problem, I mail you ---
**Author:** ![Russell\_Ebbing](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/russell_ebbing/32/79404_2.png) [@Russell\_Ebbing](https://community.homey.app/u/Russell_Ebbing)\ **Post date:** [October 17, 2025, 3:54am UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/149 "2025-10-17T03:54:43Z")
The experimental version works for several Apollo devices. I’m using this version for the R-Pro-1 mmWave radar works well. I beleive PLT-1 and Air-1, MR2 mmWave are supported in the experimental version. > **[Apollo Automation | Homey](https://homey.app/en-us/app/com.apolloautomation/Apollo-Automation/test/)** > > Your Trusted Partner in Smart Home Automation ---
**Author:** ![Andreas\_Nikolai](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andreas_nikolai/32/79470_2.png) [@Andreas\_Nikolai](https://community.homey.app/u/Andreas_Nikolai)\ **Post date:** [October 24, 2025, 11:53pm UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/150 "2025-10-24T23:53:40Z")
Hi @Baldhor . Thanks for this great app! Im currently learning esp/arduino and ive downloaded your app. Ive had lots of problems connecting but now i think i found the problem, i think maybe your app needs to be updated to support the latest esphome firmware. It worked for me when i downgraded. Ive used gemini ai to install and learn everything but im pretty sure that the firmware was the issue. This is a more detailed message gemini made: **Issue:** The Homey app (manual add) fails to connect to devices running recent ESPHome firmware. **Details:** - A device running **ESPHome v2025.10.3** (compiled via the `esphome/esphome:latest` Docker image) was online. It was confirmed working (pingable, web server accessible, and OTA updates from the dashboard worked). - When trying to add the device manually to the Homey app (using the correct static IP: `10.0.0.10` and no API key), the app would always time out after ~15 seconds with a connection error. - The ESPHome device’s live log showed the following during the connection attempt from the Homey Pro (IP `10.0.0.108`): - The immediate `CONNECTION_CLOSED` error strongly suggested a version or protocol incompatibility. **Solution:** - We stopped the `latest` Docker container and ran `esphome/esphome:2023.12.9` instead. - After reflashing the device with this older firmware (and correcting the `ota:` syntax in the YAML for the older version), the Homey app (manual add, same IP) connected successfully on the first try. It seems the Homey app isn’t yet compatible with API changes in the late 2024 / 2025 ESPHome builds. Thanks for looking into it when you have time!, no hurry because as i said downgrading the firmware worked Edit: i now see that you stated that the app is no longer updated ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [October 25, 2025, 1:27pm UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/151 "2025-10-25T13:27:59Z")
Hi Andreas, > [@Andreas\_Nikolai](#): > > Edit: i now see that you stated that the app is no longer updated There’s a chance the app gets supported again in the future: > [@\[APP\]\[Pro\] ESPhome - Control your ESP8266/ESP32 by simple configuration files](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/146): > > Hi @Baldhor, thanks so much for all the work you’ve put into this app! At IFA I spoke with the Open Home Foundation team about the ESPHome integration you’ve built, and we’re all very interested in working together to make this an officially supported app. Since it looks like you might not be actively using Homey anymore, would you be open to discussing a possible transfer of the app, either to us at Athom or to the Open Home Foundation, depending on the path we choose? If you’re open to it, … ---
**Author:** ![bschmidt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bschmidt/32/79590_2.png) [@bschmidt](https://community.homey.app/u/bschmidt)\ **Post date:** [October 28, 2025, 11:11pm UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/152 "2025-10-28T23:11:46Z")
Hi Andreas, I’m having the same problem. I have a bunch of Konnected devices that got upgraded to ESPHome 2025.10.x and I’m seeing the same CONNECTION\_CLOSED error. Digging around I found this: > > > \# What does this implement/fix? > > This PR renames the API protocol messages \`Co…nnectRequest\` and \`ConnectResponse\` to \`AuthenticationRequest\` and \`AuthenticationResponse\` respectively. This naming change better reflects the actual purpose of these messages - they handle authentication via password validation, not the connection establishment itself. > > The RPC method is also renamed from \`connect\` to \`authenticate\` to maintain consistency. > > This change was suggested by @jesserockz in #10704 and aligns the naming with the actual functionality - these messages are only used when \`USE\_API\_PASSWORD\` is defined and handle password authentication, not the TCP connection process. > > \## Types of changes > > \- \[\] Bugfix (non-breaking change which fixes an issue) > \- \[\] New feature (non-breaking change which adds functionality) > \- \[x\] Breaking change (fix or feature that would cause existing functionality to not work as expected) > \- \[\] Code quality improvements to existing code or addition of tests > \- \[\] Other > > \*\*Related issue or feature (if applicable):\*\* > > \- Related to discussion in #10704 > > \*\*Pull request in \[esphome-docs\](https://github.com/esphome/esphome-docs) with documentation (if applicable):\*\* > > \- N/A - Internal API protocol change > > \## Test Environment > > \- \[x\] ESP32 > \- \[x\] ESP32 IDF > \- \[x\] ESP8266 > \- \[\] RP2040 > \- \[\] BK72xx > \- \[\] RTL87xx > \- \[\] nRF52840 > > \## Example entry for \`config.yaml\`: > > \`\`\`yaml > \# No configuration changes required > \# This is an internal API protocol change > api: > password: "your\_password" # Still works the same way > \`\`\` > > \## Checklist: > - \[x\] The code change is tested and works locally. > - \[x\] Tests have been added to verify that the new code works (under \`tests/\` folder). > > If user exposed functionality or configuration variables are added/changed: > - N/A - This is an internal protocol change that doesn't affect user-facing configuration > > \## Additional Notes > > \### Breaking Change Details > While this is technically a breaking change at the protocol level (only for consumers of api.proto as the wire protocol is the same), it should have minimal impact because: > 1. The primary consumer of this API (aioesphomeapi) handles this as an internal implementation detail > 2. The companion PR for aioesphomeapi updates it to use the new message names > 3. Home Assistant uses aioesphomeapi and won't be directly affected > 4. The messages are only used when password authentication is enabled (\`USE\_API\_PASSWORD\`) > > \### Changes Made > \- Renamed \`ConnectRequest\` to \`AuthenticationRequest\` in api.proto > \- Renamed \`ConnectResponse\` to \`AuthenticationResponse\` in api.proto > \- Renamed RPC method from \`connect\` to \`authenticate\` > \- Updated all C++ references: > - \`send\_connect\_response()\` → \`send\_authenticate\_response()\` > - \`on\_connect\_request()\` → \`on\_authentication\_request()\` > \- Regenerated protobuf files with new names > > \### Coordination Required > This PR should be merged in coordination with the corresponding aioesphomeapi PR to ensure compatibility. https://github.com/esphome/aioesphomeapi/pull/1346 It’s labeled as a breaking change so I suspect this is the cause. There are also several open issues noting connection problems since upgrading to 2025.10.x > **[esphome/esphome](https://github.com/esphome/esphome/issues)** > > ESPHome is a system to control your ESP8266/ESP32 by simple yet powerful configuration files and control them remotely through Home Automation systems. - esphome/esphome ---
**Author:** ![Bas\_Nahuis](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bas_nahuis/32/19577_2.png) [@Bas\_Nahuis](https://community.homey.app/u/Bas_Nahuis)\ **Post date:** [November 17, 2025, 5:35pm UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/153 "2025-11-17T17:35:44Z")
How did you downgrade it? also with existing devices? ---
**Author:** ![owuerker](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/owuerker/32/39707_2.png) [@owuerker](https://community.homey.app/u/owuerker)\ **Post date:** [November 25, 2025, 5:09pm UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/154 "2025-11-25T17:09:14Z")
If you have Home Assistant You can use older ESPHome Version through the add-on store > **[Legacy ESPHome versions add-on](https://community.home-assistant.io/t/legacy-esphome-versions-add-on/568448)** > > ESPHome is an awesome project and the amount of devices and sensors they support is immense. So every now and then, some incompatibility slips trough and ends up in a new release, breaking one of my devices. And that’s OK. Usually it is fixed... ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [November 26, 2025, 1:53am UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/155 "2025-11-26T01:53:44Z")
That’s a golden add-on! Thanks for sharing!! ---
**Author:** ![Bas\_Nahuis](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bas_nahuis/32/19577_2.png) [@Bas\_Nahuis](https://community.homey.app/u/Bas_Nahuis)\ **Post date:** [December 5, 2025, 5:20am UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/156 "2025-12-05T05:20:06Z")
Did it work? Have you made any further progress? ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [December 6, 2025, 8:57am UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/157 "2025-12-06T08:57:08Z")
I think you should inform with @Doekse for the progress status. Usually it’s: no news, no updates. ---
**Author:** ![Doekse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doekse/32/109415_2.png) [@Doekse](https://community.homey.app/u/Doekse)\ **Post date:** [December 6, 2025, 9:05am UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/158 "2025-12-06T09:05:22Z")
It’s on the roadmap! I hope that development will kick off in Q1 ---
**Author:** ![Daniel\_de\_los\_Reyes](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daniel_de_los_reyes/32/121102_2.png) [@Daniel\_de\_los\_Reyes](https://community.homey.app/u/Daniel_de_los_Reyes)\ **Post date:** [December 13, 2025, 7:30pm UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/159 "2025-12-13T19:30:27Z")
Hi @Doekse have you reached an agreement with @Baldhor for future maintenance of the ESPHome for homey app? I am thinking to invest in a ESP32 development but only if it can be reliably integrated with homey. ---
**Author:** ![danieldk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/danieldk/32/121102_2.png) [@danieldk](https://community.homey.app/u/danieldk)\ **Post date:** [December 13, 2025, 7:39pm UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/160 "2025-12-13T19:39:15Z")
One of the nicest features that I only discovered today is that ESPHome also supports the ESPHome API over Thread (through OpenThread). Yep, no Matter or HomeKit. It has a nice benefit over regular ESPHome WiFi that device availability is not dependent anymore on WiFi availability (and potentially setting up separate VLANs, etc.). As long as your Hub with Thread radio is up, all automations, etc. will continue to work. I flashed it today on an ESP32C6 Zigbee presence sensor I made (with LD2410C) and it works perfectly. It also doesn’t have the stupid error-prone phone-based onboarding. You just put your Thread Border Router’s TLV in the configuration and it works. > **[OpenThread Component](https://esphome.io/components/openthread/)** > > Instructions for setting up OpenThread component. Maybe worth supporting as well? ---
**Author:** ![Doekse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doekse/32/109415_2.png) [@Doekse](https://community.homey.app/u/Doekse)\ **Post date:** [December 13, 2025, 9:13pm UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/161 "2025-12-13T21:13:24Z")
We are working on a new and official ESPHome app ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [December 14, 2025, 5:57am UTC](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271/162 "2025-12-14T05:57:40Z")
> [@danieldk](#): > > Maybe worth supporting as well? I wonder if this shouldn’t work out-of-the-box because AFAIK, these are just networked devices like “regular” devices running ESPHome. The border router proxies between Thread and regular WiFi/Ethernet, and the only requirement will be IPv6 support. [Previous page](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271.md?page=7) [Next page](https://community.homey.app/t/app-pro-esphome-control-your-esp8266-esp32-by-simple-configuration-files/87271.md?page=9)