How to Connect Eufy Devices to Home Assistant

Eufy Integration Overview

Eufy (owned by Anker) doesn't provide an official HA integration or a public local API. The community-developed solution uses eufy-security-ws, a WebSocket bridge that logs into Eufy's cloud on your behalf and proxies device data to HA.

This is a semi-local integration: eufy-security-ws runs on your hardware (as a HA add-on or Docker container), but it still communicates with Eufy's cloud to get device states. Camera streams are fetched directly from the device (P2P), making video local.

Supported devices include:

• Eufy security cameras (eufyCam 2C, 3C, T8x series)
• Eufy video doorbells (T8210, T8213)
• Eufy sensors (entry sensor T8900, motion T8132)
• Eufy RoboVac robot vacuums (X8, X10, G30, etc.)
• Eufy Smart Lock Touch & Wi-Fi

eufy-security-ws Setup

1. Install HACS in HA (if not already done)
2. In HACS → Integrations → search "Eufy Security" → install the integration by fuatakgun
3. Install the eufy-security-ws add-on or run the Docker image:
   Docker — Run eufy-security-ws

   docker run -d \
     --name eufy-security-ws \
     -p 3000:3000 \
     -e USERNAME="your_eufy_email" \
     -e PASSWORD="your_eufy_password" \
     -e COUNTRY="US" \
     bropat/eufy-security-ws:latest

4. Restart HA
5. Settings → Integrations → Add → Eufy Security
6. Enter the eufy-security-ws host (e.g., localhost or the Docker host IP) and port 3000
7. All Eufy devices associated with your account appear in HA

Vacuum Automation (YAML)

automation:
  - alias: "Start vacuum when everyone leaves"
    description: "Run RoboVac when all phones leave the home zone"
    trigger:
      - platform: state
        entity_id: group.family_phones
        to: "not_home"
        for:
          minutes: 5
    condition:
      - condition: time
        after: "09:00:00"
        before: "17:00:00"
      - condition: state
        entity_id: vacuum.robovac_x8
        state: "docked"
    action:
      - service: vacuum.start
        target:
          entity_id: vacuum.robovac_x8

  - alias: "Vacuum returns to dock when home"
    trigger:
      - platform: state
        entity_id: group.family_phones
        to: "home"
    condition:
      - condition: state
        entity_id: vacuum.robovac_x8
        state: "cleaning"
    action:
      - service: vacuum.return_to_base
        target:
          entity_id: vacuum.robovac_x8

Camera Stream

Eufy cameras stream via P2P directly to your HA instance when using eufy-security-ws. Add a camera card to your dashboard:

type: picture-entity
entity: camera.eufy_front_door
camera_view: live
show_name: true

Note: P2P streaming may take 2–5 seconds to start. This is a limitation of Eufy's P2P protocol, not HA.

Known Limitations

• Not fully local: eufy-security-ws connects to Eufy's cloud for device state. If Eufy's servers go down, the integration breaks.
• Slow to start streams: P2P camera connection takes 2–5 seconds to establish.
• API changes: Eufy has changed their API several times, breaking the integration temporarily. The community usually fixes it within days.
• Limited vacuum room-by-room control: Room-based cleaning commands may not be available for all RoboVac models.
• No official support: Eufy does not support or condone this integration.

Alternatives

If Eufy's limitations bother you, consider these alternatives for local control:

• Robot vacuums: Roborock vacuums work with the official Roborock HA integration and support local control via Valetudo firmware
• Security cameras: Reolink, Amcrest, and Hikvision cameras all work locally via RTSP and have native HA integrations
• Smart locks: Schlage Encode Plus and Yale Assure work with Z-Wave or Matter for full local control

Troubleshooting

• Entities don’t appear in Home Assistant: Confirm the integration is loaded correctly and double-check that the device is supported by the platform you chose.
• Commands feel delayed: This is usually caused by cloud polling, weak Wi-Fi, or a slow Zigbee mesh rather than Home Assistant itself.
• Things work in the vendor app but not in HA: Re-check credentials, local API permissions, and whether the device is using the correct network path.
• Automations misfire: Open the automation trace in Home Assistant and verify the exact entity IDs and state changes being used.

FAQ

SmartWired uses affiliate links. If you buy through our links, we may earn a commission at no extra cost to you. See our Affiliate Disclosure.