MHUB-OS 8 first boot process

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?

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.

Updating MHUB-OS to a new version

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
Updating an New system
Updating to MHUB-OS 8.00 from an earlier version

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

MHUB-OS Firmware 1.30 update – Complete

The first part of this update roll-out has now been completed. Any new MHUB’s connected to the internet will automatically upgrade when the unit is powered on, this may extend the boot time by 30 seconds

HDA Cloud is moving to a new & more sophisticated server.
This will automatically start at 8:00am (BST) Monday 30th July.

HDA Cloud is our secure online portal that allows you to remotely access any network-connected MHUB system around the world. It allows you to remotely manage, configure, and troubleshoot installations to help keep your systems running smoothly.
Perhaps most importantly, HDA Cloud is our central data storage server and we take our responsibility to keep all data super safe and secure very seriously. As such, we have provisioned the very latest server technology and security for a faster and more secure connection. Additionally, the platform will enjoy new features and upgrades which will be revealed soon!

The update will come in two stages; first, we will update MHUB systems around the world and after that is complete we will move HDA Cloud to its new home. You will not need to do anything. MHUB systems will update in the following order:

MHUB systems

~~MHUB MAX (4×4) – Monday 30th July 2018~~ – Complete
~~MHUB PRO (4×4) 40 – Wednesday 1st August 2018~~ – Complete
~~MHUB (8×6+2) – Wednesday 1st August 2018~~ - Complete
~~MHUB (4×3+1) – Thursday 2nd August 2018~~ - Complete
~~MHUB PRO (4×4) 70 – Friday 3rd August 2018~~ – Complete
~~MHUB PRO (8×8) 70 - Friday 3rd August~~ – Complete

HDA Cloud Migration - Monday 6th August

– Complete
During this migration, HDA cloud will be unavailable. Starting at 10.00am UTC for 4 hours.

In most case’s this is a background update and should not require any user interaction. However, some systems may need a manual hard reboot (full mains power down for 10 seconds, then reconnect) to apply the update. MHUB video operation will function, but if you notice MHUB control (uControl/MHUB-OS/control system) is not responding, perform the above reboot.

To confirm that the unit has been updated either check in MHUB-OS on the MHUB setup page or check on HDA Cloud

EDID management on MHUB systems

What is EDID?
When you connect an HDMI source such as Sky Q directly to a display, the HDMI cable will send a data exchange between the two devices before they both agree to serve and display a picture. This process is called the handshake. One component of that handshake is called EDID and this is where your display tells the Sky Q what its visual and audio capabilities are (resolution, refresh rate, stereo or multi-channel audio, HDR, etc, etc). In return, Sky Q will choose a picture format that best fits that profile and output something specifically for that display only.

A source device can only output a single format, so you could not get it to output a 4K signal and a 1080p signal simultaneously. It has to be one or the other.

EDID in MHUB
If a device sits in between the source and display (like MHUB) then it must broker that handshake. The complexity comes when you have multiple displays of varying specifications connected to your system. For example, you may have 4K, 1080p, and 1080i capable displays, each with varying audio support. These displays send EDID information back to MHUB. If no EDID profile has been configured in the MHUB system the source will output the lowest common denominator, basically the spec of the least capable display.

This is where EDID management within the MHUB comes into play. You can set a fixed profile that is passed to the source device directly from the MHUB, overriding any information coming from connected displays. Doing this allows you to fix the output of the source regardless of display(s).

The benefit of this would be if you wanted your source device to always output a fixed signal, such as 3840×2160(4k) with 5.1 audio, setting this on the MHUB will ensure that will be what the source outputs.

However, if any display is incapable of receiving the fixed video and audio output you could be left with no video output/audio on those displays unless your MHUB supports video downscaling

MHUB-OS first boot process

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

FIRST-BOOT1

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-BOOT2

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-BOOT3

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

What is the difference between a HDA Cloud & a HDA Pro account?

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

You can also monitor the following:

IP configuration
Temperature
Firmware (MHUB-OS, and MHUB)

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.

Voice control with Amazon Echo using the “MHUB 4K PRO Control / MHUB 4K PRO Smarthome” Skill

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.

