This guide explains how to control your NETIO PDU from uOS, uControl App and uControl Remote.

NETIO API

What this guide will cover:

1. Understanding switching outputs, batches, ports and their status.
2. How to create a NETIO 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 NETIO first

You can get the IP address of your NETIO by:

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

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

NETIO 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 NETIO API looks like

In the example above we are going to send a command to the Netio PDU (at 192.168.1.15) to execute a power switch turning output 1 to ON.

Understanding what those variables in the API above mean:

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

If you get a response in the web browser similar to the one below, and you heard the NETIO PDU tick to signify a switch, then you’re good to take this command and put it into uOS:

• Download command examples to make your integration easier.

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.

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

What this guide will cover:

1. How to gather information about your lights and use this to set their states.
2. How to create a Philips Hue API so that you can control any light in the property.
3. How to add that API into uOS

Important: you must have a developers account first

Before you can access the full Philips Hue API you must have made a Philips Hue Developer account.

Retrieving the IP address

There are a few ways you can get the IP address of your Philips Hue device:

1. Use a network scanner app like Fing to find Philips Hue on your network.
2. Use Philips Hue broker server discovery process.
3. Log into your wireless router and look for Philips Hue in the DHCP table.
4. The Philips Hue app – Start the Hue app and push link to connect to the bridge. Use the app to find the bridge and try controlling lights to ensure that everything is working. Then, go to the settings menu in the app, go to Hue Bridges, select your bridge and then the IP address of the bridge will be revealed.

Generating an access token

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

Firstly, we need to make an access token so you can make changes to the lighting.

To start this process, head over to the web browser API by typing in the command below with the IP address specific to your Philips Hue bridge.

Once loaded, you should see a grey “CLIP API Debugger” extension pop up, you then need to type /api/newdeveloper and click GET. You will get a reply in the command response which will state you’re an unauthorised user.

We now need to use the randomly generated username that the bridge creates for you. To incorporate this, do the following:

1. Start off by typing /api into the URL.
2. Then go ahead and type {"devicetype":"my_hue_app#iphone peter"} into the message body, we have used Peter as our example but your username will most likely be different so change it accordingly.
3. Lastly, select your method as POST.

After clicking POST you should get an error response telling you to press the link button, make sure to go press it on the bridge and then click POST again on the API. This is a security step which stops other people from accessing your lights.

You should then be given your access code which will look similar to the one below, make sure you hold onto this as it will be needed for all commands moving forward.

Now we have our acces token and you’re familiar with using the API, we can start controlling our lights. Watch the slideshow to see how to do execute different commands and what they do.

Testing your APIs

As Philips API commands require a command for the URL and also the message body, you will have to test if they’re working on the Clip API Debugger program. If they work, they are ready to be added into uOS!

• Download command examples to make your integration easier.

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.

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.

Important: The tail end connects into your MHUB system

These can be purchased here: https://hdanywhere.com/products/accessories

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.

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.

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.

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.

• Guide 1 – MHUB 100A models & MHUB U (4×1+1) 40
• Guide 2 – MHUB U (4×3+1) 40 & (8×6+2) 40
• Guide 3 – Older MHUB models (micro USB on front)

• Serial to USB A cable.
• USB to Serial adaptor or a PC with a 9-pin serial COM port (see below for image)
• Hercules Software – Hercules SETUP utility – Produced by www.HW-group.com.

Steps

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



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 (included in your MHUB packaging)
• USB to Serial adaptor or a PC with a 9-pin serial COM port (see below for image)
• Hercules Software – Hercules SETUP utility – Produced by www.HW-group.com.

Steps

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



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