Environment
- Device: Marstek VenusE 3.0 (2x units)
- Firmware: 148
- Integration version: v1.1.0
- Home Assistant Core version: 2026.6.4 (Home Assistant Container)
- Connection: Local API over WiFi (no LAN/Modbus)
Problem
On both of my VenusE 3.0 units, the following entities never report a
non-zero / known value, even while the battery is actively charging
(observed SOC rising from 52% to 64% over ~15 minutes):
- sensor.marstek_venuse_3_0_power -> state: unknown
- sensor.marstek_venuse_3_0_power_in -> state: 0
- sensor.marstek_venuse_3_0_power_out -> state: 0
- sensor.marstek_venuse_3_0_solar_power -> state: 0 (correct at night,
but same behavior suspected during the day)
Meanwhile sensors like state_of_charge, available_capacity,
battery_temperature, total_grid_import/export and
total_solar_energy update correctly.
This looks like the same root cause as #119 (bat_power field missing
from ES.GetStatus) but on FW 148 instead of FW 156, and affects VenusE
3.0 specifically (related to #128, which reports solar_power stuck at
0 on FW 148 for a Venus A).
Impact
Without a working power sensor, it's impossible to build an
energy (kWh) sensor via a Riemann-sum integral helper for the Home
Assistant Energy Dashboard's battery charge/discharge tracking.
Expected
bat_power (and derived power_in/power_out/solar_power) should reflect
live charge/discharge power, matching what the official Marstek app
shows for the same period.
Happy to provide a diagnostics dump or raw API response if useful.
Environment
Problem
On both of my VenusE 3.0 units, the following entities never report a
non-zero / known value, even while the battery is actively charging
(observed SOC rising from 52% to 64% over ~15 minutes):
but same behavior suspected during the day)
Meanwhile sensors like
state_of_charge,available_capacity,battery_temperature,total_grid_import/exportandtotal_solar_energyupdate correctly.This looks like the same root cause as #119 (bat_power field missing
from ES.GetStatus) but on FW 148 instead of FW 156, and affects VenusE
3.0 specifically (related to #128, which reports solar_power stuck at
0 on FW 148 for a Venus A).
Impact
Without a working power sensor, it's impossible to build an
energy (kWh) sensor via a Riemann-sum integral helper for the Home
Assistant Energy Dashboard's battery charge/discharge tracking.
Expected
bat_power(and derived power_in/power_out/solar_power) should reflectlive charge/discharge power, matching what the official Marstek app
shows for the same period.
Happy to provide a diagnostics dump or raw API response if useful.