lilyoyo1

This isn't necessarily true for a lot of people. Outside of basic multi-way setups, most of my controllers actually do different things based on the location. For example, what I need to happen when hitting my away button from the kitchen is different than me doing the same from the front door or garage. If one wants every controller to be the same, they could make it easier by adding responders to the scene first and configuring them. Once done, add the controllers and they will take on the scene attributes automatically

They aren't completely discontinued. There's currently an extreme shortage of chips. Instead of trying to put out their full product line, they're trying to focus on the major selling items to keep those in stock. There are plenty of posts on this forum as well as on the news detailing the current global supply of chips and how it's causing problems for everything

John was an advisor/project manager. Steve, most likely will be back. He's been back and forth 3 or 4 times over the years.

Sounds like it's a programming issue that needs to be fixed in a future firmware update. Unfortunately not all issues can be solved via troubleshooting steps. In your case, while it's not the answer you wanted it was the best answer given. The same happened to me with my yale locks. I had to go back to 5.0.16 due to issues with 5.3 and 5.3.2. This update seems to allow them to work properly (time will tell once i have time to test)

Damn Google and their invisible pages

You're welcome. Glad you got it working. It's already in there under adding devices

No. If the lock is within 3 feet of the isy, it should add. Did you do a remove first?

https://forum.universal-devices.com/topic/29371-zwave-tips-and-tricks/

See 4th post below yours for answer

Have you set up port forwarding in the new router

In addition to the list posted, there are many nuances to zwave that makes it difficult to track. For the most part, sticking with reputable companies such as ge, homeseer, aeotech, and others will yield the best results. There are many cheaper alternatives out there. However, many times the protocol is forked where features do not work properly or systems have problems talking to those devices. This can change from firmware to firmware (fibaro). Before investing heavily into any zwave device, purchase 1 to test with your isy to ensure it works properly, then purchase what you want in greater quantites

I've seen that. Ive done the same

Everything depends on what you're using. If it's not compatible with the isy then it won't work with the isy. I would not assume the isy could be a secondary controller of anything you choose to use. Not only are you added an extra layer to your system, if you're not up on how zwave (and your primary) controller works, you'll be creating issues for yourself that you may not be able to fix and will receive limited assistance (if any) from others

Sometimes I wonder if he's just trolling us. He pops in from time to time with the same issues just phrased differently. Despite multiple people saying post programs and details, those are often lacking and slow to do so. Either he's trolling or is seriously in over his head when it comes to using the isy

https://forum.universal-devices.com/topic/31074-new-house-and-starting-fresh-which-to-use-z-wave-or-insteon-or/?tab=comments#comment-300330 https://forum.universal-devices.com/topic/29371-zwave-tips-and-tricks/

Use something else! However, if you really want to use that you'll want to be on at least 5.0.16c and look at this post

How old is your plm? It would help more if you would share what problems you're having vs having tunnel vision and focusing on what you think it is. Most issues people have isn't because of their PLM. Many times, its either noise (poor communication) or poor installation (including programming and/or setup)

When the conditions are met. The isy is event driven

You're original question is completely different than what you are saying now! Your original question requires the device status (along with programming) in order to work. What you are saying you want now is a simple timer which does not require device status. If the lights are on, then bring on the lights is irrelevant (you wouldn't notice) when its time to turn on. The same applies for if they are already off. The isy sending an off signal is irrelevant since they would stay off. The more information you provide about what you're trying to accomplish will lessen confusion and help you solve the problems you're having

It's a feature that's used by so few and so rarely most don't even think about it being something they really need. I remember when they first came out with the beta units for it and forgot about it afterwards. Didn't even realize the feature made it to production units since it wasn't something I used. With the way things are, I barely have a need for all the buttons on keypads now. I'll end up using their 4 button kpls in my new house once they release that one because the 6 is too much

Does your UI match your firmware

Being that it's supported in multiple other systems, it can't be that obscure. Multiple folks had to hear about it along with gaining access to add to their systems.