lilyoyo1

Zwave locks also work.

If you're not having problems with direct communication between devices then I would focus on the area around the plm. If it's with all of your devices when controlled from the isy, it could be the plm going bad. You can try to factory reset it just in case (unplug for 10 sec. Plug in while holding set button until beeping stops). The choose restore plm> restore devices. Make sure it's not plugged into a surge protector or one isn't around

Are these devices directly linked via scenes or controlling programs

Whether upgrading will fix your issues depends on your issues. From a pure controller/programming standpoint, it probably won't since performance shouldn't change unless you've made changes or devices are going bad. From a connection standpoint between the isy and HA, you could have issues that would be addressed by upgrading. Since you'd be using pg2 which is not supported (nor is your isy) updates could have been made to HA and other devices which could potentially be causing issues. Since no details were given, there's not much we can say. There is new instruction functionality with the new systems in regard to being able to control insteons latest and greatest. Since old insteon devices don't have anything new added, there's no functions to add. It's really not our place to say whether you're right or wrong. I look at it more as a situation on wether or not you want to have a more modern setup or continue with what you have now. Personally, I only upgrade when there's a compelling reason to. Either my system has died and I need a new one or there has been a noticeable change that enhances my experience. There's a huge difference in processing programs with the eisy2 vs isy994. I last used polisy and I was shocked at the difference in speed when it came to devices triggering. I can only imagine the jump from eisy2 compared to isy994. Just basing that off my polisy experience, and yes, that alone is worth a few hundred bucks. Heads up, swapping devices has never changed. You can still swap like for like devices (2477d for 2477d). I'm not sure of previous flaws unless you're talking about Java only. Java doesn't bother me personally. Not all new shiny things are better than older stuff. Java gets the job done. If I had to run it 24/7 it would probably matter more. However, to program every so often knowing if I never open the interface again, it'll continue to work; matters much more. When I look at programming HA or habitat vs UDIs java interface, I'd take their programming anytime. Especially since the underlying system itself is rock solid.

Unfortunately this is par for the course when it comes to Zwave. I helped a friend with his zwave setup zooz 800 series. I would take UDI controllers over it any day. The programming was terrible with hubitat. With that said, you'd still experience the same thing with EISY and zwave. It was so bad, he ended up ripping all of it out and going with Ra3 like I told him to do from the beginning. Be careful about swapping to insteon though. Depending on your setup, removing those can impact your mesh network. Depending on setup (sounds like the whole home is done so you should be ok), you could potential break the routing table your devices are using to communicate. With zwave being self healing, if you have enough devices, you'll be ok. To me, lighting is an experience and with how zwave works, I couldnt live with its limitations. Regardless of cost, you're paying extra for an experience that you are not getting. Its worth it to upgrade to insteon vs going through what you are dealing with. While there are work arounds, the more you go from natural operation to having to remember different presses (and explaining to people who are already overwhelmed with just the thought of using the system) detracts from enjoying your home and really isnt worth it IMO.

I agree. Zwave has a place, it's just not for lighting.

You probably have a chatty device. It's been a while since Ive used UD but you should be able to check the event viewer ( set to level 3) and see what it picks up

When I used insteon. I had a bulb added to mine to make sure that they were operable as well.

It is self contained which is why yours has continued to work even though it's been over a year since support ended. The fee is for udi to manually transfer modules over from one to another since it's a device that they no longer support. With that said, if you're buying an isy that already has zwave, there would be nothing for udi to do. You would just back up and restore your isy to the new. Once done, add your zwave devices.

Oh, you're fancy.

Goodness Mr early adopter... How is the bridge outside of the system? Do you notice a difference? Have you tried to see if network resources work with it?

I'm assuming that you're telling the lights to turn "on" in those situations. Why not make an "on" program and set that to the color temp you want?

Network resources can also be used if he goes the program route. Then the only color used would be what is chosen

Since you're using programs for everything else, why cant you use a program for when you physically trigger the light switch to turn on? Then you can have it turn on to the color temp that you desire.

Are you sure? Part of the instructions says for you to plug your PLM into your eisy. With you leaving the plm on the isy, the EISY cannot read your insteon network.