To enable the MHUB 4K PRO Control Skill you will need to add the skill first by pressing the "Enable" button in your Amazon Alexa app. Once enabled you will be forwarded to HDA Cloud to link your account with Amazon Alexa. Enter your HDA Cloud username and password and your MHUB will be connected to Alexa!

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

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.

Creating and Editing Sequences

Sequences allow your MHUB to make more complex things happen. For example, a single command could be setup to Turn on a TV, switch to your Satellite box and enter the number keys for a movie channel. These sequences can be triggered in a number of ways to provide a better user experience for MHUB owners.

Sequences are setup within MHUB-OS via the ‘Sequences and Scheduling’ page. They can also be setup remotely via the HDA Cloud (Currently only available for HDA PRO’s, coming soon to end users)

Within this page you can see and edit your current sequences. You can also test all your sequences to make sure they are functioning correctly.

To create a new sequence click the ‘Create New Sequence’ button.

The first part of the Sequence Creation page contains several naming fields which serve different purposes. They are:

Sequence name – This is the name that will be displayed within MHUB-OS
Description – Provide a short description of the sequence so you can see what it does at a short glance
uControl label – This is how the sequence will be labelled within the uControl app
Voice label – This is where voice control (such as Alexa) reads the title of the sequence so it can be triggered. You may find if you are struggling to trigger a particular sequence by voice that you can improve the function by changing the title that your voice control device is listening for.

The next section contains the tools to build your sequence using the available parameters

Command Type

Switch – Execute a simple switching command, first define the input and then the output you would like it switched to
Source – Deliver a command to a source device via the IR engine. This can be something simple like a ‘play’ command or something more complex like a ‘Go to channel command’ (a ‘Go to channel command’ delivers sequential number inputs so you can direct a TV receiver to a specific channel)
Display- Deliver a command to a connected display (or projector) such as ‘Power on’ or ‘Volume up’
Audio – Will integrate with “MHUB Audio”
Delay – Add a delay between one command and the next (Time in milliseconds to wait, eg. 500ms = 0.5 sec)

You can either choose to save the command or add ‘another command’ to create a more complex scenario. For instance, in the following example, we have first a “source switch” followed by a “Go to channel command” with a 500ms Delay.

Installing, configuring & using uControl on iOS & Android

uControl is HDANYWHERE’s free remote control app and is available for iOS and Android mobile platforms. Below is a guide to configuring and then using uControl.

Checklist:

Your MHUB is powered on and connected as per 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.
Your Android or iOS device is connected to the same network as your MHUB
You have downloaded the latest version of uControl from the relevant app store

Connecting to your MHUB with uControl

Before using uControl, it needs to be linked to your MHUB. Please follow the instructions below on how to do this.

Open uControl and press the ‘SETUP A NEW MHUB SYSTEM’ button. uControl will now search your network for any MHUB devices.
uControl will show relevant options. Press ‘CONNECT TO’ MHUB4K44PRO/MHUB4K88PRO/MHUB4K431/MHUB4K682/MHUBPRO4440/MHUBAUDIO64
The app will now check the status of the unit, This can take upto 10 seconds, then it will show the screen ‘CONTINUE SETUP ON MHUB DEVICE’
This will take you to the First Boot process on MHUB-OS where you will setup your system – First Boot Process
After the first boot process is completed you will be shown the following screen. Click ‘ACCESS UCONTROL’ and you will be taken to the main uControl interface.

Using uControl

After uControl is paired with your MHUB you can start to use it to control your device

Source switching on uControl

Source switching is performed by swiping left or right on the input bar and tapping on the required input. When input names are configured on MOS\MHUB SETUP page they will be reflected here.

To change to a different output, tap on the menu icon, and select the desired output from the popout menu, once again any output names configured on the MOS\MHUB SETUP page will be reflected here.

Using uControl to control source and display devices

To enable uControl to control your source or display devices, an IR pack is required and must be installed on your MHUB. This IR pack contains all the relevant information including a screen layout for uControl.

To install an IR pack navigate to the settings menu by pressing on the MENU icon, and tapping on SETTINGS located at the bottom off the pop-out menu. This will bring up the setting page, tap on DOWNLOAD UCONTROL PACKS. this will take you to the UCONTROL page on MHUB-OS.

