Start with what the sensor measures
Energy and sensor monitoring works best when the series describes a clear physical quantity. A power reading and an energy meter total may come from the same device, but they answer different questions. Mixing their types or units can make a chart look plausible while its interpretation is wrong.
MetriBeacon accepts measurements through its HTTPS ingest API. Sensors, scripts and integrations can send observations that you collect locally. Begin with one validated sensor and compare its reading with a reference before building alerts around it.
Distinguish power from energy
| Quantity | Typical unit | Typical series interpretation |
|---|---|---|
| Instantaneous power | W | Gauge showing the measured level |
| Accumulated energy | kWh | Counter showing a cumulative total |
| Temperature | °C | Gauge showing a measured temperature |
A reading of 500 W describes power at the observation time. A meter reading of 1234.5 kWh is a cumulative energy total. It is not a new consumption amount to add to every earlier reading. Choose the measurement type and unit according to what your device actually reports.
Calculate changes from a continuous counter
If an energy total rises from 1234.0 to 1234.5 kWh within one continuous counter period, the observed increase is 0.5 kWh. Adding both readings would not measure energy used. Keep the cumulative readings intact and use the suitable change or rate presentation when examining consumption.
That difference does not describe every fluctuation in power between the two observations. It also depends on the meter's reporting behaviour. Read timing, measurement precision and coverage alongside the result rather than inferring details the source never recorded.
Connect an existing collection path
- Identify the sensor quantity, unit and whether it is a level or cumulative total.
- Create a monitor and an appropriately typed measurement series.
- Configure your local integration to send readings through the HTTPS API.
- Use a scoped key and keep it out of public URLs and examples.
- Compare the first observations with the device's own readings.
- Add freshness and threshold rules only after the data is trustworthy.
The sensor monitoring guide covers sources such as Home Assistant, MQTT and ESP32. MQTT data needs your own broker and a local bridge that forwards observations to HTTPS; do not assume a device becomes connected simply by entering an MQTT topic in MetriBeacon.
Treat resets as a new counter period
A meter replacement, device reset or integration change can reset a cumulative total. That is different from negative energy use. Preserve the documented counter and reset semantics in your collector instead of silently subtracting across unrelated counter periods.
Investigate a sudden drop before interpreting it as a physical event. Check the device, integration, unit and timestamp. A changed unit or collector error can resemble a reset. Use the HTTPS API documentation when implementing the reporting format.
Keep unavailable readings unavailable
If a sensor cannot provide a value, do not send zero to make its chart continuous. Zero power can be a valid reading; a disconnected sensor is missing evidence. These states need different treatment.
A missing-value rule can notify you when a series has not updated within its expected interval. A heartbeat can show that its shared transmitter remains connected while the sensor itself is silent. Choose both expectations according to the normal reporting rhythm and test them with a safe source.
Read history before drawing conclusions
Choose a consistent period and inspect the chart's resolution and coverage. Aggregation may smooth brief peaks, and an incomplete period should not be compared casually with a fully observed one. Use the history documentation to understand the available views and exports.
A dashboard is useful for trends, but the measurements alone do not establish a billing amount or a savings claim. Tariffs, meter scope and the completeness of your data belong in any separate cost calculation.
Frequently asked questions
Should I send watts or kilowatt-hours?
Send the quantity your source actually measures, with its correct unit. If it reports both power and accumulated energy, use separate series with suitable types.
Can I sum cumulative meter readings?
That would count the same accumulated energy repeatedly. Inspect differences within a continuous counter period instead.
Can MetriBeacon connect directly to every sensor?
No universal device connection is implied. Use a supported local collection path or implement an HTTPS integration, then verify its observations.
Start with a trustworthy measurement
Create a free account, connect one sensor and check its type, unit and timestamps. For a public endpoint associated with your integration, the Website/API template below adds an availability check. Sensor reporting itself uses your own collection path.
