# \[APP\]\[Pro\] Esphome Controller App

**URL:** <https://community.homey.app/t/app-pro-esphome-controller-app/150421>\
**Category:** Apps\
**Tags:** app, flow, homey-pro\
**Created:** [February 1, 2026, 1:54pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421 "2026-02-01T13:54:22Z")\
**Posts on this page:** 20\
**Page:** 11

<div class="post-metadata">

**Author:** ![Aco\_Mihaljevic](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aco_mihaljevic/32/121367_2.png) [@Aco\_Mihaljevic](https://community.homey.app/u/Aco_Mihaljevic)\
**Post date:** [April 22, 2026, 7:09am UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/202 "2026-04-22T07:09:25Z")

</div>

\*\*  
Test Report: ESPHome Controller - Generic Driver & Light Driver

Hi Ugur,

Detailed test results for the two things you mentioned in your previous reply: generic driver auto-discovery and the Light driver `supportedColorModes` fix.

**Setup**

Hardware: Sonoff RE5V1C (ESP8266), ESPHome 2025.12.5, Homey Pro 2023 latest, ESPHome Controller latest beta (app restarted)

ESP exposes 6 entities through Native API (confirmed in ESP web UI log):

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/a/ca7b635baa7f2db7a959136bf321dfd526e471e6.png)

**Test A — Generic ESPHome Device Driver**

| ESP entity | Visible in Homey? | Note |
| --- | --- | --- |
| Relay (light.binary) | ✅ | On/off works |
| WiFi RSSI | ✅ | **Name override** : shows “Signal Strength” instead of “WiFi RSSI” |
| Uptime (raw sec) | ❌ | Entity is sent but never appears in Homey UI |
| Uptime Human | ✅ | **Name override** : shows “Uptime” instead of “Uptime Human”, takes the “slot” of the raw Uptime entity |
| IP Address | ❌ | Entity sent (template text\_sensor), doesn’t appear in Homey UI |
| Current SSID | ❌ | Entity sent (template text\_sensor), doesn’t appear in Homey UI |

Issues:

1. **Text\_sensor entities aren’t discovered** — three template text\_sensors are being sent from the ESP, only one (Uptime Human) shows up in Homey.

2. **Name field is ignored** — Homey replaces user-defined names with generic names based on device\_class. “WiFi RSSI” → “Signal Strength”, “Uptime Human” → “Uptime”. This breaks the ability to have multiple entities of the same class with meaningful names (which was the original case in my first post — two temperature sensors on the same device as `pad_temp` and `ambient_temp`).

3. **Icon metadata is ignored** — `icon: "mdi:clock-outline"` A generic dashed-frame icon is shown. Is this a limitation on Homey’s part or do I need some other approach?

4. **device\_class: duration not mapped** — raw Uptime with `device_class: duration` and `unit: s` doesn’t create any capability in Homey.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/b/9b3b547507c25208d13e47acc6998765b423d492.png)

**Test B — Dedicated “Light Driver”**

- On/off button works ✅

- **Brightness slider present** — shouldn’t be, binary light exposes only `ON_OFF` color mode

- **RGB color picker present** — shouldn’t exist

- **Cold/Warm (color temperature) slider present** — shouldn’t exist

- No diagnostic entities (WiFi RSSI, Uptime, IP, SSID, Human Uptime) shown

Homey Light driver still shows all four sliders. It seems the `supportedColorModes` reading doesn’t work as intended.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/3/e32546c80740b84cb245460dcfb11bc63307cca5.png)

YAML I’m using (Homey-relevant parts)

