Battery-free IoT sensors can reduce reliance on routine battery replacement, but they require a system-level approach to energy use. A sensor node must gather energy, store enough to operate, take measurements and communicate results while working within a limited power budget. For industrial automation engineers and system integrators, the central design question is not simply which harvester to use; it is how the complete sensing and communication cycle fits the available energy.
A solar-powered reference design built around a low-power Bluetooth Low Energy (BLE) radio illustrates the key considerations. Its principles apply to other wireless sensor nodes as well: select efficient components, accumulate energy between transmissions, and make measurement and reporting intervals responsive to what the system can support.
Battery-free IoT sensors depend on the whole power budget
An IoT node needs energy for more than the sensor itself. The microcontroller, radio, power management, storage losses and any supporting circuitry all affect how long the node can operate between energy-gathering opportunities. Components should therefore be evaluated together, including their active, standby and deep-sleep behavior.
Wireless communication is often a brief but relatively demanding event. The reference design describes a transmission that may draw about 10 mA for up to 10 milliseconds. A low duty cycle lets the harvester collect energy for much longer than the radio uses it: harvesting for one second before a 10-millisecond transmission gives a 100-to-1 time ratio, while harvesting for 10 seconds before a 5-millisecond transmission gives a 2,000-to-1 ratio. These ratios describe time available for accumulation, not a guarantee of system performance; actual feasibility depends on illumination, energy consumption and storage.
Protocols such as BLE and Zigbee Green Power support short, low-power transmissions. Protocol selection should also account for range, security, receiver behavior, hardware integration, interoperability and implementation cost. The best fit depends on the application and its gateway or receiving infrastructure.
Choosing an energy harvester and operating interval
Indoor solar harvesting may provide enough energy for sensors that report slowly changing conditions, provided the light level and duty cycle suit the application. The design example considers a solar cell producing 16 microamps at 200 lux or 80 microamps at 1,000 lux. Against a radio transmission current of approximately 10 mA, the design uses the time between transmissions to accumulate energy. It describes a potential operating interval of one to 10 seconds under its intended conditions.
Illumination varies considerably with location, time, weather and sensor orientation. A window-side sensor, an office desk and a corridor can receive different light levels, even within the same building. Designers should assess the actual installation environment rather than assume a single indoor-light condition. Where light is insufficient or unavailable for extended periods, a battery may be more appropriate than a capacitor-only approach.
Capacitor storage, startup and voltage regulation
Capacitors can store harvested energy for near-term use and may simplify a design that does not need to operate through long periods without light. Compared with batteries, they generally store less energy for a given volume. Batteries can support longer operation without harvesting, but add requirements such as charge and discharge management and cell protection.
A capacitor-based node still needs its supply voltage managed. The capacitor voltage changes as it charges and discharges, while sensors and microcontrollers have defined operating ranges. Regulation can stabilize the supply, and a voltage limit can protect components when the harvester’s open-circuit voltage is higher than the electronics can accept. In the described design, a diode prevents the storage capacitor from discharging back through the harvester.
Startup is a distinct challenge. If the controller begins operating before the capacitor has enough stored energy, its initial power draw may pull the voltage below the level needed to keep it running. A startup circuit can hold the electronics off until the capacitor reaches a threshold, then disable them again if voltage falls too low. The example uses a voltage supervisor to enable operation after the storage voltage reaches 2.63 V, with the supply switching off near 1.5 V. Its measured startup energy and operating voltage range informed the capacitor sizing, with additional capacitance needed to allow for component tolerances, temperature and aging.
Firmware makes harvesting work in practice
Hardware establishes the available energy budget; firmware decides how to use it. An energy-aware node can check its supply voltage, defer a measurement when energy is insufficient, and enter deep sleep while the storage element recharges. When enough energy is available, it can power the sensors, collect readings, prepare a packet, transmit and return to a low-power state.
In the reference design, sensors communicate with the controller over I2C and can use sleep modes. Some can monitor conditions independently and wake the controller through an interrupt when a configured event occurs. This can avoid keeping the controller active unnecessarily. Turning off sensor power when measurements are not required can further reduce consumption.
BLE advertising offers a way to broadcast readings without establishing and maintaining a connection. That can reduce communication overhead, but advertising payload capacity is limited, and custom sensor data may require a receiving application that knows how to interpret it. In managed industrial deployments, the receiving software and gateway can be controlled as part of the system; deployments involving equipment from multiple vendors should consider interoperability and data-format requirements.
Practical implications for industrial sensor deployments
Energy-harvesting nodes are best suited to applications where measurements can be periodic or event-driven and where the installation environment provides a usable energy source. The described platform combines solar harvesting, capacitor storage, BLE advertising and temperature, environmental and acceleration sensing. Potential monitoring areas include building conditions, equipment or access events, air quality and worker safety. These examples do not remove the need to validate the energy budget for each deployment.
Before committing to a battery-free design, engineers should evaluate illumination at the mounting location, measurement and reporting frequency, radio requirements, startup energy, storage capacity, voltage regulation and expected periods without harvesting. They should also confirm how gateways receive and interpret sensor data. The practical lesson is that battery-free sensing is achieved through coordinated design: harvest enough energy, preserve it between tasks and make every measurement and transmission fit the available budget.