Why in 2026 is there not a UI way to group input booleans

[sehafr]

What can we not group Input Booleans though the UI in 2026. Inexcusable

[HappyCadaver (Rick Furtado)]

You mean like using the entities card?

[Didgeridrew]

Why in 2026 can't people use the search tool to look for something before decrying its non-existence.... Inconceivable!

GitHub - portbusy/ha-input-boolean-group: Custom component for Home Assistant to enable...

[dtrott (David Trott)]

Also this from a previous post:

Input Boolean Groups!

If you use MQTT (or simply have the broker installed/running) there is a work around for this. You can use an MQTT Switch, with: Retain: true Set the command_topic and state_topic to the same value. That defines an MQTT switch, however it functions the same as an input boolean - the only difference being that internally it identifies as a switch, so it can be used in a switch group. I do appreciate the work to solve the root issue, but frankly I think a better solution would be to fix the…

[Edwin_D]

@sehafr

Inexcusable

Nobody needs to excuse themselves for not giving you things for free.

[dtrott (David Trott)]

I previously mentioned that I thought that input booleans should be marked as switches. However a counter argument was made that that would mean all IBs would be listed as switches so that was undesirable.

Giving it some more thought, the simplest solution would be to allow input booleans to be configured to identify as a switch or not, or worst case have two types of control:

• input boolean.
• input switch

Frankly the majority of HA functionality** is turning stuff on and off so I think its justified to have a special case for functionality related to the primary use case.

I am already doing it with MQTT switches, it's just that it isn't particularly user friendly.

** - From an every day "what does it do" perspective.

[tom_l]

@sehafr

What can we not group Input Booleans though the UI in 2026. Inexcusable

Feature requests go here: home-assistant · Discussions · GitHub