lilyoyo1

Most likely your first attempts at adding the devices.

its not your plm

Sounds like the perfect time for a new Polisy

No worries. Just showing how easy it is to find general information like this on the forums now. @Geddyput in a lot of time and effort to clean things up and make the every day items much easier to locate and use

It's not in the wiki. It's where it's always been under the sub forum software releases and updates> current releases. ***Thanks to @MrBill who alerted me that there is a link in the wiki which will take you to the current release subforum. I was incorrect saying it's not there.***

Its restore PLM AND restore devices

Potential future use

Factory reset per wiki instructions

If it's not under the battery compartment you can link it to another device and add that device with existing links

The Isy exposes everything within the device list which is why you have those extra nodes. They are part of zwave regardless of whether or not the mfg. takes advantage of it. It's complicated but some zwave devices can be directly linked to another but both devices has to support that ability and class that it uses. For those that do, you're generally limited to 4 -5 devices and they must be in direct range of the controlling device.

Yes, you need a hub with zwave and you cannot avoid the popcorn effect though it's not as pronounced as it once was. Any 700 series device will suffice. Currently zooz is most popular

Look at your first line. Program for what you want to know not what you don't want to know

Isy firmware AND UI? Did you configure the scene attributes and controller?

I stay away from variables as much as possible for many tasks. However, i will use them when multiple scenarios come into play as it's easier to manage things and keep running how i want and when I want... Especially as more and more talks are integrated and automated with cross capabilities. I agree that most basic things do not require them.

When I get that, it's normally after updates. A few days later it disappears. You can try to unlink and relink your account

True and false works for basic tasks but as you start automating and integrating different systems it starts having an impact. In high use cases, it's better to plan ahead vs getting caught in a trap where logic isnt working properly because other variables are thrown into the mix. I'm looking more at what can be done (and probably will as he progresses) vs only today since we know all of this changes over time. No

https://forum.universal-devices.com/forum/179-isy-on-polisy/

With your zwave devices, there really isn't a clean way that i know of since both devices are already set up. You may be able to with network resources but i don't know how I would make that work. That's why I was saying it may be better to split things according to what works with each other.

Like i said, you don't see it Variable of 0- program runs Control on-1 second program doesn't run Fade up- 3 - light doesn't change at new time so it stays dim Fade off-1 second program doesn't run Tap Off -1 second program doesn't run Double tap off- 2 long term time out. Programs don't run The things that can be captured and how goes on and on. Then you can use each variable state for on/off to have it work the way you want.

All of those options can play into changing a variable if programmed properly. Since you don't understand that, you don't see it.

Yes. I'm not going to rehash what 2 people have already stated because you can't get over the fact that there are better ways to program things to account for more than basic actions. Regardless, it's not our house. We each have our own method of programming and it's up to the op to decide what's best for his situation short and long term

That's because you aren't seeing the big picture in regards to future changes nor when other devices can potentially come into play. For example, if you dim a light on/off or to a certain percentage; is it still on or considered off? Should the program trigger a second time or stay put? What about assistants? If you tell your assistant to turn on/or off, do you want it to come back on or stay off and for how long. What if you add a motion sensor? When that turns it on/off, how is the program supposed to respond. For the ops specific situation, you would want to account for someone dimming the light up or down or using voice/app control. If other devices are linked to his (status button as a controller, what happens then if it's turned on? How does that impact the programs? Should he add sensors later, they can be easily integrated into the programs to account for those as well. Variables allow you to capture those minute details which can improve performance and experience.

To keep things from getting complicated, I split my system up with devices that work together that way my zwave routing was minimally effected. With you having the amount of devices that you have, the likelihood of poor routing killing either unit is small

The same premise applies to any button/keypad. It's up to theprogrammer to decide how they want to do things as there are different ways to get things working

Even simplerprograms/situations will grow to become more complex over time. As you can see, a simple variable (hmm, ironic how it's called that) thrown into the mix can exponentially complicate things. It's easier to start out building with the future in mind than mucking things as you add more capabilities to your system