```yaml
light:
  - platform: binary
    id: relay
    name: "Relay"
    output: relay_out
    icon: "mdi:lightbulb"
    restore_mode: RESTORE_DEFAULT_OFF

sensor:
  - platform: wifi_signal
    name: "WiFi RSSI"
    update_interval: 60s
    device_class: signal_strength
    unit_of_measurement: "dBm"
    accuracy_decimals: 0
    entity_category: diagnostic

  - platform: uptime
    name: "Uptime"
    id: uptime_sec
    update_interval: 60s
    device_class: duration
    unit_of_measurement: "s"
    accuracy_decimals: 0
    entity_category: diagnostic

text_sensor:
  - platform: template
    name: "IP Address"
    id: ip_addr
    icon: "mdi:ip-network"
    entity_category: diagnostic
    update_interval: 60s
    lambda: |-
      return {WiFi.localIP().toString().c_str()};

  - platform: template
    name: "Current SSID"
    id: current_ssid
    icon: "mdi:wifi"
    entity_category: diagnostic
    update_interval: 60s
    lambda: |-
      return {WiFi.SSID().c_str()};

  - platform: template
    name: "Uptime Human"
    id: uptime_human
    icon: "mdi:clock-outline"
    update_interval: 60s
    entity_category: diagnostic
    lambda: |-
      if (isnan(id(uptime_sec).state)) {
        return {"starting..."};
      }
      int seconds = (int)id(uptime_sec).state;
      int days = seconds / 86400;
      seconds %= 86400;
      int hours = seconds / 3600;
      seconds %= 3600;
      int minutes = seconds / 60;
      char buf[32];
      sprintf(buf, "%dd %02dh %02dm", days, hours, minutes);
      return {buf};

```

**Summary list:**

1. Light driver - binary light should show only on/off without any sliders

2. Generic driver - template text\_sensor discovery

3. Generic driver - device\_class: duration mapping

4. Generic driver - respect for `name` field - instead of overriding with a generic name

5. Generic driver - icon metadata - If this is possible

I would like you to suggest to me if there is a different approach, feel free to point that out.

Happy to test the new beta with these fixes and send logs + screenshots. And let me know if you need a different YAML setup

---

<div class="post-metadata">

