lilyoyo1

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.

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