Can't configure PTZ with go2rtc

[dominik-cenkner]

OT: I'm really glad that I found this project and looking forward to use it as a more stable replacement for Frigate (which have more complex configuration, frequent connection errors on WiFi cameras and wonky live view).

Either I'm doing something wrong, or it is not possible to use ptz while connecting to camera via go2rtc. Seems like camera configured in ptz section is using host parameter of camera from ffmpeg section and this is usually "localhost" if go2rtc is used. Here is my (simplified) setup for Reolink E340:

go2rtc:
  streams:
    postielka:
      - rtsp://admin:*****@192.168.2.205:554/h264Preview_01_main
  webrtc:
    candidates:
      - 192.168.1.251:8555
      - stun:8555

ffmpeg:
  camera:
    postielka:
      name: postielka
      host: localhost
      port: 8554
      path: /postielka
      width: 2560
      height: 1440
      fps: 20
      codec: h264
      audio_codec: aac

ptz:
  cameras:
    postielka:
      # onvif_host: 192.168.2.205
      onvif_port: 8000
      onvif_username: admin
      onvif_password: *****

I would expect to have an option to explicitly specify camera host in ptz section but there is no such parameter like onvif_host.

[kaburagisec]

Yes, this is because the current PTZ component doesn't account for changes in the streaming URL when using go2rtc with restreaming, which results in ONVIF requests being sent to the localhost instead of the camera endpoint. This issue has been resolved in a draft PR at #1205