Using control drivers which require authorisation before use.

update-mos

HDANYWHERE are now working with Intrinsic Dev for control driver integration.

If you see the label “DRIVER REQUIRES LICENSE ACTIVATION FROM VENDOR” then this means you need to create an account and generate a license key before the driver will work. As always, the driver remains FREE OF CHARGE. The process takes under 5 minutes to complete and offers HDA Pros the following benefits:

1. Track and find your drivers for every install you commission.
2. Be kept updated if the driver gets patched or improvements are added.
3. Check to see if the driver is operating correctly.
4. The ability to improve your HDA Pro listing

 

1. Visit https://www.intrinsicdev.com/ and login or create an account.

1

 

2. Ensure that you are logged in.

2

3. Find the HDA driver you want to download https://www.intrinsicdev.com/brands/hdanywhere

3

 

4. Click on “Get License Key”

 

5. You will need to provide the MAC address of your controller and some site details. Scroll to the bottom of the page and a button will appear to proceed/download. If you have not completed this step correctly then the button to download will not appear.

5

 

6. Download the driver and make a note of the activation code.

6

Using FLIRC with Amazon devices for use with uControl

Some devices no longer have built in IR receivers to 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.

The FLIRC device can be found here – https://flirc.tv/

If you are using this with a firestick you will also need an OTG cable like this –


    update-mos

    Install the flirc software on your computer, and install this profile into the FLIRC – Fire TV

    Connect the OTG cable to the Firestick, then the FLIRC then the power.

Next locate the IR transmitter from you HDANYWHERE device on or near to the FLIRC.

Once this is done you can install the FireTV(FLIRC) IR pack and control your Amazon device with uControl.

uControl input error on iOS (version 2.4.6.1.0.4)

This bug has been resolved in uControl on iOS (2.4.7.1.0.2). You must delete uControl from your iOS device first and reinstall it from the App Store for the patch to apply.

We have received reports from customers informing us that input labels and switching ability has been lost in the latest release of uControl on iOS (version 2.4.6.1.0.4).

Affected systems will present the following symptoms:

No input labels inside uControl

The problem exists exclusively within uControl on iOS. We recommend that you do not change your MHUB settings, run any updates or change any configuration. The repair will be delivered via a patch applied to the uControl app.

  • App will find and connect to MHUB as normal.
  • App will load in to zone as normal.
  • App will not display switching/uControl pack options

The error involves MHUB systems from late 2016 / early 2017 which were sold on MHUB-OS version 7.0 or lower and then upgraded. When these systems were upgraded to MHUB-OS version 8.0+ a one-time script was required to convert data from the old format (version 7 and below) to the new format (version 8 and above) which is active today still. To maintain backwards compatibility the original data format was kept on older systems.

uControl (version 2.4.6.1.0.4) contains updates for brand new systems (MHUB PRO 2.0) and MHUB AUDIO operating in stacked mode and removes the backwards check for compatibility. This has been confirmed as the source of the issue.

This blog post will update daily to help keep track of our progress and attempt to rectify the problem.

Update timeline

Wednesday 24th June 2020
Testing confirmed OK overnight. uControl on iOS (2.4.7.1.0.2) deployed to general userbase.
We recommend a fresh install, by deleting the app from your iOS device then reinstalling from the app store.

Tuesday 23rd June 2020
Patch is being tested. Please email us (support@hdanywhere.com) if you would like to beta test this release.

Monday 22nd June 2020
Cause has been identified and work on patch is underway.

Sunday 21st June 2020
Senior technical staff upgrade issue urgency level. Developers begin work to start identifying cause.

Saturday 20th June 2020
First notice of problem reported. Customer services respond using standard procedures.

Friday 19th June 2020
uControl on iOS (2.4.6.1.0.4) deployed to general userbase.

Using ARC with Control4 and MHUB

Control4 does not natively support Audio Return Channel (ARC). With more and more content coming from the likes of Netflix, AppleTV, Disney+ Youtube and BBC iPlayer, this presents a problem for installers who want to take this audio and feed it to external speakers as part of their Control4 project.

This video shows you how MHUB and our Control4 driver makes the impossible possible and describes the steps you need to follow in Composer to achieve ARC in Control4.

More information:

Please ensure that both your MHUB and the Control4 driver supports ARC.

Download control driver:

http://support.hdanywhere.com/hda-control-drivers/

Five reasons why Control4 dealers prefer working with MHUB:

https://hdanywhere.com/why-c4-dealers-prefer-mhub-pro-2

