LinuxMCE - User contributions [en]

LmceRemote

2010-03-10T17:16:54Z

Caiman: /* Using it remotely */

= LMCE Remote =
LMCE Remote is an iPhone application which can be used to:
* load available lights from LMCE
* display the lights status
* set each light on or off

== Screenshots ==
[[Image:LmceRemoteLights.jpg]]
[[Image:LmceRemoteSettings.jpg]]

The light and room names on this screenshot are in French, but they are retrieved directly from LMCE. They will appear just as you entered them in the lightning wizard.

== Intent ==
Please note, this is not, and is not intended to be a full Orbiter. The goal of this app is to be lightweight so that it remains very responsive even when used over a 3G connection.

== Status and Availability ==
At the moment, the app is in a functioning state (for the features mentioned above).

The source code has been given to the LMCE development team.

It is also available on google code: http://code.google.com/p/lmce-remote/

The current plan is to have the binary version on the app store soon for a few dollars. All net benefits will go to research against cancer.

== Beta testing ==
Beta testers are welcome after they have installed the web service and have it working (check with http://dcerouter/lmce-ws/index.rb?cmd=getLights). Once that is done, PM me (caiman) your iPhone device ID to get a build, or compile it yourself from the source code to test it on the iphone simulator or on a device if you have purchased the iphone developer license.

== Using it remotely ==
By default, the application will connect to the hostname 'dcerouter'. This should work fine locally on most installations. The application can also be used remotely by following these steps:

* subscribe to a dynamic dns if required
* open and forward a TCP port xxxx on your internet router to the port your core Apache is listening to (usually 80)
* setup apache authentication as your server is now exposed
* setup apache to listen to the same port as the external port you have redirected (it can listen on multiple ports)
* setup split-dns, so that when queried from your LAN, the dyndns hostname resolved to the internal IP of your core
* enter your external hostname in the iphone app settings tab, as well as your apache username and password

== Want to help? ==
If you want to contribute, packaging the [[web service|WebService]] and making it easy to install is the best thing you can do. LMCE needs a good web service.
LmceRemote comes with a basic web service that is sufficient for the purposes of this app. But having a clean and robust web service shipped together with LMCE would be fantastic.
I am looking for someone who can help package my temporary web service in a nice .deb, and resolve the dependencies (there are some issues with ruby gems). You can pm me (caiman) on the forum.

== Upcoming features ==
Some additional features are being considered for short term:
* Add a tab with scenarios
* Add a tab to set security mode

== Architecture ==
There were three possible approaches to connect to LMCE:

* Connect directly to the DCE router
** Pros:
*** seemed to be the cleanest approach, closed to a real orbiter
** Cons:
*** need to implement the DCE protocol
*** it is unclear how to obtain a list of the available scenarios through this protocol
*** remote access is difficult because of the lack of authentication mechanism

* Connect to the web interface
** Pros:
*** easy to implement for simple actions
*** easier remote access as the web server is often made available externally
** Cons:
*** requires parsing HTML for more advanced actions and is prone to errors
*** requires double authentication when used for remote access (apache auth, then lmce auth)

* Implement a [[web service|WebService]]
** Pros:
*** can access all required information in Lmce databases
*** very lean and network efficient
*** easily made available externally with apache authentication
** Cons:
*** The user needs to install the [[web service|WebService]] on the core before it can be used

I have chosen to go for the [[web service|WebService]] approach.

LmceRemote

2010-03-10T14:51:07Z

Caiman: /* Status and Availability */

= LMCE Remote =
LMCE Remote is an iPhone application which can be used to:
* load available lights from LMCE
* display the lights status
* set each light on or off

== Screenshots ==
[[Image:LmceRemoteLights.jpg]]
[[Image:LmceRemoteSettings.jpg]]

The light and room names on this screenshot are in French, but they are retrieved directly from LMCE. They will appear just as you entered them in the lightning wizard.

== Intent ==
Please note, this is not, and is not intended to be a full Orbiter. The goal of this app is to be lightweight so that it remains very responsive even when used over a 3G connection.

== Status and Availability ==
At the moment, the app is in a functioning state (for the features mentioned above).

The source code has been given to the LMCE development team.

It is also available on google code: http://code.google.com/p/lmce-remote/

The current plan is to have the binary version on the app store soon for a few dollars. All net benefits will go to research against cancer.

== Beta testing ==
Beta testers are welcome after they have installed the web service and have it working (check with http://dcerouter/lmce-ws/index.rb?cmd=getLights). Once that is done, PM me (caiman) your iPhone device ID to get a build, or compile it yourself from the source code to test it on the iphone simulator or on a device if you have purchased the iphone developer license.

== Using it remotely ==
By default, the application will connect to the hostname 'dcerouter'. This should work fine locally on most installations. The application can also be used remotely by following these steps:

* subscribe to a dynamic dns if required
* open and forward a TCP port on your internet router to the port your core Apache is listening to (usually 80)
* setup apache authentication
* setup split-dns, so that when queried from your LAN, the dyndns hostname resolved to the internal IP of your core

== Want to help? ==
If you want to contribute, packaging the [[web service|WebService]] and making it easy to install is the best thing you can do. LMCE needs a good web service.
LmceRemote comes with a basic web service that is sufficient for the purposes of this app. But having a clean and robust web service shipped together with LMCE would be fantastic.
I am looking for someone who can help package my temporary web service in a nice .deb, and resolve the dependencies (there are some issues with ruby gems). You can pm me (caiman) on the forum.

== Upcoming features ==
Some additional features are being considered for short term:
* Add a tab with scenarios
* Add a tab to set security mode

== Architecture ==
There were three possible approaches to connect to LMCE:

* Connect directly to the DCE router
** Pros:
*** seemed to be the cleanest approach, closed to a real orbiter
** Cons:
*** need to implement the DCE protocol
*** it is unclear how to obtain a list of the available scenarios through this protocol
*** remote access is difficult because of the lack of authentication mechanism

* Connect to the web interface
** Pros:
*** easy to implement for simple actions
*** easier remote access as the web server is often made available externally
** Cons:
*** requires parsing HTML for more advanced actions and is prone to errors
*** requires double authentication when used for remote access (apache auth, then lmce auth)

* Implement a [[web service|WebService]]
** Pros:
*** can access all required information in Lmce databases
*** very lean and network efficient
*** easily made available externally with apache authentication
** Cons:
*** The user needs to install the [[web service|WebService]] on the core before it can be used

I have chosen to go for the [[web service|WebService]] approach.

LmceRemote

2010-03-10T14:50:43Z

Caiman:

= LMCE Remote =
LMCE Remote is an iPhone application which can be used to:
* load available lights from LMCE
* display the lights status
* set each light on or off

== Screenshots ==
[[Image:LmceRemoteLights.jpg]]
[[Image:LmceRemoteSettings.jpg]]

The light and room names on this screenshot are in French, but they are retrieved directly from LMCE. They will appear just as you entered them in the lightning wizard.

== Intent ==
Please note, this is not, and is not intended to be a full Orbiter. The goal of this app is to be lightweight so that it remains very responsive even when used over a 3G connection.

== Status and Availability ==
At the moment, the app is in a functioning state (for the features mentioned above).

The source code has been given to the LMCE development team.

It is also available on google code: http://code.google.com/p/lmce-remote/

The current plan is to have the binary version on the app store soon for a few dollars. All net benefits will go to research against cancer.

Beta testers are welcome after they have installed the web service and have it working (check with http://dcerouter/lmce-ws/index.rb?cmd=getLights). Once that is done, PM me (caiman) your iPhone device ID to get a build, or compile it yourself from the source code to test it on the iphone simulator or on a device if you have purchased the iphone developer license.

== Using it remotely ==
By default, the application will connect to the hostname 'dcerouter'. This should work fine locally on most installations. The application can also be used remotely by following these steps:

* subscribe to a dynamic dns if required
* open and forward a TCP port on your internet router to the port your core Apache is listening to (usually 80)
* setup apache authentication
* setup split-dns, so that when queried from your LAN, the dyndns hostname resolved to the internal IP of your core

== Want to help? ==
If you want to contribute, packaging the [[web service|WebService]] and making it easy to install is the best thing you can do. LMCE needs a good web service.
LmceRemote comes with a basic web service that is sufficient for the purposes of this app. But having a clean and robust web service shipped together with LMCE would be fantastic.
I am looking for someone who can help package my temporary web service in a nice .deb, and resolve the dependencies (there are some issues with ruby gems). You can pm me (caiman) on the forum.

== Upcoming features ==
Some additional features are being considered for short term:
* Add a tab with scenarios
* Add a tab to set security mode

== Architecture ==
There were three possible approaches to connect to LMCE:

* Connect directly to the DCE router
** Pros:
*** seemed to be the cleanest approach, closed to a real orbiter
** Cons:
*** need to implement the DCE protocol
*** it is unclear how to obtain a list of the available scenarios through this protocol
*** remote access is difficult because of the lack of authentication mechanism

* Connect to the web interface
** Pros:
*** easy to implement for simple actions
*** easier remote access as the web server is often made available externally
** Cons:
*** requires parsing HTML for more advanced actions and is prone to errors
*** requires double authentication when used for remote access (apache auth, then lmce auth)

* Implement a [[web service|WebService]]
** Pros:
*** can access all required information in Lmce databases
*** very lean and network efficient
*** easily made available externally with apache authentication
** Cons:
*** The user needs to install the [[web service|WebService]] on the core before it can be used

I have chosen to go for the [[web service|WebService]] approach.

LmceRemote

2010-03-10T14:04:11Z

Caiman: added link to source code

= LMCE Remote =
LMCE Remote is an iPhone application which can be used to:
* load available lights from LMCE
* display the lights status
* set each light on or off

== Screenshots ==
[[Image:LmceRemoteLights.jpg]]
[[Image:LmceRemoteSettings.jpg]]

The light and room names on this screenshot are in French, but they are retrieved directly from LMCE. They will appear just as you entered them in the lightning wizard.

== Intent ==
Please note, this is not, and is not intended to be a full Orbiter. The goal of this app is to be lightweight so that it remains very responsive even when used over a 3G connection.

== Architecture ==
There were three possible approaches to connect to LMCE:

* Connect directly to the DCE router
** Pros:
*** seemed to be the cleanest approach, closed to a real orbiter
** Cons:
*** need to implement the DCE protocol
*** it is unclear how to obtain a list of the available scenarios through this protocol
*** remote access is difficult because of the lack of authentication mechanism

* Connect to the web interface
** Pros:
*** easy to implement for simple actions
*** easier remote access as the web server is often made available externally
** Cons:
*** requires parsing HTML for more advanced actions and is prone to errors
*** requires double authentication when used for remote access (apache auth, then lmce auth)

* Implement a [[web service|WebService]]
** Pros:
*** can access all required information in Lmce databases
*** very lean and network efficient
*** easily made available externally with apache authentication
** Cons:
*** The user needs to install the [[web service|WebService]] on the core before it can be used

I have chosen to go for the [[web service|WebService]] approach.

== Status and Availability ==
At the moment, the app is in a functioning state (for the features mentioned above).

The source code has been given to the LMCE development team.

It is also available on google code: http://code.google.com/p/lmce-remote/

The current plan is to have the binary version on the app store soon for a few dollars. All net benefits will go to research against cancer.

Beta testers are welcome after they have installed the web service and have it working (check with http://dcerouter/lmce-ws/index.rb?cmd=getLights). Once that is done, PM me (caiman) your iPhone device ID to get a build, or compile it yourself from the source code to test it on the iphone simulator or on a device if you have purchased the iphone developer license.

== Want to help? ==
If you want to contribute, packaging the [[web service|WebService]] and making it easy to install is the best thing you can do. LMCE needs a good web service.
LmceRemote comes with a basic web service that is sufficient for the purposes of this app. But having a clean and robust web service shipped together with LMCE would be fantastic.
I am looking for someone who can help package my temporary web service in a nice .deb, and resolve the dependencies (there are some issues with ruby gems). You can pm me (caiman) on the forum.

== Upcoming features ==
Some additional features are being considered for short term:
* Add a tab with scenarios
* Add a tab to set security mode

Web service

2010-03-10T14:01:48Z

Caiman: /* LMCE Web Service */

=== LMCE Web Service ===
The web service described on this page is used by the iPhone application [[LmceRemote]].

It is a ruby script ([[WebServiceSource|see source]]) run by the Apache web server.

There are a few dependencies that need to be installed first. It would be great to have them installed via debian packages but I had to go for a manual install via ruby gem.
* rubygems
* json
* cgi
* mysql

=== Want to help ? ==
Help is welcome to make the installation of this webservice easier to end users. Topics to cover:
- ruby dependencies
- initial install
- setting-up authentication in apache

=== Other Webservices ===
There are other initiatives to provide web services in LMCE:
* http://github.com/chrisbirkinshaw/lmce_webservice
* A webservice plugin by Hari
Both are being considered for this project too.

Web service

2010-03-10T14:00:39Z

Caiman: /* Other Webservices */

=== LMCE Web Service ===
The web service described on this page is used by the iPhone application [LmceRemote].

It is a ruby script ([[WebServiceSource|see source]]) run by the Apache web server.

There are a few dependencies that need to be installed first. It would be great to have them installed via debian packages but I had to go for a manual install via ruby gem.
* rubygems
* json
* cgi
* mysql

=== Want to help ? ==
Help is welcome to make the installation of this webservice easier to end users. Topics to cover:
- ruby dependencies
- initial install
- setting-up authentication in apache

=== Other Webservices ===
There are other initiatives to provide web services in LMCE:
* http://github.com/chrisbirkinshaw/lmce_webservice
* A webservice plugin by Hari
Both are being considered for this project too.

Web service

2010-03-10T14:00:03Z

Caiman: /* LMCE Web Service */

=== LMCE Web Service ===
The web service described on this page is used by the iPhone application [LmceRemote].

It is a ruby script ([[WebServiceSource|see source]]) run by the Apache web server.

There are a few dependencies that need to be installed first. It would be great to have them installed via debian packages but I had to go for a manual install via ruby gem.
* rubygems
* json
* cgi
* mysql

=== Want to help ? ==
Help is welcome to make the installation of this webservice easier to end users. Topics to cover:
- ruby dependencies
- initial install
- setting-up authentication in apache

=== Other Webservices ===
There are other initiatives to provide web services in LMCE:
* [http://github.com/chrisbirkinshaw/lmce_webservice]
* A webservice plugin by Hari
Both are being considered for this project too.

LmceRemote

2010-03-02T11:24:30Z

Caiman: /* Availability */

= LMCE Remote =
LMCE Remote is an iPhone application which can be used to:
* load available lights from LMCE
* display the lights status
* set each light on or off

== Screenshots ==
[[Image:LmceRemoteLights.jpg]]
[[Image:LmceRemoteSettings.jpg]]

The light and room names on this screenshot are in French, but they are retrieved directly from LMCE. They will appear just as you entered them in the lightning wizard.

== Intent ==
Please note, this is not, and is not intended to be a full Orbiter. The goal of this app is to be lightweight so that it remains very responsive even when used over a 3G connection.

== Architecture ==
There were three possible approaches to connect to LMCE:

* Connect directly to the DCE router
** Pros:
*** seemed to be the cleanest approach, closed to a real orbiter
** Cons:
*** need to implement the DCE protocol
*** it is unclear how to obtain a list of the available scenarios through this protocol
*** remote access is difficult because of the lack of authentication mechanism

* Connect to the web interface
** Pros:
*** easy to implement for simple actions
*** easier remote access as the web server is often made available externally
** Cons:
*** requires parsing HTML for more advanced actions and is prone to errors
*** requires double authentication when used for remote access (apache auth, then lmce auth)

* Implement a [[web service|WebService]]
** Pros:
*** can access all required information in Lmce databases
*** very lean and network efficient
*** easily made available externally with apache authentication
** Cons:
*** The user needs to install the [[web service|WebService]] on the core before it can be used

I have chosen to go for the [[web service|WebService]] approach.

== Status and Availability ==
At the moment, the app is in a functioning state (for the features mentioned above).

The source code has been given to the LMCE development team and will be made available shortly.

The current plan is to have the binary version on the app store soon for a few dollars. All net benefits will go to research against cancer.

Beta testers are welcome after they have installed the web service and have it working (check with http://dcerouter/lmce-ws/index.rb?cmd=getLights). Once that is done, PM me (caiman) your iPhone device ID to get a build, or compile it yourself from the source code once published.

== Want to help? ==
If you want to contribute, packaging the [[web service|WebService]] and making it easy to install is the best thing you can do. LMCE needs a good web service.
LmceRemote comes with a basic web service that is sufficient for the purposes of this app. But having a clean and robust web service shipped together with LMCE would be fantastic.
I am looking for someone who can help package my temporary web service in a nice .deb, and resolve the dependencies (there are some issues with ruby gems). You can pm me (caiman) on the forum.

== Upcoming features ==
Some additional features are being considered for short term:
* Add a tab with scenarios
* Add a tab to set security mode

LmceRemote

2010-03-01T09:13:13Z

Caiman: /* Availability */

= LMCE Remote =
LMCE Remote is an iPhone application which can be used to:
* load available lights from LMCE
* display the lights status
* set each light on or off

== Screenshots ==
[[Image:LmceRemoteLights.jpg]]
[[Image:LmceRemoteSettings.jpg]]

The light and room names on this screenshot are in French, but they are retrieved directly from LMCE. They will appear just as you entered them in the lightning wizard.

== Intent ==
Please note, this is not, and is not intended to be a full Orbiter. The goal of this app is to be lightweight so that it remains very responsive even when used over a 3G connection.

== Architecture ==
There were three possible approaches to connect to LMCE:

* Connect directly to the DCE router
** Pros:
*** seemed to be the cleanest approach, closed to a real orbiter
** Cons:
*** need to implement the DCE protocol
*** it is unclear how to obtain a list of the available scenarios through this protocol
*** remote access is difficult because of the lack of authentication mechanism

* Connect to the web interface
** Pros:
*** easy to implement for simple actions
*** easier remote access as the web server is often made available externally
** Cons:
*** requires parsing HTML for more advanced actions and is prone to errors
*** requires double authentication when used for remote access (apache auth, then lmce auth)

* Implement a [[web service|WebService]]
** Pros:
*** can access all required information in Lmce databases
*** very lean and network efficient
*** easily made available externally with apache authentication
** Cons:
*** The user needs to install the [[web service|WebService]] on the core before it can be used

I have chosen to go for the [[web service|WebService]] approach.

== Availability ==
At the moment, the app is in a functionning state (for the features mentioned above).
It is however not yet available to the public. Expect it on the app store soon for a small fee. Once the cost of the SDK is recovered, all benefits go to research against cancer.

Source code will also be available shortly for anyone who wants to play with it. Just need to find the right place.

Beta testers are welcome after they have installed the web service and have it working (check with http://dcerouter/lmce-ws/index.rb?cmd=getLights)
In that case, PM me your iPhone device ID to get a build, or get the source code once published.

== Want to help? ==
If you want to contribute, packaging the [[web service|WebService]] and making it easy to install is the best thing you can do. LMCE needs a good web service.
LmceRemote comes with a basic web service that is sufficient for the purposes of this app. But having a clean and robust web service shipped together with LMCE would be fantastic.
I am looking for someone who can help package my temporary web service in a nice .deb, and resolve the dependencies (there are some issues with ruby gems). You can pm me (caiman) on the forum.

== Upcoming features ==
Some additional features are being considered for short term:
* Add a tab with scenarios
* Add a tab to set security mode

LmceRemote

2010-02-28T21:12:46Z

Caiman: /* Availability */

= LMCE Remote =
LMCE Remote is an iPhone application which can be used to:
* load available lights from LMCE
* display the lights status
* set each light on or off

== Screenshots ==
[[Image:LmceRemoteLights.jpg]]
[[Image:LmceRemoteSettings.jpg]]

The light and room names on this screenshot are in French, but they are retrieved directly from LMCE. They will appear just as you entered them in the lightning wizard.

== Intent ==
Please note, this is not, and is not intended to be a full Orbiter. The goal of this app is to be lightweight so that it remains very responsive even when used over a 3G connection.

== Architecture ==
There were three possible approaches to connect to LMCE:

* Connect directly to the DCE router
** Pros:
*** seemed to be the cleanest approach, closed to a real orbiter
** Cons:
*** need to implement the DCE protocol
*** it is unclear how to obtain a list of the available scenarios through this protocol
*** remote access is difficult because of the lack of authentication mechanism

* Connect to the web interface
** Pros:
*** easy to implement for simple actions
*** easier remote access as the web server is often made available externally
** Cons:
*** requires parsing HTML for more advanced actions and is prone to errors
*** requires double authentication when used for remote access (apache auth, then lmce auth)

* Implement a [[web service|WebService]]
** Pros:
*** can access all required information in Lmce databases
*** very lean and network efficient
*** easily made available externally with apache authentication
** Cons:
*** The user needs to install the [[web service|WebService]] on the core before it can be used

I have chosen to go for the [[web service|WebService]] approach.

== Availability ==
At the moment, the app is in a functionning state (for the features mentioned above).
It is however not yet available to the public. Expect it on the app store soon for a small fee.

Beta testers are welcome after they have installed the web service and have it working (check with http://dcerouter/lmce-ws/index.rb?cmd=getLights)
In that case, PM me your iPhone device ID

== Want to help? ==
If you want to contribute, packaging the [[web service|WebService]] and making it easy to install is the best thing you can do. LMCE needs a good web service.
LmceRemote comes with a basic web service that is sufficient for the purposes of this app. But having a clean and robust web service shipped together with LMCE would be fantastic.
I am looking for someone who can help package my temporary web service in a nice .deb, and resolve the dependencies (there are some issues with ruby gems). You can pm me (caiman) on the forum.

== Upcoming features ==
Some additional features are being considered for short term:
* Add a tab with scenarios
* Add a tab to set security mode

Web service

2010-02-28T21:08:52Z

Caiman:

WebServiceSource

2010-02-28T21:06:10Z

Caiman:

This script needs to be placed in /var/www/lmce-ws/index.rb

<pre>

#!/usr/bin/ruby

require 'rubygems'
require 'json'
require 'cgi'
require 'mysql'

def hashresult(query)
# Execute SQL query and return result as an array, one entry per row
# setup sql database
db = Mysql.new("localhost", "root", "")
db.select_db("pluto_main")

result = db.query(query)
arr = Array.new
#result.each_hash(with_table=true) do |row|
result.each do |row|
arr << row
end
return arr
end

def getlights()
# return list of lights (devices with (DeviceTemplate.FK_DeviceCategory = 73)
query = "SELECT Device.PK_Device, Device.Description, Device.State, Device.FK_Room FROM Device,DeviceTemplate WHERE (Device.FK_DeviceTemplate = DeviceTemplate.PK_DeviceTemplate) AND (DeviceTemplate.FK_DeviceCategory = 73) ORDER BY PK_Device ASC"
return hashresult(query)
end

def getrooms()
# return list of all rooms
query = "SELECT Room.PK_Room, Room.Description FROM Room ORDER BY Room.Description ASC"
return hashresult(query)
end

def getscenarios()
query = "SELECT CommandGroup.PK_CommandGroup, CommandGroup.Description, CommandGroup.Hint, CommandGroup.FK_Template, CommandGroup_Room.FK_Room
FROM CommandGroup, CommandGroup_Room
WHERE (CommandGroup_Room.FK_CommandGroup = CommandGroup.PK_CommandGroup)
ORDER BY Sort ASC;"
return hashresult(query)
end

def gettemplates()
query = "
SELECT PK_Template, Description
FROM Template
;"
return hashresult(query)
end

def sendcommand(id,command)
return `/usr/pluto/bin/MessageSend localhost 0 #{id} 1 #{command}`
end

# Send header to http client
puts "Content-type: text/html\r\n\r\n"
#puts "Content-type: application/json\r\n\r\n"

# Process CGI arguments
c=CGI.new
cmd=c['cmd']

return_obj = case cmd
when 'getLights' then getlights()
when 'getRooms' then getrooms()
when 'getScenarios' then getscenarios()
when 'getTemplates' then gettemplates()
when 'sendCommand' then sendcommand(c['id'], c['command'])
else "use cmd=xxx where xxx is getLights, getRooms, getScenarios, getTemplates"
end

# Send the return object as JSON
puts return_obj.to_json

</pre>

WebServiceSource

2010-02-28T21:04:59Z

Caiman: New page: This script needs to be placed in /var/www/lmce-ws/index.rb <nowiki> #!/usr/bin/ruby require 'rubygems' require 'json' require 'cgi' require 'mysql' def hashresult(query) # Execute SQL...

This script needs to be placed in /var/www/lmce-ws/index.rb

<nowiki>

#!/usr/bin/ruby

require 'rubygems'
require 'json'
require 'cgi'
require 'mysql'

def hashresult(query)
# Execute SQL query and return result as an array, one entry per row
# setup sql database
db = Mysql.new("localhost", "root", "")
db.select_db("pluto_main")

result = db.query(query)
arr = Array.new
#result.each_hash(with_table=true) do |row|
result.each do |row|
arr << row
end
return arr
end

def getlights()
# return list of lights (devices with (DeviceTemplate.FK_DeviceCategory = 73)
query = "SELECT Device.PK_Device, Device.Description, Device.State, Device.FK_Room FROM Device,DeviceTemplate WHERE (Device.FK_DeviceTemplate = DeviceTemplate.PK_DeviceTemplate) AND (DeviceTemplate.FK_DeviceCategory = 73) ORDER BY PK_Device ASC"
return hashresult(query)
end

def getrooms()
# return list of all rooms
query = "SELECT Room.PK_Room, Room.Description FROM Room ORDER BY Room.Description ASC"
return hashresult(query)
end

def getscenarios()
query = "SELECT CommandGroup.PK_CommandGroup, CommandGroup.Description, CommandGroup.Hint, CommandGroup.FK_Template, CommandGroup_Room.FK_Room
FROM CommandGroup, CommandGroup_Room
WHERE (CommandGroup_Room.FK_CommandGroup = CommandGroup.PK_CommandGroup)
ORDER BY Sort ASC;"
return hashresult(query)
end

def gettemplates()
query = "
SELECT PK_Template, Description
FROM Template
;"
return hashresult(query)
end

def sendcommand(id,command)
return `/usr/pluto/bin/MessageSend localhost 0 #{id} 1 #{command}`
end

# Send header to http client
puts "Content-type: text/html\r\n\r\n"
#puts "Content-type: application/json\r\n\r\n"

# Process CGI arguments
c=CGI.new
cmd=c['cmd']

return_obj = case cmd
when 'getLights' then getlights()
when 'getRooms' then getrooms()
when 'getScenarios' then getscenarios()
when 'getTemplates' then gettemplates()
when 'sendCommand' then sendcommand(c['id'], c['command'])
else "use cmd=xxx where xxx is getLights, getRooms, getScenarios, getTemplates"
end

# Send the return object as JSON
puts return_obj.to_json

</nowiki>

Web service

2010-02-28T20:58:39Z

Caiman: New page: === LMCE Web Service === The web service described on this page is used by the iPhone application [LmceRemote]. It is a ruby script run by the Apache web server. The...

=== LMCE Web Service ===
The web service described on this page is used by the iPhone application [LmceRemote].

It is a [[WebServiceSource|ruby script]] run by the Apache web server.

There are a few dependencies that need to be installed first. It would be great to have them installed via debian packages but I had to go for a manual install via ruby gem.

LmceRemote

2010-02-28T20:54:15Z

Caiman:

LmceRemote

2010-02-28T20:52:15Z

Caiman: /* Architecture */

LmceRemote

2010-02-28T20:47:06Z

Caiman: /* Screenshots */

LmceRemote

2010-02-28T20:46:54Z

Caiman: /* Screenshots */

LmceRemote

2010-02-28T20:45:30Z

Caiman: /* Want to help? */

LmceRemote

2010-02-28T20:42:34Z

Caiman: /* Availability */

LmceRemote

2010-02-28T16:43:40Z

Caiman:

LmceRemote

2010-02-28T16:40:56Z

Caiman: /* Architecture */

LmceRemote

2010-02-28T16:38:30Z

Caiman:

File:LmceRemoteSettings.jpg

2010-02-28T16:37:17Z

Caiman: Screenshot of the Lmce Remote iPhone application, settings tab

Screenshot of the Lmce Remote iPhone application, settings tab

File:LmceRemoteLights.jpg

2010-02-28T16:36:53Z

Caiman: Screenshot of the Lmce Remote iPhone application, lights tab

Screenshot of the Lmce Remote iPhone application, lights tab

LmceRemote

2010-02-28T16:33:44Z

Caiman:

= LMCE Remote =
LMCE Remote is an iPhone application which can be used to:
* load available lights from LMCE
* display the lights status
* set each light on or off

== Screenshots ==
[[Image:Example.jpg]]
[[Image:Example.jpg]]

== Intent ==
Please note, this is not, and is not intended to be a full Orbiter. The goal of this app is to be lightweight so that it remains very responsive even when used over a 3G connection.

== Architecture ==
There were three possible approaches to connect to LMCE:

=== Connect directly to the DCE router ===
Pros:
- seemed to be the cleanest approach, closed to a real orbiter
Cons:
- need to implement the DCE protocol
- it is unclear how to obtain a list of the available scenarios through this protocol
- remote access is difficult because of the lack of authentication mechanism

=== Connect to the web interface ===
Pros:
- easy to implement for simple actions
- easier remote access as the web server is often made available externally
Cons:
- requires parsing HTML for more advanced actions and is prone to errors
- requires double authentication when used for remote access (apache auth, then lmce auth)

=== Implement a web service ===
Pros:
- can access all required information in Lmce databases
- very lean and network efficient
- easily made available externally with apache authentication
Cons:
- The user needs to install the web service on the core before it can be used

I have chosen to go for the web service approach.

== Upcoming features ==
Some additional features are being seriously considered:
* Add a tab with scenarios
* Add a tab to set security mode

LmceRemote

2010-02-28T16:33:05Z

Caiman: Created page

= LMCE Remote =
LMCE Remote is an iPhone application which can be used to:
* load available lights from LMCE
* display the lights status
* set each light on or off

== Intent ==
Please note, this is not, and is not intended to be a full Orbiter. The goal of this app is to be lightweight so that it remains very responsive even when used over a 3G connection.

== Architecture ==
There were three possible approaches to connect to LMCE:

=== Connect directly to the DCE router ===
Pros:
- seemed to be the cleanest approach, closed to a real orbiter
Cons:
- need to implement the DCE protocol
- it is unclear how to obtain a list of the available scenarios through this protocol
- remote access is difficult because of the lack of authentication mechanism

=== Connect to the web interface ===
Pros:
- easy to implement for simple actions
- easier remote access as the web server is often made available externally
Cons:
- requires parsing HTML for more advanced actions and is prone to errors
- requires double authentication when used for remote access (apache auth, then lmce auth)

=== Implement a web service ===
Pros:
- can access all required information in Lmce databases
- very lean and network efficient
- easily made available externally with apache authentication
Cons:
- The user needs to install the web service on the core before it can be used

I have chosen to go for the web service approach.

== Upcoming features ==
Some additional features are being seriously considered:
* Add a tab with scenarios
* Add a tab to set security mode

Apple Iphone

2010-02-28T16:14:34Z

Caiman: Created LmceRemote page

[[Category:Orbiters]]
[[Image:Iphone.gif]]
==About this device==
* 3.5-inch (diagonal) widescreen multi-touch display
** 480-by-320-pixel resolution at 163 ppi
** Support for display of multiple languages and characters simultaneously
* OS X
* Quad-band (850, 900, 1800, 1900 MHz)
* Wi-Fi (802.11b/g)
* EDGE
* Bluetooth 2.0+EDR
* 2.0 megapixels

This is a very popular device that many users would prefer to use as an Orbiter.

==Lmce related applications running on iPhone==
* [[LmceRemote]] - Lightweight remote to control LMCE lights

CM11

2010-02-09T20:23:20Z

Caiman: Added note about GC100

{| align="right"
| __TOC__
|}
[[Category: Power Line Control]]

== Description ==
The CM11 (A/F/G/U/...) is a device that uses [http://hypermetrics.com/rubyhacker/x10proto.html X10] protocol to control lights and other appliances around the house by injecting data into powerline.

Each X10 device has an address formed as ''housecode''[A..P]+''unitcode''[1..16]. As powerlines are usually shared between near houses/apartments it's a good idea to choose an other housecode than your neighbor, or have a suitable filter installed by a qualified electrician.

Note that some electric equipment can generate a lot of static on the powerlines. This can drasticly reduce the performance of the X10 installation. The solution is to install filters, effectively isolating these devices from the rest of the power grid. These type of filters are usually installed between the power socket and plug of the appliance. Some X10 switches and dimmers also have these filters built in already (depending on the make and model of course) to ensure more reliable operation.

== Setup ==
# [http://192.168.80.1/ web admin] -> Show devices tree -> ''the device to which the CM11 is connected'' (For instance "CORE". If you are running a hybrid core, make sure you select the "CORE" device not the "The core/hybrid".)
# Create Child Device -> Pick device template -> CM11A (The wizzard pops up to say she didn't detect lighting?, then shows "dev81" and an OK button in 1.1-RC1, I just ignored this).
# Device data -> COM Port on PC -> ''the port to which this device is connected'' -> '''save'''. (ttyS0="com1", ttyS1="com2", and so on, "pci0000:00/0000:00:13.1+2" in my case, which is a USB port [http://forum.linuxmce.org/index.php?topic=1850.msg8883#msg8883]).

== Adding lights ==
# [http://192.168.80.1/ web admin] -> Show devices tree -> CM11A
# Create Child Device -> Pick device template -> ''take your pick'' (I added "Light Switch (on/off)")
# Device data -> Port/Channel Number -> ''HousecodeUnitcode'' -> '''save''' (codes range from "A1" to "P16", no seperator)

When you are done adding lights, you can continue with the setup wizzard to assign them to the proper rooms and give them names (she refers to ZWave devices and seems unable to actually controll the X10 devices in 1.1-RC1) Also you might have to "reload the router" before they actually work (orbiter screens will be also be regenerated), but they do work.

== Troubleshooting ==

===Reset CM11A Completely===
I had a terrible time getting my CM11A to work under LinuxMCE. After about 2 weeks of searching, i found a post on the internet [http://www.shed.com/ddt1.html here]. Basically, what it narrows down to is that whenever the interface is moved to a new PC, it may lock up. To clear this, unplug the serial cable from the CM11A, unplug the CM11A from the wall, and remove its batteries (they aren't even needed for how LinuxMCE uses the interface). Let it sit for at least 15 minutes, then hook it back up. (I have also read that some people had to let it sit overnight during this step)
After 2 weeks of frustration, everything works as it should now. If you are having problems getting your CM11A to work, i highly recommend doing this procedure.

===CM11A Disabled Periodically===
If you are finding that the CM11A device and its children (i.e. light switches, etc) are being disabled periodically, try connecting the CM11A to a different serial port. Doing so solved the disabling problem in [http://forum.linuxmce.org/index.php?topic=8238.msg54578#msg54578 this case].

===CM11A used behind a GC100===
If you use a GC100 to connect your CM11A further away from the computer, be sure to add the CM11A device under the CORE in the web admin, and not under the GC100. If you do so the devices will start but commands will not be passed down to the CM11A.

== See also ==
* Insteon [http://wiki.linuxmce.org/index.php/Insteon_-_Setting_Up_PLM_Template PLM] now supports bidirectional X10 communication.
* The older [[CM11A]] page, which appears to be more aimed at development.
* The pluto [http://plutohome.com/wiki/index.php/CM11A CM11A] page.
* The pluto [http://plutohome.com/wiki/index.php/Gc100 gc100] page for setup on the serial port of the gc100.
* An interesting comment about pluto with the CM11 [http://smart-home-blog.com/archives/726#comments] containing a workaround dealing with sensors and remotes.
* Discussions on the forum:
** [http://forum.linuxmce.org/index.php?topic=1762.msg8037#msg8037 Re: UK & Ireland Users]
** [http://forum.linuxmce.org/index.php?topic=1882.0 CM11]
** [http://forum.linuxmce.org/index.php?topic=1850.0 CM11g]

Everspring SM103

2010-02-03T22:30:43Z

Caiman: /* Status */

[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Security]]
[[Category: Works without caveats on 0810]]
[[Image:SM103-s.jpg|thumb|200px|SM103]]

= Status =
Tested with the latest svn Z-Wave driver (will be included in 0810).

Confirmed working with 0810-beta2 using the same procedure as [http://wiki.linuxmce.org/index.php/ACT_Homepro_Motion_Detector]

= About =
The Everspring SM103 is a battery powered Z-Wave door/window sensor. It uses a frequency of 868MHz. There is also a US version.

= Links =
http://www.everspring.com

[http://www.techstyleuk.co.uk/index_files/sm103.htm For sale at Techstyle UK Ltd.]

Everspring SM103

2010-02-03T22:30:24Z

Caiman:

[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Security]]
[[Category: Works without caveats on 0810]]
[[Image:SM103-s.jpg|thumb|200px|SM103]]

= Status =
Tested with the latest svn Z-Wave driver (will be included in 0810).
Confirmed working with 0810-beta2 using the same procedure as [http://wiki.linuxmce.org/index.php/ACT_Homepro_Motion_Detector]

= About =
The Everspring SM103 is a battery powered Z-Wave door/window sensor. It uses a frequency of 868MHz. There is also a US version.

= Links =
http://www.everspring.com

[http://www.techstyleuk.co.uk/index_files/sm103.htm For sale at Techstyle UK Ltd.]

Z-Wave Getting Started

2010-02-02T09:17:19Z

Caiman:

[[Category: ZWave]]
So you decided to expand your LMCE system and add some Home Automation to the mix? Well the goal for this page is to let you know what you are going to need to start with and give you ideas and options to expand on in the future.

=LMCE Interface=
You are going to need some kind of method for LMCE to control your Z-Wave installation. There are currently 2 different types of interfaces, both of which us a USB stick that plugs into the LMCE Core.

Here are the Choices:

==USB Stick without Controller==
This type of z-wave USB stick acts as an interface into the Z-Wave system only. It allows LMCE to have full control, however, you will need a seperate Z-Wave master controller(Required). A master controller can be used in addition to LMCE to control Z-Wave devices.

Some examples of these sticks are: 
[[Tricklestar_300ZW-US-W|US Tricklestar]] 
[[Tricklestar_300ZW-EU-W|EU Tricklestar]] 
[[Seluxit_viaSENS_Homecontroller|Seluxit viaSENS Homecontroller]] 
[[Intermatic_HA23C|Intermatic HA23C]] 

Make sure to check out each options individual page to see about any issues or problems you might have with the respective USB stick

==USB Stick with Controller==
This type of stick not only provides the interface to LMCE, it also acts as a Z-Wave master control. There is not a physical controller with buttons on the USB stick, but it is built in so an actual master controller is not needed.

Some examples of these sticks are: 
[[MCV_Z-Wave_Dongle|Mi Casa Verde USB + Inclusion Controller in one]]

Make sure to check out each options individual page to see about any issues or problems you might have with the respective USB stick

=Devices=
These are some of the devices that you will use around the house with your z-wave installation or to replace current devices as you build a new Z-Wave system or grow a current one.

Keep in mind this page is for simple options someone new to Z-Wave can use for refence on how they want to proceed with their home setup. If you are not sure or need more clarification, it is always best to check with a trained professional.

==Dimmers==
Dimmers function similar to a light switch, however they are not simply on or off. They also cover everything in between for ultimate light control. Generally, they will only work with incandescent lights and will not function with fluorescent or compact fluorescent bulbs.

The [[Intermatic_HA06C|Intermatic HA06C]] is an example of this.

Dimmer Switches can replace current dimmer switches in your house along with normal switches that control light fixtures.

Dimmer switches should not be used for replacing switches which control a cieling fan, fluorescent bulbs or an outlet receptacle.

==Switches==
Switches are a simple switch that is either On or Off

The [[Wayne_Dalton_HA18WD|Wayne Dalton HA18WD]] is an example of this.

Switches can replace any current switch in your home. Because they only offer On and Off control, they are best used to control fluorescent light fixtures, fixtures that include a cieling fan with lights operating on a single switch and switches that control an outlet receptacle.

For the best Z-Wave and LMCE experience, it is recommended to get a dimmer switch if replacing a fixture that support incandescent bulbs.

==Receptacles==
Receptacles are the outlets which you plug your stuff into.

Generally there is not a need to replace these but it can be useful for these needs:

* Turn the Receptacle on or of at specific time to conserver power
* If you do not have a permanent light fixture and a lamp is attached to this Receptacle.

If you currently have a switch controlling a Receptacle, it is not advised to replace the Receptacle with one of these unless you are eliminating the switch. Otherwise the switch will need to remain in the On position for the receptacle to operate correctly.

==Door Locks==

==Heating\Cooling Control==

==Setting associations==
The web interface allows you to create associations between devices (I believe this requires SIS mode, not sure).
Click "Show device tree" then navigate to your z-wave controller (under CORE) and select "Send command to device". A popup window will show and you can choose the "Set Association" command.
Enter three parameters:
* the zwave NodeID of the source device, the one that will send the command
* the group in the source device that will trigger the send (typically the button number on a multi-paddle switch)
* the NodeID(s) device(s)
Example: 5 / 2 / 7,8 would cause devices 7 and 8 to turn on when you press button 2 of device 5

Known Issues 0710 Beta4

2008-04-11T08:00:22Z

Caiman: Added link to CM11a i386 binaries

* "Failed to get IVTV video driver" message on status window on Orbiter. This is because IVTV package fails to install.This can probably be safely ignored as the IVTV driver is now built into the Linux kernel.

* VIA video support is a bit lame at the moment: Cursor leaves dandruff with OpenChrome drivers (fix is to enable SWCursor in xorg.conf, need to make default), MythTV menu text not always drawn with VIA proprietary drivers

* nVidia 7150 + and some 6150 and 7050 systems have high cpu problem. This causes high Xorg usage with MythTV + Xine, unless V-Sync disabled. On machines with SSE (most modern CPUs), the solution is to install nvidia drivers 169.12 and add
Option "UseEvents" "true"
to the video device section of the /etc/xorg.conf file. Then you can fully enable v-sync in nvidia-settings without drowning the CPU.

* Zwave children have the device data's and room reseted after reload router. A fixed was committed (svn rev #19914) in General Info Plugin for this. To fix this on your machine, follow the steps:
''- cd /usr/pluto/bin''

''- mv General_Info_Plugin.so General_Info_Plugin.so.orig''

''- wget -c ftp://builder32.linuxmce.com/Download/GIP-beta4-fix/i386/General_Info_Plugin.so '' (for i386)

''or''

''- wget -c ftp://builder32.linuxmce.com/Download/GIP-beta4-fix/x86_64/General_Info_Plugin.so '' (for amd64)

''- reload router''

* Sorting by genre, performed etc. doesn't work correctly. A fixed was committed (svn rev #19953) in Media Plugin for this. Also, now you can rip audio cd and play it in track order (the track number attribute will be attach to audio files). To fix this on your machine, follow the steps:

''- cd /usr/pluto/bin''

''- mv Media_Plugin.so Media_Plugin.so.orig''

''- wget -c ftp://builder32.linuxmce.com/Download/Media_Plugin-beta4-fix/i386/Media_Plugin.so '' (for i386)

''or''

''- wget -c ftp://builder32.linuxmce.com/Download/Media_Plugin-beta4-fix/x86_64/Media_Plugin.so '' (for amd64)

''- reload router''

* MythTV affects performance of system because of too verbose logging, sometimes even freezing. The fix was commited (svn rev #19965). To fix it on your machine, follow the steps

''- cd /usr/pluto/bin''

''- mv MythTV_Player MythTV_Player.orig''

''- wget -c ftp://builder32.linuxmce.com/Download/MythTV_Player-beta4-fix/i386/MythTV_Player '' (for i386)

''or''

''- wget -c ftp://builder32.linuxmce.com/Download/MythTV_Player-beta4-fix/x86_64/MythTV_Player '' (for amd64)

''- chmod +x MythTV_Player''

''- reload router''

* Asterisk/FreePBX (automatic) configuration seems to be broken. It fails to accept incoming calls, the following error is logged:
[Mar 6 23:11:25] WARNING[19471] pbx.c: Channel 'SIP/0878700000-081dffa8' sent into invalid extension '102' in context 'custom-linuxmce', but no invalid handler

* Support disked MD was dropped completely in 0710

* DVDs fail to play on the M/D but play OK on the Core.
This is caused by the bug in the mounting script which is fixed already in the SVN. See the instruction how to patch your M/Ds in this post: http://forum.linuxmce.org/index.php?topic=4585.msg27572#msg27572

* CM11A fixes:

'' - download TAR file for AMD64 - http://www.mediafire.com/?yl1mozw0p9r or [http://www.k-net.eu.org/lmce/cm11a-x86.tgz here for i386]

'' - copy libSerial to /usr/pluto/lib

'' - copy CM11A and Lighting_Plugin.so to /usr/pluto/bin

'''DO NOT FORGET BACKUP ORIGINAL FILES!'''

'' - reload router

ZWave API

2008-04-06T09:25:53Z

Caiman: /* Traces */ Info on decoding initialization data

[[Category: Hardware| ]]
[[Category: Automation]]
[[Category: ZWave]]
[[Category: Programmer's Guide]]

= Introduction =
The ZWave API is not available for free. You have to get the Zensys SDK for command specifications and device class definitions. This page tries to collect all the freely available information about ZWave. The final goal is to provide a header file with all necessary definitions for basic operation with open source software.

IMPORTANT: all information added to this page _must_ have a reference to the source where it came from.

= API =
== Frame specification ==
Karl Denning implemented basic ZWave support in his software "HomeDaemon". He advised that basic frame specification can be derived from his source code (http://www.intouchcontrolsforum.com/forums/showpost.php?s=e11a812b08256225ebb66a73d8f6d193&p=173&postcount=13).
== Basic Classes ==
From the Leviton Z-Wave RS232 ASCII Interface Programming Guide (RZC0P-1LW, 10/9/2007):
Controller 1
Static controller 2
Slave 3
Routing Slave 4
that leads us to some definitions:
#define OZA_BASIC_CLASS_CONTROLLER 0x01
#define OZA_BASIC_CLASS_STATIC_CONTROLLER 0x02
#define OZA_BASIC_CLASS_SLAVE 0x03
#define OZA_BASIC_CLASS_ROUTING_SLAVE 0x04

== Device Types ==
From the Z-Wave Configuration Information-1.pdf:
CONTROLLER 0x01 (like the ZTH200, Classes: )
SWITCH/APPLIANCE 0x10 (ZRP200, Classes: 25, 27, 75)
DIMMER 0x11 (ZDP200, ZDW230, .., Classes: 26, 27, 75, ...)
TRANSMITTER 0x12
THERMOSTAT 0x08
SHUTTER 0x09

== Command and Device classes ==
From the Electronic Solutions, Inc. DBMZ Advanced User manual:

=== Command/Device Classes ===
==== Basic Slave Device ====
==== All ====
==== Multilevel Switch ====
* COMMAND_CLASS_SWITCH_MULTILEVEL
MULTILEVEL_SWITCH_GET
MULTILEVEL_SWITCH_SET
MULTILEVEL_SWITCH_START_LEVEL_CHANGE
MULTILEVEL_SWITCH_STOP_LEVEL_CHANGE

additional information from http://zwaveworld.com/forum/index.php?showtopic=237:
>?FI003,017,000 //basic class 3 (slave), generic class 0x11 (multlevel switch), specific class 0

==== Basic ====
* COMMAND_CLASS_BASIC
BASIC_GET
BASIC_SET
==== Mandatory ====
==== Multilevel Sensor ====
(from the Vizia RF Application Note)
* COMMAND_CLASS_SENSOR_MULTILEVEL
example get:
>N4SE49,4 (RZC0P Syntax)
sensor report:
<N004:049,005,001,009,075
049: device class
005: command report
001: value send is a temperature value
009: value represented with 1 byte in degrees fahrenheit
075: 75° F
==== Manufacturer Specific ====
* COMMAND_CLASS_MANUFACTURER_SPECIFIC
Show the ESI product data:
MANUFACTURER_SPECIFIC_GET
Example return message:
0x00 0x33 0x52 0x50 0x30 0x32
0x00: maunfacturer id high byte
0x33: manufacturer id low byte, ID: 0x0033
Product type ID "RP"
Product ID "02"

==== Version ====
* COMMAND_CLASS_VERSION
VERSION_GET
Example return message:
0x04 0x02 0x06 0x01 0x01 0x5a
0x04: Library type 4 for basic slave device
0x02: Protocol version 2
0x06: Protocol sub version 6
0x01: Application version 1
0x01: Application sub version 1
0x5a: ?

==== All Switch ====
* COMMAND_CLASS_SWITCH_ALL
SWITCH_ALL_GET
SWITCH_ALL_ON
SWITCH_ALL_OFF
==== Configuration ====
* COMMAND_CLASS_CONFIGURATION
Each parameter is a single byte ("0" or "1")
CONFIGURATION_GET
CONFIGURATION_SET
==== Power Level ====
* COMMAND_CLASS_POWERLEVEL
POWERLEVEL_TEST_NODE_SET
POWERLEVEL_TEST_NODE_GET
POWERLEVEL_TEST_NODE_REPORT
Example: POWERLEVEL_SET, 5, 60
set the ZWave node's power level to 5 for the length of 60 seconds

== Device configuration data ==
= Traces =
Starting the ZWave device:
<pre>
40 03/28/08 15:53:34.590 0x1 0x3 0x0 0x15 0xe9 (#####) <0xb698bb90>
41 03/28/08 15:53:34.741 0x6 0x1 0x10 0x1 0x15 0x5a 0x2d 0x57 0x61 0x76 0x65 0x20 0x32 0x2e 0x33 0x31 0x0 0x1 0x96 (#####Z-Wave 2.31###) <0xb718cb90>
40 03/28/08 15:53:34.792 0x1 0x3 0x0 0x20 0xdc (### #) <0xb698bb90>
41 03/28/08 15:53:35.042 0x6 0x1 0x8 0x1 0x20 0x0 0x0 0x55 0x28 0x2 0xa9 (#### ##U(##) <0xb718cb90>
40 03/28/08 15:53:35.092 0x1 0x3 0x0 0x2 0xfe (#####) <0xb698bb90>
41 03/28/08 15:53:35.342 0x6 0x1 0x25 0x1 0x2 0x4 0x4 0x1d 0x3 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x2 0x1 0xc4 (##%#) <0xb718cb90>
40 03/28/08 15:53:35.393 0x1 0x4 0x0 0x52 0x1 0xa8 (###R##) <0xb698bb90>
41 03/28/08 15:53:35.643 0x6 0x1 0x4 0x1 0x52 0x1 0xa9 (####R##) <0xb718cb90>
40 03/28/08 15:53:35.694 0x1 0x3 0x0 0x56 0xaa (###V#) <0xb698bb90>
41 03/28/08 15:53:35.944 0x6 0x1 0x4 0x1 0x56 0x0 0xac (####V##) <0xb718cb90>
40 03/28/08 15:53:35.995 0x1 0x4 0x0 0x41 0x1 0xbb (###A##) <0xb698bb90>
41 03/28/08 15:53:36.245 0x6 0x1 0x9 0x1 0x41 0xc9 0x0 0x0 0x3 0x11 0x0 0x6d (####A######m) <0xb718cb90>
40 03/28/08 15:53:36.296 0x1 0x4 0x0 0x41 0x2 0xb8 (###A##) <0xb698bb90>
41 03/28/08 15:53:36.545 0x6 0x1 0x9 0x1 0x41 0xd2 0x6 0x0 0x2 0x2 0x0 0x62 (####A######b) <0xb718cb90>
</pre>
Interesting string:
0x1 0x2 0x4 0x4 0x1d 0x3 0x0 0x0 0x0 ...
0x1 means it is a response
0x2 means it is initialization data
0x4 is the version
0x4 is the capabilities
LMCE will look for the next 4 bytes to get the list of devices. It seems to be a bit map. In this case, the first byte is 0x3 or in binary 00000011 so devices ID 1 and 2 are present. It is unclear to me why we only look at 4 bytes (32 zwave devices) while the protocol supports 252

Switching on a ZDP200 lamp plug from the Orbiter:
<pre>
40 03/28/08 15:49:20.707 0x1 0xa 0x0 0x13 0x1 0x3 0x26 0x1 0x63 0x5 0x6 0xa3 (#\n####&#c###) <0xb68f3b90>
41 03/28/08 15:49:21.007 0x6 0x1 0x4 0x1 0x13 0x1 0xe8 (#######) <0xb70f4b90>
41 03/28/08 15:49:21.307 0x1 0x5 0x0 0x13 0x6 0x0 0xef (#######) <0xb70f4b90>
</pre>

Pressing "all units on" on the ZTH200:
<pre>
41 03/28/08 15:50:58.553 0x1 0x8 0x0 0x4 0x4 0xef 0x2 0x27 0x4 0x39 (#######'#9) <0xb70f4b90>
41 03/28/08 15:50:58.854 0x1 0x8 0x0 0x4 0x0 0xef 0x2 0x27 0x4 0x3d (#######'#=) <0xb70f4b90>
</pre>

Pressing "all units off" on the ZTH200:
<pre>
41 03/28/08 15:51:43.713 0x1 0x8 0x0 0x4 0x4 0xef 0x2 0x27 0x5 0x38 (#######'#8) <0xb70f4b90>
41 03/28/08 15:51:44.014 0x1 0x8 0x0 0x4 0x0 0xef 0x2 0x27 0x5 0x3c (#######'#<) <0xb70f4b90>
</pre>

Pressing the local switch on the ZDP200 (toggling from off to on):
<pre>
41 03/28/08 15:52:37.284 0x1 0xc 0x0 0x49 0x84 0x1 0x6 0x3 0x11 0x0 0x26 0x27 0x75 0x5f (###I######&'u_) <0xb70f4b90>
</pre>

= References =
http://www.basshome.com/leviton_z-wave_documentation_1970_ctg.htm

http://zwaveworld.com/forum/index.php?showtopic=237

http://www.eilhk.com/en/product/Datasheet/Zensys/SDS10243-2%20-%20Z-Wave%20Protocol%20Overview.pdf

or

http://www.smarthus.info/support/download/zwave/Z-Wave%20Protocol%20Overview.pdf

http://www.eilhk.com/en/product/Datasheet/Zensys/INS10244-3%20-%20Z-Wave%20Node%20Type%20Overview%20and%20Network%20Installation%20Guide.pdf

or

http://www.smarthus.info/support/download/zwave/Z-Wave%20Node%20Type%20Overview%20and%20Network.pdf

http://www.smarthus.info/support/download/zwave/Z-Wave%20Configuration%20Information.pdf

http://www.ddj.com/embedded/193104353

= Tools used =
http://sourceforge.net/projects/slsnif/

= Links =

http://www.intouchcontrolsforum.com/forums/showthread.php?t=41&page=2

http://www.elec-solutions.com/docs/motor_controls/dbmz/DBMZ_v1+1_Advanced_User_Manual.pdf

http://zwaveworld.com/forum/index.php?showtopic=227&st=20

http://www.denninger.net/homedaemon.htm

http://forums.controlthink.com/

GlobalCache GC-100

2008-03-30T15:22:59Z

Caiman: /* Serial Port */ Removed info to modify gc100-serial-bridge.sh because the patch is already in 0710 beta 4

{| align="right"
| __TOC__
|}
[[Category: Hardware]]
[[Category: Automation]]
[[Category: Infrared]]

[[Image:GC100.jpg|right]]

GC100 is a device which allows you to have remote connection almost anywhere. It's a network device which will forward all your data to :
* couple of serial ports
* [[IR]] senders and/or sensors
* several relays
For more details about the product check [http://www.globalcache.com/products/gc-index.html manufacturer web site].

== Send IR codes ==
LinuxMCE implementation of GC100 assumes that in device tree we'll have children and the messages are actually addressed to them instead of GC100 itself.

So when you are sending "ON" to TV controlled by GC100, the message is routed to the GC100, it finds [[infrared]] code for "ON" for that specific TV, sends a command to gc100 to send a specific [[infrared]] sequence, which will blink IR sender connected to specific port, and the TV will turn on.

The only two commands that GC100 implements itself are : '''CMD_Send_Code''' used to test which IR is suitable for your equipment and '''CMD_Learn_IR''' used to learn new IR codes.

== Learn IR codes ==
The learning device is actually unrelated to GC100. It may be plugged into one of GC100's serial ports (don't forget to set them to 9600 bps), or in regular serial port, just be sure you specified right port in GC100 device data.

There are several other devices that support learning of infrared codes : [[IRTrans]], [[Tira]], [[USB_UIRT]].

Learning is done from [[LinuxMCE-admin|web page]]. When clicking "Learn" gc100 will start a thread that will try to get data from the port. If nothing is received in 30 seconds the thread will die. The page will continue to refresh trying to see if anything was added, but after 30 seconds it's useless.

== Sensors ==
The gc100 jacks are by default configured as IR transmitters, but they can be configured to function as sensors. The sensors are, in their most basic form, two wires connected to a jack plug. When you cross them, a "sensor tripped" event is emitted. I am not currently aware of how this is supposed to function, who will intercept the event and how will it react to it. One idea for using a sensor is attaching a doorbell button to it, which, when pressed, will notify you in some way.

You must go into the gc100's web panel and set the input jack to 'sensor w/ auto notify' to use an i/r jack for a sensor.

== How to ==
=== Install ===
The device is not quite [[plug&play]]. You have to perform a factory reset and to add it from orbiter ("Add GC100" button).

A script will do some tricks with IP, will submit some pages on GC100's interface and so on. It will install needed software and after that it should say that device is ready to use (don't forget to [[quickreload]])

=== Before the first use ===
* Insert proper wires in relays, devices in serial ports, [[IR]] LEDs and/or sensors.
* Go to device's webpage and set proper inputs/outputs, baud rates and so on.
* Add child devices in [[LinuxMCE-admin]] webpage and set proper device data to match the wiring.

This should do it.

=== Changes in LinuxMCE 0710 beta 4 ===
The way the gc100 is configured in the database changes in LinuxMCE 0710 beta 4. If you are upgrading from a previous release and have a gc100 set up, you will have to reconfigure it.

The device tree will now have children for each relay, transmitter and sensor port. These are autodetected depending on the settings made to the gc100 itself and updated as the settings change.

If until now you would put a TV directly under the gc100, you will have to put it under a transmitter child from now on. This will tell the gc100 which port to use to send the code, instead of sending it using all available transmitters like it did until now. This will allow you to add more IR devices which use the same codes without stepping on each other's toes, since the IR codes will be routed just to the target device. The old functionality is still in place and you can still add a TV directly under the gc100, but make sure you mark the checkbox that says "Don't autoconfigure" if you don't want the gc100 to manage its children, so your device remains in its place.

This is also true for relays. Add your lights, or other devices that support On and Off commands, under the relay children. The On and Off commands will be routed to the right relay this way.

=== Known Problems ===

==== MAC detection ====

--[[User:Nite man|Nite man]] 06:03, 25 January 2008 (PST) To solve the MAC detection problem replace the function ''get_gc100mac()'' in the script ''/usr/pluto/bin/gc100-conf.pl'' by new one below:

sub get_gc100mac {
my($mac, $page, $ret);

`curl http://192.168.1.70/Commands.cgi -o gc100mac1 --silent`;
`curl http://192.168.1.101/Commands.cgi -o gc100mac2 --silent`;

open FILE, "gc100mac1";
$ret = read FILE, $page, -s "gc100mac1";
close FILE;

unless($page) {
open FILE, "gc100mac2";
$ret = read FILE, $page, -s "gc100mac2";
close FILE;
}

($mac) = $page =~ /((?:[\dA-F]{2}-){5}[\dA-F]{2})/i;

if($mac) {
$mac =~ tr/\-/\:/;
loggc("Mac Found $mac\n");
system "rm -f gc100mac1 gc100mac2";
return $mac;
} else { exit 1 }

}

or apply that [[http://smart-home-blog.com/wp-content/plugins/wp-downloadMonitor/download.php?id=18 gc100-conf.pl.patch]]

Currently the support for the gc100 in LinuxMCE is broken, at least for some models or firmware versions. The ''/usr/pluto/bin/gc100-conf.pl'' script is for some reason unable to determine the gc100's MAC Adress after it has been reset to factory defaults. As a result it is only half configured and not added to the system properly.

The only known workaround [http://smart-home-blog.com/archives/688] [http://forum.linuxmce.org/index.php?topic=1990.msg9161#msg9161] at this time is to manually edit the perl script, and hardcode the MAC address of your gc100. In short, find this line in the script:
sub get_gc100mac {
Then insert this line immediately following it (replace ''00:00:00:00:00:00'' with the adress of your gc100):
'''return "''00:00:00:00:00:00''";'''
As a result it should look something like this now:
exit(4);
}
}

sub get_gc100mac {

'''return "''00:00:00:00:00:00''"''';

`curl <nowiki>http://192.168.1.70/Commands.cgi</nowiki> -o gc100mac1 --silent`;
`curl <nowiki>http://192.168.1.101/Commands.cgi</nowiki> -o gc100mac2 --silent`;
open(FILE,"gc100mac1");
@data1 = <FILE>;
close(FILE);

Reset the gc100 to factory defaults if necessary and you should be able to add it from an orbiter as described above.

Another possible workaround ''might'' be described on the [http://plutohome.com/wiki/index.php/Gc100 Plutohome wiki for the gc100], under '''Complete Manual Install'''.

Firmware versions known to be affected:
* 2.4-06 (GC100-06)

==== Serial Port ====

Previous problems in the gc100-serial-bridge.sh script were fixed in 0710 beta4.

The GC100 serial port needs to be setup for 4800 bauds.

In some cases the gc100 may respond with "configuration is locked". If that happens, you need to re-configure the gc100 manually from factory defaults. In the /usr/pluto/bin/gc100-conf.pl, modify the wget call in the "sub configure_webgc" function to add parameter "Y=0" which means "do not lock config":
sub configure_webgc {
$local_ip = shift;
system("wget -q -T 3 --read-timeout=4 -t 1 \"http://192.168.1.70/commands.cgi?2=$local_ip&3=255.255.255.0&4=$gw$Y=0&7=submit\"");
system("wget -q -T 3 --read-timeout=4 -t 1 \"http://192.168.1.101/commands.cgi?2=$local_ip&3=255.255.255.0&4=$gw&Y=0&7=submit\"");
}
or if you do it all manually from the command line:
wget -q -T 3 --read-timeout=4 -t 1 "http://192.168.1.70/commands.cgi?2=192.168.80.23&3=255.255.255.0&4=192.168.80.1&Y=0&7=submit"
and adapt to the desired IP address.

You can now edit the port speed with the browser. If your browser hangs when you submit, you can use this the following wget call instead:
wget -q -T 3 --read-timeout=4 -t 1 "http://192.168.80.23/serial.cgi?C=1&B=5&F=0&A=submit"

==== Firmware version 3.0 and later ====

gc100 with firmware version 3.0 and later is Plug&Play, but not yet supported as such by LinuxMCE. It implements a DHCP client and also has a discovery beacon. Because it is able to get an IP address from the DHCP server, you won't be able to add it using the manual method describe here when using a default installation. You either have to use the completely manual installation procedure described on the [http://plutohome.com/wiki/index.php/Gc100#Complete_Manual_Install Plutohome Wiki for gc100], if you know what IP address the DHCP server gave it, or temporarily disable the DHCP server on the core (write down the DHCP settings, because they are erased from the database when you disable the DHCP server from Pluto-Admin - you can also /etc/init.d/dhcp3-server stop, add the gc100 and /etc/init.d/dhcp3-server start, without erasing the database).

== Implementation details ==
In ''gc100.cpp'' there is a lot of code for format conversion and other stuff. Practically it's not a big deal it receives a command, find a proper IR sequence and sends it to gc100.

==== Operating the relays, IR transmitters, and sensors ====
The gc100 software architecture uses two threads to communicate with the gc100 regarding relays, IR transmitters and sensors, one for sending messages (SocketThread) and one for receiving (EventThread). The reason for this is that the gc100 protocol isn't completely a request-reply protocol, even if it seems like that at first. The gc100 can initiate a transmission when a sensor is tripped, enough to break the request-reply paradigm. The program was designed to treat the communication as asynchronous. Messages are sent to the device without expecting a reply, and the replies are treated as independent events and state change reports, without linking a request to a reply in the program logic (except for the initialization phase).

GlobalCache GC-100

2008-03-30T15:15:07Z

Caiman: /* Serial Port */ added info to change serial port speed

{| align="right"
| __TOC__
|}
[[Category: Hardware]]
[[Category: Automation]]
[[Category: Infrared]]

[[Image:GC100.jpg|right]]

GC100 is a device which allows you to have remote connection almost anywhere. It's a network device which will forward all your data to :
* couple of serial ports
* [[IR]] senders and/or sensors
* several relays
For more details about the product check [http://www.globalcache.com/products/gc-index.html manufacturer web site].

== Send IR codes ==
LinuxMCE implementation of GC100 assumes that in device tree we'll have children and the messages are actually addressed to them instead of GC100 itself.

So when you are sending "ON" to TV controlled by GC100, the message is routed to the GC100, it finds [[infrared]] code for "ON" for that specific TV, sends a command to gc100 to send a specific [[infrared]] sequence, which will blink IR sender connected to specific port, and the TV will turn on.

The only two commands that GC100 implements itself are : '''CMD_Send_Code''' used to test which IR is suitable for your equipment and '''CMD_Learn_IR''' used to learn new IR codes.

== Learn IR codes ==
The learning device is actually unrelated to GC100. It may be plugged into one of GC100's serial ports (don't forget to set them to 9600 bps), or in regular serial port, just be sure you specified right port in GC100 device data.

There are several other devices that support learning of infrared codes : [[IRTrans]], [[Tira]], [[USB_UIRT]].

Learning is done from [[LinuxMCE-admin|web page]]. When clicking "Learn" gc100 will start a thread that will try to get data from the port. If nothing is received in 30 seconds the thread will die. The page will continue to refresh trying to see if anything was added, but after 30 seconds it's useless.

== Sensors ==
The gc100 jacks are by default configured as IR transmitters, but they can be configured to function as sensors. The sensors are, in their most basic form, two wires connected to a jack plug. When you cross them, a "sensor tripped" event is emitted. I am not currently aware of how this is supposed to function, who will intercept the event and how will it react to it. One idea for using a sensor is attaching a doorbell button to it, which, when pressed, will notify you in some way.

You must go into the gc100's web panel and set the input jack to 'sensor w/ auto notify' to use an i/r jack for a sensor.

== How to ==
=== Install ===
The device is not quite [[plug&play]]. You have to perform a factory reset and to add it from orbiter ("Add GC100" button).

A script will do some tricks with IP, will submit some pages on GC100's interface and so on. It will install needed software and after that it should say that device is ready to use (don't forget to [[quickreload]])

=== Before the first use ===
* Insert proper wires in relays, devices in serial ports, [[IR]] LEDs and/or sensors.
* Go to device's webpage and set proper inputs/outputs, baud rates and so on.
* Add child devices in [[LinuxMCE-admin]] webpage and set proper device data to match the wiring.

This should do it.

=== Changes in LinuxMCE 0710 beta 4 ===
The way the gc100 is configured in the database changes in LinuxMCE 0710 beta 4. If you are upgrading from a previous release and have a gc100 set up, you will have to reconfigure it.

The device tree will now have children for each relay, transmitter and sensor port. These are autodetected depending on the settings made to the gc100 itself and updated as the settings change.

If until now you would put a TV directly under the gc100, you will have to put it under a transmitter child from now on. This will tell the gc100 which port to use to send the code, instead of sending it using all available transmitters like it did until now. This will allow you to add more IR devices which use the same codes without stepping on each other's toes, since the IR codes will be routed just to the target device. The old functionality is still in place and you can still add a TV directly under the gc100, but make sure you mark the checkbox that says "Don't autoconfigure" if you don't want the gc100 to manage its children, so your device remains in its place.

This is also true for relays. Add your lights, or other devices that support On and Off commands, under the relay children. The On and Off commands will be routed to the right relay this way.

=== Known Problems ===

==== MAC detection ====

--[[User:Nite man|Nite man]] 06:03, 25 January 2008 (PST) To solve the MAC detection problem replace the function ''get_gc100mac()'' in the script ''/usr/pluto/bin/gc100-conf.pl'' by new one below:

sub get_gc100mac {
my($mac, $page, $ret);

`curl http://192.168.1.70/Commands.cgi -o gc100mac1 --silent`;
`curl http://192.168.1.101/Commands.cgi -o gc100mac2 --silent`;

open FILE, "gc100mac1";
$ret = read FILE, $page, -s "gc100mac1";
close FILE;

unless($page) {
open FILE, "gc100mac2";
$ret = read FILE, $page, -s "gc100mac2";
close FILE;
}

($mac) = $page =~ /((?:[\dA-F]{2}-){5}[\dA-F]{2})/i;

if($mac) {
$mac =~ tr/\-/\:/;
loggc("Mac Found $mac\n");
system "rm -f gc100mac1 gc100mac2";
return $mac;
} else { exit 1 }

}

or apply that [[http://smart-home-blog.com/wp-content/plugins/wp-downloadMonitor/download.php?id=18 gc100-conf.pl.patch]]

Currently the support for the gc100 in LinuxMCE is broken, at least for some models or firmware versions. The ''/usr/pluto/bin/gc100-conf.pl'' script is for some reason unable to determine the gc100's MAC Adress after it has been reset to factory defaults. As a result it is only half configured and not added to the system properly.

The only known workaround [http://smart-home-blog.com/archives/688] [http://forum.linuxmce.org/index.php?topic=1990.msg9161#msg9161] at this time is to manually edit the perl script, and hardcode the MAC address of your gc100. In short, find this line in the script:
sub get_gc100mac {
Then insert this line immediately following it (replace ''00:00:00:00:00:00'' with the adress of your gc100):
'''return "''00:00:00:00:00:00''";'''
As a result it should look something like this now:
exit(4);
}
}

sub get_gc100mac {

'''return "''00:00:00:00:00:00''"''';

`curl <nowiki>http://192.168.1.70/Commands.cgi</nowiki> -o gc100mac1 --silent`;
`curl <nowiki>http://192.168.1.101/Commands.cgi</nowiki> -o gc100mac2 --silent`;
open(FILE,"gc100mac1");
@data1 = <FILE>;
close(FILE);

Reset the gc100 to factory defaults if necessary and you should be able to add it from an orbiter as described above.

Another possible workaround ''might'' be described on the [http://plutohome.com/wiki/index.php/Gc100 Plutohome wiki for the gc100], under '''Complete Manual Install'''.

Firmware versions known to be affected:
* 2.4-06 (GC100-06)

==== Serial Port ====

The GC100's serial port does not work under LinuxMCE without a small modification, see: [http://forum.linuxmce.org/index.php?topic=2161.msg10140#msg10140 Re: GC100 + CM11 setup]

The following commands should correct this issue (and make a backup copy just in case):
mv /usr/pluto/bin/gc100-serial-bridge.sh /usr/pluto/bin/gc100-serial-bridge.sh.backup
sed -e 's/false/0/g' /usr/pluto/bin/gc100-serial-bridge.sh.backup >/usr/pluto/bin/gc100-serial-bridge.sh

It basicly replaces '''false''' with '''0''' in the ''/usr/pluto/bin/gc100-serial-bridge.sh'' file. Afterwards a reboot may be in order.

The GC100 serial port also needs to be setup for 4800 bauds.

In some cases the gc100 may respond with "configuration is locked". If that happens, you need to re-configure the gc100 manually from factory defaults. In the /usr/pluto/bin/gc100-conf.pl, modify the wget call in the "sub configure_webgc" function to add parameter "Y=0" which means "do not lock config":
sub configure_webgc {
$local_ip = shift;
system("wget -q -T 3 --read-timeout=4 -t 1 \"http://192.168.1.70/commands.cgi?2=$local_ip&3=255.255.255.0&4=$gw$Y=0&7=submit\"");
system("wget -q -T 3 --read-timeout=4 -t 1 \"http://192.168.1.101/commands.cgi?2=$local_ip&3=255.255.255.0&4=$gw&Y=0&7=submit\"");
}
or if you do it all manually from the command line:
wget -q -T 3 --read-timeout=4 -t 1 "http://192.168.1.70/commands.cgi?2=192.168.80.23&3=255.255.255.0&4=192.168.80.1&Y=0&7=submit"
and adapt to the desired IP address.

You can now edit the port speed with the browser. If your browser hangs when you submit, you can use this the following wget call instead:
wget -q -T 3 --read-timeout=4 -t 1 "http://192.168.80.23/serial.cgi?C=1&B=5&F=0&A=submit"

==== Firmware version 3.0 and later ====

gc100 with firmware version 3.0 and later is Plug&Play, but not yet supported as such by LinuxMCE. It implements a DHCP client and also has a discovery beacon. Because it is able to get an IP address from the DHCP server, you won't be able to add it using the manual method describe here when using a default installation. You either have to use the completely manual installation procedure described on the [http://plutohome.com/wiki/index.php/Gc100#Complete_Manual_Install Plutohome Wiki for gc100], if you know what IP address the DHCP server gave it, or temporarily disable the DHCP server on the core (write down the DHCP settings, because they are erased from the database when you disable the DHCP server from Pluto-Admin - you can also /etc/init.d/dhcp3-server stop, add the gc100 and /etc/init.d/dhcp3-server start, without erasing the database).

== Implementation details ==
In ''gc100.cpp'' there is a lot of code for format conversion and other stuff. Practically it's not a big deal it receives a command, find a proper IR sequence and sends it to gc100.

==== Operating the relays, IR transmitters, and sensors ====
The gc100 software architecture uses two threads to communicate with the gc100 regarding relays, IR transmitters and sensors, one for sending messages (SocketThread) and one for receiving (EventThread). The reason for this is that the gc100 protocol isn't completely a request-reply protocol, even if it seems like that at first. The gc100 can initiate a transmission when a sensor is tripped, enough to break the request-reply paradigm. The program was designed to treat the communication as asynchronous. Messages are sent to the device without expecting a reply, and the replies are treated as independent events and state change reports, without linking a request to a reply in the program logic (except for the initialization phase).

EIB/KNX

2007-09-28T08:15:04Z

Caiman:

KNX (EIB) is a standardised (EN 50090,ISO/IEC 14543), OSI-based network communications protocol for intelligent buildings. KNX is the successor to, and convergence of, three previous standards: the European Home Systems Protocol (EHS), BatiBUS, and the European Installation Bus (EIB).

The KNX standard is administered by the Konnex Association. [http://www.konnex.org konnex.org]

== How to install and use EIB ==

Connect your Core-Server with a serial cable to the EIB. Your BUS Connector has to have the FT1.2Protocol. (like [http://www.eibmarkt.com/cgi-bin/eibmarkt.storefront/46f9364200e19a48274450f3362b0652/Product/View/N434019 this]). You can use it from any Company (Gira, Berker, Siemens, ... ) but it is very important to have the correct protocol. (I bought the wrong one).
When you have connect it you have to add the EIB Interface in the WebAdmin. Go to Devices-->Interface and choose EIB, select the correct COM-Port, do a reload - router and you are ready to use it.
You can also go in a console and look into the log file (DeviceID_EIB.log) to see if everything works fine.

== How to add devices ==

In the Webadmin you have on the left side new menu buttons for Lights, Drapes, Sensors and Thermostats. At first you have to add the groupadresses. You have to upload a file with the correct information about your System. The format is:

<pre>
"LichtARschalt"/"0"/"0"/"1"
"Licht-SZ-schalt"/"0"/"0"/"10"
"Licht-SZ-dimm"/"0"/"0"/"11"
"Licht-SZ-wert"/"0"/"0"/"12"
</pre>

=== Lights ===

Goto EIB Lights on the Webadmin. Give the Name of your Light and choose if it is dimmable or not. Click on the "Pick" Button -> choose the correct groupaddress for on/off and dim. In Webadmin->Lights you can add the room and type of your light. After that you can put the EIB light on the floorplan.

=== Thermostats ===

In my house the thermostats have two states (cold and warm). I don't want to change the temperature with LinuxMCE, i only want to turn on and off the heating. When the temperature is reached the EIB turns off the heating by itself.
So, what did i do?
At first i allowed my thermostat to change the state (on/off) by the bus and gave it a groupaddress (like 2/0/10)
I go to the Webadmin->Scenarios->Climate and create for every room two scenarios (on and off). Then go to the Webadmin->Advanced->Configuration->Scenarios-Climate and choose the first Scenario. Add the EIB Device and the Command EIB_Write.
Now you have to insert the groupaddress, data string and data type. Insert the groupaddress (2/0/10), the data string (1=on, 2=off) and for the data type put 6 in the field. Press save and you can test it.

This is a lot of work, but so you can write a very small php-page to execute one of the scenarios. That's very comfortable because you can turn on and off the heating from anywhere with the browser of a mobile phone.

=== Drapes ===

It's the same as the thermostats. I don't use the EIB-Drapes, I create my own scenarios and send the commands with EIB_Write to the bus. This works very well.

=== Sensors ===

I don't really have sensors. I only tried to create a sensor that is a light-switch. Every time I turn on the light the sensor was tripped and the Commands were executed.

== Problems ==

=== How to send the Time on the bus? ===

I want to send the system time of the server every ten minutes to the bus. The reason is, the internal clocks of the thermostats don't have a real clock, so they need the correct time/date every hour to synchronize.
Has anyone tried this???

=== Can't read from the bus ===

I want to read data from the bus. Like how warm is it in the rooms or is a light on or off.
I think this function isn't implemented yet... I will try to implement it, but i don't know how to build a working development system.

EIB/KNX

2007-09-28T08:14:40Z

Caiman:

KNX (EIB) is a standardised (EN 50090,ISO/IEC 14543), OSI-based network communications protocol for intelligent buildings. KNX is the successor to, and convergence of, three previous standards: the European Home Systems Protocol (EHS), BatiBUS, and the European Installation Bus (EIB).

The KNX standard is administered by the Konnex Association. [http://www.konnex.org konnex.org]

== How to install and use EIB ==

Connect your Core-Server with a serial cable to the EIB. Your BUS Connector has to have the FT1.2Protocol. (like [http://www.eibmarkt.com/cgi-bin/eibmarkt.storefront/46f9364200e19a48274450f3362b0652/Product/View/N434019 this]. You can use it from any Company (Gira, Berker, Siemens, ... ) but it is very important to have the correct protocol. (I bought the wrong one).
When you have connect it you have to add the EIB Interface in the WebAdmin. Go to Devices-->Interface and choose EIB, select the correct COM-Port, do a reload - router and you are ready to use it.
You can also go in a console and look into the log file (DeviceID_EIB.log) to see if everything works fine.

== How to add devices ==

In the Webadmin you have on the left side new menu buttons for Lights, Drapes, Sensors and Thermostats. At first you have to add the groupadresses. You have to upload a file with the correct information about your System. The format is:

<pre>
"LichtARschalt"/"0"/"0"/"1"
"Licht-SZ-schalt"/"0"/"0"/"10"
"Licht-SZ-dimm"/"0"/"0"/"11"
"Licht-SZ-wert"/"0"/"0"/"12"
</pre>

=== Lights ===

Goto EIB Lights on the Webadmin. Give the Name of your Light and choose if it is dimmable or not. Click on the "Pick" Button -> choose the correct groupaddress for on/off and dim. In Webadmin->Lights you can add the room and type of your light. After that you can put the EIB light on the floorplan.

=== Thermostats ===

In my house the thermostats have two states (cold and warm). I don't want to change the temperature with LinuxMCE, i only want to turn on and off the heating. When the temperature is reached the EIB turns off the heating by itself.
So, what did i do?
At first i allowed my thermostat to change the state (on/off) by the bus and gave it a groupaddress (like 2/0/10)
I go to the Webadmin->Scenarios->Climate and create for every room two scenarios (on and off). Then go to the Webadmin->Advanced->Configuration->Scenarios-Climate and choose the first Scenario. Add the EIB Device and the Command EIB_Write.
Now you have to insert the groupaddress, data string and data type. Insert the groupaddress (2/0/10), the data string (1=on, 2=off) and for the data type put 6 in the field. Press save and you can test it.

This is a lot of work, but so you can write a very small php-page to execute one of the scenarios. That's very comfortable because you can turn on and off the heating from anywhere with the browser of a mobile phone.

=== Drapes ===

It's the same as the thermostats. I don't use the EIB-Drapes, I create my own scenarios and send the commands with EIB_Write to the bus. This works very well.

=== Sensors ===

I don't really have sensors. I only tried to create a sensor that is a light-switch. Every time I turn on the light the sensor was tripped and the Commands were executed.

== Problems ==

=== How to send the Time on the bus? ===

I want to send the system time of the server every ten minutes to the bus. The reason is, the internal clocks of the thermostats don't have a real clock, so they need the correct time/date every hour to synchronize.
Has anyone tried this???

=== Can't read from the bus ===

I want to read data from the bus. Like how warm is it in the rooms or is a light on or off.
I think this function isn't implemented yet... I will try to implement it, but i don't know how to build a working development system.