From e02855173a399df3032950299fba8b309bae5639 Mon Sep 17 00:00:00 2001
From: tajniak81 <13187254+tajniak81@users.noreply.github.com>
Date: Wed, 2 Sep 2026 10:28:41 +0200
Subject: [PATCH] One register, one slider
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The settings card took over the charger's current ceiling last commit and the
control card kept its own slider for it, so the same register had two controls a
card apart, each showing whatever it was last dragged to rather than what the
charger holds.

The control card gives it up on the local path. What is left there is what the
card is named for: start, stop, boost — things done to the session in front of
you, not settings the charger keeps.

It stays on the OCPP path, where there is nothing to hand it to. A charging
profile is not a setting the charger reports back, so there is no settings card
on that side of the page, and the clear button belongs to it — clearing is an
OCPP command the register map has no equivalent for.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 Web App/web/src/views/Charging.vue | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/Web App/web/src/views/Charging.vue b/Web App/web/src/views/Charging.vue
index cd3782c..928a123 100644
--- a/Web App/web/src/views/Charging.vue	
+++ b/Web App/web/src/views/Charging.vue	
@@ -1076,7 +1076,13 @@ onMounted(async () => {
             </button>
           </div>
 
-          <div class="mt-3">
+          <!-- The limit, on the OCPP path only. On the local one the settings
+               card owns it: there it is the charger's own ceiling register, read
+               back and written, and the same slider in two cards was the same
+               register twice. OCPP has no settings card to move it to — a
+               charging profile is not a setting the charger reports — so here it
+               stays, with the clear that only OCPP can send. -->
+          <div v-if="!ctlIsModbus" class="mt-3">
             <label class="dh-label flex justify-between">
               <span>{{ t("charging.control.limit") }}</span><span class="data text-body">{{ limitAmps }} A</span>
             </label>
@@ -1085,10 +1091,7 @@ onMounted(async () => {
               <button class="dh-btn dh-btn-ghost grow" :disabled="ctlBusy === 'limit'" @click="doAction('limit', { amps: limitAmps })">
                 {{ t("charging.control.applyLimit") }}
               </button>
-              <!-- Clearing a limit is an OCPP command; the register map takes an
-                   explicit ceiling, so in Modbus mode there is nothing to clear to. -->
               <button
-                v-if="!ctlIsModbus"
                 class="dh-btn dh-btn-ghost grow"
                 :disabled="ctlBusy === 'clear-limit'"
                 @click="doAction('clear-limit')"