Operation Guide
Overview
All factory default settings on the SM5000 can be updated post-deployment through the device's built-in web interface. This chapter walks through each page the operator will encounter, shows exactly what is on screen, documents the corresponding LCD state where relevant, and explains how to update each setting.
1Accessing the Web Interface
Open a web browser and navigate to the device's IP address (e.g. http://10.248.116.199). The device responds with a login page.
admin Password: admin123 - identical across all units. Change immediately after first login.- Open a web browser on a device connected to the same network as the SM5000.
- Enter the device's IP address in the address bar (e.g.
http://10.248.116.199). - Enter the username and password then click Login.
- On success the browser redirects to the main page.
2Main Page
After logging in the operator arrives at the main page - the central hub of the SM5000 web interface. All device status and every configurable setting are on a single scrollable page divided into five sections.
The System Status panel is read-only and auto-refreshes every 60 seconds. It provides a real-time snapshot of device health - firmware version, IP address, uptime, free memory, and current MQTT and Modbus connection states.
System Status
| Device | HAY.05.22K |
| Firmware Version | 1.0.0 |
| IP Address | 10.248.116.199 (Static) |
| Uptime | 4110 seconds |
| Free Memory | 146140 bytes |
| OTA Status | ✅ Ready |
| MQTT | 🔴 Disconnected |
| Broker | 10.248.117.190:1883 |
| Modbus TCP | ✅ Port 502 |
| Slave ID | 1 |
Current temperature and humidity from Sensor Front and Sensor Rear. The Calibration row shows whether a reference sensor is connected. Per-sensor offsets can be entered and saved directly.
Sensor Readings & Network Configuration
Current Readings
| Sensor | Temperature (°C) | Humidity (%RH) |
|---|---|---|
| Sensor Front | 0.0 | 0.0 |
| Sensor Rear | 0.0 | 0.0 |
| Calibration | ❌ Not connected |
Auto-refresh in 30 seconds
Calibration Information
| Parameter | Sensor Front | Sensor Rear |
|---|---|---|
| Temp Offset (°C) | 0.0 | 0.0 |
| Humidity Offset (%RH) | 0.0 | 0.0 |
- In the Calibration Information table, enter the offset value for Sensor Front or Sensor Rear.
- Click Save Offsets. A browser popup confirms: “✅ Calibration saved!” - no reboot required.
- To remove all offsets, click Reset to Zero.
Switch between Static IP and DHCP modes and set all network parameters. Each unit must be assigned a unique IP address here. Saving reboots the device to apply the new settings.
Network Configuration
① Before Update
② Rebooting
③ After Update
- Scroll to Network Configuration on the main page.
- Select Static IP or DHCP.
- If Static IP: enter the IP Address, Subnet, Gateway, and DNS.
- Click Save & Reboot. The device displays a confirmation page then reboots within 10 seconds.
- The browser redirects to the new IP address automatically.
Settings Saved - Rebooting...
Device will restart in 10 seconds with new network settings.
You will be redirected automatically.
Broker connection and the 7-level topic hierarchy. The device name is also set here. The device name and hierarchy must be verified or updated by the commissioner during deployment. The topic preview updates live and prevents saving if the total exceeds 50 characters.
MQTT Settings - Connection
MQTT Topic Hierarchy
AU/NSW/HAY/BLD1/05/05/HAY.05.22K① Before Update
② Rebooting
③ After Update
- Check or uncheck Enable MQTT as required.
- Enter the broker IP address - this must match the SyncFM host IP.
- Update the port if it differs from the default (1883).
- Enter username and password only if broker authentication is required.
- Select the correct Country and City from the dropdowns.
- Enter Datacentre, Building, Floor, and Datahall as agreed during pre-shipment consultation.
- Enter the unique Device Name for this unit (e.g.
HAY.05.22K). - Verify the Topic Preview is correct and does not exceed 50 characters.
- Click Save MQTT Settings. The device reboots to apply changes.
Enable or disable the Modbus TCP server. When enabled the device exposes sensor data on port 502 via 9 holding registers accessible by any Modbus-compatible BMS or SCADA system.
Modbus Settings
- Scroll to Modbus Settings at the bottom of the main page.
- Check Enable Modbus TCP Server to enable, or uncheck to disable.
- Click Save Modbus Settings. The device reboots and redirects back to the main page - there is no separate confirmation screen.
3Time Page
Accessible via the ⏱ Time link in the navigation bar. Allows viewing the current synchronisation status, selecting the time source, configuring the NTP server, and setting a fallback default time.
The Current Time Status table shows the device's real-time sync state. There are four possible states.
| State | Logging | Active Source | Notes |
|---|---|---|---|
| AWAITING_SYNC | ❌ No (waiting) | ⏳ Waiting for sync | Booted, waiting up to 5 min for Fleet Manager. |
| UNSYNCED_NEVER | ✅ Yes (Default Time) | ⚠ Using Default Time | 5-min timeout, no sync received. Timestamps may be inaccurate. |
| UNSYNCED_LOST | ✅ Yes (Internal Clock) | ⚠ Using Internal Clock | Was synced, then lost Fleet Manager. Minor drift expected. |
| SYNCED | ✅ Yes | 📡 Fleet Manager / 🌐 NTP | Time updates received every minute. Logging enabled. |
Switch between Fleet Manager, NTP, and Disabled modes. If NTP is selected, the NTP server address can be updated here. Clicking Apply reboots the device.
⏱ Time Source Configuration
Synchronises with a network time server. Requires network access.
Receives time broadcasts from SyncFM via MQTT. No internet required.
- Navigate to the Time page using the ⏱ Time link.
- Select NTP, Fleet Manager, or Disabled.
- If NTP is selected, update the NTP Server address if required.
- Click Apply Time Source. The device reboots to apply the change.
The Default Time is a fallback timestamp the device uses when it boots and no time source is available within the 5-minute timeout. Setting this to a recent date ensures data log timestamps are in the correct date range even if SyncFM is temporarily unreachable at boot.
🕐 Default Time (Fallback)
Used when the device boots without any time synchronization available. The device waits up to 5 minutes for a sync source before using this default.
| Current Default: | 2025-02-15 07:00:00 |
| Unix Timestamp: | 1739566800 |
Set New Default Time
- Navigate to the Time page and scroll to Default Time (Fallback).
- Enter the desired Date and Time.
- Select the correct Timezone from the dropdown.
- Verify the Preview shows the expected Unix timestamp and UTC time.
- Click Save Default Time & Restart. The device reboots and stores the value in NVS.
4Data Logger
Accessible via the 📖 Data Logger link in the navigation bar. Provides access to stored sensor history, data export tools, and 24-hour trend charts.
The SM5000 logs sensor readings every minute and stores up to 10,080 data points - exactly one full week of data. When capacity is reached, the oldest entries are overwritten in a circular buffer.
Data Logger
📥 Download historical sensor data in CSV format:
Download Full CSV (4320 entries)Last 24 Hours (1440 entries)Clear All DataDateTime, Sensor1_Temp_C, Sensor1_Humidity_%, Sensor2_Temp_C, Sensor2_Humidity_%.Below the export section, the Data Logger page renders live temperature and humidity charts covering the last 24 hours of logged data.
http://<SyncFM-IP>:3000/chart.min.js). If SyncFM is unreachable when the page loads, charts will not render. All other Data Logger functionality remains available regardless.5Settings Page
Accessible via the ⚙ Settings link in the navigation bar. Provides a consolidated view of all stored configuration values, the live Modbus register map, authentication management, and the factory reset function.
A read-only snapshot of all values currently written to NVS. Allows the operator to verify the active configuration - network mode, device name, MQTT broker, auth username, and connection states - at a glance. The password field is always masked.
Stored Configuration
| Setting | Stored Value | Description |
|---|---|---|
| use_dhcp | false | Network mode |
| device_name | HAY.05.22K | Device identifier |
| auth_user | admin | Authentication username |
| auth_pass | •••••••• | Password (hidden) |
| mqtt_enabled | true | MQTT publishing enabled |
| mqtt_broker | 10.248.117.190 | MQTT broker address |
| mqtt_port | 1883 | MQTT broker port |
| ip_address | 10.248.116.199 | Static IP |
| subnet_mask | 255.255.252.0 | Subnet mask |
| gateway | 10.248.116.1 | Default gateway |
| dns_server | 10.248.116.1 | DNS server |
| Modbus TCP | Enabled | Modbus server state |
The Modbus Register Map table shows all 9 holding registers with their current live values. The Device Status decode table beneath it translates the Register 40005 bitfield into human-readable system states, helping diagnose issues without requiring a separate Modbus client tool.
| Register | Address | Description | Current Value |
|---|---|---|---|
40001 | 0 | Sensor Front Temp (×10 °C) | 232 (23.2 °C) |
40002 | 1 | Sensor Front Humidity (×10 %) | 456 (45.6 %) |
40003 | 2 | Sensor Rear Temp (×10 °C) | 235 (23.5 °C) |
40004 | 3 | Sensor Rear Humidity (×10 %) | 448 (44.8 %) |
40005 | 4 | Device Status (Bitfield) | 0x3F |
40006 | 5 | Uptime Low Word | 4110 |
40007 | 6 | Uptime High Word | 0 |
40008 | 7 | IP Bytes 1-2 | 0x0AF8 |
40009 | 8 | IP Bytes 3-4 | 0x74C7 |
Device Status Examples (Register 40005)
| Decimal | Hex | Binary | Meaning |
|---|---|---|---|
| 63 | 0x3F | 00111111 | All systems operational |
| 59 | 0x3B | 00111011 | MQTT disconnected, everything else OK |
| 47 | 0x2F | 00101111 | System memory low (<50KB free) |
| 61 | 0x3D | 00111101 | Sensor 2 not responding |
| 32 | 0x20 | 00100000 | Only config valid, major issues |
| 39 | 0x27 | 00100111 | Network down, sensors working |
Allows updating the web interface username and password. Minimum password length is 6 characters. Saving immediately terminates the current session - the operator must log in again with the new credentials.
🔐 Authentication Management
- Navigate to the Settings page and scroll to Authentication Management.
- Enter the new username and password (minimum 6 characters).
- Confirm the password in the Confirm Password field.
- Click Update Authentication Credentials and confirm the prompt.
- The session is immediately terminated and the browser redirects to the login page after 5 seconds.
- Log in with the new credentials to resume access.
Erases all stored preferences and restores the device to the configuration embedded in the currently installed firmware - including the default IP address, device name, MQTT settings, and credentials.
DANGER: Completely resets device to factory defaults. This will:
- Reset network to DHCP
- Reset device name to default
- Clear all MQTT configuration
- Reset authentication to admin/admin123
- Clear all logs and preferences
- Disable Modbus TCP
- Restart the device
- Navigate to the Settings page and scroll to the bottom.
- Check: “I understand this will erase all settings”.
- Click 🔴 FACTORY RESET DEVICE.
- Two confirmation dialogs appear in sequence - click OK on both to proceed.
- The device clears all preferences, displays the factory reset sequence on the LCD, and reboots.
① Clearing
② Restarting
③ Countdown
④ Boot (defaults)
Countdown shows 3 → 2 → 1 before rebooting. After boot the device returns to its firmware-default device name and IP address.
6Logout
Clicking the 🔒 Logout link in the navigation bar terminates the current session and redirects to the login page. The device automatically redirects after 3 seconds, or the operator can click Login Again immediately.
Your session has been terminated.
Redirecting to login page in 3 seconds...
7Device Preferences
All configuration changes made through the web interface are written to the SM5000's non-volatile storage (NVS) - a dedicated flash partition independent of the firmware partition. Every setting listed below will survive a power cycle and will not be overwritten by an OTA firmware update. Only a factory reset clears these values.
| Preference | NVS Key | Description |
|---|---|---|
| Network | ||
| IP Mode | use_dhcp | Whether DHCP or static IP is used |
| IP Address | ip | Static IP address |
| Subnet Mask | subnet | Network subnet mask |
| Gateway | gateway | Default gateway IP |
| DNS Server | dns | DNS server IP |
| Device | ||
| Device Name | device_name | Unique unit identifier used in MQTT topic and LCD display |
| MQTT | ||
| MQTT Enabled | mqtt_enabled | Whether MQTT publishing is active |
| Broker Address | mqtt_broker | SyncFM MQTT broker IP address |
| Broker Port | mqtt_port | MQTT broker TCP port |
| MQTT Username | mqtt_user | Broker authentication username |
| MQTT Password | mqtt_pass | Broker authentication password |
| Country | mqtt_country | Topic hierarchy - Country level |
| City | mqtt_city | Topic hierarchy - City level |
| Datacentre | mqtt_datacentre | Topic hierarchy - Datacentre level |
| Building | mqtt_building | Topic hierarchy - Building level |
| Floor | mqtt_floor | Topic hierarchy - Floor level |
| Datahall | mqtt_datahall | Topic hierarchy - Datahall level |
| Authentication | ||
| Username | auth_user | Web interface login username |
| Password | auth_pass | Web interface login password |
| Calibration | ||
| Sensor 1 Temp Offset | cal_temp1 | Temperature offset for Sensor Front |
| Sensor 1 Humidity Offset | cal_hum1 | Humidity offset for Sensor Front |
| Sensor 2 Temp Offset | cal_temp2 | Temperature offset for Sensor Rear |
| Sensor 2 Humidity Offset | cal_hum2 | Humidity offset for Sensor Rear |
| Time | ||
| Time Source | time_source | Preferred time source (Fleet Manager / NTP / Disabled) |
| NTP Server | ntp_server | NTP server address (if NTP mode enabled) |
| Default Fallback Time | default_time | Unix timestamp used as fallback when no sync is available at boot |
| Modbus TCP | ||
| Modbus Enabled | modbus_en | Whether the Modbus TCP server is active |
| Chart Scales | ||
| Temperature Min/Max | chart_tmin / chart_tmax | Saved Y-axis scale for the temperature trend chart |
| Humidity Min/Max | chart_hmin / chart_hmax | Saved Y-axis scale for the humidity trend chart |
