Looping over two lists at the same time?

[Equis]

I would like to loop and perform an action on a list of devices, but evaluate a second list of sensors as a condition. Right now I have three pistons that close 5 different blinds but only if the window is closed. It works fine, but three pistons are running at the same time. I'm about to add more blinds to my setup, so I thought this would be a good exercise to streamline this process, so I don't have to maintain 4 or more pistons that do the same thing.

So, here's what I'd like to do...

Only individually close Shade 1, Shade 2, and Shade 3 if Sensor 1, Sensor 2, Sensor 3 contacts are closed. If Sensor 1 is closed, close Shade 1. If Sensor 2 is open, do not close Shade 2, just loop to the next one.

Thoughts? Is there a way to loop and index two lists or somehow associate the shade with the sensor, even if it's manual when creating the variable?

[Equis]

Dang! ChatGPT with a solution? After a couple prompts to get it to understand I wanted two lists, here's where it led me. I used lights in my example for simplicity.

Understood! Here's an updated version of the webCoRE piston that iterates over a list of sensors and turns on the corresponding light if the sensor is closed:

1. Open your webCoRE dashboard and create a new piston.
2. Define the trigger:
   • Click on "Add a new trigger."
   • Select any one of the open/close sensors from the list.
   • Choose the event (e.g., "contact sensor changes to closed").
3. Add a variable to store the list of sensors and lights:
   • Click on "Add a new variable."
   • Name the variable (e.g., "sensorLightMap").
   • Set the type to "List."
   • In the "Value" field, enter the mappings of sensors to lights in JSON format. For example:

     [
       {"sensor": "Sensor 1", "light": "Light 1"},
       {"sensor": "Sensor 2", "light": "Light 2"},
       {"sensor": "Sensor 3", "light": "Light 3"}
     ]
     

4. Add a loop to iterate over the sensor-light mappings:
   • Click on "Add a new loop."
   • Select "For each" loop.
   • In the "Items" field, enter the name of the variable you created in Step 3 ("sensorLightMap").
5. Add a condition to check if the current sensor is closed:
   • Click on "Add a new condition" within the loop.
   • Select the expression condition.
   • Enter the following expression: {currentItem.sensor}'s contact is closed.
6. Add an action to turn on the corresponding light:
   • Click on "Add a new statement" within the loop.
   • Select "Control a device."
   • Choose the light device from the list ({currentItem.light}) to dynamically select the corresponding light based on the sensor.
   • Set the action to "Turn on."
7. Save and test the piston:
   • Give your piston a name and save it.
   • Use the webCoRE testing tools to verify if the piston functions as expected.
   • Make sure your open/close sensors and lights are correctly configured and triggering events in webCoRE.

In this updated piston, the loop iterates over the list of sensor-light mappings and checks if the current sensor is closed. If it is closed, the corresponding light is turned on. Adjust the piston based on your specific devices and preferences, and ensure the sensor and light names match the ones you have in your system.

[Pantheon]

Did ChatGPT generate that? If so, I'm impressed.

[Equis]

It did! I didn't even know if it could do webCoRE pistons, so I started simple and just asked it to turn on a light with motion from a sensor. Here's the whole conversation.

I would have loved a green snapshot with an import code, but maybe that's asking too much.

[Equis]

Ok, I don't think this is really that close. It's referencing functions and options that don't appear to exist. lol

[dadarkgtprince]

if sensor 1 = closed then close shade1
if sensor 1 = closed AND sensor2 = closed AND sensor3 = closed then close shade1, close shade2, close shade 3

i'm not a webcore person, but having multiple conditionals might help. i used to do something similar when i had to automate a remote (before i got a bond bridge) for my shades. i would assign each shade a binary value(1, 2, 4, 8, 16, etc), then if the shade was opened, add its value. when i got to the end, depending on the total value, i would close the respective blinds

[Equis]

Well, this isn't exactly what I was looking for, but it appears to work. I just have to maintain two lists of devices and keep them in the same order.

(I also figured out that using expressions, you can add text to a device name to make a new device name. So, for example if you have an Office Shade device, you can use an expression to append "sensor" making reference to an Office Shade Sensor device. That would work if I had a sensor on every window, but I'm using one sensor to indicate status on a few different windows.)