A simple message queue solves simple problems. Kafka is a forward only data stream. That means HaKafkaNet handles several use cases that most other automation frameworks can't.
@leosperry thanks for this. Can you please shed some light on some examples of particular use cases that Kafka solves that the others may not be able to solve?
@king-cog When home assistant shuts down, it loses track of any automations currently running and/or waiting for some time to elapse. The same is true for most automation frameworks. HaKafkaNet is different because Kafka gives it the ability to replay events. That means it can restart any automation that was or should have been executing. More than that, at start-up it can optionally run actions that should have happened in the past. Here's a common example where this comes into play in home automations: You may have dozens of lights throughout your home. For about half of them, you want them to turn off either automatically after a certain amount of time or if there is no motion detected for an amount of time. This amount of time could be anywhere from minutes to hours, or even 24 hours or more. HaKafkaNet is that flexible. So, your light turns on, and a timer starts. Then your automation framework restarts for any reason: running an update, power failure, anything. Will your lights still turn off at the appropriate time? With HaKafkaNet, they will.
Hello from India
Why Kafka? Why not other simpler messege queue services?
A simple message queue solves simple problems. Kafka is a forward only data stream. That means HaKafkaNet handles several use cases that most other automation frameworks can't.
@leosperry thanks for this. Can you please shed some light on some examples of particular use cases that Kafka solves that the others may not be able to solve?
@king-cog When home assistant shuts down, it loses track of any automations currently running and/or waiting for some time to elapse. The same is true for most automation frameworks. HaKafkaNet is different because Kafka gives it the ability to replay events. That means it can restart any automation that was or should have been executing. More than that, at start-up it can optionally run actions that should have happened in the past.
Here's a common example where this comes into play in home automations:
You may have dozens of lights throughout your home. For about half of them, you want them to turn off either automatically after a certain amount of time or if there is no motion detected for an amount of time. This amount of time could be anywhere from minutes to hours, or even 24 hours or more. HaKafkaNet is that flexible. So, your light turns on, and a timer starts. Then your automation framework restarts for any reason: running an update, power failure, anything. Will your lights still turn off at the appropriate time? With HaKafkaNet, they will.
@@king-cog 16:29
Starts at 2:59
❤❤❤❤❤❤❤😂😂 Hello ❤❤❤❤ ĐK ❤❤❤ OK