Terminology Update
In line with best practice and inclusivity, we have updated the terminology used throughout our system interfaces and support documentation:
- Load Controller (formerly Master)
- Secondary Device (formerly Slave)
- Gateway Device (formerly vHub Device) – Please note that a Load Controller does not necessarily need to be a vHub-enabled unit.
When setting up a myenergi eco-system, it is essential to pair devices correctly. The system always includes a primary Load Controller (master).
This article outlines the correct pairing procedure for each device type, including guidance on re-pairing. If re-pairing a device, you must first remove it from the Load Controller (master)'s linked device list before initiating a new pairing attempt.
zappi 2.0, zappi 2.1, eddi, libbiThe pairing process for our screen-based devices (zappi, eddi, libbi) is largely the same, although menu names may vary slightly. Begin by identifying the device to act as the Load Controller (master). NOTE: If you are pairing to a zappi GLO, please see the zappi GLO section.
On each Secondary Device (slave):
To initiate pairing:
|
harviTo pair a harvi device:
Pairing is complete once the countdown timer reaches zero and the question mark icon disappears. |
hubTo pair the hub device:
The pairing completes when the timer reaches zero and the question mark disappears from the screen. |
Repairing into an existing systemTo re-pair a device, it must first be removed from the Load Controller (master)'s linked device list:
Once removed, follow the appropriate pairing process again as outlined above. |
Connecting with zappi GLOWhen pairing and creating an ecosystem for zappi GLO, you will need to use the Installer Assistant App. If zappi GLO is the first myenergi product on site
If zappi GLO is being added to an existing myenergi setupImportantYou will need access to the existing device(s) to complete this process.
If pairing to an existing zappi GLO
|
eco-system Pairing Golden Rules
When pairing devices into an ecosystem, it's important to follow the rules below to ensure a successful setup and avoid any disruption to existing settings or data:
-
All devices must use the same radio channels.
Before starting the pairing process, double-check that all devices are configured to use the same radio channel. If the channels differ, the devices will not be able to communicate or join the same ecosystem. -
Only one Primary (Master) device is allowed.
The Primary device acts as the Controller for the entire ecosystem. You must not attempt to pair a second Primary device, as this will cause conflicts and prevent devices from linking correctly. -
Only one Gateway (vHub) device is permitted.
The Gateway handles all external communications (such as internet access). Having more than one can result in communication failures or data routing issues. -
Keep the existing Primary (Master) device wherever possible.
If you already have a functioning ecosystem, avoid changing the Primary device. Replacing it will reset the device hierarchy and could result in the loss of stored usage data, user settings, and historical logs. Only replace the Primary device if absolutely necessary.