IMAP Email Content

The imap_email_content integration will read emails from an IMAP email server and report them as a state change within Home Assistant. This is useful if you have a device that only reports its state via email.


To enable this sensor, add the following lines to your configuration.yaml file:

# Example configuration.yaml entry
  - platform: imap_email_content
    port: 993
    username: YOUR_USERNAME
    password: YOUR_PASSWORD
    folder: YOUR_FOLDER
      - [email protected]

Configuration Variables

server string Required

The IP address or hostname of the IMAP server.

port integer (Optional, default: 993)

The port where the server is accessible.

name string (Optional)

Name of the IMAP sensor.

username string Required

Username for the IMAP server.

password string Required

Password for the IMAP server.

folder string (Optional, default: INBOX)

Folder to get mails from.

senders string Required

A list of sender email addresses that are allowed to report state via email. Only emails received from these addresses will be processed.

value_template template (Optional)

If specified this template will be used to render the state of the sensor. If a template is not supplied the message subject will be used for the sensor value. The following attributes will be supplied to the template.


The from address of the email.


The body of the email.


The subject of the email.


The date and time the email was sent.

verify_ssl boolean (Optional, default: true)

If the SSL certificate of the server needs to be verified.

Example - keyword spotting

The following example shows the usage of the IMAP email content sensor to scan the subject of an email for text, in this case, an email from the APC SmartConnect service which tells whether the UPS is running on battery or not.

  - platform: imap_email_content
    name: house_electricity
    port: 993
    username: MY_EMAIL_USERNAME
    password: MY_EMAIL_PASSWORD
      - [email protected]
    value_template: >-
      {% if 'UPS On Battery' in subject %}
      {% elif 'Power Restored' in subject %}
      {% endif %}

The same template structure can scan the date, body or sender for matching text before setting the state of the sensor.

Example - extracting formatted text from an email using template sensors

This example shows how to extract numbers or other formatted data from an email to change the value of a template sensor to a value extracted from the email. In this example, we will be extracting energy use, cost, and billed amount from an email (from Georgia Power) and putting it into sensor values using a template sensor that runs against our IMAP email sensor already set up. A sample of the body of the email used is below:

Yesterday's Energy Use:                             76 kWh
Yesterday's estimated energy cost:                  $8
Monthly Energy use-to-date for 23 days:             1860 kWh
Monthly estimated energy cost-to-date for 23 days:  $198

To view your account for details about your energy use, please click here.

Below is the template sensor which extracts the information from the body of the email in our IMAP email sensor (named sensor.energy_email) into 3 sensors for the energy use, daily cost, and billing cycle total.

  - sensor:
    - name: "Previous Day Energy Use"
      unit_of_measurement: "kWh"
      state: >
       {{ state_attr('sensor.energy_email','body')
         | regex_findall_index("\*Yesterday's Energy Use:\* ([0-9]+) kWh") }}
    - name: "Previous Day Cost"
      unit_of_measurement: "$"
      state: >
        {{ state_attr('sensor.energy_email', 'body')
          | regex_findall_index("\*Yesterday's estimated energy cost:\* \$([0-9.]+)") }}
    - name: "Billing Cycle Total"
      unit_of_measurement: "$"
      state: >
        {{ state_attr('sensor.energy_email', 'body')
          | regex_findall_index("\ days:\* \$([0-9.]+)") }}

By making small changes to the regular expressions defined above, a similar structure can parse other types of data out of the body of other emails.