Skip to content

Conversation

@james-ctc
Copy link
Member

Describe your changes

In OCPP 1.6 previously only custom configuration could be updated via method calls.
This updated allows method calls to update OCPP configuration with the same processing that would occur had the request been via OCPP.

Issue ticket number and link

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • If OCPP 2.0.1 or OCPP2.1: I have updated the OCPP 2.x status document
  • I read the contribution documentation and made sure that my changes meet its requirements

feat: set custom key removed and replaced with set key
This allows all OCPP 1.6 keys to be set via EVerest internal and
stable APIs

Signed-off-by: James Chapman <james.chapman@pionix.de>
When some keys are updated then an action is performed.
This commit ensures the same actions are preformed regardless
of where the update comes from (method call or OCPP)

Signed-off-by: James Chapman <james.chapman@pionix.de>
Signed-off-by: James Chapman <james.chapman@pionix.de>
@james-ctc james-ctc merged commit 94996c0 into apricot/develop Nov 17, 2025
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants