v0.8.5

Logging improvements for diagnostics

This release includes all diagnostic changes since 0.8.1. Versions 0.8.2 through
0.8.4 were not published as GitHub releases.

• Include discovery rejection reasons and bounded received model/type pairs in
  normal bridge logs so missing devices can be investigated without debug mode.
• Collect one complete startup report with actual bridge/library/Node versions,
  authentication and inventory results, model/firmware details, anonymous device
  and HomeBase references, migration counts and push startup. Preserve available
  evidence when setup fails and distinguish missing observations from failures.
• Show explicit HomeBase/owner connection states, distinguish connection from
  state-refresh failures and record timestamped connection loss and recovery.
  Suppress unchanged repeated logs.
• Add an authenticated support download containing the complete latest discovery
  and up to 100 recent diagnostic events. Include it in Home Assistant's standard
  diagnostic download with actual HA/integration versions, also for failed setup.
• Bundle the verified eufy-mega-client 0.12.2 release for bounded received firmware
  and parent context on rejected devices. Independently filter shared reports in
  the bridge and HA integration to exclude credentials and device identities.
• Document collection steps, required versions, privacy checks and report field
  meanings. Link the guide from support pages and both issue forms.

Upgrade and recovery

Update the Eufy Viewer integration to 0.8.5 through HACS and restart Home
Assistant. Separately update the bridge app or Docker installation to 0.8.5.
The bridge includes library 0.12.2, which needs no manual installation.

Download diagnostics from the integration's menu after the bridge has completed
one startup discovery. Alternatively, collect the complete Eufy discovery:
and Eufy backend: lines from the bridge's normal Logs tab. Debug is not needed
and bridge logs remain usable with an older integration. Review the file before
sharing it. See the diagnostic collection guide.

Existing Mega installations need no new login or migration because of this
update. Installations older than 0.8.0 must still follow the
Mega migration guide.
Keep a backup of the previous integration, bridge and private bridge data.
For rollback, restore that matching backup through the normal installation or
Supervisor restore path.

Scope and known limitations

Device admission, camera commands and media behavior are unchanged. This release
adds evidence for issue #40,
not a confirmed fix for the reporter's missing C30 or floodlight camera.
The C30 model is already recognized by the library. The reporter's actual
model/type, topology and discovery result are still needed to locate the failure.
No additional hardware or media support is claimed.

The existing Home Assistant Python dependency limitation tracked in
issue #30 remains unresolved.
The affected cryptography dependency and its alert are unchanged. This release
does not fix that vulnerability or claim a clean Python dependency audit.

Source commit: 9066b421ee57ce586b5f5a11ed914beadabfa66c

Validation: Diagnostic-only changes, with no changes to model admission, camera commands or media behavior. On 11 September 2026, bridge/integration 0.8.5 with public library 0.12.2 was checked on Home Assistant 2026.9.1 after backed-up installation and restart. Four cameras, one HomeBase and 15 available entities retained their identities and settings. The actual authenticated HA and bridge diagnostic downloads contained seven discovery rows and five recent events, matching model/firmware and owner connection state. Known private identifiers and credentials were absent and an unauthenticated bridge request returned 401. Installed-code synthetic checks covered failed or empty discovery, rejected-device parent context and connection transitions with debug disabled. No camera actuation or additional media/hardware support was tested or claimed. Runtime files in this release match that checked installation. The reporter's missing C30/floodlight issue remains open pending their report in #40. The previously accepted HA-owned cryptography limitation in #30 remains unresolved, with its alert open and no clean Python audit claimed. Required CI, npm dependency audits and release bundle verification run again on this exact release commit.

Download checksums and exact component versions are included in the release assets.