[Config Support]: home assistant + nestcam #20569
Replies: 8 comments 1 reply
-
|
Your go2rtc configuration shows the For your Nest cam with entity ID cameras:
tuin: # <------ Name the camera
enabled: true
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/1_tuin # <----- Use the go2rtc restream
input_args: preset-rtsp-restream
roles:
- detect
- record
detect:
enabled: true # <---- enable detection once you have a working camera feed
width: 1280
height: 720The key points:
After updating your configuration, restart Frigate. You should then see the camera feed in the Frigate UI. Once confirmed working, you can configure your Coral detector by updating the detectors section in your config. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
@inkeep that doesn't seem to work. In go2rtc in the config menu under home assistant i see "no sources". So i assume it's not getting the cameras loaded automatically from homeassistant. What should |
Beta Was this translation helpful? Give feedback.
-
|
@inkeep logfiles s6-rc: info: service s6rc-oneshot-runner successfully started |
Beta Was this translation helpful? Give feedback.
-
|
Based on your logs and the fact that go2rtc shows "no sources" under Home Assistant, the issue is that the Home Assistant integration in go2rtc isn't properly discovering your Nest cameras. The error For Nest cameras specifically, you'll likely need to manually configure the streams in go2rtc rather than relying on automatic discovery. Since Nest cameras typically don't provide direct RTSP streams, you'll need to use a different approach. Try adding the stream manually to your go2rtc configuration. You can access this through the go2rtc web interface at port 1984, or by manually editing your configuration (1). If your Nest camera is accessible through Home Assistant as go2rtc:
streams:
1_tuin:
- "ffmpeg:http://homeassistant.local:8123/api/camera_proxy/camera.1_tuin#video=copy"However, this approach may require authentication tokens. A more reliable method for Nest cameras is to check if they provide any direct streaming URLs that you can configure directly in go2rtc. Alternatively, you may need to configure your camera to connect directly to the original Nest stream source rather than going through Home Assistant, depending on your Nest camera model and setup. If the automatic Home Assistant integration continues to show "no sources", you should verify that your Home Assistant cameras are properly accessible and that the go2rtc Home Assistant integration has the correct permissions to discover them (1). 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
@inkeep what permissions should i check for go2rtc ? I understand auto discovery should be possible ? |
Beta Was this translation helpful? Give feedback.
-
|
Based on the documentation, auto discovery should work with the Home Assistant integration in go2rtc (1). However, there are no specific permission settings mentioned in the available sources for go2rtc's Home Assistant integration. Your go2rtc configuration shows the hass:
config: /homeassistantThe fact that you see "NO SOURCES" suggests the integration isn't finding any compatible camera entities in Home Assistant. This could be because:
Since auto discovery isn't working for your Nest cameras, you'll need to manually configure the streams. For cameras that don't provide direct RTSP access (like many Nest cameras), you may need to use alternative methods or check if your specific Nest camera model supports direct streaming protocols that go2rtc can access (1). The documentation doesn't specify particular permission requirements beyond having the 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
Anyone knows what to do here ? It's nest cam (battery). thanks ! |
Beta Was this translation helpful? Give feedback.
-
|
Frigate is designed to work with cameras that are always streaming. Even if you get this to work, it likely won't be tenable as the battery will drain too quickly |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 thank you. They are called nest cam (battery) but they are actually continuously connected to power |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
Hi, i installed frigate full access add-on on my homeassistant server. I have nest cams linked to home assistant and can access them and watch their videofeed within homeassistant.
However I don't manage to get/see these streams in frigate.
I understand I need to configure go2rtc to get the cameras from home assistant (i read somehwere they can load automatically). I don't manage to do this.
Then I understand there is a second step needed to actually display them in frigate. Which again I don't know what to do.
One of the nest cams visisble in home assistant has this entity id:
camera.1_tuin
Version
0.16.1-e664cb2
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
config (which is automatically generated i guess): api: origin: '*' hass: config: /homeassistant log: format: text webrtc: candidates: - 192.168.179.112:8555 - stun:8555 ffmpeg: bin: /usr/lib/ffmpeg/7.0/bin/ffmpeg log: Time Level Message 23:16:44.950 info go2rtc version=1.9.9 platform=linux/amd64 revision=fa580c5 23:16:44.950 info config path=/dev/shm/go2rtc.yaml 23:16:44.951 info [rtsp] listen addr=:8554 23:16:44.951 info [api] listen addr=:1984 23:16:44.952 info [webrtc] listen addr=:8555Frigate stats
No response
Operating system
Home Assistant OS
Install method
Home Assistant Add-on
docker-compose file or Docker CLI command
n/aObject Detector
Coral
Screenshots of the Frigate UI's System metrics pages
No response
Any other information that may be helpful
i have a coral usb that is not yet configured in the config file either
Beta Was this translation helpful? Give feedback.
All reactions