Structure File

The structure file contains all the information needed to create a user interface and is stored in XML format on the Miniserver. It is important to note that each user will receive their own unique structure file depending on whether they are accessing the Miniserver over the local network, or remotely via the internet. This is done so that certain users or user groups only have access to subsets of functions, and some functions may be locked to prevent use over the internet.

Contents

1. LoxApp.xml

2. LoxApp2.xml

3 LoxLIVE – The Root Element

4. Images - Picture Source

4.1 Image - Picture Element

5. Group- Group Eelement

6. Function- Simple Circuits

6.1 Detail- depiction details
6.2 action – switching command
6.3 state – simple status request
6.4 stateAll – complex status query

7. Function Blocks – More than simple PLC control

7.1 Push Button (double) +/-
7.2 Push Button (double) On/Off
7.3 Alarm system
7.4 Push Button +/-
7.5 Operating time counter
7.6 Dimmer
7.7 Heating mixer
7.8 Blinds
7.9 Automatic Blinds
7.10 Multifunction Switch
7.11 Lighting Scenes
7.12 Lighting Scenes (learn)
7.13 Lighting Controller
7.14 RGB Lighting Scenes
7.15 Room Control
7.16 Sauna Control 1
7.17 Sauna Control 2
7.18 Timer
7.19 Push Button
7.20 Status
7.21 Tracker
7.22 Door
7.23 Staircase Light Switch

1. LoxApp.xml

LoxApp.xml should no longer be used - instead we recommend to use LoxAPP2.xml.
This structure file contains different information as mentioned above. Specifically it concerns the following (head) elements: Loxone Miniservers remote control V 2.0.3.10 8

  • <LoxLIVE>: Information about Miniserver
  • <images>: Required icons and their source
  • <Group>: Grouping of the switch functions, the basic subdivision after space and category is a Loxone standard.
  • <Function> & <Blockfunction>: Technical and uesr interface - specific description of the switch functions.

Here is an example of an easy structure file which contains only one switch function - a switch which controls the mirror light in a bathroom:

 <?xml version="1.0" encoding="utf-8"?>
<LoxLIVE Version="16" 
         Date="22.11.2010 23:44:50" 
         globalURI="http://haus.dyndns.org/" 
         name="BeispielMiniserver">
   <images>
      <image n="1" link="images/b4f643f0-b6c4-11df-aed881fd.png"/>
      <image n="2" link="images/b4f643ef-b6c4-11df-aeddd41d.png"/>
   </images>
   <Group name="Raum">
      <Group name="Bad" image="1">
         <Group name="Beleuchtung" image="2">

            <Function name="Spiegel" 
                  UUIDaction="04da32e2-3749-11df-a16efa9dec583"
                  UUIDstate="75849462-e8cf-11df-aeb7a745eec3d">
              <detail Type="Pushbutton"/>
              <action>
                 dev/sps/io/EEE0000000AA.KGI14.0.44
              </action>
              <state>
                 dev/sps/io/EEE0000000AA.KGI14.0.44/astate
              </state>
            </Function>

         </Group>
      </Group>
   </Group>
   <Group name=“Kategorie“>
      <Group name="Beleuchtung" image="2">
         <Group name="Bad" image="1">

            <Function name="Spiegel" 
                      UUIDaction="04da32e2-3749-11df-a16efa9dec583"
                      UUIDstate="75849462-e8cf-11df-aeb7a745eec3d">
               <detail Type="Pushbutton"/>
               <action>
                  dev/sps/io/EEE0000000AA.KGI14.0.44
               </action>
               <state>
                  dev/sps/io/EEE0000000AA.KGI14.0.44/astate
               </state>
            </Function>

         </Group>
      </Group>
   </Group>
</LoxLIVE>

In the next examples, the elements of the structure file, their characteristics and their meanings will be more fully expounded and explained.

2. LoxApp2.xml

