You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @TypQxQ - thanks for all the work on this integration.
You mentioned you can't test the DC charger yourself since your charger's a different brand. I run a Sigenergy DC EV charger (SigenStor EC 10.0 SP AU, firmware V100R001C22SPC114) daily, so I'm glad to be a real-hardware test bench for the DC side.
I've been following the recent DC-charger changes - the running-state-based is_on (#373), the new Start/Stop buttons (#374), and the availability gating - and I can validate them end-to-end once they're in a release (or I'm happy to run main). Specifically I can confirm on real hardware:
The Start/Stop buttons actually start and stop a live session, and whether the availability gate correctly blocks a Start while the charger is Idle (the inverter otherwise rejects the 41000 write with Modbus Illegal Data Address).
The running-state values my charger really reports through a full session (Idle -> Occupied -> Preparing -> Charging -> Ended), so the enum and the is_on/availability logic match reality.
A few registers that respond on my firmware but I'm unsure are in the V2.8 doc - e.g. dc_charger_max_charging_power_limit (41002) reads a real 12.5 kW and dc_charger_total_charging_capacity reads ~242 kWh. Happy to map out exactly which DC registers my firmware answers so the supported set is accurate.
Just point me at a branch or tell me what's most useful to verify, and I'll send back results/logs. Thanks again!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi @TypQxQ - thanks for all the work on this integration.
You mentioned you can't test the DC charger yourself since your charger's a different brand. I run a Sigenergy DC EV charger (SigenStor EC 10.0 SP AU, firmware
V100R001C22SPC114) daily, so I'm glad to be a real-hardware test bench for the DC side.I've been following the recent DC-charger changes - the running-state-based
is_on(#373), the new Start/Stop buttons (#374), and the availability gating - and I can validate them end-to-end once they're in a release (or I'm happy to runmain). Specifically I can confirm on real hardware:Idle(the inverter otherwise rejects the 41000 write with Modbus Illegal Data Address).Idle -> Occupied -> Preparing -> Charging -> Ended), so the enum and theis_on/availability logic match reality.dc_charger_max_charging_power_limit(41002) reads a real 12.5 kW anddc_charger_total_charging_capacityreads ~242 kWh. Happy to map out exactly which DC registers my firmware answers so the supported set is accurate.Just point me at a branch or tell me what's most useful to verify, and I'll send back results/logs. Thanks again!
All reactions