Charge Amps Aura missing functionality

[Miggle007]

I am gladly using this integration and I am able to do the following:

• Read the current power usage per connector (the Aura has two connectors)
• View the actual status per connector (available, charging, ..)
• Switch the connector on or off
• Dim the light
• Read the total consumed energy

However, I am mainly missing the thing that I want to automate on: Set the current per connector. When taking a look at the REST API documentation this is available. When digging in to this custom component it seems to be built in to this integration.

Does anyone recognize this?
Does this also has to do with the CAPI > OCPP?

[ReconOperator]

Maybe I'm missunderstanding you, but have you checked the documentation here?
https://github.com/kirei/hass-chargeamps?tab=readme-ov-file#services

set_max_current -- set max current for connector

I have a Halo with OCPP and I can set the max current with this Action in HA

You can test it under developer tools

[tretabyte]

Hi,
did you build yourself the "Set Max Current"?, I've been trying to do it, but I don't have enough skills for it (I even made a post request here to see if we can get that by default with no luck).
Another thing that would be useful would be to have a remote start and remote stop buttons, that way you can always turn it on but not start the charging until you really want it to.

[ReconOperator]

Hi, did you build yourself the "Set Max Current"?, I've been trying to do it, but I don't have enough skills for it (I even made a post request here to see if we can get that by default with no luck). Another thing that would be useful would be to have a remote start and remote stop buttons, that way you can always turn it on but not start the charging until you really want it to.

Yes i have done an automation for the "Set Max Current" that uses input from a input select helper.

alias: Halo Set Max Current
description: Set Max current on Charge Amps Halo
mode: single
triggers:

• entity_id:
  • input_select.set_current
    trigger: state
    conditions: []
    actions:
• data:
  chargepoint: "redacted"
  connector: 1
  max_current: |-
  {% if is_state("input_select.set_current", "6") %}
  6
  {% elif is_state("input_select.set_current", "8") %}
  8
  {% elif is_state("input_select.set_current", "10") %}
  10
  {% elif is_state("input_select.set_current", "12") %}
  12
  {% elif is_state("input_select.set_current", "14") %}
  14
  {% elif is_state("input_select.set_current", "16") %}
  16
  {% else %}
  Unknown
  {% endif %}
  action: chargeamps.set_max_current

[tretabyte]

mind sharing the entire yaml for that automatition?

this is what I have and its supposed to work but somehow it doesn't do the change

alias: chargeamp set_current
description: ""
triggers:
  - trigger: state
    entity_id:
      - input_select.set_current
conditions: []
actions:
  - action: chargeamps.set_max_current
    data:
      chargepoint: XXXXXXXXXX
      connector: 1
      max_current: |-
        {% if is_state("input_select.set_current", "6") %}
        6
        {% elif is_state("input_select.set_current", "8") %}
        8
        {% elif is_state("input_select.set_current", "10") %}
        10
        {% elif is_state("input_select.set_current", "12") %}
        12
        {% elif is_state("input_select.set_current", "14") %}
        14
        {% elif is_state("input_select.set_current", "16") %}
        16
        {% elif is_state("input_select.set_current", "18") %}
        18
        {% elif is_state("input_select.set_current", "20") %}
        20
        {% elif is_state("input_select.set_current", "22") %}
        22
        {% elif is_state("input_select.set_current", "24") %}
        24
        {% elif is_state("input_select.set_current", "26") %}
        26
        {% else %}
        Unknown
        {% endif %}
mode: single

[ReconOperator]

I shared the complete .yaml of the automation.

Did you create the input_select.set_current helper?

[tretabyte]

I shared the complete .yaml of the automation.

Did you create the input_select.set_current helper?

yep I did and the selector works
wait.. I think it's working, somehow it takes like 1min or so to update but it works
thank you very much for the help :)

[Miggle007]

Hi @ReconOperator, Many many thanks for this! I've been looking everywhere except in developer tools. I've tested it just now and indeed this works perfectly. I'll create some sort of input selector the way you did in order to use it in manually changing and and mostly in automizing (peak shaving) this. Great and thanks again. My issue has been resolved.

[Miggle007]

My issue has been resolved by using the developer tools

[Miggle007]

@tretabyte I have created a slightly different automation. Perhaps it's useful for you as well. I have created a slider helper from 6A (minimum supported by ChargeAmps) to 16A (maximum in my case) called input_number.maximum_current_connector_1_left. Furthermore I have two helpers and two automations, because I need to be able to set the max_current for each connect independantly.

This results in a slightly shortened automation:

alias: chargeamps set current L
description: Set Current for ChargeAmps Aura Connector 1
triggers:
  - trigger: state
    entity_id:
      - input_number.maximum_current_connector_1_left
conditions: []
actions:
  - action: chargeamps.set_max_current
    data:
      chargepoint: 1234567890A
      connector: 1
      max_current: |
        {{ states("input_number.maximum_current_connector_1_left") }}
mode: single

[tretabyte]

@tretabyte I have created a slightly different automation. Perhaps it's useful for you as well. I have created a slider helper from 6A (minimum supported by ChargeAmps) to 16A (maximum in my case) called input_number.maximum_current_connector_1_left. Furthermore I have two helpers and two automations, because I need to be able to set the max_current for each connect independantly.

This results in a slightly shortened automation:

alias: chargeamps set current L
description: Set Current for ChargeAmps Aura Connector 1
triggers:

• trigger: state
  entity_id:

  • input_number.maximum_current_connector_1_left
    conditions: []
    actions:

• action: chargeamps.set_max_current
  data:
  chargepoint: 1234567890A
  connector: 1
  max_current: |
  {{ states("input_number.maximum_current_connector_1_left") }}
  mode: single

Basically you created another automation that will change the input_number depending on which input_silder you picked and then it changes the max_current sent to the charger, is that right?

[Miggle007]

@tretabyte I have created a slightly different automation. Perhaps it's useful for you as well. I have created a slider helper from 6A (minimum supported by ChargeAmps) to 16A (maximum in my case) called input_number.maximum_current_connector_1_left. Furthermore I have two helpers and two automations, because I need to be able to set the max_current for each connect independantly.
This results in a slightly shortened automation:

alias: chargeamps set current L
description: Set Current for ChargeAmps Aura Connector 1
triggers:

• trigger: state
  entity_id:

  • input_number.maximum_current_connector_1_left
    conditions: []
    actions:

• action: chargeamps.set_max_current
  data:
  chargepoint: 1234567890A
  connector: 1
  max_current: |
  {{ states("input_number.maximum_current_connector_1_left") }}
  mode: single

Basically you created another automation that will change the input_number depending on which input_silder you picked and then it changes the max_current sent to the charger, is that right?

Yes, that's exactly what it does!

[Miggle007]

And the last update is my remote start and stop. I've created a helper (boolean on/off) called input_boolean.remote_start_stop_connector_1_left. Again I have two helpers, because of the two connectors on the Aura. I don't think this is the best way or the best way of doing it. Hoewever it does the job for me:

alias: Remote Start and Stop
description: Remote Start and Stop
triggers:
  - trigger: state
    entity_id:
      - input_boolean.remote_start_stop_connector_1_left
conditions: []
actions:
  - if:
      - condition: template
        value_template: >-
          {{ is_state('input_boolean.remote_start_stop_connector_1_left','on')
          }}
    then:
      - action: chargeamps.remote_start
        data:
          chargepoint: 1234567890A
          connector: 1
          rfid_length: 4
          rfid_format: Dec
          rfid: 111111111
        target:
          entity_id: chargeamps.remote_start
    else:
      - action: chargeamps.remote_stop
        data:
          chargepoint: 1234567890A
          connector: 1
        target:
          entity_id: chargeamps.remote_stop
mode: single

You'll need to wait about 1 minute after a remote start or stop to send a new (inversed) remote start or stop.

[tretabyte]

oh man, you are really the MVP :)

[ReconOperator]

You can add this if you want a lite more robust checking for turning on the switch and sending the remot start command

Turn on

• repeat:
  sequence:
  - data:
  chargepoint: XXXXXXXXX
  connector: 1
  action: chargeamps.enable
  - delay:
  hours: 0
  minutes: 0
  seconds: 5
  milliseconds: 0
  while:
  - condition: state
  entity_id: switch.XXXXXXXXXXX
  state: "off"
  - condition: template
  value_template: "{{ repeat.index <= 20 }}"

remote start

• repeat:
  sequence:
  • continue_on_error: true
    data:
    chargepoint: XXXXXXXXXXXX
    connector: 1
    rfid_length: 4
    rfid_format: Dec
    rfid: XXXXXXXXXXXXXXX
    action: chargeamps.remote_start
  • delay:
    hours: 0
    minutes: 1
    seconds: 0
    milliseconds: 0
    while:
  • condition: numeric_state
    entity_id: sensor.XXXXXXXXX_power
    below: 1
  • condition: template
    value_template: "{{ repeat.index <= 10 }}"

[tretabyte]

You can add this if you want a lite more robust checking for turning on the switch and sending the remot start command

Turn on

* repeat:
  sequence:
  - data:
  chargepoint: XXXXXXXXX
  connector: 1
  action: chargeamps.enable
  - delay:
  hours: 0
  minutes: 0
  seconds: 5
  milliseconds: 0
  while:
  - condition: state
  entity_id: switch.XXXXXXXXXXX
  state: "off"
  - condition: template
  value_template: "{{ repeat.index <= 20 }}"

remote start

* repeat:
  sequence:
  
  * continue_on_error: true
    data:
    chargepoint: XXXXXXXXXXXX
    connector: 1
    rfid_length: 4
    rfid_format: Dec
    rfid: XXXXXXXXXXXXXXX
    action: chargeamps.remote_start
  * delay:
    hours: 0
    minutes: 1
    seconds: 0
    milliseconds: 0
    while:
  * condition: numeric_state
    entity_id: sensor.XXXXXXXXX_power
    below: 1
  * condition: template
    value_template: "{{ repeat.index <= 10 }}"

I'm guessing this is to place with the automation?
mind sharing the full automation with the formated code? (use the """""`" to open close the pasted code)

[ReconOperator]

Sure, its scrips that i call from automations for different triggers

Halo Remote Start
https://pastebin.com/rrZBP2Zw

Halo Remote Stop
https://pastebin.com/ft2Huubt

Halo Turn Off
https://pastebin.com/aYJftzEq

Halo Turn On
https://pastebin.com/Nr71DYY2

Suspended By EV
https://pastebin.com/PgFfE5cZ

[tretabyte]

Sure, its scrips that i call from automations for different triggers

Halo Remote Start https://pastebin.com/rrZBP2Zw

Halo Remote Stop https://pastebin.com/ft2Huubt

Halo Turn Off https://pastebin.com/aYJftzEq

Halo Turn On https://pastebin.com/Nr71DYY2

Suspended By EV https://pastebin.com/PgFfE5cZ

oh I see you have an additional helper to control the energy cost and block the charging if it goes above a certain value, interesting!

[ReconOperator]

Yes I live in Sweden and we can choose from different "subscriptions" on how to pay for electricity. I have spot price. So I'm basically just checking the prices ahead and setting a value for when to charge or not. Could do it by selecting for example the 5 cheapest hours of the day dynamic also.