Transport Adaptors¶
These are the notification transport adaptors built into Supernotify:
- Alexa Devices Transport Adaptor
- Alexa Media Player Transport Adaptor
- Chime Transport Adaptor
- Discord Transport Adaptor
- Email Transport Adaptor
- Generic Transport Adaptor
- Gotify Transport Adaptor
- HTML5 Browser Push Transport Adaptor
- Kodi Transport Adaptor
- LaMetric TIME Transport Adaptor
- Matrix Transport Adaptor
- Media Player Transport Adaptor
- Mobile Push Transport Adaptor
- MQTT Transport Adaptor
- Notify Entity Transport Adaptor
- ntfy Transport Adaptor
- Persistent Transport Adaptor
- Pushover Transport Adaptor
- SMS (Text Messaging) Transport Adaptor
- Telegram Transport Adaptor
- TTS Transport Adaptor
Customizing Transports¶
Options¶
Most transport adaptors support an additional set of options, some common ones for handling titles or suppressing URLs, and some specific to a transport.
In this example, image attachments for emails get tuned ( since these are commonly needed, the email delivery transport defaults to always having progressive and optimize being true, unless explicitly overridden)
transports:
email:
delivery_defaults:
action: notify.smtp
options:
jpeg_opts:
progressive: true
optimize: true
quality: 50
png_opts:
optimize: true
Entities¶
Each loaded Transport Adaptor has a switch.supernotify_transport_XXXX entity in Home Assistant, with its configuration and current state as attributes. Turning it off, whether from a dashboard, Developer Tools or an automation, suppresses all of the deliveries that use that transport, and turning it on again re-enables them. The delivery switches keep their own state throughout. See Delivery Entities.
Table of Options¶
All of these are set by passing an options block in Delivery config or Transport defaults. See the Options Reference for the full, generated list of common and transport-specific options, their types, examples and descriptions - and Default Options for the actual default value each transport sets.
jpeg_opts can also be set per runtime call by passing in the media block.
Options typed as Selection Rules (e.g. device_os_select, target_select) share a common flexible syntax - see that page for the full set of forms.