Hive is an advanced web-based network management tool specifically designed for Meshmerize networks. It streamlines the visualization, configuration, and operation of distributed Meshmerize networks, accessible conveniently through your web browser. This tool is integral for managing the complex dynamics of Meshmerize networks, ensuring optimal performance and ease of use.
Hive's architecture comprises three primary components:
We continually strive to enhance Hive's capabilities. If you encounter any bugs or have suggestions for improvement, please contact us at [email protected]. Your feedback is invaluable in making Hive an even more powerful tool for network management.
You can create a new Hive deployment through the Meshmerize Portal - see here for more information on starting a new Hive deployment
Note: You can configure which node group each node belongs to, from
Nodes > [select the node] > Management > Name & group.
The nodes that are connected to Hive will show up on the topology map. You can upload any arbitrary image (e.g. Floor plan, Satellite image of the site, etc.) as the background for this topology map through the
Hive settings > Floor plan page. Inside the topology page, you can drag and drop the static nodes, so that it better resembles your scenario.
The colored lines between nodes represent direct links between neighbor nodes. You can filter the node groups that should be displayed on the topology map. Typically, you might want to hide the mobile nodes and only show the static nodes on the map.
On the Topology page, topology offers the set of the following management functions:
The GPS topology uses Leaflet to display the GPS coordinates of the nodes. This feature only works if GPS data is provided by the Hive-Worker. For Hive-Worker to do that, the GPS functionality needs to be enabled inside the device settings and GPS coordinates need to be written to the
/tmp/mmgps_data file on the device. The following sections will explain the steps necessary to display your device's GPS coordinates inside the GPS Topology.
The GPS can be enabled either by using the Luci graphical interface or by editing the
/etc/config/meshmerize on the device.
Luci (GUI): check the “GPS” box inside the Meshmerize Configuration tab.
option gps ‘1’ to the
hive-worker section of
/etc/config/meshmerize on the device to enable the GPS functionality.
If GPS is enabled Hive-Worker will expect that the GPS coordinates are provided by the file
/tmp/mmgps_data on your device.
To parse the coordinates correctly, Hive-Worker needs them to be in the format of the decimal degrees standard, in this case with six decimal places. The latitude and longitude values need to be separated by a blank space.
51.361938 13.468690 ← the blank space is important.
The GPS coordinate updates are determined by both the Hive Settings update frequency and the GPS receiver being used.
Nodes page displays all the nodes known to Hive and information about the node :
|Node is online.|
|Node is offline|
|Trial node (node doesn't have a valid license).|
|Shadow node (Has not been seen by the Mesh management, but was referenced by other nodes).|
|Node error - contact support|
Control Panel can be opened from the left navigation bar. It provides a method to send commands to multiple nodes at the same time.
The control panel offers network-wide command execution. You can run commands simultaneously on multiple nodes, either by using the input field or by uploading prepared scripts. The results of the commands are displayed in real-time (if live updates are enabled): you can follow the live feedback of latency or throughput measurement tools.
This tab allows you to send a single command to all nodes which are selected from the filter
This tab allows you to send a single file to a target directory in all nodes that are selected from the filter
This tab has filters that you can apply to target a specific set of nodes for the command or the file.
NOTE: Irrespective of whether you have a filter active or not, commands and files are sent to ALL devices that have a checkmark in their card in the grid below
Shows each node that is satisfying the above filter and a checkmark that indicates whether or not the command/file is sent to it. It also shows an overview of its status, the last command, its status, and its reply
Configurations allow users to apply a wide variety of settings in bulk to all nodes.
To configure the entire network, we use two key steps: Actions and Tasks
Actions run a single set of predefined commands on a node with user-entered values for variables. They take values from the form inputs and run a pre-defined set of commands based on the form values. Form values can include inputs in form fields or node-specific variables like or
Actions can be enabled or disabled by pressing the circle icons. Only enabled actions will be run during tasks, and disabled actions will be ignored.
A single action can be run using the icon
Underlying commands need to be imported to a hive-instance by Meshmerize Support
Tasks can be used for batch management of network nodes
1 task will run 1 action with a defined set of form inputs on one/many group(s) of nodes
Taks can be provided an "order" parameter that can help create a queue of tasks. All tasks can be enabled/disabled by checking the "is active" checkbox.
The tasks page is to chain different tasks together using the order parameter to run multiple actions for a set of nodes. Tasks are a set of actions applied to specific nodes, filling in all the placeholders, details can be found in the individual task page, along with the active checkbox.
All tasks can be automatically run on the entire network based on “order” and “is active” values
Taks can be run with an "apply" action at the end which can apply configuration changes by committing on success and reverting on failure.
It is recommended to run the tasks on the entire network when new nodes are added to the network
The user (customer’s network admin/service staff) can run tasks to help maintain uniform config across the network
This tab shows the history and status of previously executed tasks
This tab includes the list of settings that define the operation of the Hive as well as the operation of the access point agents. Some of the settings have [R] in the beginning of the name, which means that after saving the value, all access point agents will be restarted and will be offline for some time (only the agent is restarted not the node). Button "Restart AP agents" will manually trigger the restart of the agents.
This tab allows set your alert preferences for events in the network
This tab allows you to create a custom set of node groups (for example access points, robots, drones, etc.) with respective icons. Later the groups can be assigned to nodes on the Node page.
In this tab a new firmware can be uploaded to be later flushed on the nodes. Firmware updates can be done on the Node page.
In this tab you can upload your own floor plans or any custom images that will be displayed in the topology overview. You can have multiple images, but only one active topology image, which can be changed with the help of the radio button in the table. Every image has fields "width" and "height", which define how large will be the topology area. They shouldn't necessarily correspond to the dimensions of the image. The larger the dimensions the deeper you will be able to zoom in topology overview.
In this tab you can upload files that can be later uploaded to a node, or multiple nodes. You will find the same form on the Node page, and all the files uploaded through that form will end up here in the managed list.
In this tab, you can control the devices that are allowed to connect to Hive. You can create a list of allowed IPs, and a list of IPs that can be auto-approved to connect to Hive
You can also manually add MAC addresses of devices to Hive, this will allow them to communicate with Hive as soon as they come online
The bottommost tab shows a list of devices that are pending approval to connect to Hive, and also lists of approved and ignored devices. You can change their status by clicking on the , or .
The device passwords shown here are required by the device for continuous communication with Hive. Changing this password requires reconfiguration of the devices.
Adding Custom Data to be retrieved in possible through this setting. For changes to be applied you should restart all the AP agents from the Hive Settings -> System. After saving the value, all access point agents will be restarted and will be offline for some time (only the agent is restarted not the node). Button "Restart AP agents" will manually trigger the restart of the agents.
This page allows you to create, invite, update, and delete users. Admin users are marked with the Cog icon.
Admin users can execute management functions, such as change settings, send commands, upload files, etc.
Simple users can only view the information without any influence on the Hive.
Clicking on a user's name allows the admin to deactivate, promote to admin, and also reset a user's password.
Users can also create Access Tokens for API access to Hive. This would be needed for connecting Hive with other apps or performing other functions such as configuring new actions