Lighting Strategy

1. Overview

The lighting strategy module uses intelligent automatic control strategies to achieve fine control of the lamp. Support is based on the following trigger conditions:

• Sensors: can pass different sensors and status parameters. Commonly used are brightness, illuminance, traffic sensors, etc.
• Time triggering: Timing control down to the minute level
• Latitude and longitude trigger: Dynamically adjusts based on sunrise/sunset times

It is suitable for scenarios such as road lighting, park landscape lighting, and building intelligent lighting.

2. Function Introduction

2.1 Strategy List

Lists all lighting strategies added by the user in the current domain and subdomains.

2.1.1 Operation Steps

1. Log in to the system and select the Smart Strategy module in the system menu to enter.
2. In the left menu items, click Lighting Strategy to enter the strategy list.

2.1.2 Interface Description

• Pagination displays all strategies (default sorted by strategy name in ascending order)
• Quick search bar (supports strategy name fuzzy query)
• Status filter (enabled/disabled)
• List displays key information:
  • Strategy Name: Supports editing
  • Status: Current strategy status (enabled/disabled), supports filtering by status
  • Domain: Domain to which the strategy belongs
  • Associated Groups: Number of lamp groups associated with the strategy
  • Create Time: Display the creation time of the strategy, supports sorting by time
  • Update Time: Display the last update time of the strategy configuration, supports sorting by time
  • Quick Operations: Display the executable operation instructions for the current strategy
    • ：Edit the strategy name
    • ：Delete the current strategy
    • ：Enable the current strategy
    • ：Disable the current strategy

2.2 Create Strategy

2.2.1 Operation Steps

1. Log in to the system and select the Smart Strategy module in the system menu to enter.
2. In the left menu items, click Lighting Strategy to enter the strategy list.
3. Click the "Create" button in the upper left corner of the page, enter the create page.
4. Follow the page prompts to complete the strategy name and domain selection, click the "Save" button, and enter the strategy details page.

Definition

If Edge Execution is checked, it means that the strategy is executed on the edge side, and the gateway device needs to be selected for execution.

2.3 Strategy Details

This section is used to view the current strategy execution configuration and preview effects.

2.3.1 Interface Description

1. Basic Information Area
   • Strategy Name: Supports editing
   • Status: Current strategy status (enabled/disabled), supports filtering by status
   • Domain: Domain to which the strategy belongs
   • Update Time: Display the last update time of the strategy configuration, supports sorting by time
2. Variable Area: Display the related variable parameters defined in the current strategy
   • Variable Name: User-defined name for the variable, used to mark the variable
   • Variable Name: User-defined name for the variable, used to mark the variable
   • Unit: Variable value unit, such as %, lux, Celsius degrees, etc., mainly used for identification, not affecting strategy calculation
   • Type: Current variable type, currently supports two types
     • Constant: Variable value will not change after strategy definition
     • Sensor: Variable value is determined by sensor real-time status
   • Parameters: Meanings are different depending on the above variable type
     • Constant: When the variable type is constant, it means the constant parameter value
     • Sensor: When the variable type is sensor, you need to select the specific sensor and sensor status parameter
   • Default Value: Current variable default value
   • Description: Detailed description of the variable, helping users understand
3. Rule Area: List displays the execution conditions and status parameters in the current strategy
   • Trigger Conditions: Users can add multiple execution conditions, including:
     • Variable parameter status in the variable area
     • Time Parameters: Support absolute time or astronomical time based on latitude and longitude (offset adjustable) time range
     • Execution Cycle: Strategy execution cycle, default is effective for all dates, supports user-defined month, day, week execution at a certain time point
   • Instruction Parameters: Lamp execution instruction, switch or dim

2.3.2 Configuration Variables

1. Click the "Edit" button in the strategy parameter area to enter the strategy edit state.

   

2. Add constant type variables: In the variable area, select the add button, pop up the add variable interface.

   • Variable type selects constant
   • Input variable basic information: name, variable name, unit, default value
   • Constant Value: Enter the constant value or select the associated sensor device and parameter

   

3. Add sensor type variables: In the variable area, select the add button, pop up the add variable interface.

   • Variable type selects sensor
   • Input variable basic information: name, variable name, unit, default value
   • Sensor Parameters: Select the specific sensor and sensor status parameter according to the interface guide

   

2.3.3 Variable Examples

The following are some common variable examples in tunnel lighting scenarios:

Type	Variable	Name	Unit	Description
Sensor	Q	Vehicle Flow	veh/(h.ln)	Vehicle flow sensor
Sensor	L20	Outside Brightness	cd/m2	Outside brightness sensor
Sensor	DI	Switch Status	N/A	Switch sensor (switch)
Constant	Lth1	Entry Brightness	cd/m2	Tunnel entry brightness design value
Constant	LLF	Maintenance Coefficient		System maintenance coefficient, which needs to be updated periodically according to the design requirements

2.3.4 Configuration Strategy Rules

1. Configure available trigger conditions: Click the Condition Edit button in the upper right corner of the specification area, and then select the rules conditions that need to be used.

   

2. Configure trigger rules: Select the add button, add a rule, and then configure the corresponding trigger conditions based on the different types of condition parameters.

   

   

   

   

3. Configure the device status under the specified rule conditions

   

Definition

All strategy parameter changes need to be saved to take effect.

2.4 Device

This section configures the target device collection for the current strategy execution. The execution device is the lamp group.

2.5 Execution History

The execution history of the current strategy is displayed here, including the execution time, execution status, execution results, and other information.

2.6 Operation Log

The operation log of the current strategy is displayed here, including the operator, operation time, operation content, and other information.