Subsystems

Subsystems are logical groupings of devices and zones that represent major functional areas of your automation system, such as lighting, AV, HVAC, security, and shades.

Overview

The Subsystems page provides a comprehensive interface for managing all subsystems in your GEM installation. Each subsystem can contain multiple devices and zones, and can be enabled or disabled independently.

Viewing Subsystems

The main grid displays all configured subsystems with the following columns:

• ID - Unique identifier for the subsystem
• Name - Internal name (lowercase with underscores)
• Device - Optional associated hardware device
• Enabled - Whether the subsystem is currently active
• Sort Index - Display order in user interfaces

Grid Actions

• Add - Create a new subsystem
• Edit - Modify an existing subsystem
• Delete - Remove a subsystem (warning: this may affect associated zones and devices)
• Sort - Reorder subsystems by dragging rows
• Reload - Refresh the grid data

Creating a Subsystem

To create a new subsystem:

1. Click the Add button in the grid toolbar
2. Fill in the required fields:
   • Name - Internal identifier (auto-formatted to lowercase_with_underscores)
   • Label - User-friendly display name
3. Configure optional settings:
   • Device - Select an associated hardware controller (optional)
   • Enabled - Toggle to enable/disable the subsystem
4. Click Save Subsystem

Naming Convention

• Name: Must be lowercase letters, numbers, and underscores only (e.g., living_room_lights)
• Label: Can be any human-readable text (e.g., "Living Room Lights")

The Name field will automatically format your input when you click away from the field.

Editing a Subsystem

Click the Edit icon next to any subsystem to open the editor. The editor provides three tabs:

Subsystem Tab

Configure the basic properties of the subsystem:

• Name - Internal identifier (cannot be changed if zones/devices depend on it)
• Label - Display name
• Device - Optional parent device controller
• Enabled - Active state

Attributes Tab

Custom attributes allow you to store additional configuration data specific to each subsystem. Common attributes include:

• icon - Icon name for UI display
• color - Theme color for the subsystem
• default_level - Default brightness/volume level
• relay_states - Custom relay state mapping (JSON)

See the Attributes documentation for detailed information on managing attributes.

References Tab

Shows all places in the system that reference this subsystem (zones, macros, UI zones, UI macros). Click the Find References button to search. Results are grouped by category with counts and navigation links.

This is useful before deleting a subsystem to understand its impact across the system.

Common Subsystems

Typical GEM installations include these standard subsystems:

Name	Purpose	Typical Device Types
lighting	Lighting control	Lutron, Philips Hue, Relays
shades	Window treatments	QMotion, Somfy, Lutron
av	Audio/Video	Matrix switchers, receivers
hvac	Climate control	Thermostats, dampers
security	Security systems	Panels, cameras, sensors
access	Access control	Door locks, gates
pool	Pool/Spa control	Pool controllers, pumps
irrigation	Landscape watering	Irrigation controllers

Deleting Subsystems

Before deleting a subsystem:

1. Verify no zones are assigned to it (check the Zones page)
2. Verify no devices reference it
3. Check that no macros or triggers depend on subsystem-level operations

Deleting a subsystem does not automatically delete its zones or devices - you may need to reassign them first.

Tips

• Organization: Use subsystems to logically group related zones (e.g., all lighting zones in the lighting subsystem)
• Naming: Choose clear, descriptive names that match your building's function
• Device Assignment: Assign a parent device when the subsystem maps to a specific hardware controller
• Enable/Disable: Disable subsystems during commissioning or troubleshooting without deleting configuration
• Sort Order: The sort index affects the display order in user interfaces and mobile apps