Skip to content
English
  • There are no suggestions because the search field is empty.

How and When to Restart, Reboot, or Power Cycle an Enbase Hub

Learn the difference between Restart App, Reboot Hub, and a physical power cycle on an Enbase Hub, when to use each action, and when to contact Detechtion Support.

An Enbase Hub can be restarted in three different ways: Restart App, Reboot Hub, or a physical power cycle. These actions are not interchangeable. Use the least disruptive option that matches the issue you are troubleshooting.

1. Restart App

Use Restart App after changing Task or Channel properties in the Hub Control Panel (HCP).

Go to HCP > Utilities > Restart App.

Restart App restarts the Hub firmware application only. It does not restart the Hub operating system and does not require disconnecting power or wiring.

Use Restart App when:

  • You changed a Task property.
  • You changed a Channel property.
  • You need to restart the Enbase application without rebooting the entire Hub.

2. Reboot Hub

Use Reboot Hub when a software change requires the Hub operating system to reload.

Go to HCP > Utilities > Reboot Hub.

A reboot is performed through software and does not require physically disconnecting power. The Hub will temporarily become unavailable, and you will need to reconnect to HCP after the reboot is complete.

Use Reboot Hub when:

  • You changed settings on the Network tab, including the IP address, gateway, or netmask.
  • Support instructs you to reload the Hub operating system as part of troubleshooting.

3. Physical Power Cycle

A physical power cycle disconnects and restores power to the Enbase Hub at the panel. This is more disruptive than Restart App or Reboot Hub and should be used when the Hub is unresponsive or when the issue cannot be addressed through software.

A physical power cycle may be appropriate when:

  • Hub LEDs are flickering, or the LEDs are on but the Hub does not respond through HCP or the network.
  • The Hub experienced a brief undervoltage event and voltage dropped below 9 V during operation.
  • Battery Saver disconnected power and the Hub must be restored using the physical Power Up/Power Reset button.
  • Support is investigating a suspected database corruption or unexpected restart condition.

Battery Saver Recovery

If Battery Saver has disconnected Hub power, restore power by pressing and holding the physical Power Up/Power Reset button until the system boots and the relay resets.

If the Hub does not recover or immediately loses power again, stop troubleshooting and contact Detechtion Support.

Checking for a Possible Database Issue

If the Hub is restarting unexpectedly, review HCP > System Status > Utility and compare Kernel Startup Time with Startup Time.

A significant gap between Kernel Startup Time and Startup Time can indicate a database problem. If you see this condition, contact Detechtion Support. A power cycle may be used as part of the troubleshooting process, but recurring symptoms require further investigation.

Safety Before a Physical Power Cycle

Before disconnecting or reconnecting any cable or power source, confirm that the area is non-hazardous and follow the applicable panel installation and operations manual.

Do not disconnect wiring or power in a hazardous area. If you are unsure whether it is safe to perform a physical power cycle, stop and contact Detechtion Support.

What Should I Do After Power Is Restored?

Allow the Hub to complete its startup sequence, then verify that the Hub is responsive and communication has returned.

Check whether the original LED, voltage, HCP, or network symptom is still present. If the same issue returns after the power cycle, do not repeatedly cycle power as a workaround.

When Should I Contact Support?

Contact Detechtion Support if:

  • The Hub remains unresponsive after a physical power cycle.
  • LED flickering or abnormal LED behavior continues.
  • Low-voltage symptoms continue or the Hub repeatedly loses power.
  • Battery Saver repeatedly disconnects the Hub.
  • The Hub continues to restart unexpectedly.
  • A possible database issue is identified.
  • You suspect the Hub may be damaged.

Persistent symptoms may require hardware failure confirmation and, when appropriate, the hardware return or replacement (RMA) process.