Portable Power Station DPs

This topic describes a total of 38 standard data points (DPs) for the portable power station product. You can apply them to your product based on your needs. According to the property of a DP, you can report DP status to the cloud or send DP commands to the device. The cloud and app panel can parse data and present it to the end user.

Standard DP

DP ID	DP	Identifier	Data transfer type	Data type
1	Battery percentage	battery_percentage	Report	value
2	Remaining time	remain_time	Report	value
3	Battery voltage and current, actual power, and rated power	battery_parameters	Report	raw
4	Fault alert	fault	Report	raw
5	USB port switch	usb_management	Report and send	raw
6	AC1 switch	switch_1	Report and send	bool
7	AC2 switch	switch_2	Report and send	bool
8	Car port control	car_port_control	Report and send	enum
9	Light mode	light_mode	Report and send	enum
10	Device temperature	temp_current	Report	value
11	Power mode	power_mode	Report	enum
12	Radio switch	radio	rw	bool
13	Manually-input radio frequency	radio_frequency	Report and send	value
14	AM/FM selection	am_fm	Report and send	enum
15	Volume control	volume_set	Report and send	value
16	Auto radio search	radio_search	Report and send	bool
17	Auto FM/AM channel search	radio_list	Report and send	raw
18	Laser light control	laser_lamp_control	Report and send	raw
19	Ambient light	switch_led	Report and send	bool
20	Scene	scene_data_raw	Report and send	raw
21	AC output set	ac_output_set	Report and send	raw
22	Alert set	station_alarm_set	Report and send	raw
23	Undervoltage management	undervol_set	Report and send	raw
24	Temperature unit	temp_set_enum	Report and send	enum
25	Buzzer setting	beep	Report and send	bool
26	Standby time	standby_time	Report and send	value
27	Screen timeout	standby_bright	Report and send	value
28	Device ID	inverter_id	Report	string
29	Network mode	network_mode	Report and send	enum
30	Device version	device_version	Report	raw
31	BMS message	bms_message	Report	raw
32	AC message	ac_message	Report	raw
33	DC message	dc_message	Report	raw
34	USB message	usb_message	Report	raw
35	MPPT message	mppt_message	Report	raw
36	Online state	online_state	Report and send	enum
37	Total energy production	reverse_energy_total	Report	value
38	Scheduled charging	device_timer	Report and send	raw

Property

DP 1: Battery percentage

Valid values range from 0 to 100%.

DP 2: Remaining time

• The data is in hex format, two bytes in length, in big-endian.
• Precision of the unit: minutes
• Convert the time data in hex into decimal format for display. Example: 00 64 in hex represents 100 minutes.
• Communication logic:
  • Case 1: The device reports data regularly or does not report it.
  • Case 2: Refer to the logic used for DP 37.

DP 3: Battery parameters

• The data is in hex format, eight bytes in length, in big-endian.
• Precision of the unit
  • Voltage of two bytes, in 0.1V steps.
  • Current of two bytes, in 0.1A steps.
  • Power of two bytes, in 0.1W steps.
  • Rated power of two bytes, in 0.1W steps.
• Message format:
  Example: 00 78 00 0B 00 84 13 88 indicates that the battery voltage is 12.0V, current is 1.1A, actual power is 13.2W, and rated power is 500.0W.
• Communication logic:
  • Case 1: The device reports data regularly or does not report it.
  • Case 2: Refer to the logic used for DP 37.

DP 4: Fault alert

• The data is in hex format, four bytes in length, in big-endian.

• Message format:
  The reported fault alert must be four bytes in length. A bit represents the alert occurrence. 1: An alert occurs. 0: No alert occurs. Unused bits are padded with zeros. The high bit is not defined but padded with zeros.
  Example: 0X00 00 00 09 indicates that AC overcurrent and abnormal grid frequency occur.

• Communication logic:
  The device must report the complete four-byte data to the app, even if only a single alert occurs. The device must report the complete four-byte data to the app for status updating, even if only a single alert is cleared.

