1. Context

When upgrading or replacing an AnywAiR ANY1 Controller with an ANY2, users may temporarily see both systems displayed in the AnywAiR Ducted App.
This occurs because residual pairing data from the original controller remains cached in the app.
To ensure a clean transition, the following procedure removes the legacy record and re-establishes connection with the new controller.


2. Recommended Procedure

Step 1: Remove the Existing App

  1. On the customer’s mobile device, delete (uninstall) the AnywAiR Ducted App completely.

    • This action clears all locally stored system pairings and configuration data.


Step 2: Reinstall the App

  1. Reinstall the latest version of the AnywAiR Ducted App from the appropriate store:

  2. Launch the app after installation.

  3. On startup, the app will display the message:

    “No systems paired (FG71)”
    This indicates that no previous controller records remain on the device.


Step 3: Pair the New ANY2 Controller

  1. Ensure the ANY2 controller is powered on and in pairing mode (Wi-Fi indicator flashing).

  2. In the app, select “Add System” or “Pair New Device.”

  3. Follow the on-screen instructions to connect to the controller via your 2.4GHz Wi-Fi network.

  4. Once pairing is complete, the app will recognize only the new ANY2 system and associate it with the customer’s account.


3. Validation

After successful pairing:

  • Confirm that only one system appears in the app’s system list.

  • Verify full functionality — including mode control, zoning, scheduling, and temperature monitoring.

  • Optionally, log out and back into the app to confirm persistent pairing to the new controller.


4. Notes & Best Practices

  • Always verify that the old ANY1 unit has been physically disconnected or reset before pairing the new device.

  • If multiple controllers appear even after reinstallation, perform a network reset on the new controller and repeat the pairing process.

  • Customers using multiple devices (phones or tablets) should repeat this process on each device to prevent cached data conflicts.