@alteriom/painlessmesh 1.9.20 → 2.0.0

package/examples/sendToInternet/{PC_NODE_README.md → pc_node/PC_NODE_README.md}

@@ -6,7 +6,7 @@ This example provides a **PC-based mesh node** that can join a painlessMesh netw
 
 ### The Problem This Solves
 
-Previous examples (`mock_server_test.ino`) tested the bridge making HTTP requests directly, but did **NOT** test the complete flow:
+Previous examples (`../mock_server_test/mock_server_test.ino`) tested the bridge making HTTP requests directly, but did **NOT** test the complete flow:
 
 ```
 Regular Node → Mesh Network → Bridge → Internet → Bridge → Mesh Network → Regular Node
@@ -90,7 +90,7 @@ brew install cmake boost
 For testing, start the mock HTTP server:
 
 ```bash
-cd ../../test/mock-http-server
+cd ../../../test/mock-http-server
 python3 server.py
 ```
 
@@ -101,13 +101,13 @@ The server will run on `http://localhost:8080` by default.
 ### Quick Build (Using make)
 
 ```bash
-cd examples/sendToInternet
+cd examples/sendToInternet/pc_node
 
 # Initialize dependencies (if not already done)
-cd ../../test
+cd ../../../test
 git clone https://github.com/bblanchon/ArduinoJson.git
 git clone https://github.com/arkhipenko/TaskScheduler
-cd ../examples/sendToInternet
+cd ../examples/sendToInternet/pc_node
 
 # Build
 cmake .
@@ -131,9 +131,9 @@ make
 
 ```bash
 g++ -std=c++14 -o pc_mesh_node pc_mesh_node.cpp \
-    -I../../src -I../../test/include -I../../test/ArduinoJson/src \
-    -I../../test/TaskScheduler/src -I../../test/boost \
-    ../../test/catch/fake_serial.cpp ../../src/scheduler.cpp \
+    -I../../../src -I../../../test/include -I../../../test/ArduinoJson/src \
+    -I../../../test/TaskScheduler/src -I../../../test/boost \
+    ../../../test/catch/fake_serial.cpp ../../../src/scheduler.cpp \
     -lboost_system -pthread
 ```
 
@@ -371,14 +371,14 @@ brew install boost
 #### "ArduinoJson not found"
 
 ```bash
-cd ../../test
+cd ../../../test
 git clone https://github.com/bblanchon/ArduinoJson.git
 ```
 
 #### "TaskScheduler not found"
 
 ```bash
