7 | | This Plugin allows the SQBlaster to show up as an IR Device under MiOS, and any existing IR Remote devices can be re-attached to use the SQBlaster instead of the prior USB-UIRT or GC-100 IR interfaces. |
| 7 | This Plugin allows the SQBlaster to show up as an ''IR Transmitter'' under MiOS, and any existing ''IR Devices'' can be re-attached to use the SQBlaster instead of the prior USB-UIRT or GC-100 IR interfaces. It also goes on to show how these ''IR Devices'' can be sourced from the MiOS IR Catalog, hand-built, or extracted from SQRemote files. |
| 8 | |
| 9 | In MiOS, the Remote Control functions are broken into a few different components. Each of these components is required to Control "something" over IR from a MiOS (Vera) unit. |
| 10 | |
| 11 | Roughly, these are: |
| 12 | |
| 13 | a. A physical device that can accept ''Pronto Codes'' and Transmit, or ''Blast'', IR signals.\\ |
| 14 | We'll call this the ''IR Transmitter''. An example is the SQBlaster device from !SquareConnect, other examples include the GC100, iTach and USB-UIRT devices. |
| 15 | |
| 16 | b. A MiOS Plugin for the ''IR Transmitter''.\\ |
| 17 | This ''Plugin'' will adapt calls, from a MiOS defined interface, and translate them into calls that the ''IR Transmitter'' requires in order to deliver the ''Pronto Codes'' as IR signals. |
| 18 | |
| 19 | c. A MiOS ''IR Transmitter Device'', created for the SQBlaster Plugin from (b), and configured to use the correct IP Address of the SQBlaster\\ |
| 20 | |
| 21 | d. A MiOS ''IR Plugin'' for each piece of AV Gear you want to Control.\\ |
| 22 | Each ''IR Device'', such as a TV/Receiver/AirConditioning etc, has a specific set of ''actions'' that can be performed, as well as a specific set of ''Pronto Codes'' that need to be delivered for each of these actions. |
| 23 | In MiOS, these need to be represented as another Plugin, and related Device, that can be called upon to trigger the sending of a specific IR Code for each of it's actions. |
| 24 | These can be sourced from: |
| 25 | 1. the MiOS "Remote Control" Catalog ''OR;'' |
| 26 | 2. hand built ''OR;'' |
| 27 | 3. derived from the [http://box.net box.net] Backup of your SQRemote configuration |
| 28 | |
| 29 | The process for hand building these is outlined here: |
| 30 | Building [http://forum.micasaverde.com/index.php?topic=4542.msg24677#msg24677 MiOS ProntoCode IR] by hand |
| 31 | |
| 32 | The process for transforming existing SQBlaster/SQRemote `devnnnnnnnn.xml` files, from a Backup on Box.net, into MiOS Plugin file(s) outlined here: |
| 33 | [http://forum.micasaverde.com/index.php?topic=4639.msg29906#msg29906 MiOS IR Device Extraction from SQRemote Devices] |
| 34 | |
| 35 | e. A MiOS ''IR Device'', created for the ''IR Plugin'' from (d)\\ |
| 36 | This MiOS''IR Device'' must be associated, in the MiOS UI, to use the MiOS ''IR Transmitter'' from (c). |
| 37 | |
| 38 | NOTE: In MiOS Beta release 1.1.1183, the IR-Device mechanism was broken, along with the ability to associate an IR Device with it's ''IR Transmitter''. This has been fixed in the subsequent Beta builds. |
| 39 | |
| 40 | |