Metasys Setpoint Commands Don't Work or Stick

Problem

Changing a thermostat setpoint or control value in Metasys UI doesn't update the actual controller. Value reverts immediately or doesn't register at all. Effective setpoint won't budge.

Root Cause

BACnet priority array is locked at priority 16 (highest override), or the setpoint isn't linked to any actual control logic in the controller programming.

Solution

1. Check if Point is in Local Control:

   • In Metasys UI, right-click the setpoint point
   • Go to Properties and look for a Hardware or Local/Remote Control tab
   • If it shows Local, the point is bypassed and remote commands are ignored
   • Switch to Remote mode if allowed

2. Release Priority Array Lock:

   • Right-click the setpoint point in Metasys UI
   • Select Command → Release All
   • This clears all BACnet priorities and allows new commands to write at priority 16

3. If "Release All" Doesn't Work:

   • The programmer may have written logic that overwrites your command
   • Example: The VAV program sets its own setpoint at priority 8, overriding your priority 16 write
   • Use the CCT (Controller Configuration Tool) to inspect the actual controller program and find the conflict

4. For Thermostat-Specific Issues:

   • Check if the thermostat has a local override (buttons on the device itself)
   • If someone set a local override on the thermostat, Metasys commands won't override it—must clear local override first
   • Check both occupied and unoccupied setpoint values (you may be changing the wrong one)

5. After Changing Setpoint:

   • Verify the controller reloaded the new program/config (may require reset or reboot)
   • Sometimes a controller power-cycle is needed to pick up changes

6. If Issue Persists:

   • Ask the programming tech to check the CCT file—the setpoint binding may be broken or not linked to anything