DOMOCAM Integration (HQVT Monitoring)
The DOMOCAM integration connects ACCELERO to DOMOCAM cameras with facial recognition. The devices identify people, and ACCELERO receives these events in real time, records them, generates access logs, and triggers notifications (pop-up, e-mail, Telegram, and MQTT) according to the event type and the camera's alert level.
This integration is provided as a plugin (hqvt, internally identified as HQVT) and must be installed and enabled by the IONGRADE technical team. Contact support to check compatibility with your ACCELERO version.
Current plugin version: 2.1.0 β compatible with ACCELERO 2.17.0 or higher.
What the integration doesβ
With the plugin active, the DOMOCAM cameras begin to communicate with ACCELERO. The system synchronizes people's facial templates to the devices and receives back the recognition events, transforming them into access records and logs.
| Feature | What happens in ACCELERO |
|---|---|
| Device registration | Each DOMOCAM camera is registered as a device with IP, port, credentials, communication gateway, and associated area |
| Facial template synchronization | People's photos (according to the configured categories) are sent to the cameras for recognition |
| Event reception | Known person, blocked person, and unknown person are received and stored as DOMOCAM events |
| Access log generation | Each recognition event generates an access log in ACCELERO, passing through the access verification rule |
| Real-time monitoring | A monitor screen that displays events as they arrive, with the captured image |
| Notifications | Pop-up to the operator, e-mail, Telegram, and MQTT, filtered by event type and alert level |
| Last seen | Records in the person's registration the time and the device of the last identification |
It turns DOMOCAM facial recognition cameras into access control points integrated with ACCELERO, with centralized logs, monitoring, and alerts.
Configurationβ
Navigation path: Settings > DOMOCAM

The screen is organized into tabs: Facial recognition, Gateways, Settings, Synchronize templates, and Clear storage.
Settings tabβ
Defines the notification and storage behavior.

| Field | Description |
|---|---|
| Which event should generate an alert Pop-up? | Multi-selection of the event types that generate an alert pop-up to the operator: Access allowed, Access blocked, and Access denied |
| Do you want to receive notifications on Telegram? | Enables sending notifications via Telegram |
| Do you want to receive notifications by e-mail? | Enables sending notifications by e-mail |
| Do you want to receive notifications by MQTT? | Enables publishing notifications via MQTT on the topic `{FACILITY}/io/domocam/{DEVICEID}/{known,unknown,blocked}` |
| Categories | Categories of people whose facial templates are synchronized with the devices |
| Categories for automatic removal | Categories whose templates are automatically removed from the devices |
| Automatic removal exception | Categories that are left out of automatic removal |
| Size of the space reserved for DOMOCAM images (MB) | Disk space reserved for the images captured by the events |
When the storage limit is reached, the system automatically removes the oldest image when saving a new one, keeping disk usage under control.
Synchronize templates tabβ
Allows manually sending the facial templates to the selected devices.

| Button | Function |
|---|---|
| Test template sending | Counts how many templates would be sent, without sending them (dry-run) |
| Resend templates | Synchronizes the facial templates of the eligible people to the selected devices |
| Delete all | Deletes all facial registrations from the selected devices |
Clear storage tabβ
Deletes all images stored by the DOMOCAM events.
The storage cleanup cannot be undone. The button requires captcha confirmation before executing.
Registering DOMOCAM devicesβ
Navigation path: Settings > DOMOCAM, Facial recognition tab
Each DOMOCAM camera is registered as a device. The list allows creating, editing, searching, and deleting devices.

