Gira S1 Quick guide

KNX
Product documentation
Status of the documentation:
10.08.2020
Gira S1
Order No. 2089 00
Gira S1 (Fig. 1:1)

Order No. 2089 00 Page 2
Contents
1. Configuration of the Gira S1 at a glance ........................................................................................4
1.1. Installation (see Chapter 6) .................................................................................................... 4
1.2. Configuration in the ETS (see Chapter 7)............................................................................... 4
1.3. Configuration in the Gira Device portal (see Chapter 9) ........................................................ 4
1.4. Configuration of access to the application (see Chapter 9.7) ................................................ 4
2. Product description ........................................................................................................................5
2.1. Functions................................................................................................................................ 5
2.2. KNX Secure Ready .................................................................................................................6
2.3. Functional description............................................................................................................ 6
2.4. Gira Device portal................................................................................................................... 7
2.5. Client software (Gira S1 Windows client) .............................................................................. 8
3. Application scenarios .....................................................................................................................9
3.1. Access to the Gira X1............................................................................................................. 9
3.2. Configuration and control of the Gira HomeServer .............................................................10
3.3. Access to KNX installations .................................................................................................11
3.4. Access to websites on the remote network......................................................................... 12
3.5. Access via other TCP protocols ...........................................................................................13
3.6. User rights and user groups................................................................................................. 13
4. Time server ...................................................................................................................................14
5. Data logger ...................................................................................................................................15
5.1. Access to the data logger archive ........................................................................................16
6. Installation ....................................................................................................................................17
6.1. Device design....................................................................................................................... 17
6.2. Installation and electrical connection .................................................................................. 17
7. Configuration in the ETS ..............................................................................................................19
7.1. Creating Gira S1 as a device in the ETS............................................................................... 19
7.2. Assigning physical addresses .............................................................................................. 20
7.3. Setting the IP address, subnet mask and address of the default gateway ..........................21
7.4. Transferring application programs and configuration data .................................................22
7.5. Parameters ...........................................................................................................................23
7.6. Object table ..........................................................................................................................27
8. Displays and operation .................................................................................................................33
8.1. LED status displays.............................................................................................................. 33
8.2. Factory reset ........................................................................................................................34
8.3. Firmware update of the device ............................................................................................35
9. Using the Gira Device portal ........................................................................................................36
9.1. Start page............................................................................................................................. 36
9.2. Device overview ...................................................................................................................37
9.3. Registering a Gira S1 ...........................................................................................................38

Order No. 2089 00 Page 3
9.4. Links .....................................................................................................................................39
9.5. Notifications .........................................................................................................................40
9.6. Device data ..........................................................................................................................41
9.7. Access to applications .........................................................................................................42
9.8. Configuring notifications ......................................................................................................44
9.9. Portal user administration ....................................................................................................46
10.Gira S1 Windows client ................................................................................................................49
10.1.Installation............................................................................................................................ 49
10.2.Connecting to the Gira Device portal ...................................................................................50
10.3.Configuring the access options of a Gira S1 ........................................................................52
10.4.Ending a remote access connection .................................................................................... 59
11.Technical data ..............................................................................................................................60
11.1.Accessories .......................................................................................................................... 60
12.Frequently asked questions (FAQs) ..............................................................................................61
13.Troubleshooting and support .......................................................................................................63
14.Gira S1 device website .................................................................................................................64
15.License agreement .......................................................................................................................65

Configuration of the Gira S1 at a glance
Order No. 2089 00 Page 4
1. Configuration of the Gira S1 at a glance
This page displays the configuration process at a glance. You can find more detailed instructions for
start-up in the chapters that are indicated below in the respective steps.
1.1. Installation (see Chapter 6)
• Mount the Gira S1.
• Connect the power supply,
• the KNX connection and
• the network connection.
1.2. Configuration in the ETS (see Chapter 7)
• Create the Gira S1 as a device in the ETS.
• Assign the physical addresses for the Gira S1.
• Assign the required group addresses.
• Transfer the application program and configuration.
1.3. Configuration in the Gira Device portal (see Chapter 9)
• Register the Gira S1.
• Create the users.
• Transfer device ownership, if necessary.
• Optionally, you can set up notifications, for example.
1.4. Configuration of access to the application (see Chapter 9.7)
• First generate the activation codes in the Gira Device portal.
• Then enter the codes in the corresponding input screen of the
relevant application (e.g. Gira X1 app, Gira HomeServer app,
Gira S1 Windows client or Gira Project Assistant).
2089 00
Gira S1
KNX 24 V DC
LAN

