Illusion

Thanks Darrell, I did search the forums and did not find that info. The Wiki had not occurred to me. I will check there first before posting a question next time.

ISY-26 here. How many characters can the password and or username be? Is caps allowed and relevant? Are symbols allowed? I am trying to change my password to an 11 character and I get an error of <,> not allowed. There is no "," in my attempts. I am a little hesitant to just try different options as last time I had to reset the password and username in the ISY via Telnet because it took one and I could not figure out what had happened and could never figure out what it was looking for. I did notice that with this new version (2.7.5) it shows what I typed with a dialog box before submitting it. Much better.

Guy, I have that $100 X-10 fan control and it is GREAT! The only waste of money is the fact that it is X-10, tuff to include in scenes and the thought that an Insteon fan control may come out. I am hoping for one myself.

I am trying to get this. Simple example. I have a table lamp, it is linked to KPL.D. It also is part of an all off scene and a movie lighting scene. The all off scene is KPL.C in non toggle mode and will turn off all the lights in the Living Room regardless of what is on. The movie scene is triggered by a RemoteLinc.5 It seems to me that I should track status with a program in the ISY but this post by Michel makes me wonder if I am missing something more elegant. I tried putting the KPL.D in the movie scene as a responder, but that did not work as the table lamp has an on level of off for the movie scene, and the KPL.D gets turned on then. Is it different if the KPL.D is a Controller vs Responder? Can a KPL secondary be a controller of more that one scene?

I have spent the better part of a day working on my Verizon Fios Actiontec MI424-WR modem/router. I have several thoughts I would like to share as this thread was tremendously helpful and I would like to add to it. I am not sure that a static IP address is necessary with this router. The first screen you come to when you attempt to forward ports is "Add Port Forwarding Rule" Rather than specifying an IP address on your network to port forward to, this router allows you to specify a device. If you specify a device (the isy) I believe the applied port forwarding rule created will follow that device to whichever IP address the router assigns it. This is how I am doing it now and it appears to work flawlessly. First off, Sloop and Michel, I think there is a much easier way of accomplishing this. I have read the instruction manual for this router and have come up with this: If you simply select "HTTPS - Secured Web Server" from the protocol drop down it creates a rule: "TCP Any -> 443" the exact rule created by manually adding a server port as Sloop did and I did initially. This further buttresses the claim that the source port needs to be set for Any. Michel, I think setting the source port to any at this point does not in fact create a DMZ Host. While I am not clear what this function is for in this router, I found a preexisting rule for the local host and it included any as its source port... in the server port subsection, not in the parent port forwarding rule. You still have the selection "Forward to Port:" set as "Same as incoming port" in the rule. While all this is a bit confusing I think setting the isy up in this router could be as simple as a couple of steps. If you have an isy with the default port of 443 still set and set for DHCP I think all you need to do is connect it to your Actiontec router, let it get an IP address and follow these steps: 1. Login to your router 2. Click Firewall 3. Click yes 4. Click Port Forwarding in the left hand Navigation screen 5. Click the add in the bottom left of the screen 6. Select the ISY in the "Networked Computer / Device:" drop down menu 7. Select the HTTPS in the "Protocol" drop down menu 8. Click Apply This will create a rule that should chase your isy. The rule created will be identical to what Sloop made, but the server port settings will be put in by the router. No need to set the isy to a Static IP, no need to configure the router to deal with a Static IP, no need to specify server ports. And now on to the issue of Dynamic IP from the ISP: It appears from the manual that this router will update http://www.dyndns.com/ if you use that as you DNS Hosting site. In the advanced settings you simply select Dynamic DNS and input your DYNDNS account info and wamo, you have an updating account without any client having to run on your computer. I just did this yesterday, so we will see how it works when Verizon changes the public IP. I have my fingers crossed.

Gary, I am getting ready to drop a bunch of money with Smarthome on the Venstar 1700 insteon thermostats (20% off sale). I cannot tell what features the ISY supports without adding the device. Are you saying that the ISY cannot poll the information the thermostat receives from the outdoor sensor? If that is true I will save the dough on purchasing the outdoor sensors as ISY integration would be the only reason I would get them.

Rand, I do not have a ISY capable of the Weather Module, but am considering getting one. Am I reading you posts correctly that the module receives current data, but not predictive data. For example, one of the things that would justify the expense and hassle of changing my system to a new ISY would be knowing that it is greater than 70% chance of rain tomorrow or going to be high humidity, or low temp, so do not allow the sprinklers to run today. Or it is going to be really cold tomorrow, even though it is really hot right now, so do not crank down the AC, just wait. The way I am reading your post, this is not supported, and the data is not even there. Am I correct?

Okay Michel, I will accept that this is "fixed". I had a hard time accepting this. I have tested this for two weeks since installing 2.7.1 and the chime only has double sounded twice, which I suspect was do to X-10 issues. I have not seen the double command sent by the isy in the event viewer since upgrading to 2.7.1 While I know this puts this issue to rest with you {since there is no longer a problem} if someone else is reading this and can satisfy my curiosity I still would like to hear your thoughts. If you read the previous posts carefully, you will see that the trigger for the isy sending the second, undesired X-10 command was an if then program in the isy that had nothing to do with the program that was supposed to send the single X-10 command, except that the program in question was called from the same program that initiated the X-10 command. I am stumped, and it took me a long time to even find this association, but when I did it was a 100% correlation. Michel, thanks for fixing this issue. See that, I did not use quotes there, indicating that I really am coming to terms with this being a fix.

Have you had any luck reproducing this? Even if you do not have a fix, I would like validation that I am not crazy.

More data points for analysis: I changed Front Porch Motion On to: Front Porch Motion On: If From Sunset To Sunrise (next day) And Status 'Front Porch' is not On Then Set 'Front Porch' On Else - No Actions - (To add one, press 'Action') Now if I trigger the motion detector after sunset, the isy only sends the second X-10 F3 on command set if the porch light is not already on. If the porch light is off I get the two distinct command sequences sent from the isy and the chime sounds twice. If the porch light is on, the isy sends one command sequence and the chime sounds once. So it is the actual act of turning on the porch light that seems to be causing the isy to send an undesired second command set. Why in the world would altering a downstream program that has nothing to do with X-10 have such an effect as causing the isy to send multiple X-10 command sequences in another upstream program? Chris Jahn Help!

Michel, No, the dusk/dawn feature of the detector in question is disabled via the jumper. The detector is active 27/7 I think we have a bug here, or at the very least an anomaly. Last night I did some troubleshooting. I removed the line Run Program 'Front Porch Motion On' (If) from Motion-Front Porch and triggered the program after sunset by moving in view of the detector, and the chime only sounds once. The event viewer confirms that the isy only sent the F3 command once. If I put that line back in and trigger the detector after sunset the isy sends two F3 on command sequences. (Of course sunset is subjective here because for testing purposes I am altering the internal clock of the isy to facilitate daylight hours testing.) The system did not used to do this per my memory. This anomaly started with the betas somewhere around 2.6.13. That is not a hard and fast fact though as it is only now that I understand when the double chime is happening. It took me a while to figure out that it was only after sunset. One more data points for analysis: The chime will not occur twice if the program is trigger from the program menu. It must be triggerd by the if statement being made true via the motion detector seeing motion.

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.