u/Medtag212

Working through a LoRaWAN sensor node design and hit the classic problem - sleep current looks perfect on paper, but real world consumption is 3-4x higher than expected.

Usual suspects I’ve been through:

∙	GPIO states during sleep , floating pins pulling current through internal resistors

∙	Peripheral clocks not fully disabled before entering stop mode

∙	LSE startup time causing the MCU to stay in a higher power state longer than expected

∙	IWDG keeping certain regulators alive

The one that got me - SPI flash not entering deep power down before sleep. Datasheet said 1µA standby, reality was 80µA because the CS line wasn’t being driven high explicitly before the sleep sequence.

What are the non-obvious power leaks that have burned you on low power STM32 or similar designs? Particularly interested in anything related to LoRaWAN duty cycle management and sleep/wake timing.

A lot of hardware products start on ESP32 because it’s accessible. Then BLE, WiFi, OTA, power management and real hardware constraints hit at the same time.

Curious what founders and makers here do when firmware complexity outgrows what they can handle solo. Do you find help through the community? Take a chance on Upwork? Just push through alone?

And firmware engineers - how do serious clients usually find you?