Skip to content
CC2 Device Documentation

User Association & Notification Names

When a duress alert is triggered, the notification that appears on other devices includes a subject name — this is the person who triggered the alert. Understanding where this name comes from is critical for fixing mismatches.

Where the notification name comes from

Section titled “Where the notification name comes from”

The portal builds the notification command using its own device record, not the device’s internal data.

The field associatedUser from the portal’s device list is used as the subj in the MQTT command.

Fallback order:

  1. associatedUser (if set)
  2. device.name (the device’s display name in the portal)
  3. "Unknown User"

What the device itself stores (independent)

Section titled “What the device itself stores (independent)”

The device’s own duresshome DV shows user_name and user_role widgets. These are set by the device’s allocation configuration (vname, vrole) and are displayed to the wearer.

These values are never used for alert notifications. The portal does not read the device’s vname or user_name widget.

How to verify

Section titled “How to verify”
  1. Open the portal’s device list and find the device that triggered the duress.
  2. Look at the “Associated User” column.
  3. Compare it with the expected name.
  4. Optionally, the device’s user_name widget can be inspected via MQTT (fget /dvs/duresshome.json or via devdata), but this only confirms the device’s internal setting — it does not affect the notification.

How to fix a wrong notification name

Section titled “How to fix a wrong notification name”
  • Do not try to change the device’s vname or duress DV.
  • Instead, update the Associated User field in the portal (Device Assignment page or API).
  • After updating, the next duress alert will use the new name.
Section titled “Related”