mirror of
https://github.com/AlexxIT/go2rtc.git
synced 2026-04-22 23:57:20 +08:00
Alex X
43 lines
1.1 KiB
Markdown
43 lines
1.1 KiB
Markdown
# ONVIF
|
|
|
|
## ONVIF Client
|
|
|
|
[`new in v1.5.0`](https://github.com/AlexxIT/go2rtc/releases/tag/v1.5.0)
|
|
|
|
The source is not very useful if you already know RTSP and snapshot links for your camera. But it can be useful if you don't.
|
|
|
|
**WebUI > Add** webpage support ONVIF autodiscovery. Your server must be on the same subnet as the camera. If you use Docker, you must use "network host".
|
|
|
|
```yaml
|
|
streams:
|
|
dahua1: onvif://admin:password@192.168.1.123
|
|
reolink1: onvif://admin:password@192.168.1.123:8000
|
|
tapo1: onvif://admin:password@192.168.1.123:2020
|
|
```
|
|
|
|
## ONVIF Server
|
|
|
|
A regular camera has a single video source (`GetVideoSources`) and two profiles (`GetProfiles`).
|
|
|
|
Go2rtc has one video source and one profile per stream.
|
|
|
|
## Tested clients
|
|
|
|
Go2rtc works as ONVIF server:
|
|
|
|
- Happytime onvif client (windows)
|
|
- Home Assistant ONVIF integration (linux)
|
|
- Onvier (android)
|
|
- ONVIF Device Manager (windows)
|
|
|
|
PS. Support only TCP transport for RTSP protocol. UDP and HTTP transports - unsupported yet.
|
|
|
|
## Tested cameras
|
|
|
|
Go2rtc works as ONVIF client:
|
|
|
|
- Dahua IPC-K42
|
|
- OpenIPC
|
|
- Reolink RLC-520A
|
|
- TP-Link Tapo TC60
|