Chapter 2

Operation Guide

Configuring the device via the web interface

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.

Must Configure on Each Unit
Pre-Configured - Verify Only
  • MQTT Settings & Hierarchy - §2.4
  • Modbus TCP - §2.5
  • Sensor Calibration Offsets - §2.2.2

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.

http://10.248.116.199
🔒 SM5000 Login
admin
••••••••
Login
Default Credentials Username: admin Password: admin123 - identical across all units. Change immediately after first login.
Session Behaviour One active session at a time. Logging in from a new browser or IP terminates any existing session.
2.1.1 - How to Log In
  1. Open a web browser on a device connected to the same network as the SM5000.
  2. Enter the device's IP address in the address bar (e.g. http://10.248.116.199).
  3. Enter the username and password then click Login.
  4. 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.

1. System Status - Live overview of device health, firmware, network, MQTT, and Modbus state.
2. Sensor Readings & Calibration - Current readings from both sensors, calibration sensor status, and offset controls.
3. Network Configuration - IP address, subnet, gateway, and DNS settings.
4. MQTT Settings - Broker connection details and the 7-level topic hierarchy.
5. Modbus TCP Settings - Enable or disable the Modbus TCP server.
2.2.1 - System Status

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.

http://10.248.116.199
🏠 Main|⏱ Time|📖 Data Logger|⚙ Settings|🔒 Logout

System Status

DeviceHAY.05.22K
Firmware Version1.0.0
IP Address10.248.116.199 (Static)
Uptime4110 seconds
Free Memory146140 bytes
OTA Status✅ Ready
MQTT🔴 Disconnected
Broker10.248.117.190:1883
Modbus TCP✅ Port 502
Slave ID1
LCD Display - Normal Operation
HAY.05.22K10.248.116.199
2.2.2 - Sensor Readings & Calibration

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.

http://10.248.116.199

Sensor Readings & Network Configuration

Current Readings

SensorTemperature (°C)Humidity (%RH)
Sensor Front0.00.0
Sensor Rear0.00.0
Calibration❌ Not connected

Auto-refresh in 30 seconds

Calibration Information

ParameterSensor FrontSensor Rear
Temp Offset (°C)0.00.0
Humidity Offset (%RH)0.00.0
💾 Save Offsets🔄 Reset to Zero
2.2.2.1 - How to Update Calibration Offsets
  1. In the Calibration Information table, enter the offset value for Sensor Front or Sensor Rear.
  2. Click Save Offsets. A browser popup confirms: “✅ Calibration saved!” - no reboot required.
  3. To remove all offsets, click Reset to Zero.
Calibration offsets apply to all outputs simultaneously - MQTT telemetry, Modbus TCP registers, and the web interface display.
2.2.3 - Network Configuration

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.

http://10.248.116.199

Network Configuration

Current Mode:Static IP
New Mode:○ DHCP● Static IP
IP Address:10.248.116.199
Subnet:255.255.252.0
Gateway:10.248.116.1
DNS:10.248.116.1
Save & Reboot
LCD Display - IP Change Sequence (10.248.116.199 → 10.248.116.200)

① Before Update

HAY.05.22K10.248.116.199

② Rebooting

System StartingPlease wait...

③ After Update

HAY.05.22K10.248.116.200
2.2.3.1 - How to Update Network Settings
  1. Scroll to Network Configuration on the main page.
  2. Select Static IP or DHCP.
  3. If Static IP: enter the IP Address, Subnet, Gateway, and DNS.
  4. Click Save & Reboot. The device displays a confirmation page then reboots within 10 seconds.
  5. The browser redirects to the new IP address automatically.
Preference Persistence: Network settings are written to NVS immediately on save and will survive a power cycle or OTA firmware update. See Device Preferences.
What the device shows after saving:

Settings Saved - Rebooting...

Device will restart in 10 seconds with new network settings.

You will be redirected automatically.

2.2.4 - MQTT Settings

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.

