Phone control starts with a compatible controller and a working connection at the pergola. It does not follow automatically from buying a motorised roof. Before adding Wi-Fi control, identify the equipment you want to operate, check the Australian controller documentation and decide how everyone in the household will use it.
Swipe the table sideways, or focus it and use the arrow keys.
| Check | Evidence to keep |
|---|---|
| Equipment match | Model and controller references; confirmed supported functions. |
| Network readiness | 2.4 GHz setup availability and a practical connection check at the controller position. |
| Individual response | A named control matched to the correct visible device. |
| Shared use | Account owner, authorised household access and the normal physical-control method. |
Start with the actual devices
List the roof, lighting and each powered side accessory separately. Record the pergola model and any controller references from your order. The Australian RF Controller listing describes app control for several device categories, but that is not confirmation that every existing motor or accessory is compatible. Ask for the match for your actual equipment before ordering.
Give devices practical names such as “garden-side screen” rather than relying on a numbered channel. Keep the physical remote reference beside each name. This makes it easier to notice when an app button has been paired with the wrong device.
Check the connection where it will be used
The RF Controller manual linked from the Australian listing specifies Smart Life and a 2.4 GHz Wi-Fi network for setup. Check that the relevant network is available and usable at the intended controller position. A strong signal indoors does not establish reliable operation beyond an external wall.
Do not use the manual’s open-area RF range as a promise for your patio. Walls, location and the actual installation matter. Keep network passwords private; provide the installer with the access they need through an agreed process rather than putting credentials in a general project document.
Test one function before creating a scene
Follow the matching manual for pairing. With the moving area clear and the device visible, identify what each control actually operates. Confirm the intended response before adding several devices to a combined command. A scene that moves a roof and a side screen together is useful only when both individual mappings are correct.
An app command is not evidence that the pergola has a weather sensor, obstruction detection or a verified closed-state report. Do not add those expectations unless the exact equipment documentation supports them.
Make household access part of the handover
The manual describes family invitations through Home Management. Agree who manages the account and how another household member receives access. Confirm the appropriate sharing process before resetting a controller; the manual also describes a reset-based second-phone procedure, so a reset should not be your default way to add a family member.
Keep the normal physical controls available and learn the documented response to a lost connection. Before relying on the setup, leave with a device list, the matching manual and a clear route to support. Phone control should make a known system easier to use, not hide which part is moving.