-cd ../../test
+cd ../../../test
 git clone https://github.com/arkhipenko/TaskScheduler
 ```
 
@@ -476,7 +476,7 @@ python3 test/mock-http-server/server.py &
 SERVER_PID=$!
 
 # Build PC node
-cd examples/sendToInternet
+cd examples/sendToInternet/pc_node
 cmake . && make
 
 # Run test (assuming bridge is running at known IP)
@@ -501,10 +501,10 @@ kill $SERVER_PID
 
 ## Related Documentation
 
-- [sendToInternet Example](sendToInternet.ino) - ESP32/ESP8266 example
-- [Mock HTTP Server](../../test/mock-http-server/README.md) - Testing endpoint
-- [Bridge Documentation](../../BRIDGE_TO_INTERNET.md) - Bridge setup guide
-- [Testing Guide](../../test/mock-http-server/TESTING_GUIDE.md) - Complete testing workflow
+- [sendToInternet Example](../sendToInternet.ino) - ESP32/ESP8266 example
+- [Mock HTTP Server](../../../test/mock-http-server/README.md) - Testing endpoint
+- [Bridge Documentation](../../../BRIDGE_TO_INTERNET.md) - Bridge setup guide
+- [Testing Guide](../../../test/mock-http-server/TESTING_GUIDE.md) - Complete testing workflow
 
 ## Credits
 

package/examples/sendToInternet/{build.sh → pc_node/build.sh}

@@ -73,10 +73,10 @@ echo "   - Windows: See https://www.boost.org/"
 echo ""
 echo "Checking test dependencies..."
 
-if [ ! -d "../../test/ArduinoJson/src" ]; then
+if [ ! -d "../../../test/ArduinoJson/src" ]; then
     echo "⚠️  ArduinoJson not found"
     echo "   Cloning ArduinoJson..."
-    cd ../../test
+    cd ../../../test
     if [ -d "ArduinoJson" ]; then
         rm -rf ArduinoJson
     fi
@@ -86,10 +86,10 @@ else
     echo "✓ ArduinoJson found"
 fi
 
-if [ ! -d "../../test/TaskScheduler/src" ]; then
+if [ ! -d "../../../test/TaskScheduler/src" ]; then
     echo "⚠️  TaskScheduler not found"
     echo "   Cloning TaskScheduler..."
-    cd ../../test
+    cd ../../../test
     if [ -d "TaskScheduler" ]; then
         rm -rf TaskScheduler
     fi
@@ -135,7 +135,7 @@ if make 2>&1; then
     echo ""
     echo "Next steps:"
     echo "  1. Start mock HTTP server:"
-    echo "     cd ../../test/mock-http-server && python3 server.py"
+    echo "     cd ../../../test/mock-http-server && python3 server.py"
     echo ""
     echo "  2. Configure and upload bridge to ESP32/ESP8266"
     echo "     (see sendToInternet.ino with IS_BRIDGE_NODE=true)"

package/examples/sendToInternet/{pc_mesh_node.cpp → pc_node/pc_mesh_node.cpp}

@@ -38,6 +38,15 @@
  * - 5555 is the TCP port the bridge is listening on (MESH_PORT)
  **/
 
+// This is a PC-side (desktop) program: it needs Boost and the Arduino
+// emulation layer under test/, neither of which exists for an embedded
+// target. Both the Arduino IDE and arduino-cli compile *every* .cpp in a
+// sketch folder, so without this guard they try to build this file for the
+// ESP and fail on <boost/asio/ip/address.hpp>. ARDUINO is defined by every
+// Arduino toolchain, so the whole file collapses to an empty translation
+// unit there and is left to the CMake/g++ build described above.
+#ifndef ARDUINO
+
 #include <iostream>
 #include <string>
 #include <memory>
@@ -356,6 +365,8 @@ int main(int argc, char* argv[]) {
     node.runUpdateLoop(10);
     
     std::cout << "\n✓ PC Mesh Node shutting down..." << std::endl;
-    
+
     return 0;
 }
+
+#endif  // !ARDUINO

package/examples/sharedGateway/README.md

@@ -225,8 +225,7 @@ WiFi.channel()
 
 ## Related Documentation
 
-- [Shared Gateway Design Document](../../docs/design/SHARED_GATEWAY_DESIGN.md)
-- [Bridge Mode Example](../bridge/README.md)
+- [Bridge Mode Example](../bridge/bridge.ino)
 - [Bridge Failover Example](../bridge_failover/README.md)
 - [painlessMesh Documentation](https://gitlab.com/painlessMesh/painlessMesh/-/wikis/home)
 

package/examples/tcpRetryConfig/README.md

@@ -0,0 +1,110 @@
+# tcpRetryConfig
+
+Tuning painlessMesh's TCP connection retry behaviour with
+`setTcpRetryConfig()` (issue
+[#378](https://github.com/Alteriom/painlessMesh/issues/378)).
+
+## What this controls
+
+When a node acquires an IP and tries to open its TCP connection to the mesh,
+that connection can fail — the parent's TCP server may not be ready yet, the
+network stack may still be settling, or several nodes may be connecting at
+once. painlessMesh retries with exponential backoff before giving up and
+falling back to a full WiFi reconnect.
+
+Five parameters describe that behaviour:
+
+| Field | Default | Meaning |
+|---|---|---|
+| `maxRetries` | 5 | TCP connect attempts after the first before giving up |
+| `retryDelayMs` | 1000 | Base delay between retries; scaled 1x, 2x, 4x, 8x, 8x |
+| `stabilizationDelayMs` | 500 | Wait after IP acquisition before the first attempt |
+| `exhaustionReconnectDelayMs` | 10000 | Wait before the WiFi reconnect that follows exhaustion |
+| `failureBlockDurationMs` | 60000 | How long a failed peer is skipped during AP selection |
+
+With the defaults, a node that cannot reach its parent spends
+1 + 2 + 4 + 8 + 8 = **23 s** retrying, then waits another **10 s** before
+reconnecting WiFi, and will not re-select that same peer for **60 s**.
+
+## Profiles in this sketch
+
+Switch with `#define ACTIVE_PROFILE`.
+
+| | `PROFILE_REALTIME` | default | `PROFILE_RELIABLE` | `PROFILE_BATTERY` |
+|---|---|---|---|---|
+| `maxRetries` | 1 | 5 | 10 | 2 |
+| `retryDelayMs` | 200 | 1000 | 2000 | 3000 |
+| `stabilizationDelayMs` | 100 | 500 | 1000 | 500 |
+| `exhaustionReconnectDelayMs` | 1000 | 10000 | 30000 | 60000 |
+| `failureBlockDurationMs` | 5000 | 60000 | 180000 | 300000 |
+| worst-case retry time | 0.2 s | 23 s | 126 s | 9 s |
+| full failure cycle | 1.2 s | 33 s | 156 s | 69 s |
+
+- **`PROFILE_REALTIME`** — real-time sensor and LED meshes, the use case from
+  [discussion #368](https://github.com/Alteriom/painlessMesh/discussions/368).
+  A node stuck in a 23 s backoff is worse than one that drops and re-scans, so
+  fail fast and move on.
+- **`PROFILE_RELIABLE`** — industrial meshes where getting connected matters
+  more than how long it takes. `maxRetries = 10` is the maximum the library
+  accepts.
+- **`PROFILE_BATTERY`** — every retry is radio-on time. Few attempts, spaced
+  widely, and a long blocklist so the node stops waking up for a peer that is
+  known to be down.
+
+## Clamping
+
+`setTcpRetryConfig()` coerces the two values that can render a node unusable:
+
+- `maxRetries` is capped at **10**. Each retry allocates an `AsyncClient` and
+  schedules a task, so an unbounded value is a heap and recursion-depth hazard
+  on ESP8266.
+- `retryDelayMs` is held between **50 ms** and **60000 ms**. A zero delay would
+  schedule retries with no spacing — a hot loop allocating an `AsyncClient`
+  every scheduler tick. The ceiling keeps `retryDelayMs * 8` clear of `uint32_t`
+  overflow.
+
+Everything else passes through untouched, including zeros, which are
+meaningful:
+
+- `maxRetries = 0` — do not retry at all; fall straight back to a WiFi
+  reconnect on the first TCP error.
+- `stabilizationDelayMs = 0` — attempt the TCP connection immediately on IP
+  acquisition.
+- `exhaustionReconnectDelayMs = 0` — reconnect WiFi immediately after
+  exhaustion.
+- `failureBlockDurationMs = 0` — never blocklist a failed peer.
+
+Call `getTcpRetryConfig()` after setting to see what actually took effect; the
+sketch prints this at startup.
+
+## The defaults exist for a reason
+
+painlessMesh 1.9.x deliberately *raised* these values (retries 3 → 5, base
+delay 500 ms → 1000 ms) to fix real-world mesh instability. Tuning them back
+down reintroduces the problems that change fixed. Symptoms of an over-aggressive
+profile:
+
+- **Connection churn** — nodes repeatedly connect and drop. `maxRetries` is too
+  low for how long your parent actually takes to be ready; raise it or raise
+  `stabilizationDelayMs`.
+- **Rapid reconnect loops / network congestion** — a node hammers a parent whose
+  TCP server is down. `exhaustionReconnectDelayMs` is too short.
+- **The same dead peer is picked over and over** — `failureBlockDurationMs` is
+  shorter than one full retry-plus-reconnect cycle, so the peer comes off the
+  blocklist before the node has finished failing over. Keep
+  `failureBlockDurationMs` greater than
+  `(sum of retry backoffs) + exhaustionReconnectDelayMs`. All three profiles
+  above satisfy this; `catch_tcp_blocklist.cpp` pins it as a test.
+
+Change one parameter at a time and watch the serial log with
+`mesh.setDebugMsgTypes(ERROR | STARTUP | CONNECTION)`.
+
+## Building
+
+```bash
+# PlatformIO
+pio run -e esp32     # or -e esp8266
+
+# Arduino CLI
+arduino-cli compile --fqbn esp32:esp32:esp32 examples/tcpRetryConfig/tcpRetryConfig.ino
+```

package/examples/tcpRetryConfig/platformio.ini

@@ -0,0 +1,26 @@
+[platformio]
+src_dir = .
+
+[env]
+lib_deps =
+    bblanchon/ArduinoJson
+    arkhipenko/TaskScheduler
+
+lib_ldf_mode = deep+
+[env:esp8266]
+platform = espressif8266
+board = nodemcuv2
+framework = arduino
+lib_extra_dirs = ../../
+lib_deps =
+    ${env.lib_deps}  ; Inherit common dependencies
+    esp32async/ESPAsyncTCP@^2.0.0  ; Only for ESP8266
+
+[env:esp32]
+platform = espressif32
+board = esp32dev
+framework = arduino
+lib_extra_dirs = ../../
+lib_deps =
+    ${env.lib_deps}  ; Inherit common dependencies
+    esp32async/AsyncTCP

package/examples/tcpRetryConfig/tcpRetryConfig.ino

@@ -0,0 +1,154 @@
+//************************************************************
+// Tuning the TCP connection retry behaviour (issue #378)
+//
+// painlessMesh retries a failed TCP connection with exponential backoff
+// before giving up and falling back to a full WiFi reconnect. The defaults
+// (5 retries, 1s base delay -> 1s, 2s, 4s, 8s, 8s) are tuned for general
+// purpose meshes and deliberately favour reliability over speed.
+//
+// setTcpRetryConfig() lets you pick a different trade-off. Three ready-made
+// profiles are shown below; switch between them with ACTIVE_PROFILE.
+//
+// Read examples/tcpRetryConfig/README.md before changing these values - the
+// defaults exist because 1.9.x raised them to fix real mesh instability.
+//************************************************************
+#include <painlessMesh.h>
+
+#define   MESH_SSID       "whateverYouLike"
+#define   MESH_PASSWORD   "somethingSneaky"
+#define   MESH_PORT       5555
+
+// ---------------------------------------------------------------------------
+// Profiles
+// ---------------------------------------------------------------------------
+#define PROFILE_REALTIME  1   // low latency: fail fast, reconnect fast
+#define PROFILE_RELIABLE  2   // industrial: many retries, long backoff
+#define PROFILE_BATTERY   3   // conserve power: few retries, long block
+
+// >>> Change this line to try a different profile <<<
+#define ACTIVE_PROFILE    PROFILE_REALTIME
+
+// Prototypes
+void sendMessage();
+void receivedCallback(uint32_t from, String &msg);
+void newConnectionCallback(uint32_t nodeId);
+void droppedConnectionCallback(uint32_t nodeId);
+
+Scheduler     userScheduler;
+painlessMesh  mesh;
+
+Task taskSendMessage(TASK_SECOND * 5, TASK_FOREVER, &sendMessage);
+
+// Build the retry configuration for the selected profile.
+painlessmesh::tcp::TcpRetryConfig buildRetryConfig() {
+  painlessmesh::tcp::TcpRetryConfig cfg;  // starts at the library defaults
+
+#if ACTIVE_PROFILE == PROFILE_REALTIME
+  // Real-time sensor / LED meshes: a stalled node is worse than a dropped
+  // one. Give up on the TCP handshake almost immediately and go straight
+  // back to scanning for another parent.
+  cfg.maxRetries = 1;                    // default 5
+  cfg.retryDelayMs = 200;                // default 1000
+  cfg.stabilizationDelayMs = 100;        // default 500
+  cfg.exhaustionReconnectDelayMs = 1000; // default 10000
+  cfg.failureBlockDurationMs = 5000;     // default 60000
+
+#elif ACTIVE_PROFILE == PROFILE_RELIABLE
+  // Industrial / high-reliability meshes: connectivity matters more than
+  // how long it takes to get there. Retry patiently and keep a failed peer
+  // out of the running for a good while.
+  cfg.maxRetries = 10;                     // default 5 (this is the maximum)
+  cfg.retryDelayMs = 2000;                 // default 1000
+  cfg.stabilizationDelayMs = 1000;         // default 500
+  cfg.exhaustionReconnectDelayMs = 30000;  // default 10000
+  // Must exceed one full failure cycle (126s of retries + 30s reconnect),
+  // otherwise a dead peer leaves the blocklist before we finished failing
+  // over and gets re-selected immediately.
+  cfg.failureBlockDurationMs = 180000;     // default 60000
+
+#elif ACTIVE_PROFILE == PROFILE_BATTERY
+  // Battery-powered nodes: every retry is radio time. Few attempts, spaced
+  // widely, and a long blocklist so we do not keep waking up for a peer
+  // that is known to be down.
+  cfg.maxRetries = 2;                      // default 5
+  cfg.retryDelayMs = 3000;                 // default 1000
+  cfg.stabilizationDelayMs = 500;          // default 500
+  cfg.exhaustionReconnectDelayMs = 60000;  // default 10000
+  cfg.failureBlockDurationMs = 300000;     // default 60000
+
+#else
+  #error "ACTIVE_PROFILE must be one of PROFILE_REALTIME, PROFILE_RELIABLE, PROFILE_BATTERY"
+#endif
+
+  return cfg;
+}
+
+void setup() {
+  Serial.begin(115200);
+
+  mesh.setDebugMsgTypes(ERROR | STARTUP | CONNECTION);
+
+  // Apply the retry configuration BEFORE init() so the very first connection
+  // attempt already uses it.
+  mesh.setTcpRetryConfig(buildRetryConfig());
+
+  mesh.init(MESH_SSID, MESH_PASSWORD, &userScheduler, MESH_PORT);
+
+  // Read the configuration back. Values outside safe operating bounds are
+  // clamped by the setter, so this prints what is actually in effect - not
+  // necessarily what was requested.
+  painlessmesh::tcp::TcpRetryConfig active = mesh.getTcpRetryConfig();
+  Serial.println();
+  Serial.println(F("Effective TCP retry configuration:"));
+  Serial.printf("  maxRetries                 = %u\n",
+                (unsigned)active.maxRetries);
+  Serial.printf("  retryDelayMs               = %u\n",
+                (unsigned)active.retryDelayMs);
+  Serial.printf("  stabilizationDelayMs       = %u\n",
+                (unsigned)active.stabilizationDelayMs);
+  Serial.printf("  exhaustionReconnectDelayMs = %u\n",
+                (unsigned)active.exhaustionReconnectDelayMs);
+  Serial.printf("  failureBlockDurationMs     = %u\n",
+                (unsigned)active.failureBlockDurationMs);
+
+  // Worst-case time spent retrying before falling back to a WiFi reconnect.
+  uint32_t worstCase = 0;
+  for (uint8_t i = 0; i < active.maxRetries; ++i) {
+    worstCase += painlessmesh::tcp::retryBackoffDelay(active, i);
+  }
+  Serial.printf("  -> worst-case retry time   = %u ms\n", (unsigned)worstCase);
+  Serial.printf("  -> plus reconnect delay    = %u ms\n",
+                (unsigned)(worstCase + active.exhaustionReconnectDelayMs));
+  Serial.println();
+
+  mesh.onReceive(&receivedCallback);
+  mesh.onNewConnection(&newConnectionCallback);
+  mesh.onDroppedConnection(&droppedConnectionCallback);
+
+  userScheduler.addTask(taskSendMessage);
+  taskSendMessage.enable();
+}
+
+void loop() {
+  mesh.update();
+}
+
+void sendMessage() {
+  String msg = "Hello from node ";
+  msg += mesh.getNodeId();
+  mesh.sendBroadcast(msg);
+}
+
+void receivedCallback(uint32_t from, String &msg) {
+  Serial.printf("tcpRetryConfig: Received from %u msg=%s\n", from, msg.c_str());
+}
+
+void newConnectionCallback(uint32_t nodeId) {
+  Serial.printf("--> Connected to node %u\n", nodeId);
+}
+
+void droppedConnectionCallback(uint32_t nodeId) {
+  // With an aggressive profile you should expect to see this more often -
+  // and to see the reconnect that follows it happen much sooner.
+  Serial.printf("--> Dropped connection to node %u\n", nodeId);
+}

package/keywords.txt

@@ -4,6 +4,8 @@
 painlessMesh	KEYWORD1
 Scheduler	KEYWORD1
 Task	KEYWORD1
+TcpRetryConfig	KEYWORD1
+SendOptions	KEYWORD1
 
 # Methods and Functions (KEYWORD2)
 init	KEYWORD2
@@ -18,11 +20,57 @@ getNodeList	KEYWORD2
 getNodeId	KEYWORD2
 getNodeTime	KEYWORD2
 setDebugMsgTypes	KEYWORD2
+checkAcks	KEYWORD2
+pendingAcks	KEYWORD2
+setTcpRetryConfig	KEYWORD2
+getTcpRetryConfig	KEYWORD2
+stop	KEYWORD2
+isConnected	KEYWORD2
+subConnectionJson	KEYWORD2
+startDelayMeas	KEYWORD2
+onNodeDelayReceived	KEYWORD2
+setRoot	KEYWORD2
+setContainsRoot	KEYWORD2
+isRoot	KEYWORD2
+stationManual	KEYWORD2
+setHostname	KEYWORD2
+initAsBridge	KEYWORD2
+initAsSharedGateway	KEYWORD2
+isBridge	KEYWORD2
+setRouterCredentials	KEYWORD2
+enableBridgeFailover	KEYWORD2
+onBridgeRoleChanged	KEYWORD2
+onBridgeStatusChanged	KEYWORD2
+onGatewayChanged	KEYWORD2
+setElectionStartupDelay	KEYWORD2
+setElectionRandomDelay	KEYWORD2
+setElectionTimeout	KEYWORD2
+setMinimumBridgeRSSI	KEYWORD2
+setBridgeStatusInterval	KEYWORD2
+setBridgeTimeout	KEYWORD2
+hasInternetConnection	KEYWORD2
+hasLocalInternet	KEYWORD2
+getBridges	KEYWORD2
+getPrimaryBridge	KEYWORD2
+getPrimaryGateway	KEYWORD2
+enableSendToInternet	KEYWORD2
+sendToInternet	KEYWORD2
+enableMessageQueue	KEYWORD2
+queueMessage	KEYWORD2
+flushMessageQueue	KEYWORD2
+getQueueStats	KEYWORD2
+initOTASend	KEYWORD2
+initOTAReceive	KEYWORD2
+overCapacity	KEYWORD2
+apChildren	KEYWORD2
+getTcpRetryConfig	KEYWORD2
 subConnectionJson	KEYWORD2
 asNodeTree	KEYWORD2
 
 # Alteriom Extensions (KEYWORD1)
 SensorPackage	KEYWORD1
+MessageAckPackage	KEYWORD1
+deliveryCallback_t	KEYWORD1
 CommandPackage	KEYWORD1
 StatusPackage	KEYWORD1
 
@@ -46,4 +94,8 @@ COMMUNICATION	LITERAL1
 GENERAL	LITERAL1
 MSG_TYPES	LITERAL1
 REMOTE	LITERAL1
-DEBUG	LITERAL1
+DEBUG	LITERAL1
+PRIORITY_CRITICAL	LITERAL1
+PRIORITY_HIGH	LITERAL1
+PRIORITY_NORMAL	LITERAL1
+PRIORITY_LOW	LITERAL1

package/library.json

@@ -6,7 +6,7 @@
     "type": "git",
     "url": "https://github.com/Alteriom/painlessMesh"
   },
