A commercial office fit-out in Singapore's CBD typically allocates 18-24 DIN modules per floor for electrical protection — circuit breakers, RCDs, surge protectors. Adding per-tenant energy metering used to mean either bulky panel-mounted meters that consumed 8-12 additional modules, or current transformer (CT) solutions that required separate enclosures and 415V wiring.

The DIN rail WiFi meter changes that equation. At 4 modules wide (72 mm), it snaps onto the same TH35 rail as the rest of the panel, measures active and reactive energy to Class 1.0 accuracy, and pushes data to a cloud dashboard via the building's existing WiFi network. No additional wiring. No separate communication enclosures. No on-site configuration laptops.

DIN Rail Mounting and Installation

The physical footprint drives the design. A standard DIN rail meter occupies 4 modules (18 mm each) and is secured by the rail's spring-loaded retaining clip. The terminal block accepts 1.5-16 mm² solid or stranded conductors, with separate voltage and current terminals clearly labeled on the housing.

Installation follows a straightforward sequence. Mount the meter on the DIN rail. Connect the line and neutral through the meter (35 mm² busbar compatible). Tighten to 2.5 N·m torque. Close the terminal cover. Power up. The meter boots in approximately 3 seconds and immediately begins accumulating energy, even before any communication is configured.

The WiFi configuration is where this product diverges from traditional DIN meters. Instead of requiring a laptop with serial cable to set a Modbus address, the meter creates a temporary access point on first boot. A technician connects with a smartphone, opens a local web page hosted by the meter, and enters the building's WiFi credentials. The meter reboots, joins the network, and begins transmitting data within 60 seconds.

For larger installations — 50+ meters per panel — our engineering team developed a batch-configuration tool. The installer uploads a CSV with meter serial numbers and desired parameters (WiFi SSID, reporting interval, cloud endpoint). The tool pushes configurations to all meters on the local network simultaneously. A 120-meter deployment across 8 floors was fully configured in 47 minutes using this approach.

The enclosure is polycarbonate with a UL 94 V-0 flame rating. Operating temperature spans -25°C to +55°C, covering most commercial and light-industrial environments. The IP rating is IP51 (dust-protected, drip-proof), suitable for indoor panel mounting. For semi-outdoor panels, an IP65 variant is available with gasket-sealed terminal covers.

WiFi Connectivity and Cloud Integration

The WiFi module is based on the ESP32-WROOM-32D, supporting 802.11 b/g/n at 2.4 GHz. (5 GHz is not supported — a deliberate choice, as many commercial buildings have legacy 2.4 GHz access points that predate the 5 GHz rollout.) The module maintains a persistent TCP connection to up to three configurable endpoints simultaneously.

Data transmission uses a configurable JSON payload over HTTP POST. The default reporting interval is 60 seconds, carrying:

- Per-phase voltage, current, active power, reactive power, power factor

- Total and tariff-segregated active/reactive energy (up to 4 tariffs)

- Meter temperature, signal strength (RSSI), uptime

- Tamper status flags (cover open, magnetic field, reverse energy flow)

Our cloud platform receives this data, stores it in a time-series database, and serves it through a RESTful API. Building management system (BMS) integrators typically poll the API at 5-minute intervals to populate their energy dashboards. The API documentation runs to 47 pages and covers authentication (OAuth 2.0), endpoint definitions, rate limits (100 requests/minute per API key), and error handling.

For deployments that cannot use cloud connectivity — government facilities, air-gapped networks, or sites with strict outbound firewall policies — the meter also supports direct Modbus TCP. Any SCADA or BMS with Modbus TCP client capability can read the meter's holding registers directly. The register map follows Sunspec Modbus (register 40000+), ensuring compatibility with solar inverter monitoring systems and other renewable energy equipment.

Real-time Energy Monitoring Features

The value proposition of WiFi connectivity is not just data collection — it is what the building operator can do with that data in real time. The meter's embedded firmware supports several monitoring features that previously required external energy management software:

Threshold alerts. The operator configures power or energy thresholds through the cloud dashboard. When a tenant's consumption exceeds the threshold, the meter (or the cloud platform, depending on configuration) sends an alert via email, webhook, or MQTT message. A property management company in Kuala Lumpur configured 800W per-workstation thresholds across 340 small-office tenants; the alert system identified 23 instances of after-hours HVAC operation within the first month, saving an estimated SGD 4,200 in monthly utility costs.

Load profiling. The meter stores 1-minute interval data in non-volatile memory for the most recent 60 days. This data is available for download through the API or can be pushed to the cloud automatically. Facility operators use load profiles to identify equipment scheduling issues, verify demand response performance, and allocate energy costs to individual cost centers.

Power quality monitoring. Voltage sag/swell events are logged with timestamp, duration, and magnitude. The meter detects sags below 90% Un and swells above 110% Un, recording up to 100 events in a circular buffer. For commercial buildings with sensitive IT equipment, this visibility helps diagnose whether voltage disturbances originate from the utility supply or from large loads within the building.

Tariff management. Four tariff registers allow time-of-use (TOU) energy allocation. The meter's internal RTC is synchronized via NTP over WiFi, maintaining ±2 seconds accuracy. TOU schedules are configured through the cloud platform and pushed to meters over-the-air. A shopping mall in Bangkok uses TOU metering to allocate daytime (08:00-22:00) consumption to the retail tenant and nighttime consumption to the common-area budget, automating an energy cost split that previously required manual meter reading and spreadsheet allocation.

Building Management System Integration

Integration with third-party BMS platforms follows one of three patterns, depending on the BMS capability:

RESTful API pull. The BMS polls our cloud API at regular intervals. This is the simplest integration and works with any BMS that can make outbound HTTPS requests. Credentials use OAuth 2.0 with 90-day token rotation.

MQTT push. The meter (or cloud platform) publishes energy data to the building's MQTT broker. This is the preferred pattern for real-time BMS applications where 60-second latency is unacceptable. MQTT topics follow a hierarchical structure: building/floor/panel/meter/phase/parameter. A BMS in Jakarta subscribes to +/+/+/+/+/power to receive real-time power readings from all meters in the facility.

Modbus TCP. For BMS platforms that cannot make outbound connections or use MQTT, the meter exposes standard Modbus registers over TCP port 502. The BMS acts as Modbus client and polls the meter at its configured polling rate. This is the most widely compatible option and works with virtually every BMS platform manufactured in the last 15 years.

Our integration team maintains pre-built connectors for 14 BMS platforms, including Siemens Desigo, Schneider Electric EcoStruxure, Johnson Controls Metasys, and Honeywell Enterprise Buildings Integrator. For BMS platforms not in this list, we provide the Modbus register map, API specification, and up to 8 hours of integration engineering support at no cost with orders exceeding 500 meters.