Illusion

Thanks for your reply. It sure does look to me like the isy is sending a second F3 chime on order if the program triggers after sunset. Due to the 1s delay I have put in, I never get a second chime in daylight hours, and always get a second chime after sunset. I just cannot figure out why.

In the interest of preserving battery life and reducing network traffic: Has anyone found that a change to the darkness sensitivity of the motion detectors can eliminate the Dusk/Dawn event altogether? I am sure that I am not the only person who is not interested in this feature, and certainly not on all my detectors. It seems to me that each time the device has to send a wireless command, it is using power unnecessarily for a feature I do not care about-not to mention all the unnecessary wireless traffic. Of course, if the feature were disabled I assume that it would also disable it internally in the device itself. So if we can shut it off altogether, we would not be able to use the "Only Trigger At Night" mode of the device, which could actually increase network traffic and battery usage as the detector would be sending commands all day and night, even when we only want a trigger to occur in darkness. Here the isy would have to always do the determination of wether on not to trigger the event. This would be a bad deal for the objectives of reduced traffic and power usage by the detectors. Any thoughts on this?

And the reason the chime sounds twice if it is after sunset, but only once if the sun is up?

Some of my motion detectors seem to send multiple on commands for a single motion event. Walking in front of the motion detector during daylight hours I get this Using the Event Viewer set on Level 1: 2009/02/20 09:00:56 : [ A 3C 31 1] DON 1 2009/02/20 09:00:56 : [ A 3C 31 1] DON 1 2009/02/20 09:00:57 : [ X10] F3 2009/02/20 09:00:57 : [ X10] F3/On (3) But after sunset the same single motion action will cause this: 2009/02/20 09:40:07 : [ A 3C 31 1] DON 1 2009/02/20 09:40:08 : [ A 3C 31 1] DON 1 2009/02/20 09:40:09 : [ X10] F3 2009/02/20 09:40:09 : [ X10] F3/On (3) 2009/02/20 09:40:09 : [ E B9 9C 1] ST 255 2009/02/20 09:40:09 : [ X10] F3 2009/02/20 09:40:09 : [ X10] F3/On (3) Where a.3c.31 is the motion detector, X-10 F3 is my alert chime, and e.b9.9c is the relaylinc switch that controls the front porch light. Questions. 1. Why does the motion detector send two on commands? 1.5 Is the double on signal causing the second chime after sunset somehow? 2. Why does the F3 chime sound twice if the motion detector is triggered after sunset but only chime once if the motion detector is trigger before sunset? 3. Why is the system not also sending the porch light on command twice after sunset? I am lost on this one. The net results of a daylight motion trigger is what I want, ie the chime alerts, the porch light does not turn on. The net results after sunset that I am after is for the porch light to turn on and the alert chime to sound once. Motion-Front Porch: If Control 'Front Porch-Sensor' is switched On Then Run Program 'Front Porch Motion On' (If) Wait 1 second Send X10 'F3/On (3)' Wait 5 minutes Run Program 'Front Porch Motion Off' (If) Else - No Actions - (To add one, press 'Action') Front Porch Motion On: If From Sunset To Sunrise (next day) Then Set 'Front Porch' On Else - No Actions - (To add one, press 'Action') Front Porch Motion Off: If Status 'Front Porch' is On Then Set 'Front Porch' Off Else - No Actions - (To add one, press 'Action') Motion-Front Porch: Enabled Front Porch Motion On: Disabled Front Porch Motion Off: Disabled The calling of an off program instead of just turning off the light is in deference to certain forum members that shall remain nameless always harping on reducing network traffic as much as possible. I have restructured all my programs to reduce network traffic as much as possible.

Had to power down and restart ISY-26 after upgrading to 2.6.14 Seems to be going well other than that.

Michel, I know that you are saving up the UI issues for last, but here is another one for you ongoing list. In the configuration screen of the AC when I have the window sized less than my full 1920 * 1200 the add button for email addresses can get cut off... quite nicely I might add. The field where you then put in your address re-centers itself under the Notifications Settings list leaving no hint the the existence of said button. I spent several hours trying to set up notifications to no avail without the existence of that button. In fact I had composed a lengthy forum post looking for help. Before submitting the post, I had the idea to maximize my AC window, as all the research I had done on the forum and Wiki kept talking about this "Add" button that I could not find! Well of course there it was when I used my full screen resolution. I know that this post exposes me as a bit of a novice user, but as I have said before, I think it is important to keep the novice users perspective as that is by far the broader market. If I could get this confused, I am sure others in the future will experience the same thing.

Added four motion detectors last night. No status bar came up when linking, but they all seemed to get added to the system just fine. I think I used to get a status in 2.6.8 when I added motion detectors. I do not know if this is the same issue others are seeing or another unique problem.

Thanks Rand, I will keep the repeating names on the programs that are not called from other programs then. I like symmetry. Thanks for the quick reply, as I am working on this tonight.

I was noticing that when I try to have a program interact with another program, there is no path tree. I take this to mean that all my programs should have unique names throughout the program tree. So no naming a program "All On" and having a different version of this in each rooms program folder, at least not if I am trying to have other programs call this program. Am I thinking right here?

Now that I am programing with my new motion detectors, I notice that lots of buttons in the "Program Detail" page are truncated like "move line up" and "add to then" etc.

Hey, Am I crazy? I seem to remember the Event Viewer showing the items name, like [Front Porch Flood] but as I look at it today it shows [ A 82 17 1] which is not nearly as convenient for me. Did I do something to change the way the info is displayed and can I get the labels back? Is this a result of upgrading to 2.6.11? Or am I just crazy and remembering something that was never showed labels?

My four buttons in the "Manage Programs" square under the list of programs in the "Program Details" page of the administrative console are cut short. They do not expand as I expand the divider and I cannot see what they are supposed to say. I had this problem first appear in 2.6.6 and I have it still in 2.6.11 I am using a Mac and the problem persists with Safari and Firefox web browsers.

Okay, so I guess that issue was a compelling enough reason to jump on the beta. 2.6.6 and all is well. It does everything I wanted to. Darrell, I would not say that 2.6 was properly managing my 1.65 KPL. In light of how quickly the KPL responded properly with 2.6.6 I would say that in fact 2.6 was not interfacing well with the 1.65 KPL. While it did turn some lights on and off, sub button programing with the KPL Load in it never worked even close to right. Thanks for you help everyone. Now I guess it is time to figure out how to talk to this box from the internet. I am off to give myself an education.

The KPL in question is v1.65. I removed the cover plate and confirmed this. I did a factory reset and restore on the KPL with the same results. Pressing the KPL.C "all off" button tuns off all loads and the LED load indicator on the KPL but not the KPL primary load (the actual light). I removed the KPL load from the scene and manually tap linked the KPL.C secondary button to the KPL load and everything works fine for me this way. The KPL.C turns off the load as I wished. The only problem with this arrangement is that the ISY and the real world are not in sync, and of course now I cannot use the restore function on that KPL or I will loose control of the local load. Michel, I can confirm that I do not have a slider for the load when the sub button is selected. Of course now that I have removed the load from the scene I am not supposed to, but before I pulled it out, I re-confirmed that I had no slider for the load.

Yea, I have sliders for the other devices. I have the slider for the KPL Load in the Scene (the one that occurs when the ISY triggers the scene) just not in the list when the secondary button is selected. I guess I should mention... I am running v2.6 of ISY. I know all you guys grab the betas the minute they come out, but this has been working fine for all my purposes so far.

Two issues with that.... 1, I have no slider for the load device of the KPL in question. 2. Even if I had the slider, isn't that the "On" level. When I turn the scene off, why would the light go to the on level?

So if it is a v1.65, how would I assign a 2% level to the off function?

I think we may be misunderstanding each other here. I want the light to turn off when I use the all off button. It is not turning off. All I want to do is have KPL.C be an all off button that includes the KPL Primary load. Are you saying that that is not possible on a KPL below version 1.6? It is a version v.2C in the ISY. If you need the actual version number I will have to pull the switch plate.

I made a scene called "All Off" I selected the KPL primary load, the KPL.C secondary, some switchlincs, a swithclinc relay, an appliancelinc and added them to the scene. I made everything a responder except KPL.C which is the controller. I set KPL.C as non toggle in "Off" mode. I use the KPL.C button. All loads turn off....Except the KPL Primary load? I restore device. Same results. I air gap the KPL for 20s. Same results. Interestingly, the KPL main load indicator LED goes to the "Off" position when KPL.C is pressed. Sometimes in the ISY GUI it shows as "Off" even though the light connected to the KPL is still on. I should be able to do this, right? I understand that I cannot assign a different ramp rate and level from the local settings, but the light should still be turning off at the local rate, right? There is no such thing as a "Off" level, is there. It almost seems like the KPL has a 100% off level when the KPL.C "All Off" button is used.

