Skip to main content

Status History

All components in NeuroomNet have a status that can change over time. The following statuses exist:

  • ONLINE1: The respective device is switched on and in contact with NeuroomNet
  • OFFLINE1: The respective device is switched off or not in contact with NeuroomNet
  • Various (freely definable) error statuses

The purpose of the Status History module is to allow the history of the statuses of all components and groups (groups inherit the status of their subordinate components or subgroups) to be viewed retrospectively2. For example, the following can be displayed:

  • When which devices were running, or which devices were in which status at what time
  • Uptime / downtime of devices
  • Display of power consumption and energy costs of individual devices or groups3

These displays can be useful for the following reasons:

  • Optimising / minimising power consumption (it may become apparent that certain devices are running all day when they do not need to; this could potentially be optimised using time control or scripts)
  • Finding out whether the devices and the entire infrastructure / NeuroomNet installation are running with sufficient reliability (a high downtime of important devices can, for example, indicate a possible problem that should be investigated)

The frontend of the Status History module therefore consists of two tabs, each described in the following two subchapters:

  • Status View: The actual module functionality, i.e. displaying the status history data
  • Settings: Basic settings for the status history can be configured here

Footnotes​

  1. Important note: Depending on the provider of the respective component, the statuses may not correspond to the actual state (switched on vs. switched off) of the device represented by the component in the real world. For example, components connected via UDP are always shown as online in NeuroomNet because they are not in regular contact with NeuroomNet (in contrast to components/devices connected via TCP, for example). Apart from this, there are also cases such as a temporary intranet outage, during which all TCP components will appear offline to NeuroomNet even though the devices themselves are still running. ↩ ↩2

  2. Technically, it is possible to display old statuses because NeuroomNet has logged all status changes in a dedicated database since version 2023.3. ↩

  3. The display of power consumption is currently only approximated via a specified average consumption of the respective components/devices. A future version of NeuroomNet plans to integrate specific smart sockets that actually measure power consumption for more accurate readings. ↩