Journey event  ·  14 Sep 2026

Zigbee canopy and Tuya tank readings are never written to fleet_history by their lanes – they only reach history via the 60 s computed recorder (change or 5 min

FIXED in PR #259: history_ops.record_lane_row / record_canopy write at receipt from zigbee_mqtt.on_message and TuyaLane.ingest (seat = 'zigbee' / 'tuya', metric = the entity id the

  state copied from the tracker, never improved

  event date 2026-09-14

Event date 2026-09-14
Version found
Version fixed
Expected kit firmware
Release file
SHA-256
Served count
Source https://app.notion.com/3db2b4cda37081929022dfe1eae7d8e3

FIXED in PR #259: history_ops.record_lane_row / record_canopy write at receipt from zigbee_mqtt.on_message and TuyaLane.ingest (seat = ‘zigbee’ / ‘tuya’, metric = the entity id the fleet exposes, change-or-5-min throttle); resolve_entity_metric maps sensor./binary_sensor.dsc_zigbee, dsc_tuya_, dsc_canopy_* to those seats; genuinely derived values (sensor.dsc_tank_ec_normalized) stay on the computed seat. 3 tests. Verify: reservoir tester EC chart at 15 m shows every report, not one point a minute. — Original: both push lanes updated the in-memory cache only; readings only reached history through the 60 s computed recorder.

All events  ·  DSC  ·  CannaLib  ·  Site  ·  Firmware releases

Empty rows are honest

A blank cell means the tracker has no value for it. Nothing on this page is filled in to look complete.