Using LinuxMCE-Admin - Revision history

Perspectoff: Redirecting to LinuxMCE Admin Website

2008-05-22T04:09:40Z

←Older revision		Revision as of 04:09, 22 May 2008
Line 1:		Line 1:
	~~Also see:~~ [[LinuxMCE Admin Website]]		#REDIRECT [[LinuxMCE Admin Website]]

	~~<p>You need a web browser to configure your LinuxMCE system using the built-in [[LinuxMCE Admin Website]]~~
	Since the Hybrid + Media Directors have one built in, you can choose Advanced > Computing and click the "LinuxMCE Admin" website to bring it up directly on the Hybrid. Or, from any web browser in your home, go to the URL: http://myip/LinuxMCE_admin where myip is the IP address of the
	~~Core/Hybrid. To find the ip of your Core/Hybrid, choose Advanced, Advanced Options and it's shown at the top.~~

	~~Login then click [[Wizard Pages\|Wizard]]. You will see the following screen.</p>~~
	~~[[Image:Wizard.jpg\|200px]]~~

	~~<p>Follow each of the links in the left panel to choose your basic settings, add the devices, scenarios, and event handlers.~~
	Here's an example for setting up an ultra low-cost smart home setup based on [[X10]]. The equipment we mention will cost under $1,000, although the procedure is exactly the same with a $100,000 high-end based on [[Lutron]], [[Vantage]], [[EIB]], etc. So, please read the example regardless of your system type, so you understand the techniques.</p>
	~~<p><b>EXAMPLE: Adding other devices</b></p><p>Example:~~
	You have 2 [[gc100]]'s which give you Infrared control of you're a/v equipment, extra serial ports to plug other stuff into, ttl inputs and relays. You have some TVs and stereos to control, and also a [[CM11A]] module to control [[X10]] devices, plus some [[X10]] lights and [[thermostats]].
	~~You will plug the [[CM11A]] into one of the rs232 serial ports on the [[gc100]]. You also have an alarm panel with a serial interface, some squeeze box audio players, and some network cameras.</p>~~

	~~<p>After specifying [[Basic Info]] on the first couple wizard pages, like family members and rooms, you get to [[Interfaces]].~~
	Here you add all the devices that are used to interface with, or control other devices. So, the [[gc100]] is an interface device, but the TVs and stereos it controls are on the a/v page. The [[CM11A]], [[Vantage]], [[Lutron]], etc. are also interfaces, the lights, blinds, drapes, etc. they control are on the [[Lights]]\|lighting page. The alarm panel is an interface, the motion, glass break, smoke alarms, etc., are on the [[Security]].
	~~Some home automation devices do not require an interface, some do. An IP-based camera does not require an interface device-add it directly to [[Surveillance Cameras]].~~
	Analog cameras do need some sort of interface device, like a camera capture board, which you must first add to the interfaces page. Add the interface devices first on the interface page, and then the devices they control on the respective page. If you want to add [[EIB]] lights (on the lights page), you won't be allowed to do that until you first add the [[EIB]] interface on the interfaces page, because an [[EIB]] light cannot be used without an interface. If you add interfaces for both an [[EIB]] Lighting system, and an [[X10]] lighting system, then on the lighting page you will be able to add both types of lights, and the 'Controlled Via' field will show you what interface is being used.</p>
	<p>Back to our example: Plug one of your [[gc100]]'s into the network, and click the 'add gc100' button on the interface page. [[gc100]]'s are treated special because they are IP-based, but their network configuration is a bit different and does not allow them to be plug-and-play. Once you got the message that it was found and configured, click on the Interfaces page again--now you'll see it there. Maybe give it a descriptive name so you can remember which is which. Now plug in the 2nd gc100, and repeat.
	Next choose 'Add Devices' and add the [[CM11A]]. Like all [[RS232]] devices, it is not plug and play, you must add it manually. Repeat for the alarm panel. In both cases, the Controlled Via devices is the Core, since that's where the software drivers will be run. But, when you go to choose the port, it only shows the Core's internal serial ports, and you want to plug it into one of the ports on the gc100. So, click '[[Wizard]]', 'Restart' and 'quick reload router'. That causes the [[DCE Router]] to reload the list of devices in the house so it sees the new gc100's you added, and adds the ports. Refresh the Interfaces page, and now you can choose the gc100 ports for the CM11A and alarm panel.</p><p>Next, add your TVs and stereos on the [[AV Devices]] and indicate how they are connected (which AV inputs). If your model is not in the database you will need to add it. If the I/R codes for your device aren't listed or don't work, you will click the A/V properties button and either [[Learning/typing my own code\|learn them]] using the gc100's learner (plug it into serial port 1 and click 'learn'), or [[Learning/typing my own code\|copy+paste the I/R codes in pronto format]] from a source like www.remotecentral.com. Your devices and I/R codes will automatically be sent to LinuxMCE and added to the master database for other users unless you uncheck the box. In the 'controlled via' choose whichever one of the gc100's has the infrared emitter attached for that device. Turn your Squeeze Boxes on, set the network to [[DHCP]], and plug them in. LinuxMCE will automatically recognize them and configure them. You will see a confirmation message and be asked to pick the room they're in. Refresh the A/V page to see the Squeeze Boxes and indicate how you connect them to your stereo system.</p>

	<p>On the [[Media Directors]] and [[Orbiters]] page, be sure your settings are correct. Then on the [[Lights]] and [[Climate]] pages, add all your [[X10]] lights/thermostats. The 'Controlled Via' is the [[CM11A]] device. On the security page, add all your motion detectors, smoke alarms, etc. The 'Controlled Via' is the alarm panel.
	~~On the [[Floorplans]], drag and drop your devices on the maps you upload. You'll need to do a 'regen orbiter' followed by a 'quick reload router' before you can use the floorplans.</p>~~

	<p>Now let's test the devices. Do another 'quick reload router' so [[DCERouter]] sees these new devices. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing [[Devices]] from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, go to 'Advanced', 'Logs' and check the logs for the interface, the [[CM11A]] in this case.</p>



	~~===Adding custom entries in LinuxMCE-Admin menus===~~

	Currently only option is to enter entries into Pluto_main database, table PageSetup. There you'll find other entries already, go to the end and add yours (but be careful not to break anything and also save your changes, cause they can probably lost in migration or updates - not sure)...

	Anyway for simple test I've created two entries: "Tinia" as main menu entry (after Telecom) and then subentry for phpmyadmin that I frequently use. If I highlight only important fields, my entries look like this :

	~~'''PK_PageSetup FK_..._Parent Website OrderNum FK_Package Description pageURL showInTopMenu'''~~
	~~190 NULL 1 70 NULL Tinia 1~~
	~~191 190 1 0 NULL PHPMyAdmin http://192.168.0.1/phpmyadmin/ 1~~

	~~If FK_PageSetup_Parent is empty, then you'll have main entry on green main bar. If you want subentry, then you just specify PK_PageSetup of your parent in FK_PageSetup_Parent. You can also add URL~~
	~~[[Category:Tutorials~~]]