• Bit definitions

  • Bit0 for undervoltage alert (overdischarge protection): alert enablement, action enablement, and threshold setting.
  • Bit1 for early undervoltage alert: alert enablement.
  • Bit2 for battery temperature alert: alert enablement, action enablement, and threshold setting.
  • Bit3 for overload alert: alert enablement, action enablement, and threshold setting (in percentage).
  • Bit4 for overcurrent protection alert: alert enablement, action enablement, and threshold setting (in percentage).
  • Bit5 for output short circuit protection: when a short circuit occurs, the device confirms the action and enables an alert, with no settings required.
  • Bit6 for overcharge protection alert: alert enablement and action enablement.
  • Bit7 for overvoltage protection alert: alert enablement, action enablement, and threshold setting.
  • Bit8 for fan fault alert: alert enablement and action enablement.
  • Bit9 for other hardware fault alerts: alert enablement and action enablement. (These are new alerts. The alert dialog can be closed and will reappear when users open the panel again.)
  • Bit10 for inverter overtemperature protection.

DP 5: USB port switch (the main switch, up to six USB ports supported)

• The data is in hex format, in big-endian.

• Format

  • The first byte: 0x00 indicates the main switch is off. 0x01 indicates the main switch is on.
  • The second byte: 0x00 indicates USB-A1 is off. 0x01 indicates USB-A1 is on. The text displayed on the app: USB-A1
  • The third byte: 0x00 indicates USB-A2 is off. 0x01 indicates USB-A2 is on. The text displayed on the app: USB-A2
  • The fourth byte: 0x00 indicates USB-A3 is off. 0x01 indicates USB-A3 is on. The text displayed on the app: USB-A3
  • The fifth byte: 0x00 indicates USB-C1 is off. 0x01 indicates USB-C1 is on. The text displayed on the app: USB-C1
  • The sixth byte: 0x00 indicates USB-C2 is off. 0x01 indicates USB-C2 is on. The text displayed on the app: USB-C2
  • The seventh byte: 0x00 indicates USB-C3 is off. 0x01 indicates USB-C3 is on. The text displayed on the app: USB-C3
    If the device reports FF for a byte, the panel will parse but not display it.
    Example: 0x01 01 01 FF 01 00 FF indicates that the main switch of the USB port is on, USB-A1 and USB-A2 are occupied, USB-A3 is not equipped, USB-C1 is occupied, USB-C2 is available, and USB-C3 is not equipped.

• Communication logic:

  • Case 1: During the initial pairing, the mobile phone must be connected to the Tuya IoT cloud. Over a Bluetooth connection to the app, the device reports this DP to notify the app panel of the available USB port. Meanwhile, information about the USB port will be stored in the cloud.
  • Case 2: When the mobile phone is not connected to the Tuya IoT cloud, the device should proactively report this DP during communication with the app. This allows the app panel to parse and display the USB port information.
  • Case 3: When the mobile phone is connected to the Tuya IoT cloud, the app panel will prioritize retrieving the USB port configuration stored in the cloud when users open the app. After the device is connected to the app and reports the current USB port status, the app panel will update the information accordingly.

DP 6: AC1 switch

• The data is in hex format, one byte in length.

• 0x00 indicates AC1 is off. 0x01 indicates AC1 is on.

• Communication logic:
  The device should proactively report this DP during communication with the app. This allows the app panel to parse and display the switch status. The device reports the current status to the app panel when there is a change in this DP.

  If multiple AC ports share one switch, choose AC1. Then, change the app multilingual UI text of AC1 to AC.

DP 7: AC2 switch

• The data is in hex format, one byte in length.
• 0x00 indicates AC2 is off. 0x01 indicates AC2 is on.
• Communication logic:
  The device should proactively report this DP during communication with the app. This allows the app panel to parse and display the switch status. The device reports the current status to the app panel when there is a change in this DP.

DP 8: Car port control

• The data is of enum type, in hex format, one byte in length.
• Communication logic:
  The device should proactively report this DP during communication with the app. This allows the app panel to parse and display the car port information. The device reports the current status to the app panel when there is a change in this DP.

DP 9: Light mode

• The data is in hex format, one byte in length.

• Status:

  • 0x00: Off
  • 0x01: On
  • 0x02: Bright light
  • 0x03: Night light
  • 0x04: SOS flashlight
  • 0x05: Strobe light

• Communication logic:

  The device should proactively report this DP during communication with the app. This allows the app panel to parse and display the light status. After receiving a command, the device executes it and returns the current status to the app panel.

DP 10: Device temperature

• The data is in hex format, four bytes in length, in big-endian.
• Precision of the unit: 0.1°C
• Message format:
  Example: The device reports 0x01, indicating 0.1°C.
• Communication logic:
  • Case 1: The device reports data regularly or does not report it.
  • Case 2: Refer to the logic used for DP 37.

DP 11: Power mode

• Message format:
  0x00: Standby mode (neither charging nor discharging)
  0x01: Charging
  0x02: Discharging
  0x03: Charging and discharging

• Communication logic:

  • After receiving the command from the app panel, the MCU enters the specified mode and returns the current status.
  • When a fault occurs in the inverter, the MCU proactively reports the status of the switch.

DP 12: Radio switch

• Message format:
  0x00: Off. 0x01: On.
• Communication logic:
  After receiving an on/off command from the app, the device executes it and returns the current status.

DP 13: Manually-input radio frequency

• The data is in hex format, four bytes in length, accurate to one decimal place. The size of a value defaults to four bytes.
• Message format:
  Example: 0x03 C8 represents 96.8 MHz. The units for AM and FM are kHz and MHz, respectively.
• Communication logic:
  After receiving the radio frequency setting from the app, the device executes it and returns the current status.

DP 14: AM/FM selection

• The data is in hex format, one byte in length.
• Message format:
  In the first byte, 0x00 is for FM, and 0x01 is for AM. The units for AM and FM are kHz and MHz, respectively.
• Communication logic:
  After receiving the AM/FM selection from the app, the device saves it and returns the current status.

DP 15: Volume control

• The data is in hex format, one byte in length. Valid values range from 1% to 100%.
• Message format:
  Example: 0x64 indicates 100%, with no decimal places.
• Communication logic:
  After receiving the command from the app, the device executes it and returns the current status.

DP 16: Auto radio search

• The data is in hex format, up to 45 bytes in length, in big-endian, accurate to one decimal place.
• Message format:
  The app sends the command true 0X01 to the device to initiate a radio search.
• Communication logic:
  After receiving the command from the app, the device executes it and returns the current status.

DP 17: Auto FM/AM channel search

• The data is in hex format, in big-endian. Each radio station is three bytes in length. In total, there are 30 stations, with 15 FM stations and 15 AM stations, resulting in a length of 90 bytes. The format of radio frequency: a three-digit integer with one decimal place. Example: 04 1E indicates 105.4.

• Message format:
  The first byte 01 represents station 1, and the second and third bytes represent the frequency of station 1. The fourth byte represents station 2, and the fifth and sixth bytes represent the frequency of station 2, and so on. The device can report up to 15 FM stations and 15 AM stations.

  The radio module must filter out frequency bands with poor reception.

  Example: data in hex format, 01 (station 1, the first FM station) 03 A2 02 (station 2, the second FM station) 03 B6 FF … FF (the first 45 bytes, padded with FF if there are fewer than 15 FM stations) 10 (station 16, the first AM station) 03 7B 11 (station 17, the second AM station) 03 84 FF … FF (the last 45 bytes, padded with FF if there are fewer than 15 AM stations)
  The example indicates that the first FM station broadcasts at 93.0 MHz. The second FM station broadcasts at 95.0 MHz. Other bytes for FM stations are padded with FF. The first AM station broadcasts at 89.1 kHz. The second AM station broadcasts at 90.0 kHz. Other bytes for AM stations are padded with FF.