This structure file is built up in a similar way to the LoxAPP.xml file. The key differences are:

  • Categories, rooms and functions are shown in their own lists. List assignment must be carried out by the user.
  • Functions and block functions are in a common list.
  • The switching commands must be composed by the user. UUIDaction is the name of the input or object (e.g.:/dev/sps/io/UUIDaction/Ein).
  • For the conventional functions the assigned ouputs are made available as a status (<state n = "1" …/>

Example:

<?xml version="1.0" encoding="utf-8"?>
<LoxLIVE Version="16" 
         Date="22.11.2010 23:44:50" 
         globalURI="http://haus.dyndns.org/" 
         name="BeispielMiniserver">
   <images>
      <image n="1" link="images/b4f643f0-b6c4-11df-aed881fd.png"/>
      <image n="2" link="images/b4f643ef-b6c4-11df-aeddd41d.png"/>
   </images>
   <Cats>
      <Cat n="1" name="Alarm" image="2"/>
      <Cat n="2" name="Beleuchtung" image="1"/>
      <Cat n="3" name="Nicht zugeordnet" image="3"/>
   </Cats>
   <Rooms>
      <Room n="1" name="Arbeitszimmer" image="2"/>
      <Room n="2" name="Wohnzimmer" image="1"/>
      <Room n="3" name="Nicht zugeordnet" image="3"/>
   </Rooms>
   <Functions>
      <Function name="EingangI1" room="1" cat="1" rating="5" UUIDaction="a4f643ef-b6c4-81df-aeddd41d" UUIDstate="44f643ff-b6c4-81df-aeddd41d">
         <detail Type="Pushbutton" Outputs="3"/>
         <state n="1" UUID="41f643ff-b6c4-81df-aeddd41d" name="Q1"/>
         <state n="2" UUID="42f643ff-b6c4-81df-aeddd41d" name="Q2"/>
         <state n="3" UUID="43f643ff-b6c4-81df-aeddd41d" name="AQ1" Format="%.2fV"/>
      </Function>
      <Function name="Licht" room="2" cat="2" UUIDaction="54f643ef-b6c4-81df-aeddd41d" UUIDstate="64f643ff-b6c4-81df-aeddd41d" Type="LightController" Scenes="8">
         <Scene n="1" name="Szene 1"/>
         <Scene n="2" name="Szene 2"/>
         <Scene n="3" name="Szene 3"/>
         <StateScene UUID="43f647ff-b6c4-81df-aeddd41d"/>
         <State n="1" name="L1" UUID="40f6471f-b6c4-81df-aeddd41d" type="Switch"/>
         <State n="2" name="L2" UUID="41f6471f-b6c4-81df-aeddd41d" type="Dimmer"/>
         <State n="7" name="L7" UUID="42f6471f-b6c4-81df-aeddd41d" type="RGB"/>
         <State n="8" name="L9" UUID="43f6471f-b6c4-81df-aeddd41d" type="Switch"/>
      </Function>
   </Functions>
</LoxLIVE>

 3 LoxLIVE – The Root Element

The LoxLIVE element forms the root element of the structure file.

	<LoxLIVE Version="16" 
         Date="22.11.2010 23:44:50" 
         globalURI="http://haus.dyndns.org/" 
         name="BeispielMiniserver">

 

Attribute  Description
Version Specifies which version of the structure file it is. This is used to determine whether the parser has been optimized for this structure file version or if an update is required.
Date Here you can find the timestamp of the file structure, which is used to determine, using "dev / sps / LoxAPPversion", if the temporarily stored structure file is current.
globalURI If a Miniserver is accessible from the Internet and you are connected over a local network, you can find out the Miniserver's address for the remote access here.
name Specifies the user-configured name of the Miniserver.

Possible Child Elements:

  • images
  • group

4 Images – Picture Source

Contains the image elements.

<images>
   <image n="1" link="images/b4f643f0-b6c4-11df-aed881fd.png"/>
   <image n="2" link="images/b4f643ef-b6c4-11df-aeddd41d.png"/>
</images>

Possible Child Elements:

  • images

4.1 Image – Picture Elements

Represents a picture needed for the user interface.

<image n="1" link="images/b4f643f0-b6c4-11df-aed881fd.png"/>

 

Attribute Description
n Sequential number, which is used in the groups to reference the graphic.
link Specifies the command for the image to download.

5. Group – Group Element

This element is used to group functions and block functions.

<Group name="Bad" image="1">
   <Group name="Beleuchtung" image="2" rating="5">
      ...
   </Group>
</Group>

 

Attribute Description
name Name of Group.
fav [optional] Specifies whether the function is one of the favorites. If this attribute is not present, it can be assumed that it is not.
rating [optional] Says whether the function has an rating. If this attribute does not exist, you can assume there is no rating. Allowed range: 1-5
image [optional] Reference number to identify the associated image.

Possible Child Elements:

  • group
  • function
  • block function

6 Function – Simple Circuits

This element represents virtual, analogue or digital inputs and defines how these are to be displayed on the user interface and if they contain information for the communication logic. Details on how this information is considered in the communication logic, can be found in the corresponding chapter.

<Function name="Spiegel" rating="2" 
          UUIDaction="04da32e2-3749-11df-a16efa9dec583"
          UUIDstate="75849462-e8cf-11df-aeb7a745eec3d"
          fav=“true“>

 

Attribute  Description
name Name of Function.
UUIDaction With this identification number you can assign the status-events of the WebSocket to the current input values of this function.
UUIDstate [optional] With this identification number you can assign the status-events of the WebSocket to the current ouput values of this function. If this attribute is not set, then no output is assigned to this input.
fav [optional] Specifies whether the function is part of your favourites. If this attribute is not present, it can be assumed that it is not.
rating [optional] Says whether the function has an rating. If this attribute is not present, it can be assumed that there is no rating. Allowed range: 1-5

Possible Child Elements:

  • detail
  • action
  • state
  • stateAll

6.1 Detail – Representation Details

Specifies how a function is displayed and what type of wiring it uses.

e.g.:

<detail Type="Slider"
InfoOnly="NO"
Min="0,000"
Max="10,000"
Step="1,000"
Refresh="0"
Format="%.2f°"/>

 

Attribute Description
Type Type of user interface for this function and therefore also information about the possible commands and actions.
Possible values:
- Pushbutton
- Switch
- DigUpDown (two channel pushbutton)
- DigLeftRight
- UpDown (analogue)
- LeftRight
- Slider
InfoOnly [optional] Specifies whether the Function is switchable or if the user interface is just for information purposes. By default the functions are switchable.
Min [optional] Specifies the minimum value of analogue values??.
Max [optional] Specifies the maximum value of analogue values.
Step [optional] Specifies analogue values ??in the step size (for sliders, up / down, left / right.)
Refresh [optional] Minimum waiting period before new values ??for this function are useful - in the absence of attribute a default value is accepted by 50 milliseconds (standard cycle time of PLC at the Miniserver).
Format [optional] Format string to format analogue input and output values??.

6.2 action – switching command

Switching command, with which both the input value is requested (important for the HTTP request type), as can also be switched. To query the value of the input, a command is sent unchanged to the Miniserver. To switch the input is the desired command or value is appended to the command (e.g. "/ on" or "/ 4.27")

 
		    dev/sps/io/EEE0000000AA.KGI14.0.44

6.3 state – simple status request

This command is only needed for the HTTP request version. This command queries the value of the outputs. If these outputs have different values??, so the Miniserver will return a question mark and it is appropriate to use the stateAll command.

 
		    dev/sps/io/EEE0000000AA.KGI14.0.44/astate

6.4 stateAll – complex status query

With this command the value of the outputs is requested, but in contrast to the simple status query command here is a list of all outputs back to their respective values??.

 
		    dev/sps/io/EEE0000000AA.KGI14.0.44/astate

7 Function Blocks – More than simple PLC control

Block functions were introduced to pre-define switching functions, such as blind control, lighting scenes, etc., without having to use the detour of inputs and outputs for controlling.

Block functions are multiple logical and optical related switching functions. A blind-block function for example has inputs for a full ride to the top and bottom. Push buttons which regulate blades by driving up and down any length, and a switch, which regulates the blade position. This could now be realized through several simple button functions. However, it would lack the reference to each other.

Through the implementation of a block function, one has the opportunity to make an own blind-user interface, as already is defined in advance which switching commands and status messages are needed. Further most block functions are available with two versions of the user interface: a reduced one, with only the most important control functions for the collection and a big view, which provides all switching functions.

Following types of block functions exist:

  • shutter/blinds
  • pushbutton
  • dimmer
  • lightscene
  • RGB-lightscene
       ...
Attribute  Description
name Name of function.
UUIDaction With the identification number the status of events of the Web Socket version can be assigned to the current input value of the function and switching commands can be generated.
Type This attribute determines which specific block function it is. Therefore, what child elements are to be expected and how this function has to be visualized.

Possible Child Elements:

  • Vary depending on function type
  • StateXXX contain the UUID of the corresponding status events

7.1 Push button (double) +/-

Input:

  • Push button

Command:

  • Value
  • e.g.: dev/sps/io/[uuid]/2.0

Status:

  • On/Off

7.2 Push Button (double) On/Off

Input:

  • Push button

Command:

  • on, off
  • e.g.: dev/sps/io/[uuid]/on

Status:

  • On/Off

7.3 Burglar Alarm

Input:

  • Push button: Activate, activate with delay, deactivate, and acknowledge alarm

Command:

  • off, deactivate alarm
  • on, activate alarm
  • delayed on, activate alarm with delay
  • quit, acknowledge alarm

Status:

  • Digital: StateActive, StateSilentAlarm, StateAcusticAlarm, StateOpticAlarm, StateInternalAlarm, StateExternalAlarm, StateRemoteAlarm
  • Digital and Text: StateMovement, StateGlasses, StateWindows, StateDoors, StateMisc

Time and source of alarm will be sent with the corresponding Status-UUID as Text status.

7.4 selection push button

Input:

  • Pushbutton

Command:

  • Value
  • e.g.: dev/sps/io/[uuid]/2.0

Status:

  •  On/Off

7.5 operating time counter

Input:

  • Push button: reset, reset all. start/stop

Command:

  • reset
  • resetAll
  • enable
  • disable

Status:

  • Digital: State
  • Analogue: StateTotal (seconds), StateLast (seconds)

7.6 dimmer

Input:

  • Slide: new position

Command:

  • Analogue Value

Status:

  • actual position

7.7 heating mixer

Input:

  • Temperature
  • Stop

Command:

  • Push button: Stop, StopOff
  • Analogue: Value set temperature
  • e.g.: dev/sps/io/[uuid]/23.0
  • dev/sps/io/[uuid]/stop

Status:

  • set temperature
  • actual temperature
  • Mixer position (0-10V = 0-100%)
  • Stop
  • Error

7.8 blind

Input:

  • Push button: Up, down, completely up, completely down, shade
  • Checkbox: automatic (not yet implemented)

Command:

  • up, upoff,
  • down, downoff,
  • fullup,
  • fulldown,
  • shade,
  • auto, noauto
  • stop

Status:

  • Digital: StateUp, StateDown
  • Analogue: StatePos (0.0-1.0), StateShade (Shade 0.0-1.0)

7.9 automaticjalousie

Input:

  • Push button: Up, down, completely up, completely down, shade, automatic shading

Command:

  • up, upoff,
  • down, downoff,
  • fullup,
  • fulldown,
  • shade,
  • auto, noauto
  • stop

Status:

  • Digital: StateUp, StateDown, StateAutoShade, StateSafety
  • Analogue: StatePos (0.0-1.0), StateShade (Shade 0.0-1.0)

7.10 multifunction switch

Input:

Pushbuttons/ switches

Command:

  • on, off, pulse
  • e.g.: dev/sps/io/[uuid]/pulse

Status:

  • -1 = Duration on, 0 = off, otherwise remaining time in seconds

7.11 lightscene

Input:

  • Pushbutton: +, -
  • Combobox: name choice

Command:

  • off, Scene name or value 0 – x (0=off, 1, 2, 3, ... = light scene)
  • z. B.: dev/sps/io/[uuid]/[scene name or number]

Status:

  •  actual scene

7.12 lightscene (lern)

Input:

  • Combobox: Name choice
  • Shift: Analogue value of different Inputs
  • Pushbutton: Learns the actual configurations

Commands:

  • off, Scene name or value 0 – x (0=off, 1, 2, 3, ... = light scene)
  • e.g.: dev/sps/io/[uuid]/[scene name or number]
<Blockfunction name="LichtWZ" Type="LightsceneLearn" 
               UUIDaction="5bba3129-3757-11df-9ce39e108d4dd4"  
               Scenes="5">
   <Scene nr="1" name="Alles voll auf"/>
   <Scene nr="2" name="Stimmung"/>
   <Scene nr="3" name="Lesen"/>
   <Scene nr="4" name="Szene 4"/>
   <Scene nr="5" name="Szene 5"/>
   <StateScene UUID="5bba3129-3757-11df-9ce39e108d4d742b"/>
   <State nr="1" UUID="5bba3129-3757-21df-9ce39e108d4d742b"/>
   <State nr="2" UUID="5bba3129-3757-31df-9ce39e108d4d742b"/>
   <State nr="3" UUID="5bba3129-3757-41df-9ce39e108d4d742b"/>
   <State nr="4" UUID="5bba3129-3757-51df-9ce39e108d4d742b"/>
   <State nr="5" UUID="5bba3129-3757-61df-9ce39e108d4d742b"/>
   <State nr="6" UUID="5bba3129-3757-71df-9ce39e108d4d742b"/>
   <State nr="7" UUID="5bba3129-3757-81df-9ce39e108d4d742b"/>
   <State nr="8" UUID="5bba3129-3757-91df-9ce39e108d4d742b"/>
</Blockfunction>

7.13 lighting control

Input:

  • Combobox: Name choice
  • Shift: Analogue values of single inputs
  • Pushbutton: Learns the actual configurations

Commands:

  • off, on, Scene name or value 0 – x (0=off, 1, 2, 3, ... = light scene)
  • e.g.: dev/sps/io/[uuid]/[scene name or number]
  • Analogue value
  • e.g.: dev/sps/io/[uuid]/[Ausgang]/Analogue Value
  • Overwriting of a single output
  • e.g.: dev/sps/io/[uuid]/AI1/Analogue Value (AI1-AI12 are possible)
  • A color value is specified as follows:
  • %-Wert Rot + (%-Wert Grün * 1000) + (%-Wert Blau * 1000000)
  • Lerning
  • e.g.: dev/sps/io/[uuid]/[Scene name od – number]/learn
  • Reset (Reset output gives an impulse for e.g. everything turns out in a room)
  • e.g.: dev/sps/io/[uuid]/reset
  • Reset all (ResetAll-Outputs and Reset outputs give an impulse e.g. everything turns off in the house)
  • e.g.: dev/sps/io/[uuid]/resetall

Status:

  • actual scene
  • actual values of differet outputs
<Blockfunction name="LichtWZ" Type="LightController" 
               UUIDaction="5bba3129-3757-11df-9ce39e108d4dd4"  
               Scenes="8">
   <Scene nr="1" name="Alles voll auf"/>
   <Scene nr="2" name="Stimmung"/>
   <Scene nr="3" name="Lesen"/>
   <Scene nr="4" name="Szene 4"/>
   <Scene nr="5" name="Szene 5"/>
   <Scene nr="6" name="Szene 6"/>
   <Scene nr="7" name="Szene 7"/>
   <Scene nr="8" name="Szene 8"/>
   <StateScene UUID="5bba3129-3757-11df-9ce39e108d4d742b" type="Switch"/>
   <State nr="1" UUID="5bba3129-3757-21df-9ce39e108d4d742b" type="Dimmer" name="I1"/>
   <State nr="2" UUID="5bba3129-3757-31df-9ce39e108d4d742b" type="Dimmer" name="I2"/>
   <State nr="3" UUID="5bba3129-3757-41df-9ce39e108d4d742b" type="RGB" name="I3"/>
   <State nr="4" UUID="5bba3129-3757-51df-9ce39e108d4d742b" type="RGB" name="I4"/>
   <State nr="5" UUID="5bba3129-3757-61df-9ce39e108d4d742b" type="Dimmer" name="I5"/>
   <State nr="6" UUID="5bba3129-3757-71df-9ce39e108d4d742b" type="Switch" name="I6"/>
   <State nr="7" UUID="5bba3129-3757-81df-9ce39e108d4d742b" type="Switch" name="I7"/>
   <State nr="8" UUID="5bba3129-3757-91df-9ce39e108d4d742b" type="Switch" name="I8"/>
   <State nr="9" UUID="5bba3129-3757-91df-9ce39e108d4d742b" type="Switch" name="I9"/>
   <State nr="10" UUID="5bba3129-3757-91df-9ce39e108d4d742b" type="Switch" name="I10"/>
   <State nr="11" UUID="5bba3129-3757-91df-9ce39e108d4d742b" type="Switch" name="I11"/>
   <State nr="12" UUID="5bba3129-3757-91df-9ce39e108d4d742b" type="Switch" name="I12"/>

7.14 RGB light scene

Input:

  • Pushbutton: +, -
  • Combobox: Name choice
  • Shift: Analogue value of single Inputs

Commands:

  • off, Scene name or  value 0 – x (0=off, 1, 2, 3, ... = Light scene)
  • e.g.: dev/sps/io/[uuid]/[scene name or number]
  • Overwriting a color value
  • e.g.: dev/sps/io/AI/Analogue Value
  • A color value is specified as follows:
  • %-Wert Rot + (%-Wert Grün * 1000) + (%-Wert Blau * 1000000)

Status:

  • actual scene
  • actual value of single outputs
<Blockfunction name="LichtWZ" Type="LightsceneRGB" 
               UUIDaction="5bba3129-3757-11df-9ce39e108d4dd4"  
               Scenes="3">
   <Scene nr="1" name="Alles voll auf"/>
   <Scene nr="2" name="Stimmung"/>
   <Scene nr="3" name="Lesen"/>
   <StateScene UUID="5bba3129-3757-11df-9ce39e108d4d742b"/>
   <StateRed UUID="5bba3129-3757-13df-9ce39e108d4d742b"/>
   <StateGreen UUID="5bba3129-3757-14df-9ce39e108d4d742b"/>
   <StateBlue UUID="5bba3129-3757-15df-9ce39e108d4d742b"/>
</Blockfunction>

7.15 room control

Input:

  • Temperature
  • on, off, stop

Command:

  • Pushbutton: On, Off
  • Switch: Stop, StopOff
  • Analogue: Value set temperature
  • e.g.: dev/sps/io/[uuid]/23.0

Status:

  • set temperature
  • actual temperature
  • valve postion (0-10V = 0-100%)
  • stop
  • error

 

<Blockfunction name="Raum" Type="Roomcontroller" 
               UUIDaction="5bba3129-3757-11df-9ce39e108d44">
   <StateSoll UUID="5bba3129-3757-11df-9ce39e108d4d742b"/>
   <StateIst UUID="5bba3129-3857-11df-9ce39e108d4d742b"/>
   <StatePos UUID="5bba3129-3957-11df-9ce39e108d4d742b"/>
   <StateStop UUID="5bba3129-3a57-11df-9ce39e108d4d742b"/>
   <StateError UUID="5bba3129-3a57-11df-9ce39e108d4d742b"/>
</Blockfunction>

7.16 sauna control 1

Input:

  • Temperature
  • sauna operation
  • ventilation
  • hourglass

Command:

  • temp/80 (Set- temperature: set on 80°C)
  • on, dry, off (Sauna on, start drying, Sauna off)
  • fan, fanon, fanoff (turn on/off ventilation or switch it)
  • starttimer (start hourglass)
  • timer/600 (set hourglass for 600 seconds)
  • e.g.: dev/sps/io/[uuid]/on
  • e.g.: dev/sps/io/[uuid]/timer/600

Status:

  • heating capacity: 0 – 100 %
  • temperature in °C
  • bank temperature * (if 0.0, then the sensor is not connected)
  • drying phase active
  • ventilation active
  • open door status
  • presence sensor
  • error (overheating)
  • hourglass (remaining time in seconds)
<Blockfunction name="FinnSauna" Type="Sauna" 
               UUIDaction="5bba3129-3757-11df-9ce39e208d4d0">
   <StatePower UUID="5bba3129-3757-11df-9ce39e208d47423"/>
   <StateTemp UUID ="5bba3129-3757-11df-9ce39e208d4d742d"/>
   <StateBench UUID ="5bba3129-3757-11df-9ce39e308d4d742d"/>
   <StateDry UUID ="5bba3129-3757-11df-9ce39e408d4d742d"/>
   <StateFan UUID ="5bba3129-3757-11df-9ce39e508d4d742d"/>
   <StateDoor UUID ="5bba3129-3757-11df-9ce39e608d4d742d"/>
   <StatePresence UUID ="5bba3129-3757-11df-9ce39e708d742d"/>
   <StateError UUID ="5bba3129-3757-11df-9ce39e808d4d742d"/>
   <StateTimer UUID ="5bba3129-3757-11df-9ce39e908d4d742d"/>
</Blockfunction>

7.17 sauna control 2

Input:

  • temperature
  • humidity
  • sauna operation
  • ventilation
  • hourglass

Command:

  • mode/0 0=Sauna off
  • 1= finnish operating manual
  • 2= moist operation manual
  • 3= finnish sauna (automatic, 80 °, no evaporator)
  • 4= herbal sauna (automatic, 45 °, 50% humidity))
  • 5= soft bath (automatic, 50 °, 50% humidity)
  • 6= hot air bath (automatic, 45 °, 20% humidity)
  • temp/80 (Set-temperature: set on 80°C)
  • humidity/40 (Humidity: set on 40%)
  • on, dry, off (Sauna on, start drying, sauna off)
  • fan, fanon, fanoff (set on/off or switch ventilation))
  • start timer (start hourglass)
  • timer/600 (Set timer on 600 seconds)
  • e.g.: dev/sps/io/[uuid]/on
  • e.g.: dev/sps/io/[uuid]/timer/600

