Skip to content

Releases

DirectorLink · Hikvision 1.1.2

Choose a tag to compare

@github-actions github-actions released this 10 Oct 17:10
Immutable release. Only release title and notes can be modified.

DirectorLink · Hikvision 1.1.2

Free, open-source Control4 driver for Hikvision IP cameras and NVRs. Part of DirectorLink Drivers.

DirectorLink is an independent project, not affiliated with Control4 or Snap One.

Update both files with Driver → Add or Update Driver or Agent. Keep the file names exactly as they are: a browser's (1).c4z copy installs as a separate driver. Check the downloads against SHA256SUMS.txt.

Camera

  • New string variable DIRECTORLINK_CAMERA_EVENTS = Alert=1: the id of the Alert event, so DirectorLink finds the camera's alerts without reading driver.xml. It comes after the existing variables (their order never changes) and is set on every start, like DIRECTORLINK_CAMERA and DIRECTORLINK_CAMERA_KIND.

Hub

  • No changes apart from the version number.

DirectorLink · Hikvision 1.1.1

Choose a tag to compare

@github-actions github-actions released this 05 Oct 19:54
Immutable release. Only release title and notes can be modified.

DirectorLink · Hikvision 1.1.1

Free, open-source Control4 driver for Hikvision IP cameras and NVRs. Part of DirectorLink Drivers.

Update both files with Driver → Add or Update Driver or Agent. Keep the file names exactly as they are: a browser's (1).c4z copy installs as a separate driver. Check the downloads against SHA256SUMS.txt.

Hub

  • A refused login is tried again. A device that refused the login (for example an NVR still starting after a firmware upgrade) is tried once more after 15 minutes, and at once when you run Search Network or enter the password again (even the same one). Before, the hub stopped trying until the driver restarted.
  • Status clears as soon as the login works again (it used to keep showing "Login failed").

Camera

  • A refused login is tried again after 15 minutes, and at once when the same password is entered again on the camera's Properties page or sent by the hub.
  • After a reboot (for example a firmware upgrade), the camera driver reads the camera again, so Camera shows the new firmware and Video the current streams.

Lockout protection stays: a wrong password costs one attempt, then at most one more every 15 minutes, far below the cameras' lockout limits.

DirectorLink · Hikvision 1.1.0

Choose a tag to compare

@github-actions github-actions released this 05 Oct 19:06
Immutable release. Only release title and notes can be modified.

DirectorLink · Hikvision 1.1.0

Free, open-source Control4 driver for Hikvision IP cameras and NVRs. Part of DirectorLink Drivers.

Update both files with Driver → Add or Update Driver or Agent. Keep the file names exactly as they are: a browser's (1).c4z copy installs as a separate driver. Check the downloads against SHA256SUMS.txt.

Camera

  • DirectorLink camera agreement v1. The camera driver sets the variables DIRECTORLINK_CAMERA = 1 and DIRECTORLINK_CAMERA_KIND = camera on every start, also after a driver update. They come after the existing variables, so existing programming is not affected. From DirectorLink 1.10 the app recognizes the cameras this way; DirectorLink 1.8 and 1.9 still recognize them by file name.
  • LAST_ALERT only carries the agreement's labels: Person, Vehicle, Face, Motion, Line Crossing, Intrusion, Region Entrance, Region Exiting, Tamper, Scene Change, Object Left, Object Removed, Alarm Input, PIR, Animal, Package, License Plate. The Alert event, LAST_ALERT (set just before Alert fires) and the rules for when Alert fires (Alert On, the hub's switch, snooze, hold time) are unchanged.
  • More Hikvision detections go to the nearest one: loitering → Intrusion, people gathering → Person, fast moving → Motion, parking and vehicle detection → Vehicle, license plate recognition → Vehicle with the alert label License Plate, defocus → Tamper. Animal, package and license plate targets give those alert labels.
  • The Last alert is condition also offers Animal, Package and License Plate.

Hub

  • No changes apart from the version number.

DirectorLink · Hikvision 1.0.6

Choose a tag to compare

