LinuxMCE - User contributions [en]

User:KlfJoat/Front doorbell

2010-12-12T05:43:34Z

Klfjoat: New page: Because, seriously, how cool would it be to do a Ferris Bueller? ;-)

Because, seriously, how cool would it be to do a Ferris Bueller? ;-)

User:KlfJoat

2010-12-12T05:43:07Z

Klfjoat: /* Objectives */

A guy interested in setting up LinuxMCE and documenting it. Whether I am successful in either of those endeavors remains to be seen. *grins*

I am an IT security expert in another life. Ethical hacking, audits, consulting, infosec, regulatory compliance, that sort of thing.

I am quite familiar with Linux. I've run Linux as my primary home OS since April 2005. I switched over at work in 2007 after realizing that Cygwin wouldn't give me the same level of power. I've run RedHat, Fedora, Gentoo, and dabbled with Suse. I primarily run Ubuntu for desktop OS's. Trying out Ubuntu Server on a new hosted Xen VPS I've got.

Changed jobs recently so I'm back running WinXP as a primary work OS... what a jarring transition! After years of ease, going back to this piece of junk is giving me nightmares. What do you mean the window doesn't snap to the outline of the screen?!?!?!

Anyway, not a programmer, but I'm not a n00b either. I've done enough sysadmin, server, networking, desktop, and hacking work that I can find my way around if I need to. And I understand the basics.

I hope to help with feedback, testing, and system integration tasks.

== Vision ==
''The endgame.''

I see myself having a whole-house LMCE setup. That means a seamless TV/media experience in the kitchen, den, bedroom, outdoors, and possibly more. Intelligent VoIP allowing calls between rooms, separate voicemail boxes, and call forwarding. All components are using as little power as possible. All components integrate seamlessly with the system. It is expansion-ready, to allow me to add in cable/satellite/netflix/other boxes. The system should impress, not because it's flashy and in-your-face, but because of its low-key, seamless integration with the house.

== Goals ==
''How to reach the vision.''

I want it all. Really. The convergence aspects of LMCE appeal to me '''greatly'''. To that end, my goals are:
* I want whole-house structured cabling
* I want to be able to watch good TV shows at any time.
* I want surround sound.
* I don't want to futz with discs more than twice (load into system, and put away in CD/DVD binder).
* I want to go to sleep at night, knowing that my doors are locked, the alarm is armed, and my motorized gate is closed.
* I want to be able to check the security of my home from anywhere.
* I want to be able to "down-shift" my home into lower energy consumption when I am traveling.
* I want devices that will interface directly with LMCE as possible.
* I want to be able to show artwork.

== Objectives ==
''To meet the goals.''

* [[/Structured cabling closet]]
* [[/Structured wiring]]
* [[/Alarm system]] installed
* [[/Media network]]
** Wireless-N
** Gig-E switch
* [[/LinuxMCE Core]]
* Analog + Digital [[/Video capture|video capture]]
* MD for [[/Den|den]] with DVD drive
* MD for [[/Kitchen|kitchen]] (recipe program a plus!)
* MD for the [[/Bedroom|bedroom]]
* [[/Outdoor speakers]] (+MD?)
* Controllable, programmable [[/Thermostat|thermostat]]
* [[/VoIP]]
* Native orbiters
* Follow me
* [[/Security cameras]]
* [[/Door locks]]
* [[/Motorized gate control]]
* [[/Front doorbell]]

== Discussions ==
* [[/Considerations|My Considerations]]

== External Links to Review ==
* http://www.cocoontech.com/portal
* http://www.homeseer.com

