feat(OCPP2.x): Dynamic device model initialization #1194
Merged
Conversation
This file contains hidden or 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
Pietfried
force-pushed
the
feature/ocpp-dynamic-device-model-initialization
branch
3 times, most recently
from
e6ede4a to
64bc2d6
Compare
Pietfried
force-pushed
the
feature/ocpp-dynamic-device-model-initialization
branch
from
0c83128 to
97300d1
Compare
Pietfried
changed the title
Pietfried
requested review from
hikinggrass,
corneliusclaussen,
SebaLukas,
AssemblyJohn and
mlitre
as code owners
4 tasks
mlitre
reviewed
Jun 5, 2025
Pietfried
force-pushed
the
feature/ocpp-dynamic-device-model-initialization
branch
2 times, most recently
from
360b357 to
f6a6a23
Compare
mlitre
reviewed
Jun 11, 2025
mlitre
previously approved these changes
Jun 12, 2025
Pietfried
commented
Jun 12, 2025
mlitre
approved these changes
Jun 12, 2025
hikinggrass
approved these changes
Jun 12, 2025
Pietfried
force-pushed
the
feature/ocpp-dynamic-device-model-initialization
branch
from
9b8baf9 to
800aca1
Compare
… startup - Updated ComposedDeviceModelStorage to accept EVSE manager references - Refactored EverestDeviceModelStorage to build device model from EvseManager data - Added static definitions for EVSE and Connector variable characteristics - Introduced variable handling, component creation, and attribute updates - Subscribing to hw capabilities to use them in the EverestDeviceModel - Added log warning in case device model component variable combination is present multiple times Signed-off-by: Piet Gömpel <pietgoempel@gmail.com>
Pietfried
force-pushed
the
feature/ocpp-dynamic-device-model-initialization
branch
from
800aca1 to
c1fc6ab
Compare
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
This PR extends to OCPP201 module to dynamically initialize the EVSE and Connector device model components based on the EVerest configuration.
Before this change, the correct number of EVSE and Connector components had to be defined and installed manually. This PR in libocpp ensures that the custom EVSE and Connector components are not installed anymore by default.
Note: To migrate using the EVSE and Connector components managed by OCPP201 module instead of the libocpp device model, the Connector and EVSE components should be removed from the installation directory. When EVerest starts up, it will then remove these components from libocpp's device model storage.
Issue ticket number and link
Checklist before requesting a review