1.7 Troubleshooting and Escalation
1.7 Troubleshooting and Escalation
In this lesson: you will be able to run the basic checks and know when — and with what information — to call for support.
Your job: quick checks and good escalation
Things occasionally go wrong. As an operator, your job is not to fix the deep faults — it is to do the quick checks and escalate well.
A controller shows offline
First, is it just one, or all of them? One offline usually means that controller lost power or has a wiring/comms issue on the bus. All offline usually means the gateway itself lost its connection to the bus — check that the gateway is powered and connected.
A value looks wrong or frozen
Check the last-updated time on the Dashboard. If data has not refreshed, it is a comms problem, not a bad sensor. If it is refreshing but the number looks wrong, note the point name and value — that is useful detail for whoever you escalate to.
Something is behaving oddly
Check the Dashboard for that amber override banner — a forgotten override is a very common cause of “the system is not doing what it should.”
Escalating well
When you do need to escalate, give good information: which controller by name and address, what you observed, when it started, and whether it is one controller or many. That turns a vague “it is not working” into something your integrator can act on quickly.
And remember your limits by role — programming and bus changes are deliberately above the operator level. Escalating is not failing; it is the right call.
Key points
- One controller offline usually points to that controller's power or bus wiring; all offline points to the gateway's connection.
- The last-updated time distinguishes a comms problem (not refreshing) from a bad reading (refreshing but wrong).
- A forgotten override is a very common cause of odd behaviour — check the amber banner.
- When escalating, give controller name/address, what you saw, when it started, and one vs many controllers.
- Programming and bus changes are above the operator level by design — escalating is the right call.
Check your understanding
- One controller is offline but the others are fine. What does that usually point to?
- A value looks frozen. What single thing tells you whether it is a comms problem?
- Name two things to include when you escalate an issue.