4×4 and 8×8 HDBaseT / HDMI Matrix: MHUB PRO 2.0

https://hdanywhere.com/mhub-pro-2

HDANYWHERE product information on power usage and BTU outputs

The table below details the PSU DC rating, the system power draw in watts and BTU(British thermal unit) heat output of each device.

Product Code Release PSU Rating (DC) Power Draw (watts) BTU

XTND

XTND2K30 2017 5V 1A 2.5 9
XTND4K40ARC 2018 24V 1A 20 68
XTND4K100TPC 2018 24V 1A 12 41

MHUB

MHUBAUDIO64 2018 24V 13.4A 520 1774
MHUBMAX44 2018 24V 2.71A 19.2 66
MHUB431U 2018 24V 2.71A 36 123
MHUB862U 2018 24V 2.71A 28 198
MHUBPRO4440 2018 24V 2.71A 40 136
MHUBPRO8870 2018 24V 6.3A 98 334
MHUB4K44PRO 2016 24V 2.71A 42.72 146
MHUB4K88PRO 2016 24V 6.3A 100 341
MHUBPRO24440 2019 24V 5A 68 232
MHUBPRO288100 2019 24V 6.3A 130 444

SPLITTERS AND SCALERS

SPLITTERMAX12 2019 5V 1A 2 7
SPLITTERMAX14 2019 5V 1A 2 7
SIGNALMANAGER 2018 5V 1A 1.65 6

Voice control with Amazon Alexa* using the “MHUB AV” Skill

HDANYWHERE (HDA) Amazon Alexa App Skill

*Before you activate the Alexa Voice Service with your MHUB, make sure Amazon support your territory and version. We cannot guarantee voice services or offer support to those territories not officially supported by Amazon. Check here: https://www.amazon.co.uk/gp/help/customer/display.html?nodeId=202207000

What you need to get your MHUB to respond to voice commands:

  1. You have completed the first-boot procedure within MHUB-OS
  2. You have MHUB-OS version 8.10 or higher installed on your MHUB
  3. You have an active HDA Cloud account
  4. You have downloaded uControl packs for all displays and source devices you want to control
  5. You have completed input mapping in MHUB-OS
  6. You have an active Amazon account
  7. You have an Amazon Alexa enabled device, such as Amazon Dot/Echo/Show

Setting up AV Skill

Configure voice commands to do exactly what you want

Let’s take the command “Alexa, Turn on football” as an example.

It might appear like a very simple command but there are a number of things that need to happen in order to watch football! First the TV might need to turn on, but in which room? The volume might need to be set to a desired limit. The correct source input might need to be selected on MHUB and finally that source will need to navigate to the channel hosting the football.

You can configure all those actions in what we call a “Sequence”.

Taking the example above:
Alexa (this wakes up your Amazon Dot/Echo/Show)
Turn on… (this invokes the smarthome skill)
football (this is your custom name for the Sequence, it can be anything you want)

Inside MHUB-OS we can configure exactly what “football” does.

  • You can select if you want MHUB to turn your TV on and adjust the volume
  • You can tell MHUB to switch to the source device with has the football on it
  • You can instruct MHUB to change the channel on that source device

Read more about Sequences and Scheduling.

Troubleshooting

  • When searching for devices, nothing is found
    1. Check you cloud account details were entered correctly
    2. Ensure only 1 system is linked with the cloud account being used
    3. Ensure you have backed up the system to cloud after configuring the Alexa Skill on MHUB-OS
  • When you try to control a zone Alexa says the command isnt supported
    1. Ensure there are no other devices linked to the Alexa that have the same name as the zone.

Here’s a table of all the commands you can tell your MHUB to do…

Now you’re ready to go. Take a look at a full list of commands that you can say to your Echo.

Loxone API 2.0 installation guide

The latest control driver from Loxone can be downloaded here

The Loxone API 2.0 driver is compatible with the following HDANYWHERE products:

MHUB431U
MHUB862U
MHUB4KPRO44
MHUBPRO4440
MHUB4KPRO88
MHUBMAX44
MHUBAUDIO64

and the following Loxone products:

Miniserver
Miniserver Go


IMPORTANT

Before setting up the Loxone driver, the MHUB must have been through its first boot process. This can be done by navigating to the MHUB’s IP address in a web browser or in uControl and following the onscreen instructions. No other setup of the matrix is required.

Add the HDANYWHERE MHUB device template as a “Virtual Output”

Loxone 1

