Energy consumption measurement
Attention
Function under validation.
Products fitted with an energy meter measure the electrical consumption of their outputs, and publish that measurement over the mesh network.
Two quantities follow: the energy index, a timestamped running total of the energy consumed since the last reset, and the instantaneous power, current and voltage readings.
Measurement covers the product’s total consumption: a single meter covers all outputs together, whatever control feature is assigned to them.
📋 Requirement: The product measures its total consumption through a single energy meter.
Energy index publication
The product periodically publishes its timestamped energy index over the mesh network. The Mobile App and the IoTHub build the consumption curve from it.
The index is a running total in kWh: every publication carries the whole value measured since the last reset, which makes the curves superimposable with those of a smart meter.
Publication is set through the energy-publish-control feature property, which also carries the reset of the running total. It is disabled in factory configuration, and the user enables it from the Mobile App.
📋 Requirement: The published energy value is the running total consumed since the last reset, expressed in kWh.
📋 Requirement: The timestamp carried by a publication matches the real time of the measurement.
📋 Requirement: The index is published every 15 minutes.
📋 Requirement: Publications fall on quarter hours, at minutes 0, 15, 30 and 45.
📋 Requirement: In factory configuration, periodic publication of the index is disabled.
📋 Requirement: The Mobile App offers the publication switch and the reset of the running total in the product page.
Periodic power publication
The product also publishes its power periodically, in addition to the on-demand reading.
Publication is set through the power-publish-control feature property, which carries both its enabling and its period. It is aimed at integrators who ask for it: it is set through the Backend or through MQTT, and the Mobile App does not expose it.