Real world example
| This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto. |
Here's an example for setting up a 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 devices
Example: You have 2 http://www.globalcache.com 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 tv's and stereo's 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. 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 with 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. This means with Pluto all devices, like lights, are merged together regardless of their type. When you create a lighting scenario, you will see all your lights in one checklist, even if some are X10 and others are Lutron.
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 so you have to click that button to tell Pluto you plugged a new one in, causing Pluto to look for it. Once you got the message that it was found and configured, click on the Interfaces page again to refresh it--now you'll see it there. Maybe give it a descriptive name so you can remember which is which, and click the 'save/update' button. 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. The extra serial ports on the gc100 will appear as serial ports on the Core. 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 to the Core. Click again on the link for the Interfaces page to refresh it, and now you can choose the gc100 ports for the CM11A and alarm panel. Note the serial ports appear as [gc100 device #]_[port on gc100]. The gc100 device # is shown on the interfaces page, and ports are numbered with the first serial port being 0.
Next, add your tv's and stereo's on the AV Devices and indicate how they are connected (which AV inputs). If your Sony VCR's audio output is connected to the JVC Receiver, and the video output to the Samsung Plasma, you will add all 3 devices, then click the 'Edit' link next to the VCR's 'A: V:'. Choose the Receiver as the Audio Device, then choose the input on the Receiver the VCR is connected to. If, after choose the receiver, you see that the Receiver's inputs are not shown, click the 'a/v properties' for the Receiver. You can also click the 'Connection Wizard' link to make the connections visually, one room at a time.
If your model is not in the database you will need to add it. After adding it, click the 'a/v properties' button to specify information about the device, and the 'ir/gsd codes' button to specify infrared codes or the commands if its a 'Generic Serial Device', like something controlled with RS232 or Ethernet. If the I/R codes for your device aren't listed or don't work, you will click the i/r button and either Learning/typing my own code from a source like www.remotecentral.com. Your devices and I/R codes will automatically be sent to Pluto and added to the master database for other users unless you uncheck the box. In the 'controlled via' chose whichever one of the gc100's has the infrared emitter attached for that device.
Turn in and plug on your Squeeze Boxes and accept the default 'DHCP network' setting.. Pluto will automatically recognize them and configure them. You will see a confirmation message on all the orbiters 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, 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. When DCERouter sees the new SqueezeBoxes, it will automatically create some Media Scenarios for you to listen to music on them. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing Advanced Pages Devices from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, click the 'Follow Log' link to display a popup showing activity for that device. Now try again and see if the device is reporting any errors in the log. You can select 'Advanced', 'Devices', select your Core or Hybrid in the tree on the left, and click 'DCERouter'. Then follow DCERouter's log to be DCERouter sees the new CM11 software module and is routing commands to it.
EXAMPLE (cont): Scenarios, Events & Security
In the Scenarios, in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want Pluto 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'.
