Error 400 sending to Gotify within a notifications group

[V4ler1an]

I use notification groups in Home Assistant and would really like to be able to add Gotify to some of them. The gotify notification entity is called 'notify.gotify'. When I add it to the relevant group in configuration.yaml, it's accepted by the developer tool config checker, but creates a 400 error when trying to send a message using the group. Is this a known limitation, or should it work? Or have I set this up wrong? The gotify messaging works normally from HA when I send it to just notify.gotify instead of through the group. If this is a limitation, is there any way it could be resolved?

My group in configuration.yaml:

• name: Notify_Group_1
  platform: group
  services:
  • action: my_phone
  • action: gotify

Error:

ERROR (MainThread) [custom_components.gotify.notify] Error while sending gotify message: 400 Client Error: Bad Request for url: https://<my_gotify_server>/message

[V4ler1an]

I've just found that if i strip the message clean of anything in its 'data' yaml field it does successfully send the message to gotify through the group. This is a shame because I have all sorts of yaml in my notifications and I don't know what specifically is causing the error. It would also be a big job to make all my notifications Gotify friendly. Is there a way to get gotify to ignore the data? Any idea how I might get this to work?

Update: I've discovered that the 'priority: high' value I had in my notifications under data: was the issue. This is required to make notifications appear when the phone is on do not disturb. Either removing it or changing it to 'priority: 10' will avoid the 400 error.

Is there anything clever I could do to make the gotify add-on only concern itself with the title and message, ignoring any data: values? Thanks for any help.

[1RandomDev]

Is there anything clever I could do to make the gotify add-on only concern itself with the title and message, ignoring any data: values?

That's not supported right now, but would be no big deal to add in the future.

A much better approach in my opinion would be automatically mapping the priorities high, normal, low and min to their equivalent numeric values in Gotify.

[V4ler1an]

Sorry for being a bit of a noob, can you give me any pointers on how I might setup this mapping?

[V4ler1an]

One other issue. I have quite a number of notifications that are sent to make my phone read a text-to-speech message. These are triggered by there being 'TTS' in the message body and nothing else. The actual text read out is in the data: yaml. A way to filter out these messages would be really helpful.

[1RandomDev]

In v1.2.0 priorities specified as a string are automatically mapped to their corresponding numeric values. And I have added an option msg_blacklist that can be set to an array of messages that should be discarded.

[V4ler1an]

Perfect! Works great on both, thank you. A question... if I add Home Assistant as an app multiple times into Gotify with different names / tokens, would the Gotify HA add-on support multiple notification services in configuration.yaml? Would it match them up by token? I'm curious because I could then have multiple categorised channels in Gotify.

[1RandomDev]

You can add multiple instances with different names, then call them by name.

[V4ler1an]

Great, i'll have a play with that. Have you thought much about making the add-on recognise some of HA's standard methods for things like images or clickable actions?

[1RandomDev]

Not really right now since it would be a lot of work and I personally don't see a reason to continue using Google/Apple based notifications with Gotify.
Edit: Maybe I'll look into it when I'm bored.

[V4ler1an]

Yes I also like keeping things off the Internet and away from the data brokers-in-chief. Fortunately HA does have a direct local only option for the companion app that avoids Google's firebase. The native HA messaging allows some useful stuff though. Thanks for your help.