Skip to content
Draft
50 changes: 50 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,56 @@ driver no longer knows FTW wrote, so that offset stays; today only the
operator's control on the heating card writes it. Not yet checked on
hardware.

### sonnen 2.1.0

The driver can set sonnenBatterie charge and discharge power. It needs FTW's
`host.http_put`: sonnen changes its operating mode only through
`PUT /api/v2/configurations`, and answers PATCH and POST there with 404.
Without that function, or without `capabilities.http.allow_write`, the
driver refuses commands and keeps reporting telemetry.

- A battery command puts the unit in manual mode (`EM_OperatingMode` 1) and
posts `/setpoint/charge/<W>` or `/discharge/<W>`, limited to the unit's
`IC_InverterMaxPower_w` and an optional `max_power_w` set by the owner. If the
unit has left manual mode, the driver enters it again once and retries.
- A manual setpoint holds until it is replaced. Without a battery command for
60 s, the driver clears the setpoint and returns the unit to the automatic
mode it ran before. That mode is self-consumption (2) or time-of-use (10).
Default mode and `deinit` do the same and read the mode back. At start, the
driver clears a manual setpoint other than 0 that a stopped FTW left
behind. It leaves a manual mode with setpoint 0 alone, because that may be
the owner's idle and moves no power. After three handovers the unit
refuses, the unprompted paths stop writing; an unreachable unit does not
count toward the three.
- Every control session starts with a confirmed `PUT`. `host.http_post` is
not gated by `allow_write`, so without write access the driver posts
nothing, even when the unit already reports manual mode.
- `{"error": ...}` replies, such as a wrong token's `Unauthorized`, are failed
reads, not `w = 0`.
- Emits `control_power_w` and `control_power_observed_at` from
`/latestdata` for control feedback. It emits `setpoint_w` only after the
driver's own setpoint `POST` was confirmed in this session and a fresh read
confirms manual mode. In the automatic modes `SetPoint_W` is the unit's
own load-following target (1255 W was seen in self-consumption), not a
command. In a manual mode the driver has not yet written, it is what the
unit held before; the first poll after start reported -1622 and -942 W. A
`/configurations` reply without `EM_OperatingMode` is a failed read, so no
decision rests on a mode from an earlier read.

None of these safeguards runs when FTW itself is gone. The HIL gate for host
loss while the unit holds a manual setpoint is still open.

### sonnen 2.0.4

Battery power has the site sign. sonnen reports `Pac_total_W` positive while
discharging and negative while charging; the driver passed it through, so
FTW showed every charge as a discharge and the reverse. It now negates the
value: charging is positive. On a sonnenBatterie with software 1.40.5 on
2026-11-13, in manual mode, a 500 W charge setpoint read back over six reads
as `Pac_total_W` -495 to -504 W, `SetPoint_W` -500 and `BatteryCharging`
true. `battery_pac_w` keeps the vendor's own sign. The driver stays
read-only.

### easee_cloud 1.4.1

The driver says its session energy is coarse, with `session_wh_coarse`. Easee
Expand Down
4 changes: 2 additions & 2 deletions SUPPORT_STATUS.md
Original file line number Diff line number Diff line change
Expand Up @@ -158,8 +158,8 @@ Catalog source is not proof that a target can install or run a driver.
| solis | 2.1.1 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
| solis_string | 1.1.3 | ftw-core | not_assessed | — | not_recorded | not_assessed |
| solis_string | 1.1.3 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
| sonnen | 2.0.3 | ftw-core | not_assessed | — | not_recorded | not_assessed |
| sonnen | 2.0.3 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
| sonnen | 2.1.0 | ftw-core | not_assessed | — | not_recorded | not_assessed |
| sonnen | 2.1.0 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
| sungrow | 1.6.1 | ftw-core | not_assessed | — | not_recorded | not_assessed |
| sungrow | 1.6.1 | blixt-l1 | not_assessed | — | not_recorded | not_assessed |
| tesla_cloud | 0.2.0 | ftw-core | not_assessed | — | not_recorded | not_assessed |
Expand Down
8 changes: 4 additions & 4 deletions devices.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2175,8 +2175,8 @@ manufacturers:
protocols:
- protocol: http
driver: "sonnen"
version: "2.0.3"
version: "2.1.0"
ders: [battery, meter]
control: false
firmware_versions: ""
notes: "Community driver, untested"
control: true
firmware_versions: "1.40.5"
notes: "Battery sign and manual-mode setpoints measured on one unit (software 1.40.5). Control is not yet HIL-accepted."
Loading