Vertex groups consist of 1 or more Vertex controllers. Vertexes in a group communicate internally with each other in the group with peer to peer (server/client) communication. A Vertex controller in a group ‘sees’ (knows only of the existence of) other Vertexes in the same group. Commands from other Vertex groups are not present, which reduces traffic on this internal XMPP bus. Communication between groups is still possible. This is done via TCP/IP communication and is slightly slower in speed. Using groups is an optimization of communication, where you can separate and limit communication between floors, areas, etc.
Vertex cluster is a system of up to 25 Vertex controllers. Communication between clusters is done via TCP/IP. All Vertexes in one cluster share the same cluster ID - CUID (a Node.js based identifier with collision-resistant communication). Vertexes in a cluster can be divided into groups.
Most sites have only one cluster on the LAN, if your site has more than 25 controllers, we recommend contacting support for configuration advice.
To manage your cluster enter NetConfig: http://VERTEX_IP/netconfig/home
After that, you will see all units which you want to configure as groups. You have 15 Vertex groups in one network, so you can create up to 15 stand alone Vertex groups.
Vertex group in netconfig is NOT the same as vertex group in GUI/Node-RED. Vertex group in netconfig is a group of Vertex controllers. Vertex group in GUI/Node-RED is a group of luminaires.
The last step is sending the configuration to Vertexes with CUID. Choose to send the configuration with the old CUID.
It is important when you are replacing one Vertex. CUID identifies your site. By selecting the old CUID you don't have to authorise it again (you don’t lose access and connection to Glamox Connect).
For a better understanding, consider these two examples:
Vertex controllers in one Vertex group in one cluster in one network
Vertex controllers in different Vertex groups in one cluster in one network
0 Comments