Skip to content

v0.20.4 - Rename BME280 temperature field temp_c to tmp_c (2026-06-04)

What Changed?

This release updates the BME280 temperature field name from temp_c to tmp_c to match a firmware change in the OSECHI detector. The change affects monitor_events.py, the test data file events.jsonl, and example output in the documentation. No API or library changes are required.

What's New

Fix: Rename temp_c to tmp_c across codebase

What it does: Updates all references to the BME280 temperature field from temp_c to tmp_c to match the updated device firmware (kurkintons).

Files updated:

  • examples/monitor_events.py: event.get("temp_c") → event.get("tmp_c")
  • src/kazunoko/data/events/events.jsonl: all 100 events updated
  • docs/getting-started/first-measurement.md: example output updated
  • docs/workflow/read-events.md: example output updated (JSONL and LTSV formats)

Installation

Quick Start

# Get the release
git checkout v0.20.4

# Setup
uv sync

# Run CLI
uv run kazunoko --help

What's Different from the Last Version?

🐛 Fixed

  • examples/monitor_events.py: BME280 temperature field renamed temp_c → tmp_c
  • src/kazunoko/data/events/events.jsonl: all 100 events updated with new field name
  • docs/getting-started/first-measurement.md: example JSONL output updated
  • docs/workflow/read-events.md: example JSONL and LTSV output updated

Is It Safe to Upgrade?

Backward Compatible: No (firmware-dependent)

  • Users running older firmware that still outputs temp_c will see tmp_c return 0.0 in monitor_events.py.
  • Users running updated firmware (kurkintons with tmp_c) must upgrade to this version to display temperature correctly.

Tests Passed

  • ✅ Builds without errors
  • ✅ monitor_events.py reads temperature via tmp_c field

Release Details

  • Date: 2026-06-04
  • Version: v0.20.4
  • Files Changed: 4
  • Commits: ca90389, d04a8d6, 6f1045f

Next Steps

Continue tracking firmware field name changes and keeping the codebase in sync.