LinuxMCE - User contributions [en]

ISY994i

2015-01-07T03:27:03Z

Mkbrown69: Updates to documentation, and for future driver updates.

[[Category: Automation]]
[[Category: Insteon]]
{{versioninfo|1004Status=Basic Functions Working|1004UpdatedDate=10 January 2014|1004UpdatedBy=Michael Brown|1204Status=Working, In Development|1204UpdatedDate=10 January 2014|1204UpdatedBy=Michael Brown}}

More info to come. Like the driver itself, this page is a work in progress. Please stand by... Another update will hopefully land in January 2015.

The ISY994i is a home automation controller from Universal Devices. It has an embedded processor, runs it's own real-time OS, is network connected, and manages the various home automation devices as a stand-alone controller. Configuring and administering the ISY is done via a Java application "console", which is used to manage devices, create programs and scheduled events, upgrade the device firmware, and add functionality via purchased license keys. It exposes it's functionality via well-developed application programming interfaces (API's).

The LMCE ISY driver is being written using the Ruby GSD Device interface, and leverages the ISY's API to expose the managed devices and controls to LMCE. The driver has been written with the assumption that the ISY "owns" the connected devices, and exposes them to LMCE for integration and control as an external controller. As the API's develop, some capabilities to configure the ISY from LMCE may be created. Until then, the expectation is that all home automation device configuration and management will occur using the Universal Devices Java admin console, and that the configuration and capabilities will be exposed to LMCE for use via it's capabilities.

'''ISY Models'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Model
! IR Support
! Max. Devices/Scenes
! Max. Programs
|-
| ISY994i
| No
| 256
| 300
|-
|-
| ISY994i/IR
| Yes
| 256
| 300
|-
| ISY994i PRO
| No
| 1024
| 1000
|-
|-
| ISY994i/IR
| Yes
| 1024
| 1000
|-
|}

Zigbee devices have the 'Z' device suffix on the model number (e.g. ISY994iZ/IR PRO). The Z-wave device is has just passed the alpha testing phase, and will be going into beta testing soon. Support for the Z-wave radio will likely be added when it's released (and I have the opportunity to get one), as there's some pretty cool Z-wave sensors available...

[http://www.universal-devices.com/residential/isy994i-series/ Manufacturer Web page at UniversalDevices.com]

The LMCE driver utilizes template # 2276.

'''NOTE''': The Driver has a dependency on the libmysql-ruby and libmysql-ruby1.8 packages, which are not currently part of the driver's automatic installation. For now, you will need to manually install the ruby-mysql packages using the command "sudo apt-get install libmysql-ruby1.8 libmysql-ruby" and then reload the router. This will be addressed in the next update of the driver, along with better scene controls and weather module integrations.

'''ISY Hardware Interface support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Insteon
| Support for Insteon PLM's including X10 transmission/reception
| Working
|-
| UPB
| Support for UPB Modems
| N/A
|-
| Zigbee
| Support for the optional Zigbee model/radio.
| N/A
|-
| Z-wave
| Support for the optional Z-wave model/radio.
| N/A
|-
|}

The ISY series supports optional (paid) upgrades which can enable additional functionality in the ISY device. It allows home automation users to start off small, and add additional functionality later as their environment grows or their needs change. For example, a non-pro model can be upgraded by purchasing a Pro upgrade license key. Some hardware upgrades can be done in the field by purchasing the hardware directly from Universal Devices web store. The following table shows the LMCE driver support for the various add-on software modules. Features marked N/A have not been implemented yet.

'''ISY module support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Climate Module
| The ISY HAMweather Climate Module
| In progress, pending 12.04
|-
| Networking Module
| The ISY networking module
| N/A
|-
| X10 Module
| The ISY X10 module which incorporates X10 devices into the device tree. Note: if you want to be able to control X10 devices from LMCE or any Orbiter, or receive events for X10 devices, you will need this module license.
| Working, Tested
|-
| Electricity Module
| The ISY electricity monitoring module for Brultech devices
| N/A
|-
| Irrigation Module
| The irrigation module used in conjunction with the Climate (HAMweather) module.
| N/A
|-
| ELK Module
| The ISY <-> Elk M1 Security Panel interface module.
| N/A
|}

----

'''Using the ISY Driver'''
The ISY driver is configured for auto-discovery using DHCP. When the ISY requests an IP addresses, LinuxMCE will automatically add the device template. You will need to login to the LinuxMCE Administration Page, and change the username and password to match those configured in the ISY. The template defaults to admin:admin. Afterwards, you will need to reload the router.

When the DCErouter reloads, the driver will establish a connection to the ISY. It will create child devices of the ISY in LinuxMCE, by reading all configured /managed devices from the ISY, and creating a corresponding child in LMCE. You will need to reload the router in order to use the devices from LMCE. Similarly, scenes (groups) will be downloaded and appropriate child devices created. After all devices and scenes have been recognized, you can then edit the devices in LMCE to set the room, floor plan ID (icons used in the Floor plan view in Orbiter), etc. when you are complete, reload the router again. Your devices and Insteon scenes are now available to use in LMCE scenarios.

'''Troubleshooting'''

If you're having problems, the logs are the best place to look to see what's going on. There are two logs: the <dev#>_Generic _Serial_Device.log has to do with LMCE's interaction with the driver, and <dev#>_ISY-994i-GSD.log, which logs the driver's interaction with the ISY. Both are located in /var/log/pluto.

Mine are 189_Generic_Serial_Device.log and 189_ISY-994i-GSD.log (as an example).

By default, the <dev#>_ISY-994i-GSD.log logs a minimal amount of the interaction between the driver and the ISY. That could give you hints as to what is happening when. To get more in-depth information as to what's going on, you'll need to enable Debug mode. In the WebAdmin, go to Generic Serial Devices, and check the box next to debug in the device info screen. Reload the router to restart the driver with verbose logging.

ISY994i

2014-03-04T03:06:45Z

Mkbrown69:

[[Category: Automation]]
[[Category: Insteon]]
{{versioninfo|1004Status=Basic Functions Working|1004UpdatedDate=10 January 2014|1004UpdatedBy=Michael Brown|1204Status=Working, In Development|1204UpdatedDate=10 January 2014|1204UpdatedBy=Michael Brown}}

More info to come. Like the driver itself, this page is a work in progress. Please stand by...

The ISY994i is a home automation controller from Universal Devices. It has an embedded processor, runs it's own real-time OS, is network connected, and manages the various home automation devices as a stand-alone controller. Configuring and administering the ISY is done via a Java application "console", which is used to manage devices, create programs and scheduled events, upgrade the device firmware, and add functionality via purchased license keys. It exposes it's functionality via well-developed application programming interfaces (API's).

The LMCE ISY driver is being written using the Ruby GSD Device interface, and leverages the ISY's API to expose the managed devices and controls to LMCE. The driver has been written with the assumption that the ISY "owns" the connected devices, and exposes them to LMCE for integration and control as an external controller. As the API's develop, some capabilities to configure the ISY from LMCE may be created. Until then, the expectation is that all home automation device configuration and management will occur using the Universal Devices Java admin console, and that the configuration and capabilities will be exposed to LMCE for use via it's capabilities.

'''ISY Models'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Model
! IR Support
! Max. Devices/Scenes
! Max. Programs
|-
| ISY994i
| No
| 256
| 300
|-
|-
| ISY994i/IR
| Yes
| 256
| 300
|-
| ISY994i PRO
| No
| 1024
| 1000
|-
|-
| ISY994i/IR
| Yes
| 1024
| 1000
|-
|}

Zigbee devices have the 'Z' device suffix on the model number (e.g. ISY994iZ/IR PRO). The Z-wave device is has just passed the alpha testing phase, and will be going into beta testing soon. Support for the Z-wave radio will likely be added when it's released (and I have the opportunity to get one), as there's some pretty cool Z-wave sensors available...

