Required tools
Replacing the uControl Remote’s battery (Step-by-step instructions)
Author Archives: HDANYWHERE Support Team
What MHUB systems does uControl Remote support?
uControl Remote will work with any HDA system marked “uControl inside”. These are typically MHUB’s, MZMA or uControl Zone Processors which shipped with uControl OS (uOS) version 10 or above. MHUB’s which were installed with MHUB-OS (MOS) will not support the uControl Remote, but some can be upgraded (see below).
| List of systems that support uControl Remote | ||
|---|---|---|
Natively Supported |
||
| MHUB (4×1+1) 40 | ||
| MHUB (4×4) 100A | ||
| MHUB (6×6) 100A | ||
| MHUB S (8+8×8) 100A | ||
| MHUB S (16+16×16) 100A | ||
| MZMA (6×4) 55 | ||
| uControl Zone Processor 1 | ||
| uControl Zone Processor 5 | ||
| uControl Connect Processor | ||
UpgradableREQUIRES A UCONTROL ZONE PROCESSOR 1 |
||
| MHUB PRO 2.0 (4×4) 40 | ||
| MHUB PRO 2.0 (8×8) 100 | ||
| MHUB U (4×3+1) 40 (coming soon) | ||
| MHUB U (8×6+2) 40 (coming soon) |
Supported Stacked SystemsREQUIRES A UCONTROL ZONE PROCESSOR 1 |
|
| MHUB PRO 2.0 (4×4 & 8×8) & MZMA | ||
| MHUB S (100A) & MZMA | ||
| MHUB S (100) + MHUB S (100A) | ||
uOS First Boot Process for Standalone & Stacked Systems
uOS 11 – A Guide to Every Page
IMPORTANT: For the best setup experience, we recommend using a tablet or laptop instead of a smartphone. Using a larger screen makes it easier to navigate the setup process and view all the options clearly.
Pages
Accessing the menu
THIS GUIDE IS FOR uOS 11 AND ABOVE:
This guide is for HDA devices that are operating uOS 11 or above and have completed the First Boot Process. This guide does not apply to ANY hardware running MHUB-OS or uOS devices that are running on version 11 or lower. How to update your system.
Accessing the menu
The uOS interface features a hidden dropdown menu that provides access to all system settings. To reveal the menu, simply click on the uControl logo located in the top left corner of the screen.
Control Panel
Web Interface for direct control of system state.
Gives users direct access to the system state via a web interface, bypassing any other control methods. Control is grouped by Zone and will differ depending on what outputs from your HDA device were assigned to them. For example, if you add a video output and an audio output in a Zone named “Living Room” then uOS will display both video switching, audio switching and (hardware dependent) volume controls in the “Living Room” section of the Control Panel
What can you control?
- Source Selection: Choose which video or audio source is routed to the Zone in question.
- Volume: If your HDA device supports volume control then a slider and mute controls will appear.
- System Power: At the bottom of the page is power control for the entire system. It is recommended to use this control only if you wish to turn the entire system off.
What to do if you can not see any controls on this page or controls do not appear to be working correctly.
Ensure that you have created your Zone and assigned either a video or audio output from your HDA device to it. If you are still experiencing a problem, contact HDA Support.
When to use the Control Panel
The web interface is a valuable troubleshooting and backup tool if you have lost control from your normal control method. If you’re experiencing issues with your HDA system, try controlling it directly through this page.
Inputs (Sources)
Management of connected AV input devices.
This page allows you to manage all the AV source devices connected to your HDA system.
- Custom Naming: Give your devices meaningful names (e.g., “Blu-ray Player” instead of “Input 1″) for easy identification throughout the system.
- Global Visibility: Control which input sources are available system-wide. For example, if you have an 8-input system but only use 5 sources, you can disable the unused inputs (6, 7, and 8) so they appear nowhere in uOS. Important: Hiding an input here makes it unavailable across your entire system, unlike Zone-level visibility settings which only control source visibility of active inputs. This is manaaged from the “Zones” page.
- Manage Connections: Tell uOS how multiple HDA devices are connected to one another if you are operating a Stacked System
Zones
Manage the Zones in your system.
.
This page is for configuring and customising the Zones within your HDA system. This page provides a clear overview of your entire system from one place.
Key functions on this page
- Zone Naming: Personalise your Zones with names that make sense to you (e.g., “Living Room” instead of “Zone 2″).
- Source Visibility: Control which AV input sources are available in each Zone. For example, you might want to make the “Blu-ray Player” source available in the “Living Room” but not in the “Kitchen.”
- Zone Configuration: Add or remove Zones from your system or change what outputs from your HDA device are assigned to them.
If you are using uControl to control your system, then these Advanced features are also recommended.
- Zone (On/Off) Automation: Select what Sequence is assigned to the Zone ON and Zone Off (e.g. TV off, lights off) event.
- Default Volume Control:Choose which device from your uControl library has primary control over the Zone’s volume.
Recommendation:Add or remove Zones from your system or change what outputs from your HDA device are assigned to them.
AV Settings
Fine-tune your audio and video settings.
.
This page allows you to customise advanced audio and video settings for your HDA system to achieve optimal performance. This page displays settings specific to your HDA device hardware. If you have a stacked system with multiple HDA devices, you’ll find settings for each device grouped by hardware name and type. This allows for granular control over each device in your system.
Key functions on this page
- EDID Management: Control how your HDA device communicates with displays to ensure compatibility and optimal resolution.
- Video Scaling: Adjust how video content is scaled and displayed on your screens.
- Audio Volume Presets:Configure input gain and max volume levels for sources and Zones.
- EQ Settings:Fine-tune audio equalisation for specific Zones or outputs.
Devices
Add new devices to uControl or manage how they work.
.
Control your devices and their features seamlessly through the uControl app, a uControl Remote, or Smart Automations. To get started, click or tap on the button labelled “ADD NEW DEVICE” and simply find and install the appropriate uControl pack, driver or establish a uControl IP connection for any Smart Devices (eg, lights, blinds, PDUs etc).
Once installed, all devices that uControl can control will appear here along with any important data such as the current IP address, what input or output the pack is assigned to and the ID.
It is also possible to test CEC commands from the pre-installed uControl CEC pack. This is available at the bottom of the page if your HDA devices supports HDMI-CEC control.
Add device control to uOS
AV Device: select between installing a uControl pack (IR, IP or a Driver) for AV devices like TVs, Blu-ray players, AV receivers, and set-top boxes.
.
Choose between a uControl (IR or IP) pack for the device and select which input or output it is connected to. The AV device might not be connected to an input or output, and can be assigned to a Zone instead.
.
.
A detailed step-by-step guide can be found here: How to install a uControl pack.
Smart Device: Create a manual IP connection to smart home devices such as smart lighting, blinds/shades, and power sockets/plugs within your Zones.
A detailed step-by-step guide can be found here: Cheatsheets for common Smart Devices.
Smart Automations
Powerful automations to enhance your uControl experience.
Create powerful automations, called Sequences (a series of commands executed one after another), and add intelligence to them using Functions with “if this, then that” rules to enhance and automate your uControl experience.
You can create Sequences that can turn your HDA device on or off, switch and route inputs or control the volume state in any zone. If you wish to enhance these further with AV device or Smart Device control then ensure you have installed uControl packs for them or have established IP connections before creating your Smart Automations.
Key functions on this page
- Sequences: A sequence is a series of commands executed one after another. For example, a “Movie Night” sequence might dim the lights, lower the blinds, turn on the TV, and start your Blu-ray player.
- Functions: Functions add intelligence to your automations. They can be custom commands or (“if this, then that”) logical rules. For example, a function could automatically adjust the thermostat when the temperature outside changes or turn on the lights when motion is detected.
Scheduling
Automate your Smart Automations with Scheduling
After your Smart Automations have been created you can choose to schedule them to suit your project requirements. For example, you may want all displays in an office environment to turn off at 7pm and for this to happen every Monday to Friday.
Remotes
Configure and customise your uControl Remotes.
ADD YOUR REMOTES LAST:
Once you’ve configured your system Zones, installed all packs, set up Smart Automations, and tested everything in the uControl app — it’s time to add your uControl Remote.
Why wait?
This approach streamlines the Remote setup process. By configuring your system first, the settings are automatically copied to the uControl Remote, making the Remote configuration faster and easier. This ensures that your Remote is ready to use with minimal additional setup.
.
Getting the Remote on WiFi & configuring it for use.
A detailed guide on how to configure the uControl Remote can be found here.
Wall Mode
A simple interface for walls and desktop applications.
.
Design a simplified interface for the uControl app called “Wall Mode.” This mode will display only 6 large tiles on the iPad screen when held in landscape orientation.
Wall Mode is ideal for iPads mounted on walls or placed on tabletops. It makes using the app easier for newcommers or those that do not know how to use the system by hiding all the other menus and options, and presenting the user with just 6 essential controls for a single zone.
IMPORTANT:You can not configure Wall Mode until you have setup Smart Automations. It is recommended that Wall Mode is configured after any uControl Remotes.
To configure a tile, simply click or tap on the tile that you want to configure and add your Smart Automation to it. If uControl driver packs support wall mode configurations then you will have the option to add a driver widget to your tile (e.g Sonos) so that you can see realtime data on that particular tile.
Voice Control
Amazon Alexa voice control
This section allows you to enable or disable Amazon Alexa voice control for your HDA system.
Compatibility
Please note that voice control functionality depends on your specific HDA hardware and system configuration. If your system supports Alexa integration, you’ll find the following options:
A detailed step-by-step guide can be found here: How to configure voice control and account linking to your Amazon Account for the “AV Skill”.
Setup
General uOS setup
What you will find on this page
- Names and software versions: The official name for your HDA device(s) along with current software and firmware versions.
- Timezone: Set the timezone for uOS. By default, uOS will sync its time to GMT clocks. If you intend on using Scheduling to automate your Smart Automations then it is recommended that you set this to your timezone. This is a manual setting.
- Access control: Set a PIN code to lock access to uOS. It is STRONGLY RECOMMEDED that you keep a record of this PIN somewhere safe or connect your system to HDA Cloud so HDA Support can recover this for you. Once the PIN is set and in the event that it is forgotten or lost, only a system reset will recover your system.
User Accounts
Warranty extension and improved customer service
User Accounts connect your HDA device to HDA Cloud, our global data storage and service delivery platform. There are multiple benefits of connecting your HDA device to our cloud servers but the most common reason is the free warranty extension if this is done within 30 days of purchase.
There are two types of account: 1) Owner/User Accounts which belongs to the owner of the HDA device(s) being registered and 2) HDA Pro Accounts which can be used for monitoring the system remotely.
At all times the Owner Account has executive control of uOS, their HDA Cloud account and their HDA device hardware. It is possible to terminate HDA Pro access directly from this page. The absense of an Owner Account will keep the unit technically offline (with the exception of critical updates) and no information about the system or its state will be sent to HDA servers.
Network
Ethernet and WiFi settings for your HDA device(s)
Adjust uOS’ network settings to suit your Local Area Network configuration. IMPORTANT: proceed with care when changing these settings as you can lose connection to your controller if you make a mistake.
Advanced
Power-user access
Advanced settings for management and maintenance of uOS. Warning: This is an advanced area of uOS and changes here can affect system stability or potentially invalidate warranty status. Please use these tools carefully.
Before making any changes on this page, ensure you have a thorough understanding of the potential impact. If you are unsure about any settings, please contact HDA support for assistance.
Update your system to uOS 11
Please read this first before updating your system:
This guide will assist you with updating your MHUB, MZMA or Zone Processor to uControl OS (uOS) 11.
The update will enable support for both the new uControl App and the uControl Remote which can be configured after completing the steps in this support post.
It is strongly recommended that you read this guide carefully before you start the update process.
15 minutes (approximately). Difficulty: Easy.
What this guide will cover:
Before you start the update, check that:
- Your HDA controller is currently running uOS (10.XX)
- You have uControl 2016 app installed
- Your HDA controller and uControl 2016 app have access to the Internet
- All HDA devices and uControl 2016 app are visible on your network.
- A note of all HDA device IPs on your network, or the ability to scan for them using an app like Fing.
- IMPORTANT:Once your system has updated, uOS will need some additional configuration applied before the new uControl app or uControl Remote will start to work.
STACKED SYSTEMS:
It is recommended that every device in your stacked system is updated to uOS 11. Start by updating your master controller, followed by each MHUB or MZMA in your stack. If parts of your stacked system feature older MHUB’s or MHUB Audio systems running MHUB-OS then you will not need to update these.
1. Load uControl 2016 app to start the update process.
Load the uControl 2016 app and follow the instructions in this guide to update your system(s). Ensure that you complete this process for all HDA devices which can be upgraded to uOS 11 (see checklist above). Please note that any MHUB operating on MHUB-OS (black background colour) can not be updated to uOS 11.
2. Check that your HDA system has updated to uOS 11.
After the update completes, check uOS to confirm that it is running uOS 11 which can be done by visiting the IP address of your HDA device. Repeat this step for each HDA device on your network if you are operating a stacked system.
If you are using a control system (Crestron, Control4, Savant, URC etc) then you’re complete at this stage. If you plan to use a HDA interface like uControl Remote or uControl app to control your system then continue to Step 3 below.
3. You’re almost there! Prepare uOS for uControl app and uControl Remote.
You need to make two small changes in uOS to make ensure that the new uControl app or uControl Remote will work when you are ready to configure them.
Return back to the uOS “Setup” page and scroll down until you see the “Manage Zones” button, then select it.
A page will load with a table that lists all the Zones you have defined in uOS. Select the Zone that you wish to edit by tapping on the edit button (pencil icon)
You will now see all information pertaining to that particular zone, you will need to make two small changes for every zone in your system..
Change #1: Choose your video & audio source visibility.
uOS 11 gives you the ability to show or hide any input that is connected to your HDA system. You can choose to show all inputs or filter them so that only AV inputs you select are visible in that zone. If you’re unsure or in a rush you can choose “Select All” and edit this option later.
If you select “Filter” a list of all inputs that your HDA system is controlling will appear with a green coloured switch, here you can choose to turn that input on or off inside that zone.
Change #2: Set the default volume for every zone.
New to uOS 11 is a declaration of what device is controlling the volume. This is a new setting and will ensure that both uControl app and uControl Remote’s default volume keys are mapped to the device you choose here.
IMPORTANT:
You must repeat this step for every zone in your system if you wish to use the new uControl App or uControl Remote. If you fail to do this step uControl App will not work correctly and you may experience problems when configuring uControl Remote.
Your HDA system is now ready to use!
Congratulations, your HDA system is now updated and ready to work with the new uControl app and uControl Remote.
Configuring the uControl Remote for use
Before you begin:
To ensure a smooth setup process for your uControl Remote, please make sure you have the following in place before you start:
uOS 11 or above: The uControl Remote will work correctly with uOS 11 or above. Ensure that you have checked for updates beforehand.
Powered On: Press and hold the HDA Key (top left circular button) and the Power Key (top right circular button) simultaneously for 5 seconds.
Sufficient Power: Ensure the Remote is charging using the provided USB-C cable or a wireless charger.
Setup tested on uControl app: uControl Remote should be the last device setup in uOS. It is recommended that all uControl packs have been downloaded, all Smart Automations have been created and tested inside uControl app before transfering any configuration to .
20 minutes (approximately) to work through.
Contents:
In a hurry? Refer to the quick start guide in your packaging
The fastest way to connect your uControl Remote to your WiFi network is to refer to the quick start guide found inside your packaging.
If you need more help then a detailed version of this process is described below.
Getting uControl Remote on your WiFi network (full description)
1. Ensure that the uControl Remote is charging before you start
2. Turn the uControl Remote ON
3.Connect directly to uControl Remote’s WiFi
To connect to uControl Remote’s WiFi use password hdanywhere.
4. Access the uControl Remote’s Network Page.
At this stage, uControl Remote will scan all available WiFi networks within range. uControl Remote only supports 2.4GHz WiFi and WPA/WPA2/WEP security standards.
5. Wait for connection
Once the uControl Remote has joined your WiFi network, it will be given a new IP address, take a note of this IP address as you will need it when you configure your uControl Remote for use.
Starting uControl Remote basic configuration.
Make sure your uControl Remote is on the same network as you controller and that the Remote is charging.
Visit uOS and navigate to the “Remote” page.
Make sure that all uControl Packs, Smart Automations & Zone Settings have been completed before proceeding.
Enter your uControl Remote’s IP address.
Add your uControl Remote to your Zone or Room.
Optional step: rename your devices so they are easier to read on uControl Remote’s screen.
Select what will be doing the volume control in your Zone or Room.
More about volume: uOS will automatically select devices you’ve installed that offer volume control and will present them in this list based on how they are categorised by HDA. This includes TVs, Projectors, audio streamers/amplifiers (Wiim, Sonos), AVRs and HDA hardware like MHUB or MZMA.
If you have multiple devices that are all volume controllable (eg TV + AVR) then you will still need to nominate which device is default but uOS will transfer all options to the remote. This means you can switch away from the default option by pressing and holding the “AUDIO” key on the Remote. If you power down the remote or it is restarted, uControl Remote will revert to it’s default setting.
Basic setup is complete.
Troubleshooting Control4 with HDA
Included below are some troubleshooting steps we recommend carrying out if having issues with integrating Control4 with HDA devices:
Unable to connect your MHUB to the driver?
- There are many drivers to choose from so you must ensure you have the correct one installed, a link to our drivers page can be found here. There are drivers for basic switching or product specific drivers that offer a more in dpeth form of control, so it is vital the correct one is downloaded and that you are not using an old copy. If you are unsure which driver to download please contact support.
- Ensure that your HDA device has not changed its IP address.
- Try manually connecting to the system by inputting the HDA devices IP address into the driver, making sure to disable auto-discovery.
- Make sure that the devices are up to date.
- Go through first boot on MHUB-OS or uOS.
- Make sure you have set the unit to be powered on at all times in the driver by setting the state to true.
Connected but having issues controlling the system?
- In a Stacked System you will need to download a separate instance of the driver for each unit.
- Make sure the correct ports are assigned in the driver.
- If you’re using IR pass-through make sure to use our IR Transmitters.
Picture problems with laptop/PC and MHUB Stack
Picture problems can occur in an MHUB Stacked System when there is a laptop or PC as an input. The problem presenting itself can vary depending on the graphics card in the device and typically picture passes to the first MHUB in the Stack (S1), but not to the second MHUB (S2).
To resolve the issue we can place an HDMI Splitter MAX (1×2) in between the input (laptop/PC) and the Source (IN) port on MHUB. Your laptop or PC woud be connected via HDMI and plugged into the unlabelled input on the HDMI Splitter MAX (1×2), then taking another HDMI cable plug this into the HDMI port labelled A on the splitter and connect it into your desired input on the Foundation Layer (S1). For the second MHUB (S2) you would take another HDMI cable and plug it into the port labelled B on the Splitter, and connect it to the Source (IN) port on the second MHUB (S2).
If you are part of one of the unlucky 2% this issue affects please note that this is the most efficient work around to date, however, we are investigating a more permanent software fix for a future rollout. If this work around fails and the issue persists, which can happen please contact HDANYWHERE Support.
Wiring diagram:
Philips Hue Sync box and MHUB
Philips Hue Sync boxes can add a layer of depth to your home cinema experience, however, it can cause problems to a system as adding this switch at the display end can interfere with EDID and HDCP signals causing picture/audio problems.
While this issue does not always happen with a Philips Hue Sync box in an A/V distribution system, when it does there is a setting that can be disabled to work around it which is CEC.
There is an article on disabling CEC for your HDANYWHERE system which covers sending the command via a URL/web browser search bar, Hercules and Netcat. If you disable CEC and are still having issues with your Philips Hue Sync box please contact HDANYWHERE Support.
Enabling/Disabling CEC on your HDANYWHERE device
You may not need to use CEC or you have been prompted to disable it by support as it can cause conflicts between displays and external devices like soundbars, causing audio pass-through issues.
The examples in the guide focus on disabling CEC, however, to re-enable it replace “Off” with “On”.
There are 3 ways to disable CEC:
Please note
The command variable is x meaning you put the Output port here when you want to disable it. To disable Output A put 1, to disable Output B put 2 and so on. To disable all Output ports +1 to however many HDBaseT ports there are. For example if you have a 4-way matrix input 5 to disable all ports.
Using an MHUB S (8+8×8)? Make sure to only send HDMI command – CecOutxOff!
URL
To execute the command successfully you will need to be on a laptop/PC which is connected to the same network as your HDA device, and its IP address. For this example our HDA devices IP address is 192.168.0.149. Send it in your web browsers URL/search bar, the first command disables CEC for HDMI and the second command is for HDBaseT.
HDMI
192.168.0.149/api/instr?cmd=CecOutxOff!
HDBaseT
192.168.0.149/api/instr?cmd=CecFOutxOff!
If done correctly you will see a response saying “Cec Out x Off” for one Output that has been disabled or “Cec Out all Off” if all Outputs were disabled.
Hercules
Hercules SETUP utility
useful serial port terminal (RS-485 or RS-232terminal) , UDP/IP terminal and TCP/IP Client Server terminal. Produced by www.HW-group.com.
If you don’t have Hercules already download it using the link above, we can use it to send our CEC command to our device. Once installed run the software. Hercules only requires the command itself so you don’t need to include 192.168.0.149/api/instr?cmd= like you do in URL.
You should see a response in black below Received/Sent data saying CEC has been disabled if done correctly.
Nc
Netcat can be used to send direct commands to a device via TCP or UDP. You will need to open up your terminal and enter nc 192.168.0.149 8000 and press enter.
Please note 192.168.0.149 is only an example IP address and yours may be different. Below you will see both the HDMI command (CecOut1Off!) and HDBaseT command (CecFOut1Off!) being sent with their responses below, to exit press Ctrl + C.
IR transmitter positioning for popular brands
Some source devices need the IR transmitter to be placed in a very specific location. This page shows a number of popular controllable soure devices and their IR transmitter positioning incase you’re unable to locate it.
Sources:
Christmas and New Year opening and dispatch timetable
HDANYWHERE will be operating a reduced customer and dispatch service over Christmas and New Year. Dispatch will resume in the new year and the last day for dispatch is Thursday 21st. During this period a reduced customer service level will operate meaning Call Back Requests and WhatsApp messages will be temporarily disabled until January 2nd.
- Thursday 21st December 2023: Last day of dispatch
- Friday 22nd December 2023: No dispatch. Reduced customer service.
- Wednesday 27th December 2023: No dispatch. Reduced customer service.
- Thursday 28th December 2023: No dispatch. Reduced customer service.
- Friday 29th December 2023: No dispatch. Reduced customer service.
- Tuesday 2nd January 2024: Dispatch resumes. Full customer service.
MHUB 100A and MZMA Stack
Please read:
This guide will show you how to build a stacked system using an MHUB (4×4)/(6×6) 100A and an MZMA (6×4) 55 with uControl acting as the main method of control for the system.
Make sure the only HDA devices on the network are the ones you want to put into the Stacked System. If you still cannot discover them in the app consider your network infrastructure, the app may struggle to find the system(s) if there are things like network switches in the residence, so try simplifying it whilst going through setup.
This guide is intermediate in difficulty and assumes that you have installed MHUB before in standalone mode.
It is strongly recommended that you read this guide carefully before commissioning your stacked system to ensure all features of the system work as expected.
25 minutes (approximately) to work through.
What you will learn:
Checklist
To create a stacked system please make sure you have the following before you start:
- MHUB (4×4) or (6×6) 100A
- MZMA (6×4) 55
- Zone Processor, uControl Connect (x1)
- Audio cable(s) to create connections between your MHUB (4×4)/(6×6) 100A and MZMA (6×4) 55
CHECK SOFTWARE VERSIONS:
Check that ALL hardware above has been updated to the latest software version BEFORE you start configuration on uControl app.
Glossary
the following terms are used throughout this guide.
Foundation Layer
The MHUB system which is directly connected to a video source(s) is referred to as the Foundation Layer. Ideally, this system should be physically installed at the bottom of your MHUB stack. Inside uOS this system is referred to as S1 (see Stack Layer below).
Connections
A Connection is used to define the cabled connections between each component in an MHUB/MZMA Stack. The combination of HDA devices in your Stack will determine which ports can be paired or not.
Stack Layer
The Stack Layer is an alphanumeric identifier within uOS, starting from the Foundation Layer (Layer S1). This identifier represents the order of HDA systems that are connected to one another by a Connection. For example, if you had four HDA systems stacked together, then you would start with the Foundation Layer (Layer S1), then the second HDA device (Layer S2), followed by the third HDA device (Layer S3) and, finally, the fourth HDA device (Layer S4).
Master / Controller
An HDA device (like a Zone Processor) designed to control MHUB and/or MZMA (6×4) 55 systems operating in Stack mode. Any Stack that needs to be controlled by uControl must have a Master / Controller present in your setup. This is identified as M1 in uOS.
uControl
uControl is our control system for configuration and control of stacked systems. When we refer to “uControl” in this article we are referring to our app specifically.
Wiring
A video and audio system is made possible by the audio ports on the back of the MHUB (4×4)/(6×6) 100A and MZMA (6×4) 55. Connect the 3.5mm Stereo port labelled Audio (In) on the back of the MZMA (6×4) 55 to the 3.5mm Stereo port on the back of the MHUB (4×4)/(6×6) 100A labelled Audio (Out).
- “Audio (OUT)”
The audio ports on the back of the MHUB (4×4)/(6×6) 100A are labelled Audio (Out). - “Audio (In)”
The audio ports on the back of the MZMA (6×4) 55 are labelled Audio (In).
- Connect your 3.5mm stereo cables to the Audio (In) port of the MZMA (6×4) 55 and repeat for every zone.
- Connect your 3.5mm stereo cables to the Audio (Out) port of the MHUB (4×4)/(6×6) 100A and repeat for every zone.
- Connect speakers via phoenix connector into the Audio (OUT) of the MZMA (6×4) 55 and repeat for every zone.
- Connect your HDBaseT/network cabling into the Video (OUT) of your MHUB (4×4)/(6×6) 100A then into your display receiver and repeat for each zone.
Watch video: How to wire MHUB (4×4)/(6×6) 100A and MZMA (6×4) 55 stack
This video describes how to wire an MHUB (4×4)/(6×6) 100A with an MZMA (6×4) 55 to create a stack.
Initialising your Stacked Video and Audio System using uControl
Ensure that your MHUB (4×4)/(6×6) 100A and MZMA (6×4) 55 are correctly wired for stacking covered in the part above and that the following is completed:
- Both MHUB (4×4)/(6×6) 100A and MZMA (6×4) 55 systems in your stack are powered ON.
- Your Master / Controller device (Zone Processor or uControl Connect) is powered ON.
- All HDA systems and the Master Controller are connected to the LAN and reachable by their IP address.
- IMPORTANT: All hardware has been individually updated to the latest software version.
Configuring MHUB (4×4)/(6×6) 100A and MZMA (6×4) 55 to operate in stacked mode cannot be undone without resetting the system and starting again. Ensure that you have your wiring information handy and that you know exactly how the system is connected together before initialising your stack.
1. Connect to system
To get started press connect to system on the uControl Homepage.
2. Stack
If the HDA devices are on the network you will be presented with the option to create a stack, video standalone or audio standalone, as this contains an MHUB (4×4)/(6×6) 100A and an MZMA (6×4) 55 choose stack.
3. Master Controller
The Zone Processor acts as the bridge between 2 or more HDA devices and all data goes through this device, acting as a brain. It needs to be selected as the Master Controller.
4. Layers
Next we need to choose our layers, starting with the Foundation Layer. Press identify to the right of the HDA device to make the power LED blink, when you know which is which select your primary MHUB for 1 and the other HDA device for 2, then hit continue.
5. Naming devices
Now we have chosen where our devices go in the stack, we must name them so that they’re easily identifiable.
6. Access uControl
Assigning our hardware has now been complete, after pressing access uControl we will continue the setup in uOS.
7. Cloud Account
The first thing to do in uOS is to create a Cloud Account, or pair it to an existing one if possible. Cloud Accounts allow for Installers and HDA Tech Support to gather additional information regarding your systems performance.
8. Control Type
Choose uControl as Control Tyoe.
9. System Name
Confirm the names of your devices.
10. Setup Connections
This next step will allow us to make the manual connections between the multiple devices.
11. Manual Connections
This is where you tell the system how it is all linked. In this example Audio Output (A) is connected to Audio Input (1). For the second connection Audio Output (B) is connected to Audio Input (2). Repeat this step for every required connection.
12. Naming Sources
Name your inputs after what identifies them the easiest. This can be naming it after the specific source that is connected, or naming them incrementally.
13. Zones
A zone is where a display is located, so name the zones after the room those displays are in. To add an output to a zone, choose which output from the list and then press “+OUTPUT”, check that the output has been added below in bold and then press “Create Zone”. Repeat process for all zones.
14. Complete
Now the system has been configured press “Finish” and you will be taken out of the web interface.
15. Reboot
The last step is to remove the power cable from your Zone Processor and wait 2 minutes, then plug it back in. Ths is needed to apply the settings you have just changed, once the 2 minutes is up press “Continue”.
After hitting continue you will be taken into the uControl interface where you can begin setting up the necessary packs and additional features like Functions and Sequences. For more guides on setting up systems after the first boot, please refer to our uOS support page.
MHUB PRO 2.0 and MZMA Stack
Please read:
This guide will show you how to build a stacked system using an MHUB PRO 2.0 and an MZMA (6×4) 55 with uControl acting as the main method of control for the system.
Make sure the only HDA devices on the network are the ones you want to put into the Stacked System. If you still cannot discover them in the app consider your network infrastructure, the app may struggle to find the system(s) if there are things like network switches in the residence, so try simplifying it whilst going through setup.
This guide is intermediate in difficulty and assumes that you have installed MHUB before in standalone mode.
It is strongly recommended that you read this guide carefully before commissioning your stacked system to ensure all features of the system work as expected.
25 minutes (approximately) to work through.
What you will learn:
Checklist
To create a stacked system please make sure you have the following before you start:
- MHUB PRO 2.0 (4×4) or (8×8)
- MZMA (6×4) 55
- Zone Processor, uControl Connect (x1)
- Audio cable(s) to create connections between your MHUB PRO 2.0 and MZMA (6×4) 55
CHECK SOFTWARE VERSIONS:
Check that ALL hardware above has been updated to the latest software version BEFORE you start configuration on uControl app.
Glossary
the following terms are used throughout this guide.
Foundation Layer
The MHUB system which is directly connected to a video source(s) is referred to as the Foundation Layer. Ideally, this system should be physically installed at the bottom of your MHUB stack. Inside uOS this system is referred to as S1 (see Stack Layer below).
Connections
A Connection is used to define the cabled connections between each component in an MHUB/MZMA Stack. The combination of HDA devices in your Stack will determine which ports can be paired or not.
Stack Layer
The Stack Layer is an alphanumeric identifier within uOS, starting from the Foundation Layer (Layer S1). This identifier represents the order of HDA systems that are connected to one another by a Connection. For example, if you had four HDA systems stacked together, then you would start with the Foundation Layer (Layer S1), then the second HDA device (Layer S2), followed by the third HDA device (Layer S3) and, finally, the fourth HDA device (Layer S4).
Master / Controller
An HDA device (like a Zone Processor) designed to control MHUB and/or MZMA (6×4) 55 systems operating in Stack mode. Any Stack that needs to be controlled by uControl must have a Master / Controller present in your setup. This is identified as M1 in uOS.
uControl
uControl is our control system for configuration and control of stacked systems. When we refer to “uControl” in this article we are referring to our app specifically.
Wiring
A video and audio system is made possible by the audio ports on the back of the MHUB PRO 2.0 and MZMA (6×4) 55. Connect the 3.5mm Stereo port labelled Audio (In) on the back of the MZMA (6×4) 55 to the 3.5mm Stereo port on the back of the MHUB PRO 2.0 labelled Audio (Out).
- “Audio (Out)”
The audio ports on the back of the MHUB PRO 2.0 are labelled Audio (Out). - “Audio (In)”
The audio ports on the back of the MZMA (6×4) 55 are labelled Audio (In).
- Connect your 3.5mm stereo cables to the Audio (In) port of the MZMA (6×4) 55 and repeat for every zone.
- Connect your 3.5mm stereo cables to the Audio (Out) port of the MHUB PRO 2.0 and repeat for every zone.
- Connect speakers via phoenix connector into the Audio (OUT) of the MZMA (6×4) 55 and repeat for every zone.
- Connect your HDBaseT/network cabling into the Video (OUT) of your MHUB PRO 2.0 then into your display receiver and repeat for each zone.
Watch video: How to wire MHUB PRO 2.0 and MZMA (6×4) 55 stack
This video describes how to wire an MHUB PRO 2.0 with an MZMA (6×4) 55 to create a stack.
Initialising your Stacked Video and Audio System using uControl
Ensure that your MHUB PRO 2.0 and MZMA (6×4) 55 are correctly wired for stacking covered in the part above and that the following is completed:
- Both MHUB PRO 2.0 and MZMA (6×4) 55 systems in your stack are powered ON.
- Your Master / Controller device (Zone Processor or uControl Connect) is powered ON.
- All HDA systems and the Master Controller are connected to the LAN and reachable by their IP address.
- IMPORTANT: All hardware has been individually updated to the latest software version.
Configuring MHUB PRO 2.0 and MZMA (6×4) 55 to operate in stacked mode cannot be undone without resetting the system and starting again. Ensure that you have your wiring information handy and that you know exactly how the system is connected together before initialising your stack.
1. Connect to system
To get started press connect to system on the uControl Homepage.
2. Stack
If the HDA devices are on the network you will be presented with the option to create a STACK, VIDEO STANDALONE or AUDIO STANDALONE, choose STACK.
3. Master Controller
The Zone Processor acts as the bridge between 2 or more HDA devices and all data goes through this device, acting as a brain. It needs to be selected as the Master Controller.
4. Setting Stack Layers
Select your MHUB as the primary device, and then select MZMA as the secondary device.
5. Naming devices
Name the devices so that they’re easily identifiable.
6. Access uControl
Your HDA devices are now in Stack mode and are ready for configuration. You can now proceed to perform First Boot of your Stack with the Master Controller (M1)
7. Owner Account
Owner Accounts allow installers to add their HDA PRO account to their system for additional features, and to increase the warranty period. We recommend you do not skip this step.
8. Control Type
Choose uControl as the Control Type.
9. System Name
Confirm the names of your devices.
10. Setup Connections
This next step will allow us to make the manual connections between the multiple devices.
11. Manual Connections
Connect your ports by linking Audio Input (1) to Audio Output (A), and the same for Audio Input (2) and Audio Output (B). Continue to do so until all your Audio Inputs are linked with your Audio Outputs. If you have 5 or more zones of audio requiring multiple MZMA’s, select MZMA (S3) from the drop down which will be your third HDA device in the stack as the MHUB PRO 2.0 is the primary, or (S1). Repeat the first steps until all Audio Inputs are assigned to Audio Outputs.
12. Naming Sources
Name your inputs after what identifies them the easiest. This can be naming it after the specific source that is connected, or naming them incrementally.
13. Zones
Name the Zones after the rooms in the property which have the device(s) plugged into the corresponding ports. For example if the kitchen has the display plugged into Video Output (B) add this to that Zone, the same goes for the audio device Audio Output (B). To add your Outputs to the Zones select them from the dropdown box and then press +OUTPUT. Repeat these steps for all Outputs and Zones.
13a. Zones
Once you have added all Outputs to the zone it should look like below, press CREATE ZONE to finish.
13b. Zones
Check over your zones and make sure you have assigned your devices to the correct zones.
14. Complete
Now the system has been configured press “Finish” and you will be taken out of the web interface.
15. Reboot
The last step is to remove the power cable from your Zone Processor and wait 2 minutes, then plug it back in. This is needed to apply the settings you have just changed, once the 2 minutes is up press “Continue”.
After hitting continue you will be taken into the uControl interface where you can begin setting up the necessary packs and additional features like Functions and Sequences. For more guides on setting up systems after the first boot, please refer to our uOS support page.
How to build an MHUB S stacked system
Please read:
This guide will show you how to build a stacked system using two or more MHUB S with uControl acting as the main method of control for the system.
This guide is intermediate in difficulty and assumes that you have installed MHUB before in standalone mode.
Make sure the only HDA devices on the network are the ones you want to put into the Stacked System. If you still cannot discover them in the app consider your network infrastructure, the app may struggle to find the system(s) if there are things like network switches in the residence so try simplifying it whilst going through setup.
It is strongly recommended that you read this guide carefully before commissioning your stacked system to ensure all features of the system work as expected.
25 minutes (approximately) to work through.
What you will learn:
Checklist
To create a stacked system please make sure you have the following before you start:
- MHUB S (x2 or more)
- Zone Processor, uControl Connect (x1)
- HDMI cable(s) to create connections between your MHUB S systems
CHECK SOFTWARE VERSIONS:
Check that ALL hardware above has been updated to the latest software version BEFORE you start configuration on uControl app.
Glossary
the following terms are used throughout this guide.
Foundation Layer
The MHUB S system which is directly connected to a video source(s) is referred to as the Foundation Layer. Ideally, this system should be physically installed at the bottom of your MHUB S stack. Inside uOS this system is referred to as S1 (see Stack Layer below).
Connections
A Connection is used to define the cabled connections between each component in an MHUB Stack. The combination of HDA devices in your Stack will determine which ports can be paired or not.
Stack Layer
The Stack Layer is an alphanumeric identifier within uOS, starting from the Foundation Layer (Layer S1). This identifier represents the order of MHUB systems that are connected to one another by a Connection. For example, if you had four MHUB S systems stacked together, then you would start with the Foundation Layer (Layer S1), then the second MHUB S (Layer S2), followed by the third MHUB S (Layer S3) and, finally, the fourth MHUB S (Layer S4).
IR Cascade
MHUB S supports infrared (IR) passback from any display receiver connected to any MHUB system to another MHUB, through a process called IR Cascading. IR Cascading works from the top of your Stack, down the MHUB Stack Layers, until it reaches the Foundation Layer Source IR outputs or is instructed to stop elsewhere by uOS.
Master / Controller
An HDA device (like a Zone Processor) designed to control MHUB and/or MZMA systems operating in Stack mode. Any Stack that needs to be controlled by uControl must have a Master / Controller present in your setup. This is identified as M1 in uOS.
uControl
uControl is our control system for configuration and control of stacked systems. When we refer to “uControl” in this article we are referring to our app specifically.
Wiring
Stacking video and cascading IR is made possible by two ports on the rear of each MHUB S.
- “Mirror (OUT)” port
Connect the mirror out HDMI port to each Source Input at the Foundation Layer MHUB to the corresponding Source In HDMI port of the next MHUB in the stack. - “Stack IR (IN)” & “Stack IR (OUT)” ports
(Only needed if you are using IR Passback in your stack)
Used for MHUB S’ IR Cascading function and can be connected using the Source IR Stacking Cable included with MHUB S. Stack IR only works with a maximum of 4 MHUB S systems.
- Using HDMI cables, connect your video input/source to the lowest MHUB in your stack (Foundation Layer) first. Connect them to the “Source (IN)” port.
- Repeat step 1 for every video/input source.
- From the Foundation Layer locate the “Mirror (OUT)” port and connect a short HDMI cable to it. Complete this connection by connecting the HDMI cable to the “Source (IN)” port on the MHUB S in the layer above.
- Repeat step 3 for every MHUB S in your stack.
Watch video: How to wire MHUB S to create a stack
This video describes how to wire MHUB S systems together to create a stack.
Watch video: IR Cascading
If you plan to control your video input/sources using the original source remote control from displays served by stacked MHUB S then you will need to cascade IR down your stack.
There are some general rules to follow when doing this:
- Cascading IR applies to source control only. You cannot Cascade IR to displays.
- Cascading IR goes down the Stacking Layers only, from last to first.
- Similar to Connections, IR Cascading can only be defined between incremental Stacking Layers: S3 to S2 and finally S1. It is not possible to jump between devices, for example, S3 to S1.
- The Source IR Stacking Cable is 50cm/1.64ft so bear this in mind when rack mounting MHUB S, you must use the one supplied with the full kit.
- All “Source IR (OUT)” ports have two modes: Local and Passthrough. If the port is set to Local, then any IR received from a stacked MHUB will be transmitted on the receiving MHUB. If the port mode is Passthrough then the IR signal will be transported off that MHUB down the Stack Layer until it reaches an instruction to execute the IR command Locally.
- IMPORTANT: Local and Passthrough modes can be set from uOS on the Zone Processor.
- Any input served from a “Mirror (Out)” port must match the “Source (IN)” port identifier. You can not switch port IDs (eg. Mirror 1 to Input 4)
How to wire MHUB S for IR cascading
This video describes how to send IR from a stacked MHUB S to the Foundation Layer.
Initialising your Stacked System using uControl
Ensure that your MHUB S systems are correctly wired for stacking covered in the part above and that the following is completed:
- All MHUB S systems in your stack are powered ON.
- Your Master / Controller device (Zone Processor or uControl Connect) is powered ON.
- All MHUB S systems and the Master Controller are all connected to the LAN and reachable by their IP address.
- IMPORTANT: All hardware has been individually updated to the latest software version.
Configuring MHUB to operate in stacked mode can not be undone without resetting the system and starting again. Ensure that you have your wiring information handy and that you know exactly how the system is connected together before initialising your stack.
1. Connect to system
To get started press connect to system on the uControl Homepage.
2. Stack
If the HDA devices are on the network you will be presented with the option to create a stack, video standalone or audio standalone, as this contains two MHUB S’ it is a Stack.
3. Master Controller
The Zone Processor acts as the bridge between 2 or more HDA devices and all data goes through this device, acting as a brain. It needs to be selected as the Master Controller.
4. Setting Stack Layers
Next we need to choose our layers, starting with the Foundation Layer. Press identify to the right of the HDA device to make the power LED blink, when you know which is which select your primary MHUB for 1 and the other HDA device for 2, then hit continue.
4b. Order of layers
The order of your physical stack may be different to the order in uControl, as the MHUB with the IP address 192.168.11.147 could be the Foundation layer. It is important to mirror the order of the MHUB’s.
5. Naming devices
Name the devices so that they’re easily identifiable.
6. Access uControl
Your MHUB’s are now in Stack mode and are ready for configuration. You can now proceed to perform First Boot of your Stack with the Master Controller (M1)
7. Owner Account
Owner Accounts allow installers to add their HDA PRO account to their system for additional features, and to increase the warranty period. We recommend you do not skip this step.
8. Control Type
Choose uControl as the Control Type.
9. System Name
Confirm the names of your devices.
10. Setup Connections
This next step will allow us to make the manual connections between the multiple devices.
11. Manual Connections
This is where you tell the system how it is all linked. In this example source device 1 will be connected to Source (In)1 of the first layer (S1) in the stack and then mirrored with a shorter HDMI cable going into Source (In)1 of the second layer (S2), meaning the source will be available on both MHUB’s and therefore more zones. The same goes for Input 2 being paired with Source 2 on the second layer. Make sure to repeat how ever many times needed for your amount of source devices.
12. Zones
A zone is where a display is located, so name the zones after the room those displays are in. To add an output to a zone, choose which output from the list and then press “+OUTPUT”, check that the output has been added below in bold and then press “Create Zone”. Repeat process for all zones.
13. Complete
Now the system has been configured press “Finish” and you will be taken out of the web interface.
14. Reboot
The last step is to remove the power cable from your Zone Processor and wait 2 minutes, then plug it back in. This is needed to apply the settings you have just changed, once the 2 minutes is up press “Continue”.
After hitting continue you will be taken into the uControl interface where you can begin setting up the necessary packs and additional features like Functions and Sequences. For more guides on setting up systems after the first boot, please refer to our uOS support page.