Home Assistant ONVIF Camera Events Guide: Local Streams, Presence Context and Automation Review

August 17, 2026

ONVIF setup is often treated as a camera discovery task, but the useful outcome is usually an event that can be checked and routed into a household workflow. A driveway event might prepare a notification, while an occupied-room signal can decide whether a light or media action should be proposed.

This Guide focuses on the event layer after a supported camera is reachable. It does not replace the camera manufacturer's documentation or Home Assistant integration requirements. Check local network access, credentials, stream profiles and privacy boundaries before enabling automations.

What Camera Events Add to Home Assistant

Camera event

Identify the supported ONVIF event and its source camera.

Room context

Use Home Assistant area, presence and schedule context to reduce ambiguity.

Human review

Prepare a notification or device action and verify it before execution.

An ONVIF camera can provide an event or stream signal, while Home Assistant supplies the automation conditions and device actions. Adding presence context helps separate a camera event from an occupied room, an expected visit or a state that needs human review.

Before You Start

Confirm the camera and Home Assistant are on the intended local network.
Create a dedicated camera account with only the permissions required by the integration.
Record the camera area, event name, stream profile and expected state transition.
Decide whether the first result should be a notification, a light action or a saved event log.
Keep locks, alarms, access devices and other sensitive actions outside automatic execution.
Define what should happen when the camera, stream or presence sensor is unavailable.

Control note: Start with read-only review or a draft. Confirm recipients, dates, files, locations and smart-home devices before any external or sensitive action.

Build a Reviewable ONVIF Event Workflow

1. Choose the event

Start with one supported event such as motion, line crossing or a device-state change.

2. Verify the local stream

Confirm the camera address, port, credentials and stream profile independently of automation.

3. Assign the Home Assistant area

Place the camera and related devices in the intended area so the workflow has room context.

4. Map the event entity

Check the entity ID and state transition exposed by the ONVIF integration.

5. Add presence context

Use eMotion Air, eMotion Pro or eMotion Ultra only when occupancy should change the decision.

6. Add a time or schedule guard

Limit the first test to a defined time window instead of enabling an all-day action.

7. Prepare one low-impact response

Start with a notification, event log or one light rather than a multi-device scene.

8. Request an automation preview

Use LinknLink App Agent+ or Home Assistant tools to show the trigger, conditions and action before approval.

9. Test expected and unexpected states

Compare an event in an occupied room, a vacant room and an unavailable-sensor state.

10. Add appliance control last

If an IR appliance is involved, test a compatible eRemote HA command separately before linking it to the camera event.

Example Prompts and What to Review

Use case	Example request	Review before action
Driveway notification	When the supported driveway event appears, prepare a notification with the camera name and timestamp.	Camera, event, recipient and notification scope
Occupied-room guard	When a camera event appears in an occupied room, prepare a light action but show it before running it.	Area, presence state and light entity
Vacant-room review	When the camera event occurs while the room is vacant, create a review item instead of starting a scene.	Vacancy state, delay and fallback
Office schedule	During the office schedule, prepare one desk-light action for a supported event and keep it reversible.	Schedule, event and light
Media pause proposal	If a camera event and occupancy transition happen together, propose a media pause and show the target player.	Event order, player and approval
IR action after review	After the camera event is verified, prepare one compatible IR command through eRemote HA.	IR target, command, room and manual override

Prompt pattern: State the goal, define the permitted scope, add constraints, name prohibited actions and request a preview before execution.

Use Read, Prepare, Approve and Execute Stages

Stage	Agent task	User control
Read	Inspect only the permitted source.	Choose the app, date range, room, folder or account.
Prepare	Extract entities and build a draft or proposed plan.	Check assumptions, missing information and affected resources.
Approve	Present the action and destination.	Confirm or revise before execution.
Execute	Run the supported action after approval.	Verify the result and keep a reversal path when possible.

Review Checklist

Is the camera event from the intended device and area?
Does the local stream remain available when the event is received?
Are credentials and camera permissions limited to the required integration?
Does presence context change the action only when it should?
Are vacant, unavailable and duplicate-event states defined?
Is the first response easy to observe and reverse?
Are sensitive devices excluded from silent execution?
Does the Home Assistant automation match the preview shown before approval?

Privacy, Permissions and Safer Defaults

Cross-app tasks can touch personal communications, calendars, files, photos, locations and household devices. Grant the smallest useful permission, keep unrelated data out of scope and avoid sharing credentials, passwords, one-time codes or private account details.

Use drafts for messages and attachments. Use scene previews for smart-home changes. Keep purchases, access control, security devices and destructive file actions behind explicit human confirmation.

Troubleshooting

The camera is discovered but no event arrives

Confirm the event profile, integration entity, camera permissions and local network path separately.

The stream works but the automation is wrong

Check the event entity ID and state transition rather than relying on the display name.

The event fires repeatedly

Review duplicate listeners, event cooldown and automation mode before adding more conditions.

Presence changes the wrong action

Check the Home Assistant area and sensor entity, then test occupied and vacant states independently.

The camera becomes unavailable

Define a fallback notification or hold state; do not treat an unavailable camera as a confirmed event.

The Agent proposes too much

Split the workflow into read, prepare, approve and execute stages, starting with one reversible response.

Frequently Asked Questions

Can Home Assistant use ONVIF camera events locally?

Supported cameras and integrations can expose local event or stream data when the network, profile and credentials meet the integration requirements. Verify the exact camera model and integration behavior.

Why add a presence sensor to an ONVIF automation?

Presence can add room context so an event is evaluated alongside occupancy, schedule or vacancy state instead of triggering the same action in every situation.

Does this Guide replace ONVIF installation instructions?

No. Use the camera and Home Assistant integration documentation for discovery, credentials, ports and profiles. This Guide covers event routing and automation review after the connection is available.

What should the first camera action be?

Start with a notification, event log or one light action that is easy to observe and reverse. Add climate, media or IR control after the event path is stable.

Can Agent+ prepare the Home Assistant automation?

When the relevant LinknLink App and Home Assistant capabilities are available, Agent+ can help organize the goal and show a proposed handoff. Review entities and actions before approval.

Can an ONVIF event control an air conditioner?

Only through a compatible appliance-control path such as eRemote HA and a supported Home Assistant integration. Test one IR command independently and keep a manual override.

Start with One Event and One Reversible Action

Choose one supported camera event, verify the local stream and prepare one notification or light action. Review the proposed automation before adding presence rules or appliance control.