Add support for RTSP cameras for Nest source - #1253
Conversation
|
This is nice, drops the need of https://github.com/felipecrs/hass-expose-camera-stream-source for these cameras. |
|
Although I suppose users still has to provide their own authentication details instead of having them fetched from Home Assistant, right? (which would make total sense). |
|
I didn't look at the Hass integration works so unsure if it will properly fetch credentials. I suppose if it works with the WebRTC cameras that it should work with this change as well, as any changes I made happen after the Nest API is initialized. I guess one issue may be with the stream URL expecting a protocol parameter. I updated the logic that generated the URL in the "Add" tab of the UI to include this. I can take a look at that later today to make sure it works properly. |
|
Any news on this? I think I saw a comment on a different issue saying that work on Nest-integrated cameras had been abandoned. This was particularly difficult for me since I have a Nest Doorbell Wired Camera (1st gen) that supports RTSP stream only. I saw https://github.com/felipecrs/hass-expose-camera-stream-source was recommended by you @felipecrs on various other issues. But, I managed to utilize the RTSPtoWebRTC integration, setting up the RTSP server on the same port as go2rtc, to add my Nest Doorbell camera to go2rtc. Could this a good alternative to the expose camera source? |
|
@RobotTheMLG The Nest Doorbell Gen1 supports WebRTC now. just upgraded mine a couple weeks ago. It's now working in Frigate through latest release of Go2RTC. I suggest you double check the Nest/Google Home app to see if you can upgrade yours. Source: https://developers.google.com/nest/device-access/release-notes#legacy_camera_migration |
Are you sure you have the Nest Doorbell 1st gen (Formally Nest Hello)? I believe that documentation is referring to the current Nest Wired Doorbell (2nd gen). |
|
Yes, It's an original Nest Hello. |
|
https://developers.google.com/nest/device-access/supported-devices This page still says that Nest Hello is RTSP-only. But it may just be outdated. If there are no more devices that are RTSP-only, maybe this PR is unnecessary then. |
|
For my 1st gen Nest Hello I have a Google Home app notification which reads as follows:
I've only just enrolled in the Public Preview so I don't know if that's a recent announcement or what "supported soon" will turn out to mean in terms of functionality or timescale. |
|
Apologies, I had forgotten to go back to this. That’s correct, as soon
as you migrate the cameras to Google Home it’ll update them to WebRTC.
That’s part of why the transition is has to be opted in to.
I remember seeing some doc that explained this but I can’t find it now.
But, as soon as you enable the preview the cameras will be updated with
WebRTC support.
I’m still using Nest because the Google Home app doesn’t work as well
for some workflows, and has a terrible UX. But, I know that’s an edge
case so if we don’t need to support this we can close this PR.
- jamal
On September 9, 2024, John Watson ***@***.***> wrote:
<https://developers.google.com/nest/device-access/supported-devices>
This page still says that Nest Hello is RTSP-only. But it may just be
outdated.
If there are no more devices that are RTSP-only, maybe this PR is
unnecessary then.
—
Reply to this email directly, view it on GitHub
<#1253 (comment)>,
or unsubscribe <https://github.com/notifications/unsubscribe-
auth/AAAOJTIY7EQ7JYJOF6BCKHTZVXFRTAVCNFSM6AAAAABKYA7IZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZYGU4DMMBSGU>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I believe I found a useful article by Google on this specific process: https://support.google.com/googlenest/answer/13038234?hl=en I mistakenly believed that I had "migrated" because my Nest Hello camera appeared in Google Home but that is incorrect. These specific steps actually need to be taken to "migrate" the camera. A potential problem would be users that wish to keep utilizing the Nest app to manage their camera. |
Right. I guess @AlexxIT has to decide now. Worst case users can still use https://github.com/felipecrs/hass-expose-camera-stream-source to import their RTSP-only Nest cameras into go2rtc. |
|
Not sure what I'm missing, but I have an first gen Nest Hello with a Nest Aware subscription, but I don't have the option to migrate in the Nest app. I'm in the Public Preview of the Home app for a long time. Maybe it's region related, since I'm in Europe. |
Seems like my enrollment to the Public Preview may have just been taking a while. I have now successfully migrated my 1st gen Nest Hello and have it hooked up to Home Assistant and streaming into frigate via go2rtc without any apparent issues so far. |
| refreshToken := query.Get("refresh_token") | ||
| projectID := query.Get("project_id") | ||
| deviceID := query.Get("device_id") | ||
| protocols := strings.Split(query.Get("protocols"), ",") |
There was a problem hiding this comment.
The array doesn't make sense. There is no priority check below. The first protocol specified will always be selected.
|
Thanks! Did a little refactoring. I don't use Nest, so hopefully it all works. |
AlexxIT
changed the title
@felipecrs does your expose module work with Nest Hello Doorbell? (Gen 1)? Having trouble getting the go2rtc straight method to work in frigate and would give this a try since I have the nest working in HA no issues. Thanks |
|
It should work, if you haven't upgraded your firmware to the WebRTC-only one. |
I assume you mean the Nest unit itself? I think mine is already upgraded to WebRTC. When I go thru the steps with the refresh token and auth code, etc the output has this in it. Unless you mean something else? "supportedProtocols": [ |
|
If you migrated your doorbell to the Google Home app, then you no longer have RTSP capability on it. It's WebRTC-only. This PR is not relevant for you anymore, nor my integration. Your best option is the Nest source in go2rtc. You can find better details in this PR: |
Thanks Ill check out. I actually originally found this on the frigate git and followed the steps (which seems to work for some) but I keep getting a 404 not found in my go2rtc log within frigate, so exploring all options. It works in HA at least |
nest: add support for RTSP cameras
8 participants
Add support for RTSP cameras for Nest. The protocol information is carried in the stream URL, to avoid having to make a call to resolve the device when a stream is started. The same logic for extending the stream is used, but StreamExtensionToken is used when it's an RTSP stream.