Forcing current state value 

Chris,

I have a relay device (Insteon-to-Somfy) that is fairly unreliable; the Insteon switch receives its commands 100% of the time, but the connection between it and the Somfy drapes is only about 75% (e.g. the drapes responds correctly about 3/4 of the time).

The "fix" I'm trying to set up is a simple script to repeat the "On" or "Off" command 3 times in a row, with a few seconds delay between each send.

CastleOS isn't allowing that, however; because the Insteon switch is telling it "I'm already on", CastleOS won't send a "turn on" command.

I've tried using device.currentState = "0", but that doesn't seem to override CastleOS's understanding of the on state (it still won't send "On" even if currentState is "0").

Is there any way to force CastleOS to send a state switch regardless of current perceived state?

Thanks,

-Scott

That's what I'm using. Specifically:


int tries = 3;
int delayTime = 10;

//set current state to Off;
device.currentState = "0";
for (int tryIdx = 1; tryIdx <= tries; tryIdx++)
{
device.ToggleDevicePower(true);
System.Threading.Thread.Sleep(delayTime * 1000);
}

Hmm, you're right. I thought the Insteon events weren't showing up in the log, but I just checked and the events are there. I guess the problem is on the Somfy transmitter end, which must be deciding that the shades are already in the desired state so it isn't transmitting the command.