If you would like to contribute extensions to this, please submit the pull request in the dev branch. For bug fixes, the pull request can also be made on the main branch
This is a Python 3 Application that turns on your ESS unit (controller) at the right time when your hourly dynamic energy prices are low. Or used for discharging when prices are extremely high.
Since 2025 the European spot markets deliver 15-minute prices via ENTSO-E. SEUSS works internally on quarter-hour items but groups them into clusters of a configurable length (charging_block_minutes, discharging_block_minutes, switching_block_minutes, default 60 min) for selection and switching. Within tariff_resolution: hourly (the default for typical Awattar/Tibber retail tariffs), the four quarters of an hour share the average price so clusters land on full hours.
Why this matters:
- ⚖ Tariff-aware: Hourly billing? Use
tariff_resolution: hourlyand quarters within an hour are treated equally — clusters align to full hours, just like before. Quarterly billing? Switch toquarterlyand SEUSS uses the real 15-min spread. - ⏱ Configurable cluster length: Whether you want 60-minute charge clusters or 30-minute ones is now a config setting, not hard-wired.
- 🔌 Predictable totals:
8 charge × 60 min + 16 discharge × 60 min = 24 h fully covered. The optionalfill_gaps_with_short_clusterskeeps the day contiguous when sliding-window placement leaves small slivers. - 🛠 Hardware stability: The hard cap is checked per quarter, so a single expensive 15-min slot in an otherwise cheap cluster pauses charging without breaking the cluster apart visually (it shows olive in the chart).
For a detailed explanation of the cluster model, see the full design note.
- Victron Venus OS energy storage systems such as the MultiPlus II series
- aWATTar
- Entso-E
- Tibber
The control of the ESS unit (controller) is done via mqtt. The advantage of this control is: that this application does not have to run directly on VenusOS. Direct control with D-BUS is in the works
This version was successful with
- Linux Ubuntu >= 22.04
- Venus OS Raspberry >= v3.12
tested
Download the installation script from the GitHub repository execute the following command in your terminal:
wget -O seuss_install.sh https://raw.githubusercontent.com/ckvsoft/SEUSS/dev/scripts/seuss_install.sh`
Run the installer script with additional options to prepare everything in a subdirectory for your inspection. For example:
bash seuss_install.sh`
The default directory is /data/seuss (Venus OS) But you can optionally specify a different directory by using the environment variable TARGET_DIRECTORY e.g.
TARGET_DIRECTORY=/opt/seuss bash seuss_install.sh`
On a Cerbo GX the filesystem is mounted read only. See https://www.victronenergy.com/live/ccgx:root_access. In order to make the filesystem writeable you need to execute the following command before running the installation script:
/opt/victronenergy/swupdate-scripts/resize2fs.sh
After SEUSS has been successfully installed, a website is available at the IP address and port 5000 of
the Computer/VenusOS on which SEUSS was installed.
- You can view or download the log file.
- Furthermore, the configuration can be carried out using the [Config Editor] menu item.
- Tool tips for most points are displayed here.
These can also be found in the Settings description. For those who prefer to work in a config file, there is config.json
| Setting | Meaning |
|---|---|
time_zone |
Essential for correct timing of operations based on your geographic location. Format like Europe/Vienna, Europe/Amsterdam, ... |
tariff_resolution |
How your contract bills the electricity. hourly (default) — billing is per hour even if the spot data is quarter-hour (typical Awattar / Tibber retail tariffs). The four 15-minute prices of an hour are averaged so cluster selection lands on full hours.quarterly — true 15-minute billing; clusters may start on :15, :30 or :45 of an hour. |
log_file_path |
Sets an alternative path to which the log files are saved. |
log_level |
Used Loglevel are: INFO, WARNING, ERROR and DEBUG. see Log Levels |
Please change prices (always use Cent/kWh, no matter if you're using Awattar (displaying Cent/kWh) or Entsoe API (displaying EUR/MWh) / net prices excl. tax).
Since the move to 15-minute spot data, SEUSS works internally on quarter-hour items but groups them into clusters (= contiguous blocks) for charging, discharging and switching. Each cluster is exactly the configured *_block_minutes long. The number of clusters is the corresponding number_of_*_prices_* setting. So 8 charge clusters × 60 min = 8 hours of charging.
When sliding-window placement (tariff_resolution: quarterly) leaves small gaps between charge and discharge clusters, the optional fill_gaps_with_short_clusters covers those slivers with shorter discharge blocks so the chart paints contiguously when the totals add up to 24 h.
| Setting | Meaning |
|---|---|
use_second_day |
enable/disable to compare today and tomorrow prices if they become availableNote: If you activate this and the prices decrease over several days,it is possible that there will be no charging or switching for several days until the lowest prices are reached. |
number_of_lowest_prices_for_charging |
Number of cheapest charge clusters per day, where each cluster is charging_block_minutes long.mode 1 (integer): the literal number of clusters, e.g. 8 with charging_block_minutes=60 gives 8 hours of charging per day.mode 2 (decimal in (0, 1)): thresholding mode, e.g. 0.85 selects every cluster whose average is below 85% of the day average — the count is computed.Legacy: 1.0 is treated as "1 cheapest cluster" (the old "100% of average" interpretation never made sense and is preserved as integer-1).Sanity tip: if charging + discharging ≠ 24 (with *_block_minutes=60), SEUSS logs a startup WARNING so you know hours will be left unassigned (grey in the chart) or that the total exceeds the day. |
number_of_highest_prices_for_discharging |
Number of most expensive discharge clusters per day, each discharging_block_minutes long. Same dual-mode semantics as the charging counterpart (integer = literal count, decimal >1 = "above X×day-average"). |
number_of_lowest_prices_for_switching |
Independent cluster count for smart-switch operation. 0 (default) falls back to number_of_lowest_prices_for_charging. Set this when your smart switches should run on a different schedule than the ESS charging window (e.g. boilers that need longer runs). |
charging_block_minutes |
Length of each charging cluster in minutes. Multiples of 15, no upper limit. Default 60 keeps the historical hour-cluster behaviour. Smaller values trade against switching-cycle wear. |
discharging_block_minutes |
Length of each discharging cluster in minutes. Same rules as charging_block_minutes. |
switching_block_minutes |
Length of each smart-switch cluster in minutes. |
fill_gaps_with_short_clusters |
When sliding-window cluster placement leaves a gap of less than *_block_minutes between two selected blocks, fill it with a shorter discharge cluster (15 / 30 / 45 min). Default true. Disable to keep cluster lengths strictly equal to *_block_minutes and accept small white slivers in the chart. |
charging_price_limit |
Charging is always enabled when the per-quarter price is below this value, regardless of cluster selection. Use this as a "safety floor": below this price, always charge. |
charging_price_hard_cap |
Charging is strictly prohibited when the per-quarter price exceeds this value. Checked per quarter (not per cluster average), so a single expensive 15-minute slot inside an otherwise cheap cluster still pauses charging for that quarter. The chart paints such quarters olive instead of green so you see them at a glance. Only active with charging_strategy: cap. |
charging_strategy |
cap (default, classic behaviour) or economic. With economic, the hard cap is replaced by the marginal displaced price rule: SEUSS charges whenever quarter_price / round_trip_efficiency is below the price of the most expensive hour an additional charged kWh would displace (merit-order stack of the upcoming expensive phase, capped by usable SOC + what the remaining charge window can deliver at the auto-detected charge power). Charges above the old cap on price-spike days (cheaper than direct grid purchase) and skips below the cap when the battery already bridges to a cheaper window. skip_charge_when_cheaper_cluster_coming and skip_charge_when_battery_covers_expensive_phase are subsumed and ignored in this mode. |
economic_price_ceiling |
Absolute price leash (Cent/kWh) for charging_strategy: economic. Pure data-error protection (bogus feed prices) -- NOT an economic decision. Default 60. |
round_trip_efficiency |
Charge+discharge+inverter efficiency used by the economic rule (default 0.90). The charge price is divided by this before comparing against the displaced price. Also written once to the Victron SystemEfficiency setting when the dynamic_ess backend is active. |
Charge power is auto-detected (no config key): the economic rule prefers the measured grid-charge power (last_grid_charge_power_w, auto-calibrated during grid-charge sessions, 7-day freshness); without a measurement it derives the capability from the GX/BMS (min of Max charge current setting and BMS CCL × pack voltage), falling back to a conservative built-in default. The legacy charge_power_watts key is ignored and hidden in the editor.
| control_backend | How SEUSS controls the Victron: auto (default) detects the firmware and prefers dynamic_ess; classic toggles Schedule/Charge Day + MaxDischargePower (SD-backed localsettings writes); dynamic_ess pushes hourly target-SOC slots into the Victron Dynamic ESS scheduler (Mode 4, officially reserved for third-party controllers). The schedule mirrors the active strategy's price rule -- a window the strategy would refuse (hard cap in cap mode, marginal threshold in economic mode) becomes a hold slot, and the window containing "now" follows the live abort decision of each evaluation cycle. In dynamic_ess mode SEUSS never writes MaxDischargePower -- it stays a user-owned pure power limit. Do NOT combine dynamic_ess with VRM Dynamic ESS or the Victron scheduled-charge menu (they fight over the same scheduler). |
| use_solar_forecast_to_abort | When enabled, charging is aborted while two conditions both hold: (a) the combined adjusted solar forecast for today + tomorrow covers at least two days of average consumption, AND (b) the current battery SOC alone covers consumption until tomorrow's sunrise (with a 10% safety buffer). Either condition alone has known failure modes (forecast-only drains the battery overnight; SOC-only ignores a streak of bad-weather days), so both must hold. Falls back to "charging allowed" on any missing data. Default false. The accuracy of the underlying solar forecast is governed by the solar_adj_* settings below. |
| skip_charge_when_battery_sufficient | DEPRECATED, hidden in the editor -- replaced by skip_charge_when_battery_covers_expensive_phase, which uses a broader, more correct horizon. Original behaviour preserved for backward compatibility: skips charging when current usable SOC covers consumption until the next equally-cheap-or-cheaper charge cluster. Default false. |
| skip_charge_when_battery_covers_overnext | DEPRECATED, hidden in the editor -- logically redundant with the above (if SOC doesn't reach the next cheap cluster it can't reach the overnext one either). Default false. |
| skip_charge_when_battery_covers_expensive_phase | When enabled, charging is skipped if the current usable SOC alone covers consumption until the next charge cluster of any price -- i.e. for the entire upcoming expensive phase until SEUSS would actively charge again. Conservative: doesn't model recharge from the next cluster, only counts what's in the pack now. Recommended successor to the two flags above. Default false. |
| smart_discharge_priority_to_expensive_hours | When enabled and the battery's usable SOC isn't enough to cover the full upcoming expensive phase, SEUSS prioritises discharge to the most expensive blocks only; cheaper expensive-phase blocks are skipped (grid covers those hours instead). The pack thus saves energy for the priciest hours. The decision is recomputed each evaluation cycle as SOC changes. Default false. |
| skip_charge_for_upcoming_negative_prices | When enabled, SEUSS skips a current (positive-price) charge attempt if there are future quarters in today's or tomorrow's price list priced below zero ct/kWh AND the battery will have enough free capacity to absorb that "you-get-paid-to-charge" energy later. The intent is to keep headroom in the pack for the negative-price window, not to pay for charging now and then have no room for the free slot. The check is conservative: if the current quarter is itself already negative, charging is NEVER skipped (we want to grab as much free energy as possible). If the negative window is too long to fit into the available headroom, current cheap charging is also allowed because the pack couldn't absorb it all anyway. Does NOT control grid export, feed-in, or what SEUSS does during the negative window itself -- it only delays positive-price charging in anticipation of an upcoming negative one. Default false. |
| skip_charge_when_cheaper_cluster_coming | When enabled, SEUSS skips the current charge attempt -- even while inside a cheap cluster where it would normally charge -- if a strictly cheaper future charge cluster exists AND a forward simulation says the plan is safe. The simulation walks the pack's SOC across the entire remaining chain of charge clusters: between clusters it drains at the recent average consumption plus it credits the solar forecast (today's hourly forecast; tomorrow's total spread across 08-18h), and inside each cluster it recharges at the last measured grid-charging power (last_grid_charge_power_w, auto-calibrated whenever grid and battery power are simultaneously positive). Only if the simulated SOC never drops below zero does SEUSS skip -- otherwise it charges now. Typical effect: at 10:00 in a 23 ct cluster with 19 ct coming at noon and PV feeding the pack, SEUSS waits for the cheaper block instead of paying the extra 4 ct. Requires at least one prior grid-charge cycle for calibration and consumption history; until then the option never skips. The charging_price_limit floor always wins (prices at/below it are never skipped). Default false. |
| cheaper_cluster_min_reserve_hours | Safety reserve for the skip_charge_when_cheaper_cluster_coming simulation, expressed in hours of average consumption. The simulated SOC must stay above this margin at every point of the chain -- on top of the pack's configured minimum SOC, which is already subtracted before the simulation starts. Protects against forecast and consumption estimation errors: with the default of 2.0, skipping is only allowed when the plan keeps at least two hours of typical consumption in the pack as headroom above the minimum. Set to 0 to restore the old skip-at-exactly-zero behaviour. |
| solar_adj_ewma_alpha | Smoothing factor for the solar forecast adjustment factor (adjustment_factor in stats). Range 0.0–1.0. Each day's observed-vs-forecast ratio enters the persisted multiplier with weight alpha; the prior value keeps weight 1 - alpha. Default 0.3 (moderate smoothing). 1.0 reproduces the legacy behaviour (each day overwrites the factor). 0.0 freezes the factor at its current value. |
| solar_adj_min_theoretical_wh | Minimum theoretical net yield (Wh) accumulated since 00:00 before SEUSS will update the adjustment factor on a given evaluation. Default 1000. Lower values learn earlier in the day but react more strongly to morning weather quirks; raise this if your forecast tends to over-correct on cloudy mornings. |
| solar_adj_min_sun_hours | Minimum hours past local sunrise (approximated as hours past 06:00) before SEUSS will update the adjustment factor. Default 4.0. Pairs with solar_adj_min_theoretical_wh -- both conditions must be met. Set higher in regions with very late sunrise. |
| solar_adj_max_daily_change | Maximum absolute change of the adjustment factor per evaluation. Default 0.20 (i.e. ±20% per day). Set to 0 to disable the cap. Prevents a single freak day from yanking the factor across its full [0.2, 2.0] range. |
| delay_grid_charging_below_active_soc_limit | Prevents charging from the grid when it returns if SOC is below the Active SOC Limit and electricity prices are high. |
| discharge_fallthrough_on_charge_veto | When a charge window matches but the charge is vetoed (economic marginal rule, SOC target, outlier leash), let the battery fall through to the regular discharge rules instead of idling for that window. Default false (historical pause behaviour). SOC protection is unchanged: the surplus / phase-required planner math still decides what the discharge may use. |
The price chart in the SEUSS web UI now shows quarter-resolution colours on top of the hourly bars:
- Green — quarter is part of an active charging cluster and the per-quarter price is under the effective ceiling (
charging_price_hard_capincapstrategy,economic_price_ceilingineconomicstrategy). Past hours show as darker green. - Olive — quarter is part of a charging cluster but the price rule blocks it (hard cap in
capstrategy, marginal-price rule ineconomicstrategy), so SEUSS will skip that 15-minute slot. Distinguishes "would charge but blocked" from "unrelated grey hour". - Red — quarter is part of an active discharging cluster. Past hours show as darker red.
- Grey — quarter is not part of any cluster (because
charging + dischargingtotals don't cover 24 h).
When fill_gaps_with_short_clusters produces a 3-quarter discharge or charge block (e.g. 12:00–12:45) the leftover quarter (12:45) inherits the hour's block colour instead of falling through to grey, so each block-hour paints solid red or green.
Hovering over an hour bar shows a tooltip with the four real per-quarter prices for that hour — useful when tariff_resolution=quarterly makes them differ.
The chart text adapts automatically to light and dark mode via the chart-text CSS class in views/static/styles.css.
Machine-readable price snapshot (current quarter price, cheap-block flag, hourly price curves for today/tomorrow with per-hour colour flags, effective hard cap). Built for external displays/controllers such as a thermostat.
Battery + decision snapshot, refreshed every evaluation cycle (RAM-only, no SD writes):
{
"state": "charging", // "charging" | "discharging" | "idle" | "unknown" (before first cycle)
"soc_percent": 52.0,
"soc_wh": 9330.0,
"capacity_wh": 17900.0,
"min_soc_percent": 10.0,
"control_backend": "dynamic_ess",
"charging_strategy": "economic",
"current_price": 38.05,
"charge_condition": "lowestprice_block_2 ... active",
"discharge_condition": "Discharge allowed: ... surplus ...",
"economic": {
"marginal_price": 45.0, // ct/kWh the next charged kWh would displace
"threshold_quarter_price": 40.5, // charge while quarter price is below this
"basis": "stats", // "stats" | "fallback" | "no-phase" | ...
"round_trip_efficiency": 0.9,
"charge_power_w": 2500.0,
"charge_power_source": "measured"
},
"timestamp": "2026-09-29T08:35:11"
}Check timestamp for staleness before acting on it — the value only updates while the SEUSS evaluation loop is alive.
| Setting | Meaning |
|---|---|
use_vrm |
If this point is enabled (true), an attempt is made to connect to the Victron via the VRM portal. This requires a user/password in the VRM portal |
ip_address |
The local IP address of the Victron. This is required if use_vrm is disabled (false).Otherwise this field remains empty |
unit_id |
VRM Portal ID can be found in the Settings / VRM online portal / VRM Portal Id.Note: This ID is required to access the Victron even if you are not using a VRM portal |
user |
mail adress you use to connect to VRM portal |
password |
password you use to connect to VRM portal |
max_discharge_power |
Default: -1 If you use Limit inverter power in the ESS menu then this value must be entered here.If the inverter is set to Discharge false by this app then this value will be overwritten in the ESS.This limit here is set in discharge mode in the ESS. If no limit is set then leave the value at -1.Example: Enter 1000 to limit the discharge to 1000W, Enter -1 for full PowerVenusOS ≥ 3.50: SEUSS writes this value ONCE (only if the register was 0) and then gates discharge per decision via the hub4 RAM override ( /Overrides/MaxDischargePower) -- the register itself keeps YOUR value permanently. On older firmware the register is toggled value ↔ 0 per decision (as before). |
only_observation |
If only observation is activated the essunit will only be used for statistical purposes. The essunit does not execute any conditions |
enabled |
To use this entry it must be enabled. Otherwise disabled |
Charge = the ESS Scheduled charge levels window (armed during green blocks, target = the SoC level you set in the Victron GUI). Discharge = the limit above.
- VenusOS ≥ 3.50: the per-decision gating happens through the hub4
RAM overrides (
/Overrides/ForceCharge,/Overrides/MaxDischargePower) -- zero SD writes for switching; the SD registers keep your values. - Older firmware: the SD registers are toggled per decision
(
Schedule/Charge/0/Day7/-7,MaxDischargePowervalue/0), guarded to write only on change. - SEUSS never writes
/Settings/DynamicEss/*-- the former Dynamic-ESS backend was removed 2026-10. A leftoverDynamicEss/Mode=4disables the classic "Scheduled charge levels" feature on VenusOS 3.7x (shows Inactive); set Dynamic ESS to off once if that page shows Inactive.
| Setting | Meaning |
|---|---|
country |
Choose location AT or DE |
fee |
This parameter defines the fee to be added to the base price. The fee can be specified as a percentage (e.g., 3% + 2.5 for 3% of the base price plus a fixed fee of 2.5 cents), or just a fixed amount (e.g., 2.5 for a flat fee of 2.5 cents). The fixed fee must always be specified in cents. If no fee should be applied, this field must be left empty. The final price is calculated using the formula: Final price = Base price + Fee. Please note that the price is calculated excluding tax, and the fee is already included in the final price. For the special case of "entsoe", there is no direct fee. In this case, the fee should be taken from the primary market. If "entsoe" is the primary market, the fee should be taken from the fallback market instead. |
primary |
If this market is enabled this point sets it as the primary market |
enabled |
To use this entry it must be enabled. Otherwise disabled |
| Setting | Meaning |
|---|---|
api_token |
How to get the free api_security_token: 1. Go to https://transparency.entsoe.eu/ --> register and create an account 2. Send an email to transparency@entsoe.eu with “Restful API access” in the subject line 3. The ENTSO-E Helpdesk will respond to your request within 3 working days. 4. Generate a security token at https://transparency.entsoe.eu/usrm/user/myAccountSettings |
in_domain |
To find out your in and out domain key go to: https://www.entsoe.eu/data/energy-identification-codes-eic/eic-area-codes-map/ |
out_domain |
like in_domain |
fee |
This parameter defines the fee to be added to the base price. The fee can be specified as a percentage (e.g., 3% + 2.5 for 3% of the base price plus a fixed fee of 2.5 cents), or just a fixed amount (e.g., 2.5 for a flat fee of 2.5 cents). The fixed fee must always be specified in cents. If no fee should be applied, this field must be left empty. The final price is calculated using the formula: Final price = Base price + Fee. Please note that the price is calculated excluding tax, and the fee is already included in the final price. For the special case of "entsoe", there is no direct fee. In this case, the fee should be taken from the primary market. If "entsoe" is the primary market, the fee should be taken from the fallback market instead. |
primary |
If this market is enabled this point sets it as the primary market |
enabled |
To use this entry it must be enabled. Otherwise disabled |
| Setting | Meaning |
|---|---|
api_token |
To get the tibber_api_key: 1. log in with a free or customer Tibber account at https://developer.tibber.com/settings/access-token 2. Create a token by selecting the scopes you need (select "price") 3. Use this link to create a free account with your smartphone: https://tibber.com/de/invite/ojgfbx2e |
price_unit |
Set to: "energy" to use the spotmarket-prices (default), "total" to use the total prices including taxes and fees, "tax" to use only the taxes and fees |
fee |
This parameter defines the fee to be added to the base price. The fee can be specified as a percentage (e.g., 3% + 2.5 for 3% of the base price plus a fixed fee of 2.5 cents), or just a fixed amount (e.g., 2.5 for a flat fee of 2.5 cents). The fixed fee must always be specified in cents. If no fee should be applied, this field must be left empty. The final price is calculated using the formula: Final price = Base price + Fee. Please note that the price is calculated excluding tax, and the fee is already included in the final price. For the special case of "entsoe", there is no direct fee. In this case, the fee should be taken from the primary market. If "entsoe" is the primary market, the fee should be taken from the fallback market instead. |
primary |
If this market is enabled this point sets it as the primary market |
enabled |
To use this entry it must be enabled. Otherwise disabled |
| Setting | Meaning |
|---|---|
locLat |
Latitude |
locLong |
Longitude |
angle |
Angle of your panels 0 (horizontal) … 90 (vertical) |
direction |
Plane azimuth, -180 … 180 (-180 = north, -90 = east, 0 = south, 90 = west, 180 = north) |
totPower |
Installed peak power in kWp -- the hardware ceiling above which the inverter cannot deliver, regardless of irradiance. Used as a hard cap on each hour's forecast (min(theoretical_yield, totPower * 1000)). |
total_area |
Physical surface area of the installed panels in m², as mounted on roof / ground / wall. Sum of the glass area of all modules in this group (e.g. 10 modules × 1.7 m² = 17 m²). Together with efficiency this drives the theoretical hourly yield: irradiance_W_per_m² × total_area × efficiency. Important: if you leave this at 0 (the default), the theoretical yield is 0 and the entire forecast for this panel collapses to zero -- only the totPower cap remains, and min(0, cap) = 0. So you must set both total_area and efficiency for the forecast to work, even though totPower already encodes the hardware limit. A future revision may consolidate these. |
efficiency |
Module efficiency in % (typical 18–22 for modern silicon). Multiplied with total_area to convert irradiance into Wh. You can also lower this value over time to model panel ageing or persistent partial shading without changing the physical area. |
damping_morning |
With this parameter you can adjust the result in the morning. Value float 0..1, default 0 |
damping_evening |
With this parameter you can adjust the result in the evening. Value float 0..1, default 0 |
horizon |
Season-correct horizon shading: obstruction silhouette as [[azimuth_deg, elevation_deg], ...] (compass direction of the obstruction from the panel's point of view and the elevation angle below which it blocks the sun; linear interpolation between waypoints; wraps at 360). Empty ([], default) = open sky, no shading. See Horizon shading below. |
horizon_residual |
Share of the forecast kept in hours where the sun is BEHIND an obstruction (a tree never blocks 100% -- diffuse light remains). Percent, default 15. Blocked hours get this residual instead of a hard 0. |
enabled |
To use this entry it must be enabled. Otherwise disabled |
A fixed damping_evening factor cannot distinguish seasons: a tree that
shades the array on autumn afternoons (low sun) does nothing in summer,
and a southern hill eats winter hours. The horizon profile models the
actual geometry instead -- the sun's elevation and azimuth are computed
per forecast hour (NOAA solar position, no network) and compared with
your silhouette:
"horizon": [[120, 0], [180, 8], [210, 8], [240, 25], [280, 25], [320, 0]],
"horizon_residual": 15This example reads: open sky from the east up to 180°; a hill to the south blocking everything below ~8°; a tree in the southwest blocking everything below 25° between 240° and 280°; open sky from 320°.
Measuring the values (once, from the panel position): a compass app for the azimuth of tree/hill, a free inclinometer app for the elevation of the treetop / hill ridge. Rough values are fine -- linear interpolation smooths the rest.
Behaviour: hours with the sun behind the silhouette produce
horizon_residual % of the forecast; hours above it run the normal
damping. Panels without a horizon entry behave exactly as before.
| Setting | Meaning |
|---|---|
ips |
A list of IP addresses assigned to the device. Use | to separate multiple IPs. Prefix an IP with ! to temporarily disable it without removing it from the list. Example: "10.1.1.20 | !10.1.1.21" (IP 10.1.1.21 is disabled). |
user |
The username required for authentication (if applicable). |
password |
The password required for authentication (can be encoded in base64). |
enabled |
To use this entry, it must be set to true. Otherwise, it is false (disabled). |
| Setting | Meaning |
|---|---|
ips |
A list of IP addresses assigned to the device. Use | to separate multiple IPs. Prefix an IP with ! to temporarily disable it without removing it from the list. Example: "10.1.1.30". |
user |
The username required for authentication. |
password |
The password required for authentication (can be encoded in base64). |
enabled |
To use this entry, it must be set to true. Otherwise, it is false (disabled). |
| Setting | Meaning |
|---|---|
ips |
A list of IP addresses assigned to the device. Use | to separate multiple IPs. Prefix an IP with ! to temporarily disable it without removing it from the list. Example: "192.168.178.1 | !10.1.1.23" (IP 10.1.1.23 is disabled). |
ains |
A list of AINs (Actor Identification Numbers) for Fritz devices. Multiple AINs are separated by commas, and if multiple IPs are used, the AINs for each IP are separated by |. Example: "1234,3443,2333 | 1234,4456,7866,3421". |
user |
The username required for authentication. |
password |
The password required for authentication (can be encoded in base64). |
enabled |
To use this entry, it must be set to true. Otherwise, it is false (disabled). |
By default every IP under a smart-switch entry uses the global number_of_lowest_prices_for_switching and switching_block_minutes from the prices section. Two optional pipe-separated lists let you override these per IP:
| Setting | Meaning |
|---|---|
lowest_prices_per_ip |
Pipe-separated list, position-aligned with the active IPs in ips (i.e. excluding any prefixed with !). Each entry is the cluster count for that IP. An empty entry means "use the global default". Example: "8|4|" runs the first IP on the 8 cheapest clusters, the second on 4, the third on the global default. |
block_minutes_per_ip |
Pipe-separated list, position-aligned with the active IPs in ips. Each entry is the cluster length in minutes (multiple of 15) for that IP. An empty entry means "use the global default". Example: "60|30|". |
When any smart-switch entry uses one of these overrides, all switches are evaluated per-IP — the legacy "switch them all together based on a single condition" logic kicks in only when no override is configured anywhere.
The /stats route shows a multi-tab dashboard with daily, 7-day, monthly, and yearly aggregations of everything SEUSS has measured.
Today / Yesterday / 7 Days / Month / Year — each tab shows the same set of tiles for that range. Today updates live (see below); the other tabs are server-rendered snapshots that refresh on page reload.
| Tile | Meaning |
|---|---|
| House Consumption | Wh consumed by AC loads in the range. |
| Grid Import / Export | Energy imported from / exported to the grid. |
| PV Production | Total PV yield. |
| Battery Charged / Discharged | Wh in / Wh out of the battery. |
| Cycles | charge_wh / battery_capacity_wh. The capacity is auto-detected from the Victron battery monitor (live nominal voltage × installed Ah). |
| RTE | Round-trip efficiency (discharge / charge × 100). Renders as -- when the range has more discharge than charge — that means the battery was net-drained, not that energy was magically created. Look at Month/Year for a realistic ~92–96% on healthy LFP packs. |
| Loss | Integrated max(input − usable, 0) over the range, in Wh. Inverter / wiring loss should be a few percent of throughput. |
| Imbalance (signed) | Integrated input − usable WITHOUT the max(…, 0) clamp. Positive = normal (equals Loss). Negative = SEUSS recorded more consumption than known sources can supply, pointing at a missing source (PV inverter not registered with the GX) or a sensor sign issue. |
| Grid Cost | Cost of the grid energy used in the range. Stored as cents, shown as €. |
| Skip Counters | How often each abort condition (Solar / Battery-range / Overnext / Expensive-phase / SOC-target) skipped a charge in the range. Useful to see which abort condition is actually doing work in your setup. |
The Today tab subscribes to the same WebSocket as the home status page. While Today is active, Consumption / Grid / Grid Export / PV / Battery Charge / Battery Discharge / Cost / Loss / Imbalance update without a page reload. Cycles, RTE, and the skip counters are server-derived and refresh on page reload.
Below the comparison table, a per-hour breakdown of today's Loss and Imbalance shows when during the day the energy balance went off — a steady sensor offset shows up in every hour, while a bug tied to a specific event (e.g. inverter standby at night) shows up only in those hours. Hours with no activity yet (loss = 0 and imbalance = 0) are hidden so the table only contains real measurements.
When use_solar_forecast_to_abort is on (or PV panels are configured), the stats page also shows the adjusted Open-Meteo forecast that the abort logic uses. Forecast Today is measured PV so far + adjusted forecast for the rest of the day; Forecast Tomorrow is the adjusted forecast for the full next day; Measured Today and Rest Today are the two components that make up Forecast Today. The Adjustment Factor is the EWMA-smoothed ratio of recent actual yield vs. the raw API forecast (clipped to [0.2, 2.0]) — 1.00 = forecast on target, <1.0 = consistently below forecast (dirty panels, shading), >1.0 = better than forecast. SEUSS multiplies every raw API number by this before applying any abort logic, so the displayed values are exactly what the conditions compare against.
| Setting | Meaning |
|---|---|
stats_history_retention_days |
How many days of per-day history to keep (consumption_wh_by_day, grid_wh_by_day, etc.). Default 400 — covers a year-over-year comparison plus a month buffer. Set to 0 to disable cleanup. |
The ERROR log level indicates error conditions within an application that hinder the execution of a specific
operation. While the application can continue functioning at a reduced level of functionality or
performance,ERROR logs signify issues that should be investigated promptly.
Events logged at the WARN level typically indicate that something unexpected has
occurred, but the application can continue to function normally for the time being.
It is also used to signify conditions that should be promptly addressed before they
escalate into problems for the application.
The INFO level captures events in the system that are significant to the
application's business purpose. Such events are logged to show that the system is
operating normally. Production systems typically default to logging at this level
so that a summary of the application's normal behavior is visible to anyone
reviewing the logs.
The DEBUG level is used for logging messages that aid developers in identifying
issues during a debugging session. The content of the messages logged at the DEBUG
level will vary depending on your application, but they typically contain
detailed information that assists its developers in troubleshooting problems
efficiently. This can include variables' state within the surrounding scope or
relevant error codes. |
The idea is inspired by the @christian1980nrw project linked below. This project is my first with the Victron Venus OS, so I adopted some ideas and approaches from the following projects. The approach is the same and for very narrow systems the implementation with a bash script is probably better