Skip to content

PowerView® KNX integration manual Hub Gen 1

IMPORTANT

Below procedure can only be applied by using a PowerView® Hub Gen 1!

This guide will explain step-by-step how to integrate a PowerView® network into an existing KNX system. The following instruction will show you how to:

  • Install and program the KNX to RS-232 interface module
  • Correctly set up an prepare your PowerView® network
  • Activate PowerView® scenes from the KNX network

1. Hardware overview

Connecting your PowerView® network to a KNX network requires you to have the following hardware.

PowerView® Hub

KNX-RS232 interface

HT-18 power supply 18VDC

Serial cable

2. Hardware installation

Activating PowerView® scenes, correctly set up inside the App, from the KNX network is only possible with the installation of additional hardware. We explain in detail which components are needed and how to make the physical connections.

2.1 Preparing the serial cable

The serial cable (article 17.0317.1858), to make the connection from the PowerView® Hub to the KNX network, needs some preparation.

2.1.1

Cut the serial cable at the DB9 connector.

2.1.2

Strip the end of the cable about 4cm.

3 wires will become visible:

  • brown

  • red

  • black

2.1.3

Strip the end of the wires for about 5mm.

2.2. Preparing the power cable

The power supply 18VDC (article 17.0343.0000), to power the KNX-RS232 interface, needs some preparation.

2.2.1

Cut the DC wires at the female DC plug.

2.2.2

Strip the end of both wires for about 5mm.

2.3. Installing the KNX serial interface

For making the connection to the KNX network, and extra piece of hardware is needed.

We have opted to use a KNX-RS232 bidirectional communication interface from the company Zennio®. For all technical information, we refer to the product web page.

2.3.1

Disconnect the 4-pin connector from the device.

2.3.2

Take the serial cable your prepared and connect the brown wire on terminal A, the red wire on terminal B

Do not connect the black wire yet!

2.3.3

Take the prepared HT-18 power supply and connect the grey (solid) wire on the minus (-) terminal, the white/grey (dotted) wire on the plus (+) terminal.

Do not tighten the minus (-) screw yet!

2.3.4

Take the black wire from the serial cable and connect together with the grey wire from the HT-18 power supply on the minus (-) terminal!

2.3.5

Locate the KNX bus connector on the device.

2.3.6

Connect the device to the local KNX network.

Strip the black and red wires of the KNX cable and connect to the device.

2.3.7

Put the 4-pin connector back into the device.

2.3.8

Connect the other end of the serial cable to the serial port of the PowerView® Hub.

2.3.9

Put the power plug into a power socket.

2.3.10

Hardware installation is done.

3. PowerView® Hub IP address

It is important you have correctly set up your PowerView® network:

  • Your PowerView® blinds are installed, limits are set or calibrated

  • Your PowerView® Hub is installed correctly

  • Your PowerView® blinds are discovered in the App

  • You have created all your PowerView® scenes

By default, when the PowerView® Hub is connected to a home router on the Local Area Network (LAN), the DHCP server will give the Hub a random IP address. In most cases this will be in the range of:

192.168.0.100 - 192.168.0.255

When making the connection from the PowerView® network to KNX, the Hub's IP address has to be set to a fixed IP address. The fixed IP address makes sure that the KNX network can always find the PowerView® Hub, even after a power failure occurs.

We explain in detail how to do.

3.1. Looking up your Hub's IP/MAC address

3.1.1

Open the PowerView® App on your mobile iOS or Android device.

Make sure your mobile device is connected to your local network.

3.1.2

Press the horizontal lines at the top left corner to open the dashboard.

3.1.3

Select your Hub name to go into its settings menu.

In our sample, the Hub is named Home

3.1.4

Press the info button.

3.1.5

Select Hub info.

3.1.6

Make a note of the Hub's IP Address and MAC address.

We will require this information later on when setting the fixed IP address inside the router's settings.

3.1.7

Close the PowerView® App.

3.2. Home router settings

Once we have noted down the Hub's current ('unfixed') IP address and MAD address, we can assign a fixed IP address for the Hub by changing the IP address assignment of the router to the Hub.

In our sample, we have noted:

IP address : 192.168.0.100

MAC address : 00:26:74:ff:73:88

Next up, we have to log into the router and change some settings.

IMPORTANT

The procedure can be different depending on the brand of the home router.

Please refer to the home router's manual for more information.

3.2.1

  • Open an internet browser.
    e.g. use Safari on an Apple® iPad

Make sure your device is connected to the home router!

  • Put in the address/search bar, the router's IP address and hit Go.
    The first 3 numbers of the router's IP address are the same as the IP address of the Hub.

The last number is always 1.

  • Result: 192.168.0.1

3.2.2

  • The login screen of the router will appear.

  • Put in the admin username and passwordand hit the Login button.
    By default, a (new) router often uses a standard username and password (e.g. admin or 1234).
    We strongly advise to change the default password, if needed.

Consult your router's manual how-to-do.

  • Result: User: admin
    Password: password

3.2.3

  • Search for the DHCP Settings page and select it.

  • Check the START and END IP address range and make a note.
    You can only choose an IP address within this range and assign it as a fixed IP address for the Hub.

Do not change the START and END IP address range unless you know what you're doing!

  • Result: Start IP Address: 192.168.0.100
    End IP Address: 192.168.0.199

3.2.4

  • Search for the DHCP Client List page and select it.

  • The MAC and IP address of the Hub should be visible in the list.

Hit the Refresh button if the MAC and IP address cannot be found.

  • Result: ALL GOOD!

3.2.5

  • Search for the Address Reservation page and select it.

  • Select the Add New... button.

3.2.6

  • Put in the Hub's MAC Address and desired Reserved IP Address.

  • Hit the Save button.

In this sample, we have choosen 192.168.0.105 to be the Hub's new IP address.

  • Result: MAC Address: 00-26-74-ff-73-88
    Reserved IP Address: 192.168.0.105

3.2.7

  • Hit the click here link. You will be redirected to a Reboot page.

  • Hit the Reboot button.

  • Result: Restarting...

4. PowerView® scenes configuration

4.1. Scenes overview

In our example, we have made the room

  • Kitchen

Within this room, the scenes

  • Morning

  • Noon

  • Evening

were created.

If we want to activate a particular scene with the KNX automation system, we have to retrieve the scene information within this room.

4.1.1

  • Open an internet browser.

Make sure your device is connected to the home router!

  • Put in the address/search bar, the Hub's IP address followed by /api/scenes/ an hit Go.
    Use the same Hub's IP address as defined in step 3.2.6

In our sample, this is 192.168.0.105

  • Result: 192.168.0.105/api/scenes/

4.1.2

Select, copy & paste all displayed text to a text editor.
e.g. use the Notes app on an Apple® iPad

4.1.3

  • Open the text editor and go to the copied text.

  • Rearrange the text as seen below to get a better sight on the information displayed.
    We seperate the sceneIds and sceneData information.

In our samples, the 3 scenes (Morning; Noon; Evening) correspond to one of the following scene ID's:
- 64869
- 45131
- 3273

  • The corresponding scene name can be read out within the SceneData section.

4.1.4

  • The scene name is base64 encoded and for pratical reasons has to be converted to unicode utf-8 readable text.

The base64 encoded text can be recognized by the letters and figures between the quotes ending each with ==.

  • Use this translator webpage to convert the base64 encoded text.

  • Select, copy & paste each base64 encoded text to the translator and take a note of the result.

4.1.5

In our example, following scene IDs correspond to:

  • 64869: Morning

  • 45131: Noon

  • 3273: Evening

IMPORTANT

Changing or deleting any PowerView® scenes within the app will change Scene id's.

Therefore, the procedure explained in this chapter has to be redone.

4.2. Serial API

To be able to activate PowerView® scenes trough the KNX system, these communication specifics apply:

  • Each request to the Hub begins with a ? followed by a two-character ASCII command. Each successful response from the Hub begins with a ! followed by the same two ASCII characters.

  • All messages are terminated with a carriage return (0x0D). From here on, a carriage return is designated as <cr>.

  • Scene and Room identifiers are transmitted as an ASCII string representing an integer value ranging from zero (0) to 65535. Indexes, used for retrieving information about individual Rooms and Scenes, are also transmitted as an ASCII string representing an integer.

  • Names of scenes and Rooms are always located as the last parameter of a response and may include spaces.

The format to execute a scene or list of scenes send to the Hub:

?SE < scene ID1 > < scene ID2 > < scene ID3 > ... < scene ID28 > < cr >

In our example, we get:

Scene name

Scene id

Scene execution request

Morning

64869

?SE 64869

Noon

45131

?SE 45131

Evening

3273

?SE 3273


Note

It is strongly recommended to make a table overview, as seen above, of all configured scenes that have to be activated by the KNX system.

4.2. ETS® software configuration

The KNX automation system is set up using the ETS® software. The configuration and commissioning is done by a certified KNX installer. For more information, visit the official KNX web page.

Note

In this instruction, we will use ETS®

4.2.1

  • Download the Application Program of the Zennio® ZN1RX-SKXOPEN RS232 bidirectional communication interface.

  • Go to the product product web page, download and save the the Application Program for either ETS3, ETS4 or ETS5.

4.2.2

  • Open your ETS® software, select your project and import the Application Program of the Zennio® ZN1RX-SKXOPEN.

  • Add the product to the right location (e.g. Room 1) and assign its individual address (e.g. 1.1.5).

