Modify the SetChargingProfile command

Oct 13, 2025 by miodeya.com 26 views

Introduction

The SetChargingProfile issue is a critical problem that affects the functionality of charging stations, particularly when it comes to setting the intensity of the charger. This issue arises when the type of profile sent is not compatible with the expected behavior, resulting in an error. In this article, we will delve into the details of the problem, examine the reproduction steps, and discuss the expected behavior. We will also explore potential solutions to this issue, including modifying the SetChargingProfile command and implementing a simpler message by changing the key instead of sending a SetChargingProfile.

Describe the Bug

The SetChargingProfile issue occurs when trying to change the intensity of the charger. The problem arises when the type of profile sent is not compatible with the expected behavior, resulting in an error. Specifically, when trying to change the maximum amperage value via the web interface, the system sends an error due to the type of profile sent.

To Reproduce

To reproduce this issue, follow these steps:

Try to change the maximum amperage value via the web interface.
Observe the error message that is displayed.

Expected Behavior

The expected behavior is that the system should send an "Absolute" profile instead of a "Relative" profile. Additionally, it would be simpler to send a message by changing the key instead of sending a SetChargingProfile.

Screenshots

The following screenshot illustrates the error message that is displayed when trying to change the maximum amperage value via the web interface.

Log Messages

The following log messages illustrate the error that occurs when trying to change the maximum amperage value via the web interface.

