Request a firmware review
Menu
Startups whose device talks to a phone, a gateway or the cloud

Wireless links that recover on their own

A radio link that works on the bench is only the start. We write the firmware that provisions devices, recovers from dropped links and is ready when the test lab asks for it.

Key characteristics

Radios
Bluetooth LE, Wi-Fi, LTE-M, NB-IoT, Thread, LoRaWAN
You provide
Cloud endpoint, carrier or SIM choice, app team contact
You receive
Design note, measured throughput and current, test log
Certification
We prepare the firmware and claim no certification

Connectivity is where problems in connected devices tend to show up first. A phone operating system update changes how Bluetooth behaves, a gateway reboots and forty sensors have to find it again, a cellular modem sits in a basement with one bar of signal. The radio chip and its vendor stack give you a link on the bench. The firmware decides what happens when that link is slow, busy or gone, and that is the part we write.

The radios we work with

Radio Typical use What the firmware has to get right
Bluetooth LE Phone apps, wearables, sensors reporting to a gateway Connection parameters, GATT design, bonding, differences between phones, throughput for updates
Wi-Fi Mains-powered home and office devices, cameras Getting onto the user’s network, reconnects after router changes, power use if on battery
LTE-M and NB-IoT Devices with no local gateway, asset trackers, remote sensors Network attach, sleeping between check-ins, data cost, weak coverage
Thread and Matter Smart home devices that must work across ecosystems Commissioning, interoperability, which Matter SDK release you build on
LoRaWAN Long range, small payloads, years on a battery Very small messages, limited airtime, updates split into fragments

A few facts drive the design. In Bluetooth Core 4.2 and later, an LE data packet can carry up to 251 octets of payload, against 27 in versions 4.0 and 4.1. Bluetooth 5 added the LE 2M PHY, which runs the physical layer at 2 Ms/s; the Bluetooth SIG puts its theoretical bandwidth at about 1.7 times that of 4.2, but support for it is optional, so the phone or gateway on the other end decides whether you get it. LTE-M (3GPP eMTC) and NB-IoT were standardized by 3GPP in Release 13. Matter is an open-source, application-layer standard guided by the Connectivity Standards Alliance that runs over Thread and Wi-Fi; its SDK reached release 1.6 in August 2026. LoRaWAN is a low-power, wide-area networking specification for battery-operated devices, and the LoRa Alliance lists firmware updates over the air and multicast among its features.

Provisioning

Every device needs an identity and a way onto its network: a Bluetooth bond with a phone or gateway, Wi-Fi credentials entered through an app, a SIM and a device certificate for your cloud, a Matter setup code, LoRaWAN join keys. We design how each is created at the factory (see manufacturing firmware), delivered to the device, stored, rotated, and erased when a unit is reset or resold. Then we document the handoff to your cloud team: what the device sends when it first connects, how it proves who it is, and what the server must answer.

Reconnection behavior

The most valuable connectivity work is often unglamorous: deciding what the device does when the link fails, and writing it down. We settle questions like these with you:

  • How long to wait before retrying, and how the wait grows, with some randomness, so a whole fleet does not hit the gateway or the network at once after an outage.
  • What to store while offline, how much, and what to drop first when storage fills.
  • How to tell a dead link from a slow one, and when to restart the radio or the whole device.
  • What the device reports when it comes back: how long it was gone, why, and how much it buffered.

Then we test the rules on real hardware: restart the gateway, take the access point away, move the device somewhere with weak coverage, and log how long reconnects take.

Example (fictional). Loamwick’s LW-1 probes talk Bluetooth LE to a solar-powered gateway, which forwards readings to Loamwick’s cloud over LTE-M cellular. Requirement FW-005 says a probe must reconnect to the gateway within 10 minutes after the gateway restarts; it is verified by restarting the gateway 20 times and logging reconnect times. Because each of the 4 gateways downloads a new probe image once over LTE-M and relays it to its probes over Bluetooth LE, a rollout to the 40-probe pilot fleet needs four cellular downloads, not forty. See the example project.

Connectivity and updates

The radio sets how long an update takes, how much energy it uses and what it costs. The default example in the BLE update time calculator moves a 412 KB image with 244-byte payloads, 3 packets per connection event and a 30 ms connection interval: 19.1 KB/s of image data, about 21.6 seconds of transfer, and 36.6 seconds including verify, swap and reboot. The same link with 20-byte payloads takes about 4.4 minutes. On cellular the question is data cost, which the over-the-air data cost calculator works out for full and delta images across a fleet. LoRaWAN-class links need small or fragmented updates and patience. The update path itself is covered in over-the-air updates, and the energy side in low-power design.

Preparing for certification

Radios bring certification steps that sit outside the firmware but depend on it. In the US, the FCC’s rules for the service a device operates in can require radio-frequency equipment to be authorized, either under a Supplier’s Declaration of Conformity or by a grant of certification from a Telecommunication Certification Body (47 CFR 2.901). The Bluetooth SIG requires every Bluetooth product to complete its qualification process on or before the date it is first sold or distributed. Matter, Wi-Fi and cellular products can have further requirements from their industry bodies and carriers, so ask your module vendor and carrier early.

Our part is the firmware a lab needs: test modes that transmit or receive on a chosen channel at a set power, radio settings kept in one documented place, and a frozen radio configuration before testing starts. Our production readiness checklist puts pre-certification radio tests in the DVT gate. We do not certify products, and this page is not regulatory advice.

What you receive

  • A connectivity design note: protocols, parameters, provisioning flow and reconnection rules.
  • Measured throughput and current for each radio state on your hardware.
  • An interoperability and reconnect test log, including the phones or gateways you care about.
  • Test firmware for the certification lab.

Where to start

If your link works on the bench but you are not sure how it behaves in the field, start with a firmware review: we read your radio code, provisioning flow and update plan and tell you in writing what to fix first. Request a firmware review, or read more in the connectivity and power section of Field Update.

Send us your board and your plan.

A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.

Request a firmware review

Or email sales@fumbar.com, or call (720) 675-4202.