Sevket Gökay
Sevket Gökay
this is by design. i addressed this point in various issues, here is [one example](https://github.com/steve-community/steve/issues/217#issuecomment-545353260).
an excerpt from [another msg](https://github.com/steve-community/steve/issues/1294#issuecomment-1802900271): > however, all these possibilities assume steve to be a tight controller and gatekeeper for the sake of security. there is a tone in spec...
steve already has the functionality of what you call "soft stop", which the user has to do manually in GUI because i didn't enforce this globally. what is your suggestion?...
i think you are focusing too much on a technicality (i.e. state machines) but not much on the business side. state machine is a just a model of real world...
thank you for the lecture on state machines... even though i know them quite well myself and implemented them professionally before. as i said, feel free to contribute to the...
> if you're running the CSMS on a GMT+X timezone. so, you are running steve not in the default (i.e. UTC) but some other timezone?
hey @UBT-FJ did you look at the ocpp spec?
the details page of an ocpp tag has the field "Expiry Date/Time" which you can set.
> I was thinking maybe the problem is the TZ as I'm in CEST and SteVe is in UTC? you found the reason. database, backend, frontend are using UTC for...
after [this PR](https://github.com/steve-community/steve/issues/1787), your TZ-related issues should be resolved, since we support full ISO 8601 with timezones now.