STATUS DISPLAY FOR PUSH BUTTONS

The following document describes what the status is when an input is configured as a button - the following document uses the 'Push Button' as an example

See how it works with Loxone

Important: This is an input that is configured as a button, not to block the function 'buttons' (this is referred to in the document as a 'switch' or 'switch object'). It is also not a digital input, which is configured as a button though, but also as a 'status only'.

With push buttons as a 'status only' have been configured, the only action-UUID is visualized (either as text or icon, depending on configuration).

There are three triggers for a change in color of a push button

  • Amendment to the state-UUID value
  • Change in the action-UUID value (only if no state-specified UUID)
  • Activity visualization (to detect whether the user has pressed it).

Is described in the following cases when and how to visualize what is the reason. First one thing: Each time you press the push button by pressing the green visualization.

A push button with no exit

Push button with no exit

Info from the File Structure

<Function name="1 PB ohne Ausgang"
    UUIDaction="action">
  <detail Type="Pushbutton"/>
</Function>

Pulse

The push button is released very quickly, at the mini server is thus only a "pulse" at. Because of this push button has no outputs, this has no effect, it is only by pressing green visualization and white again.

Push Button: pushButtonHit Push Button: Push button release APP -> mini Server: dev / sps / io / action / pulse SC: action - 0 SC: action - 0 Push Button: receivedInputState: '0 '

1
2
3
4
5
6
Pushbutton: pushButtonHit
Pushbutton: pushButtonRelease
APP -> Miniserver: dev/sps/io/action/pulse
SC: action - 0
SC: action - 0
Pushbutton: receivedInputState: '0'

Note: "SC: xxx - x" is the value that was sent to the mini server app, where xxx is the UUID and x is the current value.

On/Off

Once the push button is pressed, the mini server receives the "on" command and it is the input to "1". Since there is no exit, this one also visualized - the push button is green.

Once the push button is released, the "off" command goes to the mini-server and the input is reset to "0". The push button turns white again.
 

1
2
3
4
5
6
7
8
9
PushbuttonViewController: pushButtonHit
APP -> Miniserver: dev/sps/io/action/on
SC: action - 1
Pushbutton: receivedInputState: '1'
 
Pushbutton: pushButtonRelease
APP -> Miniserver: dev/sps/io/action/off
SC: action - 0
Pushbutton: receivedInputState: '0'

 

Push button with a directly attached output

Push button directly attached to output

Info from the File Structure

<Function name="2 PB mit direktem Ausgang"
    UUIDaction="action"
     UUIDstate="state">
  <detail Type="Pushbutton"
       Outputs="1"/>
  <State n="1"
      UUID="state"
      name="2 Ausgang des PB"/>
</Function>

Pulse

After this push button has a state-UUID attribute, instead of this action UUID attribute used to visualize the status. So keep the push button white (with the exception of a short green flare to visualize that the user has actually pressed the push button).

1
2
3
4
5
6
7
8
9
10
Pushbutton: pushButtonHit
Pushbutton: pushButtonRelease
APP -> Miniserver: dev/sps/io/action/pulse
SC: action - 0
SC: state - 0
SC: action - 0
SC: state - 0
Pushbutton: receivedInputState: '0'
Pushbutton: receivedOutputState: '0'
change pb to OFF

On/Off

Again, only the value of the state is visualized by the UUID. After "on" arrived, the state-UUID goes to 1 and the push button is green. The "off" turn off the output, the push button turns white again.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Pushbutton: pushButtonHit
APP -> Miniserver: dev/sps/io/action/on
SC: action - 1
SC: state - 1
Pushbutton: receivedInputState: '1'
Pushbutton: receivedOutputState: '1'
change pb to ON
 
Pushbutton: pushButtonRelease
APP -> Miniserver: dev/sps/io/action/off
SC: action - 0
SC: state - 0
Pushbutton: receivedInputState: '0'
Pushbutton: receivedOutputState: '0'
change pb to OFF

Push button with a directly attached output

Push button directly attached to output

Info from the File Structure