[http://www.universal-devices.com/residential/isy994i-series/ Manufacturer Web page at UniversalDevices.com]

The LMCE driver utilizes template # 2276.

'''NOTE''': The Driver has a dependency on the libmysql-ruby and libmysql-ruby1.8 packages, which are not currently part of the driver's automatic installation. For now, you will need to manually install the ruby-mysql packages using the command "sudo apt-get install libmysql-ruby1.8 libmysql-ruby" and then reload the router.

'''ISY Hardware Interface support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Insteon
| Support for Insteon PLM's including X10 transmission/reception
| Working
|-
| UPB
| Support for UPB Modems
| N/A
|-
| Zigbee
| Support for the optional Zigbee model/radio.
| N/A
|-
| Z-wave
| Support for the optional Z-wave model/radio.
| N/A
|-
|}

The ISY series supports optional (paid) upgrades which can enable additional functionality in the ISY device. It allows home automation users to start off small, and add additional functionality later as their environment grows or their needs change. For example, a non-pro model can be upgraded by purchasing a Pro upgrade license key. Some hardware upgrades can be done in the field by purchasing the hardware directly from Universal Devices web store. The following table shows the LMCE driver support for the various add-on software modules. Features marked N/A have not been implemented yet.

'''ISY module support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Climate Module
| The ISY Weatherbug Climate Module
| In progress, pending 12.04
|-
| Networking Module
| The ISY networking module
| N/A
|-
| X10 Module
| The ISY X10 module which incorporates X10 devices into the device tree. Note: if you want to be able to control X10 devices from LMCE or any Orbiter, or receive events for X10 devices, you will need this module license.
| Working, Tested
|-
| Electricity Module
| The ISY electricity monitoring module for Brultech devices
| N/A
|-
| Irrigation Module
| The irrigation module used in conjunction with the Climate (Weatherbug) module.
| N/A
|-
| ELK Module
| The ISY <-> Elk M1 Security Panel interface module.
| N/A
|}

----

'''Using the ISY Driver'''
The ISY driver is configured for auto-discovery using DHCP. When it requests an IP addresses, LinuxMCE will automatically add the device template. You will need to login to the LinuxMCE Administration Page, and change the username and password to match those configured in the ISY. The template defaults to admin:admin. Afterwards, you will need to reload the router.

When the DCErouter reloads, the driver will establish a connection to the ISY. It will create child devices of the ISY in LinuxMCE, by reading all configured /managed devices from the ISY, and creating a corresponding child in LMCE. You will need to reload the router in order to use the devices from LMCE. Similarly, scenes (groups) will be downloaded and appropriate child devices created. After all devices and scenes have been recognized, you can then edit the devices in LMCE to set the room, floor plan ID (icons used in the Floor plan view in Orbiter), etc. when you are complete, reload the router again. Your devices and Insteon scenes are now available to use in LMCE scenarios.

'''Troubleshooting'''

If you're having problems, the logs are the best place to look to see what's going on. There are two logs: the <dev#>_Generic _Serial_Device.log has to do with LMCE's interaction with the driver, and <dev#>_ISY-994i-GSD.log, which logs the driver's interaction with the ISY. Both are located in /var/log/pluto.

Mine are 189_Generic_Serial_Device.log and 189_ISY-994i-GSD.log (as an example).

By default, the <dev#>_ISY-994i-GSD.log logs a minimal amount of the interaction between the driver and the ISY. That could give you hints as to what is happening when. To get more in-depth information as to what's going on, you'll need to enable Debug mode. In the WebAdmin, go to Generic Serial Devices, and check the box next to debug in the device info screen. Reload the router to restart the driver with verbose logging.

ISY994i

2014-03-04T03:05:09Z

Mkbrown69: Add troubleshooting info to the page.

[[Category: Automation]]
[[Category: Insteon]]
{{versioninfo|1004Status=Basic Functions Working|1004UpdatedDate=10 January 2014|1004UpdatedBy=Michael Brown|1204Status=Working, In Development|1204UpdatedDate=10 January 2014|1204UpdatedBy=Michael Brown}}

More info to come. Like the driver itself, this page is a work in progress. Please stand by...

The ISY994i is a home automation controller from Universal Devices. It has an embedded processor, runs it's own real-time OS, is network connected, and manages the various home automation devices as a stand-alone controller. Configuring and administering the ISY is done via a Java application "console", which is used to manage devices, create programs and scheduled events, upgrade the device firmware, and add functionality via purchased license keys. It exposes it's functionality via well-developed application programming interfaces (API's).

The LMCE ISY driver is being written using the Ruby GSD Device interface, and leverages the ISY's API to expose the managed devices and controls to LMCE. The driver has been written with the assumption that the ISY "owns" the connected devices, and exposes them to LMCE for integration and control as an external controller. As the API's develop, some capabilities to configure the ISY from LMCE may be created. Until then, the expectation is that all home automation device configuration and management will occur using the Universal Devices Java admin console, and that the configuration and capabilities will be exposed to LMCE for use via it's capabilities.

'''ISY Models'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Model
! IR Support
! Max. Devices/Scenes
! Max. Programs
|-
| ISY994i
| No
| 256
| 300
|-
|-
| ISY994i/IR
| Yes
| 256
| 300
|-
| ISY994i PRO
| No
| 1024
| 1000
|-
|-
| ISY994i/IR
| Yes
| 1024
| 1000
|-
|}

Zigbee devices have the 'Z' device suffix on the model number (e.g. ISY994iZ/IR PRO). The Z-wave device is has just passed the alpha testing phase, and will be going into beta testing soon. Support for the Z-wave radio will likely be added when it's released (and I have the opportunity to get one), as there's some pretty cool Z-wave sensors available...

[http://www.universal-devices.com/residential/isy994i-series/ Manufacturer Web page at UniversalDevices.com]

The LMCE driver utilizes template # 2276.

'''NOTE''': The Driver has a dependency on the libmysql-ruby and libmysql-ruby1.8 packages, which are not currently part of the driver's automatic installation. For now, you will need to manually install the ruby-mysql packages using the command "sudo apt-get install libmysql-ruby1.8 libmysql-ruby" and then reload the router.

'''ISY Hardware Interface support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Insteon
| Support for Insteon PLM's including X10 transmission/reception
| Working
|-
| UPB
| Support for UPB Modems
| N/A
|-
| Zigbee
| Support for the optional Zigbee model/radio.
| N/A
|-
| Z-wave
| Support for the optional Z-wave model/radio.
| N/A
|-
|}

The ISY series supports optional (paid) upgrades which can enable additional functionality in the ISY device. It allows home automation users to start off small, and add additional functionality later as their environment grows or their needs change. For example, a non-pro model can be upgraded by purchasing a Pro upgrade license key. Some hardware upgrades can be done in the field by purchasing the hardware directly from Universal Devices web store. The following table shows the LMCE driver support for the various add-on software modules. Features marked N/A have not been implemented yet.

