Having trouble migrating stmp to new notification actions in 2026.8

Configuration
1

I have been following this thread and patiently waited until 2026.8.3 before updating. Bit the bullet this morning. First thing I got was this.

Detected use of deprecated action notify.gmail_notifications

Warning · Reported by SMTP

This stops working in version 2027.3.0. Please address before upgrading.

The action notify.gmail_notifications is deprecated and will be removed in a future release.

Please update your automations and scripts to use the notify entities with the notify.send_message or smtp.send_message actions instead.

Example automation using notify.send_message action:

action: notify.send_message
target:
  entity_id: notify.recipient
data:
  message: Hello World
  title: Hello

Example automation using smtp.send_message action:

action: smtp.send_message
target:
    entity_id: notify.recipient
data:
  title: Hello
  message: Hello World
  html: <html><body>Hello World<br><img src="cid:snapshot"></body></html>
  attachments:
    - media_source:
        media_content_id: media-source://camera/camera.demo_camera
        media_content_type: application/vnd.apple.mpegurl
      filename: snapshot.jpg
      content_id: snapshot

I have hundreds of automations that now need to be changed to support the new format. Will this be an automatic merge process like many other merges have been?

2

I wouldn’t bet on it.

Do a search, there have been a number of threads on this topic.

3

You can poke around and find info on how to adapt, from the repair, documentation and forums - but I haven’t found a single place yet with total information. Here is how I modified my notify.send_gmail type actions:

    - service: notify.send_message
      data:
        title: "Message Title"
        message: "Information"
      target:
        entity_id: notify.hass_gmail_<redacted>

If you edit an action using the developer tools in UI mode, you can select an existing target from the dropdown list. Switch to yaml mode and copy the entity_id – or just search your states for a notify. entity.

4

https://community.home-assistant.io/search?q=SMTP%20after%3A2026-07-30%20order%3Alatest

5

Unfortunately, from what I see in here, all of this is useless. It does not give you any suggestions on “how to fix this” without me having to go through hundreds of automations.

6

smtp does not use the new notifier, and a few issues are raised SMTP feature regression - no longer able to provide any email · Issue #178359 · home-assistant/core · GitHub

maybe also check the discussion/fr section to add a new smtp service that would do just that

7

ohh, i didn’t know
I have another Integration " Tibber " which supports “notify” ( To the Tibber Phone-App ), so no need for smtp, or open an email-app
And as i hate “notification-pop-ups” this is only for “Emergency Warnings” … gives one a little “kick” also then, when it’s triggered :joy:

8

I guess there’s a little good news…

For anything I do commonly in my automations more than a few times, like notifications, I use a script. Consider that when updating your automations. Scripts are flexible in how you call them, you can add features over time when needed, and then all your actual notification code lives in once place so much easier to update in the future. I also create wrapper scripts if I want to simplify parameters passed and provide defaults.

9

This! 

10

Step 1: search and replace all notify actions with send_message.

Step 2: copy the target: block from a test action in the developer tools.

Step 3. search all notify.send_message actions and paste in the target block.

I had 38. Yes it’s a pain, everyone gets it. Your choice is stay on the version you’re running, it will work as is forever as long as you don’t upgrade anything else as well. Or, upgrade and maintain – it’s the development model HA has chosen, for better or worse.

11

Yes, I know this is doable. I support all of my family’s Home Assistant. For me over 600 automations that need to be changed across 6 installs.

I have been slowly working on it and ran into an issue with html in the message body.

Someone correct me if I am wrong, but it appears that html is not a documented standard field of notify.send_message. I have many automations using html in the message body.
For example:

html: >

Todays Forecast Summary:

  • Condition: {{ states('sensor.condition') }}
  • Detail: {{ states('sensor.forecast').split('Wind')[0] | trim }}
  • Wind: {{ states('sensor.wind_speed') }} km/h
  • High: {{ states('sensor.high_temperature') }}°
  • UV Index: {{ states('sensor.uv_index') }}

Daily Extremes:

  • High: {{ states('sensor.high_temperature') }}°
  • Low: {{ states('sensor.low_temperature') }}°
  • Chance of precip: {{ states('sensor.chance_of_precip') | replace('unknown', '0') | replace('unavailable', '0') }}%

The message body in my email appears like this

html: >
  <div style="font-family: Arial, sans-serif; line-height: 1.4; color: #333;
  font-size: 13px; max-width: 500px;">

    <h2 style="margin: 0; padding: 5px 10px; font-size: 13px; background-color: #1a5276; color: #ffffff; text-transform: uppercase;">Todays Forecast Summary:</h2>
    <ul style="margin: 8px 0 15px 0; padding-left: 25px; list-style-type: disc;">
      <li><b>Condition:</b> <span style="color: #d35400; font-weight: bold;">Light Rain</span></li>
      <li><b>Detail:</b> Today. Cloudy with 70 percent chance of showers and risk of thunderstorms. Local smoke.</li>
      <li><b>Wind:</b> 8 km/h</li>
      <li><b>High:</b> <span style="color: #c0392b; font-weight: bold;">22°</span></li>
      <li><b>UV Index:</b> 4</li>
    </ul>

    <h2 style="margin: 0; padding: 5px 10px; font-size: 13px; background-color: #1a5276; color: #ffffff; text-transform: uppercase;">Daily Extremes:</h2>
    <ul style="margin: 8px 0 15px 0; padding-left: 25px; list-style-type: disc;">
      <li><b>High:</b> <span style="color: #c0392b; font-weight: bold;">22°</span></li>
      <li><b>Low:</b> <span style="color: #2980b9; font-weight: bold;">12°</span></li>
      <li><b>Chance of precip:</b> 70%</li>
    </ul>

HTML It looks like this in notify.gmail_notifications

image
image730×425 8.71 KB

Yes, I know smtp.send_message supports html. Unfortunately I didn’t know notify.send_message had issues with html in the message body. So, Now the hundred or so that I have done need to be done over… Not Happy…

Anyone know of any potential issues/conflicts that I need to look out for in smtp.send_message

12

This is the sort of thing Opencode is extremely good at. Tedious and boring.