steve-community / steve-plugsurfing Goto Github PK

as the title says.

@apheleia, can we make the changes in the code, without fearing to break your system?

I have sometimes problem with database on test server.

When I log to steve-ps I get these error message 👍

I am not really sure of what happen. This is probably due to an very important number of active transaction. It seems only append with the PS version. So I do not know if the problem do not come from PS server which should be down (after a reboot of Steve everything is fixed).

After somes google check, it seems that problem could be cause by a not coherent configuration between database (MariaDB in my case) and HikariCP. I should be interested to test somes change on max_connections and timeout of Hiraki but I can't find the config files.

FYI part of logs :

logstevepbhiraki.txt

When an PlugSurfing Tag is retun once at BLOCKED by plugsurfing verify method it stay locked even if the verify result change and become verified as TRUE.

When a remote start is done by PS app and the user do not "really" start the charge (wrong charge point or car never connected). Or when the user "stop" transaction directly by unplug the cable and not by remote.

In these cases, the user is lock in a strange situation. PS app think the plug is still in transaction and if the user press the "stop" button in PS he get an error and is not able to use the charge point before a clear cache or desinstall / reinstall app.

There is a possibility that the issue come from Plugsurfing but I suspect that Steve do not send/confirm stop informations :

• At the end a transaction not stopped by remote
• When a remote start was transmit to the chargepoint and the chargepoint do not confirm the "real" start of a transaction.

In Plugsurfing version of Steve the "connector status" view is not as complete as the normal Steve version.

The view do not indicate status of each connectors but only for the 0 and last events on others connectors. It is surprising because information are well available in database.

Maybe it is a technical choice due to Plugsurfing specificity.

Hello,
I all-ready tried Steve, and it is pretty awesome. I have a question concerning OCPP 1.6 compatibility.

OCPP 1.6 is very near from OCPP 1.5-J. New features concern mainly smart-charging. As specified in protocol definition, only "core" features are mandatory and we allready have them in Steve (1.5).

So, I would like to know if it is possible to update Steve and let it accept OCCP 1.6 charging stations and consider them like a 1.5(-J) charging station.

I am pretty sure there is something to do in /src/main/java/de/rwth/idsg/steve/ocpp/OcppVersion.java but my tests did not work.

Regards

When I add a charge point on the PS-STEVE. The field "web site" of the form is not saved properly, the field is saved by the email address. It works fine after an update in a second time.

I am pretty sure that the problem come from here : https://github.com/RWTH-i5-IDSG/steve-plugsurfing/blob/f10c2cc933440487ef2bd6eebe24d75d041aa596/src/main/java/de/rwth/idsg/steve/extensions/plugsurfing/repository/impl/StationRepositoryImpl.java#L194

Connector Status does not show anything on the homepage.

Similarly, when slecting a connectorID for an OCPP task, the connectorID drop down menu is empty.

Have one question: whether the current project "Steve" cover old project "Steve-plugsurfing"?

Tried build Steve-plugsurfing" with the environment of "Steve", build failed. Any suggestions?