'''ISY module support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Climate Module
| The ISY Weatherbug Climate Module
| In progress, pending 12.04
|-
| Networking Module
| The ISY networking module
| N/A
|-
| X10 Module
| The ISY X10 module which incorporates X10 devices into the device tree. Note: if you want to be able to control X10 devices from LMCE or any Orbiter, or receive events for X10 devices, you will need this module license.
| Working, Tested
|-
| Electricity Module
| The ISY electricity monitoring module for Brultech devices
| N/A
|-
| Irrigation Module
| The irrigation module used in conjunction with the Climate (Weatherbug) module.
| N/A
|-
| ELK Module
| The ISY <-> Elk M1 Security Panel interface module.
| N/A
|}

----

'''Using the ISY Driver'''
The ISY driver is configured for auto-discovery using DHCP. When it requests an IP addresses, LinuxMCE will automatically add the device template. You will need to login to the LinuxMCE Administration Page, and change the username and password to match those configured in the ISY. The template defaults to admin:admin. Afterwards, you will need to reload the router.

When the DCErouter reloads, the driver will establish a connection to the ISY. It will create child devices of the ISY in LinuxMCE, by reading all configured /managed devices from the ISY, and creating a corresponding child in LMCE. You will need to reload the router in order to use the devices from LMCE. Similarly, scenes (groups) will be downloaded and appropriate child devices created. After all devices and scenes have been recognized, you can then edit the devices in LMCE to set the room, floor plan ID (icons used in the Floor plan view in Orbiter), etc. when you are complete, reload the router again. Your devices and Insteon scenes are now available to use in LMCE scenarios.

'''Troubleshooting'''
If you're having problems, the logs are the best place to look to see what's going on. There are two logs: the <dev#>_Generic _Serial_Device.log has to do with LMCE's interaction with the driver, and <dev#>_ISY-994i-GSD.log, which logs the driver's interaction with the ISY. Both are located in /var/log/pluto.

Mine are 189_Generic_Serial_Device.log and 189_ISY-994i-GSD.log (as an example).

By default, the <dev#>_ISY-994i-GSD.log logs a minimal amount of the interaction between the driver and the ISY. That could give you hints as to what is happening when. To get more in-depth information as to what's going on, you'll need to enable Debug mode. In the WebAdmin, go to Generic Serial Devices, and check the box next to debug in the device info screen. Reload the router to restart the driver with verbose logging.

ISY994i

2014-01-11T05:12:24Z

Mkbrown69: Update to indicate the driver works in 12.04

[[Category: Automation]]
[[Category: Insteon]]
{{versioninfo|1004Status=Basic Functions Working|1004UpdatedDate=10 January 2014|1004UpdatedBy=Michael Brown|1204Status=Working, In Development|1204UpdatedDate=10 January 2014|1204UpdatedBy=Michael Brown}}

More info to come. Like the driver itself, this page is a work in progress. Please stand by...

The ISY994i is a home automation controller from Universal Devices. It has an embedded processor, runs it's own real-time OS, is network connected, and manages the various home automation devices as a stand-alone controller. Configuring and administering the ISY is done via a Java application "console", which is used to manage devices, create programs and scheduled events, upgrade the device firmware, and add functionality via purchased license keys. It exposes it's functionality via well-developed application programming interfaces (API's).

The LMCE ISY driver is being written using the Ruby GSD Device interface, and leverages the ISY's API to expose the managed devices and controls to LMCE. The driver has been written with the assumption that the ISY "owns" the connected devices, and exposes them to LMCE for integration and control as an external controller. As the API's develop, some capabilities to configure the ISY from LMCE may be created. Until then, the expectation is that all home automation device configuration and management will occur using the Universal Devices Java admin console, and that the configuration and capabilities will be exposed to LMCE for use via it's capabilities.

'''ISY Models'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Model
! IR Support
! Max. Devices/Scenes
! Max. Programs
|-
| ISY994i
| No
| 256
| 300
|-
|-
| ISY994i/IR
| Yes
| 256
| 300
|-
| ISY994i PRO
| No
| 1024
| 1000
|-
|-
| ISY994i/IR
| Yes
| 1024
| 1000
|-
|}

Zigbee devices have the 'Z' device suffix on the model number (e.g. ISY994iZ/IR PRO). The Z-wave device is has just passed the alpha testing phase, and will be going into beta testing soon. Support for the Z-wave radio will likely be added when it's released (and I have the opportunity to get one), as there's some pretty cool Z-wave sensors available...

[http://www.universal-devices.com/residential/isy994i-series/ Manufacturer Web page at UniversalDevices.com]

The LMCE driver utilizes template # 2276.

'''NOTE''': The Driver has a dependency on the libmysql-ruby and libmysql-ruby1.8 packages, which are not currently part of the driver's automatic installation. For now, you will need to manually install the ruby-mysql packages using the command "sudo apt-get install libmysql-ruby1.8 libmysql-ruby" and then reload the router.

'''ISY Hardware Interface support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Insteon
| Support for Insteon PLM's including X10 transmission/reception
| Working
|-
| UPB
| Support for UPB Modems
| N/A
|-
| Zigbee
| Support for the optional Zigbee model/radio.
| N/A
|-
| Z-wave
| Support for the optional Z-wave model/radio.
| N/A
|-
|}

The ISY series supports optional (paid) upgrades which can enable additional functionality in the ISY device. It allows home automation users to start off small, and add additional functionality later as their environment grows or their needs change. For example, a non-pro model can be upgraded by purchasing a Pro upgrade license key. Some hardware upgrades can be done in the field by purchasing the hardware directly from Universal Devices web store. The following table shows the LMCE driver support for the various add-on software modules. Features marked N/A have not been implemented yet.

'''ISY module support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Climate Module
| The ISY Weatherbug Climate Module
| In progress, pending 12.04
|-
| Networking Module
| The ISY networking module
| N/A
|-
| X10 Module
| The ISY X10 module which incorporates X10 devices into the device tree. Note: if you want to be able to control X10 devices from LMCE or any Orbiter, or receive events for X10 devices, you will need this module license.
| Working, Tested
|-
| Electricity Module
| The ISY electricity monitoring module for Brultech devices
| N/A
|-
| Irrigation Module
| The irrigation module used in conjunction with the Climate (Weatherbug) module.
| N/A
|-
| ELK Module
| The ISY <-> Elk M1 Security Panel interface module.
| N/A
|}

----

'''Using the ISY Driver'''
The ISY driver is configured for auto-discovery using DHCP. When it requests an IP addresses, LinuxMCE will automatically add the device template. You will need to login to the LinuxMCE Administration Page, and change the username and password to match those configured in the ISY. The template defaults to admin:admin. Afterwards, you will need to reload the router.

When the DCErouter reloads, the driver will establish a connection to the ISY. It will create child devices of the ISY in LinuxMCE, by reading all configured /managed devices from the ISY, and creating a corresponding child in LMCE. You will need to reload the router in order to use the devices from LMCE. Similarly, scenes (groups) will be downloaded and appropriate child devices created. After all devices and scenes have been recognized, you can then edit the devices in LMCE to set the room, floor plan ID (icons used in the Floor plan view in Orbiter), etc. when you are complete, reload the router again. Your devices and Insteon scenes are now available to use in LMCE scenerios.

ISY994i

2013-12-24T02:41:25Z

Mkbrown69:

[[Category: Automation]]
[[Category: Insteon]]
{{versioninfo|1004Status=In Development|1004UpdatedDate=6 December 2013|1004UpdatedBy=Michael Brown}}

More info to come. Like the driver itself, this page is a work in progress. Please stand by...

The ISY994i is a home automation controller from Universal Devices. It has an embedded processor, runs it's own real-time OS, is network connected, and manages the various home automation devices as a stand-alone controller. Configuring and administering the ISY is done via a Java application "console", which is used to manage devices, create programs and scheduled events, upgrade the device firmware, and add functionality via purchased license keys. It exposes it's functionality via well-developed application programming interfaces (API's).

The LMCE ISY driver is being written using the Ruby GSD Device interface, and leverages the ISY's API to expose the managed devices and controls to LMCE. The driver has been written with the assumption that the ISY "owns" the connected devices, and exposes them to LMCE for integration and control as an external controller. As the API's develop, some capabilities to configure the ISY from LMCE may be created. Until then, the expectation is that all home automation device configuration and management will occur using the Universal Devices Java admin console, and that the configuration and capabilities will be exposed to LMCE for use via it's capabilities.

'''ISY Models'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Model
! IR Support
! Max. Devices/Scenes
! Max. Programs
|-
| ISY994i
| No
| 256
| 300
|-
|-
| ISY994i/IR
| Yes
| 256
| 300
|-
| ISY994i PRO
| No
| 1024
| 1000
|-
|-
| ISY994i/IR
| Yes
| 1024
| 1000
|-
|}

Zigbee devices have the 'Z' device suffix on the model number (e.g. ISY994iZ/IR PRO). The Z-wave device is has just passed the alpha testing phase, and will be going into beta testing soon. Support for the Z-wave radio will likely be added when it's released (and I have the opportunity to get one), as there's some pretty cool Z-wave sensors available...

[http://www.universal-devices.com/residential/isy994i-series/ Manufacturer Web page at UniversalDevices.com]

The LMCE driver utilizes template # 2276.

NOTE: The Driver has a dependency on the libmysql-ruby and libmysql-ruby1.8 packages, which are not currently part of the driver's automatic installation. For now, you will need to manually install the ruby-mysql packages using the command "sudo apt-get install libmysql-ruby1.8 libmysql-ruby" and then reload the router.

'''ISY Hardware Interface support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Insteon
| Support for Insteon PLM's including X10 transmission/reception
| Working
|-
| UPB
| Support for UPB Modems
| N/A
|-
| Zigbee
| Support for the optional Zigbee model/radio.
| N/A
|-
| Z-wave
| Support for the optional Z-wave model/radio.
| N/A
|-
|}

