WIFI Switch with ESP32 using MQTT

@Mahihassi

With over a decade of experience as an electrical engineer specializing in firmware development and IoT product engineering, I am well-versed in providing full-stack solutions for demanding projects such as yours. I hold extensive knowledge in microcontrollers and embedded systems, particularly with the ESP32 you're using, making me swiftly adaptable to your project-specific setup. Having worked with MQTT, Wi-Fi, GPIO, and storage systems before, I am already familiar with the high-level logic you need to tie everything together seamlessly. My skills also encompass building robust schedules and incorporating on-demand timers along with event logging to handle local and networked operations gracefully. With my background in PCB design and RF hardware, I'll ensure your custom board's integrity is maintained while implementing clean and modular code structures. This will make future expansion or modification significantly easier for you. Offering not just my software capabilities but a holistic approach to product development, I can also complement this project by creating mobile or web applications that optimize control functionality from real-time dashboards to AI-powered analytics. Meeting deadlines is a core competence of mine too; rest assured that I am well-prepared to start right away and deliver your well-documented solution promptly. Reach out to a proficient freelancer who can truly add value to your project; let's build your intelligent Wi-Fi switch together.

@elect2eng

I have done this kind of project for multiple clients earlier. It was using mqtt to communicate with the broker. It is not becoming clear as how you want to integrate your mobile app with this equipment. does mobile app send the data over mqtt or google firebase database? Please send me the circuit diagram or GPIO details for push button

@nehasingh17

Hi, We at HardFault can help you complete the high-level logic and scheduler layer for your ESP32 PlatformIO project. Since your low-level drivers for Wi-Fi, MQTT, GPIO, and storage are already working, we can directly focus on building the intelligent application layer — MQTT JSON command parsing, relay control with acknowledgement timestamps, offline event logging + sync, persistent daily/weekly scheduling, on-demand timer control, and clean modular state-machine architecture. We have experience with ESP32, MQTT-based IoT systems, scheduling logic, local persistence, and reliable embedded firmware design. We’ll keep the code well-structured, easy to extend, and organize all configurable parameters (topics, pins, debounce, timers, etc.) in one place for quick updates. Since this is time-sensitive, we are ready to start immediately. One quick question — are you already using an RTC/NTP sync for timestamps, or should we integrate a reliable fallback mechanism for schedule accuracy after reboot/network loss?

@Webslinger01

I have built and deployed ESP32 IoT systems with MQTT, relay control, JSON command handling, and persistent scheduling before — including a cold storage monitoring system with ESP32, MQTT pub/sub, relay automation, and offline event buffering. Platform IO, Arduino Json, and NVS-backed storage are my regular workflow. I have ESP32 boards in stock and can validate the logic on real hardware in my lab before delivery. I will write only the state-machine and scheduler layer on top of your existing drivers: • MQTT subscriber: Arduino Json command parse → relay execute → ACK publish with timestamp • Button handler: debounced ISR, timestamped event stored to NVS queue, flushed to broker on reconnect — no events lost • Scheduler: daily + weekly cron-style entries parsed from JSON, stored in NVS, auto-resume after power loss • On-demand timer: activated via MQTT topic, cancellable mid-run • All constants (topics, pins, debounce, etc.) in a single config header Delivery in 2 days: full Platform IO source tree, well-commented, ready to compile and flash. Please share the existing project repo so I can review your driver interfaces before writing the integration layer.

@soniaer987

Hi, I've worked with ESP32, PlatformIO, and MQTT-based IoT projects before, so I understand exactly what you need just the high-level logic layer, not a rewrite from scratch. I'll integrate cleanly with your existing drivers and implement: JSON command parsing over MQTT, relay control with acknowledgement publishing, push-button event logging with offline storage and sync, daily/weekly scheduler that survives power loss, and on-demand timer via MQTT topic. All constants will be grouped in one config header for easy maintenance, and the code will be modular and well-commented. Since your boilerplate is already in place, I can get straight to work and deliver the complete PlatformIO source tree quickly. Ready to start immediately. Want to connect?

@ThynkLoop

