![Logo_quer_farbig.png]](https://docs.sentinum.de/hs-fs/hubfs/Logo_quer_farbig.png?height=40&name=Logo_quer_farbig.png){kind=logo}
1. Version History
| Version | Date | Change |
|---|---|---|
| 1.0.0 | June 2, 2025 | Initial release |
| 1.0.1 | March 25, 2026 |
|
2. Overview
The Hyperion Energy Meter (Sentinum) transmits energy data via the MIOTY protocol. This document describes the payload structure, profiles, and field definitions starting with firmware version 1.3.
Device info:
-
Type EUI:
FCA84A0000000006 - Vendor: Sentinum
- Protocol: mioty
-
Firmware:
v1.3+ (Payload only for
fw_minor_ver ≥ 3andstatus = 0)
3. Configuring Profiles
| Profile | Setting/Value |
|---|---|
| 0 | 000 |
| 1 | 001 |
| 2 | 002 |
| 3 | 003 |
| 4 | 004 |
Familiarize yourself with the display.
3.1. Step 1: mioty® DevEUI
Use the down arrow key to scroll to the section "mioty® DevEUI Settings", as shown in the screen below.
This menu displays the unique device identifier (DevEUI) of the Hyperion energy meter.
3.2. Step 2: Navigate to Mioty Payload Profile
Use the down arrow key to navigate to "Mioty Payload Profile Settings".
The number displayed at the bottom of the screen corresponds to the currently selected payload profile.
3.3. Step 3: Changing the Profile
Using an insulated screwdriver, press the button on the lower right, as shown in the image. The number will then be displayed as a 3-digit value, e.g., 001. Use the button to navigate right through the decimal places;
and use the down button to adjust the respective digit (increment it).
The profile must always be specified as a three-digit number,
for example, 001 or 004.
Even if values such as 009
can be set on the meter, this is not
a valid profile.
A 0 can be reached again by incrementing the
respective digit up to 9.
After 9, the value jumps back to
0.
Please use only the profiles
000 through 004.
In the following image, 004 has been set.
3.4. Step 4: Confirm Profile
To change the profile, use an insulated pen or screwdriver to press and hold the button on the lower right until the display and numeric keypad flash briefly.
4. Payload Structure
| Field | Size | Type | Description |
|---|---|---|---|
fw_base_id |
4 bits | uint | Firmware base identifier |
fw_major_ver |
4 bits | uint | Major firmware version |
fw_minor_ver |
4 bits | uint | Minor firmware version |
dev_sub_type |
4 bits | uint | Device subtype |
msg_counter |
8 bits | uint | Uplink counter |
status |
8 bits | uint | Device status (0 = normal) |
serial_num |
32 bits | uint | Serial number |
app_version |
32 bits | uint | Application version |
mid_version |
32 bits | uint | Middleware version |
profile |
8-bit | uint | Profile selector (0 to 4) |
5. Naming Conventions
-
Voltage:
u_lX(Phase/Line) -
Current:
i_lX(phase/total) -
Power:
p_lX_a(active power, phase/total) -
Energy:
e_t{a|1|2}_{a|r}_ {i|e}(e.g.,e_ta_a_i) -
Power Factor:
pf_lX -
Frequency:
f -
Transformer Ratio:
{ct|vt}_{act|old}_{prim|sec}
6. Transmission Frequencies
| Profile | Transmission Frequency (min) |
|---|---|
| 0 | 5 |
| 1 | 2 |
| 2 | 2 |
| 3 | 2 |
| 4 | 15 |
7. Factory Setting
Profile 0 is used as the factory setting (see Chapter 8).
8. Profiles
8.1. Profile 0 – Complete Data
Comprehensive measurement values for power, current, voltage, energy meters, and power quality.
-
Power (W):
p_l1_a,p_l2_a,p_l3_a,p_l123_a -
Current (mA):
i_l1,i_l2,i_l3,i_l123 -
Voltage (V ÷10):
u_l1,u_l2,u_l3,u_l12,u_l23,u_l31 -
Energy (Wh):
e_ta_a_i,e_ta_a_e,e_ta_r_i,e_ta_r_e -
Power Quality:
pf_l1,pf_l2,pf_l3(÷100),f(Hz ÷10) -
Status:
pwr_fail
8.2. Profile 1 – Voltage & Current
Focus on voltage and current values, including power quality metrics.
-
Voltage (V ÷10):
u_l1,u_l2,u_l3,u_l12,u_l23,u_l31 -
Current (mA):
i_l1,i_l2,i_l3,i_l123 -
Power Quality:
pf_l1,pf_l2,pf_l3(÷100),f(Hz ÷10)
8.3. Profile 2 – Power & Current
Focus on active power, current measurements, and power quality values.
-
Power (W):
p_l1_a,p_l2_a,p_l3_a,p_l123_a -
Current (mA):
i_l1,i_l2,i_l3,i_l123 -
Power Quality:
pf_l1,pf_l2,pf_l3(÷100),f(Hz ÷10)
8.4. Profile 3 – Energy Meter
Minimum payload for billing and monitoring applications.
-
Energy (Wh):
-
e_ta_a_i,e_ta_a_e -
e_ta_r_i,e_ta_r_e8.5. Profile 4 – Historical Data
Extended profile with timestamps, tariff information, and current and voltage transformer configurations (Little-Endian format).
-
Time / Index:
index,epoch,epoch_old -
Energy by Tariff (Wh):
-
Tariff 1:
e_t1_a_i,e_t1_a_e,e_t1_r_i,e_t1_r_e -
Rate 2:
e_t2_a_i,e_t2_a_e,e_t2_r_i,e_t2_r_e
-
Tariff 1:
-
Currents (mA):
i_l1,i_l2,i_l3,i_l4,i_l123 -
Power (W):
p_l1_a,p_l2_a,p_l3_a,p_l123_a,p_l123_a_avg -
Voltage (V ÷ 10):
u_l1,u_l2,u_l3 -
Power Quality:
f(Hz ÷ 10),pf_l1,pf_l2,pf_l3(÷ 10) -
CT/VT Configuration:
ct_act_prim,ct_act_sec,ct_old_prim,ct_old_sec,vt_act_prim,vt_act_sec,vt_old_prim,vt_old_sec
9. Data Encoding
Component Quantity Type Scaling Unit Description Voltage 32-bit int ÷ 10 V Phase and conductor voltages Current 32-bit int 1:1 mA Phase and total current Power 32-bit int 1:1 W Active power Energy 64-bit uint 1:1 Wh Energy meter readings Power factor 8-bit int ÷ 100 (Big Endian), ÷ 10 (Little Endian) – Value range −1.0 to +1.0 Frequency 16-bit int ÷ 10 Hz Mains frequency Timestamp 64 bits uint 1:1 s Unix epoch timestamp CT/VT ratio 16-bit uint 1:1 – Current and Voltage Transformer Ratios 10. Usage Instructions
Profile selection:
- Profile 0 = Full monitoring
- Profile 1 = Voltage quality
- Profile 2 = Power analysis
- Profile 3 = Billing data
- Profile 4 = Historical Data
JavaScript Example:
const voltage = raw_u_l1 / 10; // 2350 → 235.0 V const pf = raw_pf_l1 / 100; // -85 → -0.85 const net_energy = e_ta_a_i - e_ta_a_e; const ct_ratio = ct_act_prim / ct_act_sec;11. Compatibility and Notes
- Firmware version ≥ 1.3 required
-
Payload evaluation only if
fw_minor_ver ≥ 3andstatus = 0 - All fields are transmitted; there are no hidden fields
- The little-endian byte order must be observed during decoding
- The various profiles allow for optimization of the payload size according to the respective use case
- Profile 4 supports time series analysis based on Unix epoch timestamps
-
Time / Index:
-