• Communication logic:

  After receiving the DP 16 command, the device starts a channel search, and then arranges and returns 15 FM stations and 15 AM stations in sequential order. If there are fewer than 15 FM stations, pad the byte with FF.

DP 18: Laser light control

• The data is in hex format, three bytes in length.
• Status:
  • The first byte: 0x00: Off.
  • The second byte: 0x01: Brightness 1 0x02: Brightness 2 0x03: Brightness 3
  • The third byte: 0x01: Blinking 1 0x02: Blinking 2 0x03: Blinking 3
    If the device reports FF for a byte, the panel will parse but not display it.
• Communication logic:
  After receiving a command from the app, the device executes it and returns the current status.

DP 19: Ambient light

• The data is in hex format, one byte in length, in big-endian.
• Message format:
  0x00: Turn off. 0x01: Turn on.

DP 20: Scene

• The data is in hex format, in big-endian.

• Message format:
  Total of 14 bytes. Value: 0011223344445555666677778888
00: Scene ID, indicating a lighting effect such as soft, vibrant, colorful, dynamic, dreamy, or Mediterranean.
  11: The transition interval between lighting modes. It ranges from 0 to 100.
  22: The lighting mode duration. It ranges from 0 to 100.
  33: The lighting mode. 0: Static. 1: Jumping. 2: Gradient.
  4444: Hue. It ranges from 0 to 360, corresponding to 0x0000 to 0x0168.
  5555: Saturation. It ranges from 0 to 1,000, corresponding to 0x0000 to 0x03E8.
  6666: Value. It ranges from 0 to 1,000, corresponding to 0x0000 to 0x03E8.
  7777: Brightness. It ranges from 0 to 1,000.
  8888: Color temperature. It ranges from 0 to 1,000.

  The scene number indicates the number of units in one scene. Up to eight units are allowed.

• Communication logic:

  If the ambient light is off, the device does not need to report this DP when connected to the app over Bluetooth. If the ambient light is on, after receiving a command over a Bluetooth connection, the device executes it and reports the scene ID to the panel for display.

DP 21: AC output setting

• The data is in hex format, two bytes in length, in big-endian.

• Message format:

  • The first byte for voltage. 0x00: 220V. 0x01: 120V.
  • The second byte for frequency. 0x00: 50 Hz. 0x01: 60 Hz.

DP 22: Alert setting

• The data is in hex format, in big-endian. The total length is the result of the alert quantity multiplied by four bytes.

• Message format:

  Each alert consists of four bytes, with the first byte indicating its presence. The second byte: Specify whether the device triggers an alert and performs an action when the anomaly occurs. The third and fourth bytes: The alert threshold.
  Example: 0X01 03 00 6E 03 01 01 OE, indicating that the meter supports undervoltage alert and has a threshold set at 11.0V. When the threshold is reached, an alert will be triggered and appropriate action will be taken. Temperature alert is supported, with a threshold of 40°C. When the threshold is reached, an alert will be triggered without any action taken. No other alerts are supported.

