-
-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CAMERAS GETTING "No Response" NEARLY EVERY TIME. #930
Comments
I am having the same issue. |
The new streaming setup is using WebRTC instead of SIP, and may run into new issues that you were not facing before. If it is unable to connect, it's likely due to network complications between your homebridge server and the Ring servers (or local camera if you are using Ring Edge). Do you have a complicated network setup? Is it possible your network is blocking these new connections? |
I do have a kind of complicated network. how can I check if it is getting blocked? should I open some port or something? |
WebRTC uses random ports, so it will be completely dependent on your network. One easy thing to try is to see if the Ring App (ios/android) can access the live stream from the same point on the network as your homebridge server |
yeah, the Ring app works with no problem from my laptop and from my phone without issues. just homebridge is having issues. and it used to work without any issues. |
I am not sure if this helps but, when I start the stream from the Home app it is loading for a bit and then gives up but it did update the thumbnail in the app. |
K, I don't have any immediate solutions other than downgrading to v9 for now. This is likely something in |
Thanks, @dgreif downgrading to homebridge-ring v9.24.0 fixed the issue for me. |
All the exact same issues as bkarakashev reported under v11.0.0. Reverted to homebridge-ring v9.24.0 and all cameras working again. ... When two steps back is a giant leap forward. |
This method can make the HomeAPP stream, but after 15 seconds there is no response.... |
Facing same issues, unable to get homebridge video but ring app works just fine. |
In my environment, WebSocket disconnects a short time (8~40 seconds) after the WebRTC connection is established. https://github.com/dgreif/ring/blob/master/api/streaming/streaming-connection-base.ts#L65 And then the WebRTC connection is also disconnected https://github.com/dgreif/ring/blob/master/api/streaming/streaming-connection-base.ts#L136 |
@shinyoshiaki I didn't realize you used the ring client, that's wonderful news 😁 . I'm hoping that some of the PRs from @koush will fix these issues but I can't say for certain. Any chance you can publish a release of werift soon to get those changes out? I don't have much free time right now, so any debugging help you can provide would be very much appreciated! As far as the WebSocket disconnecting, I haven't run into that issue at all yet. Ultimately I plan to handle disconnects by starting a new stream and keeping the single ffmpeg instance going, but I haven't gotten around to implementing that piece yet. Theoretically we can keep streaming past the 10 minute max with that approach 😄. |
I don't think koush's PR has much to do with this case. From the second picture in the bug report, it looks like the connection is destroyed by homebridge's StopStreamRequest 8 seconds after the successful connection of ice. DTLS negotiation after the Ice connection may have failed. This is the first time that werift has been used for anything other than experimental purposes, so it is not surprising that negotiation issues arising from this kind of network environment may arise. May need to increase the amount of logs first to determine the cause. |
I'm using werift quite extensively in Scrypted. It recently replaced node-webrtc (which is a node binding of chromium libwebrtc) completely within the project. It provides a webrtc gateway, in for both video sources and video sinks. The current webrtc sources are webcams, google gen 2 cameras, and ring. The current webrtc sinks are chromecast, nest hubs, Alexa hub, and all manner of browsers. Everything works great, I have not had any issues and users haven't reported anything like this. Additionally, werift has replaced the srtp sender throughout the project (homekit/rtsp, where it was previously using ffmpeg). Incidentally you may want to take a look at the h264 repacketizer, was considering submitting that to werift proper. https://github.com/koush/scrypted/blob/main/plugins/homekit/src/types/camera/h264-packetizer.ts As a data point: on my fork of ring-client-api, haven't had any issues with webrtc. But SIP is still the default for my users. The adventurous users on WebRTC have not seen any issues. The recommended network environment for docker is host networking. This may be a potential reason. My other guess is that the code I added to determine connection state when there are multiple ice transports (in the non bundle case) is possibly buggy. |
@shinyoshiaki, thanks for the quick release of werift! Totally understand that it's experimental at this point, but even as an experiment it's a great leap forward from the SIP code I had before. I've updated to the latest |
Just confirmed with @donavanbecker that one of his cameras is still failing to connect after the update. @shinyoshiaki is this something you would be willing to dig into further? If so, I think the easiest thing would be to chat via the Homebridge discord server, and I can set up a private channel between you, me and @donavanbecker to talk further. |
11.0.1 did not resolve the issue for me |
I don't have much time during the week, maybe I can do it on the weekend. (and I can't speak english. so I can only text chat.) |
That's fine. Just let us know once you get on to discord and we can get a private chat setup with @dgreif and myself |
Huge thank you to @shinyoshiaki for going way out of your way to help us debug this! Looks like Ring sometimes requires PCMU instead of OPUS. @MoTechnicalities @donavanbecker I've released Note, I've only implemented the incoming audio fixes. 2-way audio will not currently work for the cameras that use PCMU. If this fix looks good, I'll figure out that piece next. |
I can confirm that |
Same for me. |
@dgreif Still hoping to get that fake motion sensor removed from Ring bulbs some day too. That issue was closed without a fix. |
Return audio should be fixed in |
Re: 11.0.2-beta.1 |
I have a similar or even the same issue on all versions >9.24.0 (including the new beta). For me the following error appears. With version 9.24.0 everything works fine.
|
Anyone still having issues, you are likely not on v16 of node (instructions for updating). Locking this thread to prevent more chatter, please open a new issue with full details if you are experiencing streaming issues. |
Bug Report
Describe the Bug
A clear and concise description of the problem...To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.Screenshots/Logs
If applicable, add screenshots and log output to help explain your problem.Additional context
Add any other context about the problem here.Homebridge Ring Config
Post homebridge-ring platform config without sensitive information
Environment
The text was updated successfully, but these errors were encountered: