Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Live streaming bugs with v8

See original GitHub issue

Live Streaming Issue

Describe the live streaming issue

Have two different bugs, but all surrounding live streaming. Something broke in homebridge-ring v8 for me as far as live streaming goes.

Snapshots work fine. But, if I try to live stream, I see the circle “loader” spinning in the video. Is this expected? I’m not sure it’s working at all. It was working fine on an earlier version of homebridge-ring (7.X). The logs indicate it should be working just fine, but I don’t see any streaming happening. If it is expected, then it’s a bit confusing behavior, though not sure if it can be turned off.
If I live stream, and then force quit the home app while viewing the live stream itself, homebridge-ring has a very difficult time recovering. Basically prevents viewing of the live stream at all, even after reopening the home app. There is an overlay on the video that says “No Response. Wait until someone else in this home stops viewing this camera and try again”.

This is akin to #157 that I reported earlier, but seems now it’s no longer recoverable. Seems I have to restart homebridge to fix it now.

Screenshots/Logs

For issue 1, above:

[5/18/2020, 6:38:08 AM] [Ring] Snapshot for Front Door is still within its life time (19.475s old)
[5/18/2020, 6:38:10 AM] [Ring] Preparing Live Stream for Front Door
[5/18/2020, 6:38:12 AM] [Ring] Waiting for stream data from Front Door (1.682s)
[5/18/2020, 6:38:12 AM] [Ring] Received stream data from Front Door (2.128s)
[5/18/2020, 6:38:14 AM] [Ring] Streaming active for Front Door
[5/18/2020, 6:38:28 AM] [Ring] Stopped Live Stream for Front Door

For issue 2, above:

1|homebridge  | [5/18/2020, 6:40:30 AM] [Ring] Preparing Live Stream for Garage
1|homebridge  | [5/18/2020, 6:40:31 AM] [Ring] sip INVITE request failed with status 401
1|homebridge  | [5/18/2020, 6:40:31 AM] [Ring] Failed to prepare stream for Garage (0.487s)
1|homebridge  | [5/18/2020, 6:40:31 AM] [Ring] Error: sip INVITE request failed with status 401
1|homebridge  |     at sipClient.send (/usr/lib/node_modules/homebridge-ring/lib/api/sip-call.js:117:28)
1|homebridge  |     at searching (/usr/lib/node_modules/homebridge-ring/node_modules/sip/sip.js:1316:5)
1|homebridge  |     at /usr/lib/node_modules/homebridge-ring/node_modules/sip/sip.js:1297:41
1|homebridge  |     at Object.message (/usr/lib/node_modules/homebridge-ring/node_modules/sip/sip.js:1103:7)
1|homebridge  |     at Object.signal (/usr/lib/node_modules/homebridge-ring/node_modules/sip/sip.js:982:55)
1|homebridge  |     at /usr/lib/node_modules/homebridge-ring/node_modules/sip/sip.js:1344:24
1|homebridge  |     at onMessage (/usr/lib/node_modules/homebridge-ring/node_modules/sip/sip.js:558:9)
1|homebridge  |     at content (/usr/lib/node_modules/homebridge-ring/node_modules/sip/sip.js:493:7)
1|homebridge  |     at headers (/usr/lib/node_modules/homebridge-ring/node_modules/sip/sip.js:480:9)
1|homebridge  |     at TLSSocket.<anonymous> (/usr/lib/node_modules/homebridge-ring/node_modules/sip/sip.js:504:27)
1|homebridge  |     at TLSSocket.emit (events.js:198:13)
1|homebridge  |     at addChunk (_stream_readable.js:288:12)
1|homebridge  |     at readableAddChunk (_stream_readable.js:265:13)
1|homebridge  |     at TLSSocket.Readable.push (_stream_readable.js:224:10)
1|homebridge  |     at TLSWrap.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

Environment

Ring Camera: [e.g. Stickup Cam Battery]
OS: Raspbian GNU/Linux 10 (buster)
Node.js: v10.20.1
NPM: v6.14.5
homebridge-ring v8.2.0 (but, was working fine before the 8.X upgrade)
homebridge v1.1.0

Network Environment

Everything is on the same mesh Wifi network. I can provide more details here if it would be helpful, but it doesn’t seem like this is an issue given that 1) it was working fine before in v7.X (last release before v8), and 2) snapshots, etc. are being pulled just fine.