Neuer Adapter ioBroker.evcc
-
ich hab gerade nochmal 2 korrekturen nachgeschoben .. bitte aktualisieren..da wurden zu viele Ordner angelegt
also am besten den Status nochmal löschen
da ist noch ein Fehler seh ich gerade
-
@arteck
Wollte ich gerade noch schreiben das ziemlich viele Log-Einträge kommen. Hast Du aber selber schon gesehen. -
so jetzt
-
@arteck
Ist leider immer noch ziemlich viel im Log los.
-
@wolfi913 sagte in Neuer Adapter ioBroker.evcc:
@arteck
Ist leider immer noch ziemlich viel im Log los.
ja du musst den evcc.1.status ordner löschen
-
@wolfi913 Jup. Eben nochmal probiert, bleibt ohne Ordner:
-
@arteck sagte in Neuer Adapter ioBroker.evcc:
ja du musst den evcc.1.status ordner löschen
Hatte ich vergessen
Beim Start ein paar warnings aber dann alles ruhig.
-
@merlin123 hast du auch in den Einstellungen die checkbox gesetzt ?
-
@merlin123 sagte in Neuer Adapter ioBroker.evcc:
@wolfi913 Jup. Eben nochmal probiert, bleibt ohne Ordner:
Hast Du den Haken gesetzt?
-
@arteck
Eine Warnung vom admin ist jetzt noch hinterhergekommen:2025-02-04 18:59:52.281 - warn: admin.0 (307) evcc has an invalid jsonConfig: [{"instancePath":"/items/general/items/dissolveObjects","schemaPath":"#/definitions/checkboxProps/additionalProperties","keyword":"additionalProperties","params":{"additionalProperty":"attr"},"message":"must NOT have additional properties"},{"instancePath":"/items/general","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/9/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}] -
-
@arteck
Gerne doch.
Bei mir tauchen bisher keine außergewöhnlichen Meldungen mehr im Log auf, weder durch evcc noch durch admin.
Habe die Instanz jetzt etwa knapp 10 Minuten laufen. Vorher kam das Warning im admin nach ca. 3 Minuten und dann erneut nach weiteren 6 Minuten. Scheint also jetzt problemlos zu funktionieren. -
@wolfi913 sagte in Neuer Adapter ioBroker.evcc:
@arteck
Gerne doch.
Bei mir tauchen bisher keine außergewöhnlichen Meldungen mehr im Log auf, weder durch evcc noch durch admin.
Habe die Instanz jetzt etwa knapp 10 Minuten laufen. Vorher kam das Warning im admin nach ca. 3 Minuten und dann erneut nach weiteren 6 Minuten. Scheint also jetzt problemlos zu funktionieren.das warning kam immer wenn du in die Einstellungen vom Adapter gegangen bist..
-
@arteck
Ja, hatte ich nicht mehr auf dem Schirm das ich da noch 'nen Screenshot gemacht hatte.
Jetzt passiert da aber nichts mehr. Weder bei Neustart der Instanz noch beim Aufruf der Instanzeinstellungen. -
@wolfi913 Boah... Natürlich hab ich den Haken vergessen
Geht jetzt 
Log bleibt auch leer
-
Hallo!
Bin heute draufgekommen, das meine Werte, welche ich mittels EVCC Adapter auslese nicht mehr stimmen.
Ich bekomme auch folgende Warnung:evcc has an invalid jsonConfig: [{"instancePath":"/items/general/items/_donation/button","schemaPath":"#/patternProperties/%5E.%2B/properties/button/type","keyword":"type","params":{"type":"boolean"},"message":"must be boolean"},{"instancePath":"/items/general","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/9/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]Was muss ich tun?
-
habe jetzt, wie oben gelesen das Update installiert, jetzt schauts so aus:
evcc.0 2025-02-06 20:07:08.747 error DB closed evcc.0 2025-02-06 20:07:08.746 error Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:633:26) at Socket.emit (node:events:518:28) at TCP.<anonymous> (node:net:343:12) evcc.0 2025-02-06 20:07:08.745 error unhandled promise rejection: DB closed evcc.0 2025-02-06 20:07:08.744 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). evcc.0 2025-02-06 20:05:27.830 warn State "evcc.0.status.version" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.828 warn State "evcc.0.status.tariffPriceLoadpoints" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.826 warn State "evcc.0.status.tariffPriceHome" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.824 warn State "evcc.0.status.tariffGrid" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.821 warn State "evcc.0.status.tariffFeedIn" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.805 warn State "evcc.0.status.statistics" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.804 warn State "evcc.0.status.Statistics.Total.solarPercentage" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.798 warn State "evcc.0.status.Statistics.Total.chargedKWh" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.796 warn State "evcc.0.status.Statistics.Total.avgPrice" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.756 warn State "evcc.0.status.Statistics.ThisYear.solarPercentage" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.754 warn State "evcc.0.status.Statistics.ThisYear.chargedKWh" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.752 warn State "evcc.0.status.Statistics.ThisYear.avgPrice" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.750 warn State "evcc.0.status.Statistics.ThisYear.avgCo2" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.748 warn State "evcc.0.status.Statistics.365d.solarPercentage" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.747 warn State "evcc.0.status.Statistics.365d.chargedKWh" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.742 warn State "evcc.0.status.Statistics.365d.avgPrice" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.740 warn State "evcc.0.status.Statistics.365d.avgCo2" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.733 warn State "evcc.0.status.Statistics.30d.solarPercentage" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.409 warn State "evcc.0.status.homePower" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.407 warn State "evcc.0.status.gridConfigured" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.404 warn State "evcc.0.status.grid" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.403 warn State "evcc.0.status.Grid.Currents.2" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.400 warn State "evcc.0.status.Grid.Currents.1" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.397 warn State "evcc.0.status.Grid.Currents.0" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.395 warn State "evcc.0.status.Grid.energy" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.393 warn State "evcc.0.status.Grid.power" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.391 warn State "evcc.0.status.greenShareLoadpoints" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.389 warn State "evcc.0.status.greenShareHome" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.384 warn State "evcc.0.status.fatal" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.383 warn State "evcc.0.status.eebus" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.380 warn State "evcc.0.status.currency" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.379 warn State "evcc.0.status.bufferStartSoc" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.376 warn State "evcc.0.status.bufferSoc" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.374 warn State "evcc.0.status.batterySoc" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.370 warn State "evcc.0.status.batteryPower" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.366 warn State "evcc.0.status.batteryMode" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.362 warn State "evcc.0.status.batteryGridChargeActive" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.360 warn State "evcc.0.status.batteryEnergy" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.357 warn State "evcc.0.status.batteryDischargeControl" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.352 warn State "evcc.0.status.batteryCapacity" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.349 warn State "evcc.0.status.battery" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.343 warn State "evcc.0.status.Battery.0.controllable" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.340 warn State "evcc.0.status.Battery.0.soc" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.338 warn State "evcc.0.status.Battery.0.capacity" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.334 warn State "evcc.0.status.Battery.0.energy" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:05:27.331 warn State "evcc.0.status.Battery.0.power" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:04:01.956 warn State "evcc.0.status.Statistics.Total.solarPercentage" has no existing object, this might lead to an error in future versions evcc.0 2025-02-06 20:04:01.954 warn State "evcc.0.status.Statistics.Total.chargedKWh" has no existing object, this might lead to an error in future versions -
@jwedenig sagte in Neuer Adapter ioBroker.evcc:
habe jetzt, wie oben gelesen das Update installiert, jetzt schauts so aus:
ja aber nur bei ersten start....
-
stimmt, danke
-
@arteck
Hab bei mir Deinen überarbeiteten Adapter mal mit der neuen evcc-Versionv0.200.0getestet.
Ohne "Status Knoten auflösen" funktioniert der modifizierte Adapter.
Bei meiner 2. Instanz, bei der dieses Feature aktiviert ist, stürzt er aber leider bei mir ab.
Anbei mal zwei Debug-Logs falls Du's Dir genauer anschauen willst:
Alte Datenpunkte nicht gelöscht
debug_log_evcc1.txt
Alte Datenpunkte vor dem Start der Instanz gelöscht
debug_log_evcc1_dp-vorher-geloescht.txt
