-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: Camera movement command is not working for some cameras #54
Comments
@faithoflifedev This problem is in the latest version of the project. Let me know if you need anything else. |
Hi @dinurymomshad, without an actual device, it's difficult to troubleshoot this type of an issue, but here's something that I can see, based on the logs provided. In the first request made it has the following timestamp for the authentication portion of the request: <Created xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-20
0401-wss-wssecurity-utility-1.0.xsd">2024-01-08T20:22:08.004Z</Created> Notice that the ISO8601 formatted date has millisecond resolution. For the next request the timestamp is: <Created xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-20
0401-wss-wssecurity-utility-1.0.xsd">2024-01-08T20:22:08.088009Z</Created> This one has nanosecond resolution for some strange reason. The Onvif device uses the timestamp as part of the authentication process. I can't say for sure, but I'm suspecting that the device your using doesn't support nanoseconds for time resolution and this is messing up the authentication. I'll see if I can provide you some code to test with later that might resolve this (assuming this is actually the problem). |
Hi @dinurymomshad, Ignore my previous post. I've been able to recreate the issue and I'm now working to resolve. |
Hi @dinurymomshad, I just published |
Sorry for the delay, but here is a log. Notice how "MainStream" token works to fetch PTZ profiles even though it doesn't exist in the list of media profile. But absolute move doesn't work.
|
@dinurymomshad, you'll need to use a First, I recommend installing chocolatey if you haven't already, then install jq choco install jq
onvif media1 get-profiles | jq -r '.[] | ."@token"' This will output a list of the valid profile tokens for your device. Based on the debug info you provided, this would look like:
So the command to get a list of the first 5 presets would look like: onvif ptz get-presets --limit 5 --profile-token CH01 | jq -r '.[] | ."@token" + "\t" + .Name' |
I've tried as you said. It's not working.
|
The values for: All need to be between -1 and 1 |
Profile Token CH01_sub
Profile Token CH01
|
Hi @dinurymomshad, the command you supplied works as expected on the devices that I have available for testing. I don't think I can provide any further help here. |
Would you like to remotely test the camera if we set things up? This camera is better in terms of overall functionality compared to the older models. |
@dinurymomshad, one more thing to try List the configuration tokens for your device onvif ptz get-configurations Which should show you something like
Which should display the X, Y, Zoom limits for your device. |
Thanks for the feedback. Here it is:
|
You can send me a DM at faithoflifedev and we can discuss this in more detail. |
Hi @dinurymomshad, I just published |
Hi @dinurymomshad, I just published a developer release for v3.0.0 which appears to might resolve the |
This is continuation of fix for #53.
Here is the log:
The text was updated successfully, but these errors were encountered: