As a member of the EnOcean Alliance, we have developed a standardized OTA update mechanism for devices using the EnOcean protocol. OTA updates are essential for maintaining devices deployed in the field, particularly in locations where direct access is limited or impractical. This is especially relevant for energy-harvesting devices, which are often installed in places where servicing is costly or difficult.
The framework provides a consistent method for delivering firmware updates across different EnOcean-based projects. Instead of building a new OTA mechanism for each device type, a universal approach can be applied. This standardization improves reliability, as the update process is based on a tested and repeatable method. It also reduces the likelihood of errors that may occur with ad-hoc solutions.
By minimizing the need for custom development, the framework simplifies integration into existing workflows, and shortens the time required to bring devices to market. At the same time, it supports the long-term maintainability of deployed systems by enabling secure and efficient updates throughout the device lifecycle.
As an experienced embedded development company, WizzDev supports clients from prototype to production.
Our expertise covers hardware, firmware, and cloud integration — giving you a single partner for the entire development process.
As one of the trusted embedded systems development companies, and a proven embedded firmware company, we deliver more than code — we deliver connected ecosystems.
With AWS Partner status, we design cloud-ready architectures that grow with your business. Our agile team adapts quickly, solves technical bottlenecks, and helps you launch faster with fewer risks.
From the beginning, this project was not about experimenting with different approaches, but about following the specification provided by EnOcean. Our task was to prepare a reference implementation that could serve as part of a universal OTA standard for EnOcean devices. That meant every design decision had to stay aligned with the rules set in the documentation, even when it added extra constraints.
We built the demo in pure C, keeping it minimal: two programs in two files. The source device takes a file, splits it, and sends it over the air. The destination device receives the stream and reassembles it — all while simulating the limitations of an energy-harvesting node. Because such devices have very limited power and processing resources, the communication protocol had to be designed to place almost no extra burden on the receiver.
According to the specification, the file is divided into 8-byte packets, grouped into 256-byte blocks (32 messages each). After each block, the receiver performs an integrity check by validating one randomly selected byte. This lightweight method keeps the load low while maintaining reliability. Transmission speed is limited to about 80 bytes per second, which is sufficient for firmware updates in constrained energy conditions.
Since the channel is wireless, we had to account for packet loss and interference. We introduced mechanisms for retransmission and safe reassembly. With these in place, the destination can reconstruct the full file with a success rate of around 99.99%. At this demo stage, some steps are still handled in software. The final version, however, will shift more of the workload into hardware. This is not yet a production-ready system, but it is one of the first working examples of the emerging OTA standard for EnOcean devices.
The process starts with the complete file.
File is grouped into 256-byte blocks, then split into 32 x 8-byte packets.
Packets are sent over the air at ~80 bytes/sec.
Energy Harvesting Device receives and reassembles packets into a block.
After each block, one random byte is validated to ensure reliability.
As a Poland-based embedded development company (CET), we share time zones with European clients — making daily updates and sprint reviews smooth.
We use Jira and agile methods to track progress, milestones, and deliverables. You always see where the project stands.
We hand over source code, documentation, and test procedures, ensuring you stay in control long after delivery.
Whether it’s embedded system software development or complete IoT ecosystems, once the scope is defined and NDA signed, we move directly into execution without delays.









Chief Executive Officer
With over a decade in embedded systems development and connected products. I’ve helped bring to market everything from diagnostic devices and smart thermostats to large-scale sensor networks. At WizzDev, we know the real challenges start when hardware meets the real world—tight deadlines, noisy data, certification hurdles, and integration bottlenecks. That’s why we work side by side with tech leads and product managers to unblock projects, stabilize firmware, streamline cloud integration, and deliver reliable, scalable solutions that make it to market on time.
Chief Executive Officer
With over a decade in embedded systems development and connected products. I’ve helped bring to market everything from diagnostic devices and smart thermostats to large-scale sensor networks. At WizzDev, we know the real challenges start when hardware meets the real world—tight deadlines, noisy data, certification hurdles, and integration bottlenecks. That’s why we work side by side with tech leads and product managers to unblock projects, stabilize firmware, streamline cloud integration, and deliver reliable, scalable solutions that make it to market on time.