Control Mycroft by email
Allows you to send commands to mycroft by email, inspired by this blog post
I did not use mycroft home backend for skill settings, it is irresponsible to get your email credentials in there. Instead you need to edit mycroft.conf
This is a security measure, i will not change this behaviour
Add the following section to your mycroft.conf
"email": {
"mail": "",
"password": "",
"address":"imap.gmail.com",
"port":993,
"folder":"inbox",
"time_between_checks":30,
"include_read": false,
"whitelist": ["[email protected]", "[email protected]"]
}
only mail, password and whitelist are required, other parameters use the defaults for gmail, if using a different provider you might need to change address and port
time_between_checks is in seconds, it is the time to sleep between checking for new emails, the "lag" between a command and its execution
whitelist is a list of emails allowed to send commands to mycroft, if the sender is not in this list then the emails will be ignored
some uses cases, like using siri Notes, will mark emails as read, setting "include_read" to true will process those emails, note that this will execute ALL old emails on first run, it is strongly recommended that you only set this flag if using a newly created folder
You might need to change some settings in your email provider, for gmail you need to
- enable less secure apps https://myaccount.google.com/lesssecureapps
- enable imap https://mail.google.com/mail/u/1/?tab=mm#settings/fwdandpop
- ✔️ - tested and confirmed working
- ❌ - incompatible/non-functional
- ❓ - untested
- 🚧 - partial support
platform | status | tag | version | last tested |
---|---|---|---|---|
Chatterbox | ❓ | dev | never | |
HolmesV | ❓ | dev | never | |
LocalHive | ❓ | dev | never | |
Mycroft Mark1 | ❓ | dev | never | |
Mycroft Mark2 | ❓ | dev | never | |
NeonGecko | ❓ | dev | never | |
OVOS | ❓ | dev | never | |
Picroft | ❓ | dev | never | |
Plasma Bigscreen | ❓ | dev | never |
tag
- link to github release / branch / commitversion
- link to release/commit of platform repo where this was tested
- JarbasAl
Configuration
#configuration