Hermetry comes with a library of 106 codecs for common LoRaWAN sensors. Each one decodes the payloads of one sensor or a family of sensors from one maker. Devices on Automatic use the library without any setup when their maker and FPort match a library codec.
Open the library
- Open Devices.
- Open the ⋯ menu and select LoRaWAN codecs.
The drawer lists every codec you can use: the library’s (Source: Library) and your own (Source: Yours). You need the permission to view LoRaWAN codecs (users by default).
| Column | Shows |
|---|---|
| Id | The codec id. Library ids are short names built from the maker and model. Your codecs start with t. |
| Name | What the codec decodes, for example a temperature and humidity sensor |
| Vendor | The device maker |
| Models | The model names the codec covers |
| FPorts | The FPorts it decodes; empty means every port |
| Kind | The table format, tlv or layout |
| Source | Library or Yours |
| Verified | Verified on a device or Not verified (decoded from the maker’s published format and checked against its test vectors) |
| Revision, Updated, Status | The current revision, when it changed, Published or Withdrawn |
Search by id, name, vendor, model or maker code (OUI).
What the library covers
| Sensor type | Examples of values |
|---|---|
| Indoor air quality | CO₂, particulate matter, formaldehyde, ozone, temperature, humidity, pressure, light |
| Temperature and humidity | Room sensors, labels, probes (including PT100 and thermocouple transmitters), insertion and dual-probe sensors |
| Doors, windows and contacts | Open/closed state, open counts |
| Pulses and digital inputs | Pulse counters, input states |
| Electrical current | Current transformer clamps (single and three channel), multi-channel current sensors, smart sockets and meter plugs |
| Water leaks | Leak detected, membrane and probe leak sensors |
| Level and distance | Ultrasonic, radar and LiDAR distance, capacitive liquid level, submersible level, pressure and level transmitters, fill level |
| Tilt | Tilt angle and tilt alarms |
| Soil and agriculture | Soil moisture, temperature, conductivity (EC), pH, leaf moisture |
| Gas and odour | Gas detectors, odour detectors |
| Pressure and flow | Pipe pressure, flow meters |
| Weather and environment | Weather stations, light level, sound level |
| Tracking | Outdoor asset trackers (GPS and Wi-Fi), container and card trackers, badges, contact-tracing tags |
| Buttons and alarms | Panic buttons, smart and wearable buttons, safety badges, scene panels |
| Occupancy and people | People counters, desk and workplace occupancy, radar presence, fall detection, PIR motion |
| Parking | Parking-space sensors |
| Control | Solenoid valve controllers, multi-interface controllers, light controllers, thermostats, radiator thermostats |
There is no LoRaWAN vibration sensor in the library today. For a sensor that is missing, write your own codec.
Find the codec for your sensor
- Search the drawer for the sensor’s model name, as printed on it.
- Open the codec and check Models and FPorts.
- Check Makers (OUI): if your DevEUI starts with one of these six-digit codes, Automatic picks this codec by itself.
- If your DevEUI does not start with a listed maker code (for example, the supplier assigned its own DevEUIs), choose the codec by name on the device or profile.
A codec’s page
Open a codec from the list to see:
| Section | Shows |
|---|---|
| Codec | Id, revision, Fingerprint (SHA-256), models, FPorts, makers (OUI), origin and source |
| Keys it decodes | Every output key with its unit, taken from the codec’s own test vectors |
| Revisions | Every published revision, with its size and number of keys |
| Test bench | Try the codec with a real payload |
| The codec table | The table itself (read-only for library codecs) |
The page also reminds you: Downlinks are sent as raw hex or base64. Codecs decode only; see Sending downlinks.
Test a codec
- Open the codec and scroll to Test bench.
- Enter the FPort (1–255) and the Payload (hex) the device sent (spaces allowed, at most 255 bytes). Copy the payload from your device’s maker tool, or from a message decoded with None.
- Select Decode.
The bench shows the decoded Key, Value and Unit, any Warnings and Errors, and Bytes left over when the codec did not use all bytes. The codec did not recognise this frame. means the codec has no rule for this FPort or payload shape.
Output key names
Library codecs name their keys the way the device maker’s documentation names them, for example temperature_red or a text state such as "occupied". Different makers use different names for the same quantity. If you want one naming across your fleet, see Cleaning up decoded values.
Changes to the library
- The platform updates the library over time. A new revision of a codec may add keys but never removes or renames one, and never changes a key’s unit. Your flows and dashboards keep working.
- A codec can be Withdrawn by the platform. Devices that chose it decode with the automatic choice instead.
- Library codecs are read-only for you. To change one, use Save a copy; see Write your own codec.