I've attached a beta of the IRTrans plug-in created for HS3 for those experienced users willing to do some testing.
Note: This is a paid plug-in ($39.95) and the beta will expire at the end of September.
This version supports core functionality related to receiving and sending IR commands in HS3 via triggers and actions.
What's Working:
What's Not Yet Available:
To Install:
If you want to use your existing learned codes, you can choose the "hs2_signals" remote when defining triggers. The problem is that they are all named by number which related to HS2's "Signal Location", which isn't very meaningful in HS3. I've created a utility that will create separate remote files for each HS2 infrared device along with it's learned codes, and the code names stored in HS2.
Please let me know what other features you want to see in this plug-in along with any issues you're seeing in the betas.
Thanks,
Note: This is a paid plug-in ($39.95) and the beta will expire at the end of September.
This version supports core functionality related to receiving and sending IR commands in HS3 via triggers and actions.
What's Working:
- Full support for selection of individual remotes, buses, and devices in triggers.
- Full support for selection of individual remotes, buses, devices, and external LEDs in actions.
- Triggers and conditions for detecting changes in connection status with the IRTrans server software.
- IR sequence detection (matching on a sequence of signals within a time period).
- IR code repeating (ex. HSTouch users can hold a button down to repeat an IR code).
- Scripting support for sending IR codes and controlling relays.
- Web interface for configuring the plug-in.
- Send IR codes and control relays from the "Send Code" web page.
What's Not Yet Available:
- Control of relays through events.
To Install:
- Download the attached zip and extract into the HomeSeer HS3 folder, or wherever your other working plug-ins are installed.
- Re-start HS3.
- Go to PLUG-INS | Manage and enable the IRTrans plug-in.
- You'll now see a top-level trigger called "IRTrans Trigger" when selecting a trigger or condition, and a top-level action called "IRTrans Action" when selecting actions.
If you want to use your existing learned codes, you can choose the "hs2_signals" remote when defining triggers. The problem is that they are all named by number which related to HS2's "Signal Location", which isn't very meaningful in HS3. I've created a utility that will create separate remote files for each HS2 infrared device along with it's learned codes, and the code names stored in HS2.
Please let me know what other features you want to see in this plug-in along with any issues you're seeing in the betas.
Thanks,
Comment