Divus Heartbeat User manual

DIVUS HEARTBEAT user manual . 1
DIVUS
HEARTBEAT
User manual
Version 1.0
REV05-2018-04-16

DIVUS HEARTBEAT user manual . 2
GENERAL INFORMATION
DIVUS GmbH
Pillhof 51
I-39057 Eppan (BZ) - Italy
Operating instructions, manuals and software are protected by copyright. All rights are reserved. Copying,
multiplication, translation and conversion, either partially or as a whole, is not permitted. You are allowed to make
a single copy for backup purposes.
We reserve the right to make changes to the manual without prior notification.
We assume no responsibility for any errors or omissions that may appear in this document.
We do not assume liability for the flawlessness and correctness of the programs and data contained on the
delivered discs.
You are always welcome to inform us of errors or make suggestions for improving the program.
The present agreement also applies to special appendices to the manual.
This manual can contain terms and descriptions, which improper use by third can harm the copyrights of the
author.
Please read the manual before beginning and keep the manual for later use.
The manual has been conceived and written for users who are experienced in the use of PCs and automation
technology.
CONVENTIONS
[KEYS]
Keys that are to be pressed by the user are given in square brackets, e.g. [CTRL] or [DEL]
COURIER
On-screen messages are given in the Courier font, e.g. C:\>
COURIER BOLD
Keyboard input to be made by the user are given in Courier bold, e.g. C:\>DIR).
Names of buttons to be pressed, menus or other onscreen elements and product names are
PICTOGRAMS
In this manual, the following symbols are used to indicate particular text blocks.
Caution!
A dangerous situation may arise that may cause damage to material.
Hint
Hints and additional notes
New
New features

DIVUS HEARTBEAT user manual . 3
INDEX
GENERAL INFORMATION __________________________________________________________________________ 2
CONVENTIONS ___________________________________________________________________________________ 2
INDEX ___________________________________________________________________________________________ 3
1INTRODUCTION________________________________________________________________________________ 6
1.1 GENERAL INFORMATION_____________________________________________________________________ 6
1.2 THE MANAGER _____________________________________________________________________________ 7
1.2.1 DIVUS SECURE INTRANET ______________________________________________________________ 7
1.2.2 RESIDENTIAL INTERCOM NETWORK _____________________________________________________ 8
1.2.3 HOME LAN/WAN ______________________________________________________________________ 8
1.3 THE MANAGED SWITCH (DMS-8P-L2+) _______________________________________________________ 8
2SYSTEM INFRASTRUCTURE _____________________________________________________________________ 9
2.1 GRAPHS/SCHEMES _________________________________________________________________________ 9
2.1.1 GENERAL SCHEME_____________________________________________________________________ 9
2.1.2 ISOLATED NETWORK SCHEME _________________________________________________________ 10
2.1.3 DIVUS SECURE INTRANET (DSI) SCHEME________________________________________________ 12
2.1.4 RESIDENTIAL INTERCOM NETWORK (RIN) SCHEME_______________________________________ 13
3WEB INTERFACE______________________________________________________________________________ 14
3.1 FIRST ACCESS: THE SETUP WIZARD _________________________________________________________ 14
3.1.1 STEP 1 - START_______________________________________________________________________ 14
3.1.2 STEP 2 LICENSE AGREEMENT ________________________________________________________ 15
3.1.3 STEP 3 SYSTEM INTEGRATOR DETAILS ________________________________________________ 16
3.1.4 STEP 4 CUSTOMER DETAILS _________________________________________________________ 17
3.1.5 STEP 5 PROJECT SETUP _____________________________________________________________ 18
3.1.6 STEP 6 NETWORK CONFIGURATION - DIVUS SECURE INTRANET_________________________ 18
3.1.7 STEP 7 NETWORK CONFIGURATION - RESIDENTIAL INTERCOM __________________________ 19
3.1.8 STEP 8 SUMMARY / LAST STEP ______________________________________________________ 19
3.1.9 NETWORK SCAN______________________________________________________________________ 20