**Author:** ![ugrbnk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ugrbnk/32/145764_2.png) [@ugrbnk](https://community.homey.app/u/ugrbnk)\
**Post date:** [April 22, 2026, 10:23am UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/203 "2026-04-22T10:23:56Z")

</div>

@Aco_Mihaljevic @Silicon

1. Fixed Light Driver: Resolved an issue where binary lights (ON/OFF only) incorrectly displayed brightness, color temperature, and RGB sliders. Stale capabilities are now cleanly removed, preventing UI clutter.
2. Enhanced Text Sensors: The generic driver now supports all `text_sensor` entities (e.g., IP Addresses, SSID names), not just “uptime” sensors.
3. Duration Sensor Support: Sensors utilizing the `duration` device class or time-based units (`s`, `min`, `h`) are now properly discovered and mapped to generic measurements.
4. Preserved Entity Names: Fixed an issue where custom sensor names defined in ESPHome YAML were overwritten by Homey’s default localized capability titles (e.g., forcing “Signal Strength” instead of “WiFi RSSI”). Custom names are now strictly respected.
5. Ratgdo v32 Enhancements: Added dedicated matching rules for Ratgdo v32 garage controllers. `vehicle_detected`, `vehicle_arriving`, and `vehicle_leaving` are now correctly mapped to Presence sensors. `vehicle_distance_actual` and other distance inputs are natively supported as numeric measurements.

> **[ESPHome Controller | Homey](https://homey.app/en-tr/app/com.ugrbnk.esphome/ESPHome-Controller/test/)**
>
> Your DIY devices, seamlessly integrated

---

<div class="post-metadata">

**Author:** ![Silicon](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/silicon/32/120849_2.png) [@Silicon](https://community.homey.app/u/Silicon)\
**Post date:** [April 23, 2026, 12:42am UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/204 "2026-04-23T00:42:08Z")

</div>

This seems to match when adding a generic ESPHome device but not when adding as a ratgdo, and I think there is an issue with not using the base ratgdo yaml.

Edit: also I’m not sure it is a yaml issue… I’m not getting cards I might expect like vehicle arriving to use in flows, but I can see the status when viewing the device.

---

<div class="post-metadata">

**Author:** ![Aco\_Mihaljevic](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aco_mihaljevic/32/121367_2.png) [@Aco\_Mihaljevic](https://community.homey.app/u/Aco_Mihaljevic)\
**Post date:** [April 23, 2026, 12:29pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/205 "2026-04-23T12:29:53Z")

</div>

Hi Ugur,

Tested the new beta 1.1.24. Here is what I found

**What is fixed ✅**

Dedicated Light driver no longer shows the RGB color picker or Cold/Warm slider for binary light.  
All good, thanks!

* * *

**Test A — Generic ESPHome Device Driver**

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/7/579eea50d28aca771bea8aff4996877677ecb80a.jpeg)

What works: Relay on/off button, Signal Strength display, Uptime Human display.

What doesn’t work:

1. **`name` field override inconsistent — respected on some entities, not on others** — from my ESP I’m sending:

2. **Template text\_sensor entities invisible** — IP Address and Current SSID are sent from the ESP (confirmed in the log), but don’t appear in Homey UI:

```yaml
   [D][text_sensor:097] 'IP Address': Sending state '192.168.50.2'
   [D][text_sensor:097] 'Current SSID': Sending state 'mitardobriNet'

```

1. **Raw Uptime (sensor with `device_class: duration`) invisible** — sent from the ESP, doesn’t show up in Homey UI:

```yaml
   [D][sensor:135] 'Uptime': Sending state 12191.79 s

```

1. **Icon metadata ignored** — `icon: "mdi:clock-outline"` and other icons don’t get applied. A generic dashed-frame icon is shown.

2. **Brightness slider present** — the generic driver shows a brightness slider for binary light even though the hardware is a relay (on/off only). My YAML uses the simplest binary light platform which exposes only the on/off capability — no brightness support. The slider can be moved but doesn’t do anything.

* * *

**Test B — Dedicated Light Driver**

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/a/ba16c116fb176fc27b58ec73397e11eb02e48251.jpeg)

What works: Relay on/off button, RGB and Cold/Warm sliders are gone (that’s the fix from last round).

What doesn’t work:

1. **Brightness slider still present** — same issue as in Test A. Binary light has no brightness capability since the hardware is a relay. The slider should disappear for on/off-only devices just like you removed RGB and Cold/Warm.

2. **Diagnostic sensors completely missing** — when I add the ESP as “ESPHpmeLight” none of the WiFi RSSI / Uptime / IP Address / Current SSID / Uptime Human sensors show up in the UI. I also checked the tools.developer - they are not there either.  
_For comparison, any Shelly devices (Lights, 1PM, RGB) in Homey show all diagnostics on the device dashboard (signal strength, uptime, etc.) alongside the main control. It would be really useful if the dedicated Light driver did the same — sensors on the dashboard next to the on/off control._

* * *

**UI Bug — Buttons disappear when switching between devices**

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/4/e469ec73d4f865337431a4982e24cd9e5a052451.jpeg)

_[screenshot: empty dashboard]_

Happens on **both drivers** (Generic and Light). Steps to reproduce:

1. Click and open the ESPHome device in Homey UI

2. Click on another device in Homey

3. Go back to the ESPHome device

Result: All buttons (ON/OFF and Brightness) disappear. Dashboard on Generic i OK. The page has to be refreshed to get the buttons back

* * *

It seems we are doing well 🙌

Well done, thanks!

---

<div class="post-metadata">

**Author:** ![ugrbnk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ugrbnk/32/145764_2.png) [@ugrbnk](https://community.homey.app/u/ugrbnk)\
**Post date:** [April 24, 2026, 6:41am UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/206 "2026-04-24T06:41:24Z")

</div>

Thank you for the tests you’ve conducted and your feedback.

Ratgdo Fix: Enabled full visibility for all entities in the Ratgdo driver, including vehicle sensors, distance measurements, and secondary switches. New Sensor Support: Added support for previously missing entities like IP Address, SSID, Gas, and Frequency sensors. UI Bug Fix: Resolved the issue where control buttons and sliders would disappear when switching between device cards. Binary Light Fix: Removed redundant brightness sliders for simple On/Off lights (e.g., status LEDs). Naming Consistency: User-defined entity names from ESPHome YAML are now fully respected over generic translations. Icon Mapping: Added automatic icon mapping for common sensors like Uptime, Distance, and RSSI. Core Stability: Refactored driver architecture for more robust connections and consistent state updates across all device types.

> **[ESPHome Controller | Homey](https://homey.app/en-tr/app/com.ugrbnk.esphome/ESPHome-Controller/test/)**
>
> Your DIY devices, seamlessly integrated

---

<div class="post-metadata">

**Author:** ![Aco\_Mihaljevic](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aco_mihaljevic/32/121367_2.png) [@Aco\_Mihaljevic](https://community.homey.app/u/Aco_Mihaljevic)\
**Post date:** [April 24, 2026, 2:15pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/207 "2026-04-24T14:15:34Z")

</div>

Hi Ugur,

Tested v1.2.1. Big progress, thanks!

**Fixed ✅**

Binary light brightness slider, UI bug with disappearing buttons, raw Uptime now visible, IP Address now visible, Signal Strength has wifi icon, Dedicated Light shows diagnostic sensors.

* * *

**Test A — Generic ESPHome Device Driver**

Works: Relay on/off, Signal Strength, Sensor Value (Uptime), Uptime Human, IP Address.

Doesn’t work:

- **Current SSID invisible** — ESP sends it (confirmed in log), doesn’t show in Homey UI

- Entity mapping / naming issue (below will be explained)

- Icons from YAML not woriking

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/b/0bc4273d678a6ec27498ad3e9d96d1ff6872906c.jpeg)

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/8/8835b9d088d5cef65cd0d30b403e0fcf04fb39d0.jpeg)

* * *

**Test B — Dedicated Light Driver**

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/3/833d269b4b5e7ad208f63f45e0eee9a149b821c3.jpeg)

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/d/cd3f38ec9e7371b0cfb0c093b406495f64268475.jpeg)

