lilyoyo1

You only need an off to turn off the button that you are controlling. If you look at how I set the scenes up, you'll see the other buttons are configured to turn off whenever the controller is turned on. How you turn off the controller depends on what you are trying to accomplish. That's why I included examples of how I use mine. To help you understand the differences ways.

Older devices aren't as capable as newer devices but it shouldn't matter overall. The writes to those will be much slower as i1 isn't nearly as quick as i2cs. The way I set my scenes up are as follows: A- Controller- Default B- Responder- off C- Responder- off D- Responder- off Other devices- desired state A- Responder- off B- Controller- Default C- Responder- off D- Responder- off Other devices- desired state The same applies for the rest of the buttons. Depending on what the scene is for is how I determine how I'm going to use programs. For example, my all off scenes turns everything off. Using a program to turn the scene off isn't a big deal. I'll just have a program turn the same scene off 2 seconds after it's triggered. While I could get away with 1 second, the extra second is there to ensure all other communication has stopped. However, if I have lights that turn on for whatever reason, I'll create a separate scene and add that button as a responder. This way, the lights I want on will stay on even though the kpl backlight gets turned off. An example of this is my media room. My all off button isn't directly linked to everything. Instead I created a program with everything as responders. During the day, hitting the all off will trigger my off program setting the scene off (includong the all off button. At night, triggering the scene will run a program turning the scene on. This in turn turns the lights to 50%, turns on the hallway lights, and turns everything else off. I have the button in a separate program which then turns the button off after 2 seconds. The room will turn itself off after a couple of minutes as will the hall lights.

Yes I have without any issues. Are you just updating the scene or the controllers in the scenes as well?

Clear your Java cache. You should still have update neighbors

It's worth reading as there are a few nuances that you could potentially avoid if you're aware of the pitfalls of those who blazed the path before you. Personally, I think you're being overly cautious but it's not a bad plan since you don't have much anyway. Since you're planning on a fresh zwave install, you shouldn't have anything to worry about. Factory reset the zwave board before re-installing your zwave devices and you'll be good to go. You may need to bring devices close to the ish to re-add them.

What exactly are you having issues with? What are you trying to accomplish and what is actually happening? Without details it's hard to help you get on the right path. Too many people have working systems within the parameters they're confined to so most likely it's human error vs the system itself.

Keep in mind, when you use mutually exclusive, that resides in the devices. If you haven't reset them (or remove the function via console), it could still be there which will effect how your buttons respond to new scenes and programs.

Insteon's business is not dependent on the isy no more than UDIs business is tied to insteon. Both would survive without each other. There are a large number of insteon/ISY users so it would be a hit but at the same time, many of those users already have their devices so they've already gotten their money. Back when smarthome sold the isy, it was outsold by the hub by a large number (I'm only counting smarthome sales). Many of the employees pushed the isy because they felt it was a better system (it's definitely the best) than the hub, indigo, homeseer, etc. What ended up happening is that users would start with the hub and then upgrade to more advanced systems later. They have a symbiotic relationship and it's my hope that both see that it can be mutually benefictial to both. At the end of the day, both companies will survive without the other....it's the end users who will pay the price for them not working together

The harmony nodeserver won't do it but the hue emulator nodeserver may work

I don't know what a 6 link switch is. I'm assuming you're talking about a keypadlinc. The wiki has the information on how to add devices to the isy. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Link_Management_Menu If you're trying to set up an insteon scene you can also find the instructions in the isy wiki. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Scene

Everything about that looks like a phishing attempt.

NWI isnt supported in most non plus devices. All devices would need to be plus and support NWI for it to work. You can exclude from anywhere when a device is part of an existing network but since his is a new network, it wouldnt work.

I don't use non toggle options. I keep mine in Toggle mode, set device to their proper state and use programs to turn off the kpl backlight when necessary

See adding devices

Won't help with what you're trying to do. They lock needs to be closer to the isy

Change default to off and see what happens

Non toggle on=buttons on Non toggle off= buttons off That's how it's built into the device. You can always create a scene, add the button to that scene, and then create a program that turns that scene off anytime you physically press the button after a second or 2

If it's not close to the isy it won't exclude or include

FYI- if the ISY is not aware of an insteon device, it will still add due to how the protocol works. However, since it is not part of the isy data base, it will not have the necessary information needed to have the proper settings of the device. You would get a different message during adding and how it shows up. Since yours says that it cannot determine insteon engine, its recognizing what the device is and so forth....Its just not able get all the information it needs to complete the process. Most times, this comes down to communication between the ISY and device, incorrect code for what that device is reporting, or something happened at the factory which a factory reset wipes out. I attached an image of what you would receive if the ISY did not have the 2477d in its database.

The Id could be incorrect. Follow the instructions i gave previously and you don't have to worry about typing in the id

If that was the case, it would still add to the isy. It would simply say unsupported device type (something along those lines). With that said, it is still in the console.

Nothing. The universal heal had been removed and replaced with update neighbors for individual devices as this is the best method for updating zwave devices

There's not a large contingent of irule users on here. You're better off going to the irule forum with your issues

Highly unlikely to cause any problems. Many people on here are (and have been) constantly writing new links for years without issue

I hope so too. I'm pushing for you