Yes there is, but you have to do it in yaml.
Instead of creating a trigger for every state of your ac, you can use the not_to in your trigger.
Something like:
triggers:
- trigger: state
entity_id: climate.test
not_to:
- "unknown"
- "unavailable"
- "off"
Relevant docs are here if you want to read up on it.
Otherwise, you can use a ready-made Blueprint like this one. It’ll do basically the same thing, but doing it this way you won’t learn new stuff 