Skip to content
English
  • There are no suggestions because the search field is empty.

Hyperion Mioty Profile  

Firmware and Data Profile Reference for Hyperion Energy Meter

📄 You can view the PDF above or download it here .

Overview 

The Hyperion Energy Meter (Sentinum) transmits energy data via the MIOTY protocol. This document describes the payload structure, profiles, and field definitions (from firmware v1.3 onwards).

Device info:

  • Type EUI: FCA84A0000000006
  • Vendor: Sentinum
  • Protocol: mioty
  • Firmware: v1.3+ (payload only for fw_minor_ver ≥ 3 and status = 0)

Setting Profiles 

Profile Setting/Value
0 0
1 001
2 002
3 003
4 004

Familiarize yourself with the display

Step 1: Mioty DEVEUI

Use the down arrow key to scroll down to the "Mioty DevEUI Settings" section as shown on the screen. Here you will see the device number.

Step 2: Navigate to Mioty Payload profile 

Use the down arrow key to navigate to "Mioty Payload Profile Settings."

The number below indicates the set payload profile.

Step 3: change the profile 

Use an insulated screwdriver to press the button on the bottom right, as shown in the image. The number will then be displayed as 3 digits, in this case 001. Use the button on the right to navigate through the decimal places, and the button on the bottom to manipulate (increase) the respective place.

 
Note: The profile must always be specified in the following format: 001 or 004, etc. Even if the meter setting for a code of 009 is possible, for example, this is not a valid profile. A 0 can be reached again by counting up to 9, after which the digit jumps back to 0. Please set the profiles 000 to 004.

In the following image, 004 has been set 

Step 4: Confirm profile 

 
Note: To change the profile, press and hold the button on the rear right with an insulated pen or screwdriver until the display and keypad flash briefly.

Payload structure

Field Size Type Description
fw_base_id 4 bits uint Firmware base identifier
fw_major_ver 4 bits uint Major version
fw_minor_ver 4 bits uint Minor version
dev_sub_type 4 bits uint Device subtype
msg_counter 8 bits uint Uplink counter
status 8 bit uint Device status (0 = normal)
serial_num 32 bit uint Serial number
app_version 32 bit uint Application version
mid_version 32 bit uint Middleware version
profile 32 bit uint Profile selector (0–4)

Naming convenions

  • Voltage: u_lX (phase/line)
  • Current: i_lX (phase/total)
  • Power: p_lX_a (active, 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}

Transmission frequencies 

Profile Transmission frequency (min)
0 5
1 2
2 2
3 2
4 15

Profiles 

Profile 0: Complete Data

Comprehensive measured values: power, current, voltage, energy, 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–3 (÷100), f (Hz ÷10)
  • Status: pwr_fail

Profil 1: Voltage & Current 

Focus on voltage and current values with power quality.

  • 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–3 (÷100), f (Hz ÷10)

Profile 2: Power &Current 

Focus on active power, currents, 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
  • Power quality: pf_l1–3 (÷100), f (Hz ÷10)

Profile 3: Energy meter 

Minimum payload for billing & monitoring.

  • Energy (Wh):
    • e_ta_a_i, e_ta_a_e
    • e_ta_r_i, e_ta_r_e

Profile 4: Historical data 

Extended profile, including timestamp, tariffs, and CT/VT configuration (little-endian).

  • Time/index: index, epoch, epoch_old
  • Energy by tariff (Wh):
    • T1: e_t1_a_i/e, e_t1_r_i/e
    • T2: e_t2_a_i/e, e_t2_r_i/e
  • Currents (mA): i_l1–4, 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–3 (÷10)
  • CT/VT configuration: ct_act_prim/sec, ct_old_prim/sec, vt_act_prim/sec, vt_old_prim/sec

Data encoding 

Component Size Type Scaling Unit
Voltage 32b int ÷10 V
Current 32b int 1:1 mA
Power 32b int 1:1 W
Energy 64b uint 1:1 Wh
Power Factor 8b int ÷100 (÷10 for LE)
Frequency 16b int ÷10 Hz
Timestamp 64b uint 1:1 s
CT/VT ratio 16b uint 1:1

Usage Instructions 

Profile selection:

  • Profile 0 = Full monitoring
  • Profile 1 = Voltage quality
  • Profile 2 = Power analysis
  • Profile 3 = Billing
  • Profile 4 = Historical data

Example .js:

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;
  

Compatibility

  • Firmware ≥1.3 required
  • Payload only with fw_minor_ver ≥ 3 and status = 0
  • All fields are visible, no hidden fields
  • Observe endianness correctly
  • Optimize profiles — Payload size depending on use case
  • Profile 4 enables time series analyses with epoch timestamps

 

Specifications subject to change without notice. All information provided without guarantee.