How fast does the digitalSTROM system react? How can this be influenced? Does another server bring more speed? This article provides explanations.
Where do reaction times occur?
Whenever an action is triggered in the system, there is a certain reaction time. Since digitalSTROM is a decentralized system, not every communication runs via the server, quite the opposite: the normal push-button operation is processed directly in the digitalSTROM meter. This also applies to rooms that consist of several circuits. However, if links are created in the server apps, e.g. in the scene responder, communication also runs via the server and is deliberately delayed, see below.
If IP devices are addressed, e.g. Sonos, their response times are also added.
Are the reaction times perceived as disturbing?
Typically, digitalSTROM customers do not find the reaction times disturbing. digitalSTROM usually switches the light much faster than some energy-saving lamps need to ignite. The high reliability of digitalSTROM is extremely important here: If a customer can rely on the reaction, he won't be bothered if he walks half a step into the room before the lights turn on.
However, if you have an unreliable system, you stand impatiently next to the push-button, press it, wait to see if the light turnes on, press it again, etc. This is usually perceived as quite annoying. digitalSTROM, however, always reacts absolutely reliably. (Note: If problems should occur, please make sure to record them in time and inform the digitalSTROM support so that a quick and uncomplicated solution can be found.)
What are the reaction times?
- Touch signal for a color group (light, shadow, ...):
The transmission of a push-button signal after pressing until the start of the execution in the terminal takes about 450 ms, even if several circuits (meters) are involved. Example: A photoelectric proximity switch in the living room controls the light in the corridor. Communication takes place via 2 digitalSTROM meters, the delay time here is 450 ms as well.
- Calling up a mood scene is linked via scene responder:
An example would be: If mood scene 3 is called in the living room, mood scene 1 is to be called in the corridor.
In this case, the scene responder first waits to see whether other key tips will follow in the living room. Only when it can be sure that the user has called mood scene 3 (and not mood scene 4 instead) will the configured action be executed (switch on the light in the corridor). The waiting time is about 1.5 seconds so that the light in the hallway is switched on about 2 seconds after the mood scene call in the living room.
- Smartphone controls a color group (light, shadow, ...):
Here the transmission from the smartphone to the dSS is much faster so that the terminal block can start execution after around 250 ms.
- dSS-App controls individual device:
digitalSTROM is optimized for room mood scene calls. If an individual device is addressed, e.g. via the scene responder, the transmission time increases from 250 ms to approx. 750 ms.
- Command sequence:
If a command sequence is programmed in a dSS app (e.g. a user-defined action calls up several activities), these commands are each processed with a pause of one second.
- Five or more rooms linked to one meter:
If one meter controls several rooms (e.g. meter corridor controls corridor, storeroom, and guest bathroom, because they share a circuit), the push-button operation becomes 240 ms slower from the fifth room on linked to one meter. However, this only applies to the first click of an operating action. Example: The light push-button of the fifth room is tapped 3 times so that mood scenes 1, 2 and 3 are called up quickly one after the other. In this case, the call for mood scene 1 will be 240 ms slower, mood scene 2 and 3 will be performed as fast as in the other rooms. Rooms 1 - 4 can still be operated quickly. The additional delay is due to the somewhat more complex room addressing for the higher room numbers. If a room is addressed, the subsequent operation takes place normally quickly.
- IP devices:
With IP devices, the digitalSTROM server generates the necessary control commands and forwards them to the IP devices. The reaction time therefore directly depends on the addressed device. In addition, the time for data transmission of the triggering device is added. If the triggering device is a digitalSTROM push-button, approx. 200 ms have to be added after the push-button was pressed.
If Sonos is controlled, a lot of communication is necessary. In particular, if several Sonos devices are to react simultaneously to a ringing signal, for example, a huge amount of information must be retrieved from each Sonos device when the signal is received (current playlist, playback position, play/pause state, repeat/shuffle, volume, group membership, ...), then a new common playback group must be formed, then the ringing signal is played and then all information is restored on all Sonos devices.
Can a faster server improve response times?
In short, in most cases not. But for point 7 a significant acceleration could be achieved. Especially when using multiple Sonos devices, the difference is immense.
A faster server helps in these respects:
- Controlling IP devices.
- The configurator loads faster and runs much more smoothly.
- The smartphone apps load faster and run more smoothly because information can be retrieved faster from the server.
In addition, a modern server has the advantage of offering more resources that can be well used for future device integration. In addition, significantly more devices can be managed in one installation.