ABB Terra current control? #474

michigoe11 · 2022-04-02T17:26:58Z

michigoe11
Apr 2, 2022

Hello,
I have the "ABB Terra AC TAC-W11-G5-R-0" Wallbox and I'm able to start and stop the charging by switching the "Charge_Control", but I would also like to control the current. I try to set a value for the "Maximum_Current", but it's ignored and stays at 16, no matter what I enter. I checked the debug log, but there are no entries created when I try to change the max current.

Any idea, why it doesn't work?
I installed your integration manually, by copying the contents of the "custom_components" folder to my home assistant instance, I'm not sure if that does matter.

I also tried to connect the Wallbox to the OCPP adapter of ioBroker. I was able to control the current there, so I'm sure, the Wallbox supports current control via OCPP.

lbbrhzn · 2022-04-02T18:33:16Z

lbbrhzn
Apr 2, 2022
Maintainer

Copying the contents of custom_components instead of using HACS should work fine.

Did you change the log level in your configuration.yaml file?
See https://home-assistant-ocpp.readthedocs.io/en/latest/debugging.html

0 replies

michigoe11 · 2022-04-02T19:24:26Z

michigoe11
Apr 2, 2022
Author

yes, i did.

this is the content of the log. i started charging, tried to change the max current three times and stopped the charging.

