Introduction to the SIoT V1 Web Interface

1. Login Interface

The login interface of SIoT V1 is relatively straightforward, consisting primarily of three main components: the Username and Password input fields, and the Login button.

• Username Input Field: Enter your login username, which defaults to siot.
• Password Input Field: Enter your login password, which defaults to dfrobot.
• Login Button: Submit credentials to authenticate and enter the administration console.

2. Project List

After logging in, you will typically see the Project List first. This page serves as the primary entry point for SIoT data management, used to view existing projects on the platform and navigate to their corresponding device levels.

Visually, the Project List page consists of the following functional areas:

• Top Navigation Bar: Switch between different pages such as "Project List", "Device List", and "Send Message".
• Search Area: Search for projects by Project ID and set the number of records displayed per page.
• Data Table Area: Displays current project records stored in the broker.
• Action Area: Perform operations on projects, such as viewing, adding notes, or deleting.

Common columns in the data table include:

• Project ID: The identifier or name of the current project.
• Remarks: Supplementary notes explaining the project's purpose.
• Action: Provides entries to navigate to child pages or manage the project (View Device List, Add Remarks, Delete).

Suggestions for Project Organization:

• Divide projects by class/grade.
• Divide projects by experimental theme.
• Divide projects by creative design system.

For beginners, think of this page as the "Main Directory Page". Finding the project first, then selecting the device, and finally inspecting messages provides a clear and logical workflow.

3. Device List

The Device List page organizes Topics that have logged messages into a readable device view, sorted in descending order by update timestamp for quick access to recently debugged devices.

In the "Action" column, standard features include: View Messages, Clear Messages, Delete Device, and Add Remarks.

[!CAUTION]
Clearing messages and deleting devices are irreversible operations. Please proceed with caution.

SIoT V1 typically adopts a "Project/Device" Topic hierarchy (e.g., siot/temp, siot/led), forming the following tree structure:

Project (siot)
 ├── Device A (temp)
 ├── Device B (light)
 └── Device C (led)

3.1 View Messages (Data Analysis and Export)

"View Messages" is one of the most frequently used pages, as it instantly turns abstract MQTT packets into visual data.

Detailed Breakdown of Interface Features:

1. Message Publishing Area: Allows sending test messages directly to the current Topic.
   

2. Time Filtering Area: Specify start and end dates/times to query log messages.
   

3. Record Count Area: Set the maximum number of message entries displayed per page.
   

4. Export Query Results: Export filtered query data directly as an .xls spreadsheet for scientific experiment logging.
   

5. Hide/Show Line Chart Area: Visualizes numerical trend changes over time in a line chart, equipped with zoom, reset, refresh, and download image controls.

1. Auto-Refresh Messages: Check this box to automatically refresh and append incoming data in real time.
   

2. Data Table Area: Displays exact Topic paths, message payloads, and arrival timestamps.
   

3.2 Clear Messages

Click this option to erase all existing historical message logs recorded for this device.

3.3 Delete Device

Permanently delete the selected device channel along with all its historical records.

3.4 Add Remarks

Add or update explanatory notes and descriptions for the device.

4. Sending Control Commands and the -> Instruction-Only Prefix Rule

The "Send Message" page provides one of the most convenient remote control debugging utilities.

Common test control commands include ON and OFF:

[!IMPORTANT]
-> Instruction-Only Prefix Rule:
If you prepend the prefix -> to the message payload (for example, sending ->off), the payload will be treated as a "pure command message". Such messages will not be stored in the database, making them ideal for high-frequency control scenarios where historical database logging is unnecessary.