oberkc

You are not the only one that has occasional trouble with clocks. I, for one, have had troubles before. I simply tried another time source without trying to figure out why. Sometimes, you get lucky. I also have a VAGUE recollection that success can sometimes be based on the frequency that you sync time. I believe the ISY has a setting for frequency of updates. Assuming I remember correctly, what is your set to? More than once a day?

I had assumed you had already created the scene and that the only change necessary was for you to change your behavior. Apparently not. Did you instead create an ISY program to turn on the outlet in response to a command from the switch? If so, I definitely suggest a scene, rather than a program. Make sure your scene includes both outlet and switch, and make sure the switch is defined as "controller". Then, in moblinc, control the scene rather than outlet or switch directly. And...yes...delete the old program.

Yes, there is. You created a "scene" when you programmed your button to contol your fireplace. The scene included your button and your outletlinc. In order for both devices to reflect current status when controlled via mobilinc, you must turn on (or off) the scene, rather than turn on a single device within the scene.

In case you have not seen it, each update gets a new topic, with change description. Try here: http://forum.universal-devices.com/viewforum.php?f=25 You can review each update at your leisure and find what is in each, including recognition of any new devices. I have not memorized the change log, unfortunately, so I cannot answer without performing the same review.

Unspoken regarding this suggestion is that programs with "wait" statements will be interrupted should an initial condition (such as "status") change. So...when the light is turned off, then back on, this will halt the execution of the program, starting it again when the light is turned off the second time. In some cases, this can be undesireable. In this case, however, it is a nice capability.

I use the garage door kit and ISY based upon the excellent example in the UD wiki. It takes advantage of latching mode and works beautifully (at least for me it does). The example, however, is based on a scene relationship between controller (keypad) and responder (relay). There is no ISY program controlling the garage door. I remain a little unclear about your goals with your garage door kit, but I think it premature to globally accept a lack of door mode behavior. The door mode behavior does work in certain conditions. If, however, your C# program can handle only direct commands, then perhaps that is a limitation you will have to live with.

It seems that each version of software brings with it recognition of new devices. Perhaps your new insteon device data was added after ISY v3.2.6? Have you checked the change description for the newer software builds? I know that 3.2.6 is the most recent formal "release", but I would not hesitate to update to a newer software version if I thought it would solve a problem.

Since it is easy, my first instinct would be to clear the java cache.

I would not be looking at access points for any issues you are having with hop count. I would look, instead, for powerline communication problems.

I mounted mine on the door frame, low, near the floor. It is not necessary to mount it to concrete.

I agree that the included instructions don't apply when using an ISY-99. I also found the instructions regarding the colored wires to be confusing, at best. I am not sure that i agree that these terms don't apply. NO would apply your second example, in my mind (close when magnet is near). NC would refer to your first example (closed when magnet is away). I suspect, too, that much of your issues are related to the way the IOlinc operates outside the control of universal devices. The relay, for example, does not report status.

I am curious which "box" you have...is it the signalinc? Is it wired into two breakers from your panel?

Are you sure that it is necessary to include the "stop program" command? My recollection is that initiating a "run program" will interrupt an ongoing wait statement.

is your variable defined as an "integer" or "state"? I believe this program would work as you expect if the variable is a "state" type.

Perhaps, also, that program is being called by another program, such as: if ... then run sunset program

I understand that integer variables will not TRIGGER a program evaluation, but STATE programs will. For example, your program C1 has in it only a condition based on an integer variable. If my understanding is correct, this program will NOT execute, because there is nothing to trigger an evaluation. Perhaps this is why your series of programs is getting stuck? But, as I said, I have yet to need variables and can speak only based on things I have read around here. Hopefully, others can confirm this.

I stared at this set of programs for a while and am having trouble following the logic. What is the purpose of the two variables? Perhaps including some explanation as to the purpose of the various programs would help spur broader response. I don't use variables in any of my programming, but I understand there are two types: integer and state. What types are your two variables? If integer, this could explain why you are not getting the response you expect.

It could be a lot of things, but my first thought is to make sure you have the latest version of firmware for the isy. I recall the bulb being added relatively recently.

This is how I would do it. I understand that there is no such thing as "scene status", so one must look for triggers from the individual scene controllers. No better way is coming to mind.

It works with mine. Please note that both have sections in this forum, under third party products. I would imagine, also, that one could find a good description on mobilinc at the app store and play store.

I use mobilinc. I also continue to use conductor, but I understand that it is no longer supported.

Good catch. I forgot about the bulblinc option.

My understanding is that zigbee support IS pretty limited. If I recall correctly, I believe it may be limited to certain energy monitors. Hopefully, others can confirm with greater certainty. This allows all the apple fans to start claiming that the iPhone is the first device to allow one to control a lightbulb through their smartphone.

I agree with bmiller...this likely does not come directly from a panel, but another fixture or outlet. The wiring you describe is pretty common based on my limited experience. It is known as a switch loop. Yes, an inlinelinc is likely your only option without running additional conductors.

That was my assumption, but I was not certain. Given this, I agree with your conclusion: I don't think this statement will accomplish the desired goal.