Embedded Wi-Fi Product Development

Wifi

Wi-Fi is the connectivity most people already have, which is why it is so often the right answer for a product that lives in a home or an office. Ambimat has used Wi-Fi extensively in smart-home work and in in-house consumer devices, where the user’s own router is the infrastructure and the phone is the interface.

Where Wi-Fi fits in connected-product design

Wi-Fi suits products that sit in a building, have mains power or a rechargeable cell, and need real bandwidth or a direct route to the internet without a hub of their own. It is a poor fit where the node runs for years on a coin cell, where there is no network to join, or where hundreds of devices need to relay for each other — those are questions for LPWAN and mesh respectively.

  • Consumer and in-house devices that connect through the customer’s own router
  • Products whose primary interface is a phone application
  • Devices that talk directly to a cloud back-end without a dedicated gateway
  • Retrofit products, where pulling cable is not an option
  • Systems that also offer a wired path, with Wi-Fi as the deployed default

Ambimat’s Wi-Fi experience

The longest-running example is home automation. In 2010 Ambimat designed an in-house product for automating the lights and fans of a home using wireless technology, Ethernet and Wi-Fi — a system built so appliances could be operated without touching a switchboard, through a remote controller or a phone, with scenes and schedules the homeowner could change themselves. That work was then offered as a design service to two further Indian customers, in 2018 and again in 2020.

The full account is on the Smart Homes page. Wi-Fi also appears as one of the selectable uplinks on the AmbiAutomation HVAC bridge board, alongside cellular and Ethernet — in commercial buildings the choice of uplink belongs to the site, so the product has to support more than one.

Engineering considerations

Module and chipset selection comes first and constrains everything after it: certification status, antenna options, the driver and stack you inherit, and how long the part will still be buyable. Antenna design and placement then decide whether the product works at the far end of a house or only next to the router, and that is a PCB and enclosure question rather than a firmware one.

The part customers underestimate is provisioning — getting a device with no screen and no keyboard onto a network whose password the owner has to type somewhere. It has to work for a non-technical person on the first try, survive a router change, and fail in a way that can be recovered without a support call. After that comes the application layer: reconnection behaviour, what the device does offline, and how it reaches the back-end without leaving an open door on the customer’s LAN.

Wi-Fi or wired

In practice the decision is rarely about throughput. It is about who owns the network, whether anyone will pull a cable, and what happens when the link is down. A home product with no installer gets Wi-Fi. A plant room with structured cabling and an IT policy gets Ethernet. A product that will be sold into both should be designed with the uplink as a configurable layer from the start, which is the approach Ambimat has taken on multi-interface products.

Discuss a Wi-Fi connected product