Put in the cameras IP addresss, username and password, click Find/Inspect.
It will find the cam as Generic ONVIF.
Go to PTZ tab, click enable.
Done.
This ^^^^ works for 99% of folks.
For folks that might not be aware, there are two totally
separate 'admin' accounts on the camera.
This one (in red) is the account that everyone uses when they log into the webUI (or via an app, like smartPSS).
This one (in green) is a completely different account, and it's used to access the camera via ONVIF.
Blue Iris needs the password for the '
ONVIF' admin account in order to properly Find/Inspect a camera (and configure the camera within Blue Iris).
For 99% of folks, the two separate admin accounts have the exact same password... so even if they type the password for the 'webUI' admin account into Blue Iris, it's still going to work.
But .... for the 1% of folks whose cameras got somehow borked to where the webUI 'admin' account has a different password than the 'ONVIF' admin account, ... if you put your 'webUI' admin password into Blue Iris, BI will fail to to connect to your camera using ONVIF.
When BI fails to properly connect using ONVIF, your camera will return DIFFERENT information to BI (during Find/Inspect), and BI will configure the camera *differently*, and that camera will not act like a normal 5231 in BI.
In that case, it's not as simple as going into the PTZ tab and clicking enable. I mean, you can do that, but PTZ won't work.
When BI properly connects to your camera via ONVIF, this is what the 5231 tells it:
Opening 192.168.1.20 port 80...
HTTP Get / request...
OK
ONVIF GetSystemDateAndTime
2018-03-09T15:30:50.000Z
Requesting device information...
Manufacturer: Dahua
Model: IPC-HDW5231R-Z
FirmwareVersion: 2.460.Dahua 00.7.R, build: 2017-03-06
GetCapabilities...
Querying services
Has Imaging services: /onvif/imaging_service
Has media services: /onvif/media_service
Has RTP_RTSP_TCP, requesting profiles
first profile is MediaProfile000
first source is 000
requesting URI for profile MediaProfile000
RTSP URI: /cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
Has Event services: /onvif/event_service
RelayOutputs: 0
InputConnectors: 0
Has Device IO services: /onvif/deviceIO_service
AudioOutputs: 0
Has PTZ service: /onvif/ptz_service
Done
When BI can't connect via ONVIF, this is what the camera returns to it:
Opening 192.168.1.20 port 80...
HTTP Get / request...
OK
ONVIF GetSystemDateAndTime
2018-03-09T15:31:39.000Z
Requesting device information...
Bad response
GetCapabilities...
Querying services
Has Imaging services: /onvif/imaging_service
Has media services: /onvif/media_service
Has RTP_RTSP_TCP, requesting profiles
Has Event services: /onvif/event_service
RelayOutputs: 0
InputConnectors: 0
Has Device IO services: /onvif/deviceIO_service
AudioOutputs: 0
Has PTZ service: /onvif/ptz_service
Checking for common cameras...
Foscam FI86xx/98xx compatible?
Foscam FI89xx compatible?
Foscam FI9821 V2 compatible?
Foscam FI9821 media port compatible?
RTSP port open?
RTSP port detected!
Done