Author Archives: HDANYWHERE Support Team

Controlling GUDE power switching from uOS

This guide explains how to control your GUDE PDU from uOS, uControl App and uControl Remote. Here is a full overview of GUDE’s API.

Gude power switching in uOS

What this guide will cover:

  1. Understanding switching outputs, batches, ports and their status.
  2. How to create a GUDE API so that you can control power in the property.
  3. How to add that API into uOS.

Important: you must have the IP for GUDE first

You can get the IP address of your GUDE by:

  • Using a network scanner application like Fing on your mobile phone to scan your network.
  • Log into your wireless router and look up Gude in the DHCP table.

For the purposes of this guide we are going to pretend that your GUDE PDU 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.

GUDEs ports are simple, port 1 is equal to 1 (p=1) and port 2 is equal to 2 (p=2) and so on. When typing your commands, make sure to follow this logic.

What a typical GUDE API looks like

http://user:secret@192.168.1.15/ov.html?cmd=1&p=1&s=1

The command above switches an output on or off (cmd=1). More specifically it switches/powers output 1 (p=1) on (s=1).

http://user:secret@192.168.1.15/ov.html?
user:secret will only change if updated by the user, otherwise it will always be user:secret, the IP address will most likely be different to the above example.

Understanding what those numbers in the API above mean:

cmd=1, 2, 5, 12
This is the command which decides what kind of switch occurs:

  • cmd=1 switches the output.
  • cmd=2 cancels a batch switch.
  • cmd=5 starts a batch switch.
  • cmd=12 performs a reset.

p=1, 2 …, N
This is the number of the output which is being switched.

s=1
This is the state of the switch. 0 being off and 1 being on.

“&”
This sign allows you to add parameters to your command, every command must be linked by it.

How to Batch Switch using GUDE

Batch switching allows for multiple power outputs to be switched on or off simultaneously with a delay in between each switch if wanted. Below is an example of a batch switch, let’s break it down:

http://user:secret@192.168.1.15/ov.html?cmd=5&p=1&a1=0&a2=1&s=5

  • cmd is equal to 5 signifying a batch switch.
  • p is 1 so port number 1 will be switched.
  • a1 means action followed by a sequential number which increases with each additional action.
  • s in a batch switch is different to a normal switch. s is the delay in seconds between each action. As a defines whether an output is on or off a replaces s.

Testing your APIs

We recommend that you test every API before you enter them into uOS. All IP based APIs have different requirements when it comes to testing but the GUDE API is great because it is super simple.

To test your API, open a web browser and enter the full API in the URL window and hit enter.

Screenshot-2023-05-12-121405

Testing your GUDE API is as easy as entering it into your favourite browser and hitting enter. If the GUDE device does what you expected it to then you’re good to enter it into uOS.

If the GUDE 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 PDU switch.
  • 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.

Controlling Rako scenes and lights from uOS

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

Rako Lighting in uOS

What this guide will cover:

  1. How to find room, channel, scene and level IDs in Rako’s API.
  2. How to create a Rako API so that you can control any light or scene in the property.
  3. How to add that API into uOS.

Important: you must setup Rako first

For the purposes of this guide we are going to assume that your Rako controller 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.

Important: To get an overview of your project, which for this example is on IP address 192.168.1.15, type 192.168.1.15/rako.xml into a web browsers search engine and enter.

What a typical Rako API looks like

192.168.1.15/rako.cgi?room=5&ch=4&sc=0

In most cases you will either want to turn a light on/off or change the scene in any particular room. To do this you will need to send an API which looks like the example above.

In the example above we are going to send a command to the Rako controller (at 192.168.1.15) to execute a Scene 0 in Room 5 on Light 4.

Understanding what those numbers in the API above mean:

room=5
This is the ID of the room which your Rako devices are installed in.

ch=4
This is the channel which is how Rako refers to individual lights or RGB values.

sc=3
This is the scene ID.

“&”
This is a separator which is used to separate room, channel and scene values or IDs.

HELPFUL: Commonly used Scene IDs in Rako

  • Scene 0 = Off.
  • Scene 1-16 = Custom Scenes which you have made in Rako (lights at 10%, RGB value etc).

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 Rako API is great because it is super simple.

To test your API, open a web browser and enter the full API in the URL window and hit enter.

Screenshot 2023-05-11 at 11.55.56

Testing your Rako API is as easy as entering it into your favourite browser and hitting enter. If the Rako device does what you expected it to then you’re good to enter it into uOS.

If the Rako 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 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.

Update MHUB or Zone Processor Firmware Utility

Please read the instructions (included in the .zip file) carefully before using this software.