-  "version": "1.9.20",
+  "version": "2.0.0",
   "frameworks": [
     "arduino"
   ],
@@ -87,13 +87,15 @@
     "examples/namedMesh/namedMesh.ino",
     "examples/otaReceiver/otaReceiver.ino",
     "examples/otaSender/otaSender.ino",
-    "examples/alteriom/mppt_example/alteriom_mppt_example.ino",
-    "examples/priority/priority_basic_example.ino",
-    "examples/priority/priority_with_queue.ino",
-    "examples/sendToInternet/mock_server_test.ino",
+    "examples/alteriom/mppt_example/mppt_example.ino",
+    "examples/priority/priority_basic_example/priority_basic_example.ino",
+    "examples/priority/priority_with_queue/priority_with_queue.ino",
+    "examples/sendToInternet/mock_server_test/mock_server_test.ino",
     "examples/sendToInternet/sendToInternet.ino",
     "examples/sharedGateway/sharedGateway.ino",
     "examples/startHere/startHere.ino",
-    "examples/webServer/webServer.ino"
+    "examples/webServer/webServer.ino",
+    "examples/commandControl/commandControl.ino",
+    "examples/reliableSensorLogging/reliableSensorLogging.ino"
   ]
 }

package/library.properties

@@ -1,5 +1,5 @@
 name=Alteriom PainlessMesh
