Solcast über MQTT einbinden?

[Fliegeral]

Guten Tag,
ich verwende bei mir eine OpenHab Installation, welche schon für PV Vorhersagen mit Solcast verbunden ist.
Da man dort (Solcast) aber nur wenige Abfragen am Tag fahren kann, würde ich gern meine RAW-Daten über MQTT an EVCC übergeben.
Wie kann ich dies einstellen?
Mir fehlt noch eine gure Übersicht über die MQTT Möglichkeiten von EVCC.
In OpenHab sind die Raw Daten im Json Format mit Actuals gefolgt von den forecasts. Bei den Werten wird der PV-Wert aber im Intervall von 30min hinterlegt (dann aber immer der für eine Stunde)
Ich könnte auch ein neues JSON erstellen, dazu muss ich aber die Struktur wissen.
Grüße

[VolkerK62]

evtl hilft dir das weiter?
#18887

[Fliegeral]

Den Post habe ich schon entdeckt und würde ich gern ausprobieren.
Was ich hier nicht verstehe ist im JQ Part der yaml nur das Start / End / Price. Vor allem wenn in dem Beispiel oben ja nur ein Start und PV Forecast enthalten ist.

[mdkeil]

Da ich ebenfalls noch einen free Solcast-Zugang mit zwei unterschiedlichen Dachneigungen nutze, bräuchte ich eine kurze Info, was genau erwartet wird.. /start/end/price wird vermutlich die Struktur vom dyn. Strompeis sein.. die Frage, was dann für den PV-Forcast bei price erwartet wird.. vermutlich ein Wert in kWh?

[Timer2000]

also in home assistant bekommst du halb-stündliche daten und das für die nächsten 7 Tage. Ich denke mal für EVCC reichen 3 Tage für eine Wochenendeplanung aus. Leider ist das für jeden Tag ein separater Sensor. Ich vermute mal für EVCC müssten die Daten für auf einen Sensor reduziert werden. MQTT für die Übertragung macht sicherlich Sinn.

Wäre zu klären wie die Daten in HA aufbereitet werden müssen und wie das dann in EVCC eingetragen werden muss damit das funktioniert. Meine Kentnisse reichen da nicht aus.

Ach ja, ich habe auch bereits zwei Dachflächen in Solcast integriert, das war damals noch möglich. Bei den neuen Registrierungen ist das ganze wohl auf eine Fläche begrenzt.

[iseeberg79]

Habt ihr drüber nachgedacht, die Daten der evcc API zu verwenden? Beim Strompreis http://localhost:7070/api/tariff/grid - sollte für Solar auch möglich sein/werden?

[Fliegeral]

Ist natürlich auch eine Möglichkeit, aber meine Kommunikation mit EVCC läuft hauptsächlich über MQTT (ich schicke mir auch Ladepläne und Stromwerte so aus Openhab ins EVCC). In der Doku zum Tariff finde ich aber auch keine Post Funktion sondern nur eine GET (https://docs.evcc.io/docs/integrations/rest-api) , also auch hier das Problem mit einer Beschreibung. Die Frage, wie die Daten kommen sollen bleibt also.

[mdkeil]

Also ich habe eine mqtt Umsetzung via node red realisiert.. evcc scheint das Format auch zu akzeptieren

tariffs:
  solar:
    type: custom
    forecast:
      source: mqtt
      topic: nodered/solcast

evcc tariff

solar:
From                   To                     Price/Cost
2025-02-18 00:00:00    2025-02-18 01:00:00    0.000
2025-02-18 01:00:00    2025-02-18 02:00:00    0.000
2025-02-18 02:00:00    2025-02-18 03:00:00    0.000
2025-02-18 03:00:00    2025-02-18 04:00:00    0.000
2025-02-18 04:00:00    2025-02-18 05:00:00    0.000
2025-02-18 05:00:00    2025-02-18 06:00:00    0.000
2025-02-18 06:00:00    2025-02-18 07:00:00    0.000
2025-02-18 07:00:00    2025-02-18 08:00:00    0.000
2025-02-18 08:00:00    2025-02-18 09:00:00    774.345
2025-02-18 09:00:00    2025-02-18 10:00:00    6437.555
2025-02-18 10:00:00    2025-02-18 11:00:00    10459.820
2025-02-18 11:00:00    2025-02-18 12:00:00    12952.750
2025-02-18 12:00:00    2025-02-18 13:00:00    14560.175
2025-02-18 13:00:00    2025-02-18 14:00:00    14753.690
2025-02-18 14:00:00    2025-02-18 15:00:00    13622.370
2025-02-18 15:00:00    2025-02-18 16:00:00    11513.845
2025-02-18 16:00:00    2025-02-18 17:00:00    8127.905
2025-02-18 17:00:00    2025-02-18 18:00:00    3251.060
2025-02-18 18:00:00    2025-02-18 19:00:00    0.000
2025-02-18 19:00:00    2025-02-18 20:00:00    0.000
2025-02-18 20:00:00    2025-02-18 21:00:00    0.000
2025-02-18 21:00:00    2025-02-18 22:00:00    0.000
2025-02-18 22:00:00    2025-02-18 23:00:00    0.000
2025-02-18 23:00:00    2025-02-19 00:00:00    0.000
2025-02-19 00:00:00    2025-02-19 01:00:00    0.000
2025-02-19 01:00:00    2025-02-19 02:00:00    0.000
2025-02-19 02:00:00    2025-02-19 03:00:00    0.000
2025-02-19 03:00:00    2025-02-19 04:00:00    0.000
2025-02-19 04:00:00    2025-02-19 05:00:00    0.000
2025-02-19 05:00:00    2025-02-19 06:00:00    0.000
2025-02-19 06:00:00    2025-02-19 07:00:00    0.000
2025-02-19 07:00:00    2025-02-19 08:00:00    0.000
2025-02-19 08:00:00    2025-02-19 09:00:00    1257.210
2025-02-19 09:00:00    2025-02-19 10:00:00    6142.920
2025-02-19 10:00:00    2025-02-19 11:00:00    9890.845
2025-02-19 11:00:00    2025-02-19 12:00:00    12669.845
2025-02-19 12:00:00    2025-02-19 13:00:00    13868.180
2025-02-19 13:00:00    2025-02-19 14:00:00    14079.505
2025-02-19 14:00:00    2025-02-19 15:00:00    13043.335
2025-02-19 15:00:00    2025-02-19 16:00:00    10537.850
2025-02-19 16:00:00    2025-02-19 17:00:00    6481.965
2025-02-19 17:00:00    2025-02-19 18:00:00    1610.565
2025-02-19 18:00:00    2025-02-19 19:00:00    5.680
2025-02-19 19:00:00    2025-02-19 20:00:00    0.000
2025-02-19 20:00:00    2025-02-19 21:00:00    0.000
2025-02-19 21:00:00    2025-02-19 22:00:00    0.000
2025-02-19 22:00:00    2025-02-19 23:00:00    0.000
2025-02-19 23:00:00    2025-02-20 00:00:00    0.000
2025-02-20 00:00:00    2025-02-20 01:00:00    0.000
2025-02-20 01:00:00    2025-02-20 02:00:00    0.000
2025-02-20 02:00:00    2025-02-20 03:00:00    0.000
2025-02-20 03:00:00    2025-02-20 04:00:00    0.000
2025-02-20 04:00:00    2025-02-20 05:00:00    0.000
2025-02-20 05:00:00    2025-02-20 06:00:00    0.000
2025-02-20 06:00:00    2025-02-20 07:00:00    0.000
2025-02-20 07:00:00    2025-02-20 08:00:00    0.000
2025-02-20 08:00:00    2025-02-20 09:00:00    508.360
2025-02-20 09:00:00    2025-02-20 10:00:00    3466.605
2025-02-20 10:00:00    2025-02-20 11:00:00    6465.575
2025-02-20 11:00:00    2025-02-20 12:00:00    6994.295
2025-02-20 12:00:00    2025-02-20 13:00:00    6675.845
2025-02-20 13:00:00    2025-02-20 14:00:00    5416.995
2025-02-20 14:00:00    2025-02-20 15:00:00    3358.835
2025-02-20 15:00:00    2025-02-20 16:00:00    1748.725
2025-02-20 16:00:00    2025-02-20 17:00:00    711.995
2025-02-20 17:00:00    2025-02-20 18:00:00    184.505
2025-02-20 18:00:00    2025-02-20 19:00:00    0.000
2025-02-20 19:00:00    2025-02-20 20:00:00    0.000
2025-02-20 20:00:00    2025-02-20 21:00:00    0.000
2025-02-20 21:00:00    2025-02-20 22:00:00    0.000
2025-02-20 22:00:00    2025-02-20 23:00:00    0.000
2025-02-20 23:00:00    2025-02-21 00:00:00    0.000

aber die Anzeige in evcc bleibt leer.. wo ist mein Fehler? /cc @andig

[mdkeil]

ok, neustart von evcc und gut war es ;)

