---
title: 'IoT prototype development in India: from dev kit to an approved device'
description: >-
  IoT prototype development in India in seven stages, with the WPC and BIS
  approvals built in from the first board so your design does not block the
  launch.
author: elroot_labs
date: '2026-11-13'
categories:
  - iot
---
IoT prototype development in India works best in stages: prove the idea on a development kit, choose a radio and parts with approvals in mind, design a first custom board, fit it into an enclosure, test it where it will be used, and prepare the approvals before you sell. If the device uses Wi-Fi, Bluetooth or another radio in licence-exempt bands, it needs the Department of Telecommunications' Equipment Type Approval before it can be imported, sold or used, and most devices can get it by self-declaration with an RF test report. Planning for that from the first board avoids a redesign later.

## Stage 1: Write down the one job the device does

Before buying any parts, write one page that answers four questions. What does the device measure or control? Where will it be installed? What powers it: mains, battery or solar? How does it send data: Wi-Fi, Bluetooth, cellular or a wired link?

Every later decision depends on these answers. A battery-powered sensor on a farm and a mains-powered controller in an office need different radios, enclosures and approvals, even if the core idea is the same.

## Stage 2: Prove the idea on a development kit

Build the first version on an off-the-shelf development board with the sensors wired in. This is where firmware takes shape and where you find out whether the sensor readings are good enough to be useful.

Keep this stage cheap and fast. Changing a wire costs nothing. Changing a custom board costs a new manufacturing run. Move on only when the device does its one job reliably on the bench.

## Stage 3: Choose the radio and parts with approvals in mind

The radio decides which approval you need. India's [Equipment Type Approval (ETA)](https://www.eservices.dot.gov.in/equipment-type-approval-eta), issued by the Wireless Planning and Coordination (WPC) Wing of the Department of Telecommunications, is "required for the import, sale, and use of wireless communication devices that operate in de-licensed frequency bands or involve radio frequency (RF) transmission."

An application needs an RF test report, so choose a radio and antenna arrangement you can get tested, and keep the radio design close to the module maker's reference. While choosing parts, check that each one is available from more than one supplier and that the exact part numbers will still be in stock when you move from ten units to a thousand.

## Work out the battery life before you choose the battery

If the device runs on a battery, do the arithmetic before you order parts, because it often changes the design. We worked one through for an ESP32, using the figures in Espressif's [ESP32 datasheet](https://www.espressif.com/sites/default/files/documentation/esp32_datasheet_en.pdf): 10 µA in deep sleep, 240 mA while transmitting Wi-Fi at full power, and 95 to 100 mA while receiving. The rest are our assumptions, and you should replace them with measurements from your own board: a 2,000 mAh battery, and about 3 seconds awake at an average of 120 mA each time the device connects to Wi-Fi and sends a reading.

| Reporting pattern                                  | Average draw      | Estimated battery life |
| -------------------------------------------------- | ----------------- | ---------------------- |
| Every minute                                       | 6.01 mAh per hour | about 2 weeks          |
| Every 5 minutes                                    | 1.21 mAh per hour | about 69 days          |
| Every 15 minutes                                   | 0.41 mAh per hour | about 7 months         |
| Every hour                                         | 0.11 mAh per hour | about 2 years          |
| Every hour, with a regulator drawing 50 µA at idle | 0.16 mAh per hour | about 17 months        |
| Every hour, connecting and sending in 1.5 seconds  | 0.06 mAh per hour | about 3.8 years        |

![Bar chart of ESP32 battery life by reporting interval: reporting every minute draws 6.01 mAh per hour, about 2 weeks of battery; every hour draws 0.11 mAh per hour, about 2 years; hourly with a 1.5-second send, about 3.8 years.](/images/blog/elroot/figures/esp32-battery-life-by-reporting-interval.png)

Three things stand out. The reporting interval decides almost everything, so ask whether the user needs a reading every minute or would be happy with one every hour. If they want frequent readings but not frequent updates, measure often and send in batches. Second, the time spent connecting matters as much as the transmit current: halving it nearly doubled the hourly estimate. Third, once the device sleeps most of the time, small constant drains start to dominate. A voltage regulator that draws 50 µA doing nothing cut the hourly estimate by about a third, more than the chip's own sleep current. Choose a low-quiescent-current regulator, and measure the whole board's sleep current with a meter, because the datasheet's 10 µA is for the chip alone. These estimates also ignore battery self-discharge and heat, both of which shorten real life.

## Stage 4: Design the first custom board

