Skip to main content

Component Types tab

For more background information, we recommend reading the following articles:

Create and manage new component types​

Module Setup: Screenshot creating a new component type

To better specify a component, a component type can be created with "Add component type" 1.

For this purpose, the name 2 is assigned and a suitable preview icon 3 is selected from a list. This is displayed as an avatar in the hierarchy and in monitoring as soon as a component is assigned the type.

Then the interface protocols 4 are selected for which the new type should be available. Additional protocols can also be added later.

Don't forget to save at the end. 5.

Alias for actions​

In the component type, it is possible to assign a descriptive name for actions using an alias. Parameter values can even be predefined in the alias.

Module Setup: Screenshot creation of an alias for an action

In the example above, in the “Light” component type, the KNX command “Send Data to Actor = 0” is labeled “LightOff”.

In return, “Send Data to Actor = 1” is labeled “LightOn”.

The names “LightOn” and “LightOff” are displayed as actions in setup and monitoring and are easier to understand for users.

In the “Socket” component type, the command could again be named “SocketOff” and “SocketOn”.

See Provider HTTP for another example of aliases in the context of Provider HTTP (where aliases usually must be used).

Usage notes: To add a new alias, you may first need to select an interface and action in the respective combo boxes before the “Add alias” button becomes active. Additionally, after entering, you must click “Save” at the top so that the changes entered are activated and saved.

Important warning: Alias actions can confuse the system, as the names must be globally unique (across everything, including fixed actions of components). For example, if you define an alias “Light on” with a fixed value (e.g. 1) and another “Light on” where the value remains open and thus uses a parameter, it is not defined which action NeuroomNet knows. Only one is certain: either the one with or the one without a parameter. This can lead to significant malfunctions.


It is therefore recommended that alias actions do not use open parameters, i.e. all parameters of the action are assigned a constant value.