Perspectoff: /* Scenarios, Events & Security */

2008-05-22T04:07:24Z

Scenarios, Events & Security

←Older revision		Revision as of 04:07, 22 May 2008
Line 26:		Line 26:
	<p>Now let's test the devices. Do another 'quick reload router' so [[DCERouter]] sees these new devices. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing [[Devices]] from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, go to 'Advanced', 'Logs' and check the logs for the interface, the [[CM11A]] in this case.</p>		<p>Now let's test the devices. Do another 'quick reload router' so [[DCERouter]] sees these new devices. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing [[Devices]] from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, go to 'Advanced', 'Logs' and check the logs for the interface, the [[CM11A]] in this case.</p>

	~~===Scenarios, Events & Security===~~

	<p>In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living room to view a camera. When you do a 'quick reload router', [[DCERouter]] will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using LinuxMCE with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want LinuxMCE to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.</p>

	===Adding custom entries in LinuxMCE-Admin menus===		===Adding custom entries in LinuxMCE-Admin menus===

Perspectoff at 18:34, 21 May 2008

2008-05-21T18:34:03Z

←Older revision		Revision as of 18:34, 21 May 2008
Line 1:		Line 1:
			Also see: [[LinuxMCE Admin Website]]

	<p>You need a web browser to configure your LinuxMCE system using the built-in [[LinuxMCE Admin Website]]		<p>You need a web browser to configure your LinuxMCE system using the built-in [[LinuxMCE Admin Website]]
	Since the Hybrid + Media Directors have one built in, you can choose Advanced > Computing and click the "LinuxMCE Admin" website to bring it up directly on the Hybrid. Or, from any web browser in your home, go to the URL: http://myip/LinuxMCE_admin where myip is the IP address of the		Since the Hybrid + Media Directors have one built in, you can choose Advanced > Computing and click the "LinuxMCE Admin" website to bring it up directly on the Hybrid. Or, from any web browser in your home, go to the URL: http://myip/LinuxMCE_admin where myip is the IP address of the

