# Why is the temperature view empty for the selected container even though data exists?

**URL:** <https://community.dockflow.com/t/why-is-the-temperature-view-empty-for-the-selected-container-even-though-data-exists/166>\
**Category:** How-to Q&A\
**Tags:** temperature-data, area-reefer-temperature\
**Created:** [November 6, 2026, 3:19pm UTC](https://community.dockflow.com/t/why-is-the-temperature-view-empty-for-the-selected-container-even-though-data-exists/166 "2026-11-06T15:19:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dockflow](https://community.dockflow.com/letter_avatar_proxy/v4/letter/d/a9a28c/32.png) [@dockflow](https://community.dockflow.com/u/dockflow)\
**Post date:** [November 6, 2026, 3:19pm UTC](https://community.dockflow.com/t/why-is-the-temperature-view-empty-for-the-selected-container-even-though-data-exists/166/1 "2026-11-06T15:19:39Z")

</div>

In the temperature view, readings are shown for the **selected** container only. If a tradeflow  
holds several containers and you are looking at the wrong one, the view is empty even though data  
exists.

Select the specific container that carries the device.

This also explains a common false alarm: a placeholder container added to a file will never show  
temperature data, because no device is attached to it.

**Example**  
A user looks at the temperature view while the wrong container in a tradeflow is selected. The view is empty even though temperature data exists. After selecting the specific container that carries the device, the readings appear. A placeholder container added to the file never shows temperature data because no device is attached to it.