NEWS
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. :+1: -
@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. :+1:@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. :+1:das warning kam immer wenn du in die Einstellungen vom Adapter gegangen bist..
-
@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. :+1:das warning kam immer wenn du in die Einstellungen vom Adapter gegangen bist..
-
@merlin123 sagte in Neuer Adapter ioBroker.evcc:
@wolfi913 Jup. Eben nochmal probiert, bleibt ohne Ordner:
Hast Du den Haken gesetzt?
-
@wolfi913 Boah... Natürlich hab ich den Haken vergessen :P Geht jetzt :D
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?
-
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 -
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....
-
@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....
-
so hab da mal ne anpassung gemacht...
evcc hat die Strukur geändert .. bewusst oder unbewusst (wird sich zeigen)
der Adapter hat jetzt in den Einstellungen
bekommen..für alle die eine Ordnerstruktur bevorzugen..
dann wird der Status Ordner so gebildet
untendrunter sind dann natürlich die alten Objekte.. wobei hier auch evcc nicht alles liefert..
am besten mal den Status Ordner löschen dann wird der nochmal richtig angelegt....
GIT Install https://github.com/arteck/ioBroker.evcc
sollte es ok sein .. mach ich ein PR
@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 -
@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 -
so weiter gehts.. einmal von GIT installieren..
und LOG posten es reicht aber nur die error zeile
die mit error pfad anfängt
-
@arteck sagte in Neuer Adapter ioBroker.evcc:
die mit error pfad anfängt
Diese hier?
2025-02-27 18:30:46.923 - error: evcc.1 (8091) Error: The state contains the forbidden properties start, end, price! -
@arteck sagte in Neuer Adapter ioBroker.evcc:
such im Log nach pfad
Sorry, aber da sind in meinem Log keine Treffer zu finden. Auch nicht nach nochmaliger Installation und Löschung aller DP vor Start der Instanz. Ich hatte die Zeile genommen, die Deiner Beschreibung am nächsten kam.
Ergänzung:
Evtl. (ich kenn mich da aber leider zu wenig aus) könnte das hier weiterhelfen2025-02-27 22:20:25.411 - error: evcc.1 (9170) Error: The state contains the forbidden properties start, end, price! at Validator.validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/validator.js:299:13) at Evcc._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:4984:21) at Evcc.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:4962:17) at Evcc.setStatusEvcc (/opt/iobroker/node_modules/iobroker.evcc/build/main.js:373:46) at /opt/iobroker/node_modules/iobroker.evcc/build/main.js:219:22 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-02-27 22:20:25.411 - error: evcc.1 (9170) The state contains the forbidden properties start, end, price! 2025-02-27 22:20:25.411 - error: evcc.1 (9170) 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(). -
@arteck sagte in Neuer Adapter ioBroker.evcc:
such im Log nach pfad
Sorry, aber da sind in meinem Log keine Treffer zu finden. Auch nicht nach nochmaliger Installation und Löschung aller DP vor Start der Instanz. Ich hatte die Zeile genommen, die Deiner Beschreibung am nächsten kam.
Ergänzung:
Evtl. (ich kenn mich da aber leider zu wenig aus) könnte das hier weiterhelfen2025-02-27 22:20:25.411 - error: evcc.1 (9170) Error: The state contains the forbidden properties start, end, price! at Validator.validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/validator.js:299:13) at Evcc._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:4984:21) at Evcc.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:4962:17) at Evcc.setStatusEvcc (/opt/iobroker/node_modules/iobroker.evcc/build/main.js:373:46) at /opt/iobroker/node_modules/iobroker.evcc/build/main.js:219:22 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-02-27 22:20:25.411 - error: evcc.1 (9170) The state contains the forbidden properties start, end, price! 2025-02-27 22:20:25.411 - error: evcc.1 (9170) 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().@wolfi913 dann hast du nicht das richtige repo
von hier installiert ??
zigbee hab ich, zwave auch, nuc's genauso und HA auch
-
@wolfi913 dann hast du nicht das richtige repo
von hier installiert ??
@arteck sagte in Neuer Adapter ioBroker.evcc:
dann hast du nicht das richtige repo
Eigentlich schon das richtige verwendet.
Sonst dürfte ja normalerweise auch das im Log nicht auftauchen
Evcc.setStatusEvcc (/opt/iobroker/node_modules/iobroker.evcc/build/main.js:373:46)
Das ist ja von Dir neu eingebaut worden.Als Ergänzung mal rausgesucht:
2025-02-27 21:58:00.153 - info: host.iobroker-test iobroker url https://github.com/arteck/ioBroker.evcc --host iobroker-test --debug 2025-02-27 21:58:01.157 - info: host.iobroker-test iobroker install arteck/ioBroker.evcc#cdceb4f9d8037ed7c952acd3a2d66e4f9b570dee 2025-02-27 21:58:01.247 - info: host.iobroker-test iobroker NPM version: 10.8.2 2025-02-27 21:58:01.247 - info: host.iobroker-test iobroker Installing arteck/ioBroker.evcc#cdceb4f9d8037ed7c952acd3a2d66e4f9b570dee... (System call) -
@arteck sagte in Neuer Adapter ioBroker.evcc:
dann hast du nicht das richtige repo
Eigentlich schon das richtige verwendet.
Sonst dürfte ja normalerweise auch das im Log nicht auftauchen
Evcc.setStatusEvcc (/opt/iobroker/node_modules/iobroker.evcc/build/main.js:373:46)
Das ist ja von Dir neu eingebaut worden.Als Ergänzung mal rausgesucht:
2025-02-27 21:58:00.153 - info: host.iobroker-test iobroker url https://github.com/arteck/ioBroker.evcc --host iobroker-test --debug 2025-02-27 21:58:01.157 - info: host.iobroker-test iobroker install arteck/ioBroker.evcc#cdceb4f9d8037ed7c952acd3a2d66e4f9b570dee 2025-02-27 21:58:01.247 - info: host.iobroker-test iobroker NPM version: 10.8.2 2025-02-27 21:58:01.247 - info: host.iobroker-test iobroker Installing arteck/ioBroker.evcc#cdceb4f9d8037ed7c952acd3a2d66e4f9b570dee... (System call)Ich habe offensichtlich das selbe Problem. Nach meinem Update von evcc auf die aktuelle Version bekomme ich in iobroker einige (für mich wichtige) Werte nicht mehr angezeigt, wie gridPower
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"}] -
Ich habe offensichtlich das selbe Problem. Nach meinem Update von evcc auf die aktuelle Version bekomme ich in iobroker einige (für mich wichtige) Werte nicht mehr angezeigt, wie gridPower
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"}]@christobal0815 Die neuste Adapter Version von Github (wie oben beschrieben) hast Du installiert?
-
@christobal0815 Die neuste Adapter Version von Github (wie oben beschrieben) hast Du installiert?
@merlin123 said in Neuer Adapter ioBroker.evcc:
@christobal0815 Die neuste Adapter Version von Github (wie oben beschrieben) hast Du installiert?
Ich halte meine Adapter via iobroker Up-to-date. Ich bin auf Version 0.1.1
Ob ich ihn damals über github installiert habe oder von iobroker, kann ich nicht mehr sagen. Soll ich den Adapter deinstallieren und über github die Version 0.1.1 erneut installieren? -
@merlin123 said in Neuer Adapter ioBroker.evcc:
@christobal0815 Die neuste Adapter Version von Github (wie oben beschrieben) hast Du installiert?
Ich halte meine Adapter via iobroker Up-to-date. Ich bin auf Version 0.1.1
Ob ich ihn damals über github installiert habe oder von iobroker, kann ich nicht mehr sagen. Soll ich den Adapter deinstallieren und über github die Version 0.1.1 erneut installieren?Ich habe die letzten Posts hier gelesen, aber leider nicht ganz verstanden, wie ich das Problem nun lösen kann. Offensichtlich hat es etwas mit dem Format der bestehenden Datenpunkte zutun? Soll ich nun einfach eine neue Instanz für .evcc in iobroker anlegen und die alte Instanz deaktivieren? Oder nur selektiv die betroffenen Datenpunkte im Objektbaum entfernen? Legen diese sich dann wieder neu an?
Danke
Support us
618
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge