Understanding MxMessages of NurseAssist: Events, Payload Structure and Default Profiles

[Mx-PhilippH]

About

This article explains how the Kepler NurseAssist App on the MOBOTIX c71 smart sensor generates and uses local MxMessages for event handling.

It provides an overview of:

• how NurseAssist events trigger MxMessages
• the structure and content of the JSON payload
• available notification types
• and the default preconfigured camera event profiles associated with NurseAssist alarms

The goal is to give a clear understanding of how event data is generated and can be used for further integrations or custom workflows.

How NurseAssist Events Generate MxMessages

The Kepler NurseAssist App continuously analyzes video sensor data on the edge in real-time to monitor the status / position of a person of interest based on predefined detection logics.
A local MxMessage is generated when the monitored person transitions into a state that is linked to a user-enabled notification.

This means:

• The sensor detects a state change (e.g., from In Bed to Sitting On The Edge Of Bed, or a Fall Detected state)
• The system checks whether a corresponding notification is activated in the NurseAssist configuration
• If the notification is enabled, a corresponding MxMessage is created and triggered on the camera

If a notification is not enabled, the event may still be internally detected by the system, but no MxMessage will be generated and therefore no downstream actions (e.g., event control, integrations) will be triggered.

This MxMessage serves as a standardized internal event that can be:

• processed by the camera’s event control
• linked to custom action profiles in action groups
• forwarded to external systems (e.g., via HTTPS IP Notify or MQTT Publish)

Each NurseAssist alarm is therefore not only a simpel notification, but also equipped with event data that can be used for automation and integration.

NurseAssist MxMessage JSON Payload Structure

After a NurseAssist event triggers an MxMessage, the camera generates a structured JSON payload that contains all relevant event information.

Below a real example:

{
  "local": {
    "KeplerNurseAssist": {
      "notification": {
        "cameraName": "Room13",
        "cameraSerial": "mx10-32-233-13",
        "notificationType": "FallDetected",
        "timestamp": "2026-04-21T14:35:49Z",
        "timestampUnix": 1776782149,
        "uuid": "a7f0a07a-f7c4-480e-810a-cdd671916e58"
      }
    }
  }
}

Payload Structure Explained

The exact structure of each MxMessage may vary slightly depending on the event type, but the overall format remains consistent to ensure reliable integration and parsing:

local Top-level container indicating that the message originates from the local device.

KeplerNurseAssist Identifies the app that generated the event allowing differentiation from other apps or system messages on the device.

notification Contains the actual event data.

“notification” Object Fields

cameraName Network device name defined within the sensor’s network settings

cameraSerial Unique serial number of the device, also known as factory IP address.

notificationType Describes the type of detected NurseAssist event / status, which is the key field for event classification, filtering and mapping to 3rd party systems.

timestamp ISO 8601 formatted timestamp (UTC) of when the event occurred.

timestampUnix Unix timestamp of the event, useful for systems that require numeric time formats.

uuid Unique identifier for the event.

Available NurseAssist Notification Types

Attached is a list of all possible notificationType values, grouped by the required NurseAssist license:

NurseAssist Basic License (pre-installed)

NurseAssist Notification	notificationType
Fall Detected	“FallDetected”
Person In Bed	“PersonInBed”
Person Not In Bed	“PersonNotInBed”
Situation Normal (only in Corridor Mode)	“SituationNormal”

NurseAssist Extended License

NurseAssist Notification	notificationType
Fall Detected / Person Lying On The Floor	“FallDetected”
Person Sitting On The Floor	“SittingOnFloor”
Person In Bed	“InBed”
Person Sitting On The Edge Of Bed	“SittingOnEdgeOfBed”
Person Out Of Bed	“OutOfBed”
Person In Bathroom	“InBathroom”
Person Out Of Room	“OutOfRoom”
Person Entering Room	“EnteringRoom”
Missing Bed / Bed not detected	“MissingBed”

Default c71 NurseAssist Event Profiles

On a MOBOTIX c71 NurseAssist sensor, several event profiles are preconfigured by default to ensure a plug n’ play user experience. These profiles correspond to the notification types available with the NurseAssist Basic License and can be found and extended under:

Setup Menu → Event Control → Event Overview → Message Events

^[1]Example of a default pre-configured message event profile on the c71 NurseAssist sensor. This profile uses a JSON comparison on the incoming MxMessage, specifically evaluating the notificationType field (e.g., "FallDetected"), to trigger the corresponding event.

The available default event profiles include:

• KeplerNurseAssist as generic app event triggered with each incoming app message
• FallDetected
• NotInBed
• InBed
• SituationNormal

Caution: By default, only the generic NurseAssist message event profile is active. The other preconfigured event profiles can be activated as needed.

Tip: When using the NurseAssist Extended features, it is recommended that you duplicate one of the existing profiles and adjust the event profile name and the notificationType used for JSON filtering according to the additional event notification.

---

1. Footnotes ↩︎