Sensorberg devices should be in safe virtual networks, separated from any other network device. All sensorberg devices will use a defined set of technologies to communicate to each other. This chapter will bring some technical details to all network operators who want to integrate our solution.
For simplicity, we recommend to use one VLAN for all sensorberg hardware. This ensures that no routing or firewall issues preventing our devices from connecting. If this is not possible for your installation, you may run sensorberg devices in multiple VLANs as long as the router or firewall is allowing the following set of services between all components:
|TCP||443, 9443||Over-the-air upgrade of Access Hub Lite|
|TCP||8883 - 8885||Secure MQTT connection for sensorberg components|
If you plan to integrate sensorberg devices via wifi, please follow these requirements:
Please make sure to combine both Wifi and Ethernet (e.g. by using a software switch in your router). If this is not possible, please refer to this page to allow necessary traffic between devices when using multiple VLANs.
All sensorberg devices are using mDNS technology for plug-and-play functionality. mDNS is a service discovery functionality using multicast IP topics. This ensures that you will have minimal effort in integrating sensorberg into your current setup. For security reasons, this might be forbidden by your network hardware. For sensorberg solution to work, you have to make sure, that your network is allowing mDNS reflection into multiple VLANs (if used). If all devices belong to one network, this might not be a problem at all.
A successful mDNS setup can be tested using one of the following apps
You should see a service named
_sbbridgecontroller._tcp appearing when connected to the sensorberg VLAN.
If our smart spaces solution should be integrated with 3rd party hardware or services, additional requirements might apply. We try to cover them here, but if in a doubt, please ask our customer support for help.
|TCP||1884||OPUS SmartHome Gateway / EnOcean||OPUS Gateway to Sensorberg Building Hub|
|TCP / UDP||5060||Intercom VoIP connection||Sensorberg Building Hub to Intercom Gateway|
Any sensorberg device uses the following, outgoing connections, which should be allowed by your firewall or router:
|TCP||22||Emergency connection to our devices, opens up a SSH Tunnel|
|TCP||80||HTTP Traffic for operating system updates|
|TCP||443||HTTPS Traffic for connection to your Smart Space|
|TCP||4505 - 4506||Saltstack ZeroMQ connection for software updates by Sensorberg|
|TCP||8883||MQTT connection to your Smart Space|
|TCP||9443||Encrypted logfile shipping to Sensorberg cloud|