The ISY series supports optional (paid) upgrades which can enable additional functionality in the ISY device. It allows home automation users to start off small, and add additional functionality later as their environment grows or their needs change. For example, a non-pro model can be upgraded by purchasing a Pro upgrade license key. Some hardware upgrades can be done in the field by purchasing the hardware directly from Universal Devices web store. The following table shows the LMCE driver support for the various add-on software modules. Features marked N/A have not been implemented yet.

'''ISY module support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Climate Module
| The ISY Weatherbug Climate Module
| In progress, pending 12.04
|-
| Networking Module
| The ISY networking module
| N/A
|-
| X10 Module
| The ISY X10 module which incorporates X10 devices into the device tree. Note: if you want to be able to control X10 devices from LMCE or any Orbiter, or receive events for X10 devices, you will need this module license.
| Working, Tested
|-
| Electricity Module
| The ISY electricity monitoring module for Brultech devices
| N/A
|-
| Irrigation Module
| The irrigation module used in conjunction with the Climate (Weatherbug) module.
| N/A
|-
| ELK Module
| The ISY <-> Elk M1 Security Panel interface module.
| N/A
|}

----

'''Using the ISY Driver'''
The ISY driver is configured for auto-discovery using DHCP. When it requests an IP addresses, LinuxMCE will automatically add the device template. You will need to login to the LinuxMCE Administration Page, and change the username and password to match those configured in the ISY. The template defaults to admin:admin. Afterwards, you will need to reload the router.

When the DCErouter reloads, the driver will establish a connection to the ISY. It will create child devices of the ISY in LinuxMCE, by reading all configured /managed devices from the ISY, and creating a corresponding child in LMCE. You will need to reload the router in order to use the devices from LMCE. Similarly, scenes (groups) will be downloaded and appropriate child devices created. After all devices and scenes have been recognized, you can then edit the devices in LMCE to set the room, floor plan ID (icons used in the Floor plan view in Orbiter), etc. when you are complete, reload the router again. Your devices and Insteon scenes are now available to use in LMCE scenerios.

ISY994i

2013-12-08T05:00:02Z

Mkbrown69: Correct Device template number.

[[Category: Automation]]
[[Category: Insteon]]
{{versioninfo|1004Status=In Development|1004UpdatedDate=6 December 2013|1004UpdatedBy=Michael Brown}}

More info to come. Like the driver itself, this page is a work in progress. Please stand by...

The ISY994i is a home automation controller from Universal Devices. It has an embedded processor, runs it's own real-time OS, is network connected, and manages the various home automation devices as a stand-alone controller. Configuring and administering the ISY is done via a Java application "console", which is used to manage devices, create programs and scheduled events, upgrade the device firmware, and add functionality via purchased license keys. It exposes it's functionality via well-developed application programming interfaces (API's).

The LMCE ISY driver is being written using the Ruby GSD Device interface, and leverages the ISY's API to expose the managed devices and controls to LMCE. The driver has been written with the assumption that the ISY "owns" the connected devices, and exposes them to LMCE for integration and control as an external controller. As the API's develop, some capabilities to configure the ISY from LMCE may be created. Until then, the expectation is that all home automation device configuration and management will occur using the Universal Devices Java admin console, and that the configuration and capabilities will be exposed to LMCE for use via it's capabilities.

'''ISY Models'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Model
! IR Support
! Max. Devices/Scenes
! Max. Programs
|-
| ISY994i
| No
| 256
| 300
|-
|-
| ISY994i/IR
| Yes
| 256
| 300
|-
| ISY994i PRO
| No
| 1024
| 1000
|-
|-
| ISY994i/IR
| Yes
| 1024
| 1000
|-
|}

Zigbee devices have the 'Z' device suffix on the model number (e.g. ISY994iZ/IR PRO). The Z-wave device is has just passed the alpha testing phase, and will be going into beta testing soon. Support for the Z-wave radio will likely be added when it's released (and I have the opportunity to get one), as there's some pretty cool Z-wave sensors available...

[http://www.universal-devices.com/residential/isy994i-series/ Manufacturer Web page at UniversalDevices.com]

The LMCE driver utilizes template # 2276.

'''ISY Hardware Interface support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Insteon
| Support for Insteon PLM's including X10 transmission/reception
| Working
|-
| UPB
| Support for UPB Modems
| N/A
|-
| Zigbee
| Support for the optional Zigbee model/radio.
| N/A
|-
| Z-wave
| Support for the optional Z-wave model/radio.
| N/A
|-
|}

The ISY series supports optional (paid) upgrades which can enable additional functionality in the ISY device. It allows home automation users to start off small, and add additional functionality later as their environment grows or their needs change. For example, a non-pro model can be upgraded by purchasing a Pro upgrade license key. Some hardware upgrades can be done in the field by purchasing the hardware directly from Universal Devices web store. The following table shows the LMCE driver support for the various add-on software modules. Features marked N/A have not been implemented yet.

'''ISY module support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Climate Module
| The ISY Weatherbug Climate Module
| In progress, pending 12.04
|-
| Networking Module
| The ISY networking module
| N/A
|-
| X10 Module
| The ISY X10 module which incorporates X10 devices into the device tree. Note: if you want to be able to control X10 devices from LMCE or any Orbiter, or receive events for X10 devices, you will need this module license.
| Working, Tested
|-
| Electricity Module
| The ISY electricity monitoring module for Brultech devices
| N/A
|-
| Irrigation Module
| The irrigation module used in conjunction with the Climate (Weatherbug) module.
| N/A
|-
| ELK Module
| The ISY <-> Elk M1 Security Panel interface module.
| N/A
|}

----

'''Using the ISY Driver'''
The ISY driver is configured for auto-discovery using DHCP. When it requests an IP addresses, LinuxMCE will automatically add the device template. You will need to login to the LinuxMCE Administration Page, and change the username and password to match those configured in the ISY. The template defaults to admin:admin. Afterwards, you will need to reload the router.

When the DCErouter reloads, the driver will establish a connection to the ISY. It will create child devices of the ISY in LinuxMCE, by reading all configured /managed devices from the ISY, and creating a corresponding child in LMCE. You will need to reload the router in order to use the devices from LMCE. Similarly, scenes (groups) will be downloaded and appropriate child devices created. After all devices and scenes have been recognized, you can then edit the devices in LMCE to set the room, floor plan ID (icons used in the Floor plan view in Orbiter), etc. when you are complete, reload the router again. Your devices and Insteon scenes are now available to use in LMCE scenerios.

ISY994i

2013-12-07T03:40:07Z

Mkbrown69: Update for device template number

[[Category: Automation]]
[[Category: Insteon]]
{{versioninfo|1004Status=In Development|1004UpdatedDate=6 December 2013|1004UpdatedBy=Michael Brown}}

More info to come. Like the driver itself, this page is a work in progress. Please stand by...

The ISY994i is a home automation controller from Universal Devices. It has an embedded processor, runs it's own real-time OS, is network connected, and manages the various home automation devices as a stand-alone controller. Configuring and administering the ISY is done via a Java application "console", which is used to manage devices, create programs and scheduled events, upgrade the device firmware, and add functionality via purchased license keys. It exposes it's functionality via well-developed application programming interfaces (API's).

The LMCE ISY driver is being written using the Ruby GSD Device interface, and leverages the ISY's API to expose the managed devices and controls to LMCE. The driver has been written with the assumption that the ISY "owns" the connected devices, and exposes them to LMCE for integration and control as an external controller. As the API's develop, some capabilities to configure the ISY from LMCE may be created. Until then, the expectation is that all home automation device configuration and management will occur using the Universal Devices Java admin console, and that the configuration and capabilities will be exposed to LMCE for use via it's capabilities.

'''ISY Models'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Model
! IR Support
! Max. Devices/Scenes
! Max. Programs
|-
| ISY994i
| No
| 256
| 300
|-
|-
| ISY994i/IR
| Yes
| 256
| 300
|-
| ISY994i PRO
| No
| 1024
| 1000
|-
|-
| ISY994i/IR
| Yes
| 1024
| 1000
|-
|}

Zigbee devices have the 'Z' device suffix on the model number (e.g. ISY994iZ/IR PRO). The Z-wave device is has just passed the alpha testing phase, and will be going into beta testing soon. Support for the Z-wave radio will likely be added when it's released (and I have the opportunity to get one), as there's some pretty cool Z-wave sensors available...

[http://www.universal-devices.com/residential/isy994i-series/ Manufacturer Web page at UniversalDevices.com]

The LMCE driver utilizes template # 2423.

'''ISY Hardware Interface support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Insteon
| Support for Insteon PLM's including X10 transmission/reception
| Working
|-
| UPB
| Support for UPB Modems
| N/A
|-
| Zigbee
| Support for the optional Zigbee model/radio.
| N/A
|-
| Z-wave
| Support for the optional Z-wave model/radio.
| N/A
|-
|}

