8/22/2017
Topic:
Forcing current state value
Scott Goffman
|
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 |
9/3/2017
Topic:
Forcing current state value
Scott Goffman
|
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);
} |
9/3/2017
Topic:
Forcing current state value
Scott Goffman
|
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. |
9/7/2017
Topic:
Insteon Mini Remote as Trigger
Scott Goffman
|
From reading other forum posts and experimenting, it looks like CastleOS does not support Insteon Mini Remotes directly.
If it's possible (that is, if they behave enough like other Insteon Controllers for this to work) I think it would be a great feature to add support for them as Triggers.
Specifically, my use case is for a theater, where I want to use a Mini Remote to turn the whole system (including Insteon lights, projector, amplifier, etc.) on or off. I can hook up everything I need to a CastleOS Scene, but can't trigger that scene with the mini remote.
I can't just link the mini remote to the lights device and use that to trigger everything else, because the lights need to be turned OFF while everything else remains on.
The only solution I've come up with so far is to add a second Insteon device (e.g. an ApplianceLinc), link the mini remote to it, and use its state as the scene trigger. This just seems like a silly waste of a device that will have nothing actually plugged into it. 
Please let me know if I'm missing another way of making this work.
Thanks,
-Scott |
9/7/2017
Topic:
Insteon Mini Remote as Trigger
Scott Goffman
|
I tried to use my workaround method, but it's a no-go; I linked the remote to an ApplianceLinc, but using it to turn the ApplianceLinc on/off doesn't trigger the event.
Turning the ApplianceLinc on/off through CastleOS does trigger the event, so I know it's working on that front.
-Scott |
9/11/2017
Topic:
Insteon Mini Remote as Trigger
Scott Goffman
|
Chris Cicchitelli wrote:
Did you do a two way link of the appliancelinc back to CastleOS after you linked it to the mini remote?
If you mean using the "Link Device" button in CastleOS to link it back to the PLM, then yes, I did do that. Or are you saying I should NOT do that? |
9/11/2017
Topic:
Insteon Mini Remote as Trigger
Scott Goffman
|
"the Device to CastleOS link": Is that created with the "Link Device" button in CastleOS?
"CastleOS to device": Is that simply adding the Insteon device in CastleOS?
I've done both of those; if there is another step required, please give more details. |
9/11/2017
Topic:
Insteon Mini Remote as Trigger
Scott Goffman
|
Looks like it's a problem with that particular device; it's a very old ApplianceLinc (rev 1.1), and the linking back to CastleOS just never seems to work.
I tried the same method with a newer ApplianceLinc (rev 4.6) and it works as expected.
I need to find a less annoying hobby. |
9/11/2017
Topic:
Insteon Mini Remote as Trigger
Scott Goffman
|
Well...
I've linked the mini-remote so it controls the ApplianceLinc on/off.
I've linked the ApplianceLinc to CastleOS up so that switching it on/off manually (using the Set button) is reported correctly to CastleOS (and events are triggered).
But if I turn I turn the ApplianceLinc on/off with the mini-remote, the state change is NOT reported to CastleOS. |
10/12/2017
Topic:
Patch notes
Scott Goffman
|
Chris,
Can you post patch notes here (or somewhere) whenever a new Beta is released? I grabbed the version from 9/14/17, but have no idea what's changed or what to test, so can't give any useful feedback.
Also, after installing 1.3.3210, CastleOS is showing there's a new Beta version available, but there's nothing new to download (latest is still from 9/14).
-Scott |
8/17/2018
Topic:
End of the road?
Scott Goffman
|
After a reboot, my CastleOS is showing "Trial Expired". Looks like it's no longer able to connect to the license servers.
PM'd Chris, but no response, and his last logon to this site was 7/3.
So is Castle OS dead? I guess I'm moving on to either OpenHAB or HomeGenie. Their setup/config is waaaay more complex than COS, but they're open-source and not tied to a cloud service that might go away at any moment.
Anyone have other suggestions for replacements?
-Scott |