[keesmod]

Checklist

• I've read the publishing documentation.
• I've added the HACS action to my repository.
• (For integrations only) I've added the hassfest action to my repository.
• The actions are passing without any disabled checks in my repository.
• I've added a link to the action run on my repository below in the links section.
• I've created a new release of the repository after the validation actions were run successfully.

Links

Link to current release: https://github.com/keesmod/ha-eufy-cam/releases/tag/v0.3.0
Link to successful HACS action (without the ignore key): https://github.com/keesmod/ha-eufy-cam/actions/runs/34037418795/job/101497918601
Link to successful hassfest action (if integration): https://github.com/keesmod/ha-eufy-cam/actions/runs/34037418795/job/101497918473

Integration

Eufy Security Viewer lets users browse and play existing HomeBase recordings in Home Assistant, with bundled Events and camera cards, idle snapshots and on-demand WebRTC video/listen-only audio. Requires Home Assistant 2026.9.0 or newer and a separately installed companion bridge (HA App Store or Docker), documented in the README.

The integration domain is eufy_viewer; brand/icon.png and brand/icon@2x.png are included in the component. It is an independent custom integration and does not override a core integration. Hardware recording validation covers HomeBase 3 T8030 firmware 3.8.6.0; wider device compatibility is not claimed.

The linked validation run succeeded on release commit a252283b5c79c2f8b4f531309ead0296e9fdd3aa at 13:53:49 UTC on 6 September 2026. Release v0.3.0 was published afterwards at 13:54:33 UTC.

[hacs-bot]

Thank you for submitting your repository to HACS (Home Assistant Community Store).

Your submission is in the review queue:
Your repository is waiting to be reviewed and included in HACS.

You can view the current queue here. Pull requests are processed in the order they were created, oldest first.

What to avoid during review:
To help reviewers work efficiently, don't do the following:

• Comment on the pull request - The reviewer will contact you when they have feedback or questions.
• Open a new pull request - This won't speed up the process and creates duplicate work.
• Ask followers to comment on the pull request - This won't speed up the process and may delay your review.
• Merge in the default branch - Only do this if a maintainer asks you to resolve a merge conflict.

If you need to make changes:
You can continue updating your repository while waiting for review. Changes to your repository will be reflected when the reviewer examines it. Only comment on the pull request if you need to withdraw your submission or have critical information for reviewers.

About draft pull requests:
Draft pull requests aren't included in the review queue. Your pull request may be marked as draft by a reviewer if issues need to be addressed. Once you've resolved all issues, mark it as ready for review to re-enter the queue.

What happens next:
Once a reviewer examines your submission, they'll either:

• Approve and merge your pull request if everything meets the requirements
• Request changes or ask questions if adjustments are needed

[frenck]

Hi @keesmod, thanks for the submission! 👋

One thing for a future release: webrtc.py (line 60) and late_audio.py use hass.data["go2rtc"], which is a private key of the core go2rtc integration, and its authenticated session to manage your streams. That is not a public API, so a core refactor can change it without notice and your WebRTC path silently drops to JPEG. If you can, move to a public route, for example letting the camera entity hand its stream to core's WebRTC handling.

Approving and merging now.

../Frenck

                       

Blogging my personal ramblings at frenck.dev
Or subscribe to my free bi-weekly newsletter: frenck.dev/newsletter

[hacs-bot]

Congratulations! Your repository has been added to HACS 🎉

Your repository has been approved:
Your repository has been successfully merged into the HACS default repository list.
It might take up to 8 hours before your repository appears in HACS for users.

Resources:

• HACS Discord
• Home Assistant Developer Blog

Thank you for contributing to the Home Assistant community! 🎉