This fixes an issue where camera streams would stop working after upgrading from v2.4.6 beta to v3.0.3+. Users experienced cameras that would spin indefinitely in the Home app without establishing a stream, with logs showing "Device appears to be inactive. Stopping stream." after approximately 25 seconds.

Root Cause

The issue was in the timeout logic in src/streamingDelegate.ts where the timeout was calculated as request.video.rtcp_interval * 5 * 1000. This resulted in very aggressive timeouts (typically 5-25 seconds) that would trigger when RTCP communication had issues, particularly:

• High bitrate streams that some Apple devices/home hubs couldn't handle properly
• Network congestion or packet loss affecting RTCP messages
• HomeKit attempting to reconfigure streams to lower bitrates (which were ignored)

Solution

1. Implemented conservative timeout bounds: Added minimum timeout of 30 seconds and maximum of 5 minutes to prevent premature stream termination while still catching truly inactive devices
2. Fixed initial timeout handling: Added proper initial timeout when streams start, since RTCP messages might be delayed
3. Added debug logging: Added logging to help troubleshoot timeout issues when debug mode is enabled

The timeout calculation now uses:

const timeout = Math.max(30000, Math.min(baseTimeout, 300000))

This ensures streams have sufficient time to establish proper RTCP communication without being prematurely terminated, while still maintaining reasonable timeouts for genuinely inactive devices.

Testing

• All existing tests pass
• Added comprehensive unit tests for timeout calculation logic
• Verified builds and linting pass

Fixes #772.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.