2025-03-09 20:11:37.829 INFO (MainThread) [ocpp] Plaza_1: send [2,"9706e144-0ceb-4349-8ed6-e83888e0d4c0","SetChargingProfile",{"connectorId":0,"csChargingProfiles":{"chargingProfileId":8,"stackLevel":1,"chargingProfileKind":"Relative","chargingProfilePurpose":"ChargePointMaxProfile","chargingSchedule":{"chargingRateUnit":"W","chargingSchedulePeriod":[{"startPeriod":0,"limit":22000}]}}}]
2025-03-09 20:11:38.087 INFO (MainThread) [ocpp] Plaza_1: receive message [4,"9706e144-0ceb-4349-8ed6-e83888e0d4c0","PropertyConstraintViolation","When chargingProfilePurpose =ChargingStationMaxProfile, chargingProfileKind SHALL NOT be Relative",{}]
2025-03-09 20:11:38.088 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140528426986384] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2794, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2837, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1007, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
        hass, entity, func, data, call.context
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1079, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/number/__init__.py", line 122, in async_set_value
    await entity.async_set_native_value(native_value)
  File "/config/custom_components/ocpp/number.py", line 131, in async_set_native_value
    resp = await self.central_system.set_max_charge_rate_amps(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        self.cpid, num_value
        ^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/config/custom_components/ocpp/api.py", line 345, in set_max_charge_rate_amps
    return await self.charge_points[cp_id].set_charge_rate(limit_amps=value)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/ocpp/ocppv16.py", line 323, in set_charge_rate
    resp = await self.call(req)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/ocpp/charge_point.py", line 421, in call
    response = await self._get_specific_response(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        call.unique_id, self._response_timeout
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/config/custom_components/ocpp/chargepoint.py", line 341, in _get_specific_response
    raise resp.to_exception()
ocpp.exceptions.PropertyConstraintViolationError: PropertyConstraintViolationError: When chargingProfilePurpose =ChargingStationMaxProfile, chargingProfileKind SHALL NOT be Relative,  {}`

Additional Context

When using the slider to select the maximum amperage, it would be best to send the following command.

action: ocpp.configure
metadata: {}
data:
  devid: number.plaza_120_maximum_current
  ocpp_key: MaxChargeCurrentLimit
  value: "16"
response_variable: OCPP_Response

This command would send a message by changing the key instead of sending a SetChargingProfile.

2025-03-09 20:43:59.891 INFO (MainThread) [ocpp] Plaza_1: send [2,"11d019a5-00de-4cf2-8048-dd1fddc6007c","GetConfiguration",{"key":["MaxChargeCurrentLimit"]}]
2025-03-09 20:44:01.661 INFO (MainThread) [ocpp] Plaza_1: receive message [3,"11d019a5-00de-4cf2-8048-dd1fddc6007c",{"configurationKey":[{"key":"MaxChargeCurrentLimit","readonly":false,"value":"16"}]}]

Potential Solutions

Based on the analysis of the problem, there are two potential solutions to this issue:

Modify the SetChargingProfile command: The first solution is to modify the SetChargingProfile command to send an "Absolute" profile instead of a "Relative" profile. This would require changes to the code that handles the SetChargingProfile command.
Implement a simpler message by changing the key: The second solution is to implement a simpler message by changing the key instead of sending a SetChargingProfile. This would require changes to the code that handles the GetConfiguration command.

Conclusion

The SetChargingProfile issue is a critical problem that affects the functionality of charging stations. By analyzing the problem, reproducing the issue, and examining the expected behavior, we have identified two potential solutions to this issue. These solutions involve modifying the SetChargingProfile command and implementing a simpler message by changing the key instead of sending a SetChargingProfile. By implementing these solutions, we can resolve the SetChargingProfile issue and ensure that the charging station functions correctly.

Future Work

Future work on this issue should focus on implementing the two potential solutions identified in this article. This will require changes to the code that handles the SetChargingProfile command and the GetConfiguration command. Additionally, testing and validation of the changes should be performed to ensure that the issue is resolved and the charging station functions correctly.

References

[1] OCPP 1.6 specification
[2] Home Assistant documentation
[3] Custom Components documentation

Note: The references provided are for informational purposes only and are not directly related to the issue at hand. However, they may be useful for further research and understanding of the topic.

Introduction

The SetChargingProfile issue is a critical problem that affects the functionality of charging stations. In our previous article, we examined the problem, reproduced the issue, and identified two potential solutions to this issue. In this article, we will provide a Q&A section to address common questions and concerns related to the SetChargingProfile issue.

Q&A

Q: What is the SetChargingProfile issue?

A: The SetChargingProfile issue is a critical problem that affects the functionality of charging stations. It occurs when trying to change the intensity of the charger, resulting in an error due to the type of profile sent.

Q: What are the reproduction steps for the SetChargingProfile issue?

A: To reproduce the SetChargingProfile issue, follow these steps:

Try to change the maximum amperage value via the web interface.
Observe the error message that is displayed.

Q: What is the expected behavior for the SetChargingProfile issue?

A: The expected behavior is that the system should send an "Absolute" profile instead of a "Relative" profile. Additionally, it would be simpler to send a message by changing the key instead of sending a SetChargingProfile.

Q: What are the potential solutions to the SetChargingProfile issue?

A: There are two potential solutions to the SetChargingProfile issue:

Modify the SetChargingProfile command: The first solution is to modify the SetChargingProfile command to send an "Absolute" profile instead of a "Relative" profile.
Implement a simpler message by changing the key: The second solution is to implement a simpler message by changing the key instead of sending a SetChargingProfile.

Q: How can I implement the potential solutions to the SetChargingProfile issue?

A: To implement the potential solutions, you will need to make changes to the code that handles the SetChargingProfile command and the GetConfiguration command. This may involve modifying the code to send an "Absolute" profile instead of a "Relative" profile, or implementing a simpler message by changing the key.

Q: What are the benefits of implementing the potential solutions to the SetChargingProfile issue?

A: Implementing the potential solutions to the SetChargingProfile issue will resolve the issue and ensure that the charging station functions correctly. This will also improve the overall user experience and reduce the likelihood of errors.

Q: What are the potential risks of implementing the potential solutions to the SetChargingProfile issue?

A: Implementing the potential solutions to the SetChargingProfile issue may require changes to the code, which can be complex and time-consuming. Additionally, there is a risk that the changes may introduce new errors or issues.

Q: How can I test and validate the changes to the code to ensure that the SetChargingProfile issue is resolved?

A: To test and validate the changes to the code, you can use a combination of manual testing and automated testing. This may involve testing the charging station with different scenarios and configurations to ensure that the issue is resolved.

Conclusion

The SetChargingProfile issue is a critical problem that affects the functionality of charging stations. By understanding the problem, reproducing the issue, and identifying potential solutions, we can resolve the issue and ensure that the charging station functions correctly. We hope that this Q&A article has provided valuable information and insights to help you address the SetChargingProfile issue.

Future Work

Future work on this issue should focus on implementing the potential solutions and testing and validating the changes to the code. This will ensure that the issue is resolved and the charging station functions correctly.

References

[1] OCPP 1.6 specification
[2] Home Assistant documentation
[3] Custom Components documentation

Note: The references provided are for informational purposes only and are not directly related to the issue at hand. However, they may be useful for further research and understanding of the topic.