Skip to content

Eufy cameras

Eufy cameras reach Aperture in two separate ways. Video comes over RTSP, like any other camera, on the models that offer it. Control (pan/tilt, the siren) goes through a bridge, eufy-security-ws, that signs in to your Eufy account. This page covers the bridge: what Aperture expects of it, signing in, and adding the controls to a camera.

Only some Eufy models offer an RTSP stream, mostly indoor and wired ones, and it has to be switched on in the Eufy app. Battery cameras usually do not offer one. Add the stream like any other camera; see Add cameras.

The bridge does not add video. A Eufy camera without RTSP cannot be recorded or watched in Aperture, bridge or not.

Aperture does not install eufy-security-ws; install it yourself, following that project’s own instructions. Aperture then manages its account, so the bridge has to be set up the way Aperture expects:

Requirement Value
Runs on The Aperture server itself.
systemd unit eufy-security-ws.service. Aperture restarts this unit whenever you save the account.
Config file /var/lib/aperture/eufy-bridge.json, the file the bridge reads its account from. Aperture writes it.
WebSocket address http://127.0.0.1:3000. Aperture connects here; the app has no field to change it.

The bottom of the Eufy card repeats these values as the server uses them: “Aperture does not install the bridge. It expects eufy-security-ws on this machine, run by systemd as … and listening on …, with its config at ….”

When you save the account, Aperture writes username, password and country into the config file and leaves any other keys you set there untouched. It writes the file in one step (so the bridge never reads half a file), with mode 0640 and the owner the file already had, then runs systemctl restart eufy-security-ws.service. The bridge reads its account only when it starts, which is why the restart is needed.

  1. Open Integrations and select Eufy. The status reads Not set up.
  2. Enter your Eufy account email, Password and Country, the two-letter code of the country your Eufy account is registered in. The field starts with DE; change it if your account is elsewhere.
  3. Click Sign in. Aperture writes the account to the bridge and restarts it; the button shows “Restarting bridge…”. If the bridge cannot be updated (for example, the unit does not exist), you see “could not update the bridge:” with the reason, and Aperture does not save the account. The bridge’s config file may already hold it at that point.
  4. Answer any challenge Eufy raises (see below). The status changes to Connected.

The status at the top of the card:

Status Meaning
Not set up No account saved yet.
Signing in… The bridge is running and signing in to Eufy.
Needs you Eufy wants a verification code or a captcha.
Connected The bridge is signed in.
Offline An account is saved but the bridge does not answer. The card says “The bridge is not responding. It may still be starting, or it may have rejected the account.” with the last error under it.

Eufy often asks for more during sign-in, and the bridge passes the question on to Aperture, which shows it on the same card:

  • Verification code: “Eufy emailed a verification code to” your address. Type the code into Code and click Verify. Expect this straight after the first sign-in.
  • Captcha: Eufy shows an image. Type what it says into Answer and click Submit.

Aperture keeps one connection open to the bridge so that it hears these prompts as they arrive. If the bridge is down, Aperture tries to reconnect every 10 seconds.

While the bridge is not connected, the account fields stay on the card; change them and click Update account. Leave Password empty (“unchanged”) to keep the saved one, for example to change only the country. Every save restarts the bridge, and a new verification code may follow. Saves are recorded in the Activity Log.

Once connected, the card lists the account’s Devices:

Column Content
Name The device’s name in the Eufy app.
Model Its model, when the bridge reports one.
Pan & tilt Yes when the device itself reports that it can pan and tilt. Aperture never guesses this from the model name.
Serial number With a copy button. You need it to attach controls to a camera.

“Signed in, but this account reports no devices yet. Eufy can take a minute after a fresh sign-in.” means the list is empty. After a fresh sign-in the bridge reports the devices a little after it connects, so Aperture reads the list again when the bridge says it is connected and whenever it reports a device added or removed, and the card keeps checking every 4 seconds until devices appear. A device you add to your Eufy account later shows up the same way. If the list stays empty some minutes after the status reads Connected, check the bridge’s own log (journalctl -u eufy-security-ws -n 50).

The controls come from the Eufy Control example extension, which uses the same bridge. It holds no Eufy credentials itself.

  1. Add the camera’s RTSP stream to Aperture first, so there is a camera to attach the controls to.
  2. Install the Eufy Control extension and approve its permissions.
  3. In its settings:
    • eufy-security-ws address: leave it at http://127.0.0.1:3000. Use http://, not ws://.
    • Camera mapping: for each camera, pick the Aperture camera and enter its Eufy serial number from the Devices list above.
    • Jog step (ms): how long one nudge moves the camera, 500 ms by default. Eufy cameras pan in timed bursts rather than to an angle, so this is the unit of movement.

A mapped camera then shows a pan/tilt jog wheel over its picture, and a Eufy menu in the player toolbar with the bridge’s and the device’s status and Sound alarm (10s) / Stop alarm buttons.

  • Cloud dependency. Control works only while Eufy’s cloud accepts the bridge’s sign-in. When Eufy is unreachable, or asks for a new code, the controls stop until you answer on the Eufy card.
  • Same machine, fixed address. The bridge must run on the Aperture server as eufy-security-ws.service, listening on 127.0.0.1:3000, with its config at /var/lib/aperture/eufy-bridge.json.
  • No video through the bridge. Recording and live view need the camera’s own RTSP stream.
  • One account. Aperture manages one Eufy account for the bridge.
  • “could not update the bridge: restarting eufy-security-ws.service …” The unit does not exist or failed to restart. Check it with systemctl status eufy-security-ws and journalctl -u eufy-security-ws -n 50.
  • The status stays Offline. The bridge is not listening on 127.0.0.1:3000, or it stopped after rejecting the account. The bridge’s own log says which.
  • Connected, but a camera shows no jog wheel. Check that the device reports Pan & tilt: Yes, and that its serial number is mapped to the right camera in the extension’s settings.

Related: Add cameras · Extensions · Privacy