How data actually moves through the platform.
Four flows underneath everything you build on Espoirnet Platform — telemetry in, state changes reported, commands delivered and confirmed, and the two directions running at once.
A reading becomes a live chart, continuously.
Sensor data streams in over MQTT and lands on the dashboard as it arrives — not on a refresh, not on a polling delay.
The platform knows when something changes on the device itself.
A physical switch flips, a sensor's binary state changes — the device reports it, and the platform records the new state as device-reported, not user-initiated.
A command isn't done until the device says so.
An automation or a person sends a command. It's delivered to the device, executed, and acknowledged — so the platform knows it actually landed, not just that it was sent.
The same wire, listening and speaking at once.
Device-reported state and platform-issued commands travel independently, in either direction, on the same connection — the platform is never just polling.
Automation and analytics tie it all together.
Telemetry and state changes are only useful if something can act on them, or if you can see the trend behind them. See exactly how a trigger turns into a confirmed command — and how the same stored telemetry becomes a dashboard or a report.