sfhutchi

Thanks for the info. I am not familiar with I2CS, but a quick search seems to imply that this is part of some of the newer devices that I have. In my situation, I have some buttons that drive scenes on the latest Keypadlinc. If I understand correctly I can update the number of retries for devices within the scene? Anyone have any experience... good, bad, or indifferent to playing with these settings?

I recently upgraded to a 994 and am looking for a basic overview of the 'retry' function. I guess that this may have been there in the past, but I never stumbled across it. Specifically is it something that can help the reliability of scenes or other functions. I periodically have issues with a device or two in a scene that doesn't respond to a scene command or something else. Does this simply send the same command multiple times or is there some type of acknowledgement signal that the device sends? I also see some information in the wiki about Group Clean Retries. Does anyone have a dummies overview of these functions? When they should be considered? How people are effectively using them today? etc? I assume that there is a performance tradeoff so are there any rules of thumb about when to use them? Steve

I had a dead PLM, and had to do an ISY restore to get everything working again. I first tried a Restore Modem, but the ISY didn't recognize any local changes. I then did an ISY restore again (within a week's time frame) to upgrade to the 994.

I recently restored my device and my scenes list the responders, but only show the settings for one responder. In other words, if I have 5 responders to a scene, I can only see the settings for one of the 5 devices rather than all 5. I can recreate the scene, but I am hoping that I don't have to do this on all my scenes to get them back to working properly.

To be honest, I haven't made it a priority. I have an unused Zwave light module that I can trigger with my alarm system... but haven't gotten around to buying an insteon module to plug into it as a trigger.

Good suggestions. Thanks. I am just looking mainly for status... I will also look at imeter to learn more about it.

My alarm panel (not tied into my Insteon setup with ISY) can output to ZWave devices. I would like to figure out a way to get a notification to my ISY configuration when the system is armed, disarmed, etc. Has anyone come up with a low cost way to provide a bridge? I was thinking about plugging a Zwave light module into an Insteon SynchroLinc with some load (probably a light). This way I could detect the change driven by the Zwave device and use this for my input on the ISY. Not a very elegant solution... but it might work. Any other ideas or suggestions? I am guessing that others have been in this same situation.

My understanding is that Universal Devices has abandoned the floor plan feature and has only left it for backward compatibility with some 3rd party applications. My feeling is that if it is not going to be developed further, than it should be pulled from the current releases. I agree that it gives a bad impression and appears to be a half-developed feature. For a new user it may look like something with potential but previous notes have said that it is being phased out.

Are you getting good coverage in your bathroom with this setup? I am thinking that we need something more reliable like ultrasonic or some type of rf field disruption to be reliable. Unreliable motion sensing in a bedroom or a bathroom is really a nuisance.

I implemented a delayed start on a fan in a guest bath that my wife doesn't use... This way it doesn't seem to bother her. It seems to work well. If the bathroom light is one for 5 minutes or more, then the fan turns on. A separate program will turn the fan off it has been on for 15 minutes. This way if you turn it on manually, it also will get turned off by the same program. If the user turns the light off and leaves before 5 minutes, then the fan never comes on.

I like your thought about using the time of day to determine whether someone might be using the shower. Very creative.

That is interesting. I have been using this for years. It works great for sunrise type scenarios in a bedroom or a bathroom. Actually it would be nice to even go longer. I have a morning scene in a bathroom where I start at 20%, then go to a 9 minute ramp from there. Worked very well until I had to replace a broken Switchlinc. I guess the 1 minute won't kill me, but it is noticeably quicker. Yes. I think that this would be an appropriate solution for now. At least you don't get thrown for a loop like I did when the '9 minute' ramp setting seems to be written to the device, but you then see the opposite.

That is interesting. If that is the case, it seems that some logic should be built into ISY to handle this (not allow 9 minute ramp rate on these switches).

it is a Switchlinc . The scene is called directly from a program. I just tried it with an 8 minute ramp and it seems to work. I'll keep testing because it isn't clear why 9 minutes won't work.

I have a scene: Very Slow Master Bath Light - One responder (Master Bath Light) - 80% at 9 minutes When I call this scene it goes to 80% at what appears to be the local ramp rate (or a few seconds). I deleted this scene and recreated... and get the same thing. I had this scene working with a different switch in the past. I have since changed out the switch and now can't get the scene to work. Any ideas?

Add another vote for interest. Would run on an HTC EVO. Great to see the continued active development for ISY interfaces.

Thanks for the pointer. This worked well to let me know what each was. Maybe one of the guys from UDI knows how to sort them... or why they get out of order. I have never seen this before (that I noticed).

Once I renamed all my buttons on 8 button KPL, how do I tell which one relates to which button (physically). In a new KPL I installed, the first one is the load, but the others are not sorted properly. Is there a way to see the underlying address? Is there a way to have them sorted properly? For what it is worth, if I look under 'Buttons Grouping', there is a different order, but that is wrong also. I am thinking about removing the KPL again and re-linking and then rebuilding everything, but I am wondering if I will see the same thing again and only have wasted more time. Any ideas.

This is probably good advice. I still need to have dimmable lights, so I likely won't go with CFLs, but I may have to back off on some of the motion sensing activity. The occupancy sensing is just too unreliable.

Probably a dumb question... but how did you complete this trial and error? Did you have one person on a ladder holding it while testing... or did you find a way to temporarily mount the sensor?

Thanks for the pointers.... Couple questions. You said that if you are up and stay up, the lights turn on at 75%, otherwise they turn on at 30%. Are you saying that if the light is already on or are you saying that it turns on at 75% because you have some other logic to determine that you were already up? You also state that once motion turns off you resume the previously programmed levels. Are you stating that you are somehow recording the manually set level or are you simply returning to a programmed state that you had for that time of day?

I am sure that many of you have dealt with this... The wife has generally tolerated most of the tinkering and programming of the lights over the past few years. In general, I tried to keep the manual controls as common as possible to 'standard' light controls, but added other functionality. The biggest challenges were the automated time-outs for lights that may have been left on. Sometimes this caused some frustration but nothing major. .... Then I decided to get into motion sensors. Let me just say that it is not going as well as expected. Maybe because I decided to tackle the master bath first. I started by using the motion sensor as a method to turn the light on in the evening and also in the middle of the night (at a dim level)... and then after a period of time with no motion... turn the lights off. My wife feels helpless without having direct control because while I think that 40% at 2am may be good, she wants 100%, etc. Since the program has no way of knowing what level the light is at, it forces things back to 40% if that is what I have specified at that time. Little by little, I am making some improvements (e.g. enabling and disabling the motion programs based on manual input), and will soon implement some flags to try to get an idea of whether the light was manually turned on.. or if it was on by motion... etc... ..But I figured some of you have gone through this already and have some more ideas of what may work better 'out of the box'. As a side note, I clearly have some problems detecting motion while someone is in the shower and sometimes sitting at the mirror fixing hair, etc.. How have others dealt with this? I am actually considering another motion sensor over the shower for the shower situation, but I am not sure that this will do it. Unfortunately, the system can't know the intentions of the person entering the bathroom. Are they simply going in for a quick walk to the closet, going to take a shower, going to the bathroom, etc.. Possibly the answer is good options to override the programs with one or two button presses if you are outside of the 'standard' time schedule.

Oops. I wonder why I didn't think of this. I have a program that temporarily disables and then re-enables the motion based programs if the switch is manually adjusted. Thanks for setting me straight. Steve

I have a program that I have disabled, then a day or so later it is re-enabled. I disable again... and then the same happens. I don't recall seeing this happen in the past. Any ideas what to look for? Steve

Excellent. I'll give it a try.