Power and Sensor Management

Jotting down random ideas.

When sensors (and other applicable components, such as neopixels) are idle, try and harvest energy from them.

Only transmit data if value has changed within specific threshold. For example, temperature readings would only be transmitted if temp has changed by 0.1℃ or more.

Decouple sensor readings from data transmissions? This could potentially allow some readings to be deferred until day time when there is more energy available (eg. via PV). It could also allow batching of data packets to make better use of TCP/UDP frame size?

Determine TTL for sensor results; after TTL expires, a new reading is taken. Prior to TTL expiry, sensor is inactive to save power, although ad-hoc sensor updates may be required if data from that sensor is required for some other sensor or calculation.

Each sensor should have a profile that determines when it is active. For example, some sensors might have different day/night schedules, others will be regular intervals, etc. Alternatively just a linear schedule?

Sensors should be prioritised so that less important readings can be skipped if power is low. Maybe the priority could be assigned to the sensors' schedule? For example, it might be more important to take readings at certain times than at other times.

Power down MCUs whenever possible to conserve energy. MCUs that monitor transient sensors should ideally use specialised MCU that facilitates powering down most of circuit until a sensor value needs processing.