I was under the impression that when you run a program from the Program Summary page that the 'Then' path was executed immediately regardless of conditions; however I am not finding this to be the case. I have programs that reside in my "Security" folder which houses all of my "Away" programs. If I try to test programs in this folder by using the 'run' or 'run else' commands the programs will not execute unless the "Security" folder condition is met or I first use 'Run' on the folder condition. While the status does change to "True" the "Running Then" only appears for a split second before going idle, even on long running programs. Is this the normal operating condition?

The 2 second random is because I have lots of lights using this template. If two off (X-10) requests happen to coincide the ISY will try each again at a slightly different time. Oh, wait! The only way two X-10 signals can collide is if they are sent from different transmitters simultaneously, and that can not happen here because the ISY uses only one transmitter. Doh... Okay that was pretty stupid. I will take the random 2 sec out when I clean up my start times and repeat 15 times. Thanks for getting back to me. I did also notice that in the end I ended up with almost exactly what you had posted earlier in this topic. Sometimes the ISY is so powerful with it's command set it can be hard to think about how little needs to be coded. Reading that post the first time I guess the power of those few lines did not sink in. I had to go the hard way myself to understand. The first version of my "Away-Look" template had each on and off cycle written as a separate line. After getting my head around it I have ended up with this very simple looking code that does exactly the same thing with 90% fewer code lines.

Thanks Chris. That is what I thought after sleeping on it. Thanks for the confirming this.

If From Sunset + 20 minutes To 2:00:00AM (next day) Then Wait 20 minutes (Random) Set 'Bathroom Vanity' On Repeat 15 times Wait 20 minutes Wait 20 minutes (Random) Set 'Bathroom Vanity' Off Wait 20 minutes Wait 20 minutes (Random) Set 'Bathroom Vanity' On Else Wait 15 minutes (Random) Repeat 3 times Set 'Bathroom Vanity' Off Wait 2 seconds (Random) I am trying to refine this code. This is the template for my "Lived -In" away look. I have a program similar to this for each light that is part of the away look. Questions: 1. Is the 2.00am (next day) the proper code for this program to go false about 6 hours after going true (in the summer anyway)? 2. Could I change the repeat so the code would be: If From Sunset + 20 minutes To 2:00:00AM (next day) Then Wait 20 minutes (Random) Set 'Bathroom Vanity' On Repeat Every 0 seconds Wait 20 minutes Wait 20 minutes (Random) Set 'Bathroom Vanity' Off Wait 20 minutes Wait 20 minutes (Random) Set 'Bathroom Vanity' On Else Wait 15 minutes (Random) Repeat 3 times Set 'Bathroom Vanity' Off Wait 2 seconds (Random) I feel like this will not repeat at all (the repeat 0 seconds scares me), but from Chris' example this should work, no? I like the repeat every 0 seconds as I do not have to put a large repeat in there. I know that with a 15 times repeat it will work, but again I am trying to refine my programming. Chris, so 'repeat every 0 seconds' is nothing like 'repeat 0 times'? I know from reading other posts that 'repeat 0 times' effectively comments out programming lines, but are you saying that 'repeat every 0 seconds' does not? The wait 2 seconds (Random) at the end is for the X-10 lights mostly as I use this as a template for all my lights that I have not yet converted over to Insteon. This way if there is a transmission collision with another command the request gets resent. Oh, even more refined! Looking over my post I think I could change the code to be: If From Sunset To 2:00:00AM (next day) Then Repeat Every 0 seconds Wait 20 minutes Wait 20 minutes (Random) Set 'Bathroom Vanity' On Wait 20 minutes Wait 20 minutes (Random) Set 'Bathroom Vanity' Off Else Wait 15 minutes (Random) Repeat 3 times Set 'Bathroom Vanity' Off Wait 2 seconds (Random) This would do exactly what the first set of code did but with much less programming, right?

If Time is 12:00:00PM Or Time is 1:00:00PM Or Time is 2:00:00PM And Status 'Bathroom Sink Heater' is On Then Set 'Bathroom Sink Heater' Off Else - No Actions - (To add one, press 'Action') If it is not clear, what I am trying to do is turn off the IR Sink Heater if it has been left on. I have the ISY looking at this three times a day. If it has been left on at any of these times I want the ISY to turn it off. Do I need Parentheses around the 'OR' arguments? I know that it will work with them there, but will it work without them there?

Why couldn't deeepdish use the Darrell method of timing of key presses with X-10 except this time with insteson? Check out this link: http://forum.universal-devices.com/view ... ht=palmpad I feel like this would work, no?