Bug fix - When disabling the mMaximumChargingCurrentLimitFromCommand was not being updated, so we didn't get attribute updates for MaximumChargeCurrent when toggling Enable-Disable-Enable.

Author: jamesharrow

examples/energy-management-app/energy-management-common/src/EnergyEvseDelegateImpl.cpp

@@ -63,7 +63,9 @@ Status EnergyEvseDelegate::Disable()
 
     /* update MinimumChargeCurrent & MaximumChargeCurrent to 0 */
     SetMinimumChargeCurrent(0);
-    SetMaximumChargeCurrent(0);
+
+    mMaximumChargingCurrentLimitFromCommand = 0;
+    ComputeMaxChargeCurrentLimit();
 
     /* update MaximumDischargeCurrent to 0 */
     SetMaximumDischargeCurrent(0);
@@ -1360,24 +1362,6 @@ int64_t EnergyEvseDelegate::GetMaximumChargeCurrent()
     return mMaximumChargeCurrent;
 }
 
-CHIP_ERROR EnergyEvseDelegate::SetMaximumChargeCurrent(int64_t newValue)
-{
-    int64_t oldValue = mMaximumChargeCurrent;
-
-    if (newValue >= kMaximumChargeCurrent)
-    {
-        return CHIP_IM_GLOBAL_STATUS(ConstraintError);
-    }
-
-    mMaximumChargeCurrent = newValue;
-    if (oldValue != mMaximumChargeCurrent)
-    {
-        ChipLogDetail(AppServer, "MaximumChargeCurrent updated to %ld", static_cast<long>(mMaximumChargeCurrent));
-        MatterReportingAttributeChangeCallback(mEndpointId, EnergyEvse::Id, MaximumChargeCurrent::Id);
-    }
-    return CHIP_NO_ERROR;
-}
-
 /* MaximumDischargeCurrent */
 int64_t EnergyEvseDelegate::GetMaximumDischargeCurrent()
 {