How do I make devices run on battery for a long time? — answered by Engineer Saeed Baatiah
Battery life is determined more by the firmware than by the hardware. A device that stays permanently connected drains in days; one that wakes hourly, transmits and sleeps can run for months. The practical decision: what is the least frequent reading that is still useful to you? Measuring hourly instead of every minute extends life many times over, and the difference in value is usually zero.
The biggest power consumer in a connected device is not the sensor but the connection itself. A device that stays permanently attached to the network drains in days; one that wakes, transmits and sleeps can run for months on the same battery. So the most important decision is a software one: how often does it wake? And that decision is yours rather than mine — what is the least frequent interval still useful for your decision?
Examples showing the scale of the difference: sampling every minute means 1,440 wake-ups a day; hourly means 24. That is sixty times the consumption, and zero difference in value if you read the report once a day. Another practical rule: transmit on change rather than on a fixed schedule — a door sensor reporting only when the door opens is far cheaper than one announcing every minute that the door is still shut.
And do not leave the human cost out of the sums: who climbs up to change the battery, how many times a year, and how long it takes. A device in a warehouse ceiling with a three-month battery costs you four visits a year per unit — and across fifty units that becomes a full-time job.
- The connection consumes far more than the sensor
- Hourly instead of every minute = sixty times the battery life
- Transmit on change, not on a fixed schedule
- Count who changes the battery and how often — at fifty units it is a job