Forum

<p>Subject: Home + Project auto-assigns area-0 addresses that cannot be addressed via OpenWebNet (F460 + MH200)</p><p> </p><p>Hello,</p><p> </p><p>My MyHOME installation uses an F460 (firmware 2.0.18, managed with Home + Project / Home + Control) plus an MH200 as OpenWebNet gateway for a local home-automation integration. I hit a reproducible addressing problem and would appreciate advice.</p><p> </p><p>PROBLEM</p><p>Home + Project automatically assigns light points in area 0. Through an OpenWebNet gateway these points cannot be addressed individually: the address is interpreted as an area command.</p><p> </p><p>FINDINGS</p><p>1. Home + Project export:</p><p>   – Terrace heater: Device Id 00E59491, A:0 PL:2 I:0, PUL: yes</p><p>   – Same module 00E59491 has its other outputs at A:7 PL:2, A:7 PL:3, A:7 PL:4</p><p>   – Other area-0 objects: A:0 PL:1, PL:4, PL:5 (I:0), A:0 PL:1 (I:1), eight DALI channels A:0 PL:2-9 (I:1), one dimmer at A:00 PL:10 (I:1)</p><p> </p><p>2. Via the MH200 (OpenWebNet command session):</p><p>   – General status request *#1*0##: the actuator answers *1*1*2## / *1*0*2##</p><p>   – Command *1*1*2##: executed as an area command, points 21-28 switch on; the heater does not react</p><p>   – *#1*02##: NACK</p><p>   – *#1*0002##: NACK</p><p> </p><p>3. Readdressing the output to A:7 PL:1 with MyHOME_Suite:</p><p>   – *#1*71## answers *1*0*71##; the point is now controllable via OpenWebNet</p><p>   – Home + Control / Home + Project can no longer control the object</p><p>   – After editing the object in Home + Project, the address is set back to A:0 PL:2. Reproducible.</p><p> </p><p>4. The F460 accepts an OPEN session (HMAC authentication succeeds) but answers NACK to every frame, including *#1*12## and *1*0*12##.</p><p> </p><p>QUESTIONS</p><p>1. Can Home + Project be prevented from auto-assigning area-0 addresses, or made to keep a manually assigned address (e.g. A:7 PL:1) when an object is edited?</p><p>2. Which OpenWebNet gateway (MH201, MH202, F461, other) can address area-0 light points (A:0 PL:x and A:00 PL:10) individually, and with which WHERE notation?</p><p>3. Can the F460 accept commands from third-party software at all?</p><p> </p><p>I can provide the full export and bus logs.</p><p> </p><p>Thank you,</p><p>Peter</p>

Hello Peter,

I opened an internal support ticket. I’ll tell you once I know more

Have a good day,

Leslie – Community Manager

Here is their answer :

Regarding your installation, using an MH200 as an OpenWebNet gateway together with an F460 managed through Home + Project / Home + Control is the correct setup for third-party integration.

The F460 itself cannot be used as an OpenWebNet gateway. There are internal restrictions that prevent it from accepting OpenWebNet commands from third-party software.

Addressing assigned by Home + Project

Home + Project assigns addresses progressively, starting from Area 0, Point-to-Point address 1 (A=0, PL=1), then A=0, PL=2, and so on, up to A=10, PL=15.

This addressing rule cannot be changed within Home + Project.

From your description, your system includes an F422A. This device is normally used in larger installations, when the standard number of available addresses is not sufficient.

The F422A extends the SCS addressing structure. For example, two devices installed on different branches of an F422A may have the same SCS address, such as A=0, PL=5, but they are differentiated by their level address:

• Devices connected to the IN branch have level address 0.
• Devices connected to the OUT branch have level address 1.

For this reason, the position of the OpenWebNet gateway is very important. Standard OpenWebNet commands can be used to control lights located on the same branch as the gateway. To control devices located on a different branch, extended frames must be used.

Different frames are required depending on whether the command is intended for point-to-point control, area control, general control, or group control. General and group commands are sent to all branches.

General status request

Regarding the general status request:

*#1*0##

and the reply:

*1*1*2##

*1*0*2##

This does not appear to be a correct response to a general status request. It is likely that an area command was transmitted at the same time.

When sending *#1*0##, you should receive a status response for each light. Please repeat the test and check the messages received.

Readdressing through MyHOME_Suite

It is not possible to modify device settings using MyHOME_Suite on an installation configured through Home + Project.

Changing an address through MyHOME_Suite creates a mismatch with the configuration database stored in the F460. Therefore, when the object is subsequently edited in Home + Project, its address is automatically restored according to the Home + Project addressing rules.

In addition, if you change the address of devices installed on the OUT branch of an F422A, the address acquisition procedure must be run again. Since the F422A does not have a button to start this procedure, it can only be performed through the Home + Project application.

Direct communication with the F460

Although the F460 accepts an OPEN session and HMAC authentication, it cannot be used as an OpenWebNet gateway.

Therefore, it will return NACK responses to OpenWebNet frames sent by third-party software, including frames such as:

*#1*12##

*1*0*12##

Other answers to your questions

1. Is there a way to prevent Home + Project from automatically assigning Area-0 addresses, or to preserve a manually assigned address after editing an object?

No. Home + Project automatically assigns addresses according to its progressive addressing rules, and this behaviour cannot be modified. Manual changes made through MyHOME_Suite cannot be preserved.

2. Which OpenWebNet gateways can individually address Area-0 light points, and which WHERE notation should be used?

The gateway must be positioned correctly within the F422A branch structure. Standard OpenWebNet frames can control devices located on the same branch as the gateway, while extended frames are required for devices located on other branches.

Please refer to the OpenWebNet documentation for the specific supported frames and WHERE syntax for your gateway model and topology.

3. Can the F460 accept OpenWebNet commands from third-party software?

No. The F460 cannot be used as an OpenWebNet gateway. It can communicate only with the Home + Control application.

Have a good day,

Leslie – Community Manager