Skip to content

First Steps (Branch feature config‐overhaul)

Andreas edited this page Jan 1, 2025 · 3 revisions

1. Install and start Server (Readme)

2. API Calls can be found under: http://IP:8503/docs

3. Define REST Inputs, here one Example in NodeRed:

msg.payload = {
    ems: {
        pv_prognose_wh: (context.data.pv_forecast || []).map(value => parseInt(value) || 0),
        strompreis_euro_pro_wh: (context.data.strompreis || []).map(value => parseFloat(value.toFixed(8)) || 0),
        einspeiseverguetung_euro_pro_wh: Array(48).fill((7 / (1000.0 * 100.0))),
        preis_euro_pro_wh_akku: parseFloat((context.data.akku_preis * (0.01 / 1000.0)).toFixed(8)),
        gesamtlast: context.data.gesamtlast
    },
    pv_akku: {
        capacity_wh: 33000 * 0.8,
        charging_efficiency: 0.88,
        discharging_efficiency: 0.88,
        max_charge_power_w: 5000,
        initial_soc_percentage: parseInt(context.data.soc) || 0,
        min_soc_percentage: parseInt(context.data.min_soc_prozent) || 0,
        max_soc_percentage: 100
    },
    wechselrichter: {
        max_power_wh: 10000
    },
    eauto: {
        capacity_wh: 60000,
        charging_efficiency: 0.95,
        discharging_efficiency: 1,
        max_charge_power_w: parseInt(context.data.eauto_max_power) || 1,
        initial_soc_percentage: parseInt(context.data.soc_tesla) || 0,
        min_soc_percentage: parseInt(context.data.eauto_soc_ui) || 0,
        max_soc_percentage: 100
    },
    dishwasher: context.data.spuel ? {
        consumption_wh: parseInt(context.data.spuel[1]) || 0,
        duration_h: parseInt(context.data.spuel[0]) || 0
    } : null,
    temperature_forecast: (context.data.temperature_forecast || []).map(value => parseFloat(value.toFixed(1)) || 0),
    start_solution: context.data.start_solution && context.data.start_solution.length >= 2
        ? context.data.start_solution
        : [0, 0]
};

4. CONFIG

4.1 Old Config / First Config

  1. If you have a old config EOS.config.json rename it to EOS.config.old
  2. Start the Server
  3. Open http://IP:8503/v1/config
  4. Find "config_file_path": C:\\Users\\drbac\\AppData\\Local\\net.akkudoktor.eos\\net.akkudoktor.eos\\EOS.config.json
  5. This is the path with the config file. Open this File!

4.2 Prediction Providers

(optional) Use our Prediction Providers for PV Forecast, Load Forecast. List of your activated prediction Providers: http://IP:8503/v1/prediction/keys

4.2.1 Option 1: Direct Integration

In Development.

4.2.2 Option 2: Use REST API

Activate needed Predictions directly For Example: Electricty Price with our API: "elecprice_charges_kwh": 22.05, "elecprice_provider": "ElecPriceAkkudoktor", Reload the server and test: http://IP:8503/strompreis This result can be used as input for /optimize You can also list all available prediction keys: http://IP:8503/v1/prediction/keys