Selected RTP Stream Configuration: 1st Gen Indoor Cameras

[mfischler]

Is there an existing issue for this?

• I have searched the existing issues

Describe The Bug

When attempting to create a RDP stream from a 1st Gen Indoor Camera, the following error message occurs:

[homebridge-ring] This plugin slows down Homebridge. The write handler for the characteristic 'Selected RTP Stream Configuration' on the accessory '[REDACTED]' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.

Other camera models stream video correctly. All cameras that are 1st Gen Indoor cameras fail.

To Reproduce

Open a live feed from a selected camera.

Expected behavior

Camera feed is captured and displayed.

Relevant log output

[homebridge-ring] This plugin slows down Homebridge. The write handler for the characteristic 'Selected RTP Stream Configuration' on the accessory '[REDACTED]' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.

Screenshots

No response

Homebridge Ring Config

{
    "refreshToken": "[REDACTED]",
    "unbridgeCameras": true,
    "hideAlarmSirenSwitch": true,
    "showPanicButtons": false,
    "cameraStatusPollingSeconds": 10,
    "platform": "Ring"
}

Additional context

No response

OS

Raspian

Node.js Version

v24.18.0

NPM Version

v11.16.0

Homebridge/HOOBs Version

v2.2.1

Homebridge Ring Plugin Version

v14.3.0

Operating System

Raspian 6.12.34+rpt-rpi-v8 arm64

[tsightler]

In the end, this message means the camera didn't respond in a timely manner. Unlike when you stream in the app using native WebRTC, HomeKit is much more sensitive to startup delay. In general, if the stream can't start within as few seconds, it will fail and trigger this message. in Homebridge, there's not a lot we can do about it.

I think it's unlikely to be related to the model, but I guess not impossible, you might try enabled debug on the plugin and seeing if there's more data. Quite honestly, without plugin logs, there's really nothing to go on which is why log output is requested when opening an issue.

[mfischler]

Additional Debug Logs.

[24/07/2026, 22:29:07] [homebridge-ring] This plugin slows down Homebridge. The write handler for the characteristic 'Selected RTP Stream Configuration' on the accessory ‘[REDACTED] didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.
[24/07/2026, 22:29:07] [Ring] Stopped Live Stream for [REDACTED]
[24/07/2026, 22:29:07] [Ring] connectionStateChange: closed
[24/07/2026, 22:29:07] [Ring] iceConnectionStateChange: closed
[24/07/2026, 22:29:07] [Ring] Call ended before answered
[24/07/2026, 22:29:07] [Ring] Streaming active for [REDACTED] (9.115s)
[24/07/2026, 22:29:09] [Ring] Used cached snapshot for [REDACTED]
[24/07/2026, 22:29:09] [Ring] Loading new snapshot into cache for [REDACTED]
[24/07/2026, 22:29:10] [Ring] Snapshot cached for [REDACTED] (0.577s)
[24/07/2026, 22:29:17] [Ring] Return Audio ([REDACTED]): stopped gracefully
[24/07/2026, 22:29:17] [Ring] Return Audio ([REDACTED]): Input #0, sdp, from 'pipe:':
Metadata:
title : Talk
Duration: N/A, bitrate: N/A
Stream #0:0: Audio: opus (libopus), 48000 Hz, mono, s16
Stream mapping:
Stream #0:0 -> #0:0 (opus (libopus) -> opus (libopus))

[24/07/2026, 22:29:17] [Ring] Return Audio ([REDACTED]): [in#0/sdp @ 0x7fb01f6430] Error during demuxing: Operation timed out

[24/07/2026, 22:29:17] [Ring] Return Audio ([REDACTED]): [af#0:0 @ 0x7fb01b2a40] No filtered frames for output stream, trying to initialize anyway.

[24/07/2026, 22:29:17] [Ring] Return Audio ([REDACTED]): Output #0, rtp, to 'rtp://127.0.0.1:38662':
Metadata:
title : Talk
encoder :
[24/07/2026, 22:29:17] [Ring] Return Audio ([REDACTED]): Lavf62.3.100

[24/07/2026, 22:29:17] [Ring] Return Audio ([REDACTED]): Stream #0:0: Audio: opus, 48000 Hz, stereo, s16, 48 kb/s
Metadata:
encoder : Lavc62.11.100 libopus

[24/07/2026, 22:29:17] [Ring] Return Audio ([REDACTED]): [out#0/rtp @ 0x7fb01b5d00] video:0KiB audio:0KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: unknown
[out#0/rtp @ 0x7fb01b5d00] Output file is empty, nothing was encoded(check -ss / -t / -frames parameters if used)

[24/07/2026, 22:29:17] [Ring] Return Audio ([REDACTED]): size= 0KiB time=N/A bitrate=N/A speed=N/A elapsed=0:00:10.01

[24/07/2026, 22:29:17] [Ring] Return Audio ([REDACTED]): Exiting normally, received signal 15.

[tsightler]

I would need the full logs, from the start of the stream until the end, this appears to be only after the shutdown as you can see the log entry at 22:29:07 indicates the stream had been alive for 9 seconds at that point, but there's nothing prior to that in the logs provided.

[Sistaveley]

Yep I’ve got the same issue. However it’s not with 1st gen indoor cameras but all the cameras, indoor and outdoor across multiple generations. It started happening probably around a week or two ago as well.

I’m not as tech savvy so if someone can tell me how to get the details logs I am happy to share them.

I’m running a Synology NAS with Homebridge installed and this Ring plugin v14.3.0
Homebridge v2.2.1
Homebridge UI v5.27.0
Node is v22.19.0

Homebridge Logs
handler for the characteristic 'Selected RT
P Stream Configuration' on the accessory 'P
antry 3FD4' didn't respond at all!. Please
check that you properly call the callback!
See https://homebridge.io/w/JtMGR for more
info.
[8/1/2026, 8:25:11 PM] [Ring] Stopped Live
Stream for Pantry
[8/1/2026, 8:25:11 PM] [Ring] connectionSta
teChange: closed
[8/1/2026, 8:25:11 PM] [Ring] iceConnection
StateChange: closed
[8/1/2026, 8:25:11 PM] [Ring] Streaming act
ive for Pantry (9.209s)