Firmware that keeps the data flowing.

We build the embedded software inside connected products, from the sensor node and its radio to the broker and the dashboard. Teams bring us a board and a deadline; they leave with devices that ship.

SensorSHT40FirmwareESP32RadioWi-Fi / LoRaBrokerMQTTDashboardyour teamSensorFirmwareRadioBrokerDashboard
Lab node onlineprobaho/lab/node-01/telemetry--.-- °C--.- % RHSimulated data until the lab hardware goes live

What we build

Everything between the sensor and the screen, with the most care spent where products usually fail: power, radio and recovery.

  • Firmware development

    Production firmware in C and C++ for bare-metal, FreeRTOS and Zephyr targets. Drivers, state machines, bootloaders and the tests that keep them honest.

    • STM32
    • ESP32
    • nRF52
    • FreeRTOS
    • Zephyr
  • Wireless connectivity

    Reliable links that survive real conditions: reconnect logic, buffering through outages, and payloads sized for the radio you have.

    • MQTT
    • LoRaWAN
    • BLE
    • Wi-Fi
    • LTE-M
  • Low-power design

    Sleep strategies, peripheral gating and current profiling, measured on real hardware, until the battery estimate is one you can put on a datasheet.

    • Power profiling
    • Sleep modes
    • Energy budgets
  • Cloud and network onboarding

    Getting devices onto the network and their data into your cloud: MQTT integration with AWS IoT Core, and complete LoRaWAN onboarding on commercial network operators.

    • AWS IoT Core
    • The Things Industries
    • Senet (Netmore)
    • LoRaWAN onboarding
  • Bring-up and rescue

    New board that will not boot, or a field fleet that resets at 3 a.m.? We read the schematics, attach the probes and find the cause.

    • Board bring-up
    • Logic analysis
    • Root-cause reports
  • Updates and production

    Secure over-the-air updates, manufacturing test firmware and provisioning, so the thousandth unit behaves like the first.

    • OTA
    • Secure boot
    • Factory test

A working lab, not a slide deck

A sensor node on our bench publishes over MQTT, and a second node reports over LoRaWAN. Change the LED colour, cut the connection, queue a downlink, and watch the firmware handle it.

Open the live lab

Running on simulated data while the lab hardware is being installed.

MQTT node

probaho/lab/node-01/telemetry
Temperature
--
Current draw
--
Wi-Fi RSSI
--

LoRaWAN node

Class A, uplink every few minutes

Waiting for first uplink

RSSI
--
SNR
--
Spreading factor
--

Selected work

The constraint, the work, and the number that mattered at the end.

  1. Commercial IoT hardware, US manufacturerIndependent contract firmware engineering by our founder, 5+ years and ongoing

    Firmware for an 8-channel LoRaWAN gateway

    Constraint. A gateway for remote, solar-powered and mobile sites, with cellular, Wi-Fi and Ethernet backhaul, that installers can set up in minutes.

    The work. LoRaWAN, MQTT and BLE configuration firmware, plus an onboard LoRaWAN network server that handles joins, uplinks and a focused set of MAC commands on the gateway itself.

    3,000+ units produced

  2. Healthcare logisticsSample, replace

    Cold-chain monitor for a pharmacy group

    Constraint. Vaccine fridges needed alerts within a minute of a door left open, even during internet outages.

    The work. ESP32 loggers publishing over MQTT with QoS 1, local flash buffering and Last Will alerts for offline devices.

    0 lost readings across 6 weeks of field trials

  3. EnergySample, replace

    Firmware rescue for a smart-meter startup

    Constraint. Field units rebooted several times a day and nobody could reproduce it on the bench.

    The work. Crash logging to retained RAM, a watchdog audit and a fix for a stack overflow in the metering ISR.

    Resets cut from 4 per day to none in 30 days

How an engagement runs

Fixed-scope phases, so you always know what the next invoice buys.

  1. Discover

    A short paid scoping phase. We read your schematics and requirements, list the risks, and agree what “done” means.

  2. Prototype

    Firmware running on your hardware early, with the riskiest parts proven first: the radio link, the power budget, the sensor.

  3. Harden

    Fault handling, updates, tests and long-run soak tests. The unglamorous work that decides whether devices survive the field.

  4. Hand over

    Documented source, build instructions and a walkthrough with your team. You own everything we write.

A small lab with a narrow focus

Probaho Labs is an embedded engineering consultancy based in Dhaka. We work with hardware startups, manufacturers and research teams who need firmware written well and connectivity that holds up outside the lab.

Probaho (প্রবাহ) is Bengali for flow: of current through a trace, of packets through a network, of data from a field sensor to the person who needs it. Keeping that flow reliable is the job.

Founder name Sample, replace

Founder and principal engineer

Years of experience, specialities and a line about how you like to work.

Have a board and a deadline?

Tell us what the device does, where it will live and when it needs to ship. We reply within two working days with questions or a scoping proposal.

Email us athello@probaholabs.com
Open in email app