PTZ5A4K-25x Stopped working after being in web interface. How to reconnect

JHW

Getting the hang of it
Jul 21, 2019
23
40
West Virginia
So I was following along Andy's video on adjusting the settings, mostly the PTZ auto tracking while I was in the web interface. I think I also clicked the PTZ maintenance button while I was there. Anyhow after about 30 seconds before saving anything, the camera was no longer reachable, and Blue Iris showed "No Signal". I went out to the camera and the PTZ was moving sometimes. I still couldn't get connected to it, so I went into my POE switch and stopped delivering power. I turned the power back on and the switch's POE indicator went from 'disabled - to searching -to delivering power. But still now joy on logging into the camera via the web interface or restarting it in Blue Iris. Anyone know the troubleshooting steps to take with this. I'm thinking maybe I'll have to reset it.

Update: Ok, oddly enough after I posted this, the camera came back up on its own. I'm not sure why it disconnected in the first place or took so long to come back online. I'm wondering whether the PTZ maintenance button I clicked made it go offline into lockout for determined time.
But while I'm here, I'll say that it seems odd in the Motion Detection section of the settings, when you click on an area to exclude from motion detection. That setting moves with the PTZ, pan left/right or up/down. So how the heck does that work if the area moves around with the PTZ?
 
Last edited:
So I was following along Andy's video on adjusting the settings, mostly the PTZ auto tracking while I was in the web interface. I think I also clicked the PTZ maintenance button while I was there. Anyhow after about 30 seconds before saving anything, the camera was no longer reachable, and Blue Iris showed "No Signal". I went out to the camera and the PTZ was moving sometimes. I still couldn't get connected to it, so I went into my POE switch and stopped delivering power. I turned the power back on and the switch's POE indicator went from 'disabled - to searching -to delivering power. But still now joy on logging into the camera via the web interface or restarting it in Blue Iris. Anyone know the troubleshooting steps to take with this. I'm thinking maybe I'll have to reset it.

if you somehow defaulted camera, you will find it at 192.168.1.108.
Your computer must be in 192.168.1.xxx / 255.255.255.0 network segment..

Or use Dahua config or any Dahua NVR with camera registration page - to find and configure camera.
 
Maintenance includes a reboot and that is why you lost connection until the PTZ fired back up.

Why are you using Motion Detection? Most here use IVS as it is far superior.
 
  • Like
Reactions: bigredfish
Yep, a reboot as mentioned.

I can't see using MD on a PTZ unless you have tracking disabled in which case its just an expensive long range fixed focus camera
 
Maintenance includes a reboot and that is why you lost connection until the PTZ fired back up.

Why are you using Motion Detection? Most here use IVS as it is far superior.
What I am trying to achieve is have the PTZ and zoom follow along when it detects motion. Where would I find IVS? I see there is an "enable auto-track" in BI's PTZ/Control tab. I'm trying to understand whether these settings are made in the web GUI or in BI or in both. I also have CodeProject.AI installed but now realized the dashboard is unreachable. Haven't had much luck tinkering with it. If I recall it was sucking up a lot of resource.
 
Yep, a reboot as mentioned.

I can't see using MD on a PTZ unless you have tracking disabled in which case its just an expensive long range fixed focus camera
It is an expensive camera. Doesn't help that I have so many trees around here. I mounted it on my garage corner around 8' high to get under the canopies, and have moved it twice to try for a better view. I had it auto-tracking before but with all the leaves moving around in the wind, this PTZ was going crazy, and it had a pretty bad ability to track me walking. Seemed like it was way too sensitive and always over shot. I upgraded the firmware and still need to dig into the right settings for this thing to auto track.

I thought the MD was used to paint out areas that you wanted the camera to ignore, but then that defined area seems to move along with the PTZ, rendering the idea sort of useless. Can you point to any good info on configuring IVS for this thing, or am I overthinking it.
 
The PTZ maintenance button likely triggered a temporary lockout, causing the camera to go offline. Power cycling just forced it to reboot faster.
If you need stable masks, a fixed camera or software that supports scene-based masking is better. For now, avoid the maintenance button unless necessary and check for firmware updates.
 
You use the camera for auto tracking not BI.

MD is so old school.

IVS uses AI and is where the tracking is.

This video shows how to set up IVS and auto tracking


OMG - I'm an idiot. Wow, I just bought 4 IPC-Color4K from Andy and set them up using MD. Didn't even know there was a smart plan for them. Now I'm just realizing my older HDW4831 and T549M that I've had for years also have IVS and smart plan. Guess I'll be changing these things around. Thanks for the info. BTW, these new cams with the 1/1.2 sensor are so bright and clear at night.
 
Still having problems with the auto tracking. I can see it attempting to auto track when a car or person is moving along in the field of view, but as soon as the camera begins to zoom and track, the connection drops, the frame freezes and then re-establishes connection. Getting about 100 or so drop outs a day. I was thinking maybe a problem with the POE was causing this but then when I manually zoom and pan, I don't have any problems. So to test whether BI was the problem, I dropped the camera from BI and lo and behold auto tracking is working. Now I just need to figure out why BI is causing this problem.
 
