oberkc

It shows 352 links. I don't know if that is good or bad. I am starting to see a couple devices get out of sync, but am not sure if this is the result of my recent power interruption or something else. I will continue to watch these devices and restore those that continue to be a problem.

At about 830 last night, all (most actually...a couple stayed on) turned off. I have no programs set to run at that time, so I was a bit surprised. In an attempt to diagnose the problem, I tried logging onto "My Lighting" based on the memorized shortcut from my desktop (the one I always use). No good...error. I then went to my bookmark from the UDI site and "find ISY". This found the ISY, but no devices or programs or login appeared. I then unplugged the PLM and, after 20 seconds or so, plugged it back in. Suddenly, all appears to be working normally again. Some, but not all, of the lights normally on at this time of the day even came on again. At no time did I see any unusual LED indication on the front of the ISY. The log shows no event at the time the lights went off. Any ideas what this may indicate, if anything. Should I be ordering a spare PLM?

I have a couple of override programs, but they are intended simply to delay the automatic turning of lights off at the end of the day. Adding this condition is relatively straing forward.... if time is 1100p and status "keypad button" is off then turn lights off Alternatively, you could create a folder with the keypad off being the folder condition. That is the easy part. The more interesting part is what you want to happen when you turn the override button off. Do you want it to revert to the condition it would be in were the program executing on the normal schedule? Another question to answer is what you want to happen when you turn the button on, with the lights (or heater) currently off. Do you want your device to come on? If so, perhaps you could consider like a conditional program such as: if time from xx:xx to yy:yy then else Then add the next two programs maintain, or revert back to, a scheduled condition: if status "conditional program" is true and status KPL button is false then turn lights on else and a third program: if status "conditional program" is false and status of KPL button is false then turn lights off else Then adding, perhaps, a fourth program to ensure that the light (or other device) is on any time that the override button is on: if status KPL button is true then turn on light else I suspect there are more elegant solutions, but something like this should work and I don't have enough brain cells to quicly figure it out.

That is also consistent with my recollection, but a more authoritative source would be better.

I understand that there are hardware versions and software versions, and that it is the version that shows up on the ISY amin console that should give you concern if it is v35. It sounds like you may have an issue with the v35 devices.

Without explanation of the difference between control and status, I suggest the following changes to your program: If control 'Front Door Walkway - Sensor' is switched On and Status 'Front Porch Light' is 30% Then Run timer program (then path) Else -No Action Eliminate the second program and keep the third and fourth: If Time is Sunset Then Set 'Front Porch Light' 30% Else -No Action If Time is Sunrise Then Set 'Front porch Light' Off Else -No Action Create a program folder, where the conditions are: if From sunset to sunrise (next day) Then run the programs in this folder In this program folder create the "timer program" referenced in the first program: if then Set 'Front Porch Light' On Wait 10 minutes Set 'Front Porch Light' 30% else One problem may occur....if the front porch light is manually controllable, this whole scheme can fall apart if someone comes along and dims or brightens your light. For example, if someone comes along and dims your light to something less than 30%. All of a sudden, your program will never evaluate as true (until manually set to 30% or next sunset). If such a possibility concerns you, you may consider an alternative to your first program: If control 'Front Door Walkway - Sensor' is switched On and Status 'Front Porch Light' is not off Then run timer program (then path) Else -No Action I hope this works out for you.

OK, so the light brightens (suggesting that the program executes) but does not dim back (suggesting that the program halts execution). I note that your program still relies on motion sensor "status" rather than "control". I think changing to "control" will (as suggested by J0rdan) will solve most of your problems. I expect that you will still have a potential problem at sunrise. I will provide more detailed program suggestions when I get more time.

Who are "They"? Did they tell you how to control speed? I see nothing on the fantech web page suggesting anyting with regards to insteon. Since you did not say which particular model of fantech you installed, I can only assume that this is some type of electric motor-driven device. My understanding is consistent with Brian H: there is no insteon device rated to control speed of inductive loads, such as an electric motor. You could use a relay to control on and off only. Any of the insteon relay devices would work, assuming that they meet the needed power ratings. You could use the ISY to automate on-off cycle times.