Product description
Order No. 2089 00 Page 5
2. Product description
2.1. Functions
• Secure remote access to your smart home with KNX using the Gira HomeServer or Gira X1 app.
• Secure remote access to web-based visualisations.
• Secure remote maintenance and remote programming of the Gira HomeServer, Gira G1, Gira X1,
Gira L1, and Gira KNX IP router.
• Secure remote programming via the Gira HomeServer Expert.
• Secure remote programming via the Gira Project Assistant (GPA).
• Secure remote maintenance and remote programming of KNX projects using ETS4 or ETS5 in con-
junction with the Gira Project Assistant or the Gira S1 Windows client. The programming and diag-
nosis is supported via a group and bus monitor.
• Secure remote access to HTML pages (e.g. camera, NAS, router or switch) in the smart home net-
work (depending on the technical implementation of the respective device website).
• Secure data transfer courtesy of SSL/TLS encryption.
• Portal server is located in Germany and is subject to German laws on data.
• Independence from internet provider and routers used. Secure remote access even with IPv6 Dual
Stack Lite - (e.g. with Unitymedia), LTE, or UMTS connections.
• Management of access to the secure connections via KNX communication objects, Gira X1 app,
Gira HomeServer app, and QuadClient.
• Status signalling of the secure connections via KNX communication objects.
• Send KNX status messages via e-mail. An attachment can be added to the e-mail, as an option.
• Send KNX status messages by SMS or voice call via the chargeable, additional service sms77 or
MessageBird.
• Optimised KNX IP communication, for mobile or very slow connections.
• Supports the accelerated transfer of the ETS to KNXnet/IP devices via a direct KNX IP connection.
• An integrated Ethernet switch (two RJ45 connections) simplifies the connection of multiple IP
devices. This enables multiple Gira S1 or other IP devices in the distribution to be connected without
the aid of other active components.
• The Gira S1 can be used as a data logger. It incorporates a card reader for microSDHC cards up to
32 GB. The KNX EIB telegrams in an ETS4-compliant format can be recorded to the card for analysis
purposes. The card memory can be used as a ring memory or as a ROM.
• As a clock, the Gira S1 can send the time and date to the bus at configurable intervals. It is possible
to trigger the sending of the current time and the current date via a trigger.

Product description
Order No. 2089 00 Page 6
2.2. KNX Secure Ready
The Gira S1 is prepared for KNX Secure. The necessary FDSK (Factory Default Setup Key) are located
on the side of the device as a sticker and are also included within the device packaging. Devices with-
out these stickers are not "Secure Ready".
For maximum safety, we recommend removing the stickers on the device.
You cannot restore the FDSK yourself.
Keep the FDSK safe. If you lose the FDSK despite all care, please contact our support.
2.3. Functional description
The Gira S1 is installed in the customer's home network and prepares the home network for secure
access via the Internet.
The Gira S1 is connected to the home network via Ethernet. It connects to the Gira Device portal auto-
matically using the existing Internet access. Communication between the Gira S1 and the Gira Device
portal is encrypted using AES and secured with digital certificates (for details, see chapter 2.4.1
“HTTPS proxy httpaccess.net”).
You can already access almost all network devices using the Internet.
The Gira Smarthome App and the GPA can communicate directly with the Gira S1 via the Gira Device
portal. With other Windows applications, such as ETS or Gira Expert, access is via the Gira S1 Win-
dows client (see chapter 2.5 “Client software (Gira S1 Windows client)”).
If you have a KNX installation in your house, you can connect it to the Gira S1 using the KNX connec-
tion if desired. As a result, the KNX devices can be accessed from anywhere, e.g. with the ETS.

