Hi!
Ich habe auch eine Terra Box von ABB und wollte diese jetzt mit iobroker verbinden. Leider benötige ich aber in Terra Config ein Zertifikat:
"1.Format supported:'.pfx','.cer','.pem'
2.Encoding format supported:Basic64"
Was habt ihr da hoch geladen? Ich habe mit openssl verschiedene Zertifikate generiert, leider klappte aber nichts. 
Danach kann ich ja erst den tollen Adapter ausprobieren.
Edit: Hat sich erledigt, falls noch mal jemand sucht. Das Protokoll muss auf ws stehen und nicht auf wss.
Nun habe ich die Wallbox verbunden und es sieht alles gut aus.
Eine Frage habe ich, kann ich denn mehrer Autos unterscheiden?
Ich habe verstanden, dass du alle Werte die es gibt weg schreibst. Oder gibt es noch Werte die noch nicht weg geschrieben werden?
Dann müsste ich mir die mal anzeigen lassen....
@baeckerman83 sagte in Alpha Testing: OCPP Wallbox Adapter:
Eine Frage habe ich, kann ich denn mehrer Autos unterscheiden?
Nein, der Charger bekommt im Normalfall keine Daten von deinem Auto. Für viele neuere Autos gibt es allerdings auch Adapter, villt. hilft das weiter.
@foxriver76 Danke für deine schnelle Antwort. Das ist schade. Hatte gehofft, das wird ne ID ausgetauscht. Dann hätte man auch was bauen können statt RFID Chip über diese ID freischalten. Aber gut, dann weiß ich nur wieviel meine Autos geladen haben.
Ich habe noch eine Fragen.
Ich wolle jetzt den Energie Stand auslesen, und zwar per NodeRed. Damit ich ihn immer Speichern kann wenn der Status wieder auf "Available" springt. Leider bekomm ich aber statt den Value aber: ""Object for state ocpp.1..Wally.meterValues.Energy_Active_Import_Register do not exist""
Kann Energy_Active_Import_Register denn nicht einfach ausgelesen werden? In der Objekt Liste ist der Wert gesetzt und ich kann ihn auch sehen.
Edit: Ich glaube mein Problem ist das /, aber wie bekomme ich das Weg aus der ID: "ocpp.1./Wally.meterValues.Energy_Active_Import_Register"
@baeckerman83 hm passiert das im JavaScript Adapter? Der Slash ist eigentlich erlaubt und sollte nicht ersetzt werden.
@foxriver76 ich benutze nicht den Javascript Adapter, ich benutze den NodeRed Adapter. Auch eine Abfrage per HTTP Rest API ist durch den / nur über einen Umweg möglich.
@fl4sh-0 said in Alpha Testing: OCPP Wallbox Adapter:
Charglimit
Hi!
Wie hast du das ChargeLimit gesetzt? Ich habe es an der Box per BT auf 6 A gestellt und wollte es jetzt per iobroker auf 16 A stellen. Iobroker zeigt es auch an, aber auf L1 kommt trotzdem nur 6 A an. (Mein Auto lädt nur 1 Phasig, der neue ab September dann dreiphasig).
Stelle ich es an der Box auf 16 A, dann steht da auch 16 A. 
@baeckerman83 said in Alpha Testing: OCPP Wallbox Adapter:
@fl4sh-0 said in Alpha Testing: OCPP Wallbox Adapter:
Charglimit
Hi!
Wie hast du das ChargeLimit gesetzt? Ich habe es an der Box per BT auf 6 A gestellt und wollte es jetzt per iobroker auf 16 A stellen. Iobroker zeigt es auch an, aber auf L1 kommt trotzdem nur 6 A an. (Mein Auto lädt nur 1 Phasig, der neue ab September dann dreiphasig).
Stelle ich es an der Box auf 16 A, dann steht da auch 16 A.
Moin, du musst das Chargelimit in der App via BT auf 16A einstellen. Dann sollte sich Current_Offered auf 16A ändern. Das ist dann die maximale Leistung die von der Wallbox abgegeben werden kann. Anschließen kannst du über den iobroker zwischen 0A und 6A -16A steuern und immer nur ganze Zahlen. Leider geht der Ladezyklus erst ab 6A los.
Gruß
@fl4sh-0 Ok, ich habe es an der Box wieder auf 16A gestellt. Current_Offered steht auch wieder auf 16A.
Jetzt müsste ich doch einfach das chargeLimit ändern? zum Beispiel auf 6A, oder? Bei mir bleibt das Feld aber auch rot, also nicht bestätigt.
@baeckerman83 @fl4sh-0 leider klappt auch transactionActive nicht, wenn ich es auf false stelle wenn das Auto dran hängt stoppt er den Lade Vorgang nicht. Du hattest doch auch die Version 1.5.2, muss da noch was aktiviert werden, dass ich das von außen steuern kann?
Ich stelle zur Zeit die Werte direkt auf der Objekt Seite ein da ich dort gleich eine Rückmeldung bekomme.
@foxriver76 Ich habe jetzt noch mal Versucht das ChargeLimit und die Transaction zu setzen.
Nun habe ich Fehlermeldungen bekommen im Log. Ich bin mir aber sicher, dass die Verbindung zur Box stabil ist. An was könnte das noch liegen? Connected ist auch Dauerhaft auf true, letzte Änderung war als ich mal den Netzwerk Stecker am 30.06. gezogen habe, passt also.
ocpp.1
2022-07-02 21:18:30.049 error Cannot execute command "transactionActive" for "/Wally": Timeout for message dd212e27-10ed-48d5-a8b4-89c45a8b6d01
ocpp.1
2022-07-02 21:18:29.298 info Received MeterValues from "/Wally"
ocpp.1
2022-07-02 21:18:00.090 error Cannot execute command "chargeLimit" for "/Wally": Socket closed 227ec557-f815-40de-87ba-fd2ff2480092
ocpp.1
2022-07-02 21:17:57.314 info Received MeterValues from "/Wally"
ocpp.1
2022-07-02 21:17:30.190 error Cannot execute command "chargeLimit" for "/Wally": Timeout for message ef94db1b-491e-42b1-bbb3-2d82cd0b84e3
ocpp.1
2022-07-02 21:17:25.420 info Received MeterValues from "/Wally"
ocpp.1
2022-07-02 21:16:53.434 info Received MeterValues from "/Wally"
ocpp.1
2022-07-02 21:16:21.536 info Received MeterValues from "/Wally"
ocpp.1
2022-07-02 21:15:49.539 info Received MeterValues from "/Wally"
ocpp.1
2022-07-02 21:15:30.051 error Cannot execute command "chargeLimit" for "/Wally": Timeout for message b514b321-05e7-4bb2-a000-a772ba85f7ed
Guten Morgen
Tolles Projekt!
Ich habe mir eine günstige XCharge Wallbox gekauft.
Nachdem ich es jetzt geschafft habe diese jetzt zu verbinden, habe ich komische Eigenarten.
Die MeterValues scheinen einmal pro Minute aktualisiert zu werden.
Das Chargelimit steht Anfangs auf (null)A, wenn dort jetzt ein Wert setzte zB. 6A sehe ich auf dem Port die Meldung, dass er nichts senden kann weil die Wallbox nicht connected ist.
Hatte jemand sowas auch schonmal?
Sind eure Metervalues Live oder auch nur alle 60sek.?
XCharge verkauft eigentlich nicht B2C, der Support war zwar freundlich, die Dokumentationen die Sie aber haben sind maximal sperrlich. Über die genutzen Protokolle und der Implementierung gibts leider nichts.
Wenn das Chargelimit funktionieren würde, wäre die C2EU von XCharge wohl die günstigste 1 phasig Steuerbare Wallbox auf dem Markt.
Besten Dank
@foxriver76 Ich habe eben OCPP bei meiner WallBoxPulsar Plus aktiviert, ich bekomme auch Daten von dieser (inkl. dem HaertBeat) nur kann ich keine Daten schicken, da ich immer eine Warnung bekomme:
ocpp.0
2022-07-08 12:21:09.578 debug Received heartbeat from "/WallBoxCP"
ocpp.0
2022-07-08 12:21:09.576 debug {"commandOcpp":"Heartbeat"}
ocpp.0
2022-07-08 12:20:59.202 warn No valid connectorId for "/WallBoxCP"
ocpp.0
2022-07-08 12:20:56.115 warn No valid connectorId for "/WallBoxCP"
ocpp.0
2022-07-08 12:20:50.735 warn No valid connectorId for "/WallBoxCP"
ocpp.0
2022-07-08 12:20:45.766 warn No valid connectorId for "/WallBoxCP"
ocpp.0
2022-07-08 12:20:14.540 debug Received heartbeat from "/WallBoxCP"
Wie auch bei anderen hier, ist diese aber auf "0" gestellt und ich wüsste auch nicht, was der richtige Wert wäre.
Passt auch zu den Daten hier:
und zu diesem Log:
ocpp.0
2022-07-08 12:06:33.734 debug {"info":"","vendorId":"com.wallbox","vendorErrorCode":"","connectorId":0,"errorCode":"NoError","status":"Available","timestamp":"2022-07-08T10:06:33Z","commandOcpp":"StatusNotification"}
Die Meldung oben erscheint immer dann, wenn ich in iobroker versuche die
ocpp.0./WallBoxCP.availability
oder
ocpp.0./WallBoxCP.transactionActive
zu ändern. Die Box entsperrt sich auch nicht, wie schon vorher von @thoko berichtet.
Im IoBroker sind ja gar keine Daten von der Wallbox.
Sicher das die Wallbox richtig konfiguriert ist?
Bei den MeterValues müssten viel mehr Daten.
Ist connected to Server auf true?
@moonlanderpi Ich hab nur die WallBox konfiguriert, die meterValues kommen erst, wenn an der Wallbox auch ein Auto hängt, hab ich verstanden. Nur ist das gerade unterwegs. Der Objektbaum wurde so angelegt, als die ersten Daten der Wallbox gekommen sind und die Wallbox sagt auch, dass OCPP konfiguriert und verbunden ist.
@grillkoenig
Kann es jetzt bei mir nicht kontrollieren, bin aber der Meinung connectorID muss auf 1 sein.
Das ist wenn ich mich recht erinnere die Anzahl der Ladepunkte an der Wallbox und welchen man davon anspricht.
Schonmal mit 1 probiert?
@moonlanderpi Mit "1" als connectorId ist die warning im Log weg, aber die LED an der WallBox bleiben gelb. Ich muss das am Wochenende mal mit einem angeschlossenen Auto probieren.
Hier mal mein Log
Das sieht ganz anders aus bei euch.
Er reagiert zwar auf den Heartbeat, aber das senden des Limits ignoriert er komplett?
pi@iobroker-pi:~ $ iobroker debug ocpp
Debugger listening on ws://127.0.0.1:9229/75122cd1-3a71-4cfe-af10-a671ac9a6cc5
For help, see: https://nodejs.org/en/docs/inspector
2022-07-08 13:47:29.467 - debug: ocpp.0 (25736) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-07-08 13:47:29.553 - debug: ocpp.0 (25736) Objects client ready ... initialize now
2022-07-08 13:47:29.558 - debug: ocpp.0 (25736) Objects create System PubSub Client
2022-07-08 13:47:29.561 - debug: ocpp.0 (25736) Objects create User PubSub Client
2022-07-08 13:47:29.634 - debug: ocpp.0 (25736) Objects client initialize lua scripts
2022-07-08 13:47:29.647 - debug: ocpp.0 (25736) Objects connected to redis: 127.0.0.1:9001
2022-07-08 13:47:29.704 - debug: ocpp.0 (25736) Redis States: Use Redis connection: 127.0.0.1:9000
2022-07-08 13:47:29.729 - debug: ocpp.0 (25736) States create System PubSub Client
2022-07-08 13:47:29.732 - debug: ocpp.0 (25736) States create User PubSub Client
2022-07-08 13:47:29.772 - debug: ocpp.0 (25736) States connected to redis: 127.0.0.1:9000
2022-07-08 13:47:29.864 - error: ocpp.0 (25736) adapter disabled
2022-07-08 13:47:30.150 - info: ocpp.0 (25736) starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.ocpp, node: v14.20.0, js-controller: 4.0.23
2022-07-08 13:47:30.232 - info: ocpp.0 (25736) Starting OCPP Server
[winston] Attempt to write logs with no transports, which can increase memory usage: {"message":"Listen on default host:9220","level":"debug"}
2022-07-08 13:47:30.335 - info: ocpp.0 (25736) Server listening on port 9220
2022-07-08 13:47:33.454 - debug: ocpp.0 (25736) Connection from "/C2011601CNYEYPES" with credentials "undefined", protocol: "http", OCPP: ocpp1.6
2022-07-08 13:47:33.457 - info: ocpp.0 (25736) New valid connection from "/C2011601CNYEYPES" (http/ocpp1.6)
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","protocol":"ocpp1.6","isValid":true,"headers":{"connection":"Upgrade","host":"192.168.178.49:9220","sec-websocket-key":"+ie0hhWn+5ZzLlCqt6RrJQ==","sec-websocket-protocol":"ocpp1.6","sec-websocket-version":"13","upgrade":"websocket"},"level":"info","message":"[OCPP] Request for connect \"/C2011601CNYEYPES\" (ocpp1.6) - Valid identifier. Headers: {\"connection\":\"Upgrade\",\"host\":\"192.168.178.49:9220\",\"sec-websocket-key\":\"+ie0hhWn+5ZzLlCqt6RrJQ==\",\"sec-websocket-protocol\":\"ocpp1.6\",\"sec-websocket-version\":\"13\",\"upgrade\":\"websocket\"}"}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"ip":"::ffff:192.168.178.93","protocol":"ocpp1.6","url":"/C2011601CNYEYPES","level":"info","message":"[OCPP] New connection from \"::ffff:192.168.178.93\", protocol \"ocpp1.6\", url \"/C2011601CNYEYPES\""}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Received message: [2,\"10949\",\"BootNotification\",{\"firmwareVersion\":\"1.1.1807.1-2.2.10.23\",\"imsi\":\"460010912121001\",\"chargePointModel\":\"C2EU\",\"chargePointSerialNumber\":\"C2011601CNYEYPES\",\"chargePointVendor\":\"XC\"}] [2,\"10949\",\"BootNotification\",{\"firmwareVersion\":\"1.1.1807.1-2.2.10.23\",\"imsi\":\"460010912121001\",\"chargePointModel\":\"C2EU\",\"chargePointSerialNumber\":\"C2011601CNYEYPES\",\"chargePointVendor\":\"XC\"}]","level":"info"}
2022-07-08 13:47:33.826 - info: ocpp.0 (25736) New device connected: "/C2011601CNYEYPES"
2022-07-08 13:47:33.830 - info: ocpp.0 (25736) Requesting StatusNotification from "/C2011601CNYEYPES"
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Sending message: [2,\"d9c4683b-438b-4fbd-bc42-5cb53e96ca3f\",\"TriggerMessage\",{\"requestedMessage\":\"StatusNotification\"}] [2,\"d9c4683b-438b-4fbd-bc42-5cb53e96ca3f\",\"TriggerMessage\",{\"requestedMessage\":\"StatusNotification\"}]","level":"info"}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Received response: [3,\"d9c4683b-438b-4fbd-bc42-5cb53e96ca3f\",{\"status\":\"Accepted\"}] [3,\"d9c4683b-438b-4fbd-bc42-5cb53e96ca3f\",{\"status\":\"Accepted\"}]","level":"info"}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Received message: [2,\"10950\",\"StatusNotification\",{\"errorCode\":\"NoError\",\"timestamp\":\"2022-07-08T12:47:33+00:00\",\"connectorId\":1,\"status\":\"Available\"}] [2,\"10950\",\"StatusNotification\",{\"errorCode\":\"NoError\",\"timestamp\":\"2022-07-08T12:47:33+00:00\",\"connectorId\":1,\"status\":\"Available\"}]","level":"info"}
2022-07-08 13:47:33.924 - debug: ocpp.0 (25736) {"errorCode":"NoError","timestamp":"2022-07-08T12:47:33+00:00","connectorId":1,"status":"Available","commandOcpp":"StatusNotification"}
2022-07-08 13:47:33.925 - info: ocpp.0 (25736) Received Status Notification from "/C2011601CNYEYPES": Available
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Sending response: [3,\"10950\",{}] [3,\"10950\",{}]","level":"info"}
2022-07-08 13:47:34.049 - debug: ocpp.0 (25736) {"firmwareVersion":"1.1.1807.1-2.2.10.23","imsi":"460010912121001","chargePointModel":"C2EU","chargePointSerialNumber":"C2011601CNYEYPES","chargePointVendor":"XC","commandOcpp":"BootNotification"}
2022-07-08 13:47:34.051 - info: ocpp.0 (25736) Received boot notification from "/C2011601CNYEYPES"
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Sending response: [3,\"10949\",{\"status\":\"Accepted\",\"currentTime\":\"2022-07-08T12:47:34.068Z\",\"interval\":55}] [3,\"10949\",{\"status\":\"Accepted\",\"currentTime\":\"2022-07-08T12:47:34.068Z\",\"interval\":55}]","level":"info"}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Received message: [2,\"10951\",\"StatusNotification\",{\"connectorId\":1,\"timestamp\":\"2022-07-08T12:47:34+00:00\",\"errorCode\":\"NoError\",\"status\":\"Available\"}] [2,\"10951\",\"StatusNotification\",{\"connectorId\":1,\"timestamp\":\"2022-07-08T12:47:34+00:00\",\"errorCode\":\"NoError\",\"status\":\"Available\"}]","level":"info"}
2022-07-08 13:47:34.430 - debug: ocpp.0 (25736) {"connectorId":1,"timestamp":"2022-07-08T12:47:34+00:00","errorCode":"NoError","status":"Available","commandOcpp":"StatusNotification"}
2022-07-08 13:47:34.432 - info: ocpp.0 (25736) Received Status Notification from "/C2011601CNYEYPES": Available
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Received message: [2,\"10952\",\"Heartbeat\",{}] [2,\"10952\",\"Heartbeat\",{}]","level":"info"}
2022-07-08 13:47:34.439 - debug: ocpp.0 (25736) {"commandOcpp":"Heartbeat"}
2022-07-08 13:47:34.441 - debug: ocpp.0 (25736) Received heartbeat from "/C2011601CNYEYPES"
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Sending response: [3,\"10952\",{\"currentTime\":\"2022-07-08T12:47:34.443Z\"}] [3,\"10952\",{\"currentTime\":\"2022-07-08T12:47:34.443Z\"}]","level":"info"}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Sending response: [3,\"10951\",{}] [3,\"10951\",{}]","level":"info"}
2022-07-08 13:47:34.921 - info: ocpp.0 (25736) Requesting MeterValues from "/C2011601CNYEYPES"
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Sending message: [2,\"7bf9002a-49b1-4852-a069-cd7399692c85\",\"TriggerMessage\",{\"requestedMessage\":\"MeterValues\"}] [2,\"7bf9002a-49b1-4852-a069-cd7399692c85\",\"TriggerMessage\",{\"requestedMessage\":\"MeterValues\"}]","level":"info"}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Received response: [3,\"7bf9002a-49b1-4852-a069-cd7399692c85\",{\"status\":\"Accepted\"}] [3,\"7bf9002a-49b1-4852-a069-cd7399692c85\",{\"status\":\"Accepted\"}]","level":"info"}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Received message: [2,\"10953\",\"MeterValues\",{\"connectorId\":1,\"meterValue\":[{\"timestamp\":\"2022-07-08T12:47:34+00:00\",\"sampledValue\":[{\"context\":\"Trigger\",\"value\":\"0.0\",\"unit\":\"A\",\"measurand\":\"Current.Import\",\"format\":\"Raw\",\"location\":\"Outlet\",\"phase\":\"L1\"},{\"context\":\"Trigger\",\"value\":\"233.3\",\"unit\":\"V\",\"measurand\":\"Voltage\",\"format\":\"Raw\",\"location\":\"Outlet\",\"phase\":\"L1\"},{\"context\":\"Trigger\",\"value\":\"6340\",\"unit\":\"Wh\",\"measurand\":\"Energy.Active.Import.Register\",\"format\":\"Raw\",\"location\":\"Outlet\"}]}]}] [2,\"10953\",\"MeterValues\",{\"connectorId\":1,\"meterValue\":[{\"timestamp\":\"2022-07-08T12:47:34+00:00\",\"sampledValue\":[{\"context\":\"Trigger\",\"value\":\"0.0\",\"unit\":\"A\",\"measurand\":\"Current.Import\",\"format\":\"Raw\",\"location\":\"Outlet\",\"phase\":\"L1\"},{\"context\":\"Trigger\",\"value\":\"233.3\",\"unit\":\"V\",\"measurand\":\"Voltage\",\"format\":\"Raw\",\"location\":\"Outlet\",\"phase\":\"L1\"},{\"context\":\"Trigger\",\"value\":\"6340\",\"unit\":\"Wh\",\"measurand\":\"Energy.Active.Import.Register\",\"format\":\"Raw\",\"location\":\"Outlet\"}]}]}]","level":"info"}
2022-07-08 13:47:35.014 - debug: ocpp.0 (25736) {"connectorId":1,"meterValue":[{"timestamp":"2022-07-08T12:47:34+00:00","sampledValue":[{"context":"Trigger","value":"0.0","unit":"A","measurand":"Current.Import","format":"Raw","location":"Outlet","phase":"L1"},{"context":"Trigger","value":"233.3","unit":"V","measurand":"Voltage","format":"Raw","location":"Outlet","phase":"L1"},{"context":"Trigger","value":"6340","unit":"Wh","measurand":"Energy.Active.Import.Register","format":"Raw","location":"Outlet"}]}],"commandOcpp":"MeterValues"}
2022-07-08 13:47:35.017 - info: ocpp.0 (25736) Received MeterValues from "/C2011601CNYEYPES"
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Sending response: [3,\"10953\",{}] [3,\"10953\",{}]","level":"info"}
2022-07-08 13:47:36.011 - info: ocpp.0 (25736) Sending GetConfiguration to "/C2011601CNYEYPES"
2022-07-08 13:48:15.864 - debug: ocpp.0 (25736) Sending SetChargingProfile for /C2011601CNYEYPES
2022-07-08 13:48:29.180 - debug: ocpp.0 (25736) {"commandOcpp":"Heartbeat"}
2022-07-08 13:48:29.183 - debug: ocpp.0 (25736) Received heartbeat from "/C2011601CNYEYPES"
2022-07-08 13:48:43.758 - debug: ocpp.0 (25736) Sending SetChargingProfile for /C2011601CNYEYPESDas setzten von Availability funktioniert, jemand eine Idee warum da nichts gesendet wird?
2022-07-08 14:04:04.291 - debug: ocpp.0 (25736) {"commandOcpp":"Heartbeat"}
2022-07-08 14:04:04.292 - debug: ocpp.0 (25736) Received heartbeat from "/C2011601CNYEYPES"
2022-07-08 14:04:31.656 - debug: ocpp.0 (25736) Sending ChangeAvailability for /C2011601CNYEYPES: Inoperative
2022-07-08 14:04:32.527 - debug: ocpp.0 (25736) {"connectorId":1,"timestamp":"2022-07-08T13:04:32+00:00","errorCode":"NoError","status":"Unavailable","commandOcpp":"StatusNotification"}
2022-07-08 14:04:32.530 - info: ocpp.0 (25736) Received Status Notification from "/C2011601CNYEYPES": Unavailable
2022-07-08 14:04:59.303 - debug: ocpp.0 (25736) {"commandOcpp":"Heartbeat"}
2022-07-08 14:04:59.305 - debug: ocpp.0 (25736) Received heartbeat from "/C2011601CNYEYPES"Sorry gelobe Besserung
pi@iobroker-pi:~ $ iobroker debug ocpp
Debugger listening on ws://127.0.0.1:9229/9525d1f9-4e6e-4427-8085-06d0c63aa0a6
For help, see: https://nodejs.org/en/docs/inspector
2022-07-08 19:11:02.689 - debug: ocpp.0 (1506) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-07-08 19:11:02.785 - debug: ocpp.0 (1506) Objects client ready ... initialize now
2022-07-08 19:11:02.790 - debug: ocpp.0 (1506) Objects create System PubSub Client
2022-07-08 19:11:02.793 - debug: ocpp.0 (1506) Objects create User PubSub Client
2022-07-08 19:11:02.873 - debug: ocpp.0 (1506) Objects client initialize lua scripts
2022-07-08 19:11:02.885 - debug: ocpp.0 (1506) Objects connected to redis: 127.0.0.1:9001
2022-07-08 19:11:02.944 - debug: ocpp.0 (1506) Redis States: Use Redis connection: 127.0.0.1:9000
2022-07-08 19:11:02.969 - debug: ocpp.0 (1506) States create System PubSub Client
2022-07-08 19:11:02.973 - debug: ocpp.0 (1506) States create User PubSub Client
2022-07-08 19:11:03.032 - debug: ocpp.0 (1506) States connected to redis: 127.0.0.1:9000
2022-07-08 19:11:03.124 - error: ocpp.0 (1506) adapter disabled
2022-07-08 19:11:03.428 - info: ocpp.0 (1506) starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.ocpp, node: v14.20.0, js-controller: 4.0.23
2022-07-08 19:11:03.508 - info: ocpp.0 (1506) Starting OCPP Server
[winston] Attempt to write logs with no transports, which can increase memory usage: {"message":"Listen on default host:9220","level":"debug"}
2022-07-08 19:11:03.611 - info: ocpp.0 (1506) Server listening on port 9220
2022-07-08 19:11:04.000 - debug: ocpp.0 (1506) Connection from "/C2011601CNYEYPES" with credentials "undefined", protocol: "http", OCPP: ocpp1.6
2022-07-08 19:11:04.002 - info: ocpp.0 (1506) New valid connection from "/C2011601CNYEYPES" (http/ocpp1.6)
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","protocol":"ocpp1.6","isValid":true,"headers":{"connection":"Upgrade","host":"192.168.178.49:9220","sec-websocket-key":"TSCsoaMNHeBhvENtnKEFqQ==","sec-websocket-protocol":"ocpp1.6","sec-websocket-version":"13","upgrade":"websocket"},"level":"info","message":"[OCPP] Request for connect \"/C2011601CNYEYPES\" (ocpp1.6) - Valid identifier. Headers: {\"connection\":\"Upgrade\",\"host\":\"192.168.178.49:9220\",\"sec-websocket-key\":\"TSCsoaMNHeBhvENtnKEFqQ==\",\"sec-websocket-protocol\":\"ocpp1.6\",\"sec-websocket-version\":\"13\",\"upgrade\":\"websocket\"}"}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"ip":"::ffff:192.168.178.93","protocol":"ocpp1.6","url":"/C2011601CNYEYPES","level":"info","message":"[OCPP] New connection from \"::ffff:192.168.178.93\", protocol \"ocpp1.6\", url \"/C2011601CNYEYPES\""}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Received message: [2,\"11286\",\"BootNotification\",{\"firmwareVersion\":\"1.1.1807.1-2.2.10.23\",\"imsi\":\"460010912121001\",\"chargePointModel\":\"C2EU\",\"chargePointSerialNumber\":\"C2011601CNYEYPES\",\"chargePointVendor\":\"XC\"}] [2,\"11286\",\"BootNotification\",{\"firmwareVersion\":\"1.1.1807.1-2.2.10.23\",\"imsi\":\"460010912121001\",\"chargePointModel\":\"C2EU\",\"chargePointSerialNumber\":\"C2011601CNYEYPES\",\"chargePointVendor\":\"XC\"}]","level":"info"}
2022-07-08 19:11:04.152 - info: ocpp.0 (1506) New device connected: "/C2011601CNYEYPES"
2022-07-08 19:11:04.155 - info: ocpp.0 (1506) Requesting StatusNotification from "/C2011601CNYEYPES"
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Sending message: [2,\"b71c38c0-1566-4148-b827-47f709a490ef\",\"TriggerMessage\",{\"requestedMessage\":\"StatusNotification\"}] [2,\"b71c38c0-1566-4148-b827-47f709a490ef\",\"TriggerMessage\",{\"requestedMessage\":\"StatusNotification\"}]","level":"info"}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Received response: [3,\"b71c38c0-1566-4148-b827-47f709a490ef\",{\"status\":\"Accepted\"}] [3,\"b71c38c0-1566-4148-b827-47f709a490ef\",{\"status\":\"Accepted\"}]","level":"info"}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Received message: [2,\"11287\",\"StatusNotification\",{\"errorCode\":\"NoError\",\"timestamp\":\"2022-07-08T17:11:03+00:00\",\"connectorId\":1,\"status\":\"Finishing\"}] [2,\"11287\",\"StatusNotification\",{\"errorCode\":\"NoError\",\"timestamp\":\"2022-07-08T17:11:03+00:00\",\"connectorId\":1,\"status\":\"Finishing\"}]","level":"info"}
2022-07-08 19:11:04.213 - debug: ocpp.0 (1506) {"errorCode":"NoError","timestamp":"2022-07-08T17:11:03+00:00","connectorId":1,"status":"Finishing","commandOcpp":"StatusNotification"}
2022-07-08 19:11:04.214 - info: ocpp.0 (1506) Received Status Notification from "/C2011601CNYEYPES": Finishing
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Sending response: [3,\"11287\",{}] [3,\"11287\",{}]","level":"info"}
2022-07-08 19:11:04.338 - debug: ocpp.0 (1506) {"firmwareVersion":"1.1.1807.1-2.2.10.23","imsi":"460010912121001","chargePointModel":"C2EU","chargePointSerialNumber":"C2011601CNYEYPES","chargePointVendor":"XC","commandOcpp":"BootNotification"}
2022-07-08 19:11:04.340 - info: ocpp.0 (1506) Received boot notification from "/C2011601CNYEYPES"
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Sending response: [3,\"11286\",{\"status\":\"Accepted\",\"currentTime\":\"2022-07-08T17:11:04.363Z\",\"interval\":55}] [3,\"11286\",{\"status\":\"Accepted\",\"currentTime\":\"2022-07-08T17:11:04.363Z\",\"interval\":55}]","level":"info"}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Received message: [2,\"11288\",\"StatusNotification\",{\"connectorId\":1,\"timestamp\":\"2022-07-08T17:11:04+00:00\",\"errorCode\":\"NoError\",\"status\":\"Finishing\"}] [2,\"11288\",\"StatusNotification\",{\"connectorId\":1,\"timestamp\":\"2022-07-08T17:11:04+00:00\",\"errorCode\":\"NoError\",\"status\":\"Finishing\"}]","level":"info"}
2022-07-08 19:11:04.578 - debug: ocpp.0 (1506) {"connectorId":1,"timestamp":"2022-07-08T17:11:04+00:00","errorCode":"NoError","status":"Finishing","commandOcpp":"StatusNotification"}
2022-07-08 19:11:04.581 - info: ocpp.0 (1506) Received Status Notification from "/C2011601CNYEYPES": Finishing
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Sending response: [3,\"11288\",{}] [3,\"11288\",{}]","level":"info"}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Received message: [2,\"11289\",\"Heartbeat\",{}] [2,\"11289\",\"Heartbeat\",{}]","level":"info"}
2022-07-08 19:11:04.625 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"}
2022-07-08 19:11:04.627 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES"
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Sending response: [3,\"11289\",{\"currentTime\":\"2022-07-08T17:11:04.630Z\"}] [3,\"11289\",{\"currentTime\":\"2022-07-08T17:11:04.630Z\"}]","level":"info"}
2022-07-08 19:11:05.212 - info: ocpp.0 (1506) Requesting MeterValues from "/C2011601CNYEYPES"
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Sending message: [2,\"bd690c97-9bca-4451-a945-d0b289f30f8b\",\"TriggerMessage\",{\"requestedMessage\":\"MeterValues\"}] [2,\"bd690c97-9bca-4451-a945-d0b289f30f8b\",\"TriggerMessage\",{\"requestedMessage\":\"MeterValues\"}]","level":"info"}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Received response: [3,\"bd690c97-9bca-4451-a945-d0b289f30f8b\",{\"status\":\"Accepted\"}] [3,\"bd690c97-9bca-4451-a945-d0b289f30f8b\",{\"status\":\"Accepted\"}]","level":"info"}
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Received message: [2,\"11290\",\"MeterValues\",{\"connectorId\":1,\"meterValue\":[{\"timestamp\":\"2022-07-08T17:11:04+00:00\",\"sampledValue\":[{\"context\":\"Trigger\",\"value\":\"43.0\",\"unit\":\"Celsius\",\"measurand\":\"Temperature\",\"format\":\"Raw\",\"location\":\"Body\"},{\"context\":\"Trigger\",\"value\":\"0.0\",\"unit\":\"A\",\"measurand\":\"Current.Import\",\"format\":\"Raw\",\"location\":\"Outlet\",\"phase\":\"L1\"},{\"context\":\"Trigger\",\"value\":\"234.3\",\"unit\":\"V\",\"measurand\":\"Voltage\",\"format\":\"Raw\",\"location\":\"Outlet\",\"phase\":\"L1\"},{\"context\":\"Trigger\",\"value\":\"0.0\",\"unit\":\"kW\",\"measurand\":\"Power.Active.Import\",\"format\":\"Raw\",\"location\":\"Outlet\"},{\"context\":\"Trigger\",\"value\":\"6340\",\"unit\":\"Wh\",\"measurand\":\"Energy.Active.Import.Register\",\"format\":\"Raw\",\"location\":\"Outlet\"}]}]}] [2,\"11290\",\"MeterValues\",{\"connectorId\":1,\"meterValue\":[{\"timestamp\":\"2022-07-08T17:11:04+00:00\",\"sampledValue\":[{\"context\":\"Trigger\",\"value\":\"43.0\",\"unit\":\"Celsius\",\"measurand\":\"Temperature\",\"format\":\"Raw\",\"location\":\"Body\"},{\"context\":\"Trigger\",\"value\":\"0.0\",\"unit\":\"A\",\"measurand\":\"Current.Import\",\"format\":\"Raw\",\"location\":\"Outlet\",\"phase\":\"L1\"},{\"context\":\"Trigger\",\"value\":\"234.3\",\"unit\":\"V\",\"measurand\":\"Voltage\",\"format\":\"Raw\",\"location\":\"Outlet\",\"phase\":\"L1\"},{\"context\":\"Trigger\",\"value\":\"0.0\",\"unit\":\"kW\",\"measurand\":\"Power.Active.Import\",\"format\":\"Raw\",\"location\":\"Outlet\"},{\"context\":\"Trigger\",\"value\":\"6340\",\"unit\":\"Wh\",\"measurand\":\"Energy.Active.Import.Register\",\"format\":\"Raw\",\"location\":\"Outlet\"}]}]}]","level":"info"}
2022-07-08 19:11:05.304 - debug: ocpp.0 (1506) {"connectorId":1,"meterValue":[{"timestamp":"2022-07-08T17:11:04+00:00","sampledValue":[{"context":"Trigger","value":"43.0","unit":"Celsius","measurand":"Temperature","format":"Raw","location":"Body"},{"context":"Trigger","value":"0.0","unit":"A","measurand":"Current.Import","format":"Raw","location":"Outlet","phase":"L1"},{"context":"Trigger","value":"234.3","unit":"V","measurand":"Voltage","format":"Raw","location":"Outlet","phase":"L1"},{"context":"Trigger","value":"0.0","unit":"kW","measurand":"Power.Active.Import","format":"Raw","location":"Outlet"},{"context":"Trigger","value":"6340","unit":"Wh","measurand":"Energy.Active.Import.Register","format":"Raw","location":"Outlet"}]}],"commandOcpp":"MeterValues"}
2022-07-08 19:11:05.307 - info: ocpp.0 (1506) Received MeterValues from "/C2011601CNYEYPES"
[winston] Attempt to write logs with no transports, which can increase memory usage: {"url":"/C2011601CNYEYPES","message":"[OCPP] Sending response: [3,\"11290\",{}] [3,\"11290\",{}]","level":"info"}
2022-07-08 19:11:06.297 - info: ocpp.0 (1506) Sending GetConfiguration to "/C2011601CNYEYPES"
2022-07-08 19:11:59.453 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"}
2022-07-08 19:11:59.456 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES"
2022-07-08 19:12:09.710 - debug: ocpp.0 (1506) Sending SetChargingProfile for /C2011601CNYEYPES
2022-07-08 19:12:54.459 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"}
2022-07-08 19:12:54.461 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES"
