Overkiz integration: confirm whether Somfy TaHoma Zigbee group entities are commanded as true groups or expanded to individual covers

Third party integrations
1

Overkiz / Somfy TaHoma Zigbee Groups - How Are Group Commands Handled?

I’m trying to better understand how the Overkiz integration handles Somfy Zigbee group entities and whether the integration preserves Somfy’s intended group behavior.

Environment

  • Home Assistant Core 2026.x
  • Overkiz Integration
  • Somfy TaHoma Hub
  • Somfy Sonesse 40 WireFree Zigbee battery motors

Background

Within Home Assistant, the Overkiz integration exposes both individual shade entities and what appear to be dedicated Somfy Zigbee group entities.

Examples in my installation include:

  • Dining Group (6 shades)
  • Kitchen Group (4 shades)
  • Family Patio Group (3 shades)
  • Family TV Group (3 shades)

These group entities are separate from Home Assistant cover groups that I create myself.

When I control the group entities exposed by Overkiz, performance is noticeably better than sending commands to individual shades or using a Home Assistant cover group. This suggests that some type of grouping is being preserved.

What I’m Trying to Understand

When I call:

service: cover.open_cover
target:
entity_id: cover.some_somfy_group

or

service: cover.close_cover
target:
entity_id: cover.some_somfy_group

what actually happens behind the scenes?

Specifically:

  1. Does Home Assistant simply send the command directly to the TaHoma group object?
  2. Does the Overkiz integration translate the command into multiple individual shade commands?
  3. Has anyone verified whether these exposed group entities represent true Somfy Zigbee groups?

Why I’m Asking

I have been discussing synchronization behavior with Somfy support. Their explanation is that dedicated Zigbee groups were created specifically to allow multiple motors to move in unison and are only exposed through third-party integrations.

Before I spend more time troubleshooting synchronization behavior, I’d like to understand whether Home Assistant is preserving the Somfy group object exactly as intended or whether there are any known limitations in how Overkiz exposes or handles these entities.

I’m not reporting a bug at this point. I’m simply trying to understand the architecture and expected behavior.

If anyone familiar with the Overkiz integration or its implementation can provide insight, I’d appreciate it.

2

Already discussed 1:1 via another channel, adding my reply here for full transparency.

Today, Home Assistant will sent each command as a single Action in an Action Group. This means that every device command will end up in a single execution.

This is the reason why you might see a small delay between executions, when you use a scene or group in Home Assistant. For 16 devices, it will create 16 executions. The limit of a Somfy gateway is ~10 executions, thus we do retry here on errors. You should be able to see this in the log when you turn on debug mode in HA.

If you create a scenario in your TaHoma app, all device commands will be grouped in a single Action Group, thus there should be no delay. If there is a delay, that is due to the communication between your gateway and your devices.

We are working on a new feature where we look at requests executed in a very short timeframe in Home Assistant, and we combine multiple commands in a single execution.

You can give this a try: Commands lost when controlling multiple covers simultaneously via Local API (execution queue full) in Overkiz · Issue #169923 · home-assistant/core · GitHub, to see if it solves your issues.