Hello foxdriver76,

thanks for the development of the ocpp adaper !
Just wanted to test the adapter, unfortunately I only get the output "index_m.html not found" in the configuration.
Am I doing something wrong ? I have installed the adapter normally via npm.

Thanks

!

Originally posted by @foxriver76 in #16 (comment)

Um die Verbrauchswerte erfassen zu können ist es erforderlich, von der Station regelmässig - wenigstens aber beim Starten und Beenden des Ladevorgangs, die Werte abzufragen. Dazu gibt es ein paar Parameter, MeterValueSampleInterval ist einer. Es wäre schön, wenn man die GetConfig-Methode aus dem Admin-Bereich des Adapters aufrufen könnte (Rückgabe als Textbox-output) und vor allem eine Listenversion von Prameter/Value mitgeben könnte beim Verbinden über die ChangeConfig-Methode posten könnte. Damit würden auch gleich "Heart-beat" und andere Dinge einstellbar werden. Diese Liste könnte der User invividuell füllen, vermutlich wird sie als default bei der Installation mit der Zeit mehr und mehr defaults mitbringen ;)

Liste der Parameter:
https://library.e.abb.com/public/0d9afc6917f84901be1d409da42c1fdf/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.7.pdf
Suche nach "Standard Configuration keys"

Think about update stable version to 0.4.0

Version: stable=0.3.3 (50 days old) => latest=0.4.0 (15 days old)
Installs: stable=82 (74.55%), latest=19 (17.27%), total=110
Click to edit

As you can see from the log´s, after some time (days) I regulary see the adapter still working in principle. Also reactions when plug-in the car as update in "Preparing" are updated in the objects. Means, TCP to the station and adapter itself is working.

However, when writing "transactionActive" to "true" it does not write it out to the station. Instead, it log´s "Timeout for message xyz.." -- And it never comes back, no option. Restarting the adapter, wait for re-connect to the wallbox, the same procedure works.

Anything I might log / test to gather more useful information?

logfile -->

ocpp.0 | 2022-11-23 19:23:41.440 | info | starting. Version 0.8.1 (non-npm: foxriver76/ioBroker.ocpp) in /opt/iobroker/node_modules/iobroker.ocpp, node: v16.18.1, js-controller: 4.0.23
ocpp.0 | 2022-11-23 19:23:36.007 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
ocpp.0 | 2022-11-23 19:23:36.005 | info | terminating
ocpp.0 | 2022-11-23 19:23:35.979 | info | Got terminate signal TERMINATE_YOURSELF
ocpp.0 | 2022-11-23 19:23:33.387 | error | Cannot execute command "transactionActive" for "/ABL-10115184.2": Timeout for message 8cf5fa4a-9059-4ba7-ad29-676a4ccc593e
ocpp.0 | 2022-11-23 19:22:39.292 | error | Cannot execute command "transactionActive" for "/ABL-10115184.2": Timeout for message 9e062967-4798-4d96-9eef-2afe917ec1ba
ocpp.0 | 2022-11-23 19:19:00.271 | error | Cannot execute command "transactionActive" for "/ABL-10115184.2": Timeout for message 020dec24-d1c3-4d85-b03d-a0580b39592c
ocpp.0 | 2022-11-23 19:16:37.117 | warn | Status from "/ABL-10115184.2" contains an errorCode: NoError
ocpp.0 | 2022-11-23 19:16:37.106 | info | Received Status Notification from "/ABL-10115184.2": Preparing
ocpp.0 | 2022-11-23 19:25:00.397 | warn | Status from "/ABL-10115184.2" contains an errorCode: NoError
ocpp.0 | 2022-11-23 19:25:00.396 | info | Received Status Notification from "/ABL-10115184.2": Charging
ocpp.0 | 2022-11-23 19:24:59.479 | warn | Status from "/ABL-10115184.2" contains an errorCode: NoError
ocpp.0 | 2022-11-23 19:24:59.479 | info | Received Status Notification from "/ABL-10115184.2": SuspendedEV
ocpp.0 | 2022-11-23 19:24:51.827 | info | Received MeterValues from "/ABL-10115184.2"
ocpp.0 | 2022-11-23 19:24:51.740 | info | Received Start transaction from "/ABL-10115184.2"
ocpp.0 | 2022-11-23 19:24:28.219 | info | Sending GetConfiguration to "/ABL-10115184"

Die angelegten Verzeichnisse für die Ladestation beginnen mit einem "/" - das verhindert die Verarbeitung zum Beispiel in node-red, dort werden diese nodes nicht geschaltet. Entweder sollten diese führenden dashes (und andere Sonderzeichen) unterdrückt werden oder -- noch besser und kompatibel mit bisherigen Installationen - es sollte einen config-schalter geben, mit dem dieses Verhalten geschaltet werden kann.

Beispiel für einen solchen Ordner, siehe "name":
{
"type": "device",
"common": {
"name": "/ABL-10115184"
},
"native": {
"chargePointVendor": "ABL",
"chargePointModel": "3W2264",
"chargePointSerialNumber": "10115***",
"chargeBoxSerialNumber": "10097***",
"firmwareVersion": "1.8p2",
"commandOcpp": "BootNotification"
},
"from": "system.adapter.ocpp.0",
"user": "system.user.admin",
"ts": 1665172706***,
"_id": "ocpp.0./ABL-10115184",
"acl": {
"object": 1638,
"owner": "system.user.admin",
"ownerGroup": "system.group.administrator"
}
}

Ich nutze aktuell den Adapter v0.6.0 und bekomme u. a. die LED-Farben der Wallbox geliefert.

Interessant wäre es, wenn diese in einen Datenpunkt geschrieben werden.

Bei mir sind es:

• Blue
• Yellow
• Green
• Off

ocpp.0	2022-08-28 16:22:51.204	info	Received DataTransfer from "http://192.168.178.80:9220/EVB-XXXXXXXXX" with id "evbStatusNotification": 1,Preparing,NoError,No error.,0,Green,0,{20,7984,100},{0,0},{B,11916,9894,61568},0,0,380,2022-08-28T14:22:50Z,0,3,{0,0,0,0,0,0,0,0,0},300,1,0,113,0,310,900,0
ocpp.0	2022-08-28 16:22:57.104	info	Received Authorization Request from "http://192.168.178.80:9220/EVB-XXXXXXXXX"
ocpp.0	2022-08-28 16:22:58.152	info	Received Status Notification from "http://192.168.178.80:9220/EVB-XXXXXXXXX": Preparing
ocpp.0	2022-08-28 16:22:58.196	info	Received DataTransfer from "http://192.168.178.80:9220/EVB-XXXXXXXXX" with id "evbStatusNotification": 1,Preparing,NoError,No error.,0,Off,0,{20,7984,100},{0,0},{B,11910,9164,61568},0,0,380,2022-08-28T14:22:57Z,0,3,{0,0,0,0,0,0,0,0,0},300,0,0,113,0,310,900,0
ocpp.0	2022-08-28 16:23:01.164	info	Received Status Notification from "http://192.168.178.80:9220/EVB-XXXXXXXXX": SuspendedEVSE
ocpp.0	2022-08-28 16:23:01.392	info	Received Status Notification from "http://192.168.178.80:9220/EVB-XXXXXXXXX": SuspendedEV
ocpp.0	2022-08-28 16:23:02.444	info	Received Start transaction from "http://192.168.178.80:9220/EVB-XXXXXXXXX"
ocpp.0	2022-08-28 16:23:03.564	info	Received Status Notification from "http://192.168.178.80:9220/EVB-XXXXXXXXX": Charging
ocpp.0	2022-08-28 16:23:07.465	info	Received DataTransfer from "http://192.168.178.80:9220/EVB-XXXXXXXXX" with id "evbStatusNotification": 1,SuspendedEVSE,NoError,No error.,0,Yellow,1,{20,7981,10},{0,0},{B,11917,8788,7804},0,0,380,2022-08-28T14:23:00Z,1,3,{0,0,0,0,0,0,0,0,0},300,0,0,125,0,310,60,0
ocpp.0	2022-08-28 16:23:12.464	info	Received DataTransfer from "http://192.168.178.80:9220/EVB-XXXXXXXXX" with id "evbStatusNotification": 1,SuspendedEV,NoError,No error.,0,Yellow,1,{20,7981,10},{0,0},{B,11920,8652,12208},0,0,380,2022-08-28T14:23:00Z,1,3,{0,0,0,0,0,0,0,0,0},300,0,0,125,0,310,60,0
ocpp.0	2022-08-28 16:23:17.464	info	Received DataTransfer from "http://192.168.178.80:9220/EVB-XXXXXXXXX" with id "evbStatusNotification": 1,Charging,NoError,No error.,1,Blue,1,{20,7981,10},{0,0},{C,11920,5884,12208},0,0,380,2022-08-28T14:23:03Z,1,3,{0,0,0,0,0,0,0,0,0},300,0,0,114,0,310,60,0
ocpp.0	2022-08-28 16:34:20.867	info	New valid connection from "http://192.168.178.80:9220/EVB-XXXXXXXXX" (http/ocpp1.6)
ocpp.0	2022-08-28 16:38:05.902	info	Received MeterValues from "http://192.168.178.80:9220/EVB-XXXXXXXXX"
ocpp.0	2022-08-28 16:38:10.449	info	Received DataTransfer from "http://192.168.178.80:9220/EVB-XXXXXXXXX" with id "evbStatusNotification": 1,Charging,NoError,No error.,1,Blue,1,{20,7984,26},{0,0},{C,11920,6076,12191},0,0,390,2022-08-28T14:38:05Z,1,3,{0,0,0,0,0,0,0,0,0},320,15,1,112,0,340,160,0

Danke für diesen tollen Adapter!

Moin, nochmal danke für deine Tolle Arbeit. Könntest du bei Gelegenheit die MeterValues ergänzen?
Die Wallbox ist eine ABB Terra AC und diese Daten werden bereits aus dem ocpp Log mitgeliefert.

2022-01-18 20:00:50.625 debug {"connectorId":1,"transactionId":1,"meterValue":[{"timestamp":"2022-01-18T19:00:50.000Z","sampledValue": [{"value":"229.60","context":"Sample.Periodic","format":"Raw","measurand":"Voltage","phase":"L1-N","unit":"V"}, {"value":"9.57","context":"Sample.Periodic","format":"Raw","measurand":"Current.Import","phase":"L1","unit":"A"}, {"value":"2170","context":"Sample.Periodic","format":"Raw","measurand":"Power.Active.Import","phase":"L1","unit":"W"}, {"value":"229.90","context":"Sample.Periodic","format":"Raw","measurand":"Voltage","phase":"L2-N","unit":"V"}, {"value":"9.54","context":"Sample.Periodic","format":"Raw","measurand":"Current.Import","phase":"L2","unit":"A"}, {"value":"2163","context":"Sample.Periodic","format":"Raw","measurand":"Power.Active.Import","phase":"L2","unit":"W"}, {"value":"232.40","context":"Sample.Periodic","format":"Raw","measurand":"Voltage","phase":"L3-N","unit":"V"}, {"value":"0.0","context":"Sample.Periodic","format":"Raw","measurand":"Current.Import","phase":"L3","unit":"A"}, {"value":"0","context":"Sample.Periodic","format":"Raw","measurand":"Power.Active.Import","phase":"L3","unit":"W"}, {"value":"176","context":"Sample.Periodic","format":"Raw","measurand":"Energy.Active.Import.Register","unit":"Wh"}, {"value":"10","context":"Sample.Periodic","format":"Raw","measurand":"Current.Offered","unit":"A"}]}], "commandOcpp":"MeterValues"}

Hello,

My Problem im not getting fixed is the Web port delivers a Upgrade Required when accessing.
Further in the console of the Webbrowser it shows an error 426.

Versions:

• Adapter version: V0.12.5
• JS-Controller version: 4.0.24
• Node version: v16.19.1
• Operating system: Linux

Ladesäulen, die mehr als einen Ladepunkt haben, werden über "connectorId" 1,2,.. gezeigt. Leider sind damit Änderungen / Abfragen nicht so ohne weiteres möglich. Logischer wäre doch, einen Pfad "connectors" mit jeweils einem Baum "1",.."2",.. zu erzeugen, in dem sich dann jeweils meterValues, status, transactionActive und so weiter befinden - oder?

Guten Morgen

Meine WB scheint zum ändern der Werte immer den IDTag zu benötigen.
Soweit ich das im Debug sehe, wird Standartmäßig die "1" mitgesendet.
Ich müsste aber den Tag von meiner RFID Karte mitsenden.
Ist es möglich diesen irgendwo einzufügen?

by checking config SupportedFeatureProfiles

Think about update stable version to 0.12.5

Version: stable=0.4.0 (460 days old) => latest=0.12.5 (135 days old)
Installs: stable=320 (70.64%), latest=78 (17.22%), total=453
Click to edit

Think about update stable version to 0.5.1

Version: stable=0.4.0 (133 days old) => latest=0.5.1 (15 days old)
Installs: stable=174 (85.71%), latest=17 (8.37%), total=203
Click to edit

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/foxriver76/ioBroker.ocpp

• [E019] Invalid repository URL: [email protected]:foxriver76/ioBroker.ocpp.git. Expected: git+https://github.com/foxriver76/ioBroker.ocpp.git
• [E140] width and height of logo are not equal
• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.ocpp"

I have also found warnings that may be fixed if possible.

• [W801] .npmignore not found

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Since 19.01.2022:

2022-01-20 12:28:10.553  - �[32minfo�[39m: host.iobroker-d Updating repository "beta" under "http://download.iobroker.net/sources-dist-latest.json"
2022-01-20 12:28:11.441  - �[33mwarn�[39m: host.iobroker-d warning: Following packages cannot be read: ocpp
2022-01-20 12:28:11.709  - �[32minfo�[39m: admin.0 (127) Repository received successfully.

Hi, is it possible to support OCPP 2.0.1?

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Describe the bug

Bug 1:
I tried to connect a Wallbox Pulsar Plus. Conection works, but when I try to set the object "transactionActive" to true, I can see in the log an error message:

error: Cannot execute command "transactionActive" for "/martin.1": validation of RemoteStartTransaction failed

Just before that message I see this debug message:
debug: Sending RemoteStartTransaction for /martin.1: {"connectorId":1,"idTag":"ioBroker","chargingProfile":{"chargingProfileId":1,"stackLevel":0,"chargingProfilePurpose":"TxDefaultProfile","chargingProfileKind":"Recurring","recurrencyKind":"Daily","chargingSchedule":{"duration":86400,"startSchedule":"2013-01-01T00:00Z","chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":7,"numberPhases":1}]}}}

Bug 2:
When I try to set the object "chargeLimit" to any value, e.g. 11, I can see in the log an error message:

error: Cannot execute command "chargeLimit" for "/martin.1": validation of SetChargingProfile failed

Just before that message I see this debug message:

debug: Sending SetChargingProfile for /martin.1

Maybe you can give me a hint where in your code I could look at.

Kind Regards, Martin Schneider (email: [email protected]).

Versions:

• Adapter version: 0.12.5
• JS-Controller version: ?
• Node version: ?
• Operating system: docker on QNAP nas

Moin @foxriver76,
könntest du einmal prüfen, ob man die RFID-Nummer auch in den idTag schreiben kann?
Ich habe aktuell 3 RFID-Chips im Einsatz und die Anzahl der Zeichen sind ca. 14-15.

Hier ist der Auszug aus dem Log:

ocpp.0 | 2023-01-16 21:06:21.227 | debug | {"idTag":"XXXXXXXXXXXXXX","commandOcpp":"Authorize"}
ocpp.0 | 2023-01-16 21:06:15.845 | info | Received Status Notification from "/TACW1142021G1020.1": SuspendedEVSE
ocpp.0 | 2023-01-16 21:06:15.845 | debug | "connectorId":1,"errorCode":"NoError","info":"null","status":"SuspendedEVSE","vendorErrorCode":"0x0000","commandOcpp":"StatusNotification"}
ocpp.0 | 2023-01-16 21:06:15.345 | info | Received Start transaction from "/TACW1142021G1020.1"
ocpp.0 | 2023-01-16 21:06:15.345 | debug | {"connectorId":1,"idTag":"XXXXXXXXXXXXXX","meterStart":0,"timestamp":"2023-01-16T20:06:13.000Z","commandOcpp":"StartTransaction"}