Dropdowns in card editor do not work

[ChriKn]

Checklist

• I have updated the card to the latest version available
• I have cleared the cache of my browser
• I have checked if the problem is already reported

The problem

I just installed the card and tried to fill out the fields.
I can't select any of the options.
The robot shows up, the platforms are shown, but I can't select it or toggle with arrow keys.
Tried on multiple browsers (firefox, chromium) private windows.
I searched for such an apparently obvious bug and couldn't find anything.

Help or ideas are appreciated.

What version of a card has described problem?

v2.3.2

What was the last working version card?

No response

What vacuum model do you have problems with?

vacuum.valetudo

Which integration do you use to control your vacuum (link)?

none - valetudo

What browser (browsers/apps) does have this problem?

Chromium / Firefox

What version of Home Assistant do you use?

core-2026.3.4

What type of installation are you running?

Home Assistant OS

Card's configuration

No configuration at all as I can't select anything

Javascript errors shown in the browser's console (if applicable)

Additional information

No response

[Simotion14]

Hello, i have the same Problem. I also had everything updatet and cleared. The robot is schown in the Card but when i want to change the Platform to Dreame i cant change it to anything else than the Xiaomi Miio.

[PiotrMachowski]

Ok, it appears that dropdowns in card editor are broken at this moment, you have to use yaml to change appropriate values

[mdb17]

I am also experiencing this issue.

[w531t4]

also experiencing this issue

[igor-kholopov]

Yep, the problem still exists

[nejc-cc]

HA 2026.5 (PR #51705 "New list components", merged May 7 2026) completely rewrote ha-select. It no longer uses mwc-select/mwc-list-item internally - it now wraps ha-dropdown + ha-dropdown-item. The slot children () passed by the card editor are silently ignored, so the dropdowns open but user can't click anything.

The new ha-select API:

• Still fires a selected event, but the value is now in e.detail.value (not e.target.value)
• Accepts an .options property (string array, or HaSelectOption[]) instead of slot children

Fix for the three editor dropdowns (entity, platform, camera):

1. Remove slot children from each
2. Pass options via the .options property instead
3. Update handlers to read from e.detail.value

// Before
<ha-select
    @selected="${this._valueChanged}"
    .value="${this._entity}">
    ${entities.map(e => html`<mwc-list-item .value="${e}">${e}</mwc-list-item>`)}
</ha-select>

// After
<ha-select
    @selected="${this._valueChanged}"
    .options="${entities}"
    .value="${this._entity}">
</ha-select>

// Before (in handlers)
const value = e.target.value;

// After
const value = e.detail?.value ?? e.target.value;

Same pattern applies to _platformChanged and _cameraChanged. The @selected event name itself is unchanged — only the payload moved from e.target.value to e.detail.value.

Hope this helps :)

[Paatsch]

Hope this helps :)

Unfortunately it didn‘t. Problem with selection still existent

[PiotrMachowski]

Fixed in v2.4.0