LinuxMCE - User contributions [en]

Z-Wave Getting Started

2010-08-01T21:57:29Z

Dpaul:

{{Versioninfo}}
[[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.

For information about how to set up the ZWave devices in LMCE, see [[Z-Wave]].

= 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:

== Supported ==

=== USB Interface 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. A master controller(remote) can be used in addition to LMCE to control Z-Wave devices. A separate controller may be required for some of these interfaces(those that don't support SIS mode).

Some examples of these devices are:<br>
* [[ACT Homepro ZCS000]]
* [[ACT Homepro ZCS010]]
* [[ACT Homepro ZCS101]]
* [[ACT Homepro ZCS201]]
* [[ACT Homepro ZCU000]]
* [[ACT Homepro ZCU010]]
* [[Intermatic HA22]]
* [[Intermatic_HA23C|Intermatic HA23C]]
* [[Intermatic HA20C]]
* [[Tricklestar_300ZW-US-W|US Tricklestar]] (Supports SIS)
* [[Tricklestar_300ZW-EU-W|EU Tricklestar]] (Supports SIS)
* [[Seluxit_viaSENS_Homecontroller|Seluxit viaSENS Homecontroller]] (Supports SIS)

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 Interface 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:<br>
* [[Aeon Labs Z-Wave Interface]] with built-In Inclusion Remote
* [[MCV_Z-Wave_Dongle|Mi Casa Verde USB + Inclusion Controller in one]]
* [[Z~Series USB Stick with Z-Wave]] (Australian / New Zealand Z-Wave)

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

== UNSUPPORTED ==
'''those don't work'''

* [[ACT Homepro ZCU101]]
* [[ACT Homepro ZCU201]]

=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 ceiling 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 ceiling 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==

== PIR (Binary Sensor) support ==

*[[ACT Homepro Motion Detector]]
*[[Express Controls EZmotion]]

== 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 device(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

Z-Wave Getting Started

2010-08-01T21:55:47Z

Dpaul: /* USB Interface without Controller */

ZWave

2010-07-31T21:41:29Z

Dpaul: /* SUC/SIS Mode (recommended) */

{{Versioninfo|810Status=Working|810UpdatedDate=12th May 2010|810UpdatedBy=sambuca}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Programmer's Guide]]
[[Category: Documentation]]

Z-Wave™ is a wireless RF-based communications technology designed for residential and light commercial control and status reading applications such as meter reading, lighting and appliance control, HVAC, access control, intruder and fire detection.

== Overview ==
The support from LinuxMCE system is represented by an executable '''ZWave''' (it's placed in /usr/pluto/bin) which is the device implementation and a '''DeviceTemplate (1754)''' which is used to create LinuxMCE Devices for ZWave.
There are high speed (4x 40kbps) and standard speed Z-Wave devices.

For information about what hardware to get look at [[Z-Wave Getting Started]], or check out the [[:Category:ZWave|Z-Wave Wiki Category]].

== How to install and use ZWave ==
=== Automatic installation - Lighting Wizard ===
The [[Lighting Wizard]] allows you to easily integrate LinuxMCE into your Z-Wave network. It is started after you plug in the Z-Wave dongle. Just follow the onscreen instructions. However the Lighting Wizard does not support SUC/SIS mode (see below) and because of this is now not the best way to include ZWave devices into your ZWave network. If you have a ZWave USB interface and an Inclusion Controller that supports SUC/SIS mode then this is the recommended configuration to use.

=== SUC/SIS Mode (recommended) ===
In SUC/SIS mode, LMCE adds your devices automatically as you include them into the Z-Wave network. Inclusion can be done using an inclusion remote or the "Add Node" command in LMCE (this option is really only successful in smaller test installations or possibly in smaller apartments for example). LMCE will assign new Node ids to the included devices and will add them in the Device tree under your ZWave USB interface

#To use the SUC/SIS mode, send a "Reset" command to the ZWave USB interface.
##In the web admin, go to Advanced -> Devices, find the ZWave device in the tree, select it, click "Send Command To Device" in the right pane.
##Select "Reset" and click Send Command. (Reset will remove all devices from you Z-Wave network).
#Next do a Reload Router (**This reload is essential**).
#When using SUC/SIS mode you must add an Inclusion Controller as the 2nd device in your ZWave network (the first device being the ZWave USB interface itself). An Inclusion Controller is the device you use to include ZWave devices into the ZWave network - this might be your ZWave remote control or possibly a wireless wall switch as these can often do double duty as an Inclusion Controller. You can add additional Inclusion Controllers or indeed any other ZWave devices at any time in the future as needed, and they will be added to your Device Tree automatically for you - this is the unique power of SUC/SIS.
##'''If using a Tricklestar Remote and USB:'''
###First select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen).
###Next put the remote in configuration mode, then press and hold up until the LED flashes green, then press up four times. The LED will begin flashing green. Once added, the remote LED should start flashing faster then go steady green indicating success. If it goes red then reset the remote (hold up til green, then hold up 10 seconds until 3 color LED), and redo step 1-2.
##'''If not using a Tricklestar remote and USB:'''
###Select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen).
###Next bring your Inclusion Controller close to your Core's/MD's ZWave USB interface and click once on its button or paddle (if a Wireless light switch) to include it into the ZWave Network. Your device should now indicate a successful inclusion if not repeat the last step.
# Do a quick reload of the router, twice.
#If your Inclusion Remote indicated a successful inclusion you are now ready to start including light switches and other devices using the device you added as an Inclusion Controller (ie your ZWave remote or a wireless Light Switch) - and not the 'Add Node' command in Web Admin.
#Place your inclusion controller device into Inclusion Mode (consult the devices manual for the details of how to include devices using it).
#Now while holding it close to the device you want to include press any button on the front of that device (usually one of the paddles on a light switch for example).
#Wait for the successful inclusion indication on the device you are including and if you have an Orbiter or Web Orbiter nearby you should also see a brief announcement that device was added successfully. A few second later a router reload screen will pop up - it is an important reload.
#Now you can move to the next device and include it. A router reload is suggested after each include.
#Keep doing this until all of your devices are included. With SUC/SIS there is no need to include all of your ZWave devices in one hit. You stop and continue another time without any issues. So adding some more devices months into the future is simple and easy to do.
#Check in Web Admin's Wizard->Devices->Lights page to make sure all of your included devices are present (if not do a reload router).

* Note: When including devices using SUC/SIS mode always start by including the devices that are closest to where the Core's ZWave USB interface is located and finish with the device that is furthest away. This enables the inclusion process to utilise the ZWave mesh network to communicate with the Core's ZWave USB interface.

* Not all ZWave interfaces support SIS mode. See the page of the individual interface to check, here is a list of interfaces [[Z-Wave Getting Started#Interface]].

=== Alternate setup of [[Tricklestar Remote]] (not recommended) ===

=== Manual setup / Download configuration ===
Once you have successfully installed the ZWave USB controller and it is seen on LinuxMCE ([[media:zwave_homepro_interface.png]]), you can proceed by populating the ZWave network information to LinuxMCE.

# Add your ZWave devices to your master ZWave master remote controller (like ZTH200)
#* Once the devices are added to remote and verified they are working (you can control them with your remote controller), you need to copy the ZWave network information to LinuxMCE.
# Go to LinuxMCE admin page (<nowiki>"http://dcerouter/lmce-admin/"</nowiki>), then choose "Wizard -> Devices -> Interfaces -> [your ZWave controller] -> Advanced".
## On the device page select "Send command to device".
## Select command "Download Configuration" and choose "Send Message".
##* Leave the data and file fields as blank
# Now LinuxMCE is waiting for the ZWave information and you should send a copy of the ZWave network with your master remote controller to LinuxMCE.
#* If you are using HomePro remote controller this is done by selecting: "Setup -> Copy Remote Ctrl. -> Send Information -> Identical Copy". Once you have done that, the remote will show "Sending information..." and after successful sending it will return to clock screen (this shouldn't take more than couple of minutes).
#* You can monitor the process by watching the Zwave log file on LinuxMCE (usually "/var/log/pluto/*ZWave.log"). Unfortunately the admin page doesn't give much information of what is being done and is everything going smoothly. If the process is successfully, you should see the LinuxMCE communicating with the USB controller
#* Make sure the sending remote controller is near enough the USB receiver, otherwise nothing will happen.
# Go to device tree (Show devices tree) and you should see ([[Media:zwave_devices_tree.png]]) the newly added ZWave modules/devices on the tree under "CORE -> ZWave".

You should do quick reload (Wizard -> Restart -> Quick Reload Router) in order to use the newly added devices with LinuxMCE. Once you have done that you should be able to control (like switching on/off) the devices under the Light ([[Media:zwave_lights.png]]).

== Setting associations ==
If you use SIS mode, associations will be set automatically, so that LMCE is always associated with each new device. This allows LMCE to receive messages when a device changes state.

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

== Tweak advanced ZWave settings ==
If you want to tweak some specific settings of your ZWave devices then read [[Tweak_advanced_ZWave_settings|this article]].

= Implementation =
== Open version ==
The new open Z-Wave driver will be included in the upcoming 0810 release.
The source code is available in LinuxMCE's SVN repository: http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src/ZWave.

A 32bit binary of the new Z-Wave driver for 0710 can be found here: http://vt100.at/files/ZWave-0.0.2-0710-32bit.bz2
Just swap with the existing /usr/pluto/bin/ZWave and quick reload the router.

== Fiire driver ==
Fiire (a company no longer in business) also provided a Z-Wave driver, it is binary only: [[Fiire ZWave Patch]]

== Old version ==
This is the version shipped with 0710. The source code for the old version is not available as it depends on proprietary files from Zensys.

== Z-Wave API documentation ==

[[ZWave API]]

ZWave

2010-07-31T21:40:06Z

Dpaul: /* SUC/SIS Mode (recommended) */

{{Versioninfo|810Status=Working|810UpdatedDate=12th May 2010|810UpdatedBy=sambuca}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Programmer's Guide]]
[[Category: Documentation]]

Z-Wave™ is a wireless RF-based communications technology designed for residential and light commercial control and status reading applications such as meter reading, lighting and appliance control, HVAC, access control, intruder and fire detection.

== Overview ==
The support from LinuxMCE system is represented by an executable '''ZWave''' (it's placed in /usr/pluto/bin) which is the device implementation and a '''DeviceTemplate (1754)''' which is used to create LinuxMCE Devices for ZWave.
There are high speed (4x 40kbps) and standard speed Z-Wave devices.

For information about what hardware to get look at [[Z-Wave Getting Started]], or check out the [[:Category:ZWave|Z-Wave Wiki Category]].

== How to install and use ZWave ==
=== Automatic installation - Lighting Wizard ===
The [[Lighting Wizard]] allows you to easily integrate LinuxMCE into your Z-Wave network. It is started after you plug in the Z-Wave dongle. Just follow the onscreen instructions. However the Lighting Wizard does not support SUC/SIS mode (see below) and because of this is now not the best way to include ZWave devices into your ZWave network. If you have a ZWave USB interface and an Inclusion Controller that supports SUC/SIS mode then this is the recommended configuration to use.

=== SUC/SIS Mode (recommended) ===
In SUC/SIS mode, LMCE adds your devices automatically as you include them into the Z-Wave network. Inclusion can be done using an inclusion remote or the "Add Node" command in LMCE (this option is really only successful in smaller test installations or possibly in smaller apartments for example). LMCE will assign new Node ids to the included devices and will add them in the Device tree under your ZWave USB interface

#To use the SUC/SIS mode, send a "Reset" command to the ZWave USB interface.
##In the web admin, go to Advanced -> Devices, find the ZWave device in the tree, select it, click "Send Command To Device" in the right pane.
##Select "Reset" and click Send Command. (Reset will remove all devices from you Z-Wave network).
#Next do a Reload Router (**This reload is essential**).
#When using SUC/SIS mode you must add an Inclusion Controller as the 2nd device in your ZWave network (the first device being the ZWave USB interface itself). An Inclusion Controller is the device you use to include ZWave devices into the ZWave network - this might be your ZWave remote control or possibly a wireless wall switch as these can often do double duty as an Inclusion Controller. You can add additional Inclusion Controllers or indeed any other ZWave devices at any time in the future as needed, and they will be added to your Device Tree automatically for you - this is the unique power of SUC/SIS.
##'''If using a Tricklestar Remote:'''
###First select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen).
###Next put the remote in configuration mode, then press and hold up until the LED flashes green, then press up four times. The LED will begin flashing green. Once added, the remote LED should start flashing faster then go steady green indicating success. If it goes red then reset the remote (hold up til green, then hold up 10 seconds until 3 color LED), and redo step 1-2.
##'''If not using a tricklestar remote:'''
###Select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen).
###Next bring your Inclusion Controller close to your Core's/MD's ZWave USB interface and click once on its button or paddle (if a Wireless light switch) to include it into the ZWave Network. Your device should now indicate a successful inclusion if not repeat the last step.
# Do a quick reload of the router, twice.
#If your Inclusion Remote indicated a successful inclusion you are now ready to start including light switches and other devices using the device you added as an Inclusion Controller (ie your ZWave remote or a wireless Light Switch) - and not the 'Add Node' command in Web Admin.
#Place your inclusion controller device into Inclusion Mode (consult the devices manual for the details of how to include devices using it).
#Now while holding it close to the device you want to include press any button on the front of that device (usually one of the paddles on a light switch for example).
#Wait for the successful inclusion indication on the device you are including and if you have an Orbiter or Web Orbiter nearby you should also see a brief announcement that device was added successfully. A few second later a router reload screen will pop up - it is an important reload.
#Now you can move to the next device and include it. A router reload is suggested after each include.
#Keep doing this until all of your devices are included. With SUC/SIS there is no need to include all of your ZWave devices in one hit. You stop and continue another time without any issues. So adding some more devices months into the future is simple and easy to do.
#Check in Web Admin's Wizard->Devices->Lights page to make sure all of your included devices are present (if not do a reload router).

* Note: When including devices using SUC/SIS mode always start by including the devices that are closest to where the Core's ZWave USB interface is located and finish with the device that is furthest away. This enables the inclusion process to utilise the ZWave mesh network to communicate with the Core's ZWave USB interface.

* Not all ZWave interfaces support SIS mode. See the page of the individual interface to check, here is a list of interfaces [[Z-Wave Getting Started#Interface]].

=== Alternate setup of [[Tricklestar Remote]] (not recommended) ===

=== Manual setup / Download configuration ===
Once you have successfully installed the ZWave USB controller and it is seen on LinuxMCE ([[media:zwave_homepro_interface.png]]), you can proceed by populating the ZWave network information to LinuxMCE.

# Add your ZWave devices to your master ZWave master remote controller (like ZTH200)
#* Once the devices are added to remote and verified they are working (you can control them with your remote controller), you need to copy the ZWave network information to LinuxMCE.
# Go to LinuxMCE admin page (<nowiki>"http://dcerouter/lmce-admin/"</nowiki>), then choose "Wizard -> Devices -> Interfaces -> [your ZWave controller] -> Advanced".
## On the device page select "Send command to device".
## Select command "Download Configuration" and choose "Send Message".
##* Leave the data and file fields as blank
# Now LinuxMCE is waiting for the ZWave information and you should send a copy of the ZWave network with your master remote controller to LinuxMCE.
#* If you are using HomePro remote controller this is done by selecting: "Setup -> Copy Remote Ctrl. -> Send Information -> Identical Copy". Once you have done that, the remote will show "Sending information..." and after successful sending it will return to clock screen (this shouldn't take more than couple of minutes).
#* You can monitor the process by watching the Zwave log file on LinuxMCE (usually "/var/log/pluto/*ZWave.log"). Unfortunately the admin page doesn't give much information of what is being done and is everything going smoothly. If the process is successfully, you should see the LinuxMCE communicating with the USB controller
#* Make sure the sending remote controller is near enough the USB receiver, otherwise nothing will happen.
# Go to device tree (Show devices tree) and you should see ([[Media:zwave_devices_tree.png]]) the newly added ZWave modules/devices on the tree under "CORE -> ZWave".

You should do quick reload (Wizard -> Restart -> Quick Reload Router) in order to use the newly added devices with LinuxMCE. Once you have done that you should be able to control (like switching on/off) the devices under the Light ([[Media:zwave_lights.png]]).

== Setting associations ==
If you use SIS mode, associations will be set automatically, so that LMCE is always associated with each new device. This allows LMCE to receive messages when a device changes state.

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

== Tweak advanced ZWave settings ==
If you want to tweak some specific settings of your ZWave devices then read [[Tweak_advanced_ZWave_settings|this article]].

= Implementation =
== Open version ==
The new open Z-Wave driver will be included in the upcoming 0810 release.
The source code is available in LinuxMCE's SVN repository: http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src/ZWave.

A 32bit binary of the new Z-Wave driver for 0710 can be found here: http://vt100.at/files/ZWave-0.0.2-0710-32bit.bz2
Just swap with the existing /usr/pluto/bin/ZWave and quick reload the router.

== Fiire driver ==
Fiire (a company no longer in business) also provided a Z-Wave driver, it is binary only: [[Fiire ZWave Patch]]

== Old version ==
This is the version shipped with 0710. The source code for the old version is not available as it depends on proprietary files from Zensys.

== Z-Wave API documentation ==

[[ZWave API]]

ZWave

2010-07-31T21:35:22Z

Dpaul: /* SUC/SIS Mode (recommended) */

{{Versioninfo|810Status=Working|810UpdatedDate=12th May 2010|810UpdatedBy=sambuca}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Programmer's Guide]]
[[Category: Documentation]]

Z-Wave™ is a wireless RF-based communications technology designed for residential and light commercial control and status reading applications such as meter reading, lighting and appliance control, HVAC, access control, intruder and fire detection.

== Overview ==
The support from LinuxMCE system is represented by an executable '''ZWave''' (it's placed in /usr/pluto/bin) which is the device implementation and a '''DeviceTemplate (1754)''' which is used to create LinuxMCE Devices for ZWave.
There are high speed (4x 40kbps) and standard speed Z-Wave devices.

For information about what hardware to get look at [[Z-Wave Getting Started]], or check out the [[:Category:ZWave|Z-Wave Wiki Category]].

== How to install and use ZWave ==
=== Automatic installation - Lighting Wizard ===
The [[Lighting Wizard]] allows you to easily integrate LinuxMCE into your Z-Wave network. It is started after you plug in the Z-Wave dongle. Just follow the onscreen instructions. However the Lighting Wizard does not support SUC/SIS mode (see below) and because of this is now not the best way to include ZWave devices into your ZWave network. If you have a ZWave USB interface and an Inclusion Controller that supports SUC/SIS mode then this is the recommended configuration to use.

=== SUC/SIS Mode (recommended) ===
In SUC/SIS mode, LMCE adds your devices automatically as you include them into the Z-Wave network. Inclusion can be done using an inclusion remote or the "Add Node" command in LMCE (this option is really only successful in smaller test installations or possibly in smaller apartments for example). LMCE will assign new Node ids to the included devices and will add them in the Device tree under your ZWave USB interface

#To use the SUC/SIS mode, send a "Reset" command to the ZWave USB interface.
##In the web admin, go to Advanced -> Devices, find the ZWave device in the tree, select it, click "Send Command To Device" in the right pane.
##Select "Reset" and click Send Command. (Reset will remove all devices from you Z-Wave network).
#Next do a Reload Router (**This reload is essential**).
#When using SUC/SIS mode you must add an Inclusion Controller as the 2nd device in your ZWave network (the first device being the ZWave USB interface itself). An Inclusion Controller is the device you use to include ZWave devices into the ZWave network - this might be your ZWave remote control or possibly a wireless wall switch as these can often do double duty as an Inclusion Controller. You can add additional Inclusion Controllers or indeed any other ZWave devices at any time in the future as needed, and they will be added to your Device Tree automatically for you - this is the unique power of SUC/SIS.
##'''If using a Tricklestar Remote:'''
###First select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen).
###Next put the remote in configuration mode, then press and hold up until the LED flashes green, then press up four times. The LED will begin flashing green. Once added, the remote LED should go steady green indicating success. If it goes red then reset the remote (hold up til green, then hold up 10 seconds until 3 color LED), and redo step 1-2.
##'''If not using a tricklestar remote:'''
###Select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen).
###Next bring your Inclusion Controller close to your Core's/MD's ZWave USB interface and click once on its button or paddle (if a Wireless light switch) to include it into the ZWave Network. Your device should now indicate a successful inclusion if not repeat the last step.
# Do a quick reload of the router, twice.
#If your Inclusion Remote indicated a successful inclusion you are now ready to start including light switches and other devices using the device you added as an Inclusion Controller (ie your ZWave remote or a wireless Light Switch) - and not the 'Add Node' command in Web Admin.
#Place your inclusion controller device into Inclusion Mode (consult the devices manual for the details of how to include devices using it).
#Now while holding it close to the device you want to include press any button on the front of that device (usually one of the paddles on a light switch for example).
#Wait for the successful inclusion indication on the device you are including and if you have an Orbiter or Web Orbiter nearby you should also see a brief announcement that device was added successfully. A few second later a router reload screen will pop up - it is an important reload.
#Now you can move to the next device and include it. A router reload is suggested after each include.
#Keep doing this until all of your devices are included. With SUC/SIS there is no need to include all of your ZWave devices in one hit. You stop and continue another time without any issues. So adding some more devices months into the future is simple and easy to do.
#Check in Web Admin's Wizard->Devices->Lights page to make sure all of your included devices are present (if not do a reload router).

* Note: When including devices using SUC/SIS mode always start by including the devices that are closest to where the Core's ZWave USB interface is located and finish with the device that is furthest away. This enables the inclusion process to utilise the ZWave mesh network to communicate with the Core's ZWave USB interface.

* Not all ZWave interfaces support SIS mode. See the page of the individual interface to check, here is a list of interfaces [[Z-Wave Getting Started#Interface]].

=== Alternate setup of [[Tricklestar Remote]] (not recommended) ===

=== Manual setup / Download configuration ===
Once you have successfully installed the ZWave USB controller and it is seen on LinuxMCE ([[media:zwave_homepro_interface.png]]), you can proceed by populating the ZWave network information to LinuxMCE.

# Add your ZWave devices to your master ZWave master remote controller (like ZTH200)
#* Once the devices are added to remote and verified they are working (you can control them with your remote controller), you need to copy the ZWave network information to LinuxMCE.
# Go to LinuxMCE admin page (<nowiki>"http://dcerouter/lmce-admin/"</nowiki>), then choose "Wizard -> Devices -> Interfaces -> [your ZWave controller] -> Advanced".
## On the device page select "Send command to device".
## Select command "Download Configuration" and choose "Send Message".
##* Leave the data and file fields as blank
# Now LinuxMCE is waiting for the ZWave information and you should send a copy of the ZWave network with your master remote controller to LinuxMCE.
#* If you are using HomePro remote controller this is done by selecting: "Setup -> Copy Remote Ctrl. -> Send Information -> Identical Copy". Once you have done that, the remote will show "Sending information..." and after successful sending it will return to clock screen (this shouldn't take more than couple of minutes).
#* You can monitor the process by watching the Zwave log file on LinuxMCE (usually "/var/log/pluto/*ZWave.log"). Unfortunately the admin page doesn't give much information of what is being done and is everything going smoothly. If the process is successfully, you should see the LinuxMCE communicating with the USB controller
#* Make sure the sending remote controller is near enough the USB receiver, otherwise nothing will happen.
# Go to device tree (Show devices tree) and you should see ([[Media:zwave_devices_tree.png]]) the newly added ZWave modules/devices on the tree under "CORE -> ZWave".

You should do quick reload (Wizard -> Restart -> Quick Reload Router) in order to use the newly added devices with LinuxMCE. Once you have done that you should be able to control (like switching on/off) the devices under the Light ([[Media:zwave_lights.png]]).

== Setting associations ==
If you use SIS mode, associations will be set automatically, so that LMCE is always associated with each new device. This allows LMCE to receive messages when a device changes state.

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

== Tweak advanced ZWave settings ==
If you want to tweak some specific settings of your ZWave devices then read [[Tweak_advanced_ZWave_settings|this article]].

= Implementation =
== Open version ==
The new open Z-Wave driver will be included in the upcoming 0810 release.
The source code is available in LinuxMCE's SVN repository: http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src/ZWave.

A 32bit binary of the new Z-Wave driver for 0710 can be found here: http://vt100.at/files/ZWave-0.0.2-0710-32bit.bz2
Just swap with the existing /usr/pluto/bin/ZWave and quick reload the router.

== Fiire driver ==
Fiire (a company no longer in business) also provided a Z-Wave driver, it is binary only: [[Fiire ZWave Patch]]

== Old version ==
This is the version shipped with 0710. The source code for the old version is not available as it depends on proprietary files from Zensys.

== Z-Wave API documentation ==

[[ZWave API]]

ZWave

2010-07-31T19:09:31Z

Dpaul: /* SUC/SIS Mode (recommended) */

{{Versioninfo|810Status=Working|810UpdatedDate=12th May 2010|810UpdatedBy=sambuca}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Programmer's Guide]]
[[Category: Documentation]]

Z-Wave™ is a wireless RF-based communications technology designed for residential and light commercial control and status reading applications such as meter reading, lighting and appliance control, HVAC, access control, intruder and fire detection.

== Overview ==
The support from LinuxMCE system is represented by an executable '''ZWave''' (it's placed in /usr/pluto/bin) which is the device implementation and a '''DeviceTemplate (1754)''' which is used to create LinuxMCE Devices for ZWave.
There are high speed (4x 40kbps) and standard speed Z-Wave devices.

For information about what hardware to get look at [[Z-Wave Getting Started]], or check out the [[:Category:ZWave|Z-Wave Wiki Category]].

== How to install and use ZWave ==
=== Automatic installation - Lighting Wizard ===
The [[Lighting Wizard]] allows you to easily integrate LinuxMCE into your Z-Wave network. It is started after you plug in the Z-Wave dongle. Just follow the onscreen instructions. However the Lighting Wizard does not support SUC/SIS mode (see below) and because of this is now not the best way to include ZWave devices into your ZWave network. If you have a ZWave USB interface and an Inclusion Controller that supports SUC/SIS mode then this is the recommended configuration to use.

=== SUC/SIS Mode (recommended) ===
In SUC/SIS mode, LMCE adds your devices automatically as you include them into the Z-Wave network. Inclusion can be done using an inclusion remote or the "Add Node" command in LMCE (this option is really only successful in smaller test installations or possibly in smaller apartments for example). LMCE will assign new Node ids to the included devices and will add them in the Device tree under your ZWave USB interface

#To use the SUC/SIS mode, send a "Reset" command to the ZWave USB interface.
##In the web admin, go to Advanced -> Devices, find the ZWave device in the tree, select it, click "Send Command To Device" in the right pane.
##Select "Reset" and click Send Command. (Reset will remove all devices from you Z-Wave network).
#Next do a Reload Router (**This reload is essential**).
#When using SUC/SIS mode you must add an Inclusion Controller as the 2nd device in your ZWave network (the first device being the ZWave USB interface itself). An Inclusion Controller is the device you use to include ZWave devices into the ZWave network - this might be your ZWave remote control or possibly a wireless wall switch as these can often do double duty as an Inclusion Controller. You can add additional Inclusion Controllers or indeed any other ZWave devices at any time in the future as needed, and they will be added to your Device Tree automatically for you - this is the unique power of SUC/SIS.
##'''If using a Tricklestar Remote:'''
###First put the remote in configuration mode, then press and hold up until the LED flashes green, then press up four times. The LED will begin flashing green.
###Next select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen). The remote LED should go steady green indicating success. If it goes red then reset the remote (hold up til green, then hold up 10 seconds until 3 color LED), and redo step 1-2.
##'''If not using a tricklestar remote:'''
###Select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen).
###Next bring your Inclusion Controller close to your Core's/MD's ZWave USB interface and click once on its button or paddle (if a Wireless light switch) to include it into the ZWave Network. Your device should now indicate a successful inclusion if not repeat the last step.
# Do a quick reload of the router, twice.
#If your Inclusion Remote indicated a successful inclusion you are now ready to start including light switches and other devices using the device you added as an Inclusion Controller (ie your ZWave remote or a wireless Light Switch) - and not the 'Add Node' command in Web Admin.
#Place your inclusion controller device into Inclusion Mode (consult the devices manual for the details of how to include devices using it).
#Now while holding it close to the device you want to include press any button on the front of that device (usually one of the paddles on a light switch for example).
#Wait for the successful inclusion indication on the device you are including and if you have an Orbiter or Web Orbiter nearby you should also see a brief announcement that device was added successfully. A few second later a router reload screen will pop up - it is an important reload.
#Now you can move to the next device and include it. A router reload is suggested after each include.
#Keep doing this until all of your devices are included. With SUC/SIS there is no need to include all of your ZWave devices in one hit. You stop and continue another time without any issues. So adding some more devices months into the future is simple and easy to do.
#Check in Web Admin's Wizard->Devices->Lights page to make sure all of your included devices are present (if not do a reload router).

* Note: When including devices using SUC/SIS mode always start by including the devices that are closest to where the Core's ZWave USB interface is located and finish with the device that is furthest away. This enables the inclusion process to utilise the ZWave mesh network to communicate with the Core's ZWave USB interface.

* Not all ZWave interfaces support SIS mode. See the page of the individual interface to check, here is a list of interfaces [[Z-Wave Getting Started#Interface]].

=== Alternate setup of [[Tricklestar Remote]] (not recommended) ===

=== Manual setup / Download configuration ===
Once you have successfully installed the ZWave USB controller and it is seen on LinuxMCE ([[media:zwave_homepro_interface.png]]), you can proceed by populating the ZWave network information to LinuxMCE.

# Add your ZWave devices to your master ZWave master remote controller (like ZTH200)
#* Once the devices are added to remote and verified they are working (you can control them with your remote controller), you need to copy the ZWave network information to LinuxMCE.
# Go to LinuxMCE admin page (<nowiki>"http://dcerouter/lmce-admin/"</nowiki>), then choose "Wizard -> Devices -> Interfaces -> [your ZWave controller] -> Advanced".
## On the device page select "Send command to device".
## Select command "Download Configuration" and choose "Send Message".
##* Leave the data and file fields as blank
# Now LinuxMCE is waiting for the ZWave information and you should send a copy of the ZWave network with your master remote controller to LinuxMCE.
#* If you are using HomePro remote controller this is done by selecting: "Setup -> Copy Remote Ctrl. -> Send Information -> Identical Copy". Once you have done that, the remote will show "Sending information..." and after successful sending it will return to clock screen (this shouldn't take more than couple of minutes).
#* You can monitor the process by watching the Zwave log file on LinuxMCE (usually "/var/log/pluto/*ZWave.log"). Unfortunately the admin page doesn't give much information of what is being done and is everything going smoothly. If the process is successfully, you should see the LinuxMCE communicating with the USB controller
#* Make sure the sending remote controller is near enough the USB receiver, otherwise nothing will happen.
# Go to device tree (Show devices tree) and you should see ([[Media:zwave_devices_tree.png]]) the newly added ZWave modules/devices on the tree under "CORE -> ZWave".

You should do quick reload (Wizard -> Restart -> Quick Reload Router) in order to use the newly added devices with LinuxMCE. Once you have done that you should be able to control (like switching on/off) the devices under the Light ([[Media:zwave_lights.png]]).

== Setting associations ==
If you use SIS mode, associations will be set automatically, so that LMCE is always associated with each new device. This allows LMCE to receive messages when a device changes state.

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

== Tweak advanced ZWave settings ==
If you want to tweak some specific settings of your ZWave devices then read [[Tweak_advanced_ZWave_settings|this article]].

= Implementation =
== Open version ==
The new open Z-Wave driver will be included in the upcoming 0810 release.
The source code is available in LinuxMCE's SVN repository: http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src/ZWave.

A 32bit binary of the new Z-Wave driver for 0710 can be found here: http://vt100.at/files/ZWave-0.0.2-0710-32bit.bz2
Just swap with the existing /usr/pluto/bin/ZWave and quick reload the router.

== Fiire driver ==
Fiire (a company no longer in business) also provided a Z-Wave driver, it is binary only: [[Fiire ZWave Patch]]

== Old version ==
This is the version shipped with 0710. The source code for the old version is not available as it depends on proprietary files from Zensys.

== Z-Wave API documentation ==

[[ZWave API]]

ZWave

2010-07-31T18:12:21Z

Dpaul: /* Alternate setup making Tricklestar Remote the primary controller is not recommended */

{{Versioninfo|810Status=Working|810UpdatedDate=12th May 2010|810UpdatedBy=sambuca}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Programmer's Guide]]
[[Category: Documentation]]

Z-Wave™ is a wireless RF-based communications technology designed for residential and light commercial control and status reading applications such as meter reading, lighting and appliance control, HVAC, access control, intruder and fire detection.

== Overview ==
The support from LinuxMCE system is represented by an executable '''ZWave''' (it's placed in /usr/pluto/bin) which is the device implementation and a '''DeviceTemplate (1754)''' which is used to create LinuxMCE Devices for ZWave.
There are high speed (4x 40kbps) and standard speed Z-Wave devices.

For information about what hardware to get look at [[Z-Wave Getting Started]], or check out the [[:Category:ZWave|Z-Wave Wiki Category]].

== How to install and use ZWave ==
=== Automatic installation - Lighting Wizard ===
The [[Lighting Wizard]] allows you to easily integrate LinuxMCE into your Z-Wave network. It is started after you plug in the Z-Wave dongle. Just follow the onscreen instructions. However the Lighting Wizard does not support SUC/SIS mode (see below) and because of this is now not the best way to include ZWave devices into your ZWave network. If you have a ZWave USB interface and an Inclusion Controller that supports SUC/SIS mode then this is the recommended configuration to use.

=== SUC/SIS Mode (recommended) ===
In SUC/SIS mode, LMCE adds your devices automatically as you include them into the Z-Wave network. Inclusion can be done using an inclusion remote or the "Add Node" command in LMCE (this option is really only successful in smaller test installations or possibly in smaller apartments for example). LMCE will assign new Node ids to the included devices and will add them in the Device tree under your ZWave USB interface

#To use the SUC/SIS mode, send a "Reset" command to the ZWave USB interface.
##In the web admin, go to Advanced -> Devices, find the ZWave device in the tree, select it, click "Send Command To Device" in the right pane.
##Select "Reset" and click Send Command. (Reset will remove all devices from you Z-Wave network).
#Next do a Reload Router (**This reload is essential**).
#When using SUC/SIS mode you must add an Inclusion Controller as the 2nd device in your ZWave network (the first device being the ZWave USB interface itself). An Inclusion Controller is the device you use to include ZWave devices into the ZWave network - this might be your ZWave remote control or possibly a wireless wall switch as these can often do double duty as an Inclusion Controller. You can add additional Inclusion Controllers or indeed any other ZWave devices at any time in the future as needed, and they will be added to your Device Tree automatically for you - this is the unique power of SUC/SIS.
##'''If using a Tricklestar Remote:'''
###First put the remote in configuration mode, then press and hold up until the LED flashes green, then press up four times. The LED will begin flashing green.
###Next select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen). The remote LED should go steady green indicating success. If it goes red then reset the remote (hold up til green, then hold up 10 seconds until 3 color LED), and redo step 1-2.
##'''If not using a tricklestar remote:'''
###Select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen).
###Next bring your Inclusion Controller close to your Core's/MD's ZWave USB interface and click once on its button or paddle (if a Wireless light switch) to include it into the ZWave Network. Your device should now indicate a successful inclusion if not repeat the last step.
# Do a quick reload of the router, twice.
#If your Inclusion Remote indicated a successful inclusion you are now ready to start including light switches and other devices using the device you added as an Inclusion Controller (ie your ZWave remote or a wireless Light Switch) - and not the 'Add Node' command in Web Admin.
#Place your inclusion controller device into Inclusion Mode (consult the devices manual for the details of how to include devices using it).
#Now while holding it close to the device you want to include press any button on the front of that device (usually one of the paddles on a light switch for example).
#Wait for the successful inclusion indication on the device you are including and if you have an Orbiter or Web Orbiter nearby you should also see a brief announcement that device was added successfully.
#Now you can move to the next device and include it.
#Keep doing this until all of your devices are included. With SUC/SIS there is no need to include all of your ZWave devices in one hit. You stop and continue another time without any issues. So adding some more devices months into the future is simple and easy to do.
#Check in Web Admin's Wizard->Devices->Lights page to make sure all of your included devices are present (if not do a reload router).

* Note: When including devices using SUC/SIS mode always start by including the devices that are closest to where the Core's ZWave USB interface is located and finish with the device that is furthest away. This enables the inclusion process to utilise the ZWave mesh network to communicate with the Core's ZWave USB interface.

* Not all ZWave interfaces support SIS mode. See the page of the individual interface to check, here is a list of interfaces [[Z-Wave Getting Started#Interface]].

=== Alternate setup of [[Tricklestar Remote]] (not recommended) ===

=== Manual setup / Download configuration ===
Once you have successfully installed the ZWave USB controller and it is seen on LinuxMCE ([[media:zwave_homepro_interface.png]]), you can proceed by populating the ZWave network information to LinuxMCE.

# Add your ZWave devices to your master ZWave master remote controller (like ZTH200)
#* Once the devices are added to remote and verified they are working (you can control them with your remote controller), you need to copy the ZWave network information to LinuxMCE.
# Go to LinuxMCE admin page (<nowiki>"http://dcerouter/lmce-admin/"</nowiki>), then choose "Wizard -> Devices -> Interfaces -> [your ZWave controller] -> Advanced".
## On the device page select "Send command to device".
## Select command "Download Configuration" and choose "Send Message".
##* Leave the data and file fields as blank
# Now LinuxMCE is waiting for the ZWave information and you should send a copy of the ZWave network with your master remote controller to LinuxMCE.
#* If you are using HomePro remote controller this is done by selecting: "Setup -> Copy Remote Ctrl. -> Send Information -> Identical Copy". Once you have done that, the remote will show "Sending information..." and after successful sending it will return to clock screen (this shouldn't take more than couple of minutes).
#* You can monitor the process by watching the Zwave log file on LinuxMCE (usually "/var/log/pluto/*ZWave.log"). Unfortunately the admin page doesn't give much information of what is being done and is everything going smoothly. If the process is successfully, you should see the LinuxMCE communicating with the USB controller
#* Make sure the sending remote controller is near enough the USB receiver, otherwise nothing will happen.
# Go to device tree (Show devices tree) and you should see ([[Media:zwave_devices_tree.png]]) the newly added ZWave modules/devices on the tree under "CORE -> ZWave".

You should do quick reload (Wizard -> Restart -> Quick Reload Router) in order to use the newly added devices with LinuxMCE. Once you have done that you should be able to control (like switching on/off) the devices under the Light ([[Media:zwave_lights.png]]).

== Setting associations ==
If you use SIS mode, associations will be set automatically, so that LMCE is always associated with each new device. This allows LMCE to receive messages when a device changes state.

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

== Tweak advanced ZWave settings ==
If you want to tweak some specific settings of your ZWave devices then read [[Tweak_advanced_ZWave_settings|this article]].

= Implementation =
== Open version ==
The new open Z-Wave driver will be included in the upcoming 0810 release.
The source code is available in LinuxMCE's SVN repository: http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src/ZWave.

A 32bit binary of the new Z-Wave driver for 0710 can be found here: http://vt100.at/files/ZWave-0.0.2-0710-32bit.bz2
Just swap with the existing /usr/pluto/bin/ZWave and quick reload the router.

== Fiire driver ==
Fiire (a company no longer in business) also provided a Z-Wave driver, it is binary only: [[Fiire ZWave Patch]]

== Old version ==
This is the version shipped with 0710. The source code for the old version is not available as it depends on proprietary files from Zensys.

== Z-Wave API documentation ==

[[ZWave API]]

Tricklestar Remote

2010-07-31T18:11:51Z

Dpaul: /* Manual Setup using SUC Mode with the Tricklestar Remote */

= Alternate Setup using SUC Mode with the Tricklestar Remote =

'''This mode is not recommended as it makes the remote the primary controller, and the USB dongle the secondary controller!'''

SIS mode currently needs either the Seluxit ViaSens ZWave USB controller installed or the new Tricklestar USB Controller (see here for info on installing this controller [[ZWave_DeviceTemplate_PlugAndPlay | ZWave Device Template Plug'n'Play]]). Please note that you cannot currently use the Lighting Wizard when configuring SIS mode. You will also need to update to a current version of the new Open ZWave binary.

# Firstly reset your ZWave USB controller so that you can start to add devices in SIS mode. Use Web Admin ->Wizard->Devices->Interfaces and find the device called 'ZWave' and click its 'Advanced' button. In the next screen click on 'Send command to device' and then select 'Reset' from the drop-down list, Tick 'Delivery Confirmation' and then click 'Send Message'. Now if you see 'Message received OK' your ZWave USB controller has been successfully reset.
# Next we need to download the configuration from the Tricklestar remote into your USB ZWave controller ie we are making it a 'Secondary Controller' on the ZWave network. Firstly we need to set the remote into Configuration Mode (see also the manual) this is done with the little switch on the bottom side next to the USB connector. Then do the following button presses on the Tricklestar remote which should be in close proximity to the ZWave USB interface - Press and hold the Remotes top most button down until you see a Green LED light up then release the button and press it briefly again. The Green LED should now be blinking slowly (if it isn't then repeat this step again). Now back in Web Admin use the 'Send Command to Device' screen again and select 'Download Configuration' from the drop-down. Now click 'Send Message' and watch the slowly flashing Green LED on the remote. If the LED stops flashing and glows continuously green for a few seconds then you have succeeded in including the Remote. However if you see a Red LED displayed continuously for a few secs something went wrong - in this case please repeat this whole step again. Assuming you got a Green LED at the end of this step you should (after waiting a couple of minutes for the inclusion prcess to finish) do a reload router before continuing. NOTE: If it does not work that way, try sending the 'Download Configuration' command first and then press and hold the Remotes top most button down until it goes green and the press the same button again shortly, that way around it worked better for me (was a tip from Hari).
# Next we can Include each of your ZWave devices into the ZWave network (before starting to include devices it is important that they are located and fixed in their final locations). Using the Tricklestar remote go to each ZWave device (again you should be in close proximity to each device as you Include them) and do the following;
## Press and hold the Remotes top most button down until you see a Green LED light up then release the button and press it briefly again. The Green LED should now be blinking slowly (if it isn't then repeat this step again).
## Now briefly press the Inclusion button on the device you are including. You should see the remotes Green LED stop flashing and glow continuously Green for a few seconds. If you did then you have succeeded in including the device. However if you see a Red LED displayed continuously for a few secs something went wrong - in this case please repeat this whole step again.
## Repeat the step above for each ZWave device would like to include in your ZWave network.
# After including your last ZWave device, go back to Web Admin, do a reload router (or maybe two if LinuxMCE tells you to) and select Wizards->Devices->Lights. You should now see all the devices you included have been auto-magically added to the 'Wizard: Lights' screen! This is power of SIS mode! Now you can change your device names in the 'Description' field, select which 'Room' they are actually in and use 'PK_FloorplanObjectType' drop-down to select the floor plan icon they will display when placed on the floor plan etc. When you have updated this info for each ZWave device click 'Update' at the bottom of the screen.
# If devices are not added automatically - meaning there is no popup on the Orbiters showing "added new device X" - then you can try this. If you have added logging you wil see in /var/log/pluto/*_ZWave.log" that lightswitches are detected by the USB controller because it shows up like this "Got basic report from node X, value: X". After addind the first device go to the USB Controller and do a 'Download Configuration' like above again - but this time '''without''' doing a 'reset' first. Then do a quick reload router once or twice and try adding the next device. Now it should work.

Of course at anytime when you want to add some new ZWave devices to your installation just do the inclusion steps above with the remote & the device your adding - you dont need to add all your devices in one go. Each time you include a new device just do a reload router and auto-magically it will be in your ZWave devices tree.

Note, you should never do the download config again after you have initially added the USB controller to the Tricklestar remote. To add a new node just put the Tricklestar into config mode with the switch and then add the new nodes with the "up till flash- up" procedure. Same for device removal. The Tricklestar will notify the USB controller about the change. This is automatically detected by LinuxMCE and you will see a popup on all orbiters with the new zwave node id.

= Manual Excluding devices using SIS Mode with the Tricklestar Remote =

Why do I have to do this ? (Quote from hari)
Z-Wave is a mesh. The routing table is updated at inclusion/exclusion. When you move stuff around without following the procedure (except portable devices like remote controllers) you can get network problems.

# Put the Configuration Switch of the Trickestar Remote in “Configuration Mode” like this. Press-and-hold “Up” Operation button for 2 seconds to enter Configuration Mode. LED Indicator will illuminate Green. Short-press the “Down” Operation Button one time to put the device into Exclusion Mode. The Green LED should now be blinking slowly (if it isn't then repeat this step again).
# Press the Exclusion Initiator of the Device to be Excluded (normally the same button as the Inclusion Initiator).
# LED Indicator on the Remote will illuminate Green when device is successfully excluded and illuminate Red if the operation is unsuccessful. Orbiters will show a message that the device is removed.
# Repeat steps 2-4 for each Device to be Excluded from the Network.
# After Excluding all the devices that you would like to remove, go back to Web Admin, do a reload router and select Wizards->Devices->Lights. The Excluded devices should now be gone.

Tricklestar Remote

2010-07-31T18:10:18Z

Dpaul: /* Manual Setup using SIS Mode with the Tricklestar Remote */

= Manual Setup using SIS Mode with the Tricklestar Remote =

'''This mode is not recommended as it makes the remote the primary controller, and the USB dongle the secondary controller!'''

SIS mode currently needs either the Seluxit ViaSens ZWave USB controller installed or the new Tricklestar USB Controller (see here for info on installing this controller [[ZWave_DeviceTemplate_PlugAndPlay | ZWave Device Template Plug'n'Play]]). Please note that you cannot currently use the Lighting Wizard when configuring SIS mode. You will also need to update to a current version of the new Open ZWave binary.

# Firstly reset your ZWave USB controller so that you can start to add devices in SIS mode. Use Web Admin ->Wizard->Devices->Interfaces and find the device called 'ZWave' and click its 'Advanced' button. In the next screen click on 'Send command to device' and then select 'Reset' from the drop-down list, Tick 'Delivery Confirmation' and then click 'Send Message'. Now if you see 'Message received OK' your ZWave USB controller has been successfully reset.
# Next we need to download the configuration from the Tricklestar remote into your USB ZWave controller ie we are making it a 'Secondary Controller' on the ZWave network. Firstly we need to set the remote into Configuration Mode (see also the manual) this is done with the little switch on the bottom side next to the USB connector. Then do the following button presses on the Tricklestar remote which should be in close proximity to the ZWave USB interface - Press and hold the Remotes top most button down until you see a Green LED light up then release the button and press it briefly again. The Green LED should now be blinking slowly (if it isn't then repeat this step again). Now back in Web Admin use the 'Send Command to Device' screen again and select 'Download Configuration' from the drop-down. Now click 'Send Message' and watch the slowly flashing Green LED on the remote. If the LED stops flashing and glows continuously green for a few seconds then you have succeeded in including the Remote. However if you see a Red LED displayed continuously for a few secs something went wrong - in this case please repeat this whole step again. Assuming you got a Green LED at the end of this step you should (after waiting a couple of minutes for the inclusion prcess to finish) do a reload router before continuing. NOTE: If it does not work that way, try sending the 'Download Configuration' command first and then press and hold the Remotes top most button down until it goes green and the press the same button again shortly, that way around it worked better for me (was a tip from Hari).
# Next we can Include each of your ZWave devices into the ZWave network (before starting to include devices it is important that they are located and fixed in their final locations). Using the Tricklestar remote go to each ZWave device (again you should be in close proximity to each device as you Include them) and do the following;
## Press and hold the Remotes top most button down until you see a Green LED light up then release the button and press it briefly again. The Green LED should now be blinking slowly (if it isn't then repeat this step again).
## Now briefly press the Inclusion button on the device you are including. You should see the remotes Green LED stop flashing and glow continuously Green for a few seconds. If you did then you have succeeded in including the device. However if you see a Red LED displayed continuously for a few secs something went wrong - in this case please repeat this whole step again.
## Repeat the step above for each ZWave device would like to include in your ZWave network.
# After including your last ZWave device, go back to Web Admin, do a reload router (or maybe two if LinuxMCE tells you to) and select Wizards->Devices->Lights. You should now see all the devices you included have been auto-magically added to the 'Wizard: Lights' screen! This is power of SIS mode! Now you can change your device names in the 'Description' field, select which 'Room' they are actually in and use 'PK_FloorplanObjectType' drop-down to select the floor plan icon they will display when placed on the floor plan etc. When you have updated this info for each ZWave device click 'Update' at the bottom of the screen.
# If devices are not added automatically - meaning there is no popup on the Orbiters showing "added new device X" - then you can try this. If you have added logging you wil see in /var/log/pluto/*_ZWave.log" that lightswitches are detected by the USB controller because it shows up like this "Got basic report from node X, value: X". After addind the first device go to the USB Controller and do a 'Download Configuration' like above again - but this time '''without''' doing a 'reset' first. Then do a quick reload router once or twice and try adding the next device. Now it should work.

Of course at anytime when you want to add some new ZWave devices to your installation just do the inclusion steps above with the remote & the device your adding - you dont need to add all your devices in one go. Each time you include a new device just do a reload router and auto-magically it will be in your ZWave devices tree.

Note, you should never do the download config again after you have initially added the USB controller to the Tricklestar remote. To add a new node just put the Tricklestar into config mode with the switch and then add the new nodes with the "up till flash- up" procedure. Same for device removal. The Tricklestar will notify the USB controller about the change. This is automatically detected by LinuxMCE and you will see a popup on all orbiters with the new zwave node id.

= Manual Excluding devices using SIS Mode with the Tricklestar Remote =

Why do I have to do this ? (Quote from hari)
Z-Wave is a mesh. The routing table is updated at inclusion/exclusion. When you move stuff around without following the procedure (except portable devices like remote controllers) you can get network problems.

# Put the Configuration Switch of the Trickestar Remote in “Configuration Mode” like this. Press-and-hold “Up” Operation button for 2 seconds to enter Configuration Mode. LED Indicator will illuminate Green. Short-press the “Down” Operation Button one time to put the device into Exclusion Mode. The Green LED should now be blinking slowly (if it isn't then repeat this step again).
# Press the Exclusion Initiator of the Device to be Excluded (normally the same button as the Inclusion Initiator).
# LED Indicator on the Remote will illuminate Green when device is successfully excluded and illuminate Red if the operation is unsuccessful. Orbiters will show a message that the device is removed.
# Repeat steps 2-4 for each Device to be Excluded from the Network.
# After Excluding all the devices that you would like to remove, go back to Web Admin, do a reload router and select Wizards->Devices->Lights. The Excluded devices should now be gone.

ZWave

2010-07-31T18:09:03Z

Dpaul: /* Setup using Tricklestar Remote */

{{Versioninfo|810Status=Working|810UpdatedDate=12th May 2010|810UpdatedBy=sambuca}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Programmer's Guide]]
[[Category: Documentation]]

Z-Wave™ is a wireless RF-based communications technology designed for residential and light commercial control and status reading applications such as meter reading, lighting and appliance control, HVAC, access control, intruder and fire detection.

== Overview ==
The support from LinuxMCE system is represented by an executable '''ZWave''' (it's placed in /usr/pluto/bin) which is the device implementation and a '''DeviceTemplate (1754)''' which is used to create LinuxMCE Devices for ZWave.
There are high speed (4x 40kbps) and standard speed Z-Wave devices.

For information about what hardware to get look at [[Z-Wave Getting Started]], or check out the [[:Category:ZWave|Z-Wave Wiki Category]].

== How to install and use ZWave ==
=== Automatic installation - Lighting Wizard ===
The [[Lighting Wizard]] allows you to easily integrate LinuxMCE into your Z-Wave network. It is started after you plug in the Z-Wave dongle. Just follow the onscreen instructions. However the Lighting Wizard does not support SUC/SIS mode (see below) and because of this is now not the best way to include ZWave devices into your ZWave network. If you have a ZWave USB interface and an Inclusion Controller that supports SUC/SIS mode then this is the recommended configuration to use.

=== SUC/SIS Mode (recommended) ===
In SUC/SIS mode, LMCE adds your devices automatically as you include them into the Z-Wave network. Inclusion can be done using an inclusion remote or the "Add Node" command in LMCE (this option is really only successful in smaller test installations or possibly in smaller apartments for example). LMCE will assign new Node ids to the included devices and will add them in the Device tree under your ZWave USB interface

#To use the SUC/SIS mode, send a "Reset" command to the ZWave USB interface.
##In the web admin, go to Advanced -> Devices, find the ZWave device in the tree, select it, click "Send Command To Device" in the right pane.
##Select "Reset" and click Send Command. (Reset will remove all devices from you Z-Wave network).
#Next do a Reload Router (**This reload is essential**).
#When using SUC/SIS mode you must add an Inclusion Controller as the 2nd device in your ZWave network (the first device being the ZWave USB interface itself). An Inclusion Controller is the device you use to include ZWave devices into the ZWave network - this might be your ZWave remote control or possibly a wireless wall switch as these can often do double duty as an Inclusion Controller. You can add additional Inclusion Controllers or indeed any other ZWave devices at any time in the future as needed, and they will be added to your Device Tree automatically for you - this is the unique power of SUC/SIS.
##'''If using a Tricklestar Remote:'''
###First put the remote in configuration mode, then press and hold up until the LED flashes green, then press up four times. The LED will begin flashing green.
###Next select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen). The remote LED should go steady green indicating success. If it goes red then reset the remote (hold up til green, then hold up 10 seconds until 3 color LED), and redo step 1-2.
##'''If not using a tricklestar remote:'''
###Select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen).
###Next bring your Inclusion Controller close to your Core's/MD's ZWave USB interface and click once on its button or paddle (if a Wireless light switch) to include it into the ZWave Network. Your device should now indicate a successful inclusion if not repeat the last step.
# Do a quick reload of the router, twice.
#If your Inclusion Remote indicated a successful inclusion you are now ready to start including light switches and other devices using the device you added as an Inclusion Controller (ie your ZWave remote or a wireless Light Switch) - and not the 'Add Node' command in Web Admin.
#Place your inclusion controller device into Inclusion Mode (consult the devices manual for the details of how to include devices using it).
#Now while holding it close to the device you want to include press any button on the front of that device (usually one of the paddles on a light switch for example).
#Wait for the successful inclusion indication on the device you are including and if you have an Orbiter or Web Orbiter nearby you should also see a brief announcement that device was added successfully.
#Now you can move to the next device and include it.
#Keep doing this until all of your devices are included. With SUC/SIS there is no need to include all of your ZWave devices in one hit. You stop and continue another time without any issues. So adding some more devices months into the future is simple and easy to do.
#Check in Web Admin's Wizard->Devices->Lights page to make sure all of your included devices are present (if not do a reload router).

* Note: When including devices using SUC/SIS mode always start by including the devices that are closest to where the Core's ZWave USB interface is located and finish with the device that is furthest away. This enables the inclusion process to utilise the ZWave mesh network to communicate with the Core's ZWave USB interface.

* Not all ZWave interfaces support SIS mode. See the page of the individual interface to check, here is a list of interfaces [[Z-Wave Getting Started#Interface]].

=== Alternate setup making [[Tricklestar Remote]] the primary controller is not recommended ===

=== Manual setup / Download configuration ===
Once you have successfully installed the ZWave USB controller and it is seen on LinuxMCE ([[media:zwave_homepro_interface.png]]), you can proceed by populating the ZWave network information to LinuxMCE.

# Add your ZWave devices to your master ZWave master remote controller (like ZTH200)
#* Once the devices are added to remote and verified they are working (you can control them with your remote controller), you need to copy the ZWave network information to LinuxMCE.
# Go to LinuxMCE admin page (<nowiki>"http://dcerouter/lmce-admin/"</nowiki>), then choose "Wizard -> Devices -> Interfaces -> [your ZWave controller] -> Advanced".
## On the device page select "Send command to device".
## Select command "Download Configuration" and choose "Send Message".
##* Leave the data and file fields as blank
# Now LinuxMCE is waiting for the ZWave information and you should send a copy of the ZWave network with your master remote controller to LinuxMCE.
#* If you are using HomePro remote controller this is done by selecting: "Setup -> Copy Remote Ctrl. -> Send Information -> Identical Copy". Once you have done that, the remote will show "Sending information..." and after successful sending it will return to clock screen (this shouldn't take more than couple of minutes).
#* You can monitor the process by watching the Zwave log file on LinuxMCE (usually "/var/log/pluto/*ZWave.log"). Unfortunately the admin page doesn't give much information of what is being done and is everything going smoothly. If the process is successfully, you should see the LinuxMCE communicating with the USB controller
#* Make sure the sending remote controller is near enough the USB receiver, otherwise nothing will happen.
# Go to device tree (Show devices tree) and you should see ([[Media:zwave_devices_tree.png]]) the newly added ZWave modules/devices on the tree under "CORE -> ZWave".

You should do quick reload (Wizard -> Restart -> Quick Reload Router) in order to use the newly added devices with LinuxMCE. Once you have done that you should be able to control (like switching on/off) the devices under the Light ([[Media:zwave_lights.png]]).

== Setting associations ==
If you use SIS mode, associations will be set automatically, so that LMCE is always associated with each new device. This allows LMCE to receive messages when a device changes state.

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

== Tweak advanced ZWave settings ==
If you want to tweak some specific settings of your ZWave devices then read [[Tweak_advanced_ZWave_settings|this article]].

= Implementation =
== Open version ==
The new open Z-Wave driver will be included in the upcoming 0810 release.
The source code is available in LinuxMCE's SVN repository: http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src/ZWave.

A 32bit binary of the new Z-Wave driver for 0710 can be found here: http://vt100.at/files/ZWave-0.0.2-0710-32bit.bz2
Just swap with the existing /usr/pluto/bin/ZWave and quick reload the router.

== Fiire driver ==
Fiire (a company no longer in business) also provided a Z-Wave driver, it is binary only: [[Fiire ZWave Patch]]

== Old version ==
This is the version shipped with 0710. The source code for the old version is not available as it depends on proprietary files from Zensys.

== Z-Wave API documentation ==

[[ZWave API]]

ZWave

2010-07-31T18:07:42Z

Dpaul: /* SUC/SIS Mode (recommended) */

{{Versioninfo|810Status=Working|810UpdatedDate=12th May 2010|810UpdatedBy=sambuca}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Programmer's Guide]]
[[Category: Documentation]]

Z-Wave™ is a wireless RF-based communications technology designed for residential and light commercial control and status reading applications such as meter reading, lighting and appliance control, HVAC, access control, intruder and fire detection.

== Overview ==
The support from LinuxMCE system is represented by an executable '''ZWave''' (it's placed in /usr/pluto/bin) which is the device implementation and a '''DeviceTemplate (1754)''' which is used to create LinuxMCE Devices for ZWave.
There are high speed (4x 40kbps) and standard speed Z-Wave devices.

For information about what hardware to get look at [[Z-Wave Getting Started]], or check out the [[:Category:ZWave|Z-Wave Wiki Category]].

== How to install and use ZWave ==
=== Automatic installation - Lighting Wizard ===
The [[Lighting Wizard]] allows you to easily integrate LinuxMCE into your Z-Wave network. It is started after you plug in the Z-Wave dongle. Just follow the onscreen instructions. However the Lighting Wizard does not support SUC/SIS mode (see below) and because of this is now not the best way to include ZWave devices into your ZWave network. If you have a ZWave USB interface and an Inclusion Controller that supports SUC/SIS mode then this is the recommended configuration to use.

=== SUC/SIS Mode (recommended) ===
In SUC/SIS mode, LMCE adds your devices automatically as you include them into the Z-Wave network. Inclusion can be done using an inclusion remote or the "Add Node" command in LMCE (this option is really only successful in smaller test installations or possibly in smaller apartments for example). LMCE will assign new Node ids to the included devices and will add them in the Device tree under your ZWave USB interface

#To use the SUC/SIS mode, send a "Reset" command to the ZWave USB interface.
##In the web admin, go to Advanced -> Devices, find the ZWave device in the tree, select it, click "Send Command To Device" in the right pane.
##Select "Reset" and click Send Command. (Reset will remove all devices from you Z-Wave network).
#Next do a Reload Router (**This reload is essential**).
#When using SUC/SIS mode you must add an Inclusion Controller as the 2nd device in your ZWave network (the first device being the ZWave USB interface itself). An Inclusion Controller is the device you use to include ZWave devices into the ZWave network - this might be your ZWave remote control or possibly a wireless wall switch as these can often do double duty as an Inclusion Controller. You can add additional Inclusion Controllers or indeed any other ZWave devices at any time in the future as needed, and they will be added to your Device Tree automatically for you - this is the unique power of SUC/SIS.
##'''If using a Tricklestar Remote:'''
###First put the remote in configuration mode, then press and hold up until the LED flashes green, then press up four times. The LED will begin flashing green.
###Next select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen). The remote LED should go steady green indicating success. If it goes red then reset the remote (hold up til green, then hold up 10 seconds until 3 color LED), and redo step 1-2.
##'''If not using a tricklestar remote:'''
###Select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen).
###Next bring your Inclusion Controller close to your Core's/MD's ZWave USB interface and click once on its button or paddle (if a Wireless light switch) to include it into the ZWave Network. Your device should now indicate a successful inclusion if not repeat the last step.
# Do a quick reload of the router, twice.
#If your Inclusion Remote indicated a successful inclusion you are now ready to start including light switches and other devices using the device you added as an Inclusion Controller (ie your ZWave remote or a wireless Light Switch) - and not the 'Add Node' command in Web Admin.
#Place your inclusion controller device into Inclusion Mode (consult the devices manual for the details of how to include devices using it).
#Now while holding it close to the device you want to include press any button on the front of that device (usually one of the paddles on a light switch for example).
#Wait for the successful inclusion indication on the device you are including and if you have an Orbiter or Web Orbiter nearby you should also see a brief announcement that device was added successfully.
#Now you can move to the next device and include it.
#Keep doing this until all of your devices are included. With SUC/SIS there is no need to include all of your ZWave devices in one hit. You stop and continue another time without any issues. So adding some more devices months into the future is simple and easy to do.
#Check in Web Admin's Wizard->Devices->Lights page to make sure all of your included devices are present (if not do a reload router).

* Note: When including devices using SUC/SIS mode always start by including the devices that are closest to where the Core's ZWave USB interface is located and finish with the device that is furthest away. This enables the inclusion process to utilise the ZWave mesh network to communicate with the Core's ZWave USB interface.

* Not all ZWave interfaces support SIS mode. See the page of the individual interface to check, here is a list of interfaces [[Z-Wave Getting Started#Interface]].

=== Setup using [[Tricklestar Remote]] ===

=== Manual setup / Download configuration ===
Once you have successfully installed the ZWave USB controller and it is seen on LinuxMCE ([[media:zwave_homepro_interface.png]]), you can proceed by populating the ZWave network information to LinuxMCE.

# Add your ZWave devices to your master ZWave master remote controller (like ZTH200)
#* Once the devices are added to remote and verified they are working (you can control them with your remote controller), you need to copy the ZWave network information to LinuxMCE.
# Go to LinuxMCE admin page (<nowiki>"http://dcerouter/lmce-admin/"</nowiki>), then choose "Wizard -> Devices -> Interfaces -> [your ZWave controller] -> Advanced".
## On the device page select "Send command to device".
## Select command "Download Configuration" and choose "Send Message".
##* Leave the data and file fields as blank
# Now LinuxMCE is waiting for the ZWave information and you should send a copy of the ZWave network with your master remote controller to LinuxMCE.
#* If you are using HomePro remote controller this is done by selecting: "Setup -> Copy Remote Ctrl. -> Send Information -> Identical Copy". Once you have done that, the remote will show "Sending information..." and after successful sending it will return to clock screen (this shouldn't take more than couple of minutes).
#* You can monitor the process by watching the Zwave log file on LinuxMCE (usually "/var/log/pluto/*ZWave.log"). Unfortunately the admin page doesn't give much information of what is being done and is everything going smoothly. If the process is successfully, you should see the LinuxMCE communicating with the USB controller
#* Make sure the sending remote controller is near enough the USB receiver, otherwise nothing will happen.
# Go to device tree (Show devices tree) and you should see ([[Media:zwave_devices_tree.png]]) the newly added ZWave modules/devices on the tree under "CORE -> ZWave".

You should do quick reload (Wizard -> Restart -> Quick Reload Router) in order to use the newly added devices with LinuxMCE. Once you have done that you should be able to control (like switching on/off) the devices under the Light ([[Media:zwave_lights.png]]).

== Setting associations ==
If you use SIS mode, associations will be set automatically, so that LMCE is always associated with each new device. This allows LMCE to receive messages when a device changes state.

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

== Tweak advanced ZWave settings ==
If you want to tweak some specific settings of your ZWave devices then read [[Tweak_advanced_ZWave_settings|this article]].

= Implementation =
== Open version ==
The new open Z-Wave driver will be included in the upcoming 0810 release.
The source code is available in LinuxMCE's SVN repository: http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src/ZWave.

A 32bit binary of the new Z-Wave driver for 0710 can be found here: http://vt100.at/files/ZWave-0.0.2-0710-32bit.bz2
Just swap with the existing /usr/pluto/bin/ZWave and quick reload the router.

== Fiire driver ==
Fiire (a company no longer in business) also provided a Z-Wave driver, it is binary only: [[Fiire ZWave Patch]]

== Old version ==
This is the version shipped with 0710. The source code for the old version is not available as it depends on proprietary files from Zensys.

== Z-Wave API documentation ==

[[ZWave API]]

File:Vpn1.jpg

2010-07-27T15:44:27Z

Dpaul: uploaded a new version of "Image:Vpn1.jpg"

VPN

2010-07-27T15:43:23Z

Dpaul:

{{versioninfo}}
[[Category: Networking]]
VPN (Virtual Private Networking) provides secure communication to your core when you are away. It also offers a lot of potential for connecting multiple cores (between houses, apartments, etc.). This would enable families and friends to share security cameras, call/intercom each other for free via Asterisk, pipe security notifications to every device at every connected residence, and possibly even share media (legality?)
==Installing PPTP and OpenVPN on the core==
Download the patches and vpn package

Apply the diff patch
cd /var/www/lmce-admin ; sudo patch -p0 < /tmp/vpn.svn.diff

Install the php scripts
cd /var/www/lmce-admin ; sudo tar -xvf /tmp/vpn-php.tar

Install the package
sudo dpkg -i /tmp/lmce-vpn-scripts_1-2_all.deb

Now go to the web admin -> users and check out your new links.

[[Image:Vpn1.jpg]]

Click the PPTP Password link to set up PPTP and set user passwords. Click "Delete User" to disable PPTP for that user only.

[[Image:PPTP1.jpg]]

Click OpenVPN Config to set up OpenVPN and generate user configurations

[[Image:Openvpn1.jpg]]

Once the set up is finished, you can download the configs or Delete the user.

[[Image:Openvpn2.jpg]]

==Setting up the VPN clients==

==Requirements for a VPN plugin==
* Security
** Encryption
** Secure method of "pairing" houses
This could be done by sharing a public key with whomever you wish to pair with. User 1 would enter User 2's public key along with an optional message. User 2 would manually approve User 1 for pairing, and the cores would connect securly via VPN and automatically share security notifications and anything else set in a settings panel.
* Options panel for data to share with "paired" cores

==Wish List==

Add what you would like VPN to make possible in LinuxMCE

==External Links==
#[http://openvpn.net/ OpenVPN]

VPN

2010-07-27T15:01:42Z

Dpaul:

{{versioninfo}}
[[Category: Networking]]
VPN (Virtual Private Networking) provides secure communication to your core when you are away. It also offers a lot of potential for connecting multiple cores (between houses, apartments, etc.). This would enable families and friends to share security cameras, call/intercom each other for free via Asterisk, pipe security notifications to every device at every connected residence, and possibly even share media (legality?)
==Installing PPTP and OpenVPN on the core==
Download the patches and vpn package

Apply the diff patch
cd /var/www/lmce-admin ; sudo patch -p0 < /tmp/vpn.svn.diff

Install the php scripts
cd /var/www/lmce-admin ; sudo tar -xvf /tmp/vpn-php.tar

Install the package
sudo dpkg -i /tmp/lmce-vpn-scripts_1-2_all.deb

Now go to the web admin -> users and check out your capabilites.

[[Image:Vpn1.jpg]]

Click the PPTP Password link to set up PPTP and set user passwords. Click "Delete User" to disable PPTP for that user only.

[[Image:PPTP1.jpg]]

Click OpenVPN Config to set up OpenVPN and generate user configurations

[[Image:Openvpn1.jpg]]

Once the set up is finished, you can download the configs or Delete the user.

[[Image:Openvpn2.jpg]]

==Setting up the VPN clients==

==Requirements for a VPN plugin==
* Security
** Encryption
** Secure method of "pairing" houses
This could be done by sharing a public key with whomever you wish to pair with. User 1 would enter User 2's public key along with an optional message. User 2 would manually approve User 1 for pairing, and the cores would connect securly via VPN and automatically share security notifications and anything else set in a settings panel.
* Options panel for data to share with "paired" cores

==Wish List==

Add what you would like VPN to make possible in LinuxMCE

==External Links==
#[http://openvpn.net/ OpenVPN]

VPN

2010-07-27T15:01:16Z

Dpaul:

{{versioninfo}}
[[Category: Networking]]
VPN (Virtual Private Networking) provides secure communication to your core when you are away. It also offers a lot of potential for connecting multiple cores (between houses, apartments, etc.). This would enable families and friends to share security cameras, call/intercom each other for free via Asterisk, pipe security notifications to every device at every connected residence, and possibly even share media (legality?)
==Installing PPTP and OpenVPN on the core==
Download the diff and package

Apply the diff patch
cd /var/www/lmce-admin ; sudo patch -p0 < /tmp/vpn.svn.diff

Install the php scripts
cd /var/www/lmce-admin ; sudo tar -xvf /tmp/vpn-php.tar

Install the package
sudo dpkg -i /tmp/lmce-vpn-scripts_1-2_all.deb

Now go to the web admin -> users and check out your capabilites.

[[Image:Vpn1.jpg]]

Click the PPTP Password link to set up PPTP and set user passwords. Click "Delete User" to disable PPTP for that user only.

[[Image:PPTP1.jpg]]

Click OpenVPN Config to set up OpenVPN and generate user configurations

[[Image:Openvpn1.jpg]]

Once the set up is finished, you can download the configs or Delete the user.

[[Image:Openvpn2.jpg]]

==Setting up the VPN clients==

==Requirements for a VPN plugin==
* Security
** Encryption
** Secure method of "pairing" houses
This could be done by sharing a public key with whomever you wish to pair with. User 1 would enter User 2's public key along with an optional message. User 2 would manually approve User 1 for pairing, and the cores would connect securly via VPN and automatically share security notifications and anything else set in a settings panel.
* Options panel for data to share with "paired" cores

==Wish List==

Add what you would like VPN to make possible in LinuxMCE

==External Links==
#[http://openvpn.net/ OpenVPN]

File:Openvpn1.jpg

2010-07-27T14:30:59Z

Dpaul: uploaded a new version of "Image:Openvpn1.jpg"

File:Openvpn2.jpg

2010-07-27T14:27:28Z

Dpaul:

File:PPTP1.jpg

2010-07-27T14:25:19Z

Dpaul:

File:Openvpn1.jpg

2010-07-27T14:23:59Z

Dpaul:

File:Vpn1.jpg

2010-07-27T14:18:51Z

Dpaul:

Play Games on LinuxMCE

2009-10-01T04:50:45Z

Dpaul: /* Wait 60 seconds for LinuxMCE to identify and Tag the Media */

In addition to audio and video media, LinuxMCE can play games originally designed for many different game systems. LinuxMCE contains a copy of the Multiple Arcade Machine Emulator (MAME) to play arcade games, and the Multiple Emulator Super System (MESS) to play games meant for many home video game systems.

== Supported Systems ==

LinuxMCE currently can support the following game systems:

* [[Arcade games emulated by MAME]]
* [[Atari 2600]]
* [[Atari 5200]]
* [[Atari 7800]]

With each game system, LinuxMCE presents integrated controls for all supported control methods, and provides a seamless way to import, catalog, and play all the games stored on your core or any attached storage device. Simply copy the ROMs into their respective system folders, and LinuxMCE will attempt to identify, and tag each one to the best of its ability.

[[Notes on how LinuxMCE Detects ROMs]]

== Enabling The Game Player ==

To use the Game support, you must enable the Game Player. The Game Player adds support for all the above game systems to a Media Director at once, and '''you must enable the Game Player on each Media Director you wish to be able to play games.'''

=== Quick Instructions for those Familiar with LinuxMCE ===

# Go to http://dcerouter/ (the web admin)
# from the Top menu, go to Wizard > [[Media Directors]]
# Find the media director on which you wish to enable Game Support.
# Press the [ Edit ] Button next to Software Modules
# Find the Game Player. Select it by checking its box.
# Press [ Save ]
# Watch your nearest orbiter for messages. You should see installation messages.
## When asked, Press Quick Reload Router
## When the Orbiter re-appears, it will ask you to regenerate orbiters. Regenerate all orbiters in the house.
# The Games Button should now be visible under [[Media]]

=== Step by Step Instructions ===

==== Go to http://dcerouter/ ====

[[Image:WebAdminLogon.png|right|Logging Onto the Web Admin]]

For information on Logging into the Web Admin, go here: [[LinuxMCE Admin Website]]

==== Go to Wizard > [[Media Directors]] ====

[[Image:WizardMediaDirectors.png|right]]

The Wizard > [[Media Directors]] Page provides everything you need to adjust the operation of each media director in the house. For each system you wish to be able to play games, you need to do these instructions.

==== Press the Edit button next to [[Software Modules]] ====

The Software Modules page allows you to select software that can easily be installed into [[LinuxMCE]] To be installed onto each media director. We want to select the Game Player.

==== Find and Select the Game Player and press Save ====

[[Image:WizardMediaDirectorsSoftwareModulesGamePlayer.png|right]]

If you wish to uninstall the [[Game Player]] at a later time for this media director, simply uncheck the box, and press '''Save'''.

==== Watch your orbiter for Installation Messages ====

Your Orbiter should emit many messages relating to the installation of the software. If this is the first media director you are installing onto, the [[Core]] will also need to install the [[Game PlugIn]] so that it can manage the different [[Game Player]] instances throughout the house. The installation of the Game PlugIn also installs data packages which provide metadata and images for game ROMs to make the automatic game cataloguing process possible. '''This process of installing the [[Game PlugIn]] the first time can take a long time. Please Be Patient. Subsequent installations do not take as much time.''' We will improve this installation time significantly in future releases.

==== Reload Your Router ====

Once the installation process is complete, the system will ask you to reload the router. ''You must do this so the system can use the Game Player.'' Press '''[[Quick Reload Router]]''' This process should take approximately 15 seconds.

==== Regenerate Your Orbiters ====

Once your router is reloaded, and the system finds the new [[Game Player]] running, it will ask to regenerate all your orbiters in the house so that the Games button will be visible. This process should take approximately 2 minutes, per [[Orbiter]] on average.

== Loading Games onto the system ==

Once the Game PlugIn has been installed, you will then need to install some games. By default, some public domain games are installed, as example, but should you also have more, you can install them by copying them onto the [[Core]], or any storage device that uses LinuxMCE Folder Structure. The Following example assumes you are copying the ROMs directly onto the [[Core]].

=== Quick Instructions ===

# Open a file window to \\DCEROUTER\public\games
# Find the target game system.
# Copy the ROMs to this location.

=== Step by Step Instructions ===

==== Open a File Window to \\DCEROUTER\public\games and Find the Target Game System folder ====

[[Image:DCERouterPublicGames.png|right]]

Using Network Places on Windows, or Connect to Server on Mac or Linux, open a network connection to your [[Core]], select the Public share. You can also select the user shares if you wish to keep ROMs private to a single member of the house, ''Games stored in this manner can only be accessed by entering the user's PIN number after selecting the user's name in the [[Media Browser]].''

Once you've opened the Public, or User folder, Select the Games folder.

Then Find the appropriate Games Folder. Currently the game folders are:

* MAME - Place Arcade games here.
* a2600 - Place [[Atari 2600]] games here.
* a5200 - Place [[Atari 5200]] games here.
* a7800 - Place [[Atari 7800]] games here.

==== Copy over the ROMs ====

Drag over the ROMs from your source media to this target folder.

==== Wait 60 seconds for LinuxMCE to identify and Tag the Media ====

[[Image:GamesList.png|right]]

After 60 seconds, LinuxMCE will have detected the new ROMs, and attempted to tag them. If LinuxMCE can tag them, then it will attach descriptive attributes such as Title, Manufacturer, and Year, and attempt to find and attach a picture of the Box or Cartridge artwork. Right now, metadata is only parsed for MAME games. It is a simple TOSEC parser in place for appropriately named ROMs, but it doesn't deal with every known variation of TOSEC or the GoodSet, etc.

''If you find box or cartridge artwork for a game that we do not have, we would very much appreciate it if you would send it to one of the developers so that it may be included in the metadata package.''

== Playing Games ==

Playing Games in LinuxMCE is simple. You merely need to select the Games scenario from the Media Scenarios. '''The Games scenario will be available in any room with a media director that has the [[Game Player]] installed.''' then play the game with your desired gaming device.

=== Selecting a Game ===
tap
You will then be presented with the [[Media Browser]] which will be populated with every found game for every game system. Should you wish to filter this, you can filter it by either selecting '''Options''' on UI1, or by selecting the '''Sort''' popup. You can currently sort by:

* Recently Played
* Filename
* Title
* Manufacturer
* Year
* Game System

Once a Game has been selected, and the '''Play''' button has been pressed, the emulator should start and present the selected game.

=== Using Orbiter Controls for each Game system ===

Because each game system works differently and was interacted with diferently, LinuxMCE provides different Orbiter screens so that you can accurately interact with the emulated version of the game system. Some buttons are also common to all game systems, and some are specific to each game system emulated.

Under UI1, the Game buttons are available on the orbiter screens, for on-screen orbiters, this is selected by:

* Tapping the '''Menu''' button on a remote
* Tapping the '''Middle Grey''' button on the Gyration Go Mouse

For non on screen orbiters, you will see the remote appear in the same manner as the videos and music remotes, with all functions visible.

Under UI2, tapping the '''Menu''' key will show the same functions as described above in the left most "Now Playing" menu.

==== Common Controls ====

* '''[[Power/Off]]''' - This button, like all other media types, will cause the game to stop, and will return you to the main menu.
* '''[[Thumbnail]]''' - Allows you to take a picture of the screen, to assign to an attrbute, such as the game title. This picture will then show up in the File Browser.
* '''[[Bookmarks]]''' - Allows you to save bookmarks on games and systems that support them. ''Not all game systems support Bookmarks, and due to the way MAME and MESS work, we can't tell you ahead of time which ones will and wont. Bookmark support is added per system driver and can change as newer versions of MAME and MESS appear.''
* '''[[View Attributes]]''' - Allows you to see the attributes of the currently playing game, including the attached artwork.
* '''[[P1]]''' - Tells the system that 1 player is to play. Other Player buttons include P2, P3, and P4, which say 2, 3, and 4 players respectively. Which of these buttons are available on which system varies, and can be called '''[[Start]]''' instead.
* '''[[Pause]]''' - Pauses the game. The screen will darken when the game is paused, to serve as a visual cue.
* '''[[Reset]]''' - Resets the game or game system.
* '''[[Monitor Mode]]''' - Toggle. Broadcasts animated images of the playing game to all orbiters in the room. This can be used, for example, to watch the game from somewhere else in the house. No audio is broadcast. Animation will be slower than real time.

You can use any HID based joystick, specifically the X-Arcade tankstick. You can also use the Stelladaptor for Atari 2600 controllers attached for Atari 2600 games.

==== Controls and Notes for each System ====

* [[Atari 2600]]
* [[Atari 5200]]
* [[Atari 7800]]

'''Important Legal Notice:''' Obtaining ROM images of games you do not own is illegal in many countries, including the United States of America and countries in the European Union. LinuxMCE does not provide ROM images, nor does it provide, or facilitate the means by which to get ROM images that are still under copyright.

[[Category:Documentation]]

Play Games on LinuxMCE

2009-10-01T04:50:07Z

Dpaul: /* Common Controls */

In addition to audio and video media, LinuxMCE can play games originally designed for many different game systems. LinuxMCE contains a copy of the Multiple Arcade Machine Emulator (MAME) to play arcade games, and the Multiple Emulator Super System (MESS) to play games meant for many home video game systems.

== Supported Systems ==

LinuxMCE currently can support the following game systems:

* [[Arcade games emulated by MAME]]
* [[Atari 2600]]
* [[Atari 5200]]
* [[Atari 7800]]

With each game system, LinuxMCE presents integrated controls for all supported control methods, and provides a seamless way to import, catalog, and play all the games stored on your core or any attached storage device. Simply copy the ROMs into their respective system folders, and LinuxMCE will attempt to identify, and tag each one to the best of its ability.

[[Notes on how LinuxMCE Detects ROMs]]

== Enabling The Game Player ==

To use the Game support, you must enable the Game Player. The Game Player adds support for all the above game systems to a Media Director at once, and '''you must enable the Game Player on each Media Director you wish to be able to play games.'''

=== Quick Instructions for those Familiar with LinuxMCE ===

# Go to http://dcerouter/ (the web admin)
# from the Top menu, go to Wizard > [[Media Directors]]
# Find the media director on which you wish to enable Game Support.
# Press the [ Edit ] Button next to Software Modules
# Find the Game Player. Select it by checking its box.
# Press [ Save ]
# Watch your nearest orbiter for messages. You should see installation messages.
## When asked, Press Quick Reload Router
## When the Orbiter re-appears, it will ask you to regenerate orbiters. Regenerate all orbiters in the house.
# The Games Button should now be visible under [[Media]]

=== Step by Step Instructions ===

==== Go to http://dcerouter/ ====

[[Image:WebAdminLogon.png|right|Logging Onto the Web Admin]]

For information on Logging into the Web Admin, go here: [[LinuxMCE Admin Website]]

==== Go to Wizard > [[Media Directors]] ====

[[Image:WizardMediaDirectors.png|right]]

The Wizard > [[Media Directors]] Page provides everything you need to adjust the operation of each media director in the house. For each system you wish to be able to play games, you need to do these instructions.

==== Press the Edit button next to [[Software Modules]] ====

The Software Modules page allows you to select software that can easily be installed into [[LinuxMCE]] To be installed onto each media director. We want to select the Game Player.

==== Find and Select the Game Player and press Save ====

[[Image:WizardMediaDirectorsSoftwareModulesGamePlayer.png|right]]

If you wish to uninstall the [[Game Player]] at a later time for this media director, simply uncheck the box, and press '''Save'''.

==== Watch your orbiter for Installation Messages ====

Your Orbiter should emit many messages relating to the installation of the software. If this is the first media director you are installing onto, the [[Core]] will also need to install the [[Game PlugIn]] so that it can manage the different [[Game Player]] instances throughout the house. The installation of the Game PlugIn also installs data packages which provide metadata and images for game ROMs to make the automatic game cataloguing process possible. '''This process of installing the [[Game PlugIn]] the first time can take a long time. Please Be Patient. Subsequent installations do not take as much time.''' We will improve this installation time significantly in future releases.

==== Reload Your Router ====

Once the installation process is complete, the system will ask you to reload the router. ''You must do this so the system can use the Game Player.'' Press '''[[Quick Reload Router]]''' This process should take approximately 15 seconds.

==== Regenerate Your Orbiters ====

Once your router is reloaded, and the system finds the new [[Game Player]] running, it will ask to regenerate all your orbiters in the house so that the Games button will be visible. This process should take approximately 2 minutes, per [[Orbiter]] on average.

== Loading Games onto the system ==

Once the Game PlugIn has been installed, you will then need to install some games. By default, some public domain games are installed, as example, but should you also have more, you can install them by copying them onto the [[Core]], or any storage device that uses LinuxMCE Folder Structure. The Following example assumes you are copying the ROMs directly onto the [[Core]].

=== Quick Instructions ===

# Open a file window to \\DCEROUTER\public\games
# Find the target game system.
# Copy the ROMs to this location.

=== Step by Step Instructions ===

==== Open a File Window to \\DCEROUTER\public\games and Find the Target Game System folder ====

[[Image:DCERouterPublicGames.png|right]]

Using Network Places on Windows, or Connect to Server on Mac or Linux, open a network connection to your [[Core]], select the Public share. You can also select the user shares if you wish to keep ROMs private to a single member of the house, ''Games stored in this manner can only be accessed by entering the user's PIN number after selecting the user's name in the [[Media Browser]].''

Once you've opened the Public, or User folder, Select the Games folder.

Then Find the appropriate Games Folder. Currently the game folders are:

* MAME - Place Arcade games here.
* a2600 - Place [[Atari 2600]] games here.
* a5200 - Place [[Atari 5200]] games here.
* a7800 - Place [[Atari 7800]] games here.

==== Copy over the ROMs ====

Drag over the ROMs from your source media to this target folder.

==== Wait 60 seconds for LinuxMCE to identify and Tag the Media ====

[[Image:GamesList.png|right]]

After 60 seconds, LinuxMCE will have detected the new ROMs, and attempted to tag them. If LinuxMCE can tag them, then it will attach descriptive attributes such as Title, Manufacturer, and Year, and attempt to find and attach a picture of the Box or Cartridge artwork.

''If you find box or cartridge artwork for a game that we do not have, we would very much appreciate it if you would send it to one of the developers so that it may be included in the metadata package.''

== Playing Games ==

Playing Games in LinuxMCE is simple. You merely need to select the Games scenario from the Media Scenarios. '''The Games scenario will be available in any room with a media director that has the [[Game Player]] installed.''' then play the game with your desired gaming device.

=== Selecting a Game ===
tap
You will then be presented with the [[Media Browser]] which will be populated with every found game for every game system. Should you wish to filter this, you can filter it by either selecting '''Options''' on UI1, or by selecting the '''Sort''' popup. You can currently sort by:

* Recently Played
* Filename
* Title
* Manufacturer
* Year
* Game System

Once a Game has been selected, and the '''Play''' button has been pressed, the emulator should start and present the selected game.

=== Using Orbiter Controls for each Game system ===

Because each game system works differently and was interacted with diferently, LinuxMCE provides different Orbiter screens so that you can accurately interact with the emulated version of the game system. Some buttons are also common to all game systems, and some are specific to each game system emulated.

Under UI1, the Game buttons are available on the orbiter screens, for on-screen orbiters, this is selected by:

* Tapping the '''Menu''' button on a remote
* Tapping the '''Middle Grey''' button on the Gyration Go Mouse

For non on screen orbiters, you will see the remote appear in the same manner as the videos and music remotes, with all functions visible.

Under UI2, tapping the '''Menu''' key will show the same functions as described above in the left most "Now Playing" menu.

==== Common Controls ====

* '''[[Power/Off]]''' - This button, like all other media types, will cause the game to stop, and will return you to the main menu.
* '''[[Thumbnail]]''' - Allows you to take a picture of the screen, to assign to an attrbute, such as the game title. This picture will then show up in the File Browser.
* '''[[Bookmarks]]''' - Allows you to save bookmarks on games and systems that support them. ''Not all game systems support Bookmarks, and due to the way MAME and MESS work, we can't tell you ahead of time which ones will and wont. Bookmark support is added per system driver and can change as newer versions of MAME and MESS appear.''
* '''[[View Attributes]]''' - Allows you to see the attributes of the currently playing game, including the attached artwork.
* '''[[P1]]''' - Tells the system that 1 player is to play. Other Player buttons include P2, P3, and P4, which say 2, 3, and 4 players respectively. Which of these buttons are available on which system varies, and can be called '''[[Start]]''' instead.
* '''[[Pause]]''' - Pauses the game. The screen will darken when the game is paused, to serve as a visual cue.
* '''[[Reset]]''' - Resets the game or game system.
* '''[[Monitor Mode]]''' - Toggle. Broadcasts animated images of the playing game to all orbiters in the room. This can be used, for example, to watch the game from somewhere else in the house. No audio is broadcast. Animation will be slower than real time.

You can use any HID based joystick, specifically the X-Arcade tankstick. You can also use the Stelladaptor for Atari 2600 controllers attached for Atari 2600 games.

==== Controls and Notes for each System ====

* [[Atari 2600]]
* [[Atari 5200]]
* [[Atari 7800]]

'''Important Legal Notice:''' Obtaining ROM images of games you do not own is illegal in many countries, including the United States of America and countries in the European Union. LinuxMCE does not provide ROM images, nor does it provide, or facilitate the means by which to get ROM images that are still under copyright.

[[Category:Documentation]]

PPTP

2009-09-17T02:47:03Z

Dpaul: New page: Placeholder for PPTP Client Setup.

Placeholder for PPTP Client Setup.

Volume Control Doesn't Work

2009-05-08T22:50:02Z

Dpaul:

[[Category:Tutorials]]
If you are unable to control or mute your volume, you can try this solution:

Edit the alsa-base config file in the /etc/modprobe.d directory

dcerouter_1:~# vi /etc/modprobe.d/alsa-base

Add the following code to the bottom of the file.

options snd-intel8x0 ac97_quirk=hp_only

Reboot

----

AC97 Quirk Option
=================

The ac97_quirk option is used to enable/override the workaround for
specific devices on drivers for on-board AC'97 controllers like
snd-intel8x0. Some hardware have swapped output pins between Master
and Headphone, or Surround (thanks to confusion of AC'97
specifications from version to version :-)

The driver provides the auto-detection of known problematic devices,
but some might be unknown or wrongly detected. In such a case, pass
the proper value with this option.

The following strings are accepted:
default Don't override the default setting
none Disable the quirk
hp_only Bind Master and Headphone controls as a single control
swap_hp Swap headphone and master controls
swap_surround Swap master and surround controls
ad_sharing For AD1985, turn on OMS bit and use headphone
alc_jack For ALC65x, turn on the jack sense mode
inv_eapd Inverted EAPD implementation
mute_led Bind EAPD bit for turning on/off mute LED

For backward compatibility, the corresponding integer value -1, 0,
... are accepted, too.

For example, if "Master" volume control has no effect on your device
but only "Headphone" does, pass ac97_quirk=hp_only module option

Volume Control Doesn't Work

2009-05-08T22:48:05Z

Dpaul: New page: If you are unable to control or mute your volume, you can try this solution: Edit the alsa-base config file in the /etc/modprobe.d directory dcerouter_1:~# vi /etc/modprobe.d/alsa-base...

If you are unable to control or mute your volume, you can try this solution:

Edit the alsa-base config file in the /etc/modprobe.d directory

dcerouter_1:~# vi /etc/modprobe.d/alsa-base

Add the following code to the bottom of the file.

options snd-intel8x0 ac97_quirk=hp_only

Reboot

----

AC97 Quirk Option
=================

The ac97_quirk option is used to enable/override the workaround for
specific devices on drivers for on-board AC'97 controllers like
snd-intel8x0. Some hardware have swapped output pins between Master
and Headphone, or Surround (thanks to confusion of AC'97
specifications from version to version :-)

The driver provides the auto-detection of known problematic devices,
but some might be unknown or wrongly detected. In such a case, pass
the proper value with this option.

The following strings are accepted:
- default Don't override the default setting
- none Disable the quirk
- hp_only Bind Master and Headphone controls as a single control
- swap_hp Swap headphone and master controls
- swap_surround Swap master and surround controls
- ad_sharing For AD1985, turn on OMS bit and use headphone
- alc_jack For ALC65x, turn on the jack sense mode
- inv_eapd Inverted EAPD implementation
- mute_led Bind EAPD bit for turning on/off mute LED

For backward compatibility, the corresponding integer value -1, 0,
... are accepted, too.

For example, if "Master" volume control has no effect on your device
but only "Headphone" does, pass ac97_quirk=hp_only module option

MythTv: Don't scan live tv

2009-04-14T01:08:20Z

Dpaul: /* Making MythTV LiveTv recordings invisible to LinuxMCE */

[[Category:Tutorials]]

== Making MythTV LiveTv recordings invisible to LinuxMCE ==

For those who watch a lot of live TV, you'll notice that LinuxMCE adds all of those LiveTV recordings to the LinuxMCE DB. Not only does this fill up the database, but it makes browsing media quite ugly. A side effect of deleting recordings through LinuxMCE is that the recordings cannot be deleted or expired from MythTV, causing the list of recordings to grow out of control. There is an easy way to solve these issues.

== Locating and editing the SaveMythRecording.sh file ==

The file is stored in
/usr/pluto/bin

The first thing to do is make the directory that will hold the recordings:

mkdir /home/public/data/videos/tv_shows_0

Then make a backup of the SaveMythRecording.sh script:

cp /usr/pluto/bin/SaveMythRecording.sh /usr/pluto/bin/SaveMythRecording.sh.bak

Now edit SaveMythRecording.sh with your favorite program:

#!/bin/bash

dir=/home/public/data/videos/tv_shows_0

mv $3/$4 $dir/$4
touch $3/$4
chown mythtv:public $3/$4

echo "$(date) $0-$1-$2-$dir-$4" >> /var/log/pluto/donerecording.log
/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 69 29 "$1" 57 "$2" 35 "$dir/$4"''

== Prevent UpdateMedia from scanning LiveTV recordings ==

Create a file, /home/public/data/videos/tv_shows_1.folderlock, to prevent scanning:

touch /home/public/data/videos/tv_shows_1.folderlock

== Conclusion ==

Now when browsing Media, LiveTv recordings will not show in the Video list. Your recordings will never be expired or deleted by MythTv, and MythTv will continue functioning without errors. '''All LiveTv recordings and scheduled recordings can still be expired and deleted through the MythWeb interface without impacting LinuxMCE.'''

MythTv: Don't scan live tv

2009-04-14T01:03:54Z

Dpaul: /* Making MythTV LiveTv recordings invisible to LinuxMCE */

[[Category:Tutorials]]

== Making MythTV LiveTv recordings invisible to LinuxMCE ==

For those who watch a lot of live TV, you'll notice that LinuxMCE adds all of those LiveTV recordings to the LinuxMCE DB. Not only does this fill up the database, but it makes browsing media quite ugly. Also, a side effect of deleting recordings through LinuxMCE is that the recordings cannot be deleted or expired from MythTV - That causes the list to grow beyond being manageable. There is an easy way to solve these issues.

== Locating and editing the SaveMythRecording.sh file ==

The file is stored in
/usr/pluto/bin

The first thing to do is make the directory that will hold the recordings:

mkdir /home/public/data/videos/tv_shows_0

Then make a backup of the SaveMythRecording.sh script:

cp /usr/pluto/bin/SaveMythRecording.sh /usr/pluto/bin/SaveMythRecording.sh.bak

Now edit SaveMythRecording.sh with your favorite program:

#!/bin/bash

dir=/home/public/data/videos/tv_shows_0

mv $3/$4 $dir/$4
touch $3/$4
chown mythtv:public $3/$4

echo "$(date) $0-$1-$2-$dir-$4" >> /var/log/pluto/donerecording.log
/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 69 29 "$1" 57 "$2" 35 "$dir/$4"''

== Prevent UpdateMedia from scanning LiveTV recordings ==

Create a file, /home/public/data/videos/tv_shows_1.folderlock, to prevent scanning:

touch /home/public/data/videos/tv_shows_1.folderlock

== Conclusion ==

Now when browsing Media, LiveTv recordings will not show in the Video list. Your recordings will never be expired or deleted by MythTv, and MythTv will continue functioning without errors. '''All LiveTv recordings and scheduled recordings can still be expired and deleted through the MythWeb interface without impacting LinuxMCE.'''

MythTv: Don't scan live tv

2009-04-14T01:02:38Z

Dpaul: /* Conclusion */

[[Category:Tutorials]]

== Making MythTV LiveTv recordings invisible to LinuxMCE ==

For those who watch a lot of live TV, you'll notice that LinuxMCE adds all of those LiveTV recordings to the LinuxMCE DB. Not only does this fill up the database, but it makes browsing media quite ugly. There is an easy way to solve this.

== Locating and editing the SaveMythRecording.sh file ==

The file is stored in
/usr/pluto/bin

The first thing to do is make the directory that will hold the recordings:

mkdir /home/public/data/videos/tv_shows_0

Then make a backup of the SaveMythRecording.sh script:

cp /usr/pluto/bin/SaveMythRecording.sh /usr/pluto/bin/SaveMythRecording.sh.bak

Now edit SaveMythRecording.sh with your favorite program:

#!/bin/bash

dir=/home/public/data/videos/tv_shows_0

mv $3/$4 $dir/$4
touch $3/$4
chown mythtv:public $3/$4

echo "$(date) $0-$1-$2-$dir-$4" >> /var/log/pluto/donerecording.log
/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 69 29 "$1" 57 "$2" 35 "$dir/$4"''

== Prevent UpdateMedia from scanning LiveTV recordings ==

Create a file, /home/public/data/videos/tv_shows_1.folderlock, to prevent scanning:

touch /home/public/data/videos/tv_shows_1.folderlock

== Conclusion ==

Now when browsing Media, LiveTv recordings will not show in the Video list. Your recordings will never be expired or deleted by MythTv, and MythTv will continue functioning without errors. '''All LiveTv recordings and scheduled recordings can still be expired and deleted through the MythWeb interface without impacting LinuxMCE.'''

Suspend

2009-04-13T13:14:46Z

Dpaul: /* Setup using PM-Utils */

[[Category: Tutorials]]

{| align="right"
| __TOC__
|}
This article describes how to suspend your MD to RAM (standby) or to disk (hibernation).

Please note that this functionality is not yet integrated into LinuxMCE, and will thus need some editing of Linux configuration files. Integration of the suspend functions has not been reported in the new issue-tracking system. The old Mantis-ID is 3822.

Ubuntu 710 removed the s2ram utility used to suspend-to-ram. But suspend to disk may still work, depending on your hardware and drivers. It might also be possible to use the s2both command, which is supposed to suspend to RAM and at the same time write the image to disk, to have a backup in case of power-out.

Ubuntu 810 uses pm-utils as the standard suspend/resume framework. Using this is recommended. It will also work with 710.
Description of how to use pm-utils are below.

== Motivation ==
* Saving power
* Quick boot (usefull if your MD is noisy and you turn it off when not in use)

== Setup using PM-Utils ==
PM-utils are the new package in Ubuntu 810 that are responsible for suspending and resuming your computer. It uses the HAL database to find information about what special tricks it need to pull off to get your particular hardware to successfully resume.

The setup for pm-utils was tested after completing the hibernate setup below, so you may have to include some parts of that to get this to work. In particular the NVidia part may be required.

Install pm-utils
apt-get install pm-utils

Create a file /etc/pm/sleep.d/01lmce
#!/bin/bash

. /usr/lib/pm-utils/functions

RETVAL=0
case "$1" in
hibernate|suspend)
/usr/pluto/bin/suspend.sh
RETVAL=$?
;;
thaw|resume)
/usr/pluto/bin/resume.sh
;;
*)
;;
esac

exit $RETVAL

Create a file /usr/pluto/bin/resume.sh
#!/bin/bash

/usr/bin/screen -d -m -S "LMCE Launch Manager" /usr/pluto/bin/lmce_launch_manager.sh

Create a file /usr/pluto/bin/suspend.sh
#!/bin/bash

. /usr/pluto/bin/Config_Ops.sh
. /usr/pluto/bin/SQL_Ops.sh
. /usr/pluto/bin/pluto.func

echo "LMCE Suspend Process Started"

## Turn on WOL

/usr/pluto/bin/enable_wol.sh

## Find local IP address

LocalIP=$(ip addr show dev eth0|grep "inet "|cut -f6 -d" "|cut -f1 -d/)

## Use local IP address to find MD device number

FindMDDeviceQ="SELECT PK_Device FROM Device
WHERE IPAddress='$LocalIP';
"

DeviceID=$(RunSQL "$FindMDDeviceQ")

## Identify immediate children DCE devices that are currently Registered

FindChildrenQ="SELECT Device.PK_Device
FROM Device
JOIN DeviceTemplate ON Device.FK_DeviceTemplate=DeviceTemplate.PK_DeviceTemplate
LEFT JOIN Device AS Device_Parent on Device.FK_Device_ControlledVia=Device_Parent.PK_Device
LEFT JOIN DeviceTemplate AS DeviceTemplate_Parent
ON Device_Parent.FK_DeviceTemplate=DeviceTemplate_Parent.PK_DeviceTemplate
WHERE (Device.FK_Device_ControlledVia=$DeviceID
OR (Device_Parent.FK_Device_ControlledVia=$DeviceID AND DeviceTemplate_Parent.FK_DeviceCategory IN (6,7,8) ) )
AND DeviceTemplate.FK_DeviceCategory <> 1
AND DeviceTemplate.ImplementsDCE=1
AND Device.Registered=1;
"

DeviceList=$(RunSQL "$FindChildrenQ")

## Send SYSCOMMAND_0 (device shutdown) message to all immediate children. These devices will relay the message to all decendents

for Device in $DeviceList; do

/usr/pluto/bin/MessageSend "$DCERouter" 0 "$Device" 7 0 163 "start_local_devices"

done

## Send SYSCOMMAND_0 message to MD device itself
/usr/pluto/bin/MessageSend dcerouter 0 $DeviceID 7 0 163 "start_local_devices"

## Wait for DCE devices to complete their shutdown

MaxLoopCount=50
for ((i = 0; i < MaxLoopCount; i++)); do
Devices=$(cat /usr/pluto/locks/pluto_spawned_local_devices.txt | grep -v '^$' | tr '\n' ',')
Devices="${Devices%,}"
<nowiki>if [[ -z "$Devices" ]]; then</nowiki>
break
fi
RegCount=0
Q="SELECT COUNT(*) FROM Device WHERE PK_Device IN ($Devices) AND Registered=1"
RegCount=$(RunSQL "$Q")
<nowiki> if [[ "$RegCount" -eq 0 ]]; then </nowiki>
break
fi
echo "Waiting for $RegCount devices to shutdown ($Devices)"
sleep 1
done

echo "Done waiting"

## Kill the LM processes

killall -q -s SIGKILL -r lmce_launch_manager\*

Make sure all three scripts are executable
chmod +x <script>

Reboot the MD, and that's it. The setup is complete. You can try to suspend by typing pm-suspend. The suspend can take some time as LMCE is stopping the devices on your MD. If your hardware is supported, it will resume and restart lmce.

== Setup using hibernate ==
It is now recommended to use the pm-utils way of suspending. This way may still work though.

On the MD in question, make sure you have the uswsusp and hibernate packages installed.

apt-get install uswsusp hibernate

Check your BIOS setting to make sure that suspend to ram is enabled.

== Using NVidia graphics card ==

Edit your xorg.conf file and add this line to the "Device" section:

Option "NvAGP" "1"

Also make sure no other ''vendor'' AGP modules are loaded, like intel_agp, sis_agp etc. The ''agpgart'' module is fine, though.
Use
lspci | grep agp
to list all loaded agp modules.

If you see any agp modules besides agpgart, add a line to /etc/modprobe.d/blacklist to blacklist the module.

Edit the /etc/hibernate/ram.conf file, and comment the two lines
#EnableVbeTool yes
#VbetoolPost yes

Edit the /etc/hibernate/blacklisted-modules, and comment the line:
#nvidia

== Lirc module unloading and reloading ==

'''Not needed for 710'''

Some lirc modules (at least lirc_serial) needs reloading after suspend. Like for enabling wol, we add a file in the /etc/hibernate/scriptlets.d/ folder, with a descriptive name ''lirc''.
# Stops and unloads the current lirc module before suspending, and
# restarts lirc when resuming

AddSuspendHook 30 UnloadLirc
AddResumeHook 30 StartLirc

UnloadLirc() {
/etc/init.d/lirc stop
if [ -f /etc/lirc/hardware.conf ];then
. /etc/lirc/hardware.conf
rmmod $MODULES
fi
}

StartLirc() {
/etc/init.d/lirc start
}

== Suspend to RAM ==

Run
hibernate-ram
to suspends the MD to ram. The script first checks if it recognizes your hardware, to take the correct actions before suspending.
If you get a message that your machine is unknown, edit the /etc/hibernate/ususpend-ram.conf file, and un-comment the
USuspendRamForce yes
line, to force it to suspend anyway.

== Suspend to disk / Hibernation ==

Before trying to set up suspend to disk, I recommend that you first get suspend to ram working. All setup needed for suspend to RAM is also required for suspend to disk.

To enable suspend to disk, you will need to set up a swap partition on the MD in question. This is because the suspend implementation in the current kernel can only save the memory to the swap area. To achieve this on a diskless MD, you might use a CF card and a CF/IDE adapter. A CF card with 1 or 2 GB should be sufficient. However, with a CF card, you should make sure your MD has enough physical ram to avoid using swap, because CF cards may have lower performance than a normal IDE disk.

Edit the /etc/fstab file for the MD and add an entry for the swap partition
/dev/sda1 none swap sw 0 0
Adjust the partition to match your swap partition. Make sure you select the right one, or you WILL destroy your data. In the case of a diskless MD, you will probably only have one partition (a CF card for instance). You might need to do partitioning on the disk if it is a empty disk. This is outside the scope of this article.

Copy two files from /usr/share/initramfs-tools/scripts/local-premount/ (resume, uswsusp) into /etc/initramfs-tools/scripts/nfs-premount/
Not sure if both files are required, but it doesn't hurt.

These scripts will run before any file systems have been mounted, and after any disk drivers has been loaded. Both are important: mounting any file systems before resuming can corrupt your data, according to the documentation. And we need to have the drivers loaded to access the suspended image.

After copying the two files, run
update-initramfs -u
to update the initramfs image, which includes the scripts in the boot up process.

Now reboot your MD. When it has started up again, you can type
hibernate-disk
to initiate suspend to disk.

== References ==
The hibernate script uses uswsusp by default when trying to suspend to ram. For more information about the s2ram utility used, read the [http://en.opensuse.org/S2ram S2ram howto]

The [http://en.opensuse.org/NVidia_Suspend_HOWTO NVidia suspend howto]

Gyration GYR3101US

2009-04-02T04:24:52Z

Dpaul:

[[category: Tutorials]]
{| align="right"
| __TOC__
|}
== Summary ==
[[Image:Gyration.JPG|right]]
The Gyration GYR3101US remote (aka Gyration MCE RF Remote) is identical in style to the [http://fiire.com/fiire-chief.php Fiire Chief]. The keys are not mapped as nicely as the custom-designed Fiire Chief, but the Gyration's firmware can be updated to gain similar functionality using the
[http://cf.ccmr.cornell.edu/cgi-bin/w3mman2html.cgi?xmodmap(1) Xmodmap] program (and its corresponding config file) .

The Gyration remote control uses the gyro feature just like the Fiire Chief and the Gyration mouse. (The major difference is how the remote is detected and used by LinuxMCE, of course.)

==Availability==

*[http://www.newegg.com/Product/Product.aspx?Item=N82E16880105001 New Egg] -- US$99 (April 2008).

==Default capabilities==
*When the device is plugged in, it is identified and configured as a GO Wireless USB device. The "gyration mouse" bit works immediately. By default the ''Stop'' button will stop media playback, and the ''skip forward and back'' buttons work. If this is all you want, you're done. No further configuration is needed.

*By default LinuxMCE recognizes the ''volume up/down'' keys, the 10 number keys, the MCE button, and the media controls ''play/stop/ffwd/rwd/pause/skip fwd/skip back''.

== How to Setup ==
*Gyration codes: [[Gyration-GYR3101US-codes]]

*I wanted the "Ambience" (Volume/Lighting) control key mapped, as well as the Channel/Chapter function, and the pull up menu for watching/listening to media.

*To enable the volume control, I used the ''xev'' application from the KDE desktop terminal window, and identified the required keys.

xev

The first time this is run, it will pop-up a test window. Specify your mouse there, and then press the buttons on the Gyration remote to see the results in the terminal. Pay special attention to the

keycode

entries -- they are what you will specify in the .Xmodmap file.

On my particular setup (which I think is the default) the keys show up as:

Volume Up keycode 176
Volume Down keycode 174
MCE button keycode 97

Now the keys in LinuxMCE that provide the ''volume/channel/menu'' functions are:

F6 = Channel/Chapter FFWD/RWD/PAUSE menu
F7 = Menu button
F8 = Volume/Lighting button "ambience"

== Update to get more MythTV functionality ==

MythTV Keys

P = Pause # Pause key on remote
R = Record # Record key on remote
Z = 30 second skip # Right skip key under directional pad
Q = 10 second back # Left skip key under directional pad
I = Info # Info button
F9 = Mute # Mute button
Y = Switch Cards # Pictures button

Using this info, I created the following .Xmodmap file as root user in /etc

cd /etc
sudo vi /etc/.Xmodmap

/etc/.Xmodmap
keycode 176 = F8
keycode 174 = F6
keycode 97 = F7
keycode 110 = P
keycode 177 = R
keycode 153 = Z
keycode 144 = Q
keycode 134 = I
keycode 160 = F9
keycode 237 = Y

Now after creating the file, make sure it is loaded when LinuxMCE starts up. To do this add the following (as root) to the script file ''/usr/pluto/bin/lmce_launch_manager.sh'':

sudo vi /usr/pluto/bin/lmce_launch_manager.sh

Add a line before the line '''KDE_DEBUG=1''' so that it looks like

xmodmap /etc/.Xmodmap
KDE_DEBUG=1

Save the file. You have two choices to get it going.

1. Fire off the command

sudo xmodmap /etc/.Xmodmap

:(This must be done from the KDE desktop term window (Konsole), as it needs to be run in the X environment. (You can also export the display like: export DISPLAY=:0;xmodmap /etc/.Xmodmap .)

2. Restart the core.

:By placing the file in the lmce_launch_manager.sh script, anytime the core is rebooted, your settings are automagically set up.

== Media Directors ==

:To get this working on a media director, follow the directions above, but add the xmodmap directive to the file ''/usr/pluto/bin/LaunchOrbiter.sh'', instead of ''/usr/pluto/bin/lmce_launch_manager.sh''. Add it below the line '''N_Desktops=$(wmctrl -d | wc -l) # zero based'''. It should look like this:

/usr/bin/xset -dpms s off
N_Desktops=$(wmctrl -d | wc -l) # zero based
/usr/bin/xmodmap /etc/.Xmodmap

==Troubleshooting==
Problem:
There are a couple of oddities to that I have encountered. When I watch a movie and want to change the volume or lighting for a movie (or pre-recorded program), it does what it supposed to. But when I watch Mythtv live, pressing the volume up on the Gyration remote invokes the MythTV Sleep Timer.

Solution: !!!!Update. As of 710 release I have not had to unmap these keys!!!!! But Just in case.... Read On.
This can be resolved by remapping the sleep timer key using the Mythweb application located at http://core.ip.address/mythweb/ (for internal open systems) or at http://core.dhcp.server.adress/mythweb/

This can be avoided by unmapping the following keys in Mythweb/Settings/Controls

F6
F7
F8

Unmap these keys. Make sure you scroll down the whole list, as they appear more than once.

After you have completed these steps the following keys will perform these functions:

*MCE button pulls up LinuxMCE menu system
*Volume Up button brings up the "Ambience" controls during media playback
*Volume Down button brings up the ''Channel/Chapter Fast Forward/Rewind and Pause'' functions
*The Gyration center button does movement correctly
*If you double click the center button, the mouse stays active, but remember to click once more to turn off (or you'll kill the batteries).
*The Gyration Left button acts like the left mouse button for "Choose" functions
*The Gyration Right button is the "exit" or "clear item" button
*The left and right buttons are just like mouse buttons
*The Number keys work with MythTV
*The Pause button will pause MythTV
*The Record button will start an on-the-fly-recording
*The skip forward button does the standard 30 second skip correctly
*The skip back button does the 10 second back skip correctly
*The Pictures button will switch tuner cards if you have more than one. Nice for DVB users who don't use VDR.
*The Mute button functions correctly
*The Info button functions correctly

==Alternate Config by Glasswalker==
I have created this alternate config for the GYR3101US (stock gyration remote). I have managed to get most functions working (with the exception of the keys which use non-standard HID codes of course). However this has only been tested in the LMCE interface and with video/audio playback. I have not tested in Myth or VDR at all.

The thing I like about this config, is it is easily implemented via a single change to the device template for the Go Cordless GC1005M Mouse (the device that the GYR3101US is detected as). It is device template ID #1812

It is simple to make this edit:
#In the WebAdmin page, go to Advanced, then Configuration, then Device Templates.
#Under "Do you know the ID of the device template?" type in 1812, and hit "GO"
#Then, on the Device Template line, click "Pick device template"
#Scroll down to the "Device Data" section, and find "#59 Configuration(string)"
#In the "Default Value" column, paste in the contents of the config text which I have provided below.
#Scroll to the bottom of the page, and click "Save"
#Then do a quick reload of the router, and the remote should begin using the new configuration.
That's basically it. And all without any direct configuration file editing. The beauty is you edit in this one place, and these changes automatically propagate to all GYR3101US remotes you are using in your home. No filesystem changes, no hacking on the shell. I found this solution much "cleaner" than some of the above options

(note: it is most likely also less complete. Since I do not use myth or VDR at the moment, I have no reason to test in those apps to make sure there are no conflicts or bugs with this mapping in those apps. Please feel free to make your own additions or modifications to compensate for that, or if those apps simply don't play nice with this method, then revert to one of the other methods which are confirmed to work with those apps).

===What this config provides===
*The number keys should map correctly
*All media playback buttons map the correct functions (play,stop,ff,rw,skip,pause)
*The arrow keys, OK button, and back button are mapped to the appropriate functions
*The airmouse continues to work normally
*The Green Media button will pull up the LMCE menu during media playback
That's basically it that's important at this point. Until we get a customized HID driver to recognize the remaining functions of the remote.

*A note on the config file. This may just be my situation, but the volume keys, when I pressed up, the volume went down, and of course pressing down made the volume go up. Simply switching the volume section of the config to this:

### Volume/Channel/MCE Control ###
voldn,174,R
VolUp,176,R
#chup,100156,R
#chdown,100157,R
#MCE,100194,H
Mute,100226,D

Resolved the issue: But I must say, excellent work Glasswalker!!
--[[User:Sethj|Sethj]] 13:22, 30 January 2009 (CET)

===Config Text===
<pre>
### Power Control ###
#Power,100130,U
#Halt,100130,H

### Media Control ###
Stop,164,D
Record,177,D
Pause,110,D
Play,179,D
Rewind,152,D
fastforward,180,D
SkipPrior,144,R
SkipNext,153,R

### Navigation ###
ok,36,D,Y
Up,98,R,Y
Down,104,R,Y
Left,100,R,Y
Right,102,R,Y
#Back,234,D
## Added MythTV Guide functionality - since info is pretty much useless ##
guide,134,U
#info,134,U

### Volume/Channel/MCE Control ###
##Assign the volume rose to the volume buttons ##
yellow,174,R
yellow,176,R
#voldn,174,R
#VolUp,176,R
#chup,100156,R
#chdown,100157,R
#MCE,100194,H
Mute,100226,D

### Media Shortcut / Special Buttons ###
#Music,237,U
#Videos,100000,U
#tv,100391,U
#Pictures,100393,U
#red,237,U
#green,100000,U
#yellow,100000,U
#blue,100000,U
#shortcutr,237,H
#shortcutg,100000,H
#shortcuty,100000,H
#shortcutb,100000,H

### Number Buttons ###
1,10,U,Y
2,11,U,Y
3,12,U,Y
4,13,U,Y
5,14,U,Y
6,15,U,Y
7,16,U,Y
8,17,U,Y
9,18,U,Y
0,19,U,Y
shortcut1,10,H,Y
shortcut2,11,H,Y
shortcut3,12,H,Y
shortcut4,13,H,Y
shortcut5,14,H,Y
shortcut6,15,H,Y
shortcut7,16,H,Y
shortcut8,17,H,Y
shortcut9,18,H,Y
shortcut0,19,H,Y

### Special Buttons Below Numbers ###
Clear,9,D
enter,36,D,Y
#setup_menu,100000,D,Y
#last,100000,D,Y
#input,100000,D,Y
#dvd_menu,100000,D,Y

### Customized For LMCE Ease of Use ###

#MCE Button mapped to "green" for pulling up menu during playback
green,97,U
#Back button mapped to "red" to back out of things
red,234,D
</pre>

==Map the chapter/FF/Rew Rose to picture button (below volume)==

#Scroll down to the "Device Data" section, and find "#60 Mapping(string)"
#In the "Default Value" column, paste in the contents of the config text which I have provided below.
#Scroll to the bottom of the page, and click "Save"
#Then do a quick reload of the router, and the remote should begin using the new configuration.

<pre>
2,183=2,73
3,183=3,73
2,184=2,74
3,184=3,74
2,182=2,72
3,182=3,72
2,237=2,72
3,237=3,72
</pre>

With these changes, most remote buttons work during media playback, and MythTV. There is no need to make changes to the .Xmodmap file - everything should be done through LinuxMCE device template.

Gyration GYR3101US

2009-04-02T04:15:32Z

Dpaul: /* Config Text */

Postfix configured with Gmail SMTP

2009-03-31T19:05:18Z

Dpaul:

[[Category:Tutorials]]

== Configure Postfix to send mail using Gmail SMTP servers ==

For those who want to send email from LinuxMCE, you can configure postfix to forward mail through your gmail account.

== Automatic Install and Configure Postfix ==

I have created scripts that can be ingegrated ino linuxmce, or run in interactive mode.

Go to the console of your core as root.

Get the scripts:
wget http://donpaul.info/configure_postfix.tar

Untar the scripts:
cd /usr/pluto/bin ; tar -xvf /root/configure_postfix.tar

Run the interactive script:
/usr/pluto/bin/Configure_Postfix_interactive.sh

== Manual Install and Configure Postfix ==

If you prefer to do things yourself...

'''* make sure you replace "Full Name" with your name, and "user@gmail.com" with your actual gmail address. *'''

Install postfix

apt-get install postfix

Create the CA:

/usr/lib/ssl/misc/CA.pl -newca

CA certificate filename (or enter to create)

Making CA certificate ...
Generating a 1024 bit RSA private key
.............++++++
..++++++
writing new private key to './demoCA/private/cakey.pem'
Enter PEM pass phrase:
Verifying - Enter PEM pass phrase:
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:US
State or Province Name (full name) [Some-State]:North Carolina
Locality Name (eg, city) []:
Organization Name (eg, company) [Internet Widgits Pty Ltd]:LinuxMCE
Organizational Unit Name (eg, section) []:
Common Name (eg, YOUR name) []:Full Name
Email Address []:email@gmail.com

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:
An optional company name []:
Using configuration from /usr/lib/ssl/openssl.cnf
Enter pass phrase for ./demoCA/private/cakey.pem:
Check that the request matches the signature
Signature ok
Certificate Details:
Serial Number:
9d:29:da:d3:76:20:17:10
Validity
Not Before: Mar 31 01:01:29 2009 GMT
Not After : Mar 30 01:01:29 2012 GMT
Subject:
countryName = US
stateOrProvinceName = North Carolina
organizationName = LinuxMCE
commonName = Full Name
emailAddress = usrer@gmail.com
X509v3 extensions:
X509v3 Subject Key Identifier:
A0:79:00:CA:90:00:E4:81:12:00:2A:73:00:00:CA:BD:54:08:03:7B
X509v3 Authority Key Identifier:
keyid:A0:79:00:CA:90:00:E4:81:12:00:2A:73:00:00:CA:BD:54:08:03:7B
DirName:/C=US/ST=North Carolina/O=LinuxMCE/CN=Full name/emailAddress=user@gmail.com
serial:90:20:0A:03:06:00:17:10

X509v3 Basic Constraints:
CA:TRUE
Certificate is to be certified until Mar 30 01:01:29 2012 GMT (1095 days)

Write out database with 1 new entries
Data Base Updated</nowiki>

Extend the key for 10 years

openssl x509 -in demoCA/cacert.pem -days 3650 -out cacert.pem -signkey demoCA/private/cakey.pem

Copy the extended key

cp cacert.pem demoCA

Generate private key

openssl req -new -nodes -subj '/CN=dcerouter/C=US/ST=North Carolina/O=LinuxMCE/CN=Full Name/emailAddress=user@gmail.com' -keyout key.pem -out req.pem -days 3650

Sign private key

openssl ca -out cert.pem -infiles req.pem

Copy to the postfix directory

cp demoCA/cacert.pem /etc/postfix
cp key.pem /etc/postfix
cp cert.pem /etc/postfix
chmod 644 /etc/postfix/cert.pem
chmod 644 /etc/postfix/cacert.pem
chmod 400 /etc/postfix/key.pem

Install the CA Certificates

apt-get install ca-certificates

Add thawte certificate

cat /etc/ssl/certs/Thawte_Premium_Server_CA.pem >> cacert.pem

Create transport file:

# Contents of /etc/postfix/transport
#
# This sends mail to Gmail
* smtp:[smtp.gmail.com]:587
#local mail delivered local
dcerouter relay:[dcerouter]

Create generic file
touch /etc/postfix/generic

Create sasl_passwd file:

# Contents of /etc/postfix/sasl_passwd
#
[smtp.gmail.com]:587 user@gmail.com:password

Be sure to hash the files:

postmap sasl_passwd
postmap transport
postmap generic

Add these lines to the bottom of /etc/postfix/main.cf

## TLS Settings
smtp_tls_loglevel = 1
smtp_enforce_tls = yes
smtp_tls_CAfile = /etc/postfix/cacert.pem
smtp_tls_cert_file = /etc/postfix/cert.pem
smtp_tls_key_file = /etc/postfix/key.pem
smtp_tls_session_cache_database = btree:/var/run/smtp_tls_session_cache
smtp_use_tls = yes
smtpd_tls_CAfile = /etc/postfix/cacert.pem
smtpd_tls_cert_file = /etc/postfix/cert.pem
smtpd_tls_key_file = /etc/postfix/key.pem
smtpd_tls_received_header = yes
smtpd_tls_session_cache_database = btree:/var/run/smtpd_tls_session_cache
smtpd_use_tls = yes
tls_random_source = dev:/dev/urandom

## SASL Settings
# This is going in to THIS server
smtpd_sasl_auth_enable = no
# We need this
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtpd_sasl_local_domain = $myhostname
smtp_sasl_security_options = noanonymous
#smtp_sasl_security_options =
smtp_sasl_tls_security_options = noanonymous
smtpd_sasl_application_name = smtpd

## Gmail Relay
relayhost = [smtp.gmail.com]:587

# Disable DNS Lookups
disable_dns_lookups = yes
#
# Great New feature Address Mapping
# for example may mchirico@localhost to mchirico@gmail.com
smtp_generic_maps = hash:/etc/postfix/generic
#
#
transport_maps = hash:/etc/postfix/transport

restart postfix

/etc/init.d/postfix restart

install mailx

apt-get install mailx

test forward

mailx -s "testing from linuxmce" youremail@domain.com < /etc/hosts

View log

tail /var/log/mail.log

You should see your message "Sent"

Postfix configured with Gmail SMTP

2009-03-31T17:56:57Z

Dpaul: /* Install and Configure Postfix */

[[Category:Tutorials]]

== Configure Postfix to send mail using Gmail SMTP servers ==

For those who want to send email from LinuxMCE, you can configure postfix to forward mail through your gmail account.

== Install and Configure Postfix ==
'''* make sure you replace "Full Name" with your name, and "user@gmail.com" with your actual gmail address. *'''

Install postfix

apt-get install postfix

Create the CA:

/usr/lib/ssl/misc/CA.pl -newca

CA certificate filename (or enter to create)

Making CA certificate ...
Generating a 1024 bit RSA private key
.............++++++
..++++++
writing new private key to './demoCA/private/cakey.pem'
Enter PEM pass phrase:
Verifying - Enter PEM pass phrase:
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:US
State or Province Name (full name) [Some-State]:North Carolina
Locality Name (eg, city) []:
Organization Name (eg, company) [Internet Widgits Pty Ltd]:LinuxMCE
Organizational Unit Name (eg, section) []:
Common Name (eg, YOUR name) []:Full Name
Email Address []:email@gmail.com

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:
An optional company name []:
Using configuration from /usr/lib/ssl/openssl.cnf
Enter pass phrase for ./demoCA/private/cakey.pem:
Check that the request matches the signature
Signature ok
Certificate Details:
Serial Number:
9d:29:da:d3:76:20:17:10
Validity
Not Before: Mar 31 01:01:29 2009 GMT
Not After : Mar 30 01:01:29 2012 GMT
Subject:
countryName = US
stateOrProvinceName = North Carolina
organizationName = LinuxMCE
commonName = Full Name
emailAddress = usrer@gmail.com
X509v3 extensions:
X509v3 Subject Key Identifier:
A0:79:00:CA:90:00:E4:81:12:00:2A:73:00:00:CA:BD:54:08:03:7B
X509v3 Authority Key Identifier:
keyid:A0:79:00:CA:90:00:E4:81:12:00:2A:73:00:00:CA:BD:54:08:03:7B
DirName:/C=US/ST=North Carolina/O=LinuxMCE/CN=Full name/emailAddress=user@gmail.com
serial:90:20:0A:03:06:00:17:10

X509v3 Basic Constraints:
CA:TRUE
Certificate is to be certified until Mar 30 01:01:29 2012 GMT (1095 days)

Write out database with 1 new entries
Data Base Updated</nowiki>

Extend the key for 10 years

openssl x509 -in demoCA/cacert.pem -days 3650 -out cacert.pem -signkey demoCA/private/cakey.pem

Copy the extended key

cp cacert.pem demoCA

Generate private key

openssl req -new -nodes -subj '/CN=dcerouter/C=US/ST=North Carolina/O=LinuxMCE/CN=Full Name/emailAddress=user@gmail.com' -keyout key.pem -out req.pem -days 3650

Sign private key

openssl ca -out cert.pem -infiles req.pem

Copy to the postfix directory

cp demoCA/cacert.pem /etc/postfix
cp key.pem /etc/postfix
cp cert.pem /etc/postfix
chmod 644 /etc/postfix/cert.pem
chmod 644 /etc/postfix/cacert.pem
chmod 400 /etc/postfix/key.pem

Install the CA Certificates

apt-get install ca-certificates

Add thawte certificate

cat /etc/ssl/certs/Thawte_Premium_Server_CA.pem >> cacert.pem

Create transport file:

# Contents of /etc/postfix/transport
#
# This sends mail to Gmail
* smtp:[smtp.gmail.com]:587
#local mail delivered local
dcerouter relay:[dcerouter]

Create generic file
touch /etc/postfix/generic

Create sasl_passwd file:

# Contents of /etc/postfix/sasl_passwd
#
[smtp.gmail.com]:587 user@gmail.com:password

Be sure to hash the files:

postmap sasl_passwd
postmap transport
postmap generic

Add these lines to the bottom of /etc/postfix/main.cf

## TLS Settings
smtp_tls_loglevel = 1
smtp_enforce_tls = yes
smtp_tls_CAfile = /etc/postfix/cacert.pem
smtp_tls_cert_file = /etc/postfix/cert.pem
smtp_tls_key_file = /etc/postfix/key.pem
smtp_tls_session_cache_database = btree:/var/run/smtp_tls_session_cache
smtp_use_tls = yes
smtpd_tls_CAfile = /etc/postfix/cacert.pem
smtpd_tls_cert_file = /etc/postfix/cert.pem
smtpd_tls_key_file = /etc/postfix/key.pem
smtpd_tls_received_header = yes
smtpd_tls_session_cache_database = btree:/var/run/smtpd_tls_session_cache
smtpd_use_tls = yes
tls_random_source = dev:/dev/urandom

## SASL Settings
# This is going in to THIS server
smtpd_sasl_auth_enable = no
# We need this
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtpd_sasl_local_domain = $myhostname
smtp_sasl_security_options = noanonymous
#smtp_sasl_security_options =
smtp_sasl_tls_security_options = noanonymous
smtpd_sasl_application_name = smtpd

## Gmail Relay
relayhost = [smtp.gmail.com]:587

# Disable DNS Lookups
disable_dns_lookups = yes
#
# Great New feature Address Mapping
# for example may mchirico@localhost to mchirico@gmail.com
smtp_generic_maps = hash:/etc/postfix/generic
#
#
transport_maps = hash:/etc/postfix/transport

restart postfix

/etc/init.d/postfix restart

install mailx

apt-get install mailx

test forward

mailx -s "testing from linuxmce" youremail@domain.com < /etc/hosts

View log

tail /var/log/mail.log

You should see your message "Sent"

Postfix configured with Gmail SMTP

2009-03-31T01:24:29Z

Dpaul: /* Install and Configure Postfix */

[[Category:Tutorials]]

== Configure Postfix to send mail using Gmail SMTP servers ==

For those who want to send email from LinuxMCE, you can configure postfix to forward mail through your gmail account.

== Install and Configure Postfix ==

Install postfix

apt-get install postfix

Create the CA:

/usr/lib/ssl/misc/CA.pl -newca

CA certificate filename (or enter to create)

Making CA certificate ...
Generating a 1024 bit RSA private key
.............++++++
..++++++
writing new private key to './demoCA/private/cakey.pem'
Enter PEM pass phrase:
Verifying - Enter PEM pass phrase:
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:US
State or Province Name (full name) [Some-State]:North Carolina
Locality Name (eg, city) []:
Organization Name (eg, company) [Internet Widgits Pty Ltd]:LinuxMCE
Organizational Unit Name (eg, section) []:
Common Name (eg, YOUR name) []:Full Name
Email Address []:email@gmail.com

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:
An optional company name []:
Using configuration from /usr/lib/ssl/openssl.cnf
Enter pass phrase for ./demoCA/private/cakey.pem:
Check that the request matches the signature
Signature ok
Certificate Details:
Serial Number:
9d:29:da:d3:76:20:17:10
Validity
Not Before: Mar 31 01:01:29 2009 GMT
Not After : Mar 30 01:01:29 2012 GMT
Subject:
countryName = US
stateOrProvinceName = North Carolina
organizationName = LinuxMCE
commonName = Full Name
emailAddress = usrer@gmail.com
X509v3 extensions:
X509v3 Subject Key Identifier:
A0:79:00:CA:90:00:E4:81:12:00:2A:73:00:00:CA:BD:54:08:03:7B
X509v3 Authority Key Identifier:
keyid:A0:79:00:CA:90:00:E4:81:12:00:2A:73:00:00:CA:BD:54:08:03:7B
DirName:/C=US/ST=North Carolina/O=LinuxMCE/CN=Full name/emailAddress=user@gmail.com
serial:90:20:0A:03:06:00:17:10

X509v3 Basic Constraints:
CA:TRUE
Certificate is to be certified until Mar 30 01:01:29 2012 GMT (1095 days)

Write out database with 1 new entries
Data Base Updated</nowiki>

Extend the key for 10 years

openssl x509 -in demoCA/cacert.pem -days 3650 -out cacert.pem -signkey demoCA/private/cakey.pem

Copy the extended key

cp cacert.pem demoCA

Generate private key

openssl req -new -nodes -subj '/CN=dcerouter/C=US/ST=North Carolina/O=LinuxMCE/CN=Full Name/emailAddress=user@gmail.com' -keyout key.pem -out req.pem -days 3650

Sign private key

openssl ca -out cert.pem -infiles req.pem

copy to the postfix directory

cp demoCA/cacert.pem /etc/postfix
cp key.pem /etc/postfix
cp cert.pem /etc/postfix
chmod 644 /etc/postfix/cert.pem
chmod 644 /etc/postfix/cacert.pem
chmod 400 /etc/postfix/key.pem

Install the CA Certificates

apt-get install ca-certificates

Add thawte certificate

cat /etc/ssl/certs/Thawte_Premium_Server_CA.pem >> cacert.pem

Create transport file:

# Contents of /etc/postfix/transport
#
# This sends mail to Gmail
* smtp:[smtp.gmail.com]:587
#local mail delivered local
dcerouter relay:[dcerouter]

Create generic file
# touch /etc/postfix/generic

Create sasl_passwd file:

# Contents of /etc/postfix/sasl_passwd
#
[smtp.gmail.com]:587 user@gmail.com:password

Be sure to hash the files:

postmap sasl_passwd
postmap transport
postmap generic

Add these lines to the bottom of /etc/postfix/main.cf

## TLS Settings
smtp_tls_loglevel = 1
smtp_enforce_tls = yes
smtp_tls_CAfile = /etc/postfix/cacert.pem
smtp_tls_cert_file = /etc/postfix/cert.pem
smtp_tls_key_file = /etc/postfix/key.pem
smtp_tls_session_cache_database = btree:/var/run/smtp_tls_session_cache
smtp_use_tls = yes
smtpd_tls_CAfile = /etc/postfix/cacert.pem
smtpd_tls_cert_file = /etc/postfix/cert.pem
smtpd_tls_key_file = /etc/postfix/key.pem
smtpd_tls_received_header = yes
smtpd_tls_session_cache_database = btree:/var/run/smtpd_tls_session_cache
smtpd_use_tls = yes
tls_random_source = dev:/dev/urandom

## SASL Settings
# This is going in to THIS server
smtpd_sasl_auth_enable = no
# We need this
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtpd_sasl_local_domain = $myhostname
smtp_sasl_security_options = noanonymous
#smtp_sasl_security_options =
smtp_sasl_tls_security_options = noanonymous
smtpd_sasl_application_name = smtpd

## Gmail Relay
relayhost = [smtp.gmail.com]:587

# Disable DNS Lookups
disable_dns_lookups = yes
#
# Great New feature Address Mapping
# for example may mchirico@localhost to mchirico@gmail.com
smtp_generic_maps = hash:/etc/postfix/generic
#
#
transport_maps = hash:/etc/postfix/transport

restart postfix

/etc/init.d/postfix restart

install mailx

apt-get install mailx

test forward

mailx -s "testing from linuxmce" youremail@domain.com < /etc/hosts

View log

tail /var/log/mail.log

You should see your message "Sent"

Postfix configured with Gmail SMTP

2009-03-31T01:22:42Z

Dpaul: New page: Category:Tutorials == Configure Postfix to send mail using Gmail SMTP servers == For those who want to send email from LinuxMCE, you can configure postfix to forward mail through you...

[[Category:Tutorials]]

== Configure Postfix to send mail using Gmail SMTP servers ==

For those who want to send email from LinuxMCE, you can configure postfix to forward mail through your gmail account.

== Install and Configure Postfix ==

Create the CA:

/usr/lib/ssl/misc/CA.pl -newca

CA certificate filename (or enter to create)

Making CA certificate ...
Generating a 1024 bit RSA private key
.............++++++
..++++++
writing new private key to './demoCA/private/cakey.pem'
Enter PEM pass phrase:
Verifying - Enter PEM pass phrase:
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:US
State or Province Name (full name) [Some-State]:North Carolina
Locality Name (eg, city) []:
Organization Name (eg, company) [Internet Widgits Pty Ltd]:LinuxMCE
Organizational Unit Name (eg, section) []:
Common Name (eg, YOUR name) []:Full Name
Email Address []:email@gmail.com

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:
An optional company name []:
Using configuration from /usr/lib/ssl/openssl.cnf
Enter pass phrase for ./demoCA/private/cakey.pem:
Check that the request matches the signature
Signature ok
Certificate Details:
Serial Number:
9d:29:da:d3:76:20:17:10
Validity
Not Before: Mar 31 01:01:29 2009 GMT
Not After : Mar 30 01:01:29 2012 GMT
Subject:
countryName = US
stateOrProvinceName = North Carolina
organizationName = LinuxMCE
commonName = Full Name
emailAddress = usrer@gmail.com
X509v3 extensions:
X509v3 Subject Key Identifier:
A0:79:00:CA:90:00:E4:81:12:00:2A:73:00:00:CA:BD:54:08:03:7B
X509v3 Authority Key Identifier:
keyid:A0:79:00:CA:90:00:E4:81:12:00:2A:73:00:00:CA:BD:54:08:03:7B
DirName:/C=US/ST=North Carolina/O=LinuxMCE/CN=Full name/emailAddress=user@gmail.com
serial:90:20:0A:03:06:00:17:10

X509v3 Basic Constraints:
CA:TRUE
Certificate is to be certified until Mar 30 01:01:29 2012 GMT (1095 days)

Write out database with 1 new entries
Data Base Updated</nowiki>

Extend the key for 10 years

openssl x509 -in demoCA/cacert.pem -days 3650 -out cacert.pem -signkey demoCA/private/cakey.pem

Copy the extended key

cp cacert.pem demoCA

Generate private key

openssl req -new -nodes -subj '/CN=dcerouter/C=US/ST=North Carolina/O=LinuxMCE/CN=Full Name/emailAddress=user@gmail.com' -keyout key.pem -out req.pem -days 3650

Sign private key

openssl ca -out cert.pem -infiles req.pem

copy to the postfix directory

cp demoCA/cacert.pem /etc/postfix
cp key.pem /etc/postfix
cp cert.pem /etc/postfix
chmod 644 /etc/postfix/cert.pem
chmod 644 /etc/postfix/cacert.pem
chmod 400 /etc/postfix/key.pem

Install the CA Certificates

apt-get install ca-certificates

Add thawte certificate

cat /etc/ssl/certs/Thawte_Premium_Server_CA.pem >> cacert.pem

Create transport file:

# Contents of /etc/postfix/transport
#
# This sends mail to Gmail
* smtp:[smtp.gmail.com]:587
#local mail delivered local
dcerouter relay:[dcerouter]

Create generic file
# touch /etc/postfix/generic

Create sasl_passwd file:

# Contents of /etc/postfix/sasl_passwd
#
[smtp.gmail.com]:587 user@gmail.com:password

Be sure to hash the files:

postmap sasl_passwd
postmap transport
postmap generic

Add these lines to the bottom of /etc/postfix/main.cf

## TLS Settings
smtp_tls_loglevel = 1
smtp_enforce_tls = yes
smtp_tls_CAfile = /etc/postfix/cacert.pem
smtp_tls_cert_file = /etc/postfix/cert.pem
smtp_tls_key_file = /etc/postfix/key.pem
smtp_tls_session_cache_database = btree:/var/run/smtp_tls_session_cache
smtp_use_tls = yes
smtpd_tls_CAfile = /etc/postfix/cacert.pem
smtpd_tls_cert_file = /etc/postfix/cert.pem
smtpd_tls_key_file = /etc/postfix/key.pem
smtpd_tls_received_header = yes
smtpd_tls_session_cache_database = btree:/var/run/smtpd_tls_session_cache
smtpd_use_tls = yes
tls_random_source = dev:/dev/urandom

## SASL Settings
# This is going in to THIS server
smtpd_sasl_auth_enable = no
# We need this
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtpd_sasl_local_domain = $myhostname
smtp_sasl_security_options = noanonymous
#smtp_sasl_security_options =
smtp_sasl_tls_security_options = noanonymous
smtpd_sasl_application_name = smtpd

## Gmail Relay
relayhost = [smtp.gmail.com]:587

# Disable DNS Lookups
disable_dns_lookups = yes
#
# Great New feature Address Mapping
# for example may mchirico@localhost to mchirico@gmail.com
smtp_generic_maps = hash:/etc/postfix/generic
#
#
transport_maps = hash:/etc/postfix/transport

restart postfix

/etc/init.d/postfix restart

install mailx

apt-get install mailx

test forward

mailx -s "testing from linuxmce" youremail@domain.com < /etc/hosts

View log

tail /var/log/mail.log

You should see your message "Sent"

MythTv: Don't scan live tv

2009-03-20T14:07:27Z

Dpaul:

[[Category:Tutorials]]

== Making MythTV LiveTv recordings invisible to LinuxMCE ==

For those who watch a lot of live TV, you'll notice that LinuxMCE adds all of those LiveTV recordings to the LinuxMCE DB. Not only does this fill up the database, but it makes browsing media quite ugly. There is an easy way to solve this.

== Locating and editing the SaveMythRecording.sh file ==

The file is stored in
/usr/pluto/bin

The first thing to do is make the directory that will hold the recordings:

mkdir /home/public/data/videos/tv_shows_0

Then make a backup of the SaveMythRecording.sh script:

cp /usr/pluto/bin/SaveMythRecording.sh /usr/pluto/bin/SaveMythRecording.sh.bak

Now edit SaveMythRecording.sh with your favorite program:

#!/bin/bash

dir=/home/public/data/videos/tv_shows_0

mv $3/$4 $dir/$4
touch $3/$4
chown mythtv:public $3/$4

echo "$(date) $0-$1-$2-$dir-$4" >> /var/log/pluto/donerecording.log
/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 69 29 "$1" 57 "$2" 35 "$dir/$4"''

== Prevent UpdateMedia from scanning LiveTV recordings ==

Create a file, /home/public/data/videos/tv_shows_1.folderlock, to prevent scanning:

touch /home/public/data/videos/tv_shows_1.folderlock

== Conclusion ==

Now when browsing Media, LiveTv recordings will not show in the Video list. Your recordings will never be expired or deleted by MythTv, and MythTv will continue functioning without errors. All LiveTv recordings and scheduled recordings can still be expired and deleted through the MythWeb interface without impacting LinuxMCE.

MythTv: Don't scan live tv

2009-03-20T04:28:45Z

Dpaul: /* Conclusion */

== Making MythTV LiveTv recordings invisible to LinuxMCE ==

For those who watch a lot of live TV, you'll notice that LinuxMCE adds all of those LiveTV recordings to the LinuxMCE DB. Not only does this fill up the database, but it makes browsing media quite ugly. There is an easy way to solve this.

== Locating and editing the SaveMythRecording.sh file ==

The file is stored in
/usr/pluto/bin

The first thing to do is make the directory that will hold the recordings:

mkdir /home/public/data/videos/tv_shows_0

Then make a backup of the SaveMythRecording.sh script:

cp /usr/pluto/bin/SaveMythRecording.sh /usr/pluto/bin/SaveMythRecording.sh.bak

Now edit SaveMythRecording.sh with your favorite program:

#!/bin/bash

dir=/home/public/data/videos/tv_shows_0

mv $3/$4 $dir/$4
touch $3/$4
chown mythtv:public $3/$4

echo "$(date) $0-$1-$2-$dir-$4" >> /var/log/pluto/donerecording.log
/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 69 29 "$1" 57 "$2" 35 "$dir/$4"''

== Prevent UpdateMedia from scanning LiveTV recordings ==

Create a file, /home/public/data/videos/tv_shows_1.folderlock, to prevent scanning:

touch /home/public/data/videos/tv_shows_1.folderlock

== Conclusion ==

Now when browsing Media, LiveTv recordings will not show in the Video list. Your recordings will never be expired or deleted by MythTv, and MythTv will continue functioning without errors. All LiveTv recordings and scheduled recordings can still be expired and deleted through the MythWeb interface without impacting LinuxMCE.

MythTv: Don't scan live tv

2009-03-20T03:52:36Z

Dpaul: /* Locating and editing the SaveMythRecording.sh file */

== Making MythTV LiveTv recordings invisible to LinuxMCE ==

For those who watch a lot of live TV, you'll notice that LinuxMCE adds all of those LiveTV recordings to the LinuxMCE DB. Not only does this fill up the database, but it makes browsing media quite ugly. There is an easy way to solve this.

== Locating and editing the SaveMythRecording.sh file ==

The file is stored in
/usr/pluto/bin

The first thing to do is make the directory that will hold the recordings:

mkdir /home/public/data/videos/tv_shows_0

Then make a backup of the SaveMythRecording.sh script:

cp /usr/pluto/bin/SaveMythRecording.sh /usr/pluto/bin/SaveMythRecording.sh.bak

Now edit SaveMythRecording.sh with your favorite program:

#!/bin/bash

dir=/home/public/data/videos/tv_shows_0

mv $3/$4 $dir/$4
touch $3/$4
chown mythtv:public $3/$4

echo "$(date) $0-$1-$2-$dir-$4" >> /var/log/pluto/donerecording.log
/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 69 29 "$1" 57 "$2" 35 "$dir/$4"''

== Prevent UpdateMedia from scanning LiveTV recordings ==

Create a file, /home/public/data/videos/tv_shows_1.folderlock, to prevent scanning:

touch /home/public/data/videos/tv_shows_1.folderlock

== Conclusion ==

Now when browsing Media, LiveTv recording will not show up in the list. Your recordings will never be expired or deleted by MythTv, and MythTv will continue functioning without errors. All LiveTv recordings and scheduled recordings can still be expired and deleted through the MythWeb interface without impacting LinuxMCE.

MythTv: Don't scan live tv

2009-03-20T03:51:50Z

Dpaul: /* Locating and editing the SaveMythRecording.sh file */

== Making MythTV LiveTv recordings invisible to LinuxMCE ==

For those who watch a lot of live TV, you'll notice that LinuxMCE adds all of those LiveTV recordings to the LinuxMCE DB. Not only does this fill up the database, but it makes browsing media quite ugly. There is an easy way to solve this.

== Locating and editing the SaveMythRecording.sh file ==

The file is stored in
/usr/pluto/bin

The first thing to do is make the directory that will hold the recordings:

mkdir /home/public/data/videos/tv_shows_0

Then make a backup of the SaveMythRecording.sh script:

cp /usr/pluto/bin/SaveMythRecording.sh /usr/pluto/bin/SaveMythRecording.sh.bak

Now edit SaveMythRecording.sh with your favorite program:

#!/bin/bash

dir=/home/public/data/videos/tv_shows_0

mv $3/$4 $dir/$4
touch $3/$4 | chown mythtv:public $3/$4

echo "$(date) $0-$1-$2-$dir-$4" >> /var/log/pluto/donerecording.log
/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 69 29 "$1" 57 "$2" 35 "$dir/$4"''

== Prevent UpdateMedia from scanning LiveTV recordings ==

Create a file, /home/public/data/videos/tv_shows_1.folderlock, to prevent scanning:

touch /home/public/data/videos/tv_shows_1.folderlock

== Conclusion ==

Now when browsing Media, LiveTv recording will not show up in the list. Your recordings will never be expired or deleted by MythTv, and MythTv will continue functioning without errors. All LiveTv recordings and scheduled recordings can still be expired and deleted through the MythWeb interface without impacting LinuxMCE.

MythTv: Don't scan live tv

2009-03-20T03:51:29Z

Dpaul: /* Locating and editing the SaveMythRecording.sh file */

== Making MythTV LiveTv recordings invisible to LinuxMCE ==

For those who watch a lot of live TV, you'll notice that LinuxMCE adds all of those LiveTV recordings to the LinuxMCE DB. Not only does this fill up the database, but it makes browsing media quite ugly. There is an easy way to solve this.

== Locating and editing the SaveMythRecording.sh file ==

The file is stored in
/usr/pluto/bin

The first thing to do is make the directory that will hold the recordings:

mkdir /home/public/data/videos/tv_shows

Then make a backup of the SaveMythRecording.sh script:

cp /usr/pluto/bin/SaveMythRecording.sh /usr/pluto/bin/SaveMythRecording.sh.bak

Now edit SaveMythRecording.sh with your favorite program:

#!/bin/bash

dir=/home/public/data/videos/tv_shows_0

mv $3/$4 $dir/$4
touch $3/$4 | chown mythtv:public $3/$4

echo "$(date) $0-$1-$2-$dir-$4" >> /var/log/pluto/donerecording.log
/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 69 29 "$1" 57 "$2" 35 "$dir/$4"''

== Prevent UpdateMedia from scanning LiveTV recordings ==

Create a file, /home/public/data/videos/tv_shows_1.folderlock, to prevent scanning:

touch /home/public/data/videos/tv_shows_1.folderlock

== Conclusion ==

Now when browsing Media, LiveTv recording will not show up in the list. Your recordings will never be expired or deleted by MythTv, and MythTv will continue functioning without errors. All LiveTv recordings and scheduled recordings can still be expired and deleted through the MythWeb interface without impacting LinuxMCE.

MythTv: Don't scan live tv

2009-03-20T03:32:45Z

Dpaul:

== Making MythTV LiveTv recordings invisible to LinuxMCE ==

For those who watch a lot of live TV, you'll notice that LinuxMCE adds all of those LiveTV recordings to the LinuxMCE DB. Not only does this fill up the database, but it makes browsing media quite ugly. There is an easy way to solve this.

== Locating and editing the SaveMythRecording.sh file ==

The file is stored in
/usr/pluto/bin

The first thing to do is make the directory that will hold the recordings:

mkdir /home/public/data/videos/tv_shows

Then make a backup of the SaveMythRecording.sh script:

cp /usr/pluto/bin/SaveMythRecording.sh /usr/pluto/bin/SaveMythRecording.sh.bak

Now edit SaveMythRecording.sh with your favorite program:

#!/bin/bash

dir=/home/public/data/videos/tv_shows

mv $3/$4 $dir/$4
touch $3/$4 | chown mythtv:public $3/$4

echo "$(date) $0-$1-$2-$dir-$4" >> /var/log/pluto/donerecording.log
/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 69 29 "$1" 57 "$2" 35 "$dir/$4"''

== Prevent UpdateMedia from scanning LiveTV recordings ==

Create a file, /home/public/data/videos/tv_shows_1.folderlock, to prevent scanning:

touch /home/public/data/videos/tv_shows_1.folderlock

== Conclusion ==

Now when browsing Media, LiveTv recording will not show up in the list. Your recordings will never be expired or deleted by MythTv, and MythTv will continue functioning without errors. All LiveTv recordings and scheduled recordings can still be expired and deleted through the MythWeb interface without impacting LinuxMCE.

MythTv: Don't scan live tv

2009-03-20T03:25:11Z

Dpaul: /* Making MythTV liveTv recordings invisible to LinuxMCE */

[[Category:Tutorials]]

== Making MythTV LiveTv recordings invisible to LinuxMCE ==

For those who watch a lot of live TV, you'll notice that LinuxMCE adds all of those LiveTV recordings to the LinuxMCE DB. Not only does this fill up the database, but it makes browsing media quite ugly. There is an easy way to solve this.

== Locating and editing the SaveMythRecording.sh file ==

The file is stored in
/usr/pluto/bin

The first thing to do is make the directory that will hold the recordings:

mkdir /home/public/data/videos/tv_shows

Then make a backup of the SaveMythRecording.sh script:

cp /usr/pluto/bin/SaveMythRecording.sh /usr/pluto/bin/SaveMythRecording.sh.bak

Now edit SaveMythRecording.sh with your favorite program:

#!/bin/bash

dir=/home/public/data/videos/tv_shows

mv $3/$4 $dir/$4
touch $3/$4 | chown mythtv:public $3/$4

echo "$(date) $0-$1-$2-$dir-$4" >> /var/log/pluto/donerecording.log
/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 69 29 "$1" 57 "$2" 35 "$dir/$4"''

== Prevent UpdateMedia from scanning LiveTV recordings ==

Create a file, /home/public/data/videos/tv_shows_1.folderlock, to prevent scanning:

touch /home/public/data/videos/tv_shows_1.folderlock

== Conclusion ==

Now when browsing Media, LiveTv recording will not show up in the list. Your recordings will never be expired or deleted by MythTv, and MythTv will continue functioning without errors. All LiveTv recordings and scheduled recordings can still be expired and deleted through the MythWeb interface without impacting LinuxMCE.

MythTv: Don't scan live tv

2009-03-20T03:24:42Z

Dpaul: /* Locating and editing the SaveMythRecording.sh file */

[[Category:Tutorials]]

== Making MythTV liveTv recordings invisible to LinuxMCE ==

For those who watch a lot of live TV, you'll notice that LinuxMCE adds all of those LiveTV recordings to the LinuxMCE DB. Not only does this fill up the database, but it makes browsing media quite ugly. There is an easy way to solve this.

== Locating and editing the SaveMythRecording.sh file ==

The file is stored in
/usr/pluto/bin

The first thing to do is make the directory that will hold the recordings:

mkdir /home/public/data/videos/tv_shows

Then make a backup of the SaveMythRecording.sh script:

cp /usr/pluto/bin/SaveMythRecording.sh /usr/pluto/bin/SaveMythRecording.sh.bak

Now edit SaveMythRecording.sh with your favorite program:

#!/bin/bash

dir=/home/public/data/videos/tv_shows

mv $3/$4 $dir/$4
touch $3/$4 | chown mythtv:public $3/$4

echo "$(date) $0-$1-$2-$dir-$4" >> /var/log/pluto/donerecording.log
/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 69 29 "$1" 57 "$2" 35 "$dir/$4"''

== Prevent UpdateMedia from scanning LiveTV recordings ==

Create a file, /home/public/data/videos/tv_shows_1.folderlock, to prevent scanning:

touch /home/public/data/videos/tv_shows_1.folderlock

== Conclusion ==

Now when browsing Media, LiveTv recording will not show up in the list. Your recordings will never be expired or deleted by MythTv, and MythTv will continue functioning without errors. All LiveTv recordings and scheduled recordings can still be expired and deleted through the MythWeb interface without impacting LinuxMCE.

MythTv: Don't scan live tv

2009-03-20T03:24:30Z

Dpaul: /* Making MythTV liveTv recordings invisible to LinuxMCE */

MythTv: Don't scan live tv

2009-03-20T03:23:53Z

Dpaul:

[[Category:Tutorials]]

== Making MythTV liveTv recordings invisible to LinuxMCE ==

For those who watch a lot of live TV, you'll notice that LinuxMCE add all of those LiveTV recording to the LinuxMCE DB. Not only does this fill up the database, but it makes browsing media very ugly. There is an easy way to solve this.

== Locating and editing the SaveMythRecording.sh file ==

The file is stored in
/usr/pluto/bin

The first thing to do is make the directory that will hold the recordings:

mkdir /home/public/data/videos/tv_shows

Then make a backup of the SaveMythRecording.sh script:

cp /usr/pluto/bin/SaveMythRecording.sh /usr/pluto/bin/SaveMythRecording.sh.bak

Now edit SaveMythRecording.sh with your favorite program:

#!/bin/bash

dir=/home/public/data/videos/tv_shows

mv $3/$4 $dir/$4
touch $3/$4 | chown mythtv:public $3/$4

echo "$(date) $0-$1-$2-$dir-$4" >> /var/log/pluto/donerecording.log
/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 69 29 "$1" 57 "$2" 35 "$dir/$4"''

== Prevent UpdateMedia from scanning LiveTV recordings ==

Create a file, /home/public/data/videos/tv_shows_1.folderlock, to prevent scanning:

touch /home/public/data/videos/tv_shows_1.folderlock

== Conclusion ==

Now when browsing Media, LiveTv recording will not show up in the list. Your recordings will never be expired or deleted by MythTv, and MythTv will continue functioning without errors. All LiveTv recordings and scheduled recordings can still be expired and deleted through the MythWeb interface without impacting LinuxMCE.

MythTv: Don't scan live tv

2009-03-20T00:45:07Z

Dpaul: New page: Category:Tutorials == Making MythTV liveTv recordings invisible to LinuxMCE == For those who watch a lot of live TV, you'll notice that LinuxMCE add all of those LiveTV recording to ...

[[Category:Tutorials]]

== Making MythTV liveTv recordings invisible to LinuxMCE ==

For those who watch a lot of live TV, you'll notice that LinuxMCE add all of those LiveTV recording to the LinuxMCE DB. Not only does this fill up the database, but it makes browsing media very ugly. There is an easy way to solve this.

== Locating and editing the SaveMythRecording.sh file ==

The file is stored in
/usr/pluto/bin

The first thing to do is make the directory that will hold the recordings:

mkdir /home/public/data/videos/tv_shows

Then make a backup of the SaveMythRecording.sh script:

cp /usr/pluto/bin/SaveMythRecording.sh /usr/pluto/bin/SaveMythRecording.sh.bak

Now edit SaveMythRecording.sh with your favorite program:

#!/bin/bash

dir=/home/public/data/videos/tv_shows

cp $3/$4 $dir
cat /dev/null > $3/$4
echo "$(date) $0-$1-$2-$dir-$4" >> /var/log/pluto/donerecording.log
/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 69 29 "$1" 57 "$2" 35 "$dir/$4"''

== Prevent UpdateMedia from scanning LiveTV recordings ==

Create a file, /home/public/data/videos/tv_shows_1.folderlock, to prevent scanning:

touch /home/public/data/videos/tv_shows_1.folderlock

== Conclusion ==

Now when browsing Media, LiveTv recording will not show up in the list. Your recordings will never be expired or deleted by MythTv, and MythTv will continue functioning without errors. All LiveTv recordings and scheduled recordings can still be expired and deleted through the MythWeb interface without impacting LinuxMCE.

Linksys SPA2000

2009-03-17T04:59:32Z

Dpaul: /* Setup */

== General Information ==

The Sipura (now bought out by Linksys) spa 2000 is a pstn (analog phone line) to Asterisk gateway device that provides a SIP interface for 2 FXS ports (analog phone). This allows you to use your analog phones with LinuxMCE/Asterisk.

http://www.voip-info.org/wiki/index.php?page=Sipura+SPA-2000

== Setup ==

We are going to accomplish this setup in 2 easy steps:
1) Adding the device for the internal phone lines (FXS ports)
2) Configuring the spa2000

'''Step 1 - Adding the device template for the FXS ports (your internal phone/phones)'''

In the web admin, on the left pane under devices, select Phones. On the resulting page, you should see all of the Orbiter Embedded Phones that your system already has. At the bottom of this page, click the "Add Device" button, then select "Generic SIP Softphone" from the Device Template picker. Click the "Pick device template" button.
Now notice that you have a new phone device in you list. Change the name to something like "House Line", set the PK_FloorplanObjectType to "Cordless Phone", set the Phone Type to SIP. Notice that the PhoneNumber is already filled out. LEAVE THIS ALONE AND REMEMBER IT! This will be the extension of your internal analog phones (or whatever single phone you have plugged into the FXS Port!) Also, you can assign this phone a room (it really doesn't matter which one you choose) and make sure the "Controlled By" column says Asterisk. If it does not say "Asterisk", click on it and choose Asterisk (Asterisk) - from the dropdown. When finished, Hit the Update button at the bottom of the screen to save these changes. You will have to reload your router, and do a quick regen on all orbiters manually (from the Devices->Orbiters section)

Repeat the above steps to create another device if you plan on using the second FXS port.

'''Step 2 - Configuring the spa2000'''

This part assumes a factory default starting point. To do this, hook up an analog phone to the FXS (phone) port, and dial ****
When prompted, enter ****73738# from the telephone keypad, then press 1 to confirm. This will reset the unit to factory defaults.

Now go ahead and connect the spa2000 to your internal network switch. Dial **** from the connected handset to get the IP address. Open up a web browser on the network, and enter the IP address to go to the spa2000 admin page. In the upper right hand corner, click on the link for Advanced.

Next, go to the SIP tab. Change the following:
RTP Packet Size: 0.020

Next, go to the Line 1 tab. Change the following:

Line Enable: Yes

SIP Port: 5060

Proxy: 192.168.80.1

Register: Yes

Register Expires: 3600

Make Call Without Reg: yes

Ans Call Without Reg: yes

Display Name: <extension number LMCE assigned your Generic Phone device> (mine was 206 for example)

UserID: <again, extension number LMCE assigned your Generic Phone device>

Password: <once again, extension number LMCE assigned your Generic Phone device>

Use AuthID: no

Preferred Codec: set to G711u

Use Pref Codec Only: no

Dial Plan: (xxx|xxxx|xxxxxxx|xxxxxxxxxx|1xxxxxxxxxx)

Next, go to the Line 2 tab. Make the same changes as above.

Now enjoy LMCE Telecom on your old analog phone line!

[[Category:Tutorials]][[Category:PSTN Setups]]

Linksys SPA2000

2009-03-17T04:59:14Z

Dpaul: /* Setup */

Linksys SPA2000

2009-03-17T04:58:18Z

Dpaul: /* General Information */

== General Information ==

The Sipura (now bought out by Linksys) spa 2000 is a pstn (analog phone line) to Asterisk gateway device that provides a SIP interface for 2 FXS ports (analog phone). This allows you to use your analog phones with LinuxMCE/Asterisk.

http://www.voip-info.org/wiki/index.php?page=Sipura+SPA-2000

== Setup ==

We are going to accomplish this setup in 2 easy steps:
1) Adding the device for the internal phone lines (FXS ports)
2) Configuring the spa2000

'''Step 1 - Adding the device template for the FXS ports (your internal phone/phones)'''

In the web admin, on the left pane under devices, select Phones. On the resulting page, you should see all of the Orbiter Embedded Phones that your system already has. At the bottom of this page, click the "Add Device" button, then select "Generic SIP Softphone" from the Device Template picker. Click the "Pick device template" button.
Now notice that you have a new phone device in you list. Change the name to something like "House Line", set the PK_FloorplanObjectType to "Cordless Phone", set the Phone Type to SIP. Notice that the PhoneNumber is already filled out. LEAVE THIS ALONE AND REMEMBER IT! This will be the extension of your internal analog phones (or whatever single phone you have plugged into the FXS Port!) Also, you can assign this phone a room (it really doesn't matter which one you choose) and make sure the "Controlled By" column says Asterisk. If it does not say "Asterisk", click on it and choose Asterisk (Asterisk) - from the dropdown. When finished, Hit the Update button at the bottom of the screen to save these changes. You will have to reload your router, and do a quick regen on all orbiters manually (from the Devices->Orbiters section)

Repeat the above steps to create another device if you plan on using the second FXS port.

'''Step 2 - Configuring the spa2000'''

This part assumes a factory default starting point. To do this, hook up an analog phone to the FXS (phone) port, and dial ****
When prompted, enter ****73738# from the telephone keypad, then press 1 to confirm. This will reset the unit to factory defaults.

Now go ahead and connect the spa2000 to your internal network switch. Dial **** from the connected handset to get the IP address. Open up a web browser on the network, and enter the IP address to go to the spa2000 admin page. In the upper right hand corner, click on the link for Advanced.

Next, go to the SIP tab. Change the following:
RTP Packet Size: 0.020

Next, go to the Line 1 tab. Change the following:
Line Enable: Yes
SIP Port: 5060
Proxy: 192.168.80.1
Register: Yes
Register Expires: 3600
Make Call Without Reg: yes
Ans Call Without Reg: yes
Display Name: <extension number LMCE assigned your Generic Phone device> (mine was 206 for example)
UserID: <again, extension number LMCE assigned your Generic Phone device>
Password: <once again, extension number LMCE assigned your Generic Phone device>
Use AuthID: no
Preferred Codec: set to G711u
Use Pref Codec Only: no
Dial Plan: (xxx|xxxx|xxxxxxx|xxxxxxxxxx|1xxxxxxxxxx)

Next, go to the Line 2 tab. Make the same changes as above.

Now enjoy LMCE Telecom on your old analog phone line!

[[Category:Tutorials]][[Category:PSTN Setups]]

Linksys SPA2000

2009-03-17T04:57:55Z

Dpaul: /* Setup */

== General Information ==

The Sipura (now bought out by Linksys) spa 2000 is a pstn (analog phone line) to Asterisk gateway device that provides a SIP interface for 2 FXS ports (analog phone). This allows you to use your analog phones with LinuxMCE/Asterix.

http://www.voip-info.org/wiki/index.php?page=Sipura+SPA-2000

== Setup ==

We are going to accomplish this setup in 2 easy steps:
1) Adding the device for the internal phone lines (FXS ports)
2) Configuring the spa2000

'''Step 1 - Adding the device template for the FXS ports (your internal phone/phones)'''

In the web admin, on the left pane under devices, select Phones. On the resulting page, you should see all of the Orbiter Embedded Phones that your system already has. At the bottom of this page, click the "Add Device" button, then select "Generic SIP Softphone" from the Device Template picker. Click the "Pick device template" button.
Now notice that you have a new phone device in you list. Change the name to something like "House Line", set the PK_FloorplanObjectType to "Cordless Phone", set the Phone Type to SIP. Notice that the PhoneNumber is already filled out. LEAVE THIS ALONE AND REMEMBER IT! This will be the extension of your internal analog phones (or whatever single phone you have plugged into the FXS Port!) Also, you can assign this phone a room (it really doesn't matter which one you choose) and make sure the "Controlled By" column says Asterisk. If it does not say "Asterisk", click on it and choose Asterisk (Asterisk) - from the dropdown. When finished, Hit the Update button at the bottom of the screen to save these changes. You will have to reload your router, and do a quick regen on all orbiters manually (from the Devices->Orbiters section)

Repeat the above steps to create another device if you plan on using the second FXS port.

'''Step 2 - Configuring the spa2000'''

This part assumes a factory default starting point. To do this, hook up an analog phone to the FXS (phone) port, and dial ****
When prompted, enter ****73738# from the telephone keypad, then press 1 to confirm. This will reset the unit to factory defaults.

Now go ahead and connect the spa2000 to your internal network switch. Dial **** from the connected handset to get the IP address. Open up a web browser on the network, and enter the IP address to go to the spa2000 admin page. In the upper right hand corner, click on the link for Advanced.

Next, go to the SIP tab. Change the following:
RTP Packet Size: 0.020

Next, go to the Line 1 tab. Change the following:
Line Enable: Yes
SIP Port: 5060
Proxy: 192.168.80.1
Register: Yes
Register Expires: 3600
Make Call Without Reg: yes
Ans Call Without Reg: yes
Display Name: <extension number LMCE assigned your Generic Phone device> (mine was 206 for example)
UserID: <again, extension number LMCE assigned your Generic Phone device>
Password: <once again, extension number LMCE assigned your Generic Phone device>
Use AuthID: no
Preferred Codec: set to G711u
Use Pref Codec Only: no
Dial Plan: (xxx|xxxx|xxxxxxx|xxxxxxxxxx|1xxxxxxxxxx)

Next, go to the Line 2 tab. Make the same changes as above.

Now enjoy LMCE Telecom on your old analog phone line!

[[Category:Tutorials]][[Category:PSTN Setups]]