FreeMaint Connect: connected devices and sensors

What FreeMaint Connect does, which devices it supports, what the Business plan includes and how measurements turn into maintenance.

5 min read
Print this section

FreeMaint Connect brings live measurements from your meters and sensors into FreeMaint — electricity, temperature, humidity, current, vibration or any value your own system can send — and turns them into maintenance: alerts, work orders, run hours and energy reports. It has its own section in the menu: Connected devices.

How it works

  1. Create a connection — In Connected devices → Integrations, click Connect a device and choose where your measurements come from: a Shelly meter, a LoRaWAN network (The Things Stack, ChirpStack, Milesight gateway) or the HTTP API.
  2. Paste what FreeMaint shows you — FreeMaint displays an access key and, depending on the source, a script, a URL and a header. You paste them into your device or platform — no integrator needed.
  3. Devices appear by themselves — A device that sends data for the first time appears in Connected devices → Devices, with one channel per measurement (for example power, energy, temperature).
  4. Put the measurements to work — Attach a device to an asset, watch a channel with an alert rule, feed an asset meter for meter-based preventive maintenance, or feed an energy meter for cost and CO₂.

Three words to know

Integration

One connection with its own access key: a Shelly script, a LoRaWAN application, a gateway or your own script. You can pause it, rotate its key or delete it.

Device

A physical meter or sensor that sends data through an integration. It shows its state (new, online, late, offline), its battery and signal when available, and its last message.

Channel

One measurement of a device — for example the power of phase A or a temperature. Alerts, history curves and meter links are set per channel.

Supported devices

These models are recognised automatically and their data is decoded by FreeMaint. They carry the Compatible badge: validated on the manufacturer's documentation. The Lab-tested badge is given once a model has been tested on the physical device.

  • Shelly Pro 3EM, Shelly EM Gen3, Shelly Pro EM-50, Shelly Plug S Gen3 and Shelly 1PM Gen3 — Wi-Fi or Ethernet energy meters, plugs and relays.
  • Milesight CT101 — LoRaWAN current transformer clamped on a cable.
  • Milesight EM300-TH — LoRaWAN temperature and humidity sensor.
  • Any other system that can send JSON over HTTP: Node-RED, Home Assistant, a PLC gateway or your own script.

Plans and limits

Connecting devices and editing alert rules requires the Business plan, which includes 100 active channels. The Enterprise plan includes 5,000. An inactive channel does not count toward the limit. Data you already collected stays visible on every plan.

Tip

FreeMaint does not speak Modbus, MQTT, BACnet or OPC UA directly. A gateway that reads those protocols (Node-RED, Home Assistant, a Teltonika router) can forward the values through the HTTP API.

Who can do what

View connected devices and their readings

Seeing devices, channels and history requires the Connect read permission.

Manage integrations, devices and channels

Creating integrations and editing devices or channels requires the Connect manage permission.

Manage alert rules (thresholds, zones, automatic work orders)

Creating and editing alert rules requires the alert rules permission (Administrators and Managers by default).

View and acknowledge device alerts

Seeing and acknowledging alerts requires the alerts permission (Administrators, Managers, Supervisors and Technicians by default).

Was this page helpful?