What changed since 5.0.0-beta.9

If your HomeBase showed as "Not responding" in the Home app, this is the release that fixes it.

It happened to any base left on Schedule, Geofencing, a Custom mode, or with its alarm switched off.
The plugin only understood Home, Away and Disarmed, and answered a question it could not answer with an
error — which the Home app shows as the whole accessory being unreachable, even though your sensors and
cameras were working. Nothing pointed at the guard mode, which is the actual cause.

Now every mode your base reports has something to show. Off reads as disarmed, and Schedule, Geofencing
and the Custom modes read as Night, with a fault marker to say the state shown is approximate.

And you can now say what each HomeKit state means on your own base. In the device's settings there is a
small table: HomeKit's Home, Away, Night and Off against your station's nine modes. Assign Night a mode and
HomeKit gains a Night control it did not have; leave a state empty and it stays out of the Home app. The
defaults are Home, Away and Disarmed, so nothing changes unless you change it.

This is the setting 4.x had and 5.x did not.

Several cameras behind one HomeBase now stream at the same time, each over its own connection to the
base, at full frame rate. A HomeKit Secure Video recording is no longer refused because someone is watching
another camera on that base, and a recording is no longer stopped when they start. Snapshots still stand
aside while a camera is being watched or recorded, and the last picture answers in their place — a still
shares the base's session, so it cannot help taking it.

Runs against the newest eufy SDK, 0.2.0-beta.12, which is what serves those cameras at once.

Why a new plugin at all

The old plugin talked to eufy through a library that is no longer maintained, and eufy changed how its
app talks to their servers. Rather than patch around that, the whole foundation was rebuilt against how
the current eufy app actually behaves.

That is why this took a while, and why it is a fresh start instead of an upgrade.

What happens to 4.x

It stays on npm and keeps working for as long as eufy's side lets it. It is not maintained: no bug
fixes, no support for new devices, and no work to follow changes eufy makes.

Everything from here — fixes, devices, features — happens on 5.x. That is the whole reason the rewrite
exists, and keeping two plugins alive would slow it down for everybody.

You do not need to move today. You will need to move.

What you get in the Home app

• Cameras — live video and audio, snapshots, two-way talk, and HomeKit Secure Video recording
• Doorbells — the doorbell press
• Motion sensors
• Contact sensors — door and window open/closed
• Locks
• Security modes — home, away, off
• Sirens
• Smart lights
• Battery level and charging

Logging in handles captcha and two-factor codes. You stay logged in across Homebridge restarts.

Why you might see less than that list

The plugin only adds something to the Home app when your device actually reports it. Devices differ, even
within the same product range — two cameras that look the same can report different things.

So a device can show up in the plugin's dashboard without appearing in the Home app yet. That is not a
crash, and it is worth telling us about.

When the plugin is unsure what a setting means, it deliberately shows nothing rather than guessing. A
switch that does the wrong thing is worse than a switch that is not there.

Things you will notice

• A switch or lock can take a moment to settle. The plugin waits for the device to confirm what it
  actually did instead of assuming the command worked.
• Some devices appear with fewer controls than the eufy app shows. That is the point above, not a bug.

Something not working? Use the built-in diagnostics

Do this before opening an issue — it does most of the work for you.

In the Homebridge UI, open this plugin's settings, find the device that is misbehaving, and click
Run diagnostics.

It then walks you through it:

1. It asks a few questions about what is wrong and picks the matching profile.
2. It tells you exactly what to do to make the fault happen again, and what to check first.
3. You click Start diagnostics session and reproduce the problem while it watches.
4. It shows you a manifest of everything it collected, and what it always leaves out.
5. You click Download encrypted archive — the file stays on your machine. Nothing is uploaded.

Attach that file to your issue, or share it with a maintainer. It carries what we need and not your
serial numbers, addresses or login details.

Some devices show Diagnostic only with a note saying "Nothing is wrong with your setup and there is
nothing here to fix." That is the case described above — the device is recognized, but its main function
does not have a verified representation yet. No need to report those unless you can help test one.

Still stuck?

Open an issue: https://github.com/homebridge-plugins/homebridge-eufy/issues

Tell us which eufy devices you own and what you expected to see, and attach the diagnostics archive if
you were able to create one.

Did you report something before and get closed automatically? That was leftover automation from when
the project was on hold. It is now removed for real — it had still been running from a branch we had missed.
Please open your report again; it stays open and it gets read.

Thank you

Wingers — for testing build after build on real devices, chasing the problems that only show up
sometimes, and sending the logs that turned guesses into fixes.

And max246, lenoxys and martijnpoppen.

Documentation ·
Requirements ·
Setting it up