Works: Same as Test A

Doesn’t work: Same issues as Test A

* * *

**Main remaining issue — entity mapping**

Changelog says _“User-defined entity names from ESPHome YAML are now fully respected”_, but some entities are being remapped into generic Homey capabilities entirely — not just renamed:

| ESP sends | Homey shows | Value |
| --- | --- | --- |
| `name: "Uptime Human"` | “Uptime Human” ✅ | “1d 04h 46m” |
| `name: "IP Address"` | “IP Address” ✅ | “192.168.50.2” |
| `name: "WiFi RSSI"` (device\_class: signal\_strength) | **“Signal Strength”** ❌ | -76 dBm |
| `name: "Uptime"` (device\_class: duration) | **“Sensor Value”** ❌ | 103626.1 s |

The “Sensor Value” label on raw Uptime is revealing — the value (103626 s) matches the uptime, but the entity got mapped to a generic “Sensor Value” capability instead of keeping its name.

This affects the multi-instance use case from my original post. For a device with two temperature sensors:

yaml

```yaml
- name: "Pad Temperature"
  device_class: temperature
- name: "Cat Body Temperature"
  device_class: temperature

```

If the same logic applies, both would collapse into one generic `measure_temperature` capability and lose their distinct names. Your earlier reply mentioned sub-capabilities via `object_id` (e.g., `measure_temperature.pad_temp`) are already supported — but that doesn’t seem to be happening for `duration` or `signal_strength`.

Ideally: always use YAML `name` as display title, or properly implement sub-capabilities per `object_id`.

* * *

**Icons**

Changelog mentions auto icon mapping for Uptime, Distance, RSSI. RSSI works, but Uptime (raw and Human) still shows a dashed-frame instead of a timer/clock icon.