[Fliegeral]

So will ich das auch machen. Leider scheint grad so schön die Sonne und ich möchte die Ladung nicht laufend unterbrechen. Wie schaut bei dir der String im MQTT aus?

[mdkeil]

[
  {
    start: '2025-02-17T23:00:00Z',
    end: '2025-02-18T00:00:00Z',
    price: 0
  },
  {
    start: '2025-02-18T00:00:00Z',
    end: '2025-02-18T01:00:00Z',
    price: 0
  },
  {
    start: '2025-02-18T01:00:00Z',
    end: '2025-02-18T02:00:00Z',
    price: 0
  },
  {
    start: '2025-02-18T02:00:00Z',
    end: '2025-02-18T03:00:00Z',
    price: 0
  },
  {
    start: '2025-02-18T03:00:00Z',
    end: '2025-02-18T04:00:00Z',
    price: 0
  },
  {
    start: '2025-02-18T04:00:00Z',
    end: '2025-02-18T05:00:00Z',
    price: 0
  },
  {
    start: '2025-02-18T05:00:00Z',
    end: '2025-02-18T06:00:00Z',
    price: 0
  },
  {
    start: '2025-02-18T06:00:00Z',
    end: '2025-02-18T07:00:00Z',
    price: 0
  },
  {
    start: '2025-02-18T07:00:00Z',
    end: '2025-02-18T08:00:00Z',
    price: 774.345
  },
  {
    start: '2025-02-18T08:00:00Z',
    end: '2025-02-18T09:00:00Z',
    price: 6437.555
  },
  {
    start: '2025-02-18T09:00:00Z',
    end: '2025-02-18T10:00:00Z',
    price: 10459.82
  },
  {
    start: '2025-02-18T10:00:00Z',
    end: '2025-02-18T11:00:00Z',
    price: 12952.75
  },
  {
    start: '2025-02-18T11:00:00Z',
    end: '2025-02-18T12:00:00Z',
    price: 14560.175
  },
  {
    start: '2025-02-18T12:00:00Z',
    end: '2025-02-18T13:00:00Z',
    price: 14759.915
  },
  {
    start: '2025-02-18T13:00:00Z',
    end: '2025-02-18T14:00:00Z',
    price: 13631.125
  },
  {
    start: '2025-02-18T14:00:00Z',
    end: '2025-02-18T15:00:00Z',
    price: 11627.999999999998
  },
  {
    start: '2025-02-18T15:00:00Z',
    end: '2025-02-18T16:00:00Z',
    price: 8257.470000000001
  },
  {
    start: '2025-02-18T16:00:00Z',
    end: '2025-02-18T17:00:00Z',
    price: 3269.555
  },
  {
    start: '2025-02-18T17:00:00Z',
    end: '2025-02-18T18:00:00Z',
    price: 0
  },
  {
    start: '2025-02-18T18:00:00Z',
    end: '2025-02-18T19:00:00Z',
    price: 0
  },
  {
    start: '2025-02-18T19:00:00Z',
    end: '2025-02-18T20:00:00Z',
    price: 0
  },
  {
    start: '2025-02-18T20:00:00Z',
    end: '2025-02-18T21:00:00Z',
    price: 0
  },
  {
    start: '2025-02-18T21:00:00Z',
    end: '2025-02-18T22:00:00Z',
    price: 0
  },
  {
    start: '2025-02-18T22:00:00Z',
    end: '2025-02-18T23:00:00Z',
    price: 0
  },
  {
    start: '2025-02-18T23:00:00Z',
    end: '2025-02-19T00:00:00Z',
    price: 0
  },
  {
    start: '2025-02-19T00:00:00Z',
    end: '2025-02-19T01:00:00Z',
    price: 0
  },
  {
    start: '2025-02-19T01:00:00Z',
    end: '2025-02-19T02:00:00Z',
    price: 0
  },
  {
    start: '2025-02-19T02:00:00Z',
    end: '2025-02-19T03:00:00Z',
    price: 0
  },
  {
    start: '2025-02-19T03:00:00Z',
    end: '2025-02-19T04:00:00Z',
    price: 0
  },
  {
    start: '2025-02-19T04:00:00Z',
    end: '2025-02-19T05:00:00Z',
    price: 0
  },
  {
    start: '2025-02-19T05:00:00Z',
    end: '2025-02-19T06:00:00Z',
    price: 0
  },
  {
    start: '2025-02-19T06:00:00Z',
    end: '2025-02-19T07:00:00Z',
    price: 0
  },
  {
    start: '2025-02-19T07:00:00Z',
    end: '2025-02-19T08:00:00Z',
    price: 1420.67
  },
  {
    start: '2025-02-19T08:00:00Z',
    end: '2025-02-19T09:00:00Z',
    price: 6445.320000000001
  },
  {
    start: '2025-02-19T09:00:00Z',
    end: '2025-02-19T10:00:00Z',
    price: 10171.23
  },
  {
    start: '2025-02-19T10:00:00Z',
    end: '2025-02-19T11:00:00Z',
    price: 12951.655
  },
  {
    start: '2025-02-19T11:00:00Z',
    end: '2025-02-19T12:00:00Z',
    price: 14151.399999999998
  },
  {
    start: '2025-02-19T12:00:00Z',
    end: '2025-02-19T13:00:00Z',
    price: 14457.579999999998
  },
  {
    start: '2025-02-19T13:00:00Z',
    end: '2025-02-19T14:00:00Z',
    price: 13466.025000000001
  },
  {
    start: '2025-02-19T14:00:00Z',
    end: '2025-02-19T15:00:00Z',
    price: 10974.089999999998
  },
  {
    start: '2025-02-19T15:00:00Z',
    end: '2025-02-19T16:00:00Z',
    price: 6916.87
  },
  {
    start: '2025-02-19T16:00:00Z',
    end: '2025-02-19T17:00:00Z',
    price: 2002.4099999999999
  },
  {
    start: '2025-02-19T17:00:00Z',
    end: '2025-02-19T18:00:00Z',
    price: 5.68
  },
  {
    start: '2025-02-19T18:00:00Z',
    end: '2025-02-19T19:00:00Z',
    price: 0
  },
  {
    start: '2025-02-19T19:00:00Z',
    end: '2025-02-19T20:00:00Z',
    price: 0
  },
  {
    start: '2025-02-19T20:00:00Z',
    end: '2025-02-19T21:00:00Z',
    price: 0
  },
  {
    start: '2025-02-19T21:00:00Z',
    end: '2025-02-19T22:00:00Z',
    price: 0
  },
  {
    start: '2025-02-19T22:00:00Z',
    end: '2025-02-19T23:00:00Z',
    price: 0
  },
  {
    start: '2025-02-19T23:00:00Z',
    end: '2025-02-20T00:00:00Z',
    price: 0
  },
  {
    start: '2025-02-20T00:00:00Z',
    end: '2025-02-20T01:00:00Z',
    price: 0
  },
  {
    start: '2025-02-20T01:00:00Z',
    end: '2025-02-20T02:00:00Z',
    price: 0
  },
  {
    start: '2025-02-20T02:00:00Z',
    end: '2025-02-20T03:00:00Z',
    price: 0
  },
  {
    start: '2025-02-20T03:00:00Z',
    end: '2025-02-20T04:00:00Z',
    price: 0
  },
  {
    start: '2025-02-20T04:00:00Z',
    end: '2025-02-20T05:00:00Z',
    price: 0
  },
  {
    start: '2025-02-20T05:00:00Z',
    end: '2025-02-20T06:00:00Z',
    price: 0
  },
  {
    start: '2025-02-20T06:00:00Z',
    end: '2025-02-20T07:00:00Z',
    price: 0
  },
  {
    start: '2025-02-20T07:00:00Z',
    end: '2025-02-20T08:00:00Z',
    price: 508.36
  },
  {
    start: '2025-02-20T08:00:00Z',
    end: '2025-02-20T09:00:00Z',
    price: 3439.71
  },
  {
    start: '2025-02-20T09:00:00Z',
    end: '2025-02-20T10:00:00Z',
    price: 6231.465
  },
  {
    start: '2025-02-20T10:00:00Z',
    end: '2025-02-20T11:00:00Z',
    price: 6779.41
  },
  {
    start: '2025-02-20T11:00:00Z',
    end: '2025-02-20T12:00:00Z',
    price: 6795.65
  },
  {
    start: '2025-02-20T12:00:00Z',
    end: '2025-02-20T13:00:00Z',
    price: 5413.975
  },
  {
    start: '2025-02-20T13:00:00Z',
    end: '2025-02-20T14:00:00Z',
    price: 3085.02
  },
  {
    start: '2025-02-20T14:00:00Z',
    end: '2025-02-20T15:00:00Z',
    price: 1668.8
  },
  {
    start: '2025-02-20T15:00:00Z',
    end: '2025-02-20T16:00:00Z',
    price: 731.385
  },
  {
    start: '2025-02-20T16:00:00Z',
    end: '2025-02-20T17:00:00Z',
    price: 195.07
  },
  {
    start: '2025-02-20T17:00:00Z',
    end: '2025-02-20T18:00:00Z',
    price: 0
  },
  {
    start: '2025-02-20T18:00:00Z',
    end: '2025-02-20T19:00:00Z',
    price: 0
  },
  {
    start: '2025-02-20T19:00:00Z',
    end: '2025-02-20T20:00:00Z',
    price: 0
  },
  {
    start: '2025-02-20T20:00:00Z',
    end: '2025-02-20T21:00:00Z',
    price: 0
  },
  {
    start: '2025-02-20T21:00:00Z',
    end: '2025-02-20T22:00:00Z',
    price: 0
  },
  {
    start: '2025-02-20T22:00:00Z',
    end: '2025-02-20T23:00:00Z',
    price: 0
  }
]

