Knowledge for Planning

Operation and Maintenance

A sensor system isn’t finished after acceptance; it’s in operation. The questions that arise at this stage are different from those asked during planning: How do you know when a device has stopped working? When should a battery be replaced, and when should a CO2 sensor be calibrated? And who will still know, after three years, which sensor is installed in which room?

3Levels of service status: OK, Warning, Critical
1The file contains the entire system configuration
0Additional database for history
5 to 10years of service life, depending on power supply and reporting frequency

How can I tell if a sensor has failed?

Alarms and Malfunctions

A defective or malfunctioning wireless sensor does not report a fault—it does not report anything at all. To ensure that this silence is meaningful, each device sends a signal to indicate it is operational: Even if no measurement value changes, it repeats its last value, typically at least every twelve hours, depending on the device.

That’s why an unused room doesn’t trigger an error message. An empty office, a warehouse with no activity, a weekend: The value doesn’t change, but the device still reports. If even this “sign of life” fails to appear, the problem lies with the device, the power supply, or the wireless connection—and not because no one was in the room.

The Alarms page of the dashboard lists all sensors that have not reported within their expected interval. This means no one has to check device by device; the list fills up on its own and is usually empty.

One question remains for planning purposes, and it needs to be answered before the system is handed over: Who checks this list, and how often?

Is there a fault message sent to the building management system? Yes, but not via a switch that you flip. If the message is not only to appear on the dashboard but also to be sent externally to the building management system, that is part of the project scope: We’ll set up the fault message together with you and implement it as part of the contract—for example, via a second MQTT broker that receives only fault messages, separate from the measurement values. This therefore belongs in the scope of work and not in the commissioning phase.

That is why the list is reliable: Without a signal, silence would be ambiguous—it could mean a malfunctioning device or simply that nothing happened. With the signal, a sensor that does not transmit for longer than its interval is a confirmed finding, not a guess.

How Long a Battery Lasts and When to Replace It

Maintenance

How long does a sensor’s battery last, who replaces it, and how often? Batteries are replaced based on condition, not on a schedule. The maintenance page lists every battery- or solar-powered sensor along with its current voltage and status: OK, Warning, or Critical. The cell is replaced when the device enters the “Warning” status, not because a set interval has elapsed. This eliminates the need to replace fully charged cells and, at the same time, prevents a sensor from failing unnoticed.

We’ll provide two figures regarding service life. For devices powered solely by one or more batteries, we estimate a typical minimum service life of five years. The reporting interval is the primary factor affecting how much longer the device will actually last: a sensor that transmits less frequently will last longer.

Devices with solar cells ideally operate entirely without a battery. In that case, it is not power consumption that limits the operating time, but rather the cell’s maximum service life of ten years, as specified by the battery manufacturer. Accordingly, a sensor in a windowless archive is closer to the five-year mark than one near a south-facing window.

The cell type and number are listed in every data sheet—some devices use one cell, others use two. This information should be included in maintenance planning—along with the number of affected devices and their accessibility. Replacing a sensor located under a ceiling eight meters high costs more than the cell itself.

Solar with a Buffer TankThe Standard ConfigurationA solar cell for operation, plus one or two cells as a backup for dark days—about two AAA batteries for the EnoSense® CO2. Runs quietly as long as the room is lit.
Battery OnlyWhere there’s no lightDepending on the device, one or two batteries; the EnoSense® People Counter uses two AAA batteries. It will eventually appear in the warning list—this is the intended behavior, not an error.
Mains Power or PoEReceivers, traffic lights, countersNo maintenance required on the power supply. Instead, the device is connected to a line that’s already in place during the renovation.

How often does a CO2 sensor need to be calibrated?

CO2 Sensors

The operator decides how often a CO2 sensor needs to be calibrated: Automatic calibration is not currently enabled on our sensors. Calibration therefore does not occur automatically but must be manually initiated—on the device itself, using the service button. The exact procedure is described in the manual for the respective device; there is a short video in the video library for both the service button and the calibration process.

No test gas or removal of the device is necessary for this: fresh air serves as the reference. All that’s needed is someone to initiate the process—and the information that this button exists.

For planning purposes, this means: CO2 balancing is a maintenance service and, as such, must be included in the maintenance schedule and the request for proposals. It does not happen automatically. The dashboard alerts you if it has been too long since the last adjustment (ECS Manual, Section 4.6), but the responsibility for taking action lies with the operator or with us.

