Repository navigation
[Feature Request] v1.6.0 Beta: Missing 'homeLoadPower' in 'saj_h1' profile prevents full migration #118
Description
Hi @djansen1987,
Testing the new v1.6.0 Beta branch to fix the GreenHeiss login issue (which works great, thank you!).
However, during the migration from v1.5.7, I found a blocking issue regarding the entity mapping for H1 Hybrid Inverters.
Hardware:
- GreenHeiss (SAJ) H1 Inverter + SAJ SEC Meter.
The Issue:
I cannot get a complete set of energy sensors using a single profile in sensors.yaml. The essential data seems split between the saj_h1 and saj_sec profiles, forcing me to choose between seeing my Solar Production OR my House Consumption.
Here is the comparison/mapping table I created while testing both profiles independently:
| Data Concept | Profile saj_h1 (Target for H1) |
Profile saj_sec (Target for Meter) |
Result |
|---|---|---|---|
| Grid Power (Net) | ✅ gridPower |
❌ totalGridPower (Unavailable) |
saj_h1 is better. |
| PV Power (Generation) | ✅ pvPower |
❌ totalPvgenPower (Unavailable) |
saj_h1 is better. |
| Home Load (Consumption) | ❌ MISSING | ✅ homeLoadPower |
saj_sec is better. |
| Battery Data | ✅ Available | ❌ Unavailable | saj_h1 is required. |
Migration Context:
In previous versions (or when using saj_sec in the past), we could calculate missing values or access totalLoadPower.
Now, if I switch my config to sensors: saj_h1 (which is the correct match for my hardware to see battery stats), I lose the Home Load visibility entirely.
Request:
Could you please expose/map the homeLoadPower (or totalLoadPower) entity within the saj_h1 profile?
Since the H1 inverter reads the SEC meter data to function, this value should be available to the inverter profile. This would allow H1 users to have a single, complete profile for Energy Dashboarding without creating manual template sensors to calculate Load from Grid/PV.
Thanks for your hard work!
Activity
jaesbit commentedon May 14, 2026
Hi @BorjaIglesias,
I’ve opened a PR that migrates the integration to the newer Elekeeper API through a dedicated client library:
#121
One of the changes is that H1-related sensors are no longer limited by the old
saj_h1/saj_secsplit in the same way. The PR exposeshomeLoadPower,outPowerandtotalLoadPowerfrom the unified Elekeeper load power value, so it should cover the missing household consumption use case you described.If you have a chance to test it with your H1 + SEC setup, feedback would be very useful. In particular, I’d like to confirm whether the Energy Dashboard can now see PV, grid, battery and home load from the same integration path.