[Support]: Onvif "move" command : weak/questionable implementation #20464
Replies: 2 comments 1 reply
-
Based on the error logs you've provided, your camera is returning "Action Not Implemented" errors for PTZ commands. This is a known ONVIF compatibility issue with certain camera models. Your Meari Speed 18T camera appears to have incomplete ONVIF support, similar to other cameras documented in the PTZ compatibility list (1). The error "Action Not Implemented" suggests your camera's ONVIF implementation doesn't properly support the specific PTZ commands that Frigate uses. Frigate uses the For your specific camera model, you have a few options:
iptables -t nat -A PREROUTING -d 192.168.1.10 -j DNAT --to-destination $CAMERA_IP
iptables -t nat -A POSTROUTING -s $CAMERA_IP -j SNAT --to-source 192.168.1.10
Unfortunately, your camera model isn't listed in the working PTZ cameras table (1), and based on the "Action Not Implemented" errors, it appears to have incomplete ONVIF support similar to other cameras that don't work properly with Frigate's PTZ implementation. The root cause is that changes to ONVIF command formatting would need to be made upstream in the 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
As the AI correctly indicated, Frigate uses the Line 435 in 9d85136 On a key up or mouse up event, Frigate sends an ONVIF Line 412 in 9d85136 This is working as designed in Frigate. If you believe there is an error in the implementation of the specific ONVIF code, you'll want to reach out on their GitHub repo. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Describe the problem you are having
One of my IP cameras (I have three different brands) responds with an error when executing the "Move" PTZ command using Frigate's UI. The IPC begins to move but then can't stop.
I encounter same behavior when trying to realize PTZ control of this IPC by the Home Assistant.
I've also found reports from other users of similar IPC behavior, and I suspect the cause is the same.
This occurs because the IPC doesn't support the version of "Stop" command used by Frigate.
However, all my IP cameras support the version of this command used by a wide range of other ONVIF-related software.
It's for example the well-known open source Onvif device manager, the professional VMS, the CLI onvif control script.
I think the source of the problem is the indication of the action "Stop" in the
<Header>
section of XML message. All the SW mentioned above produce XML messages in IP packets which contain "Stop" command only in<Body>
section.To proove this fact here's attached dumps of captured IP traffic of PTZ "Move" actions produced by every mentioned program for the same IPC where is clearly seen which versions of the "Stop" XML request were followed by OK HTTP retcode and which ones were followed by error.
ptz_cont_move.zip
Steps to reproduce
Version
0.16.1-e664cb2
In which browser(s) are you experiencing the issue with?
any supported by Frigate
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
Operating system
Debian
Install method
Docker Compose
Network connection
Wired
Camera make and model
Manufacturer: Meari Model: Speed 18T FirmwareVersion: 5.5.4 SerialNumber: 119698137 HardwareId: ppstrong-c95-tuya2_general_8733-5.5.4.20230724
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
RPi 5 8Gb
Beta Was this translation helpful? Give feedback.
All reactions