Gateway / Nodes List

This Nodes > List View page shows the list of nodes that have been added to the Gateway. This list may be empty if there is no ZAP (Zigbee Access Point) connected or if the ZAP is connected but no wireless nodes have been added to the Gateway.

Nodes List

Note the hierarchy of settings for Nodes and Sensors. The nodes list (above) lists each node connected to the Gateway, with status information and links to take action or view node settings.

The node settings page provides status and communications information specific to that node, allowing users to change node level settings and list the sensors associated with that node. Navigate to the node settings page using the drop-down ‘action’ menu. The user can then go a level deeper into a settings page for each sensor.

Note: Some “batch commands” are available from the nodes list page that can save time when configuring data export. A batch command is a command that changes settings for all of the sensors on a node.

For each node in the network the following information is shown:

Name: The node name, by default this is the node serial number but may be assigned on the Nodes > Settings page (use the ‘action’ drop-down menu to access this page).

Product Code: The EpiSensor specific product code. Details on product codes can be found in the products section of this user guide or at

Serial: The unique serial number of the node (also referred to as the “long address” of the node).

Last Data: The amount of time since the last data point was received from any sensor of this node. This will show “None” if no data has been received.

Note: this value is approximated to the nearest second, minute, hour or day. For example “5 hours” could be 5 hours plus any number of minutes and seconds past the hour. The exact time of the last data point can be found on the Node Settings page.

Export: If at least one sensor of this node is enabled for data export then a tick will be shown . Otherwise it is set to the following icon:

In Sync: A warning icon will be shown if there are over-the-air commands pending for this node: Over-the-air commands are issued as a result of selecting an “Action” from the drop down list for each node. If the node is ‘in-sync’ with the information on the Gateway, the following icon will be shown:

Status: If no communications have been received (data or heartbeats) from a node in the last 30 minutes, the status column will show the following icon: Otherwise the column will show the following icon: The purpose of this field is to highlight nodes that are no longer connected to the wireless network. “Heartbeats” are messages received regularly from all nodes on the network that inform that Gateway that they are active on the network.

Firmware: This field lists the version of firmware that each node is running. For optimal performance the node firmware version should be 2.60 or higher.

‘Legacy mode’ will automatically be enabled for nodes with a firmware version of 2.6 or lower. There are no additional settings to be configured for this mode. Data from these nodes will be interpolated to a 15 minute reporting interval. Cumulative sensors such as kWh or pulse sensors will report in kWh/15min period, for example. The Export ID and other parameters for these sensors can be configured in the normal way. For more information on Legacy Mode please contact

For each node in the network the actions shown below are available from the drop down list:

Nodes List Action Dropdown

Each of the actions above is described in more detail as follows:

Ping: Send a “Ping” over-the-air command to the node. The purpose of sending a Ping command to a node is to check if it is alive.

Refresh All Properties: A “node property” can be a read-only or configurable parameter relating to a node or sensor. Selecting this action will issue a command to request that all node properties be refreshed. This action will result in numerous over-the-air commands being issued. It can be used if the settings pages for a node or sensor have not been fully populated (i.e. that some fields are displaying a dash “-“ symbol). This could be caused by the Gateway being powered down while a new node is being added.

Export All: Enable data export from all sensors of this node. Export can be enabled or disabled for individual sensors from the Nodes > Settings (via “Action” drop-down list) > Sensor Settings (via “Action” drop-down list).

Export None: Disable data export for all sensors of this node. Export can be enabled or disabled for individual sensors of this node from the Nodes > Settings (via “Action” drop-down list) > Sensor Settings (via “Action” drop-down list).

Reset Node: Send an over-the-air command to reset the node. This is equivalent to power cycling the node (i.e. switching the nodes off and then on). No settings on the node will be lost.

Factory Reset Node: Send an over-the-air “factory reset” command to the node. In this case all node settings will be lost; the node will disconnect from the Gateway and will be returned to a factory default state.

Settings: Navigate to the Settings page for this node.

Delete: Remove this node from the Gateway. This does not remove the node from the wireless sensor network; it merely removes the node from the Gateway’s records. This typically would be used to remove unresponsive nodes from the list. If a responsive node is removed from the list, it will automatically be added the next time it sends a heartbeat or a data point to the Gateway. To permanently delete a live node from the Gateway, first issue a “Factory Reset Node” command to the node, then delete the node from the Gateway.

After an action has been selected, a response message will be displayed at the top of the page. In the case of actions which result in over-the-air commands being issued, the response message can only confirm that the command was sent. The log file (accessed through Logs > Log View) will provide information regarding the response received from the node, assuming the Log Level is set to a high enough level (see ‘Log Settings’ section for more information). When the command has completed (successfully or not) the In-Sync flag will show the tick symbol. However, to confirm that the command has been implemented users must either check the log file, or the relevant settings page.

The Gateway’s web interface is designed to work on a variety of mobile phone and tablet web browsers. If the Gateway is accessed from these devices, the screen size will adapt. For mobile phone browsers in portrait mode, the top navigation bar will be replaced with a drop down list. In addition, on pages that include a table of data, some columns will be hidden to improve the user experience:

Nodes List Mobile Browser

Next Page >>