I am not sure if this is related ot the issues described in the thread, but I have been having extraordinarily strange behaviour with Programs And/Or Networking Resources. It is hard to pinpoint exactly what is happening, but the best I can describe it is that my program commands to send network commands get either lost, sent in the wrong order, or the timing is wacked.
Specially the one instance I can recreate is a pown on sequence for my Home Theater. I send IR and Network commands to get things going, and have pauses in to assure that devices power on before getting any further commands. Some commands that are supposed to be sent before a wait delay, get sent after the paude, and frequently in place of the command that was positioned after the wait.
Here's an example:
Set Scene 'Basement LED On'
Resource 'Basement LED Yellow'
Resource 'Home Theater Receiver Power On'
Set Scene 'IR TV Power On'
Wait 1 Second
Resource 'Directv Home Theater On'
wait 6 seconds
Resource 'Home Theater Receiver Volume -26DB'
Resource 'Home Theater Receiver HDMI 2'
Wait 30 Seconds
Set Scene 'AV rack LED Off'
Wait 1 Second
Set Scene 'Home Theater Nook LED Off'
Resource 'All LED Ambience'
Okay, so what happens is that the switch to HDMI 2 on the receiver happens AFTER the 30 second delay. The final network command to adjust LED lighting to ambience levels never happens until I execute another program with a network resource and it triggers then.
It is almost like the caching/queuing of the network resource commands has a defect.
Please help!
Thanks