Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GetConfiguration without key #1442

Open
MateoGreil opened this issue Dec 24, 2024 · 0 comments
Open

GetConfiguration without key #1442

MateoGreil opened this issue Dec 24, 2024 · 0 comments

Comments

@MateoGreil
Copy link

Is your feature request related to a problem? Please describe.
The current implementation of get_configuration with ocpp_key = "" (which corresponds to requesting all configurations in the OCPP protocol) does not properly store the result in the Timestamp Config Response attribute. When key = "", it only saves the first value as key: first_value, instead of returning all the keys and values.

Describe the solution you'd like
When making a get_configuration request with ocpp_key = "", the desired behavior is to have all the keys and values returned and stored properly, not just the first value. This would allow retrieving all the configurations of the charger when an empty key is provided.

Furthermore, it would be beneficial to have an ocpp_configurations sensor that gets updated on each boot and each set_configuration call. This attribute should return the result of get_configuration with key = "", providing a way to view all the configurations of the charger.

Describe alternatives you've considered
Today, without this feature, I use the log to know the configuration of my charger.

Additional context
When the get_configuration is done with a key (it's working properly):
image
When the get_configuration is done without a key (it's not working properly):
image

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

No branches or pull requests

1 participant