Product description
Order No. 2089 00 Page 7
Figure 1: Overview of secure remote access using the Gira S1
2.4. Gira Device portal
You manage your Gira S1 using the Gira Device portal (https://geraeteportal.gira.de). Through the Gira
Device portal, you can also provide other users with access to your Gira S1 and hence to the KNX and
network devices in your home network.
You can assign any number of Gira S1 devices to one account on the Gira Device portal. If you or
persons authorised by you wish to access end devices in your home network, the Gira Device portal
always plays the part of the intermediary. The Gira Device portal does not store the data transferred,
but only forwards it on.
The server for the Gira Device portal is operated in Germany in compliance with the German data pro-
tection guidelines.
Note
For technical reasons, the use of the Gira Device portal requires the use of cookies in the web browser.
Blind
Switch
Lamp
Gira device portal
or
Gira
HomeServer
Gira X1
At homeInternet
Secure remote access
via Gira X1 App /
Gira HomeServer App
Remote maintenance/
programming: Gira X1 via GPA,
HomeServer via Experte,
KNX via ETS
While away
Gira S1Router
= encrypted
data transmission

Product description
Order No. 2089 00 Page 8
2.4.1. HTTPS proxy httpaccess.net
Most network devices today, such as cameras or network printers, have an integrated web server for
access with a web browser. Access via the Gira Device portal is especially easy in such cases. Each
network device that can be accessed via a Gira S1 automatically receives its own name under the
domain httpaccess.net. Using this name, you can access the corresponding network device from any-
where using a web browser.
All communication via the Internet is also encrypted, and user authentication occurs according to the
access authorisation set on the Gira Device portal for the Gira S1.
To save you from having to remember links, the Gira Device portal manages a list of links of the end
devices, which you can access at httpaccess.net. If the network device supports UPnP, the Gira Device
portal can enter it automatically in the list of links. You can also enter devices in the list manually if
they are not added automatically.
2.4.2. Communication – Secure, reliable and easy to handle
For communication with the portal server, the Gira S1 uses the standard protocols HTTPS, TLS/SSL
and WebSockets. All data is encrypted using AES.
Gira S1 and the Gira Device portal authenticate each other with digital certificates and RSA key pairs.
The certificates are issued by our own certification office.
Through the use of standard protocols and because the Gira S1 actively connects to the Gira Device
portal, we achieve the best possible compatibility with the existing infrastructure. For your Internet
router, the Gira S1 communication is no different from the encrypted connection of your web browser,
e.g. for online banking or Google searches.
The advantage for you is that the Gira S1 works without requiring any complex configuration. This is
a major advantage compared to other approaches to secure remote access, such as VPN or SSH tun-
nelling.
In contrast to other solutions, remote access even works via a mobile phone or IPv6 connection, even
if it doesn't have a unique IP address that can be accessed externally.
2.4.3. Gira S1 notifications
KNX group objects and system events such as the logging in/logging out of a Gira S1 to/from the
portal can be used to generate notifications in the portal server. In addition to static texts, they may
also contain values from the KNX or even an attachment, such as a camera image.
These notifications can be configured for forwarding via e-mail, phone or text message. Send KNX
status messages by text message or voice call via the chargeable, additional service sms77 or Mes-
sageBird.
2.5. Client software (Gira S1 Windows client)
You install the Gira S1 Windows client on a Windows computer. Through the Gira S1 Windows client,
other applications running on your computer are given access to your devices without having to sup-
port the remote access function themselves.
The Gira S1 Windows client establishes an encrypted connection to the Gira S1 via the Gira Device
portal. This connection is made available to other applications on your computer and on your local
network so that they can access devices on the remote network. Examples:
• You can configure KNX devices via KNXnet/IP using the ETS.
• You can configure a HomeServer using the Gira HomeServer Expert.
• You can access a Windows computer using a remote desktop connection.
• Using SSH and/or X Windows, you can access a Linux computer or embedded Linux devices.
• Many other use cases are supported via freely configurable TCP port forwarding.

Application scenarios
Order No. 2089 00 Page 9
3. Application scenarios
3.1. Access to the Gira X1
In conjunction with the Gira X1, the building functions can be controlled using secure remote access
with the Gira X1 app.
The programming or maintenance of the Gira X1 using the Gira Project Assistant (GPA) can also be
carried out via the secure remote access.
Figure 2: Configuration and operation of the Gira X1
Blind
Switch
Lamp
Gira device portal Gira X1
At homeInternet
Secure remote access
via Gira X1 App
Remote maintenance/
programming: Gira X1 via GPA,
While away
Gira S1Router
= encrypted
data transmission

Application scenarios
Order No. 2089 00 Page 10
3.2. Configuration and control of the Gira HomeServer
Access to the Gira HomeServer works in a similar way to access to the KNX installation. On the one
hand, the KNX installation is accessed via the Gira HomeServer using the Eiblib/IP protocol, while on
the other hand, the configuration is supported with the Expert. In addition, you can access the KNX
installation directly via the interface function of the Gira S1. Here too, all data transmitted via the Inter-
net is encrypted.
Figure 3: Secure configuration of the Gira HomeServer with the Gira S1.
Note
Since automatic detection is not possible for the Eiblib/IP and the HomeServer configuration protocol,
the following must be observed for the use of these protocols via remote access: The Gira S1 Windows
client makes protocol transmission available locally via the IP address 127.0.0.1. In other words, if an
Eiblib/IP connection is configured in the ETS, for example, 127.0.0.1 must be entered for the IP
address for use via remote access (instead of the IP address of the Gira HomeServer on the remote
network). The same applies for downloading with the Expert. For more information, see chapter 10.3.2
“Configuring the Gira HomeServer remotely and using the Eiblib/IP”.
Blind
Switch
Lamp
Gira device portal
Gira
HomeServer
At homeInternet While away
Gira S1Router Gira
KNX IP Router
Gira G1
Remote maintenance/
programming: Gira S1 Windows Client,
HomeServer via Experte,
KNX via ETS
Secure remote access via
Gira HomeServer App
= encrypted
data transmission

Application scenarios
Order No. 2089 00 Page 11
3.3. Access to KNX installations
The Gira S1 Windows client enables secure access to KNX installations via the Internet. For this pur-
pose, the Gira S1 Windows client is installed on the computer and started in parallel to the ETS. Since
the KNX/IP protocol is completely unprotected today, the Gira S1 transfers all KNX/IP data encrypted
with SSL/TLS to the Gira Device portal while the portal, in turn, exchanges this data encrypted with
SSL/TLS with the Gira S1 Windows client. The Gira S1 Windows client then provides the KNX/IP data
for the ETS unencrypted locally on the computer using the ETS so that the ETS can be used completely
transparently in the usual way.
The Gira Project Assistant (GPA) constitutes an alternative to the Gira S1 Windows Client. To use this
option, you must create a GPA project, activate the "Remote maintenance" option in the project scope,
and select "Gira S1 remote access module" as the remote access method. Then, enter your remote
access ID and authentication key in the "Configure remote access" area. You only need to set this up
once. Now click on "Connect" (top right). The GPA will establish the connection to the Gira S1. You
can now start the ETS and see the remote system's ETS interfaces in the "Bus" area. The interfaces
found have the prefix "GPA".
Figure 4: Secure remote access to the KNX installation with the Gira S1.
Once a connection to a specific Gira S1 has been established using the Gira S1 Windows client (see
chapter 10.2 “Connecting to the Gira Device portal”), the KNX/IP interfaces available on the remote
network appear in the ETS as if the ETS itself were on the remote network. To avoid confusion with
other devices on your own network, it is possible to append a text to the device name normally dis-
played in the ETS. In addition, it is also possible to make only the KNX/IP interface of the Gira S1
available for the sake of simplicity. In addition to the KNX/IP interfaces, all devices that can be loaded
directly via IP (see chapter “Accelerate transfer: Select transfer path IP”) are made known to the ETS
so that these accelerated downloads also work via remote access. For more information, see chapter
10.3 “Configuring the access options of a Gira S1”.
Blind
Switch
Lamp
Gira device portal
At homeInternet
Remote maintenance / programming:
GPA / Gira S1 Windows Client,
KNX via ETS
While away
Gira S1Router
= encrypted
data transmission

Application scenarios
Order No. 2089 00 Page 12
3.3.1. Limitations and authorisation of access rights via KNX communication objects
If the Gira S1 is added to an ETS project, its communication objects can be used to prohibit or allow
access options via KNX, even at runtime. The access rights limitations defined via the KNX in the
remote installation always take precedence over the definitions in the portal. In this way, remote
access can be deactivated completely, regardless of the settings in the Gira Device portal, through
the use of group telegrams.
3.4. Access to websites on the remote network
Remote access via the Gira S1 enables secure access to websites on the remote network. For this
purpose, the unencrypted (HTTP) data on the remote network (see Figure 5) is transported to the Gira
Device portal server via an encrypted SSL/TLS connection and then to the web browser via an HTTPS
connection.
Figure 5: Secure access to websites via remote access.
The easiest way to access websites on the remote network via HTTP is through the Gira Device portal.
Access via the Gira Device portal is quick to configure. For a description on this, see chapter 9.4
“Links”.
TV receiver
Washing machine
IP camera
Gira device portal
At homeInternet While away
Gira S1Router
= encrypted
data transmission

Application scenarios
Order No. 2089 00 Page 13
3.5. Access via other TCP protocols
Using the Gira S1, it is possible to use nearly all TCP-based protocols securely over the Internet.
The Remote Desktop Protocol (RDP), which Microsoft has defined for remote access to Windows com-
puters, is widely used, among others. Together with the Gira S1 Windows client, you can easily con-
figure access. For more information, see chapter 10.3.3 “Using other TCP protocols via remote
access”.
3.6. User rights and user groups
Irrespective of the type of access (e.g. websites, KNX, HomeServer, remote desktop connection),
access rights for the predefined user groups “residents” and “installer” can be configured for each
relationship between the Gira S1 and portal user and controlled dynamically using KNX communica-
tion objects.
A typical scenario after handing over the keys could look like this:
• With the Gira S1, one or more portal users of the electrical trade company/system integrator are
linked in the role of the “installer” for maintenance purposes.
• With the Gira S1, one or more portal users are linked in the role of “resident”, typically all family
members, for visualisation on a smartphone and website access.
• The Gira S1 is configured using the parameters in the ETS in such a way that the users with the
“residents” user group always have access; in addition, the users in the “installer” user group have
access by default.
• If the installer wants to access the system for a maintenance appointment or due to a call from the
home owner, he/she contacts the home owner. The home owner then grants the installer access by
selecting an option in his/her visualisation or using the corresponding communication object. Auto-
matic deactivation of access after a certain period of time is also easy to arrange using logic or a
timer.
• For security-sensitive residents, it is also possible to deactivate remote access completely using a
button or visualisation. In this case, the Gira S1 no longer reports to the portal, and remote access is
impossible.
• The Gira S1 indicates that a connection has been established via remote access using KNX commu-
nication objects, thereby making suitable processing in a visualisation/logic (e.g. e-mail when some-one
connects) easily possible.
In addition, software access, such as visualisations, can be controlled using activation codes. Each
user can create any number of codes on each Gira S1 to which he/she has access, e.g. for visualisation
(see chapter 9.7 “Access to applications”).

Time server
Order No. 2089 00 Page 14
4. Time server
As a time server, the Gira S1 can send the current time to the KNX bus at configurable intervals. For
this, first you activate the "Time server" parameter in the "General" parameter view so that the param-
eter page “Time server” becomes visible (see chapter 7.5 “Parameters”). You configure then the
respective desired interval with the "Send time" and "Send date" parameters. The time sent is obtained
from the system time. This is synchronised with a NTP server which can be configured via device
website. The interval for sending the communication object 52 “Date and time” to the KNX bus is the
shorter one of the parameters "Send time" (communication object 50) and "Send date" (communica-
tion object 51) if they differ.
The device can be configured for various UTC time zones. The "Time zone" parameter used for this is
located in the "General" parameter view.
Time changeover is taken into account either automatically depending on the time zone set or not at
all. A "Generic Time Zone w/o DST" must be parameterised so that no automatic time changeovers
are carried out.
The time server will only send the date and time if at least one successful NTP synchronisation has
been executed after device startup. This is to prevent the sending of a wrong system time.
With the time server function, a communication object is provided with which the sending of the time/
date can be triggered (trigger). For more details, see chapter 7.6 “Object table”.
The time server function is deactivated at delivery.

Data logger
Order No. 2089 00 Page 15
5. Data logger
The Gira S1 can be used as a data logger. The data logger functionality is controlled via the "Data
logger" parameter in the "General" parameter view (see chapter 7.5 “Parameters”). If it is set to "Yes",
the data logger functionality is always activated. If a microSD card is inserted into the device or if
there is already a microSD card in the device, logging begins automatically if it is not deactivated via
the "Activate data logger" communication object.
The data logger state is sent via the "Data logger status" communication object. The data logger status
can also be queried directly. As long as the data logger is active, the communication object has the
value 1. The communication object “Data logger status” assumes the value 0 if:
• the microSD card is removed,
• no memory capacity is available on the microSD card, or
• the data logger is deactivated via the "Activate data logger" communication object.
The data logger supports two types of memory management. The microSD card memory can be used
as static or cyclic buffer.
When used as cyclic buffer, the remaining memory is monitored. When the remaining memory capac-
ity drops below 2.5 Mbyte, the oldest log file is deleted to create space for new data.
When used as static buffer, logging is automatically ended as soon as the microSD card is full until a
new card with sufficient capacity is inserted.
Via the "Data logging format" parameter in the same parameter view, it can be configured whether
an ETS 3 (.trx) or an ETS 4/ ETS 5 (.xml) compliant data format should be used. The data logger can
be activated or deactivated via the "Activate data logger" communication object.
Naming and saving the log files on the microSD card is in accordance with the following scheme:
2010_01_06_TP1.trx (Year_Month_Day).
If there is a loss of voltage and a resulting loss of time/date, a file name can be repeated. In this case,
a tilde (~) is attached to the end of the file name, for further repetitions, consecutive numbers (~1) are
added to the tilde.
The Gira S1 supports SDHC cards up to a maximum of 32 GB. The cards must be formatted with FAT32.
Important note
To prevent damage to the card, you should deactivate logging before removing the microSD card.
Various communication objects are available for monitoring the memory status. The current card sta-
tus and the occupancy level are queried via these communication objects. For more details, see chap-
ter 7.6 “Object table”.
Important note: If the NTP server cannot be reached after a power failure, a default time is used. Fur-
ther logging is based on this time, until the NTP server is available again.

Data logger
Order No. 2089 00 Page 16
5.1. Access to the data logger archive
Via the device website, the data logger archive can be accessed. The menu item is also available when
the datalogger is deactivated in order to download old files if necessary. In addition to the actual files,
the status of the microSD card is also displayed.
When the microSD card is inserted, the log files stored on the microSD card are listed under “Con-
tent”. These are grouped by year and month. By default, the years and months are minimized and can
be expanded by the plus sign next to the year / month.
Figure 6: Data logger archive
The number next to a month or a single file indicates the file size in bytes.
Push the download symbol to start the download of a xml-file.

Installation
Order No. 2089 00 Page 17
6. Installation
Safety note
Electrical devices may only be installed and connected by a qualified electrician.
Failure to observe the instructions can result in damage to the device, fire or other dangers.
6.1. Device design
1. Programming button
2. KNX connection
3. External power supply connection
4. Programming LED (red):
on = programming mode active
5. Operating LED (green):
on = Gira S1 ready for operation
flashing slowly = Gira S1 not yet parametrised or parametrised
incorrectly
flashing quickly = internal device error
6. KNX-LED (yellow)
on = connection to KNX system
off = no connection to KNX system
flashing = KNX data transfer
7. Network connection with LED (green/orange)
green on = data transfer rate 100 Mbit/s
green off = data transfer rate 10 Mbit/s
orange on = connection to IP network
flashing orange = no connection to IP network, no data being
received from IP network
8. microSD card (up to 32 GB (SDHC))
A microSD card must be inserted for the data logger to be able to record telegrams.
6.2. Installation and electrical connection
Danger
There is a danger of electric shock if live parts are touched in the installation area.
Electric shock may lead to death.
Isolate before working on the device and cover up live parts in the vicinity!
2089 00
Gira S1
KNX 24 V DC
4
5
6
7
1
23
8

Installation
Order No. 2089 00 Page 18
6.2.1. Mounting the device
Observe the ambient temperature. Ensure sufficient cooling.
• Snap the device onto a top-hat rail according to DIN EN 60715. See figure 1 for installation position.
• Connect the external power supply to the connection terminal (3). Recommendation: Use white-
yellow connection terminal.
• Connect KNX line with red-black bus terminal (2).
• Attach cover cap over the KNX/external power supply connection.
• Establish network connection by plugging RJ45 plug into RJ pin jack (7).
6.2.2. Attaching the cover cap
A cover cap must be attached to protect the bus connection from danger-
ous voltages in the connection area.
• Guide bus line to the rear.
• Attach cover cap over the bus terminal until it engages.
6.2.3. Removing the cover cap
• Press cover cap on the sides and remove.

Configuration in the ETS
Order No. 2089 00 Page 19
7. Configuration in the ETS
Configuration of the Gira S1 in the ETS is divided into the following steps:
1. Create the Gira S1 as a device in the ETS (Chapter 7.1).
2. Assign the physical address for the device as well as up to three physical addresses for the interface
(Chapter 7.2).
3. Set the IP address, IP subnet mask and default gateway address of the Gira S1 or select “Obtain
an IP address automatically” (from a DHCP server) (Chapter 7.3).
4. Set general parameters for the Gira S1, including a DNS server, if applicable (for information on the
parameters, see Chapter 7.5).
5. Connect group addresses to group objects (for information on the object table, see Chapter 7.6).
6. Program the physical addresses (Chapter 7.3.1).
7. Transfer the application program and configuration (Chapter 7.4).
Accelerate transfer: Select transfer path IP
Programming (transfer from the ETS to the device) occurs in the ETS. No additional KNX data interface
is required for the transfer (bus connection via bus connection terminal). The ETS can reach the device
from both the IP side and the KNX TP side.
Due to considerably shorter transfer
times, download via the IP side of the
device is recommended. You can select
this option on the ETS start page in the
“Bus” - “Connections” - “Options” view:
To transfer the ETS via the IP side, select
the “Use direct KNX IP connection if
available” option.
7.1. Creating Gira S1 as a device in the ETS
If you have not already done so, perform a one-time import of the ETS device application for the Gira
S1 to the device catalogue of your ETS. You can download the ETS application free of charge at
www.downloads.gira.de.
Product catalogue
Product name: Gira S1
Design: DRA (series installation)
Order No.: 2089 00
State of delivery
Upon delivery or after a factory reset, the Gira S1 is configured as follows before it is loaded with ETS
for the first time:
• Remote access is activated for the “residents” user group
• The physical address is 15.15.255 and the three additional physical addresses for the tunnelling
server all have the address 15.15.254.

Configuration in the ETS
Order No. 2089 00 Page 20
If you already have an ETS project with a previous database entry, you can also update the application
program. To do so, drag the new database entry into the project and then select the device with the
old database entry. Now select “Information” in the device “Properties” and select the “Application”
(ETS4.2) or “Application program” tab (ETS5). You can now replace the old database entry by clicking
the “Update application program” (ETS4.2) or “Update” button (ETS5). Existing links to group
addresses are not lost. You can now delete the newly added device. In ETS4.2, you require a special
license for this. From ETS5 and higher, this is possible with any license.
7.2. Assigning physical addresses
The Gira S1 has three tunnelling servers (KNX/IP interfaces). These interfaces can be used for down-
loading and in the group and bus monitor modes. In addition to the device's physical address, the
device also has (up to) three additional physical interfaces. You can configure these, as with many
products today, using the interface settings after opening the KNX/IP connection in the ETS. In this
case, you must take special care to ensure that the addresses are not already used elsewhere.
From ETS4 and higher, it is possible to specify the number of additional addresses for products to
ensure that these can be configured in the ETS. A list containing the additional addresses appears for
this purpose below the input box for the physical address in the device properties in the ETS. In this
case, the ETS ensures that the addresses are unique in the project and automatically loads three
addresses to the device when programming the physical address.
If you do not require all three interfaces, you can also enable addresses using the “Park” function.
When adding a device, the ETS usually pre-assigns the additional addresses automatically.
Figure 7: Additional physical addresses in ETS4 (left) and ETS5 (right)
Configure the
additional interface
addresses here