Documentation · 3.8.1
Automations and notifications
Make TedEnergy react to your conditions (time, battery level, weather, Tempo day…), act on Home Assistant and be notified, without writing a line of code.
Documentation up to date with TedEnergy 3.8.1.
The principle
An automation says: “when these conditions are true, then TedEnergy does this”. It is made of conditions, effects applied while conditions are true, and actions run at the start and the end. Everything is built on the Automations page, with a visual editor.
Examples: keep the battery during off-peak hours, keep a reserve at night, limit an inverter at certain times, switch to holiday mode, switch an appliance on with surplus solar, warn when an inverter is in error.
Conditions
Conditions combine with AND and OR, in nested groups. Each condition compares a variable with a value or another variable:
- TedEnergy variables: powers (solar, house, grid, batteries), battery levels, current mode, each inverter's state (error, pause, starting, fallback connection), the day's balance, next tariff period, sunrise and sunset, solar forecast, equipment, charging station…
- Device values: each device exposes stable values (level, power, temperature…) that do not change even if its connection changes. Connector values (cloud, local API, MQTT) and Home Assistant entities are also usable.
- Date and time: compared in time (a date with time zone, “01/11/2026 14:08”, “22:30”), with functions (hour, weekday, hours remaining until, since…) and an offset (± minutes, hours, days). Example: “now ≥ next calibration − 12 h”.
- Drag and drop (or a menu) lets you reorganise conditions and groups.
An unknown value (device unreachable, not yet received) makes the condition false, unless you tick “decide nothing when a value is unknown”: the automation then does nothing rather than decide on a missing value.
Effects on regulation
While conditions are true, an automation can apply one or more effects, on the whole regulation, all inverters, one inverter, a cluster or a zone:
- Forced standby: no setpoint sent any more.
- Discharge blocked or charge blocked: the direction is forbidden.
- Forced charge: batteries charge from the grid, like during a scheduled slot.
- Disabled or enabled: like the switch on the Inverters page.
- Limited charge or limited discharge to a given power.
- Imposed minimum or maximum level for the battery.
- Imposed setting: a setting of the Settings page takes a value while the condition lasts, then gets its own back.
- Imposed value on a Home Assistant entity or a device: it takes the chosen value at the start and goes back to the previous one at the end.
If two automations impose different values on the same target, they are flagged as competing: each has a priority (1 wins). Competing ones are flagged on each line with a link to the other.
Actions
At the start and end of an automation, TedEnergy can also run actions: write a value to a Home Assistant entity, call a Home Assistant service (with its data), send a webhook (address, method, content, headers), or write to the log. A failed action is retried several times. Variables such as the automation's name or the time can be inserted in a webhook's content.
Delays and stability
- After X seconds of true condition: avoids reacting to a brief spike.
- Delayed end: the effect carries on for a while after the condition turns false.
- Minimum delay between two starts: avoids repeated triggering.
- Stay active at least N minutes: the automation keeps its effects a minimum time after its start, even if the condition drops.
- After TedEnergy restarts, automations resume where they were and leave measurements a short time to arrive.
Templates, folders and editing
- Ready-made templates (off-peak: keep the battery, at night: keep a reserve, surplus solar to an appliance, car charging, limit an inverter at night, maintenance, absence…) create an automation to adapt.
- You edit one automation at a time in a window: save, duplicate, delete, test (what would it do now?) and run its actions. Changing one automation is never blocked by another, incomplete one.
- A switch on each line enables or disables it at once.
- Automations are filed in folders (one level) to find your way; the display order is the filing order.
- The library lets you import automations shared by other users and share yours (with your ted-energy.fr account).
History and simulation
Each automation shows its last activity and keeps a history of its triggers. A simulation replays it on the past to see when it would have triggered before enabling it; it flags variables missing from the history.
Notifications
The Notifications and log page gathers what TedEnergy has to tell you. Notification rules work like automations: conditions, a message, and the choice of a phone notification (Android app). TedEnergy also sends system notifications: license, update, PDF report, inverter in error, protection triggered.
- Tabs: notifications, warnings and errors, settings change history (who changed what, and from where: local interface, app, remote access, support), inverter log.
- The inverter log notes every state, mode and setpoint change, with the reason; it can be downloaded, like the main logs, with a diagnostic package.
- The Store's Anomaly alerts feature offers ready-made alerts (see The Store).
Using TedEnergy values in Home Assistant
TedEnergy can make its values available to Home Assistant, read-only: through a local API (a home-network address) or by publishing them over MQTT. Your Home Assistant automations can then rely on solar power, battery levels, the current mode… without Home Assistant being able to command anything. The full guide, with the list of values and examples, is in Help › Using TedEnergy values in Home Assistant in the interface.
Frequently asked questions
How many automations can I create?
The number depends on your license (see License and account). If the limit is exceeded, the last ones in the list are disabled, with a warning.
My automation does not trigger.
Open it and use Test: TedEnergy shows each condition's value. Also check that it is enabled, that no variable is unknown and that the configured delays have elapsed.
Two automations contradict each other.
They are flagged as competing. Set their priority, or merge them into one.
Ready to make all your batteries work together?
Free download: your free license arrives as soon as your email address is confirmed, no credit card required.