PTZ control quit working with SD4A425DB-HNY

T

tigerwillow1

Known around here
Jul 18, 2016
4,608
10,455
USA, Oregon
All of a sudden the BI PTZ controls quit working on my SD4A425DB-HNY mini PTZ camera. They still work on the camera's web interface and smartPSS. I rebooted the camera and the BI machine with no luck. I don't recall changing anything that should affect this. Any hints on what to look at?

An unrelated problem, but just in case, all of my cameras with the new user interface show yellow triangles on BI, listing "GetEventsError", Error 8000ffff. This includes the PTZ, T180, thermal, and S3 cameras.
 
If you updated BI recently, it may have changed the PTZ protocol. Go to that tab and try the different Dahua versions. V4 is what most think is the stable one.


When BI restarts, it can take several minutes for that GetEventsError to go away. BI seems to be overly sensitive to the newer GUI. Some sort of handshake error.

Usually after a few minutes the camera will calm down and the triangle goes away.

If it doesn't, in the camera GUI, Under Network > Access Platform, turn onvif authenticator off and that will fix the error.
 
  • Like
Reactions: tigerwillow1
Thanks for the hints.

No luck with trying other PTZ protocols. It was originally set to ONVIF, the PTZ controls worked a couple of days ago, and I haven't updated anything. The only thing I've done is I turned the dome by hand today, but since PTZ works on the other interfaces I'm ruling that out as a cause.

I don't see a setting called onvif authenticator. Could that possibly be "Login Verification" on the Platform Access/ONVIF page?
 
That is weird. Might be one of those have to delete the camera in BI and add again, but first I would try the find/inspect button again and see if that clears out whatever funky thing happened.

Yeah Login Verification should be the same thing.
 
  • Like
Reactions: tigerwillow1
Yep, weird. I shut off the ONVIF login authentication and the yellow triangle immediately went away. PTZ still didn't work. On a whim I did a BI restart camera. Now the PTZ controls work. I'll file this in the random computer weirdness bucket. 2 problems fixed, thanks for the help.
 
  • Like
Reactions: GaryCAa
This is some sort of a weird bug related to date. I have two totally separate BI systems. One of them has a bunch of cameras including nine PTZs of different flavors. Two different types of Andy PTZs - the older ones and the current ones - and several different Axis cameras. PTZ quit working on all. The second system has only five non PTZs on it. Neither has been updated recently. I've been trying to figure this out since earlier this evening. I added a Dahua (new Andy) to the second system. PTZ didn't work. I added a Axis Q6044-E to the second system. PTZ didn't work.
I set the date on the second system (I can deal with the bad date on that one) back a day to 3/8/2025 - same time of day - and restarted the service. Still no PTZ. I turned off NTP on the PTZ4M-25X-PV and set the date to 3/8/25. No PTZ. I made BI reconnect to the camera - config, save. PTZ worked. I then turned off NTP on the Q6044-E, and set the date to 3/8/25. Still not PTZ. I made BI reconnectto the Axis. PTZ then worked.

More info to follow.....
 
Setting the camera date to March 10 seems to correct the issue. I'm attaching a video of my screen showing the issue happening when the camera date is March 9. Appears that the problem begins at 00:00 UTC on March 9. Looking at a packet capture - attached - the time is expressed in UTC between the camera and BI. BTW, these cameras are not publicly exposed, so I'm not concerned about the IP's and user name being exposed in the packet capture. I'm going to set the clock back temporarily on the cameras so they can use PTZ later today. It would be great if BI could duplicate and fix the bug. Not a bug in the camera unless it's a bigger bug that affects all ONVIF as this is happening in multiple brands of PTZ camera. Also, prior to the packet capture, I set the time back to the correct date - March 9 - on the computer running BI - the one I was using as a test victim that usually only has 5 cameras. Date being March 9 on the machine running BI seems to have no effect on the issue. It's when the PTZ camera being controlled has a date of March 9 that the issue happens.
 

Attachments

  • Like
Reactions: tigerwillow1
wittaj said:
That is weird. Might be one of those have to delete the camera in BI and add again, but first I would try the find/inspect button again and see if that clears out whatever funky thing happened.

Yeah Login Verification should be the same thing.
Click to expand...
Actually, you seem to have guessed right in 2023. This appears to not be the first time it has happened. This is what sparked my thought that it might be date related.
wittaj

Post in thread 'PTZ controls suddenly stopped working'

That is strange. Let's blame time change LOL
  • Like
 
Similar issues with SmartPSS/Lite

It’s a DST Issue

bigredfish

Thread 'SmartPSS/Lite Playback NETSDK Error'

So some of you may be getting the following NETSDK error when trying to use SmartPSS/Lite today and using the timeline to start/playback a clip.
This problem has been around for years and seems to most frequently show up after a DST switch like we had last night
NETSDK-error.jpg

Note that your NVR IS recording fine, and if you go to the NVR GUI the Search and AI search/playback functions still works fine. Interestingly, so does mobile DMSS

This is a bug in SmartPSS/Lite. It will occur on ANY NVR you try to use the playback timeline on with SmartPSS/Lite, so if you manage more...
 
You must log in or register to reply here.
Top Bottom