The first custom board is where most expensive mistakes happen: an antenna over copper, thin power traces, decoupling capacitors far from the chip. Your chip maker's hardware guide usually gives the exact rule for each; for the ESP32, Espressif's [PCB layout guidelines](https://docs.espressif.com/projects/esp-hardware-design-guidelines/en/latest/esp32/pcb-layout-design.html) set minimum power trace widths, decoupling capacitor placement and the number of ground vias under the chip. Order a small batch, because you will almost certainly change something.

## Stage 5: Fit it into an enclosure

A board that works on the bench can fail inside its case. Metal enclosures, batteries and mounting brackets placed near the antenna detune it. For ESP32 designs, Espressif's [PCB layout guidelines](https://docs.espressif.com/projects/esp-hardware-design-guidelines/en/latest/esp32/pcb-layout-design.html) recommend a clearance of at least 15 mm around the antenna in all directions inside the housing. Test the radio range with the board inside the enclosure, not on the bench.

Check heat as well. A sealed plastic box in an Indian summer gets far hotter than a lab, so run the device in its enclosure at the highest temperature it will face.

## Stage 6: Test it where it will live

Install a handful of units in the real environment for a few weeks. Field tests find the problems bench tests miss: patchy network coverage, power cuts, dust, heat and people unplugging things. Design the firmware to keep recording when the connection drops and to sync when it returns; we have written about why [offline behaviour belongs in the data model](/blog/local-first-field-software).

Record every failure. The field log becomes the list of changes for the next board.

## Stage 7: Prepare the approvals before you sell

Two schemes apply to many IoT devices sold in India.

The Department of Telecommunications' [ETA page](https://www.eservices.dot.gov.in/equipment-type-approval-eta) states that ETA "is permitted on self-declaration" for all products operating in WPC de-licensed bands except four types: radar, jamming devices, drones and satellite equipment. The documents required are an RF test report, technical literature and, for an Indian representative, an authorisation from the manufacturer. The listed fee is Rs. 10,000, the application goes through the Saral Sanchar portal, and the approval is valid for life unless WPC revokes it.

The Bureau of Indian Standards runs the [Compulsory Registration Scheme (CRS)](https://www.crsbis.in/BIS/about-crs.do) for electronics and IT goods. It operates under the Ministry of Electronics and IT's compulsory registration order, first notified on 3 October 2012 for fifteen categories, with fifteen more added on 7 November 2014. The scheme's [public dashboard](https://www.crsbis.in/BIS/publicdashAction.do) listed 83 product categories in November 2026. Check whether your device, or the power adapter you plan to ship with it, falls into one of them before you lock the parts list.

## The stages at a glance

| Stage                 | What you prove                        | What to decide for later               |
| --------------------- | ------------------------------------- | -------------------------------------- |
| 1. One-page brief     | The device has one clear job          | Power source, radio, installation site |
| 2. Development kit    | The idea works and the data is useful | Firmware structure                     |
| 3. Radio and parts    | Parts are available and testable      | Which approvals apply                  |
| 4. First custom board | The design works outside a dev kit    | Layout fixes for the next run          |
| 5. Enclosure          | Radio range and heat inside the case  | Antenna clearance, venting             |
| 6. Field test         | It survives the real environment      | Firmware and hardware changes          |
| 7. Approvals          | It can be sold legally in India       | Test reports and registrations         |

## Frequently asked questions

### Does a Wi-Fi or Bluetooth IoT device need WPC approval in India?

Yes. Equipment Type Approval from the WPC Wing is required for the import, sale and use of wireless devices that operate in de-licensed bands or involve RF transmission. Most such devices can apply by self-declaration with an RF test report.

### How much does Equipment Type Approval cost?

The Department of Telecommunications' [eServices page](https://www.eservices.dot.gov.in/equipment-type-approval-eta) lists a fee of Rs. 10,000 for ETA, paid through the Saral Sanchar portal. RF testing at a lab is a separate cost.

### Does my IoT device need BIS registration?

It does if its product category is covered by the Compulsory Registration Scheme. Check the scheme's list of categories on the BIS CRS portal, and check the power adapter separately.

### Should I build the first prototype on a custom board?

Usually not. Prove the idea on a development kit first, then design a custom board once the firmware and sensors work. It is cheaper to change wires than boards.

We build connected hardware alongside software, including [DeskBuddy](/work/deskbuddy) and [Edge Node Tech](/work/edge-node-tech). If you are planning a device for the Indian market, you can [tell us what it needs to do](/contact).