The ISY series supports optional (paid) upgrades which can enable additional functionality in the ISY device. It allows home automation users to start off small, and add additional functionality later as their environment grows or their needs change. For example, a non-pro model can be upgraded by purchasing a Pro upgrade license key. Some hardware upgrades can be done in the field by purchasing the hardware directly from Universal Devices web store. The following table shows the LMCE driver support for the various add-on software modules. Features marked N/A have not been implemented yet.

'''ISY module support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Climate Module
| The ISY Weatherbug Climate Module
| In progress, pending 12.04
|-
| Networking Module
| The ISY networking module
| N/A
|-
| X10 Module
| The ISY X10 module which incorporates X10 devices into the device tree. Note: if you want to be able to control X10 devices from LMCE or any Orbiter, or receive events for X10 devices, you will need this module license.
| Working, Tested
|-
| Electricity Module
| The ISY electricity monitoring module for Brultech devices
| N/A
|-
| Irrigation Module
| The irrigation module used in conjunction with the Climate (Weatherbug) module.
| N/A
|-
| ELK Module
| The ISY <-> Elk M1 Security Panel interface module.
| N/A
|}

----

'''Using the ISY Driver'''
The ISY driver is configured for auto-discovery using DHCP. When it requests an IP addresses, LinuxMCE will automatically add the device template. You will need to login to the LinuxMCE Administration Page, and change the username and password to match those configured in the ISY. The template defaults to admin:admin. Afterwards, you will need to reload the router.

When the DCErouter reloads, the driver will establish a connection to the ISY. It will create child devices of the ISY in LinuxMCE, by reading all configured /managed devices from the ISY, and creating a corresponding child in LMCE. You will need to reload the router in order to use the devices from LMCE. Similarly, scenes (groups) will be downloaded and appropriate child devices created. After all devices and scenes have been recognized, you can then edit the devices in LMCE to set the room, floor plan ID (icons used in the Floor plan view in Orbiter), etc. when you are complete, reload the router again. Your devices and Insteon scenes are now available to use in LMCE scenerios.

ISY994i

2013-12-04T04:13:21Z

Mkbrown69: Update for X10 module info.

[[Category: Automation]]
[[Category: Insteon]]
{{versioninfo|1004Status=In Development|1004UpdatedDate=2nd December 2013|1004UpdatedBy=Michael Brown}}

More info to come. Like the driver itself, this page is a work in progress. Please stand by...

The ISY994i is a home automation controller from Universal Devices. It has an embedded processor, runs it's own real-time OS, is network connected, and manages the various home automation devices as a stand-alone controller. Configuring and administering the ISY is done via a Java application "console", which is used to manage devices, create programs and scheduled events, upgrade the device firmware, and add functionality via purchased license keys. It exposes it's functionality via well-developed application programming interfaces (API's).

The LMCE ISY driver is being written using the Ruby GSD Device interface, and leverages the ISY's API to expose the managed devices and controls to LMCE. The driver has been written with the assumption that the ISY "owns" the connected devices, and exposes them to LMCE for integration and control as an external controller. As the API's develop, some capabilities to configure the ISY from LMCE may be created. Until then, the expectation is that all home automation device configuration and management will occur using the Universal Devices Java admin console, and that the configuration and capabilities will be exposed to LMCE for use via it's capabilities.

'''ISY Models'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Model
! IR Support
! Max. Devices/Scenes
! Max. Programs
|-
| ISY994i
| No
| 256
| 300
|-
|-
| ISY994i/IR
| Yes
| 256
| 300
|-
| ISY994i PRO
| No
| 1024
| 1000
|-
|-
| ISY994i/IR
| Yes
| 1024
| 1000
|-
|}

Zigbee devices have the 'Z' device suffix on the model number (e.g. ISY994iZ/IR PRO). The Z-wave device is has just passed the alpha testing phase, and will be going into beta testing soon. Support for the Z-wave radio will likely be added when it's released (and I have the opportunity to get one), as there's some pretty cool Z-wave sensors available...

[http://www.universal-devices.com/residential/isy994i-series/ Manufacturer Web page at UniversalDevices.com]

The LMCE driver utilizes template # TBD.

'''ISY Hardware Interface support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Insteon
| Support for Insteon PLM's including X10 transmission/reception
| Working
|-
| UPB
| Support for UPB Modems
| N/A
|-
| Zigbee
| Support for the optional Zigbee model/radio.
| N/A
|-
| Z-wave
| Support for the optional Z-wave model/radio.
| N/A
|-
|}

The ISY series supports optional (paid) upgrades which can enable additional functionality in the ISY device. It allows home automation users to start off small, and add additional functionality later as their environment grows or their needs change. For example, a non-pro model can be upgraded by purchasing a Pro upgrade license key. Some hardware upgrades can be done in the field by purchasing the hardware directly from Universal Devices web store. The following table shows the LMCE driver support for the various add-on software modules. Features marked N/A have not been implemented yet.

'''ISY module support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Climate Module
| The ISY Weatherbug Climate Module
| In progress, pending 12.04
|-
| Networking Module
| The ISY networking module
| N/A
|-
| X10 Module
| The ISY X10 module which incorporates X10 devices into the device tree. Note: if you want to be able to control X10 devices from LMCE or any Orbiter, or receive events for X10 devices, you will need this module license.
| Working, Tested
|-
| Electricity Module
| The ISY electricity monitoring module for Brultech devices
| N/A
|-
| Irrigation Module
| The irrigation module used in conjunction with the Climate (Weatherbug) module.
| N/A
|-
| ELK Module
| The ISY <-> Elk M1 Security Panel interface module.
| N/A
|}

----

'''Using the ISY Driver'''
The ISY driver is configured for auto-discovery using DHCP. When it requests an IP addresses, LinuxMCE will automatically add the device template. You will need to login to the LinuxMCE Administration Page, and change the username and password to match those configured in the ISY. The template defaults to admin:admin. Afterwards, you will need to reload the router.

When the DCErouter reloads, the driver will establish a connection to the ISY. It will create child devices of the ISY in LinuxMCE, by reading all configured /managed devices from the ISY, and creating a corresponding child in LMCE. You will need to reload the router in order to use the devices from LMCE. Similarly, scenes (groups) will be downloaded and appropriate child devices created. After all devices and scenes have been recognized, you can then edit the devices in LMCE to set the room, floor plan ID (icons used in the Floor plan view in Orbiter), etc. when you are complete, reload the router again. Your devices and Insteon scenes are now available to use in LMCE scenerios.

Template:Versioninfo

2013-12-04T03:43:14Z

Mkbrown69: Update to include 1204

{| border="1" cellspacing="0" cellpadding="5" align="right"
! Version
! Status
! Date Updated
! Updated By
|-
| 710
| {{{710Status|Unknown}}}
| {{{710UpdatedDate|N/A}}}
| {{{710UpdatedBy|N/A}}}
|-
| 810
| {{{810Status|Unknown}}}
| {{{810UpdatedDate|N/A}}}
| {{{810UpdatedBy|N/A}}}
|-
| 1004
| {{{1004Status|Unknown}}}
| {{{1004UpdatedDate|N/A}}}
| {{{1004UpdatedBy|N/A}}}
|-
| 1204
| {{{1204Status|Unknown}}}
| {{{1204UpdatedDate|N/A}}}
| {{{1204UpdatedBy|N/A}}}
|-
|colspan="4" style="text-align: center;"|[[UsageTemplateVersionInfo|Usage Information]]
|}

