Define what the controls should do
Automation connects sensors, actuators and decision rules. Its value comes from a specific task: maintaining temperature, limiting demand or changing operation when occupants leave. Describe the desired building behaviour before choosing devices. A collection of apps does not demonstrate that heating, ventilation and shading will cooperate or that occupants can understand the resulting controls.
Give each function an authority
Identify the main controller and priorities for every function. Heating and cooling can oppose each other if separate controllers issue conflicting commands. Sensor location matters: direct sunlight or a nearby warm air stream may make a reading unrepresentative of the room. Review switching delays, hysteresis and restart behaviour, as well as the nominal temperature setting shown on the screen.
Prepare for lost connections
An internet outage, a flat sensor battery and a failed central controller require different responses. Decide which functions must remain local and manually accessible. Protective duties need appropriate hardware; a consumer cloud routine cannot replace electrical protection. Hand over access credentials, a settings backup and a documented recovery route so that routine operation does not depend on one installer remaining available.
Test complete scenarios
At acceptance, simulate loss of connectivity, changes in occupancy mode and restoration of power. Compare the response with an agreed scenario table, including fault indications. Event logs can help explain excessive consumption when timestamps and signals are consistent. A function and priority list is enough to begin an automation discussion; compatibility of particular devices must then be checked against their documentation. Successful button operation alone is not evidence that failure modes have been handled.