Integrations
Connects to whatever you run
Open protocols, over an appliance that joins the network and finds the controllers. Nothing is ripped out, and the existing head end keeps doing its job.
01Protocols
What we read, and whether we write
Read and write are stated separately, because they are not the same commitment. Vairitas reads widely. It does not command plant.
ProtocolVendorAccessStatusNotes
BACnet/IPOpen standardReadLiveDiscovery and object enumeration across any conformant controller.
TrendHoneywellReadLiveIQ controllers, including those behind a vCNC gateway.
Tridium NiagaraHoneywellReadLiveAX and N4 stations over oBIX.
Modbus/TCPOpen standardReadPlannedMeters and industrial devices, on the roadmap.
MatterportMatterportReadLiveWalkable scans with live telemetry pinned into them.
No inbound path, and no write path
The appliance polls outbound over HTTPS and is never addressed inbound. It holds a secret scoped to its own site, so one box cannot act as another. Where a protocol supports writing, we still do not command plant in normal operation.
Not sure what is on your site?
Most estates do not have a current inventory of their own controls. Finding out is the first thing we do, and it does not require one.