Next, assign your Inputs and outputs

Loxone 2

Loxone 3

The video below shows the entire process

 

RTI API 2.0 installation guide

The latest control driver from Chowmain software can be downloaded here included in the download is also an in-depth guide to installing the driver

The HDAnywhere MHUB RTI driver allows for control of the HDAnywhere range of Video and Audio distribution products. The driver allows for direct switching of inputs to outputs,  the ability to switch preconfigured zones, control of audio levels (volume, mute, etc) and the ability to send IR codes as well as being able to reboot or restart the system.  It is compatible with the following systems:

MHUB431U
MHUB862U
MHUB4KPRO44
MHUBPRO4440
MHUB4KPRO88
MHUBMAX44
MHUBAUDIO64

and the following RTI products:

RP-4RF
XP-3
XP-6
XP-6s
XP-8s
XP-8v

rti-HDA

IMPORTANT

Before setting up the RTI driver, the MHUB must have been through its first boot process. This can be done by navigating to the MHUB’s IP address in a web browser or in uControl and following the onscreen instructions. No other setup of the matrix is required, but this step must be completed before the RTI processor can utilise the matrix I/O ports. It is not required otherwise.

Control 4 API 2.0 installation guide

The latest control driver from Chowmain software can be downloaded here

It allows the Control processor to utilise the IR inputs and outputs of the HDANYWHERE matrix as if it was there own. Allowing installers to spec smaller Control 4 processors than they would typically need and is compatible with the following HDANYWHERE products:

MHUB431U
MHUB862U
MHUB4KPRO44
MHUBPRO4440
MHUB4KPRO88
MHUBMAX44
MHUBAUDIO64

and the following Control 4 products:

CA-1
EA-1
EA-3
EA-5
HC250
HC800
HC1000

control4-ca1
IMPORTANT

Before setting up the Control 4 driver, the MHUB must have been through its first boot process. This can be done by navigating to the MHUB’s IP address in a web browser or in uControl and following the onscreen instructions. No other setup of the matrix is required, but this step must be completed before the C4 processor can utilise the matrix I/O ports. It is not required otherwise.

Add the HDANYWHERE driver as you would any other driver, the driver will auto-discover a video matrix or multiple Audio Matrices

The next step is to setup your control and AV connections. Traditionally in a normal Control 4 setup, you would bind the source devices ‘control inputs’ with an IR output on the C4 controller. Instead, with the MHUB Video driver’s you can route the control through the MHUB’s IR ports utilising the IP>IR Engine. Similarly, Display IR is routed through the Display IR ports on the matrix. This video shows how to make these bindings

MHUB-OS 8 and uControl 2 update troubleshooting and FAQ

Below is a list of three issues which have been reported to HDANYWHERE (HDA) after updating older systems to MHUB-OS 8 (MOS 8). If you have encountered any of these problems then you will find a solution below. If your issue is not shown below then contact the HDA support team via email on – support@hdanywhere.com.

Jump to issues and solutions:

  1. My MHUB is stuck in a loop and is always prompting me to update again – I can not access any other MHUB-OS page.
  2. I am having problems connecting with HDA Cloud because there is an error with my serial number.
  3. I have connected to my MHUB and all my settings are gone.
  4. I can’t get uControl to connect to MHUB.
  5. I have an 8×8 system and I can not control my TVs anymore.

1.
I’ve clicked the update from within MHUB-OS and now appear to be stuck on an update page and cannot access any other MHUB-OS page.

This error can occur when MHUB fails to complete the update process completely. This can be caused by a power outage, multiple sessions of MHUB-OS being open at the same time (browser tabs, app) or network issues as the update is applied to MHUB. This has been patched in version 8.02 of MHUB-OS. However, if you find yourself with a problem like this, you will need to contact HDANYWHERE technical support services by emailing support@hdanywhere.com with the subject line: “Update error code:728″ and we will treat this with the highest priority.

2.
I’ve updated to MHUB-OS 8 and when linking to HDA cloud it says there is an error with my serial number.

This error can occur when the MHUB cannot connect with HDA cloud. This can be caused by network issues or power outage. This has been patched in MHUB-OS version 8.02. However, should you find yourself in this situation you can recover the serial number following these steps

  1. Step 1 – Load a web browser on a pc or mac(such as Chrome), and enter the following in to the URL bar [MHUB IP ADDRESS]/diagnostics.php. Then click on “GET SERIAL NUMBER”
  2. Step 2 – Confirm that you want to change the serial number
  3. Step 3 – You will get a notifcation saying that the serial number has been updated, and should notice the serial number is showing in the system information section near the top of the page.

