e-Mail Notifications¶
Configuration¶
If you have e-mail configured in Home Assistant, you can include it in Supernotify by setting up an e-mail delivery:
The email for transport must match the name given to a SMTP notify integration in your config, which will look like this Amazon Simple Email Service example:
Targets¶
There are several ways of supplying targets:
Built-into the SMTP Notify configuration¶
The recipient field is a mandatory field. Not recommended, other than as a back-up address if no other target provided.
Supernotify Delivery¶
- name: Supernotify
platform: supernotify
delivery:
plain_email:
transport: email
target:
- joe@mcdoe.com
- billy@weeschool.edu
Supernotify Recipient¶
This has the advantage that e-mail addresses can be defined in one place, and you can send targeted email notifications in automations by using the person entity instead.
- name: Supernotify
platform: supernotify
...
recipients:
- person: person.joe_mcdoe
email: joe@mcdoe.com
- person: person.billy_mcdoe
email: billy@weeschool.edu
On Action Call¶
Whatever method has been defined, you can always override it on an notification action call
- action: notify.supernotify
data:
message: Something went off in the basement
target: john@mcdoe.co.bn
Example SMTP Configuration¶
Only 1.5% of Home Assistant users who share their data use the SMTP integration, so it is relatively rare for people to use email notifications, despite that being the simplest, most common way to communicate.
Much of the complexity of e-mail is in receiving mail, its much simpler to send it, and lots of services on the internet to do so, some of which have free tiers for low volume.
Google Mail¶
Out of the box, there's support in Home Assistant for Google Mail Integration. See the Home Assistant Example
Amazon Simple Email Service¶
In this example, the username and password live separately in the secrets.yaml file, see Storing Secrets for more on that.
Amazon SES is a cheap and easy to use service, with the overhead of having to set up an Amazon AWS service if you don't have one already. The free tier saves money for new AWS accounts, although you can send 1000 emails for $0.10 USD so it doesn't save all that much ( more if you send attachments like images, though only $0.12 USD per Gb at 2025 prices.)
- name: email
platform: smtp
port: 587
timeout: 30
encryption: starttls
sender: hass@myhouse.org
recipient: admin@myhouse.org
server: email-smtp.eu-west-2.amazonaws.com
username: !secret aws_smtp_key
password: !secret aws_smtp_secret
Amazon have more help on how to get their SMTP set up at Set up email sending with Amazon SES
Warning
Amazon AWS can be a very cheap way of getting services like e-mail and storage with its pay-as-you-go serverless model, 10c a month buys a decent amount of emails.
However, it can also be exceedingly expensive if abused or mis-configured.
Follow the Security Best Practices, including MFA for the main account, and giving Home Assistant a dedicated IAM user that can only access the services it really needs, with the account ID and secret key kept secure.
Add a budget and cost alerts if you're still worried!
Other Email Options¶
- ha-smtp - HACS integration for SMTP that doesn't need YAML config
- email-notifier - Another UI-configured alternative SMTP integration
- MS365 Mail for Home Assistant - Microsoft based e-mail sending
- Self Hosting
- Mail-in-a-Box - Run on your own server, including receiving mail, running own webmail service
- Mailu - Docker based self-hosted email
- Mailcow - Docker based self-hosted email