In most cases the core system firmware for your device will not require updating. Most updates for uOS or MHUB-OS can be downloaded from our cloud via the uControl app. This update utility is designed to update low-level firmware and should be carried out carefully.

Download Update Utility

Please contact us to confirm if your system requires an update and to request your update file.

Resolving MHUB-OS “Critical Error”

IMG_1329

If you notice that uControl has stopped responding or your control system is no longer controlling your MHUB or HDA device and you see a screen similar to the one above when you visit MHUB-OS’ IP address then it is likely that a core file within MHUB has become corrupted or is missing.

Generally, this error affects systems that are on very early versions of MHUB-OS, usually versions 7 or lower (at the time of writing 8.15+ is considered stable). On systems that are already on 8+ it is possible to restore the system sucessfully from a backup but earlier ones will need a HDA technician to check your system to identify the damaged system file and repair it.

If your system is out of warranty then there is a charge of 1 unit for this repair. Please contact HDANYWHERE first to arrange a technician slot.

Using Sky Q and MHUB on maximum video and audio settings

If you have a Sky Q 4K capable box and 4k capable displays this support post will guide you through getting the most out of your setup when using HDA systems.

Does my HDA system support Sky Q maximum output

You will need to confirm if your system is capable of passing the signal from your Sky box. Only the following systems are supported -

  1. MHUB PRO 2.0
  2. MHUB S
  3. MHUB U systems running MHUB-OS version 8.26 or greater

If your system isn’t listed above it may still support Sky Q at 4K, however, HDR will not be supported.

Configuring the MHUB System

You may need to do some minor configuration on the MHUB to get the most out of the Sky Q. To do this you will need to adjust the MHUB’s EDID settings for the input where the Sky is connected. Where possible we would recommend copying the EDID from your display. To configure EDID settings follow this guide – EDID Settings

Setting Sky Q to output 4K 10 bit

After setting the EDID on your MHUB you will then need to set the output of the Sky Q system. To do this Press the HOME button and scroll down to settings. Then in the settings menu scroll down to SETUP, then AUDIO VISUAL.

The first option will be Picture resolution, use the D-Pad and select 2160 [UHD]. You will then get onscreen instructions to select either 10-bit or 8-bit colour. Select 10-bit colour, then confirm everything is fine by following the onscreen instructions. You can also check out Sky’s guide here – Changing Resolution

There is a timer to confirm the picture is fine, if it expires before you can confirm simply press LEFT and ENTER after selecting 10-bit colour whilst the screen is still black.

Setting Sky Q to output Dolby Atmos Audio

to get Dolby Atmos from your sky box you need to change the Audio settings. These are located in the same menu as the video settings above. Scroll down to DIGITAL AUDIO OUTPUT HDMI. The setting required is ‘Dolby Digital Plus’.

Please be aware if any display cannot handle a 4K output and decode Dolby Digital Plus you may get no video and audio. If this happens you may have to adjust these settings.

1

2

3

4

5

6

7

Resetting your system

DO NOT RESET YOUR SYSTEM IF YOU DO NOT KNOW WHAT YOUR HDA DEVICE DOES:
Your HDA hardware is an integrated system and very similar to a central heating boiler.
It maybe controlling your AV sources, displays, speakers, lights etc. If you reset your system and you do not know how to restore it yourself then it could render your AV unusable.

Is your system managed by a HDA Pro Installer?

If your system has been built and serviced by a HDA Pro Installer then please contact them first before resetting your device. This is especially important if they are servicing your system. If you proceed with a system reset then your HDA Pro can reserve the right to charge a call out fee to restore your system to a working state.

Resetting your system

If you are already connected to a HDA system:
uControl menu (top left menu icon) > Settings Cog (bottom left) > Utilities > Reset

1-2-con

If you are not connected to any system:
uControl Splash Screen > Advanced > Utilities > Reset

1-2-ncon

Tapping on reset will not work. You will need to tap the reset button 10 times in order to unlock the reset process. Follow instructions inside the app to continue with the system reset.

Setting up Apple Hey Siri

Siri Shortcuts & HDANYWHERE.

With any Apple device along with an MHUB or Zone Prossesor you can use Apple “Hey Siri” and our API to send commands to uControl/uOS to control virtually any display, source inputs plus lighting control.

Below you will find a step by step how-to guide.

 

Unable to get HDR through MHUB or XTND to TV / Projector

If your MHUB is marked with “TPC” then it is capable of passing a HDR picture to your display. There are a number of reasons why HDR may not be fed through your HDA device. This support post aims to troubleshoot the most common reasons and how to resolve them.