http://10.248.116.199

MQTT Settings - Connection

Enable MQTTEnabled
Broker10.248.117.190
Port1883
Username(blank)
Password••••••••

MQTT Topic Hierarchy

Topic Preview:
AU/NSW/HAY/BLD1/05/05/HAY.05.22K
Length: 30 characters (Limit: 50)
CountryAU - Australia
CityNSW - New South Wales
DatacentreHAY
BuildingBLD1
Floor05
Datahall05
Device NameHAY.05.22K
Save MQTT Settings
LCD Display - Device Name Change Sequence (Default → HAY.05.22K)

① Before Update

SM500010.248.116.199

② Rebooting

System StartingPlease wait...

③ After Update

HAY.05.22K10.248.116.199
2.2.4.1 - How to Update MQTT Broker Settings
  1. Check or uncheck Enable MQTT as required.
  2. Enter the broker IP address - this must match the SyncFM host IP.
  3. Update the port if it differs from the default (1883).
  4. Enter username and password only if broker authentication is required.
2.2.4.2 - How to Update the Topic Hierarchy & Device Name
  1. Select the correct Country and City from the dropdowns.
  2. Enter Datacentre, Building, Floor, and Datahall as agreed during pre-shipment consultation.
  3. Enter the unique Device Name for this unit (e.g. HAY.05.22K).
  4. Verify the Topic Preview is correct and does not exceed 50 characters.
  5. Click Save MQTT Settings. The device reboots to apply changes.
Topic Length Limit: If the total topic exceeds 50 characters the Save button turns red and is disabled. Shorten one or more hierarchy fields to proceed.
Preference Persistence: MQTT settings and device name are written to NVS immediately on save and will survive a power cycle or OTA firmware update.
2.2.5 - Modbus TCP Settings

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.

http://10.248.116.199

Modbus Settings

Enable Modbus TCPEnable Modbus TCP Server
Save Modbus Settings
2.2.5.1 - How to Enable or Disable Modbus TCP
  1. Scroll to Modbus Settings at the bottom of the main page.
  2. Check Enable Modbus TCP Server to enable, or uncheck to disable.
  3. 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.

3.1 - Current Time Status

The Current Time Status table shows the device's real-time sync state. There are four possible states.

StateLoggingActive SourceNotes
AWAITING_SYNC❌ No (waiting)⏳ Waiting for syncBooted, waiting up to 5 min for Fleet Manager.
UNSYNCED_NEVER✅ Yes (Default Time)⚠ Using Default Time5-min timeout, no sync received. Timestamps may be inaccurate.
UNSYNCED_LOST✅ Yes (Internal Clock)⚠ Using Internal ClockWas synced, then lost Fleet Manager. Minor drift expected.
SYNCED✅ Yes📡 Fleet Manager / 🌐 NTPTime updates received every minute. Logging enabled.
NTP Mode: When NTP is the time source, the Active Source shows 🌐 NTP (Connected) when synced, with status: “✅ NTP Synchronized - Syncs hourly.”
3.2 - Time Source Configuration

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.

http://10.248.116.199/time

⏱ Time Source Configuration

🌐 NTPNetwork Time Protocol

Synchronises with a network time server. Requires network access.

NTP Serverpool.ntp.org
📡 Fleet ManagerDefault - Recommended (selected)

Receives time broadcasts from SyncFM via MQTT. No internet required.

⚠ DisabledTesting / troubleshooting only
Apply Time SourceRefresh Status
3.2.1 - How to Update the Time Source
  1. Navigate to the Time page using the ⏱ Time link.
  2. Select NTP, Fleet Manager, or Disabled.
  3. If NTP is selected, update the NTP Server address if required.
  4. Click Apply Time Source. The device reboots to apply the change.
Disabled Mode: Intended for testing and troubleshooting only. Data logging continues but timestamps will drift over time.
3.3 - Default Time (Fallback)

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.

http://10.248.116.199/time