If after using the serial number recovery method above, it still does not appear, you will need to contact HDANYWHERE technical support services by emailing support@hdanywhere.com with the subject line: “Update error code:628″

3.
uControl has updated, when I reconnected to my MHUB all my settings were gone.

This can occur when reconnecting to your MHUB after uControl has updated to version 2 or greater and selecting the incorrect option. When uControl loads you are shown 2 options:

  • “SETUP A NEW MHUB SYSTEM” – This is used when you are connecting to a brand new or unconfigured MHUB system. If you select this option and have a previously configured system, all user data will be removed requiring the MHUB to be fully reconfigured like a new system.
  • “CONNECT TO AN EXISTING MHUB SYSTEM” – This is used when you are connecting to a previously configured MHUB system. Existing data will remain untouched, and uControl will sync the data stored. If you were connected with a previous version of uControl this option should be used.

4.
After the update, uControl can not connect to MHUB

HDANYWHERE released an update to uControl and all MHUB systems on Wednesday 10th October 2018. To ensure that your MHUB works correctly both your MHUB and uControl must be on the correct software version.

MHUB / MHUB-OS = version 8 or above
uControl (iOS / Android) = version 2 or above

If you find that one version of uControl can connect to MHUB and the other can not then it is very likely that you did not complete the update to MHUB-OS. As soon as you have run this process then uControl should work on all devices with no issue. For this solution HDANYWHERE are assuming that your system is already in a pre-configured state and that you are wanting to CONNECT TO AN EXISTING SYSTEM.

Steps to resolve this issue:

  1. Ensure that you have the latest version of uControl installed on your iOS or Android device. Download uControl for iOS or download uControl for Android
  2. Once you have the app installed, please load it up and follow the instructions here:

5.
I have a 8×8 or 8×6+2 system and after the update, I lost the ability to control my TVs

If you are able to control your source devices with uControl but can not control your displays then a quick update to your MHUB will resolve this problem. Instructions detailing how to update your MHUB can be found here. Ensure that you use uControl to update your MHUB and do not try to update your system via MHUB-OS.

MHUB-OS 8: a quick guide to zones

Zones define a physical space in a property where outputs from MHUB terminate.

A Zone can include a maximum of 1 video output and a maximum of 4 audio outputs. For example, you can create a zone called “Kitchen” and assign 1 video and 1 audio output to it to provide you with viewable TV and sound. A Zone must contain at least 1 output from an MHUB for it to be addressable for control. Note: outputs can not be shared or split to more than 1 Zone.


MHUB zones

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:

  1. EULA and Privacy policy
  2. Name your MHUB
  3. Name your source devices
  4. Create zones
  5. Assign outputs to zones
  6. Confirm zones
  7. Connect MHUB to HDA Cloud
  8. Complete setup

HDANYWHERE(HDA) recommends that every MHUB install goes through its first boot process to ensure that the MHUB is setup correctly.

How long does the process take to complete

If you have an update to install then then first boot usually take about 10 minutes. If there is no update you can normally finish the entire process and have an operational MHUB system well within 5-7 minutes.

Yes. You do not need to access MHUB-OS if you don’t want to. But this is only recommended if you intend to control you MHUB via a control system. You will also miss the opportunity to increase your warranty period and open your MHUB to additional features or services.

I don’t want to use MHUB-OS or go through the first boot process, will MHUB work like a normal?

Yes. You do not need to access MHUB-OS if you don’t want to. But this is only recommended if you intend to control you MHUB via a control system. You will also miss the opportunity to increase your warranty period and open your MHUB to additional features or services.

I made a mistake in the first boot process, can I go back or make a change?

Yes. You can go all the way back to the update step and correct any incorrect information you entered. Alternatively, you can also access MHUB-OS (after you have completed first boot) and change anything then.

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

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.

  1. Click ‘Connect to an exisiting MHUB system’, uControl will scan your network for any MHUB systems
  2. Select your MHUB device
  3. Connect to your MHUB
  4. 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:

  1. Click ‘CONNECT TO MHUB SYSTEM’, uControl will scan your network for any MHUB systems
  2. Select your MHUB device
  3. uControl will check the current version of MHUB-OS, if an update is required, you will be prompted to update it.
  4. Connect to your MHUB
  5. 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.


update-mos

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

 MHUB Firmware 1.30

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