github
/
apprise
mirror of https://github.com/caronc/apprise
1
0
Fork 0
Code Issues Releases Wiki Activity

Updated Notify_fcm (markdown)

master
Chris Caron 2022-01-25 18:21:59 -05:00
parent 65cdfee9ae
commit 1f21ecb959
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Notify_fcm.md

@ -48,6 +48,10 @@ You can mix and match these entries as well:
| Device | No | The device you wish send your message to | Device | No | The device you wish send your message to
| Topic | No | The topic you want to publish your message to. | Topic | No | The topic you want to publish your message to.
| mode | No | The mode can be set to either **legacy** or **oauth2**. This is automatically detected depending on what you provide the Apprise URL. But you can explicitly set this here if you require. | mode | No | The mode can be set to either **legacy** or **oauth2**. This is automatically detected depending on what you provide the Apprise URL. But you can explicitly set this here if you require.
| priority | No | The FCM Priority. By default the priority isn't passed into the payload so it takes on all upstream defaults. Valid options here are `min`, `low`, `normal`, `high`, and `max`.
| image | No | Set this to `yes` if you want to include an image as part of the payload. Depending on your firebase subscription; this may or may not incur charges. By default this is set to `no`
| image_url | No | Specify your own custom image_url to include as part of the payload. If this is provided, it is assumed `image` is `yes`. You an additionally set `image=no` to enforce that this assumption does not happen.
| color | No | Identify the colour of your notification by specifying your own custom RGB value (in format \#RRGGBB where the hashtag (`#`) is optional. The other options are `yes` and `no`. When set to `no`, the `color` argument simply is not part of the payload at all. When set to `yes` (default), Apprise chooses the color based on the message type (info, warning, etc).
**Note:** This notification service does not use the title field; only the _body_ is passed along. **Note:** This notification service does not use the title field; only the _body_ is passed along.