Failed to activate stream #1286
Comments
|
I have the exact same issue. |
|
@DerMuri I am using homebridge-ring v11.8.1
|
|
This is a strange issue as it appears at first glance to be unrelated to any of the recent changes in ring-homebridge/ring-client-api, which is further confirmed by the fact that users are having it with v11.8.1 as well. It looks like some kind of dependency conflict with some downstream package as I'm not sure why the standalone dtls package is installed. Unfortunately, I'm travelling this week and won't have any chance to dig into it until sometime early next week. |
No hurry. Thanks for addressing the issue. Your work is much appreciated. |
|
FYI, I too am having this issue. It began when I updated to version 11.8.1. If it helps here's the log when opening a stream. [11/08/2023, 09:11:27] [Ring] Preparing Live Stream for Front Door |
|
I have similar logs as well |
|
Seeing a lot of reports of this, including some in the Google Nest homebridge plugin. I agree with @tsightler that it's likely a dependency (or sub dependency) that changed, but I don't have any specific ideas on which one at this point. I have not been able to reproduce this myself yet. For those who are experience it, could you provide the following info:
This should hopefully help us narrow down the cause. |
|
Hi thanks for looking into it. Nods.js: v18.17.1 |
|
Thanks for investigating this. Node.js version: 18.17.1 |
Node.js version: 18.17.1 Thanks |
|
Me too. Recently upgraded to latest NodeJS version v18.17.1. |
Node.js version: v18.17.1 The iat (time issued) of the refresh token of the ring plugin was: [13/08/2023, 21:46:45] [Ring] Preparing Live Stream for Garden Tree
[13/08/2023, 21:46:46] [Ring] Stream Prepared for Garden Tree (0.399s)
[13/08/2023, 21:46:46] [Ring] Activating stream for Garden Tree (0.446s)
[13/08/2023, 21:46:47] [Ring] iceConnectionStateChange: completed
[13/08/2023, 21:46:47] [Ring] Failed to activate stream
[13/08/2023, 21:46:47] [Ring] RangeError: offset is out of bounds
at Uint8Array.set (<anonymous>)
at Function.padStart (/usr/local/lib/node_modules/homebridge-ring/node_modules/webcrypto-core/build/webcrypto-core.js:972:13)
at Function.encodeSignature (/usr/local/lib/node_modules/homebridge-ring/node_modules/webcrypto-core/build/webcrypto-core.js:940:22)
at Function.sign (/usr/local/lib/node_modules/homebridge-ring/node_modules/@peculiar/webcrypto/build/webcrypto.js:1575:54)
at EcdsaProvider.onSign (/usr/local/lib/node_modules/homebridge-ring/node_modules/@peculiar/webcrypto/build/webcrypto.js:1737:25)
at EcdsaProvider.sign (/usr/local/lib/node_modules/homebridge-ring/node_modules/webcrypto-core/build/webcrypto-core.js:157:28)
at SubtleCrypto.sign (/usr/local/lib/node_modules/homebridge-ring/node_modules/webcrypto-core/build/webcrypto-core.js:1405:39)
at Function.create (/usr/local/lib/node_modules/homebridge-ring/node_modules/@peculiar/x509/build/x509.cjs.js:2407:35)
at Function.value [as createSelfSignedCertificateWithKey] (/usr/local/lib/node_modules/homebridge-ring/node_modules/dtls/src/context/cipher.ts:108:18)
at RTCDtlsTransport.setupCertificate (/usr/local/lib/node_modules/homebridge-ring/node_modules/werift/src/transport/dtls.ts:76:9)
at ensureCert (/usr/local/lib/node_modules/homebridge-ring/node_modules/werift/src/peerConnection.ts:1293:34)
at RTCPeerConnection.ensureCerts (/usr/local/lib/node_modules/homebridge-ring/node_modules/werift/src/peerConnection.ts:1301:7)
at RTCPeerConnection.createAnswer (/usr/local/lib/node_modules/homebridge-ring/node_modules/werift/src/peerConnection.ts:1306:5)
at WeriftPeerConnection.createAnswer (/usr/local/lib/node_modules/homebridge-ring/node_modules/ring-client-api/lib/streaming/peer-connection.js:121:24)
at WebrtcConnection.handleMessage (/usr/local/lib/node_modules/homebridge-ring/node_modules/ring-client-api/lib/streaming/webrtc-connection.js:29:32)
[13/08/2023, 21:46:47] [Ring] connectionStateChange: closed
[13/08/2023, 21:46:47] [Ring] iceConnectionStateChange: closedHope this helps! |
|
Let us know if you need assistance in testing: Shoutout to @tsightler and @dgreif ❤️ edit: I installed the beta12 version and now all snapshots are working on ring cameras - it loads longer for the livestream, but remains with the same error in a failed state - however the behavior seems to be improving |
|
Another thing that might be interesting, what other plugins are installed (if any) and what is the iOS version in use. |
|
|
Running Homebridge on Rpi4
TVOS 17 and IOS 17 MacOS Ventura
Same issue on all above versions. Developer as well public beta.
Attached plugin used.
…On Mon, 14 Aug 2023 at 7:50 PM, DerMuri ***@***.***> wrote:
- Homebridge is running on *macOS Monterey*
- The other plugins are: *Homebridge Hue, Homebridge Xiaomi Fan*
- The issue appears regardless where I try to open the stream. I am on
Sonoma beta, iOS 17
Beta, tvOS 17 beta. I haven't tested it on a non-beta OS, yet.
—
Reply to this email directly, view it on GitHub
<#1286 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQFLWWHLZ2XQAKZ5RC6KZ5DXVIXZZANCNFSM6AAAAAA3JONFD4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
|
Thanks everyone that has provided npm output. I have hidden them for now to make the thread more readable but they were extremely useful. Going through the details the only difference I could find between my working setup and the non-working ones was the version of pvtsutils. My working setup was using 1.3.2 while the broken ones above have 1.3.3, and sure enough, updating my version to 1.3.3 reproduces the issue. Also, v1.3.3 was updated 8 days ago and a very similar issue with the padStart function has already been reported on the pvtsutils project page: PeculiarVentures/pvtsutils#12 Manually reverting the package back to pvtsutils v1.3.2 solves the issue which is the workaround for now. |
|
Thank you for the thorough investigation work @tsightler! I just released |
|
@dgreif appreciate the effort and release! - I tried and it didn't update it within Unfortunately the |
|
One of the most confusing things for me is that I just did my Homebridge install fresh last night and I only received pvtsutils 1.3.2, even though 1.3.3 was available. I had to manually update to 1.3.3 to get it. |
|
Thanks for the quick response @cebrakadabra. Give For context, it looks like there is an npm bug where it doesn't respect the |
|
@tsightler npm can be weird that way. It has a local cache that it checks first, so if you had previously installed 1.3.2, it would see that and say "this version satisfies my needs" and just use that. I'm guessing that's what happened |
Thank you! ❤️ |
It works! Thanks so much! |
|
Thanks everyone for contributing and working on this. I can confirm upgrading to 12.0 beta 2 installed pvtsutils 1.3.2 & resolved the problem. |
|
Thank you all SO much for your amazing help with this! I can also confirm that |
|
Hi Everyone. Can someone give guidance on how to manually upgrade? |
|
Thank you so much beta 2 works and resolved live streaming issue.
Sent from Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: reesek ***@***.***>
Sent: Tuesday, August 15, 2023 11:09 PM
To: dgreif/ring ***@***.***>
Cc: shaileshck ***@***.***>; Comment ***@***.***>
Subject: Re: [dgreif/ring] Failed to activate stream (Issue #1286)
Thank you all SO much for your amazing help with this! I can also confirm that v12.0.0-beta.2 resolved the issues with live streaming!
—
Reply to this email directly, view it on GitHub<#1286 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQFLWWCSVPXZLKNTLL4UG7DXVOX4LANCNFSM6AAAAAA3JONFD4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Any idea of when it will move out of beta and become available through the Homebridge interface? Thanks very much |
|
Thx, working again |
The beta should be installable via the Homebridge UI even now, that's how I did it. Just select install alternate version and select the v12.0.0-beta.2 version from the drop down list. |
|
Perfect, thank you…. works great |
Thank you!!!!!! |
|
Looks like all positive feedback flowing in, so I'm going to go ahead and close + lock this issue. I'll probably cut an official release in the next week or so. |
Streaming Issue
I can receive snapshot and notifications just fine but I am unable to get a livestream to work through the home app. It works fine on the ring app. I am fairly new to home bridge and I am not sure if I missed something while setting it up. Any help would be appreciated. Thank you.
Proposed Solution
The specific cause of the error could be related to incorrect data handling, data offsets, or indices during the cryptographic operations. However, I am unsure and am requesting help.
Environment
Homebridge
What operating system are you on?
Mac
Relevant log output
Honesty Time
The text was updated successfully, but these errors were encountered: