A LoRaWAN smart plug can do more than switch a connected electrical device on or off. It can also report energy and power measurements and provide indicators of mains quality. For automation engineers and operations teams, that combination offers a way to monitor and control a plug-in load through a LoRaWAN network, while making installation and reporting choices that suit the application.
What a LoRaWAN smart plug does
The SmartPlug is a LoRaWAN Class C device powered from the mains and fitted with an internal antenna. It is placed between a wall socket and the electrical device to be controlled. A relay switches power to that device, while the SmartPlug measures its electrical consumption and evaluates aspects of the supply it is connected to.
The device implements On/Off, Simple Metering-Like and Power Quality application clusters, alongside Basic, Configuration and LoRaWAN clusters. In practical terms, those functions let a system exchange relay commands and reports, configure measurement reporting, and receive metering and mains-quality data. Application frames are sent on port 125; suitable codecs are needed to decode frame payloads.
Installation and radio considerations
Installation is straightforward: plug the SmartPlug into a wall socket, then connect the target electrical device to the SmartPlug. Its housing is intended for use inside or outside a building, but it must be protected from vertical water spray and direct sunlight.
Radio placement still matters. Limit obstacles that could attenuate the radio signal, and position the device as high as practical. These considerations apply even though the SmartPlug is powered from the socket: a usable mains connection does not by itself ensure reliable LoRaWAN communication.
When plugged in, the device starts automatically. Its LED blinks green while network association is in progress. A press of the user button changes the relay state. After a reboot, the SmartPlug retains its previous relay state, an important detail when considering how connected equipment behaves after an interruption.
Energy metering and power quality
For the connected load, the SmartPlug reports active energy in watt-hours (Wh), reactive energy in volt-ampere-hours (VARh), active power in watts (W), and reactive power in volt-amperes (VAR). It also reports an accumulation duration in number of samples. The polarity of power measurements carries meaning: active power can indicate consumption or production, while reactive power distinguishes inductive from capacitive load.
The Power Quality cluster provides indicators for the electrical mains. These include current, minimum and maximum frequency; current, minimum and maximum RMS voltage; and counters for overvoltage events, voltage sags and device reboots. Overvoltage and sag counters depend on configured thresholds. A sag is counted when voltage falls below the configured sag threshold for at least the configured number of half-cycles.
These values can help teams observe supply conditions alongside load behavior. They are reported measurements and counters; interpreting them requires understanding the configured thresholds and the units or encoding used by the application codec.
Configure reporting for the application
The default configuration reports the Simple Metering Current Metering attribute hourly. Changes to reporting must respect applicable radio duty-cycle limits. The documentation gives the EU’s most restrictive example as 0.1%, corresponding to approximately one frame per hour at spreading factor 12. The appropriate reporting setup therefore needs to balance the application’s monitoring needs with the permitted airtime.
Standard reports and batch reports
Standard reporting can be configured around a measurement change, a minimum interval between reports, and a maximum interval. For example, a relay-state report can be requested for every state change, with a periodic report as a backstop. A power-quality configuration can set a minimum delay, a maximum reporting interval and a voltage change that triggers a report, while leaving other measurement changes unable to trigger one.
Batch reporting records selected measurements and sends grouped data according to configured intervals and changes. The documented example batches active energy, active power and peak voltage using separate labels. Each measurement has its own delta and resolution settings, while the batch uses minimum and maximum reporting intervals. This approach can organize multiple readings, but its configuration and decoding are more involved than a simple status report.
In either mode, confirm the endpoint, cluster and attribute used for each measurement. The SmartPlug has one controlled output and one measurement input, both associated with endpoint 0 in the documented examples. A mismatch between the configured attribute and the intended measurement can prevent the receiving application from interpreting reports as expected.
Network recovery and reset behavior
Reassociation and factory reset are different procedures. Reassociation can be triggered by three short user-button presses or a LoRaWAN cluster command. It can also be requested under configured conditions, such as a period without a downlink, a reached frame count or an acknowledgement failure. Reassociation retains the AppEUI, DevAddr and application configuration, but LoRaWAN settings such as channel and data rate are lost.
A factory reset, triggered by two short presses followed by a long press of about seven seconds, deletes application settings such as configured batches and reports. The AppEUI and DevAddr are retained, but LoRaWAN and application configurations are lost. Understanding this distinction helps technicians choose the right recovery action and anticipate what must be restored afterward.
Practical implications for automation teams
A LoRaWAN smart plug brings switching, energy metering and mains-quality indicators together at a plug-in load. To use it effectively, plan the radio location, define which measurements matter, configure reporting intervals and thresholds deliberately, and verify that the application can decode the resulting frames. Also account for relay-state retention after reboot, duty-cycle constraints, and the different effects of reassociation and factory reset. These steps help make remote load control and monitoring more predictable within a broader industrial automation system.
Access Official Technical PDF