2022-04-02 21:00:17 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'ocpp_central_g2' to 'G2': ping=1.0 ms, pong=1.0 ms
2022-04-02 21:00:37 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'ocpp_central_g2' to 'G2': ping=3.0 ms, pong=1.0 ms
2022-04-02 21:00:57 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'ocpp_central_g2' to 'G2': ping=1.0 ms, pong=1.0 ms
2022-04-02 21:01:00 INFO (MainThread) [ocpp] G2: send [2,"8a85dc8d-8643-481b-9d5d-c5d315c33d51","GetConfiguration",{"key":["AuthorizeRemoteTxRequests"]}]
2022-04-02 21:01:00 INFO (MainThread) [ocpp] G2: receive message [3, "8a85dc8d-8643-481b-9d5d-c5d315c33d51", {"configurationKey": [{"key": "AuthorizeRemoteTxRequests", "readonly": false, "value": "false"}], "unknownKey": []}]
2022-04-02 21:01:00 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for AuthorizeRemoteTxRequests: false
2022-04-02 21:01:00 INFO (MainThread) [ocpp] G2: send [2,"394092ea-8f90-411d-ac18-7694c312f5b7","RemoteStartTransaction",{"idTag":"G2","connectorId":1}]
2022-04-02 21:01:01 INFO (MainThread) [ocpp] G2: receive message [3, "394092ea-8f90-411d-ac18-7694c312f5b7", {"status": "Accepted"}]
2022-04-02 21:01:01 INFO (MainThread) [ocpp] G2: receive message [2, "5548591", "StatusNotification", {"connectorId": 1, "errorCode": "NoError", "info": "null", "status": "SuspendedEV", "vendorErrorCode": "0x00"}]
2022-04-02 21:01:01 INFO (MainThread) [ocpp] G2: send [3,"5548591",{}]
2022-04-02 21:01:02 INFO (MainThread) [ocpp] G2: receive message [2, "8282826", "StatusNotification", {"connectorId": 1, "errorCode": "NoError", "info": "null", "status": "Charging", "vendorErrorCode": "0x00"}]
2022-04-02 21:01:02 INFO (MainThread) [ocpp] G2: send [3,"8282826",{}]
2022-04-02 21:01:03 INFO (MainThread) [ocpp] G2: receive message [2, "1538872", "StartTransaction", {"connectorId": 1, "idTag": "G2", "meterStart": 0, "timestamp": "2022-04-02T19:01:01.000Z"}]
2022-04-02 21:01:03 DEBUG (MainThread) [custom_components.ocpp] id_tag='G2' not found in auth_list, default authorization_status='Accepted'
2022-04-02 21:01:03 INFO (MainThread) [ocpp] G2: send [3,"1538872",{"transactionId":1648926063,"idTagInfo":{"status":"Accepted"}}]
2022-04-02 21:01:13 INFO (MainThread) [ocpp] G2: receive message [2, "7410878", "MeterValues", {"connectorId": 1, "transactionId": 1648926063, "meterValue": [{"timestamp": "2022-04-02T19:01:13.000Z", "sampledValue": [{"value": "237.10", "context": "Transaction.Begin", "format": "Raw", "measurand": "Voltage", "phase": "L1-N", "unit": "V"}, {"value": "15.54", "context": "Transaction.Begin", "format": "Raw", "measurand": "Current.Import", "phase": "L1", "unit": "A"}, {"value": "3657", "context": "Transaction.Begin", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L1", "unit": "W"}, {"value": "239.40", "context": "Transaction.Begin", "format": "Raw", "measurand": "Voltage", "phase": "L2-N", "unit": "V"}, {"value": "0.0", "context": "Transaction.Begin", "format": "Raw", "measurand": "Current.Import", "phase": "L2", "unit": "A"}, {"value": "0", "context": "Transaction.Begin", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L2", "unit": "W"}, {"value": "240.90", "context": "Transaction.Begin", "format": "Raw", "measurand": "Voltage", "phase": "L3-N", "unit": "V"}, {"value": "0.0", "context": "Transaction.Begin", "format": "Raw", "measurand": "Current.Import", "phase": "L3", "unit": "A"}, {"value": "0", "context": "Transaction.Begin", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L3", "unit": "W"}, {"value": "0", "context": "Transaction.Begin", "format": "Raw", "measurand": "Energy.Active.Import.Register", "unit": "Wh"}, {"value": "16", "context": "Transaction.Begin", "format": "Raw", "measurand": "Current.Offered", "unit": "A"}]}]}]
2022-04-02 21:01:13 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Voltage, phase_info: {'unit': 'V', 'L1-N': 237.1, 'L2-N': 239.4, 'L3-N': 240.9} value: 238.633333 unit :V
2022-04-02 21:01:13 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Current.Import, phase_info: {'unit': 'A', 'L1': 15.54, 'L2': 0.0, 'L3': 0.0} value: 15.540000 unit :A
2022-04-02 21:01:13 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Power.Active.Import, phase_info: {'unit': 'W', 'L1': 3657.0, 'L2': 0.0, 'L3': 0.0} value: 3657.000000 unit :W
2022-04-02 21:01:13 INFO (MainThread) [ocpp] G2: send [3,"7410878",{}]
2022-04-02 21:01:17 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'ocpp_central_g2' to 'G2': ping=1.0 ms, pong=1.0 ms
2022-04-02 21:01:37 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'ocpp_central_g2' to 'G2': ping=1.0 ms, pong=1.0 ms
2022-04-02 21:01:45 INFO (MainThread) [ocpp] G2: receive message [2, "3318596", "MeterValues", {"connectorId": 1, "transactionId": 1648926063, "meterValue": [{"timestamp": "2022-04-02T19:01:45.000Z", "sampledValue": [{"value": "236.90", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L1-N", "unit": "V"}, {"value": "15.63", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L1", "unit": "A"}, {"value": "3677", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L1", "unit": "W"}, {"value": "239.50", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L2-N", "unit": "V"}, {"value": "0.0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L2", "unit": "A"}, {"value": "0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L2", "unit": "W"}, {"value": "241.00", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L3-N", "unit": "V"}, {"value": "0.0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L3", "unit": "A"}, {"value": "0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L3", "unit": "W"}, {"value": "38", "context": "Sample.Periodic", "format": "Raw", "measurand": "Energy.Active.Import.Register", "unit": "Wh"}, {"value": "16", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Offered", "unit": "A"}]}]}]
2022-04-02 21:01:45 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Voltage, phase_info: {'unit': 'V', 'L1-N': 236.9, 'L2-N': 239.5, 'L3-N': 241.0} value: 238.633333 unit :V
2022-04-02 21:01:45 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Current.Import, phase_info: {'unit': 'A', 'L1': 15.63, 'L2': 0.0, 'L3': 0.0} value: 15.630000 unit :A
2022-04-02 21:01:45 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Power.Active.Import, phase_info: {'unit': 'W', 'L1': 3677.0, 'L2': 0.0, 'L3': 0.0} value: 3677.000000 unit :W
2022-04-02 21:01:45 INFO (MainThread) [ocpp] G2: send [3,"3318596",{}]
2022-04-02 21:01:57 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'ocpp_central_g2' to 'G2': ping=1.0 ms, pong=2.0 ms
2022-04-02 21:02:00 INFO (MainThread) [ocpp] G2: send [2,"e8f3d954-b072-4243-a3e9-94055fcfb25a","RemoteStopTransaction",{"transactionId":1648926063}]
2022-04-02 21:02:00 INFO (MainThread) [ocpp] G2: receive message [3, "e8f3d954-b072-4243-a3e9-94055fcfb25a", {"status": "Accepted"}]
2022-04-02 21:02:01 INFO (MainThread) [ocpp] G2: receive message [2, "3314344", "StatusNotification", {"connectorId": 1, "errorCode": "NoError", "info": "null", "status": "SuspendedEV", "vendorErrorCode": "0x00"}]
2022-04-02 21:02:01 INFO (MainThread) [ocpp] G2: send [3,"3314344",{}]
2022-04-02 21:02:04 INFO (MainThread) [ocpp] G2: receive message [2, "1276208", "StatusNotification", {"connectorId": 1, "errorCode": "NoError", "info": "null", "status": "Finishing", "vendorErrorCode": "0x00"}]
2022-04-02 21:02:04 INFO (MainThread) [ocpp] G2: send [3,"1276208",{}]
2022-04-02 21:02:05 INFO (MainThread) [ocpp] G2: receive message [2, "9736208", "StopTransaction", {"meterStop": 56, "idTag": "G2", "timestamp": "2022-04-02T19:02:00.000Z", "transactionId": 1648926063, "reason": "Remote"}]
2022-04-02 21:02:05 INFO (MainThread) [ocpp] G2: send [3,"9736208",{"idTagInfo":{"status":"Accepted"}}]

This is shown in the "Features" list: Profiles.AUTH|REM|FW|CORE
I wonder why smart charging isn't listed there, because afaik it's necessary for current control.

3 replies

lbbrhzn Apr 2, 2022
Maintainer

Then I think that explains it. If the Smart Changing feature is missing, the integration will not set the max current.

lbbrhzn Apr 2, 2022
Maintainer

If you're feeling adventurous you can try to remove the check for the smart charging profile in your code.
In the file api.py, line 542, change:

if prof.SMART in self._attr_supported_features:

to

if prof.CORE in self._attr_supported_features:

michigoe11 Apr 2, 2022
Author

well, in the meanwhile I figured out to skip the check by adding "self._attr_supported_features |= prof.SMART" outside the if statement in line 481
and I got {"status": "Rejected"} as answer.

and by checking the log, smart charging is indeed not in the featureset:

2022-04-02 12:17:25 INFO (MainThread) [ocpp] G2: receive message [3, "e9d80677-d40c-458c-8165-873b39a49b7a", {"configurationKey": [{"key": "SupportedFeatureProfiles", "readonly": true, "value": "Core,FirmwareManagement,LocalAuthListManagement,RemoteTrigger"}], "unknownKey": []}]
2022-04-02 12:17:25 INFO (MainThread) [custom_components.ocpp] Supported feature profiles: Core,FirmwareManagement,LocalAuthListManagement,RemoteTrigger

But then I wonder how the OCPP adapter of ioBroker do that, because it works there.
And the manufacturer recomends the software EisBär for load management and that also is using OCPP.
So somehow it must be possible.
When I have the opportunity, I will try ioBroker again and try to figure out, what they do differently.

lbbrhzn · 2022-04-02T20:53:02Z

lbbrhzn
Apr 2, 2022
Maintainer

There may be a configuration setting for it. My Wallbox has that. You can get a list of all configuration settings by calling the ocpp.get_configuration service with an empty key and checking your log.

service: ocpp.get_configuration
data:
  ocpp_key: ""

0 replies

michigoe11 · 2022-04-02T21:53:42Z

michigoe11
Apr 2, 2022
Author

I got it to work! :)

but step by step...

I called "ocpp.get_configuration" as you recommended
this was the answer:
{"configurationKey": [{"key": "GetConfigurationMaxKeys", "readonly": true, "value": "20"}, {"key": "HeartbeatInterval", "readonly": false, "value": "3600"}, {"key": "MeterValueSampleInterval", "readonly": false, "value": "30"}, {"key": "AuthorizationKey", "readonly": false}, {"key": "LocalAuthorizeOffline", "readonly": false, "value": "true"}, {"key": "LocalPreAuthorize", "readonly": false, "value": "false"}, {"key": "LocalAuthListEnabled", "readonly": false, "value": "true"}, {"key": "LocalAuthListMaxLength", "readonly": true, "value": "16"}, {"key": "SendLocalListMaxLength", "readonly": true, "value": "8"}, {"key": "SupportedFeatureProfiles", "readonly": true, "value": "Core,FirmwareManagement,LocalAuthListManagement,RemoteTrigger"}, {"key": "ChargeProfileMaxStackLevel", "readonly": true, "value": "1"}, {"key": "ChargingScheduleAllowedChargingRateUnit", "readonly": true, "value": "Current,Power"}, {"key": "ChargingScheduleMaxPeriods", "readonly": true, "value": "3"}, {"key": "MaxChargingProfilesInstalled", "readonly": true, "value": "2"}, {"key": "NumberOfConnectors", "readonly": true, "value": "1"}, {"key": "AllowOfflineTxForUnknownId", "readonly": false, "value": "false"}, {"key": "AuthorizeRemoteTxRequests", "readonly": false, "value": "false"}, {"key": "ConnectionTimeOut", "readonly": false, "value": "120"}, {"key": "WebSocketPingInterval", "readonly": false, "value": "60"}, {"key": "FreeVendEnabled", "readonly": false, "value": "false"}, {"key": "MeterValuesAlignedData", "readonly": false, "value": "Energy.Active.Import.Register"}, {"key": "MeterValuesAlignedDataMaxLength", "readonly": true, "value": "4"}, {"key": "ClockAlignedDataInterval", "readonly": false, "value": "300"}]}

it looks very strange to me, that it has options like "ChargingScheduleAllowedChargingRateUnit" and "ChargingScheduleMaxPeriods", although smart charging isn't in the "SupportedFeatureProfiles".

as I said, it works in ioBroker. so I configured the Charging Profile in your api.py (line 563) exactly the same way, as it is in the ioBroker adapter.
so it's now:

cs_charging_profiles={
	om.charging_profile_id.value: 1,
	om.stack_level.value: 0,
	om.charging_profile_purpose.value: "TxDefaultProfile",
	om.charging_profile_kind.value: "Recurring",
	om.recurrency_kind.value: "Daily",
	om.charging_schedule.value: {
		om.duration.value: 86400,
		om.start_schedule.value: "2013-01-01T00:00Z",
		om.charging_rate_unit.value: "A",
		om.charging_schedule_period.value: [
			{om.start_period.value: 0, om.limit.value: lim}
		],
	},
},

and it works:

2022-04-02 23:19:46 INFO (MainThread) [ocpp] G2: send [2,"ccd7bb2f-4408-4b13-9490-1508aec953e6","SetChargingProfile",{"connectorId":0,"csChargingProfiles":{"chargingProfileId":1,"stackLevel":0,"chargingProfilePurpose":"TxDefaultProfile","chargingProfileKind":"Recurring","recurrencyKind":"Daily","chargingSchedule":{"duration":86400,"startSchedule":"2013-01-01T00:00Z","chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":12.0}]}}}]
2022-04-02 23:19:46 INFO (MainThread) [ocpp] G2: receive message [3, "ccd7bb2f-4408-4b13-9490-1508aec953e6", {"status": "Accepted"}]

this was the rejection with the original profile in your api.py:

2022-04-02 22:03:31 INFO (MainThread) [ocpp] G2: send [2,"81c639a2-9d68-4b0f-b635-dea2c18b408f","SetChargingProfile",{"connectorId":0,"csChargingProfiles":{"chargingProfileId":8,"stackLevel":1,"chargingProfileKind":"Relative","chargingProfilePurpose":"ChargePointMaxProfile","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":14.0}]}}}]
2022-04-02 22:03:31 INFO (MainThread) [ocpp] G2: receive message [3, "81c639a2-9d68-4b0f-b635-dea2c18b408f", {"status": "Rejected"}]