The inclusion form (New device button) asks for description, IP, port, gateway, user, password, and Device ID. Location, alert level, Update area, and Synchronize only the categories are on the device edit screen.
Device fieldsβ
| Field | Description |
|---|---|
| Description | Identification name of the device |
| Active | Defines whether the device is active (only active devices synchronize templates) |
| IP address | IP of the DOMOCAM camera |
| Port | Communication port |
| Gateway | Communication gateway responsible for mediating the message exchange with the camera |
| User | Access user for the camera |
| Password | Access password (leave blank to not change existing data) |
| Device ID | Identifier of the device on the DOMOCAM camera |
| What is the location of the DOMOCAM? | Area associated with the device β used for the access log and updating the person's location |
| What is the desired alert level? | Alert level of the camera: Light alert level, Medium alert level, or High alert level. It is used to filter which operators receive notifications |
| Update area | Switch shown on the device record. See the note below about the behavior in version 2.1.0 |
| Synchronize only the categories | Restricts template synchronization to specific categories on this device |
The DOMOCAM camera communicates with ACCELERO through a gateway (configured on the Gateways tab). Register the gateway before associating it with the device.
Fields added to the entitiesβ
The plugin extends the Person registration and the Operator registration with DOMOCAM-specific data.
Personβ
In the person registration, the plugin adds the field:
| Field | Description |
|---|---|
| DOMOCAM - Person status | Allowed or Blocked. Defines whether the person is treated as blocked in the DOMOCAM recognition |

Operatorβ
In the operator registration, the plugin adds the Domocam section:
| Field | Description |
|---|---|
| Telegram user | Telegram user (@) that receives the notifications |
| What is the desired alert level? | Multi-selection of the alert levels (light, medium, high) that the operator wants to receive by e-mail/Telegram |

An operator only receives the notification of a camera if the alert level configured on the camera is among the levels that the operator selected in their registration.
DOMOCAM Monitorβ
Navigation path: Logs > Monitor DOMOCAM
Monitoring screen that displays the recognition events as they arrive, in real time.

How it worksβ
- Click Monitor to start receiving events in real time. The button changes to Stop monitoring.
- Each new event appears at the top of the list with the data and the images: the person's registration photo and the image captured by the camera, side by side. The list keeps the last events received.
- Blocked person events are highlighted in red; unknown person events, in yellow.
Filtersβ
The filters are under the Filters... button.
| Filter | Description |
|---|---|
| Devices | Filters by one or more DOMOCAM cameras |
| Event Type | Filters by recognition event type |
The Save filters button stores the filter preference in the browser, so that it is reapplied on the next visit.
Data displayed per eventβ
Event type, time, similarity, name, device name, and the captured image.
DOMOCAM Logβ
Navigation path: Logs > Log DOMOCAM
Complete history of all DOMOCAM events received, with filters (Search button) and detailing.

