| Author |
|
smarty
Super User
Joined: May 21 2006
Location: United States
Online Status: Offline
Posts: 728
|
| Posted: June 17 2006 at 21:18 | IP Logged
|
|
|
I have been able to set up my USB UIRT and learn a couple of remotes. The learn work...I have USBUIRT control of the IR devices. Now, I want to use incoming IR to trigger PH to do something. I can see the incoming IR in the log file, but the trigger doesn't fire.
Here is my trigger:
insert into triggers values ('TEST1','TEST1','ph_tts("this is the I R trigger")',2,'GV',0,1,'1',1,0,2);
I am using a remote called "GV", Trigger type is "IR In", Status is "active", Trigger ID is is "any".
This trigger should fire with any button push from this remote. I even went back and tried to re-learn a few buttons (in case something changed). Ideas?
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: June 19 2006 at 23:32 | IP Logged
|
|
|
Smarty,
I imported your trigger and everything looks fine with it. In your USB-Uirt "Settings" screen (in the Controllers section of the Explorer), do you have "Enable Remote Control" checked? This must be checked in order for incoming IR triggers to fire and also to allow the learning of the "Incoming Code".
Also, keep in mind that a bug was just discovered with the USB-Uirt and certain remotes that use a short "repeat" sequence. With this type of remote and "Enable Remote Control" checked, you will not be able to successfully learn the incoming code and will most likely prevent you from learning the outgoing code as well (this is fixed in the upcoming beta). If your remote is one of these types, then just press the button quickly, check the eventlog and copy and paste the "short" incoming code into the "Incoming Code" field in the IR Equipment Details screen.
To sum up, in order for the Incoming IR trigger to fire, you must have "Enable Remote Control" checked in the Uirt settings and have "learned" incoming codes in the IR Equipment Details screen.
Dave.
|
| Back to Top |
|
| |
smarty
Super User
Joined: May 21 2006
Location: United States
Online Status: Offline
Posts: 728
|
| Posted: June 20 2006 at 21:16 | IP Logged
|
|
|
Dave,
Thanks. Yes, the "Enable Remote Control" was checked (enabled). After I cut and pasted the incoming IR code from the Event Log into the "Incoming Code" box for the particular IR key in question, the trigger worked just fine.
As you would guess, I then went back to attempt to re-learn the key in question (and a few others for good measure). PH re-learned the same incoming codes (but they didn't match what the codes were in the Event Log - weird). Weirder still, is that the outgoing codes from the same PH IR table controls the external IR device just fine. It appears just the incoming codes no longer match what the even log sees.
Lastly, in the controller settings area, does the "Save Signal Type" effect this in any way? I am saving as "UIRT Raw".
Thanks for your replies....it helps us newbies!!
Edited by smarty - June 20 2006 at 21:29
__________________
Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: June 23 2006 at 23:04 | IP Logged
|
|
|
Smarty,
UIRT Raw is just fine. You could also save as Pronto if you wanted a "generic" format. The UIRT Struct is usually not recommended because it may not contain enough data to replicate the code effectively.
If I remember correctly, one of the things you did recently was load the -4 patch. The -4 patch contained some major changes to the USB-Uirt controller so this may account for the changes you're now seeing.
I would probably attempt relearning all of your IR codes since the -4 patch has been loaded. If the code does not seem to be learned or takes a very long time, then I would turn off the "Enable Remote Control" option and learn just the outgoing codes first. Then re-enable the option and briefly press the button and note the incoming code value in the eventlog and copy and paste it into the "Incoming Code" value of the IR screen.
This will all be changing in the next beta where the USB-Uirt issues should be finally worked out. Ive tested on a number of different remotes and the learning issues should be resolved so this process will only be temporary.
Another thing to note...learning of IR codes is never exact. You can learn an IR code and retrieve a Pronto or Raw sequence and immediately relearn the same code again and most likely the sequences will not match or be exact. However, if you actually understand how the sequence is constructed and compare them relatively, you'll see that they are essentially the same and will work just fine. There is a fair amount of "slop" in IR codes and most sequences are measured in milliseconds. So if an on signal is 600 ms the first time and measured as 595 ms the second time, this won't make any difference.
HTH,
Dave.
|
| Back to Top |
|
| |
|
|
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: USBUIRT Incoming IR Triggers
