lilyoyo1

This is a closed thread. You should create a new post for your question

Did you recently update your isy? Did you try admin/admin

The same isy994 is the latest and greatest. UDI has released polisy which is destined to become the new ISY but until then (until further notice), the 994 is the latest and greatest

Did you buy this used

The ones that get me are those that complain that Udi didn't do anything to make them aware of the issue and until you point it out

I forgot about that. Let me go back to add it. Lol edit: I added the invisible BOLD RED UNDERLINED ink so that it can be ignored as usual

@MrBill I should add don't upgrade to 5.3 if you do not have the new board.

Who reads nowadays? That's too much work!

Try rebooting your isy

Does your firmware and ui match

4.0 was eol once 5.0 matured. It'll be supported in regards to continuing to work as is but no new database updates for new/upcoming devices. All advantages of 5.0 has been stated. Nothing else is there

If all you have is insteon and feel the way you do about expanding, then I don't see any point in upgrading

You did it wrong. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Link_Management_Menu

Does your firmware and ui match? What was your exact process to add the device

You may be right. I've never liked the toggle modes to see how they react to different variables to know for certain. At least he has something to go off of in order to get going. He can easily set up the scene properly and if that still doesn't work out the kpls back into non toggle mode to see what happens

I think it's a combination of both in regards to trying to use a single scene in addition to using the toggle modes vs non toggle. Toggle send a specific command to everything in that scene. Since controllers are responders too, a toggle on would tell all devices to turn on regardless of how configured. The isy allows him to use 1 scene since they are still their own controllers within that scene. I do the same with my upstairs lights. The 4 locations that turns on those lights together are all controllers in 1 scene. However, the behavior is different depending on which button i hit. With that said, the scene isn't setup to be mutually exclusive so it doesn't cause any other issues. Regardless, he's doing something wrong with his setup since we both know it's possible to accomplish what he's trying to do.

It wasn't posted in the wrong forum. The problem most likely is that you didn't tag (get the attention of those) who resonded to your original question, after you asked your follow up question. They probably didn't check back in to see if you said anything else. To answer your question, the only nuances that someone can say upfront would be to ensure that you have enough devices to built a strong and solid mesh network. Anything else would be specific to whatever programming you were writing.

It probably does play a large part in things and how they work. Insteon's weed designed to work without a controller so the right modes are built into the devices themselves. Because of this, they would override the information that is sent via a scene. Toggle on- on command sent Toggle off- off always sent

Your issue has nothing to do with insteon, zwave, no the isy. It is completely how you are setting things up. 2 different people have shown you with examples what to do only for you to still do it incorrectly (according to your examples). This is solely operator error. Not Insteon, zwave or isy shortfalls.

I can't speak on your version with 5.3 since I haven't used those since the dual band versions came out. One thing I noticed is that you're using a single scene with all buttons as controllers instead of individual scenes for each controller with the other buttons as responders in the corresponding scenes like I had in my earlier example Ie: A- Main Light (one scene) B- Lamps (Separate scene) C- Relax (Separate Scene)

My programs have nothing to do with the other buttons. For the most part, all of my systems are designed to work without a controller so it's paramount that a controller is not needed for most of the setup. If you set your scene up exactly as I have shown, the other buttons will turn off on their own. Most likely you have not configured your buttons in the controller to send the off command to your other buttons. I've configured hundreds of keypads over the years in this manner and all have the same behavior once programmed.

Did you try start linking and use the set button on the outlet

You can find the reasons for why your isy is blinking by reading the wiki https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs.2FLights. Make sure your isy is connected to your network

⚠️ warning: poster above is a spammer. Previous post was a copy and paste from a 4 year old post

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.