Skip to main content

FAQs

This FAQ covers common technical and operational questions about managing controllers in XSponse. For detailed procedures, refer to the related user guides linked at the bottom of the page.

What is the difference between restarting services and rebooting the controller?​

Restarting services only restarts the internal processes of the controller (e.g., network or agent services), while rebooting restarts the entire device hardware. Restarting is faster and less disruptive, ideal for addressing transient issues without downtime.

When should I restart services instead of rebooting?​

Restart services when you're experiencing minor issues like:

  • Temporary communication loss
  • UI unresponsiveness
  • OTA updates not being picked up
  • Sync delays Use reboot only if restarting services does not resolve the problem or if there's a deeper hardware-level issue.

Does restarting services affect controller configuration?​

No. Restarting services does not alter configuration, logs, or historical data. It temporarily interrupts communication but preserves all settings.

What happens to online status during a services restart?​

The controller may briefly show as offline during the restart process, but it should return to "Online" within a few seconds after services resume.

Will current sync or OTA jobs be canceled if I restart services?​

Yes. Active jobs may be interrupted. It is best to verify no critical actions are running before performing a services restart.

Can I restart services remotely?​

Yes. Both Restart Services and Reboot can be executed remotely through the XSponse UI, as long as the controller is online and communicating with the platform.

What does a controller reboot do under the hood?​

A reboot powers down the controller hardware and restarts the entire system stack, including OS, services, network, and internal agents.

Can rebooting resolve controller sync issues?​

Yes. Rebooting can help reinitialize services and network stacks that may be causing persistent sync failures. Use it as a last resort after trying a service restart.

Will I lose log history after a reboot?​

No. Logs are preserved through reboots unless the controller's storage is corrupted or intentionally cleared.

How long does a reboot typically take?​

It usually takes about 1–2 minutes. During this time, the controller will appear offline.

Is it safe to reboot the controller during production hours?​

It’s best to reboot during low-activity periods to avoid interrupting in-progress jobs or communications. Rebooting is disruptive and should be planned when possible.

What if a controller doesn’t come back online after a reboot?​

Wait a few minutes and refresh the UI. If it remains offline:

  • Check power and network connections
  • Attempt a hard power cycle
  • Contact support if it remains unresponsive

Can I view a history of reboots or service restarts?​

Yes. You can view these events in the Logs section under the corresponding controller. Look for action labels like REBOOT or SERVICE_RESTART.

What is the difference between Production OTA and Staging OTA?​

  • Staging OTA allows testing firmware updates in a pre-production environment.
  • Production OTA applies updates to live devices and should be used only after validating builds.

Can I cancel an OTA update once initiated?​

No. Once pushed, an OTA update will proceed unless the controller loses connectivity. You can monitor status in the logs, but cancellation is not supported.

Why does my OTA update remain in “Pending”?​

The controller may be:

  • Offline
  • Busy with another operation
  • Not yet eligible due to build rules or version mismatch Try restarting services to prompt it to check in.

What does the Sync function do?​

Sync forces the controller to:

  • Pull the latest configuration from the platform
  • Push local logs
  • Revalidate its cloud connection This is useful for manual updates or recovering from desync issues.

Is syncing safe during other tasks?​

Yes. Syncing is non-disruptive but may consume bandwidth. Avoid syncing during time-sensitive uploads or critical performance windows.

How often should I sync a controller?​

Controllers sync periodically on their own. Manual sync is only needed if:

  • You’ve changed configuration and want to apply it immediately
  • The controller hasn’t synced for an extended period
  • You're troubleshooting an issue

Can sync trigger configuration rollback?​

No. Sync only pulls the latest saved configuration from the platform. It won’t revert or override current settings unless explicitly changed.

What kind of logs are available in the controller log viewer?​

You can view:

  • System activity
  • OTA updates
  • Reboots and restarts
  • Error and exception events
  • Sync records Each log is timestamped and categorized for easy filtering.

Are logs deleted on a rolling basis?​

Yes. Logs are retained according to your retention policy and storage limits. Older entries may be pruned automatically.

What’s the best way to verify if a controller is healthy?​

Check:

  • Online status
  • Last activity timestamp
  • Sync logs
  • Errors in the log viewer
  • Response to manual sync or restart

Can I rename a controller?​

Yes. Go to the controller's action menu and use Edit Name to change its identifier for easier tracking in the UI.

Will renaming a controller affect its functionality?​

No. Renaming is cosmetic and does not affect how the device functions or communicates with the platform.

What does the "Last Activity Time" column mean?​

It shows the most recent timestamp when the controller communicated with the platform—either via sync, heartbeat, or action log.

Why does a controller appear as "Online" but not respond to actions?​

This may indicate:

  • A partial connection issue
  • Frozen services
  • A mismatch between cloud status and local activity Try restarting services or syncing the controller.

Can multiple controllers be rebooted or synced at once?​

Currently, actions like reboot, restart services, or sync must be performed per controller. Bulk actions may be supported in future updates.

Will a controller auto-update firmware?​

Only if explicitly configured for auto-OTA or if an update is pushed manually from the platform.

What should I do if a controller is permanently unresponsive?​

After verifying power and network:

  • Try a hard reboot (unplug/replug)
  • Review logs for last successful activity
  • Contact support with controller ID and log export if needed