If you'd like to see for yourself: The video library features “EnoSense® CO2 Service Button—Where the Button Is Located and What It Does” and “EnoPuck® CO2 Calibration—Adjusting the CO2 Level,” which together run just under two minutes.

How do I program a sensor, and who performs the commissioning?

Commissioning

Can the electrician do this on their own, or do we need to be involved? The division of labor is clear: the electrician installs and connects the equipment, and we get the system up and running. Programming, configuration, and commissioning—setting up sensors, registering receivers, assigning rooms, and configuring data transfer—are tasks that DEUTA Controls handles as a paid service; they are not the responsibility of the operator or the installer. Include this service as a separate line item, not as an add-on to the delivery.

The complete configuration—each sensor in its designated location, each receiver with its address, and the gateway settings—is contained in a single file. It can be backed up and restored. How do I document which sensor is installed in which room? That’s exactly the point: This documents which sensor is installed in which room. Anyone involved in the construction project who requests this list will receive it from the file, not from a manually updated spreadsheet.

For larger installations, the process is reversed: The file is created in advance at the desk, and on-site commissioning involves importing the data rather than programming each device individually. That’s the difference between spending one day versus one week on the job site.

What you need to provide: nothing. We usually handle the commissioning ourselves and bring all the necessary equipment, including a laptop and wireless technology.

We deliberately avoid giving a blanket estimate of how long the setup will take per floor: The duration depends on the type of sensors and whether they can be programmed in advance. Once the floor plan and desired configuration have been discussed, we’ll provide you with an estimate for your building within one to two days.

For handover: Request this configuration file as part of the documentation. It serves as the inventory list, the room assignment, and the recovery tool if a gateway is replaced.

What Happens During a Power Outage

Restart

The system stores all the information it needs to operate in non-volatile memory: sensor assignments, receivers, and data transfer settings. When power is restored, it restarts automatically. No user intervention is required, and nothing needs to be reprogrammed.

This has two implications for planning. First, the restart does not need to be included in the operating instructions because no action is required on the user’s part. Second, a power outage only affects the gateway and receivers anyway: The sensors themselves are powered by solar cells or batteries and continue to take measurements—they simply reconnect to a receiver after the system restarts.

The cost of downtime: downtime metrics. Anyone who needs complete coverage—for example, for documentation purposes—should ensure that their gateway and network infrastructure are protected against interruptions. This is a matter of electrical design, not sensor technology.

How long are measurement values stored, and where are they stored?

History

The gateway maintains its own history of measurement values as files on the device, with automatic rotation of the oldest entries. This data feeds the trend and comparison views in the dashboard. No additional database needs to be set up or maintained for this purpose.

This history is intended for reviewing past conditions within the building—such as the trend over a week or documentation of a heating period—and is not meant to serve as a long-term archive. Its duration depends on the number of sensors and the reporting interval; we can provide the specific duration for your system upon request.

If it takes years, the values are recorded in the target system. That is precisely why the question of data retention belongs in the data path specification and not in the sensor specification.

What this means for your request for proposals

8 points
  • Specify who views the alert list and how often.
  • Designate external fault notifications as a separate item if desired—this is configured in the project, for example, via a second broker.
  • Include the cell type and number of battery-powered devices in the maintenance schedule, specifying the mounting height and service life.
  • If there is a requirement to provide proof, clarify whether the gateway and network technology should have an uninterrupted power supply—the sensors themselves continue to measure during a power outage.
  • Designate CO2 calibration as a maintenance service: It is triggered on the device and does not occur automatically.
  • List commissioning and configuration as a separate, chargeable item.
  • Request the system’s configuration file as part of the documentation.
  • Specify the retention period for the measurement data and identify which system will store it long-term.
Status and Sources

Information current as of September 16, 2026. Regulatory information has been compiled to the best of our knowledge and does not constitute legal advice. The text of the currently applicable version is always authoritative.

  • Alarms, Maintenance, and Supply Status: ECS Operating Manual, Sections 4.5 through 4.7.
  • Configuration and Recipe File: ECS Operating Manual, Sections 3.3 and 9.
  • History on the Gateway: ECS Operating Manual, Section 7.3.
  • Calibration: Procedure described in the manual for the respective device; see also the videos “Service Button” and “Calibration” in the video library.
  • Cell types, number of cells, and power supply type: Data sheet for the respective device.

Would you like us to run the numbers for your building?

Send us the floor plan, dimensions, and target system. You’ll receive a recommendation for the number of units, a list of part numbers, and a quote.