Category: Miscellaneous

  • Sending TV audio from MHUB to in-wall or ceiling speakers using MHUB PRO 2.0 and MHUB AUDIO

    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).

    Download the MHUB (V&A) guide.

    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…

    .

    Contacting us is super easy and we respond fast. Let us know if you have any questions about setting up a V&A system.

  • Controlling AudioFlow from uOS

    This guide explains how to pull data from the Audioflow API so you can control it directly from uOS, uControl App and uControl Remote.

    Before you begin, you will need:

    Important: You must have the IP address for AudioFlow first

    You can get the IP address of your AudioFlow switch by:

    • Using a network scanner application like Fing on your mobile phone to scan your network.
    • Download the AudioFlow app and connect it to your network. From here go to settings, and you will see its IP address.

    Step 1 – Getting Data

    Step 2 – Build Function

    Need more help with the API? Get in touch.

    All HDA staff are able to help with any API questions you might have including any advanced features. Get in touch for help or assistance.

  • MHUB PRO 2.0 and MZMA Stack

    mhub-pro2-hero-guide

    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

    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

    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

    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

    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

    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).

    1. “Audio (Out)”
      The audio ports on the back of the MHUB PRO 2.0 are labelled Audio (Out).
    2. “Audio (In)”
      The audio ports on the back of the MZMA (6×4) 55 are labelled Audio (In).
    Ports used in stack
    Figure 1: Showing stereo connection between MHUB PRO 2.0 and MZMA (6×4) 55.
    1. Connect your 3.5mm stereo cables to the Audio (In) port of the MZMA (6×4) 55 and repeat for every zone.
    2. Connect your 3.5mm stereo cables to the Audio (Out) port of the MHUB PRO 2.0 and repeat for every zone.
    3. Connect speakers via phoenix connector into the Audio (OUT) of the MZMA (6×4) 55 and repeat for every zone.
    4. 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.
    fig2
    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.

    1. 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.

    1. Connect to system
    2. 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.

    1. Connect to system
    2. Stack
    3. Master Controller

    4. Setting Stack Layers

    Select your MHUB as the primary device, and then select MZMA as the secondary device.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers

    5. Naming devices

    Name the devices so that they’re easily identifiable.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. 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)

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. 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.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Owner Account

    8. Control Type

    Choose uControl as the Control Type.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Owner Account
    8. Control Type

    9. System Name

    Confirm the names of your devices.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Owner Account
    8. Control Type
    9. System Name

    10. Setup Connections

    This next step will allow us to make the manual connections between the multiple devices.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Owner Account
    8. Control Type
    9. System Name
    10. 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.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Owner Account
    8. Control Type
    9. System Name
    10. Connection
    11. 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.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Owner Account
    8. Control Type
    9. System Name
    10. Connection
    11. Manual Connections
    12. 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.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Owner Account
    8. Control Type
    9. System Name
    10. Connection
    11. Manual Connections
    12. Zones

    13a. Zones

    Once you have added all Outputs to the zone it should look like below, press CREATE ZONE to finish.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Owner Account
    8. Control Type
    9. System Name
    10. Connection
    11. Manual Connections
    12. Zones

    13b. Zones

    Check over your zones and make sure you have assigned your devices to the correct zones.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Owner Account
    8. Control Type
    9. System Name
    10. Connection
    11. Manual Connections
    12. Zones

    14. Complete

    Now the system has been configured press “Finish” and you will be taken out of the web interface.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Owner Account
    8. Control Type
    9. System Name
    10. Connection
    11. Manual Connections
    12. Zones
    13. 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”.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Owner Account
    8. Control Type
    9. System Name
    10. Define Connection
    11. Manual Connections
    12. Zones
    13. Complete
    14. 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.

  • 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

  • How to deal with Picture loss/dropout on your display(s) when using MHUB

    ​Your MHUB is similar to a central heating system in that there are many components that all need to come together to deliver a working system. An intermittent or full loss in picture on one or more displays can be down to a number of things.

    • HDMI cables going into MHUB and from the display receivers to the displays
    • Your network cabling infrastructure, the termination quality, the distance of the cable run and the number of times that cable runs through patch panels or wall plates.
    • The physical output port on the MHUB
    • The display receivers
    • The actual source devices (more common than you think!) and the AV they are outputting (4K, 1080p, surround sound, HDCP format etc)

    Unfortunately, there is no fast way to determine this. To do this test correctly you will need to test for several days to ensure the results are accurate and your system is stable.

    If dropout occurs on one display in your property…

    The first thing to do is disconnect all sources and outputs from MHUB so you are left with 1 source (preferably the source you notice picture loss on) and 1 output (preferably the display you notice picture loss most frequently on).

    Grab a piece of paper and log the following outcomes when you test the following:

    1. If picture loss is happening only in one location in your property then take a display receiver (and the HDMI cable going into the display) from a known working location and swap it in the area you’re noticing picture loss.
    2. If you still experience picture loss then run freshly terminated Cat 6 cable from the MHUB to the display receiver point-to-point (no breaks in cable) and check again.
    3. If you are still having a problem then connect your new Cat 6 cable to another output port on MHUB.
    4. If #3 doesn’t resolve the problem then disconnect your source from MHUB (and the HDMI cable) and plug it directly into your test display using the same HDMI cable.
    5. If the picture is stable then take the source and the HDMI cable back to MHUB and plug it into another HDMI input and test for picture loss on your display.
    6. Finally, drop the resolution on your HDMI source to something you know the display will accept easily (something like 1080p Stereo)

    If dropout occurs on all displays in your property…

    Start by disconnecting your source from MHUB (and the HDMI cable) and plug it directly into a test display using the same HDMI cable.

    Grab a piece of paper and log the following outcomes when you test the following:

    1. If the picture is stable then take the source and the HDMI cable back to MHUB and plug it into another HDMI input and test for picture loss on your display.
    2. If you still experience loss in picture then drop the resolution on your HDMI source to something you know the displays will accept easily (something like 1080p Stereo)
    3. Remove all outputs from MHUB until you’re left with only one output connected, it could be any port but we recommend starting with A. Check for a stable picture and repeat for each output port individually.
    4. If all ports passed the test in #4 then start connecting additional outputs back to MHUB starting B (so you should have A + B now), if the picture is stable add output C and so on.

    If you log any problems or positives with each test then let us know and we can assist you further.

  • Controlling KNX from uOS

    This guide explains how to pull data from KNX’s protocol so you can control it directly from uOS.

    KNX in uOS

    Please note: this guide assumes you have access and knowledge of ETS6, and your own KNX/Weinzierl gateway. In this guide we are using a BAOS 774 gateway, but you may have a different one, so refer to this site for more Weinzierl product knowledge.

    What this guide will cover:

    1. How to control KNX devices in your home.
    2. How to add that API into uOS.

    Important: you must have the gateway IP address first

    You can get the IP address of your gateway by:

    • Use a network scanner application like Fing on your mobile phone to scan your network.
    • You can also get the IP address from the properties tab of the device in KNX’s ETS.

    For the purposes of this guide we are going to pretend that your Weinzierl gateway is on IP address 192.168.1.15 and your uOS device (MHUB, MZMA or Zone Processor) is on 192.168.1.196. We will use this to illustrate all examples moving forward.

    What a typical BAOS API command looks like

    http://192.168.1.15/baos/SetDatapointValue?Datapoint=2&Format=DPT1&Length=1&Value=false

    The above command will trigger our BAOS gateway to send a telegram to datapoint 2, which will switch off our light.

    Understanding what the variables in the API above mean:

    http://192.168.1.15
    The command starts with http:// as it can be sent over a URL, followed by the IP address of your KNX/Weinzierl gateway.

    /baos/
    This is the device type of a Weinzierl device.

    SetDatapointValue?Datapoint=2
    Here we are setting this command to send to our KNX data point to two.

    &Format=DPT1
    This is the sub data point, and sets the rules of which values are allowed.

    &Length=1&Value=false
    This is the length of the data point type, and the value is boolean therefore setting it on or off.

    Testing your APIs

    We recommend that you test every API before you enter them into uOS. All IP based APIs all have different requirements when it comes to testing but the KNX API is great because it can be tested on your browser.

    To test your API, open a web browser and enter the full API (including http://192.168.1.15) in the URL window and hit enter.

    If the KNX device responds as you expected then your API is working and you can proceed adding it into uOS.

    If it doesn’t work then try the following:

    • Make sure the IP address is correct.
    • Make sure that you do not have any typos.
    • Ensure that your IDs are correct and that you’re observing the correct device.
    • Make sure that the structure of the API matches our example no spaces, no special characters, data is in the correct case (often lowercase).

    How to add your APIs into uControl

    Need more help with the API? Get in touch.

    All HDA staff are able to help with any API questions you might have including any advanced features. Get in touch for help or assistance.

  • 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

    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

    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

    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

    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

    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).

    1. “Audio (OUT)”
      The audio ports on the back of the MHUB (4×4)/(6×6) 100A are labelled Audio (Out).
    2. “Audio (In)”
      The audio ports on the back of the MZMA (6×4) 55 are labelled Audio (In).
    Ports used in stack
    Figure 1: Showing stereo connection between MHUB (4×4)/(6×6) 100A and MZMA (6×4) 55.
    1. Connect your 3.5mm stereo cables to the Audio (In) port of the MZMA (6×4) 55 and repeat for every zone.
    2. Connect your 3.5mm stereo cables to the Audio (Out) port of the MHUB (4×4)/(6×6) 100A and repeat for every zone.
    3. Connect speakers via phoenix connector into the Audio (OUT) of the MZMA (6×4) 55 and repeat for every zone.
    4. 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.
    fig2
    Figure 2: Wiring guide showing video and audio connection between MHUB (4×4)/(6×6) 100A and MZMA (6×4) 55(s).

    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.

    1. 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 an MHUB (4×4)/(6×6) 100A and an MZMA (6×4) 55 choose stack.

    1. Connect to system
    2. 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.

    1. Connect to system
    2. Stack
    3. 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.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers

    5. Naming devices

    Now we have chosen where our devices go in the stack, we must name them so that they’re easily identifiable.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming

    6. Access uControl

    Assigning our hardware has now been complete, after pressing access uControl we will continue the setup in uOS.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl

    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.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Cloud Account

    8. Control Type

    Choose uControl as Control Tyoe.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Cloud Account
    8. Control Type

    9. System Name

    Confirm the names of your devices.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Cloud Account
    8. Control Type
    9. System Name

    10. Setup Connections

    This next step will allow us to make the manual connections between the multiple devices.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Cloud Account
    8. Control Type
    9. System Name
    10. Connections

    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.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Cloud Account
    8. Control Type
    9. System Name
    10. Connections
    11. 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.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Cloud Account
    8. Control Type
    9. System Name
    10. Connections
    11. Manual Connections
    12. Sources

    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.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Cloud Account
    8. Control Type
    9. System Name
    10. Connection
    11. Manual Connections
    12. Sources
    13. Zones

    14. Complete

    Now the system has been configured press “Finish” and you will be taken out of the web interface.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Cloud Account
    8. Control Type
    9. System Name
    10. Connection
    11. Manual Connections
    12. Sources
    13. Zones
    14. 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. Ths is needed to apply the settings you have just changed, once the 2 minutes is up press “Continue”.

    1. Connect to system
    2. Stack
    3. Master Controller
    4. Layers
    5. Naming
    6. Access uControl
    7. Cloud Account
    8. Control Type
    9. System Name
    10. Define Connection
    11. Manual Connections
    12. Sources
    13. Zones
    14. Complete
    15. 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.

  • 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.

  • Enabling DHCP on MHUB if you have lost it on your network

    If your MHUB has been configured with a fixed IP address and you changed your network infrastructure then your MHUB may become unreachable by your new router.

    With MHUB PRO models you can enable DHCP from the MENU button on the front panel by holding it down for 3 seconds. For MHUB 100A & MHUB U (4×1+1) 40 models you need to follow Guide 1, for MHUB U (4×3+1) 40 & (8×6+2) 40 models follow Guide 2 and for older MHUB U (micro USB on front) models use Guide 3.


    MHUB 100A & MHUB U (4×1+1) 40

    To reset DHCP on an MHUB (4×4, 6×6, 8+8×8) 100A you can either use the Hercules method which is included below, or you can hold down Output A on the front panel of the matrix for 10 seconds.

    To reset an MHUB S (16+16×16) 100A press and hold button 1 for 10 seconds.

    To reset to DHCP on an MHUB U (4×1+1) 40 you can press and hold the 2 front panel buttons for 10 seconds.

    Items needed

    Steps

    1. Install Hercules and open the software on your PC or laptop

      2. Hercules interface

    2. Connect the serial to phoenix cable to the MHUB, and then your serial to USB adaptor into a laptop or PC.
    3. Go back to Hercules, ensure that the Baud is 115200, the Data Size is 8, the parity is None, the Handshake is OFF and finally, the Mode is Free.
    4. Click on the “Open” button. Your PC will now connect directly to the MHUB.
    5. Type DHCPON! in the box labelled “Send” and click “Send”. Make sure that “Hex” remains unticked.
    6. You will receive a response in the “Received/Sent Data” box. This will confirm that the MHUB has been reset to DHCP.
    7. Hard reboot your MHUB by pulling the power out from the back of the system.
    8. Reconnect MHUB to your router as normal and power up the system. Your MHUB should now be discoverable.

    MHUB U

    Items needed

    Steps

    1. Install Hercules and open the software on your PC or laptop

      2. Hercules interface

    2. Connect the serial to phoenix cable to the MHUB, and then your serial to USB adaptor into a laptop or PC.
    3. Go back to Hercules, ensure that the Baud is 115200, the Data Size is 8, the parity is None, the Handshake is OFF and finally, the Mode is Free.
    4. Click on the “Open” button. Your PC will now connect directly to the MHUB.
    5. Type DHCPON! in the box labelled “Send” and click “Send”. Make sure that “Hex” remains unticked.
    6. You will receive a response in the “Received/Sent Data” box. This will confirm that the MHUB has been reset to DHCP.
    7. Hard reboot your MHUB by pulling the power out from the back of the system.
    8. Reconnect MHUB to your router as normal and power up the system. Your MHUB should now be discoverable.

    Serial to phoenix Cable

    IMG_10May2021at131731

    MHUB 4K (with micro USB on front panel)

    If your MHUB U has a micro USB port on the right hand side of the front panel then please follow these steps to reset your system. Using Hercules from the steps above, send the following command:

    • Baud Rate 9600
    • Data Size 8
    • No parity
    • Restore Command: %0911. (include the full stop “.”)
    • Query IP Command: %9964.

  • Controlling SilentGliss from uOS

    This guide explains how to pull data from the SilentGliss API so you can control it directly from uOS.

    Shelly in uOS

    What this guide will cover:

    1. How to control SilentGliss window coverings in your home.
    2. How to add that API into uOS.

    Important: you must have the IP addresses first

    You can get the IP address of your SilentGliss gateway device:

    1. Use a network discovery app like Fing to find the SilentGliss gateway on your network.

    What a typical SilentGliss API command looks like

    192.168.1.15/sgbms/v1/device/7/command

    This command only shows the structure and does not include the actual action of the command which needs to be included in the body. This will be explained further through the guide.

    192.168.1.15/
    This is the IP addresss of the gateway, a forward slash (/) needs to be added between each unique variable.

    sgbms/v1
    This is the URL version of the gateway.

    device/7
    This specifies we are affecting a device and what its ID is.

    command
    Command must go at the end as we are performing a POST execution method which is atempting to perform an action.

    Testing your APIs

    We recommend testing your API command before entering it into uOS to ensure it works. To do this we recommend installing an application called Postman.

    If it doesn’t work then try the following:

    • Make sure the IP address is correct.
    • Make sure that you do not have any typos.
    • Ensure that your IDs are correct and that you’re observing a light in the correct room and location.
    • Make sure that the structure of the API matches our example no spaces, no special characters, data is in the correct case (often lowercase).

    How to add your APIs into uControl

    Need more help with the API? Get in touch.

    All HDA staff are able to help with any API questions you might have including any advanced features. Get in touch for help or assistance.