ITex Services s.r.o.

[ ITexSpot · evcc ]

Electricity spot price in evcc

A custom tariff with an outlook for the whole week: evcc then schedules car charging into the cheapest hours, even if they are not until Thursday.

Beta · free · read-only key

Czech bidding zone (CZ) only — prices in CZK, Czech distribution tariffs.

Configuration

evcc.yaml
tariffs:
  currency: CZK
  grid:
    type: custom
    features: [cacheable]       # keeps the last prices during an outage
    interval: 1h                # how often to download the forecast
    forecast:
      source: http
      uri: https://api.itexservices.cz/v1/k/its_YOURKEY/evcc.json
      jq: 'tostring'

evcc.json returns an array of hourly slots starting from the current hour. value is in CZK/kWh: the final price if the key has a stored tariff (supplier margin, distribution, VAT), otherwise the plain spot price — in that case add distribution and VAT in evcc via charges and tax. An interval of 1 h is enough; the data changes three times a day.

evcc.json response (shortened)
[
  { "start": "2026-11-18T13:00:00Z", "end": "2026-11-18T14:00:00Z", "value": 4.012 },
  { "start": "2026-11-18T14:00:00Z", "end": "2026-11-18T15:00:00Z", "value": 4.105 }
]

The key is in the path of the address — this is the recommended way: the response goes through our cache and is faster. If your version of evcc supports headers for the source, you can also use the address https://api.itexservices.cz/v1/evcc.json with the header Authorization: Bearer its_…, but such a response is not stored in the cache and is slower. An interval of 1 h means 24 requests a day, which fits even the Free tier.

With ?strategie=p90 in the address you plan more cautiously (with a higher forecast price), with p10 more boldly.

Safe behavior during an API outage

The API may stop responding for a while, return an error or return stale data. Your home automation has to expect this — build it so that an outage breaks nothing:

  • The relay stays in its last safe state. Without valid data, do not switch anything on because of a “cheap hour”. Return devices to the behavior the house would have without ITexSpot (boiler on a time schedule, inverter without export limiting, battery in normal mode).
  • Fallback window. For loads that must run (boiler, charging), keep a fixed window in usually cheap hours, for example 1–5 am. When the data is not valid, run by that window.
  • Detect invalid data. Always check the data status. In JSON it is stav (ok, stara_data = stale data, limit, neplatny_klic = invalid key, nedostupne = unavailable), in the Loxone text output stav_kod: 0 = OK, 1 = stale data, 401 key, 429 limit, 503 outage. Then stari_min (age in minutes): the data changes three times a day, so overnight it is routinely up to about 16 hours old. A value above 1,800 minutes (30 h) means no new data is being produced.
  • A lost connection may not show in the values. Loxone and other systems keep the last value they read when the server is unreachable. stari_min, however, grows with every successful request. When it stops changing, requests are not getting through.
  • On a 429 or 503 error, wait as long as the Retry-After header says and do not retry immediately.
The forecast is indicative information, not a guarantee. Your home automation must cope with the API not responding for a while — set a sensible default and watch the age of the data. Details are in the API terms.