I have an Olevia LT32HV. From what I've been reading around the web these TVs don't work exactly as they should with the Harmony models, and mine is no exception.

Here's my setup:

Watch TV - uses Component 1
Play Game - uses Component 2
Watch DVD - uses DVI

See if you can follow this...

When I switch to DVI from Component 1, and try to switch back to either Watch TV or Play Game, the TV will be put to the correct input.

But, if I switch to DVI from Component 2, and try to switch back to either Watch TV or Play Game, the wrong inputs will be set for either of those. It will stay that way until I use the help button.

I'm using the default set of commands from the Harmony Database for this TV. My question is, why does it switch back correctly if i got to DVI from Component 1, and not the same way if I switch from Component 2? It should be the EXACT same procedure.

Maybe someone coded the functions wrong? I happen to be a somewhat-capable programmer as well...is there a way for me to edit them somehow?

And more food for thought, why isn't this remote capable of handling multiple cyclical inputs for one television? Will this feature be added by an update soon?

Finally, is there anything I can do to fix this? I must have tried a million different input command combinations but they didn't work. I really don't want to add any ghost TVs to my setup if I don't have to. That'll confuse me a lot. A step by step guide would be appreciated.

It might also be nice to alert the folks at Logitech so they can come up with a permanent solution for this kind of issue...I don't think they'd listen to me though.

Thanks.

Sounds like it always goes to component 1 no matter what. If it's consistent you can just add additional commands to the activities that use component 2 to get it there.

Like I said, if I switch to DVI from Component 1, I can hop around the activities and inputs without any issues whatsoever. My setup stays like I set it:

Watch TV - uses Component 1
Play Game - uses Component 2
Watch DVD - uses DVI

But...if I switch to DVI from the activity using Component 2...next time I try to go back to the Component activities, they will be set to the opposite Component input, like this:

Watch TV - uses Component 2
Play Game - uses Component 1
Watch DVD - uses DVI

The Olevias have three seperate buttons that cycle various inputs...

