A line per frame, for the frames nobody has named

ANKER_MQTT_FRAME_LOG logs every inbound cloud frame with its bytes,
decoded or not — the ones this package drops are exactly the ones worth
naming, so they are logged before the drop.

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

Docker/.env.example

@@ -34,6 +34,15 @@ AUTH_USERS_COLLECTION=users
 # public wss:// base, or set OCPP_REQUIRE_TLS=false on a trusted network.
 OCPP_REQUIRE_TLS=true
 OCPP_PUBLIC_URL=
+
+# Diagnostic only. Set to 1 to log every frame the charger publishes over Anker's
+# cloud broker — the ones DriverVault decodes and the ones it cannot, with their
+# bytes. It is how an unnamed frame gets named: hold a control read open, do the
+# thing in the Anker app, then read the frames back out of the container log.
+# Leave blank on a normal stack; a triggered charger writes a line every few
+# seconds.
+ANKER_MQTT_FRAME_LOG=
+
 # The charger can dial either door: the API Server port directly, or the Web
 # App port, whose BFF now proxies /ocpp/ through to it. The endpoint the panel
 # shows is the API Server port only when OCPP_PUBLIC_URL says so — left blank it