Using Esphome with rest api.

[pczolee]

Hello.

I have a charger which is working with esphome. I found that I can enable rest interface in esphome and than I can use that to work with evcc. Unfortunately I'm not familiar with this, so please help me. I made this config:

- name: wallbox
  type: custom
 status:
    source: http
    uri: http://192.168.1.86/text_sensor/status
    jq: if .state == "Waiting for EV" or .state == "Available" or .state == "Unavailable" or .state == "Outlet disabled" then "A" elif .state == "Preparing" or .state == "EV is asking for charging" or .state == "SuspendedEVSE" or .state == "SuspendedEV" or .state == "Finishing" then "B" elif .state == "EV is charging" then "C" else "" end
  enabled:
    source: http
    uri: http://192.168.1.86/switch/enable
    jq: .state == "ON"
  enable:
    source: http
    uri: http://192.168.1.86/switch/enable/{{if .state}}turn_on{{else}}turn_off{{end}}
    method: POST
  maxcurrent:
    source: http
    uri: http://192.168.1.86/number/max_amps/set?value="${maxcurrent}"
    method: POST

I have problem with the "enable", and maybe the "maxcurrent" not working, rest looks good.

The answer of enable query looks like:
http://192.168.1.86/switch/enable
{"id":"switch-enable","value":true,"state":"ON"}
I can turn on off off with:
http://192.168.1.86/switch/enable/turn_on or http://192.168.1.86/switch/enable/turn_ff

The answer of maxcurrent query looks like:
http://192.168.1.86/number/max_amps
{"id":"number-max_amps","value":"16","state":"16"}
I can set to 10A with: http://192.168.1.86/number/max_amps/set?value=10

Can anybody help me how to make it work?
Thanks

[VolkerK62]

I guess, you must use .enable and not .state

  enable:
    source: http
    uri: http://192.168.1.86/switch/enable/{{if .enable}}turn_on{{else}}turn_off{{end}}
    method: POST

[VolkerK62]

depends on the default charge mode

[pczolee]

depends on the default charge mode

Well, it is mode: pv

[pczolee]

With mode: minpv it is not switching off at startup. But, when I switch it off from the ui it switch the charger off (as it should be), but when I want to switch back to minpv, it is remaining off.

[VolkerK62]

pls show a debug logifle of this ...

[VolkerK62]

and not sure, if this will work

enabled:
  source: http
  uri: http://192.168.1.86/switch/enable
  jq: .state == "ON"

It should show the actual switch state of the charger. So true/false or 0/1

[pczolee]

Well, with this config everything looks good, just the enable isn't working, but I can live without that if there is no solution..

- name: wallbox
  type: custom
  status:
    source: http
    uri: http://192.168.1.86/text_sensor/status
    jq: if .state == "Waiting for EV" or .state == "Available" or .state == "Unavailable" or .state == "Outlet disabled" then "A" elif .state == "Preparing" or .state == "EV is asking for charging" or .state == "SuspendedEVSE" or .state == "SuspendedEV" or .state == "Finishing" then "B" elif .state == "EV is charging" then "C" else "" end
  enabled:
    source: http
    uri: http://192.168.1.86/switch/enable
    jq: .state == "ON"
  enable:
    source: http
    uri: http://192.168.1.86/switch/enable/turn_on
#    uri: http://192.168.1.86/switch/enable/{{if .enable}}turn_on{{else}}turn_off{{end}}
    method: POST
  maxcurrent:
    source: http
    uri: http://192.168.1.86/number/max_amps/set?value=${maxcurrent}
    method: POST
  currents: # to provide the measured charging currents (A)
    - source: http # source for L1 current
      uri: http://192.168.1.86/sensor/max_current
      jq: .value
    - source: http # source for L2 current
      uri: http://192.168.1.86/sensor/max_current
      jq: .value
    - source: http # source for L3 current
      uri: http://192.168.1.86/sensor/max_current
      jq: .value

[mfuchs1984]

This is how enable worked for me with the home assistant API.

enable:
      source: http
      uri: http://<HOME_ASSISTANT_IP>:8123/api/services/switch/{{if .enable}}turn_on{{else}}turn_off{{end}}
      method: POST
      body: "{\"entity_id\": \"switch.charger_charge_control\"}"
      auth:
        type: bearer
        password: <YOUR_BEARER_TOKEN>

So the line you commented out line basically looks good.

[mfuchs1984]

http://192.168.1.86/switch/enable

Doesn't your switch have an id? This is an example from the esphome docu:

Creating a POST request to /switch/dehumidifier/turn_on would for example result in the component called “Dehumidifier” to be turned on. The server will respond with a 200 OK HTTP return code if the call succeeded.

To me it seems like your call is missing the "Dehumidifier" (just a placeholder). Or is thr switch simply called "enable"?

And in the mentioned trace log, you'll see the response.

[pczolee]

This is how enable worked for me with the home assistant API.

enable:
      source: http
      uri: http://<HOME_ASSISTANT_IP>:8123/api/services/switch/{{if .enable}}turn_on{{else}}turn_off{{end}}
      method: POST
      body: "{\"entity_id\": \"switch.charger_charge_control\"}"
      auth:
        type: bearer
        password: <YOUR_BEARER_TOKEN>

So the line you commented out line basically looks good.

Yes I thought so, but it not switching on never, just of. so something is wrong :( .

[pczolee]

http://192.168.1.86/switch/enable

Doesn't your switch have an id? This is an example from the esphome docu:

Creating a POST request to /switch/dehumidifier/turn_on would for example result in the component called “Dehumidifier” to be turned on. The server will respond with a 200 OK HTTP return code if the call succeeded.

To me it seems like your call is missing the "Dehumidifier" (just a placeholder). Or is thr switch simply called "enable"?

And in the mentioned trace log, you'll see the response.

No, there is no ID. As you can see on my first post the switch itself working in this way (from a browser for example).

[mfuchs1984]

Trace log?