I had some issues with activity switching. When making a cold start (from full power down) to an activity, the receiver (that’s generous - it’s a YSP-2200 soundbar!) and TV (Samsung LED from around 2009) would fail to input switch. They would only turn on. If the cold start activity differed from the activity on power off, the inputs were wrong. If I re-engaged the activity once all devices were fully powered on there were no input switching issues.
I read as much as I could from the FAQ and the forums, doing searches for “delay next command” and “delay” (among others). It appeared the issue was a need to delay input commands to these two devices (soundbar and TV). But that did not appear to resolve for everybody, and my experience was spotty. I’m setting all this up to ask a question (test a theory, really) and create what (hopefully) would’ve been the thread I needed.
How does “Delay Next Command” work? Does it:
- Wait the specified delay before issuing another command to that DEVICE?
- Wait the specified delay before issuing the next command in that ACTIVITY?
It appears to be choice #1, can someone confirm?
Here’s why this matters: I found at least one forum post where the person claimed setting the delay up to 10s (10,000ms) did not help. I have three devices in my “watch TV” activity:
- Yamaha soundbar (IR Control)
- Samsung TV (IR Control)
- DirecTV HR23-700 (IP Control)
All IR control is through the GC Itach wireless I just got from the Roomie store. My activity powers on the three devices and then switches to the needed inputs on soundbar and TV. As mentioned, my problem was from a cold start the inputs wouldn’t switch. Since everything worked fine once things were fully powered on, I concluded repeats were not the issue.
My activity commands are:
- Power on TV
- Power on Soundbar
- Power on DVR
- Switch to TV HDMI1 input
- Swtich to Soundbar HDMI1 input
I tried to add a delay to the ACTIVITY where I thought it made sense: between #3 and #4 (so I made the “Delay Next Command” to the IP controlled DVR have delay 10s). This did nothing to fix the issue. Further, when watching the top of the virtual remote to follow the commands being issued, there was no apparent delay between steps #3 and #4. To repeat: no matter what “delay next command” I put on the power up DVR command, it had no discernible effect on the activity.
Then, I decided to add the delay between steps #2 and #3. This seemed counterintuitive to me - might as well get the DVR powering up before hitting the delay. But, it worked. Further, when watching the commands issued at the top of the virtual remote, there was a discernable delay (of about 5s - what I’d set) before command #3 was issued.
Thus my question from above. If the “Delay Next Command” inserts a wait before issuing another command to a device, this explains the behavior I saw. There was never a second command to the IP controlled DVR in the activity, so Roomie saw no reason to delay. That would explain why I needed to put the delay after the Soundbar’s commmand (command #2)…because the soundbar has another command in the activity (input switching), and so Roomie behaved as I expected.
Again, if I’m understanding the behavior correctly I believe this would’ve helped other users. I could not find this explained clearly here on the forums anywhere.