[Config Support]: ERROR : No appropriate Onvif profiles found for camera #15078
-
Describe the problem you are havingIssue using 0.15.0-beta1 Camera Config is as follows And the frigate.ptz.onvif: debug logs are as follows I have confirmed that the credentials and ip are correct manually with go2rtc test where it populates with the 3 substreams and profiles Version0.15.0-33825f6 Frigate config fileshown aboveRelevant Frigate log outputshown aboveRelevant go2rtc log outputshown aboveFrigate statsNo response Operating systemOther Linux Install methodDocker Compose docker-compose file or Docker CLI commandnot relevantObject DetectorCoral Screenshots of the Frigate UI's System metrics pagesNo response Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Answered by
WillEhman
Nov 24, 2024
Replies: 1 comment 5 replies
-
|
Changes were made in this PR to check for appropriate ONVIF support. These changes were a part of 0.14.0, so what you're seeing is not because of any changes in 0.15 beta. Your camera is reporting that it does not have a PTZ configuration, so there are no ONVIF profiles for Frigate to use for PTZ controls:
|
Beta Was this translation helpful? Give feedback.
5 replies
-
|
I'm not sure. Did you try a good old fashioned reboot? Have you made any configuration changes to the camera? |
Beta Was this translation helpful? Give feedback.
-
|
I've been facing this issue for a few days now, done several reboots, it has not worked since updating to the 0.15 beta, I may try rolling back to 0.14 to see if I can get it going again. |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue in 0.14, I suspect a parallel auto-update to the camera firmware may be to blame |
Beta Was this translation helpful? Give feedback.
-
|
The (private) update provided by Tapo has fixed the issue. Thank you. If anyone else has this issue I suggest they bug tp-link and get them to fix their firmware. |
Beta Was this translation helpful? Give feedback.
Answer selected by
WillEhman
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The (private) update provided by Tapo has fixed the issue. Thank you. If anyone else has this issue I suggest they bug tp-link and get them to fix their firmware.