Puck - Do you have an example of the Macro you are using to turn on one camera at a time via appliance modules?
Welcome to the forum
stevegipson. There are a couple of ways you can handle the camera switching macros when using just appliance modules for power:
The simplest method: When you turn one on, you also send the commands to turn each of the others off.
Using Flags: Designate a status flag for each camera. When you trigger a macro to turn one on, you use "else conditions" to check if any other camera is currently on (looking at each designated flag). If another status flag is set, then the macro will turn just that camera off, turn the new camera on, clear the old flag & set the new flag. If no flag is set, then you just turn on the camera and set its status flag.
The flags method is more complicated, but I recommend using flags if your cameras are controlled by motion sensors. This way when a camera switches, the previous motion sensor's off signal can be ignored so the camera that is currently on does not get turned off until its dedicated motion sensor sends an off signal.
I originally had my macros set up this way and when I factored in all the various action combinations based on daytime/nighttime - home/away, the number of the else conditions per macro was enormous. At that point I purchased some auto-switching camera power supplies from X10 to use instead of appliance modules. However, I still use dedicated flags for each camera to make sure another zone doesn't turn off the wrong camera.