LinuxMCE - User contributions [en]

Converting Philips RC-5 to Pronto

2009-07-25T20:21:01Z

DomoDude:

If you haven't done so already, you may want to read up on [[Learning/typing my own code]].

When your device uses '''Philips RC-5''' codes for its infrared commands from the remote control, you'll find that these codes cannot be directly used in the LinuxMCE templates. What is needed, are Pronto codes. Specifically, Pronto codes that start with 0000. You may be able to find other pronto codes for your device, but the infrared transmitter code in LMCE can only do the 0000 (raw) sequences.

As an example, I have an Arcam amplifier which uses ''system code'' 16, and e.g. ''command code'' 123 to turn it on. To convert RC5 16-123 to raw pronto, it is possible to use a small utility called IRCodeDoctor (http://www.ir-toolkit.com). Simply execute it with
"java -jar IRCodeDoctor.jar". You'll get a small window. Right-click in the "IR-Code" field, and select'' New Code -> RC5''. Enter your system and command codes, and you will end up with a Pronto code "5000 0073 0000 0001 0010 007B". However, the first 4 digits are 5000, not 0000! Make sure you right click again in that window, and click ''Convert to RAW''. Click ''OK'' in the popup about the Toggle bit, it does not need to be set. The Pronto code will then change to the raw Pronto code "0000 0073 0000 000B 0040 0020 0020 0040 0040 0020 0020 0020 0020 0020 0020 0040 0020 0020 0020 0020 0040 0040 0020 0020 0020 0CC0". Note that it starts with 0000, so you're in business! Select all, copy, and paste it in your ''Type code manually'' field.

If you want to manually extend the duration of the emitted IR code, take a look at [[Extending the repeat duration of raw Pronto IR codes]]

Refer to the LinuxMCE [[AV Properties]] and [[IR/GSD codes syncronization]].

[[Category:Infrared]]

Extending the repeat duration of raw Pronto IR codes

2009-05-12T14:56:49Z

DomoDude:

Sometimes, a device does not react to an IR command because the duration of the code is too short. For example, a standard Pronto code to turn my Panasonic plasma TV on does not work. When I push the button on the remote, it ''does'' work, but I need to keep the button pressed for a fairly long time.
It would be nice to simulate that in the raw Pronto code.

Here's how it worked for me.

The first few words of the code (each consisting of 4 hexadecimal digits) say something about the following code. The first word, for example, should always be 0000 (pronto format: raw).
The third word contains the number of word pairs that are sent only once, and the fourth word contains the number of word pairs that are repeated.

My ON command for the Panasonic was this:
0000 0071 0000 0048 0080 003F 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0030 0010 0AAB

It did not work because it was too short. All that is needed is a change in the fourth word, just doubling it:

0000 0071 0000 '''0048''' ---> 0000 0071 0000 '''0096'''

and then copy/paste the remaining words (each pair of those indicates an on/off timing). This eventually gives

0000 0071 0000 '''0096''' 0080 003F 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0030 0010 0AAB 0080 003F 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0030 0010 0AAB

And presto! The ON signal is transmitted twice as long now, and my TV turns on.

Converting Philips RC-5 to Pronto

2009-05-12T09:49:44Z

DomoDude:

If you haven't done so already, you may want to read up on [[Learning/typing my own code]].

When your device uses '''Philips RC-5''' codes for its infrared commands from the remote control, you'll find that these codes cannot be directly used in the LinuxMCE templates. What is needed, are Pronto codes. Specifically, Pronto codes that start with 0000. You may be able to find other pronto codes for your device, but the infrared transmitter code in LMCE can only do the 0000 (raw) sequences.

As an example, I have an Arcam amplifier which uses ''system code'' 16, and e.g. ''command code'' 123 to turn it on. To convert RC5 16-123 to raw pronto, it is possible to use a small utility called IRCodeDoctor (http://www.ir-toolkit.com/IRCodeDoctor.jar). Simply execute it with
"java -jar IRCodeDoctor.jar". You'll get a small window. Right-click in the "IR-Code" field, and select'' New Code -> RC5''. Enter your system and command codes, and you will end up with a Pronto code "5000 0073 0000 0001 0010 007B". However, the first 4 digits are 5000, not 0000! Make sure you right click again in that window, and click ''Convert to RAW''. Click ''OK'' in the popup about the Toggle bit, it does not need to be set. The Pronto code will then change to the raw Pronto code "0000 0073 0000 000B 0040 0020 0020 0040 0040 0020 0020 0020 0020 0020 0020 0040 0020 0020 0020 0020 0040 0040 0020 0020 0020 0CC0". Note that it starts with 0000, so you're in business! Select all, copy, and paste it in your ''Type code manually'' field.

If you want to manually extend the duration of the emitted IR code, take a look at [[Extending the repeat duration of raw Pronto IR codes]]

Refer to the LinuxMCE [[AV Properties]] and [[IR/GSD codes syncronization]].

[[Category:Infrared]]

Extending the repeat duration of raw Pronto IR codes

2009-05-12T09:48:08Z

DomoDude: New page: Sometimes, a device does not react to an IR command because the duration of the code is too short. For example, a standard Pronto code to turn my Panasonic plasma TV on does not work. When...

Sometimes, a device does not react to an IR command because the duration of the code is too short. For example, a standard Pronto code to turn my Panasonic plasma TV on does not work. When I push the button on the remote, it ''does'' work, but I need to keep the button pressed for a fairly long time.
It would be nice to simulate that in the raw Pronto code.

Here's how it worked for me.

The first few words of the code say something about the following code. The first word, for example, should always be 0000 (pronto format: raw).
The third word contains the number of word pairs that are sent only once, and the fourth word contains the number of word pairs that are repeated.

My ON command for the Panasonic was this:
0000 0071 0000 0048 0080 003F 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0030 0010 0AAB

It did not work because it was too short. All that is needed is a change in the fourth word, just doubling it:

0000 0071 0000 '''0048''' ---> 0000 0071 0000 '''0096'''

and then copy/paste the remaining words (each pair of those indicates an on/off timing). This eventually gives

0000 0071 0000 '''0096''' 0080 003F 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0030 0010 0AAB 0080 003F 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0030 0010 0AAB

And presto! The ON signal is transmitted twice as long now, and my TV turns on.

Converting Philips RC-5 to Pronto

2009-05-02T18:32:50Z

DomoDude:

If you haven't done so already, you may want to read up on [[Learning/typing my own code]].

When your device uses '''Philips RC-5''' codes for its infrared commands from the remote control, you'll find that these codes cannot be directly used in the LinuxMCE templates. What is needed, are Pronto codes. Specifically, Pronto codes that start with 0000. You may be able to find other pronto codes for your device, but the infrared transmitter code in LMCE can only do the 0000 (raw) sequences.

As an example, I have an Arcam amplifier which uses ''system code'' 16, and e.g. ''command code'' 123 to turn it on. To convert RC5 16-123 to raw pronto, it is possible to use a small utility called IRCodeDoctor (http://www.ir-toolkit.com/IRCodeDoctor.jar). Simply execute it with
"java -jar IRCodeDoctor.jar". You'll get a small window. Right-click in the "IR-Code" field, and select'' New Code -> RC5''. Enter your system and command codes, and you will end up with a Pronto code "5000 0073 0000 0001 0010 007B". However, the first 4 digits are 5000, not 0000! Make sure you right click again in that window, and click ''Convert to RAW''. Click ''OK'' in the popup about the Toggle bit, it does not need to be set. The Pronto code will then change to the raw Pronto code "0000 0073 0000 000B 0040 0020 0020 0040 0040 0020 0020 0020 0020 0020 0020 0040 0020 0020 0020 0020 0040 0040 0020 0020 0020 0CC0". Note that it starts with 0000, so you're in business! Select all, copy, and paste it in your ''Type code manually'' field.

Refer to the LinuxMCE [[AV Properties]] and [[IR/GSD codes syncronization]].

[[Category:Infrared]]

Converting Philips RC-5 to Pronto

2009-05-02T18:15:45Z

DomoDude: New page: test.

test.

Talk:Merten 5059xx Connect Radio Central Unit

2009-02-08T21:50:07Z

DomoDude: New page: It is possible to use this unit together with LMCE, although it is a bit awkward. I programmed my lighting system with the Merten USB dongle and Merten software, so that the central unit c...

It is possible to use this unit together with LMCE, although it is a bit awkward. I programmed my lighting system with the Merten USB dongle and Merten software, so that the central unit could be programmed, too. I then made a MiCasaVerde USB stick secondary controller, which is then used by LMCE. This does require an update of the zwave driver.

Merten 5059xx Connect Radio Central Unit

2008-12-23T11:31:05Z

DomoDude:

[[Category: Hardware]]
[[Category: Lighting Automation]]
[[Category: ZWave]]

[[Image:MertenRFcentral.jpg|thumb|200px|Merten 5059xx]]
= Status =
'''NOT''' working! This unit contains a lot of proprietary code. Perhaps a workaround is possible to make this unit work with LMCE, but as it is now, integration will be limited.

= About =
This is an in-wall control unit that can be used to do advanced programming of Merten switches. Among others, the dimming ramp time can be programmed. Programming needs the Merten USB dongle! And do heed the warning under "Status".

= Features =
* See above.
* Many features, not listed due to currently bad integration options.

File:MertenRFcentral.jpg

2008-12-23T11:29:33Z

DomoDude:

Merten 5059xx Connect Radio Central Unit

2008-12-23T11:29:10Z

DomoDude: New page: Category: Hardware Category: Lighting Automation Category: ZWave Merten 5059xx = Status = '''NOT''' working! This unit contains a lot o...

[[Category: Hardware]]
[[Category: Lighting Automation]]
[[Category: ZWave]]

[[Image:Merten-5059xx.jpg|thumb|200px|Merten 5059xx]]
= Status =
'''NOT''' working! This unit contains a lot of proprietary code. Perhaps a workaround is possible to make this unit work with LMCE, but as it is now, integration will be limited.

= About =
This is an in-wall control unit that can be used to do advanced programming of Merten switches. Among others, the dimming ramp time can be programmed. Programming needs the Merten USB dongle! And do heed the warning under "Status".

= Features =
* See above.
* Many features, not listed due to currently bad integration options.

Merten 5072xx Connect Radio Push Button 4gang

2008-12-23T11:14:25Z

DomoDude:

[[Category: Hardware]]
[[Category: Lighting Automation]]
[[Category: ZWave]]

[[Image:Connect505219.jpg|thumb|200px|Merten 5072xx]]

= Status =
Working

= About =
The Merten 5072xx is a 2-surface, 4-gang Z-Wave battery powered remote controller that can be screwed or stuck to a surface.

= Features =
* dual surface, 4-gang
* special door bell mode (not yet tested)

= Device setup =
Device type: Controller
== Inclusion/Exclusion/Node Info Frame ==
* triple click on connected switch

== Input setup ==
<table border="1"><th>Button</th><th>Association Group</th><th>Parameter no</th>
<tr><td>Top Left</td><td>1</td><td>0</td></tr>
<tr><td>Bottom Left</td><td>2</td><td>1</td></tr>
<tr><td>Top Right</td><td>3</td><td>2</td></tr>
<tr><td>Bottom Right</td><td>4</td><td>3</td></tr>
</table>

== Parameter values ==
<table border="1"><th>Function</th><th>Value</th>
<tr><td>
Switching/Dimming/Shutters
</td><td>
0
</td></tr>
<tr><td>
Switching single-surface
</td><td>
4
</td></tr>
<tr><td>
Retrieve scene
</td><td>
60
</td></tr>
<tr><td>
Doorbell function
</td><td>
44
</td></tr>
<tr><td>
Move shutter single surface (changes direction each press)
</td><td>
54
</td></tr>
<tr><td>
Lower shutter as long as button is pressed
</td><td>
52
</td></tr>
<tr><td>
Raise shutter as long as button is pressed
</td><td>
55
</td></tr>

</table>
== Factory reset ==
* Press button 3 times within 1.5 seconds. The LED will flash.
* Press and hold the button for about 5 seconds until the LED turns off.

= Links =
http://www.merten.de/download

Merten 5072xx Connect Radio Push Button 4gang

2008-12-23T11:13:40Z

DomoDude:

[[Category: Hardware]]
[[Category: Lighting Automation]]
[[Category: ZWave]]

[[Image:Connect505219.jpg|thumb|200px|Merten 5071xx]]

= Status =
Working

= About =
The Merten 5072xx is a 2-surface, 4-gang Z-Wave battery powered remote controller that can be screwed or stuck to a surface.

= Features =
* dual surface, 4-gang
* special door bell mode (not yet tested)

= Device setup =
Device type: Controller
== Inclusion/Exclusion/Node Info Frame ==
* triple click on connected switch

== Input setup ==
<table border="1"><th>Button</th><th>Association Group</th><th>Parameter no</th>
<tr><td>Top Left</td><td>1</td><td>0</td></tr>
<tr><td>Bottom Left</td><td>2</td><td>1</td></tr>
<tr><td>Top Right</td><td>3</td><td>2</td></tr>
<tr><td>Bottom Right</td><td>4</td><td>3</td></tr>
</table>

== Parameter values ==
<table border="1"><th>Function</th><th>Value</th>
<tr><td>
Switching/Dimming/Shutters
</td><td>
0
</td></tr>
<tr><td>
Switching single-surface
</td><td>
4
</td></tr>
<tr><td>
Retrieve scene
</td><td>
60
</td></tr>
<tr><td>
Doorbell function
</td><td>
44
</td></tr>
<tr><td>
Move shutter single surface (changes direction each press)
</td><td>
54
</td></tr>
<tr><td>
Lower shutter as long as button is pressed
</td><td>
52
</td></tr>
<tr><td>
Raise shutter as long as button is pressed
</td><td>
55
</td></tr>

</table>
== Factory reset ==
* Press button 3 times within 1.5 seconds. The LED will flash.
* Press and hold the button for about 5 seconds until the LED turns off.

= Links =
http://www.merten.de/download

Merten 5072xx Connect Radio Push Button 4gang

2008-12-23T11:11:56Z

DomoDude: New page: Category: Hardware Category: Lighting Automation Category: ZWave Merten 5071xx = Status = Working = About = The Merten 5072xx is a 2-...

[[Category: Hardware]]
[[Category: Lighting Automation]]
[[Category: ZWave]]

[[Image:Connect507146.jpg|thumb|200px|Merten 5071xx]]

= Status =
Working

= About =
The Merten 5072xx is a 2-surface, 4-gang Z-Wave battery powered remote controller that can be screwed or stuck to a surface.

= Features =
* dual surface, 4-gang
* special door bell mode (not yet tested)

= Device setup =
Device type: Controller
== Inclusion/Exclusion/Node Info Frame ==
* triple click on connected switch

== Input setup ==
<table border="1"><th>Button</th><th>Association Group</th><th>Parameter no</th>
<tr><td>Top Left</td><td>1</td><td>0</td></tr>
<tr><td>Bottom Left</td><td>2</td><td>1</td></tr>
<tr><td>Top Right</td><td>3</td><td>2</td></tr>
<tr><td>Bottom Right</td><td>4</td><td>3</td></tr>
</table>

== Parameter values ==
<table border="1"><th>Function</th><th>Value</th>
<tr><td>
Switching/Dimming/Shutters
</td><td>
0
</td></tr>
<tr><td>
Switching single-surface
</td><td>
4
</td></tr>
<tr><td>
Retrieve scene
</td><td>
60
</td></tr>
<tr><td>
Doorbell function
</td><td>
44
</td></tr>
<tr><td>
Move shutter single surface (changes direction each press)
</td><td>
54
</td></tr>
<tr><td>
Lower shutter as long as button is pressed
</td><td>
52
</td></tr>
<tr><td>
Raise shutter as long as button is pressed
</td><td>
55
</td></tr>

</table>
== Factory reset ==
* Press button 3 times within 1.5 seconds. The LED will flash.
* Press and hold the button for about 5 seconds until the LED turns off.

= Links =
http://www.merten.de/download

Merten 5071xx Connect Radio Push Button 2gang

2008-12-23T11:09:41Z

DomoDude:

[[Category: Hardware]]
[[Category: Lighting Automation]]
[[Category: ZWave]]

[[Image:Connect507146.jpg|thumb|200px|Merten 5071xx]]

= Status =
Working

= About =
The Merten 5071xx is a 2gang Z-Wave battery powered remote controller that can be screwed or stuck to a surface.

= Features =
* 2gang
* special door bell mode (not yet tested)

= Device setup =
Device type: Controller
== Inclusion/Exclusion/Node Info Frame ==
* triple click on connected switch

== Input setup ==
<table border="1"><th>Button</th><th>Association Group</th><th>Parameter no</th>
<tr><td>Top</td><td>1</td><td>0</td></tr>
<tr><td>Bottom</td><td>2</td><td>1</td></tr>

</table>

== Parameter values ==
<table border="1"><th>Function</th><th>Value</th>
<tr><td>
Switching/Dimming/Shutters
</td><td>
0
</td></tr>
<tr><td>
Switching single-surface
</td><td>
4
</td></tr>
<tr><td>
Retrieve scene
</td><td>
60
</td></tr>
<tr><td>
Doorbell function
</td><td>
44
</td></tr>
<tr><td>
Move shutter single surface (changes direction each press)
</td><td>
54
</td></tr>
<tr><td>
Lower shutter as long as button is pressed
</td><td>
52
</td></tr>
<tr><td>
Raise shutter as long as button is pressed
</td><td>
55
</td></tr>

</table>
== Factory reset ==
* Press button 3 times within 1.5 seconds. The LED will flash.
* Press and hold the button for about 5 seconds until the LED turns off.

= Links =
http://www.merten.de/download

Merten 5071xx Connect Radio Push Button 2gang

2008-12-23T11:04:50Z

DomoDude: New page: Category: Hardware Category: Lighting Automation Category: ZWave Merten 506004 = Status = Working = About = The Merten 5071xx is a 2ga...

[[Category: Hardware]]
[[Category: Lighting Automation]]
[[Category: ZWave]]

[[Image:Merten-506004.png|thumb|200px|Merten 506004]]
= Status =
Working

= About =
The Merten 5071xx is a 2gang Z-Wave battery powered remote controller that can be screwed or stuck to a surface.

= Features =
* 4gang
* special door bell mode (not yet tested)

= Device setup =
Device type: Controller
== Inclusion/Exclusion/Node Info Frame ==
* triple click on connected switch

== Input setup ==
<table border="1"><th>Button Type</th><th>Button</th><th>Association Group</th><th>Parameter no</th>
<tr><td>Single Surface</td><td>Top</td><td>1</td><td>0</td></tr>
<tr><td></td><td>Bottom</td><td>2</td><td>1</td></tr>
<tr><td>Dual Surface</td><td>Top Left</td><td>1</td><td>0</td></tr>
<tr><td></td><td>Bottom Left</td><td>2</td><td>1</td></tr>
<tr><td></td><td>Top Right</td><td>3</td><td>2</td></tr>
<tr><td></td><td>Bottom Right</td><td>4</td><td>3</td></tr>
</table>

== Parameter values ==
<table border="1"><th>Function</th><th>Value</th>
<tr><td>
Switching/Dimming/Shutters
</td><td>
0
</td></tr>
<tr><td>
Switching single-surface
</td><td>
4
</td></tr>
<tr><td>
Retrieve scene
</td><td>
60
</td></tr>
<tr><td>
Doorbell function
</td><td>
44
</td></tr>
<tr><td>
Move shutter single surface (changes direction each press)
</td><td>
54
</td></tr>
<tr><td>
Lower shutter as long as button is pressed
</td><td>
52
</td></tr>
<tr><td>
Raise shutter as long as button is pressed
</td><td>
55
</td></tr>

</table>
== Factory reset ==
* Press button 3 times within 1.5 seconds. The LED will flash.
* Press and hold the button for about 5 seconds until the LED turns off.

= Links =
http://www.merten.de/download

Merten 5024xx Connect Sensor Cover

2008-12-23T10:53:19Z

DomoDude:

[[Category: Hardware]]
[[Category: Lighting Automation]]
[[Category: ZWave]]

[[Image:Connect5024xx.jpg|thumb|200px|Merten 5024xx]]

= Status =
Works.

= About =
The Merten 5024xx is a push button that fits onto the Merten relay (and electronic switches?) of the Connect series.

= Features =
* Really consists of 2 buttons: top and bottom half.

= Device setup =
Device type: Receiver
== Inclusion/Exclusion/Node Info Frame ==
* Triple click on connected switch within approx. 1.5 seconds.

== Parameter values ==
<table border="1"><th>Function</th><th>Value</th>
<tr><td>
Switching additional CONNECT radio receivers
</td><td>
0
</td></tr>

</table>
== Factory reset ==
* Press the connected button 3 times within 1.5 seconds. The LED will flash.
* Press and hold the button for about 5 seconds until the LED turns off.

= Links =
http://www.merten.de/download

Merten 5024xx Connect Sensor Cover

2008-12-23T10:52:35Z

DomoDude:

[[Category: Hardware]]
[[Category: Lighting Automation]]
[[Category: ZWave]]

[[Image:Connect5024xx.jpg|thumb|200px|Merten 5024xx]]

= Status =
Unknown

= About =
The Merten 5024xx is a push button that fits onto the Merten relay (and electronic switches?) of the Connect series.

= Features =
* Really consists of 2 buttons: top and bottom half.

= Device setup =
Device type: Receiver
== Inclusion/Exclusion/Node Info Frame ==
* Triple click on connected switch within approx. 1.5 seconds.

== Parameter values ==
<table border="1"><th>Function</th><th>Value</th>
<tr><td>
Switching additional CONNECT radio receivers
</td><td>
0
</td></tr>

</table>
== Factory reset ==
* Press the connected button 3 times within 1.5 seconds. The LED will flash.
* Press and hold the button for about 5 seconds until the LED turns off.

= Links =
http://www.merten.de/download

File:Connect5024xx.jpg

2008-12-23T10:51:35Z

DomoDude:

File:Connect507146.jpg

2008-12-23T10:50:53Z

DomoDude:

File:Connect507001.jpg

2008-12-23T10:50:33Z

DomoDude:

File:Connect506004.jpg

2008-12-23T10:50:02Z

DomoDude:

File:Connect505919.jpg

2008-12-23T10:49:41Z

DomoDude:

File:Connect505219.jpg

2008-12-23T10:49:21Z

DomoDude:

File:Connect504519.jpg

2008-12-23T10:48:52Z

DomoDude:

File:Connect5082xx.jpg

2008-12-23T10:48:28Z

DomoDude:

Merten 5024xx Connect Sensor Cover

2008-12-23T10:46:08Z

DomoDude: New page: Category: Hardware Category: Lighting Automation Category: ZWave = Status = Unknown = About = The Merten 5024xx is a push button that fits onto the Merten relay (and electron...

[[Category: Hardware]]
[[Category: Lighting Automation]]
[[Category: ZWave]]

= Status =
Unknown

= About =
The Merten 5024xx is a push button that fits onto the Merten relay (and electronic switches?) of the Connect series.

= Features =
* Really consists of 2 buttons: top and bottom half.

= Device setup =
Device type: Receiver
== Inclusion/Exclusion/Node Info Frame ==
* Triple click on connected switch within approx. 1.5 seconds.

== Parameter values ==
<table border="1"><th>Function</th><th>Value</th>
<tr><td>
Switching additional CONNECT radio receivers
</td><td>
0
</td></tr>

</table>
== Factory reset ==
* Press the connected button 3 times within 1.5 seconds. The LED will flash.
* Press and hold the button for about 5 seconds until the LED turns off.

= Links =
http://www.merten.de/download

Where to Buy

2008-09-22T11:51:47Z

DomoDude: /* Germany */

[[Category: Hardware| ]]
{| align="right"
| __TOC__
|}
This is '''not''' meant as an endorsement, but the question of where to buy certain things pops up regularly. Some of this equipment can be hard to find locally, so help out and add your own suppliers to the list if they aren't already there and either way feel free to add a line with your experience.

''Please add countries alphabetically, and append new stores to the bottom of the lists in order to keep things organized, thank you and good luck with that shopping list!''

== Africa ==

== America ==

=== United States ===

'''Fiire''' ([http://www.fiire.com/ english]) ''The'' remote, and also core/media director hardware.

== Asia ==

== Australia ==

== Europe ==

=== Belgium ===

'''IntelliHome''' Domotica Shop ([http://www.intellihome.be/ multi]/[http://www.intellihome.be/english/home.asp english]/[http://www.intellihome.be/nederlands/home.asp dutch]/[http://www.intellihome.be/francais/home.asp french]/[http://www.intellihome.be/deutsch/home.asp german]) Marmitek X10 Home Automation/Security Products, European shipping
* ...

'''Voipsolutions''' ([http://www.voipsolutions.be/ english]/[http://www.voipsolutions.be/language/fr french]/[http://www.voipsolutions.be/language/nl dutch]) All kinds of VoIP related hardware solutions.
* ...

=== Denmark ===

'''Seluxit''' ([http://www.seluxit.com english]) Z-wave products incl. [http://shop.seluxit.com/catalog/product_info.php?currency=EUR&products_id=30 multi-sensor] [http://shop.seluxit.com/catalog/product_info.php?currency=EUR&products_id=29 usb homecontroller]
* Not yet tested.

'''Innovus''' ([http://www.innovus.dk/ danish]/[http://www.innovus.eu english]) Z-wave products
* Not yet tested.

'''ElectronicHouseKeeper''' ([http://www.electronichousekeeper.com danish]) Their own line of Z-wave products
* Not yet tested.

=== Germany ===

'''DVBShop''' ([http://www.dvbshop.net english]) Everything you need for DVB (Cable, Sattelite or Terrestrial) digital television, worldwide shipping.

'''Zwave4u''' ([http://www.zwave4u.de german]) Z-wave products. Accepts Paypal.
* Not yet tested.

'''Merten''' ([http://www.merten.de german]) They have their own line of Z-wave products.

http://www.elektronetshop.de - Sells the Merten stuff, best price found on Sep 9, 2008

http://www.voltus.de - Also cheaper than official Merten prices, but I found service to be severely lacking (very, very unresponsive!). Summer 2008.

'''Duewi''' ([http://www.duewi.de german]) They have their own line of Z-wave products.
* No online shop.

'''Touchscreens''' ([http://www.fine-buy.de/]) They have some touchscreens, the 12.1" (http://www.fine-buy.de/shop/product_info.php?cPath=3_30_64&products_id=159) works fine: [[Egalax-Touchscreen]]

=== Italy ===

'''Z-wave Europe''' ([http://www.z-wave-europe.org/ italian]) Z-wave product list for Europe and website links.

=== Netherlands ===

'''ElekHomica''' ([http://www.elekhomica.nl/ dutch]/[http://www.elekhomica.nl/infopage2.php?language=nn english])
X10 and Zwave, even remote controlled curtainrail! EU shipping (curtainrail NL/BE only).
* Quick and painless delivery.

'''ALTERNATE''' Computerversand ([http://www.alternate.nl/ dutch]) [http://www.alternate.nl/html/productDetails.html?artno=NMZV62 airmouse] and lots of regular PC hardware,
* Usually slow on delivery.

'''iHabitat''' Home automation ([http://www.ihabitat.nl/ dutch])
[http://www.ihabitat.nl/html/global_cache.html gc100]
* A bit slow to respond to the inquiry, but fast no-nonsense delivery.

'''MyPowerShop''' ([http://www.mypowershop.eu dutch]) X10 and Z-wave products. Accepts Paypal
* Not yet tested

=== Norway ===

'''Tronika aka Smarthus''' ([http://www.smarthus.info/ norwegian]) Z-wave products incl. [http://www.smarthus.info/product_info.php?cPath=1_46_115&products_id=2248 usb homecontroller]
* Not yet tested

=== Sweden ===

'''Eliving''' ([http://www.eliving.se swedish]) Z-wave products incl. [http://www.eliving.se/product_info.php?cPath=21_29&products_id=72 usb homecontroller]
* Not yet tested

=== United Kingdom ===

'''Convergent Home Technologies - The Digital Home Specialists''' ([http://www.chtukltd.co.uk English])
* Core/Hybrids built & tested to order (AM2/nVidia, Intel)
* MD's built & tested (AM2/nVidia, AM2/ATI, Intel)
* Z-wave - full range of European units
* lmce-0710 software pre-installed & configured on all Core/Hybrids
* Full after sales support provided
* Will Ship Worldwide (but not currently to the US)

'''Let's automate''' ([http://www.letsautomate.com/index.cfm english]) ZWave home automation
* ...

Where to Buy

2008-09-22T11:51:22Z

DomoDude: /* Germany */

[[Category: Hardware| ]]
{| align="right"
| __TOC__
|}
This is '''not''' meant as an endorsement, but the question of where to buy certain things pops up regularly. Some of this equipment can be hard to find locally, so help out and add your own suppliers to the list if they aren't already there and either way feel free to add a line with your experience.

''Please add countries alphabetically, and append new stores to the bottom of the lists in order to keep things organized, thank you and good luck with that shopping list!''

== Africa ==

== America ==

=== United States ===

'''Fiire''' ([http://www.fiire.com/ english]) ''The'' remote, and also core/media director hardware.

== Asia ==

== Australia ==

== Europe ==

=== Belgium ===

'''IntelliHome''' Domotica Shop ([http://www.intellihome.be/ multi]/[http://www.intellihome.be/english/home.asp english]/[http://www.intellihome.be/nederlands/home.asp dutch]/[http://www.intellihome.be/francais/home.asp french]/[http://www.intellihome.be/deutsch/home.asp german]) Marmitek X10 Home Automation/Security Products, European shipping
* ...

'''Voipsolutions''' ([http://www.voipsolutions.be/ english]/[http://www.voipsolutions.be/language/fr french]/[http://www.voipsolutions.be/language/nl dutch]) All kinds of VoIP related hardware solutions.
* ...

=== Denmark ===

'''Seluxit''' ([http://www.seluxit.com english]) Z-wave products incl. [http://shop.seluxit.com/catalog/product_info.php?currency=EUR&products_id=30 multi-sensor] [http://shop.seluxit.com/catalog/product_info.php?currency=EUR&products_id=29 usb homecontroller]
* Not yet tested.

'''Innovus''' ([http://www.innovus.dk/ danish]/[http://www.innovus.eu english]) Z-wave products
* Not yet tested.

'''ElectronicHouseKeeper''' ([http://www.electronichousekeeper.com danish]) Their own line of Z-wave products
* Not yet tested.

=== Germany ===

'''DVBShop''' ([http://www.dvbshop.net english]) Everything you need for DVB (Cable, Sattelite or Terrestrial) digital television, worldwide shipping.

'''Zwave4u''' ([http://www.zwave4u.de german]) Z-wave products. Accepts Paypal.
* Not yet tested.

'''Merten''' ([http://www.merten.de german]) They have their own line of Z-wave products.

http://www.elektronetshop.de - Sells the Merten stuff, best price found on Sep 9, 2008
http://www.voltus.de - Also cheaper than official Merten prices, but I found service to be severely lacking (very, very unresponsive!). Summer 2008.

'''Duewi''' ([http://www.duewi.de german]) They have their own line of Z-wave products.
* No online shop.

'''Touchscreens''' ([http://www.fine-buy.de/]) They have some touchscreens, the 12.1" (http://www.fine-buy.de/shop/product_info.php?cPath=3_30_64&products_id=159) works fine: [[Egalax-Touchscreen]]

=== Italy ===

'''Z-wave Europe''' ([http://www.z-wave-europe.org/ italian]) Z-wave product list for Europe and website links.

=== Netherlands ===

'''ElekHomica''' ([http://www.elekhomica.nl/ dutch]/[http://www.elekhomica.nl/infopage2.php?language=nn english])
X10 and Zwave, even remote controlled curtainrail! EU shipping (curtainrail NL/BE only).
* Quick and painless delivery.

'''ALTERNATE''' Computerversand ([http://www.alternate.nl/ dutch]) [http://www.alternate.nl/html/productDetails.html?artno=NMZV62 airmouse] and lots of regular PC hardware,
* Usually slow on delivery.

'''iHabitat''' Home automation ([http://www.ihabitat.nl/ dutch])
[http://www.ihabitat.nl/html/global_cache.html gc100]
* A bit slow to respond to the inquiry, but fast no-nonsense delivery.

'''MyPowerShop''' ([http://www.mypowershop.eu dutch]) X10 and Z-wave products. Accepts Paypal
* Not yet tested

=== Norway ===

'''Tronika aka Smarthus''' ([http://www.smarthus.info/ norwegian]) Z-wave products incl. [http://www.smarthus.info/product_info.php?cPath=1_46_115&products_id=2248 usb homecontroller]
* Not yet tested

=== Sweden ===

'''Eliving''' ([http://www.eliving.se swedish]) Z-wave products incl. [http://www.eliving.se/product_info.php?cPath=21_29&products_id=72 usb homecontroller]
* Not yet tested

=== United Kingdom ===

'''Convergent Home Technologies - The Digital Home Specialists''' ([http://www.chtukltd.co.uk English])
* Core/Hybrids built & tested to order (AM2/nVidia, Intel)
* MD's built & tested (AM2/nVidia, AM2/ATI, Intel)
* Z-wave - full range of European units
* lmce-0710 software pre-installed & configured on all Core/Hybrids
* Full after sales support provided
* Will Ship Worldwide (but not currently to the US)

'''Let's automate''' ([http://www.letsautomate.com/index.cfm english]) ZWave home automation
* ...

GlobalCache GC-100

2008-08-30T17:34:59Z

DomoDude: /* Install */

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

[[Image:GC100.jpg|right]]

GC100 is a network-capable device which allows you to add remote control (and other input device) connectivity. It includes:

* serial ports
* [[IR|Infrared]] sensors (inputs) and outputs
* one or more relays

The remote control data is then able to be sent over an Ethernet (TCP/IP) network through the Ethernet port, without the requirement of a connection to a specific PC.

For more details about the product check [http://www.globalcache.com/products/gc-index.html the Global Cache 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). LMCE will temporarily change its internal network and look for the gc100 at its factory default of 192.168.1.70, change the configuration of the GC100, and the core then goes back to its regular network settings. Note that this will almost certainly fail if your '''exernal''' IP on the core is in the 192.168.1 network! The script will then 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-08-30T17:34:01Z

DomoDude: Added a few lines in the Install section. (Make sure core external IP is not in 192.168.1 network)

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

[[Image:GC100.jpg|right]]

GC100 is a network-capable device which allows you to add remote control (and other input device) connectivity. It includes:

* serial ports
* [[IR|Infrared]] sensors (inputs) and outputs
* one or more relays

The remote control data is then able to be sent over an Ethernet (TCP/IP) network through the Ethernet port, without the requirement of a connection to a specific PC.

For more details about the product check [http://www.globalcache.com/products/gc-index.html the Global Cache 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). LMCE will temporarily change its internal network and look for the gc100 at its factory default of 192.168.1.70, change the configuration of the GC100, and the core then goes back to its regular network settings. Note that this will almost certainly fail if your '''exernal''' IP on the core is in the 192.168.1 network! The "Add GC100" 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).