feat: add max_current sensor

[firstof9]

fixes #384

Provides max_current sensor.
Change old "max current" selector to Charge Rate to better reflect it's use.

[jstebbins]

Hi, me again 😁

I think the value you are using here for max current is still not quite providing what I would like. You are returning the max_current from the get status API:
https://openevse.stoplight.io/docs/openevse-wifi-v4/dba95e8966593-get-the-evse-status

The documentation says this value is "the actual max current value defined either by max_current_soft or a running claim". So it may not be the same as MAX CURRENT in OpenEVSE settings. I think you need to return max_current_soft from the get config API.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (main@ae4d7cb). Learn more about missing BASE report.
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #385   +/-   ##
=======================================
  Coverage        ?   83.91%           
=======================================
  Files           ?       12           
  Lines           ?      945           
  Branches        ?        0           
=======================================
  Hits            ?      793           
  Misses          ?      152           
  Partials        ?        0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[firstof9]

The documentation says this value is "the actual max current value defined either by max_current_soft or a running claim". So it may not be the same as MAX CURRENT in OpenEVSE settings. I think you need to return max_current_soft from the get config API.

They are the same value, I've verified this on my device. When I adjust the max current both values change.

[jstebbins]

They are the same value, I've verified this on my device. When I adjust the max current both values change.

But if you were to issue a post claim API call with a max_current value that is different than the MAX CURRENT config setting, my contention is that the values would then not be the same. See:
https://openevse.stoplight.io/docs/openevse-wifi-v4/ebc578ffa7ca7-make-update-an-evse-claim

[firstof9]

I did issue a claim, max_current didn't change only the "charge rate" changed.

[jstebbins]

I did issue a claim, max_current didn't change only the "charge rate" changed.

Interesting. The OpenEVSE documentation is certainly vague, and I believe in this case flat out wrong then. Empirical testing FTW.

Thanks!

[firstof9]

I also verified adjusting the selector changes the "Charge Rate" as it's labeled in the UI without it adjusting the "Max Current" 🙂