[vc_row row_type=”row” use_row_as_full_screen_section=”no” type=”grid” angled_section=”no” text_align=”left” background_image_as_pattern=”without_pattern” css_animation=””][vc_column][vc_column_text css=”.vc_custom_1445428675713{padding-bottom: 10px !important;}”]
Getting started
Step 1: Ceate a project with necessary data
Step 2: Upload your KNX group address list
- Select the KNX Addresses (file) leaf in the project view
- Export the Group addresses in ETS (3 levels, ….)
- Upload the file to the iBEMI configurator
Step 3: Create your profile
- Press the ”New” button in the [iBEMI Profiles] section and give your profile a name e.g. the house owners Surename
- You can select which type of profile you want, a iBEMI or iBEMI light profile. See differences in Licenses: iBEMI and iBEMI Light
- Click button Edit Profile to open your profile in iBEMI Profile Editor. See iBEMI Profile Editor: How to create your profile for further information.
Step 4: Add a iDevice to your project
- Select the iBEMI leaf in the project view
- Press the ”Add iDevice” and give your device a name like iPhone or iPad@home, fill in the voucher code and press ”Add”
Step 5: Sync iBEMI iDevice and project
- in the iDevice that you want to use with that project, open Settings
(by pressing respective button in upper left corner on starting page) - navigate to section License and enter license key of purchased license and press ”Register device”
- the device is now registered and you are able to load all the profiles
that you added for this iDevice in project view in iBEMI section
[/vc_column_text][vc_column_text]
How does it work
Communication: iBEMI connects directly to KNX Bus through KNXnet/IP
Gateway. Both connection types, KNXnet/IP Tunneling and KNXnet/IP
Routing, are supported.
Managing iBEMI: You are able to create
custom profiles for your projects with the iBEMI Profile Editor. To
transfer profiles to the app, you need to purchase a license for the
iDevice which is running the app. After entering the license key in the
app, iBEMI is synchronizing data of your project and you are able to
load the custom made profiles. Once your iBEMI iDevice is registered,
you can easily synchronize it with your account by pressing ”Sync”
button in ”License” or ”Profile” section.
How to set up KNX connection
You find the set up for KNX connection in Profile Settings
on first page (root element in Pages treeview) in iBEMI Profile Editor.
As connection type you can either select KNXnet/IP Tunneling or
KNXnet/IP Routing. There are ”More Settings” for both connection types
to adapt the connection to your installation: For connection type
KNXnet/IP Type you could set a custom port, for KNXnet/IP Routing you
could set custom Multicast IP address and custom port.
How to change profile type
There are two different profiles types available for the App: iBEMI and
iBEMI Light. If you create new Profile, there is option ”Create iBEMI
Light profile” to create a profile which is compatible with iBEMI Light
license (see Licenses: iBEMI and iBEMI Light). You are able to easily change profile type afterwards in iBEMI Profile Editor in Profile Settings on first page (root element in Pages treeview).
Licenses: iBEMI and iBEMI Light
There are two different license types available: iBEMI and iBEMI Light.
The two license types differ in the profiles you could use with them.
An iDevice with iBEMI Light license is limited to keep one profile at a
time. Furthermore there are also limitations in the size of iBEMI Light
profiles. You are able to add up to 89 KNX widgets to an iBEMI Light
profile. There are also limitations for the full license, iBEMI.
However, these limitations (you could place more than 5000 widgets)
shouldn’t be relevant in common usage. Please contact us if you are
struggling with iBEMI limitations.
[/vc_column_text][vc_column_text]
| Limitations | Profiles | Levels | Extension pages | Sub pages | Number of widgets |
|---|---|---|---|---|---|
| iBEMI | 10 | 12 | 4 | 5 | > 5000 |
| iBEMI Light | 1 | 1 | 1 | 0 | 89 |
If you are not sure, whether your custom profile exceeds iBEMI Light
limitations, we recommend to first create an iBEMI Light profile, to
test if its size is sufficient. You are always able to easily change
profile type to iBEMI in the iBEMI Profile Editor in Profile Settings. Profile settings are accessed by clicking root element in the treeview of Pages section.
iBEMI Profile Editor: How to create your profile
| Pages | On the left side you have the box Pages with the treeview where you can see the page layout of your profile. | ||
| I. Add a level and change the name to e.g. Floor 1, this page will be accessible in the iphone by scrolling down from the main view.II. If you add an extention page it will be the page to the right, this page will be accessible in the iPhone by scrolling to the right from the main view. |
|||
| You are able to move Levels and Rooms in the treeview by Drag&Drop. | |||
| Attributes | In the middle you have the Attributes box with a list with all the configurable pramaters for the selected widget (as name, knx addresses etc.). There are ”More Settings” option available for most widgets with optional attributes. Usually you don’t need to configure these additional attributes. |
||
| Application preview | On the right side you have the Application preview with landscape and portrait view of the selected page. Most time you will work with the big landscape preview. You are able to add buttons/widgets by pressing an open spot in the page and to select buttons/widgets to change their attributes. On all the pages you are able to add/select buttons, value label and name label in header of the page. In addition to that you could configure the two custom symbols in the upper left corner on the first page (and its extension pages).Furthermore you could move buttons to another spot in the page by Drag&Drop. You could do the same in the small portrait preview on the right side to create a different button layout for the page in portrait orientation. |
||
[/vc_column_text][vc_column_text css=”.vc_custom_1445428802772{padding-top: 10px !important;}”]
Steps to build up your profile:
- If you open a new profile in the iBEMI Profile Editor by clicking Edit
profile button, you will see one empty page with the chosen profile name
in preview window. In Attributes box you will see Profile Settings. First thing that you should do is toconfigure KNX Connection according to your installation. - Then you could go ahead and configure the content of the page to your needs: add buttons, add a value in upper right corner and you might also want to configure the header symbols.
- First page is now finished. Now you are going to add a new page. There are two options: if you want to add more buttons with kind of a global function which should be quickly accessible, you should addextension page(s) to the first page by pressing button Add Extension Page in Attributes box. Second option is to add a level page by pressing Add Level button in Pages box to start building up Level-Room structure of the profile.
- With extension page: proceed as with first page.
On extension pages you are able to add up to 8 buttons. After
finalizing the page you could again add another extension page or you
could add a level page.
With level page: usually you will add rooms to a level page by clicking Add Room button in Pages box. If you add a room, there will be a new room page added to the treeview in Pages box and you will see a button appearing on level page. This button is a Room Link button.
If you press this button in the app, you will be navigated to the room
page which is always placed to the right of the level page. If you
create a new room, you should configure Room Link button (set name of the room and select an icon) and press the button afterwards to save selection. You could also add a conventional button to level page by clicking an open spot on the page and configuring button to your needs. You could set value lable for level page too. - After creating room pages you could now add content by selecting them in treeview in Pages box and adding buttons and setting a value lable for each page. If you would like to add more buttons to one room you could add extension page(s)
by pressing button Add Extension Page. In the app extension pages of a
room are placed beneath the first page of the room. They share the same
name as the room page but besides that they can be configured
independently from room page.
There are limitations for the size of the profile. However, with iBEMI license they shouldn’t be relevant. CheckLicenses: iBEMI and iBEMI Light for further information.
Profile Settings
Profile
Settings contain general attributes of the attribute. You access them
by pressing the root element (that is first page) in treeview in Pages
box.
[/vc_column_text][vc_column_text css=”.vc_custom_1445429533502{padding-top: 20px !important;padding-bottom: 20px !important;}”]
| Attributes | ||
| Name | This is the name of the profile which is also shown in the header of first page (+ extension pages) of the profile | |
| Profile Type | At this drop down menu you are able to change profile type. An iBEMI profile is compatible only with a device with iBEMI license, an iBEMI Light profile is running on devices with either iBEMI license or iBEMI Light license. |
|
| Connection Type | You could choose either KNXnet/IP Routing or KNXnet/IP Tunneling. If you choose KNXnet/IP Tunneling you need to also set the address of your gateway in the appearing textfield. |
|
| Gateway IP address | Here you need to set the IP address of the gateway which the app should use to build up KNXnet/IP Tunneling connection | |
| More Settings | ||
| Multicast IP address | You could set a custom multicast IP address which the app should use with KNXnet/IP Routing for this profile. Default IP address is: 224.0.23.12 |
|
| Port | You could set a custom port here that the app should use with KNXnet/IP connection for this profile. Default port is: 3671 |
[/vc_column_text][vc_column_text css=”.vc_custom_1445429577523{padding-top: 20px !important;padding-bottom: 20px !important;}”]
Value Label
Value
Label is the placed in upper right corner on each page in the app. In
iBEMI Profile Editor it is configured by pressing the corresponding
field in the preview of the page.
| Attributes | ||
| KNX Address | At this parameter you have to enter the KNX group address of the desired value.Format of the address has to be Main/Middle/Sub group and the address is polled when you enter this page in the app. |
|
| Data Format | At this drop down menu you are able to choose the Data Format of the desired value. Temperature, Brightness, Windspeed, 1 byte, 2 byte, 2 byte float, Time or Date are the available Data Formats. |
|
| More Settings | ||
| Unit | You could set a Unit which is shown with the value in the app for all Data Formats except Time and Date. There are default Units for Data Formats Temperature [°C], Brightness [Lux] and Windspeed [m/s]. |
|
| Scaling factor | If Data Format is 2 byte float, you could set a custom scaling factor for the value at this parameter. This is of course optional. The default value is 0.01. |
|
| Decimal places | For Data Formats Temperature, Windspeed and 2 byte float you could set the number of decimal places of the value that should be displayed in the value label. Defaultly there is one decimal place shown with the respective Data Formats. |
|
| Time Format | You could select a custom format for the shown time. The default format is E HH:mm. | |
| Date Format | You could select a custom format for the shown date. The default format is d.MM.yyyy. |
[/vc_column_text][vc_column_text]
Header Symbols
There are two symbols in the upper left corner which you could control
through a 1bit KNX Address. Configuration of this symbols is very
simple: you just need to select a symbol in preview and chose an icon
and set the KNX Address which status the symbol should adapt to. The KNX
Address is polled to get the current status so the address should be
set as readable in ETS.
Buttons
You can place up to eight buttons on each page, except the first page of your profile: here you could place for bigger buttons.
A new button is created by clicking on an empty button spot in the page
preview. The new button is a copy of the latest modified button and it
is placed on the selected spot. You delete a button by selecting it and
clicking button Delete in Attributes box.
You are able to change
the position of the button through drag and drop in the preview
windows. You could select different positions for the buttons for
landscape or portrait orientation.
Switching
Buttons with function Switching should be connected to a KNX switch
actuator. You can select 1bit commands (ON/OFF/TOOGLE) that should be
sent on button press or/and button release.
The button could
show the current status of the connected actuator. The button is
adapting state from KNX group address which is entered at entry KNX
Address for status indication. This feedback address could be polled –
if polling is chosen, KNX Address should be set as readable so that
current state could be fetched by the app.
| Attributes | ||
| Name | Name that should be shown beneath button. | |
| KNX Address | At this parameter you have to enter the KNX group address of the 1bit actuator you’d like to control. | |
| Command on button press | You can choose which action should be performed on button press. Available actions are No function, ON, OFF and TOGGLE. No function is initially set. |
|
| Command on button release | Here you can choose which action should be performed on button release. For this button action is usually performed on button release. Available actions are No function, ON, OFF and TOGGLE. No function is initially set. |
|
| KNX Address for status indication | Here at this parameter you enter KNX group address to indicate status of the 1bit actuator. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. |
|
| Icon | Select icon that should be shown on button. | |
| More Settings | ||
| Icon for active state | Here you could select another icon that would only be shown if status of button is ON. You could also set another KNX address at the field below to control the icons. |
|
| KNX Address for controlling the icons | Usually the icons of a button are set according to its status (that is the value at ”KNX Address for status indication”). However, if you’d like to control icons independently from status, you could set a special KNX Address (1bit value) here to control the icons. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. |
[/vc_column_text][vc_column_text]
Dimming
Buttons with function Dimming should be connected to a KNX dimming
actuator. There is 4 bit and 1 byte Data Format available with this
function. With 1 byte dimming there is a slider shown in a pop up window
on button press to set the value directly. With 4 bit dimming option, a
certain increment/decrement value is send to modify dimmer output.
4 bit:
You are able to add a Switch Object (1bit) to this function to switch
dimming actuator ON and OFF. In this case, the selected dimming value is
sent on long press of button – short press is assigned to switching
action. The time interval before performing dimming action could be set
at ”Time between switching and dimming” under More Settings. You could
show the current status (ON/OFF) of the connected actuator. The button
is adapting state from KNX group address which is entered at entry KNX
Address for status indication. This feedback address could be polled –
if polling is chosen, KNX Address should be set as readable so that
current state could be fetched by the app.
You could set
Telegram Repetition option to send multiple telegrams as long as button
is pressed. At Telegram Repetition Time you could set time interval in
between the telegrams.
| Attributes | ||
| Name | Name that should be shown beneath button. | |
| Switch Object | You could choose if you’d like to have switching function with this button. | |
| KNX Address switch object | At this parameter you have to enter the KNX group address of switch object (1bit) of the dimming actuator. | |
| KNX Address dimming object | Here yo enter KNX group address of dimming object (4 bit) of the dimming actuator | |
| Command on button release | You can choose which action should be performed on button release. Available actions are Brighter, Darker and Brighter/Darker. | |
| Dimming brighter byDimming darker by | You can select the step width to increment/decrement dimming value on each button press (- or per telegram with option Telegram Repetition set.) Available values are 100%, 50%, 25%, 12,5%, 6%, 3%, 1,5%. |
|
| Telegram Repetition Time | Here you are able to add repetition function. You can choose time intervals starting from 100ms to 1s. | |
| KNX Address for status indication | Here at this parameter you enter KNX group address to indicate status (1bit) of the actuator. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. |
|
| Icon | Select icon that should be shown on button. | |
| More Settings | ||
| Icon for active state | Here you could select another icon that would only be shown if status of button is ON. You could also set another KNX address at the field below to control the icons. |
|
| KNX Address for controlling the icons | Usually the icons of a button are set according to its status (that is the value at ”KNX Address for status indication”). However, if you’d like to control icons independently from status, you could set a special KNX Address (1bit value) here to control the icons. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. |
|
| Time between switching and dimming | If you added a Switch Object to this button, you could set a custom time interval before performing dimming action here. You can choose time intervals starting from 10ms to 1s. Default interval is 300ms. |
[/vc_column_text][vc_column_text]1 byte:
You are able to add a Switch Object (1bit) to this function to switch
dimming actuator ON and OFF. In this case, the popup window with the
slider to set dimming value is prompted on long press of button – short
press is assigned to switching action. The time interval before showing
dimming control view could be set at ”Time interval before showing
control view” under More Settings. You could show the current status
(ON/OFF) of the connected actuator. The button is adapting state from
KNX group address which is entered at entry KNX Address for status
indication. This feedback address could be polled – if polling is
chosen, KNX Address should be set as readable so that current state
could be fetched by the app.
| Attributes | ||
| Name | Name that should be shown beneath button. | |
| Switch Object | You could choose if you’d like to have switching function with this button. | |
| KNX Address switch object | At this parameter you have to enter the KNX group address of switch object (1bit) of the dimming actuator. | |
| KNX Address value | Here yo enter KNX group address of value object (1 byte) of the dimming actuator | |
| KNX Feedback Address for value | You can enter KNX feedback address to fetch dimming value. The value at this address is stored for this button. If there is no feedback address available, you should enter address of ”KNX Address value” here. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. |
|
| KNX Address for status indication | Here at this parameter you enter KNX group address to indicate status (1bit) of the actuator. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. |
|
| Icon | Select icon that should be shown on button. | |
| More Settings | ||
| Time interval before showing control view | If Switch Object is set, you could set a custom time interval before showing dimming control view here. You can choose time intervals starting from 10ms to 1s. Default interval is 300ms. |
[/vc_column_text][vc_column_text css=”.vc_custom_1445429839622{padding-top: 20px !important;}”]
Shutter Control
Buttons of function Shutter Control should be connected to a KNX
shutter actuators. You could choose either operation mode Move-Step or
Step-Move-Step.
The button could indicate the current status of
the shutter actuator through the buttons border or through shutter
icons. The button is adapting state from KNX group address which is
entered at entry KNX Address for status indication (or KNX Address for
controlling the icons – find more information below). This feedback
addresses could be polled – if polling is chosen, KNX Address should be
set as readable so that current state could be fetched by the app.
| Attributes | ||
| Name | Name that should be shown beneath button. | |
| KNX Address step operation | At this parameter you have to enter the KNX group address for 1bit step operation. | |
| KNX Address move operation | KNX group address for 1bit move operation. | |
| Operation Mode | Here you are able to configure the Operation Mode of the button. You can choose either Move-Step or Step-Move-Step. Move-Step is used for controlling only the lamella. Defaultly Step-Move-Step is selected. |
|
| Function | Available functions are Up,Down and Up/Down. Function Up is defaultly set. | |
| Time between step and move operation | Here you have to set the time that it takes to fully open->close the shutter. | |
| Lamella adjustment time | Here you set the time for open->close blinds. | |
| KNX Address for status indication | Here at this parameter you enter KNX group address to indicate status (1bit) of the shutter actuator. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. |
|
| Icon | Select icon that should be shown on button. | |
| More Settings | ||
| Icon for active state | Here you could select another icon that would only be shown if status of button is ON. You could also set another KNX address at the field below to control the icons. |
|
| KNX Address for controlling the icons | Usually the icons of a button are set according to its status (that is the value at ”KNX Address for status indication”). However, if you’d like to control icons independently from status, you could set a special KNX Address (1bit value) here to control the icons. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. |
[/vc_column_text][vc_column_text css=”.vc_custom_1445429907913{padding-top: 20px !important;}”]
Value Transmitter
On button press buttons of function Value Transmitter is sending a
certain value to a given KNX group address. There are several different
data formats available for the sending value.
| Attributes | ||
| Name | Name that should be shown beneath button. | |
| KNX Address | KNX group address for the value. | |
| Data Format | Here you select the Data Format of the value. You can choose from Lightscene, Temperature, Brightness, 1 byte, 2 byte and 2 byte float. Default data format is Lightscene. |
|
| Memory Function | This function is only available with Data Format Lightscene. If you set this function, a popup window will appear on long press of button, asking if you’d like to store scene. Note: The Lightscene is not stored in the App. The App is sending store-telegram to given KNX address, if Store is selected in popup. |
|
| Value | The value that should be sent. | |
| KNX Address for status indication | This parameter is only available with Data Format Lightscene. You are able to enter KNX group address to indicate active Lightscene. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. | |
| Icon | Select icon that should be shown on button. |
[/vc_column_text][vc_column_text css=”.vc_custom_1445430569293{padding-top: 20px !important;}”]
Temperature
Button with function Temperature should be used in ventilation tasks.
On button press a popup window is shown where you could control
(increase/decrease) a temperature value.
| Attributes | ||
| Name | Name that should be shown beneath button. | |
| KNX Address value | KNX group address for temperature set value (2 byte float). | |
| KNX Feedback Address for value | Here you are able to enter feedback address for the temperature value. The value at this address is stored in the button and shown on button surface. If there is no feedback address available you should also enter the above address for set value here. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. |
|
| Icon | Select icon that should be shown on button. | |
| More Settings | ||
| Decimal places | At this parameter you could select the number of decimals that should be printed with the temperature value. Defaultly one decimal is shown. |
|
| Unit | You could set a custom unit for the value here. ”°C” is default unit. |
[/vc_column_text][vc_column_text css=”.vc_custom_1445430125315{padding-top: 20px !important;}”]
RGB
This button function is used to work with RGB controllers. On button
press a window is shown where you could pick a color and store favorite
colors. There are two different Data Formats for transmitting the color
value over KNX: ”1 byte Components” and ”3 byte Color”. With ”1 byte
Components”, the three 1 byte color components are transmitted in three
separate telegrams – with ”3 byte Color” all components are transmitted
in one telegram. The latter Data Format should be preferred if
available.
You are able to add a Switch Object (1bit) to this
function. In this case, the popup window with the slider to set color is
prompted on long press of button – short press is assigned to switching
action. The time interval before showing RGB control view could be set
at ”Time interval before showing control view” under More Settings. You
could show the current status (ON/OFF) of the connected actuator. The
button is adapting state from KNX group address which is entered at
entry KNX Address for status indication. This feedback address could be
polled – if polling is chosen, KNX Address should be set as readable so
that current state could be fetched by the app.
1 byte Components:
| Attributes | ||
| Name | Name that should be shown beneath button. | |
| Switch Object | You could choose if you’d like to have switching function with this button. | |
| KNX Address switch object | At this parameter you have to enter the KNX group address of switch object (1bit) of RGB controller. | |
| KNX Address for red color | KNX group address for red color component (1byte). | |
| KNX Address for green color | KNX group address for green color component (1byte). | |
| KNX Address for blue color | KNX group address for blue color component (1byte). | |
| KNX Feedback Address for red color | Here you should enter feedback address for red color component (1byte). The value at this address is stored in button. If there is no separate feedback address available, you should also enter set address for component here. |
|
| KNX Feedback Address for green color | Here you should enter feedback address for green color component (1byte). The value at this address is stored in button. If there is no separate feedback address available, you should also enter set address for component here. |
|
| KNX Feedback Address for blue color | Here you should enter feedback address for blue color component (1byte). The value at this address is stored in button. If there is no separate feedback address available, you should also enter set address for component here. |
|
| KNX Address for status indication | You are able to enter KNX group address to indicate status (1bit). There is a checkbox to set if this address and the other three feeback addresses for the color components should be polled or not. Note: If KNX Addresses should be polled, the addresses should be marked as readable in your ETS project. |
|
| Icon | Select icon that should shown on button. | |
| More Settings | ||
| Time interval before showing control view | If Switch Object is set, you could set a custom time interval before showing dimming control view here. You can choose time intervals starting from 10ms to 1s. Default interval is 300ms. |
3 byte Color:
| Attributes | ||
| Name | Name that should be shown beneath button. | |
| Switch Object | You could choose if you’d like to have switching function with this button. | |
| KNX Address switch object | At this parameter you have to enter the KNX group address of switch object (1bit) of RGB controller. | |
| KNX Address for color value | KNX group address for RGB color (3byte). | |
| KNX Feedback Address for color value | Here you should enter feedback address for RGB color (1byte). The value at this address is stored in button. If there is no separate feedback address available, you should also enter set address for color value here. |
|
| KNX Address for status indication | You are able to enter KNX group address to indicate status (1bit). There is a checkbox to set if this address and the feeback address for the color value should be polled or not. Note: If KNX Addresses should be polled, the addresses should be marked as readable in your ETS project. |
|
| Icon | Select icon that should shown on button. | |
| More Settings | ||
| Time interval before showing control view | If Switch Object is set, you could set a custom time interval before showing dimming control view here. You can choose time intervals starting from 10ms to 1s. Default interval is 300ms. |
[/vc_column_text][vc_column_text css=”.vc_custom_1445430266597{padding-top: 20px !important;}”]
Time Control
This button function is used to send a time value
(DPT_TimeOfDay). On button press a window is shown where you could pick a
time. The time is sent directly after picking it.
You are able
to add a Switch Object (1bit) to this function. In this case, the time
picker popup window is prompted on long press of button – short press is
assigned to switching action. The time interval before showing time
control view could be set at ”Time interval before showing control view”
under More Settings. You could show the current status (ON/OFF) of the
connected actuator. The button is adapting state from KNX group address
which is entered at entry KNX Address for status indication. This
feedback address could be polled – if polling is chosen, KNX Address
should be set as readable so that current state could be fetched by the
app.
| Attributes | ||
| Name | Name that should be shown beneath button. | |
| Switch Object | You could choose if you’d like to have switching function with this button. | |
| KNX Address switch object | At this parameter you have to enter the KNX group address of switch object (1bit) for this button. | |
| KNX Address value | KNX group address to set time value (DPT_TimeOfDay). | |
| KNX Feedback Address for value | You can enter KNX feedback address to fetch time value. The value at this address is stored for this button. If there is no feedback address available, you should enter address of ”KNX Address value” here. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. |
|
| KNX Address for status indication | You are able to enter KNX group address to indicate status (1bit) of the switching actuator. There is a checkbox to set if this address should be polled or not. Note: If KNX Address should be polled, the address should be marked as readable in your ETS project. |
|
| More Settings | ||
| Day that should be added to time value | Here you could set the day which should be added to time value. Defaultly ”No day” is set. | |
| Minute interval in control | You are able to set a custom minute interval in time picker control. Available intervals are 1min, 2min, 5min and 10min. Default value is 5min. |
|
| Time Format on button | You could select a custom format for the time which is printed on button surface. There are several different formats available. Default format is HH:mm. |
|
| Time interval before showing control view | If Switch Object is set, you could set a custom time interval before showing dimming control view here. You can choose time intervals starting from 10ms to 1s. Default interval is 300ms. |
[/vc_column_text][vc_column_text css=”.vc_custom_1445430314065{padding-top: 20px !important;}”]
Date Control
This button function is used to send a date value (DPT_Date). On
button press a window is shown where you could pick a date. The date is
sent directly after picking it.
| Attributes | ||
| Name | Name that should be shown beneath button. | |
| KNX Address value | KNX group address to set date value (DPT_Date). | |
| KNX Feedback Address for value | You can enter KNX feedback address to fetch date value. The value at this address is stored for this button. If there is no feedback address available, you should enter address of ”KNX Address value” here. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. |
|
| More Settings | ||
| Date Format on button | You could select a custom format for the date which is printed on button surface. There are several different formats available. Default format is d.MM.yyyy. |
[/vc_column_text][vc_column_text css=”.vc_custom_1445430491149{padding-top: 20px !important;}”]
Indication
With this button function a value at a KNX Address is shown on
the button – or, with data format ”1 bit Status”, the status is
indicated through the border of the button. There are several different
data formats available with this function.
| Attributes | ||
| Name | Name that should be shown beneath button. | |
| KNX Address | At this parameter you have to enter the KNX group address of the desired value. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. |
|
| Data Format | At this drop down menu you are able to choose the Data Format of the desired value. 1 bit Status, Temperature, Brightness, Windspeed, 1 byte, 2 byte, 2 byte float, Time or Date are the available Data Formats. |
|
| Icon | Select icon that should shown on button. | |
| More Settings | ||
| Icon for active state | For Data Format 1 bit Status you could select another icon that would only be shown if status of button is ON. You could also set another KNX address at the field below to control the icons. |
|
| KNX Address for controlling the icons | Usually the icons of a button are set according to its status. However, if you’d like to control icons independently from status, you could set a special KNX Address (1bit value) here to control the icons. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. |
|
| KNX Address for activating second status | For Data Format 1 bit Status you could indicate a second status which is controlled through this KNX address. Second status is indicated through a thick red border line around the button (if status is active). Second status has higher priority than common status, meaning if both status are active, red border color is shown around the button. There is a checkbox to set if this address should be polled or not. Note: If this KNX Address should be polled, the address should be marked as readable in your ETS project. |
|
| Unit | You could set a Unit which is shown with the value in the app for all Data Formats except Time and Date. There are default Units for Data Formats Temperature [°C], Brightness [Lux] and Windspeed [m/s]. |
|
| Scaling factor | If Data Format is 2 byte float, you could set a custom scaling factor for the value at this parameter. This is of course optional. The default value is 0.01. |
|
| Decimal places | For Data Formats Temperature, Windspeed and 2 byte float you could set the number of decimal places of the value that should be displayed in the value label. Defaultly there is one decimal place shown with the respective Data Formats. |
|
| Time Format | You could select a custom format for the shown time. The default format is E HH:mm. | |
| Date Format | You could select a custom format for the shown date. The default format is d.MM.yyyy. |
[/vc_column_text][vc_column_text css=”.vc_custom_1445429106784{padding-top: 20px !important;padding-bottom: 20px !important;}”]
Room Link
A room link button is automatically generated by the app if you
add a new room to a level. The button is placed on the level page –
every room link button is representanting a room in the level. If you
press a button in the app you are navigated to the corresponding room.
If you select a room link button, you could set the name of the room and
you are able to select an icon for the room link button. Room Link
buttons can’t be moved directly on level page, you could move the room
page in treeview to do so though.
[/vc_column_text][/vc_column][/vc_row]