• Communication logic:

  • Once the device is paired, it will proactively report the supported alert to the app panel in the specified format.
  • The device also reports this DP when connected to the app over Bluetooth.
  • When an anomaly occurs, the device will proactively report it to the app panel when connected over Bluetooth.

  Alert name	The first byte for alert enablement	The second byte for alert and action	The third and fourth bytes for threshold
  Undervoltage alert (overdischarge protection)	0x01: Undervoltage alert is available. If nothing is reported, it means the device does not support this alert.	Bit0: 1: Enable. The panel will issue an alert. 0: Disable. The app will issue an alert. Bit1: 1: Take an action. 0: Take no action.	Default to 11.0V. Valid values range from 1 to 100.0V.
  Early undervoltage alert	0x02: Early undervoltage alert is available. If nothing is reported, it means the device does not support this alert.	Bit0: 1: Enable. The panel will issue an alert. 0: Disable. The app will issue an alert. Bit1: 1: Take an action. 0: Take no action.	Default to 12.0V. Valid values range from 1 to 100.0V.
  Battery temperature alert	0x03: Battery temperature alert is available. If nothing is reported, it means the device does not support this alert.	Bit0: 1: Enable. The panel will issue an alert. 0: Disable. The app will issue an alert. Bit1: 1: Take an action. 0: Take no action.	Default to 40°C. Valid values range from 1 to 100°C.
  Overload alert	0x04: Overload alert is available. If nothing is reported, it means the device does not support this alert.	Bit0: 1: Enable. The panel will issue an alert. 0: Disable. The app will issue an alert. Bit1: 1: Take an action. 0: Take no action.	Default to 90%. Valid values range from 1 to 100%.
  Overcurrent protection alert	0x05: Overcurrent protection alert is available. If nothing is reported, it means the device does not support this alert.	Bit0: 1: Enable. The panel will issue an alert. 0: Disable. The app will issue an alert. Bit1: 1: Take an action. 0: Take no action.	Default to 90%. Valid values range from 1 to 100%.
  Output short circuit protection	0x06: Output short circuit protection is available. If nothing is reported, it means the device does not support this alert.	Bit0: 1: Enable. The panel will issue an alert. 0: Disable. The app will issue an alert.	Padded with 00 00.
  Overcharge protection alert	0x07: Overcharge protection alert is available. If nothing is reported, it means the device does not support this alert.	Bit0: 1: Enable. The panel will issue an alert. 0: Disable. The app will issue an alert. Bit1: 1: Take an action. 0: Take no action.	/
  Overvoltage protection	0x08: Overvoltage protection alert is available. If nothing is reported, it means the device does not support this alert.	Bit0: 1: Enable. The panel will issue an alert. 0: Disable. The app will issue an alert. Bit1: 1: Take an action. 0: Take no action.	Default to 14.0V. Valid values range from 1 to 100.0V.
  Fan fault alert	0x09: Fan fault alert is available. If nothing is reported, it means the device does not support this alert.	Bit0: 1: Enable. The panel will issue an alert. 0: Disable. The app will issue an alert. Bit1: 1: Take an action. 0: Take no action.	/
  Other hardware fault alerts	0x0A: Other hardware fault alerts are available. If nothing is reported, it means the device does not support this alert.	Bit0: 1: Enable. The panel will issue an alert. 0: Disable. The app will issue an alert. Bit1: 1: Take an action. 0: Take no action.	/

DP 23: Undervoltage management

• Background
  Specify the ports and features that are shut down when the battery is low. An alert will be triggered when the battery is low if you select the USB port, car port, AC port, radio, ambient light, and flashlight. The port or feature that is not selected can still consume power when the battery is low.

• The data is in hex format, six bytes in length, in big-endian.

• Message format:
  0x00: Not controlled. 0x01: Controlled.
  The first byte is for the AC port, the second for the ambient light, the third for the radio, the fourth for the USB port, the fifth for the car port, and the sixth for the flashlight.

• Communication logic:
  When the device is connected to the app over Bluetooth, it receives and executes the undervoltage management command, and then returns the current status to the app.

DP 24: Temperature unit

• The data is in hex format, one byte in length, in big-endian.
• Message format:
  0x00: Celsius. 0x01: Fahrenheit.
• Communication logic:
  If your product has a buzzer and temperature detection function, choose this DP. When the device is connected to the app over Bluetooth, it receives and executes the temperature unit setting command, and then returns the current status to the app.

DP 25: Buzzer setting

• The data is in hex format, one byte in length, in big-endian.
• Message format:
  0x00: Silent. 0x01: Sounding.
• Communication logic:
  When the device is connected to the app over Bluetooth, it receives and executes the buzzer setting command, and then returns the current status to the app.

DP 26: Standby time

• The data is in hex format, four bytes in length, in big-endian. The unit is minutes.
• Message format:
  Set the system standby time. Multiply the set number by one minute to get the standby time. Example: 0x01 indicates the standby time is one minute. 0x02 indicates the standby time is two minutes, and so on.
  • Example: Send 0x01 to instruct the device to set the system standby time to one minute. The MCU executes the command and then returns the set value 0x01. Send 0x79 to instruct the device to set the system standby time to 121 minutes. The MCU executes the command and then returns the set value 0x79.

