Tune Axis night-to-day dwell for temporary headlights

Bottom line: Set the night-to-day transition around the scene’s lighting behavior, rather than choosing the shortest possible switch for every camera.

Source fact: documented behavior

The DayNight API documentation defines dwell time as the number of seconds before the day/night algorithm makes a switch.

Its highway example explains that temporary headlights lasting longer than the night-to-day dwell can cause a switch to day mode and a return to night mode after the vehicle leaves.

What the source does not establish

Do not transfer a dwell value from the documentation’s example into a different scene without testing. Keep temporary passing light distinct from illumination intended to support a useful daytime view. Confirm the exact camera capabilities and channel settings before changing them. Do not present a stable transition as proof that the resulting recording provides the required investigative detail.

Applicability questions

• Which short-lived light sources enter this camera’s view at night?
• Should a passing light cause a mode change, or should the camera remain in its accepted night configuration?
• What sustained lighting condition should trigger the intended transition?
• Which recorded scene and task will the reviewer use to judge the result?

DSE recommendation: controlled next steps

The following steps are DSE recommendations based on the cited source.

DSE recommends a proposed transition test with both transient and sustained illumination cases.

1. Document the job of the affected view and the lighting events that matter to it. For a road-facing camera, distinguish passing headlights from a deliberate site-lighting change. Use site-approved representative inputs rather than creating unsafe traffic or glare. Record the current settings and the intended behavior before choosing a trial value.
2. In a noncritical pilot, observe a short illumination event and a longer illumination event under controlled, safe conditions. Mark the event times independently of the camera’s mode display. Adjust the documented dwell setting only through the supported interface and within the agreed change scope. Change one relevant setting at a time so a reviewer can attribute the observed difference to a known configuration.
3. Retrieve the recordings around both illumination events. Ask the recording owner to assess whether the transition behavior and usable detail meet the intended task. If the result is unacceptable, preserve the unsuccessful test and return to the last accepted configuration. Consider the scene’s lighting design with the responsible specialist instead of repeatedly changing timing until the live display merely appears calmer.

Verification and evidence

Keep the device and channel identity, software version, before-and-after settings, illumination-case description, event timestamps and retrieved recordings. Record mode transitions and the reviewer’s assessment separately; neither should substitute for the other. Note conditions that could not be represented safely during the pilot.

Repeat the proposed cases after a relevant lighting, camera-position or configuration change. Include an explicit disagreement case in the review: fewer mode changes but insufficient recorded detail should not automatically pass. All scenarios here are proposed DSE inputs and acceptance checks, not measured results or claims about a particular installed camera.

Official references

• DayNight API — Axis Communications; official VAPIX documentation.

Source review completed October 28, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.