Weihnachtsangebot 2025! 🎄

[MoonlanderPi]

So hab den IDTag reingebastel. Bringt auch nichts.
Stacklevel mal mit 1 probiert leider auch kein Erfolg.
Jetzt bin ich echt ratlos was es noch sein könnte.

Sending RemoteStartTransaction for /: {"connectorId":1,"idTag":"C7131506","chargingProfile":{"chargingProfileId":1,"stackLevel":1,"chargingProfilePurpose":"TxDefaultProfile","chargingProfileKind":"Recurring","recurrencyKind":"Daily","chargingSchedule":{"duration":86400,"startSchedule":"2013-01-01T00:00Z","chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":8}]}}}

`

[derSESO]

@manubt
Wie hast du das in der Elvi aktiviert/eingerichtet?
Habe diese Wallbox jetzt auch.
Danke.

[Meister Mopper]

@manubt sagte in Alpha Testing: OCPP Wallbox Adapter:

Der Adapter spricht mit einer EVBox Elvi.

Da ich in diesem thread keine weiteren Hinweise gefunden habe, bitte ich mal direkt:

Schreibt mir bitte jemand, was man in der App dieser EVBox im Installermenü der Lademanagement Software unter "different backend url" eintragen muss, damit sie mit dem ioBroker kommuniziert?

Könnte es diese Syntax sein?
ws://<IP_des_ioBroker>:<Port_der_Instanz>

edit: Okay, da muss noch ein backslash ans Ende, dann funktioniert es.

[Meister Mopper]

@foxriver76

So "Er lebt", der Server empfängt heartbeats.

Nach einem Firmwareupdate der EVBox erhalte ich folgendes debug log:

Spoiler

ocpp.0	2022-08-13 18:07:47.235	debug	Received heartbeat from "http://192.168.178.10:9220/XXXXXXXXXXXXX"
ocpp.0	2022-08-13 18:07:47.235	debug	{"commandOcpp":"Heartbeat"}
ocpp.0	2022-08-13 18:06:52.046	debug	Received heartbeat from "http://192.168.178.10:9220/XXXXXXXXXXXXX"
ocpp.0	2022-08-13 18:06:52.046	debug	{"commandOcpp":"Heartbeat"}
ocpp.0	2022-08-13 18:05:57.256	debug	Received heartbeat from "http://192.168.178.10:9220/XXXXXXXXXXXXX"
ocpp.0	2022-08-13 18:05:57.255	debug	{"commandOcpp":"Heartbeat"}
ocpp.0	2022-08-13 18:05:02.138	debug	Received heartbeat from "http://192.168.178.10:9220/XXXXXXXXXXXXX"
ocpp.0	2022-08-13 18:05:02.138	debug	{"commandOcpp":"Heartbeat"}
ocpp.0	2022-08-13 18:04:43.060	warn	Command not implemented from "http://192.168.178.10:9220/XXXXXXXXXXXXX": {"vendorId":"EV-BOX","messageId":"evbStatusNotification","data":"1,SuspendedEV,NoError,No error.,0,Yellow,1,{20,7983,10},{0,0},{B,11883,8634,12272},0,0,450,2022-08-13T16:04:31Z,1,3,{0,0,0,0,0,0,0,0,0},370,0,0,125,0,380,60,0","commandOcpp":"DataTransfer"}
ocpp.0	2022-08-13 18:04:43.059	debug	{"vendorId":"EV-BOX","messageId":"evbStatusNotification","data":"1,SuspendedEV,NoError,No error.,0,Yellow,1,{20,7983,10},{0,0},{B,11883,8634,12272},0,0,450,2022-08-13T16:04:31Z,1,3,{0,0,0,0,0,0,0,0,0},370,0,0,125,0,380,60,0","commandOcpp":"DataTransfer"}
ocpp.0	2022-08-13 18:04:38.070	warn	Command not implemented from "http://192.168.178.10:9220/XXXXXXXXXXXXX": {"vendorId":"EV-BOX","messageId":"evbStatusNotification","data":"1,SuspendedEVSE,NoError,No error.,0,Yellow,1,{20,7982,10},{0,0},{B,11881,8722,9548},0,0,450,2022-08-13T16:04:30Z,1,3,{0,0,0,0,0,0,0,0,0},370,0,0,125,0,380,60,0","commandOcpp":"DataTransfer"}
ocpp.0	2022-08-13 18:04:38.070	debug	{"vendorId":"EV-BOX","messageId":"evbStatusNotification","data":"1,SuspendedEVSE,NoError,No error.,0,Yellow,1,{20,7982,10},{0,0},{B,11881,8722,9548},0,0,450,2022-08-13T16:04:30Z,1,3,{0,0,0,0,0,0,0,0,0},370,0,0,125,0,380,60,0","commandOcpp":"DataTransfer"}
ocpp.0	2022-08-13 18:04:33.048	info	Received Start transaction from "http://192.168.178.10:9220/XXXXXXXXXXXXX"
ocpp.0	2022-08-13 18:04:33.048	debug	{"connectorId":1,"idTag":"048EAB728E6781","timestamp":"2022-08-13T16:04:29Z","meterStart":0,"commandOcpp":"StartTransaction"}
ocpp.0	2022-08-13 18:04:31.169	info	Received Status Notification from "http://192.168.178.10:9220/XXXXXXXXXXXXX": SuspendedEV
ocpp.0	2022-08-13 18:04:31.168	debug	{"connectorId":1,"status":"SuspendedEV","errorCode":"NoError","info":"B;450","timestamp":"2022-08-13T16:04:31Z","commandOcpp":"StatusNotification"}
ocpp.0	2022-08-13 18:04:31.030	info	Received Status Notification from "http://192.168.178.10:9220/XXXXXXXXXXXXX": SuspendedEVSE
ocpp.0	2022-08-13 18:04:31.029	debug	{"connectorId":1,"status":"SuspendedEVSE","errorCode":"NoError","info":"B;450","timestamp":"2022-08-13T16:04:30Z","commandOcpp":"StatusNotification"}
ocpp.0	2022-08-13 18:04:28.207	warn	Command not implemented from "http://192.168.178.10:9220/XXXXXXXXXXXXX": {"vendorId":"EV-BOX","messageId":"evbStatusNotification","data":"1,Preparing,NoError,No error.,0,Off,0,{20,7984,100},{0,0},{B,11872,9164,61568},0,0,450,2022-08-13T16:04:28Z,0,3,{0,0,0,0,0,0,0,0,0},380,0,0,114,0,380,900,0","commandOcpp":"DataTransfer"}
ocpp.0	2022-08-13 18:04:28.206	debug	{"vendorId":"EV-BOX","messageId":"evbStatusNotification","data":"1,Preparing,NoError,No error.,0,Off,0,{20,7984,100},{0,0},{B,11872,9164,61568},0,0,450,2022-08-13T16:04:28Z,0,3,{0,0,0,0,0,0,0,0,0},380,0,0,114,0,380,900,0","commandOcpp":"DataTransfer"}
ocpp.0	2022-08-13 18:04:28.163	info	Received Status Notification from "http://192.168.178.10:9220/XXXXXXXXXXXXX": Preparing
ocpp.0	2022-08-13 18:04:28.163	debug	{"connectorId":1,"status":"Preparing","errorCode":"NoError","timestamp":"2022-08-13T16:04:28Z","commandOcpp":"StatusNotification"}
ocpp.0	2022-08-13 18:04:26.915	info	Received Authorization Request from "http://192.168.178.10:9220/XXXXXXXXXXXXX"
ocpp.0	2022-08-13 18:04:26.915	debug	{"idTag":"048EAB728E6781","commandOcpp":"Authorize"}
ocpp.0	2022-08-13 18:04:21.982	warn	Command not implemented from "http://192.168.178.10:9220/XXXXXXXXXXXXX": {"vendorId":"EV-BOX","messageId":"evbStatusNotification","data":"1,Preparing,NoError,No error.,0,Green,0,{20,7984,100},{0,0},{B,11877,10068,61568},0,0,450,2022-08-13T16:04:21Z,0,3,{0,0,0,0,0,0,0,0,0},380,0,0,114,0,380,900,0","commandOcpp":"DataTransfer"}
ocpp.0	2022-08-13 18:04:21.982	debug	{"vendorId":"EV-BOX","messageId":"evbStatusNotification","data":"1,Preparing,NoError,No error.,0,Green,0,{20,7984,100},{0,0},{B,11877,10068,61568},0,0,450,2022-08-13T16:04:21Z,0,3,{0,0,0,0,0,0,0,0,0},380,0,0,114,0,380,900,0","commandOcpp":"DataTransfer"}
ocpp.0	2022-08-13 18:04:21.942	info	Received Status Notification from "http://192.168.178.10:9220/XXXXXXXXXXXXX": Preparing
ocpp.0	2022-08-13 18:04:21.942	debug	{"connectorId":1,"status":"Preparing","errorCode":"NoError","timestamp":"2022-08-13T16:04:21Z","commandOcpp":"StatusNotification"}
ocpp.0	2022-08-13 18:04:07.047	debug	Received heartbeat from "http://192.168.178.10:9220/XXXXXXXXXXXXX"
ocpp.0	2022-08-13 18:04:07.047	debug	{"commandOcpp":"Heartbeat"}
ocpp.0	2022-08-13 18:03:12.133	debug	Received heartbeat from "http://192.168.178.10:9220/XXXXXXXXXXXXX"
ocpp.0	2022-08-13 18:03:12.133	debug	{"commandOcpp":"Heartbeat"}
ocpp.0	2022-08-13 18:02:17.188	debug	Received heartbeat from "http://192.168.178.10:9220/XXXXXXXXXXXXX"
ocpp.0	2022-08-13 18:02:17.188	debug	{"commandOcpp":"Heartbeat"}

Was hat es aber mit dem log in Zeile 19 auf sich Command not implemented ?

[foxriver76]

@meister-mopper sagte in Alpha Testing: OCPP Wallbox Adapter:

DataTransfer

Die Wallbox sendet DataTransfer Nachrichten, welche ich aktuell nicht behandle. Ich kann mal sehen was man damit anstellen kann. Dafür werde ich mal etwas einbauen, dann benötige ich dein Feedback. Ich gebe dir Bescheid sobald ich es eingebaut habe.

[foxriver76]

@meister-mopper Gerne 0.6.0 probieren, es sollte ein Channel mit dataTransfer angelegt werden, der die transferierten Daten enthält.

[Meister Mopper]

@foxriver76
Super, das warn dataTransfer taucht nicht mehr auf, allerdings bekomme ich immer einen Adapter Neustart, wenn ich transactionActive umstelle true/false.

Im log kommt:

ocpp.0	2022-08-14 16:28:15.966	error	AssertionError [ERR_ASSERTION]: you must provide a joi schema at module.exports.internals.Any.root.reach (/opt/iobroker/node_modules/@ampeco/ocpp-eliftech/node_modules/joi/lib/index.js:200:14) at _loop (/opt/iobroker/node_modules/@ampeco/ocpp-eliftech/dist/helpers.js:58:35) at applyPropertiesValidators (/opt/iobroker/node_modules/@ampeco/ocpp-eliftech/dist/helpers.js:78:16) at RemoteStopTransaction.BaseCommand (/opt/iobroker/node_modules/@ampeco/ocpp-eliftech/dist/commands/BaseCommand.js:32:46) at new RemoteStopTransaction (/opt/iobroker/node_modules/@ampeco/ocpp-eliftech/dist/commands/RemoteStopTransaction.js:46:149) at Ocpp.onStateChange (/opt/iobroker/node_modules/iobroker.ocpp/build/main.js:424:27)
ocpp.0	2022-08-14 16:28:15.966	error	Exception-Code: ERR_ASSERTION: you must provide a joi schema
ocpp.0	2022-08-14 16:28:15.971	info	terminating
ocpp.0	2022-08-14 16:28:15.972	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
host.iobroker	2022-08-14 16:28:16.608	error	Caught by controller[1]: [winston] Attempt to write logs with no transports {"url":"http://192.168.178.10:9220/XXXXXXXXX","message":"[OCPP] Received message: [2,\"2a8bc2e5-df12-4664-b78f-46cb25c46eac\",\"Heartbeat\",{}] [2,\"2a8bc2e5-df12-4664-b78f-46cb25c46eac\",\"Heartbeat\",{}]","level":"info"}
host.iobroker	2022-08-14 16:28:16.608	error	Caught by controller[1]: [winston] Attempt to write logs with no transports {"url":"http://192.168.178.10:9220/XXXXXXXXX","message":"[OCPP] Sending response: [3,\"2a8bc2e5-df12-4664-b78f-46cb25c46eac\",{\"currentTime\":\"2022-08-14T14:27:49.033Z\"}] [3,\"2a8bc2e5-df12-4664-b78f-46cb25c46eac\",{\"currentTime\":\"2022-08-14T14:27:49.033Z\"}]","level":"info"}
host.iobroker	2022-08-14 16:28:16.609	error	Caught by controller[2]: [winston] Attempt to write logs with no transports {"url":"http://192.168.178.10:9220/XXXXXXXXX","error":1006,"level":"info","message":"[OCPP] Closing socket for http://192.168.178.10:9220/XXXXXXXXX: 1006"}
host.iobroker	2022-08-14 16:28:16.609	error	instance system.adapter.ocpp.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
ocpp.0	2022-08-14 16:28:47.836	info	starting. Version 0.6.0 (non-npm: foxriver76/ioBroker.ocpp#48303d5b08f18682ed681038d614133990a50c1e) in /opt/iobroker/node_modules/iobroker.ocpp, node: v14.20.0, js-controller: 4.0.23
ocpp.0	2022-08-14 16:28:47.861	info	Starting OCPP Server
ocpp.0	2022-08-14 16:28:47.885	info	Server listening on port 9220
ocpp.0	2022-08-14 16:28:56.214	info	New valid connection from "http://192.168.178.10:9220/XXXXXXXXX" (http/ocpp1.6)
ocpp.0	2022-08-14 16:28:56.264	info	New device connected: "http://192.168.178.10:9220/XXXXXXXXX"
ocpp.0	2022-08-14 16:28:56.265	info	Requesting BootNotification from "http://192.168.178.10:9220/XXXXXXXXX"
ocpp.0	2022-08-14 16:28:56.267	warn	Could not request states of "http://192.168.178.10:9220/XXXXXXXXX": you must provide a joi schema

Dieses Verhalten habe ich auch mit der Version 0.4.0 .

Kann es sein, dass dies die Ursache ist?

Could not request states of "http://192.168.178.10:9220/EVB-XXXXXXXXX": you must provide a joi schema

[foxriver76]

@meister-mopper sagte in Alpha Testing: OCPP Wallbox Adapter:

ocpp.0 2022-08-14 16:28:15.966 error AssertionError [ERR_ASSERTION]: you must provide a joi schema at module.exports.internals.Any.root.reach (/opt/iobroker/node_modules/@ampeco/ocpp-eliftech/node_modules/joi/lib/index.js:200:14) at _loop (/opt/iobroker/node_modules/@ampeco/ocpp-eliftech/dist/helpers.js:58:35) at applyPropertiesValidators (/opt/iobroker/node_modules/@ampeco/ocpp-eliftech/dist/helpers.js:78:16) at RemoteStopTransaction.BaseCommand (/opt/iobroker/node_modules/@ampeco/ocpp-eliftech/dist/commands/BaseCommand.js:32:46) at new RemoteStopTransaction (/opt/iobroker/node_modules/@ampeco/ocpp-eliftech/dist/commands/RemoteStopTransaction.js:46:149) at Ocpp.onStateChange (/opt/iobroker/node_modules/iobroker.ocpp/build/main.js:424:27)

Interessant, schaue ich mir an.

[baeckerman83]

@moonlanderpi Kannst du denn an der Wallbox selbst das Chargelimit einstellen? Ich glaube das war es bei mir. Also ich kann es zwischen 6 und 16 einstellen, oder ich stelle die Option aus, dann geht nur 16A.
Da gibt es dann noch eine Option Manuelles einstellen, die musste ich in der App der Terra Box einschalten, sonst konnte auch per OCCP nichts geschickt werden. Vermute zumindest da einen zusammenhang, da seit dem ich das gemacht habe es funktioniert.

[Nator]

Hallo zusammen.

Ich habe einen go-e Charger mit dem Adapter verbunden, allerdings kommen keine Daten an. Der Objektordner meterValues bleibt beispielsweise leer. Der Verbindung bekommt auch nur den Namen "/". Laut go-e App ist mit der Verbindung alles OK.

Log:

2022-08-26 14:19:01.680 - info: ocpp.0 (2067838) starting. Version 0.6.0 in /opt/iobroker/node_modules/iobroker.ocpp, node: v12.22.12, js-controller: 4.0.23
2022-08-26 14:19:01.690 - info: ocpp.0 (2067838) Starting OCPP Server
2022-08-26 14:19:01.715 - info: ocpp.0 (2067838) Server listening on port 9220
2022-08-26 14:19:11.562 - info: ocpp.0 (2067838) New valid connection from "/" (http/ocpp1.6)
2022-08-26 14:19:11.675 - info: ocpp.0 (2067838) New device connected: "/"
2022-08-26 14:19:11.676 - info: ocpp.0 (2067838) Requesting StatusNotification from "/"
2022-08-26 14:19:11.679 - warn: ocpp.0 (2067838) Could not request states of "/": you must provide a joi schema
2022-08-26 14:19:11.715 - info: ocpp.0 (2067838) Received boot notification from "/"
2022-08-26 14:19:11.980 - info: ocpp.0 (2067838) Received Status Notification from "/": Available
2022-08-26 14:19:12.064 - info: ocpp.0 (2067838) Received Status Notification from "/": Available

npm ls joi:

iobroker.inst@2.0.3 /opt/iobroker
├─┬ iobroker.go-e@1.0.23
│ └── joi@17.6.0
└─┬ iobroker.ocpp@0.6.0
  └─┬ @ampeco/ocpp-eliftech@1.1.0
    ├─┬ enjoi@3.2.5
    │ └── joi@13.7.0
    └── joi@13.7.0

[foxriver76]

@nator Ich kann das bei mir aktuell nicht nachstellen leider. Anscheinend kommt das Problem öfter vor wie oben bei @Meister-Mopper . Nur die Message sollte zwischen unterschiedlichen Hosts dieselbe sein und die joi Version unter ocpp ist auch identisch zu meiner. Die Frage ist nur ob node da was falsch auflöst (npm falsch hin schiebt) und eine andere Version anzieht, da du noch eine installiert hast und das evtl. dazu führt.

[foxriver76]

@foxriver76 Ich habe mal go-e parallel installiert, funktioniert bei mir trotzdem. Bin da aktuell etwas ratlos. Auf dem Host auf dem das läuft ist bei mir noch node 12.

[Meister Mopper]

@foxriver76
Ich habe den Adapter mal auf einem Slave installiert. Dort läuft Node.js 16.17.0 und npm 8.15.0.

Ich bekomme ihn jedoch nicht grün und das log zeigt das Folgende:

$ iobroker url https://github.com/foxriver76/ioBroker.ocpp.git --host rpizigbee --debug

install foxriver76/ioBroker.ocpp#48303d5b08f18682ed681038d614133990a50c1e
Installing foxriver76/ioBroker.ocpp#48303d5b08f18682ed681038d614133990a50c1e... (System call)
npm WARN skipping integrity check for git dependency ssh://git@github.com/foxriver76/ioBroker.ocpp.git
npm WARN deprecated topo@3.0.3: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated joi-date-extensions@1.2.0: This module has moved and is now available at @hapi/joi-date. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated hoek@5.0.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated hoek@6.1.3: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated joi@13.7.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
added 47 packages, removed 40 packages, and changed 8 packages in 2m86 packages are looking for funding run `npm fund` for details
upload [1] ocpp.admin /opt/iobroker/node_modules/iobroker.ocpp/admin/jsonConfig.json jsonConfig.json application/json
upload [0] ocpp.admin /opt/iobroker/node_modules/iobroker.ocpp/admin/ocpp.png ocpp.png image/png
Process exited with code 0

[foxriver76]

@meister-mopper Bitte nicht mehr von Git installieren, Adapter ist mittlerweile im Repo. Abseits davon sieht das Installations-Log unauffällig aus. Log vom Start ist eher interessant.

[Meister Mopper]

@foxriver76
Na ja, das ist wahrscheinlich auch eher unspektakulär. Ich schrieb ja, dass der Adapter nicht grün wird und somit auch mit meiner Wallbox nicht kommuniziert.

ocpp.0	2022-08-26 16:01:03.819	debug	Redis Objects: Use Redis connection: 192.168.178.10:9001
ocpp.0	2022-08-26 16:01:03.894	debug	Objects client ready ... initialize now
ocpp.0	2022-08-26 16:01:03.914	debug	Objects create System PubSub Client
ocpp.0	2022-08-26 16:01:03.916	debug	Objects create User PubSub Client
ocpp.0	2022-08-26 16:01:04.028	debug	Objects client initialize lua scripts
ocpp.0	2022-08-26 16:01:04.043	debug	Objects connected to redis: 192.168.178.10:9001
ocpp.0	2022-08-26 16:01:04.093	debug	Redis States: Use Redis connection: 192.168.178.10:6379
ocpp.0	2022-08-26 16:01:04.103	debug	States create System PubSub Client
ocpp.0	2022-08-26 16:01:04.104	debug	States create User PubSub Client
ocpp.0	2022-08-26 16:01:04.118	debug	States connected to redis: 192.168.178.10:6379
ocpp.0	2022-08-26 16:01:04.368	info	starting. Version 0.6.0 (non-npm: foxriver76/ioBroker.ocpp#48303d5b08f18682ed681038d614133990a50c1e) in /opt/iobroker/node_modules/iobroker.ocpp, node: v16.17.0, js-controller: 4.0.23
ocpp.0	2022-08-26 16:01:04.413	info	Starting OCPP Server
ocpp.0	2022-08-26 16:01:04.454	info	Server listening on port 9220
ocpp.0	2022-08-26 16:12:17.153	info	Got terminate signal TERMINATE_YOURSELF
ocpp.0	2022-08-26 16:12:17.166	info	terminating
ocpp.0	2022-08-26 16:12:17.169	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

[foxriver76]

@meister-mopper Ah.. ich hattes es so interpretiert, dass er crashed ;-)

Und in der Box hast du die OCPP Server Adresse auf deine IP vom "Slave" abgeändert?

[Meister Mopper]

@foxriver76 sagte in Alpha Testing: OCPP Wallbox Adapter:

Und in der Box hast du die OCPP Server Adresse auf deine IP vom "Slave" abgeändert?

Natürlich habe ich Depp das nicht getan. Das teste ich morgen nochmal.

[Meister Mopper]

@foxriver76
Leider bekomme ich auch mit in der Wallbox geänderter IP des Slave dasselbe Ergebnis.

Irgendwie scheint es mit Nodejs.16 noch nicht zu funktionieren. Vielleicht kann ja jemand anders dies nochmal testen.

[foxriver76]

@meister-mopper dasselbe Ergebnis heißt wieder joi Schema issue?

[Meister Mopper]

@foxriver76 sagte in Alpha Testing: OCPP Wallbox Adapter:

dasselbe Ergebnis heißt wieder joi Schema issue?

Nein, nein, der Server lauscht, aber er ses kommt keine Verbindung mit der Wallbox unter Node.js 16 zustande.

ocpp.0	2022-08-27 08:51:24.315	info	Got terminate signal TERMINATE_YOURSELF
ocpp.0	2022-08-27 08:51:24.333	info	terminating
ocpp.0	2022-08-27 08:51:24.335	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
ocpp.0	2022-08-27 08:51:29.572	debug	Redis Objects: Use Redis connection: 192.168.178.10:9001
ocpp.0	2022-08-27 08:51:29.628	debug	Objects client ready ... initialize now
ocpp.0	2022-08-27 08:51:29.631	debug	Objects create System PubSub Client
ocpp.0	2022-08-27 08:51:29.632	debug	Objects create User PubSub Client
ocpp.0	2022-08-27 08:51:29.708	debug	Objects client initialize lua scripts
ocpp.0	2022-08-27 08:51:29.716	debug	Objects connected to redis: 192.168.178.10:9001
ocpp.0	2022-08-27 08:51:29.763	debug	Redis States: Use Redis connection: 192.168.178.10:6379
ocpp.0	2022-08-27 08:51:29.774	debug	States create System PubSub Client
ocpp.0	2022-08-27 08:51:29.776	debug	States create User PubSub Client
ocpp.0	2022-08-27 08:51:29.789	debug	States connected to redis: 192.168.178.10:6379
ocpp.0	2022-08-27 08:51:29.976	info	starting. Version 0.6.0 in /opt/iobroker/node_modules/iobroker.ocpp, node: v16.17.0, js-controller: 4.0.23
ocpp.0	2022-08-27 08:51:30.015	info	Starting OCPP Server
ocpp.0	2022-08-27 08:51:30.056	info	Server listening on port 9220