lilyoyo1

The PLM isnt attached to the EISY to update anything.

i no longer use UDI and insteon due to me switching to Control 4 and Ra3. I wouldnt sleep on the marketing. The increased speed from when I used insteon, zwave, and hue with Polisy was noticeable (programs). That alone made the change worthwhile. Had EISY supported Ra3, I would've used that instead of C4. Additional note for those that may read this: EISY does support RA3 dimmers, switches, via caseta node server. Insteon I3 devices are worth switching to if starting fresh with insteon. If Ra3 never came out, I would've been using those. They are much higher quality when it comes to look and feel compared to the old ones. I wouldn't rip out my system to use them though. With that said, since the speed difference and other technologies are irrelevant to you, I don't see any reason for you to swap from one to the other. I know they've started on a new web based interface but I think that's only for beta testers right now.

I'd start from the begining to ensure each step was followed correctly. Unplug Plm and isy. Note Plm Insteon address. Plug Plm in while holding the set button to factory reset. Once beeping stops, let go. Wait 30 seconds and plug isy into power. Verify new pom is showing in isy. Once done, go to file>restore plm>restore devices.

When I used my polisy, I did this using network resources.

I don't this is Plm issue since this only happens with the same set of devices. Besides that, Insteon links are stored on the devices themselves so a bad Plm wouldn't affect local operation of the devices. I agree with Guy that a switch is probably going bad. I'd start with the controlled switch when you start your tests

Are you sure that your switches are Lutron? Lutron doesn't make zwave switches. If they are indeed Lutron, they wouldn't be part of your zwave mesh which would explain some things.

With 10 thermostats, I assume you have a fairly large home. Are your zwave devices grouped together or spread out? Is your eisy centrally located or on one end trying to communicate to another? Are your issues with every zwave device or specific ones? If it's specific, that's an easier fix. While adding repeaters can work, you want to do it strategically to get the most out of them.

I was saying you can have separate 2 networks in a home. My apologies for not clarifying that you would need 2 separate controllers for that. Even if it were possible with a single controller, range would still be an issue. Technically you can have 2 eisys talk to each other using variables and network resources but that's not something I've ever entertained due to the added complexity of the system. There are some on here who have done so but I can't say what steps they took or the end results long term. The problem is repeaters repeat the signal that is being sent. If it receives a 300 series signal the 300 series devices wouldn't be able to translate an 800 series message. This has been like this since the beginning of zwave. There are plenty of articles online on how zwave mesh works to confirm this.

This may not work depending on what series devices that you have. The signal that it repeats will still be the same signal sent from your controller. If you have 500 series devices, your eisy will send out the signal using 500 series protocol/range. The range will be determined by 500 series max range... Ditto for 700 series (Eisy does not support zwave LR)

I have newer locks so I can't say how older locks would behave. I suspect you would need to exclude and include again though with it being older zwave protocol

You can add long as you build it a strong mesh in order for everything to work properly. The networks will not repeat signals to each other

If you're looking for an answer, emailing UDI directly through their support channels is the best way to get it.

If both controllers are individually configured the same way, they should work with a single scene.

Do you actually use different light levels when you dim or tend to stick to the same settings (IE: dim to 30% each time). If its the latter, you could use the fade command to trigger your program to set the light at that level. Outside of that, you would need to use programs and set the bulb based on the insteon range which will be a poor experience

I remember when they were trying and it wasn't a knock against them. I love UDI and their products. You did an excellent job with getting their switches supported for the community which is an excellent thing. I was just letting the poster know that there is no perfect situation out there definitely none better than eisy/Insteon

I no longer use UDI equipment so I am limited in what I can say about them. From my ISY-Polisy days, I have zero negative things to say. The only reason I switched, was due to me using Radio Ra3 instead of insteon. At the time, UDI equipment did not support Ra3. Even now, it does not support Ra3 Keypads so I couldnt go back if I wanted to. Had EISY offered RA3 support before I invested in Control 4, I never would have stopped using it. if its not broke, dont fix it....Why swap out a perfectly good and working system for something new if you're using it for basic needs? Its not like the 994 suddenly stopped working because of the EISY. With 300 insteon devices- you're kinda stuck with what you have. No other system (DIY) can support that many devices. Caseta tops out at 75 devices. Unless you plan on having multiple logins and hubs, thats a non starter...Even if willing; you've added unnecessary complexity to your system...especially since they do not have keypad support. Zwave! Zwave is a non starter for me for many reasons. Some like it but after using Insteon/Ra3, there is zero chance of me ever using it. For a basic system, the Lutron DIY/prosumer stuff works really well. If all I wanted was Alexa control over a few devices i'd be willing to use them to a certain degree. For customization, you will need to add another layer of control to really get the most out of them. Lutron's Prosumer stuff (ra2/3) were really designed to be used with other control systems. That's partly why they are so basic when used by themselves but so easily integrate with other select systems. The same people who want standalone systems controlled by Alexa are not looking to use EISY and home assistant. For the most part, those same people aren't looking at RA2 (while cheaper is still the most expensive option you mentioned)

The original I3 hub was able to update the device. Whether that can happen from EISY (now or in the future) I dont know.

The look and feel of I3 devices over older Insteon devices are much more improved. They are night and day in regards to quality, fit, and finish. If I were to ever go back to Insteon, it would only be to use i3 devices. Plus they have updatable so l firmware so they can be improved over time unlike older devices

Maybe you could do a step by step write up for those who may still question where to find the information needed and where to put it in regards to the eisy/Unifi

Do they not have a backup that you can restore from their old ISY to the new? That would be your easiest option. Since you've already added the kpls, it may already be too late to find old devices. I would ask them if they have a backup so you could use that instead. If there is no backup you can turn on each kpl and see what devices also turns on (potentially off). Once added to the system via your laptop/desktop computer using the admin console, you could then control each of the devices to match the IDs to. Its going to be one heck of a time setting everything up the way you will have to. Outside of what's mentioned, you'll have to open stuff up. Most likely the devices aren't actually buried in the walls. You will however, need to check behind fixtures and so forth.

While insteon devices have codes that show up in the system, it would take the same amount of work to figure out what devices are which just like zwave if you do not rename them while adding. Yes, you can walk around and check devices to find the number, but that's highly inefficient at best if you have a large number of devices to look through. The best way to figure anything out would be to to on each device one at a time to see what device turns on in the console. Once you figure that out, rename your switch. I always left the number in front of my zwave devices with the name I wanted to go by. Personally, I would factory reset everything and start with a clean slate. If you want to go the deletion route, start with the devices that are farthest away and choose remove device. Then move closer to your controller. This method assumes that your devices are newer devices that support network wide inclusion/exclusion

That's the only one with official support. Other dongles have worked however. His issue isn't the dongle. His eisy is looking for the zmatter stick which means his dongle won't work regardless of what he's using right now.

Both zwave and zigbee uses routing to reach devices within their mesh network. Splitting up devices can impact your network if things arent done properly. I doubt the 2 networks would interfere with each other since they wouldn't know anything about one another.

If all you need is insteon and do not want anything new, the 994 would still work. You can also use Insteon with the eisy without doing anything else as well.