🕐 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

Date:2025-04-08
Time:07:00
Timezone:UTC+10:00 AEST (Sydney/Melbourne)
Preview:1744077600 / 2025-04-08T07:00:00Z
Save Default Time & Restart
3.3.1 - How to Set the Default Fallback Time
  1. Navigate to the Time page and scroll to Default Time (Fallback).
  2. Enter the desired Date and Time.
  3. Select the correct Timezone from the dropdown.
  4. Verify the Preview shows the expected Unix timestamp and UTC time.
  5. Click Save Default Time & Restart. The device reboots and stores the value in NVS.
Best Practice: Set the default time to the expected deployment date and approximate time of day. This ensures that if SyncFM is temporarily unreachable at boot, data log timestamps will fall in the correct date range rather than reverting to the factory timestamp.

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.

4.1 - Data Export

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.

http://10.248.116.199/datalogger

Data Logger

4320
Total Entries
43.0%
Storage Used
10080
Max Capacity
14:23
Last Entry

📥 Download historical sensor data in CSV format:

Download Full CSV (4320 entries)Last 24 Hours (1440 entries)Clear All Data
CSV Format: Columns: DateTime, Sensor1_Temp_C, Sensor1_Humidity_%, Sensor2_Temp_C, Sensor2_Humidity_%.
Clear All Data: Irreversible. A confirmation prompt is shown before data is deleted.
4.2 - 24-Hour Trends

Below the export section, the Data Logger page renders live temperature and humidity charts covering the last 24 hours of logged data.