== My Forum Posts ==
* [http://forum.linuxmce.org/index.php?topic=10959.0 n00b Q's - HD partitions/mounts & racks]

Orbiters

2009-11-16T18:46:48Z

Klfjoat: /* Types of Orbiters */ Wikified link to orbiter category (hardware list)

{| align="right"
| __TOC__
|}
[[Category: Orbiters]]
[[Category: Admin Website]]
[[Image:Orbiters.jpg|thumb|250px|Orbiters Page Admin Website]]The '''Orbiters''' are the devices used to communicate/interface with LinuxMCE at the user level. The Orbiter devices display the standardized Orbiter User Interface (UI) from which users control all user-aspects and functionality of LinuxMCE. Media Directors have their own on-screen Orbiter UI. 

An Orbiter can be a laptop, a Blackberry, or even a Bluetooth mobile phone.

The Orbiter UI can be controlled via a touch-screen interface, a handheld remote control (such as a Windows MCE remote control), or even a universal infrared remote control (connected by [[USB UIRT|USB-UIRT]]).

For an Orbiter device to connect, it must either have a connection to a Media Director through an input port, or it must wirelessly connect to the home automation/multimedia LAN through a wireless access point (or wireless router with the DHCP turned off). The Wireless Access Point/Router must obviously be connected to the Core server.

While you can administer the LinuxMCE system through a Media Director (through its own on-screen Orbiter User Interface), you can also control the system from many other Orbiter devices as well.

==Types of Orbiters==
See [[:Category:Orbiters|the orbiter hardware list]] for a list of devices that have been used as Orbiters.

Many Orbiters have relatively slow processors (like PDA's and mobile phones) and may be running on slow Wi-Fi connections. Therefore, Orbiters do not retrieve the large, full-size graphics that are available directly to Media Directors. This would require scaling them, redrawing the text, and re-rendering the graphics on the fly for each Orbiter, a processor-intensive operation.

Instead, all the graphics on the Orbiters are pre-scaled and pre-rendered by a software module on the Core called "[[Orbiter Generator|OrbiterGen]]". If you add new scenarios or devices or change floorplans or skins, you won't see them immediately on the Orbiter. The [[LinuxMCE Admin Website]]-->Advanced-->[[Orbiter Generator|Regenerate this Orbiter]] option is run and a wait of about 60 seconds is required while OrbiterGen renders new graphics, following which the Orbiter will be reloaded.

===Web Orbiter===

A [[Web Orbiter]] refers to any laptop (or other PC) on the LinuxMCE system which uses a standard web browser interface to display the Orbiter User Interface. The laptop or PC becomes a virtual remote control when used in this way.

====Media Director Orbiter====
[[Image:Main-menu.jpg|200px|thumb|Web Orbiter / Main Orbiter Screen (UI1)]]
All Media Directors run an on-screen Orbiter, like the one to the right. The on-screen Orbiter is controlled by the keyboard/mouse attached to the Media Director, or by a connected infrared, USB, or Bluetooth remote control. The Orbiter software can be run runs in Linux, Windows and Windows CE, and can also be run on webpads and PDAs.

In the lower right corner of the main Orbiter screen are the [[Who Am I, Where Am I|'who']] and [[Who Am I, Where Am I|'where']] buttons. This indicates the current user of the Orbiter and which room he or she currently is in (or wishes to control).

You can manually select your desired user and location. Your "location" need not be your actual physical location. For example, even if you were using the on-screen Orbiter for the Media Director in the Living Room, you could change your "location" to the Bedroom. You could then control devices as if you were in the Bedroom. Normally you wouldn't change the location for a Media Director's on-screen Orbiter (since that device stays in a fixed location), but you might change locations frequently if you were to use a wireless web pad or PDA.
[[Image:Litscen.jpg|200px|thumb|Lighting Scenario Page LinuxMCE Admin Website]]
The icons on the left all lead to [[maps]], or floorplans, of your house. These show the lighting, media, climate, telecom and security [[scenario]] categories for each room. Next to each floorplan icon is listed the scenarios for that category and room. (You create the scenarios for each room in the scenarios section of the [[LinuxMCE Admin Website]].) For example, in the Living Room you could create a lighting scenario called 'entertaining guests' that would set the light levels, play some background music, unlock the door, etc.

===Mobile Orbiters===

The mobile orbiter works pretty much like a regular orbiter. The difference is that you don't usually need to worry about the "who" and "where" buttons. The "who" is determined when you chose to install the software. The family member who installs it is assumed to always be the user. The "where" is automatic - whenever you come within range of a Media Director that can recognize the mobile orbiter, it will automatically select itself as the correct location. (Nevertheless, you are still able to manually select a different location, if you want to control a location other than the one you are in).

Since a mobile phone's display is smaller, only selected scenarios can be shown. You must choose the scenario category from the main menu, such as "lighting", and then choose the specific scenario from the sub menu that appears. You can toggle the option for 'follow-me' mode, indicated with a red F. If you hold down the 2 button, a red F will appear for media. As you move around the house, your media will follow you. All 5 categories have follow-me.

Unless you have turned off the "Auto Detect new Bluetooth Phones" option on the Media Director, compatible Bluetooth Mobile phones will automatically be detected whenever they are within range of a Media Director. Be sure you have added the family member to whom the phone belongs on the [[LinuxMCE Admin Website]] first.

A message will appear on all Orbiters (you may need to turn on the TV to see the Media Director's on-screen Orbiter) asking if there is a new mobile phone, and if so, to whom it belongs. If you choose to install the software, the phone will beep. Just hit 'yes' to accept the software, and accept the default prompts.

=====Telephone-based Orbiter devices=====
Several mobile phones can be made to work as mobile orbiters.

*[[Cisco 7970]]
*Symbian Bluetooth phone
**On the phone go to Menu-->Tools-->Manager.
**Hit the left button, choose settings, and set "Software installation" to 'on'.
**Set the "online certificate check" to 'off'.
**On the phone: Menu-->Connect-->Bluetooth-->turn Bluetooth on-->make your phone visible (public).
**Go near a Media Director with a Bluetooth dongle. Within 30 seconds or so you will see a message on any nearby Orbiter that a new phone is detected. Select the phone's owner. The software will be sent automatically to the phone as a message in the phone's inbox. Accept the default installation options. The phone will update its own software.
** If the software gets deleted and you want the Media Director to resend it:
*** Turn the phone off.
*** Go to '''[[LinuxMCE Admin Website]]-->Advanced-->[[Devices]]'''
**** Select the Orbiter off the device list on the left hand of screen
**** Once the device information is loaded in the main section of the device information page check the checkbox for "Reconfigure Device".
*** Turn the phone back on. The software should be resent.
* [[Java Mobile Orbiter]]

===Windows Laptops or Windows CE Webpads and PDAs===
[[Image:Downloadfiles.JPG|frame|right|100px|Download Page for Admin Site]]

*A laptop or a device with a web browser can function as a [[Web Orbiter|Web Orbiter]].
*Other devices can also be set up to work as an Orbiter on a Windows system by following the setup instructions [[Control LinuxMCE using a Windows device as an Orbiter|here]].

==Orbiter Setup==

===Setting up an Orbiter from the [[LinuxMCE_Admin_Website|LinuxMCE administration screen]]===
Here you add all the Orbiters you want to use in your house, no matter what type. This includes the Mobile Orbiters (e.g. mobile phones), the regular Orbiters (e.g. wireless webpads and tablet PCs), Orbiters you want to run on a normal PC, as well as the on-screen Orbiter displays (every Media Director displays an Orbiter on screen). All Orbiters connected to the system will appear on this page.

*Room: this is the room where the orbiter is normally kept. For mobile orbiters this selection isn't important since you carry them everywhere. For regular orbiters, the room is choosen by manual selection.

*Leave Monitor on for OSD: OSD (On-screen display) refers to an Orbiter that runs on a Media Director and is controlled by the keyboard/mouse, or by an infrared, USB, or Bluetooth remote control connected to the Media Director. When this option is checked, the TV will not shut off when media is finished playing, so that the Orbiter can then be displayed. The TV turns off only when the screen saver starts, or when you select Power-->Turn off display.

:If you always control the Media Director using an Orbiter such as a web pad or mobile phone, leave this option unchecked. In this configuration, the TV will come on only when you're playing media or watching TV, and will turn off when you're done.

*This device uses a Wi-Fi connection: This option is useful for webpads and PDAs with a Wi-Fi signal. Since Wi-Fi is somewhat unreliable, the Core and Orbiter will constantly 'ping' each other to make sure the connection is strong enough. The Orbiter software will exit whenever the Orbiter goes out of range.

*No Effects: Many screens have special effects, such as animated buttons, fades, and so on. If the Orbiter has a slow processor, this may slow down response time. This option will disable any special effects on the Orbiter so it will run as fast as possible.

*Language: All the text on the screen will appear in the selected language (as much as possible).

:NOTE: You can create your own menus and translate screens into other languages using [[Designer]].

*Size: Choose the screen size you want. If this is an on-screen Orbiter on a Media Director), this will also set the Media Director's screen resolution.

*Skin: There are several skins (motifs) from which to choose: 'Wood', 'Marble', etc.
*User: This is the person who normally uses this Orbiter.
*Quick Regen: To make the orbiters respond quickly, all images are pre-rendered. The User interface is "built" by the [[Orbiter Generator]] program. This option triggers the Orbiter Generator to re-generate the user interface for this orbiter. It will only regenerate screens that appear to have changed.
*Full Regen: This will cause Orbiter Generator to re-generate every screen on the Orbiter.
*Reduce image size by %: This will cause Orbiter Generator to add some padding to the screens. This is useful if the screen margins are being displayed outside of the TV screen.
:Developer info: although it may sound intuitive that the corresponding DeviceData is also called "Reduce image size by %", it is in fact called "Spacing". The PK_DeviceData for it is 150. The text "Reduce image size by %" comes from the DeviceTemplate_DeviceData table and it's the meaning of the device data in that specific device context
Offset: This causes the Orbiter to do backflips while reciting a poem backwards. (Just kidding. If you know what it does, please edit this section.)

==Change the look and feel of the Orbiter==

On the '''[[LinuxMCE Admin Website]]-->Wizard-->Devices-->[[Orbiters]]''' page you can change the look and feel of the Orbiters in several ways.

*[[Create my own skins or GUI for LinuxMCE|Create your own skin or user interface]]

==Using the Mobile Orbiter==
===Every Orbiter has a 'Rooms' button on the main menu===
Using LinuxMCE basically consists of selecting scenarios that you have previously created in the LinuxMCE Admin Website. For example, you may select the 'Good Morning' Lighting Scenario. If you want to watch TV, you will select the 'TV' scenario for that room. Since the scenarios are grouped by room, the Orbiter needs to know what room you are in. The on-screen Orbiter that runs on a Media Director will always default to the room in which it is located. You can manually specify the default room for other Orbiters, like webpads, on the Orbiters page in the LinuxMCE Admin Website. By default, mobile phone Orbiters 'follow you': whenever you enter a room with a Media Director that has a Bluetooth dongle, your phone will detect it and will switch to that room, showing you that room's scenarios. However, no matter what type of Orbiter you use, there will always be a 'rooms' button on the main menu showing the room, which can always be changed.

===Every Orbiter has a 'User' button on the main menu, except mobile phones===
With a mobile phone Orbiter, you don't need to tell LinuxMCE who is using the Orbiter. The owner of the mobile phone is initially specified on the LinuxMCE Admin Website's Orbiter page and does not change. But with other Orbiters, which may be shared by the whole family, there will be a 'user' button that lets you select who is currently using the Orbiter. This won't affect the [[scenarios]] -- those are the same for everyone. But it does affect some other things. For example, when browsing media, only the current user's private media is shown. Also, other things like speed dials, phone books, and so on, can be affected.

===Selecting a scenario from the phone's main menu===
On the mobile phones, the screen is quite small, so rather than showing you all the scenarios for a room, the phone normally just shows the categories of scenarios: 'Lighting', 'Media', 'Climate', 'Security', 'Telecom', 'Other'. Select a category, then select the scenario underneath it. The 'c' button always takes you back to the main menu. The red 'off' button stops whatever media is playing. And the 'menu' button hides Orbiter so you can use the phone as a normal phone again. To show the Orbiter again, hold the menu button until a strip of currently running programs appears, and chose 'LinuxMCE MO'. If the Orbiter isn't running, press the menu button, and choose 'LinuxMCE MO' from the menu. When you do, the Orbiter won't appear instantly--it will only appear when a Media Director is in proximity and is able to connect to the phone and talk to the LinuxMCE MO software. This can take around 15 seconds. While using the Orbiter, all the other keys have different functions depending on what you're doing. A brief legend is usually shown on the screen, and you can hold down the 'c' button for help.

===Selecting a scenario from another Orbiter's main menu with touch or mouse===
From the '''[[LinuxMCE Admin Website]]-->Wizard-->Devices-->[[Orbiters]]''' page, you can select a 'Skin'. This is the aesthetics (or motif): Wood, Marble, Modern, Classic, etc. You can also select the 'Main Menu', which determines how the user interface behaves.

If you change the 'Main Menu' interface, your Orbiter may look different from other Orbiters, and it may not display all the scenarios on the screen at the same time. In this case you may first have to choose a category, like you do with the mobile phones.

===Selecting a scenario with a keyboard's arrow keys, or an infrared remote===
When you use an on-screen Orbiter on a Media Director, you can either use the number keys or the up/down/left/right/enter keys on the keyboard (or an infrared remote control) to select a scenario.

===Quick tip===
No matter what the user interface looks like, and no matter whether you use the phone, keyboard, or infrared remote, the categories are always numbered as follows:
*1=Lighting
*2=Media
*3=Climate
*4=Telecom
*5=Security
*6=Misc

Within each category, the scenarios are numbered the same, and in the same order, for all Orbiters. For example, the 2nd media scenario is nearly always TV. Whether from a mobile phone, or using an infrared remote or keyboard for an on-screen Orbiter, 22 turns on the TV (2 for Media, 2 for TV). Also, when creating lighting scenarios, LinuxMCE encourages you to make the first lighting scenario the 'default on' and the second the 'default off'. In any room you can normally can hit 11 on any remote to turn the lights on, and 12 to turn them off. If you are consistent in setting up all rooms like this, you will find that you remember the number shortcuts quickly.

==System concepts for Orbiter Implementation==

Here's a simplified [[UML]] for Orbiter (pocketfrog implementation).

[[Integrating custom controls in Orbiter]]

[[Orbiter refactoring - the new design]]

Devel notes:

* [[SDL's TextWrapper and TextSplitter]]
* [[OpenGL implementation]]
* [[Building Orbiter for the Nokia 770]]
* [[Building Orbiter for the Nokia 800]]
* [[Computing screen]]
* [[FileSave screen]]
* [[Child devices]]

USB UIRT

2009-11-16T18:35:15Z

Klfjoat: Wikified section link to demo video

[[Category: Infrared]]

{| align="right"
| __TOC__
|}

[[Image:USB_UIRT.jpg|right]]

* Manufacturer home page: http://www.usbuirt.com/
* Seems to work in [[Video#Equipment_used_in_the_demo|the LinuxMCE 704 demo video]]

==Use in LinuxMCE==
===Connection===
* This device is [[Plug&play]], which means no significant amount of modifications are required to get it to work. Don't forget to [[Quick reload router]] after installation is complete.
* '''MAKE SURE YOU HAVE PERFECTLY GOOD BATTERIES IN YOUR REMOTE, IF YOU ENCOUNTER PROBLEMS RECORDING IR CODES'''

===Adding Remotes===
{{sectstub}}
* Windows XP MC Remote is added automatically.
* Adding different remotes (needs more work)

===Controlling AV Devices===
* [[AV Devices]] is the main page used for making and adjusting control over A/V Equipment.
* Also take a look at [[Infrared Codes]] if you are having problems with the prepopulated Codesets.

== Sales Pitch ==
The USB-UIRT, along with Automation Software such as [[LinuxMCE]], allows your PC to both Receive and Transmit infrared signals -- exactly like those used by the collection of remote controls you've acquired for your TV, VCR, Audio System, etc. The USB-UIRT can:
* Receive signals from the remote controls you already have (allowing your PC to perform actions when the 'Play' button is pressed on your VCR remote, for example)

* 'Learn' from remotes you already have and Transmit a duplicate of these signals from your PC (for example, your PC could automatically turn ON your VCR and tune it to channel 3)

* Use codes available from the Web for other remotes (such as the Philips Pronto) to control all of your equipment with Remote (IR) receivers (including special 'discrete' remote codes your brand-name remote doesn't include!). For example, the USB-UIRT could transmit the discrete 'Input 3' code to your TV to directly switch it to input 3, rather than cycling through all of the inputs.
==Technical Details==
===IR Reception===
* 34-40KHz Frequency Range
* 56KHz IR Receiver Add-On Option*
* UIR-compatible Receiver Mode
* >8 Meter Sensitivity
* IR Wavelength Filtered
* USB Wake-from-Standby Capability
* Built-in wideband IR detector for accurate Learning, including carrier frequency.
* USB Wake-from-Standby Capability

===IR Transmission===

* 20-60KHz Frequency Range
* Two (2) built-in High-Power Emitters
* 1/8" Mini-Jack for External Emitters
* UIRT-compatible Struct and Raw modes
* Extended-length code support in hardware (up to 96burst-pairs)
* Max-length burst code support in driver (up to 2048 burst-pairs)

===Dimensions===

* 2.4"W x 1.5"D x 0.7"H

==Troubleshooting (0710)==

Because of a bug within ftdi_sio.c, the UIRT can't transmit commands....

SethJ has prepared an excellent [[USB-UIRT_x86_Fix|description of the fix]].

==Availability==
USA : http://www.usbuirt.com
Europe : http://www.hightechpad.com/?q=content/usb-uirt-56k-enchanced-version

==See also==
* http://www.mythtv.org/wiki/USB-UIRT
* https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/177166

USB UIRT

2009-11-16T18:27:39Z

Klfjoat: /* See also */ Fixed mythtv wiki link for usb-uirt

[[Category: Infrared]]

{| align="right"
| __TOC__
|}

[[Image:USB_UIRT.jpg|right]]

* Manufacturer home page: http://www.usbuirt.com/
* Seems to work: http://wiki.linuxmce.com/index.php/Video#Equipment_used_in_the_demo
==Use in LinuxMCE==
===Connection===
* This device is [[Plug&play]], which means no significant amount of modifications are required to get it to work. Don't forget to [[Quick reload router]] after installation is complete.
* '''MAKE SURE YOU HAVE PERFECTLY GOOD BATTERIES IN YOUR REMOTE, IF YOU ENCOUNTER PROBLEMS RECORDING IR CODES'''

===Adding Remotes===
{{sectstub}}
* Windows XP MC Remote is added automatically.
* Adding different remotes (needs more work)

===Controlling AV Devices===
* [[AV Devices]] is the main page used for making and adjusting control over A/V Equipment.
* Also take a look at [[Infrared Codes]] if you are having problems with the prepopulated Codesets.

== Sales Pitch ==
The USB-UIRT, along with Automation Software such as [[LinuxMCE]], allows your PC to both Receive and Transmit infrared signals -- exactly like those used by the collection of remote controls you've acquired for your TV, VCR, Audio System, etc. The USB-UIRT can:
* Receive signals from the remote controls you already have (allowing your PC to perform actions when the 'Play' button is pressed on your VCR remote, for example)

* 'Learn' from remotes you already have and Transmit a duplicate of these signals from your PC (for example, your PC could automatically turn ON your VCR and tune it to channel 3)

* Use codes available from the Web for other remotes (such as the Philips Pronto) to control all of your equipment with Remote (IR) receivers (including special 'discrete' remote codes your brand-name remote doesn't include!). For example, the USB-UIRT could transmit the discrete 'Input 3' code to your TV to directly switch it to input 3, rather than cycling through all of the inputs.
==Technical Details==
===IR Reception===
* 34-40KHz Frequency Range
* 56KHz IR Receiver Add-On Option*
* UIR-compatible Receiver Mode
* >8 Meter Sensitivity
* IR Wavelength Filtered
* USB Wake-from-Standby Capability
* Built-in wideband IR detector for accurate Learning, including carrier frequency.
* USB Wake-from-Standby Capability

===IR Transmission===

* 20-60KHz Frequency Range
* Two (2) built-in High-Power Emitters
* 1/8" Mini-Jack for External Emitters
* UIRT-compatible Struct and Raw modes
* Extended-length code support in hardware (up to 96burst-pairs)
* Max-length burst code support in driver (up to 2048 burst-pairs)

===Dimensions===

* 2.4"W x 1.5"D x 0.7"H

==Troubleshooting (0710)==

Because of a bug within ftdi_sio.c, the UIRT can't transmit commands....

SethJ has prepared an excellent [[USB-UIRT_x86_Fix|description of the fix]].

==Availability==
USA : http://www.usbuirt.com
Europe : http://www.hightechpad.com/?q=content/usb-uirt-56k-enchanced-version

==See also==
* http://www.mythtv.org/wiki/USB-UIRT
* https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/177166

USB UIRT

2009-11-16T18:22:27Z

Klfjoat: /* Troubleshooting (0710) */ Changed from external link to wikilink using mediawiki markup; reworded for this change.

[[Category: Infrared]]

{| align="right"
| __TOC__
|}

[[Image:USB_UIRT.jpg|right]]

* Manufacturer home page: http://www.usbuirt.com/
* Seems to work: http://wiki.linuxmce.com/index.php/Video#Equipment_used_in_the_demo
==Use in LinuxMCE==
===Connection===
* This device is [[Plug&play]], which means no significant amount of modifications are required to get it to work. Don't forget to [[Quick reload router]] after installation is complete.
* '''MAKE SURE YOU HAVE PERFECTLY GOOD BATTERIES IN YOUR REMOTE, IF YOU ENCOUNTER PROBLEMS RECORDING IR CODES'''

===Adding Remotes===
{{sectstub}}
* Windows XP MC Remote is added automatically.
* Adding different remotes (needs more work)

===Controlling AV Devices===
* [[AV Devices]] is the main page used for making and adjusting control over A/V Equipment.
* Also take a look at [[Infrared Codes]] if you are having problems with the prepopulated Codesets.

== Sales Pitch ==
The USB-UIRT, along with Automation Software such as [[LinuxMCE]], allows your PC to both Receive and Transmit infrared signals -- exactly like those used by the collection of remote controls you've acquired for your TV, VCR, Audio System, etc. The USB-UIRT can:
* Receive signals from the remote controls you already have (allowing your PC to perform actions when the 'Play' button is pressed on your VCR remote, for example)

* 'Learn' from remotes you already have and Transmit a duplicate of these signals from your PC (for example, your PC could automatically turn ON your VCR and tune it to channel 3)

* Use codes available from the Web for other remotes (such as the Philips Pronto) to control all of your equipment with Remote (IR) receivers (including special 'discrete' remote codes your brand-name remote doesn't include!). For example, the USB-UIRT could transmit the discrete 'Input 3' code to your TV to directly switch it to input 3, rather than cycling through all of the inputs.
==Technical Details==
===IR Reception===
* 34-40KHz Frequency Range
* 56KHz IR Receiver Add-On Option*
* UIR-compatible Receiver Mode
* >8 Meter Sensitivity
* IR Wavelength Filtered
* USB Wake-from-Standby Capability
* Built-in wideband IR detector for accurate Learning, including carrier frequency.
* USB Wake-from-Standby Capability

===IR Transmission===

* 20-60KHz Frequency Range
* Two (2) built-in High-Power Emitters
* 1/8" Mini-Jack for External Emitters
* UIRT-compatible Struct and Raw modes
* Extended-length code support in hardware (up to 96burst-pairs)
* Max-length burst code support in driver (up to 2048 burst-pairs)

===Dimensions===

* 2.4"W x 1.5"D x 0.7"H

==Troubleshooting (0710)==

Because of a bug within ftdi_sio.c, the UIRT can't transmit commands....

SethJ has prepared an excellent [[USB-UIRT_x86_Fix|description of the fix]].

==Availability==
USA : http://www.usbuirt.com
Europe : http://www.hightechpad.com/?q=content/usb-uirt-56k-enchanced-version

==See also==
* http://www.mythtv.org/wiki/index.php/USB-UIRT
* https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/177166

Quick reload router

2009-11-16T18:18:48Z

Klfjoat: /* Reload Router */ Added paragraphs for readability

[[Category: Documentation]]
This command can be accessed in two ways:

*From the [[LinuxMCE Admin Website]]-->Restart-->Quick Reload Reouter
*A button on the LinuxMCE [[Launch Manager]] on the Core server.

The command restarts the [[DCERouter]], which controls all devices in the LinuxMCE system.

===Reload Router===
All devices in LinuxMCE obtain their configuration information from the DCE router, which is the central piece of software on the Core. All devices request a list of the other devices in the home from the router, so they can respond to them appropriately. (For example, an IP camera device might turn on the lights in the room whenever you're viewing the camera. To do so, the IP camera needs to know what lights are in the room.) Typically a device requests this information only when it's starting up. When you connect additional plug and play devices to the system, these new devices generally will work immediately, but their functionality may not be fully enabled within the LinuxMCE system until the DCE router is reloaded.

When the router reloads, it signals all devices on the system to simultaneously reload and re-request the system data. Each existing device can then work with each new device. This process is known as a 'reload'. It generally takes about 10 seconds.

Every time you add or remove devices, or change a device's configuration, you may be asked to do a reload. If you're going to add more devices or make more device changes, you can do the reload once you're done. If you're in the middle of watching a movie or TV, you can postpone the reload, since media players generally stop playing during reloads. Phone calls aren't affected, though, and TV shows being recorded by MythTV in the background are also unaffected.

MD Newbie Pack Slim I

2009-11-16T17:13:38Z

Klfjoat: Corrected category links with mediawiki markup (should not be external)

[[Category: Newbie_Packs]]
[[Category: Media_Directors]]
{| align="right"
| __TOC__
|}

[[Image: Silverstone_Lc19-v1.jpg|thumb|200px|Silverstone LaCasa 19 Case]]

[[Image:MSI_7329.jpg|thumb|200px|MSI Media Live (7329) Motherboard]]

[[Image:FiireChief.jpg|thumb|200px|Fiire Chief Remote Control]]

''Note: Some of the components on this list may not be available outside of Europe. Look [[:Category:Newbie_Packs|here]] for other Media Director examples.''

= Status =
Confirmed working with 0704, 0710b3, 0710b4, 0710RC1

= Features =
* Small HiFi form factor
* Brushed aluminum front
* Clear design
* Plenty of outputs (component, HDMI, ..)
* low power usage
* UI2 capable (reported up to 720p)

= Components =
== Case ==
[[SilverStone LaCasa LC19]]

See [http://www.silverstonetek.com/products/p_spec.php?pno=lc20&area=usa website] for more details. Approx. $140.

== Optical (DVD) drive ==
Pioneer (Bulk) DVR-K06 Slim Slot-In
== CPU ==
AMD BE2400
== Cooling Fan or Heat Sink ==

Silverstone NT07-AM2 Fan
([http://www.silverstonetek.com/products/p_spec.php?pno=nt07-am2&area=usa website])
*For AMD CPU sockets up to 65W power
*Low profile
*Approx. $20 (April 2008).

Available in Europe only:

NORTHQ NQ 3393 Heat sink with fan
([http://www.northq.com/products/coolers/nq3393.html website])

or

Hiper HFC10820C1
([http://www.ciao.de/HiperFlow_HFC_10820_C1__2639455 German website])

== RAM ==
2xDDR2 PC800 1GB
== Motherboard ==
[[MSI Media Live Mainboard]]

See [http://global.msi.com.tw/index.php?func=prodcpusupport&prod_no=1113&maincat_no=134&cat2_no=&cat3_no= website] for details.

== Remote ==
[[Fiire Chief]]

ZWave

2009-11-16T17:03:56Z

Klfjoat: /* Overview */ More properly linked to the ZWave wiki category using the proper mediawiki markup, and linked from a bit better place.

{| align="right"
| __TOC__
|}
[[Category: Hardware| ]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Programmer's Guide]]

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.

Look at the [[:Category:ZWave|Z-Wave Wiki Category]] to see pages for different Z-Wave devices.

The source code is available in LinuxMCE's SVN repository: http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src/ZWave.

== Implementation ==
=== Open version ===
The new open Z-Wave driver will be included in the upcoming 0810 release.

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.

=== New Fiire driver ===
Fiire also provides a new 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.

== Interfaces ==
=== Supported ===
* [[ACT Homepro ZCS000]]
* [[ACT Homepro ZCS010]]
* [[ACT Homepro ZCS101]]
* [[ACT Homepro ZCS201]]
* [[ACT Homepro ZCU000]]
* [[ACT Homepro ZCU010]]
* [[Intermatic HA22]]
* [[Intermatic HA23C]]
* [[Intermatic HA20C]]
* [[MCV_Z-Wave_Dongle|Mi Casa Verde USB + Inclusion Controller in one]]
* [[Seluxit viaSENS Homecontroller]]
* [[Tricklestar 300ZW-US-W]]
* [[Tricklestar 300ZW-EU-W]]
* [[Aeon Labs Z-Wave Interface with built-In Inclusion Remote]]

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

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

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

=== Manual Setup using SIS Mode with the Tricklestar Remote ===
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 include your Tricklestar remote into your 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.

=== 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://192.168.80.1/pluto-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]]).

== PIR (Binary Sensor) support ==

[[ACT Homepro Motion Detector]]

== Z-Wave API documentation ==

[[ZWave API]]

VistaICM

2009-11-16T16:58:26Z

Klfjoat: /* Features */ Formatted what was obvoiusly a bullet list into just that.

[[Category: Security]]

= VistaICM =

== Overview ==

The VistaICM is an alarm panel interface which will allow you to fully integrate panels supported by it with LinuxMCE. It allows both control of the security panel modes, and monitoring of the security panels zones. This means that any sensor connected to the security panel can be used to trigger events with any other device on your LinuxMCE system.

'''Note:''' Please add compatible panels to the security category as you find them.

== Features ==

* Full control over panel modes from LinuxMCE
* LinuxMCE monitors panel mode changes from keypads and acts accordingly
* Zone monitoring
* Trigger events from zone sensors
* Virtually everything that works when using LinuxMCE as your security panel is supported with this interface

== Preparation ==

You need to do a few things to prepare for your integration with LinuxMCE. The first thing you should to is to configure your alarm panel which the VistaICM is connected to for your LinuxMCE pincodes. You will need to refer to your security panel's installer manual for the detailed instructions. You can either set all of your LinuxMCE user's to use the same pincode or if your security panel supports it, you can create a user code for each of your LinuxMCE users.

'''Note:''' To configure the pin code in LinuxMCE go to '''Wizard > Basic Info > Users > Change Pin.'''

You will also want to have a list of your zones with descriptions and sensors connected to each zone prepared. This will make the process of configuring your sensors in LinuxMCE absolutely painless.

== Installation ==

The VistaICM is plug and play with the exception of the fact that you will need to manually configure your zones and sensors after the device has been detected and installed.

To configure your sensors to to '''Wizard > Devices > Security'''
Add a device for each sensor installed on your security panel. Make sure to set the Port/Channel Number of each sensor to the zone they are installed in. You also want to be sure to give each sensor a clear Description and assign it to the appropriate room.

To configure your zones go to '''Wizard > Devices > Security > Security Zones'''
Add a zone for each zone you have and assign the sensors attached to each zone to the zone you just created.

The last part of the installation is to place the sensors on your floorplan.
To do this go to '''Wizard > Devices > Floorplan Wizard''' then select your floorplan and be sure the dropdown is on Security Zone. Now just drag and drop the sensors where they are located on the floorplan.

== Known Issues/Bugs ==

'''FIXED:'''The VistaICM device thread crashes in LinuxMCE randomly, need to do more troubleshooting to finally nail this bug down once and for all.

When the panel is set to Armed - Stay the VistaICM does not send zone trigger information. I emailed In2 Networks about this and received a canned response that seems to indicate it could be a setting in the configuration of my security panel. If anyone has any idea please let me know.

When the security panel is in alarmed state LinuxMCE's mode and the panel's mode can become out of sync until disarmed/armed/disarmed again.