Bulek: /* Adding custom entries in LinuxMCE-Admin menus */

2008-04-04T10:50:40Z

Adding custom entries in LinuxMCE-Admin menus

←Older revision		Revision as of 10:50, 4 April 2008
Line 30:		Line 30:
	===Adding custom entries in LinuxMCE-Admin menus===		===Adding custom entries in LinuxMCE-Admin menus===

	~~<p>In the [[Scenarios]] page, add the scenarios, or buttons~~, you ~~want for each room. Like a Lighting scenario in the Bedroom called~~ 'Go to ~~sleep' which dims~~ the ~~lights~~, or ~~a security scenario in the living room to view a camera~~. ~~When you do a~~ '~~quick reload router~~'~~, [[DCERouter]] will automatically add Media Scenarios for each room for whatever media devices are in there~~. ~~But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in~~ '~~Using LinuxMCE with an Orbiter~~'. ~~Next add [[Events]], in other words, when something happens (a motion detector~~ is ~~tripped~~, ~~the sun sets, etc~~.) you want ~~LinuxMCE to do this (turn on a light). Also set security options~~, ~~like how~~ you ~~want to be notified when something happens~~ in ~~the house~~. ~~Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.</p>~~		Currently only option is to enter entries into Pluto_main database, table PageSetup. There you'll find other entries already, go to the end and add yours (but be careful not to break anything and also save your changes, cause they can probably lost in migration or updates - not sure)...

			Anyway for simple test I've created two entries: "Tinia" as main menu entry (after Telecom) and then subentry for phpmyadmin that I frequently use. If I highlight only important fields, my entries look like this :

			'''PK_PageSetup FK_..._Parent Website OrderNum FK_Package Description pageURL showInTopMenu'''
			190 NULL 1 70 NULL Tinia 1
			191 190 1 0 NULL PHPMyAdmin http://192.168.0.1/phpmyadmin/ 1

			If FK_PageSetup_Parent is empty, then you'll have main entry on green main bar. If you want subentry, then you just specify PK_PageSetup of your parent in FK_PageSetup_Parent. You can also add URL
	[[Category:Tutorials]]		[[Category:Tutorials]]

Bulek at 10:40, 4 April 2008

2008-04-04T10:40:47Z

←Older revision		Revision as of 10:40, 4 April 2008
Line 25:		Line 25:

	===Scenarios, Events & Security===		===Scenarios, Events & Security===

			<p>In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living room to view a camera. When you do a 'quick reload router', [[DCERouter]] will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using LinuxMCE with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want LinuxMCE to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.</p>

			===Adding custom entries in LinuxMCE-Admin menus===

	<p>In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living room to view a camera. When you do a 'quick reload router', [[DCERouter]] will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using LinuxMCE with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want LinuxMCE to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.</p>		<p>In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living room to view a camera. When you do a 'quick reload router', [[DCERouter]] will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using LinuxMCE with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want LinuxMCE to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.</p>
	[[Category:Tutorials]]		[[Category:Tutorials]]