Status:

  • heating capacity: 0 - 100%
  • evaporation capacity: 0 - 100%
  • temperature in °C
  • relative humidity in%
  • bank temperature * (if 0.0, then the sensor is not connected)
  • drying phase active
  • ventilation active
  • open door status
  • presence sensor
  • insufficient water in the evaporator
  • error (overheating)
  • hourglass (remaining time in seconds)
<Blockfunction name="Sauna" Type="SaunaVapor" 
               UUIDaction="5bba3129-3757-11df-9ce39e208d4d0">
   <StatePower UUID="5bba3129-3757-11df-9ce39e208d47423"/>
   <StateVaporPower UUID="5bba3129-3758-11df-9ce39e208d47423"/>
   <StateTemp UUID ="5bba3129-3757-11df-9ce39e208d4d742d"/>
   <StateHumidity UUID="5bba3229-3757-11df-9ce39e208d47423"/>
   <StateBench UUID ="5bba3129-3757-11df-9ce39e308d4d742d"/>
   <StateDry UUID ="5bba3129-3757-11df-9ce39e408d4d742d"/>
   <StateFan UUID ="5bba3129-3757-11df-9ce39e508d4d742d"/>
   <StateDoor UUID ="5bba3129-3757-11df-9ce39e608d4d742d"/>
   <StatePresence UUID ="5bba3129-3757-11df-9ce39e708d742d"/>
   <StateLessWater UUID="5bbc3129-3757-11df-9ce39e208d47423"/>
   <StateError UUID ="5bba3129-3757-11df-9ce39e808d4d742d"/>
   <StateTimer UUID ="5bba3129-3757-11df-9ce39e908d4d742d"/>
