"move" command : weak/questionable implementation #155
Description
Initially this issue was reported to Frigate repository. But its maintainers said that are using python-onvif-zeep-async library to realize Onvif actions.
So, here's the issue.
One of my IP cameras (I have three different brands) responds with an error when executing the "ContinuousMove" PTZ command. 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 (seems it also uses this library).
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 used version of "Stop" command.
However, all my IP cameras support the implementation of this command used by a wide range of another 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 "ContinuousMove" 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.
Dumps are in tcpdump format.
I've read the #99 but want to say that the SW mentioned above also declares "full compliance to the Onvif standard".
IPC:
Manufacturer: Meari Model: Speed 18T FirmwareVersion: 5.5.4 SerialNumber: 119698137 HardwareId: ppstrong-c95-tuya2_general_8733-5.5.4.20230724