Eufy Security

Preflight Checklist [x] I have searched the existing issues and this device has not been requested before. [x] I have checked the eufy-security-client compatibility list. Device Information [code] Upstream Compatibility No, not listed Upstream Issue _No response_ Additional Context This is for the 4G LTE Cam S330. It is currently connected to the HomeBase S380. All firmware is up-to-date at this time.

Excerpt saved from GitHub on 2026-10-22.

{ "uniqueId": "T8172P10254111FB", "displayName": "Driveway Cam", "type": 89, "name": "Driveway Cam", "model": "T8172", "serialNumber": "T8172P10254111FB", "hardwareVersion": "P1", "softwareVersion": "1.0.6.5", "stationSerialNumber": "T8030P1322511D64" }

Excerpt saved from GitHub on 2026-10-22.

Preflight Checklist [x] I have searched the existing issues and this bug has not been reported before. [x] I understand V4 is no longer maintained, and that a fix will only ever land in V5. [x] I am using a dedicated guest admin account (not my main Eufy account). [x] I have restarted Homebridge and the issue persists. Environment [code] Area Device Discovery Diagnostics Archive homebridge-eufy-support-1d26b278-6392-4755-8827-e9b9124606c9.eufysupport.gz What happened? Two devices that are recognized but not represented, a T8506 and T85L0 lock.

Excerpt saved from GitHub on 2026-10-22.

I thought it would be interesting to point out that I am testing the existing HKSV plugin (2.3.5) on the following cameras: Driveway S40 Camera T8124 Solar Solo Cam T8134 Dual Camera Solar T8170 Solar Wall Light Cam T81A0 All of the cameras operate as motion sensors and/or sirens. One thing that I realised could be an issue, I am not using a home base. Could this contribute to the issues that I have experienced with the supported S40 Cam as well as potentially the others? [code] [code]

Excerpt saved from GitHub on 2026-10-22.

What happened? Apparently when I have my C120 camera connected to the homebase the live feed video won't work. I connect it directly to the router and it works fine with homekit. Has anyone else had this issue or know how to resolve it? I'd like it to be connected to my homebase if I could. Currently on Homebridge 1.11.1, Node 24.12.0, and plugin version 4.3.7, running it all on Unraid My Doorbell E340 seems to be working fine and it didn't work when it wasn't connected to my Homebase before I got it. Device Type Indoor Camera (Supported) Plugin Version other (UnSupported) HomeBridge Version …

Excerpt saved from GitHub on 2026-10-22.

What happened? I blieve this was to be fixed with 2.3.5 but I still cannot get S220 camera to load. It shows up as a siren only in Apple Home. Photos not updated with camera: [ /] Device Type other (UnSupported) Plugin Version other (UnSupported) HomeBridge Version v1.6.x (Supported) NodeJS Version v18 (Supported) Operating System Raspbian 10+ (Supported) Relevant log output [code] [code] shell { "enableDetailedLogging": true, "CameraMaxLivestreamDuration": 30, "pollingIntervalMinutes": 10, "hkHome": 1, "hkAway": 0, "hkNight": 3, "hkOff": 63, "ignoreStations": [], "ignoreDevices": [], …

Excerpt saved from GitHub on 2026-10-22.

… handshake and that full functionality (arm/disarm, alarm, and station controls) will depend on the upstream work being completed. I’m completely comfortable proceeding with the interim state for now, knowing that this is part of a broader effort in progress. My primary goal is to access the cameras via HomeKit (proxied through Homebridge running on a Raspberry Pi 5), so even partial visibility at this stage is already helpful as things progress. Regarding access, I’m open to setting up a dedicated guest admin account to support your investigation. As recommended by eufy, I understand this …

Excerpt saved from GitHub on 2026-10-22.

Initial support for the T8E00 PoE Bullet-PTZ Cam S4 (type 301) has been submitted upstream (bropat/eufy-security-client#855) along with its companion NVR S4 Max (T8N00, type 300) in bropat/eufy-security-client#854. However, the T8E00 camera currently has only minimal device properties registered, we need device-level raw properties (the `param_type` data specific to the camera, not the NVR station) to map all its capabilities properly. @saroo786 @tjchahal-art, could one of you export diagnostics with Detailed Logging enabled? The diagnostics archive will include the device-level properties …

Excerpt saved from GitHub on 2026-10-22.

Thank you @saroo786 for reporting this. The T8N00 (Type 300) is a Eufy PoE NVR, a completely new device family that is not yet recognized by the underlying `eufy-security-client` library. The device type, station classification, and communication protocols all need to be implemented there first before the plugin can expose it to HomeKit. An upstream feature request already exists: https://github.com/bropat/eufy-security-client/issues/659 This is linked with #861 (T8E00 PoE Camera) which is part of the same NVR system. We'll track progress on the upstream issue and add support in the plugin …

Excerpt saved from GitHub on 2026-10-22.

I have the same unsupported E42. I read your above instruction on this issue. I refreshed and got the below data. (I have two indoor cams, a doorbell cam, and the E42): [code]

Excerpt saved from GitHub on 2026-10-22.

This project is currently frozen. The plugin relies on `eufy-security-client`, which its maintainer has deprecated. Eufy has moved its apps to a new "Mega" protocol, and a brand-new library is being built against it. All development effort is going there. What this means for now: ✅ The current version keeps working as-is for devices still on the old protocol. 🧊 No new features or new device support can be added. 🩹 Only strictly necessary fixes for critical breakages will be considered. 🚀 Effort is focused on the new Mega-protocol library first. Work to adopt it in this plugin has not started …

Excerpt saved from GitHub on 2026-10-22.

{ "uniqueId": "T85F1K1024281FC5", "displayName": "Front DoorLock", "type": 206, "name": "Front DoorLock", "model": "T85F1", "serialNumber": "T85F1K1024281FC5", "hardwareVersion": "V2", "softwareVersion": "1.0.9.0", "stationSerialNumber": "T85F1K1024281FC5" }

Excerpt saved from GitHub on 2026-10-22.

Describe the solution you'd like Add support for Eufy Video Doorbell E340. Currently the logs show this warning indicating the new doorbell model is not supported: [10/14/2023, 19:06:48] [EufySecurity] WARN This accessory is not compatible with HomeBridge Eufy Security plugin: Front Door Type: 94

Excerpt saved from GitHub on 2026-10-22.

… The camera actually shows up under Unsupported Devices (Type 10037) in the plugin interface, rather than not showing up at all. For context, this is the eufyCam C37. Thanks a lot for all your hard work on this plugin! Preflight Checklist [x] I have searched the existing issues and this device has not been requested before. [x] I have checked supported capabilities and understand a recognized device is not automatically represented in HomeKit. Device Information [code] How does the plugin currently show it? Unsupported Device Additional Context _No response_

Excerpt saved from GitHub on 2026-10-22.