@github-actions github-actions released this 04 Oct 17:53
Immutable release. Only release title and notes can be modified.

DirectorLink · Hikvision 1.0.6

Free, open-source Control4 driver for Hikvision IP cameras and NVRs. Part of DirectorLink Drivers.

Update both files with Driver → Add or Update Driver or Agent. Keep the file names exactly as they are: a browser's (1).c4z copy installs as a separate driver. Check the downloads against SHA256SUMS.txt.

Hub

  • Check For Updates works again. The project moved to the DirectorLink organisation on GitHub, and the hub now asks the new address. If the project moves again, the check follows GitHub's redirect instead of failing. Only matters if you turned on Check For Updates (off by default).

Camera

  • No changes apart from the version number.

DirectorLink · Hikvision 1.0.5

Choose a tag to compare

@github-actions github-actions released this 04 Oct 17:17
Immutable release. Only release title and notes can be modified.

DirectorLink · Hikvision 1.0.5

Free, open-source Control4 driver for Hikvision IP cameras and NVRs. Part of DirectorLink Drivers.

Update both files with Driver → Add or Update Driver or Agent. Keep the file names exactly as they are: a browser's (1).c4z copy installs as a separate driver. Check the downloads against SHA256SUMS.txt.

Snapshots

  • Pictures at the size each screen asks for. A grid tile or a touchscreen tile that asks for 320 px now gets a 320 px picture from the camera, a few KB instead of a full-size JPEG. Full screen still gets the whole picture. The driver tests once per camera whether it can scale pictures, and keeps the old behaviour if it can't.
  • Lighter notification pictures: 1280 px wide when the camera can scale them, else the sub stream picture (640 px, a few dozen KB) instead of a 4K picture of over 1 MB. Notifications arrive faster.
  • Setup Report and Test Snapshot show the real picture sizes, and whether the camera can scale pictures (and if not, whether it ignores or refuses the request).

NVRs

  • Dead NVR channels are not added. Add New Cameras skips NVR channels whose camera is disconnected; Found On Network counts them, and they are added once they reconnect.
  • H.264 waits for the camera. On an NVR channel whose camera is offline, the automatic switch to H.264 now waits until the camera is back, instead of logging an error.

Hub

  • Older camera driver notice clears by itself once every camera runs the same version as the hub (updating the hub first no longer leaves a stale message).
  • Check For Updates (off by default): once a day the hub asks GitHub for the latest release and shows it next to Driver Version. Nothing about the home is sent.

Privacy

The driver talks only to the Hikvision cameras and NVRs on your home network, and to GitHub once a day if you turn on Check For Updates. It sends nothing to DirectorLink and collects no usage data.

DirectorLink · Hikvision 1.0.2

Choose a tag to compare

@github-actions github-actions released this 04 Oct 04:28
Immutable release. Only release title and notes can be modified.

DirectorLink · Hikvision 1.0.2

First release. Add one driver, type the camera login once, click Add New Cameras, and every Hikvision camera on the network is in Control4, named and ready.

Free, open-source Control4 driver for Hikvision IP cameras and NVRs. Part of DirectorLink Drivers.

Files

Driver in Composer File
DirectorLink · Hikvision (shows in the project as Hikvision Hub) DirectorLink-Hikvision.c4z
DirectorLink · Hikvision Camera DirectorLink-Hikvision-Camera.c4z

Check the downloads against SHA256SUMS.txt. Keep the file names exactly as they are: a browser's (1).c4z copy installs as a separate driver.