Rwilson131 at 00:38, 31 August 2007

2007-08-31T00:38:48Z

Juliet at 12:08, 16 March 2007

2007-03-16T12:08:21Z

New page

You need a web browser to configure your LinuxMCE system using the built-in [[LinuxMCE Admin Website]]
Since the Hybrid + Media Directors have one built in, you can choose Advanced > Computing and click the "LinuxMCE Admin" website to bring it up directly on the Hybrid. Or, from any web browser in your home, go to the URL: http://myip/LinuxMCE_admin where myip is the IP address of the
Core/Hybrid. To find the ip of your Core/Hybrid, choose Advanced, Advanced Options and it's shown at the top.

Login then click [[Wizard Pages|Wizard]]. You will see the following screen.
[[Image:Wizard.jpg|200px]]

Follow each of the links in the left panel to choose your basic settings, add the devices, scenarios, and event handlers.
Here's an example for setting up an ultra low-cost smart home setup based on X10. The equipment we mention will cost under $1,000, although the procedure is exactly the same with a $100,000 high-end based on Lutron, Vantage, EIB, etc. So, please read the example regardless of your system type, so you understand the techniques.
EXAMPLE: Adding other devicesExample:
You have 2 gc100's which give you Infrared control of you're a/v equipment, extra serial ports to plug other stuff into, ttl inputs and relays. You have some TVs and stereos to control, and also a CM11A module to control X10 devices, plus some X10 lights and thermostats.
You will plug the CM11A into one of the rs232 serial ports on the gc100. You also have an alarm panel with a serial interface, some squeeze box audio players, and some network cameras.

After specifying [[Basic Info]] on the first couple wizard pages, like family members and rooms, you get to [[Interfaces]].
Here you add all the devices that are used to interface with, or control other devices. So, the gc100 is an interface device, but the TVs and stereos it controls are on the a/v page. The CM11A, Vantage, Lutron, etc. are also interfaces, the lights, blinds, drapes, etc. they control are on the [[Lights|lighting page]]. The alarm panel is an interface, the motion, glass break, smoke alarms, etc., are on the [[Security]].
Some home automation devices do not require an interface, some do. An IP-based camera does not require an interface device-add it directly to [[Surveillance Cameras]].
Analog cameras do need some sort of interface device, like a camera capture board, which you must first add to the interfaces page. Add the interface devices first on the interface page, and then the devices they control on the respective page. If you want to add EIB lights (on the lights page), you won't be allowed to do that until you first add the EIB interface on the interfaces page, because an EIB light cannot be used without an interface. If you add interfaces for both an EIB Lighting system, and an X10 lighting system, then on the lighting page you will be able to add both types of lights, and the 'Controlled Via' field will show you what interface is being used.
Back to our example: Plug one of your gc100's into the network, and click the 'add gc100' button on the interface page. gc100's are treated special because they are IP-based, but their network configuration is a bit different and does not allow them to be plug-and-play. Once you got the message that it was found and configured, click on the Interfaces page again--now you'll see it there. Maybe give it a descriptive name so you can remember which is which. Now plug in the 2nd gc100, and repeat.
Next choose 'Add Devices' and add the CM11A. Like all RS232 devices, it is not plug and play, you must add it manually. Repeat for the alarm panel. In both cases, the Controlled Via devices is the Core, since that's where the software drivers will be run. But, when you go to choose the port, it only shows the Core's internal serial ports, and you want to plug it into one of the ports on the gc100. So, click 'Wizard', 'Restart' and 'quick reload router'. That causes the DCE Router to reload the list of devices in the house so it sees the new gc100's you added, and adds the ports. Refresh the Interfaces page, and now you can choose the gc100 ports for the CM11A and alarm panel.Next, add your TVs and stereos on the [[AV Devices]] and indicate how they are connected (which AV inputs). If your model is not in the database you will need to add it. If the I/R codes for your device aren't listed or don't work, you will click the A/V properties button and either [[Learning/typing my own code|learn them]] using the gc100's learner (plug it into serial port 1 and click 'learn'), or [[Learning/typing my own code|copy+paste the I/R codes in pronto format]] from a source like www.remotecentral.com. Your devices and I/R codes will automatically be sent to LinuxMCE and added to the master database for other users unless you uncheck the box. In the 'controlled via' choose whichever one of the gc100's has the infrared emitter attached for that device. Turn your Squeeze Boxes on, set the network to DHCP, and plug them in. LinuxMCE will automatically recognize them and configure them. You will see a confirmation message and be asked to pick the room they're in. Refresh the A/V page to see the Squeeze Boxes and indicate how you connect them to your stereo system.

