oberkc

Agree. Linking and creation of basic scenes can be learned by most pretty quickly.

I believe most people will be able to learn to use it, regardless of computer programming background. Ironically, the ones who have computer background and assume that the ISY statements and programming are identical to background are some of the ones who seem to have the most trouble. While there are some that complain it is too hard for the average person, my conclusion is that such complaints are more about the time that it takes to learn, rather than not having enough brain power. Yes, it will take more than a few minute or an hour to set up. Yes, it is more complicated than setting the time on a VCR. Yes, it can take time to become proficient. If, however, you have a few hours for a few evenings, I expect you will be fine.

Green is good. I believe it also good to check the opposite direction. Initiate the test from the first floor lamplinc and see if your PLM shows green. The KPLs and IOLinc may not be dual-band, so no indication expected.

I suspect you will find this not to be true. Having your keypad as a responder in one scene and controller in another is fine. Responding to one scene will not cause the scene in which is controller to trigger.

No need to guess. Furthermore, even if you correctly identify the legs of you electrical system and confirm devices on both, how do you know they are communicating prerly to perform this function. Better is to break out the manuals for your devices and look for instructions on performing the phase bridging test. This will give you a positive confirmation (or not). As far as I know, it is the only way to have near certainty that your devices are communicating across legs of your electrical system.

Sure sounds like some type of interference to me. Hopefully, it won't come back. Were this me, I would be trying to identify the cause and eliminating.

I used the insteon morninglinc with the matching lock set. I now have a z-wave lock. I prefer how my z-wave lock, unlike the morning lock, sends out status changes. I also find the z-wave lock to respond more reliably (near 100%).

very odd. I wonder if, during the two-second ramping, that the dimmed load was causing some type of interference. If you are up for an experiment, you could temporarily remove the loads, re-apply the 2-second ramp rate, and see if the problem remains gone.

It works because when a device is in a scene as a "controller", it is, by definition, also a responder to any other controller in that scene. When you have two devices as controllers in a scene, each device controls the other, and each device responds to the other. Also, when a scene is created in the ISY, there is an unidentified controller in every scene...the ISY, itself. So, when you activate the scene from mobilinc, it is as if the ISY is the controller and every other device responds.

Latest version is 4.18. I thought you had v4.0.5?

Yes, indeed, a program can activate a scene. I see no reason the ISY cannot do what you want. Write a program: if status "insteon bulblinc" is not off set "scene" on else set "scene" off

The oven being on is not conclusive, unfortunately. It was a good thought, however. (especially true if your oven is not electric) My suspicion remains a lack of insteon communication across electrical "phases". How many insteon devices do you have, and how many are dual-band? Is your PLM dual-band? How new is your 2477D switch? You may want also to update your ISY software to the latest version. Perhaps the switch is too new for your current software to recognize.

In addition, the only test I know to isolate RF v Powerline is to perform the phase bridging test (forget exact name). Typically, this involves putting one device into a broadcast mode, initiated by four very-rapid presses of the set button. From there, observe the response of other dual-band devices. Depending on device, you are generally looking for at least one green LED indication. The ISY also includes some scene tests to guage the quality of communications. Run a couple of times to be sure, on various scenes that you have. Make sure programs are not being invoked as a result of status changes of any included device. (Temporarily disable, if need be.) Intermittent operation is, in my mind, a sign of marginal communications. I do not believe your problem is an "ISY problem", rather, a more general "insteon" problem.

If it is an active repeater, probably not. If passive, probably yes.

Oberkc, can Zwave devices can be added to insteon scenes? Worked for me. I did a quick test, but nothing thorough yet.

I agree with digger. I believe the venture into Z-wave is HUGE. The future of controllers, in my mind, is with the integration of various protocols, such as z-wave and insteon and elk, etc.... The network module, for those able or willing to learn, is a major part of this. In fact, I just added a new z-wave module this morning to replace an insteon lampling the was killed when I changed a light bulb(!?). I added the module to my existing network, and to a scene with a bunch of insteon devices. Painless. Flawless.

Controlling the scenes is, I believe, the proper course of action. Controlling individual devices, even if scene controllers, will not result in responders activating. If controlling a scene from mobilinc does not cause all responders to react as you expect, double check the responder ON levels, at the SCENE level. Make sure they are not zero.

On the other hand, were it not for the ISY, I probably would not have purchased so many other insteon devices, so smarthome wins here. I assume this is a mutually beneficial relationship. Yes, as suggested by others, this cannot help but degrade the perception of insteon.

Yes...not smartHOME...smartLABS. I thought smartlabs was entirely focused on insteon. Maybe I was wrong. But whatever the case, yes, UDI should purchase INSTEON.

I was thinking, instead, that UD should buy smartlabs.

When changing through this ISY, ensure there are no little green or red symbols next to the device name. This could indicate that there are updates to be written to the device.

You will have to confirm this in the sensor manuals, but I was thinking that the sensors can be configured in 2-scene mode. In this mode, one scene is turned on when the sensor is open, and the second scene is turned on when the sensor is closed. I wonder if this mode could be used effectively here...use one scene only to turn on the lights (don't link the lights to the second scene), and use a program to turn the lights off, triggered by an ON command from the second scene of each (both) sensor. I have attempted none of this, and don't have any of these hidden door sensors, so I could be off track here.

Perhaps a bug. I don't know. It works for me, but sometimes I must try a couple of times. One thing that helps me is to turn off the automatic write function until all changes are defined, then turn the write function back on...programming the keypad all at once.

It sometimes takes a while to write a lot of changes. The little green symbol suggests that there ARE changes to be written. Right click on a device and choose "write changes". Keep trying if it fails once. Repeated failures to write suggest, in my mind, communication difficulties.

I am a fan of user manuals. http://wiki.universal-devices.com/index.php?title=Main_Page#ISY994i_Series