SMTP Motion
homebridge-smtp-motion · v1.2.1
Converts SMTP email messages into HTTP motion alerts for homebridge-camera-ffmpeg.
What it says it supports
Devices it names
- email-sending cameras
Shows up in Apple Home as from its README
What people report
Triggers camera-ffmpeg motion from camera emails; HOOBS setup problems and only one camera per email address.
- Partly works2
| Device | Status | What they said | Source |
|---|---|---|---|
| Amcrest 5MP UltraHD camera | Partly works | On HOOBS plugin failed to find camera-ffmpeg; override_http only sent email confirmationSaved copyCamera FFmpeg Bridge: { "platform": "Camera-ffmpeg", "name": "Camera FFmpeg", "cameras": [ { "name": "frontyard", "manufacturer": "Amcrest", "model": "5MP UltraHD", "serialNumber": "AMC060D3099705C467", "unbridge": false, "videoConfig": { "source": "-i rtsp://user:pw@IP:554/cam/realmonitor?channel=1&subtype=0", "stillImageSource": "-i http://user:pw@IP/cgi-bin/snapshot.cgi?chan=1", "maxWidth": 0, "maxHeight": 0, "maxFPS": 0, "maxBitrate": 4096, "forceMax": true, "vcodec": "copy", "audio": true, "debug": true }, "motion": true, "switches": false }, { "name": "backyard", "manufacturer": … Excerpt saved from GitHub on 2026-10-22. | Issue #134 · 2022-01 |
| MotionEyeOS camera | Partly works | SMTP port error; maintainer suggested HTTP webhook insteadSaved copyI have a camera on a pi running MotionEyeOS connected to my homebridge using the FFMPEG plugin. Trying to expose the motion sensor. Using this plugin, I get an error from MotionEye that “Notification Email Failed: Check SMTP port!” See attached image. I am using the IP address of my homebridge installation as the SMTP server. Any idea what I am doing wrong? Appreciate any assistance. Thanks! Excerpt saved from GitHub on 2026-10-22. | Issue #115 · 2021-03 |
Gathered from the plugin’s GitHub issues, pull requests, discussions, wiki and docs, and from r/homebridge. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local
Receives SMTP, forwards HTTP to camera-ffmpeg; exposes no accessories itself
You’ll need
- homebridge-camera-ffmpeg
Compatibility
| Verified by Homebridge | Yes |
|---|---|
| Homebridge versions | >=1.0.0 |
| Homebridge 2.0 | No |
| Node.js | >=10 |
| Settings in Homebridge UI | Yes |
| Matter | No |
| Platform name | smtpMotion |
| License | BSD-2-Clause |
Community signals
| Downloads a week | 27 |
|---|---|
| Downloads a month | 60 |
| GitHub stars | 9 |
| Open issues | 1 |
| Closed issues | 20 |
| Last code push | 2026-01-24 |
| Latest version | 1.2.1 (2021-02-21) |
| First published | 2020-07-22 |
| Releases | 8 |
In ReReHome
Whatever this plugin publishes reaches Apple Home as a normal HomeKit accessory behind your Homebridge bridge, so ReReHome shows and controls it like any other.
Bridges get their own settings page listing the accessories behind them.
Caveats from the README
- Does not expose any devices to HomeKit itself
Sources
- npm: https://www.npmjs.com/package/homebridge-smtp-motion
- Source code: https://github.com/Sunoo/homebridge-smtp-motion
- Issues: https://github.com/Sunoo/homebridge-smtp-motion/issues
- Verified plugins list: https://github.com/homebridge/verified