Setting Up FDD Notifications for High and Low Room Temperature Alerts via Email and SMS

Setting Up FDD Notifications for High and Low Room Temperature Alerts via Email and SMS

Overview

Notifications for alerts are set up through the FDD module in KODE OS. To use this module, you first need the appropriate read and write access, which can be enabled through roles. If you don’t have access, contact KODE Support(support@kodelabs.com) to enable on your behalf.

Once access is granted, you can configure the new FDD alarm. KODE comes with a ready-to-use FDD library covering heating, cooling, mechanical systems, network connectivity, energy, air quality, and more. The library includes rules ranging from simple BMS alarms and equipment failures like chillers, boilers, pumps, and fans, to advanced rules for energy and operational efficiency.

To receive notifications, you use Notification Policies. KODE Labs provides a flexible notification engine that supports email, push notifications, SMS, and phone calls. Notifications can be customized with templates, assigned to specific rules, roles, individuals, and escalations to ensure the right people are informed at the right time.

You can open the FDD module by navigating to the right panel in KODE OS and selecting FDD.

Steps to Set Up Temperature Alerts:

Setting up Notification Policies

If you want to receive a notification when your room temperature goes above 74°F or below 68°F, you’ll need to create and configure a Notification Policy in KODE OS. This policy will manage how alerts are sent via email and SMS when an FDD alarm is triggered.

Steps:

  • Open KODE OS and go to the FDD module.

  • From the left panel, scroll down and click on Policies (located at the bottom left).

  • Click the ‘+ Create Policy’ button to create a new policy.

  • Configure your policy by defining the alert conditions, selecting the desired notification channels (email and SMS), and assigning recipients.

Once saved, your notification policy will automatically send alerts whenever the room temperature goes above 74°F or below 68°F.

Note:

Notifications will only be sent if the configuration and the Routine have already been created and are properly set up.

After clicking ‘Create Policy’, you’ll be redirected to a new view where you can set up how you would like to be notified. This setup includes two main sections: Details and Notify.

Details Section

In this section, fill in the required information:

  • Name: Choose a name that clearly describes the purpose of the policy (for example, “Room Temperature Alert”).

  • Description: Provide a short summary of what this policy covers or when it should trigger notifications.

  • On Create: Optionally, you can enable an auto-close function for events based on a defined time period

Down here you decide how you want to receive alerts once an alarm is triggered, the template on each notifications type. KODE OS offers three notification types: Email, Push, and SMS

For each type, you can customize what information is included in the message, such as:

  • Event status

  • Building name

  • Device name

  • Floor

  • Start time

This helps ensure each notification is clear and easy to understand once received.

You can choose between two template options:

  • Default Notification Template: A pre-configured template that includes all the essential information. You can modify it if needed.

  • Custom Email Template: Build your own template from scratch, including exactly the details you want in your notifications.

Return to Normal Notifications
This feature sends an additional notification when the device or system returns to normal operation. Once enabled, you can set it up the same way as the main notification by selecting the template and choosing how you want to be notified, by email, push, SMS, or a combination of these.

Note: This section is only for configuring the notification template. It defines what information will appear in the notification, such as the email or SMS content.


Notify Section

After setting up the notification template for when an alarm is triggered, the next step is to configure who will be notified and how. This is done in the Notify view.

Steps:

  • Click Next after configuring the template to go to the Notify view.

  • In the Details section, choose one of the following:

    • Group Configuration: Assign a role or specific user(s) who will receive the notification.

  • Custom Configuration: Set up different types of notifications for different users or roles. For example, one user may receive email notifications while another receives phone calls.

  • Under Notifications, select the type of alert you want to send: Push, SMS, Call, or Email.

Important Note on SMS and Calls:
Push and SMS notifications can be set up directly here, but if you are using a phone number with a new or specific prefix for the first time, contact KODE Support to enable it from the backend. Once the prefix is enabled, you can continue setting up SMS and Call notifications.

Escalation Policy:
You can define escalation rules for ongoing events. For example, if an alert is not acknowledged within a certain period, it can escalate to another user or role. Escalations can use the same notification channels: email, push, SMS, or call. Multiple escalation levels can be configured as needed.

Once all details are configured, you are ready to create the routine for this notification policy. After completing the routine, click Save, and your notification policy will be active.

FDD Configurations

After configuring your notification policy, the next step is to create, configure, or enable a routine. Routines define the conditions under which notifications are triggered.

Steps to Enable a Routine:

  • Navigate to FDD → Configs.

    • Here you will see a list of pre-configured routines added by the KODE team.

    • Most common use cases are already available, but you can also create a new routine if needed.

  • Search for and select the routine you want to enable.

    • For example: Extreme High Temperature and Extreme Low Temperature.

  • Once you click on the routine, a new window will open showing a list of compatible devices.

    • Add the devices you want to include under Folder 1 Layer.

    • Use the device dropdown to see which points are used for this routine.

  • On the right side, you will see Routine Parameters.

    • For example, the Temp High Limit defines the temperature threshold that must be reached before the alarm is triggered(set the temp. threshold).

    • Hover over the question mark icon next to each parameter for more details.

  • Scroll down to Notification Settings.

    • Configure Grouping Policy and Priority. Under Notification Policy, select the policy you created earlier to determine how alerts are sent once the parameters are met.

  • Save the routine.


Note: Saving the routine does not automatically enable it.

  • To start monitoring, select the routine in the list and click Enable.

Once enabled, the routine will actively monitor the selected devices and trigger notifications according to your configured policy. Same procedure needs to

The same procedure should be followed for any additional routines, such as Extreme Low Temperature. Configure the routine, assign devices, set the routine parameters, select the notification policy, save, and then enable it.

You can use the same notification policy for one or multiple routines, depending on your monitoring needs.


    • Related Articles

    • Use Cases by Role (Property Managers)

      Overview Building portfolios are living systems where comfort, uptime, and cost control have to coexist every hour of every day. Property managers sit at the center, orchestrating engineers, vendors, and tenant expectations while translating building ...
    • Use Cases by Role (Tenant)

      Overview Tenants want spaces that feel great, work reliably, and make costs and sustainability visible without a maze of requests and emails. Office managers and workplace teams juggle comfort concerns, after-hours events, indoor air quality ...
    • Use Cases by Role (System Integrators)

      Overview System integrators and channel partners are on the front lines of building operations. In Class A office portfolios, they typically support owners and property teams in two operating models: Embedded operator: The integrator places one ...
    • Use Cases by Industry (Healthcare)

      Overview In healthcare, every detail matters. Comfort, reliability, and compliance are not just expectations, they are requirements that directly impact patient safety and trust. Hospitals, clinics, and care facilities must maintain precise ...
    • Use Cases by Industry (Corporate)

      Overview KODE OS empowers corporate real estate and workplace teams to manage offices, campuses, and global portfolios with confidence. The platform centralizes building systems, energy performance, occupancy data, and maintenance workflows into one ...