Some devices no longer have built in IR receivers. To enable them to be used with the uControl app you can add a third party device called FLIRC. This connects to a source device via USB and turns IR codes into control commands the source device recognises.
Load up the Flirc software and in the top left click File, and then Load Configuration and choose the NVIDIA Shield profile you have just downloaded
Remove your Flirc from the laptop/PC and connect it to the female USB port on the back of your NVIDIA Shield. Next place the IR transmitter from you HDANYWHERE device on or near to the Flirc.
Once this is done you can install the NVIDIA Shield IR pack and control your NVIDIA device with uControl.
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.
Using a matrix and providing Dolby Atmos or DTS-HD audio.
If you are planning a cinema or media room supplied by MHUB that requires a multichannel audio signal like Dolby Atmos or DTS-HD then you will need additional hardware to achieve this result.
Why do I need additional hardware and what does it do?
In order to enjoy Dolby or DTS audio in a cinema or media room you will need to instruct your source device (AppleTV / Bluray / Set top box etc) to output its audio in Dolby Atmos or DTS-HD only.
If all the zones in your property can accept a multichannel Dolby or DTS signal then you will have no problem but the chances are that the rest of the rooms in the property will just have a standard TV with a left and right speaker only – think of a kitchen TV display or a TV in a kids room.
You therefore need a device that sits in-line (between) your HDMI video source and the MHUB that does the following important things:
Sends an untouched signal from your HDMI source to your AVR (as if they were connected directly to one another) to provide it with Atmos or DTS-HD audio and…
Split the signal and ‘downmix’ it so all those channels of audio are mixed into a left and right only for all other displays that the MHUB serves.
This guide explains how to pull data from Shelly’s API so you can control it directly from uOS.
Please note: this guide covers how to execute a command for a Shelly light, if you are using a different device the same logic applies, you only need to change the parameters. Please find the link to Shelly’s API document below for commands relating to different devices.
There are a few ways you can get the IP address if your Shelly device:
Use a network scanner app like Fing to find Shelly on your network.
Log into your wireless router and look for Shelly in the DHCP table.
What a typical Shelly command looks like
/color/0?turn=on&red=0&blue=0&green=255
This only shows the logic of a Shelly command, you may be controlling a relay and therefore need to use different parameters. There will be a link at the bottom which will take you to Shelly’s API documentation where you can find all their codes.
/color/0?
This is the mode of the device and declares it is an RGBW2 controller. If you were writing a command for an automated blind it would be /relay/0?.
turn=on
This affects the state of the device.
red=0&blue=0&green=255
Testing your APIs
You can test your Shelly command in the URL to see if it works. Make sure to include http:// for it to work properly.
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.
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.
Figure 1: Ports used for stacking video and transporting IR commands (cascade). You will need to identify these ports to stack into other MHUB 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.
Figure 2: (8×24) system wiring example: Connect from the Foundation Layer UP the MHUB S stack as many times as neeeded.
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)
Figure 3: In this 8×24 system a native video source remote control (in Zone R) is being used to send IR commands through the MHUB S stack from S3 back to S1 Foundation Layer and correctly sent to the source being watched in Zone R.
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.
Connect to system
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.
Connect to system
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.
Connect to system
Stack
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.
Connect to system
Stack
Master Controller
Layers
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.
Connect to system
Stack
Master Controller
Layers
5. Naming devices
Name the devices so that they’re easily identifiable.
Connect to system
Stack
Master Controller
Layers
Naming
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)
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
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.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
8. Control Type
Choose uControl as the Control Type.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
9. System Name
Confirm the names of your devices.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
10. Setup Connections
This next step will allow us to make the manual connections between the multiple devices.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
Connections
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.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
Connection
Manual Connections
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.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
Connection
Manual Connections
Zones
13. Complete
Now the system has been configured press “Finish” and you will be taken out of the web interface.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
Connection
Manual Connections
Zones
Complete
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”.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
Define Connection
Manual Connections
Zones
Complete
Reboot
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.
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
Extracting video audio from MHUB and sending it to speakers
Today’s TVs are very thin with the latest models able to be rolled away into a box! A thinner TV is lighter, easier to install and generally more pleasing to the eye as these new advancements can radically change how your traditional TV looks or is installed into your property.
These advancements have reduced the space inside the TV to an absolute minimum and often a causality of this is the internal TV speaker. Speakers are either located on the rear of the panel (leading to muffled audio) or underneath and in many cases can not provide the type of audio amplification to match the large screen sizes found in the marketplace today.
Soundbars have plugged the gap, but they aren’t the solution.
Soundbars have plugged this gap as customers try to achieve audio reproduction that matches their picture quality. Whilst a soundbar is a simple solution to the problem it fair to say that it doesn’t present itself as the most elegant in that it’s additional (visible) hardware that you need to add to your AV setup. The soundbar is also tied to the function of the TV; so it’s not very easy to listen to music on the same device, for example.
De-embed the audio and manage it separately.
Using MHUB it’s possible to extract the audio that would be sent to your TV – or even the audio generated from your TV apps like Disney+ or Netflix and send that to speakers in your room. Additionally, when the TV is off you can listen to music on the same speakers. If your speakers are embedded in your walls or are in the ceiling then you won’t even notice them, but you’ll hear the difference.
Watch the setup video instead.
MHUB PRO 2.0 + MHUB AUDIO: how does it work
To achieve this you will need to use MHUB PRO 2.0 and MHUB AUDIO operating together as one system which we call V&A (video & audio).
The MHUB PRO 2.0 can de-embed the audio from any video stream or TV app (using ARC) and downmix it into 2 channel stereo. This audio is then fed into the inputs on MHUB AUDIO which manages amplification of that audio. If you have inputs that require amplification then you can stack another MHUB AUDIO (up to three times using uControl) or as many as you want if you’re using a control system.
We are here to help. Let us know if you have any questions…
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.
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).
Figure 1: Showing stereo connection between MHUB PRO 2.0 and MZMA (6×4) 55.
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.
Figure 2: Wiring guide showing video and audio connection between MHUB PRO 2.0 and MZMA (6×4) 55(s).
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.
Connect to system
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.
Connect to system
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.
Connect to system
Stack
Master Controller
4. Setting Stack Layers
Select your MHUB as the primary device, and then select MZMA as the secondary device.
Connect to system
Stack
Master Controller
Layers
5. Naming devices
Name the devices so that they’re easily identifiable.
Connect to system
Stack
Master Controller
Layers
Naming
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)
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
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.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
8. Control Type
Choose uControl as the Control Type.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
9. System Name
Confirm the names of your devices.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
10. Setup Connections
This next step will allow us to make the manual connections between the multiple devices.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
Connections
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.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
Connection
Manual Connections
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.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
Connection
Manual Connections
Sources
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.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
Connection
Manual Connections
Zones
13a. Zones
Once you have added all Outputs to the zone it should look like below, press CREATE ZONE to finish.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
Connection
Manual Connections
Zones
13b. Zones
Check over your zones and make sure you have assigned your devices to the correct zones.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
Connection
Manual Connections
Zones
14. Complete
Now the system has been configured press “Finish” and you will be taken out of the web interface.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
Connection
Manual Connections
Zones
Complete
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”.
Connect to system
Stack
Master Controller
Layers
Naming
Access uControl
Owner Account
Control Type
System Name
Define Connection
Manual Connections
Zones
Complete
Reboot
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.
