Modbus integration
Collecta polls Modbus TCP devices such as HVAC controllers, energy meters and field sensors, reading their registers into modules on a schedule. Register values map onto typed custom fields so you can chart consumption, alert on out-of-range readings and run the data through automations and the AI agent — no SCADA layer required.
Capabilities
Poll Modbus TCP sensors and meters.
Poll Modbus TCP devices including HVAC controllers, meters and sensors
Read holding and input registers into Collecta modules
Map registers onto typed custom fields with scaling
Schedule polling intervals to match each device
Trigger alerts and automations on register thresholds
Visualize meter and sensor trends on dashboards
How it works with Collecta
From Modbus to live operations.
01
Connect
Add the connector, authenticate, and Collecta validates the link — credentials are encrypted at rest with AES-256-GCM and isolated per tenant.
02
Map to a module
Each entity, topic or device maps to a Collecta module. Fields become typed custom fields with permissions, validation and visibility rules.
03
Operate
Run automations, approvals, alerts and reports on the synced data — and query it all with the Claude-powered AI agent.
Synced data lives in the same multi-tenant workspace as your custom fields, automations and AI agent · config encrypted with AES-256-GCM · five-minute to daily intervals.
FAQ
Modbus, answered.
Modbus is a request/response protocol, so Collecta polls devices over Modbus TCP on a configurable interval and writes the returned register values into a module.
Collecta reads from typical Modbus TCP equipment such as HVAC controllers, energy meters and TCP-connected sensors.
Yes. Registers map onto typed custom fields, and Collecta formulas and automations can scale, combine and act on the values once they are ingested.