tighten esp8266 mqtt-first preset

Author: ZeroBitsTech

CHANGELOG.md

@@ -9,6 +9,7 @@
 ## Unreleased
 
 - Added `ZeroNetProfileEsp8266`, a constrained MQTT-first preset for Wemos / ESP8266.
+- Refined `ZeroNetProfileEsp8266` so HTTP stays truly off by default, MQTT idle churn is lower, and the official Wemos live compare now shows MQTT delivery with timing that beats the naive baseline in the same window.
 - Added optional offline queue gating in `ZeroHttpPump` and `ZeroMqttPump` so constrained boards can refuse backlog when link or transport is down.
 - Reduced scheduler contention in the ESP8266 preset by staggering network task start offsets and lowering idle network task cadence.
 - Updated the ESP8266 preset to recommend `kIdleYield` instead of `kIdleSleep`, which materially reduces live timing jitter in the official Wemos validation node.

README.md

@@ -111,13 +111,13 @@ They are already useful and validated on desktop plus ESP32 hardware, but they a
 Current target maturity:
 
 - **ESP32:** stable enough for production-style evaluation and controlled deployments when validated against the real HTTP/MQTT endpoint you intend to ship with.
-- **ESP8266 / Wemos:** still BETA. Live delivery is real, but timing cost is still under active hardening.
+- **ESP8266 / Wemos:** still BETA for full dual-transport use. The constrained MQTT-first preset is now the recommended path and already has repeatable live runs where MQTT delivery is real and timing beats the naive baseline, but full HTTP+MQTT behavior is still under active hardening.
 - **Other supported families:** compile-validated, but network helper maturity should still be treated as evaluation-grade until they receive the same live validation depth.
 
 Recommended board-specific path:
 
 - **ESP32:** use the default network module configs first, then validate against your real endpoint.
-- **ESP8266 / Wemos:** start with `ZeroNetProfileEsp8266`. It is a constrained MQTT-first preset that disables periodic HTTP dispatch by default, prevents offline queue buildup, staggers lighter network task cadence, and recommends a lighter idle strategy. In current validation it is the preferred path for Wemos MQTT delivery, while HTTP remains degraded/off by default.
+- **ESP8266 / Wemos:** start with `ZeroNetProfileEsp8266`. It is a constrained MQTT-first preset that disables periodic HTTP dispatch by default, prevents offline queue buildup, lowers idle MQTT churn, staggers lighter network task cadence, and recommends a lighter idle strategy. In current validation it is the preferred path for Wemos MQTT delivery, while HTTP remains degraded/off by default unless you deliberately opt back in.
 
 Current best module tradeoff reference (ESP32, `LEAN_NET`, manual pattern vs module pattern):
 

docs/wiki/Beta-Modules.md

@@ -13,12 +13,12 @@ They are already useful and validated on desktop plus ESP32 smoke tests, but the
 ## Target maturity right now
 
 - **ESP32:** the current network stack is stable enough for production-style evaluation and controlled deployments when you validate against your real server or broker.
-- **ESP8266 / Wemos:** still BETA. Live transport works, but timing cost is still under active hardening.
+- **ESP8266 / Wemos:** still BETA for full dual-transport use. The constrained MQTT-first preset now has repeatable live runs where MQTT delivery is real and timing beats the naive baseline, but the broader HTTP+MQTT path is still under active hardening.
 - **Other targets:** compile-supported, but network helpers should still be treated as validation targets until they see the same live-network coverage.
 
 Recommended default:
 
-- For constrained ESP8266 boards, start with `ZeroNetProfileEsp8266`. It is the recommended MQTT-first constrained preset: HTTP stays degraded/off by default, offline queueing is rejected, and the preset uses a lighter recommended idle strategy plus staggered network task starts so the board stays more predictable without hand-tuning every interval.
+- For constrained ESP8266 boards, start with `ZeroNetProfileEsp8266`. It is the recommended MQTT-first constrained preset: HTTP stays degraded/off by default, offline queueing is rejected, idle MQTT churn is lower, and the preset uses a lighter recommended idle strategy plus staggered network task starts so the board stays more predictable without hand-tuning every interval.
 
 ## What BETA Means Here
 

examples/LiveNetworkNode/LiveNetworkNode.ino