Important: there are different versions of HDR, make sure your display supports the format your source is outputting!
There are multiple variants of HDR such as HLG, HDR10+ and Dolby Vision, please ensure your display supports the relevant HDR technology.

When connecting your HDR enabled source and display to a HDA system you may need to adjust some settings to get it to work.

  1. First, disconnect the source and connect it directly to your display. Do you get HDR?
  2. Ensure you are using High Speed HDMI Cables, this is important as long HDMI cables (over 5m) unless Active or Fibre will not work.
  3. Was you HDA device manufactured before 2019? Does it have TPC markings or 18G/18Gbps on it anywhere? If it doesn’t then there is a good chance that your HDA device does not support HDR as it was made before the specification was finalised.
  4. Does your HDA device support scaling? If so please ensure it is set to bypass.
  5. Copy or set a custom EDID directly from your display. This post explains how to copy EDID directly from your display.

What is HDMI 2.1 and should you need to worry about it?

HDMI Specification 2.1 or HDMI 2.1 is the most recent update of the HDMI specification (June 2021). The headline is that any source, display and everything in between must support HDMI 2.1 in order to take advantage of the higher video resolution support (8K up to 10K!) and faster refresh rates (4K up to 120fps and 8K at 60fps). If you have an older HDMI cable then it is unlikely that it will be able to handle the bandwidth that’s required for HDMI 2.1.

Do I need a 2.1 HDMI cable?

Answer

What do all those new HDMI acronyms mean?

  • eARC: Enhanced Audio Return Channel
    An update to standard ARC support. eARC allows audio to be ‘pulled’ from a display and carried down the HDMI cable to an audio device like a Sonos soundbar or an AVR. The biggest difference between ARC and eARC is that eARC is capable of pulling uncompressed audio formats like 5.1, 7.1 and high bitrate, object based audio such as Dolby Atmos and DTS:X.
  • VRR: Variable Refresh Rate
    VRR enables a gaming source such as a console or computer to deliver video frames as fast as it can, which in many cases is slower than the normal static refresh rate.
  • ALLM: Auto Low Latency Mode
    This is a new HDMI feature that allows a source (e.g. an gaming console such as the XBox One S or XBox One X) to direct all compatible components in the HDMI chain (things like AVRs and displays) to enter its a low-latency mode automatically. This allows the picture to be displayed with the lowest possible delay which is important in gaming.
  • QMS: Quick Media Switching
    Reduces the black screen you see when you change source. This works when resolutions are the same between HDMI connections.
  • QFT: Quick Frame Transport
    Another measure to transport data from the source to the display as fast as possible.

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.

First generation HDMI 1.4 spec UHD 4K, next-generation HDMI 2.0 spec UHD 4K and what integrators need to know.

An analysis of 4K Interim vs 4K Proper by Chris Pinder, Founder and MD of HDanywhere, June 2015.

blog2

4K is a complicated subject matter. 4K isn’t one format, it’s an umbrella term for many combinations of resolutions, frame rates and colours. Talking about 4K in too generalised a way is dangerous. When I discuss 4K with anyone, in as non-patronising a way as possible to simplify and aid understanding, I refer to ‘i’ and ‘p’, (like 1080i and 1080p) but my ‘i’ and ‘p’ doesn’t mean interlaced and progressive, I mean first generation 4K and next-generation 4K, or in other words  ’interim’ and ‘proper’. P could also quite easily stand for ‘premium’.

This is my take on the two-speed world of 4K UHD devices at the moment. It may be labelled and marketed as 4K, it may even support HDCP 2.2 – but is it 4Ki or 4Kp?

Proper 4K (4Kp) is next-generation HDMI 2.0 spec 4K, it’s what Ultra HD Blu-ray is and what premium 4K content will be. Ultra HD video refreshes at a smooth 60 frames per second in amazing 10-bit 4:2:0 colour (or if your display doesn’t support 10-bit) 8-bit 4:4:4 colour – basically hugely superior colours than what we have seen before over HDMI. 4Kp can also support HDR content and runs at very high 18Gbps data rates and, as a result, will require all new high-bandwidth HDMI 2.0a* spec electronics.  4Kp will also have HDCP 2.2 copy protection encrypting the content, which I’ll touch on later.

What is most important from integrator perspective is that single-cable HDBaseT DOES NOT carry 4Kp. It will only carry 4Ki because HDBaseT is max 10.2Gbps and 4Kp requires 18Gbps.

Most devices out there today labelled as ’4K’ do not support 4Kp, they only support 4Ki. And by most, I mean over 95%. But this is improving, more and more displays are coming out now that support HDMI 2.0 and have a 10-bit panel. Ultra HD Blu-ray is likely going to be the first 4Kp source device we see. So what is 4Ki?