DIVUS HEARTBEAT user manual . 4
3.2 SYSTEM STATUS PAGE_____________________________________________________________________ 20
3.3 SYSTEM UPGRADE _______________________________________________________________________ 20
3.3.1 UPGRADE PROCEDURE________________________________________________________________ 21
3.4 SYSTEM SHUTDOWN _____________________________________________________________________ 23
3.5 DIVUS NETWORK REPORT PAGE___________________________________________________________ 23
3.5.1 THE GRAPHICAL SCHEME _____________________________________________________________ 24
3.5.2 THE PDF FILE OF THE REPORT _________________________________________________________ 25
3.6 DIVUS NETWORK PERFORM SCAN PAGE ___________________________________________________ 25
3.7 DIVUS NETWORK ARCHIVE PAGE__________________________________________________________ 27
3.8 SIP STATUS PAGE__________________________________________________________________________ 27
3.9 LOGS SWITCH LOGS PAGE________________________________________________________________ 28
3.10 LOGS VOIP/SIP LOGS PAGE ____________________________________________________________ 28
3.11 LOGS CALL LOGS PAGE________________________________________________________________ 28
3.12 SETTINGS SYSTEM PAGE_______________________________________________________________ 28
3.13 SETTINGS NETWORK SETTINGS PAGE ___________________________________________________ 29
3.13.1 DHCP________________________________________________________________________________ 29
3.13.1.1 DSI _____________________________________________________________________________ 29
3.13.1.2 RIN _____________________________________________________________________________ 29
3.14 SETTINGS SMART DEVICES PAGE _______________________________________________________ 30
3.15 SETTINGS FIREWALL RULES PAGE ______________________________________________________ 30
3.16 SETTINGS PORT FORWARDING PAGE____________________________________________________ 32
3.17 SETTINGS SIP SETTINGS PAGE__________________________________________________________ 33
4INTERCOM ___________________________________________________________________________________ 34
4.1 GENERAL DEFINITIONS _____________________________________________________________________ 34
4.2 GENERAL VOIP ACCOUNT SCHEME (FOR ZONE 1 AND ZONE 2) ________________________________ 35
4.2.1 BASE UNIT ___________________________________________________________________________ 36
4.3 VOIP ACCOUNTS FOR EXTERNAL UNITS______________________________________________________ 37
4.4 CONCIERGE / RECEPTION ACCOUNTS _______________________________________________________ 38
5CLIENT DEVICE SETUP FOR THE DSI AND THE RIN _______________________________________________ 39

DIVUS HEARTBEAT user manual . 5
5.1 DIVUS TOUCHZONE________________________________________________________________________ 39
5.2 DIVUS SUPERIO AND OTHER WINDOWS BASED DIVUS DEVICES _______________________________ 39
5.3 DIVUS OPENDOOR _________________________________________________________________________ 39
5.4 KNX CONTROL DEVICES (KNX SERVER, KNX SUPERIO)_________________________________________ 40
5.4.1 SPECIAL RULES FOR DIVUS KNX SERVER AND KNX SUPERIO______________________________ 40
5.5 THIRD-PARTY IP CAMS _____________________________________________________________________ 41
5.6 THIRD-PARTY CLIENT DEVICES (WITH ETHERNET INTERFACE)__________________________________ 41
5.7 ANALOGUE THIRD-PARTY DEVICES__________________________________________________________ 41
6ADVANCED TOPICS___________________________________________________________________________ 42
6.1 HOW TO MOVE A DEVICE USING A STATIC IP ADDRESS TO YOUR HEART ______ 42
6.2 HOW TO USE THE LOG FILTERING / SEARCHING FUNCTION ___________________________________ 42
6.3 HOW TO EDIT VOIP ACCOUNTS ON THE DIVUS HEARTBEAT ___________________________________ 43
6.4 HOW TO DEFINE CUSTOM VOIP GROUP CALLS ON THE DIVUS HEARTBEAT _____________________ 44
6.5 HOW TO ADD/EDIT A CUSTOM FIREWALL RULE ______________________________________________ 46
6.6 HOW TO DEFINE OR EDIT A CUSTOM PORT FORWARDING RULE _______________________________ 47
6.7 HOW TO SETUP A DEVICE FOR REMOTE VOIP ACCESS ________________________________________ 48
NOTES _________________________________________________________________________________________ 50

DIVUS HEARTBEAT user manual . 6
1Introduction
1.1 GENERAL INFORMATION
in the optimal way.
The main goals of your new DIVUS HEARTBEAT are:
•Making the connection of all your smart home devices as simple as plug and play
•Isolating and securing the most sensitive devices from undesired external attacks
•Managing, controlling and troubleshooting your network and its devices
allowing you to solve very complex network tasks and requirements automatically.
The DIVUS HEARTBEAT is made of two parts: the manager and the managed switch. These parts are held
together with the 19-inch rack adapters.
It may be expanded by adding any number of additional switches if more ports are needed.

DIVUS HEARTBEAT user manual . 7
1.2 THE MANAGER
The manager is the heart and the brain of the system: it controls 3 separate networks:
•The DIVUS Secure Intranet (also called DSI later on)
•The Residential Intercom network (RIN)
•The Home LAN/WAN
It is the gateway between all these three networks.
Its web server gives access to all the functionalities of the DIVUS HEARTBEAT.
See chapter 3 for further details about the web interface.
Note: The three network ports of the Manager are not PoE ports! If e.g. you connect one single device
to the Residential Intercom port and it needs power over the network cable, you must use a so-called PoE injector
or an additional DIVUS MANAGED SWITCH.
now have a quick look at the 3 networks.
1.2.1 DIVUS SECURE INTRANET
The DIVUS Secure Intranet is meant to offer an isolated, secure network for your smart home devices. E.g. a
DIVUS KNX SERVER, DIVUS TOUCHZONE and SUPERIO touch panels would be connected to this network. If you
follow the instructions of the DIVUS HEARTBEAT Quick Start Guide orof this manual for connecting all the devices,
any of the 8 main ports of the main MANAGED SWITCH can be used to connect to the DIVUS Secure Intranet.

