Commissioning checklist

Part 4 — Operate and fix.

---

Work through this before handing an installation over. Most of it takes minutes; all of it is cheaper now than after the client has moved in.

---

29.1 The project

• Every unit in Device manager has a Description — not just an address

• Every address matches the physical hardware

• No yellow dots on any floor plan — check every floor

• Every wire in Wire manager has a Name

• Project settings carry your name and email as author

• The project version is set, ideally with Increment version before save on

• Prefernces shows nothing close to a limit

• The .elp is saved somewhere it will be backed up

• If custom function blocks are used, the funcBloks templates are exported as .fncb or Save function blocks templates to project file is on

29.2 The central unit

• IP address, Mask and Gateway are correct — and written down

• DNS1 / DNS2 set if the CU needs internet

• NTP server set and Time zone correct

• CU time matches IDM time

• Error code is clear

• Firmware is at or above the recommended minimum for every unit

• Cloud, MQTT or Modbus configured and tested, if used

• Passwords set — and recorded where the client can retrieve them

Time zone deserves a second look. It silently shifts every schedule in the building by an hour, and nobody notices until the seasons change.

29.3 Function testing

Test physically, not by reading the project.

• Every light switches from every button that should control it

• Dimmers reach full and zero, and hold at intermediate levels

• Hold-to-dim stops on release — no light creeping to 100 %

• Blinds run fully up and down, and stop when commanded

• Blind tilt is a tilt, not a full run

• Every group responds — and contains everything it should

• "All off" leaves nothing on. Walk the building and look.

• Scenes set the levels intended

• Each heating area's Actual and Required temperatures look sane in Monitor

• Heating actually fires — valve and boiler demand both

• Antifreeze temperature set on every heating area

• Time programs fire at the right times

• Sunrise/sunset switching happens at roughly the right moment

• Timers expire after the expected interval

• SMS and calls arrive on a real phone

29.4 The awkward cases

The ones that come back as callbacks:

• Power-cycle the central unit. Does everything return to a sensible state?

• Non-volatile system bits survived that reboot

• Two people pressing different buttons at once behaves sensibly

• A held button that is never released does not leave a light climbing forever

• Conditions that gate on time-of-day work outside the hours you tested in

• Heating does not fight cooling

• What happens if a temperature sensor fails?

29.5 Handover

• The client knows what every button does

• Written down, per room, and left with them

• They know how to change heating temperatures themselves

• They know who to call

• A copy of the .elp is stored somewhere they can get it

• Your author details are in the project

• The final project is uploaded and "Projects are the same." confirms it

---

29.6 The last check

Connect and confirm:

"Projects are the same."

If it says "Projects are NOT the same!", the central unit is running something other than the file you are about to file away as the record of this installation. Resolve it before you leave.

---

Next: Chapter 30 — Troubleshooting.