Interim 4K (4Ki) runs at a 9G data rate (half that of 4Kp) and doesn’t necessarily require new HDMI 2.0 electronics. It will work on older HDMI 1.4 spec devices. It may or may not have HDCP 2.2 encryption. And colour-wise if it’s running at 60fps it can only be the lesser 8-bit 4:2:0 quarter colours. For 4:4:4 a lower 30fps refresh rate is used instead and smooth panning shots are sacrificed. 10-bit colour content just flatly isn’t supported full stop.

blog1

What is so important about colours?

4Kp/60 and 4Ki/60 if watched in black and white are EXACTLY the same. The same number of pixels wide and high, refreshing at 60 times per second, with the same pixel data for light and dark contrast. So no difference in sharpness, motion or contrast.

Where they differ is with a compromise on colour. The resolution of the colour layer that gets laid over the top of the black and white frame when combined to make the final image. With 8-bit 4:4:4 each pixel can choose a colour, whereas with 4:2:0 every 4 pixels have to share a single colour choice. Even though a cluster 4 pixels are sharing the same colour, the overlay of the black and white image creates different shades. The resulting 4:2:0 video content, although a lesser quality, is not as substantially different from 4:4:4 as you might think. In fact, when viewing the two from a couple of metres away, the human eye really struggles to differentiate them.

OK, now that you’re thinking is in tune with there being two primary types of 4K material and you understand the difference between the two.

You also NEED to be aware of a couple of associated meteors about to hit the AV side of the CI industry that relate to the facilitation of working 4K HDMI systems. (Remember HDMI is a system, NOT a cable) One is called ‘HDMI 2.0′ and the other is ‘HDCP 2.2′. The two meteors should really hit simultaneously, but not necessarily.

Meteor 1: HDMI 2.0 is the new twice-as-big digital pipeline to accommodate the higher data rates of proper 4K jumping from 9G to 18G bandwidth. Its not a new cable design, its new electronics at either end of the existing (short) HDMI cable we use. So that is new source devices (Ultra HD Blu-ray players for example) and new displays (10-bit SUHD Samsung panels for example). However for longish cable distances, say 3m and over, current passive cables may struggle with the higher data rates. We’ll begin to see some new breeds of HDMI cable types appear to solve this. Some will use integrated active/powered boosting chips and others are likely to be a copper/fibre hybrid cable. Existing long length HDMI cables, that may be buried in walls for example will be able to be utilised through the use of restorative dongles that can be placed at the start and end of the cable run. I expect to see this HDMI cable rescue/fixer market grow over the coming years sharply.

Meteor 2: HDCP 2.2 is the new 128 bit encryption designed to secure 4K content from being pirated. It is the same level of security encryption as credit card issuers use for internet transactions. Unless every device in the signal path is HDCP 2.2-capable, theoretically the content will not be shown. Source, matrix, AVR, balun, display, projector must all support HDCP 2.2. One weak link means black screen. The thing about HDCP 2.2 support is that it’s essential to ensure the best chance of displaying 4K content from your favourite content providers (i.e Hollywood and sports). The HDCP 2.2 event horizon will largely be determined by the release of Ultra-HD 4K Blu-ray and 4K content being delivered via our set-top-boxes.

Conclusion

In summary, until more next-gen 4Kp source devices, like Ultra HD Blu-ray, set-top-boxes, and media players are released we live in a kind of interim 4K limbo land, a phoney, interim 4K world with no proper, premium 4K content to enjoy. In addition to this, more displays with HDMI 2.0, HDCP 2.2 and 10-bit panels need to be released so that users can take full advantage of the advancements in picture quality offered by 4Kp. Month-on-month this situation improves.

From an integrator perspective, quite rightly there is a lot of emphasis currently on HDCP 2.2 support within matrixes. But even when HDCP 2.2 compliant, single-cable HDBaseT is a bottleneck in many video distribution systems, which will result in premium 4K content video quality being downgraded when distributed. There is a quality compromise currently in order to deliver a distributed solution over a single network cable.

SIDELINE RED HERRING: What about 4K streaming like Netflix?

Well it’s not 4Kp and it’s not 4Ki… It’s dynamically compressed, streamed 4K content using AVC H.264 and HEVC H.265 codecs with varying quality from home to home according primarily to the speed and quality of their network. For the purposes of this article, I am talking about uncompressed 4K content.

More info here: http://www.dailytech.com/Netflix+to+Stream+House+of+Cards+in+4K+via+HEVC+H265+Compression/article33962.htm

 

Picture loss/dropout on one or more displays 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.