Environmental Monitoring
BetaUnderstand how an environment changes, not just a single reading.
Hestix collects environmental readings, links them to spaces and makes their evolution over time visible, keeping the capability separate from the individual provider.
Environmental Monitoring is available in Beta: the model and the dashboard are operational, while integrations, providers and environmental workflows are still evolving.
Beta describes the perimeter of a capability that is already operational, not an unstable or unusable feature.
From sensor to space
A reading makes sense when you know where it comes from.
A sensor produces technical data. Hestix normalizes it and links it to a readable space, so readings and history stay understandable even when the provider changes.
The journey of the data stays explicit: from the device to the reading associated with a space.
- Sensor / provider
- Channel / metric
- Space
- Hestix
- Reading / history
- A device can expose multiple channels.
- A channel can be associated with a readable space.
- Hestix normalizes the data the UI actually needs.
- The UI does not depend on the provider’s internal codes.
The public model describes readings and spaces. Provider internal codes, device identifiers and credentials stay out of the page and are not part of the story.
Multiple spaces
A property is not a single sensor.
Multiple spaces can be observed in the same context: every configured space keeps its own readings and its own history.
Space
- Temperature
- Humidity
- History
Spaces depend on the configuration of each context: these examples describe the model, not product requirements.
- Living room
- Bedroom
- Bathroom
- Another configured space
Real proof
Readings and history in the same panel.
The Environmental Monitoring dashboard shows configured spaces, available values and the historical trend in one context.
- A card for every configured space
- Temperature
- Humidity
- Historical chart of the readings
- Space selection from the card
The current dashboard is mainly a consultation view: values and history are read in the UI, not edited from the browser.
The value of history
Today’s number matters. The trend matters more.
A single reading says little without a time context. History makes it observable how a space behaves over time.
Variations over time
How temperature and humidity change across the hours and days you observe.
Persistent high or low humidity
Whether a condition stays stable or comes back several times.
Differences between spaces
Different spaces can behave differently in the same period.
How a space responds over time
How an environment evolves after an external or seasonal change.
History describes environmental conditions and the trend of temperature and humidity. It does not produce diagnoses, does not automatically determine mould, biological risk or healthiness and does not define intervention thresholds.
Before and after
See what happens after an intervention.
History can help an operator compare the environmental trend before and after actions taken outside the space.
- Ventilation
- Air conditioning
- Dehumidification
Environmental Monitoring today makes the data observable. Hestix does not automatically switch air conditioners or dehumidifiers on and off and does not run closed-loop automation: controlled automations can be a future evolution of the capability.
Provider-agnostic
The sensor can change. The operating model stays.
Hestix keeps provider, normalization and interface separate, so the capability does not depend on the API or documentation of a single manufacturer.
Tuya / Smart Life is the environmental provider currently implemented in Hestix and the first ecosystem connected to Environmental Monitoring.
- The current provider can change without changing the Hestix operating model.
- New providers require a dedicated integration.
Provider-agnostic describes the architecture, not universal compatibility that is already available: Hestix does not claim automatic support for any sensor, Wi-Fi device or IoT ecosystem.
Data and automation
Observe first. Then decide what to automate.
Environmental Monitoring is an observation layer. Automations remain a later, explicit and controllable step.
The sensor produces the data
The device exposes the channels it measures; Hestix collects them without inventing them.
Hestix normalizes and makes it usable
Readings and history become a readable context for people and workflows.
Future workflows and automations stay explicit
Any environmental automation requires dedicated rules, integrations and supervision.
Environmental Monitoring is not a complete home automation system: today the value is making environmental data readable, persistent and reusable.
Inside the Hestix platform
Another kind of operating context.
Hestix does not only work with bookings, guests and access: it can also integrate physical data from spaces, useful to read daily operations from another perspective.
- Bookings and stays
- Guests and access
- Environmental data from spaces
- One shared operating layer
FAQ
Common questions about environmental monitoring.
Does Environmental Monitoring work only with Tuya / Smart Life?
No. Tuya / Smart Life is the first provider currently implemented. The Hestix capability is separate from the provider, but every new ecosystem requires a dedicated integration.
Which data does Hestix show today?
The current implementation uses temperature, humidity, the associated space and the history of the available readings.
Does Hestix automatically control air conditioners or dehumidifiers?
Not as a current general capability. Environmental Monitoring today makes environmental data observable; any automation requires dedicated workflows and integrations.
Is it already an available feature?
Yes, in Beta. The dashboard and the environmental pipeline are operational, while supported providers and workflows keep evolving.
Environmental Monitoring in Hestix
Want to see how your spaces change over time?
We can walk through the model, the dashboard and the providers already used in your operating context.