If you see a HDANYWHERE or third party device marked with “uControl inside” then it contains our control system inside it. You can find out what it can do by visiting uControl’s website here.

Comparing AV and Full versions of uControl inside

Some devices are marked “AV” where others are “Full”. This is determined by the operating system found on the device. The “full” implementation of uControl can be found in devices which have uControl OS (uOS) inside. “AV” means that the system is running MHUB-OS (MOS) and control capability is restricted to AV only or the devices that are directly connected to the MHUB system.

Full

• Control over sources, AVRs, displays and projectors (IR)
• Control over sources, AVRs, displays and projectors (IP/CEC)
• IP control over lighting, blinds, shades, PDUs, relays and more See all here
• uControl app, Alexa, Watch support
• uControl Remote
• Super Sequences, Functions and Scheduling

AV

• Control over sources, AVRs, displays and projectors (IR)
• uControl app, Alexa, Watch support
• uControl Remote*
• Sequences and Scheduling

Upgrading an older MHUB to support Full uControl

It may be possible to update your MHUB’s control capabilities by adding a uControl Zone Processor to manage your system instead. Not all models are supported so we recommend contacting us to confirm the level of support first.

*Requires a Zone Processor to be added to the system to upgrade to Full uControl capabilities.

This guide explains how to use Lutrons API protocol to control QS Standalone, RadioRA2, Quantum, Athena, HomeWorks QS, myRoom plus from Lutrons devices.

What this guide will cover:

1. How to control Lutron lights in your home.
2. How to add that API into uOS.
3. QS Standalone, RadioRA2, Quantum, Athena, HomeWorks QS, myRoom plus.

Important: you must have the IP addresses first

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

Important: This guide assumes that you are familiar with Lutron and know how to use their lighting infrastructure and that your Lutron system is operational before integrating into uOS.

What a Telnet Lutron command looks like

See “Testing your API’s” for more information on Telnet.

Understanding what the variables 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, Lutron’s method is a little different as it needs to be done over Telnet in command prompt.

To test your commands, open up command prompt on your laptop or PC and enter telnet 192.168.1.15 23

Remember, your IP address will be different, you must use the Lutron gateway IP address for this, the port is 23.

You now need to wait for it to connect which may take a few minutes, then you will be asked to login. The username is lutron, and the password is integration. You will now be able to test your commands in the terminal. Observe the device you are trying to control, and see if your commands changes the outcome.

• Download command examples to make your integration easier.

Using a MAC?

If you are using a MAC you can use Netcat to test your API command. To do so open your terminal and enter nc 192.168.1.15 23

Wait for it to connect and then you will be prompted to login. The username is lutron and the password is integration.

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.

This guide explains how to pull data from the SilentGliss API so you can control it directly from 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

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.

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.

This guide explains how to pull data from KNX’s protocol so you can control it directly from 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

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:

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.

• infoBefore You Begin
• descriptionStep 1 – Getting Data
• constructionStep 2 – Build Function

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.

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

Please note: this guide covers how to execute a command for a Shelly light, if you are using a different device the same logic applies, you only need to change the parameters. Please find the link to Shelly’s API document below for commands relating to different devices.

What this guide will cover:

1. How to control Shelly lighting in your home.
2. How to add that API into uOS.

Important: you must have the IP addresses first

There are a few ways you can get the IP address if your Shelly device:

1. Use a network scanner app like Fing to find Shelly on your network.
2. Log into your wireless router and look for Shelly in the DHCP table.

What a typical Shelly command looks like

This only shows the logic of a Shelly command, you may be controlling a relay and therefore need to use different parameters. There will be a link at the bottom which will take you to Shelly’s API documentation where you can find all their codes.

Testing your APIs

You can test your Shelly command in the URL to see if it works. Make sure to include http:// for it to work properly.

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

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.

WiFi on Zone Processor Setup Guide

This guide will walk you through the process of changing your Zone Processor (ZP) device’s network connection from a wired Ethernet setup to a wireless (WiFi) setup.
This process involves three main phases:

1. Initial Setup: Configuring the device while it’s connected via Ethernet.
2. Temporary AP Mode: Using the device’s own Access Point to connect to it directly.
3. Final WiFi Mode: Connecting the device to your building’s main WiFi network.

Part 1: Initial Wired Setup

Before you can configure the WiFi, the ZP device must first be set up on your network using an Ethernet cable.

1. Connect the ZP device directly to your router or network switch using an Ethernet cable.
2. Power on the device.
3. On a computer connected to the same network, you will need to find the ZP’s current IP address.
   Note: You can typically find this by using the uControl app or a network scanner.
4. Open a web browser and type that IP address into the address bar to access the device’s web interface (GUI).

Part 2: Switch to Access Point (AP) Mode

Next, you will temporarily turn the ZP device into its own wireless hotspot.

1. In the ZP’s web interface, navigate to the “Network” section.
2. Find the “Device Mode” setting.
3. Change the mode from Ethernet to Access Point.
4. Save the settings.

Part 3: Connect to the ZP’s Temporary Network

Your computer will lose connection to the device when it restarts. You must now connect to the new temporary network it is broadcasting.

1. On your computer or mobile device, open your WiFi settings.
2. Look for a new network name (SSID) broadcast by the ZP device. It starts with HDA-ZP (Example: HDA-ZP5-146D).

1. Connect to this network. You will be prompted for a password.
   Password: hdanywhere
2. Your device is now connected directly to the ZP, not to your main network.

Part 4: Switch to WiFi

Now that you are connected to the ZP’s temporary network, you will give it your main WiFi network’s details.

1. Open a web browser.
2. In the address bar, type: 192.168.100.1
   This is the ZP’s default IP address when it is in Access Point mode.
3. Once the web interface loads, navigate to the “Network” section again.
4. Change the “Device Mode” from Access Point to WiFi.
5. Save the settings.

1. Enter your WiFi Network and password then Save the settings again. The device will disconnect you from its temporary network.

Part 5: Locate Your Device on WiFi

Once the ZP device reboots, it will be connected to your network via WiFi. It will have a new IP address assigned by your main router.

You must now find this new IP address to access the device:

• Using the App: The simplest method is to use the uControl app, which has a built-in network scanner to find the device.
• Using Your Router: You can log back into your router’s administration page and check the “DHCP Client List” for the ZP device to see its new IP.
• Using a Network Scanner: You can use a third-party application (like Fing on mobile or Angry IP Scanner on a desktop) to scan your network and locate the ZP’s new IP address.

Once you have the new IP address, you can use it to access the ZP’s web interface as normal. Your device is now successfully connected via WiFi.

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.