@@ -28,11 +28,13 @@ namespace {
 const unsigned long kSamplePeriodUs = 100000UL;
 #if defined(ARDUINO_ARCH_ESP8266)
 const unsigned long kSampleTaskIntervalMs = ZeroNetProfileEsp8266::kSampleTaskIntervalMs;
+const bool kEnableHttpByDefault = ZeroNetProfileEsp8266::kEnableHttpByDefault;
 const unsigned long kHttpDispatchPeriodMs = ZeroNetProfileEsp8266::kHttpDispatchPeriodMs;
 const unsigned long kMqttDispatchPeriodMs = ZeroNetProfileEsp8266::kMqttDispatchPeriodMs;
 const unsigned long kHttpIoTimeoutMs = ZeroNetProfileEsp8266::kHttpIoTimeoutMs;
 #else
 const unsigned long kSampleTaskIntervalMs = 1UL;
+const bool kEnableHttpByDefault = true;
 const unsigned long kHttpDispatchPeriodMs = 500UL;
 const unsigned long kMqttDispatchPeriodMs = 500UL;
 const unsigned long kHttpIoTimeoutMs = 500UL;
@@ -422,13 +424,15 @@ void setup() {
 #if defined(ARDUINO_ARCH_ESP8266)
   httpConfig = ZeroNetProfileEsp8266::httpConfig();
 #endif
-  g_httpPump.begin(ZeroKernel,
-                   httpConnectStep,
-                   httpWriteStep,
-                   httpReadStep,
-                   httpCloseStep,
-                   httpConfig);
-  g_httpPump.setLinkProbe(isWiFiConnected);
+  if (kEnableHttpByDefault) {
+    g_httpPump.begin(ZeroKernel,
+                     httpConnectStep,
+                     httpWriteStep,
+                     httpReadStep,
+                     httpCloseStep,
+                     httpConfig);
+    g_httpPump.setLinkProbe(isWiFiConnected);
+  }
 
   ZeroMqttPump::Config mqttConfig;
 #if defined(ARDUINO_ARCH_ESP8266)
@@ -447,8 +451,10 @@ void setup() {
   ZeroKernel.addTask("Sample", sampleTask, ZeroNetProfileEsp8266::kSampleTaskIntervalMs, 0);
   ZeroKernel.addTask("WiFiMaint", wifiMaintainerTask, ZeroNetProfileEsp8266::kWiFiTaskIntervalMs,
                      ZeroNetProfileEsp8266::kWiFiTaskStartDelayMs);
-  ZeroKernel.addTask("HttpPump", httpPumpTask, ZeroNetProfileEsp8266::kHttpTaskIntervalMs,
-                     ZeroNetProfileEsp8266::kHttpTaskStartDelayMs);
+  if (kEnableHttpByDefault) {
+    ZeroKernel.addTask("HttpPump", httpPumpTask, ZeroNetProfileEsp8266::kHttpTaskIntervalMs,
+                       ZeroNetProfileEsp8266::kHttpTaskStartDelayMs);
+  }
   ZeroKernel.addTask("MqttPump", mqttPumpTask, ZeroNetProfileEsp8266::kMqttTaskIntervalMs,
                      ZeroNetProfileEsp8266::kMqttTaskStartDelayMs);
   ZeroKernel.addTask("Dispatch", dispatchTask, ZeroNetProfileEsp8266::kDispatchTaskIntervalMs,
@@ -460,13 +466,26 @@ void setup() {
   ZeroKernel.addTask("MqttPump", mqttPumpTask, 100, kMqttPumpStartDelayMs);
   ZeroKernel.addTask("Dispatch", dispatchTask, 100, kDispatchStartDelayMs);
 #endif
-  ZeroKernel.addTask("Report", reportTask, 250, kReportStartDelayMs);
+  ZeroKernel.addTask("Report", reportTask,
+#if defined(ARDUINO_ARCH_ESP8266)
+                     ZeroNetProfileEsp8266::kReportTaskIntervalMs,
+#else
+                     250,
+#endif
+                     kReportStartDelayMs);
 
   ZeroKernel.setTaskPriority("Sample", Kernel::kPriorityCritical);
   ZeroKernel.setTaskPriority("WiFiMaint", Kernel::kPriorityHigh);
-  ZeroKernel.setTaskPriority("HttpPump", Kernel::kPriorityNormal);
+  if (kEnableHttpByDefault) {
+    ZeroKernel.setTaskPriority("HttpPump", Kernel::kPriorityNormal);
+  }
+#if defined(ARDUINO_ARCH_ESP8266)
+  ZeroKernel.setTaskPriority("MqttPump", Kernel::kPriorityLow);
+  ZeroKernel.setTaskPriority("Dispatch", Kernel::kPriorityLow);
+#else
   ZeroKernel.setTaskPriority("MqttPump", Kernel::kPriorityNormal);
   ZeroKernel.setTaskPriority("Dispatch", Kernel::kPriorityNormal);
+#endif
   ZeroKernel.setTaskPriority("Report", Kernel::kPriorityLow);
 
   g_startedAtMs = millis();

src/modules/net/ZeroNetProfileEsp8266.h

@@ -13,12 +13,13 @@ namespace net {
 // This profile intentionally prefers MQTT cadence over aggressive HTTP churn.
 struct ZeroNetProfileEsp8266 {
   static const uint8_t kRecommendedIdleStrategy = Kernel::kIdleYield;
+  static const bool kEnableHttpByDefault = false;
   static const unsigned long kSampleTaskIntervalMs = 100UL;
   static const unsigned long kWiFiTaskIntervalMs = 250UL;
   static const unsigned long kHttpTaskIntervalMs = 250UL;
-  static const unsigned long kMqttTaskIntervalMs = 250UL;
+  static const unsigned long kMqttTaskIntervalMs = 500UL;
   static const unsigned long kDispatchTaskIntervalMs = 250UL;
-  static const unsigned long kReportTaskIntervalMs = 250UL;
+  static const unsigned long kReportTaskIntervalMs = 1000UL;
 
   static const unsigned long kWiFiTaskStartDelayMs = 25UL;
   static const unsigned long kHttpTaskStartDelayMs = 75UL;
@@ -58,7 +59,7 @@ struct ZeroNetProfileEsp8266 {
     config.retryBaseMs = 600UL;
     config.retryMaxMs = 3000UL;
     config.retryJitterMs = 180UL;
-    config.idleLoopIntervalMs = 150UL;
+    config.idleLoopIntervalMs = 500UL;
     config.maxRetries = 2;
     config.queueWhenTransportDown = false;
     return config;