<Function name="3 PB mit Taster vor Ausgang"
    UUIDaction="action"
     UUIDstate="state">
  <detail Type="Pushbutton"
       Outputs="1"/>
  <State n="1"
      UUID="state"
      name="3 Ausgang des PB"/>
</Function>

This push button has a button object (block function) between the input and the output. When pressed, changes the status indicated and remains changed only by pressing again you get back to its original state. Therefore, the following examples, each with two activities are described.

Pulse

As for 2, is now also a state-UUID in the structure of information, that is the only state of this UUID visualized (again with the exception of the visualization to confirm the operation).

In the first operation is activated by the object between the probe pulse input and output, state-UUID goes on and one of the push button is green.

In the second operation the probe pulse through the object is deactivated, thus the State's UUID goes to 0 and the push button is white.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Pushbutton: pushButtonHit
Pushbutton: pushButtonRelease
APP -> Miniserver: dev/sps/io/action/pulse
SC: action - 0
SC: state - 1
SC: action - 0
Pushbutton: receivedOutputState: '1'
change pb to ON
Pushbutton: receivedInputState: '0'
 
 
Pushbutton: pushButtonHit
Pushbutton: pushButtonRelease
APP -> Miniserver: dev/sps/io/action/pulse
SC: action - 0
SC: state - 0
SC: action - 0
Pushbutton: receivedOutputState: '0'
change pb to OFF
Pushbutton: receivedInputState: '0'

On/Off

At the first press of the "on" command activates the switch on the mini server object, thus the state-UUID set to 1 and the push button is green. The "off" command will have no effect here.

Note: It is important that the push button is not by closing the visualization of the activity is set back to white.

By pressing again enters the second "on", ie a rising edge of the mini-server and then switch to the object. This is disabled and the state receives UUID 0 - the push button turns white again.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
Pushbutton: pushButtonHit
APP -> Miniserver: dev/sps/io/action/on
SC: action - 1
SC: state - 1
Pushbutton: receivedOutputState: '1'
change pb to ON
Pushbutton: receivedInputState: '1'
 
Pushbutton: pushButtonRelease
APP -> Miniserver: dev/sps/io/action/off
SC: action - 0
Pushbutton: receivedInputState: '0'
 
 
Pushbutton: pushButtonHit
APP -> Miniserver: dev/sps/io/action/on
SC: action - 1
SC: state - 0
Pushbutton: receivedOutputState: '0'
change pb to OFF
Pushbutton: receivedInputState: '1'
 
 
Pushbutton: pushButtonRelease
APP -> Miniserver: dev/sps/io/action/off
SC: action - 0
Pushbutton: receivedInputState: '0'

Push button with branched logic before starting

Push button with branched logic

Info from the File Structure

1
2
3
4
5
6
7
8
9
10
11
12
<Function name="4 PB mit verzweigter Logik"
    UUIDaction="action"
     UUIDstate="action">
  <detail Type="Pushbutton"
       Outputs="2"/>
  <State n="1"
      UUID="output1"
      name="4 AG 1"/>
  <State n="2"
      UUID="output2"
      name="4 AG 2"/>
</Function>

When this push button two outputs are attached, which (may) be equal to respond, both to represent the status by the color of the push button is not possible. This case is just the status of the input and therefore visualizing the same on the action and the state-UUID.

Pulse

By changing the pulse Although the states of the individual outputs, but their condition is not visualized on the Push Button - Push the button will be white again (after he was green by the actuation of visualization).

1
2
3
4
5
6
7
8
Pushbutton: pushButtonHit
Pushbutton: pushButtonRelease
APP -> Miniserver: dev/sps/io/action/pulse
SC: action - 0
SC: output1 - 1
SC: output2 - 1
SC: action - 0
Pushbutton: receivedInputState: '0'

On/Off

Pushbutton: pushButtonHit
APP -> Miniserver: dev/sps/io/action/on
SC: action - 1
SC: output1 - 1
SC: output2 - 1
Pushbutton: receivedInputState: '1'
 
Pushbutton: pushButtonRelease
APP -> Miniserver: dev/sps/io/action/off
SC: action - 0
Pushbutton: receivedInputState: '0'