-
Notifications
You must be signed in to change notification settings - Fork 295
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
Source: Nest - "400 Bad Request" #1097
Comments
Also worth noting that when I try entering details the camera via the "Add" > "Goggle Nest" UI, I get "no sources". |
go2rtc v1.9.0 had a bug where consumer connections where not closed. |
On version 1.9.1, I still get "400 Bad Request". Is there a good method of debugging this problem? I've set the log level to debug and here is what I'm seeing: 5/11/2024, 10:08:58 AM | debug | [webrtc] new consumer src=nest-doorbell |
Sorry for repeating myself but are you sure it works on the home app?
I would try to make it work using Home Assistant first with the nest integration, then copy the exact credentials from ha ( |
I don't have Nest cameras, so can't help with that |
Ive got the same issue (nest doorbell wired), and I've triple checked my params:
Ive also made the API request to fetch the device with the access token and deviceId as per the original post here, and I get a good response back. Im using go2rtc 1.9.2 and Frigate (0.13.2-6476f8a)
But get this in Frigate go2rtc log
Eventually it gets throttled, HTTP 429. I manage to get this working with HA Google Nest addon though. I think maybe this is because Nest doorbell wired (legacy) only supports RTSP stream, and go2rtc only support Nest with webRTC stream? |
Hey,
I'm trying to get my nest camera working on Version: 1.9.1 via the following method:
However, I'm getting "400 Bad Request".
I've checked my:
client_id
client_secret
refresh_token
project_id
device_id
All are correct and I've confirmed this via commands like:
Which provided a successful response. I'll keep checking as maybe I've made and missed a tiny mistake somewhere, but assuming I've not, any ideas what might be going on? Many Thanks.
The text was updated successfully, but these errors were encountered: