Sevket Gökay

if the charging really and actually started at 13:52 in your local time, the station should have used one of the following formats to express it: - `2021-05-08T13:52:00+01:00` - `2021-05-08T12:52:00+00:00`...

> ... which the station then interprets as an hour ahead. i hope you meant steve and this was a typo. > OCPP says that it is recommended for the...

> If I set the time to UTC in steve, then when a user schedules a charge it will be the incorrect time. true, currently the user has to do...

> My preference would be for the charge point to have the option to select date format in UTC or 'no time zone offset' or the charge point doesn't update...

thanks. i think we can even extend this to an ocpp tag, because it is the other party participating in a transaction.

useful: - http://www.jooq.org/doc/latest/manual/sql-building/sql-statements/select-statement/limit-clause/ - http://blog.jooq.org/2014/08/06/join-the-no-offset-movement/ - http://blog.jooq.org/2013/11/18/faster-sql-pagination-with-keysets-continued/

thanks for sharing your contribution and repo @DeltaVetal26! i agree that steve not having a direct api is problematic and can result in less-than-optimal solutions, but i am not sure...

`org.springframework.validation.beanvalidation.LocalValidatorFactoryBean` which is created in `BeanConfiguration` uses the javax.* namespace. unfortunately, spring still uses hibernate validator < 7.0 and therefore the older namespace. this PR has to wait.

if the call in any shape or form arrives at steve, there must be an entry in the logs. if there is not, the packet probably cannot reach steve. and...

ToDos: - [x] REST Controller for OCPP Tags with CRUD functionality (i.e. what OCPP Tags page under Data Management offers: same querying possibilities, same response data models). JSON payloads. -...