Hi, I can help you develop the high-level application logic for your ESP32-based Wi-Fi switch using the existing PlatformIO project and low-level drivers. I have experience with ESP32 firmware development, MQTT-based IoT systems, JSON command parsing, scheduler/state-machine implementation, and persistent storage handling. I can deliver clean, modular, and well-commented firmware optimized for reliability and future scalability. > Proposed Approach: MQTT, Relay Control * MQTT topic subscription and JSON parsing * Immediate relay ON/OFF execution * Acknowledgement publishing with timestamps Scheduler, Timer Logic * Daily and weekly scheduling support * Persistent storage for schedule recovery after reboot * On-demand timer activation through MQTT commands Event Handling * Push-button monitoring with debounce handling * Offline event storage and retry synchronization * Reliable state-machine architecture Firmware Structure * Modular code organization * Centralized configuration/constants management * Easy future extensibility > Scope: * MQTT command logic * Scheduler and timer engine * Event storage/sync system * Relay state management * PlatformIO project integration > Deliverables: * Full PlatformIO source code * Well-commented firmware * Documentation and build instructions * Working scheduler and MQTT logic

@sahilgoti

I can implement the complete high-level automation layer on top of your existing ESP32 PlatformIO stack without modifying your working low-level drivers. The solution will include: MQTT JSON command parsing Immediate relay execution + acknowledgement publishing Persistent offline event queue for button/manual actions Daily and weekly scheduling with reboot recovery On-demand timer activation from MQTT Modular non-blocking architecture using millis() Persistent schedule storage using your existing storage layer Automatic MQTT reconnect recovery and event replay I will structure the firmware into isolated modules (scheduler, timer manager, relay controller, event queue, command parser, persistence layer) so future features can be added without rewriting the core logic. The final delivery will include the full PlatformIO source tree with clean comments and integration into your existing MQTT/storage helpers. I can start immediately.

@OyebisiHakeeem

Hello, You already have the low-level drivers and infrastructure in place, so what you need now is a reliable application layer that cleanly coordinates MQTT communication, state handling, scheduling, and persistence into a coherent system. I will implement a structured state-machine that handles MQTT JSON parsing, immediate relay control with acknowledgements, and a robust event logging mechanism that buffers button-triggered actions locally and syncs them once connectivity is restored. For the scheduling, I’ll design a persistent daily/weekly scheduler with RTC-based timing that resumes seamlessly after resets, along with an on-demand timer handler triggered via MQTT, all integrated cleanly with your existing storage and MQTT helpers. The focus will be on modularity and maintainability: separating scheduler logic, command handling, and hardware interaction, while centralizing configuration (topics, GPIOs, debounce, timing). This makes future changes straightforward without touching core logic. Tradeoff-wise, a more structured state-machine and persistent scheduler adds a bit of code complexity and memory overhead, but it significantly improves reliability, debuggability, and long-term scalability—which is important for a device expected to run continuously. I’ll deliver a clean PlatformIO project that you can compile and extend easily.

@chetanb382

Hello, I have strong experience with ESP32 firmware development, MQTT-based IoT systems, PlatformIO projects, JSON handling, automation logic, and embedded scheduling systems. Since your low-level drivers and infrastructure are already implemented, I can focus on building the clean high-level application layer required for the intelligent Wi-Fi switch behavior. My approach: • MQTT JSON command parsing and acknowledgement handling • Relay state-machine and manual button integration • Daily and weekly scheduler implementation with persistent storage • Offline event logging and automatic MQTT re-sync after reconnection • Configurable on-demand timer handling • Modular and maintainable PlatformIO code structure for future expansion Deliverables: • Full updated PlatformIO source tree • Well-commented and modular firmware • Scheduler and storage integration • Setup/testing notes and documentation Timeline: 5-6 Days Budget: ₹10000 INR Before starting, please confirm: 1. Which time synchronization method is currently used (NTP, RTC, server time, etc.)? 2. Which MQTT library/framework is already integrated in the project? 3. Is persistent storage currently handled through Preferences/NVS, SPIFFS, or another storage layer? I am ready to start immediately and can work closely with your existing project structure.

@Hemakanth56

Hi, I can build exactly what you need - the state machine, scheduler, button monitor with offline buffering, on-demand timer, and MQTT command handler - on top of your existing drivers, delivered as a clean PlatformIO /ESP-IDF project. Quick summary of what I'll deliver: • MQTT JSON parser → relay control → timestamped ACK • Button events stored locally, flushed to broker on reconnect • Daily/weekly schedules persisted to NVS, auto-resume after power loss • On-demand MQTT timer with cancel support • Single config.h for all constants • Fully commented, modular code — easy to extend Fixed price: 8000 INR| Timeline: 2–3 days | Starts immediately If you can share view-only access to the existing project first, I can confirm the driver interfaces and guarantee no integration surprises.

@puppalav6

