Connection to the outside world

Interfaces are connections that give the system its meaning. In our opinion, it is not only the number of supported interfaces that determines the quality of a system, but above all how external devices or systems are connected via these interfaces, i.e. how comprehensively or conveniently one can communicate via these interfaces.


KNX is a system for building automation (old designation EIB). Actuators and sensors are connected via the bus using a two-wire line. Sensors are for example switches, dimmers, motion detectors or temperature sensors. Actuators can be, for example, lamps, blinds or dimming actuators. If a sensor now sends a telegram to the bus, the corresponding 'programmed' actuator recognises that it is meant and behaves accordingly, for example switching on the light. NeuroomNet is connected to the KNX bus via an IP bus coupler and can also place telegrams on the bus or receive them. KNX is very popular with all electrical manufacturers. All well-known manufacturers have pretty much everything from switches to top hat rail actuators in their product range. The advantages of KNX are its flexibility, you can change at any time which lamp should be switched by which switch. The disadvantage is that it can only be installed during the construction phase, which means that it can only be installed in an existing building at great expense.


PJLink is a standard for configuring video projectors and monitors via a network interface. With this standard, a cross-manufacturer and cross-model interface can be used for the configuration and monitoring of video projectors, as it is supported by more than 100 projector models of the participating manufacturers. The functions include switching projectors on and off, reading out lamp hours, switching sources, etc. A list of the manufacturers or the supported devices can be found here:


DMX is a protocol which is traditionally used in stage and event technology. From small theatres to huge show stages the lighting is realized via DMX. Mostly light colours and the motorized axes of the moving head spotlights are controlled via DMX. But of course there are many more end devices and applications. For example, the curtain can also fall triggered by DMX or the fog machine can do its job. Due to the increasing spread of LED light in fixed installations, there are also more and more applications in the home or corporate sector. Think, for example, of indirect lighting in conference rooms. NeuroomNet connects DMX over a network, using the ArtNet protocol to communicate directly with DMX devices that understand ArtNet, or using ArtNet-DMX interfaces. Technical details: DMX can control up to 512 channels (a universe) of lighting values over one cable. It worked well for many years, but eventually exceeded the 512-channel limit and lighting consoles appeared that supported multiple DMX universes. Art-Net overcomes the channel limitation of DMX while still using the structure. It allows multiple DMX universes to be transported over Ethernet using a Cat5 cable.

Exhibition API

The Exhibition API is a proprietary NeuroomNet API. It allows programmers to connect their software to the NeuroomNet ecosystem. The NeuroomNet user interface can thus directly visualize the state of the software. For example, if there is no communication between NeuroomNet and the third party software, whether due to technical failures such as a faulty network cable or a software crash, NeuroomNet can visualize this as it does for any other component.


MQTT (Message Queuing Telemetry Transport) was developed as a simple, resource-saving and reliable network protocol for the exchange of information between devices (machine-to-machine communication - M2M). It ensures the interference-free transmission of states (measured values), state changes (events) and commands (actions) even in case of slow or temporarily interrupted network connection. It has gained great importance in the "Internet of Things" (IOT). Here, as a rule, many small and non-performing, highly specialized terminal devices (sensors, actuators) are linked together to form an automation solution. The messages are managed by a so-called "broker". This broker receives and collects data sent by the MQTT participants and distributes them to registered end points. NeuroomNet works with brokers from protocol version 3.1. Support for encryption (TLS) and authentication is possible, but only makes sense if your end devices also work with it.


With SNMP (Simple Network Management Protocol) network devices (e.g. servers, switches, NAS, printers) can be centrally monitored and controlled. Information provided by your network components is registered and processed in NeuroomNet. While monitoring, parameters are recorded and you are informed of any errors that occur. Depending on the configuration, actions in the end devices can also be triggered. NeuroomNet currently supports protocol versions 1 and 2c (community based). In the future it will also be possible to use version 3. Currently, standardized settings and parameters are used.