Video - Video1 (one press), Video2 (two presses), Video3 (three presses) (NOTE: one press to toggle each one if you're in the group)
Component - Component1 (one press), Component2 (two presses) (NOTE: one press to toggle each one if you're in the group)
DVI/VGA - VGA (one press), DVI (two presses) (NOTE: one press to toggle each one if you're in the group)

It does those in order every time you press it, AFTER having left a particular group of inputs. I tried adding and removing commands to and from the start and end of activities but when I fix one thing, it will mess up another...

Does logitech even work on solutions for such things or do they have to have a million complaints before they do something?

They will do everything possible to get those devices working and have probably already done it for others with the same TV so I would definitely give them a call. They have some capabilities to do things in your setup that you can't do.

If you leave component 1 and go to DVI, then press component once - does it go back to component 1 or go to component 2? Either that's the normal behavior of the remote to toggle when you switch from non component to component or maybe it's changing it from component 1 to component 2 before it switches to DVI.

In any case, here is one way to fix it yourself. This works any time you have a device with multiple independent toggles. Define 3 copies of the same TV device. Setup the inputs of each one as a cyclical toggle - one for video, one for component and one for DVI. Include the appropriate device with each activity based on the input needed. This will allow the harmony smart state to keep track of each toggle separately. If your TV has discrete off and on you're ok - otherwise you may need to add a 4th TV device in each activity just to control power and set the clones to No Power Buttons.

But I'd call support first. They may have a better solution.

Ok, I'll try giving them a call. You said they can do things in the setup that I can't. What kinds of things? Do they remotely access my remote or something or edit database functions?

Thanks for the help. I appreciate it very much. I'm sorry if my explanations were a little confusing. The issue confuses me too. Otherwise it's a great remote. I can't live without it.

Because your setup is stored online, they can see it and change it. However, they don't see the remote. After the changes are made, you simply login, and update the remote.

I'm happy to say I found a roundabout solution, but it works, and it doesn't involve cloning.

Since I use only Component 1, Component 2, and DVI, I went to the inputs setup screen at option 2 (press a button to go directly to each input) and scrolled to where it asks me how I get to Component 1. Here I set only one command "InputComponent" because no matter what input I am on one press gets me there.

Then I went to Component 2 and I set THREE commands "InputDvi/Vga" "InputComponent" and "InputComponent."

I put three because if you're IN the Component input cycle it would take ONE press of the component button to get to Component 2, but if you're OUT, it takes TWO presses to get it to Component 2.

If I set a command to switch to Component 2 for when I am IN the cycle, that command would take me to the wrong input if I go OUT of the cycle. So, instead I take it OUT and back IN intentionally, so no matter where I am it will get to 2. This way the remote just executes the commands and doesn't have to try and be smart about it.

And for DVI, I set two commands "InputDvi/Vga" "InputDvi/Vga."

After I did that, if you take the Inter-key delay and the Input delay down to 0 and set Inter-device delay to 100ms it switches really, really quickly...The Power On delay is at 7000

OK. That's my story. I hope it helps people who have the same problem with their Olevia LT32HV TVs.

I hope that made sense. If anyone is still wondering why I did what I did let me know and I'll see if I can explain it better. Thanks for all the replies.

P.S. Alternately to button pressing, you could also set up the TV to switch inputs using the menu/scroll/select method, but it takes longer and doesn't seem as efficient in terms of commands being sent to the TV.

Bravo JSein456, you found the proper anchoring points. This post deserves a sticky (but stickies are not supported by this site). The pseudo discrete method is always better than the cycling method. The trick was to find those anchoring points.

Well, you didn't say that you had a discrete way to get to component 1 every time. Bravo!

Yes, the above works just fine except it's not very efficient. Getting from Component 1 to Component 2 takes three commands rather than one.

There ARE some interesting functions for this TV in the Database. There is one called SetInputType Component. They used that and SetCompInput Comp1 and SetCompInput Comp2 respectively to switch component inputs by default. After having tinkered with the remote They're definitely not regular IR commands... I think they were coded.

I have an idea how to fix them so they behave properly. Is it possible to call them and have them do it there or does it have to go through some kind of special editing process before they get revised?

It seems so easy to make them behave like they're supposed to after having thought about it for a while, I wonder why Logitech didn't pick it up.

By the way, is there an update coming that actually allows the remote to properly handle TVs like this without the need for clones?

You are throwing the "ball" in the wrong court. It's the TV manufacturers that should clean up their convoluted mess. I have added the "Olevia" brand to my "avoid" list.

You're right. Maybe it was hoping too much.

I'm sorry for bumping this up again, but I wanted to let you guys know I have a better solution to my problem that might help people who have noticed the same thing I did when I posted this topic.

Basically, just stick to the default input switching method that the folks at Logitech came up with, but do one other thing:

Go to the activity that uses Component 2, review the settings for the activity, tell the update software that you want more control of devices and options and add the command "Set CompInput to Comp1" to the "when activity exits" section.

That way, before you switch out of Component 2 to any other input, it will set the input to Component 1. As long as the remote switches from Component 1 to any other input using the default setup, it will come back properly from that input.

The way the functions work it's a little complicated to explain, but it works for doing any switch combination you can think of among Component 1, Component 2, and DVI. I had to infer how the functions work by testing about a dozen command combinations and this is the best setup I've come up with short of re-coding functions and hacking the remote software, which is supposedly impossible.

If you have an Olevia LT32HV, try this, and I think you'll be happy with how the remote operates those three inputs. If you want more help or more detail (god forbid) let me know and I'll try my best.

By the way, the Olevias are not bad televisions. They're affordable and they work as good as brand names (from what I've seen in stores)...and they have a certain stylish look...for the record, I've been very happy with mine and I'd recommend it to people...

If only they made switching inputs a little less confusing for universal remotes...maybe they will one day.

P.S. You might also want to leave the four delays to what I mentioned earlier

Power On delay 7000
Input Delay 0
Inter-key delay 0
Inter-device 100

These work good...for me and the components I have anyway. Try it and if some commands seem to be "lost" bump up the Inter-device delay.