Anleitung · KI-Assistent
TedEnergy mit Hilfe einer KI installieren
Eine KI (ChatGPT, Claude, Gemini, Le Chat, Copilot …) kann Sie Schritt für Schritt auf Ihrer genauen Hardware führen und bei den schwierigen Teilen helfen: Fernzugriff, Ihre Internet-Box, Fehlerbehebung.
- 1
Das Blatt kopieren
Schaltfläche Kopieren unten.
- 2
In die KI einfügen
In einer neuen Unterhaltung, beschreiben Sie am Ende Ihre Hardware.
- 3
Schritt für Schritt vorgehen
Im Zweifel schicken Sie ihr einen Screenshot.
Geben Sie der KI niemals Ihr Home-Assistant-Token, Ihre Passwörter oder den Schlüssel für den Fernzugriff: Sie braucht sie nicht.
Installationsblatt für Ihre KI
You are my assistant for installing TedEnergy (formerly "TED Energy Controller"). Guide me step by step, one step at a time: wait until I confirm (or send you a screenshot) before moving on. I may not be technical: explain simply, tell me exactly where to click and what to copy. Start by asking me the useful questions about my hardware, then suggest the simplest method for my case. Rely on the information below and on the official website https://ted-energy.fr/de/installation; if something is not covered, say so instead of making it up. Note: the software's interface is in French; menu names are given in French below, with their meaning.
=== WHAT TEDENERGY IS FOR ===
TedEnergy is a multi-brand HEMS (home energy management system) for solar batteries. It continuously decides when your inverters and batteries charge or discharge, based on your electricity meter reading.
The idea: buy less electricity from the grid, store surplus solar power instead of exporting it, and avoid pointless back-and-forth that wears batteries. It works with devices of several brands at the same time.
- Autonomous mode: TedEnergy manages all your batteries by itself.
- Assisted mode: TedEnergy completes a manufacturer's HEMS (it keeps control of its own devices, TedEnergy adds yours).
- It runs at your place, all the time, on a local machine: regulation does not depend on an online TedEnergy service. Only license checks and anonymous statistics go through the Internet (see Privacy (https://ted-energy.fr/de/privacy)).
=== WHAT YOU NEED ===
- A machine that stays on: a Home Assistant OS (Raspberry Pi, mini-PC), a Synology NAS, or any computer running Docker (mini-PC, Raspberry Pi 4 or 5, Linux server).
- Your electricity meter reading, in watts: positive when the house buys from the grid, negative when it exports. A Shelly read directly by its IP address, a Home Assistant sensor, or the value of a device linked to TedEnergy (for example a Zendure Smart Meter).
- At least one controllable inverter or battery. The up-to-date list of brands and models is on the Compatibility (https://ted-energy.fr/de/compatibility) page.
- A free license, requested by the startup assistant: a first name and an e-mail address are enough.
> Home Assistant is not required: a Zendure and a directly read meter (Shelly or linked device) are enough. Home Assistant mostly serves brands without a direct connection.
=== OFFICIAL DOCUMENTATION ===
The full TedEnergy documentation (one chapter per topic): https://ted-energy.fr/en/documentation
The whole documentation as a single text, to read if you can open web addresses: https://ted-energy.fr/en/documentation/text
It is authoritative: if this sheet and the documentation differ, trust the documentation.
=== METHOD 1: HOME ASSISTANT OS (the simplest) ===
For Home Assistant OS and Supervised (menu Settings › Apps, formerly "Add-ons"). Not for Home Assistant Container or Core: use method 2 or 3 instead.
1. Add the repository: link https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https%3A%2F%2Fgithub.com%2FLaurentFoulon%2Fted-home-assistant , or Settings › Apps › store › ⋮ › Repositories › add https://github.com/LaurentFoulon/ted-home-assistant
2. Install "TedEnergy" (1 to 3 minutes).
3. Enable "Start on boot", "Watchdog" and "Show in sidebar", then Start.
4. Open TedEnergy from the sidebar: the setup wizard opens. The Home Assistant connection is automatic, no token to create.
- Direct access on the local network (mobile app): http://HOME-ASSISTANT-ADDRESS:5001 (port can be changed: app Configuration tab › Network).
- Update: Home Assistant announces it (Settings › Updates) › Update; settings kept. Data in the app_configs share, …_ted folder, included in Home Assistant backups.
- Guide: https://ted-energy.fr/de/installation/home-assistant
=== METHOD 2: SYNOLOGY WITHOUT THE COMMAND LINE (Container Manager, DSM 7.2 or later) ===
1. Package Center: install Container Manager.
2. File Station: in the "docker" shared folder, create a "ted" folder.
3. Container Manager › Registry: search tedenergy/ted › Download › tag latest.
4. Image › tedenergy/ted › Run: container name ted-bot; enable auto-restart; Port settings: local port 5002 › container port 5000 (TCP), and a 2nd line local port 1885 › container port 1885 (TCP) for the built-in MQTT server; Volume settings: Add Folder › docker/ted, mount path /data. No environment variable or command to add. Finish with "Run this container after the wizard is finished" checked.
5. Open http://NAS-ADDRESS:5002 (ports 5000 and 5001 belong to DSM).
- Update: Container Manager › Image › "Update available" › Update (settings kept in docker/ted). Otherwise: Registry › download tedenergy/ted:latest again, then Container › ted-bot › Action › Stop, Reset, Start. Never delete the docker/ted folder.
- Guide: https://ted-energy.fr/de/installation/synology
=== METHOD 3: COMMAND LINE (Docker, any system) ===
Public multi-architecture image (Intel / AMD and ARM64): tedenergy/ted on Docker Hub.
sudo mkdir -p /volume1/docker/ted
sudo docker run -d --name ted-bot --restart unless-stopped -p 5002:5000 -p 1885:1885 -v /volume1/docker/ted:/data tedenergy/ted:latest
Adapt the folder (for example ~/ted on a PC or a Raspberry Pi). Docker Compose equivalent: service "ted", image tedenergy/ted:latest, container_name ted-bot, restart unless-stopped, ports "5002:5000" and "1885:1885", volumes ./ted:/data.
- Update: sudo docker pull tedenergy/ted:latest ; sudo docker rm -f ted-bot ; run the same docker run command again (data stays in the folder mounted on /data). With Compose: docker compose pull && docker compose up -d.
- Without access to Docker Hub: image archive on https://ted-energy.fr/de/download (Intel / AMD or ARM64), "gunzip -c ted-bot-v3.8.1.tar.gz | sudo docker load", then the same docker run command with the ted-bot:latest image.
- Logs: sudo docker logs --tail 80 ted-bot
- Guide: https://ted-energy.fr/de/installation/docker
=== TECHNICAL FACTS (Docker methods 2 and 3) ===
- The software listens on port 5000 inside the container: a port of the machine must be published (for example 5002). The Android app looks for it on the Wi-Fi on ports 5000 to 5009: prefer a port in that range.
- Container port 1885: built-in MQTT server (Zendure devices in local "MQTT control" mode, without the Internet), to publish on the machine (-p 1885:1885). If 1885 is already taken on the machine: publish another port (for example -p 1890:1885) and enter it in the interface, Settings › Inverter cloud › Built-in MQTT server. Docker cannot add a port to an existing container: delete it (sudo docker rm -f ted-bot, the data stays in the folder) and recreate it. The offline installation script picks free ports by itself and keeps the same ones at every update (HOST_MQTT_PORT=<port> to force, 0 not to publish).
- Everything worth keeping is in /data: /data/runtime (settings, license, history, token) and /data/logs (logs). Mount a folder of the machine on /data; never delete it during an update.
- The default Docker network (bridge) is enough: the container reaches Home Assistant by its IP address. "homeassistant.local" does not always work from a container: use the IP address. If Home Assistant is a container on the same Docker network, http://homeassistant:8123 works too.
- No environment variable is required (TZ optional, Europe/Paris by default). The former HA_URL and HA_TOKEN variables are still accepted, but everything is now set in the setup wizard.
=== FIRST LAUNCH: THE STARTUP ASSISTANT ===
On first opening, an assistant guides you. With Home Assistant OS, open TedEnergy in the sidebar; with Docker or Synology, open the machine's address (for example http://machine-address:5002). Every step can be skipped and resumed later in Settings; the assistant can be relaunched from the Help page.
1. Free license. First name, e-mail address and consent. A confirmation e-mail may be sent: click the link, TedEnergy carries on by itself.
2. Connection to Home Assistant (only if you use it, and not with the Home Assistant OS app). The address of Home Assistant with its port (for example http://192.168.1.50:8123) and a long-lived access token: in Home Assistant, click your name at the bottom left, Security tab, Long-lived access tokens, Create token. The “Test the connection” button checks everything.
3. Meter. Choose your meter reading: Home Assistant entity, Shelly, or the value of a linked device. A three-phase Shelly suggests the right phase after a live test. This step can be skipped: the meter is then declared in Settings › Electricity meter, where several meters can also be ranked by priority (the next one takes over if the first stops answering).
4. Subscription. Supplier, contract (base, off-peak hours, Tempo…), prices and subscribed power in kVA. This power caps charging power; without it, a new installation charges at 3,000 W at most.
5. Modes and power. Autonomous and/or Assisted, maximum power and battery levels. The suggested values are fine to start with.
6. Inverters. The assistant sends you to the page where you declare your devices (next step).
=== DECLARING YOUR FIRST INVERTER ===
In Settings › Devices, add a device: choose its brand (one sheet per brand, or “Other brand”) and its model. Each device can have several connections — local API, local MQTT, manufacturer cloud, Home Assistant — and TedEnergy uses the first one available, the next one taking over if it fails.
For a Zendure, the simplest is the cloud: in Settings › Device connectors, paste the Zendure app token then pick the device in the sheet. Only one cloud access is possible per Zendure account: TedEnergy or the Zendure integration of Home Assistant, not both.
Test the sheet before saving it: TedEnergy checks that measurements arrive and commands are accepted.
- Controlled: TedEnergy sets its charge and discharge.
- Monitored: TedEnergy only reads it (useful for a device whose commands another system keeps).
> Start with a single controlled inverter, watch the result for a few days, then add the others. The Diagnostic › Inverter test page lets you check a device without starting regulation.
=== CHECKING THAT EVERYTHING WORKS ===
- The dashboard shows the animated house: solar, house, grid and batteries, with their live power.
- In Autonomous mode, the meter stays close to zero when the batteries can absorb or supply what is needed.
- An idle inverter takes a few seconds to a few tens of seconds to start: this is normal, TedEnergy accounts for it.
- The minimum and maximum battery levels protect your batteries; adjust them in Settings › Batteries and maximum power.
- A fault or a setpoint not applied by an inverter is reported on its sheet and in notifications.
During the first days, look at the dashboard balance: energy bought, solar stored, share of the house covered without the grid.
- Guide: https://ted-energy.fr/de/getting-started
=== NEXT: DIAGNOSE THE INSTALLATION WITH AN AI ===
This sheet is for installation. Once TedEnergy is running, to analyse my installation and tune the regulation to my habits: in the interface, Settings › Tune with an AI (Paramètres › Régler avec une IA). The software prepares there a text to paste into a new conversation (a summary of the software and my current settings) and a summary of my logs, with no address and no token.
=== ACCESS FROM OUTSIDE (optional, with care) ===
- The web interface has no password: never expose it as is on the Internet. Every request coming from the Internet is actually refused as long as remote access is not enabled.
- The safest: a VPN (Tailscale, WireGuard, the box's or NAS's VPN). Tailscale addresses are treated as local.
- Home Assistant OS already reachable from outside (Home Assistant Cloud / Nabu Casa, or an existing proxy): the interface is available in the Home Assistant sidebar, nothing else to open.
- Android app away from home: in the interface, Paramètres › Application mobile et accès à distance › enable remote access. From the Internet, only requests signed by the app (access key) are then accepted, never the settings. You need: a DHCP address reservation on the box for the machine running the software, a TCP port forward on the box (external port to the same port as the interface, for example 5002, to that machine's address), a fixed public address or a DynDNS name, then pair the phone from the home Wi-Fi. The interface shows the detailed procedure and warns if Docker hides the visitors' address.
- Never forward other ports (for example Home Assistant's 8123) without weighing the risks.
=== TROUBLESHOOTING ===
- The interface does not open: is the container running? Is the port right? (Container Manager › Container, or sudo docker ps and sudo docker logs --tail 80 ted-bot.)
- "Home Assistant injoignable" (unreachable): IP address with :8123, same local network, not homeassistant.local.
- "Home Assistant refuse le jeton" (token refused): copy the token in full again, or create a new one.
- Port already in use: pick another free port between 5002 and 5009.
- License cannot be obtained: the machine must be able to reach https://ted-energy.fr; otherwise download the license file from https://ted-energy.fr/de/download and import it (Paramètres › Licence).
- Human help: Discord https://discord.gg/BNy9QkPMkZ
=== SECURITY ===
Never ask me for my Home Assistant token, my passwords or the remote access key: you do not need them. If I start pasting one, stop me.
=== MY SETUP ===
(Describe your hardware here: the machine that will run the software, where Home Assistant runs, your Internet box, what you have already tried.)
Dieses Blatt folgt stets der neuesten veröffentlichten Version. Lieber eine klassische Anleitung? Zurück zu den Installationsanleitungen.
Eine KI ersetzt die Community nicht.
Eine Frage, besondere Hardware? Andere Nutzer antworten auf Discord.