EmsTechLabs Logo EmsTechLabs

Import Active Energy Since Last Reset Modbus Register 30073: Entities name prefix - slave entities prefix name - Import Active Energy Since Last Reset

Technical documentation for Modbus register 30073 on Import Active Energy Since Last Reset. Data type: U DWORD. Includes Python and YAML configuration examples.

January 16, 2026 1 min read

Technical Definition

The register entities name prefix - slave entities prefix name - Import Active Energy Since Last Reset at address 30073 is used to monitor entities name prefix - slave entities prefix name - import active energy since last reset on the Import Active Energy Since Last Reset.

  • Protocol: Modbus RTU
  • Data Type: U DWORD
  • Unit: kWh
  • Access: Read Only

How to Read (Python pymodbus)

Use this code snippet to read this specific value via RS485:

from pymodbus.client.sync import ModbusSerialClient

client = ModbusSerialClient(method='rtu', port='/dev/ttyUSB0', baudrate=9600)
client.connect()

# Read entities_name_prefix - slave_entities_prefix_name - Import Active Energy Since Last Reset (Address: 30073)
# Note: Check if your device uses 0-based or 1-based addressing
result = client.read_input_registers(address=30073, count=2, unit=1)

if not result.isError():
    print(f"Raw Value: {result.registers}")
else:
    print("Error reading register")

client.close()

Integration (Home Assistant)

Paste this into your configuration.yaml:

- platform: modbus_controller
  name: "entities_name_prefix - slave_entities_prefix_name - Import Active Energy Since Last Reset"
  address: 30073
  value_type: U_DWORD
  unit_of_measurement: "kWh"

Connection Diagram

Here is the standard RS485 wiring for this configuration:

graph TD
    PLC[Host Controller / Home Assistant]
    Device[Import Active Energy Since Last Reset]

    PLC -- "A+ (D+)" --> Device
    PLC -- "B- (D-)" --> Device
    PLC -- GND --> Device


💡 Engineer's Insight

Analysis: Accumulated active energy consumed from the grid since the last reset, in kilowatt-hours (kWh).

Troubleshooting: Reset counter if needed. Unexpected values may indicate meter or communication issues.