Skip to content
RenoktaRenokta

Emergency systems

Detects smoke, fire and similar emergencies and notifies the right people instantly.

Request a demo
Addressable fire alarm panels and smoke detectors lined up on a wall.

Measured point

CO level

Renokta IoT Platform · Emergency systems

Live · --:--:--

Sample building › Detectors and buttons

  • Car park CO level

    11ppm

  • Sensors online

    70/ 72

  • Average battery

    82%

  • Notification time

    6sn

CO level

Car parkBoiler room11 ppm

Warning level 22

Detector status

  • Car parkCO detector11 ppm
  • Boiler roomCO detector11 ppm
  • Server roomTemperature sensor24.9 °C
  • Panic buttonReception · battery77 %

Event feed

  • 0Critical
  • 1Major
  • 1Minor
  • 2Warning
  • Car park CO level is nearing the warning levelOpen
  • A detector in the basement is offlineOpen
  • Panic button test completedOpen

Sample screen. Values are simulated.

What is an emergency system?

An emergency system is a monitoring setup that detects events from sensors such as smoke, gas, panic buttons and door or window contacts, notifies the right people at once and keeps a record. The role of Renokta is detection, notification and logging; it does not provide fire suppression or rescue.

How does it work?

When an event occurs, sensors and buttons send a LoRaWAN message to the gateway. The platform receives it, runs the rule and sends the notification to the chosen channels. The event time and acknowledgement are recorded.

  • Sensor or button: detects the event and creates a message.
  • Gateway: carries the message to the platform.
  • Platform: runs the rule, sends the notification, logs the event.
  • User: receives the notification, acknowledges and starts the needed action.

Which quantities and events are monitored?

  • Panic button press: to pass on a call for help with location information.
  • Smoke detection: to notice the start of a fire early.
  • Gas detection: to notice a leak.
  • Door and window contact: to report unauthorised opening or a door left open.
  • Device status: battery and link information, to confirm that the sensor works.

Which detection method should you choose?

  • Wireless panic button: sends a call with a single press and needs no cabling, but the user must be able to reach it.
  • Smoke detection: catches early signs of fire; placement and environment (steam, dust) should be considered to limit false alarms.
  • Gas detection: the sensor is chosen by gas type, and different gases may need different sensors.
  • Door and window contact: reports opening, but alone does not show whether the door is locked.
  • Connection to an existing fire panel: the event output of the panel can be taken for information; the function of the panel does not change.

Who is it for?

  • Factories and warehouses: lone workers and hazardous areas.
  • Offices and business centres: panic buttons and door monitoring.
  • Schools, dormitories and healthcare sites: help calls and area monitoring.
  • Hotels and accommodation: event reporting for rooms and shared areas.
  • Building management: shared areas and technical rooms.

How do alarms and notifications work?

When an event is detected, the rule fires and a notification goes to the chosen channels (message, e-mail, dashboard). An escalation order can be defined so that an unanswered notification goes to a second person. Acknowledgement is logged with the event and time.

If a sensor loses its link or the battery runs low, the platform raises this as a separate alert. Without a connection an event cannot be delivered, so coverage and device status should be checked regularly.

This system does not replace the fire detection and alarm systems required by local regulations; it is designed as an added layer of information and records.

Integration with existing systems

Events can pass through MQTT or an API to building automation, security monitoring software or a call system. Connections to existing panels are adapted to the need, and the scope is set during the survey.

Data privacy and security

The system collects event, time and device information; it records no images or sound. Because a panic button press can identify a person, access to records is limited by role. Communication and platform access are set up with encryption and authentication. A GDPR or KVKK assessment is done with your own privacy notice and legal adviser.

Installation process and what a quote needs

During the survey, risk areas, doors and existing panels are walked through and radio coverage is tested. Devices and the notification flow are tried in a pilot area before moving to other areas.

For a quote, the area to be monitored, the number of doors and buttons, the event types to detect and the people to be notified are enough. Contact us with these details and we will plan the survey together.

Highlights

  • Wireless panic button

    A single press sends a call for help; it can be placed anywhere without running cables.

  • Smoke and gas detection

    Smoke and gas sensors report to the platform when an event occurs, and chosen people are notified.

  • Door and window contacts

    Unauthorised opening or a door left open is reported, and the event is logged with its time.

  • Notification order and acknowledgement

    Recipients are ordered, the event is acknowledged and the whole sequence is recorded.

  • Device health monitoring

    Battery and link status are tracked, and a sensor that stops reporting raises a separate alert.

From detection to notice: emergencies

Smoke, gas and temperature sensors and panic buttons report to the gateway. The platform notifies the right people and records the event.

SmokedetectorGas sensorPanicbuttonDoor contactsensorLoRaWANgatewayRenokta IoTplatformInstantalarm noticeEvent logDevice statusreport

Smoke detected

  1. The smoke detector on the storage floor switches to alarm and reports to the gateway.
  2. The platform receives the alarm and opens an event record with location, time and device.
  3. An instant notification goes to the security officer and the on-duty team.
  4. The team checks on site; notification and response times appear in the event record.

The diagram shows the logic; names are examples.

Frequently asked questions

How does an emergency system work?
A sensor or button detects the event and sends a LoRaWAN message to the gateway. The platform runs the rule, notifies the right people and logs the event.
Which sensors are used?
Wireless panic buttons, smoke and gas detection and door or window contacts are used. The choice follows the risk and area being monitored and is made during the survey.
Does it put out fires or perform rescue?
No. The system provides detection, notification and logging, with no suppression or rescue function. It does not replace the fire systems required by regulations.
What determines the cost?
The number of sensors and buttons, the monitored area, gateway needs, the notification flow and the integration scope determine the cost. Exact details follow the survey.
Is it compatible with our fire panel and systems?
Information can be taken from the event output of a panel or through an API or MQTT. The connection is adapted to your needs and does not change how the panel works.
Who owns the data and how is privacy handled?
Event records belong to the organisation. Access is limited by role and no images or sound are recorded. A GDPR or KVKK assessment should use your own privacy notice.
How long does installation take?
It varies with the size of the area and the number of devices, and becomes clear during the survey. Usually a pilot area is tried first.
What happens if the link is lost?
The platform notices that a sensor has gone quiet and raises a separate alert. An event cannot be delivered while the link is down, so coverage and device status should be checked regularly.

Our solutions

Let's plan the right solution for you, together.

Request a demo