DIVUS HEARTBEAT user manual . 8
1.2.2 RESIDENTIAL INTERCOM NETWORK
A safe, reliable network used for intercom communications: a firewall blocksany communication from this network
to the outside world except for the VoIP communication to the VoIP server, which runs on the manager itself.
Depending on the number of outdoor devices you need to connect (outdoor stations, security cams), you may
need a DIVUS MANAGED SWITCH to be connected to the main RIN (Residential Intercom Network) port.
1.2.3 HOME LAN/WAN
, it may or may not be
As default,
this port connects the DIVUS HEARTBEAT and the devices attached to it to the internet.
1.3 THE MANAGED SWITCH (DMS-8P-L2+)
The MANAGED SWITCH is an 8 ports full PoE+ switch, with two additional ports to connect to other devices in a
chain. It is known to the manager, which is therefore able to not only talk directly to the devices attached to the
Any number of DMS may be attached to
the main DMS using its dedicated ports 9 and 10 (cascading).
The other ports are currently not available for use.

DIVUS HEARTBEAT user manual . 9
2System infrastructure
In this chapter, the inner workings and the tasks of the single parts of the DIVUS HEARTBEAT will be explained
with easily understandable graphical schemes.
2.1 GRAPHS/SCHEMES
2.1.1 GENERAL SCHEME
3 networks interconnected: DIVUS HEARTBEAT splits a complex system up into 3 separate, easily manageable
and safe networks. How they are structured and how they relate to one another and to the internet is shown in
the general scheme:
The above shows a typical network structure probably the one most frequently adopted.
But to best understand how the DIVUS HEARTBEAT handles different setups, there are some other points to
consider:
1. Usually the planned scheme is the one shown above, but when the automation
devices and network are commissioned, there is no router yet it will follow
weeks or even months later.
2. Customers may prefer to have their automation system completely detached
from the internet. In that case, the final scheme will be similar to the above,
but without the connection to the router and through that the internet.

DIVUS HEARTBEAT user manual . 10
2.1.2 ISOLATED NETWORK SCHEME
So, what happens when the network has no router in the beginning but one will
be connected later on?
1. All the steps of the quick start guide should be followed. (All devices are connected, the first setup
procedure on the DIVUS HEARTBEAT is completed by the network scan)
2. In this situation, the DIVUS SECURE intranet and the RESIDENTIAL INTERCOM are fully functional (except,
of course, the online services).
3. Automatically detecting that there is no router active, the DIVUS HEARTBEAT will take control of the
a. role
b. Through DHCP and NETBIOS/WINS, it will assign IP addresses and names to the devices and
make sure that special devices (e.g. a DIVUS KNX SERVER) are reachable from anywhere.
4. To open additional communication channels to/for custom devices, you can use special pre-sets or
define your own new rules. See chapters 3.14, 6.5, 6.6 for details.
At this point, an isolated system is ready to be used. A system where a router will follow in the future can
also work with this configuration without any problems.
When the router is finally installed and connected, what happens to a previously
configured system with a DIVUS HEARTBEAT?
When the router is connected to the DIVUS HEARTBEAT:
•The DIVUS HEARTBEAT detects the new device and its roles
•The DIVUS HEARTBEAT will pass the general network management roles to the newcomer:
oDHCP server role is passed to the router. This means that all the DHCP addresses leased will
be renewed by another server which might also move all the devices to a completely different
network.

DIVUS HEARTBEAT user manual . 11
•The DIVUS HEARTBEAT will continue to play the primary or secondary WINS server for the network. In
this way, it will still be able to resolve calls to dhb-heartbeat to the desired underlying IP addresses.
•The DIVUS HEARTBEAT is able to switch from an isolated network (see 2.1.2) to a connected one (see
2.1.1) or vice-versa every time it is needed:
START
RUN DHCP CLIENT
DHCP SERVER
FOUND?
PLAY DHCP SERVER
PREVIOUS
ADDRESS
AVAILABLE?
USE PREVIOUS
ADDRESS/
NETWORK
NO
YES
STOP OWN DHCP
SERVER
YES
USE DEFAULT
ADDRESS/
NETWORK
NO