4.2.3


  • Select the Parameter tab of the product.

  • In the Main Setup screen, change the default settings to:

Velocity [baud]: 9600
Parity: No parity
Time between frames to be sent [x0.1 sec]: 1
Reception complete mode: End-frame byte
End-frame byte: 0D
Time out [msec]: 15

4.2.4

  • Select the Parameter groups screen and enable 1 or more groups.

  • Each group contains 12 objects. The number of objects needed corresponds to the number of PowerView® scenes you want to activate via the KNX system.

In our sample, we want to activate 3 PowerView® scenes (Morning, Noon and Evening), meaning we only have to enable Group 1.

4.2.5

  • Select the Group #(with # = 1, 2, 3 or 4) screen which appears.

  • From the drop-down list of each Object, select the proper Control mode.

In our sample, we select Send frame if object is 1 because we want the KNX system to activate a PowerView® scene when the object is activated sending a 1 to the group object we will create later on.

4.2.6

  • For each PowerView® scene, the PowerView® Scene execution request has to be converted first to Hexadecimal notation and filled in in the Frame to send window of each Object.

Take note of the Scene execution request strings in chapter 4.2. Serial API.

  • Use this translator webpage to convert the Scene execution request strings.

  • Select, copy and paste each Scene execution request string to the translator and take a note of the result.

In our sample, we copy and paste the Scene execution request from the Morning scene and hit the Convert! button to translate.
The corresponding hexadecimal string is: 3F5345203634383639.

In our example, we get:

Scene name

Scene id

Scene execution request

Scene execution request (hexadecimal)

Morning

64869

?SE 64869

3F5345203634383639

Noon

45131

?SE 45131

3F5345203435313331

Evening

3273

?SE 3273

3F53452033323733

4.2.7

Copy and paste the hexadecimal strings in the corresponding Frame to send window of each group object.

4.2.8

Optionally, give each group object a name by filling in the Description field.

4.2.9

  • Assign each group object to a group address.

In our sample, we made 3 group addresses (MORNING, NOON and EVENING) and drag & dropped each group object to its proper group address.
In our case, PowerView® scene Morning will be activated by pushing a button in the KNX system.

4.2.10

You are ready to activate your PowerView® scenes within the KNX automation system!

Important notice

Hunter Douglas Europe B.V. and its affiliates (Hunter Douglas) reserve the right to make corrections, enhancements, improvements and other changes to its products and services, and to discontinue any product or service. Buyers should obtain the latest relevant information before placing orders and should verify that such information is current and complete. All products (also referred to herein as "components") are sold subject to Hunter Douglas’ terms and conditions of sale supplied at the time of order acknowledgment. Hunter Douglas warrants performance of its components to the specifications applicable at the time of sale, in accordance with its standard warranty terms. Testing and other quality control techniques are used to the extent Hunter Douglas deems necessary to support this warranty. Except where mandated by applicable law, testing of all parameters of each component is not necessarily performed. Hunter Douglas assumes no liability for applications assistance or the design of Buyers' products. Buyers are responsible for their products, applications and interfaces using Hunter Douglas components. To minimize the risks associated with Buyers' products and applications, Buyers should provide adequate design and operating safeguards. Hunter Douglas does not warrant or represent that any license, either express or implied, is granted under any patent right, copyright, mask work right, or other intellectual property right relating to any combination, machine, or process in which Hunter Douglas components or services are used. Information published by Hunter Douglas regarding third-party products or services does not constitute a license to use such products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property of the third party, or a license from Hunter Douglas under the patents or other intellectual property of Hunter Douglas. Reproduction of Hunter Douglas information in Hunter Douglas data sheets is permissible only if reproduction is without alteration and is accompanied by all associated warranties, conditions, limitations, and notices. Hunter Douglas is not responsible or liable for any altered documentation. Information of third parties may be subject to additional restrictions. Resale of Hunter Douglas components or services with statements different from or beyond the parameters stated by Hunter Douglas for that component or service voids all express and any implied warranties for the associated Hunter Douglas component or service and is an unfair and deceptive business practice. Hunter Douglas is not responsible or liable for any such statements. Buyers acknowledge and agree that they are solely responsible for compliance with all legal, regulatory and safety-related requirements concerning its products, and any use of Hunter Douglas components in its applications, notwithstanding any applications-related information or support that may be provided by Hunter Douglas. Buyers represent and agree that they have all the necessary expertise to create and implement safeguards which anticipate dangerous consequences of failures, monitor failures and their consequences, lessen the likelihood of failures that might cause harm and take appropriate remedial actions. Buyers fully indemnify Hunter Douglas and its representatives against any damages arising out of the use of any Hunter Douglas components in safety-critical applications.


document version: 1.1 | generated: 2019-05-20 01:54:48