This chapter describes how to setup a bTicino MyHome domotics system.
Communication with a bTicino MyHome system requires an OpenWebNet gateway. This is a component that acts as a gateway between your ip network, and the local bus.
Examples of gateways are
bTicino F452
bTicino F454
bTicino MH200
Some years ago, bTicino was bought by Legrand. The same components are
available under the Legrand brand, but with different part number.
Please check their respective websites :
Here, we will discuss the setup of the MyHome system using a MH200 component.
Before you can send commands from your IP network, the MH200 component
needs to be configured. The first configuration will have to be done
using a RS232 connector (usb programmation cable 3559, see My home usb programming cable for pc 3559 for a picture).
BTicino has chosen a rather strange password policy. Their own tools
make a connection using a password. However, the password protocol is
not publicly documented.
They do allow to specify one or more ip ranges, from which you can
communicate with the gateway
without password.
MyURemote makes use of the second option, so we need to setup the MH200 to accept commands from our MyURemote app.
In the left menu, select Ethernet
In the right panel, you need to enter the network data of the MH200 component.
Use a static ip address for the MH200
component and for any component and device involved in MyURemote. It may
be necessary to configure your dhcp server to use a different range of
ip addresses.
Select the Authentication
menu entry in the left panel, and define a new password that you will
need to use when connecting via Ethernet. The password is shown in plain
text, so no screenshot !
Select IP address enabling mode in the left panel
You need to define a range of ip addresses that are allowed to connect to the MH200 without
a password. This range needs to include all devices (smartphones,
tables, PC's) from which you want to run MyURemote. However, keep a
(small) range of ip addresses for which you do need a password. You will need to select an ip addres from this disabled range if you want to use the TiMH200 software on the network.
Again, if your smartphones, tables and PC's get their ip address throug
dhcp, make sure that the dhcp server uses a range that lies within the range of enabled ip addresses for the MH200.
To send a configuration to the MH200 device, click Download. To load the current configuration from the MH200 device to your project, click Upload.
The first time, you will have use a Serial connection, as the device won't have an ip address.
From then on, you can select Ethernet. Be sure to do this from a PC with an ip address outside the range of enabled ip addresses, see above. Temporarily change the ip address, if necessary.
We have chosen a Serial connection, we now have to select the port
Leave the seletion to Autodetect, and click Continue
You can use the TiMH200 software to create scenarios for your MyHome system. This has nothing to do with MyURemote, but a short how to is presented here.
Click the Scenarios
entry in the left menu. In the right panel, a single line is shown. On
the far right of this line, a button becomes visible when you hover your
mouse over this line. Click this button to open the Scenario Editor.
This name is always uppercase, and does not allow spaces and special characters.
An example of a scenario is shown
here. You can select from different families of components. When a
family is selected, the available objects are shown in the second row.
The tool is too versatile to document in a couple of screenshots. For
more information, see the TiMH200 manual.
Every component (actuator, …) has an address on the bus. This address is hard configured in the device, please talk to your MyHome installer for the list of addresses.
Be sure to do this from a PC with an ip address outside the range of enabled ip addresses, see above. Temporarily change the ip address, if necessary.
The protocol is documented on Wikipedia.
To communicate with an OpenWebNet device, you send commands over a socket.
A command to change the status of a component, looks like
*WHO*WHAT*WHERE##
WHO specifies the type of component, e.g. 1 for Lights, 2 for Shutters, …
WHAT specifies the target status, e.g. 0 for Light Off, 1 for Light On, and other values for shutters and other component types
WHERE is the address of the light or the shutter on the local bus. The address can vary from 0 to 99.
Some examples
Put light with address 31 on | *1*1*31## |
Put light with address 31 off | *1*0*31## |
Move shutter with address 81 up | *2*1*81## |
Move shutter with address 81 down | *2*2*81## |
Stop moving shutter with address 81 | *2*0*81## |
You can test this, from a PC with an ip address within the range of enabled ip addresses (see above).
On linux
echo "*1*1*31##" | netcat <ip address> 20000
with <ip address> the ip address of the OpenWebNet gateway.
Or, if you have telnet on your PC
telnet 192.168.0.103 20000
Trying 192.168.0.103...
Connected to 192.168.0.103.
Escape character is '^]'.
*#*1##
Now enter the command
*1*1*31##
This should put on the light on address 31.
The full communication is repeated here.
Trying 192.168.0.103...
Connected to 192.168.0.103.
Escape character is '^]'.
*#*1##*1*1*31##
*#*1##Connection closed by foreign host.
See Sample 6