Edit IR codes - no learn option??

[skeptic]

I added a device template for my TV (Vizio vx32l), added the codes for the remote using the learn function, tested a bunch, etc.  Unfortunately the vol up/down pretty much don't work.  If I keep hitting vol up/down it will occasionally work, but not well.  I upped the ms between codes thinking that may be the issue, but it didn't do a thing.  I'm guessing I need to re-learn the codes for some buttons as I had some difficulty learning a few, vol up/down being the most painful.  When I go into "Edit IR codes" on the right hand side of each key it only says "delete code" instead of "test" and whatever the other option is when first creating it (delete?).  When I click one of the "New code" buttons it defaults to "Type code manually" instead of "Learn code" and if I select "Learn code" it jumps back to "Type code manually".

Am I going into the wrong place?  Is it not possible to relearn codes for a device after it's been created?

BTW, I am using a dual stick-on IR emitter.

[domotiqa.com]

Skeptic,

 Use webadmin - Wizard - AV Equipment - your device - AV properties. You will then get the test. I find when you go back to the template and click edit A/V properties you loose the send too device which would be why you cannot test them.

 Dave

hy,do you know if there is a way of
1/ creating cycling IR signal!
For example, my tv (panassonic plasma) can turn on/off by holding the remote buton during 2s-3s, so I tried to copy/paste the learned code several times but it's not enough !
2/ creating more complex scenario like sending one code, then 1s later sending another one...
3/ sending code depending on event, in my case, I have a air control device that I control by infra red, however the ir signal send for increasing the temperature is depend on the current temperature. For example, if it's 75°, then the signal should be 76°...
thks

[jondecker76]

Domotiqa - A while back I added features to the web admin to adjust the IR repeats for normal and volume IR commands. You can apply the fixes and try increasing the IR Repeats until you get the desired result. See instruction here:

http://forum.linuxmce.org/index.php?topic=5510.msg32690#msg32690

[domotiqa.com]

thanks both for advices and files, I'll go into it and give feedback!

For the air unit I halready have the script (just adapt it to ruby/perl...)

in french
http://ccnicolas.free.fr/domotique/climuirt.htm

in english...
http://fr.babelfish.yahoo.com/translate_url?doit=done&tt=url&intl=1&fr=bf-home&trurl=http%3A%2F%2Fccnicolas.free.fr%2Fdomotique%2Fclimuirt.htm&lp=fr_en&btnTrUrl=Traduire

Thks you

[domotiqa.com]

jon:
why your script has not been merge to the project ?

[jondecker76]

i did it after 0710 release, so now it won't be out until the next LMCE version

You can easily create a GSD for your Air unit - converting the script you found to Ruby should be very easy and wouldn't take much time. Just implement it as a Climate Device, and implement the Set Temperature command (keeping in mind that you can handle absolute temperatures, and changes such as +1,-2, etc.)

[domotiqa.com]

ok !
Just for info, did you fix these ??

Hopefully it won't be too long and I'll get that part figured out. Its one of the few bugs remaining in the toggle handling.

[skeptic]

Skeptic,

 Use webadmin - Wizard - AV Equipment - your device - AV properties. You will then get the test. I find when you go back to the template and click edit A/V properties you loose the send too device which would be why you cannot test them.

 Dave

Very interesting.  It does in fact pull up what appears to be the same screen, only it has the test buttons and allows it to learn codes.  Not sure if it will fix my volume control issues, but at least I can get back in an re-learn the codes.

Thanks!

[jondecker76]

it will be for your local installation only. The IR codes get attached to the device template, so editing them for an individual device will change it for all devices based on that template. The only way it would go to the master server is if you did an sqlcvs checkin, and even then it would have to be reviewed and accepted.

I looked into changes in the web admin to allow learning codes without an actual device being created, and after a weeks worth of work on it, the way that IR learning is implemented, it requires an end level device.

So the work flow turns out to be: Create a device template. Do not lear IR codes at this time (unless you also had a device automatically created). Then create a device, and learn the IR codes from there. The device template will now reflect the added IR codes.

[skeptic]

What would be REALLY handy would be to be able to have it learn codes for a new remote.  I have a ton of old remotes laying around, some of which would be perfect for controlling LinuxMCE such as my old DirectTV and Tivo remotes.  Unfortunately the only way I know of to add them as a USBUIRT remote is to open a shell, tail a log file, then when using the remote grab the code from the error that shows up.  Then using the MCE remote config as a guide and guess other key names build a text file using the codes from the log file...  A horrible hack, but the only way I could get my streamzap remote going. 

[skeptic]

I've ran into the same issue of not being able to learn codes as well.  A couple hints that may help.  Put new batteries in the remote. Hold the remote about an inch away from your USBUIRT.  Learning is much more sensitive than just using a remote.  If you have more than one USBUIRT, make sure you are using the correct one.  I've been bit by all three things.