Unfortunately, I’m running into a Homeyin issue. I’m looking for ways to get around it; I might be able to figure it out eventually, but it’ll take a few more tries.
Hey, no problem for me. If you need help in debugging let me know. I am patient to try as much as needed. 
Oh and if you have the source code available somewhere (e.g. github or sth) (if convenient to you), I have a dev environment for homey running here. So I can do even further debugging and CLI installs if needed.
I don’t have an air quality sensor; if you send me your YAML file, I can fix it.
My yaml follows this example: SCD4X CO₂, Temperature and Relative Humidity Sensor - ESPHome - Smart Home Made Simple
The values get submitted as my screenshot shows, but instead of being assigned to the co2 capability of your ESPHome-Controller app, it is mapped as additional capability.
Feature: Added automatic capability migration for existing paired `select` (picker) entities. Old devices with empty options lists are now automatically upgraded to the full option set without requiring re-pairing. Expanded Air Quality sensor mappings. Added native support for CO2(carbon dioxide), eCO2(equivalent CO2), VOC/TVOC, Formaldehyde (HCHO), PM1, PM10, and Nitrogen Dioxide (NOx) sensors, cleanly mapping them to Homey’s built-in capability indicators.
Refactor/Reliability: Completely refactored `ESPHomeClimateDevice` to inherit from the battle-tested `ESPHomeDevice` base class. This eliminates massive code duplication and ensures all Climate/AC devices now benefit from proper connection manager lifecycles, reconnect jitter, state queuing, and absolute memory safety.
The CO2 issue is fixed now. Recognition of multiple drop downs now also works. Thanks for that, I really appreciate your hard work man! Unfortunately for me the dropdown still does not work. I just have no elements in it. I created another diagnostics report: af3d2102-2322-4605-8ff0-51d13788c117
Hello, have you tried the latest test version?
Hi,
if you mean the v1.2.18: Yes. It is installed on my homey currently.
The dropdown is now filled with my options and works. I am super thankful for that! You are my hero. There is just one thing with the CO2 from a different ESP Board that you fixed before but it created a little “glitch”:
As you can see CO2 and eCO2 are perfectly fine. But Formaldehyde and TVOC also have a CO2 Icon. I don’t know if this means they have similar capabilities in homey or if it is just a mixup in the icons or if there are even icons for those. But I think this is not a big bug or show stopper.
In another device I can see that this is the same behavior for PM2.5, PM1.5 and PM10. So I guess that is just a icon thing. I would not bother about that further, but just let you know in case you want to fix it in future releases.
Once again: I am super grateful for your work and I am doing a donation for you to keep you motivated
Hello, thank you very much for your support and donation. I’ll fix the icon issue you mentioned in the next test version. Thank you again for your donation.
v1.2.19
- Added improved ESPHome Air Quality sensor support.
- Added custom PM1.0 and PM10 capabilities with dedicated icons.
- Fixed PM1.0 and PM10 sensor mapping to prevent PM10 from being detected as PM1.0.
- Improved dynamic sensor capability icon handling.
- Added new sensor mappings for eCO2, TVOC, formaldehyde, gas, frequency, generic measurements and text sensors.
- Improved ESPHome connection handling and reconnection stability.
- Improved shared connection management for devices using the same ESPHome host.
- Added encryption key support to repair flows.
- Fixed connection refresh when IP address, port, password or encryption key changes.
- Improved compatibility with newer ESPHome native API messages.
- Improved cover command compatibility, including zero-position and open/close commands.
- Added safer handling for disconnects and socket cleanup.
- Added Cumulative Meter support.
- Added support for additional repair screens across device types.
- Improved flow card handling for sensors, binary sensors, selects, buttons, switches, numbers, locks and lights.
- General stability improvements and cleanup.
v 1.2.25
- Improved ESPHome device pairing screen.
- Added entity scanning, entity visibility controls and optional debug entity hiding.
- Added repair tools for connection settings, entity visibility, cover command mode and diagnostics.
- Improved matching and icons for PM1, PM10, TVOC, eCO2, formaldehyde, frequency, gas and Fahrenheit temperature sensors.
- Reduced duplicate Celsius/Fahrenheit temperature sensor display.
- Improved Homey alarm compatibility for ESPHome problem binary sensors.
- Improved cover/shutter command compatibility.
- Improved connection stability and reconnect handling.
Hi,
Is there anyone that can explain me how to use a GP I/O board (KC868-A16) running ESPhome - Outputs are working, but I need to determine the state of the inputs. I can only see the card that a binary sensor has changed. Any help would be apricated..
Hello, if you have the card’s YAML file, could you send it to me? Let me see what I can do to help.
Hi @ugrbnk,
Thanks for the latest update and the fix for the ESPHome Climate NaN issue.
I’m using a Mitsubishi AC via ESPHome with this project:
The device works correctly in Home Assistant and exposes several climate attributes, but in Homey some small details seem to be missing. For example, I don’t see the available fan modes (Auto, Low, Medium, High, Quiet, etc.), while they are available in Home Assistant.
Could you check if all ESPHome Climate attributes are currently being exposed by the app?
Maybe it’s related to how this specific MitsubishiCN105ESPHome project exposes the Climate entity
Thanks!
Hi, could you please install the test version and let me know the results?
Hi @ugrbnk
Thank you for your quick response!
I can confirm that the Fan modes are now working perfectly.
Regarding the swing/oscillation settings: although my specific AC unit does not support all of these functions, I noticed a minor UX detail. Currently, the oscillation options are displayed as individual buttons on the main screen. It would be much better and cleaner if they were grouped inside a dropdown selector instead, similar to how other modes (like Fan or Mode) are managed.
Thanks again for your hard work on this update!
Hi @ugrbnk ,
This is my first post in this forum and my first attempt in this field.
I’m trying to connect a Svenar ESPHome ComfoAir controller (running on a Zehnder ComfoAir Standard 300 / ComfoD 300) to Homey using your app. The hardware works fine and the device’s own web interface shows all data correctly.
The problem: when I add the device by IP (192.168.1.153, port 6053, no encryption key), it connects for a fraction of a second and then immediately drops. The device log shows:
@2colors/esphome-native-api 1.3 (192.168.1.15): connected
@2colors/esphome-native-api 1.3 (192.168.1.15): disconnected
Reading failed CONNECTION_CLOSED errno=128
According to Claude, this looks like the known ESPHome 2025.10 breaking change that affects external (non-Home-Assistant) API clients. The device’s api: block is empty (no encryption, no password).
Would you agree? Is there any way to solve this issue?
Thanks!
Erik
Hi @Erik_Brouwer ,
Please try adding the device, and if you send me the diagnostic log and your device’s YAML code after an error occurs, I can determine the source of the error.