Link to ioBroker adapter charging profile (Line 447):
https://github.com/foxriver76/ioBroker.ocpp/blob/c4de275ee13ebfe4c1385bd7f0a91a649653e74a/src/main.ts#L447

7 replies

michigoe11 Apr 3, 2022
Author

with the original line om.stack_level.value: stack_level, I can see in the log, that stack_level is 1. you can see it in my previous log with timestamp 2022-04-02 22:03:31

but I also just tried om.stack_level.value: 1 and got rejected:

2022-04-03 11:14:11 INFO (MainThread) [ocpp] G2: send [2,"0c2097b4-3eb5-4ec6-9fa3-56b68fcc3110","SetChargingProfile",{"connectorId":0,"csChargingProfiles":{"chargingProfileId":8,"stackLevel":1,"chargingProfileKind":"Relative","chargingProfilePurpose":"TxDefaultProfile","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":12.0}]}}}]
2022-04-03 11:14:11 INFO (MainThread) [ocpp] G2: receive message [3, "0c2097b4-3eb5-4ec6-9fa3-56b68fcc3110", {"status": "Rejected"}]

Matze4711 Apr 15, 2022

Hi @michigoe11 ,
have you tested with current version?
I cannot bring it to work.
Could you please explain what exactly you changed in the Code?