-version=1.9.20
+version=2.0.0
 author=Coopdis,Scotty Franzyshen,Edwin van Leeuwen,Germán Martín,Maximilian Schwarz,Doanh Doanh,Alteriom
 maintainer=Alteriom
 sentence=A painless way to setup a mesh with ESP8266 and ESP32 devices with Alteriom extensions
@@ -8,4 +8,4 @@ category=Communication
 url=https://github.com/Alteriom/painlessMesh
 architectures=esp8266,esp32
 includes=painlessMesh.h,AlteriomPainlessMesh.h
-depends=ArduinoJson, TaskScheduler
+depends=ArduinoJson, TaskScheduler, PubSubClient

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alteriom/painlessmesh",
-  "version": "1.9.20",
+  "version": "2.0.0",
   "description": "painlessMesh is a user-friendly library for creating mesh networks with ESP8266 and ESP32 devices. This Alteriom fork includes additional packages for sensor data (SensorPackage), device commands (CommandPackage), and status monitoring (StatusPackage). It handles routing and network management automatically, so you can focus on your application. The library uses JSON-based messaging and syncs time across all nodes, making it ideal for coordinated behaviour like synchronized light displays or sensor networks reporting to a central node.",
   "keywords": [
     "arduino",
@@ -41,9 +41,9 @@
   "devDependencies": {
     "@alteriom/mqtt-schema": "^0.8.0",
     "@eslint/js": "^10.0.1",
-    "ajv": "^8.17.1",
+    "ajv": "^8.20.0",
     "ajv-formats": "^3.0.1",
-    "prettier": "^3.8.1"
+    "prettier": "^3.9.6"
   },
   "scripts": {
     "test": "run-parts --regex catch_ bin/ || echo 'Tests completed'",

package/src/AlteriomPainlessMesh.h

@@ -29,10 +29,10 @@
 /**
  * @brief AlteriomPainlessMesh library version information
  */
-#define ALTERIOM_PAINLESS_MESH_VERSION "1.9.20"
-#define ALTERIOM_PAINLESS_MESH_VERSION_MAJOR 1
-#define ALTERIOM_PAINLESS_MESH_VERSION_MINOR 9
-#define ALTERIOM_PAINLESS_MESH_VERSION_PATCH 20
+#define ALTERIOM_PAINLESS_MESH_VERSION "2.0.0"
+#define ALTERIOM_PAINLESS_MESH_VERSION_MAJOR 2
+#define ALTERIOM_PAINLESS_MESH_VERSION_MINOR 0
+#define ALTERIOM_PAINLESS_MESH_VERSION_PATCH 0
 
 /**
  * @brief Library description and usage information