# Alarm integration of c ONE / c71 NurseAssist in Ascom SmartSense

**URL:** <https://community.mobotix.com/t/alarm-integration-of-c-one-c71-nurseassist-in-ascom-smartsense/7901>\
**Category:** Kepler NurseAssist\
**Tags:** howto, integration, nurseassist, nursecallsystem\
**Created:** [January 9, 2024, 8:47am UTC](https://community.mobotix.com/t/alarm-integration-of-c-one-c71-nurseassist-in-ascom-smartsense/7901 "2024-01-09T08:47:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mx-PhilippH](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.mobotix.com/mx-philipph/32/10382_2.png) [@Mx-PhilippH](https://community.mobotix.com/u/Mx-PhilippH)\
**Post date:** [January 9, 2024, 8:47am UTC](https://community.mobotix.com/t/alarm-integration-of-c-one-c71-nurseassist-in-ascom-smartsense/7901/1 "2024-01-09T08:47:22Z")

</div>

**- About Ascom SmartSense -**  
_Ascom_ is a global solutions provider focused on healthcare ICT and mobile workflow solutions.  
The _Ascom Unite SmartSense_ solution - based on the _Ascom teleCARE IP_ platform - enables the creation of individual resident profiles. These help to create care environments that combine safety and autonomy. The solution can be complemented with various sensors and cameras as required. These sensors, video images and smart algorithms support the alarm function.

**Important Note:** There is another potential for the integration of _c ONE and_ _c71 NurseAssist_ called _Ascom Ofelia_. _Ascom Ofelia_ is an enterprise-grade alarm and workflow management suite using standard industry communication protocols like MQTT, OPC UA. MODBUS/TCP and others.  
The _c ONE and_ _c71 NurseAssist_ devices support MQTT and the integration should therefor be straight forward as well. Further information follow in a separate article.

**- Getting started -**  
The _c ONE and_ _c71 NurseAssist_ sensors come with a configuration optimized for the use case and thus differ significantly from other MOBOTIX sensors by default.  
In order to integrate the alarms into _Ascom SmartSense_, this configuration must be extended with customized IP Notify profiles and action groups, which convert the MxMessageSystem events created by the _NurseAssist app_ into compatible IP notification and address the alarm structure prepared in _Ascom SmartSense_.

**- Create a IP Notify Profile for every notification type -**  
Go to “Admin Menu → Transfer Profiles → IP Notify Profiles”. Click on the button Add new profile. Fill  
in the fields as shown in the image below:

 ![grafik](https://canada1.discourse-cdn.com/flex030/uploads/mobotix/original/2X/a/a6cb11cf13176e103f56bdb700f57538e16d2a21.png)

For FallDetected notifications, we use a GET request to the `trigger-alert` end-point:

```auto
/api/thirdparty/alerts/triggeralert?
SensorId={{SensorId}}&AlertName={{AlertName}}&SensorType

```

where

| Field | Type | Description |
| --- | --- | --- |
| SensorId | String | Unique identifier for a specific sensor. Can only contain upper/lower case letters and numbers. |
| AlertName | String | Name of the alert, should be present, in this case FallDetected |
| SensorType | String | In this case it is NurseAssist |

For NotInBed and InBed notifications, we use the `clients` end-point

```auto
/api/thirdparty/clients/status?SensorId={{SensorId}}&SensorTy
atusName={{StatusName}}

```

where

| Field | Type | Description |
| --- | --- | --- |
| SensorId | String | Unique identifier for a specific sensor. Can only contain upper/lowercase letters and numbers. |
| SensorType | String | In this case it is NurseAssist |
| StatusName | String | The name of the status, in this case either InBed or NotInBed |

**- Testing the configuration -**  
You can test the IP Notify Profile configuration by going to “Admin Menu → Network  
Setup → Test Current Network Configuration → IP Notify”. Choose the IP Notify  
Profile you configured above.