You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure why this is happening, but while experimenting with the EVSE's temperature limiting, I noticed that if the EVSE reduces the pilot current due to high temperature, this isn't reflected by the pilot field on the sensors web page, or the MQTT "pilot" field.
It looks okay on the RAPI log:
eg: current limit set to 11A, normal temperature:
$GC^20
$OK 6 32 11 13^15
After temperature limiting begins:
$GC^20
$OK 6 32 6 13^23
But "pilot" remains at 11A.
The text was updated successfully, but these errors were encountered:
kimble4
changed the title
"pilot" field does not track pilot changes
"pilot" field does not track pilot changes due to temperature limiting
Oct 8, 2024
It's the same with the current shaper, when it lowers the pilot it's not reflected in the "charge pilot max" mqtt entity. I was unsure what the "max" in that field means but I interpreted it to mean "the max current as sent through the pilot" not "the max value that the pilot can ever be". It does seem to behave like the latter, though.
I'm not sure why this is happening, but while experimenting with the EVSE's temperature limiting, I noticed that if the EVSE reduces the pilot current due to high temperature, this isn't reflected by the pilot field on the sensors web page, or the MQTT "pilot" field.
It looks okay on the RAPI log:
eg: current limit set to 11A, normal temperature:
After temperature limiting begins:
But "pilot" remains at 11A.
The text was updated successfully, but these errors were encountered: