From 4a4e4789bea099c4b46f64afbfb7833d01434df9 Mon Sep 17 00:00:00 2001 From: Claude Opus 5 Date: Wed, 5 Aug 2026 12:12:00 +0200 Subject: [PATCH] content: say that OCPP chargers need no driver, and link the guide MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit FTW ships an OCPP 1.6J + 2.0.1 central system, so a charger that speaks either connects with no Lua driver. The site never said so — a visitor asking "do I need a driver for my charger?" had no way to find out. Folded into the existing integrations card rather than a seventh one: the capability grid is repeat(3, 1fr), so a seventh card would leave a single card stranded on its own row. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> --- index.html | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/index.html b/index.html index eec5aca..42f9242 100644 --- a/index.html +++ b/index.html @@ -4,8 +4,8 @@ FTW | Open-source home energy management - - + + @@ -161,7 +161,7 @@

One local system across mixed hardware.

Coordinated out

Battery + invertercharge / discharge
-
EV chargingload / V2X
+
EV chargingOCPP / V2X
API + Home Assistantobserve / automate
@@ -210,8 +210,8 @@

Keep the history

06 / CONNECT

Open integrations

-

Use the HTTP API, Home Assistant MQTT discovery and Lua drivers to connect the rest of your home.

- HTTP · MQTT · Lua +

Use the HTTP API, Home Assistant MQTT discovery and Lua drivers to connect the rest of your home. OCPP 1.6J and 2.0.1 chargers need no driver at all.

+ HTTP · MQTT · OCPP · Lua
@@ -226,9 +226,11 @@

New hardware should be a driver, not a fork.

  • Start from an existing inverter, meter or charger driver
  • Test with simulators and the same public host API
  • Contribute the integration back through a pull request
    • +
  • Skip the driver entirely for an EV charger that speaks OCPP
    • Write a driver + OCPP chargers Browse drivers