SyncFM Required for Charts: Chart.js is loaded at runtime from the SyncFM host (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.
Chart Scale Controls: The Y-axis range for both charts can be customised using the min/max fields. Clicking Update & Save applies the new scale and persists the values to NVS - they are restored on the next page load.

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.

5.1 - Stored Configuration

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.

http://10.248.116.199/settings

Stored Configuration

SettingStored ValueDescription
use_dhcpfalseNetwork mode
device_nameHAY.05.22KDevice identifier
auth_useradminAuthentication username
auth_pass••••••••Password (hidden)
mqtt_enabledtrueMQTT publishing enabled
mqtt_broker10.248.117.190MQTT broker address
mqtt_port1883MQTT broker port
ip_address10.248.116.199Static IP
subnet_mask255.255.252.0Subnet mask
gateway10.248.116.1Default gateway
dns_server10.248.116.1DNS server
Modbus TCPEnabledModbus server state
5.2 - Modbus Register Map & Device Status

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.

RegisterAddressDescriptionCurrent Value
400010Sensor Front Temp (×10 °C)232 (23.2 °C)
400021Sensor Front Humidity (×10 %)456 (45.6 %)
400032Sensor Rear Temp (×10 °C)235 (23.5 °C)
400043Sensor Rear Humidity (×10 %)448 (44.8 %)
400054Device Status (Bitfield)0x3F
400065Uptime Low Word4110
400076Uptime High Word0
400087IP Bytes 1-20x0AF8
400098IP Bytes 3-40x74C7

Device Status Examples (Register 40005)

DecimalHexBinaryMeaning
630x3F00111111All systems operational
590x3B00111011MQTT disconnected, everything else OK
470x2F00101111System memory low (<50KB free)
610x3D00111101Sensor 2 not responding
320x2000100000Only config valid, major issues
390x2700100111Network down, sensors working
5.3 - Authentication Management

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.

http://10.248.116.199/settings

🔐 Authentication Management

Changing credentials will terminate your current session.
Current Username:admin
New Username:admin
New Password:••••••••
Confirm Password:••••••••
Update Authentication Credentials
5.3.1 - How to Update Authentication Credentials
  1. Navigate to the Settings page and scroll to Authentication Management.
  2. Enter the new username and password (minimum 6 characters).
  3. Confirm the password in the Confirm Password field.
  4. Click Update Authentication Credentials and confirm the prompt.
  5. The session is immediately terminated and the browser redirects to the login page after 5 seconds.
  6. Log in with the new credentials to resume access.
5.4 - Factory Reset

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.

Important - OTA Firmware & Factory Defaults: After a firmware update via SyncFM OTA, the factory defaults baked into the new firmware may differ from the originally shipped version. Performing a factory reset after an OTA update will restore the device to the defaults of the currently installed firmware, not the originally shipped firmware. All NVS preferences are unaffected by an OTA update - only a factory reset clears them.
http://10.248.116.199/settings
⚠ Factory Reset

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
Acknowledge:I understand this will erase all settings
🔴 FACTORY RESET DEVICE
5.4.1 - How to Perform a Factory Reset
  1. Navigate to the Settings page and scroll to the bottom.
  2. Check: “I understand this will erase all settings”.
  3. Click 🔴 FACTORY RESET DEVICE.
  4. Two confirmation dialogs appear in sequence - click OK on both to proceed.
  5. The device clears all preferences, displays the factory reset sequence on the LCD, and reboots.
LCD Display - Factory Reset Sequence

① Clearing

Factory ResetClearing settings.

② Restarting

Factory ResetRestarting...

③ Countdown

Restarting3...

④ Boot (defaults)

System StartingPlease wait...

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.

🔒 Logged Out Successfully

Your session has been terminated.

Redirecting to login page in 3 seconds...

Login Again
Session Termination: Logging out clears the session token on the device. Any other browser or tab using the same session will also lose access immediately.

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.

OTA & Preferences: When a new firmware is deployed via SyncFM OTA, the firmware binary replaces the code running on the device. The NVS preferences partition is left entirely untouched. The device boots with the new firmware but resumes with the same network address, device name, MQTT hierarchy, credentials, and calibration values it had before the update.
PreferenceNVS KeyDescription
Network
IP Modeuse_dhcpWhether DHCP or static IP is used
IP AddressipStatic IP address
Subnet MasksubnetNetwork subnet mask
GatewaygatewayDefault gateway IP
DNS ServerdnsDNS server IP
Device
Device Namedevice_nameUnique unit identifier used in MQTT topic and LCD display
MQTT
MQTT Enabledmqtt_enabledWhether MQTT publishing is active
Broker Addressmqtt_brokerSyncFM MQTT broker IP address
Broker Portmqtt_portMQTT broker TCP port
MQTT Usernamemqtt_userBroker authentication username
MQTT Passwordmqtt_passBroker authentication password
Countrymqtt_countryTopic hierarchy - Country level
Citymqtt_cityTopic hierarchy - City level
Datacentremqtt_datacentreTopic hierarchy - Datacentre level
Buildingmqtt_buildingTopic hierarchy - Building level
Floormqtt_floorTopic hierarchy - Floor level
Datahallmqtt_datahallTopic hierarchy - Datahall level
Authentication
Usernameauth_userWeb interface login username
Passwordauth_passWeb interface login password
Calibration
Sensor 1 Temp Offsetcal_temp1Temperature offset for Sensor Front
Sensor 1 Humidity Offsetcal_hum1Humidity offset for Sensor Front
Sensor 2 Temp Offsetcal_temp2Temperature offset for Sensor Rear
Sensor 2 Humidity Offsetcal_hum2Humidity offset for Sensor Rear
Time
Time Sourcetime_sourcePreferred time source (Fleet Manager / NTP / Disabled)
NTP Serverntp_serverNTP server address (if NTP mode enabled)
Default Fallback Timedefault_timeUnix timestamp used as fallback when no sync is available at boot
Modbus TCP
Modbus Enabledmodbus_enWhether the Modbus TCP server is active
Chart Scales
Temperature Min/Maxchart_tmin / chart_tmaxSaved Y-axis scale for the temperature trend chart
Humidity Min/Maxchart_hmin / chart_hmaxSaved Y-axis scale for the humidity trend chart