Feature/706 ocpp 201 california pricing requirements #757
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…pricing for 2.0.1 Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
…o feature/706-ocpp-201-california-pricing-requirements
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
…s and add more logging in the callback validate function. Implement cost and tariff from transactioneventresponse. Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
…dd multilanguage for california pricing. Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
…ve conversions to everest core. Change transaction id to identifier type. Start with metervalue triggers. Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
…california-pricing-requirements
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
… Some changes in variables with a wrong name. Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
…x some bugs, mainly with triggers. Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
…e in utils). Some comments and also send power active measurand to be sure (if it is there anyway) Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
maaikez
requested review from
Pietfried,
hikinggrass and
marcemmers
as code owners
|
Made this a pull request now. I have to merge master still. And I have a question: Should the metervalue triggers be stored to the database as well? So if libocpp crashes, the triggers will be stored? Almost all is (partly) tested with ocpp-testing, except the authorizeresponse message. |
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
maaikez
force-pushed
the
feature/706-ocpp-201-california-pricing-requirements
branch
from
8e7a9fb
to
a47c677
Compare
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
hikinggrass
requested changes
Sep 24, 2024
Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
hikinggrass
approved these changes
Sep 24, 2024
maaikez
deleted the
feature/706-ocpp-201-california-pricing-requirements
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
OCPP 201 california pricing requirements. This includes display message and tariffandcost
Issue ticket number and link
#706
Checklist before requesting a review