[Timer2000]

Kannst du das Node vielleicht zur Verfügung stellen? Und oder beschreiben was du gemacht hast?

Klingt nach einer interessanten Variante.

[Fliegeral]

Das war ein guter Tipp, mein Export aus openhab funktioniert jetzt auch.

[flole123]

Klasse, bei mir ist's jetzt auch eine Variante über Node-Red und MQTT geworden. Nur um's richtig zu machen. Habt ihr die Werte in "price" als Wh oder kWh?

[Fliegeral]

In Wh

[d3ni3]

Moin,

kann es sein das dies mit der Version 0.200.1 so nicht mehr funktioniert? /cc @andig

Ich habe folgende Config:

tariffs:
  solar:
    type: custom
    forecast:
      source: mqtt
      topic: nodered/solarprognose

Und das sehe ich dazu dann im Log:

[tariff] ERROR 2025/02/19 07:29:11 outdated
[main ] ERROR 2025/02/19 07:29:11 creating tariff solar failed: cannot create tariff type 'custom': outdated 

[Timer2000]

:(
also alle 15s in meinem Fall. da kommt nix. Nur nach einem Neustart von EVCC. Es ist zum verrückt werden.

[iseeberg79]

teil‘ doch mal deine config

[Timer2000]

Also aufeinmal ist es doch umgesprungen. Muss ich mal beobachten ob das jezt funktioniert.

Hier mal mein Code für die EVCC Aufbereitung der HA Daten:

// Hier kommt das Array aus dem Join-Node an, z.B. [ { entity_id, old_state, new_state }, {...}, {...} ]
var inputs = msg.payload;

// Array für das Zusammenführen aller Forecast-Einträge
var combined = [];

// 1) Schleife über die drei Nachrichten (Heute, Morgen, Tag_3)
for (var i = 0; i < inputs.length; i++) {
    var obj = inputs[i];

    // Prüfe, ob detailedHourly existiert
    if (
        obj.new_state &&
        obj.new_state.attributes &&
        obj.new_state.attributes.detailedHourly
    ) {
        // Hänge das Array an "combined"
        combined = combined.concat(obj.new_state.attributes.detailedHourly);
    }
}

// Falls nichts gefunden wird, brechen wir ab
if (combined.length === 0) {
    node.warn("Keine detailedHourly-Daten gefunden!");
    msg.payload = [];
    return msg;
}

// 2) Sortiere die Einträge chronologisch nach period_start
combined.sort(function (a, b) {
    return new Date(a.period_start) - new Date(b.period_start);
});

// 3) Aggregiere 30-Minuten-Daten zu stündlichen Intervallen (UTC)
var hourly = {};
for (var j = 0; j < combined.length; j++) {
    var entry = combined[j];
    var dt = new Date(entry.period_start);

    // Erstelle einen UTC-Schlüssel "YYYY-MM-DDTHH:00:00Z"
    var year = dt.getUTCFullYear();
    var month = ('0' + (dt.getUTCMonth() + 1)).slice(-2);
    var day = ('0' + dt.getUTCDate()).slice(-2);
    var hour = ('0' + dt.getUTCHours()).slice(-2);
    var hourKey = year + '-' + month + '-' + day + 'T' + hour + ':00:00Z';

    // Falls noch nicht vorhanden, init
    if (!hourly[hourKey]) {
        hourly[hourKey] = 0;
    }
    // pv_estimate summieren
    hourly[hourKey] += (Number(entry.pv_estimate) * 1000) || 0;
    }

// 4) Das gewünschte Format { start, end, price } erzeugen
var result = [];
var keys = Object.keys(hourly).sort(); // chronologisch sortieren

for (var k = 0; k < keys.length; k++) {
    var startTime = keys[k];
    // Endzeit = Start + 1 Stunde
    var startDate = new Date(startTime);
    startDate.setUTCHours(startDate.getUTCHours() + 1);

    // ISO-String ohne Millisekunden
    var endTime = startDate.toISOString().replace(/\.\d{3}Z$/, "Z");

    // price = Summe aus hourly
    result.push({
        start: startTime,
        end: endTime,
        price: hourly[startTime]
    });
}

// 5) Ergebnis in msg.payload zurückgeben
msg.payload = result;
return msg;

Auf den ersten Blick läuft es und das direkt für meine Ost/West Anlage. Jetzt muss ich da nur noch die Daten der kleinen Solaranlage mit rein nehmen. Die Werte bekomme ich über Forecast.solar, die scheinen im RAW Format in HA nicht zu liegen.

Viel Erfolg beim Nachbau.

[Timer2000]

teil‘ doch mal deine config

solar: # Forecast Solcast
type: custom
forecast:
source: mqtt
topic: homeassistant/solcast/gesamt

[Timer2000]

Ich trage interval mal nach.

[djfanatix]

For those with Home Assistant and the Solcast Integration:

Step 1: Make a template sensor

template:
  - sensor:
      - name: "Solcast EVCC Forecast"
        state: "OK"  # Placeholder state, since the data is in attributes
        attributes:
          forecasts: >
            {% set sensors = [
              'sensor.solcast_forecast_today',
              'sensor.solcast_forecast_tomorrow',
              'sensor.solcast_pv_forecast_forecast_day_3'
            ] %}
            {% set combined = namespace(value=[]) %}
            {% for sensor in sensors %}
              {% set forecasts = state_attr(sensor, 'detailedHourly') %}
              {% if forecasts is iterable and forecasts | length > 0 %}
                {% for entry in forecasts %}
                  {% set start_time = entry.period_start | as_datetime | as_local %}
                  {% set end_time = start_time + timedelta(hours=1) %}
                  {% set new_entry = {
                    'start': start_time.strftime('%Y-%m-%dT%H:%M:%SZ'),
                    'end': end_time.strftime('%Y-%m-%dT%H:%M:%SZ'),
                    'price': (entry.pv_estimate * 1000) | round
                  } %}
                  {% set combined.value = combined.value + [new_entry] %}
                {% endfor %}
              {% endif %}
            {% endfor %}
            {{ combined.value | tojson }}

Step 2: Send the data to EVCC by MQTT

alias: (EVCC)(MQTT) Solcast
description: ""
triggers:
  - trigger: time_pattern
    minutes: /5
conditions: []
actions:
  - action: mqtt.publish
    metadata: {}
    data:
      evaluate_payload: false
      qos: 0
      retain: true
      topic: evcc/solcast
      payload: "{{state_attr('sensor.solcast_evcc_forecast', 'forecasts')}}"
mode: single

Step 3: Create the template Solar

tariffs:
  solar:
    type: custom
    interval: 5m
    forecast:
       source: mqtt
       topic: evcc/solcast
       timeout: 1h 

[Timer2000]

For those with Home Assistant and the Solcast Integration:

Step 1: Make a template sensor

template:
  - sensor:
      - name: "Solcast EVCC Forecast"
        state: "OK"  # Placeholder state, since the data is in attributes
        attributes:
          forecasts: >
            {% set sensors = [
              'sensor.solcast_forecast_today',
              'sensor.solcast_forecast_tomorrow',
              'sensor.solcast_pv_forecast_forecast_day_3'
            ] %}
            {% set combined = namespace(value=[]) %}
            {% for sensor in sensors %}
              {% set forecasts = state_attr(sensor, 'detailedHourly') %}
              {% if forecasts is iterable and forecasts | length > 0 %}
                {% for entry in forecasts %}
                  {% set start_time = entry.period_start | as_datetime | as_local %}
                  {% set end_time = start_time + timedelta(hours=1) %}
                  {% set new_entry = {
                    'start': start_time.strftime('%Y-%m-%dT%H:%M:%SZ'),
                    'end': end_time.strftime('%Y-%m-%dT%H:%M:%SZ'),
                    'price': (entry.pv_estimate * 1000) | round
                  } %}
                  {% set combined.value = combined.value + [new_entry] %}
                {% endfor %}
              {% endif %}
            {% endfor %}
            {{ combined.value | tojson }}

Step 2: Send the data to EVCC by MQTT

alias: (EVCC)(MQTT) Solcast
description: ""
triggers:
  - trigger: time_pattern
    minutes: /5
conditions: []
actions:
  - action: mqtt.publish
    metadata: {}
    data:
      evaluate_payload: false
      qos: 0
      retain: true
      topic: evcc/solcast
      payload: "{{state_attr('sensor.solcast_evcc_forecast', 'forecasts')}}"
mode: single

Step 3: Create the template Solar

tariffs:
  solar:
    type: custom
    forecast:
       source: mqtt
       topic: evcc/solcast
       timeout: 1h 

Vielen Dank für deine Arbeit. Bei mir läuft es bereits mit Node-Red. Home Assistant wollte irgendwie nicht.

[alexonbandit]

For those with Home Assistant and the Solcast Integration:

Step 1: Make a template sensor

template:
  - sensor:
      - name: "Solcast EVCC Forecast"
        state: "OK"  # Placeholder state, since the data is in attributes
        attributes:
          forecasts: >
            {% set sensors = [
              'sensor.solcast_forecast_today',
              'sensor.solcast_forecast_tomorrow',
              'sensor.solcast_pv_forecast_forecast_day_3'
            ] %}
            {% set combined = namespace(value=[]) %}
            {% for sensor in sensors %}
              {% set forecasts = state_attr(sensor, 'detailedHourly') %}
              {% if forecasts is iterable and forecasts | length > 0 %}
                {% for entry in forecasts %}
                  {% set start_time = entry.period_start | as_datetime | as_local %}
                  {% set end_time = start_time + timedelta(hours=1) %}
                  {% set new_entry = {
                    'start': start_time.strftime('%Y-%m-%dT%H:%M:%SZ'),
                    'end': end_time.strftime('%Y-%m-%dT%H:%M:%SZ'),
                    'price': (entry.pv_estimate * 1000) | round
                  } %}
                  {% set combined.value = combined.value + [new_entry] %}
                {% endfor %}
              {% endif %}
            {% endfor %}
            {{ combined.value | tojson }}

Step 2: Send the data to EVCC by MQTT

alias: (EVCC)(MQTT) Solcast
description: ""
triggers:
  - trigger: time_pattern
    minutes: /5
conditions: []
actions:
  - action: mqtt.publish
    metadata: {}
    data:
      evaluate_payload: false
      qos: 0
      retain: true
      topic: evcc/solcast
      payload: "{{state_attr('sensor.solcast_evcc_forecast', 'forecasts')}}"
mode: single

Step 3: Create the template Solar

tariffs:
  solar:
    type: custom
    interval: 5m
    forecast:
       source: mqtt
       topic: evcc/solcast
       timeout: 1h 

Mega cool! Vielen lieben Dank!

[Expalmi]

danke, bei mir läuft es leider nicht.

Ich habe die Configuration.yaml um die Zeilen für den Template Sensor erweitert, der Template Sensor wird angelegt.
Ich habe eine Automation für die Übertragung an den MQTT Broker angelegt, es wird wird auch etwas in den MQTT Broker geschrieben, aber die Datenfelder sind leer.

Wo kann ich den Fehler bei mir suchen?

[Nemor213]

danke, bei mir läuft es leider nicht.

Ich habe die Configuration.yaml um die Zeilen für den Template Sensor erweitert, der Template Sensor wird angelegt. Ich habe eine Automation für die Übertragung an den MQTT Broker angelegt, es wird wird auch etwas in den MQTT Broker geschrieben, aber die Datenfelder sind leer.

Wo kann ich den Fehler bei mir suchen?

Exakt das selbe Problem bei mir. Das Attribut "Forecasts" wird angelegt hat aber keine Werte.

[hossamnagy]

For those with Home Assistant and the Solcast Integration:

Step 1: Make a template sensor

template:
  - sensor:
      - name: "Solcast EVCC Forecast"
        state: "OK"  # Placeholder state, since the data is in attributes
        attributes:
          forecasts: >
            {% set sensors = [
              'sensor.solcast_forecast_today',
              'sensor.solcast_forecast_tomorrow',
              'sensor.solcast_pv_forecast_forecast_day_3'
            ] %}
            {% set combined = namespace(value=[]) %}
            {% for sensor in sensors %}
              {% set forecasts = state_attr(sensor, 'detailedHourly') %}
              {% if forecasts is iterable and forecasts | length > 0 %}
                {% for entry in forecasts %}
                  {% set start_time = entry.period_start | as_datetime | as_local %}
                  {% set end_time = start_time + timedelta(hours=1) %}
                  {% set new_entry = {
                    'start': start_time.strftime('%Y-%m-%dT%H:%M:%SZ'),
                    'end': end_time.strftime('%Y-%m-%dT%H:%M:%SZ'),
                    'price': (entry.pv_estimate * 1000) | round
                  } %}
                  {% set combined.value = combined.value + [new_entry] %}
                {% endfor %}
              {% endif %}
            {% endfor %}
            {{ combined.value | tojson }}

Step 2: Send the data to EVCC by MQTT

alias: (EVCC)(MQTT) Solcast
description: ""
triggers:
  - trigger: time_pattern
    minutes: /5
conditions: []
actions:
  - action: mqtt.publish
    metadata: {}
    data:
      evaluate_payload: false
      qos: 0
      retain: true
      topic: evcc/solcast
      payload: "{{state_attr('sensor.solcast_evcc_forecast', 'forecasts')}}"
mode: single

Step 3: Create the template Solar

tariffs:
  solar:
    type: custom
    interval: 5m
    forecast:
       source: mqtt
       topic: evcc/solcast
       timeout: 1h 

to make this work for me, I needed to use the below config in Step3 - note the tariff: solar line

• type: custom
  tariff: solar
  interval: 5m
  forecast:
  source: mqtt
  topic: evcc/solcast
  timeout: 1h

[djfanatix]

you have to change the 3 sensor to the exact names that your solcast uses.
I think mine are changed during the years

              'sensor.solcast_forecast_today',
              'sensor.solcast_forecast_tomorrow',
              'sensor.solcast_pv_forecast_forecast_day_3'

[Nemor213]

Thats it. My sensors are named in german. Now its working, thanks

'sensor.solcast_pv_forecast_prognose_heute', 'sensor.solcast_pv_forecast_prognose_morgen', 'sensor.solcast_pv_forecast_prognose_tag_3'

[Expalmi]

thanks, my sensors where named in German, like sensor.solcast_pv_forecast_prognose_heute, after changing it works like a charm.

[larknafets]

I had some problems with offset hours. My values were 1 or 2 hours before in evcc regarding to home assistant.
I assume this is due to timestamp coming already from home assistant. Seems this is already local (and not utc). But in evcc it needs to be utc.

So I needed to change the offset which now better fits to forecast data showing up in home assistant (energy dashboard) and evcc / grafana.

      - name: "evcc Solcast Forecast"
        unique_id: "evcc_solcast_forecast"
        state: "OK"
        attributes:
          forecasts: >
            {% if now().timetuple().tm_isdst==1 %}
            {% set toffset = 2 %}
            {% else %}
            {% set toffset = 1 %}
            {% endif %}
            {% set sensors = [
              'sensor.solcast_pv_forecast_prognose_heute',
              'sensor.solcast_pv_forecast_prognose_morgen',
              'sensor.solcast_pv_forecast_prognose_tag_3'
            ] %}
            {% set combined = namespace(value=[]) %}
            {% for sensor in sensors %}
              {% set forecasts = state_attr(sensor, 'detailedHourly') %}
              {% if forecasts is iterable and forecasts | length > 0 %}
                {% for entry in forecasts %}
                  {% set start_time = entry.period_start | as_datetime - timedelta(hours=toffset) %}
                  {% set end_time = start_time + timedelta(hours=1) %}
                  {% set new_entry = {
                    'start': start_time.strftime('%Y-%m-%dT%H:%M:%SZ'),
                    'end': end_time.strftime('%Y-%m-%dT%H:%M:%SZ'),
                    'value': (entry.pv_estimate * 1000) | round
                  } %}
                  {% set combined.value = combined.value + [new_entry] %}
                {% endfor %}
              {% endif %}
            {% endfor %}
            {{ combined.value | tojson }}

Please let me know if you maybe have the same issue if your timezone is also not utc/gmt.

[TheSpirit]

if have three roofs. is there any tip how to combine the solar forecast in home assistant to send it via mqtt to evcc?
Thanks

[djfanatix]

HA Solcast integration does this automatically

[TheSpirit]

i use forecast.solar, because with three roofs within solcast, i had to pay

[TheSpirit]

is there any new official solcast integration?

[typxxi]

yes, got to ha - settings - integrations and you should find something

but it was not that usefull at least in germany. the forecast was far too good and caused issued.

We use solarprognose.de cause that is a reliable source with valid data and free up to 10 kWp size.
It offers a real construction of your PV system which means planing at every level down to a single string and the shading per months.
It has an api and delivers the usual value for today, tomorrow and so on

• inverter power output
• efficiency of the inverter
• panels and strings
• the temperature coefficient of the panels
• shading per string and month

Easier options with HA integrations are

• openmeteo
• forecastsolar

Here is an overview of today results
the first 3 columns show the data for solarprognose.de, openmeteo and forecast solar

#1 line is how we are calculating out of all of these 3 our own expectations, 50% solarpro, 30% meteo 20% forecast solar.
#2 line shows the "frozen values" from this morning cause the forecast sensors are updating over the day
#3 line shows the updated forecast sensors with their most recent values for comparison

As you can see our exxpectation was 94 kWh and so far 103,5 kWh achieved.
I also have another line with remaining production I can expect for today which is 4,9 kWh, so most likely we will get 108,5 kWh

BUT: do not forget what our goal is, cause we mix those together in a way that the values shown as expectation will be the minium we will achieve in 95% of all days

We use this as the worst scenario for our planing when to charge the car and so on.
Its goal is not a 100% precise prediction for all values and possibilities, but a safe prediciton that will be achieved on 350 days .

[Timer2000]

With Update to 0.203.0 are no values in evcc from mqtt.
I think the Integration was changed.

[iseeberg79]

Struggled as well, change price to value. Then it should work again, I don't know exactly the PR..

[Timer2000]

What is to change? The Word 'price' to 'value'

[alexonbandit]

What is to change? The Word 'price' to 'value'

Yes

[Timer2000]

Thank you, that was the solution.

[phrozen77]

Quick question:

Ever after configuring evcc to read the Solcast values over MQTT like suggested here (thanks for all the hard work upfront, really!) it takes two to five minutes (!) to fully start up (after an update or any other restart).

Does anyone else notice the same behaviour?

Before the change, it'd typically be restarted within a few seconds.

Log excerpt from after updating:

Jun 09 08:05:43 evcc evcc[8076]: [main  ] INFO 2025/06/09 08:05:43 evcc 0.204.2
Jun 09 08:05:43 evcc evcc[8076]: [main  ] INFO 2025/06/09 08:05:43 using config file: /etc/evcc.yaml
Jun 09 08:05:43 evcc evcc[8076]: [db    ] INFO 2025/06/09 08:05:43 using sqlite database: /var/lib/evcc/evcc.db
Jun 09 08:05:43 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:43 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="settings" -1 <nil>
Jun 09 08:05:43 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:43 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "settings" AND sql IS NOT NULL order by type = "table" desc 1 <nil>
Jun 09 08:05:43 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:43 SELECT * FROM `settings` LIMIT 1 -1 <nil>
Jun 09 08:05:43 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:43 SELECT * FROM `settings` 33 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [mqtt  ] INFO 2025/06/09 08:05:44 connecting evcc-1755632455 at tcp://192.168.xxx.164:1883
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="configs" -1 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [mqtt  ] DEBUG 2025/06/09 08:05:44 tcp://192.168.xxxx.164:1883 connected
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "configs" AND sql IS NOT NULL order by type = "table" desc 1 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT * FROM `configs` LIMIT 1 -1 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [main  ] INFO 2025/06/09 08:05:44 listening at :7070
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT * FROM `configs` WHERE `configs`.`class` = 5 0 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT * FROM `configs` WHERE `configs`.`class` = 2 0 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT * FROM `configs` WHERE `configs`.`class` = 1 0 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [go-e  ] TRACE 2025/06/09 08:05:44 GET http://192.168.xxx.104/api/status?filter=alw
Jun 09 08:05:44 evcc evcc[8076]: [go-e  ] TRACE 2025/06/09 08:05:44 {"alw":false}
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT * FROM `configs` WHERE `configs`.`class` = 3 0 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT * FROM `configs` WHERE `configs`.`class` = 5 0 <nil>



Jun 09 08:10:00 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:10:00 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="sessions" -1 <nil>
Jun 09 08:10:00 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:10:00 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "sessions" AND sql IS NOT NULL order by type = "table" desc 1 <nil>
Jun 09 08:10:00 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:10:00 SELECT * FROM `sessions` LIMIT 1 -1 <nil>
Jun 09 08:10:00 evcc evcc[8076]: [go-e  ] TRACE 2025/06/09 08:10:00 GET http://192.168.xxx.104/api/status?filter=alw,car,eto,nrg,wh,trx,cards
Jun 09 08:10:00 evcc evcc[8076]: [go-e  ] TRACE 2025/06/09 08:10:00 {"alw":false,"eto":7298333,"car":1,"wh":8882.108,"trx":null,"nrg":[227.23,227.85,228.47,2.48,0,0,0,0,0,0,0,0,0,0,0,0],"cards":[{"name":"n/a","energy":1,"cardId":true},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false}]}
Jun 09 08:10:00 evcc evcc[8076]: [lp-1  ] DEBUG 2025/06/09 08:10:00 charge total import: 7298.333kWh
Jun 09 08:10:00 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:10:00 SELECT * FROM `sessions` WHERE `sessions`.`Loadpoint` = "Go-E" AND `sessions`.`finished` = "0001-01-01 00:00:00+00:00" 0 <nil>
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01 site config:
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01   meters:      grid ✓ pv ✓ battery ✗
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01     grid:      power ✓ energy ✗ currents ✗
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01     pv 1:      power ✓ energy ✓ currents ✗
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01   vehicles:
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01     vehicle 1: range ✓ finish ✗ status ✓ climate ✓ wakeup ✓
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01   tariffs:
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01     grid:      pricestatic
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01     feed-in:   pricestatic
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01     co2:       ✗
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01     solar:     ✓
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] INFO 2025/06/09 08:10:01 loadpoint 1:
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] INFO 2025/06/09 08:10:01   mode:        pv
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] INFO 2025/06/09 08:10:01   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] INFO 2025/06/09 08:10:01   meters:      charge ✓
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] INFO 2025/06/09 08:10:01     charge:    power ✓ energy ✓ currents ✓
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] WARN 2025/06/09 08:10:01 ignoring deprecated minCurrent: 6.000000. please configure via UI
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] WARN 2025/06/09 08:10:01 ignoring deprecated maxCurrent: 16.000000. please configure via UI
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] DEBUG 2025/06/09 08:10:01 phase timer inactive
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] DEBUG 2025/06/09 08:10:01 pv timer inactive

