How to change a setpoint
Setpoints are the values you can write back to the installation — desired room temperature, flow temperature, operating mode. It's the one module in Properate where you change something in the building rather than just read it.
You need write access to setpoints to change values.
How to change a setpoint
- Open the building you want to work on. See How to switch building and search for a building.
- Go to Setpoints in the sidebar.
- Find the setpoint in the table.
- Click Update on its row.
- Type the new value into Value. The dialog shows Min: {value} and Max: {value}.
- Set the Priority.
- Save.
If it fails, the message says Couldn't update setpoint. Try again.
If the value is outside the limits it says The value must be between {min} and {max}. If the value is missing: Set a value.
The columns in the table
Column | Contents |
|---|---|
Sub-building | the zone the setpoint belongs to |
System | the installation |
Name | the setpoint's name |
Priority | its current priority level |
Min and Max | permitted limits |
Value | the current value |
Link | the link to the measurement |
Location | where in the building |
Unconfirmed connection | links that haven't been confirmed |
Priority — the most important thing to grasp
A setpoint can hold values at several priority levels at once, from Priority 1 to Priority 16. The lowest number wins. The tooltip says it directly: Manual override adds a higher-priority setpoint value.
That means a manual change you make overrides the automation — and it keeps overriding until somebody removes it.
Note: This is the most common mistake with setpoints. Set a value manually to test something and it stays there, blocking calendar control, cloud automations and operating curves. Use Set priority 16 to place the value at the lowest level, so the automation can still override it.
If the change is meant to be permanent, it usually belongs in the calendar or in an automation instead — see How to add an event to the calendar.
Links
Link shows which measurement the setpoint is connected to. Click to edit:
- Link to value — the measurement
- Suggested alternative links — if Properate has other candidates
- Confirm connection — for an Import link that hasn't been confirmed
- Remove link
If no link is set, it says No link is selected.
The Unconfirmed connection column shows links that arrived from an integration without anyone confirming them. Worth reviewing: an unconfirmed link may point at the wrong measurement.
Fault codes
If there's a fault on the object, a fault code is shown. The most common:
Code | Meaning |
|---|---|
No fault detected | all in order |
Communication failure | The object depends on communication with a remote sensor or device, and that communication is lost. |
Configuration error | The object's properties are not in a consistent state. |
Frequently asked questions
How long does my change apply for?
Until somebody changes it again, or until a higher-priority value is entered. A manual override has no expiry.
How do I remove a manual override?
Remove the value at the priority level you entered it at, and the setpoint falls back to the level below.
Why didn't the installation change?
Check whether a higher-priority value is present. Check the fault code too — if communication is lost, the write doesn't get through.
Can I create a setpoint that doesn't exist in the installation?
Yes, a virtual setpoint — see How to create a virtual setpoint.
Tip!
Write a note or an FDV note every time you enter a manual override, saying why and for how long it should stand. An override nobody remembers is nearly impossible to find again — it looks like the installation's normal operation, and it can sit there for years.