# Separate Axis light enablement from an activation request > Check Axis light enablement and actual on/off state separately. A disabled light cannot be activated, and an enabled capability is not itself an observed illumination result. - Canonical URL: https://update.dsesecurity.com/updates/separate-axis-light-enablement-from-an-activation-request/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-10-29T19:49:57+00:00 - Modified: 2026-10-29T19:50:08+00:00 - Last reviewed by DSE: 2026-10-29 - Resource type: Guide - DSE priority: Advisory - Topics: Video Surveillance - Reading time: 3 minutes ## What you need to know Check Axis light enablement and actual on/off state separately. A disabled light cannot be activated, and an enabled capability is not itself an observed illumination result. ## Potentially affected Axis products exposing the documented Light control interface; confirm actual device, hardware and software applicability before applying the proposed checks. ## DSE recommendation DSE recommends diagnosing enablement and activation separately before changing the light’s operational policy. ## Article Bottom line: Check whether a light is enabled before retrying an activation request. Keep the configured permission to use the light, its reported on/off state and the observed scene as distinct checkpoints. ## Source fact: documented behavior Axis’s [Light control](https://developer.axis.com/vapix/network-video/light-control/) exposes separate operations to enable or disable light functionality and to activate or deactivate a light. The enable and disable examples state that a disabled light cannot be switched on; the activation error list includes LIGHT_DISABLED_FAULT. In the information response, enabled reports enablement, while lightState reports whether the light is on or off. ## What the source does not establish Do not equate an enabled value with illuminated coverage or useful recorded detail. Do not bypass a deliberately disabled light merely to clear an error. Confirm the exact device, light identifier and approved illumination policy; leave electrical and environmental limitations with the product documentation and responsible installer. ## Applicability questions - Which actual light ID and type belong to the requested operation? - Was light functionality intentionally disabled by the owner? - What enablement and on/off state does the device currently report? - Which permitted observation will confirm the intended illumination and recorded view? ## DSE recommendation: controlled next steps The following steps are DSE recommendations based on the cited source. DSE recommends diagnosing enablement and activation separately before changing the light’s operational policy. - Read the relevant supported light information and match the identifier to the installed function. Record enablement, reported state and the owner’s intended policy. Preserve any diagnostic error with the attempted operation. If the light is deliberately disabled, resolve the business or installation reason before proposing an enablement change; do not repeatedly activate it as a substitute for that review. - Prepare an authorized pilot using a supported light and an appropriate observation window. Record the previous state and the intended end condition. Apply only the separately approved enablement or activation action needed for the case, then read the reported state again. Keep the activation response separate from the observation of the light itself. - Have the operator inspect the relevant scene and recording through the normal approved workflow. If a reported on state does not produce the required view, investigate the installed illumination and imaging arrangement rather than treating the enablement flag as acceptance. Restore the agreed policy after the exercise and document any intentionally different automatic or manual operating arrangement separately. ## Verification and evidence Retain the device/light identity, intended policy, sanitized requests and responses, reported enablement and state, and the permitted scene observation. Ask a reviewer to identify which evidence established each checkpoint. Do not broaden access or alter other lights simply to obtain a successful response. Use a proposed desk case with a disabled light and a rejected activation. Require the reviewer to seek the owner’s policy decision before enabling it. Treat actual illumination quality as a separate result to collect, not as an outcome established by this article or by the absence of an API error. ## Official references - [Light control](https://developer.axis.com/vapix/network-video/light-control/) — Axis Communications; official VAPIX documentation. Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings. ## Primary reference - Name: Axis Communications — Light control - Authority: Axis Communications - URL: https://developer.axis.com/vapix/network-video/light-control/ - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Separate Axis light enablement from an activation request,” DSE Security, https://update.dsesecurity.com/updates/separate-axis-light-enablement-from-an-activation-request/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.