This note describes what the RHT Sensor Plugin reads and where it can send it. It is not a separate agreement: the Plugin is covered by the ChromaChecker End-User License Agreement (the "EULA"). It is published because one of its two modes involves a message broker that may be on another machine.
1. What this Plugin does
RHT Sensor records temperature and humidity — the conditions a measurement was taken in — and makes them available to the rest of CC Capture, so a fingerprint or a job carries the environment it was produced in.
2. Two sources, and they behave differently
| Mode | Where the reading comes from | What leaves the workstation |
|---|---|---|
| CC RHT-USB | a sensor plugged into the workstation | nothing |
| MQTT | a broker you configure — Zigbee2mqtt, Tasmota, ESPHome, Shelly and similar | the workstation subscribes to your broker; readings travel from it over your network |
In MQTT mode the Plugin is a client of your broker. ChromaChecker does not operate it, does not receive these messages, and the broker's own credentials and transport security are what protect them. See also the IoT Bridge note, which covers the broker connection itself.
3. What is stored
The sensor type, broker address and topic are stored in the workstation's application settings. Readings are stored with the measurements they qualify.
4. Third parties
None introduced by ChromaChecker. Sensors and brokers are yours, or your supplier's.
Changes to this document
This document is versioned. A new version replaces this text at the same address, and the version you accepted is recorded by the application. Every earlier version is kept in the revision history below, so the text your Organisation agreed to can always be produced.
Revision history
| Version | Effective | What changed |
|---|---|---|
| 1.0 | August 6, 2026 | First publication |
ChromaChecker Corporation · 4324 Sanddollar Court, New Port Richey, FL 34652, USA · legal@chromachecker.com
Published at https://chromachecker.com/legal-plugin-rht-sensor
