The latest articles on DEV Community by itzdev691 (@itzdev691). https://dev.to/itzdev691 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4162226%2F455e04bd-ad6a-4785-a642-533b5af15dbf.png https://dev.to/itzdev691 en itzdev691 Sun, 04 Oct 2026 17:57:06 +0000 https://dev.to/itzdev691/im-building-vaydenet-an-embedded-communication-framework-testers-wanted-3kb1 https://dev.to/itzdev691/im-building-vaydenet-an-embedded-communication-framework-testers-wanted-3kb1 <p>Switching radios often means rewriting communication code. I’m building <strong>VaydeNet</strong> to make that easier: a shared communication layer that keeps application logic separate from the underlying transport.</p> <p>The long-term goal is to support technologies such as ESP-NOW, LoRa, Bluetooth, Wi-Fi, and Ethernet through a consistent interface.</p> <p><strong>The current prototype focuses on ESP32 and ESP-NOW.</strong> Its portable C++ engine validates packets, decodes incoming messages, delivers them to application code, and handles outgoing broadcast messages. The project is open source under Apache 2.0.</p> <p>It’s still early. Broader transport support, routing, retries, and acknowledgements remain development work.</p> <h2> Help test the current prototype </h2> <p>I’m looking for developers who can try the setup instructions, build the firmware, test communication between boards, or review the engine’s interfaces.</p> <p>Useful feedback includes:</p> <ul> <li> <strong>Setup problems:</strong> missing dependencies, confusing instructions, or failed builds.</li> <li> <strong>Hardware results:</strong> whether firmware boots and messages reach another board.</li> <li> <strong>Integration friction:</strong> difficulty using the engine in an existing application.</li> <li> <strong>Bugs:</strong> reproducible crashes, unexpected behavior, or unclear error results.</li> </ul> <p>No hardware is required to contribute useful feedback. The repository includes host tests, and documentation feedback helps make the project easier to use.</p> <h2> Getting started </h2> <p>Start with the <a href="https://github.com/itzdev691/VaydeNet#readme" rel="noopener noreferrer">README</a> and <a href="https://github.com/itzdev691/VaydeNet/blob/main/DEVELOPMENT_STATUS.md" rel="noopener noreferrer">development status</a>, then follow the instructions for your board or run the host tests.</p> <p>Report results through <a href="https://github.com/itzdev691/VaydeNet/issues" rel="noopener noreferrer">GitHub Issues</a>. Include your board, operating system, branch or commit, reproduction steps, and expected versus observed behavior. For communication tests, include what the receiving device actually observed.</p> <p>A failed build or confusing setup step is useful feedback too. Testing at this stage will help shape both the implementation and the developer experience.</p> <p><strong>Repository:</strong> <a href="https://github.com/itzdev691/VaydeNet" rel="noopener noreferrer">itzdev691/VaydeNet</a></p> opensource iot cpp python