DP 27: Screen timeout

• The data is in hex format, two bytes in length, in big-endian. The first and second bytes represent the hour and minute, respectively.
• Message format:
  Set the screen timeout. Multiply the set number by one minute to get the screen timeout time. Example: 0x01 indicates the screen timeout is one minute. 0x02 indicates the screen timeout is two minutes, and so on.
  Example: Send 0x02 to instruct the device to set the screen timeout to two minutes. The MCU executes the command and then returns the set value 0x02.

DP 28: Device ID

• The data is in string format, in big-endian.
• Communication logic:
  • During the pairing process, the device will report its device ID three times to ensure successful delivery. If the device is paired, the panel will show the device ID.
  • If the device is paired, but the panel does not show the device ID, remove the device and pair it again.

DP 29: Network mode

• This DP is used to show the current network connected, specifically designed for low power products.
• 00: Wi-Fi. 01: Local network over Bluetooth.

DP 30: Device version

• The firmware and hardware information for the four boards is in raw hex format, separated by commas (,).

• The sequence: motherboard hardware version, motherboard firmware version, BMS hardware version, BMS firmware version, inverter hardware version, inverter firmware version, MPPT hardware version, MPPT firmware version.

• If your product does not have any of the four boards, leave its information empty. For example, motherboard hardware version, motherboard firmware version, BMS hardware version, BMS firmware version, MPPT hardware version, MPPT firmware version, indicating the hardware and firmware information for the inverter does not exist.

• It is recommended that the hardware or firmware information for a board be limited to 15 alphanumeric characters.

• Message format:
  MBH00-V1.3,MBS00-V1.0,BMSH15-V1.2,BMSS15-V1.2,

• Communication logic:
  After the device is paired, it will report this DP three times to ensure successful delivery. After a restart, it reports this DP once.

DP 31: BMS message

The data is in hex format, in big-endian.

• 2B: The maximum BMS temperature, in 1°C. In the most significant bit, 0 and 1 indicate positive and negative, respectively.
• 2B: The minimum BMS temperature, in 1°C. In the most significant bit, 0 and 1 indicate positive and negative, respectively.
• 2B: The BMS voltage, in 0.1V.
• 1B: The state-of-charge (SOC) value.
• 2B: The charging current, in 0.1A.
• 2B: The discharging current, in 0.1A.
• 2B: The current capacity, in 0.1 Ah.
• 2B: The current full capacity, in 0.1 Ah.
• 2B: The estimated charging time, in minutes.
• 2B: The remaining capacity, in minutes.
• 4B: The total operating time, in minutes.
• 2B: Cycle count

DP 32: AC message

The data is in hex format, in big-endian.

• 1B: Inverter communication status. 0: Anomalous. 1: Normal. 2: Lost. 3: Out of position.
• 2B: Bus voltage, in 0.1V.
• 2B: The temperature, in 1°C. In the most significant bit, 0 and 1 indicate positive and negative, respectively.
• 2B: AC output voltage, in 0.1V.
• 2B: AC output current, in 0.01A.
• 1B: AC output frequency, in Hz.
• 2B: AC output power, in 0.1W.
• 1B: Status. 01: AC charging. 02: Inverter on. 03: AC normal.
• 2B: AC input voltage, in 0.1V.
• 2B: AC input current, in 0.01A.
• 1B: AC input frequency, in Hz.
• 2B: AC input power, in 0.1W.
• 2B: The BMS current, in 0.1A.
• 2B: The BMS voltage, in 0.1V.
• 1B: Status. 0: Normal. Other values: Anomalous.
  • Bit0: Inverter overtemperature protection.
  • Bit1: Inverter hardware protection.
  • Bit2: AC input overvoltage.
  • Bit3: AC overload protection.
  • Bit4: AC short-circuit protection.

DP 33: DC message

The data is in hex format, in big-endian.

