this post was submitted on 20 Feb 2024
12 points (100.0% liked)
homeassistant
12080 readers
4 users here now
Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I would say that, in HomeAssistant, the more “proper” way to do it is to watch entities for state changes and trigger that way.
Events are really only accessible in case you want to manage your own entity, or if you are doing something complex and it makes more sense to publish an event of your own and then trigger from that.
Triggering via entity state transitions (which, yes, under the hood operates on Events) are meant to be a universal abstraction from whatever might be firing over the event queues. Unless you need Events for some reason, IMHO keep it simple.
Yeah I always use states when I can but the original post description made it sound like the integration was directly sending a notification. If it didn't set a state (which would be weird) then you'd need an event.