# Emerging Household Energy stove use monitoring

> How Emerging Household Energy uses stove use monitors (SUMs) to record cooking events, detect stove stacking and keep sensor data continuous.

This page is about **Emerging Household Energy**: monitoring how often each cookstove in a household
is used, with stove use monitors (SUMs), so that usage can be verified and reported. It covers what
coverage and continuity the programme requires, how to register and configure a monitor, what a
reading looks like, and how to detect stove stacking.

The requirements are:

- **Complete coverage.** Install a sensor on every active cookstove, unless a deviation is
  justified.
- **Continuous monitoring.** Measure without interruption where possible.
- **Stacking detection.** Track concurrent use across several stoves to prevent double counting.
- **Data reliability.** Collect data regularly by hand when digital transmission is not possible, so
  none is lost.

<Info>
  The code on this page is an illustrative example. It shows the shape of the data and the calls,
  and has not been run as a whole. The `api.emerging.eco/v1` calls and the `emerging` Python client
  are not part of the [Emerging Platform API](/platforms/Emerging/emerging-api) contract.
</Info>

## Register a stove use monitor

Illustrative example:

<CodeGroup>
```bash Register SUM
curl -X POST https://api.emerging.eco/v1/devices \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
    "type": "StoveUseMonitor",
    "householdId": "did:ixo:household/123",
    "stoveId": "did:ixo:stove/456",
    "configuration": {
      "samplingRate": 300,
      "temperatureThreshold": 60,
      "transmissionMode": "realtime"
    }
  }'
```

```python
from emerging import Device

# Register a new Device
sum_device = Device.create(
    type="StoveUseMonitor",
    household_id="did:ixo:household/123",
    stove_id="did:ixo:stove/456",
    configuration={
        "sampling_rate": 300,  # 5 minute intervals
        "temperature_threshold": 60,  # Celsius
        "transmission_mode": "realtime"
    }
)
```

</CodeGroup>

### Device configuration

<ResponseField name="samplingRate" type="integer" required>
  Seconds between temperature readings (recommended: 1-5 minutes)
</ResponseField>

<ResponseField name="temperatureThreshold" type="integer" required>
  Temperature (°C) threshold for cooking event detection
</ResponseField>

<ResponseField name="transmissionMode" type="string" required>
  "realtime" | "batch" | "manual"
</ResponseField>

## Implementation requirements

### Installation coverage

- Install sensors on all cookstoves in the project.
- Document any deviation, with a detailed justification.
- Verify regularly that the sensors are in place.
- Monitor sensor health and calibration.

To prevent stove stacking from being missed, track temperature patterns across all of a household's
stoves, detect concurrent use, check that each cooking event is plausible, and cross-reference the
results with household surveys.

### Measurement duration

Monitoring is ongoing, with no planned interruptions. Manage battery life and keep backup data
storage.

To keep the data continuous:

- transmit in real time where possible
- collect by hand at regular intervals if needed
- have backup procedures for power and connectivity problems
- document and justify any gap in the data

### Data collection

| Method | Requirements |
| --- | --- |
| Digital transmission | The preferred method. Data is validated in real time and anomalies are detected automatically. |
| Manual collection | Required when digital transmission is not possible. Collect often enough to prevent data loss, on a set schedule, and document the chain of custody. |

For data quality, validate temperature readings, cross-check between stoves, keep device clocks in
sync and verify completeness.

### Sampling design

Full monitoring is preferred. Sampling is allowed if digital collection is impossible. A sample must
follow the [sampling guidelines](/platforms/Emerging/sample-size) and meet their requirements for
statistical validity.

## Readings

Illustrative example: a monitor's readings and status.

```json
{
  "deviceId": "did:ixo:device/sum789",
  "stoveId": "did:ixo:stove/456",
  "readings": [{
    "timestamp": "2024-02-20T08:15:00Z",
    "temperature": 85.4,
    "cookingEvent": true,
    "duration": 1800
  }],
  "status": {
    "battery": 92,
    "signal": "strong",
    "lastSync": "2024-02-20T08:20:00Z"
  }
}
```

## Detect stove stacking

Illustrative example:

```python
from emerging import HouseholdAnalytics

# Analyze stove usage patterns
analytics = HouseholdAnalytics("did:ixo:household/123")

stacking_report = analytics.detect_stacking(
    period_start="2024-02-01",
    period_end="2024-02-28",
    stove_types=["traditional", "improved"]
)

# Get detailed cooking events
events = analytics.get_cooking_events(
    min_duration=1800,  # 30 minutes
    min_temperature=60
)
```

The Emerging Platform API documents stove stacking data at
[stove stacking](/api-reference/emerging/get-stove-stacking-data).

## Link monitors to the household

Register a monitor for every stove in a household and link each one to the household's digital twin.

Illustrative example:

```python
from emerging import Household, Device

# Get household digital twin
household = Household.get("did:ixo:household/123")

# Register SUMs for all stoves
for stove in household.stoves:
    sum_device = Device.create(
        type="StoveUseMonitor",
        stove_id=stove.id,
        household_id=household.id
    )
    
    # Link to household digital twin
    household.add_device(sum_device)

# Monitor stove usage compliance
compliance = household.check_monitoring_compliance()
```

## When something goes wrong

<ResponseField name="400" type="error">
  Invalid device configuration
</ResponseField>

<ResponseField name="404" type="error">
  Device or stove not found
</ResponseField>

<ResponseField name="503" type="error">
  Data transmission failure
</ResponseField>

## Practices

| Area | What to do |
| --- | --- |
| Installation | Mount sensors securely, calibrate temperature thresholds, verify signal strength, test data transmission and document any coverage exceptions. |
| Monitoring | Check battery levels regularly, validate sensor readings, monitor data completeness, track transmission status and verify continuous operation. |
| Data collection | Have backup procedures, run regular quality checks, document how often data is collected, keep collection records and prevent data loss. |
| Stove stacking | Monitor all household stoves, track concurrent use, validate cooking patterns, cross-reference data sources and document usage anomalies. |

## Next steps

- [Household monitoring](/platforms/Emerging/household-monitoring): set up the household digital
  twin and track the whole energy transition.
- [Qualitative surveys](/platforms/Emerging/qualitative-surveys): check usage patterns with surveys.
- [Kitchen performance tests](/platforms/Emerging/kpt): verify fuel consumption measurements.
- [Household reporting](/platforms/Emerging/household-reporting): turn monitoring data into reports.
