dingo35

As stated before, for this we need the SoC, which is not available in SmartEVSE-v3 ; if you have that information available in external software (e.g. via a HomeAssistant integration...

Current 3.6.0 has delayed charging in the webserver screen, look at https://github.com/SmartEVSE/SmartEVSE-3/blob/master/docs/operation.md , paragraph "Simple Timer".

The modbus TCP bridge had to be removed because it disturbed the "regular" traffic on the modbus. We will look into making more registers of the MainsMeter and the EVMeter...

" I think it's extremely important to not leave people stranded in the event of communication loss." The problem with a "fall back" charge current is that you are operating...

Lets not repeat this discussion again: https://github.com/dingo35/SmartEVSE-3.5/issues/34

It is a non trivial, difficult change in a critical part of the code, with very few use cases (there is you and one other guy who brought this up...

There are some users (if I remember correctly especially Tesla-users) that have been able to lower the minimum charging current to 3A; we would like to stick to the standards,...

https://github.com/dingo35/SmartEVSE-3.5/issues/51

You can use the HTTP REST API, or the MQTT API, or the HomeAssistant integration for this; look at the docs!

I am starting to work on this, do I still have your cooperation for testing this, since it has been some time...?