ISY994i

2013-12-04T03:39:43Z

Mkbrown69: Minor update for feature status

[[Category: Automation]]
[[Category: Insteon]]
{{versioninfo|1004Status=In Development|1004UpdatedDate=2nd December 2013|1004UpdatedBy=Michael Brown}}

More info to come. Like the driver itself, this page is a work in progress. Please stand by...

The ISY994i is a home automation controller from Universal Devices. It has an embedded processor, runs it's own real-time OS, is network connected, and manages the various home automation devices as a stand-alone controller. Configuring and administering the ISY is done via a Java application "console", which is used to manage devices, create programs and scheduled events, upgrade the device firmware, and add functionality via purchased license keys. It exposes it's functionality via well-developed application programming interfaces (API's).

The LMCE ISY driver is being written using the Ruby GSD Device interface, and leverages the ISY's API to expose the managed devices and controls to LMCE. The driver has been written with the assumption that the ISY "owns" the connected devices, and exposes them to LMCE for integration and control as an external controller. As the API's develop, some capabilities to configure the ISY from LMCE may be created. Until then, the expectation is that all home automation device configuration and management will occur using the Universal Devices Java admin console, and that the configuration and capabilities will be exposed to LMCE for use via it's capabilities.

'''ISY Models'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Model
! IR Support
! Max. Devices/Scenes
! Max. Programs
|-
| ISY994i
| No
| 256
| 300
|-
|-
| ISY994i/IR
| Yes
| 256
| 300
|-
| ISY994i PRO
| No
| 1024
| 1000
|-
|-
| ISY994i/IR
| Yes
| 1024
| 1000
|-
|}

Zigbee devices have the 'Z' device suffix on the model number (e.g. ISY994iZ/IR PRO). The Z-wave device is has just passed the alpha testing phase, and will be going into beta testing soon. Support for the Z-wave radio will likely be added when it's released (and I have the opportunity to get one), as there's some pretty cool Z-wave sensors available...

[http://www.universal-devices.com/residential/isy994i-series/ Manufacturer Web page at UniversalDevices.com]

The LMCE driver utilizes template # TBD.

'''ISY Hardware Interface support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Insteon
| Support for Insteon PLM's including X10 transmission/reception
| Working
|-
| UPB
| Support for UPB Modems
| N/A
|-
| Zigbee
| Support for the optional Zigbee model/radio.
| N/A
|-
| Z-wave
| Support for the optional Z-wave model/radio.
| N/A
|-
|}

The ISY series supports optional (paid) upgrades which can enable additional functionality in the ISY device. It allows home automation users to start off small, and add additional functionality later as their environment grows or their needs change. For example, a non-pro model can be upgraded by purchasing a Pro upgrade license key. Some hardware upgrades can be done in the field by purchasing the hardware directly from Universal Devices web store. The following table shows the LMCE driver support for the various add-on software modules. Features marked N/A have not been implemented yet.

'''ISY module support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Climate Module
| The ISY Weatherbug Climate Module
| In progress, pending 12.04
|-
| Networking Module
| The ISY networking module
| N/A
|-
| X10 Module
| The ISY X10 module which incorporates X10 devices into the device tree.
| Working, Tested
|-
| Electricity Module
| The ISY electricity monitoring module for Brultech devices
| N/A
|-
| Irrigation Module
| The irrigation module used in conjunction with the Climate (Weatherbug) module.
| N/A
|-
| ELK Module
| The ISY <-> Elk M1 Security Panel interface module.
| N/A
|}

----

'''Using the ISY Driver'''
The ISY driver is configured for auto-discovery using DHCP. When it requests an IP addresses, LinuxMCE will automatically add the device template. You will need to login to the LinuxMCE Administration Page, and change the username and password to match those configured in the ISY. The template defaults to admin:admin. Afterwards, you will need to reload the router.

When the DCErouter reloads, the driver will establish a connection to the ISY. It will create child devices of the ISY in LinuxMCE, by reading all configured /managed devices from the ISY, and creating a corresponding child in LMCE. You will need to reload the router in order to use the devices from LMCE. Similarly, scenes (groups) will be downloaded and appropriate child devices created. After all devices and scenes have been recognized, you can then edit the devices in LMCE to set the room, floor plan ID (icons used in the Floor plan view in Orbiter), etc. when you are complete, reload the router again. Your devices and Insteon scenes are now available to use in LMCE scenerios.

ISY994i

2013-12-03T04:07:00Z

Mkbrown69: Add very basic driver usage instructions.

[[Category: Automation]]
[[Category: Insteon]]
{{versioninfo|1004Status=In Development|1004UpdatedDate=2nd December 2013|1004UpdatedBy=Michael Brown}}

More info to come. Like the driver itself, this page is a work in progress. Please stand by...

The ISY994i is a home automation controller from Universal Devices. It has an embedded processor, runs it's own real-time OS, is network connected, and manages the various home automation devices as a stand-alone controller. Configuring and administering the ISY is done via a Java application "console", which is used to manage devices, create programs and scheduled events, upgrade the device firmware, and add functionality via purchased license keys. It exposes it's functionality via well-developed application programming interfaces (API's).

The LMCE ISY driver is being written using the Ruby GSD Device interface, and leverages the ISY's API to expose the managed devices and controls to LMCE. The driver has been written with the assumption that the ISY "owns" the connected devices, and exposes them to LMCE for integration and control as an external controller. As the API's develop, some capabilities to configure the ISY from LMCE may be created. Until then, the expectation is that all home automation device configuration and management will occur using the Universal Devices Java admin console, and that the configuration and capabilities will be exposed to LMCE for use via it's capabilities.

'''ISY Models'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Model
! IR Support
! Max. Devices/Scenes
! Max. Programs
|-
| ISY994i
| No
| 256
| 300
|-
|-
| ISY994i/IR
| Yes
| 256
| 300
|-
| ISY994i PRO
| No
| 1024
| 1000
|-
|-
| ISY994i/IR
| Yes
| 1024
| 1000
|-
|}

Zigbee devices have the 'Z' device suffix on the model number (e.g. ISY994iZ/IR PRO). The Z-wave device is has just passed the alpha testing phase, and will be going into beta testing soon. Support for the Z-wave radio will likely be added when it's release, as there's some pretty cool Z-wave sensors available...

[http://www.universal-devices.com/residential/isy994i-series/ Manufacturer Web page at UniversalDevices.com]

The LMCE driver utilizes template # TBD.

'''ISY Hardware Interface support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Insteon
| Support for Insteon PLM's including X10 transmission/reception
| Working
|-
| UPB
| Support for UPB Modems
| N/A
|-
| Zigbee
| Support for the optional Zigbee model/radio.
| N/A
|-
| Z-wave
| Support for the optional Z-wave model/radio.
| N/A
|-
|}

The ISY series supports optional (paid) upgrades which can enable additional functionality in the ISY device. It allows home automation users to start off small, and add additional functionality later as their environment grows or their needs change. For example, a non-pro model can be upgraded by purchasing a Pro upgrade license key. Some hardware upgrades can be done in the field by purchasing the hardware directly from Universal Devices web store. The following table shows the LMCE driver support for the various add-on software modules.

'''ISY module support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Climate Module
| The ISY Weatherbug Climate Module
| In progress
|-
| Networking Module
| The ISY networking module
| N/A
|-
| X10 Module
| The ISY X10 module which incorporates X10 devices into the device tree.
| N/A
|-
| Electricity Module
| The ISY electricity monitoring module for Brultech devices
| N/A
|-
| Irrigation Module
| The irrigation module used in conjunction with the Climate (Weatherbug) module.
| N/A
|-
| ELK Module
| The ISY <-> Elk M1 Security Panel interface module.
| N/A
|}

----

'''Using the ISY Driver'''
The ISY driver is configured for auto-discovery using DHCP. When it requests an IP addresses, LinuxMCE will automatically add the device template. You will need to login to the LinuxMCE Administration Page, and change the username and password to match those configured in the ISY. The template defaults to admin:admin. Afterwards, you will need to reload the router.

