?FTR, I almost never turn the connect off with any device and have not had any particular issues until now...“

?

Same here.

Especially in my home/test-system, i?ve got a lot of TCP Clients in the program pointing to devices that are rarely switched on or connected because i just need them for some specific testing. Never had a problem that the TCP Client wouldn?t connect after the device is connected or switched on.

Actually, i?m assuming more issues with permanently activating and deactivtating the TCP Client, but it sounds as if that?s working reliably.

So i think i?ll give it a try.

?

Cheers,

Thorsten

?

?

Olivier,
Yeah, I'm not sure why I have a '1' on it (probably some legacy thinking...) at minimum, I usually make it an actual signal, that is driven by a '1', thru a buffer, so that I can at least toggle it in Debugger...
I like the concept of your approach, though I find that more often that not, you want the comm's running all the time for status updates (unless its a 1-way control). This in particular is a lighting system so there's alot that I want to have ready to go without having to poll and wait.

FTR, I almost never turn the connect off with any device and have not had any particular issues until now...
This is a *Problem* with Crestron and their TCP client...hopefully we'll see a fix soon...