Jan Bouwhuis

That sounds very nice. I think I'll add you blueprint example to the documentation page.

> The action part can be optimized for sure, but feel free to use the blueprint in any way you want :) Thank you for adding the posibility to use...

> I'll check that tommorow. It should work for trigger_variables? Before I had to call template inside trigger. Or does that part stays the same? It should work as you...

Superseded by #108309

Note from a previous PR by @emontnemery related to mixed group support: > There's a single custom integration published in HACS - `bodymiscale` - which also implements mixed group support...

> I don't think we have any custom components that register group states as I would expect that its only for base components. > > Someone might do it though,...

There was a change in 2024.5.b0 causing MQTT not to publish a `will`. That is `offline` to topic `homeassistant/status`. This could cause that Z2M is not triggered to publish configs...

So what is it that is not working. After MQTT starts, it should replay any retained messages. That should bring up the entities in HA. When the birth message is...

This is what I think happened. Z2M is triggered by the `birth` message `online` to `homeassistant/status`. This message should be sent after the Home Assistant MQTT integration is connected AND...

The configs are fine if they are retained, but devices become unavailable if they miss a status update. The `online` birth message is to be used for Z2M to no...