The Smart State technology is wonderful for handling devices without discrete power and input commands, but why on earth is it used when discretes are available? This makes Harmony remotes MUCH less robust. Why not always send discrete commands to devices when they are used in an activity, instead of sending nothing when the remote thinks a device is already in the right state? This behavior causes problems when Smart State gets out of sync in many real-world situations, like devices missing a command due to poor aiming or blocked line of sight, using another remote (taboo, I know, but it happens), or using the front panel buttons on the device.

Always sending discrete commands would solve all of these, and I don't see any downside. I got used to the fact that my MX-700 Power Off button always turns every device off, NO MATTER WHAT. With my Harmony I occasionally have to use the Help button.

Can I turn off the Smart State logic for some devices?

It should always send discrete codes no matter what. Something else is wrong (unless they've changed this feature).

I agree that it SHOULD do that, but it doesn't. Please see the message I just posted to the "Harmony One - Activity-dependent Power On" thread. Maybe they changed that feature. Or maybe I'm still missing something. If someone could try to reproduce my test results, it might help determine whether all Harmonys work this way or whether it's just me.

As far as I know the Harmony remotes will always send discrete input commands even if the device is already on the correct input. It will not re-send discrete power commands if it thinks the power command has already been sent.

How, in what way?
Most of my power and input commands are discrete and that presents no problem whatever.

Same experience here.

By "MUCH less robust" I mean that when Smart State gets out of sync with True State, the remote could correct the situation by re-sending the discrete codes when starting a new activity, but does not because it thinks the device is already in the desired state. On the "Harmony One - Activity-dependent Power On" thread I listed several real-world situations where the out of sync condition can happen.

Others have confirmed my test results for power codes but not for input codes. I may have something unique in my device (Harman-Kardon AVR-330), in my setup, or my remote. I will run a few more tests, but I may need help from the Logitech Support staff to get my remote set up the way I want.

It would have saved you a lot of hassle if you'd checked with Logitech support from the start whether power and input commands are sent or not on changing Activities.
I'm fairly sure that input commands always are and power commands are not, but it doesn't matter as I've never had a problem with it, so I've never enquired!

power on off are the biggest issues . .

discrete powers should always be sent . .
besides that . . they should offer some soft
of video sensor for devices that do not have discrete power . .

most of the harmony remotes i programmed in the past
have issues eventually with cable not always going on correctly,
and when cable boxes are hidden, the help feature does not help at all..

nevo remotes have an optional video sensor just like i mentioned . .
they basically monitor the video coming out of a device,
if it senses video, then it doesnt send a power command,
if it doesnt sense video , it does send power command .
and vice versa for power off . .

ensuring the cable box is always on when you need it to be . .

You want a two-way remote?
They exist, but they're not Harmonys, and they're much more expensive!

The reason why Harmony does not blindly re-send a discrete power on command when switching to another activity, is because it would also have to invoke the power on delay which could be very long for some devices. However, it will re-send the discrete power on command (and discrete input) when you select the same activity if the device is deemed and configure to use the discrete method. You can also use the Help button to re-sync regardless of device type (discrete or toggling).