</Blockfunction>

7.18 timer

The timer is a special case. The entries of the time sent through a special status (DT_DAYTIMER und EvDataDaytimer). There are always transferred all times. 

Input:

  • Trigger
  • Reset

Command:

  • set/num/entry1/entry2/… Sends all time slots

num= Number of time slots
entry = Calendar mode;from; to; activation necessary; value
from and to are the minutes since midnight
‚Value‘ is only required with an analogue time switch

  • pulse          Set Trigger for activation for time slot
  • reset
  • z. B.: dev/sps/io/[uuid]/pulse
  • z. B.: dev/sps/io/[uuid]/reset
  • dev/sps/io/[uuid]/set/2/3;600;1200;0;23.0/4;600;1200;1;24.0

Status:

  • output
  • operating mode
<Blockfunction name="Uhr" Type="DayTimer"
               modes="12" analog="true" default="21.0"
               UUIDaction="5bba3129-3757-11df-9ce39e208d4d0">
   <mode nr="-7" name="Test"/>
   <mode nr="-6" name="Alle abwesend"/>
   <mode nr="0" name="Feiertag"/>
   <mode nr="1" name="Urlaub"/>
   <mode nr="2" name="Freier Tag/Schulferien"/>
   <mode nr="3" name="Montag"/>
   <mode nr="4" name="Dienstag"/>
   <mode nr="5" name="Mittwoch"/>
   <mode nr="6" name="Donnerstag"/>
   <mode nr="7" name="Freitag"/>
   <mode nr="8" name="Samstag"/>
   <mode nr="9" name="Sonntag"/>
   <State UUID ="5bba3129-3757-11df-9ce39e808d4d742d"/>
   <StateMode UUID ="5bba3129-3757-11df-9ce39e908d4d742d"/>