Would be great if the app read the `icon` field directly from ESPHome metadata — that way users could pick any of 7000+ MDI icons via YAML ( [Material Design Icons - Icon Library - Pictogrammers](http://pictogrammers.com/library/mdi) ) without needing hardcoded mappings.

* * *

**UX note — Duplicate Device Data block**

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/7/471c78385ea181c257b2b8453c27c4ffebc689d2.png)

This is now. Tried adding the same ESP as both Generic and Light in parallel (for side-by-side comparison) — app blocked it with “Duplicate Device Data” error. Makes sense for end users, but an override option or warning instead of hard block would help for testing and advanced use, but OK.

Sorry if I’m intruding with suggestions. I work on the product team, which is my professional deformation 😅  
This is really great progress. Thanks!

Also, feel free to suggest what needs to be tested

---

<div class="post-metadata">

**Author:** ![ugrbnk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ugrbnk/32/145764_2.png) [@ugrbnk](https://community.homey.app/u/ugrbnk)\
**Post date:** [April 25, 2026, 12:37pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/208 "2026-04-25T12:37:03Z")

</div>

thank you again for the very detailed retest — it helped a lot.

I’ve pushed a new beta update focused on the remaining items from your latest report:

- Fixed: `Current SSID` text\_sensor now shows up correctly (Generic + Dedicated Light).
- Fixed: `device_class: duration` now maps to a dedicated duration capability instead of falling back to generic “Sensor Value”.
- Improved: entity mapping now prefers per-entity sub-capabilities for sensor/text/alarm/meter classes, so entities are less likely to collapse into one generic capability.
- Improved: cleanup of stale legacy capabilities (old generic mappings) after reconnect/refresh.
- Improved: uptime capabilities now use a clock icon (both text uptime and numeric duration uptime).
- Improved: basic icon hinting from ESPHome metadata (e.g. clock/timer-like icons) where possible.

Notes:

- “Duplicate Device Data” protection is still intentional to prevent accidental duplicate device IDs.
- Full direct rendering of arbitrary MDI icons from YAML is still limited by Homey capability icon handling, but icon mapping/hints are improved.

If you have time, could you please run this checklist on the new beta?

1. Generic driver:

2. Dedicated Light driver (binary light):

3. UI stability:

If possible, please share:

- one screenshot from Generic
- one screenshot from Light
- app diagnostic log right after opening both cards

Thanks again — your testing quality is excellent and super helpful.

> **[ESPHome Controller | Homey](https://homey.app/en-tr/app/com.ugrbnk.esphome/ESPHome-Controller/test/)**
>
> Your DIY devices, seamlessly integrated

---

<div class="post-metadata">

**Author:** ![Aco\_Mihaljevic](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aco_mihaljevic/32/121367_2.png) [@Aco\_Mihaljevic](https://community.homey.app/u/Aco_Mihaljevic)\
**Post date:** [April 27, 2026, 1:55pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/209 "2026-04-27T13:55:38Z")

</div>

Hi Ugur,

Cleaned up everything (deleted devices, uninstalled old beta, installed 1.2.3 fresh, re-added devices).

**1. Generic ESPHome Driver**

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/9/29f4b1ddd11062c1f61157e688739fea803daa49.jpeg)

| Entity | Status |
| --- | --- |
| Relay button | ❌ Missing |
| WiFi RSSI | ❌ Missing |
| Uptime (raw) | ✅ Shows as “Duration”, not as name from Yaml |
| Uptime Human | ❌ Missing |
| IP Address | ✅ |
| Current SSID | ✅ |

**2. Dedicated Light Driver**

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/d/5df35d1d1ed990d1543ec06a19c0103975397bf0.jpeg)

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/8/986b9140d271fb3a204efedef81fdc5095edafb0.jpeg)

| Entity | Status |
| --- | --- |
| Relay (on/off) | ✅ |
| Brightness/RGB/CCT | ✅ Not shown (correct for binary light) |
| WiFi RSSI | ❌ Missing |
| Uptime (raw) | ✅ Shows as “Duration”, not as name from Yaml |
| Uptime Human | ❌ Missing |
| IP Address | ✅ |
| Current SSID | ✅ |

**3. UI stability**

All good - stay visible when switching between devices

**Regressions vs 1.2.1**

- **Relay button is missing in Generic driver** (worked in 1.2.1)

- **WiFi RSSI is missing in both drivers** (showed as “Signal Strength” in 1.2.1)

- **Uptime Human (template text\_sensor) is missing in both drivers** (worked in 1.2.1)

ESP is sending all of these (confirmed in ESP web UI log), but they don’t appear in Homey UI

**About the diagnostic log**

I was not able to find this log in Homey UI. I also looked in tools.developer.homey.app but couldn’t find any logs specific for the app or the device  
Give me the instructions and Im happy to send it once I know where to look 🙌

Thanks!

---

<div class="post-metadata">

**Author:** ![ugrbnk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ugrbnk/32/145764_2.png) [@ugrbnk](https://community.homey.app/u/ugrbnk)\
**Post date:** [May 9, 2026, 8:42am UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/210 "2026-05-09T08:42:50Z")

</div>

**✨ New Features & Improvements: V.1.2.9**

- **Device Repair Flow (IP & Connection Update):** Added a brand new “Repair” feature for all ESPHome devices. You can now easily update a device’s IP Address, Port, or API Password directly from the device settings without having to delete and re-pair the device.

- **Connection State Flow Triggers:** Added new ‘Device came online’ and ‘Device went offline’ trigger cards for Homey Flows. You can now build automations based on your ESPHome device’s live network connection status.

**🛠 Bug Fixes & Optimizations:**

- **Memory Optimization:** Resolved an issue where multiple capability listeners were incorrectly registered upon device reconnection. This fix significantly reduces memory usage and prevents unnecessary system warnings.

- **Connection Resilience:** Improved the internal connection logic to handle unexpected disconnections and IP changes more robustly.

---

<div class="post-metadata">

**Author:** ![JeroenD](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroend/32/14297_2.png) [@JeroenD](https://community.homey.app/u/JeroenD)\
**Post date:** [May 10, 2026, 8:19pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/211 "2026-05-10T20:19:29Z")

</div>

I’m only see 1.2.8 in the App Store.

I have an occupancy sensor that doesn’t show the status anymore.

---

<div class="post-metadata">

**Author:** ![ugrbnk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ugrbnk/32/145764_2.png) [@ugrbnk](https://community.homey.app/u/ugrbnk)\
**Post date:** [May 10, 2026, 8:34pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/212 "2026-05-10T20:34:31Z")

</div>

Hello, version 1.2.9 is currently undergoing the certification process. If you’d like, you can install it from here and give it a try. If you encounter any issues, please send me the diagnostic report.

> **[ESPHome Controller | Homey](https://homey.app/en-tr/app/com.ugrbnk.esphome/ESPHome-Controller/)**
>
> Your DIY devices, seamlessly integrated

---

<div class="post-metadata">

**Author:** ![JeroenD](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroend/32/14297_2.png) [@JeroenD](https://community.homey.app/u/JeroenD)\
**Post date:** [May 11, 2026, 6:53pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/213 "2026-05-11T18:53:45Z")

</div>

Hi,

I made a report 39fd886e-6fce-4b80-8487-de6ad67613ec for it.  
I hope you have a solution for it

---

<div class="post-metadata">

**Author:** ![ugrbnk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ugrbnk/32/145764_2.png) [@ugrbnk](https://community.homey.app/u/ugrbnk)\
**Post date:** [May 11, 2026, 7:14pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/214 "2026-05-11T19:14:56Z")

</div>

Hello, I’ve reviewed the diagnostic report you sent and fixed the source of the error, then created a test version. Could you please test it again and let me know the results?

> **[ESPHome Controller | Homey](https://homey.app/en-tr/app/com.ugrbnk.esphome/ESPHome-Controller/test/)**
>
> Your DIY devices, seamlessly integrated

---

<div class="post-metadata">

**Author:** ![JeroenD](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroend/32/14297_2.png) [@JeroenD](https://community.homey.app/u/JeroenD)\
**Post date:** [May 11, 2026, 7:29pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/215 "2026-05-11T19:29:01Z")

</div>

Yes it works again! Thank you for the quick fix.  
I hope you found my donation last weekend.

---

<div class="post-metadata">

**Author:** ![ugrbnk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ugrbnk/32/145764_2.png) [@ugrbnk](https://community.homey.app/u/ugrbnk)\
**Post date:** [May 11, 2026, 8:11pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/216 "2026-05-11T20:11:41Z")

</div>

Thank you so much for your donation. I just realized it was you.

---

<div class="post-metadata">

**Author:** ![Florian\_Truck](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/florian_truck/32/164384_2.png) [@Florian\_Truck](https://community.homey.app/u/Florian_Truck)\
**Post date:** [May 16, 2026, 2:39pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/217 "2026-05-16T14:39:19Z")

</div>

Hi, first of all I want to say I love your app. It really makes my day to see someone put so much effort in this.

Now to the nasty part: I am facing a problem with ESPHome (and your app) that I do not know how to tackle it. The problem: I have a select control in my yaml hat is not bound to capabilities in homey.

```auto
select:
  - platform: tuya
    name: "Luftfilter Mode"
    tuya_id: "air_filter"
    enum_datapoint: 3 # DPId für die Modi
    options:
      0: "Manual"
      1: "Auto"
      2: "Sleep"
    internal: true
    on_value:
      then:
        - lambda: |-
            id(airfilter_mode).publish_state(x);

  - platform: template
    name: "Luftfilter Mode"
    id: airfilter_mode
    optimistic: true
    options:
      - Manual
      - Auto
      - Sleep
    set_action:
      - lambda: |-
          if (x == "Manual") {
            id(air_filter).set_enum_datapoint_value(3, 0);
          } else if (x == "Auto") {
            id(air_filter).set_enum_datapoint_value(3, 1);
          } else if (x == "Sleep") {
            id(air_filter).set_enum_datapoint_value(3, 2);
          }

```

The first select is internal because I tried to add a template select in the hope it would be recognized by your app but that was also not successful. The first select is also not recognized if i remove the internal flag.  
Now I am not sure if this is a specific problem of the implementation of your app or if I have to change something to get it work. I hope you have an idea.

Regards and thanks for the good work again.

---

<div class="post-metadata">

**Author:** ![ugrbnk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ugrbnk/32/145764_2.png) [@ugrbnk](https://community.homey.app/u/ugrbnk)\
**Post date:** [May 16, 2026, 5:18pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/218 "2026-05-16T17:18:57Z")

</div>

Hello, please try the test version I created and let me know how it goes. If it doesn’t work, please send me the diagnostic report so I can take a look.

> **[ESPHome Controller | Homey](https://homey.app/en-tr/app/com.ugrbnk.esphome/ESPHome-Controller/test/)**
>
> Your DIY devices, seamlessly integrated

---

<div class="post-metadata">

**Author:** ![Florian\_Truck](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/florian_truck/32/164384_2.png) [@Florian\_Truck](https://community.homey.app/u/Florian_Truck)\
**Post date:** [May 17, 2026, 5:23pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/219 "2026-05-17T17:23:23Z")

</div>

Thanks for the quick reply and fix!  
After switching to the test version the dropdown becomes available in the app but it has no entries.

 ![WhatsApp Image 2026-05-17 at 19.20.02](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/0/4067f28bdd1a7d19ee5ddfdac04ffe675530c9a9.jpeg)

I created a diag report under the id 8e3e2069-a6be-4a73-a1a3-a32f8cc35936

---

<div class="post-metadata">

**Author:** ![ugrbnk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ugrbnk/32/145764_2.png) [@ugrbnk](https://community.homey.app/u/ugrbnk)\
**Post date:** [May 17, 2026, 8:03pm UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/220 "2026-05-17T20:03:48Z")

</div>

Test Version 1.2.14

\* **\*\*[Feature]\*\*** Added full support for ESPHome `select` entities, exposing them as interactive dropdown pickers on the device card and in flows.

\* **\*\*[Feature]\*\*** Implemented dynamic autocomplete for the “Option” parameter in `set_select` Flow cards, allowing you to select any custom option directly from the ESPHome device at runtime.

\* **\*\*[Fix]\*\*** Solved enum capability validation errors for custom picker values by defining a comprehensive static super-set of 36 common option values with translations (Auto, Manual, Sleep, Eco, etc.).

\* **\*\*[Fix]\*\*** Fixed invalid capability chart type validation issue for `measure_gas` and other custom sensor graphs.

> **[ESPHome Controller | Homey](https://homey.app/en-tr/app/com.ugrbnk.esphome/ESPHome-Controller/test/)**
>
> Your DIY devices, seamlessly integrated

---

<div class="post-metadata">

**Author:** ![Florian\_Truck](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/florian_truck/32/164384_2.png) [@Florian\_Truck](https://community.homey.app/u/Florian_Truck)\
**Post date:** [May 18, 2026, 9:13am UTC](https://community.homey.app/t/app-pro-esphome-controller-app/150421/221 "2026-05-18T09:13:22Z")

</div>

Unfortunately still no success. DropDown is empty. Also it seems there is only one drop down in homey available but I added 2 to the device. Maybe pairing is not successful and hence not all capabilities are added. New Diag Report right after re-adding device: 805fc0f0-8992-4b74-8564-bd53529841ba

[Previous page](https://community.homey.app/t/app-pro-esphome-controller-app/150421.md?page=10)

[Next page](https://community.homey.app/t/app-pro-esphome-controller-app/150421.md?page=12)