Security & safety
Eufy Security
fuatakgun/eufy_security · vv8.2.5
HACSCloud push
Home Assistant integration to manage Eufy Security devices as cameras, home base stations, doorbells, motion and contact sensors.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
lock | Lock | Needs its own HomeKit Bridge in accessory mode |
camera | Camera | Needs its own HomeKit Bridge in accessory mode |
alarm_control_panel | Security system | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
button | Button (as a switch) | |
select | Mode picker (as switches) | |
device_tracker | Presence (as an occupancy sensor) |
2 reports below say how a device from this integration behaves in the Home app.
What people report
Works through the bropat eufy-security-ws add-on over Eufy's cloud; streaming is flaky and many 2026 reports say events stopped after cloud session invalidation. Several newer models are unsupported upstream.
- Works3
- Partly works3
- Not working5
- Requested3
- Won’t be supported1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Eufy HomeBase 3 and Cam 3 Pro | Works | Added to device list after integration crashedSaved copyThe new devices cause the integration to crash with this message: "Exception - process_messages: 18 is not a valid DEVICE_TYPE" This will add support for those devices. Excerpt saved from GitHub on 2026-10-23. | PR #471 · 2022-09 | |
| Eufy security cameras (C22, P24) | Works Local | Work great with HA and Frigate, no hub needed; network-blocked after pairingSaved copyI have a lot of eufy cams, C22, P24 and others. They work great with HA and Frigate, no local hub needed. initial online pairing in the app, network level blocking afterwards so no package leaves the LAN. Happy with all they do. Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23. | Reddit comment · 2024-01 | |
| Eufy Solocam | Works | Solocams work without Homebase; add-on exposes many sensors and controlsSaved copyThat's your mistake there. Eufycam 2C Pro requires Homebase, as stated on their website. https://support.eufy.com/s/article/Does-eufy-cameras-have-to-be-used-with-HomeBase The Eufy solocams can be used without Homebase. https://support.eufy.com/s/article/Does-eufy-SoloCam-need-to-be-connected-to-eufy-HomeBase-to-work Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23. | Reddit comment · 2024-01 | |
| Eufy HomeBase 2 alarm panel | Partly works Cloud | Broken in Home Night alarm mode stays on 'Arming...' in Home app | Night mode shows as Custom 2 alarm; Home app stuck on ArmingSaved copyIn #145 alarm_night was mapped to Custom 2 in Eufy. However, Eufy and Home Assistant both "natively" support Night mode so the current mapping is unintuitive and requires creating a Custom alarm mode when Night would work better. Home Assistant, especially using Mushroom cards will not display "Night" correctly with the current Custom mapping. Neither will Eufy display "Night". Please reconsider mapping "alarm_night" natively to Night in Eufy. If the Custom 2 mapping is required for Home Kit for some weird reason, consider adding an option "map night to Custom 2" in the configuration instead. Excerpt saved from GitHub on 2026-10-23. | Issue #1150 · 2024-05 |
| Eufy Smart Lock with Wi-Fi Bridge and Doorbell Chime T8530 | Partly works Cloud | Camera stream unreliable; works via eufyp2pstream add-onSaved copyDevice Details: - Camera Model: Eufy Smart Lock with Wi-Fi Bridge and Doorbell Chime - T8530 - Live Streaming Protocol (RTSP/P2P): P2P ### Home Assistant Details: - Virtual Machine on Synology NAS - Home Assistant Installation Type (OS - Supvervised - Core): Home Assistant OS - Home Assistant Core Version: core-2024.12.5 - Eufy Security Add-on Version: 1.9.1 - Eufy Security Integration Version: 8.1.1 - Using go2rtc Add-on or webrtc custom integration with integrated go2rtc: webrtc custom integration with integrated go2rtc ### Steps followed (same numbers as your installation guide): 1. … Excerpt saved from GitHub on 2026-10-23. | Issue #1277 · 2024-12 | |
| Eufycam 2C Pro | Partly works | Requires Homebase hub; setup described as torture by original posterSaved copyThat's your mistake there. Eufycam 2C Pro requires Homebase, as stated on their website. https://support.eufy.com/s/article/Does-eufy-cameras-have-to-be-used-with-HomeBase The Eufy solocams can be used without Homebase. https://support.eufy.com/s/article/Does-eufy-SoloCam-need-to-be-connected-to-eufy-HomeBase-to-work Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23. | Reddit thread · 2024-01 | |
| Eufy 2K Doorbell Camera | Not working | Broken in Home Stream fails to load in Home app; snapshot only | Custom eufy_security integration RTSP issueSaved copyThe problem I am having trouble getting my Eufy 2k Doorbell to stream within the Home app on my phone. I am using the eufy_security integration which creates an RSTP stream for my camera. This works flawlessly in my home assistant dashboard, but the stream fails to load within the Home app. ### What version of Home Assistant Core has the issue? 2023.1.7 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Homekit ### Link to integration documentation on our website … Excerpt saved from GitHub on 2026-10-23. | Issue #87228 · 2023-02 |
| Eufy E340 doorbell | Not working Cloud | Stream never leaves PREPARINGSaved copyProblem I have a Eufy T8N00 / NVR S4 Max system. All devices are discovered in Home Assistant, but livestreams do not work. When I press Start P2P Stream, the stream status changes from: `IDLE` to: `PREPARING` but it never reaches: `STREAMING`, `READY`, or `CONNECTED`. A stream URL is generated, for example: `rtsp://127.0.0.1:8554/T8E005...104C` but no live video appears in Home Assistant. This happens for both: * S4 cameras connected to the NVR * Eufy E340 doorbells connected/recorded through the NVR system ## Hardware ### NVR * Model: T8N00 / NVR S4 Max * Serial begins with: T8N005... * … Excerpt saved from GitHub on 2026-10-23. | Issue #1477 · 2026-06 | |
| Eufy T8222 battery doorbell with T8020 chime | Not working Cloud | Doorbell events stopped updating with shared accountSaved copySame here, +1. Setup: Eufy T8222-Z battery doorbell on T8020 chime station, integration 8.2.4, `bropat/eufy-security-ws:latest` (server 2.1.0, driver 3.8.0) on a secondary Eufy account that the doorbell is shared to. Last working `binary_sensor.doorbell_ringing` trigger was 2026-05-14 13:54 UTC. Identical HA error log signature: ``` File "/config/custom_components/eufy_security/eufy_security_api/web_socket_client.py", line 81, in _on_close File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 329, in _on_close File … Excerpt saved from GitHub on 2026-10-23. | Issue #1467 · 2026-05 | |
| Eufy T8N00 NVR S4 Max | Not working Cloud | Devices discovered but P2P streams stay in PREPARINGSaved copyProblem I have a Eufy T8N00 / NVR S4 Max system. All devices are discovered in Home Assistant, but livestreams do not work. When I press Start P2P Stream, the stream status changes from: `IDLE` to: `PREPARING` but it never reaches: `STREAMING`, `READY`, or `CONNECTED`. A stream URL is generated, for example: `rtsp://127.0.0.1:8554/T8E005...104C` but no live video appears in Home Assistant. This happens for both: * S4 cameras connected to the NVR * Eufy E340 doorbells connected/recorded through the NVR system ## Hardware ### NVR * Model: T8N00 / NVR S4 Max * Serial begins with: T8N005... * … Excerpt saved from GitHub on 2026-10-23. | Issue #1477 · 2026-06 | |
| Eufy Video Doorbell C31 (T8144P) | Not working Cloud | Motion events stopped after cloud session invalidationSaved copySame here, +1. Setup: Eufy T8222-Z battery doorbell on T8020 chime station, integration 8.2.4, `bropat/eufy-security-ws:latest` (server 2.1.0, driver 3.8.0) on a secondary Eufy account that the doorbell is shared to. Last working `binary_sensor.doorbell_ringing` trigger was 2026-05-14 13:54 UTC. Identical HA error log signature: ``` File "/config/custom_components/eufy_security/eufy_security_api/web_socket_client.py", line 81, in _on_close File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 329, in _on_close File … Excerpt saved from GitHub on 2026-10-23. | Issue #1467 · 2026-05 | |
| Eufy C220 lock | Requested | Lock/unlock support requested; owner says ask bropatSaved copyAs per the title, @fuatakgun , can you add support for this lock? Excerpt saved from GitHub on 2026-10-23. | Discussion #1018 · 2023-11 | |
| Eufy T85 smart locks (C30, E31, S3 Max) | Requested | Lock support proposed in open pull requestSaved copyAdd automatic detection of T85* devices as locks - Ensure T85* devices have required lock properties and metadata - Support for C30 (T85D0C), E31 (T85F0), S3 max (T85V0) smart locks - Maintains backward compatibility with existing devices - T85* devices now provide standard lock/unlock functionality Excerpt saved from GitHub on 2026-10-23. | PR #1369 · 2025-08 | |
| Eufy Wall Light Cam | Requested | Light entity proposed in open pull requestSaved copySummary - expose Eufy's writable `light` property as a native Home Assistant on/off `LightEntity` - load the new light platform so Wall Light Cam lights participate in light services, areas, groups, and dashboards - retain the existing `switch.*` entity as a hidden-by-default compatibility entity so existing automations keep working - keep `lightSettingsEnable`, which controls Eufy's automatic lighting behavior, as a separate configuration switch ## Root cause The integration currently maps every readable and writable boolean property to the switch platform. This classifies the Wall Light … Excerpt saved from GitHub on 2026-10-23. | PR #1501 · 2026-08 | |
| Eufy Indoor Cam C210 | Won’t be supported | Not supported by upstream eufy-security-clientSaved copyPlease check existing (open or closed) issues before creating a new one. (https://github.com/fuatakgun/eufy_security/issues?q=is%3Aissue+) If this is not an issue, you can use `Discussions` (https://github.com/fuatakgun/eufy_security/discussions) section. If you are asking for device support, please check `Supported Devices List in eufy-security-client` (https://bropat.github.io/eufy-security-client/#/supported_devices) first. Your device should be listed there with specific device model number, not device name. You can have similar model names but the support is handled by device model … Excerpt saved from GitHub on 2026-10-23. | Issue #1270 · 2024-12 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Cloud push
Goes through the maker’s cloud, which sends updates as they happen. Needs the internet and an account.
Details
| Installs (analytics) | 9,759 (1.38%) |
|---|---|
| GitHub stars | 1,405 |
| Latest version | v8.2.5 (2026-09-23) |
| Set up in the UI | Yes |
| Maintainers | @fuatakgun |
| License | MIT |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
Sources
- Documentation: https://github.com/fuatakgun/eufy_security
- Source code: https://github.com/fuatakgun/eufy_security
- Issues: https://github.com/fuatakgun/eufy_security/issues
- HACS: https://hacs.xyz