• 1B: DC status. 00: Off. 01: On.
• 2B: DC output power, in 0.1W.
• 2B: DC output current, in 0.01A.
• 2B: DC temperature, in °C. In the most significant bit, 0 and 1 indicate positive and negative, respectively.
• 1B: DC error code.
  • Bit0: DC failed to turn on.
  • Bit1: PG lost.
  • Bit2: Overtemperature protection.
  • Bit3: Overload protection.
    Example: 01 00 64(10W) 01 F4(0.5A) 80 0A(-10°C) 01, indicating the DC power failed to turn on.

DP 34: USB message

The data is in hex format, in big-endian.

• 2B: Total USB power, in 0.1W.
• 2B: Total USB current, in 0.01A.
• 2B: USB Type1 voltage, in 0.1V.
• 2B: USB Type1 current, in 0.01A.
• 2B: USB Type1 temperature, in °C. In the most significant bit, 0 and 1 indicate positive and negative, respectively.
• 2B: USB Type2 voltage, in 0.1V.
• 2B: USB Type2 current, in 0.01A.
• 2B: USB Type2 temperature, in °C. In the most significant bit, 0 and 1 indicate positive and negative, respectively.
• 2B: USB Type3 voltage, in 0.1V.
• 2B: USB Type3 current, in 0.01A.
• 2B: USB Type3 temperature, in °C. In the most significant bit, 0 and 1 indicate positive and negative, respectively.
• 1B: USB error code.
  • Bit0: USB failed to turn on.
  • Bit1: PG lost.
  • Bit2: Overtemperature protection.
  • Bit3: Overload protection.

DP 35: MPPT message

The data is in hex format, in big-endian.

• 1B: MPPT communication. 00: Anomalous. 01: Normal.
• 1B: MPPT status. 00: Off. 01: On.
• 1B: DC charging port. 00: Off. 01: On.
• 1B: PV charging port. 00: Off. 01: On.
• 2B: Input voltage, in 0.01V.
• 2B byte: Output voltage, in 0.1V.
• 2B byte: Output current, in 0.01A.
• 2B byte: Output power, in 0.1W.
• 2B: temperature 1, in °C. In the most significant bit, 0 and 1 indicate positive and negative, respectively.
• 2B: temperature 2, in °C. In the most significant bit, 0 and 1 indicate positive and negative, respectively.
• 1B byte: Status. 00: Normal. 01: Anomalous.
  • Bit0: Input voltage low.
  • Bit1: Input voltage high.
  • Bit2: Output short circuit.
  • Bit3: Output overcurrent.
  • Bit4: Overtemperature 1
  • Bit5: Overtemperature 2

DP 36: Online state

• When users check information on the app panel, the MCU will be notified to report data such as voltage, current, and power more frequently than usual.
• The data is in hex format, one byte in length.
• Message format:
  01: Online
• Communication logic:
  • Case 1: When the app panel is opened, it sends the command 01 through DP 36 to inform the MCU of this event. Then, the MCU will report data every 20 seconds. Once the user exits the app panel, even if the app remains open, the command 00 is sent to notify the MCU that it should return to its regular reporting frequency.
  • Case 2: If the app is forcibly closed, the panel will send 01 to the MCU every three minutes. On receiving the command, the MCU will start high-frequency data reporting. If the MCU does not receive 01 within three minutes, it will return to its regular reporting frequency.

DP 37: Total energy production (for photovoltaics)

Valid values range from 0 to 99999999 kWh.

DP 38: Scheduled charging

• The data is five bytes in length, in big-endian.
• Precision of the unit
• Message format:
  • The first byte. 00: Turn off scheduled charging. 01: Turn on scheduled charging.
  • The second and third bytes indicate the start hour and minute, respectively.
  • The fourth and fifth bytes indicate the end hour and minute, respectively.
    Example: 01 22 00 03 00, indicating that scheduled charging is enabled from 22:00 to 03:00.
    After receiving a command, the device executes it and returns a response to the app panel.
• Communication logic:
  Instant interaction