Still not sure about how my 895 is dealing with inputs and outputs and how it is remembering things. I have the following equipment:

Philips TV
Sony Freeview Box
Elgato PVR on a Mac Mini
Panasonic DVD/VCR

On the Philips the inputs are:

Ext1
Ext2
AV

and the outputs are:

TV (which in turn accesses the input options listed above)
PC (which cycles between Digital & Analogue - PC-D & PC-A)

So I've created two Philips TV devices, one that is used to choose the Inputs and one for the Outputs. I've then included BOTH TV's within each of the activities, even if no input/output choice is required. For instance:

Watch Freeview TV Activity:
Output - TV
Input - Ext1

Watch PVR Activity:
Output - PC-D
Input - "input choice not needed" (or whatever the option is called)

Watch DVD Activity:
Output - TV
Input - Ext2

Listen to iTunes Activity:
Output - PC-D
Input - "input choice not needed"

My question is do I need to include the "Input" choice on the "PC" Output Activities? The reason for the question is that it seems a redundant command, but I'm not sure how the remote will know where it's at without them. Currently it seems to work fine although there is a problem when I exit the Watch DVD activity when the Input option seems to get confused and cycles through to the wrong choice.

I think it may be a timing issue, (that I have yet to check thoroughly), as I have to power down the DVD player to get back to Ext1 and in doing so have to power the TV down first to stop it emitting a high pitched scream and then power it back up again when the DVD player is off! But I can't help thinking that taking out the choice can only simplify things.

Is it needed?

Dan - why do you think you don't need the input choice on watch PVR? I forgot how your TV setup works but it seems to me you'd need to tell it which input it uses - or does it select the input automatically?

Basically it comes down to this: SmartState will remember the power state (off or on) and the selected input for each device. If you have discrete input selection then it's not really needed but if you cycle through lists then it's mandatory that the remote stays in sync with the TV or it can get confused.

If it works intermittently then it's probably a timing issue - try increasing the inter-device delay for the device that is missing the commands.

And please explain how the TV works when PC-D is selected as the output - still not clear on that one.

Well, the TV has the option to be used as a simple LCD monitor for a PC via DVI or VGA connections. This option is selected by pressing the "PC" button on the original remote and once in this "Output" option you can then cycle between PC-D, (for the DVI output), and PC-A, (for the VGA output).

For TV use you would press the "TV" button on the original remote and then a separate cycle button for the TV "Inputs" of Ext1, Ext2 and AV.

So when you are using the screen as a PC monitor surely the TV input selection is irrelevant? I'm seeing it in simple terms as 2 separate channels:- PC Output and TV Input. Whether you have selected Ext1, Ext2, or AV as an input for the TV doesn't matter when you are on the other "channel" using the monitor as an output. In fact you can hear the audio from the TV when you are using the PC if you want and you can have a PIP on the PC screen of the TV if you want, (and vice versa), which proves the fact.

Which I suppose may answer my question in that surely it is irrelevant whether the device for choosing the TV input on the PC functions is linked to the activity or not. But I guess it can't hurt to keep them "in the loop" if no harm is done!?

I see. What you're calling "Outputs" are really just an alternate set of TV "Inputs". The signal is coming *into* the TV from the PC. A lot of TVs have 2 different sets of inputs to cycle through so this isn't unusual.

You're correct that the PC inputs seem to have no relation to the TV inputs so having them on separate devices is ok. If pressing TV always put you on a particular TV input then you *could* say that you go directly to each input, then send more commands.
e.g. If the order is always TV then Ext1, Ext2 and AV in that order then the sequence for Ext1 would be TV followed by TV, Ext2 would be TV followed by TV TV etc. If TV starts on the current input then that option won't work.

I think the 2 device solution is the right one. Try increasing the inter-device delay for the TV to remedy the intermittent problem of missing an input command.

You'd get much more accurate answers if you'd list the model number of your TV & perhaps a link to the manual so that we know exactly what you are talking about.

It sounds like you have a TV that has a master input mode (TV/PC), then submodes under each mode. So what you want to do is have one device that handles power & TV/PC mode selection. You add this to all your relevant activities. Then you have a second copy of the TV device (always on) that is handling mode selection under your TV devices. You probably want to add this second copy only to the TV activities. Then when you switch to a PC activity it will presumably just stay where it is & remember when you switch back to TV mode.

But it really depends on exactly what each button on your remote does, and what repeated presses do. Conceivably *3* devices could be best depending on how the TV behaves. Post your model #!

Interesting that you mention having 3 devices. Having been pointed in the right direction as to setting up "clone" devices by akirby I originally set up 3, (TV/PC choice, Monitor choice (either VGA or DVI), and TV choice, (Ext1, 2, etc))but after thinking about it a little more I changed it to two dropping the Monitor choice as VGA was never going to be used. Maybe that's the key, include the third "level" of input.

Model number is 23PF9956/12 and the link for the manual is [Link: usersmanualguide.com]. It's 2nd from the bottom, the 3.51mb file, not the 159kb one.

To summarise the input/output buttons on the remote:

PC - first press changes from TV mode to the last PC option chosen, (in other words it remembers whether it was last on either PC-D or PC-A). Further presses cycle between PC-D & PC-A only.

TV - first press changes from PC mode to the last TV input chosen, (again it remembers where it was set when last used). Further presses cycle between:

Tuner - (analogue TV signal. I forgot to mention this above)
Ext1 - Sony Freeview box (digital TV)
Ext2 - Panasonic DVD/VCR player
AV - not used

Doe this give anyone any more ideas or suggestions?

OK, that makes things a lot clearer. Unfortunately, I think it almost makes it clear that this TV is quite messy, with commands that acts like either a discrete or a cycle code depending on what state the TV is in. It's a hybrid thing that doesn't fit neatly into the paradigms Harmony has set up.

What I would do in this situation, is actually just go back to using only one device, cycling between the TV inputs. Set the PC activities to use whatever input you use most often. Then, when setting up the PC activities, use the "I send more commands" option, send the "PC" key on entry, and send the "TV" key on exit.

This will change inputs slightly more than strictly necessary, but should keep the Harmony & TV states sync'd. The 2 device solution runs into problems if the Harmony decides it's safe to resend what it thinks are "discrete" "TV/PC" commands when that will actually cause a input cycle. E.g. you are on TV activity and change to another TV activity.

Powering off your TV while inputs are changing is a bad idea. Perhaps you should just consider leaving the DVD player on when you leave the activity, turning it off only with system off? The TV screams when the DVD player is powered off and it is left on ext2?