Search by Support Category: Matrixes
If your MHUB is marked with “TPC” then it is capable of passing a HDR picture to your display. There are a number of reasons why HDR may not be fed through your HDA device. This support post aims to troubleshoot the most common reasons and how to resolve them.
Important: there are different versions of HDR, make sure your display supports the format your source is outputting!
There are multiple variants of HDR such as HLG, HDR10+ and Dolby Vision, please ensure your display supports the relevant HDR technology.
When connecting your HDR enabled source and display to a HDA system you may need to adjust some settings to get it to work.
- First, disconnect the source and connect it directly to your display. Do you get HDR?
- Ensure you are using High Speed HDMI Cables, this is important as long HDMI cables (over 5m) unless Active or Fibre will not work.
- Was you HDA device manufactured before 2019? Does it have TPC markings or 18G/18Gbps on it anywhere? If it doesn’t then there is a good chance that your HDA device does not support HDR as it was made before the specification was finalised.
- Does your HDA device support scaling? If so please ensure it is set to bypass.
- Copy or set a custom EDID directly from your display. This post explains how to copy EDID directly from your display.
*Before you activate the Alexa Voice Service with your MHUB, make sure Amazon support your territory and version. We cannot guarantee voice services or offer support to those territories not officially supported by Amazon. Check here: https://www.amazon.co.uk/gp/help/customer/display.html?nodeId=202207000
What you need to get your MHUB to respond to voice commands:
- You have completed the first-boot procedure within MHUB-OS
- You have MHUB-OS version 8.10 or higher installed on your MHUB
- You have an active HDA Cloud account
- You have downloaded uControl packs for all displays and source devices you want to control
- You have completed input mapping in MHUB-OS
- You have an active Amazon account
- You have an Amazon Alexa enabled device, such as Amazon Dot/Echo/Show
Setting up AV Skill
Configure voice commands to do exactly what you want
Let’s take the command “Alexa, Turn on football” as an example.
It might appear like a very simple command but there are a number of things that need to happen in order to watch football! First the TV might need to turn on, but in which room? The volume might need to be set to a desired limit. The correct source input might need to be selected on MHUB and finally that source will need to navigate to the channel hosting the football.
You can configure all those actions in what we call a “Sequence”.
Taking the example above:
Alexa (this wakes up your Amazon Dot/Echo/Show)
Turn on… (this invokes the smarthome skill)
football (this is your custom name for the Sequence, it can be anything you want)
Inside MHUB-OS we can configure exactly what “football” does.
- You can select if you want MHUB to turn your TV on and adjust the volume
- You can tell MHUB to switch to the source device with has the football on it
- You can instruct MHUB to change the channel on that source device
Read more about Sequences and Scheduling.
Troubleshooting
- When searching for devices, nothing is found
- Check you cloud account details were entered correctly
- Ensure only 1 system is linked with the cloud account being used
- Ensure you have backed up the system to cloud after configuring the Alexa Skill on MHUB-OS
- When you try to control a zone Alexa says the command isnt supported
- Ensure there are no other devices linked to the Alexa that have the same name as the zone.
Here’s a table of all the commands you can tell your MHUB to do…
Now you’re ready to go. Take a look at a full list of commands that you can say to your Echo.
Zones define a physical space in a property where outputs from MHUB terminate.
A Zone can include a maximum of 1 video output and a maximum of 4 audio outputs. For example, you can create a zone called “Kitchen” and assign 1 video and 1 audio output to it to provide you with viewable TV and sound. A Zone must contain at least 1 output from an MHUB for it to be addressable for control. Note: outputs can not be shared or split to more than 1 Zone.
The first boot process for MHUB-OS has remained largely unchanged with the exception of zones.
The slideshow below walks you through the steps within MHUB’s first boot process and how to setup zones to refect the different rooms or areas within you property.
If you wish to configure a stacked system please watch this video – Creating a MHUB stacked system.
You should be able to complete the process in under 10 minutes.
MHUB-OS first boot steps are as follows:
- EULA and Privacy policy
- Name your MHUB
- Name your source devices
- Create zones
- Assign outputs to zones
- Confirm zones
- Connect MHUB to HDA Cloud
- Complete setup
HDANYWHERE(HDA) recommends that every MHUB install goes through its first boot process to ensure that the MHUB is setup correctly.
How long does the process take to complete
If you have an update to install then then first boot usually take about 10 minutes. If there is no update you can normally finish the entire process and have an operational MHUB system well within 5-7 minutes.
Yes. You do not need to access MHUB-OS if you don’t want to. But this is only recommended if you intend to control you MHUB via a control system. You will also miss the opportunity to increase your warranty period and open your MHUB to additional features or services.
I don’t want to use MHUB-OS or go through the first boot process, will MHUB work like a normal?
Yes. You do not need to access MHUB-OS if you don’t want to. But this is only recommended if you intend to control you MHUB via a control system. You will also miss the opportunity to increase your warranty period and open your MHUB to additional features or services.
I made a mistake in the first boot process, can I go back or make a change?
Yes. You can go all the way back to the update step and correct any incorrect information you entered. Alternatively, you can also access MHUB-OS (after you have completed first boot) and change anything then.
If you have received a notification in uControl or by email that an update is available for your MHUB-OS then follow these steps to update your system. All updates are now handled by uControl. Please ensure you have installed the latest version.
If you have not connected to your MHUB before, please follow this guide first – Connecting to a MHUB
If you have received a notification in uControl or by email that an update is available for your MHUB then chose the correct option below:
Updating an existing system
The majority of MHUB customers will be on MHUB-OS 7 and their systems will contain user data which needs updating to the latest version. If this is you then follow these steps.
- Click ‘Connect to an exisiting MHUB system’, uControl will scan your network for any MHUB systems
- Select your MHUB device
- Connect to your MHUB
- uControl will show popup message that MHUB-OS requires updating, click ‘update’ and follow on screen prompts
Updating an New system
This is likely to happen if you have recently bought MHUB and it was shipped to you on older software. You will run through the following steps:
- Click ‘CONNECT TO MHUB SYSTEM’, uControl will scan your network for any MHUB systems
- Select your MHUB device
- uControl will check the current version of MHUB-OS, if an update is required, you will be prompted to update it.
- Connect to your MHUB
- Perform first boot process.
Updating to MHUB-OS 8.00 from an earlier version
If your version of uControl updates to version 2.0 or above automatically, any previous connection to your MHUB will be reset. This is normal and part of the update process. Follow the process as described in ‘Updating a New System’ and uControl will update your system as part of the connection process.
Follow the instructions within the app to connect back to your system. During this process uControl will check MHUB(s) to see if they also require updating.
Watch a video of it here:
Having trouble updating your MHUB, check here -Update Troubleshooting
Make sure MHUB is connected up correctly before starting the first boot process on MHUB-OS
HDANYWHERE(HDA) recommends that every MHUB install goes through its first boot process to ensure that the MHUB is setup correctly. Please follow the quick start guide (inside MHUB packaging) to make sure your MHUB is connected correctly to your source devices, displays and has an active network connection before proceeding.
I don’t want to use MHUB-OS or go through the first boot process, will MHUB work like a normal matrix?
Yes. You do not need to access MHUB-OS if you don’t want to. MHUB will work distributing video as normal and will be controllable using the included remote controls. Please note that you will not be able to access advanced features such as voice control, the uControl app or build Sequences.
Accessing MHUB-OS (MOS)
There are two ways to access MOS:
- Download our app, uControl, from the iOS or Google Play Store and let it find MHUB (and run you through the first boot) for you
- Go to your MHUB and press and hold the “MENU” button for 5 seconds to reveal its IP address. Make a note of it then put that address in to any web browser on the same network. You will be forwarded to the first boot process.
First boot process
- BEFORE STARTING:Read and agree to the End User Licence Agreement (EULA) and Privacy Statement
- First Boot Step 1 – Check for MOS updates
This is where your MHUB requests available updates from HDA cloud so your unit will update to the latest version. This is done before proceeding.
- First Boot Step 2 – Name your MHUB
Here you can give your MHUB a personal name, this can also be used to differentiate multiple installations by HDA Pro’s - First Boot Step 3 – Name your sources/inputs
On this page you can label your input devices, such as Sky, Apple or Tivo. These labels are used in the uControl app and with voice control. Please go here for best practices when adding names. [Best Practices]
- First Boot Step 4 – Name your Displays/Rooms/outputs
This page is similar to the previous step. You can choose to label them as display manufacturers or room names. Again please follow best practice guidelines available here – [Best Practices] - First Boot Step 5 – Turn update notifications On/Off
MOS updates are released periodically, here you can choose to be notified when an update is available
- First Boot Step 6 – Create or link your MHUB to a HDA cloud account, read and agree to our Terms and Conditions
MHUB4K(3rd gen) and MHUB4KPRO units can be linked to a cloud based account. When registering as a homeowner this enables a couple of things. Firstly when you register, your warranty period is extended by 1 year, in addition to that cloud access is required when using the uControl IRengine feature allowing you to control source and display devices. Cloud access is also required for voice integration. For a HDA PRO the cloud account allows you to manage your MHUB installations remotely, getting system information as well as a host of other features. - First Boot Step 7 – Secure MHUB with a PIN number
If you wish you can lock local access to MOS stopping any unwanted configuration changes from being made. - First Boot Step 8 – Complete First Boot Setup
Once you have completed the first boot process you can either ‘COMPLETE SETUP’ and go to the MOS DASHBOARD pag, . or goto the uControl page to start adding device/source control. For more information on uControl go here uControl
1. HDA Cloud
The HDA Cloud acts as our global data storage and service delivery platform offering an interface for MHUB owners, HDA Pro’s and 3rd party devices to talk to one another.
There are two types of cloud account that can be associated with an MHUB system.
2. HDA Cloud Account
The HDANYWHERE (HDA) Cloud account is the account that belongs to the Homeowner and/or End-User. The owner of the MHUB has to have a verified HDA Cloud account before any communication between MHUB systems and the HDA Cloud can take place.
Registering the MHUB system provides numerous benefits including:
- Extending the warranty period on the system by 1 year (must be registered within 30 days of purchase, Warranty is non-transferable)
- Enables advanced functions for things like voice control, uControl, integration with other IoT devices and Sequences
- Provide advanced troubleshooting information to your HDA Pro installer and HDA
- Provide your HDA Pro installer permission to remotely manage your system, they can then modify your system for you without physically being there
3. HDA Pro Account
The HDA Pro account can not be added to a unit unless a HDA Cloud account (outlined above) is present first. This account authorises the installer to monitor the MHUB on their customer’s (the homeowner) behalf. This account sits alongside the Cloud account and gives a 3rd party access to the MHUB’s data and the ability to control it. HDA Pro’s can register Here
The following Settings can be managed remotely:
- Source Routing (and switching)
- Edid management
- uControl sequence configuration
- uControl IR pack configuration
- Power management
- IP configuration
- Temperature
- Firmware (MHUB-OS, and MHUB)
You can also monitor the following:
IMPORTANT: a HDA Pro Account has to be created first Here and authorised by HDA staff before the installer can use their account details to enable monitoring on the MHUB.
4. MHUB-OS
MHUB’s operating system which acts as the bridge between using MHUB and managing it. From MHUB-OS it is possible to connect to HDA Cloud, integrate devices like Amazon Alexa, manage network settings and update software to add new features.
5. uControl
uControl is our remote control app for MHUB 4K PRO systems. It pulls all the information it needs to work directly from MHUB-OS and requires no setup or configuration. Just download it and let it find your MHUB and you’re ready to go.
Setting up the MHUB 4K PRO Control / MHUB 4K PRO Smarthome Skill on the Alexa app
We are assuming that you have already downloaded the Amazon Alexa app and have a functioning Amazon account.
Skill types:
There are two types of skill which you can enable on the Alexa app.
- Custom Skill
With a Custom Skill we have full control over the voice interaction (a voice interaction is the communication you have with an ECHO device when speaking a command and also includes the response given by the ECHO) between you and your Echo device, this allows for a greater range of voice commands including playhead, change channel, switch sources, increase/decrease volume.Click here to view a the full range of voice commands. - Smarthome Skill
The Smarthome skill differs from the custom skill in a couple of ways. Firstly, invoking a smarthome skill is fixed and defined by Amazon, this also applies to the voice interaction. We currently support on/off commands, allowing you to perform actions quickly by uttering “Alexa, turn on TV” or a custom label like “Alexa, turn on movies”. - You can of course, use both. They are FREE!
What you need to get your MHUB to respond to voice commands:
- You have completed the first-boot procedure within MHUB-OS
- You have MHUB-OS version 7.0 or higher installed on your MHUB
- You have an active HDA Cloud account
- You have downloaded uControl packs for all displays and source devices you want to control
- You have an active Amazon account
- You have an Amazon Alexa enabled device, such as Amazon Dot/Echo/Show
Linking the custom skill “MHUB 4K PRO Control”
- Go to the Skills section on the Alexa app and search for “MHUB 4K PRO Control”
- Click on the skill and select “Enable”
- Click “Link Account” – when you do this, you will be redirected to HDA Cloud’s secure login page. Enter your username and password in to the fields.
Linking the smarthome skill “MHUB 4K PRO Smarthome”
- Go to the Skills section on the Alexa app and search for “MHUB 4K PRO Control”
- Click on the skill and select “Enable”
- Click “Link Account” – when you do this, you will be redirected to HDA Cloud’s secure login page. Enter your username and password into the fields.
- After the account has been linked, visit the “Smart Home” screen then navigate to the ‘Manage devices in Smart Home’ then Devices. Next click ‘Discover’.
- This action will communicate with MHUB and pull any devices making them ready to use.
Configure voice commands to do exactly what you want
Let’s take the command “Alexa, tell my TV to watch football” as an example.
It might appear like a very simple command but there are a number of things that need to happen in order to watch football! First the TV might need to turn on, but in which room? The volume might need to be set to a desired limit. The correct source input might need to be selected on MHUB and finally that source will need to navigate to the channel hosting the football.
You can configure all those actions in what we call a “Sequence”.
Taking the example above:
Alexa (this wakes up your Amazon Dot/Echo/Show)
tell my TV to… (this invokes HDA’s custom skill)
watch (this is a special function which tells MHUB to start a Sequence)
football (this is your custom name for the Sequence, it can be anything you want)
Inside MHUB-OS we can configure exactly what “football” does.
- You can select if you want MHUB to turn your TV on and adjust the volume
- You can tell MHUB to switch to the source device with has the football on it
- You can instruct MHUB to change the channel on that source device
Read more about Sequences and Scheduling.
Here’s a table of all the commands you can tell your MHUB to do…
Now you’re ready to go. Take a look at a full list of commands that you can say to your Echo.
If you wish to control your MHUB 4K 4×3+1/8×6+2 from an external control system via a RS232 connection you will need to wire the included phoenix connector to the following specification.
Daisy chaining IR can allow you to connect the IR systems of 2 devices. This allows IR to pass from one device to another
This does not work for HDMI Mirrored ports.
a) The diagram below shows how you can link two HDA devices, such as an MHUBU86240 and an XTND4K40TPC using a MHUB + XTND Integration Kit
b) This second diagram shows how you would connect a HDA system to a 3RD PARTY extender or device such as a Harmony Remote by Daisy-chaining the IR transmitter from the 3RD party device and the IR receiver included with the MHUB system.
c) T
Windows configuration tool for MHUB 2K and MHUB 4K systems. Search for MHUB, configure EDID and network settings.
Download the MHUB 2K and MHUB 4K configuration tool.
The software configuration tool has been written for an older version of Windows. If you run the exe file on your laptop and you receive a C++ error message then please read this support article.
Description
When I try to install the software, I receive this warning:
“The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail.”
This issue is typically caused by a conflict between the program and one or more of the files in the C++ runtime libraries. These libraries are part of the Windows operating system and are used, and potentially updated, by installing or updating several Microsoft or other third party products.
If you are experiencing this error when launching or installing the program, and if the program repair option does not resolve the issue, the most effective method to correct this error is to uninstall and reinstall any Microsoft Visual C++ installations currently available on your computer before proceeding with the installation.
To uninstall all current Microsoft Visual C++ installations
Open the Control Panel and locate the list of programs.
Windows 8/10
From within the Start screen, type “Control Panel” and click on the Control Panel search result when it appears.
Select Programs and Features.
Windows 7/Vista
Click Start> Control Panel
If viewing categories, click Programs> Uninstall a Program
If viewing icons, click Programs and Features
Windows XP
Select Start> Control Panel> Add or Remove Programs
Scroll down to locate the Microsoft Visual C++ entries.
Select each one, starting from the top entry, and choose Uninstall.
Do this for each entry, until there are no more Microsoft Visual C++ entries listed.
To reinstall new Microsoft Visual C++ packages follow the instructions on this page –
Once every package has been downloaded and installed, restart Windows.
Finally, launch the program. If the error message persists after following all of these instructions, then please contact HDanywhere technical support on 01684 576348
The mHub 4K range has full support for most popular control systems via serial (RS232) or IP.
All control strings and current available drivers are available in the mHub control pack, available here – Download
IP control
To control the mHub 4k unit via IP you will first need to discover it by using the mHub controller software available in the control pack above
The mHub 4K will acquire an IP address via DHCP the first time it is connected to your home network, use the controller software to locate it on your network.
In the mHub controller software select IP and then press the ‘search’ button, this should locate your mHub matrix. Press ‘connect’ the red button should turn green.
Press the configure button
From here you can set the matrix to a static IP if you wish (this is generally good practice)
Your matrix is now on your home network and will be able to receive IP commands from whatever control system you are using.
Looking for the mHub 2K information, go here – mHub 2K
To disable the beep on the mHub 2k range of matrices please following the instructions below using either I.P or RS232 connection methods.
To adjust the settings on the mHub range of products, you will need to download the controller software Download
A) Connecting to the mHub Via I.P
The mHub 2K’s IP address is pre-configured as 192.168.0.100, your computer will need to have it’s IPV4 range configured to be within the same range initially while you setup the matrix. (You don’t need to follow this step if you have a mHub 4K system)
To configure your IPV4 settings you will need to navigate to the following menu
->Network and sharing center
—>Ethernet
—–>Properties
——->Internet Protocol Version 4 (TCP/IPv4)
———>Properties
Once you have changed the IP settings on your PC, open the Mhub controller software.
In the Control Mode Select Box choose ‘IP’, then click the ‘Search’ button. When the IP address shows in the mHub IP box, click connect.
B) Connecting to the mHub Via RS232
To connect via RS232 use the supplied serial cable can connect between the mHub and your PC, then on the Controller software select ‘RS232′, then in the RS232 Options section select the Com port being used from the drop down menu then click connect
C) Disabling the Beep
To disable the beep select the ‘Control’ tab and untick the box labeled ‘Enable Feedback Beep’.
Once changed, you can verify the beep has been disabled by performing a source switch operation.
| Error Code | Description |
| 1001 | Corrupt Service Card – Replace the SDCard or format and re-create |
| 1002 | Insert valid SDCard – No card detected or installed in the unit |
| 1003 | Write Protect Mode – SDCard is in write protect mode |
| 1004 | System Failure – MatrixOS is missing from the system and needs to be installed – i.e. rebuild the SDCard |
| 1005 | Insert Service Card – Insert an SDCard with a valid matrix OS firmware image |
| 1006 | Update failed – No firmware image found |
| 1007 | Update failed – Firmware image is corrupt or invalid |
| 1008 | Update failed – Firmware image is too large for the system. |
| 1009 | Remove service card – A bulk update card is installed and the update is complete, ready for a normal service card. |
| 1010 | Onscreen message varies – The unit update has failed and will be showing where internally in the unit it has failed. |
| 1011 | Update failed writing to flash. A critical error and process was stopped |
| 1012 | Communication Fault – The system cannot bring up internal communication bus and is unable to proceed |
| 1013 | Module Fault – Comes with specified module number |
| 1014 | System Fault – An internal IC has failed, indicated by the extended error code |
| 1015 | Input hotplug fault. Unable to enable the hot plug 5V voltage for one or more input modules |
| 1016 | EDID Setup Fault – The system cannot bring up the EDID mixing routines |
| 1017 | Communication fault – The system cannot bring up the 5V I2C communication line |
| 1018 | IR Mux fault – The system cannot bring up the IR Mux subsystem |
| 1019 | IR Capture fault – The system cannot bring up the IR capture subsystem |
| 1020 | Local Network Failure – Unable to ping the local gateway |
| 1021 | Remote Net Failure – Unable to ping DNS servers |
| 1022 | Module Power Fault – The system reports that one of the voltages used to power modules is not functioning correctly |
| 1023 | Network HW Fault – The network hardware has a hardware fault |
| 1024 | Network HW Fault – EDID Read Failure – the system has failed to read the EDID from a connected device |
| 1025 | Network HW Fault – Filesystem Fault – The system has an issue reading from the SDCard |
| 1026 | Network HW Fault – Invalid update URL – The custom URL for retrieving updates is not valid |
| 1027 | Network HW Fault – Discovery failure – the system has failed to enable its auto discovery feature (SDDP) |
| 1028 | Network HW Fault – Invalid Aux MCU – the Component fitted is incorrect |
| 1029 | Update failed – This version is too old for this part |
| 1030 | Invalid Module – A module is inserted in the wrong port |