Moving from Eufy Security / Eufy Clean
This app replaces two:
| You have | It becomes |
|---|---|
Eufy Security (com.eufylife.security) — cameras, doorbells, HomeBase, sensors | Anker Eufy (com.eufy) |
Eufy Clean (com.eufylife.home) — robot vacuums | Anker Eufy (com.eufy) |
The short version
You will re-pair your devices and rebuild your Flows. There is no way around that — a Homey device belongs to a driver inside a specific app, and a Flow card references that app's card id, so neither can be handed to a different app.
You do not have to do it all at once. Both old apps keep working while the new one is installed. Add one camera, rebuild one Flow, and take as long as you like.
What carries over, and what does not
| Devices | Re-pair. No cross-app handover exists. |
| Flows | Rebuild, or move most of them with the migration script. Card ids belong to an app. |
| Insights history | Does not transfer. New device, new log. |
| Your language | Kept — all twelve languages the old app had. |
| Your eufy account | Nothing to change. See the note about signing in below. |
Rebuilding is mostly recognition rather than relearning. alarm_motion, measure_battery and the detection triggers — a person was detected, the doorbell was pressed, a vehicle was detected — mean what they used to. Most of the old CMD_* action cards are now ordinary controls on the device, so those Flows get shorter.
A person was detected also carries a Person token — the name of the recognised face, when the camera reports one and the account has it enrolled. eufy separates a recognised person from a stranger on the wire, so An unrecognised person was detected is the card for the other case.
The old app's detection sensors are here too — person, stranger, pet, dog, vehicle, sound, crying and the three package ones — and they work the same way, because eufy leaves no choice: a detection is announced and its end never is, so the sensor is held on for a while and then cleared. How long is a setting on each device (Detection reset time, 30 seconds by default) rather than the fixed window the old app used.
A detection here fires before its picture has downloaded. A migrated Flow that sends the camera's image straight from the trigger would send the previous detection's picture. Turn on Wait for the Event image in the camera's or doorbell's settings, and its detection Flows wait for the new picture without any change to the Flows themselves.
Do it in this order
- Install Anker Eufy alongside what you have. Nothing conflicts.
- Add one device. Pick a category, choose your country, sign in once. Every other category is then available without signing in again.
- Rebuild that device's Flows, using the old ones beside them as the reference.
- Repeat at your own pace.
- Remove the old app when nothing you care about is left in it.
Moving Flows with a script
Once your devices are paired here, a HomeyScript can point most existing Flows at the new devices for you. The migration script page has the script to copy and the steps to run it.
- It finds the devices itself. An old device and a new one with the same serial number are treated as the same unit — there are no ids to fill in.
- It handles regular and Advanced Flows, from both Eufy Security and Eufy Clean.
- Each old card becomes the new card for that kind of device, with its settings converted — a night vision switch, a snooze time, an alarm duration, an arming mode. Arming moves to the new station device, or stays on a standalone camera, which is its own station.
- A Flow with a card it cannot convert safely is left alone and listed, so you can rebuild that card by hand. Nothing is half-migrated.
Run it with softRun = true first (the default). That run changes nothing: it shows which devices it paired and every change it would make. Set softRun = false to apply. Keep the old apps enabled until the final check at the end of the run reports no old devices left in any Flow.
Signing in
The old app told you to make a second eufy admin account, because Homey and your phone kept signing each other out. You no longer need to. The eufy cloud ties a session to a device identity, not just an account, and the old app used one derived from your e-mail — the same identity your phone presents. This app generates its own, so it holds a session of its own.
Use your normal eufy account.
The country matters. eufy keeps accounts on separate regional servers and decides which one to use before checking your password, so the wrong country means the sign-in fails with nothing explaining why. Pick where the account was registered, not where you are now.
What is better
- Live video on battery cameras. The old app could only stream from cameras with eufy's own RTSP server switched on, which excluded most of the range.
- New devices work without an app update. The app asks your account what each device reports and builds the controls from that, instead of carrying a hand-written list per model.
- One app, one sign-in for cameras, vacuums and everything else.
What is not there yet
- Room and zone cleaning for robot vacuums.
- Recording and two-way talk.
If something goes wrong
Device unreachable, or stuck signed out? Repair the device (device settings → Repair) to sign in again — that is what repair is for here.
Anything else: open an issue. Say which device model, what you expected, and what happened. If it is a sign-in problem, include the country you picked.