Filtersβ
| Filter | Description |
|---|---|
| Group | Recognition event type |
| Devices | One or more DOMOCAM cameras |
| Person name | Search by the person's name |
| Start date/time and End date/time | Selection by period |
Columnsβ
Date and time, type, metadata (serialized event data), and actions.
Event detailingβ
When opening an event, ACCELERO displays: event type, time, similarity, name, device name, person ID, and the captured image.
Event typesβ
DOMOCAM cameras send different event types. ACCELERO classifies them as follows:
| Type (label on the screen) | Meaning |
|---|---|
| Known person | Person recognized and with access allowed |
| Blocked person | Person recognized, but marked as blocked |
| Unknown person | Capture of a face not identified in the registration |
The cameras also send keep-alive (heartbeat) messages to signal that they are online. These signals are recorded as events of the HeartBeat type, but they do not generate an access log or a notification.
How events become access logsβ
When a DOMOCAM camera recognizes a person, ACCELERO automatically generates an access log:
- The system identifies the person from the data sent by the camera.
- If the person is not found in the registration, the Access denied - Unknown DOMOCAM person log is generated.
- If the person is found, ACCELERO applies the access verification rule to the device's area:
- Access authorized β generates the Access authorized - DOMOCAM log and updates the person's current area to the camera's area.
- Access not authorized β generates the log with the corresponding denial code.
In the current plugin code, the person's current area is updated on every authorized access, even with the Update area switch turned off on the device. Keep this in mind when placing cameras in areas that should not change occupancy.
The DOMOCAM device is treated as a virtual control channel: the area associated with the camera is used as the access destination, and the verification follows the same ACCELERO access rules.
Notificationsβ
For each eligible event, the plugin can trigger notifications through different channels. The sending depends on the options enabled on the Settings tab and on the filter by event type and alert level.
| Channel | When it triggers |
|---|---|
| Pop-up | For the event types marked in "Which event should generate an alert Pop-up?" |
| When enabled; sent to the operators whose alert level matches that of the camera | |
| Telegram | When enabled; sent to the operators with Telegram configured |
| MQTT | When enabled; published on the topic `{FACILITY}/io/domocam/{DEVICEID}/{known,unknown,blocked}` |
Example of the notification e-mail "Security event detected DOMOCAM!" received by an operator. Pending: in version 2.1.0 the generated body comes out with an empty Device name (the plugin looks the device up by its name instead of its ID) and with a leftover %%MESSAGE%% placeholder at the end.
Configure critical cameras with a high alert level and, in the operators' registration, select which levels each one should receive. This way, an event from a high-risk camera only notifies those who need to be alerted.
Use casesβ
Enable a DOMOCAM cameraβ
- Request the installation of the
hqvtplugin from IONGRADE. - In
Settings > DOMOCAM, register the communication gateway. - On the Facial recognition tab, register the camera (IP, port, credentials, Device ID, area, and alert level).
- On the Settings tab, select the categories whose people should be recognized and adjust the notifications.
- On the Synchronize templates tab, use Test template sending and then Resend templates.
- Track the DOMOCAM Monitor to validate the arrival of the events.
Investigate a denied accessβ
- Access DOMOCAM Log and filter by the person and the period.
- Open the event to see the type, similarity, device, and the captured image.
- Check whether the person is in the registration, linked to a synchronized category, and whether the area's access rule allows entry.
Track the entrance in real timeβ
- Open DOMOCAM Monitor and click Monitor.
- Optionally, filter by devices and event types and save the preference.
- Track the recognitions: blocked (red) and unknown (yellow) get highlighted.
Best practicesβ
- Specific categories: synchronize only the categories of people who should be recognized by the cameras, avoiding sending unnecessary templates to the devices.
- Gateway before the device: register and validate the communication gateway before associating the camera.
- Test before the actual send: use Test template sending (dry-run) before synchronizing the templates for real.
- Consistent alert levels: standardize the use of levels (light/medium/high) between cameras and operators so that the notifications reach those who need them.
- Storage control: adjust the size of the space reserved for images according to the event volume, remembering that the oldest images are removed when the limit is reached.
Troubleshootingβ
Events do not appear in the Monitorβ
Possible causes:
- Communication gateway offline or misconfigured
- Device inactive or with incorrect IP/port/credentials
- Browser incompatible with real-time monitoring
Solution:
- Check the gateway status on the Gateways tab.
- Confirm the IP, port, user, password, and Device ID in the device edit screen.
- Confirm that the device is Active.
Recognitions do not generate an access logβ
Possible causes:
- The person is not in the ACCELERO registration (generates "Access denied - Unknown DOMOCAM person")
- The person is not linked to a synchronized category
- The area's access rule denies entry
Solution:
- Confirm the person's registration and the category link.
- Check the area associated with the device and the access rule of that area.
- Resend the templates via the Synchronize templates tab.
Operator does not receive notificationsβ
Possible causes:
- Notification channel (e-mail/Telegram/MQTT) disabled on the Settings tab
- The camera's alert level is not among those selected by the operator
- The event type is not marked to generate a pop-up
Solution:
- Check the notification switches on the Settings tab.
- Check the camera's alert level and the levels selected in the operator's registration.
- For the pop-up, confirm the event type in "Which event should generate an alert Pop-up?".
Integration with other modulesβ
People and Categoriesβ
Template synchronization depends on the registration of People (with a facial photo) and on the category configuration. Only people of the selected categories have their templates sent to the cameras.
Areasβ
Each device is associated with an Area, which defines the access destination and can be updated as the person's current location when the recognition occurs.
Logs and Eventsβ
Each recognition generates an access log. See Logs and Monitoring to understand how these events appear in the access history.
Next Stepsβ
- People β Register the people with a facial photo and the DOMOCAM status
- Areas β Associate each camera with a destination area
- Logs and Monitoring β Track the logs generated by the recognitions
- Plugins β Learn more about ACCELERO's plugin system