The event reaches the right person, through the right channel
Notifications and integration
ProVife delivers events with images to a WhatsApp group, to email, to the operator screen and to an MQTT broker; it also turns messages coming from Home Assistant and MQTT into its own alarms and scenarios.
The value of an event is measured by how quickly someone responds to it. ProVife Notifications and integration delivers the results of analytics rules, store reports and building scenarios to the channels your team already uses. The WhatsApp account is connected with a QR code, and alarms go to the selected group with images showing the rule area and target box. Email is sent over SMTP with a certificate-verified connection. The operator screen has a bottom alert bubble, an alarm window and notification history. The MQTT integration publishes events as structured JSON to building automation and production systems, and turns messages from monitored topics into alarms. Home Assistant is used to call light, relay and siren services.
The channel your team uses
Alarms with images land in a WhatsApp group; your team does not need to learn a new tool.
Notifications that carry the evidence
Every image shows the rule area and the target box; the event is clear at a glance.
Open integration
Building automation, production and other systems connect to ProVife events via MQTT and Home Assistant.
Resilient to outages
When the connection drops, messages are queued and the connection is re-established at increasing intervals.
WhatsApp notifications
The WhatsApp account is connected by scanning the QR code in the ProVife settings screen with a phone. Once connected, groups are listed and you select the group that receives alarms. Each alarm is sent with the event image showing the rule area and target box, along with a description containing the rule’s own text, the camera, event and time. Because the connection runs in a separate process, network or account problems do not affect recording and analytics.
- Account linking with a QR code
- Target group selection from the group list
- Event image with marked target and description
- Per-minute sending limit
- Connection process separate from recording and analytics
Email notifications are sent through the configured SMTP server using STARTTLS or SSL, and the server certificate is verified. Settings are tested with a delivery test before saving. The SMTP password is stored on the server and is never returned in any response. The Store Analytics daily report is also sent with this setting, with PDF and Excel attachments. The recipient list is kept in the notification settings; different recipients can be defined for store reports. This way, security alarms and business reports reach the right teams separately.
- SMTP, STARTTLS or SSL
- Certificate-verified connection
- Delivery test
- Password never returned in responses
- Reports sent with PDF and Excel attachments
Alarms on the operator screen
The ProVife client shows alarms as an alert bubble with a thumbnail at the bottom of the screen, an alarm window that opens the related camera, and an action notification history. Sounds are mapped by alarm type. Notification preferences are kept separately on each client, so the control room screen and the manager’s desk can behave differently. The notification thumbnail is marked with the rule area and target box; the operator understands the event without opening the recording and can jump to the recording with one click if needed.
- Bottom alert bubble with thumbnail
- Alarm window that opens the camera
- Action notification history
- Sounds by alarm type
- Per-client notification preferences
MQTT
The MQTT integration publishes events to an MQTT broker. All analytics events, or only warning and critical alarms, are sent as JSON to topics separated by camera and event type; the message includes the time, analytic name, severity, camera, scenario and values. ProVife’s online status is published as a retained message on a separate topic. Messages from monitored topics become ProVife alarms and trigger Smart Home scenarios.
- Topic structure: prefix/events/camera/event type
- All events or alarms only
- Online and offline status topic
- Monitored topics with wildcards
- TLS, username and password, QoS 0 and 1
Home Assistant
Your own Home Assistant server connects with an access token. On ProVife events, services are called on the selected entities: lights turn on, relays switch, sirens sound. In the other direction, when monitored entities reach a target state, for example when a door sensor opens, a ProVife alarm is created. The access token is stored on the server and returned to the screen masked. The connection runs in a separate process; if the Home Assistant server cannot be reached, recording and analytics are not affected.
- Connection with an access token
- Service calls on events
- Alarms from entity states
- Text-to-speech and volume on speakers
- Access token stored masked
Event reports
Notification channels are complemented by reports. On the AI Monitoring screen, the selected camera’s scenario is watched live and a PDF report can be generated. On the AI Playback screen, a PDF with images is prepared from selected events; images come from the actual event frames with the target marked. Store Analytics reports, plate passes and under-vehicle scanning reports are produced by the same server, and every report is written to the audit log.
- AI Monitoring PDF report
- Event report with images and marked targets
- Store Analytics PDF and Excel reports
- Under-vehicle scanning PDF report with images
- Reports written to the audit log
Technical specifications
| QR code connection, single group, image alarms | |
| WhatsApp sending limit | Adjustable from 1 to 30 messages per minute |
| SMTP, STARTTLS or SSL, certificate verification | |
| MQTT version | MQTT 3.1.1, QoS 0 and 1, TLS |
| MQTT event topic | <prefix>/events/<camera>/<event type>, JSON |
| MQTT status topic | <prefix>/status, online and offline |
| MQTT reconnection | Interval increasing from 2 to 60 seconds, queue of up to 1,000 messages |
| Home Assistant | Access token, service calls, alarms from entity states |
| Operator screen | Alert bubble, alarm window, notification history |
Frequently asked questions
Is a separate account needed for WhatsApp notifications?
The connection is set up by scanning a QR code with a phone. For automated sending, we recommend using a separate number and a group made up only of the relevant people.
What information is sent via MQTT?
The event time, analytic name, severity, camera, scenario and values are sent as JSON. Images are not included in the MQTT message; the event image is available within ProVife.
Can a signal from an external system become an alarm in ProVife?
Yes. When the expected value arrives on a monitored MQTT topic, or a monitored Home Assistant entity reaches its target state, a ProVife alarm is created. This alarm appears in notifications and on the AI Playback screen, and triggers scenarios.
Are notifications lost if the internet goes down?
When the MQTT connection drops, messages are held in a limited queue and sent once the connection is restored. WhatsApp alarms are held for a short time; daily reports wait for the connection for hours and are retried.