GenericIP Camera Driver Installation

Use our Video Family drivers to monitor your home or business from any place in the world.


The Generic IP Camera driver for myServer requires the Video Family license.

MSRP $99.99
  1. Purchase the Video Family license.
  2. Download the GenericIP Camera driver from myInstaller and install it on the myServer PC
  3. Restart myServer
  4. Apply your Video Family license to myServer's Licensing tab.
  5. Go into the Video Family and Add a new line item.
  6. Enter in your Camera's unique name, choose GenericIPCam as the driver, type in the  IP Address and then port and a camera description.
  7. Soon, you should see your configured cameras created in the GenericIP Camera driver.
  8. Go into the GenericIP Camera driver and double click on the newly created camera link.  Type the camera's username, IP address, password and port for any fields that are empty.
  9. You can optionally enter in the camera's pan / tilt / zoom settings, if the camera supports this.  Example is shown below.
  10. Click SAVE.
  11. Tip: For the pictures to display in the myUI.Tablets.Samples camera.html webpage, ensure the cameras are numbered 1-4.  They need to have unique IDs.
  12. Tip: If you change the myServer IP address, you will need to deselect "Save Variables on Exit" in the myServer options.  Then restart.  This will delete the old variables.  On the next restart the image paths will be recreated with the myServer's latest IP address so the HTML can reference the new server's image path.

Configuring the Generic IP Camera driver

Below are settings from an inexpensive IP camera as an example:

Username:  admin    IPaddress:

Password: admin     IP Port 81

Snapshot Image: http://<<ipaddress>>:<<ipport>>/snapshot.cgi?user=<<username>>&pwd=<<password>>

Live Image: http://<<ipaddress>>:<<ipport>>/snapshot.cgi?user=<<username>>&pwd=<<password>>

Tilt Up: http://<<ipaddress>>:<<ipport>>/decoder_control.cgi?loginuse=<<username>>&loginpas=<<password>>&command=0&onestep=1

Tilt Down: http://<<ipaddress>>:<<ipport>>/decoder_control.cgi?loginuse=<<username>>&loginpas=<<password>>&command=2&onestep=1

Pan Left: http://<<ipaddress>>:<<ipport>>/decoder_control.cgi?loginuse=<<username>>&loginpas=<<password>>&command=4&onestep=1

Pan Right: http://<<ipaddress>>:<<ipport>>/decoder_control.cgi?loginuse=<<username>>&loginpas=<<password>>&command=6&onestep=1

Center: http://<<ipaddress>>:<<ipport>>/decoder_control.cgi?loginuse=<<username>>&loginpas=<<password>>&command=25&onestep=1

Start Scan: http://<<ipaddress>>:<<ipport>>/decoder_control.cgi?loginuse=<<username>>&loginpas=<<password>>&command=26&onestep=0

Stop Scan: http://<<ipaddress>>:<<ipport>>/decoder_control.cgi?loginuse=<<username>>&loginpas=<<password>>&command=27&onestep=0

Many additional camera settings to try can be found at:

The vast majority of people have dedicated NVRs these days for recording their security cameras. Plus it is more favorable to view the live streams coming directly from the cameras. Under those conditions there is no need for the camera driver to constantly take snapshots of the cameras and store them locally. It's a waste of myServer's resources. You would only have to turn on polling if your camera does not provide a motion jpeg stream and it only allows one IP connection at a time. Under those condition then you'd need to poll.

From forum post:

Server variables will not automatically be deleted. You should do a DelVariable|video* and then restart myServer to clean them up.

Don't forget to edit the individual camera properties inside the Genericipcam driver. That's a place where cameras might be getting out of sync.

Using the GenericIPCam driver in Family manager add the cameras so they look like thisFamily Manager View
cam1.png (12.45 KiB) Not viewed yet
Then open the driver. You should see something like thisDriver View
cam2.png (16.17 KiB) Not viewed yet
Finally double click on the camera to edit the details.Camera Details
cam3.png (22.53 KiB) Not viewed yet
If the camera requires authentication enter the username and password. Otherwise you can leave off the ?user=<<username>>&pw=<<password>> bits in the following urls.

The two important fields are the Snapshot Image and Live Image.

The Snapshot image is for the static jpg image capture. Its url looks like
Note: cam1 is the camera name you gave the camera in your BlueIris settings. Make sure it matches your camera name.
This image is exposed in the {{video_<id>_image}} server variable.

The live image is for the motion jpeg live stream. Its url looks like
Again Note: cam1 is the camera name you gave the camera in your BlueIris settings. Make sure it matches your camera name.
This image is exposed in the {{video_<id>_liveimage}} server variable.

You would normally want to use the live image server variable on your scenes. However, if you have more than six cameras on your system you will run into browser limitations trying to view all the cameras on one page. Most browsers (Chrome, Safari) impose a limit of a maximum of 6 concurrent connections to a single web server at a time. If you try to view 8 motion jpegs from the same BlueIris server you'll only get to see 6 of them,

The workaround for this limitation is to switch to viewing the static image variable and then in the designer checking the reload box on the image properties. This tells the javascript to immediately reload a new image as soon the the current image is displayed. You'll still see motion just at a reduced framerate. I've been able to put up to 16 cameras on one page using this technique.

On a side note cameras these days boast incredibly high resolutions. More than is necessary for any casual viewing in a browser. I typically configure Blue Iris's web server encoder options to automatically scale down the image to make things a bit more efficient. Especially on network traffic. Here's an example of what I do. Use the best hardware acceleration option that is available on your Blue Iris PC.

Price $99.99