Most modern HT equipement have 'discreet' on off codes, meaning that there is s separate code for "on" and another code for "off". For instance, if your receiver is already on, sending another [on] code will not shut the device down.
However, there is some gear (probably older but maybe even some new) that do not have discreet codes for on and off. This presents real aggravation but here is a trick you can check for.
Some devices will ignore a 2nd [on/off] code if it's sent immediately right after another AND the device is already on. Confusing but you can make this work for you.
For instance, my old Toshiba TV does not have discreet codes but if it is already turned on, it will ignore the second press of the [on/off] button if it happens too quickly. This is to protect the TV from powering back up instantly if it still hasn't really depleted the charge from trying to turn off. This can be used to simulate discrete codes.
In the above scenario, macros including these commands will always produce the desired end state.
ON Macro = [on/off], [on/off], pause 2 sec., [on/off]
If TV is already on....
(TV turns off) (ignores 2nd so stays off) (accepts 3rd after delay so TV=on)
If TV is already off...
(TV turns on) (TV turns off) (TV turns on again)
Off Macro = [on/off], [on/off]
If TV is already on...
(tv turns off) (ignores 2nd so stays off)
If TV is already off...
(TV turns on) (TV turns off)
If you do not have discreet codes and there is no trick like the above, than another option is to have a macro that turns everything on only and another that turns everything off only. Then just do not use on/off codes in any other macros.
The Harmony's and some URCs do keep track of a devices 'state' but they can get mixed up sometimes too. Harmonies include a help feature that you go through to help them get back on track.
