Docs / Reference

FAQ

Short answers to the questions facilities teams and IT ask first.

Does Rotorloop replace our BMS?

No. Your controllers and their programs keep running the building. Rotorloop is a clearer, safer way to see and adjust what they control, across brands.

What happens if Rotorloop goes down?

Nothing changes in the building. Controllers keep running their own programs, and active holds still end on time because the Connector keeps the timers at the site.

Do we need to open firewall ports?

No inbound ports. The Connector needs outbound TCP 443, plus local access to your controllers (UDP 47808 for BACnet, TCP 502 for Modbus).

Can someone set a room to 90° and leave it?

Only within the range an admin set for that point, and only for a limited time: every hold ends by itself, 12 hours at the most.

Will it fight our controls contractor's programs?

On BACnet, Rotorloop writes at an ordinary operator priority (8 by default). Anything the building's programs hold at a higher priority still wins, and ending a hold hands control straight back.

Which brands work?

See Integrations for the full list and honest status of each. Most commercial buildings connect over BACnet/IP, directly or through a gateway.

Is it only for HVAC?

No. HVAC is where we started, but the model is general: any point a controller reports, including pumps, meters, lighting, generators and process equipment.

What does it cost?

Pricing will be set with the first early-access sites. Request early access to talk it through.

Applies to Rotorloop 0.2 (development preview). Last reviewed November 2026.