You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes it is necessary to make a broadcast message about the happened event to multiple consumers.
Not to break the top-level implementation and keep the base validations, below is a suggestion on how to augment the model by introducing a list to each of the notifier:
For existing frigate-notify users, backward compatibility with current behavior (single-key approach) can also be kept.
Currently, a workaround to support multiple notifier consumers of the same kind is to run several instances of frigate-notify with different MQTT clientid in the configuration.
Thank you.
The text was updated successfully, but these errors were encountered:
Sometimes it is necessary to make a broadcast message about the happened event to multiple consumers.
Not to break the top-level implementation and keep the base validations, below is a suggestion on how to augment the model by introducing a list to each of the notifier:
For existing frigate-notify users, backward compatibility with current behavior (single-key approach) can also be kept.
Currently, a workaround to support multiple notifier consumers of the same kind is to run several instances of frigate-notify with different MQTT
clientid
in the configuration.Thank you.
The text was updated successfully, but these errors were encountered: