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.

If you find yourself encountering issues with the picture (either poor quality or no picture) then the following list of common problems and solutions will help you diagnose the problem.

Firmware – Ensure your devices are on the most up-to-date firmware. Check the manufacturer’s website and use the menu settings on any internet-connectable device, such as sources, sinks, displays, projectors, AVRS, etc etc.

Power – Check that both the MHUB and the receivers are fully powered. The front panel of the MHUB should be illuminated* and the power light on the receiver should be on. If the receiver isn’t powered try an alternate power supply from another receiver that you know works. Alternatively, if you’re using the USB power supplies double check that the USB port you are using is supplying the appropriate current.

Is your transmission distance too long? – If you have a power light but the lock light isn’t illuminated this can indicate an issue with the signal strength. The maximum transmission distance for the mHub 2K range is 50m in best-case scenarios and 100m for the MHUB 4k Range. The transmission distance can be reduced by several factors, most commonly wall plates, patch panels and stranded patch leads can significantly reduce signal strength and potentially reduce the maximum distance the matrix can transmit signal. Whenever possible you should try to use a straight point to point connection to guarantee maximum distance.

Resolution – Check that you are using compatible resolutions between your source devices and displays, in particular you should be looking for situations where a TV is perhaps older than the rest of your displays and doesn’t support the same video formats (for instance it only supports 720p) Try reducing the resolution on your source devices and see if this fixes the issue. Also, if reducing the resolution causes the picture to appear again this can point to an issue with the bandwidth which can be addressed by reducing the transmission distance.

Snow/Sparkly picture – This is most often seen when the MHUB is failing to fully establish a connection with the receiver. Your first step should be to use another working location to verify the integrity of both the receiver and output on the matrix. Once you are happy both the receiver and MHUB output are working you should take a look at all your cables. Check that your RJ45 connectors are properly terminated to 568B standards and try swapping out the HDMI cables for ones from working locations.

* – with the MHUB family of products, If the unit has been idle for 5 minutes the panel may have gone into power-saving mode

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:

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.

You may not need to use CEC or you have been prompted to disable it by support as it can cause conflicts between displays and external devices like soundbars, causing audio pass-through issues.

The examples in the guide focus on disabling CEC, however, to re-enable it replace “Off” with “On”.

There are 3 ways to disable CEC:

1. Sending a URL command
2. Hercules
3. Nc

Please note

The command variable is x meaning you put the Output port here when you want to disable it. To disable Output A put 1, to disable Output B put 2 and so on. To disable all Output ports +1 to however many HDBaseT ports there are. For example if you have a 4-way matrix input 5 to disable all ports.

Using an MHUB S (8+8×8)? Make sure to only send HDMI command – CecOutxOff!

---

Hercules SETUP utility
useful serial port terminal (RS-485 or RS-232terminal) , UDP/IP terminal and TCP/IP Client Server terminal. Produced by www.HW-group.com.

If you don’t have Hercules already download it using the link above, we can use it to send our CEC command to our device. Once installed run the software. Hercules only requires the command itself so you don’t need to include 192.168.0.149/api/instr?cmd= like you do in URL.

You should see a response in black below Received/Sent data saying CEC has been disabled if done correctly.

---

---