Note the gap between 08:05:44 and 08:10:00 (i just pressed enter a few times to make the gap more apparent).

Any pointers appreciated!

Same part of the startup, just with the additional "tariff" commented

```

Jun 09 08:27:27 evcc evcc[8129]: [main ] INFO 2025/06/09 08:27:27 evcc 0.204.2
Jun 09 08:27:27 evcc evcc[8129]: [main ] INFO 2025/06/09 08:27:27 using config file: /etc/evcc.yaml
Jun 09 08:27:27 evcc evcc[8129]: [db ] INFO 2025/06/09 08:27:27 using sqlite database: /var/lib/evcc/evcc.db
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT count() FROM sqlite_master WHERE type='table' AND name="settings" -1
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "settings" AND sql IS NOT NULL order by type = "table" desc 1
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT * FROM settings LIMIT 1 -1
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT * FROM settings 33
Jun 09 08:27:27 evcc evcc[8129]: [mqtt ] INFO 2025/06/09 08:27:27 connecting evcc-853593997 at tcp://192.168.xxx.164:1883
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT count() FROM sqlite_master WHERE type='table' AND name="configs" -1
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "configs" AND sql IS NOT NULL order by type = "table" desc 1
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT * FROM configs LIMIT 1 -1
Jun 09 08:27:27 evcc evcc[8129]: [main ] INFO 2025/06/09 08:27:27 listening at :7070
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT * FROM configs WHERE configs.class = 5 0
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT * FROM configs WHERE configs.class = 2 0
Jun 09 08:27:27 evcc evcc[8129]: [mqtt ] DEBUG 2025/06/09 08:27:27 tcp://192.168.xxx.164:1883 connected
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT * FROM configs WHERE configs.class = 1 0
Jun 09 08:27:27 evcc evcc[8129]: [go-e ] TRACE 2025/06/09 08:27:27 GET http://192.168.xxx.104/api/status?filter=alw
Jun 09 08:27:27 evcc evcc[8129]: [go-e ] TRACE 2025/06/09 08:27:27 {"alw":false}
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT * FROM configs WHERE configs.class = 3 0
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT * FROM configs WHERE configs.class = 5 0
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="sessions" -1
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "sessions" AND sql IS NOT NULL order by type = "table" desc 1
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT * FROM sessions LIMIT 1 -1
Jun 09 08:27:27 evcc evcc[8129]: [go-e ] TRACE 2025/06/09 08:27:27 GET http://192.168.xxx.104/api/status?filter=alw,car,eto,nrg,wh,trx,cards
Jun 09 08:27:27 evcc evcc[8129]: [go-e ] TRACE 2025/06/09 08:27:27 {"alw":false,"eto":7298333,"car":1,"wh":8882.108,"trx":null,"nrg":[228.78,227.23,229.4,2.79,0,0,0,0,0,0,0,0,0,0,0,0],"cards":[{"name":"n/a","energy":1,"cardId":true},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false}]}
Jun 09 08:27:27 evcc evcc[8129]: [lp-1 ] DEBUG 2025/06/09 08:27:27 charge total import: 7298.333kWh
Jun 09 08:27:27 evcc evcc[8129]: [db ] TRACE 2025/06/09 08:27:27 SELECT * FROM sessions WHERE sessions.Loadpoint = "Go-E" AND sessions.finished = "0001-01-01 00:00:00+00:00" 0
Jun 09 08:27:28 evcc evcc[8129]: [site ] INFO 2025/06/09 08:27:28 site config:
Jun 09 08:27:28 evcc evcc[8129]: [site ] INFO 2025/06/09 08:27:28 meters: grid ✓ pv ✓ battery ✗
Jun 09 08:27:28 evcc evcc[8129]: [site ] INFO 2025/06/09 08:27:28 grid: power ✓ energy ✗ currents ✗
Jun 09 08:27:28 evcc evcc[8129]: [site ] INFO 2025/06/09 08:27:28 pv 1: power ✓ energy ✓ currents ✗
Jun 09 08:27:28 evcc evcc[8129]: [site ] INFO 2025/06/09 08:27:28 vehicles:
Jun 09 08:27:28 evcc evcc[8129]: [site ] INFO 2025/06/09 08:27:28 vehicle 1: range ✓ finish ✗ status ✓ climate ✓ wakeup ✓
Jun 09 08:27:28 evcc evcc[8129]: [site ] INFO 2025/06/09 08:27:28 tariffs:
Jun 09 08:27:28 evcc evcc[8129]: [site ] INFO 2025/06/09 08:27:28 grid: pricestatic
Jun 09 08:27:28 evcc evcc[8129]: [site ] INFO 2025/06/09 08:27:28 feed-in: pricestatic
Jun 09 08:27:28 evcc evcc[8129]: [site ] INFO 2025/06/09 08:27:28 co2: ✗
Jun 09 08:27:28 evcc evcc[8129]: [site ] INFO 2025/06/09 08:27:28 solar: ✓
Jun 09 08:27:28 evcc evcc[8129]: [lp-1 ] INFO 2025/06/09 08:27:28 loadpoint 1:
Jun 09 08:27:28 evcc evcc[8129]: [lp-1 ] INFO 2025/06/09 08:27:28 mode: pv
Jun 09 08:27:28 evcc evcc[8129]: [lp-1 ] INFO 2025/06/09 08:27:28 charger: power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
Jun 09 08:27:28 evcc evcc[8129]: [lp-1 ] INFO 2025/06/09 08:27:28 meters: charge ✓
Jun 09 08:27:28 evcc evcc[8129]: [lp-1 ] INFO 2025/06/09 08:27:28 charge: power ✓ energy ✓ currents ✓
Jun 09 08:27:28 evcc evcc[8129]: [lp-1 ] WARN 2025/06/09 08:27:28 ignoring deprecated minCurrent: 6.000000. please configure via UI
Jun 09 08:27:28 evcc evcc[8129]: [lp-1 ] WARN 2025/06/09 08:27:28 ignoring deprecated maxCurrent: 16.000000. please configure via UI
Jun 09 08:27:28 evcc evcc[8129]: [lp-1 ] DEBUG 2025/06/09 08:27:28 phase timer inactive
Jun 09 08:27:28 evcc evcc[8129]: [lp-1 ] DEBUG 2025/06/09 08:27:28 pv timer inactive

</p>
</details> 

[uc0ne]

Quick question:

Ever after configuring evcc to read the Solcast values over MQTT like suggested here (thanks for all the hard work upfront, really!) it takes two to five minutes (!) to fully start up (after an update or any other restart).

Does anyone else notice the same behaviour?

Before the change, it'd typically be restarted within a few seconds.

Log excerpt from after updating:

Jun 09 08:05:43 evcc evcc[8076]: [main  ] INFO 2025/06/09 08:05:43 evcc 0.204.2
Jun 09 08:05:43 evcc evcc[8076]: [main  ] INFO 2025/06/09 08:05:43 using config file: /etc/evcc.yaml
Jun 09 08:05:43 evcc evcc[8076]: [db    ] INFO 2025/06/09 08:05:43 using sqlite database: /var/lib/evcc/evcc.db
Jun 09 08:05:43 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:43 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="settings" -1 <nil>
Jun 09 08:05:43 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:43 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "settings" AND sql IS NOT NULL order by type = "table" desc 1 <nil>
Jun 09 08:05:43 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:43 SELECT * FROM `settings` LIMIT 1 -1 <nil>
Jun 09 08:05:43 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:43 SELECT * FROM `settings` 33 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [mqtt  ] INFO 2025/06/09 08:05:44 connecting evcc-1755632455 at tcp://192.168.xxx.164:1883
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="configs" -1 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [mqtt  ] DEBUG 2025/06/09 08:05:44 tcp://192.168.xxxx.164:1883 connected
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "configs" AND sql IS NOT NULL order by type = "table" desc 1 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT * FROM `configs` LIMIT 1 -1 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [main  ] INFO 2025/06/09 08:05:44 listening at :7070
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT * FROM `configs` WHERE `configs`.`class` = 5 0 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT * FROM `configs` WHERE `configs`.`class` = 2 0 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT * FROM `configs` WHERE `configs`.`class` = 1 0 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [go-e  ] TRACE 2025/06/09 08:05:44 GET http://192.168.xxx.104/api/status?filter=alw
Jun 09 08:05:44 evcc evcc[8076]: [go-e  ] TRACE 2025/06/09 08:05:44 {"alw":false}
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT * FROM `configs` WHERE `configs`.`class` = 3 0 <nil>
Jun 09 08:05:44 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:05:44 SELECT * FROM `configs` WHERE `configs`.`class` = 5 0 <nil>



Jun 09 08:10:00 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:10:00 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="sessions" -1 <nil>
Jun 09 08:10:00 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:10:00 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "sessions" AND sql IS NOT NULL order by type = "table" desc 1 <nil>
Jun 09 08:10:00 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:10:00 SELECT * FROM `sessions` LIMIT 1 -1 <nil>
Jun 09 08:10:00 evcc evcc[8076]: [go-e  ] TRACE 2025/06/09 08:10:00 GET http://192.168.xxx.104/api/status?filter=alw,car,eto,nrg,wh,trx,cards
Jun 09 08:10:00 evcc evcc[8076]: [go-e  ] TRACE 2025/06/09 08:10:00 {"alw":false,"eto":7298333,"car":1,"wh":8882.108,"trx":null,"nrg":[227.23,227.85,228.47,2.48,0,0,0,0,0,0,0,0,0,0,0,0],"cards":[{"name":"n/a","energy":1,"cardId":true},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false}]}
Jun 09 08:10:00 evcc evcc[8076]: [lp-1  ] DEBUG 2025/06/09 08:10:00 charge total import: 7298.333kWh
Jun 09 08:10:00 evcc evcc[8076]: [db    ] TRACE 2025/06/09 08:10:00 SELECT * FROM `sessions` WHERE `sessions`.`Loadpoint` = "Go-E" AND `sessions`.`finished` = "0001-01-01 00:00:00+00:00" 0 <nil>
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01 site config:
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01   meters:      grid ✓ pv ✓ battery ✗
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01     grid:      power ✓ energy ✗ currents ✗
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01     pv 1:      power ✓ energy ✓ currents ✗
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01   vehicles:
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01     vehicle 1: range ✓ finish ✗ status ✓ climate ✓ wakeup ✓
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01   tariffs:
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01     grid:      pricestatic
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01     feed-in:   pricestatic
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01     co2:       ✗
Jun 09 08:10:01 evcc evcc[8076]: [site  ] INFO 2025/06/09 08:10:01     solar:     ✓
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] INFO 2025/06/09 08:10:01 loadpoint 1:
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] INFO 2025/06/09 08:10:01   mode:        pv
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] INFO 2025/06/09 08:10:01   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] INFO 2025/06/09 08:10:01   meters:      charge ✓
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] INFO 2025/06/09 08:10:01     charge:    power ✓ energy ✓ currents ✓
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] WARN 2025/06/09 08:10:01 ignoring deprecated minCurrent: 6.000000. please configure via UI
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] WARN 2025/06/09 08:10:01 ignoring deprecated maxCurrent: 16.000000. please configure via UI
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] DEBUG 2025/06/09 08:10:01 phase timer inactive
Jun 09 08:10:01 evcc evcc[8076]: [lp-1  ] DEBUG 2025/06/09 08:10:01 pv timer inactive

Note the gap between 08:05:44 and 08:10:00 (i just pressed enter a few times to make the gap more apparent).

Any pointers appreciated!
Same part of the startup, just with the additional "tariff" commented

I'm facing the same issue here. Restart takes a lot longer than before. Not a big problem, but I don't understand the background.

@djfanatix thanks a lot for your scripting and sharing! cool stuff!

[Expalmi]

I do have the same problem with my installation.
The mqttbroker runs on my homeassistant server. Could this be the problem?

[phrozen77]

I don’t think so - my MQTT broker is EMQX and runs in a separate container..