When the DCErouter reloads, the driver will establish a connection to the ISY. It will create child devices of the ISY in LinuxMCE, by reading all configured /managed devices from the ISY, and creating a corresponding child in LMCE. You will need to reload the router in order to use the devices from LMCE. Similarly, scenes (groups) will be downloaded and appropriate child devices created. After all devices and scenes have been recognized, you can then edit the devices in LMCE to set the room, floor plan ID (icons used in the Floor plan view in Orbiter), etc. when you are complete, reload the router again. Your devices and Insteon scenes are now available to use in LMCE scenerios.

ISY994i

2013-08-22T17:18:09Z

Mkbrown69:

[[Category: Automation]]
[[Category: Insteon]]
{{versioninfo|1004Status=In Development|1004UpdatedDate=13th June 2013|1004UpdatedBy=Michael Brown}}

More info to come. Like the driver itself, this page is a work in progress. Please stand by...

The ISY994i is a home automation controller from Universal Devices. It has an embedded processor, runs it's own real-time OS, is network connected, and manages the various home automation devices as a stand-alone controller. Configuring and administering the ISY is done via a Java application "console", which is used to manage devices, create programs and scheduled events, upgrade the device firmware, and add functionality via purchased license keys. It exposes it's functionality via well-developed application programming interfaces (API's).

The LMCE ISY driver is being written using the Ruby GSD Device interface, and leverages the ISY's API to expose the managed devices and controls to LMCE. The driver has been written with the assumption that the ISY "owns" the connected devices, and exposes them to LMCE for integration and control as an external controller. As the API's develop, some capabilities to configure the ISY from LMCE may be created. Until then, the expectation is that all home automation device configuration and management will occur using the Universal Devices Java admin console, and that the configuration and capabilities will be exposed to LMCE for use via it's capabilities.

'''ISY Models'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Model
! IR Support
! Max. Devices/Scenes
! Max. Programs
|-
| ISY994i
| No
| 256
| 300
|-
|-
| ISY994i/IR
| Yes
| 256
| 300
|-
| ISY994i PRO
| No
| 1024
| 1000
|-
|-
| ISY994i/IR
| Yes
| 1024
| 1000
|-
|}

Zigbee devices have the 'Z' device suffix on the model number (e.g. ISY994iZ/IR PRO). The Z-wave device is has just passed the alpha testing phase, and will be going into beta testing soon. Support for the Z-wave radio will likely be added when it's release, as there's some pretty cool Z-wave sensors available...

[http://www.universal-devices.com/residential/isy994i-series/ Manufacturer Web page at UniversalDevices.com]

The LMCE driver utilizes template # TBD.

'''ISY Hardware Interface support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Insteon
| Support for Insteon PLM's including X10 transmission/reception
| Working
|-
| UPB
| Support for UPB Modems
| N/A
|-
| Zigbee
| Support for the optional Zigbee model/radio.
| N/A
|-
| Z-wave
| Support for the optional Z-wave model/radio.
| N/A
|-
|}

The ISY series supports optional (paid) upgrades which can enable additional functionality in the ISY device. It allows home automation users to start off small, and add additional functionality later as their environment grows or their needs change. For example, a non-pro model can be upgraded by purchasing a Pro upgrade license key. Some hardware upgrades can be done in the field by purchasing the hardware directly from Universal Devices web store. The following table shows the LMCE driver support for the various add-on software modules.

'''ISY module support'''
{| border="1" cellspacing="0" cellpadding="5" align="left"
! Module
! Description
! Supported Features
|-
| Climate Module
| The ISY Weatherbug Climate Module
| In progress
|-
| Networking Module
| The ISY networking module
| N/A
|-
| X10 Module
| The ISY X10 module which incorporates X10 devices into the device tree.
| N/A
|-
| Electricity Module
| The ISY electricity monitoring module for Brultech devices
| N/A
|-
| Irrigation Module
| The irrigation module used in conjunction with the Climate (Weatherbug) module.
| N/A
|-
| ELK Module
| The ISY <-> Elk M1 Security Panel interface module.
| N/A
|}

ISY994i

2013-06-13T17:44:20Z

Mkbrown69:

[[Category: Automation]]
[[Category: Insteon]]
{{versioninfo|1004Status=In Development|1004UpdatedDate=13th June 2013|1004UpdatedBy=Michael Brown}}

More info to come. Please stand by...

Template # TBD

ISY module support
{| border="1" cellspacing="0" cellpadding="5" align="center"
! Module
! Description
! Supported Features
|-
| Climate Module
| The ISY Weatherbug Climate Module
| In progress
|-
| Networking Module
| The ISY networking module
| N/A
|-
| X10 Module
| The ISY X10 module which incorporates X10 devices into the device tree.
| N/A
|-
| Electricity Module
| The ISY electricity monitoring module for Brultech devices
| N/A
|-
| Irrigation Module
| The irrigation module used in conjunction with the Climate (Weatherbug) module.
| N/A
|-
| ELK Module
| The ISY <-> Elk M1 interface module.
| N/A
|}

ISY994i

2013-06-13T17:43:33Z

Mkbrown69:

[[Category: Automation]]
[[Category: Insteon]]
{{versioninfo|1004Status=In Development|1004UpdatedDate=13th June 2013|1004UpdatedBy=Michael Brown}}

More info to come. Please stand by...

Template # TBD

ISY module support
{| border="1" cellspacing="0" cellpadding="5" align="center"
! Module
! Description
! Supported Features
|-
| Climate Module
| The ISY Weatherbug Climate Module
| In progress
|-
| Networking Module
| The ISY networking module
| N/A
|-
| X10 Module
| The ISY X10 module which incorporates X10 devices into the device tree.
| N/A
|-
| Electricity Module
| The ISY electricity monitoring module for Brultech devices
| N/A
|-
| Irrigation Module
| The irrigation module used in conjunction with the Climate (Weatherbug) module.
| N/A
|-
| ELK Module
| The ISY <-> Elk M1 interface module.
| N/A
|-
| 1004Status
| The status of this page with respect to LinuxMCE Version 1004
| Unknown
|-
| 1004UpdatedDate
| The date this status was applied to to page.
| N/A
|-
| 1004UpdatedBy
| The person applying the status.
| N/A
|}

ISY994i

2013-06-13T17:04:07Z

Mkbrown69:

[[Category: Automation]]
[[Category: Insteon]]
{{versioninfo|1004Status=In Development|1004UpdatedDate=13th June 2013|1004UpdatedBy=Michael Brown}}

More info to come. Please stand by...

ISY994i

2013-06-13T17:02:32Z

Mkbrown69: Created page with "Category: Automation {{versioninfo|1004Status=In Development|1004UpdatedDate=13th June 2013|1004UpdatedBy=Michael Brown}} More info to come. Please stand by..."

[[Category: Automation]]
{{versioninfo|1004Status=In Development|1004UpdatedDate=13th June 2013|1004UpdatedBy=Michael Brown}}

More info to come. Please stand by...

NOAA Weather

2012-08-31T16:21:36Z

Mkbrown69:

{| align="right"
| __TOC__
|}
This device retrieves weather data from weather.gov. Using an ICAO identifier for a nearby airport, the weather data should be fairly accurate for your area. Not quite as good or up to date as a weather station in your back yard, it does a decent job. Keep in mind the data is only updated once per hour at 15 past.

=How to setup the NOAA Weather GSD=
==Device Template==
* Description - NOAA Weather
* Implements DCE
* Device Category - Environment Climate Device #83
* Comm Method - Ethernet
* Commands - Ruby internal commands
==GSD Code==
===New Climate Commands===
These are added under '''[[LinuxMCE Admin Website]]-->Advanced->DCE->[[Commands]]'''
====#923 Get Humidity====
<pre>
get_weather_data_request("Humidity")
</pre>
====#921 Get Temperature====
<pre>
get_weather_data_request("Temperature")
</pre>
====#922 Get Weather====
<pre>
get_weather_data_request("Weather")
</pre>
==== #395 Check for updates====
<pre>
check_weather()
</pre>
====#396 Check for updates done====
<pre>
check_weather_done()
</pre>
====#373 Private Method Listing====
<pre>
### Logging function
def log(word)
$logFile.print( Time.now.to_s + " " + word + "\n" )
$logFile.flush()
end

