Decision · switching signals

Decision signals: charge, hold or discharge each hour

The Decision API tells your EMS each hour: charge, hold or discharge — for storage, wallbox and heat pump, from the Austrian spot price.

Community Login Decision API docs
Sketch: hourly charge, hold and discharge signals over the price curve
Don’t read a chart — three clear commands, hour by hour.

Example: charge at night, discharge in the morning

The battery is half full. Spot drops overnight. The house draws in the morning. Decision sets: hold, then charge, then discharge — the EMS does not hunt the curve itself.

Window
20:00–08:00
Low price (example)
2.1 ct/kWh
Signal at 23:00
Charge

A night as signals looks like this:

  1. 20Hold
  2. 21Hold
  3. 22Charge
  4. 23Charge
  5. 00Charge
  6. 01Hold
  7. 07Discharge
  8. 08Discharge

Illustrative example, not live data. Real signals need an API key.

How the signals are built

Price, quantiles, then one command per hour.

  1. Know the week

    The same 7-day prices as Forecast — exchange today/tomorrow, forecast after that.

  2. Split cheap and expensive

    P10 for charging, P90 for discharging: cautious enough for storage and wallbox.

  3. One signal per hour

    Charge, hold or discharge — ready for a relay, PicoC or REST poll.

What your EMS gets back

One call to GET /v1/decision returns the hour, not a raw chart.

action per hour

Charge, hold or discharge — the rule the EMS can set.

price_basis

Often P10 when charging, P90 when discharging: the same band as in the live chart.

Through D+6

Not just the next three hours — the horizon covers the week.

In short

How is this different from Hours and windows?

Hours says how many hours the plant needs. Cheap-hour windows pick the N cheapest hours. Decision signals give every hour a command: charge, hold, discharge.

What does hold mean?

Neither charge nor discharge: keep the battery, pause the wallbox, don’t push the heat pump extra. The EMS stays still until the next cheap or expensive hour.

Is this the technical spec?

No. This page explains the benefit. Parameters, fields and examples are under Decision docs. Quick start in the portal after Community login.

Get the signals into your EMS

Community to try. Spec to integrate. Windows and Hours when you need an hour count instead of continuous control.

Community Decision API docs Loxone guide

Next: Cheap-hour windows · Hours Demand · Live electricity prices.