lilyoyo1

Or we can rename this thread since the original question was answered the first time. Lol

There comes a point where too much irrelevant information is provided. People don't even read whats available now but time should be spent on more information that no one will look at. Why waste time? Especially for something that rarely gets upgraded if ever.

You're assuming there are updates when there are none. You're looking at old information that no longer applies. There are 2 zwave dongle. The old 300 series which is what you have and the new 500 series. You're reading information that applies to the 500 series as it's firmware is different than the 300 series. There's no table because there has not been any updates for the dongle that you have. None for the new dongle that's out either.

I agree with you on that. My hope is that UDI will "buy" the rights to high value nodeservers such as Hue, Sonos, Lifx, and Harmony from the developers. They develop a nodeserver and work out the bugs. If it's a high demand NS, udi then purchases it. At least that way the Isy always has it and someone else can work with udi to keep it going should it be abandoned. The developer can still charge for the NS should they continue to develop and update it.

Anyone that has setup the ISY using the 4.0 branch has setup scenes the exact same way for it to be bug now. Most likely there is something within your setup itself. I would delete the whole scene, add each device as a controller (if done correctly, there is no responders in this scene. ALL should be controllers as a controller set up this way is also a responder). One way you will know its correct is if each switch is RED in the scene. Once you verify that each one is a controller, click on each switch within the scene itself and configure all devices under each controller individually.

Copy and paste the scene grouping itself from the device list. Make sure that each one of those switches are set in each controller

Dont remember the color setup in 4.0 branch. However, it seems that you have added each device as a responder instead of as controllers to one another. Each must be a controller and the levels must be set on each individual controller.

I can say it....I would be lying though. ?

USPS says 7 business days after initial complaint on the website

You know someone will post on here asking "where can they get one of those from"? Lol

No. Scenes cannot be dimmed from Alexa as she stated.

They wouldn't be personalised if all were 1 program which defeats the whole purpose. The copy and paste is the best way to accomplish what you want.

Programming the way you want and are accustomed to is different than programming an automation system which is more configuring than programming. These systems have to take into consideration the level of expertise a person may have (for the most part zero programming knowledge). The copy and paste method is the easiest and quickest way to accomplish what you want. There may be a way with variables and so forth @larryllix but to be honest, it would make things much more complicated and put you in the very situation that you are trying to avoid.

When you say manually, I'm assuming you mean use the isy to re-create your scenes and not create them by pushing the set button outside the isy. If it's the latter, you should not do that. Once a device has been removed from the isy no. However, unless you completed deleted your scenes, the old ones should still be in the isy. It would be a matter of dropping the new buttons into the right scenes. I f you've deleted your scenes and have a backup, restore the backup, take note of everything and redo.

Holding down the set button does not reset the device. You must air gap it first, then hold it in until the buzzing stops.

There are some cloud only servers that are via the portal such as RING.

Something isnt right if it was added as a 2486. I would remove it from the ISY, factory reset the device and then re-add it. Prior to re-adding to the ISY, Ensure your Firmware and UI in the ISY matches

It would not as those are 2 different time slots. I'm assuming 2 different programs were written. The lights would be off at 11pm. They would turn back on at 5am and off again after sunrise. There's no way for them to interfere with each other. What's actually happening? Post your programs for us to see what you did

If you don't believe it's another program, you can disable it and see what happens over the next few days

This is posted on the wrong forum as it has nothing to do with this topic. To get people to answer, I would create a new post under the questions and answer sub forum or magic home sub-forum

It's much simpler than the Information you laid before us. While isy portal and Mobilinc connect are from 2 different companies, they can accomplish the same thing. The choice in regards to which one to use comes down to customer needs and desires. Since I don't use apps, I prefer keeping my stuff with the Isy. Even if I did use apps, I would still prefer the isy simply because I'll always have that. The reason being, I can switch from mobilinc to another app without having to redo my setup. Should I leave the isy behind and go to another controller, (that'll never happen) I'd have to rebuild anyway even with mobilinc so it's a wash there. Should one choose to use mobilinc for Alexa, all the needed information can be found on their webpage. Its a pretty easy site to navigate (kudos @InsteonNut). Wes is generally very responsive to questions though as the owner, he'd push for his product...ditto for UDI. The forums are here with many smart people with the knowledge and skills needed to go all out. All with the willingness and desire to share our experiences. One just has to be willing to ask before jumping into things.

It's your temp causing it to turn back on. I'd have a secondary program that temporarily disabled your program if you manually turn it off

It sounds good and exciting but the work still has to be done. For a new person still finding their way; it can be daunting. There are many ways to accomplish what you are trying to do as everyone's posts can attest to. Before jumping in, I would sit down and think your whole theater routine out. While it may seem like a simple thing to add a motion sensor , there are other variables at play. Youll want to consider how much time do you need the lights on? How will the lights turn off, turn back on once done, What happens when you leave the room? Those are just the basic things. While automation is great, the worse thing is the need to do extra steps that you ordinarily would not have to because of it. Once you've answered those questions, you can move to the next step which is figuring out how to accomplish your goals. It may require investing in new hardware, waiting to gain more experience programming, or revamping your approach. Taking the time to properly plan will save you greatly on all fronts.

If they are used at night why are you having them trigger during the day time while the chickens are out?

Yes. It's still a standard switch. Just more options