Add support to disable notify-self flag on /v2/send endpoint #573
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Will allow you to send the
notify_self
property to the/v2/send
endpoint. Leaving the fieldnull
or setting it totrue
will cause the current default behavior and should therefore be backwards compatible.Setting it to
false
will prevent your devices from generating a notification when you send a message yourself.The
notify_self
property controls whether the--notify-self
flag is attached to the generated command (which currently is always the case).Useful when you are using the API for both messages that you want to be notified about (for example when your home assistant sends out an alert) and ones you don't need to be alerted to (when using from a chat application where you compose messages yourself).
I have tried to autogenerate the documentation using swaggo/swag with version v1.8.10 but either the docs haven't been updated for a while or my configuration is wrong because the diff is pretty huge. If desired, I can still run
swag init
, although I'd be glad to know if there is something I should pay attention to config-wise.