### Weather check function
def check_weather()
log("Backing up previous data")
oldweather = $weather
oldtemp = $temp
oldpressure = $pressure
olddew_point = $dew_point
oldheat_index = $heat_index
oldwindchill = $windchill
oldhumidity = $humidity
oldwind = $wind
oldvisibility = $visibility

log("Checking for weather updates")

### Get xml file from NOAA
# xmlPath = "www.weather.gov/xml/current_obs/"+$identifier+".xml"
# h = "GET "+xmlPath+" HTTP/1.0\r\n"
# log("HTTP Request: #{h}")
# conn_.Send(h)
# resv = ""
# while(true)
# buff = conn_.Recv(16384, 5000)
# if buff.length() == 0
# break
# end
# recv = recv + buff
# end
h = Net::HTTP.new('www.weather.gov', 80)
data_loc = "/xml/current_obs/"+$identifier+".xml"
resp, data = h.get(data_loc, nil)

if resp.message == "OK"

# if recv =~ /^HTTP[^\r\n]+200\sOK.+?\r\n\r\n(.+)$/m
# data = $1
# log("Recieved:\n#{data}")

data.each_line {|line|
if line =~/location>(.*)<\/location>/
$location = $1
end
if line =~/observation_time_rfc822>(.*)<\/observation_time_rfc822>/
$obs_time = $1
end
if line =~/weather>(.*)<\/weather>/
$weather = $1
end
if $units == "F"
if line =~/temp_f>(.*)<\/temp_f>/
$temp = $1
end
if line =~/pressure_in>(.*)<\/pressure_in>/
$pressure = $1
end
if line =~/dewpoint_f>(.*)<\/dewpoint_f>/
$dew_point = $1
end
if line =~/heat_index_f>(.*)<\/heat_index_f>/
$heat_index = $1
end
if line =~/windchill_f>(.*)<\/windchill_f>/
$windchill = $1
end
else
if line =~/temp_c>(.*)<\/temp_c>/
$temp = $1
end
if line =~/pressure_mb>(.*)<\/pressure_mb>/
$pressure = $1
end
if line =~/dewpoint_c>(.*)<\/dewpoint_c>/
$dew_point = $1
end
if line =~/heat_index_c>(.*)<\/heat_index_c>/
$heat_index = $1
end
if line =~/windchill_c>(.*)<\/windchill_c>/
$windchill = $1
end
end
if line =~/relative_humidity>(.*)<\/relative_humidity>/
$humidity = $1
end
if line =~/wind_string>(.*)<\/wind_string>/
$wind = $1
end
if line =~/visibility_mi>(.*)<\/visibility_mi>/
$visibility = $1
end
}
end

### Send out events for weather changes
if $weather != oldweather
ms = "/usr/pluto/bin/MessageSend dcerouter "+device_.devid_.to_s+" -1001 2 75 13 \""+$weather+"\""
system(ms)
log("Sent: #{ms}")
end
if $temp != oldtemp
ms = "/usr/pluto/bin/MessageSend dcerouter "+device_.devid_.to_s+" -1001 2 25 13 \""+$temp+"\""
system(ms)
log("Sent: #{ms}")
end
if $humidity != oldhumidity
ms = "/usr/pluto/bin/MessageSend dcerouter "+device_.devid_.to_s+" -1001 2 26 13 \""+$humidity+"\""
system(ms)
log("Sent: #{ms}")
end
check_weather_done()
end

### Post weather check
def check_weather_done()
log("Weather data from: "+$obs_time)
log("Weather check complete")
end

### Requests for weather data
def get_weather_data_request(request)
case request
when "Temperature"
log('Recieved: Get Temperature request')
ms = "/usr/pluto/bin/MessageSend dcerouter "+device_.devid_.to_s+" -1001 2 76 13 \""+$temp+"\""
system(ms)
log("Sent: #{ms}")
when "Weather"
log('Recieved: Get Weather request')
ms = "/usr/pluto/bin/MessageSend dcerouter "+device_.devid_.to_s+" -1001 2 77 13 \""+$weather+"\""
system(ms)
log("Sent: #{ms}")
when "Humidity"
log('Recieved: Get Humidity request')
ms = "/usr/pluto/bin/MessageSend dcerouter "+device_.devid_.to_s+" -1001 2 78 13 \""+$humidity+"\""
system(ms)
log("Sent: #{ms}")
end
end
====#351 Process IDLE====
<pre>
### Auto check weather every quarter past the hour per NOAA
t = Time.now

if t.min == 15
t -= (60 * 60)

if $obs_time =~/(\d\d):\d\d:\d\d/
obs_hour = $1
end

if t.hour != obs_hour.to_i
log("Quarter past the hour and weather update needed")
check_weather()
end
end
</pre>
====#355 Process Initialize====
<pre>
###
# NOAA Weather check
# 2008 Jason Speckman
###
require 'net/http'

# Init Vars

$logFile = File.new("/var/log/pluto/NOAA_Weather.log", "w")

### Change these values to match device data values
$DEVICEDATA_ICAO_CONST = 249
$DEVICEDATA_UNITS_CONST = 250

$units = ""
$identifier = ""
$location = ""
$obs_time = ""
$weather = ""
$temp = ""
$pressure = ""
$dew_point = ""
$heat_index = ""
$windchill = ""
$humidity = ""
$wind = ""
$visibility = ""

### Check for identifier and units
if device_.devdata_ != nil
if device_.devdata_[$DEVICEDATA_ICAO_CONST] != nil
$identifier = device_.devdata_[$DEVICEDATA_ICAO_CONST]
log("ICAO identifier: "+$identifier)
else
log("No ICAO identifier specified")
end
if device_.devdata_[$DEVICEDATA_UNITS_CONST] != nil
$units = device_.devdata_[$DEVICEDATA_UNITS_CONST]
else
$units = "F"
end
end

log("Units in degrees "+$units)

if $units == "F"
$press_units = "in. Hg"
else
$press_units = "hPa"
end

### Tell DCE we are a climate device
log("Starting NOAA Weather Check")
log("Setup message intercept for DCERouter")

###
# devIDfrom: device_.devid_ = my device id
# devIDto: -1000 = dcerouter
# priority:
# type: 1 = command, 2 = event
# id:

$devIDfrom = device_.devid_
devIDto = -1000
priority = ""
type = 2
id = ""

#cmd = Command.new(devIDfrom, devIDto, priority, type, id)
#cmd.params_[x] = y
#SendCommand(cmd)

#ms = "/usr/pluto/bin/MessageSend dcerouter " + device_.devid_.to_s + " -1000 8 0 5 2 4 10"
#system(ms)

log("Init complete")

### Initial weather check
check_weather()
</pre>

====#356 Process Release====
<pre>
if ($logFile != nil) then
$logFile.close
end
</pre>
==Device Data==
(These variable numbers may be different, be sure to update them in the ruby code)
* #249 ICAO Location Indicator(string) - Comment: Local airport identifier for weather info - (Required and Allowed to modify checked)
* #250 Units(string) - Comment: Degree units. Either (F) or (C) - (Required and Allowed to modify checked)
==Commands device responds to==
* Get Humidity #923
* Get Temperature #921
* Get Weather #922
==Events Sent by Device==
* Temperature Changed #25 - Temperature has changed since last update
* Weather Changed #75 - Weather has changed since last update
* Humidity Changed #26 - Humidity has changed since last update
==New climate events==
(Need to be added, I had to put them directly into the db since the admin interface would not)
* Get Temperature Response #76 - Response for Get Temperature command
* Get Weather Response #77 - Response for Get Weather command
* Get Humidity Response #78 - Response for Get Humidity command
==Issues and TODO==
* 2008-07-06 Testing new features.
* 2008-07-26 Updated code with new features
* Fixed weather.gov xml url
* Does not respond to events (Added)
* Only send weather info when there is a change from the previous weather check (Done)
* Only sends weather conditions and temperature changes (Added humidity)
* No way to ask for weather data from the device (Done)
[[category: Tutorials]]
[[Category: Climate ]]

User:Mkbrown69

2011-09-09T20:14:47Z

Mkbrown69: Created page with "My Set-up and notes to come here sometime soon..."

My Set-up and notes to come here sometime soon...