Using the drop-down menu, select which source or display you wish to install the IR pack for, This will bring up an expanded menu
Click DEVICE TYPE to select the type of device that will be connected to the chosen port.
Next click DEVICE MANUFACTURER and select the make of your device from the list and click on DOWNLOAD UCONTROL PACK – This will load two test commands from the downloaded IR Pack to confirm the commands are working as expected.
Follow the onscreen instructions to test the two commands
If the commands work as expected click YES to complete the process. If they do not, click NO and repeat step 4 until you find commands that work

Repeat the above steps until all required IR packs are installed. Once complete, click DONE on iOS or the back button on your android device

When an IR pack has been installed the uControl area of the screen is populated with the source device interface. These are device specific. Some control packs have multiple interface screens which can be navigated to by swiping left or right.

Gesture Control – This is where you navigate your devices menu or guide using one or two finger gestures or motions on your mobile device, the majority of the screen is filled with the ‘Gesture control area’
Navigation Control – This mirrors a conventional remote control, with individual buttons for navigation.
Playhead Control – This screen contains common functions used when viewing a recorded source or watching a bluray. Such as Play, pause, fast forward and rewind.
Numeric Keypad – This screen shows a 0 to 9 keypad for entering channel numbers etc.
External App – This allows uControl to open external applications such as Sonos.

When using gesture controls the following gestures are supported

Navigation – single finger swipe up, down, left or right
Enter – single finger tap
Play/Pause – two finger swipe up to play, two finger swipe down to pause.

MHUB 4K 4×3+1/8×6+2 RS232 Connection

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 – How To

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.

Software configuration tool for MHUB 2K and MHUB 4K (2014-2016)

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.

XTND 2K (30) Short run adjust settings (XTND2K30)

If you find that you have no picture or poor picture quality, you may need to adjust the EQ settings on your XTND 2K30 based on the approximate distance of your cable run. If you have any patch points add an additional 10% onto your effective distance. The below diagram shows the correct switch settings for various lengths of cable run. We suggest working from the maximum distance and working down if you are unsure of the length of your cable run.

Error Message: ‘The application has failed to start because its side-by-side configuration is incorrect’

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 –

Microsoft Vistual C++

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

A basic guide to troubleshooting video issues

If you find yourself encountering issues with the picture (either poor quality or no picture) then the following list of common problems and solutions will help you diagnose the problem.

Firmware – Ensure your devices are on the most up-to-date firmware. Check the manufacturer’s website and use the menu settings on any internet-connectable device, such as sources, sinks, displays, projectors, AVRS, etc etc.

Power – Check that both the MHUB and the receivers are fully powered. The front panel of the MHUB should be illuminated* and the power light on the receiver should be on. If the receiver isn’t powered try an alternate power supply from another receiver that you know works. Alternatively, if you’re using the USB power supplies double check that the USB port you are using is supplying the appropriate current.

Is your transmission distance too long? – If you have a power light but the lock light isn’t illuminated this can indicate an issue with the signal strength. The maximum transmission distance for the mHub 2K range is 50m in best-case scenarios and 100m for the MHUB 4k Range. The transmission distance can be reduced by several factors, most commonly wall plates, patch panels and stranded patch leads can significantly reduce signal strength and potentially reduce the maximum distance the matrix can transmit signal. Whenever possible you should try to use a straight point to point connection to guarantee maximum distance.

Resolution – Check that you are using compatible resolutions between your source devices and displays, in particular you should be looking for situations where a TV is perhaps older than the rest of your displays and doesn’t support the same video formats (for instance it only supports 720p) Try reducing the resolution on your source devices and see if this fixes the issue. Also, if reducing the resolution causes the picture to appear again this can point to an issue with the bandwidth which can be addressed by reducing the transmission distance.

Snow/Sparkly picture – This is most often seen when the MHUB is failing to fully establish a connection with the receiver. Your first step should be to use another working location to verify the integrity of both the receiver and output on the matrix. Once you are happy both the receiver and MHUB output are working you should take a look at all your cables. Check that your RJ45 connectors are properly terminated to 568B standards and try swapping out the HDMI cables for ones from working locations.

* – with the MHUB family of products, If the unit has been idle for 5 minutes the panel may have gone into power-saving mode