The last message in the map, and it reboots the charger

0108 was the one thing in the MQTT inventory nobody had wired: the device
power mode, whose single documented value restarts the charger. It is the
only way to reboot a charger that is on neither a CSMS nor the local
network — which is most of them — so the cloud transport sends it now,
and "reset" reaches it too, since that is what the OCPP path has always
called the same act.

Nothing waits for a confirmation: the device that would send it is the
device rebooting, so the command answers at once and says the charger
drops off the cloud for about a minute. The gate is unchanged and now
covers both spellings — an explicit confirm plus a password step-up,
audited either way. Modbus still refuses, because no register does this,
but its refusal now names both transports that can rather than only the
CSMS.

Both clients already had the reset button and its password prompt; they
were hidden in every mode that reads the device, which is why the cloud
never showed one. Modbus is now the only mode without it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

API Server/internal/api/integrations_ankersolix_mqtt.go

@@ -18,11 +18,11 @@ package api
 // or certificated on the customer's side; what it costs instead is a dependency
 // on Anker's cloud being up, and on an unofficial protocol.
 //
-// The command set is the charger's, not OCPP's: start, stop, boost, skip-delay
-// and a current limit, plus the one thing neither other transport can do at all
-// — writing the charger's own configuration, which is what "settings" is for.
-// Everything the register map or the CSMS can do that this cannot is refused by
-// name rather than as an unknown action.
+// The command set is the charger's, not OCPP's: start, stop, boost, skip-delay,
+// a current limit and a restart, plus the one thing neither other transport can
+// do at all — writing the charger's own configuration, which is what "settings"
+// is for. Everything the register map or the CSMS can do that this cannot is
+// refused by name rather than as an unknown action.
 
 import (
 	"context"
@@ -59,7 +59,7 @@ func (s *Server) ankerMqttAction(w http.ResponseWriter, r *http.Request, who *ca
 	// Actions this transport has no equivalent for. Naming the transport that
 	// does have them beats a bare "unknown action" the caller cannot act on.
 	switch action {
-	case "reset", "unlock", "availability", "trigger", "config":
+	case "unlock", "availability", "trigger", "config":
 		writeError(w, http.StatusBadRequest,
 			"\""+action+"\" is an OCPP command; the Anker cloud connection cannot send it. Switch the control mode to a CSMS mode to use it.")
 		return
@@ -96,6 +96,11 @@ func (s *Server) ankerMqttAction(w http.ResponseWriter, r *http.Request, who *ca
 	case "limit":
 		params["amps"] = body.Amps
 		payload["command"], payload["amps"] = "limit", body.Amps
+	case "reset", "restart":
+		// The charger's own restart, the cloud's answer to the OCPP reset. It has
+		// already been through the confirmation and the password step-up upstairs,
+		// like any other reboot.
+		payload["command"] = "restart"
 	case "settings":
 		// The values themselves are audited, not just the fact of a write: a
 		// setting that changes what the charger will draw, or whether it answers on