Eufy Home Assistant Push Notifications Not Working? 2026 Fixes
camera troubleshoot 2026-07-27 · 1,740 words

Eufy Home Assistant Push Notifications Not Working? 2026 Fixes

By Quvii Editorial How we research

For many Eufy users, the magic of Home Assistant (HA) lies in the millisecond-fast automations: a porch light snapping on the moment a camera spots a person or a notification appearing on the living room TV. When these push notifications stop working, that magic vanishes, leaving users with a smart home that is effectively “blind” to external events despite the native Eufy app functioning perfectly.

📝 Editorial Note: This guide is AI-assisted and game data evolves rapidly. Please cross-reference with in-game information. Updated: 2026-07-27.

Quick Answer: Most Eufy-HA notification failures in 2026 are caused by expired session tokens or breaking changes in the Eufy Security Add-on following the July 2026 API shift. To fix this, re-authenticate your dedicated HA sub-account, ensure “Push Notifications” are enabled in the Eufy app’s Security Modes, and update the Eufy Security Add-on to the latest patch (v1.8.x or higher) to restore the P2P handshake.

The symptom

The symptom

Related: Fix: Nest Camera Offline in Google Home App (2026 Guide) · Reolink Doorbell Cutting Off? Fix Motion Recording Duration · Gladys Assistant & Tuya Doorbell Integration Issues (2026 Guide)

When push notifications fail between Eufy and Home Assistant, the breakdown is rarely a total system crash. Instead, it manifests as a “silent failure” where the Eufy ecosystem appears healthy, but the bridge to your local automation engine is severed.

Identifying ‘Silent’ Failures

A silent failure occurs when your smartphone receives a notification from the official Eufy Security app, but Home Assistant remains oblivious. In this state, the binary_sensor entities for motion or person detection stay “Clear” or “Idle” indefinitely. Users often report that the “Last Event” attribute in the HA developer tools shows a timestamp from hours or days ago, even though they can see recent events in the Eufy app’s library.

The ‘Entity Unavailable’ vs. ‘No State Change’ distinction

It is critical to distinguish between two different error states:

  • Entity Unavailable: This usually points to a total loss of communication between the Home Assistant Core and the Eufy Security Add-on (WS Server). The integration cannot see the hardware at all.
  • No State Change: The entities are “Online” and “Available,” but they never trigger. This indicates that the P2P (Peer-to-Peer) notification stream is blocked or that Eufy’s cloud has stopped forwarding events to the third-party API.

As of mid-2026, benchmarks show a widening gap in latency between the native app and the integration when the system is misconfigured:

Notification Path2026 Avg. Latency (Local)2026 Avg. Latency (Cloud)Status
Eufy Native App0.8s – 1.5s2.5s – 4.0sStable
HA Integration (P2P)1.2s – 2.0sN/AVariable
HA Integration (Cloud)N/A5.0s – 12.0sDelayed

What’s likely happening

What's likely happening

The integration between Eufy and Home Assistant is not official; it relies on a community-maintained “Websocket” (WS) server that mimics a mobile device to receive push alerts. In 2026, several technical shifts have made this connection more fragile.

The Role of the Eufy Security Add-on

The eufy-security-ws add-on acts as the translator. It maintains a persistent P2P connection with your HomeBase 3 (S380) or SoloCams. When Eufy updates the HomeBase 3 firmware—such as the problematic v3.8.2.8 update released in May 2026—the protocol used for these handshakes can change. If the add-on isn’t updated to match these new protocols, the “handshake” fails, and motion events are never passed to the HA bus.

Why 2FA is a Double-Edged Sword for HA

Eufy’s 2026 security dashboard enforces Two-Factor Authentication (2FA) for all primary accounts. While this protects your footage, it frequently breaks the background login process required by the custom integration. If your session token expires and the integration attempts to log in, it may be blocked by a 2FA prompt that the integration cannot display, leading to an authentication loop and stopped notifications.

The Eufy-to-HA Notification Path:

  1. Event: Camera detects motion.
  2. Eufy Cloud: Event is logged; a push packet is generated.
  3. Add-on: The eufy-security-ws server (acting as a “dummy” phone) catches the packet.
  4. Integration: The HA integration reads the WS server data.
  5. HA Bus: The state of binary_sensor.front_door_motion changes to “on”.

Quick fixes (in order of likelihood)

Quick fixes (in order of likelihood)

Before diving into complex logs, follow this “Restart Hierarchy” to clear common session bottlenecks.

The ‘Restart’ Hierarchy

  1. Restart the Add-on: Navigate to Settings > Add-ons > Eufy Security. Click Stop, wait 10 seconds, and click Start. This forces a fresh P2P handshake with the HomeBase.
  2. Reload the Integration: Go to Settings > Devices & Services, find the Eufy Security card, click the three dots, and select Reload. This refreshes the entities within Home Assistant without stopping the background server.
  3. Re-authenticate: If you see a “Repair” notification in HA, your session has likely expired. You will need to enter a new 2FA code sent to your email or phone to re-establish the cloud link.

Validating Account Permissions

A common culprit in 2026 is a change in the Eufy app’s “Security Mode” settings.

  • Open the Eufy Security App.
  • Go to the Security tab and select your current mode (e.g., “Home”).
  • Tap the Gear icon next to the mode.
  • Ensure that Push Notification is checked for every camera you want to track in Home Assistant. If this is unchecked in the app, Eufy’s servers will not generate the data packet that the HA integration needs to see.

Deeper diagnostics

Deeper diagnostics

If quick fixes fail, you must look at the raw data flowing (or not flowing) through your system.

Analyzing Home Assistant Core Logs

Check your HA logs (Settings > System > Logs) for the following strings:

  • P2P connection failed: Indicates your HomeBase is blocking the local connection. This is often due to a firmware mismatch or an IP change.
  • Authentication error: Your credentials or 2FA token are invalid.
  • Schema Mismatch: This occurs after a Home Assistant Core update (like the February 2026.02 update) where the integration’s data structure no longer matches the Core’s expectations.

Network and Firewall Troubleshooting

In 2026, Eufy devices have become more sensitive to network “noise.” Ensure that:

  • Port 3000 (default for the WS server) is open and not being used by another HA add-on.
  • UDP Ports 1935, 80, and 443 are not being throttled. Some “Smart” router features or AdGuard Home instances may flag the high-frequency P2P pings from the integration as a potential DDoS attack and drop the packets.

Value vs. Alternatives: When to Switch

If you find yourself troubleshooting Eufy notifications more than enjoying them, it may be time to consider the “Local API” route. The integration’s reliance on cloud-polling and unofficial P2P reverse-engineering is inherently unstable.

For users requiring 100% reliability, the Reolink Video Doorbell WiFi (typically in the $100 range) is a strong alternative. Unlike Eufy, Reolink provides an official, locally-hosted API that Home Assistant communicates with directly. Because it doesn’t require a “middleman” cloud server for motion events, notifications are nearly instantaneous and do not break when the manufacturer updates their cloud app.

When to contact support

When to contact support

Because this integration is a third-party community project, Eufy’s official support will not help you fix the Home Assistant connection. However, you should contact them if:

  • HomeBase 3 LED is Solid Red: This indicates a hardware-level network failure or a failed firmware update (v3.x.x series).
  • Native App Notifications are Missing: If the official app isn’t getting alerts, the problem is with the Eufy cloud or the camera hardware itself.

For integration-specific bugs, such as the frozen entity issue #1416, your best resource is the GitHub Issues page for fuatakgun/eufy_security. When posting, always provide your HomeBase model, the Eufy Security Add-on version, and a sanitized log snippet.

How to prevent it

How to prevent it

Stability in 2026 requires moving away from “plug-and-play” and toward a more intentional network configuration.

Dedicated Account Best Practices

Never use your primary Eufy account for Home Assistant. Create a dedicated “Admin” sub-account (e.g., ha-bridge@yourdomain.com) and share your cameras with it. This prevents “Session Kicks,” where logging into the Eufy app on your phone automatically logs the HA integration out, killing your notifications.

Static IP and Local Network Stability

The P2P connection relies on knowing exactly where your HomeBase 3 is on the network.

  1. Assign a Static IP to your HomeBase 3 via your router’s DHCP reservation table.
  2. Assign a Static IP to your Home Assistant hardware.
  3. In the Eufy Security Add-on configuration, use the static IP of the HomeBase rather than relying on “Auto-discovery.”

Integration Watchdog

To ensure you aren’t left vulnerable when a connection drops, set up a “Watchdog” automation in HA. This YAML snippet will notify you if your cameras go offline for more than 30 minutes:

alias: "System: Eufy Offline Watchdog"
trigger:
  - platform: state
    entity_id: binary_sensor.front_door_motion
    to: "unavailable"
    for:
      minutes: 30
action:
  - service: notify.persistent_notification
    data:
      title: "Eufy Integration Failure"
      message: "The Front Door camera has been unavailable for 30 minutes. Please restart the Eufy Security Add-on."

Frequently Asked Questions

Why does the Eufy app work but Home Assistant doesn’t?

The Eufy app uses a proprietary, encrypted stream that Eufy can update at any time. The Home Assistant integration is a community “reverse-engineering” of that stream. When Eufy changes their API or encryption keys (as seen in early 2026), the official app is updated automatically, but the HA integration requires a manual update from the community developers.

Do I need a subscription for Eufy notifications in HA?

No. Eufy provides basic motion and person detection notifications for free. However, the integration requires these notifications to be enabled in the Eufy app. If you disable them to avoid phone clutter, you also cut off the data feed to Home Assistant.

Does the HomeBase 3 work better with Home Assistant than HomeBase 2?

The HomeBase 3 (S380) offers more advanced AI processing, but its P2P protocol is more complex. While it is fully supported by the fuatakgun integration as of 2026, it is also more prone to “handshake” errors following firmware updates compared to the older, simpler HomeBase 2.

Sources