lilyoyo1

The Isy is an advanced controller designed for individuals who want to get more out of their system than what the hub can do. Whether it's the Isy or something else complicated, anytime you try and take shortcuts, you'll most likely run into issues. This is why you received certain advice from people. Yes, it sucks to run around and press buttons but you don't have to do that if you have your device address list. Since you would've done so factory resetting things, you can do that process at the same time. The instructions were written from a clean slate perspective. If they tried to cover every scenario in the instructions, no one would read it and most likely return the unit thinking things were harder than they are. As a DIYer, there's a certain expectation of product knowledge and that you'll take the time to do research and ask questions for better understanding. There is a manual that covers alot. It's called the Isy cookbook and runs a few hundred pages. Can you imagine that being the instruction sheet? The add existing links should not be removed. Many advanced users run multiple systems and can use that since they know the inherent risks and how to mitigate them. It's also great for if you lose the id to a sensor. You can manually link it to another device, as that device to the Isy with that link to get the id number. Workout that, your sensor would be worthless. It has use cases. Knowing the how's and why's simply takes time just like anything else People gave the advice they did because you are a new user. You may not like the advice but it was given to put you in the best possible position to succeed. Whether we do this professionally or our own benefit, we all were in your position at some point, made mistakes, and learned from them. They say experience is the best teacher and with this it's very true.

You're welcome. I installed a few of the Sunnata dimmers in unused areas of the house. They're amazing. Using the same bulbs as I had with insteon (new and old) and the zooz zwave dimmer (for testing purposes) dimming is so much better. I can get more usable light out of the low trim level than i can from zooz and the new insteon. If you do decide to start upgrading, let me know

All good questions. Caseta does not integrate with the RadioRa line. It uses the same app but that's about it. If you had both in your home, you'd have separate systems you'd need to log into. Using the Isy/polisy nodeservers, you could integrate them together but from the lutron side of things, they'd be separate. Lutron is bound (at least should be) higher quality than insteon being that you're looking at a 200+ dollar switch vs. 50. They can afford to use better components. Insteons quality has improved over the years however. Most likely (as with many if not most) a lutron nodeserver will be developed by a 3rd party developer. I understand your hesitation but reality is that there are too many products available for UDI to try and support alone. Not only they they have to take time to develop and test, they'd have to purchase the products to have in-house to verify it works and learn it's beaviors, etc. There's already been talk from a couple of developers about supporting Ra3 but that would depend on lutron releasing the API. I know one of the caseta nodeservers already supports LEAP so im confident Ra3 will come at some point. I know some of the bigger developers of nodeservers here are present and use the equipment they develop nodeservers for (I know 1 is a Lutron dealer/installer). Personally, I don't care whether it's UDI or a 3rd party developer. With all that UDI has on their plate, adding to it only takes away from something else they could be working on. Having someone with the proper skills along with being a user themselves means a product that works great and the experience to help troubleshoot issues.

At this time, you can purchase an Rpi to run polyglot V2 on right now and test out nodeservers you may want to use. This is a low cost way of checking things out without investing too much money. While UDI doesn't offer support for this method, you can always upgrade to polisy later if you like what you experience.

Scenes accomplish the same as mutually exclusive groupings. The only difference is mutually exclusive resides at the device level so the Isy is unaware of what's going on. This can impact things such as programs and troubleshooting issues

What is it that you hope to accomplish with thread? Its been around for about 7 years or so with minimal impact and a small number of supported devices. When it comes to automation, Matter would mean more than thread by itself. But then again, it remains to be seen if matter really matters

I actually recommend that you DO NOT use button groupings. This happens at the device level and the Isy is unaware of the status. If your scenes are set up correctly, you won't need them. I don't use non toggle mode. Everything is toggle. That way when you switch to one it automatically will turn the other off. You can also turn the button that's on off which will stop that particular process. Doing it this way means you don't need a separate off button for your scenes. If you do desire a separate off, you can still set it up the same way and then make a non toggle off scene with fanlinc and all buttons in it to turn off. Your scenes look correct as far as the controllers go. Make sure the Scene itself is configured the same way. (Click on the scene and verify links)

