feat: fire events for every completed service run

[matfax]

Firing events after services allows other automations and templates to respond to saved state and variable changes. The call_service event doesn't guarantee that the update is completed.

[PiotrMachowski]

Nice idea 👍

[PiotrMachowski]

To be honest I'm still a bit unsure about this functionality. Can you describe automations/scripts that can utilize this feature?

[matfax]

The variables, in particular, might be relevant to multiple automations. You might want to update a device's state whenever a variable changes, or create a variable on that other automations depend in other ways, as some cached/lazy version of some sort of calculation, etc.

call_service doesn't ensure that the respective service is completed, last I checked. That's why you have to fire the events at the end.

This is only what I can spontaneously think of. There is a specific use case where this was necessary in my setup, it's not up at the moment so I could check.

[PiotrMachowski]

Isn't it achievable using built-in state_changed event as well?

[matfax]

It captures state changes, not state saves, restores as a subset of changes, or any variable changes.

I think the restore events might also be relevant for automations that are supposed to be triggered during startup and which rely on states being restored already.

If it's really important, I can look up my use case eventually and explain it as well. It might have involved template sensors.

[PiotrMachowski]

All things that are "stored" in saver are also visible as attributes of saver.saver entity, so their changes should result in state_changed events as well.

I think that I these custom events can be added as well though

[matfax]

Fair enough, but isn't it all cramped into the same entity? It might be difficult to match a specific variable without additional complexity.

I'm just guessing here. Cause I'm positive that I've exhausted these other methods before going this route.

I'll know more when I get my HA running again so that I can conveniently access by backed up database.

[PiotrMachowski]

Fair enough, but isn't it all cramped into the same entity?

Yes, it is. That's why I think that custom events are acceptable after all

[PiotrMachowski]

Thanks @matfax!