Chargers from Charge Amps and their claimed OCPP 1.6J support

[tuomaz]

Hi
Has anyone tried the claimed support of OCPP 1.6J of these chargers?

https://www.chargeamps.com/product/charge-amps-aura/
https://www.chargeamps.com/product/charge-amps-dawn/

[tuomaz]

I now have a Charge Amps Dawn installed. It connects and I see traffic between the charger and HA / OCCP. I will continue to test and see what works and not.

[tuomaz]

Example data, no charge ongoing (redacted som ID's?)
homeassistant | 2023-06-06 21:11:47.813 INFO (MainThread) [ocpp] XXX: receive message [2,"YYY","MeterValues",{"connectorId":1,"meterValue":[{"timestamp":"2023-06-06T19:11:47Z","sampledValue":[{"value":"75170","context":"Sample.Periodic","measurand":"Energy.Active.Import.Register","unit":"Wh"},{"value":"13.00","context":"Sample.Periodic","measurand":"Current.Offered","unit":"A"},{"value":"0.000","context":"Sample.Periodic","measurand":"Current.Import","phase":"L1","unit":"A"},{"value":"0.000","context":"Sample.Periodic","measurand":"Current.Import","phase":"L2","unit":"A"},{"value":"0.000","context":"Sample.Periodic","measurand":"Current.Import","phase":"L3","unit":"A"},{"value":"0.00","context":"Sample.Periodic","measurand":"Voltage","phase":"L1","unit":"V"},{"value":"0.00","context":"Sample.Periodic","measurand":"Voltage","phase":"L2","unit":"V"},{"value":"0.00","context":"Sample.Periodic","measurand":"Voltage","phase":"L3","unit":"V"}]}]}]

[Bryneholt]

Have you been able to start the charging with this integration?
im able to get some information, but unable to actually start the charging.

2023-08-20 15:48:39.039 INFO (MainThread) [ocpp] xxxx: send [2,"xxx-446d-4a7b-a340-a81420eef280","RemoteStartTransaction",{"idTag":"xxxx","connectorId":1}]
2023-08-20 15:48:39.056 INFO (MainThread) [ocpp] xxxx: receive message [3,"xxx-446d-4a7b-a340-a81420eef280",{"status":"Accepted"}]

but nothing does happen,
From the car point of view, the charger says "paused"

edit:

Because I had enabled RFID to charge, while using the Charge amps app, the charger still requires this.
Ie, I can only start it with the RFID tag.

[tuomaz]

I cannot stop the charging from Home Assistant. When I try to stop the charge with the "Charging control" switch, it immediately goes back to the on state. Does this work for you?

[Bryneholt]

Hello, I’ve used the workaround and created automations setting the current to 0 when to stop charging, and to 16A when to start the charging.

This works.

`alias: EV Smart Charging - Start
description: ""
trigger:

• platform: state
  entity_id:
  • sensor.smartcharger_charging
    from: "off"
    to: "on"
    condition: []
    action:
• service: number.set_value
  data:
  value: "16"
  target:
  entity_id: number.charger_maximum_current
  mode: single
  `

[Bryneholt]

And to stop

alias: EV Smart Charging - Stop
description: ""
trigger:

• platform: state
  entity_id:
  • sensor.smartcharger_charging
    from: "on"
    to: "off"
    condition: []
    action:
• service: number.set_value
  target:
  entity_id: number.charger_maximum_current
  data:
  value: "0"
  mode: single

[Miggle007]

I have the Charge Amps Aura. I am able to connect and to charge to connectorId 1 only. I am not able to use the full functionality using this OCPP instance and also, as mentioned above, not all sensors are processing the right information. I have asked Charge Amps for an API plugging into their cloud service as a workaround.

[pelleL21]

I have a Charge Amps Halo. How did you guys get the OCPP to work? I have put the adress ws://homeassistant.local:9000 in the Halo charger, but it doesen't connect to the OCPP server.

[ClarreJu]

Firmware: 184

[HenrikBurton]

Ok, that's the most resent version from feb 2025 according to the release note. Perhaps I should reconsider buying the Halo. Thanks!

[ClarreJu]

The reason I get Unavailable is because the Halo crashes every time. I have to restart it by flipping of the fuses. Not so good. I give up and go back to the cloud.

[nymeron]

any follow ups on Halo integration to HA?
Do I understand correctly, that you can either have the charger connected to their cloud or HA, but not both?

[HenrikBurton]

Correct, You can't have both.

I'm on version 189 and that works fine.

[Miggle007]

Just an extra thought:
I am using the ChargeAmps repo, also available via HACS: https://github.com/kirei/hass-chargeamps.

The advantage of using this is that the native cloud and app integeation still functions. Furthermore, I had some issues with my Chargeamps Aura and the connectorIDs (dual socket), which is not an issue with the Halo obviously.

This OCPP integration was too high maintenance for me.

[htukiain]

Is your Chargeamps upgraded to OCPP? I can remotely start charging from HA, but ending and restarting does not work from HA. All works fine from the ChargeAmpps app.

It seems that on/off and start / end charge might be different commands?

[nymeron]

can this integration be used to dynamically set current using set_max_current during the charging session?

[htukiain]

it can be used. Below is my HA-YAML for that (use only as reference / example)

alias: EV - Dynamic load balancer (stable)
description: >
Uses Shelly EM3 phase currents and last commanded EV current to keep main fuse
below limit. Requires input_number.ev_charger_setpoint.
triggers:

• trigger: time_pattern
  seconds: /30
  conditions:
• condition: state
  entity_id: binary_sensor.ev_charging_real
  state: "on"
• condition: state
  entity_id: timer.charger_cooldown
  state: idle
  actions:
• action: logbook.log
  data:
  name: EV-load-balancer
  message: >
  Tick │ ia {{ ia }} A, ib {{ ib }} A, ic {{ ic }} A │ max_phase {{
  max_phase }} A │ house_load {{ house_load }} A │ headroom_after_off {{
  headroom_after_off }} A │ ev_setpoint {{ ev_setpoint }} A → allowed_now
  {{ allowed_now }} A → target {{ target_amps }} A
• choose:
  • conditions:
    • condition: template
      value_template: "{{ allowed_now|int == 0 and ev_setpoint|float(0) > 0 }}"
      sequence:
    • action: automation.trigger
      data:
      entity_id: automation.charge_amps_stop
    • action: timer.start
      target:
      entity_id: timer.charger_cooldown
    • action: logbook.log
      data:
      name: EV-load-balancer
      message: >
      Headroom after off {{ headroom_after_off }} A too low for even
      {{ min_allowed }} A + {{ safety_margin }} A margin → charger
      disabled, cooldown 15 min started.
  • conditions:
    • condition: template
      value_template: "{{ target_amps|int != current_limit|int and target_amps|int > 0 }}"
      sequence:
    • delay: "00:00:02"
    • action: chargeamps.set_max_current
      data:
      chargepoint: 2409085367M
      connector: 1
      max_current: "{{ target_amps|int }}"
    • action: logbook.log
      data:
      name: EV-load-balancer
      message: >
      Set charger to {{ target_amps }} A (phase load A/B/C: {{ ia
      }}/{{ ib }}/{{ ic }} A)
      default: []
• action: input_number.set_value
  target:
  entity_id: input_number.ev_charger_setpoint
  data:
  value: "{{ target_amps|int }}"
• action: logbook.log
  data:
  name: EV-load-balancer
  message: >
  Stored EV setpoint {{ target_amps }} A to
  input_number.ev_charger_setpoint
  variables:
  fuse_limit: 25
  safety_margin: 1
  min_allowed: 6
  max_allowed: 16
  up_smoothing: 0.5
  ia: "{{ states('sensor.shellyem3_3494547b6480_channel_a_current')|float(0) }}"
  ib: "{{ states('sensor.shellyem3_3494547b6480_channel_b_current')|float(0) }}"
  ic: "{{ states('sensor.shellyem3_3494547b6480_channel_c_current')|float(0) }}"
  ev_setpoint: "{{ states('input_number.ev_charger_setpoint')|float(0) }}"
  max_phase: "{{ [ia, ib, ic]|max }}"
  house_load: "{{ [0, max_phase - ev_setpoint]|max }}"
  headroom_after_off: "{{ fuse_limit|float(0) - house_load|float(0) }}"
  raw_allowed_total: "{{ headroom_after_off|float(0) - safety_margin|float(0) }}"
  allowed_total_clamped: "{{ [max_allowed|float(0), raw_allowed_total]|min }}"
  allowed_now: |-
  {% if allowed_total_clamped < min_allowed %}
  0
  {% else %}
  {{ [max_allowed|float(0), allowed_total_clamped]|min | int }}
  {% endif %}
  current_limit: "{{ ev_setpoint|float(0) }}"
  target_amps: >-
  {% set c = current_limit %} {% set a = allowed_now|float(0) %} {% if a == 0
  %}
  0
  {% elif a > c %}
  {{ (c + (a - c) * up_smoothing) | round(0, 'ceil') | int }}
  {% elif a < c %}
  {{ a | int }}
  {% else %}
  {{ c | int }}
  {% endif %}
  mode: queued

[kyrreaa]

I also have the ChargeAmps Halo, and they updated my firmware just a few days ago. (4.4-2025)
I can see a log message in Homeassistant saying "WARNING (MainThread) [py.warnings] /usr/local/lib/python3.13/site-packages/dataclasses_json/core.py:201: RuntimeWarning: 'NoneType' object value of non-optional type hardware_version detected when decoding ChargePoint" and I wonder if it is related to it not showing up?

[Niek]

I managed to connect my Aura using OCPP (ws://IP:9000), but nothing seems to work. All attributes are empty and nothing appears in the logs.

[robbionline]

I'll get the Charge Amps Luna installed tomorrow. Let's see, if I get it it running. Anyone here with some advice?

[HenrikBurton]

I installed a Charge Amps Halo (I love the form that fits my hours perfectly) despite the above issues and have got it working like I wanted. One issue is the occasionally it loses connection with the OCCP server in my HA but reconnects within a minute and the lose connection again after ~2 minutes. This can be fixed by restarting the Halo. Not ok but bearable until a fix is found.

[robbionline]

I'll get the Charge Amps Luna installed tomorrow. Let's see, if I get it it running. Anyone here with some advice?

I had some issues, but mostly my own faults. The charge amps Luna works quite well now. I'll have to look why many sensors are not populated, but that may also be expected.

[perbjore]

How did you manage to connect with the luna? I've tried ws://192.168.xx.xx:9000 without any success, does it need to run against a secure OCPP instance?

[perbjore]

I had issues with my ChargeAmps luna not publishing Voltage and current correcly in the intregration for all phases. Sometimes it was set as attributes to Current.Import but it was very flaky. I've fixed it in this branch here now all the metering values are working consistently as current_import_l1-l3 and voltage_l1-l3, have asked for merging to mainline here #1839

If not you can use it directly from here in the meanwhile
https://github.com/perbjore/ocpp