thanks a lot for the Support!

michigoe11 Apr 15, 2022
Author

Hi @Matze4711,
I have the version 0.4.28, but I think it should be still the same.

assuming you installed the integration manually, you can edit the "api.py"

before line 486, i added self._attr_supported_features |= prof.SMART, so it looks like this:

self._attr_supported_features |= prof.SMART
for item in feature_list:
	if item == om.feature_profile_core.value:
		self._attr_supported_features |= prof.CORE
	elif item == om.feature_profile_firmware.value:
		self._attr_supported_features |= prof.FW
	elif item == om.feature_profile_smart.value:
		self._attr_supported_features |= prof.SMART
	elif item == om.feature_profile_reservation.value:
		self._attr_supported_features |= prof.RES
	elif item == om.feature_profile_remote.value:
		self._attr_supported_features |= prof.REM
	elif item == om.feature_profile_auth.value:
		self._attr_supported_features |= prof.AUTH

that makes sure, that the if statement in line 552 will be executed.
i forced there the stack_level to 0, by set line 575 to om.stack_level.value: 0, so it looks like this:

req = call.SetChargingProfilePayload(
	connector_id=0,
	cs_charging_profiles={
		om.charging_profile_id.value: 8,
		om.stack_level.value: 0,
		om.charging_profile_kind.value: ChargingProfileKindType.relative.value,
		om.charging_profile_purpose.value: ChargingProfilePurposeType.charge_point_max_profile.value,
		om.charging_schedule.value: {
			om.charging_rate_unit.value: units,
			om.charging_schedule_period.value: [
				{om.start_period.value: 0, om.limit.value: lim}
			],
		},
	},
)

