-
Notifications
You must be signed in to change notification settings - Fork 1
Hardware Reports
Manuel edited this page Sep 2, 2026
·
3 revisions
Devices this integration has been run against, as reported in the issue tracker. The write column is what matters most: the export controls are a beta because too few people have confirmed them on real hardware, the battery controls need no flag but are just as unconfirmed, and every row here moves that along. Fronius, SolarEdge, SMA and Kostal now have their own vendor profiles, built from vendor documents and community sources rather than project hardware; their own "Reporting back" sections in docs/ are the place for those.
| Device | Firmware | Blocks seen | Reads | Writes | Source |
|---|---|---|---|---|---|
| KACO Powador 7.8 TL3 | 1, 103, 160 | yes | no control blocks | development device | |
| KACO blueplanet 9.0 TL3 | 103, 160, 123 | yes | 123 export limit, driven for two years through a proxy before the beta existed | #17 | |
| KACO bp 20.0 NX3 M2 | V610-03043-06 | 123, 704 | yes | 123 and 704 export limit in percent work. The limit lapses after the revert time. Watt setpoint on 704 not confirmed | #17, #42 |
| KACO NH3 | 124 not established | #32 | |||
| Fronius Symo GEN24 4.0 | 1.41.10-1, 1.41.11-1 | 103, 123, no 704 | yes | 123 export limit confirmed: 20 % of a 4000 W WMax measured as 799 W. A changed limit takes effect after the enable flag is written again |
#17, #45, #49 |
| Fronius GEN24 SC Plus with BYD 60 kWh | 103, 123, 124 | yes, reported stable | 124 not yet tried | #57 | |
| SolarEdge (model not named) | 1, 103, ... | yes, on port 1502 | #25 | ||
| Kostal PIKO CI 50 | yes | #52 | |||
| Kostal PLENTICORE, PIKO IQ | no report yet | profile from the interface description, docs/kostal.md | |||
| SMA Sunny Tripower X | 701 family, 714 | yes, 714 vanishes for hours in low light | cjne/ha-sunspec#202, via the standby handling |
One issue with:
- Make and model, and the firmware version (
Vron the device card, or inlatest_valuesunder"1"in the diagnostics download) - The
detected_modelsarray from the diagnostics download - If you use the write controls: which entity you wrote, what value, and what the inverter did. A measured power reading beats a read-back value, because block 123 reads back whatever was last written regardless of what the inverter is doing.
- On a Fronius, SolarEdge, SMA or Kostal, the
vendorfield at the top of the diagnostics download (fronius,fronius_datamanager,solaredge,smaorkostal) says which profile applied, andraw_blocksshows the vendor registers behind the entities you tested. An emptyvendoron a device you expected a profile for is worth reporting on its own.
Two clean write reports per block are what takes the BETA flag off.
Recipes
- Energy dashboard and statistics
- Zero export and export limiting
- Battery control
- Alerts and notifications
- Dashboard cards
- n8n workflows
- Node-RED workflows
- Sharing the inverter
Reference
- SunSpec models explained
- Entity names and IDs
- Diagnostics file reference
- Vendor notes
- Hardware reports
- FAQ
Under the hood
In the repository