Hi there, I can step in immediately to build the application and scheduling layer for your ESP32-D switch. Having architected robust ESP32 firmware bridging local networks to cloud backends via MQTT, I am highly familiar with writing non-blocking state machines that handle network drops gracefully. Since your low-level drivers are operational, my focus is delivering a modular layer using FreeRTOS tasks and queues for maximum responsiveness. My approach: • Command Execution: Decoupled architecture where MQTT JSON payloads are parsed (ArduinoJson) and passed to the control loop via FreeRTOS queues for immediate relay execution and ACK publishing without blocking the network. • Offline Queueing: GPIO triggers debounced via hardware interrupts. If disconnected, events are serialized into a circular buffer in NVS/LittleFS. A sync task publishes this backlog chronologically upon reconnection. • Persistent Scheduling: Unix Epoch time synced via NTP. JSON schedules are parsed into trigger structs and saved to NVS. On boot, the ESP32 reloads and evaluates them non-blocking, ensuring resumption after power loss. • Code Structure: Configurations centralized in config.h. Logic strictly separated into .cpp/.h modules. I can review your PlatformIO repository and begin today. You will receive a fully commented, compilable source tree. Let's connect! Best, Puppala Veerendra

@vikram7420

Hello, I am an Electronics Engineering student with experience in ESP32, MQTT communication, embedded systems, and automation projects. I have worked on IoT-based projects including RFID systems, smart automation, and ESP32 applications. I can develop the high-level logic for your WiFi switch by integrating MQTT command handling, relay control, JSON parsing, scheduling, timer functionality, offline event storage, and synchronization with the broker. I understand the importance of reliable scheduling, persistent storage after reboot, and clean modular code structure for future scalability. I am comfortable working with PlatformIO and can integrate smoothly with your existing drivers and boilerplate code. The code will be well-structured, commented, and easy to modify. I am ready to start immediately and can deliver the complete working source within the required timeline.

@mihawarp

Hello, I would like to develop such of IoT project. Have experience in programming with C/C++ various ESP32 boards, that also include some cloud technologies. We can discuss more details via chat.

@sudipembedded

Hello, I am interested in your ESP32 Wi-Fi switch project and can start immediately. I have strong experience with ESP32, PlatformIO, MQTT, JSON parsing, IoT automation, and embedded firmware development. I can implement the complete high-level logic layer for your existing project, including: MQTT topic subscription and JSON command handling Relay ON/OFF execution with timestamped acknowledgements Push-button monitoring with debounce logic Local offline event storage and MQTT sync after reconnection Daily and weekly scheduling with persistent storage MQTT-triggered on-demand timer control Clean modular code structure with centralized configuration settings My approach will use a reliable non-blocking state-machine architecture so scheduling, MQTT communication, and button handling run smoothly together. I have previously developed: ESP32 MQTT automation systems Smart relay and home automation controllers Offline event logging systems PlatformIO-based embedded applications You will receive: Fully working PlatformIO source tree Well-commented and maintainable code Integrated scheduler and timer logic Build-ready project for flashing and testing I understand the project is time-sensitive and am ready to begin immediately for quick delivery. Best regards, Sudip Chakraborty

@paulpham93

Hi, I've read your spec - the state-machine and scheduler layer for an ESP32-D Wi-Fi switch with MQTT commands, button event buffering, persistent daily and weekly schedules, and an on-demand timer, on top of your existing drivers. This sits well within what I handle regularly. Areas that map to your project: - Firmware in C/C++ for ESP32 on PlatformIO - MQTT with JSON command parsing and acknowledgement - State-machine and scheduler design for embedded applications - Persistent storage for event buffering and schedule survival Scope I would take on: the MQTT command handling layer, the scheduling module covering daily, weekly, and on-demand timers, the button event handling with offline buffering, a centralized configuration module, and integration with your existing MQTT and storage helpers. I have specific approaches in mind for each part, but would rather lock those in once we've gone through the existing project. Deliverables: the full PlatformIO source tree ready to compile and flash, with well-commented modular code and clear separation between new logic and existing drivers. Quick note: I have delivered 230+ firmware and hardware projects across previous platforms with a 5-star average, recently migrated to Freelancer.com so my profile here is still growing. Happy to discuss budget once we align on scope, and ready to start right away. Best, Paul

@scia13

ESP32 developer ready to build your PlatformIO state machine. I'll deliver clean, modular C++ code with offline MQTT logging and persistent JSON scheduling. Ready to start immediately.

@kiennguyen64

Hi, I have solid experience with ESP32, PlatformIO, MQTT, and IoT state-machine/scheduler development. I can quickly implement the high-level logic for your Wi-Fi switch, including MQTT JSON handling, relay control, offline event logging/sync, persistent daily & weekly schedules, and on-demand timers. Clean, modular, well-commented code with full PlatformIO source delivery. Ready to start immediately.