lilyoyo1

Are you getting errors? How did you try to link

Michel has already stated they will support what they currently support. They will not add support (reverse engineering the code) for newer devices (such as the new line) unless they are given the proper documentation for it.

This all depends on what you value most from insteon. In terms of scalability, usability, and experience, none of the diy systems come to being a viable alternative. If you don't care about uniformity, redundancy, and overall system performance, then zwave would be the best alternative for the isy. The reason I say these things is that wifi devices aren't completely scalable in a full automation setting for the reasons you listed and more. In addition, you have the work involved with flashing all of your devices, maintenance, as well as network impact (can be mitigated if you know what you're doing). For me, the amount of work that goes into using them is not worth the cost savings. In regards to zwave, you're still dependant on the Isy in order to work. Should the Isy fail for any reason, your system no longer works. At least with insteon, you can design it to work outside of the Isy so that your most important stuff still work. This can be somewhat mitigated in zwave IF you have the right devices (emphasis on IF). However the ability to have direct links with zwave devices is extremely limited in the amount of devices you can have control of as well as how it could potentially affect Isy programming. IF (there's that word again) you have the proper zwave devices, the ISY can allow you to recreate some of the things you can do with insteon. However, zwave is not nearly as dynamic in regards to making changes so it doesn't allow for as robust of programming that you'll find with insteon. Finally, (the biggest issue for me) is the popcorn effect. Zwave devices respond 1 at a time not in sync the way insteon does. That's something I could never live with. If that doesn't matter to you then zwave will be fine (though it's response is slower than insteons) If you can afford it, and didn't want to stick with insteon, I would recommend using Radio ra2. There's a nodeserver for it written by @simplextechso that you can use the isy to give it the additional logic control that radio ra2 is lacking.

Did you attempt to do anything in the admin console? The dashboard is typically used for viewing your system and the admin console is for configuring your system

Firmware and UI? Restore your devices by right clicking on the device and choosing restore

No. Your best bet is to upgrade your board since it's the newer firmware that supports what you need. I know it's not what you want to hear but it's really the only option

See post directly below yours

It has not been discontinued though it will be a while before they get more in

If this a real post, your situation has nothing to do with the original post. What is your UI? I suspect that you may need to clear your Java cache.

https://forum.universal-devices.com/topic/27379-context-aware-alexa-with-an-isy/page/3/#comments

Nice install. I'm glad that you got it working. Welcome to the world of zwave. I'd temper your expectations when comparing it to insteon in regards to what you once we're able to do. They are worlds apart in that regards

same advice given previously (post directly above yours) which was ignored.

You must use the scene in order to keep things in sync and not the device

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