Home » Things to know » Compon­ents & Groups

Ever­y­thing is compo­nent

Compon­ents are the mole­cules of the NeuroomNet system

NeuroomNet has nume­rous inter­faces. If “some­thing” is connected via one of these inter­faces, be it dedicated hard­ware, soft­ware, or another endpoint, then we call it a “compo­nent”. There is probably no univer­sally valid name that sums ever­y­thing up, so we have decided on the term “compo­nent”.

Why is this important or why do I need to know this as an installer of a system?

Compon­ents are the basis of our accoun­ting system. If you do not have many compon­ents, you will only need a few licenses. We offer licenses in packages. Ther­e­fore, you do not need to know the exact number of your compon­ents in advance, but an appro­xi­mate idea will help you decide which package you need. Of course, the packages can be extended at any time.

Here are some examples for clari­fi­ca­tion:

A video projector is a compo­nent.

A projector that is connected to the system via a network is a compo­nent from the system’s point of view. It does not matter which protocol is used for commu­ni­ca­tion, be it a “universal” protocol like PJLink or a proprie­tary protocol.

Symbol of a projector
A socket can be a compo­nent.

It depends on whether you also want to address this socket sepa­ra­tely. If we assume KNX as the inter­face, then the elec­tri­cian would also have to assign an address for each socket. However, if there is only one KNX address to switch all sockets (of a room, of a floor) toge­ther, then all these sockets are only one compo­nent in NeuroomNet.

Symbol of a house with power plug
A PC is a compo­nent.

The NeuroomNet PC client (soft­ware tool) is installed on the PC. From then on, the PC is a compo­nent. The system can then switch the PC off, switch it on, reboot it or simply detect whether the PC is running. Inci­den­tally, the NeuroomNet PC client is opera­ting system inde­pen­dent and can inte­grate Windows, Linux, and Apple PC systems.

Symbol of a PC with start button
Software on the PC is a compo­nent.

A POI soft­ware, digital signage soft­ware, or a game is a compo­nent. For this, the soft­ware only has to use the API, which informs the system whether the soft­ware is running. Various other func­tions, such as a CMS connec­tion, can also be made available via the API.

Symbol of three interlocking gears

The smal­lest unit in NeuroomNet is ther­e­fore always a compo­nent.

The compo­nent type is deter­mined by the inter­face protocol, e.g. KNX, TCP/IP, PJLink, DMX, SNMP, etc.

In addi­tion, a compo­nent can also have a compo­nent type to better specify the compo­nent. Let’s take the example from above again, the KNX compo­nent. Basi­cally, NeuroomNet only knows the inter­face (KNX) and the address. But now, as an admi­nis­trator, I can still assign the compo­nent type, either the said socket or light or a heating actuator or, or.

The same is true for most compo­nent types. An SNMP compo­nent can be of type printer, network switch, etc., and a DMX compo­nent of type head-moving spot­light or fog machine, etc…

You don’t have to make a compo­nent type assign­ment, but it gives you the possibility to switch lights and sockets sepa­ra­tely, for example.

Graph with 2 protocols: Serial and PJ Link. Serial has two subordinate components: a photocopier (component 1) and a projector (component 2). Component 1 is assigned the type: Printer. With the PJ Link protocol, the 2 components are a projector (component 3) and a monitor (component 4). Components 2 and 3 are assigned the type: Projector. Component 4 is assigned the type: Screen.

Compon­ents have proper­ties

Common to all is the proper­ties’ name and type. The name can be freely assi­gned and the type results from the protocol. In the case of the socket, the type would be e.g. KNX. A type can be optio­nally assi­gned. If neces­sary, compon­ents have other proper­ties that depend on the compo­nent type, e.g. IP address, bit width, etc.

Compon­ents have actions

Depen­ding on the compo­nent, diffe­rent actions are available. In the case of the power outlet, these are usually only Power On and Power Off. In the case of the video projector, there are a few more like power on, power off, shutter on, shutter off, input HDMI1, etc.

Groups of compon­ents

Complex multi­media instal­la­tions are more than a random coll­ec­tion of devices and soft­ware. In most cases, these are already grouped in some way during the plan­ning stage: be it accor­ding to rooms or individual stations such as exhibits or work­sta­tions. This makes it clearer which devices are respon­sible for what and how they work toge­ther.

But this grou­ping can be subdi­vided and named differ­ently depen­ding on the project. That’s why you can build and name a tree struc­ture quite flexibly in NeuroomNet.

Graphic, which is hierarchically divided into several components, each of which is assigned to "Child Groups", which in turn are assigned to "Parent Groups".

Let’s take a museum as an example:

A digital exhibit as the smal­lest unit could consist of a computer, two projec­tors, and an RFID reader. So we need a group-type “exhibit”.However, other stations cannot be directly called exhibits. So we also need the group types “Digital Signage” for information displays and “Work­place” for employees*. These three group types are all on the same level, which we call “station” in this example.

Let’s think of a small digital signage station in the foyer that welcomes visitors with various images and videos or even inter­ac­tive content. This station consists of a computer, soft­ware that plays the content, and a projector to throw the output on the wall and the whole thing should be discon­nected from the power when it is turned off.

To do this, we simply group our compon­ents.

Screenshot of the application in the NeuroomNet programme with components and groups

Now all compon­ents of the group can be addressed toge­ther. If you switch off the group, it is auto­ma­ti­cally ensured that every compo­nent of this station is swit­ched off.

A switching sequence is used to specify in advance that the socket is swit­ched off last after time X or that various devices are swit­ched on first and then wait before the other devices are swit­ched on.

Groups can also be swit­ched on or off auto­ma­ti­cally via a circuit diagram.
If compon­ents are grouped, only the group appears in the building plan.
For the status of a group, the highest warning level of its child compon­ents or child groups is always passed upwards.

Screenshot of the application in the NeuroomNet programme with selected component and location in the building plan
Further nesting of groups

To be able to work with the system as comfor­tably as possible, it can be useful to nest groups in turn into further groups. At the lowest level, compon­ents can be grouped, for example, into stations, exhibits, work­sta­tions, or similar. The cate­go­ries can be defined by the user. These can be further grouped into depart­ments, depart­ments into floors, and floors into buil­dings.

In this way, buil­dings, floors, or depart­ments can be addressed in no time at all.



Ever­y­thing can be inte­grated into NeuroomNet as a compo­nent, whether device, soft­ware, or other­wise.
This ensures maximum flexi­bi­lity in the digital repli­ca­tion of the instal­la­tion.


The compon­ents can be grouped and nested as desired. This keeps the system clear and intui­tive.
The groups are easier to address and control.