What holds a key and sends readings for one asset: its channels mapped to the class's measurements, its key shown once, on and off, its traffic.
A sensor is what holds a key and sends readings for one asset — a controller on a pump, a logger, a gateway posting for the equipment behind it. It belongs to one asset of one class, and stays on it: to report for another asset, delete it and make one there.
On the class's page, once the class measures something, Sensors › New sensor:
t1 → Temperature, p1 → Pressure. A channel is letters, digits and _ . : -, up to 64,
starting with a letter or digit; two channels cannot share a measurement.The sensor sends its own names; the platform stores the class's. A firmware never has to change to fit a class: change the mapping instead (the sensor's page › Channels › Edit the channels).
A sensor sends with a key of its own, hyzsn_…. On the sensor's page (Hyz Assets › the class › the
sensor), Make a key: it is shown once, in a dialog with a first request already carrying it —
copy it into the sensor. Afterwards the page shows only its last four characters.
The same keys are in Hyz Console › Licenses and apps › Sensors, beside every sensor of the enterprise.
Switch off a sensor and everything it sends is refused (SENSOR_DISABLED) until it is switched on.
A switched-off sensor is never stale, and an asset whose sensors are all off reads None.
Haiyz can switch a sensor off too — it then reads Switched off by Haiyz, with the reason, and its enterprise cannot switch it on until Haiyz releases it (Holds and limits).
A sensor's calls are counted there, not written to the audit trail: the trail keeps what a person does to it — made, changed, deleted, its key made, replaced or revoked, a hold set or released.
A class of two thousand assets is not two thousand forms. On the class page, Make sensors for every asset without one — or tick rows in the assets table and choose Make sensors — opens one dialog:
{asset} stands for the asset's name.Up to 500 are made a call; the dialog says how many assets remain and makes the next batch on request. An asset the class does not hold is refused by name, the rest are made.
A gateway is one key that posts readings for every sensor bound to it — the credential a SCADA export, a historian or a site controller holds for the whole site. Hyz Assets › Gateways lists the enterprise's gateways as cards: whether it is on, how many sensors are bound, the key's last four characters, when it last posted and what was last refused, its address and a first request. Whoever manages assets makes one, makes its key — shown once, with a fresh confirmation — replaces or revokes it, switches it off and deletes it; deleting keeps its sensors, unbound.
A sensor is bound to a gateway in its Settings, or made bound in the batch dialog. Bound, it needs no key of its own: the gateway's call names it by its id or by its asset, and its page shows that call beside its own. The contract is on the sensor endpoint.
Delete says first what goes: its readings — those its events keep said apart — and its open events, which close and stay on the events list. When it was the last sensor reporting on its asset, the asset's latest values are cleared and it reads None; its point stays.