I think this would avoid the problem of of the sensor time-out. This sounds like a good idea to me. You may help with troubleshooting by describing your symptoms. How does it "not work"? Does it not turn on? Does it not turn off at dawn (do you want it to)? Does it not revert to 30% after ten minutes? I see two areas of concern with your program, and j0dan has hit upon one: if your motion sensor status changes to off before the ten-minute wait, then the program will cease execution of the "then" statement and begin execution of the blank "else" statement. I expect changing "status" to "control" will solve this problem. The second area of concern I see is if motion is sensed within ten minutes of sunrise. If your progam is in the ten-minute wait period when sunrise occurs, the program conditions will trigger and become false, and your "else" statement will cease execution before turning the light back to 30%. Do you intend to keep the porch light on all day at 30%? Do you have another program which turns it on (30%) at sunset and off at sunrise? There are relatively painless ways to solve your problems. I have found good value in looking at the wiki, and specifically, the write-up about motion sensors: http://www.universal-devices.com/mwiki/index.php?title=ISY-99i/ISY-26_INSTEON:Using_X-10_Motion_Sensors If you care to add a bit of detail regarding what you expect to happen that is not, I am sure someone here can offer a solution. Please include what you want to happen to the porch light at sunrise and sunset (do you want the porch light to turn off and on, respectively?)

I think this would avoid the problem of of the sensor time-out. This sounds like a good idea to me. You may help with troubleshooting by describing your symptoms. How does it "not work"? Does it not turn on? Does it not turn off at dawn (do you want it to)? Does it not revert to 30% after ten minutes? I see two areas of concern with your program, and j0dan has hit upon one: if your motion sensor status changes to off before the ten-minute wait, then the program will cease execution of the "then" statement and begin execution of the blank "else" statement. I expect changing "status" to "control" will solve this problem. The second area of concern I see is if motion is sensed within ten minutes of sunrise. If your progam is in the ten-minute wait period when sunrise occurs, the program conditions will trigger and become false, and your "else" statement will cease execution before turning the light back to 30%. Do you intend to keep the porch light on all day at 30%? Do you have another program which turns it on (30%) at sunset and off at sunrise? There are relatively painless ways to solve your problems. I have found good value in looking at the wiki, and specifically, the write-up about motion sensors: http://www.universal-devices.com/mwiki/index.php?title=ISY-99i/ISY-26_INSTEON:Using_X-10_Motion_Sensors If you care to add a bit of detail regarding what you expect to happen that is not, I am sure someone here can offer a solution. Please include what you want to happen to the porch light at sunrise and sunset (do you want the porch light to turn off and on, respectively?)

Unless there was a recent change that I missed, I do not believe a scene command or status can be used as a condition in a program.

Are you speaking of accessing your ISY outside your home network? have you enabled internet access? When you do so, a window will pop up giving you the address. I recall, also, that address being available under the configuration tab. You can't get to the admin panel, but you can see your devices and programs, etc....

Like sub-routine, I use sunrise and sunset. One could also use motion sensors (with built-in light sensors) to transmit a signal when "dark" to trigger the lights to come on. I understand that weatherbug also includes a configurable dark parameter which could be used to trigger lights (requires the weatherbug module).

No. This would be a code violation. If dimming is required, the plug-in modules are your only option.

That is probably the best way. Scenes are not avaailable as program conditioms.

Looks good to me. I don't believe so The two options of which I am aware would be motion sensors or weatherbug data. Motion sensors generally have light sensors. Weatherbug data requires the additional module, My gut sense would be that weatherbug data might work a little better, in that I understand that you could better define "dark", using some scale (0 - 100?). On the other hand, depending on where you live, you may not have a good source of data close by.

Your program condition will evalate at these points. The results will be dependent on the entire set of conditions of your program. If this is the only condition in your program, then it will do as you say.

I agree. The programming would likely be pretty straight forward. if status "pump sensor" is on then wait duration of time notify else Unfortunately, I have no direct experience with any 220V sensor.

Just in case this has not been clear to you, scene settings (on and ramp rates) can be different, depending on which controller is initiating the scene. In the ISY admin panel, look at the device tree. Choose the scene, itself, and confirm the settings. These are the settings when controlled by the ISY, such as manually or from a program. Now click on the controller keypad device button within that scene. Are the scene settings the same? These are the settings that will govern the response when initiated by the keypad. Check the setting for the light in question.

The fact that you were successful with one tends to rule out procedural issues. In my mind, this leaves hardware failure (batteries?) or communication problems. Assuming that you do not have a hardware failure: How much farther away is your second triggerlinc from an RF reciever (access point, dual band device) than the first? Do you have more than one RF device and are they on two legs of your electrical system? Have you tried locating the triggerlinc near the first, to see if you could link from there?

I generally find an outlet behind the bed and use extension cords, as necessary. Hopefully, you have such an option. What are you using as controllers?

Plug both into the same module?

It sounds like you have the bug. We may have to start an ISY-anonymous.

This sounds like one of those pesky PLM problems. Besides unplugging and plugging back in, I cannot help much. Be sure cables are securely connected, and in the correct places.

I believe it doesn't matter. I think the IOLinc has terminals for both possibilities, so you simply connect your existing sensor to the terminals that work for you.