Trigger: Unknown trigger (after extended power outage); can't get them to appear

Ah - got it. I didn’t realize that Home Assistant put all of that in the logbook. That’s kind of messy.

Effectively, the blueprint generates automations that are triggered by anything happening in the MQTT topic for zigbee2mqtt and then has conditions that limit its actions by the switches it cares about. All other MQTT updates are ignored. This is how it avoids the device actions triggers (that were missing in your original post).

I don’t know of a way to do this without having it show up in the logbook like that.

This is certainly better than the switches not working at all which was the case basically any time I did an update of Home Assistant Core so I’m fine leaving it.

If anyone else has any thoughts on how to keep the logs clean, feel free to chime in.