</Blockfunction>

7.19 push button

Input:

  • Pushbutton

Command:

  • on, off, pulse
  • z. B.: dev/sps/io/[uuid]/pulse

Status:

  • On/Off
<Blockfunction name="Taster" Type="Pushbutton" 
               UUIDaction="5bba3129-3757-11df-9ce39e108d44">
   <State UUID="5bba3129-3757-11df-9ce39e108d4d742b"/>
</Blockfunction>

7.20 status

Status:

  • Text
<Blockfunction name="Text" Type="Textstate" 
               UUIDaction="5bba3129-3757-11df-9ce39e108d44">
   <State UUID="5bba3129-3757-11df-9ce39e108d4d742b"/>
</Blockfunction>

 Changes in the text have to be sent in an EvDataText format. Optionally, an icon may be present.

 7.21 tracker

Status:

  • Text
<Blockfunction name="Texttracker" Type="Tracker" Maxentries="30"
               UUIDaction="5bba3129-3757-11df-9ce39e108d44">
</Blockfunction>

Changes in the text have to be sent in an EVDataText format. The individual lines of text are separated by a vertical bar (0x7c).

7.22 door

Input:

  • Push button: Open, close, stop

Command:

  • open, close, stop
  • z. B.: dev/sps/io/[uuid]/open

Status:

  • actual position (0.0 = open, 1.0 = closed)
  • activity indicator
<Blockfunction name="Einfahrt" Type="Door" 
               UUIDaction="5bba39-757-11df-9ce39e208d4d7420">
   <StatePos UUID="5bba3129-3757-11df-9ce39e208d4d723"/>
   <StateActive UUID ="5bba3129-3757-11df-9ce39e108dd742d"/>
</Blockfunction>

7.23 staircase light switch

Input:

  • Pushbutton/ switch

Command:

  • on, off, pulse
  • z. B.: dev/sps/io/[uuid]/pulse

Status:

  • -1 = Duration on, 0 = off, otherwise open time in seconds
<Blockfunction name="StLS" Type="StairwayLS" 
               UUIDaction="5bba3129-3757-11df-9ce39e108d44">
   <State UUID="5bba3129-3757-11df-9ce39e108d4d742b"/>
</Blockfunction>