NEWS
Easee Wallbox mit iobroker
ioBroker Allgemein
529
Beiträge
61
Kommentatoren
131.7k
Aufrufe
54
Watching
-
Hab mir jetzt mal ne Pushmeldung gemacht. Lief schon seit 23.07. nicht mehr :-(
Was meinst mit ziemlich sicher? Wenn Auto angesteckt, muss ich erst Start drücken. Wenn man jetzt Pause drückt. Gehts danach nicht mehr mit Start weiter, sondern mit resume. Wenn man sich die Stati nicht selbst wegspeichert, weiß man nicht mehr ob man nun start oder eben resume drücken muss.
Hier Log vom 23.07.
2021-07-23 20:34:57.427 - error: easee.0 (11928) Error: Request failed with status code 503 2021-07-23 20:34:57.649 - error: easee.0 (11928) Error: Request failed with status code 503 2021-07-23 20:34:57.654 - error: easee.0 (11928) 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(). 2021-07-23 20:34:57.655 - error: easee.0 (11928) unhandled promise rejection: Cannot read property 'cableLocked' of undefined 2021-07-23 20:34:57.656 - error: easee.0 (11928) TypeError: Cannot read property 'cableLocked' of undefined at Easee.setNewStatusToCharger (/opt/iobroker/node_modules/iobroker.easee/main.js:316:85) at async /opt/iobroker/node_modules/iobroker.easee/main.js:207:17 2021-07-23 20:34:57.656 - error: easee.0 (11928) Cannot read property 'cableLocked' of undefined 2021-07-23 20:34:57.671 - warn: easee.0 (11928) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-07-23 20:34:58.303 - error: host.50a2896d0707 instance system.adapter.easee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-07-23 20:34:58.307 - info: host.50a2896d0707 Restart adapter system.adapter.easee.0 because enabled 2021-07-23 20:35:00.000 - info: javascript.0 (836) script.js.ETA.ETA_5: 22 2021-07-23 20:35:00.005 - info: javascript.0 (836) script.js.Grünbeck.Schleichwasseralarm: 5.6 2021-07-23 20:35:28.356 - info: host.50a2896d0707 instance system.adapter.easee.0 started with pid 30109 2021-07-23 20:35:30.016 - error: easee.0 (30109) 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(). 2021-07-23 20:35:30.018 - error: easee.0 (30109) unhandled promise rejection: Request failed with status code 503 2021-07-23 20:35:30.020 - error: easee.0 (30109) Error: Request failed with status code 503 at createError (/opt/iobroker/node_modules/axios/lib/core/createError.js:16:15) at settle (/opt/iobroker/node_modules/axios/lib/core/settle.js:17:12) at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/axios/lib/adapters/http.js:260:11) at IncomingMessage.emit (events.js:326:22) at endReadableNT (_stream_readable.js:1241:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2021-07-23 20:35:30.020 - error: easee.0 (30109) Request failed with status code 503 2021-07-23 20:35:30.037 - warn: easee.0 (30109) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-07-23 20:35:30.654 - error: host.50a2896d0707 instance system.adapter.easee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-07-23 20:35:30.655 - info: host.50a2896d0707 Restart adapter system.adapter.easee.0 because enabled 2021-07-23 20:36:00.714 - info: host.50a2896d0707 instance system.adapter.easee.0 started with pid 30705 2021-07-23 20:36:02.741 - error: easee.0 (30705) 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(). 2021-07-23 20:36:02.743 - error: easee.0 (30705) unhandled promise rejection: Request failed with status code 503 2021-07-23 20:36:02.745 - error: easee.0 (30705) Error: Request failed with status code 503 at createError (/opt/iobroker/node_modules/axios/lib/core/createError.js:16:15) at settle (/opt/iobroker/node_modules/axios/lib/core/settle.js:17:12) at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/axios/lib/adapters/http.js:260:11) at IncomingMessage.emit (events.js:326:22) at endReadableNT (_stream_readable.js:1241:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2021-07-23 20:36:02.746 - error: easee.0 (30705) Request failed with status code 503 2021-07-23 20:36:02.764 - warn: easee.0 (30705) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-07-23 20:36:03.379 - error: host.50a2896d0707 instance system.adapter.easee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-07-23 20:36:03.380 - info: host.50a2896d0707 Restart adapter system.adapter.easee.0 because enabled 2021-07-23 20:36:03.380 - warn: host.50a2896d0707 Do not restart adapter system.adapter.easee.0 because restart loop detected@warp735 Super danke für den Fehler. Der 503 sagt aus, das die API weg war oder deine Internetverbindung gestört. Ich geh vom 1. aus sonst wäre es eher 404 gewesen.
Der Adapter müsste dann aber in einem Zustand, wartend gehen und probieren aber schmiert ab.
Schau ich mir gerne die Tage an! -
Heute morgen wieder kein geladenes Auto :-)
Adapter stieg gestern Abend wieder aus. Hab drei Pushmeldungen bekommen im Abstand von einer Minute. Er hat also dreimal versucht sich neu zu starten.
Im Log stand diesmal etwas mehr:2021-07-27 23:33:37.348 - error: easee.0 (8340) Error: Request failed with status code 504 2021-07-27 23:33:37.349 - warn: easee.0 (8340) No Chargers found! 2021-07-27 23:34:17.571 - error: easee.0 (8340) Error: Request failed with status code 504 2021-07-27 23:34:17.571 - warn: easee.0 (8340) No Chargers found! 2021-07-27 23:34:57.826 - error: easee.0 (8340) Error: Request failed with status code 504 2021-07-27 23:34:57.826 - warn: easee.0 (8340) No Chargers found! 2021-07-27 23:35:28.047 - error: easee.0 (8340) Error: Request failed with status code 503 2021-07-27 23:35:28.048 - warn: easee.0 (8340) No Chargers found! 2021-07-27 23:35:58.316 - error: easee.0 (8340) Error: Request failed with status code 503 2021-07-27 23:35:58.316 - warn: easee.0 (8340) No Chargers found! 2021-07-27 23:36:38.543 - error: easee.0 (8340) Error: Request failed with status code 504 2021-07-27 23:36:38.544 - warn: easee.0 (8340) No Chargers found! 2021-07-27 23:38:16.489 - error: easee.0 (8340) Error: Request failed with status code 502 2021-07-27 23:38:16.489 - warn: easee.0 (8340) No Chargers found! 2021-07-27 23:38:16.517 - error: easee.0 (8340) Error: Request failed with status code 502 2021-07-27 23:38:16.773 - error: easee.0 (8340) Error: Request failed with status code 503 2021-07-27 23:38:16.779 - error: easee.0 (8340) 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(). 2021-07-27 23:38:16.779 - error: easee.0 (8340) unhandled promise rejection: Cannot read property 'cableLocked' of undefined 2021-07-27 23:38:16.780 - error: easee.0 (8340) TypeError: Cannot read property 'cableLocked' of undefined at Easee.setNewStatusToCharger (/opt/iobroker/node_modules/iobroker.easee/main.js:316:85) at async /opt/iobroker/node_modules/iobroker.easee/main.js:207:17 2021-07-27 23:38:16.781 - error: easee.0 (8340) Cannot read property 'cableLocked' of undefined 2021-07-27 23:38:16.804 - warn: easee.0 (8340) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-07-27 23:38:17.412 - error: host.50a2896d0707 instance system.adapter.easee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-07-27 23:38:17.416 - info: host.50a2896d0707 Restart adapter system.adapter.easee.0 because enabled 2021-07-27 23:38:47.446 - info: host.50a2896d0707 instance system.adapter.easee.0 started with pid 15376 2021-07-27 23:38:49.153 - error: easee.0 (15376) 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(). 2021-07-27 23:38:49.155 - error: easee.0 (15376) unhandled promise rejection: Request failed with status code 503 2021-07-27 23:38:49.156 - error: easee.0 (15376) Error: Request failed with status code 503 at createError (/opt/iobroker/node_modules/axios/lib/core/createError.js:16:15) at settle (/opt/iobroker/node_modules/axios/lib/core/settle.js:17:12) at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/axios/lib/adapters/http.js:260:11) at IncomingMessage.emit (events.js:326:22) at endReadableNT (_stream_readable.js:1241:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2021-07-27 23:38:49.157 - error: easee.0 (15376) Request failed with status code 503 2021-07-27 23:38:49.172 - warn: easee.0 (15376) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-07-27 23:38:49.850 - error: host.50a2896d0707 instance system.adapter.easee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-07-27 23:38:49.851 - info: host.50a2896d0707 Restart adapter system.adapter.easee.0 because enabled 2021-07-27 23:39:19.896 - info: host.50a2896d0707 instance system.adapter.easee.0 started with pid 16020 2021-07-27 23:40:47.213 - error: easee.0 (16020) Error: Request failed with status code 504 2021-07-27 23:40:57.439 - error: easee.0 (16020) Error: Request failed with status code 504 2021-07-27 23:40:57.446 - error: easee.0 (16020) 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(). 2021-07-27 23:40:57.447 - error: easee.0 (16020) unhandled promise rejection: Cannot read property 'cableLocked' of undefined 2021-07-27 23:40:57.448 - error: easee.0 (16020) TypeError: Cannot read property 'cableLocked' of undefined at Easee.setNewStatusToCharger (/opt/iobroker/node_modules/iobroker.easee/main.js:316:85) at async /opt/iobroker/node_modules/iobroker.easee/main.js:207:17 2021-07-27 23:40:57.448 - error: easee.0 (16020) Cannot read property 'cableLocked' of undefined 2021-07-27 23:40:57.463 - warn: easee.0 (16020) Terminated (UNCAUGHT_EXCEPTION): Without reason -
Heute morgen wieder kein geladenes Auto :-)
Adapter stieg gestern Abend wieder aus. Hab drei Pushmeldungen bekommen im Abstand von einer Minute. Er hat also dreimal versucht sich neu zu starten.
Im Log stand diesmal etwas mehr:2021-07-27 23:33:37.348 - error: easee.0 (8340) Error: Request failed with status code 504 2021-07-27 23:33:37.349 - warn: easee.0 (8340) No Chargers found! 2021-07-27 23:34:17.571 - error: easee.0 (8340) Error: Request failed with status code 504 2021-07-27 23:34:17.571 - warn: easee.0 (8340) No Chargers found! 2021-07-27 23:34:57.826 - error: easee.0 (8340) Error: Request failed with status code 504 2021-07-27 23:34:57.826 - warn: easee.0 (8340) No Chargers found! 2021-07-27 23:35:28.047 - error: easee.0 (8340) Error: Request failed with status code 503 2021-07-27 23:35:28.048 - warn: easee.0 (8340) No Chargers found! 2021-07-27 23:35:58.316 - error: easee.0 (8340) Error: Request failed with status code 503 2021-07-27 23:35:58.316 - warn: easee.0 (8340) No Chargers found! 2021-07-27 23:36:38.543 - error: easee.0 (8340) Error: Request failed with status code 504 2021-07-27 23:36:38.544 - warn: easee.0 (8340) No Chargers found! 2021-07-27 23:38:16.489 - error: easee.0 (8340) Error: Request failed with status code 502 2021-07-27 23:38:16.489 - warn: easee.0 (8340) No Chargers found! 2021-07-27 23:38:16.517 - error: easee.0 (8340) Error: Request failed with status code 502 2021-07-27 23:38:16.773 - error: easee.0 (8340) Error: Request failed with status code 503 2021-07-27 23:38:16.779 - error: easee.0 (8340) 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(). 2021-07-27 23:38:16.779 - error: easee.0 (8340) unhandled promise rejection: Cannot read property 'cableLocked' of undefined 2021-07-27 23:38:16.780 - error: easee.0 (8340) TypeError: Cannot read property 'cableLocked' of undefined at Easee.setNewStatusToCharger (/opt/iobroker/node_modules/iobroker.easee/main.js:316:85) at async /opt/iobroker/node_modules/iobroker.easee/main.js:207:17 2021-07-27 23:38:16.781 - error: easee.0 (8340) Cannot read property 'cableLocked' of undefined 2021-07-27 23:38:16.804 - warn: easee.0 (8340) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-07-27 23:38:17.412 - error: host.50a2896d0707 instance system.adapter.easee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-07-27 23:38:17.416 - info: host.50a2896d0707 Restart adapter system.adapter.easee.0 because enabled 2021-07-27 23:38:47.446 - info: host.50a2896d0707 instance system.adapter.easee.0 started with pid 15376 2021-07-27 23:38:49.153 - error: easee.0 (15376) 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(). 2021-07-27 23:38:49.155 - error: easee.0 (15376) unhandled promise rejection: Request failed with status code 503 2021-07-27 23:38:49.156 - error: easee.0 (15376) Error: Request failed with status code 503 at createError (/opt/iobroker/node_modules/axios/lib/core/createError.js:16:15) at settle (/opt/iobroker/node_modules/axios/lib/core/settle.js:17:12) at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/axios/lib/adapters/http.js:260:11) at IncomingMessage.emit (events.js:326:22) at endReadableNT (_stream_readable.js:1241:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2021-07-27 23:38:49.157 - error: easee.0 (15376) Request failed with status code 503 2021-07-27 23:38:49.172 - warn: easee.0 (15376) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-07-27 23:38:49.850 - error: host.50a2896d0707 instance system.adapter.easee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-07-27 23:38:49.851 - info: host.50a2896d0707 Restart adapter system.adapter.easee.0 because enabled 2021-07-27 23:39:19.896 - info: host.50a2896d0707 instance system.adapter.easee.0 started with pid 16020 2021-07-27 23:40:47.213 - error: easee.0 (16020) Error: Request failed with status code 504 2021-07-27 23:40:57.439 - error: easee.0 (16020) Error: Request failed with status code 504 2021-07-27 23:40:57.446 - error: easee.0 (16020) 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(). 2021-07-27 23:40:57.447 - error: easee.0 (16020) unhandled promise rejection: Cannot read property 'cableLocked' of undefined 2021-07-27 23:40:57.448 - error: easee.0 (16020) TypeError: Cannot read property 'cableLocked' of undefined at Easee.setNewStatusToCharger (/opt/iobroker/node_modules/iobroker.easee/main.js:316:85) at async /opt/iobroker/node_modules/iobroker.easee/main.js:207:17 2021-07-27 23:40:57.448 - error: easee.0 (16020) Cannot read property 'cableLocked' of undefined 2021-07-27 23:40:57.463 - warn: easee.0 (16020) Terminated (UNCAUGHT_EXCEPTION): Without reason -
Ist ein Hybrid. Von daher wurscht ob Akku voll ist oder nicht :-)
Brauch ihn heute aber sowieso nicht.Aber die Api wird ja wohl kaum nur bei mir weg sein. Haben denn die anderen keine Probleme? :face_with_rolling_eyes:
@warp735 ich habe hin und wieder die selben Probleme..
habe auch eine Abfrage eingebaut ob der Adapter läuft, das funktioniert aber nicht mehr.
Worüber prüfst du, ob er noch läuft? Weil darüber kann man ja dann einen Restart des Adapters auslösen. Bisher lief er dann wieder an.. -
@warp735 ich habe hin und wieder die selben Probleme..
habe auch eine Abfrage eingebaut ob der Adapter läuft, das funktioniert aber nicht mehr.
Worüber prüfst du, ob er noch läuft? Weil darüber kann man ja dann einen Restart des Adapters auslösen. Bisher lief er dann wieder an..Aktuell frage ich nur den easee.0.online auf true ab und schick mir ne Pushnachricht. Einen automatischen Neustart bzw wiederherstellen der Verbindung muss meiner Meinung nach der Adapter selber machen. Aber so bringts ja auch nix und werd da selber was machen müssen.
Laut Easse Cloud Status gabs gestern keine Fehler. Aber kurze Aussetzer werden die wohl auch garnicht auflisten ;)Per App komme ich aktuell jedenfalls ganz normal auf die Box. Adapter ist aber rot.
-
Der Adapter darf mit dem Fehler nicht aussteigen ist ein Bug, ich schau dabei. Ihr müsst keine Extrarunde für den restart des Adapters machen, lass lieber die Energie nutzen das Teil rund zu bekommen.
Zeit ist halt der limitierende Faktor derzeit! -
gerade zufällig im Log gesehen, dass der Adapter wieder weg war. Offenbar aber nur kurz. Ist noch grün.
host.50a2896d0707 2021-07-28 11:37:08.462 error instance system.adapter.easee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) easee.0 2021-07-28 11:37:07.862 warn (12699) Terminated (UNCAUGHT_EXCEPTION): Without reason easee.0 2021-07-28 11:37:07.837 error (12699) Cannot read property 'forEach' of undefined easee.0 2021-07-28 11:37:07.836 error at processTicksAndRejections (internal/process/task_queues.js:97:5) easee.0 2021-07-28 11:37:07.836 error at runMicrotasks (<anonymous>) easee.0 2021-07-28 11:37:07.836 error at /opt/iobroker/node_modules/iobroker.easee/main.js:217:26 easee.0 2021-07-28 11:37:07.836 error at Easee.setNewSessionToCharger (/opt/iobroker/node_modules/iobroker.easee/main.js:898:25) easee.0 2021-07-28 11:37:07.836 error (12699) TypeError: Cannot read property 'forEach' of undefined easee.0 2021-07-28 11:37:07.835 error (12699) unhandled promise rejection: Cannot read property 'forEach' of undefined easee.0 2021-07-28 11:37:07.835 error (12699) 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(). easee.0 2021-07-28 11:37:07.834 error (12699) Error: Request failed with status code 504 easee.0 2021-07-28 11:36:51.917 warn (12699) No Chargers found! easee.0 2021-07-28 11:36:51.916 error (12699) Error: Request failed with status code 504 easee.0 2021-07-28 11:35:28.337 warn (12699) No Chargers found! easee.0 2021-07-28 11:35:28.336 error (12699) Error: Request failed with status code 503 bmw.0 2021-07-28 11:35:23.331 info (32262) BMW updated car data for 2 car(s) javascript.0 2021-07-28 11:35:00.005 info (6903) script.js.Grünbeck.Schleichwasseralarm: 153.5 javascript.0 2021-07-28 11:35:00.000 info (6903) script.js.ETA.ETA_5: 9 easee.0 2021-07-28 11:34:58.098 warn (12699) No Chargers found! easee.0 2021-07-28 11:34:58.094 error (12699) Error: Request failed with status code 503 -
Ist wieder abgeschmiert (rot)
Glaub ich mach das jetzt mal über die App und warte auf n Adapter Update. Zig mal am Tag das Ding reseten bringt ja auch nix.host.50a2896d0707 2021-07-28 14:36:01.618 warn Do not restart adapter system.adapter.easee.0 because restart loop detected host.50a2896d0707 2021-07-28 14:36:01.618 info Restart adapter system.adapter.easee.0 because enabled host.50a2896d0707 2021-07-28 14:36:01.617 error instance system.adapter.easee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) easee.0 2021-07-28 14:36:01.015 warn (22507) Terminated (UNCAUGHT_EXCEPTION): Without reason easee.0 2021-07-28 14:36:00.994 error (22507) Request failed with status code 504 easee.0 2021-07-28 14:36:00.994 error at processTicksAndRejections (internal/process/task_queues.js:84:21) easee.0 2021-07-28 14:36:00.994 error at endReadableNT (_stream_readable.js:1241:12) easee.0 2021-07-28 14:36:00.994 error at IncomingMessage.emit (events.js:326:22) easee.0 2021-07-28 14:36:00.994 error at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/axios/lib/adapters/http.js:260:11) easee.0 2021-07-28 14:36:00.994 error at settle (/opt/iobroker/node_modules/axios/lib/core/settle.js:17:12) easee.0 2021-07-28 14:36:00.994 error at createError (/opt/iobroker/node_modules/axios/lib/core/createError.js:16:15) easee.0 2021-07-28 14:36:00.994 error (22507) Error: Request failed with status code 504 easee.0 2021-07-28 14:36:00.992 error (22507) unhandled promise rejection: Request failed with status code 504 easee.0 2021-07-28 14:36:00.989 error (22507) 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(). host.50a2896d0707 2021-07-28 14:35:49.145 info instance system.adapter.easee.0 started with pid 22507 host.50a2896d0707 2021-07-28 14:35:19.101 info Restart adapter system.adapter.easee.0 because enabled host.50a2896d0707 2021-07-28 14:35:19.101 error instance system.adapter.easee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) easee.0 2021-07-28 14:35:18.510 warn (21865) Terminated (UNCAUGHT_EXCEPTION): Without reason easee.0 2021-07-28 14:35:18.496 error (21865) Request failed with status code 503 easee.0 2021-07-28 14:35:18.496 error at processTicksAndRejections (internal/process/task_queues.js:84:21) easee.0 2021-07-28 14:35:18.496 error at endReadableNT (_stream_readable.js:1241:12) easee.0 2021-07-28 14:35:18.496 error at IncomingMessage.emit (events.js:326:22) easee.0 2021-07-28 14:35:18.496 error at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/axios/lib/adapters/http.js:260:11) easee.0 2021-07-28 14:35:18.496 error at settle (/opt/iobroker/node_modules/axios/lib/core/settle.js:17:12) easee.0 2021-07-28 14:35:18.496 error at createError (/opt/iobroker/node_modules/axios/lib/core/createError.js:16:15) easee.0 2021-07-28 14:35:18.496 error (21865) Error: Request failed with status code 503 easee.0 2021-07-28 14:35:18.494 error (21865) unhandled promise rejection: Request failed with status code 503 easee.0 2021-07-28 14:35:18.492 error (21865) 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(). host.50a2896d0707 2021-07-28 14:35:16.839 info instance system.adapter.easee.0 started with pid 21865 host.50a2896d0707 2021-07-28 14:34:46.789 info Restart adapter system.adapter.easee.0 because enabled host.50a2896d0707 2021-07-28 14:34:46.784 error instance system.adapter.easee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) easee.0 2021-07-28 14:34:46.173 warn (8911) Terminated (UNCAUGHT_EXCEPTION): Without reason easee.0 2021-07-28 14:34:46.157 error (8911) Cannot read property 'cableLocked' of undefined easee.0 2021-07-28 14:34:46.157 error at async /opt/iobroker/node_modules/iobroker.easee/main.js:207:17 easee.0 2021-07-28 14:34:46.157 error at Easee.setNewStatusToCharger (/opt/iobroker/node_modules/iobroker.easee/main.js:316:85) easee.0 2021-07-28 14:34:46.157 error (8911) TypeError: Cannot read property 'cableLocked' of undefined easee.0 2021-07-28 14:34:46.156 error (8911) unhandled promise rejection: Cannot read property 'cableLocked' of undefined easee.0 2021-07-28 14:34:46.155 error (8911) 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(). easee.0 2021-07-28 14:34:46.150 error (8911) Error: Request failed with status code 503 easee.0 2021-07-28 14:34:45.890 error (8911) Error: Request failed with status code 502 easee.0 2021-07-28 14:33:43.426 warn (8911) No Chargers found! easee.0 2021-07-28 14:33:43.426 error (8911) Error: Request failed with status code 504 easee.0 2021-07-28 14:33:03.145 warn (8911) No Chargers found! easee.0 2021-07-28 14:33:03.140 error (8911) Error: Request failed with status code 504 -
Hey,
ich habe mir jetzt auch die version 1.0.3 drauf gemacht und logge es die tage mal mit ...
bisher sieht es aber ganz gut aus..eine Frage an alle .. in welchen Intervall lasst ihr ihn laufen ? was habt ihr da eingestellt wenn ihr PV laden damit macht ?
-
Hey,
ich habe mir jetzt auch die version 1.0.3 drauf gemacht und logge es die tage mal mit ...
bisher sieht es aber ganz gut aus..eine Frage an alle .. in welchen Intervall lasst ihr ihn laufen ? was habt ihr da eingestellt wenn ihr PV laden damit macht ?
-
@newan sagte in Easee Wallbox mit iobroker:
Nutz doch SignalR das ist dann in echtzeit
das habe ich aktiv leider nicht wirklich rausbekommen was es macht ;)
was genau steht da hinter ? und in wie weit steht das damit dem Intervall im zusammenhang ?ich schreibe ja den Parameter ....config.dynamicChargerCurrent bekomme ich ihn dann auch bestätigt oder erst nach einem erneuten lesen welches dann über das Interfall kommt ?
-
@newan sagte in Easee Wallbox mit iobroker:
Nutz doch SignalR das ist dann in echtzeit
das habe ich aktiv leider nicht wirklich rausbekommen was es macht ;)
was genau steht da hinter ? und in wie weit steht das damit dem Intervall im zusammenhang ?ich schreibe ja den Parameter ....config.dynamicChargerCurrent bekomme ich ihn dann auch bestätigt oder erst nach einem erneuten lesen welches dann über das Interfall kommt ?
@scotty89 Also Grundsätzlich ist das Intervall ja das die Daten in einem Bestimmten Zyklus abgeholt werden.
Den kannst du relativ hoch setzen und da über SignalR nicht alle Daten kommen wie Energieverbräuche etc. z.b 5 mal am Tag.Dann wählst du SignalR aus und der Adapter registriert sich an der Cloud, die schickt dann bei einer Änderung das Event direkt zum Adapter, also quasi live.
Wie gut das ganze funktioniert weiß ich nicht, da das noch nie einer getestet hat :anguished:
663
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge