NEWS
Alpha Testing: OCPP Wallbox Adapter
-
So habe jetzt mal überall rumgespielt und geloggt.
Es scheint alles irgendwie eine Reaktion auszulösen.
Nur das ChargeLimit verläuft im Sand.Wenn ich TransaktionActive schalte, sendet er auch den eingestellten Limit Wert mit habe ich gesehen. Das ändert nur an der Box nichts da diese stoppt wenn ich da spiele.
Vielleicht kann da jemand was aus dem Log lesen.
Bin da echt ratlos2022-07-08 19:22:04.531 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:22:04.534 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:22:24.979 - debug: ocpp.0 (1506) Sending RemoteStartTransaction for /C2011601CNYEYPES: {"connectorId":1,"idTag":"1","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":6}]}}} 2022-07-08 19:22:59.532 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:22:59.534 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:23:13.013 - debug: ocpp.0 (1506) Sending SetChargingProfile for /C2011601CNYEYPES 2022-07-08 19:23:21.697 - debug: ocpp.0 (1506) Sending RemoteStopTransaction for /C2011601CNYEYPES 2022-07-08 19:23:34.709 - debug: ocpp.0 (1506) Sending RemoteStartTransaction for /C2011601CNYEYPES: {"connectorId":1,"idTag":"1","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":8}]}}} 2022-07-08 19:23:54.545 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:23:54.546 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:24:49.557 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:24:49.559 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:25:44.560 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:25:44.562 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:26:39.575 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:26:39.577 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:27:34.583 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:27:34.585 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:28:29.594 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:28:29.596 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:28:32.846 - debug: ocpp.0 (1506) {"connectorId":1,"timestamp":"2022-07-08T17:28:32+00:00","errorCode":"NoError","status":"Available","commandOcpp":"StatusNotification"} 2022-07-08 19:28:32.847 - info: ocpp.0 (1506) Received Status Notification from "/C2011601CNYEYPES": Available 2022-07-08 19:28:44.783 - debug: ocpp.0 (1506) {"connectorId":1,"timestamp":"2022-07-08T17:28:44+00:00","errorCode":"NoError","status":"Preparing","commandOcpp":"StatusNotification"} 2022-07-08 19:28:44.786 - info: ocpp.0 (1506) Received Status Notification from "/C2011601CNYEYPES": Preparing 2022-07-08 19:29:24.599 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:29:24.601 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:29:37.288 - debug: ocpp.0 (1506) {"timestamp":"2022-07-08T17:29:36+00:00","idTag":"C7131506","connectorId":1,"meterStart":6340,"commandOcpp":"StartTransaction"} 2022-07-08 19:29:37.290 - info: ocpp.0 (1506) Received Start transaction from "/C2011601CNYEYPES" 2022-07-08 19:29:37.394 - debug: ocpp.0 (1506) {"connectorId":1,"timestamp":"2022-07-08T17:29:36+00:00","errorCode":"NoError","status":"Charging","commandOcpp":"StatusNotification"} 2022-07-08 19:29:37.396 - info: ocpp.0 (1506) Received Status Notification from "/C2011601CNYEYPES": Charging 2022-07-08 19:30:01.418 - debug: ocpp.0 (1506) {"connectorId":1,"meterValue":[{"timestamp":"2022-07-08T17:30:00+00:00","sampledValue":[{"value":"47.0","context":"Sample.Clock","unit":"Celsius","measurand":"Temperature","format":"Raw","location":"Body"},{"value":"9.81","context":"Sample.Clock","unit":"A","measurand":"Current.Import","format":"Raw","phase":"L1","location":"Outlet"},{"value":"225.0","context":"Sample.Clock","unit":"V","measurand":"Voltage","format":"Raw","phase":"L1","location":"Outlet"},{"value":"2.198","context":"Sample.Clock","unit":"kW","measurand":"Power.Active.Import","format":"Raw","location":"Outlet"},{"value":"6350","context":"Sample.Clock","unit":"Wh","measurand":"Energy.Active.Import.Register","format":"Raw","location":"Outlet"}]}],"transactionId":1,"commandOcpp":"MeterValues"} 2022-07-08 19:30:01.421 - info: ocpp.0 (1506) Received MeterValues from "/C2011601CNYEYPES" 2022-07-08 19:30:19.603 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:30:19.606 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:30:37.385 - debug: ocpp.0 (1506) {"connectorId":1,"meterValue":[{"timestamp":"2022-07-08T17:30:36+00:00","sampledValue":[{"value":"47.0","context":"Sample.Periodic","unit":"Celsius","measurand":"Temperature","format":"Raw","location":"Body"},{"value":"9.95","context":"Sample.Periodic","unit":"A","measurand":"Current.Import","format":"Raw","phase":"L1","location":"Outlet"},{"value":"224.9","context":"Sample.Periodic","unit":"V","measurand":"Voltage","format":"Raw","phase":"L1","location":"Outlet"},{"value":"2.227","context":"Sample.Periodic","unit":"kW","measurand":"Power.Active.Import","format":"Raw","location":"Outlet"},{"value":"6380","context":"Sample.Periodic","unit":"Wh","measurand":"Energy.Active.Import.Register","format":"Raw","location":"Outlet"}]}],"transactionId":1,"commandOcpp":"MeterValues"} 2022-07-08 19:30:37.387 - info: ocpp.0 (1506) Received MeterValues from "/C2011601CNYEYPES" 2022-07-08 19:31:14.603 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:31:14.604 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:31:37.587 - debug: ocpp.0 (1506) {"connectorId":1,"meterValue":[{"timestamp":"2022-07-08T17:31:37+00:00","sampledValue":[{"value":"45.0","context":"Sample.Periodic","unit":"Celsius","measurand":"Temperature","format":"Raw","location":"Body"},{"value":"10.02","context":"Sample.Periodic","unit":"A","measurand":"Current.Import","format":"Raw","phase":"L1","location":"Outlet"},{"value":"225.8","context":"Sample.Periodic","unit":"V","measurand":"Voltage","format":"Raw","phase":"L1","location":"Outlet"},{"value":"2.253","context":"Sample.Periodic","unit":"kW","measurand":"Power.Active.Import","format":"Raw","location":"Outlet"},{"value":"6410","context":"Sample.Periodic","unit":"Wh","measurand":"Energy.Active.Import.Register","format":"Raw","location":"Outlet"}]}],"transactionId":1,"commandOcpp":"MeterValues"} 2022-07-08 19:31:37.589 - info: ocpp.0 (1506) Received MeterValues from "/C2011601CNYEYPES" 2022-07-08 19:32:09.619 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:32:09.621 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:32:37.760 - debug: ocpp.0 (1506) {"connectorId":1,"meterValue":[{"timestamp":"2022-07-08T17:32:37+00:00","sampledValue":[{"value":"43.0","context":"Sample.Periodic","unit":"Celsius","measurand":"Temperature","format":"Raw","location":"Body"},{"value":"9.94","context":"Sample.Periodic","unit":"A","measurand":"Current.Import","format":"Raw","phase":"L1","location":"Outlet"},{"value":"225.2","context":"Sample.Periodic","unit":"V","measurand":"Voltage","format":"Raw","phase":"L1","location":"Outlet"},{"value":"2.229","context":"Sample.Periodic","unit":"kW","measurand":"Power.Active.Import","format":"Raw","location":"Outlet"},{"value":"6450","context":"Sample.Periodic","unit":"Wh","measurand":"Energy.Active.Import.Register","format":"Raw","location":"Outlet"}]}],"transactionId":1,"commandOcpp":"MeterValues"} 2022-07-08 19:32:37.762 - info: ocpp.0 (1506) Received MeterValues from "/C2011601CNYEYPES" 2022-07-08 19:32:42.762 - debug: ocpp.0 (1506) Sending SetChargingProfile for /C2011601CNYEYPES 2022-07-08 19:33:04.620 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:33:04.623 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:33:37.860 - debug: ocpp.0 (1506) {"connectorId":1,"meterValue":[{"timestamp":"2022-07-08T17:33:37+00:00","sampledValue":[{"value":"42.0","context":"Sample.Periodic","unit":"Celsius","measurand":"Temperature","format":"Raw","location":"Body"},{"value":"9.9","context":"Sample.Periodic","unit":"A","measurand":"Current.Import","format":"Raw","phase":"L1","location":"Outlet"},{"value":"224.5","context":"Sample.Periodic","unit":"V","measurand":"Voltage","format":"Raw","phase":"L1","location":"Outlet"},{"value":"2.215","context":"Sample.Periodic","unit":"kW","measurand":"Power.Active.Import","format":"Raw","location":"Outlet"},{"value":"6490","context":"Sample.Periodic","unit":"Wh","measurand":"Energy.Active.Import.Register","format":"Raw","location":"Outlet"}]}],"transactionId":1,"commandOcpp":"MeterValues"} 2022-07-08 19:33:37.862 - info: ocpp.0 (1506) Received MeterValues from "/C2011601CNYEYPES" 2022-07-08 19:33:59.648 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:33:59.651 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:34:08.486 - debug: ocpp.0 (1506) Sending RemoteStopTransaction for /C2011601CNYEYPES 2022-07-08 19:34:09.804 - debug: ocpp.0 (1506) {"timestamp":"2022-07-08T17:34:08+00:00","transactionData":[{"timestamp":"2022-07-08T17:30:00+00:00","sampledValue":[{"context":"Sample.Clock","value":"47.0","unit":"Celsius","measurand":"Temperature","format":"Raw","location":"Body"},{"context":"Sample.Clock","value":"9.81","unit":"A","measurand":"Current.Import","format":"Raw","location":"Outlet","phase":"L1"},{"context":"Sample.Clock","value":"225.0","unit":"V","measurand":"Voltage","format":"Raw","location":"Outlet","phase":"L1"},{"context":"Sample.Clock","value":"2.198","unit":"kW","measurand":"Power.Active.Import","format":"Raw","location":"Outlet"},{"context":"Sample.Clock","value":"6350","unit":"Wh","measurand":"Energy.Active.Import.Register","format":"Raw","location":"Outlet"}]},{"timestamp":"2022-07-08T17:30:36+00:00","sampledValue":[{"context":"Sample.Periodic","value":"47.0","unit":"Celsius","measurand":"Temperature","format":"Raw","location":"Body"},{"context":"Sample.Periodic","value":"9.95","unit":"A","measurand":"Current.Import","format":"Raw","location":"Outlet","phase":"L1"},{"context":"Sample.Periodic","value":"224.9","unit":"V","measurand":"Voltage","format":"Raw","location":"Outlet","phase":"L1"},{"context":"Sample.Periodic","value":"2.227","unit":"kW","measurand":"Power.Active.Import","format":"Raw","location":"Outlet"},{"context":"Sample.Periodic","value":"6380","unit":"Wh","measurand":"Energy.Active.Import.Register","format":"Raw","location":"Outlet"}]},{"timestamp":"2022-07-08T17:31:37+00:00","sampledValue":[{"context":"Sample.Periodic","value":"45.0","unit":"Celsius","measurand":"Temperature","format":"Raw","location":"Body"},{"context":"Sample.Periodic","value":"10.02","unit":"A","measurand":"Current.Import","format":"Raw","location":"Outlet","phase":"L1"},{"context":"Sample.Periodic","value":"225.8","unit":"V","measurand":"Voltage","format":"Raw","location":"Outlet","phase":"L1"},{"context":"Sample.Periodic","value":"2.253","unit":"kW","measurand":"Power.Active.Import","format":"Raw","location":"Outlet"},{"context":"Sample.Periodic","value":"6410","unit":"Wh","measurand":"Energy.Active.Import.Register","format":"Raw","location":"Outlet"}]},{"timestamp":"2022-07-08T17:32:37+00:00","sampledValue":[{"context":"Sample.Periodic","value":"43.0","unit":"Celsius","measurand":"Temperature","format":"Raw","location":"Body"},{"context":"Sample.Periodic","value":"9.94","unit":"A","measurand":"Current.Import","format":"Raw","location":"Outlet","phase":"L1"},{"context":"Sample.Periodic","value":"225.2","unit":"V","measurand":"Voltage","format":"Raw","location":"Outlet","phase":"L1"},{"context":"Sample.Periodic","value":"2.229","unit":"kW","measurand":"Power.Active.Import","format":"Raw","location":"Outlet"},{"context":"Sample.Periodic","value":"6450","unit":"Wh","measurand":"Energy.Active.Import.Register","format":"Raw","location":"Outlet"}]},{"timestamp":"2022-07-08T17:33:37+00:00","sampledValue":[{"context":"Sample.Periodic","value":"42.0","unit":"Celsius","measurand":"Temperature","format":"Raw","location":"Body"},{"context":"Sample.Periodic","value":"9.9","unit":"A","measurand":"Current.Import","format":"Raw","location":"Outlet","phase":"L1"},{"context":"Sample.Periodic","value":"224.5","unit":"V","measurand":"Voltage","format":"Raw","location":"Outlet","phase":"L1"},{"context":"Sample.Periodic","value":"2.215","unit":"kW","measurand":"Power.Active.Import","format":"Raw","location":"Outlet"},{"context":"Sample.Periodic","value":"6490","unit":"Wh","measurand":"Energy.Active.Import.Register","format":"Raw","location":"Outlet"}]}],"meterStop":6510,"transactionId":1,"idTag":"C7131506","reason":"Local","commandOcpp":"StopTransaction"} 2022-07-08 19:34:09.810 - info: ocpp.0 (1506) Received stop transaction from "/C2011601CNYEYPES" 2022-07-08 19:34:09.829 - debug: ocpp.0 (1506) {"connectorId":1,"timestamp":"2022-07-08T17:34:09+00:00","errorCode":"NoError","status":"Finishing","commandOcpp":"StatusNotification"} 2022-07-08 19:34:09.833 - info: ocpp.0 (1506) Received Status Notification from "/C2011601CNYEYPES": Finishing 2022-07-08 19:34:21.779 - debug: ocpp.0 (1506) Sending RemoteStartTransaction for /C2011601CNYEYPES: {"connectorId":1,"idTag":"1","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":8}]}}} 2022-07-08 19:34:54.666 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:34:54.668 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:35:21.726 - debug: ocpp.0 (1506) Sending ChangeAvailability for /C2011601CNYEYPES: Inoperative 2022-07-08 19:35:22.320 - debug: ocpp.0 (1506) {"connectorId":1,"timestamp":"2022-07-08T17:35:21+00:00","errorCode":"NoError","status":"Unavailable","commandOcpp":"StatusNotification"} 2022-07-08 19:35:22.322 - info: ocpp.0 (1506) Received Status Notification from "/C2011601CNYEYPES": Unavailable 2022-07-08 19:35:32.543 - debug: ocpp.0 (1506) Sending RemoteStopTransaction for /C2011601CNYEYPES 2022-07-08 19:35:45.796 - debug: ocpp.0 (1506) Sending ChangeAvailability for /C2011601CNYEYPES: Operative 2022-07-08 19:35:46.361 - debug: ocpp.0 (1506) {"connectorId":1,"timestamp":"2022-07-08T17:35:45+00:00","errorCode":"NoError","status":"Finishing","commandOcpp":"StatusNotification"} 2022-07-08 19:35:46.363 - info: ocpp.0 (1506) Received Status Notification from "/C2011601CNYEYPES": Finishing 2022-07-08 19:35:49.681 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:35:49.683 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:35:53.654 - debug: ocpp.0 (1506) Sending RemoteStartTransaction for /C2011601CNYEYPES: {"connectorId":1,"idTag":"1","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":8}]}}} 2022-07-08 19:36:32.550 - debug: ocpp.0 (1506) Sending ChangeAvailability for /C2011601CNYEYPES: Inoperative 2022-07-08 19:36:33.094 - debug: ocpp.0 (1506) {"connectorId":1,"timestamp":"2022-07-08T17:36:32+00:00","errorCode":"NoError","status":"Unavailable","commandOcpp":"StatusNotification"} 2022-07-08 19:36:33.096 - info: ocpp.0 (1506) Received Status Notification from "/C2011601CNYEYPES": Unavailable 2022-07-08 19:36:39.931 - debug: ocpp.0 (1506) Sending ChangeAvailability for /C2011601CNYEYPES: Operative 2022-07-08 19:36:40.540 - debug: ocpp.0 (1506) {"connectorId":1,"timestamp":"2022-07-08T17:36:39+00:00","errorCode":"NoError","status":"Finishing","commandOcpp":"StatusNotification"} 2022-07-08 19:36:40.541 - info: ocpp.0 (1506) Received Status Notification from "/C2011601CNYEYPES": Finishing 2022-07-08 19:36:44.684 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:36:44.686 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" 2022-07-08 19:37:39.688 - debug: ocpp.0 (1506) {"commandOcpp":"Heartbeat"} 2022-07-08 19:37:39.690 - debug: ocpp.0 (1506) Received heartbeat from "/C2011601CNYEYPES" -
@moonlanderpi sagte in Alpha Testing: OCPP Wallbox Adapter:
@glasfaser
Sorry gelobe BesserungBitte auch die anderen dazu auch änderen , die du zuvor eingestellt hast !
@glasfaser
Erledigt -
@moonlanderpi sagte in Alpha Testing: OCPP Wallbox Adapter:
Was mir auffällt das die Zeit nicht zusammen passt.
Was meinst du? Die Wallbox läuft auf Z-Zeit. Das ist aber vollkommen i. O., würde ich sagen.
Kurioserweise ist das auch nur im Protocoll. Hab die Uhrzeit in der Box gecheckt. Die passt.
-
Also bei mir geht das mit ChargeLimit ändern plötzlich. Keine Ahnung warum. Was aber ist, es funktioniert bei mir nur wenn ich ein Auto angestöpselt habe und das Auto wirklich lädt.
Hat von euch jemand OCPP und NodeRED Adapter im einsetz? Auslegen klappt jetzt mit * statt Namen der Wallbox. Schreiben geht aber nicht mit * und ohne Stern ersetzt NodeRed den / immer durch den *. Wäre hier um einen Tip dankbar. Finde NodeRed einfacher als das JS.
-
Also bei mir geht das mit ChargeLimit ändern plötzlich. Keine Ahnung warum. Was aber ist, es funktioniert bei mir nur wenn ich ein Auto angestöpselt habe und das Auto wirklich lädt.
Hat von euch jemand OCPP und NodeRED Adapter im einsetz? Auslegen klappt jetzt mit * statt Namen der Wallbox. Schreiben geht aber nicht mit * und ohne Stern ersetzt NodeRed den / immer durch den *. Wäre hier um einen Tip dankbar. Finde NodeRed einfacher als das JS.
Sorry, hab es mit JS gelöst. Finde es mit Blocky sogar viel einfacher als Node.
Leider habe ich das senden immernoch nicht hinbekommen.
Auto ist angestöpselt und lädt, dennoch wird das Chargelimit ignoriert.
Kannst du mal einstellen was du für ein String sendest bzw. bekommst wenn du das Limit gesendet hast? -
Ich habe leider keine Doku von der Box wie OCPP umgesetzt wurde.
Eine Möglichkeit ist eventuell das meine Box Watt statt Ampere braucht.
Soweit ich das im OCPP sehe ist es möglich siehe Beispieltelegram.Below you will find an example of a csChargingProfiles sent from the central system to a charge point.
Below you will find an example of a csChargingProfiles sent from the central system to a charge point. “csChargingProfiles”: { “chargingProfileId”: 158798, “chargingProfileKind”: “Absolute”, “chargingProfilePurpose”: “TxProfile”, “chargingSchedule”: { “chargingRateUnit”: “W”, “chargingSchedulePeriod”: [ { “limit”: 11000.0, “startPeriod”: 0 }, { “limit”: 9000.0, “startPeriod”: 780 }, { “limit”: 4500.0, “startPeriod”: 1680 }, “duration”: 1680 }, ], “stackLevel”: 0, “transactionId”: 339373, “validFrom”: “2020–10–15T14:32:00+00:00”, “validTo”: “2020–10–16T14:15:00+00:00” }Gibt es irgendwie eine Möglichkeit im Adapter das mal testweise von "A" auf "W" zu ändern?
-
Also Watt ist es anscheinend auch nicht.
Was ich aber bemerkt habe, dass bei RemotetransactionStart, der ID Tag mitgesendet wird.
Hab es mal bei der WB getestet, er beginnt nach Status Finishing ert wieder, wenn ich die RFID Karte vorhalte.
Den IdTag habe ich auch, aber wie bekomme ich den mitgesendet?
Eventuell erwartet die WB das, um Änderungen zu akzeptieren. -
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}]}}} ` -
Schönen guten Abend!
Also nach dem ich lange den „/„ am Ende der OCPP Server Adresse vergessen habe kann ich nun Erfolg melden.
Der Adapter spricht mit einer EVBox Elvi.
Es kommt nicht viel an aber wenigstens etwas!Sollte eigentlich mehr kommen oder ist das der aktuelle Stand ?!
Beste Grüße !
-
Schönen guten Abend!
Also nach dem ich lange den „/„ am Ende der OCPP Server Adresse vergessen habe kann ich nun Erfolg melden.
Der Adapter spricht mit einer EVBox Elvi.
Es kommt nicht viel an aber wenigstens etwas!Sollte eigentlich mehr kommen oder ist das der aktuelle Stand ?!
Beste Grüße !
@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.
Proxmox und HA
-
@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.
So "Er lebt", der Server empfängt heartbeats.
Nach einem Firmwareupdate der EVBox erhalte ich folgendes debug log:
Was hat es aber mit dem log in Zeile 19 auf sich Command not implemented ?
Proxmox und HA
-
So "Er lebt", der Server empfängt heartbeats.
Nach einem Firmwareupdate der EVBox erhalte ich folgendes debug log:
Was hat es aber mit dem log in Zeile 19 auf sich Command not implemented ?
@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.
-
So "Er lebt", der Server empfängt heartbeats.
Nach einem Firmwareupdate der EVBox erhalte ich folgendes debug log:
Was hat es aber mit dem log in Zeile 19 auf sich Command not implemented ?
@meister-mopper Gerne 0.6.0 probieren, es sollte ein Channel mit
dataTransferangelegt werden, der die transferierten Daten enthält.Hier könnt ihr mich unterstützen.
-
@meister-mopper Gerne 0.6.0 probieren, es sollte ein Channel mit
dataTransferangelegt werden, der die transferierten Daten enthält.@foxriver76
Super, das warndataTransfertaucht nicht mehr auf, allerdings bekomme ich immer einen Adapter Neustart, wenn ichtransactionActiveumstelle 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 schemaDieses 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 schemaProxmox und HA
-
@foxriver76
Super, das warndataTransfertaucht nicht mehr auf, allerdings bekomme ich immer einen Adapter Neustart, wenn ichtransactionActiveumstelle 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 schemaDieses 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@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.
-
@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. -
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 "/": Availablenpm 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 -
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 "/": Availablenpm 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@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.
Hier könnt ihr mich unterstützen.
-
@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 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.
Hier könnt ihr mich unterstützen.
-
@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.
@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 0Proxmox und HA
Support us
749
Online32.5k
Benutzer81.7k
Themen1.3m
Beiträge