DIVUS HEARTBEAT user manual . 12
2.1.3 DIVUS SECURE INTRANET (DSI) SCHEME
The DIVUS SECURE INTRANET is the network reserved for your home automation and visualisation devices. Being
a network managed by a dedicated switch and manager means having these advantages:
•A dedicated bandwidth for your home automation it will not be influenced by the use of other networks
(e.g. big downloads or streaming on a home LAN device)
•If will be safer
opartly because it is in a separate network,
opartly because there is a firewall between your home automation devices and your domestic
LAN devices.
•Devices connected to your DSI are considered trustworthy and therefore have access to all other
networks (and their devices)
•The DSI is part of the same network where your domestic LAN devices are. But the communication
from the home LAN to the DSI is possible only if custom rules are defined on the DIVUS HEARTBEAT to
allow it. See chapter 6.5 and 6.6.

DIVUS HEARTBEAT user manual . 13
2.1.4 RESIDENTIAL INTERCOM NETWORK (RIN) SCHEME
These are the relations the residential intercom network has:
1) EXTERNAL UNITS and security cams should be placed inside the RIN to take advantage of its special
security. Devices placed in the RIN
1
They only can
reach the DIVUS HEARTBEAT on its VoIP port.
2) Usually the devices of the RIN will communicate with those of the DIVUS SECURE intranet. The VoIP
communication is managed by the DIVUS HEARTBEAT which all the devices in the network can reach.
Devices placed inside the DIVUS SECURE intranet are considered trustworthy and can therefore reach
all other devices. So, showing e.g. the camera stream of an EXTERNAL UNIT on a DIVUS TOUCHZONE
placed in the DSI is not a problem, it will be accessible per default.
3) A device from the home LAN might want to access something inside the RIN. An example may be a
mobile device to be connected to the VoIP system and therefore needing access to the HEARTBEAT
HEARTBEAT. See chapter 6.5 for details.
4) Finally, also devices from the internet might be configured to get in touch with those from the RIN.
That can happen when the user needs e.g. a mobile device to be part of the VoIP system also from
outside the LAN.
See chapter 6.7 for the setup of a remote access to the intercom system.
1
hem first.
1
2
3
4

DIVUS HEARTBEAT user manual . 14
3Web interface
3.1 FIRST ACCESS: THE SETUP WIZARD
The first time the device is started, it will show the setup wizard which is used to store the most important
information about the device and the project. Choose between English (default) or German to immediately switch
3.1.1 STEP 1 - START

DIVUS HEARTBEAT user manual . 15
3.1.2 STEP 2 LICENSE AGREEMENT
Read and accept the license terms checking the checkbox in step 2:

DIVUS HEARTBEAT user manual . 16
3.1.3 STEP 3 SYSTEM INTEGRATOR DETAILS
Fill in at least the fields with a * about the system integrator, but we recommend taking the time to fill out all the
fields to have complete and clear reports thereafter.

DIVUS HEARTBEAT user manual . 17
3.1.4 STEP 4 CUSTOMER DETAILS
Again, fill in at least the fields with a * about the customer (again we recommend to fill out all the fields)

DIVUS HEARTBEAT user manual . 18
3.1.5 STEP 5 PROJECT SETUP
than one DIVUS HEARTBEAT are in the same network, their hostnames must be different to avoid issues. You
may change dhb- dhb-
end if longer than 15 characters total. Alternatively, you may also use dhb-<serial number> (e.g. dhb-21234)
as hostname. You can find the serial number on the status page.
3.1.6 STEP 6 NETWORK CONFIGURATION - DIVUS SECURE INTRANET
advanced features
we recomme (DHCP)

DIVUS HEARTBEAT user manual . 19
3.1.7 STEP 7 NETWORK CONFIGURATION - RESIDENTIAL INTERCOM
Usually you may keep these default settings for the RIN and therefore use static addresses of the 192.168.69.0
network, or change them to your special needs. If needed, you may also activate a DHCP server or a DHCP client
function. The recommended setting is using static IP addresses for this network.
If using the DHCP server function for the RIN, please make sure that there is no other device in this network
having an active DHCP service!
3.1.8 STEP 8 SUMMARY / LAST STEP
This last step shows the access data and the most important settings to be confirmed pushing the FINISH button.
Please note that you have to remember these settings to access the web interface from here on!
After pushing the FINISH button, the system will reboot to apply all the settings.

DIVUS HEARTBEAT user manual . 20
3.1.9 NETWORK SCAN
The Network scan is started automatically after the setup wizard is completed. See 3.5 and 3.6 for further details.
3.2 SYSTEM STATUS PAGE
s
state, with memory and disk usage, name and IP addresses, load, uptime and the
3.3 SYSTEM UPGRADE
If the DIVUS HEARTBEAT has access to the internet, it will check whether there is a new firmware version
available online when you open this page. If so, you will be informed and may start the upgrade procedure by
pushing the button.