Input Boolean Groups!

Share your Projects! Custom Integrations
1

Hi!

Lately, I’ve started using input_boolean’s more extensively, and I’ve been missing the ability to group them in the UI just like other groups.

So today, I wanted to share with you the custom integration I wrote that lets you do just that!

If you’re interested, you can find it here: https://github.com/portbusy/ha-input-boolean-group

It’s still in its early stages, but I’d love to hear what you think. Do you have any ideas or suggestions for the repositories? If you do, you can tell me by opening an issue on GitHub or you can just leave a comment here. :smile:

Have a good day!

2

Hi,
Thanks, this is just what I need but having installed it and restarted I dont get the Input Boolean Group option in Helpers.

Edit:
I managed to add and populate 2 entities in the itegration section.

1 Like
3

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 design flaw in Home Assistant, specifically:

  • I understand why there are different group types - to allow different functionality to be exposed in each group (fans, lights, etc).
  • However I think a switch group should be a special case - it should be possible to add anything that can be switched (on/off) into a switch group** that way if you want to have a group that turns on your: heating, lights, a fan, input booleans and your garbage disposal you can.

I thought about suggesting adding a new “switchable” group but that would quickly lead to confusion about what is the difference between a switch group and a switchable group…

4

Hi!

Unfortunately since it is an HACS integration it will show up in devices and services

But glad you made it! Let me know if you have any other issue!

5

Hi @dtrott!

Thanks for the feedback and for sharing this workaround!

• Regarding the MQTT approach: It is actually a very clever trick. My integration aims to help users who don’t use MQTT, or who simply prefer a “plug-and-play” solution directly from the UI without having to write YAML or rely on external add-ons.

• Regarding the HA design flaw: I completely agree with your point. It would be incredibly convenient if the standard switch group could accept any entity with an on/off state. Unfortunately, HA’s current Core architecture ties groups very strictly to their specific domains to handle service calls properly.

I built this integration to patch a specific gap right now, making things easier while we wait (and hope) for Home Assistant to become more flexible natively in the future.

6

Is it really necessary to create new type of services? Could you just use the same services and if entity passed is the one from your integration, you extract entities in the group and pass the call further?

7

While it’s not 100% in the UI, something similar can also be done by using a Template Switch.

Here’s a couple blueprints I put together: Switch to group Input Booleans.

The above blueprints filter the entities for just Input booleans, but they could be modified to allow any toggle-able entity type. I suspect the combination of Labels and the expanded “purpose-specific” triggers and conditions will make these kind of grouping entities less useful/necessary in the not-to-distant future.

8

If one doesn’t mind defining a configuration in YAML, you can create an “old style” Group containing Input Booleans.

For example, the following configuration creates group.main_mute.

group:
  main_mute:
    name: Main Floor Mute
    entities:
      - input_boolean.kitchen_mute
      - input_boolean.dining_mute
      - input_boolean.living_mute