Just because you never had problems with 3 installs doesn't mean others don't have issues. Plenty of people on here can attest to the multitude of folks who had had issues from importing. I am a professional and I factory reset everything. Even with Control 4. While most here may be what you call weekend warriors, many of them probably know more than many installers and can become one themselves if they felt inclined to. It's funny you try to call out folks like you're a big shot yet talking about 3 installs. I'd trust the veterans who has been here for years with thousands of posts over your 3 months and 25 posts.... Most which do not offer any help at all. The fact you're talking about other tools for the hub for someone MOVING AWAY from the hub already shows your lack of understanding. That's like me trying to fix a car after i trade it in. Why bother! Next, you feel it's easier to install strange software on his computer to manage something the Isy can already do. In the time it takes to download, figure it out, etc. He could've simply factory reset his devices and added them to the Isy and start working. Let's break this down. He'll ssh into the hub (a device he doesn't want to use), for some unknown reason, download software to manage his links, to the still need to add his devices to the isy. How much sense does that make? Yet, you want to question the credentials of those who has been in the trenches for years seeing what people have been going through and helping solve those problems. Before you start telling veterans what they don't know and newbies what they should do, maybe you should take the time to learn the product. The hub link resides in the devices whether the hub is on or not. This applies to ALL insteon devices. Next, factory resetting the hub does not remove it's link. They'd have to remove the device from the hub to remove it's link. Sure a tool could do that but what's faster? Factory resetting a device, going through the remove process or using some tool for link management? One thing i learned in the military and kept with me over the years is the kiss method (keep it simple stupid). Sometimes the simplest method is the best. No one started out telling the op to factory reset everything. Read for context and comprehension before saying something. I told him to factory reset the device and then see what happens. He started clean on his own and now has things running the way he wanted. Only when he said he imported did i say a factory reset on everything would have been said. The fact is he had 1 issue now. Who's to say there wouldn't be others later? Having best practices is important in this game. Whether it's factory resetting devices to get rid of links that may still exist to keeping spread sheets or backups, we all have our processes that we've found allow us to use the Isy with zero issues. Trying to think you know more than everyone here for whatever reason (and then proceeding to make zero sense) only serves to make others blow back on you regardless of how helpful you may think you are being.

Upnp is turned off on your router which is why it doesn't work. Personally, I wouldn't recommend using that option. My first choice would be to use the portal. Go to help>purchase modules and buy a portal subscription. Once done and enabled on your isy, you'll have remote access. The second would be to set a port forwarding rule. Again, not something I'd recommend but it's more secure than enabling upnp.

You are incorrect. The 500 board on the latest firmwares does support multi channel devices. It has for a few years now. Most likely, the device either requires custom coding in order to work or parameter changes. With that said, it should join regardless. What process did you use to get it to join

You should've created their Polisy marketing page

Udi products do not use log4shell

Experience is the best teacher. It's been said countless times on these forums not to take shortcuts as it often ends badly. This is shown often with those who import their previous setups from other controllers. Sometimes you cant say anything. You just gotta let them fail.

If you feel that's all you need, why not go for it?

Did you see if you could manually link it to another device

I'm sure there will be. Pg3 is still in testing which is why sudo is required.

Factory reset plug in module. Bring it closer to PLM, choose start linking, press and hold set button until it pops up on console

Colors depends on the theme you choose. Shows the difference between responders and controllers

Besides being terrible for lighting control for various reasons, zwave isn't a bad protocol overall. The problem with it stems from most users trying to use the bare minimum to build out their network only to run into issues. Those who build a strong network are generally pleased with the results it provides. Zigbee is much better than zwave and insteon but it has its own share of problems. You still have to build out the network as well otherwise you'll run into issues with it as well.

What's your UI? Go to help>about

As an installer I do want things to be rock solid. However, what i consider rock solid may not be the same as what someone else calls rock solid. It's up to the mfg. to provide me with a product I want to use. It's up to me not them to verify that the product is a fit for what I'm trying to accomplish. Because of that, I don't depend on what anyone says about their product. I still want to get my hands on it to see how it works inside and out. Reading about something gives information but experience is still the best teacher. Only once I've used something long enough to where i feel that I understand it's full capabilities and what I'm going to experience (pros and cons) will i deploy it in a person's house.

You could also add that no single controller supports a large number of 3rd party devices without outside developer assistance. As you've already mentioned, those that do all in house development on support a small number of outside devices. Nowhere close to the number of 3rd party devices that polisy already supports

If "Free" isn't good enough for someone i really don't know what to say. With that said, as someone already mentioned, if you click on the nodeserver you're interested in, you can see all the information you're asking about

It does have a solution....factory reset the device. With that said, this is why it's important to provide as much information as possible about your issue. Had you given those additional details in the beginning, everyone's answer would've been to factory reset your devices and start with a clean slate.

It's not only great in theory, it's great in reality as well. It's pretty easy to set up if you read the instructions. It's as simple as going to the store and hit install for the nodeserver you want. https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide