SMTP stopped working notify.send_email not found

Configuration
1

Not sure exactly when but I noticed that SMTP has stopped working for me.

My configuration.yaml-

notify:
  # Email notification
  - name: send_email
    platform: smtp
    server: smtp.mail.me.com
    port: 587
    timeout: 15
    sender: hidden
    encryption: starttls
    username: hidden
    password: !secret send_email_password
    recipient:
      - hidden
    sender_name: Home Assistant

Sample from automation-

action: notify.send_email
metadata: {}
data:
  message: Leak detected in main water heater.
  title: Main Water Heater Leak Detected
  target: hidden

When I run action I get the following error-

Action notify.send_email not found

This was working. Not sure why it’s not now???

2

Hello

Is there any error in the logs?
Have you tested it outside of the automation, say in a sample call or in
Open your Home Assistant instance and show your action developer tools.

3

From the log-
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:935
integration: Home Assistant WebSocket API(documentation, issues)
First occurred: 6:59:45 PM (1 occurrence)
Last logged: 6:59:45 PM

[139706909671104] Action notify.send_email not found

Action is not listed in DevTools.

4

Well I can see my created notify actions from the that tool. Are you sure it is still in the right place?
Was it deleted somehow?

image
image531Ă—314 24.4 KB

5

It’s still in configuration.yaml. I copied and pasted in the first post.

6

Do you have more than one notify: keys? if so it will only use one of them. you would need to consolidate them.

7

Not sure what you mean by “keys”? Here is the entire notify entry-

notify:
  # Email notification
  - name: send_email
    platform: smtp
    server: smtp.mail.me.com
    port: 587
    timeout: 15
    sender: hidden
    encryption: starttls
    username: hidden
    password: !secret send_email_password
    recipient:
      - hidden
    sender_name: Home Assistant
  # Prowl notification
  - name: prowl
    platform: prowl
    api_key: !secret prowl_api
    priority: 2
8

I found the issue. It was an authentication failure for SMTP. Evidently that keeps the action from loading but doesn’t generate a repair message. Had to go way back through the logs. Fixed now.

Thanks for taking the time to help with this!!!

1 Like