UNIHH-IOTUNIHH-IOT
Home
Guide
Manual
  • 简体中文
  • English
GitHub
Home
Guide
Manual
  • 简体中文
  • English
GitHub
  • Manual

    • Operation Manual
    • Dashboard
    • Driver Management
    • Device Management
    • Thing Models
    • Data Monitor
    • Rule Engine
    • Alarm Center
    • Log Audit
    • System Management

Operation Manual

This manual covers every functional page of the UNIHH-IOT platform. It is written for field engineers, system integrators and operations staff.

Signing In

Open the frontend URL (http://localhost:3000 in local development) and sign in. The default super-admin account is admin / unihhiot.

Login

Credentials are stored as a token in the browser; when it expires you are redirected back to the login page. Forgotten passwords are reset by an administrator under System → User Management.

Note

Change the default passwords immediately after production deployment and issue individual accounts with proper roles to every operator.

Layout

After signing in you land on the dashboard. The left sidebar carries the navigation menu, filtered by your role's permissions; the top bar holds the current user and the sign-out action.

Page Index

PageDescription
DashboardGlobal status of devices, drivers, throughput and alerts
Driver ManagementDriver status, parameters and heartbeat self-checks
Device ManagementDevice registry, point binding, acquisition toggle, write-back control
Thing ModelsProperty / service / event modeling
Data MonitorLive point values, quality flags and snapshots
Rule EngineThreshold conditions and linked actions
Alarm CenterEvent browsing, acknowledgment and disposition
Log AuditWrite-back command trail and login audit
System ManagementUsers, roles, menus and dictionaries

Recommended First Path

To walk the full "model → connect → acquire → alert" chain for the first time:

  1. Create a thing model defining the properties, services and events of one device type;
  2. Check the driver for that protocol is running and online;
  3. Create a device, bind the model and driver, configure connection parameters and point mapping;
  4. Watch live data to confirm acquisition and quality;
  5. Configure a rule on a key point;
  6. Handle the alarm — simulate an out-of-range value and verify the chain.
Edit this page on GitHub
Last Updated: 11/13/26, 3:34 AM
Contributors: sunqi
Next
Dashboard