Difference between revisions of "MyHome"
Line 42: | Line 42: | ||
|- | |- | ||
|} | |} | ||
+ | |||
+ | |rowspan="2"|gui | ||
+ | |rowspan="2"|true | ||
+ | |true | ||
+ | |enables automatic support of Web GUI objects to show the status of the system and intercept control buttons | ||
+ | |- | ||
+ | |false | ||
+ | |disables support for the Web GUI | ||
+ | |- | ||
=== Note on temperature control units === | === Note on temperature control units === |
Revision as of 14:12, 28 February 2014
MyHome is a proprietary bus system for home automation developed by BTicino. HSYCO fully integrates with MyHome using the OpenWebNet (OWN) protocol.
HSYCO supports all MyHome devices and features that the OWN protocol officially supports, including lighting, automation, scenes, AUX and CEN addressing, the temperature control unit and burglar alarm unit.
The bus architecture can be arranged as a single bus or with a riser and several local busses.
Contents
- 1 Communication
- 2 Gateway Configuration
- 3 L4686SDK Module
- 4 HSYCO Configuration
- 5 The Device Configuration Database
- 6 Datapoints
- 6.1 Gateway Module
- 6.2 Scenario Modules
- 6.3 Lighting: on/off Modules
- 6.4 Lighting: Dimmer Modules
- 6.5 Automation: Inter-locking Modules
- 6.6 Temperature Control: Central Unit
- 6.7 Temperature Control: Zones
- 6.8 Burglar Alarm: Main Panel
- 6.9 Burglar Alarm: Zones and Technical (aux)
- 6.10 Auxiliary Addresses
- 6.11 CEN Modules
- 6.12 CENPLUS Modules
- 6.13 F421 Load Control Unit
- 7 User Interface
- 8 Release Notes
Communication
HSYCO supports the Ethernet IP connection to MyHome through IP-based OWN gateways, including the F452, F453, F454, F453AV, MH200 and MH200N.
HSYCO also supports the L4686SDK module through an USB connection and an associated virtual serial port.
Gateway Configuration
The OWN gateway must be configured to allow open OWN connections from the IP address assigned to the HSYCO server.
L4686SDK Module
The L4686SDK interface module is connected to HSYCO using a USB cable.
The operating system creates a virtual serial port; its name depends on your HSYCO server configuration, and should be ttyUSB0 if there are no other devices connected to the USB ports.
You could also use the ftdi-n-n.n alias, that is unique for each physical USB port on the server. In this case, you should also list the full device name in the CommPortsList parameter.
L4686SDK Limitations
- L4686SDK firmware version 1.20.0 or later is required
- Not all protocol frames are supported. The I/O server has been tested with the following functions: scenarios, lights, automation, temperature control, AUX and CEN plus
- Check the L4686SDK documentation to know which functions are actually supported, also based on the L4686SDK firmware version
- The clock read and sync functions are not supported
- HSYCO only support the L4686SDK module on a single main bus; private raiser buses are not supported
- the USB connection cable should never be unplugged during normal operations. If the cable is unplugged, HSYCO will not be able to restore the connection to the L4686SDK until it is manually restarted.
HSYCO Configuration
Options
ID | Default | Values | Description |
---|
|rowspan="2"|gui |rowspan="2"|true |true |enables automatic support of Web GUI objects to show the status of the system and intercept control buttons |- |false |disables support for the Web GUI |-
Note on temperature control units
The 4695 four zone temperature control unit uses a zone address for the control unit itself. This address has to be marked as a special address in the tempzones parameter, enclosing it in round brackets.
For example:
tempZones=(32);33
defines a central unit having address 32, and an additional zone with address 33.
The MyHome I/O Server supports only one central unit for each SCS riser bus.
myhome.ini
The myhome.ini file is a specific configuration file located in the main directory (same directory as hsyco.ini or hsyco.jar).
This file is optional. It is only used to assign friendly names to the burglar alarm zones and technical alarms, so that these names are used in the GUI log and the security.log files.
If you have multiple My Home gateways with multiple burglar alarm panels, the parameters need to be defined for each system, using unique ids, according to the following table:
ID | Description |
---|---|
security.zone.<n> | the friendly name for burglar alarm zone <n> |
security.aux.<n> | the friendly name for burglar alarm technical alarm <n> |
The myhome.ini is automatically detected at start-up and automatically reloaded whenever it is modified.
For example, the following myhome.ini file is used to define a few friendly names of two distinct My Home systems:
mh1.security.zone.1.name=entrance mh1.security.zone.2.name=lobby mh1.security.aux.1.name=flooding mh2.security.zone.3.name=windows mh2.security.zone.5.name=driveway
The Device Configuration Database
Datapoints
Gateway Module
ID | Value | R/W | Description |
---|
Scenario Modules
ID | Value | R/W | Description |
---|
Lighting: on/off Modules
ID | Value | R/W | Description |
---|
Lighting: Dimmer Modules
ID | Value | R/W | Description |
---|
Automation: Inter-locking Modules
ID | Value | R/W | Description |
---|
Temperature Control: Central Unit
ID | Value | R/W | Description |
---|
Temperature Control: Zones
ID | Value | R/W | Description |
---|
Burglar Alarm: Main Panel
ID | Value | R/W | Description |
---|
Burglar Alarm: Zones and Technical (aux)
ID | Value | R/W | Description |
---|
Auxiliary Addresses
ID | Value | R/W | Description |
---|
CEN Modules
ID | Value | R/W | Description |
---|
CENPLUS Modules
ID | Value | R/W | Description |
---|
F421 Load Control Unit
ID | Value | R/W | Description |
---|
User Interface
Temperature Control Unit
UISET Actions
USER Commands
ID | Attribute | Set to |
---|
Name | Param | Action |
---|
Temperature Zones
Zone unlock
Name | Param | Action |
---|
Burglar Alarm Unit
UISET Actions
USER Commands
Because the MyHome burglar alarm panel cannot be directly controlled via OpenWebNet commands, there are no standard control objects for this system.
Release Notes
3.3.0
- added support of the L4686SDK interface module
3.2.2
- clock read and sync are now based on local time
3.2.1
- improved handling of connection errors
3.2.0
- new clock datapoint to read the gateway’s internal clock and set it to HSYCO's time
3.0.0
- initial release
ID | Attribute | Set to |
---|