Hikvision Hub

  • Finds everything by itself. Hikvision SADP discovery finds every camera and NVR on the network with its model, address and HTTP port, including NVRs on non-standard ports. Cameras on other subnets go in Extra Camera IPs.
  • One click adds them all. Each camera is added in the hub's room; then drag them to their rooms.
  • One login. The hub fills in every camera's Properties page (address, ports, Digest login) and channel. A login change is sent to every camera, and a camera that loses its login gets it again by itself.
  • Real names. A camera keeps its existing Control4 name (when replacing another driver), else takes its NVR channel name, else the name shown on its video. Model and IP are a last resort. Update Camera Names renames cameras already added.
  • Login checked first. A wrong password never adds cameras. The hub's Status names every device that refused the login.
  • NVR aware. Cameras reachable only through the NVR are added as NVR channels; the rest connect directly. An NVR channel whose camera is disconnected shows as offline.
  • Ignored Cameras: cameras or NVR channels that Add New Cameras should skip.
  • Video that plays: Control4 plays H.264 only, so with Sub Stream To H.264 on Automatic (the default) every camera the hub adds switches its sub stream to H.264. The main stream is not touched. Set All Sub Streams To H.264 does the same for cameras already added.
  • One alerts tile for the home: alerts on, alert, alerts off or snoozed, camera offline, working. Tap it to turn alerts on or off everywhere.
  • One Camera Alert event for all cameras, with LAST_ALERT_CAMERA, LAST_ALERT_TYPE and a snapshot from the alerting camera.
  • Plain-language Status, Cameras (online, offline, disabled, no H.264 video) and Found On Network.

Hikvision Camera

  • One place for settings: address, ports and login are on Control4's camera Properties page, like every Control4 camera. Advanced Properties adds only Camera Enabled and Channel.
  • Camera Enabled = No for a camera that is off or removed: no requests, events or offline alarms, and the hub stops counting it.
  • Video: the H.264 stream that fits each screen; the RTSP port is read from the camera. Control4 cannot play H.265, so Set Sub Stream To H.264 switches the sub stream and leaves the main stream for recording. Snapshots fall back to the main stream when the sub stream gives none.
  • Real-time detections: motion, person, vehicle, line crossing, intrusion, region entrance/exit, tamper, scene change, face, object left/removed, alarm inputs, PIR.
  • Detections and alerts: detections always run automations. Alert (notifications, snapshot, History) follows Alert On (any detection, people and vehicles, people only), the camera's and the hub's alerts switches, and snooze.
  • Controls in the camera view: alerts, alert on, snooze for 1 hour, motion detection, day/night, light (ColorVu and hybrid-light cameras), reboot.
  • Attention line: says when the camera needs an H.264 stream, gives no snapshot, has no detection that notifies Control4, or when the Properties page needs a manual touch.
  • Lockout-safe: a wrong password costs one login attempt. Requests to a device go one at a time, so overlapping Digest logins can't look like a wrong password.

Installing

  1. Upload both files with Driver → Add or Update Driver or Agent.
  2. Search DirectorLink, add DirectorLink · Hikvision, enter the camera login, and run Add New Cameras.
  3. On the cameras: tick Notify Surveillance Center on each detection.

Requirements: Control4 OS 3.2 or newer, Composer Pro. Full steps: directorlink.io/drivers/hikvision.

Known issues

  • Tested on one system (Control4 OS 4.2.4, Hikvision G2 cameras and a K-series NVR). Please report what works and what doesn't on other models, firmware and OS versions.
  • Properties page update: if Control4 does not accept the automatic update of a camera's Properties page, the camera's Attention line lists the values to enter by hand once.
  • H.265: Control4 cannot play it. Some NVRs may refuse the H.264 change for their channels; then set it on the camera's web page.
  • HTTPS: when the camera page uses HTTPS, the live event stream still uses the HTTP port.
  • People and vehicle alerts need AcuSense (human/vehicle) cameras.
  • NVR channel cameras each open their own event connection to the NVR.
  • Notification snapshots of the URL type depend on the notification agent's Digest support and are untested.

For developers

  • The shared engine in src/common/ (XML, Digest/Basic login with a one-failed-login guard, an ISAPI client that sends one request at a time per device) is built into both drivers by tools/build.py.
  • Hub ↔ camera messages over C4:SendToDevice: DL_CONFIGURE, DL_HUB_ALERTS, DL_HUB_HELLO, DL_FIX_SUBSTREAM, DL_CAMERA_STATUS, DL_CAMERA_ALERT.
  • tests/ runs the real drivers in Lua 5.1 against a stubbed Control4 API, with Digest checked by RFC 2617 math.