OK I got dd-wrt working
instead of 192.168.abc.def
I used 192.168.abc.def/24
Don’t know why but heck its progress
OK I got dd-wrt working
instead of 192.168.abc.def
I used 192.168.abc.def/24
Don’t know why but heck its progress
I’m learning a little bit every hour…
I finally found the log of the error. Can someone please translate this stuff.
Logger: homeassistant.components.imap_email_content.sensor
Source: components/imap_email_content/sensor.py:97
Integration: imap_email_content (documentation, issues)
First occurred: 7:45:50 PM (1 occurrences)
Last logged: 7:45:50 PM
Failed to login to imap.gmail.com
This log is based on this code
sensor:
- platform: imap_email_content
name: motion_status
server: imap.gmail.com
port: 993
username: !secret gmail_username
password: !secret gmail_password
folder: Inbox
scan_interval: 10
senders:
- !secret gmail_sender2
value_template: >-
{% if 'DOOR' in subject %}
motion_yes
{% endif %}
Your sensor definition looks right to me. Because the error message simply says “Faild to login to imap.gmail.com”, I think it has to be an issue related to your username or password.
I configured this integration recently with Gmail, and the first attempts for Home Assistant to login were blocked by Google because the access was from a “less secure app”. You can turn on access for less secure apps, but the warnings I got led me to believe access is off by default.
For Gmail you need to create an app password and use that instead of your actual gmail password.
@firstof9 Strike up the (Metallica) Band, break out the Margarita’s with the double chasers…
That did it. Thank You
Thank you all!!!
Hello there. Is the usage of “imap_email_content” deprecated?