lilyoyo1

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.

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.