Docs / Reference
Troubleshooting
Common problems with the Connector, discovery, values and refused changes.
The site shows "Site offline"
- Is the Connector service running on the site computer? Check its log.
- Can that computer reach the internet on TCP 443? A proxy that inspects TLS can break WebSockets. Allow Rotorloop through it.
- Was its connector revoked, or the token mistyped? The log says unauthorized. Add a new connector and use the new token.
"No data for …" (amber)
The Connector is connected, but values have stopped arriving. Usually the controllers stopped answering: a network change, a controller rebooting, or a busy MS/TP trunk. Values shown are the last ones received, with their time.
No BACnet devices found
- Local firewall. Allow inbound UDP 47808 on the Connector's computer. Without it, the replies to discovery are dropped.
- Wrong subnet. Broadcasts don't cross routers. Use a network card on the controllers' subnet, or list those controllers by address in the config. Registering with a BBMD is planned. See Installing the Connector.
- Port already in use. Another BACnet tool on the same computer (a workbench, a BACnet browser) may hold UDP 47808. Close it.
Modbus values look wrong
- Shifted by one register: check 0-based versus 1-based numbering.
- Huge or nonsense 32-bit values: swap the word order.
- Ten or a hundred times too big: set the scaling from the register map.
My change was refused
| Message | What to do |
|---|---|
| is read-only | Ask an admin to allow changes on that point. |
| above / below the allowed value | Pick a value inside the range, or ask an admin to widen it. |
| was just changed | Wait a moment. There's a minimum time between changes. |
| must stay on / off at least … | Equipment protection. Try again after the time shown. |
| life-safety point | Never changeable from Rotorloop. |
| site is offline | Nothing was sent. Try again when the status is green. |
| controller did not accept | The device refused the write. Often the point is out of service, or held at a higher priority by the building's own logic or by someone on site. |
A hold didn't seem to take effect
On BACnet, a higher priority (lower number) wins. If the building's own program or a technician on site holds the point at a higher priority, Rotorloop's hold is stored but not in control. Your controls contractor can tell you which priorities the site's programs use.
Applies to Rotorloop 0.2 (development preview). Last reviewed November 2026.