Oh wow. When you hit the find/inspect, screenshot and paste here the pop up window.
Opening 192.168.4.186 port 80...
HTTP Get / request...
OK
ONVIF GetSystemDateAndTime
2025-07-26T01:32:51.000Z
Requesting device information...
Manufacturer: General
Model: PTZ5A4K-25X
FirmwareVersion: 3.200.0000018.2.R
GetCapabilities...
Querying services
Has Imaging services: /onvif/imaging_service
Has media services: /onvif/media_service
Has RTP_RTSP_TCP, requesting profiles
profile token MediaProfile00000
profile name MediaProfile_Channel1_MainStream
profile source is 00000
profile source config is 00000
profile token MediaProfile00001
profile name MediaProfile_Channel1_SubStream1
profile source is 00000
profile source config is 00000
profile token MediaProfile00002
profile name MediaProfile_Channel1_SubStream2
profile source is 00000
profile source config is 00000
requesting URI for profile MediaProfile00000
RTSP URI: rtsp:/192.168.4.186:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
requesting URI for profile MediaProfile00001
RTSP URI: rtsp:/192.168.4.186:554/cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif
requesting URI for profile MediaProfile00002
RTSP URI: rtsp:/192.168.4.186:554/cam/realmonitor?channel=1&subtype=2&unicast=true&proto=Onvif
Has Event services: /onvif/event_service
Has WSPullPointSupport
RelayOutputs: 1
RelayOutput: 00000/Bistable/open
InputConnectors: 2
Has Device IO services: /onvif/deviceIO_service
AudioOutputs: 1
Has PTZ service: /onvif/ptz_service
Preset: 1=reset at road
Done



Also here is a copy of the log file for that camera. The data was Reset this afternoon.
nameaddressMACnotesMPixelsCODECHAElapsedFPS/keyBitrateSub FPS/keySub BitrateMotionTriggersAlertsClipsPostedWebcastNoSignal
Dahua PTZ 25x (PTZ-25) 8.3/0.3H265-0:00:08:0719.99/1.00625.8 kB/s9.99/1.0049.5 kB/s
[td]
36​
[/td]​
[td]
3​
[/td]​
[td]
3​
[/td]​
[td]
1​
[/td]​
[td]
0​
[/td]​
[td]
0​
[/td]​
[td]
361​
[/td]​
 
Last edited:
The find/inspect looks good.

I don't think it is this, but change the codec to H264 and if hardware acceleration is on, turn it off.
 
I did notice that I was running a 2nd sub stream. When I turned sub stream 2 off, I got many fewer disconnects. I had hundreds earlier, but this time just a few. Switched to H264, and it still disconnected as it was zooming in during autotrack. I'm going to remove BI from the equation again and see how it works this morning.
Update: Removed BI from the equation and I still had a camera freeze/disconnect when the PTZ when to zoom and track. My POE switch is delivering 10.9W with a max of 16W, but I don't see how this only affects auto track and not manual PTZ movements.
 
I did notice that I was running a 2nd sub stream. When I turned sub stream 2 off, I got many fewer disconnects. I had hundreds earlier, but this time just a few. Switched to H264, and it still disconnected as it was zooming in during autotrack. I'm going to remove BI from the equation again and see how it works this morning.
Update: Removed BI from the equation and I still had a camera freeze/disconnect when the PTZ when to zoom and track. My POE switch is delivering 10.9W with a max of 16W, but I don't see how this only affects auto track and not manual PTZ movements.

That is the problem - the PTZ needs POE+

You are starving the PTZ of power and will kill it early.

When it is auto tracking and then at night with IR, it is needing over 16W.
 
That is the problem - the PTZ needs POE+

You are starving the PTZ of power and will kill it early.

When it is auto tracking and then at night with IR, it is needing over 16W.
I've have the led lights turned off since earlier I was getting a lot of false triggers. The false triggers were resolved with IVS, and I've monitored my switch during the motion and not seeing anything over 10.9W. I had upped the switch to deliver 16.1W max earlier since I only have a 40' cat6 run. Still it might be my cable or my POE or switch. I'm going to switch it over to a 24v supply brick that came with it, turn off my POE and see if that fixes it. Since there's an outlet on the other side of an unfinished wall in the garage it probably doesn't even make sense to use POE with that camera. I've got a better cable tester coming in the mail. Thanks
 
We have seen many people kill a PTZ early by not using POE+ as it is getting starved for power.

Just because it "works" (which obviously it doesn't since it is rebooting under certain scenarios) doesn't mean it isn't bad for the device to be underpowering it.

Just because you haven't seen it go over 10.9watts doesn't mean it isn't wanting more - maybe at 11 watts is when the camera craps out and reboots and you lose signal.

The specs call for POE+ which is 30watts.

1753553097775.png

The distance is irrelevant (unless it is cheap cable or a bad termination) up to the max distance of 328 feet for POE.

If you are ok with an extra cable going up to power it by the power brick, that is your choice, but most people here will run that camera with POE+ so that only one cable is being used.
 
The PTZ Abides on 802.3at