Steven - I would send you some X10 bits to play with but unfortunately they are UK 230V versions
It is a very low cost option to get started - maybe $30 or so - but can be very costly if you get hooked on Home Automation
There will be starter kits but all you need is a lamp dimmer module, an Appliance module, a CM12 computer interface and perhaps a manual 'press button' controller or even an RF linked keypad controller.
The xAP connector for X10 directly uses (attaches to) the CM12U so it then becomes an Ethernet based X10 controller (shareable) . If you are already using HomeSeer with an X10 controller then when you install the xAP plugin it will use the xAP version for X10. There is a much enhanced new HS xAP plugin due imminently.
The xAP support for Nebula TV is great, includes recording etc - and there is also a true xAP TV application for TV listings with 'reminders' etc. Shortly it will have a web interface added too.
One of the great things about xAP is that it is very 'loose' in its coupling - it communicates via UDP and hence you don't get those feedback locks that so often hang applications. xAP information is received by everyone although various filters are applied (and addressing used) to indicate its relevence. A Tivo for example could listen to the modem and watch for Caller ID information to display on the TV screen. Whereas a database lookup application receives the same information and creates a log and also broadcasts back the Callers name which again the Tivo might choose to watch for and display. But if the database application was 'down' for whatever reason nothing hangs, you just lose that bit of the functionality. xAP effectively network enables all your hardware.
So Aaron - taking your wishes in your post (and speaking only from the xAP side) every device in HomeSeer becomes effectively a network device - providing realtime event reporting over Ethernet every time its status changes and also controllable over Ethernet.. It truly distributes the device control. XLobby therefore makes an ideal front end as a display/control panel for these devices. We have our simple control with 'BSC' which is suitable for 90% of real world devices (see above) which also includes a display text field that might provide a button legend if required or even perhaps an html address to a jpeg or more. And you could add more complex schema that you design yourself for example to control the 'whizzo ice cream maker'. Writing xAP connectors for devices is relatively staright forward and there are loads of examples with source code.
Schemas are designed to abstract the hardware from the equation so for example our whole homeaudio (mp3) schema drives a SliMP3 / Squeezebox or an Exstreamer just the same - and could drive WinAMP this way for example. It is a way of managing 'play this track' 'add this to playlist' 'asking what is currently playing' 'raise the volume' etc etc where the backend hardware is hidden. Later when you replace WinAMP with a Squeezebox it all continues working transparently. Some commercial applications eg MCS music already use xAP as their control for this reason.
The synergy with XLobby is great - XLobby gains access to network hardware in a continually expanding area - and once basic xAP support is in place the supported devices just grow and grow. This is not limited to true hardware as all internet based information eg weather , share prices, emails etc can be presented via BSC . XLobby forms the graphic front end for your whole system incoroprating HA - and it will work in conjunction with your favourite logic/script engin eg HomeSeer or whatever. Exactly what it is best at... and it is very good at this !
There are more complex schema that would benefit from specific support eg the 'whole house audio' is designed as a complete system rather than being broken into BSC parts. However HomeSeer can be used with any xAP schema to create devices and these 'devices' can then of course be broken down & presented back by HomeSeer as BSC should you so wish. In this way say the current track playing which was originally contained in the 'whole house audio' schema gets re-presented as a BSC TEXT type.
Loads of potential here...
Kevin