that should make it work.
(I referred to the current version of api.py on github for all line numbers.)

after my thread here, the developers adapted line 601 in the latest version, but i doubt that this line will be executed, because our Wallbox doesn't report the Smart Charging feature in the featurelist, so from my understanding, the whole function will be canceled already in line 588 with "return False".

drc38 Apr 15, 2022
Collaborator

V0.4.29 should mean you do not need to make the second edit ie om.stack_level.value: 0

drc38 Apr 15, 2022
Collaborator

@lbbrhzn how about adding an override in the config flow to select Supported Features eg auto vs tick box list?

AlexC1986 · 2022-08-20T21:20:18Z

AlexC1986
Aug 20, 2022

Hi everyone,

I`ve read through all your suggestions regarding the use of the ABB Terra, but I´m still struggling in setting the max current for a smart charge control via a script.
Based on my PV power generation and our consumption in the house, I´m calculating the power overflow and from here the max current I would like to send to the car. How do I address the max current in a script? With lots of other integrations I use Modbus and Rest APIs and have implemented the sensors into the configurations.yaml by myself, so I know how to address them. But with the ABB wallbox and OCPP I´m struggling.

Thanks in advance for your help!

2 replies

drc38 Aug 20, 2022
Collaborator

Have you looked at suggestions in #534

AlexC1986 Aug 21, 2022

Thank you very much, I must have missed this! My automation is working now, I just need to get out the "power_consumption" of my ABB now that the current control is not running ouf control when the charger starts to pump the power into my EV.

AlexC1986 · 2022-08-22T19:21:54Z

AlexC1986
Aug 22, 2022

I got the automations working but after rebooting HASS, even if my ABB Terra is online and the standard integrated "ABBTerra_availability" switch is active, I get an error message that there seems to be an issue with calling the service "number.set_value" and the logger says the following:

Logger: homeassistant.core
Source: custom_components/ocpp/api.py:593
Integration: Open Charge Point Protocol (OCPP) (documentation, issues)
First occurred: 21:07:41 (2 occurrences)
Last logged: 21:15:31

Error executing service: <ServiceCall number.set_value (c:01GB3F76SJX5ZJ1X26Z9PP7CCW): value=0.0, entity_id=['number.abbrechts_maximum_current']>
Error executing service: <ServiceCall number.set_value (c:01GB3FNHS134YH1XSEW26TRP61): value=0.0, entity_id=['number.abbrechts_maximum_current']>
Traceback (most recent call last):
File "/usr/local/lib/python3.10/asyncio/queues.py", line 159, in get
await getter
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 456, in wait_for
return fut.result()
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/ocpp/charge_point.py", line 274, in call
await self._get_specific_response(call.unique_id,
File "/config/custom_components/ocpp/api.py", line 845, in _get_specific_response
resp = await super()._get_specific_response(unique_id, timeout)
File "/usr/local/lib/python3.10/site-packages/ocpp/charge_point.py", line 307, in _get_specific_response
response = await asyncio.wait_for(self._response_queue.get(),
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 458, in wait_for
raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/core.py", line 1731, in catch_exceptions
await coro_or_task
File "/usr/src/homeassistant/homeassistant/core.py", line 1750, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
await service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 676, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 930, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 713, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/number/init.py", line 111, in async_set_value
await entity.async_set_native_value(native_value)
File "/config/custom_components/ocpp/number.py", line 127, in async_set_native_value
resp = await self.central_system.set_max_charge_rate_amps(
File "/config/custom_components/ocpp/api.py", line 269, in set_max_charge_rate_amps
return await self.charge_points[cp_id].set_charge_rate(limit_amps=value)
File "/config/custom_components/ocpp/api.py", line 593, in set_charge_rate
resp = await self.call(req)
File "/usr/local/lib/python3.10/site-packages/ocpp/charge_point.py", line 277, in call
raise asyncio.TimeoutError(
asyncio.exceptions.TimeoutError: Waited 30s for response on [2,"6c2488db-8d48-4bdc-9153-8b9bbf9aef8f","SetChargingProfile",{"connectorId":0,"csChargingProfiles":{"chargingProfileId":8,"stackLevel":3,"chargingProfileKind":"Relative","chargingProfilePurpose":"ChargePointMaxProfile","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":0.0}]}}}].

1 reply

drc38 Aug 22, 2022
Collaborator

A timeout error suggests the charger is not communicating, could be a network issue. Have you also rebooted the charger?

janrothkegel · 2022-11-06T18:21:54Z

janrothkegel
Nov 6, 2022

Hi,

thanks for sharing all this. I was also able to basically make current control work with my ABB . However, I am not able to obtain a total charging current of greater than 15A.

I tried it with 6A (per phase) giving 11.99A:

2022-11-06 18:50:25.431 INFO (MainThread) [ocpp] TACW1142721G2132: send [2,"b3f82a15-2057-4513-88e6-c54988a2d8ba","SetChargingProfile",{"connectorId":0,"csChargingProfiles":{"chargingProfileId":8,"stackLevel":0,"chargingProfileKind":"Relative","chargingProfilePurpose":"ChargePointMaxProfile","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":6.0}]}}}]
2022-11-06 18:50:26.229 INFO (MainThread) [ocpp] TACW1142721G2132: receive message [3, "b3f82a15-2057-4513-88e6-c54988a2d8ba", {"status": "Accepted"}]

2022-11-06 18:51:27.678 INFO (MainThread) [ocpp] TACW1142721G2132: receive message [2, "0513145", "MeterValues", {"connectorId": 1, "transactionId": 1667754697, "meterValue": [{"timestamp": "2022-11-06T17:51:26.000Z", "sampledValue": [{"value": "226.60", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L1-N", "unit": "V"}, {"value": "5.99", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L1", "unit": "A"}, {"value": "1342", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L1", "unit": "W"}, {"value": "226.70", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L2-N", "unit": "V"}, {"value": "6.0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L2", "unit": "A"}, {"value": "1346", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L2", "unit": "W"}, {"value": "228.50", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L3-N", "unit": "V"}, {"value": "0.0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L3", "unit": "A"}, {"value": "0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L3", "unit": "W"}, {"value": "2079", "context": "Sample.Periodic", "format": "Raw", "measurand": "Energy.Active.Import.Register", "unit": "Wh"}, {"value": "16", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Offered", "unit": "A"}]}]}]
2022-11-06 18:51:27.691 WARNING (MainThread) [custom_components.ocpp] Unknown transaction detected with id=1667754697
2022-11-06 18:51:27.693 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Voltage, phase_info: {'unit': 'V', 'L1-N': 226.6, 'L2-N': 226.7, 'L3-N': 228.5} value: 226.666667 unit :V
2022-11-06 18:51:27.694 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Current.Import, phase_info: {'unit': 'A', 'L1': 5.99, 'L2': 6.0, 'L3': 0.0} value: **11.990000** unit :A
2022-11-06 18:51:27.694 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Power.Active.Import, phase_info: {'unit': 'W', 'L1': 1342.0, 'L2': 1346.0, 'L3': 0.0} value: 2688.000000 unit :W

I tried it with 8A giving a total of 15A:

{"chargingProfileId":8,"stackLevel":0,"chargingProfileKind":"Relative","chargingProfilePurpose":"ChargePointMaxProfile","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":8.0}]}}}]
2022-11-06 18:55:07.976 INFO (MainThread) [ocpp] TACW1142721G2132: receive message [3, "9c363b16-d0b3-46a2-906c-e647f3a9613f", {"status": "Accepted"}]

2022-11-06 18:55:43.466 INFO (MainThread) [ocpp] TACW1142721G2132: receive message [2, "6010784", "MeterValues", {"connectorId": 1, "transactionId": 1667754697, "meterValue": [{"timestamp": "2022-11-06T17:55:42.000Z", "sampledValue": [{"value": "226.10", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L1-N", "unit": "V"}, {"value": "7.48", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L1", "unit": "A"}, {"value": "1677", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L1", "unit": "W"}, {"value": "227.50", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L2-N", "unit": "V"}, {"value": "7.52", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L2", "unit": "A"}, {"value": "1697", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L2", "unit": "W"}, {"value": "229.50", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L3-N", "unit": "V"}, {"value": "0.0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L3", "unit": "A"}, {"value": "0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L3", "unit": "W"}, {"value": "2296", "context": "Sample.Periodic", "format": "Raw", "measurand": "Energy.Active.Import.Register", "unit": "Wh"}, {"value": "16", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Offered", "unit": "A"}]}]}]
2022-11-06 18:55:43.480 WARNING (MainThread) [custom_components.ocpp] Unknown transaction detected with id=1667754697
2022-11-06 18:55:43.483 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Voltage, phase_info: {'unit': 'V', 'L1-N': 226.1, 'L2-N': 227.5, 'L3-N': 229.5} value: 227.033333 unit :V
2022-11-06 18:55:43.484 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Current.Import, phase_info: {'unit': 'A', 'L1': 7.48, 'L2': 7.52, 'L3': 0.0} value: **15.000000** unit :A
2022-11-06 18:55:43.484 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Power.Active.Import, phase_info: {'unit': 'W', 'L1': 1677.0, 'L2': 1697.0, 'L3': 0.0} value: 3374.000000 unit :W

And finally I tried also 10A giving a total of 15A as well:

2022-11-06 18:53:18.030 INFO (MainThread) [ocpp] TACW1142721G2132: send [2,"2bd8b5c1-d1a5-4882-8d6b-fcd92d87d23f","SetChargingProfile",{"connectorId":0,"csChargingProfiles":{"chargingProfileId":8,"stackLevel":0,"chargingProfileKind":"Relative","chargingProfilePurpose":"ChargePointMaxProfile","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":10.0}]}}}]
2022-11-06 18:53:18.832 INFO (MainThread) [ocpp] TACW1142721G2132: receive message [3, "2bd8b5c1-d1a5-4882-8d6b-fcd92d87d23f", {"status": "Accepted"}]

2022-11-06 18:53:35.568 INFO (MainThread) [ocpp] TACW1142721G2132: receive message [2, "9934583", "MeterValues", {"connectorId": 1, "transactionId": 1667754697, "meterValue": [{"timestamp": "2022-11-06T17:53:34.000Z", "sampledValue": [{"value": "225.80", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L1-N", "unit": "V"}, {"value": "7.48", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L1", "unit": "A"}, {"value": "1675", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L1", "unit": "W"}, {"value": "226.50", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L2-N", "unit": "V"}, {"value": "7.52", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L2", "unit": "A"}, {"value": "1690", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L2", "unit": "W"}, {"value": "229.30", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L3-N", "unit": "V"}, {"value": "0.0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L3", "unit": "A"}, {"value": "0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L3", "unit": "W"}, {"value": "2176", "context": "Sample.Periodic", "format": "Raw", "measurand": "Energy.Active.Import.Register", "unit": "Wh"}, {"value": "16", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Offered", "unit": "A"}]}]}]
2022-11-06 18:53:35.583 WARNING (MainThread) [custom_components.ocpp] Unknown transaction detected with id=1667754697
2022-11-06 18:53:35.585 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Voltage, phase_info: {'unit': 'V', 'L1-N': 225.8, 'L2-N': 226.5, 'L3-N': 229.3} value: 226.266667 unit :V
2022-11-06 18:53:35.586 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Current.Import, phase_info: {'unit': 'A', 'L1': 7.48, 'L2': 7.52, 'L3': 0.0} value: **15.000000** unit :A
2022-11-06 18:53:35.586 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Power.Active.Import, phase_info: {'unit': 'W', 'L1': 1675.0, 'L2': 1690.0, 'L3': 0.0} value: 3365.000000 unit :W

Anyone experienced this before?

Thanks
Jan

4 replies

drc38 Nov 6, 2022
Collaborator

What is the power capacity of the car's inverter?

janrothkegel Nov 6, 2022

Fixed, although I don't understand why it works. I changed the stack level to 1 (maybe even the value would have turned out by the default calculation of ocpp integration). Now I get an error and afterwards the try with TxDefaultProfile succeeds.

2022-11-06 19:34:18.384 INFO (MainThread) [ocpp] TACW1142721G2132: send [2,"c33158aa-0858-4826-87c6-b255196ed4aa","SetChargingProfile",{"connectorId":0,"csChargingProfiles":{"chargingProfileId":1,"stackLevel":1,"chargingProfileKind":"Relative","chargingProfilePurpose":"ChargePointMaxProfile","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":16.0}]}}}]
2022-11-06 19:34:19.179 INFO (MainThread) [ocpp] TACW1142721G2132: receive message [3, "c33158aa-0858-4826-87c6-b255196ed4aa", {"status": "Rejected"}]
2022-11-06 19:34:19.181 DEBUG (MainThread) [custom_components.ocpp] ChargePointMaxProfile is not supported by this charger, trying TxDefaultProfile instead...
2022-11-06 19:34:19.184 INFO (MainThread) [ocpp] TACW1142721G2132: send [2,"411aaf4f-5e78-42bd-9064-eac32fa852de","SetChargingProfile",{"connectorId":0,"csChargingProfiles":{"chargingProfileId":8,"stackLevel":0,"chargingProfileKind":"Relative","chargingProfilePurpose":"TxDefaultProfile","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":16.0}]}}}]
2022-11-06 19:34:19.985 INFO (MainThread) [ocpp] TACW1142721G2132: receive message [3, "411aaf4f-5e78-42bd-9064-eac32fa852de", {"status": "Accepted"}]

This gives the required current:

2022-11-06 19:34:53.866 INFO (MainThread) [ocpp] TACW1142721G2132: receive message [2, "9844534", "MeterValues", {"connectorId": 1, "transactionId": 1667759369, "meterValue": [{"timestamp": "2022-11-06T18:34:52.000Z", "sampledValue": [{"value": "224.50", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L1-N", "unit": "V"}, {"value": "14.51", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L1", "unit": "A"}, {"value": "3243", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L1", "unit": "W"}, {"value": "225.60", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L2-N", "unit": "V"}, {"value": "14.57", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L2", "unit": "A"}, {"value": "3270", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L2", "unit": "W"}, {"value": "230.30", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L3-N", "unit": "V"}, {"value": "0.0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L3", "unit": "A"}, {"value": "0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L3", "unit": "W"}, {"value": "635", "context": "Sample.Periodic", "format": "Raw", "measurand": "Energy.Active.Import.Register", "unit": "Wh"}, {"value": "15", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Offered", "unit": "A"}]}]}]
2022-11-06 19:34:53.880 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Voltage, phase_info: {'unit': 'V', 'L1-N': 224.5, 'L2-N': 225.6, 'L3-N': 230.3} value: 225.233333 unit :V
2022-11-06 19:34:53.880 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Current.Import, phase_info: {'unit': 'A', 'L1': 14.51, 'L2': 14.57, 'L3': 0.0} value: 29.080000 unit :A
2022-11-06 19:34:53.880 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Power.Active.Import, phase_info: {'unit': 'W', 'L1': 3243.0, 'L2': 3270.0, 'L3': 0.0} value: 6513.000000 unit :W

drc38 Nov 6, 2022
Collaborator

It may be unrelated if your car was limiting the charge rate for some reason, otherwise it's rather odd.

janrothkegel Nov 6, 2022

No, the car is not limiting anything. It worked with the ABB ChargerSync app before. However, I was not able to set the current higher than 8A per phase in the app anymore.
I think I figured out what happened. According to the ABB OCPP specification there shall be 3 stack levels. The configuration of the higher levels 'overrules' the lower ones. When I experimented with the OCPP integration and manually modified the stack level, I might have set the values at stack level 1. No I changed it back. But I was not able to start and stop charging at stack level 1. So I switched back to stack level 0. Now I am able to switch charging on and off as well as setting the current to all valid values ;-)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ABB Terra current control? #474

{{title}}

Replies: 7 comments 17 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

ABB Terra current control? #474

Replies: 7 comments · 17 replies

lbbrhzn Apr 2, 2022 Maintainer

michigoe11 Apr 2, 2022 Author

lbbrhzn Apr 2, 2022 Maintainer

lbbrhzn Apr 2, 2022 Maintainer

michigoe11 Apr 2, 2022 Author

lbbrhzn Apr 2, 2022 Maintainer

michigoe11 Apr 2, 2022 Author

michigoe11 Apr 3, 2022 Author

michigoe11 Apr 15, 2022 Author

drc38 Apr 15, 2022 Collaborator

drc38 Apr 15, 2022 Collaborator

drc38 Aug 20, 2022 Collaborator

drc38 Aug 22, 2022 Collaborator

drc38 Nov 6, 2022 Collaborator

drc38 Nov 6, 2022 Collaborator

Replies: 7 comments 17 replies

lbbrhzn
Apr 2, 2022
Maintainer

michigoe11
Apr 2, 2022
Author

lbbrhzn Apr 2, 2022
Maintainer

lbbrhzn Apr 2, 2022
Maintainer

michigoe11 Apr 2, 2022
Author

lbbrhzn
Apr 2, 2022
Maintainer

michigoe11
Apr 2, 2022
Author

michigoe11 Apr 3, 2022
Author

michigoe11 Apr 15, 2022
Author

drc38 Apr 15, 2022
Collaborator

drc38 Apr 15, 2022
Collaborator

drc38 Aug 20, 2022
Collaborator

drc38 Aug 22, 2022
Collaborator

drc38 Nov 6, 2022
Collaborator

drc38 Nov 6, 2022
Collaborator