uni-PRO building automation

Backup controller

If the controller fails, the second one takes over.
Continue with the arrow keys, space bar or the buttons below  ·  F = full screen
What is it about?

When the controller fails

The controller is the heart of the building automation. It switches the lights, controls the heating, moves the shading and reports faults.

If it fails - due to a defect, a power problem or a worn-out storage medium - none of this responds any more until someone is on site and replaces the device.

In a hotel, a care home or a business that cannot wait until the next working day.

LightingHeatingShading nothing responds any more
The idea

Like a co-pilot in the cockpit

The co-pilot flies along every minute. They know the route, see all the instruments and always know where the aircraft is - but they do not intervene as long as the captain is flying.

If the captain drops out, the co-pilot takes over at once - no briefing needed, because they were there the whole time.

This is exactly how the backup controller works alongside the primary controller.

Primary controller runs the installation Backup controller calculates along, switches nothing “captain” “co-pilot”
How it works

Three states - all automatic

1 Daily sync Every day the backup controller fetches the project and data of the primary controller 2 Standby It runs along completely but issues no commands and watches the primary 3 Takeover If the primary controller falls silent, the backup takes over all its tasks When the primary controller returns, the backup controller goes back to standby by itself. At every change the program restarts once - this takes only a few seconds.
How it works

How a failure is detected

  • Via the electrical installation (KNX): The primary controller regularly sends a sign of life on the bus. If it stops, the backup controller takes over.
  • Via the network: Every 10 seconds the backup controller checks whether the primary controller can be reached and its program is still running.
  • Both together: It only takes over when both paths fail. A restarting switch therefore does not trigger a takeover.
Primary controller Backup controller KNX Network
The benefits
Benefit 1

Takeover without intervention

Nobody has to go out at night or re-plug a device. The backup controller takes over by itself as soon as the primary controller has been silent for longer than the set waiting time.

After a restart of a few seconds, lighting, heating and shading respond again - the repair can wait until the next working day.

automatic
The benefits
Benefit 2

All data is available immediately

In standby the backup controller calculates everything along: measured values, states, recordings. Devices continue to be polled.

On top of that comes the daily sync with the primary controller - so project, scenes, switching times and settings are always up to date.

Result: Nothing is missing after the takeover - the histories continue without a gap.
takeover history without interruption
The benefits
Benefit 3

Never two controllers at once

As long as the primary controller is working, the backup controller issues not a single command to the outside. Nothing is switched twice, no message arrives twice.

If the fault lies in the backup controller's own network or something is simply set up wrongly, it deliberately does not take over - it reports the problem instead.

Primary switches Backup stays silent 💡 exactly one command
The benefits
Benefit 4

Always informed

Every takeover and every handback triggers a message - by e-mail, push message to the phone or Pushover. The same applies if the daily sync ever fails.

If desired, the backup controller reports “all OK” every day. That way you know the reserve is really ready when it is needed.

Backup has taken over Daily: all OK E-mail · Push · Pushover
The benefits
Benefit 5

Automatic handback

Once the primary controller is repaired or reachable again, the backup controller hands back by itself and returns to standby.

Nothing has to be switched over or copied back - the installation is back in normal operation and the reserve is ready again.

Backup back to standby Primary active again
In everyday use

What do residents and users notice?

In normal operation

Nothing. The backup controller works invisibly in the background.

During a takeover

A short pause of a few seconds, then everything works as usual.

In the app

The backup controller is set up as a second connection. If the primary fails, you simply switch to it.

For the service provider

A message that a takeover happened - and time to plan the repair calmly.

Together with the distributed project

Ideal in a network

In a distributed project several controllers run one installation together - if one fails, the others keep running.

The backup controller additionally protects the main controller (number 1). It receives the same number, waits in standby outside the network and joins it by itself on takeover.

Result: No building fails - not even the one with the main controller.
Distributed project 1 2 3 Backup 1 standby protects no. 1
Typical applications

Where a backup controller pays off

Hotel and care home

Heating, lighting and ventilation must work around the clock.

Commerce and production

A standstill costs more than the second controller.

High-end home

Anyone living in a fully automated house does not want to be left in the dark by a defect.

Remote sites

Holiday home or branch office: the installation keeps running until a technician gets there.

Summary

The backup controller at a glance

Automatic

Takes over without intervention, hands back by itself.

All data there

Runs along in standby and syncs daily.

Nothing twice

In standby no command goes to the outside.

Reliable detection

Via KNX, network or both together.

Always informed

Message on takeover, handback and a daily “OK”.

Fits the network

Protects the main controller of a distributed project.

The detailed description is in the help: Backup controller  ·  Distributed project presentation
◀ Overview ← Help