On the [[Media Directors]] and [[Orbiters]] page, be sure your settings are correct. Then on the [[Lights]] and [[Climate]] pages, add all your X10 lights/thermostats. The 'Controlled Via' is the cm11A device. On the security page, add all your motion detectors, smoke alarms, etc. The 'Controlled Via' is the alarm panel.
On the [[Floorplans]], drag and drop your devices on the maps you upload. You'll need to do a 'regen orbiter' followed by a 'quick reload router' before you can use the floorplans.

Now let's test the devices. Do another 'quick reload router' so DCERouter sees these new devices. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing [[Devices]] from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, go to 'Advanced', 'Logs' and check the logs for the interface, the CM11A in this case.

===Scenarios, Events & Security===

In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living room to view a camera. When you do a 'quick reload router', DCERouter will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using LinuxMCE with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want LinuxMCE to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.

←Older revision		Revision as of 00:38, 31 August 2007
Line 7:		Line 7:

	<p>Follow each of the links in the left panel to choose your basic settings, add the devices, scenarios, and event handlers.		<p>Follow each of the links in the left panel to choose your basic settings, add the devices, scenarios, and event handlers.
	Here's an example for setting up an ultra low-cost smart home setup based on X10. The equipment we mention will cost under $1,000, although the procedure is exactly the same with a $100,000 high-end based on Lutron, Vantage, EIB, etc. So, please read the example regardless of your system type, so you understand the techniques.</p>		Here's an example for setting up an ultra low-cost smart home setup based on [[X10]]. The equipment we mention will cost under $1,000, although the procedure is exactly the same with a $100,000 high-end based on [[Lutron]], [[Vantage]], [[EIB]], etc. So, please read the example regardless of your system type, so you understand the techniques.</p>
	<p><b>EXAMPLE: Adding other devices</b></p><p>Example:		<p><b>EXAMPLE: Adding other devices</b></p><p>Example:
	You have 2 gc100's which give you Infrared control of you're a/v equipment, extra serial ports to plug other stuff into, ttl inputs and relays. You have some TVs and stereos to control, and also a CM11A module to control X10 devices, plus some X10 lights and thermostats.		You have 2 [[gc100]]'s which give you Infrared control of you're a/v equipment, extra serial ports to plug other stuff into, ttl inputs and relays. You have some TVs and stereos to control, and also a [[CM11A]] module to control [[X10]] devices, plus some [[X10]] lights and [[thermostats]].
	You will plug the CM11A into one of the rs232 serial ports on the gc100. You also have an alarm panel with a serial interface, some squeeze box audio players, and some network cameras.</p>		You will plug the [[CM11A]] into one of the rs232 serial ports on the [[gc100]]. You also have an alarm panel with a serial interface, some squeeze box audio players, and some network cameras.</p>

	<p>After specifying [[Basic Info]] on the first couple wizard pages, like family members and rooms, you get to [[Interfaces]].		<p>After specifying [[Basic Info]] on the first couple wizard pages, like family members and rooms, you get to [[Interfaces]].
	Here you add all the devices that are used to interface with, or control other devices. So, the gc100 is an interface device, but the TVs and stereos it controls are on the a/v page. The CM11A, Vantage, Lutron, etc. are also interfaces, the lights, blinds, drapes, etc. they control are on the [[Lights\|lighting page]]. The alarm panel is an interface, the motion, glass break, smoke alarms, etc., are on the [[Security]].		Here you add all the devices that are used to interface with, or control other devices. So, the [[gc100]] is an interface device, but the TVs and stereos it controls are on the a/v page. The [[CM11A]], [[Vantage]], [[Lutron]], etc. are also interfaces, the lights, blinds, drapes, etc. they control are on the [[Lights]]\|lighting page. The alarm panel is an interface, the motion, glass break, smoke alarms, etc., are on the [[Security]].
	Some home automation devices do not require an interface, some do. An IP-based camera does not require an interface device-add it directly to [[Surveillance Cameras]].		Some home automation devices do not require an interface, some do. An IP-based camera does not require an interface device-add it directly to [[Surveillance Cameras]].
	Analog cameras do need some sort of interface device, like a camera capture board, which you must first add to the interfaces page. Add the interface devices first on the interface page, and then the devices they control on the respective page. If you want to add EIB lights (on the lights page), you won't be allowed to do that until you first add the EIB interface on the interfaces page, because an EIB light cannot be used without an interface. If you add interfaces for both an EIB Lighting system, and an X10 lighting system, then on the lighting page you will be able to add both types of lights, and the 'Controlled Via' field will show you what interface is being used.</p>		Analog cameras do need some sort of interface device, like a camera capture board, which you must first add to the interfaces page. Add the interface devices first on the interface page, and then the devices they control on the respective page. If you want to add [[EIB]] lights (on the lights page), you won't be allowed to do that until you first add the [[EIB]] interface on the interfaces page, because an [[EIB]] light cannot be used without an interface. If you add interfaces for both an [[EIB]] Lighting system, and an [[X10]] lighting system, then on the lighting page you will be able to add both types of lights, and the 'Controlled Via' field will show you what interface is being used.</p>
	<p>Back to our example: Plug one of your gc100's into the network, and click the 'add gc100' button on the interface page. gc100's are treated special because they are IP-based, but their network configuration is a bit different and does not allow them to be plug-and-play. Once you got the message that it was found and configured, click on the Interfaces page again--now you'll see it there. Maybe give it a descriptive name so you can remember which is which. Now plug in the 2nd gc100, and repeat.		<p>Back to our example: Plug one of your [[gc100]]'s into the network, and click the 'add gc100' button on the interface page. [[gc100]]'s are treated special because they are IP-based, but their network configuration is a bit different and does not allow them to be plug-and-play. Once you got the message that it was found and configured, click on the Interfaces page again--now you'll see it there. Maybe give it a descriptive name so you can remember which is which. Now plug in the 2nd gc100, and repeat.
	Next choose 'Add Devices' and add the CM11A. Like all RS232 devices, it is not plug and play, you must add it manually. Repeat for the alarm panel. In both cases, the Controlled Via devices is the Core, since that's where the software drivers will be run. But, when you go to choose the port, it only shows the Core's internal serial ports, and you want to plug it into one of the ports on the gc100. So, click 'Wizard', 'Restart' and 'quick reload router'. That causes the DCE Router to reload the list of devices in the house so it sees the new gc100's you added, and adds the ports. Refresh the Interfaces page, and now you can choose the gc100 ports for the CM11A and alarm panel.</p><p>Next, add your TVs and stereos on the [[AV Devices]] and indicate how they are connected (which AV inputs). If your model is not in the database you will need to add it. If the I/R codes for your device aren't listed or don't work, you will click the A/V properties button and either [[Learning/typing my own code\|learn them]] using the gc100's learner (plug it into serial port 1 and click 'learn'), or [[Learning/typing my own code\|copy+paste the I/R codes in pronto format]] from a source like www.remotecentral.com. Your devices and I/R codes will automatically be sent to LinuxMCE and added to the master database for other users unless you uncheck the box. In the 'controlled via' choose whichever one of the gc100's has the infrared emitter attached for that device. Turn your Squeeze Boxes on, set the network to DHCP, and plug them in. LinuxMCE will automatically recognize them and configure them. You will see a confirmation message and be asked to pick the room they're in. Refresh the A/V page to see the Squeeze Boxes and indicate how you connect them to your stereo system.</p>		Next choose 'Add Devices' and add the [[CM11A]]. Like all [[RS232]] devices, it is not plug and play, you must add it manually. Repeat for the alarm panel. In both cases, the Controlled Via devices is the Core, since that's where the software drivers will be run. But, when you go to choose the port, it only shows the Core's internal serial ports, and you want to plug it into one of the ports on the gc100. So, click '[[Wizard]]', 'Restart' and 'quick reload router'. That causes the [[DCE Router]] to reload the list of devices in the house so it sees the new gc100's you added, and adds the ports. Refresh the Interfaces page, and now you can choose the gc100 ports for the CM11A and alarm panel.</p><p>Next, add your TVs and stereos on the [[AV Devices]] and indicate how they are connected (which AV inputs). If your model is not in the database you will need to add it. If the I/R codes for your device aren't listed or don't work, you will click the A/V properties button and either [[Learning/typing my own code\|learn them]] using the gc100's learner (plug it into serial port 1 and click 'learn'), or [[Learning/typing my own code\|copy+paste the I/R codes in pronto format]] from a source like www.remotecentral.com. Your devices and I/R codes will automatically be sent to LinuxMCE and added to the master database for other users unless you uncheck the box. In the 'controlled via' choose whichever one of the gc100's has the infrared emitter attached for that device. Turn your Squeeze Boxes on, set the network to [[DHCP]], and plug them in. LinuxMCE will automatically recognize them and configure them. You will see a confirmation message and be asked to pick the room they're in. Refresh the A/V page to see the Squeeze Boxes and indicate how you connect them to your stereo system.</p>

	<p>On the [[Media Directors]] and [[Orbiters]] page, be sure your settings are correct. Then on the [[Lights]] and [[Climate]] pages, add all your X10 lights/thermostats. The 'Controlled Via' is the ~~cm11A~~ device. On the security page, add all your motion detectors, smoke alarms, etc. The 'Controlled Via' is the alarm panel.		<p>On the [[Media Directors]] and [[Orbiters]] page, be sure your settings are correct. Then on the [[Lights]] and [[Climate]] pages, add all your [[X10]] lights/thermostats. The 'Controlled Via' is the [[CM11A]] device. On the security page, add all your motion detectors, smoke alarms, etc. The 'Controlled Via' is the alarm panel.
	On the [[Floorplans]], drag and drop your devices on the maps you upload. You'll need to do a 'regen orbiter' followed by a 'quick reload router' before you can use the floorplans.</p>		On the [[Floorplans]], drag and drop your devices on the maps you upload. You'll need to do a 'regen orbiter' followed by a 'quick reload router' before you can use the floorplans.</p>

	<p>Now let's test the devices. Do another 'quick reload router' so DCERouter sees these new devices. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing [[Devices]] from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, go to 'Advanced', 'Logs' and check the logs for the interface, the CM11A in this case.</p>		<p>Now let's test the devices. Do another 'quick reload router' so [[DCERouter]] sees these new devices. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing [[Devices]] from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, go to 'Advanced', 'Logs' and check the logs for the interface, the [[CM11A]] in this case.</p>

	===Scenarios, Events & Security===		===Scenarios, Events & Security===

	<p>In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living room to view a camera. When you do a 'quick reload router', DCERouter will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using LinuxMCE with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want LinuxMCE to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.</p>		<p>In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living room to view a camera. When you do a 'quick reload router', [[DCERouter]] will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using LinuxMCE with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want LinuxMCE to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.</p>
			[[Category:Tutorials]]