Hi,
I was getting authentication errors in Unifi protect when I initially got this running.
There was no errors on the shell, and all cameras were accessible through the proxied URLs successfully.
After much troubleshooting, I found that it would work successfully with 1 or 2 cameras specified in the config.yaml but not more.
I currently have it working, as a workaround, I configured 2 cameras at a time, adopted into Unifi Protect, configured the next 2 cameras, restarted onvif server, adopted these 2 cameras, and so on for all 8 cameras.
Once all 8 were adopted in Unifi, I changed the configuration back to all 8 and they are now all working in Protect.
However, there is definitely a bug here somewhere that needs to be addressed.
Here is my YAML
onvif:
- mac: a2:a2:a2:a2:a2:a1
ports:
server: 8081
rtsp: 8554
name: Kennel_Walkway
uuid: 15b21259-77d9-441f-9913-3ccd8a82e430
highQuality:
rtsp: /ch01/0
width: 3840
height: 2160
framerate: 6
bitrate: 6144
quality: 4
lowQuality:
rtsp: /ch01/1
width: 432
height: 320
framerate: 4
bitrate: 96
quality: 1
target:
hostname: 192.168.10.93
ports:
rtsp: 554
- mac: a2:a2:a2:a2:a2:a2
ports:
server: 8082
rtsp: 8555
name: Front_Door
uuid: 15b21259-77d9-441f-9913-3ccd8a82e431
highQuality:
rtsp: /ch02/0
width: 3840
height: 2160
framerate: 6
bitrate: 6144
quality: 4
lowQuality:
rtsp: /ch02/1
width: 432
height: 320
framerate: 4
bitrate: 96
quality: 1
target:
hostname: 192.168.10.93
ports:
rtsp: 554
- mac: a2:a2:a2:a2:a2:a3
ports:
server: 8083
rtsp: 8556
name: Garage_and_Sheds
uuid: 15b21259-77d9-441f-9913-3ccd8a82e432
highQuality:
rtsp: /ch03/0
width: 3840
height: 2160
framerate: 6
bitrate: 6144
quality: 4
lowQuality:
rtsp: /ch03/1
width: 432
height: 320
framerate: 4
bitrate: 96
quality: 1
target:
hostname: 192.168.10.93
ports:
rtsp: 554
- mac: a2:a2:a2:a2:a2:a4
ports:
server: 8084
rtsp: 8557
name: Driveway
uuid: 15b21259-77d9-441f-9913-3ccd8a82e433
highQuality:
rtsp: /ch04/0
width: 3840
height: 2160
framerate: 6
bitrate: 6144
quality: 4
lowQuality:
rtsp: /ch04/1
width: 432
height: 320
framerate: 4
bitrate: 96
quality: 1
target:
hostname: 192.168.10.93
ports:
rtsp: 554
- mac: a2:a2:a2:a2:a2:a5
ports:
server: 8085
rtsp: 8558
name: Pump_Shed
uuid: 15b21259-77d9-441f-9913-3ccd8a82e434
highQuality:
rtsp: /ch01/0
width: 1920
height: 1080
framerate: 15
bitrate: 2048
quality: 4
lowQuality:
rtsp: /ch01/1
width: 432
height: 320
framerate: 4
bitrate: 96
quality: 1
target:
hostname: 192.168.10.86
ports:
rtsp: 554
- mac: a2:a2:a2:a2:a2:a6
ports:
server: 8086
rtsp: 8559
name: Back_Door
uuid: 15b21259-77d9-441f-9913-3ccd8a82e435
highQuality:
rtsp: /ch02/0
width: 1920
height: 1080
framerate: 15
bitrate: 2048
quality: 4
lowQuality:
rtsp: /ch02/1
width: 432
height: 320
framerate: 4
bitrate: 96
quality: 1
target:
hostname: 192.168.10.86
ports:
rtsp: 554
- mac: a2:a2:a2:a2:a2:a7
ports:
server: 8087
rtsp: 8560
name: Kennels
uuid: 15b21259-77d9-441f-9913-3ccd8a82e436
highQuality:
rtsp: /ch03/0
width: 1920
height: 1080
framerate: 15
bitrate: 2048
quality: 4
lowQuality:
rtsp: /ch03/1
width: 432
height: 320
framerate: 4
bitrate: 96
quality: 1
target:
hostname: 192.168.10.86
ports:
rtsp: 554
- mac: a2:a2:a2:a2:a2:a8
ports:
server: 8088
rtsp: 8561
name: Back_Runs
uuid: 15b21259-77d9-441f-9913-3ccd8a82e437
highQuality:
rtsp: /ch04/0
width: 1920
height: 1080
framerate: 15
bitrate: 2048
quality: 4
lowQuality:
rtsp: /ch04/1
width: 432
height: 320
framerate: 4
bitrate: 96
quality: 1
target:
hostname: 192.168.10.86
ports:
rtsp: 554
Hi,
I was getting authentication errors in Unifi protect when I initially got this running.
There was no errors on the shell, and all cameras were accessible through the proxied URLs successfully.
After much troubleshooting, I found that it would work successfully with 1 or 2 cameras specified in the config.yaml but not more.
I currently have it working, as a workaround, I configured 2 cameras at a time, adopted into Unifi Protect, configured the next 2 cameras, restarted onvif server, adopted these 2 cameras, and so on for all 8 cameras.
Once all 8 were adopted in Unifi, I changed the configuration back to all 8 and they are now all working in Protect.
However, there is definitely a bug here somewhere that needs to be addressed.
Here is my YAML