Skip to content

LUUM.IO

Tech Mode and the terminal#

Tech Mode exposes advanced tools for trained operators. It does not grant a new account role, site access, or permission to bypass a server restriction. Work on the intended site and understand a command before running it.

Enable Tech Mode#

  1. Open your user menu and choose Profile (Account Settings in the classic interface).
  2. Open Advanced and enable Tech Mode. Wait for the saved confirmation.
  3. Return to the intended site. In V10, open the user menu and choose Terminal. In the classic desktop interface, use the terminal icon in the header.

Admin and Company accounts can enable the setting. Super Users already have terminal access without enabling it. Basic and Public accounts do not gain terminal access through Tech Mode. Simple mode hides the terminal; switch out of Simple mode if an authorized account cannot see it. The classic mobile header does not show the desktop terminal button.

The terminal can also be toggled with T when it is available and focus is outside an editable field. Use its close control when finished. Closing the panel does not undo commands that have already completed.

Start with help#

Command Purpose
help List the commands supplied by this frontend.
help <command> Read that command's description, options and examples. For example, help stuset only displays help.
clear Clear the terminal's displayed output. It does not reset the site or devices.

The command list reflects the frontend build. It does not guarantee that every command is implemented or enabled by the connected backend. For an unsupported command or permission error, keep the error and contact engineering; do not switch environments or try a destructive alternative.

Commands such as save, set, profile, reset, reboot, replace, undelete and stuset can change cloud or device state. Device reads can also have firmware-specific effects. Help output is a safer starting point than trying a command on a live site.

What stuset does#

stuset is a destructive site reset, not a routine troubleshooting or synchronization command. Do not run it to refresh a page, repair an empty table, or finish ordinary commissioning.

The checked-in legacy backend reset does all of the following for the active site:

  • Deletes scene-to-location associations, point-to-point table rows and saved location-template rows.
  • Marks scenes, networks and non-root locations deleted.
  • Marks qualifying automation link-table entries deleted.
  • Resets device custom names to their underlying names and roles to -.

The legacy reset operations can finish independently and return per-step results. A success message alone is not proof that every operation succeeded; partial changes are possible. It is not an automatic hardware factory reset, and no automatic undo is provided by this command.

The terminal normally asks for confirmation. Its -o and --override options skip that confirmation; they do not make the operation safer or bypass server authorization. Do not use those options on a live site without an explicitly approved reset procedure, verified recovery plan and engineering supervision. The legacy endpoint admits installer/Admin, Company and Super User roles subject to the normal backend access checks.

The native Harbor API source currently has no stuset route. The shared terminal still includes the command for legacy compatibility. Do not assume the destructive legacy operation is available in Harbor, and do not redirect it to a legacy backend to work around that boundary.

If the terminal is missing or a command fails#

Check that the correct site is open, the account has the required role, Tech Mode was saved if needed, and Simple mode is off. A permission or unsupported-endpoint response requires investigation. Preserve the command text, site, time and sanitized error; exclude tokens, MQTT passwords and other credentials from screenshots or support messages.

For an authorized site reset, obtain engineering's exact backend/version and recovery procedure before any reset attempt. A normal Settings Apply, scene edit and site reset are different operations; approval for one does not authorize the others.

This guide describes the current Harbor interface and the retained legacy command behavior. Updated November 7, 2026.