How do I stop a scene from affecting another scene?

I currently have two Leviton Vizia RF+ modules in my system. One module controls a lamp in the kitchen and the other module controls a lamp in the parlor. The kitchen lamp is set to shut off first and then 20 minutes later the parlor lamp shuts off - each controlled by their own scene. The problem I have encountered is that the action of the kitchen lamp is affecting the parlor lamp. I.E. I have the parlor lamp set at 40% brightness - the kitchen lamp shuts off - the parlor lamp immediately goes to 100% brightness. Last night I turned the parlor lamp off early (before the kitchen lamp went off). When the scene ran to turn the kitchen lamp off, the parlor immediately came back on at 100% brightness.

Is it possible to stop one module from having an effect on the other module? If so - how? If no, then I think I will scrap Z Wave modules and stick with Insteon modules.

Thanks,
Ron Bernier

Are the scenes interconnected in some way? Do you have the first scene triggering the second scene? If not then one should not affect the other. If you manually run each scene separately do they work correctly?

Can you post screenshots of how you have your scenes setup?

Each module is setup with separate scenes:
Scene 1 turns the kitchen light on to 30% brightness 8 minutes before sunset.

Scene 2 turns the parlor light on to 40% brightness 3 minutes before sunset.

Scene 3 turns the kitchen light off at 21:47.

Scene 4 turns the parlor light off at 22:03.

The “problem” that I am experiencing is when the kitchen light goes off at 21:47 (scene 3), the parlor light goes to 100% brightness (parlor is not connected scene 3). Would setting up a trigger as part of scene 3 to set the parlor light to 40% brightness when the kitchen light switches off correct the problem? Currently, I do not have any triggers in my set up.

Somehow, your scenes seem to have got corrupted. The observed behaviour is not normal.

If you want to get to the bottom of why, you could confirm that scene 3 doesn’t invisibly have another action on it that is affecting the other light. On UI5, edit the scene and go to the advanced tab.

Try running the scene manually by clicking on its button. Does the same thing happen?

Try to do the same steps as the scene, on the dashboard, on the light devices. Same behaviour? If yes, it suggests some (bizarre) crosstalk between the two light modules, which I’ve never seen in Z-Wave before.

Try also to delete the scene and re-create it.

[quote=“futzle, post:4, topic:170579”]Somehow, your scenes seem to have got corrupted. The observed behaviour is not normal.

If you want to get to the bottom of why, you could confirm that scene 3 doesn’t invisibly have another action on it that is affecting the other light. On UI5, edit the scene and go to the advanced tab.

Try running the scene manually by clicking on its button. Does the same thing happen?

Try to do the same steps as the scene, on the dashboard, on the light devices. Same behaviour? If yes, it suggests some (bizarre) crosstalk between the two light modules, which I’ve never seen in Z-Wave before.

Try also to delete the scene and re-create it.[/quote]

Thank you for the reply. When I set my very basic system up a couple of weeks ago, I set it up with existing X10 modules. I wasn’t happy with the results from the X10 modules, so I ordered Z Wave modules (2 lamp modules and 2 switch modules). In UI5, I deleted the X10 modules and followed the steps for adding the Z Wave modules without making any changes to the scenes. I’m guessing that is what most likely caused my issue. Based on your response, I decided that it was probably best to delete all of my existing scenes/schedules and start fresh. I wont know until tonight if this solved the problem, but I’m fairly confident that it will.

Update - (I forgot that I could manually run the scenes) - Recreating the scenes did solve the problem. When the kitchen light shut off, the parlor light remained at 40% brightness.

Ron Bernier