Skip to main content

Email, Pushover, webhooks and ntfy

The driver sends through accounts the customer owns. This page lists what each one needs and where it goes in the setup app. Email and Pushover are on the Email and Pushover tab; webhooks and ntfy topics are on Who gets what.

ChannelReachesSet up on
Email by SMTPPeopleEmail and Pushover
Email by the SendGrid APIPeopleEmail and Pushover
PushoverPeople's phones, tablets and watchesEmail and Pushover, plus a key per person
WebhookHome Assistant, Slack, Zapier, Make, n8n, Power Automate and other servicesWho gets what
ntfyAn ntfy topic, on ntfy.sh or your own serverWho gets what

After every change, press Save and then the test button for that channel.

Email by SMTP​

Choose SMTP server and fill in:

FieldWhat to enter
ServerThe provider's SMTP server name.
PortUsually 587.
SecuritySTARTTLS (recommended). Use None only for a relay on the local network.
Username and PasswordThe account that sends.
From addressThe address messages come from. Leave it empty to use the username, if the username is an email address.
From nameThe name people see, for example "Crestron Home".
Port 465

The driver doesn't support port 465 (implicit TLS). Every provider below also accepts port 587 with STARTTLS.

Microsoft 365​

  • Server smtp.office365.com, port 587, STARTTLS.
  • The mailbox needs Authenticated SMTP turned on. It's off by default in many tenants: in the Microsoft 365 admin centre, open the user, then Mail → Manage email apps, and tick Authenticated SMTP.
  • If the account uses multi-factor sign-in, use a separate mailbox for sending, or an app password if the tenant allows them.

Gmail and Google Workspace​

  • Server smtp.gmail.com, port 587, STARTTLS.
  • The password is an app password created for the driver. The account needs 2-Step Verification turned on; then create one under Google Account → Security → App passwords.

Amazon SES​

  • Server email-smtp.<region>.amazonaws.com, for example email-smtp.eu-west-2.amazonaws.com, port 587, STARTTLS.
  • The username and password are SES SMTP credentials, created in the SES console under SMTP settings. They are different from AWS access keys.
  • The From address must be a verified identity in SES. While the account is in the SES sandbox, every recipient must be verified too.

SendGrid over SMTP​

  • Server smtp.sendgrid.net, port 587, STARTTLS.
  • The username is the word apikey and the password is a SendGrid API key.
  • Fill in the From address: it must be a verified sender in SendGrid.

Email by the SendGrid API​

Choose SendGrid and enter:

  • an API key with the Mail Send permission;
  • a From address that's a verified sender or on an authenticated domain in SendGrid;
  • a From name.

SendGrid has no free plan, so the customer needs their own paid account.

Pushover​

Pushover sends to the Pushover app on phones, tablets and watches. Each person needs the app and an account, which Pushover charges for once per platform after a trial.

  1. Sign in at pushover.net, create an application for the house, and copy its API token into Application token.
  2. On Who gets what, enter each person's Pushover user or group key. They find it on their own Pushover dashboard.

How each level arrives:

LevelPushover priority
infoLow: no sound or vibration
noticeNormal
warningHigh: sounds even in the phone's quiet hours
criticalEmergency: repeats until someone acknowledges it

A template can set its own Pushover priority and sound, which overrides the level.

A critical message repeats every Repeat a critical message every (seconds), 60 by default, until someone acknowledges it or Stop repeating after (seconds) passes, an hour by default. When someone acknowledges it, the driver raises the Critical message acknowledged in Pushover event in Crestron Home.

The test result shows how many Pushover messages the application has left this month.

Webhook​

On Who gets what, press Add a webhook and enter:

FieldWhat to enter
NameWhat the installer calls it, for example "Home Assistant".
URLThe address to call. Placeholders such as {subject} can go in it.
MethodPOST, PUT or GET.
Content typeapplication/json unless the service wants something else.
HeadersAny headers the service needs, such as Authorization. Their values are saved like passwords.
BodyWhat to send. Leave it empty to send the standard body below.

The standard body is:

{"subject":"…","body":"…","level":"warning","link":"…","tag":"…","time":"…","room":"…"}

A body of your own can use these placeholders: {subject}, {body}, {level}, {link}, {tag}, {time}, {date}, {timestamp} and any {var:name} the message carries. Values are escaped to suit the content type, so a quote in a message can't break a JSON body.

Self-signed certificates

The driver checks the certificate of an https:// address. A server with a self-signed certificate, such as a Crestron processor or a local server without a certificate from a public authority, fails with "The server's certificate isn't trusted". On the local network, use http:// for those servers.

ntfy​

On Who gets what, press Add an ntfy topic. The Topic URL starts filled in with https://ntfy.sh/ and a random topic name: subscribe to that topic in the ntfy app, or change the address to a topic on a server on the local network. If the topic needs a login, enter an Access token.

The subject becomes the notification's title, the level sets its priority (info is low, critical is the highest), and a message's link opens when the notification is tapped.

Choose a topic name nobody will guess

On the public ntfy.sh server, anyone who knows a topic name can read it. Use a long, random name, or a server of your own.

When a send fails​

Each delivery is tried again if the service doesn't answer or says it's busy: after 30 seconds, 2 minutes and 10 minutes. A refusal, such as a wrong password, isn't retried. The Send log tab shows every attempt and the service's own reason when it fails. One failed channel doesn't hold up the others.