No Video Streaming - Some Cams standalone and some connected to homebase

[Snowedin3]

Preflight Checklist

• I have searched the existing issues and this bug has not been reported before.
• I am using a dedicated guest admin account (not my main Eufy account).
• I have restarted Homebridge and the issue persists.

Environment

- **Plugin Version**: 5.0.0-beta.4
- **eufy SDK**: 0.1.0
- **Node.js Version**: v24.21.0
- **Homebridge Version**: 
- **OS**: linux x64
- **Support Case ID**: 
- **Diagnostics profile**: live-media (now)
- **Missing evidence**: none

Area

Livestream / Streaming

Diagnostics File

Attach the homebridge-eufy-.eufysupport.gz file the diagnostics page downloaded.

What happened?

Installed new plugin, Logged in, let it get devices. Restarted home bridge completely, tested streaming, no cameras stream. About 12 of mine are connected to homebase S1 and 2 of mine are stand alone (backyard and deck door) which worked on last plugin but now don't stream. I used to have to mess with the resolution and bitrates to get them to stream in the v4 plugin but looks like those settings are gone. I will add, I'm on IOS 27 release candidate on my AppleTVs and my Phone. This releases to the public on Monday.

[lenoxys]

Reopened — this one was closed by the freeze bot that was still living on the default branch. That workflow is now removed, so v5 reports stay open and get looked at. Sorry for the noise.

Now the part I need from you: the diagnostics file. The report has Diagnostics profile: live-media (now), so the wizard ran, but no homebridge-eufy-<case-id>.eufysupport.gz was attached to the issue.

Without it I can only guess between causes that look identical from the outside, and each one is a different fix:

• sdk-source-acquisition — the station never handed over a stream (P2P/relay never came up).
• first-source-keyframe — the stream opened and the camera delivered audio only, or no keyframe.
• first-adapted-output — FFmpeg refused the negotiated profile/level/bitrate, or is missing an encoder.
• controller-rtcp — media went out and your Apple TV / iPhone never acknowledged it. This is the one I would look at first given iOS 26 RC on both the controller and the hub.

The archive records which of those every session hit, plus the negotiated geometry and the FFmpeg build that ran. That distinction is the whole investigation.

To produce it: plugin settings → pick one of the cameras that will not stream → Run diagnostics → pick the Livestream / Streaming area → start collection → try the live view once or twice from the Home app while it is collecting → stop, and drag the .eufysupport.gz it gives you into a comment here. It is redacted and encrypted: no serials, addresses, tokens or account details, and nothing is uploaded anywhere by the plugin.

Two things that help, if you can:

1. Do it for one homebase camera and one standalone camera, so I can see whether the two paths fail the same way. Separate collections are fine.
2. Turn Homebridge's debug mode on before collecting, so the negotiated selection is in the log rather than inferred.

Also worth answering: which Homebridge version? v5 requires Homebridge 2, and a v1 host will load the plugin and then fail in ways that look exactly like a streaming fault.

On the missing bitrate and resolution knobs: those are gone deliberately. v5 advertises a resolution ladder and lets the controller pick, and the encoder honours the negotiated ceiling instead of a number you had to tune by hand. If it turns out a selection your devices ask for is one the pipeline cannot serve, that is a bug here to fix, not a setting to restore.

[Snowedin3]

attached are 2 log files - one camera (Driveway) that's connected to homebase s1 and one camera (Deck Door) that's standalone no home base. Also attached pic of spiney wheel. 1 out 10 times the non homebase cameras will work but usually just times out.

Homebase Cam Driveway.eufysupport.gz

No Homebase Deck Door.eufysupport.gz