CoRE - Get peer assistance here with setting up Pistons

SmartApps & Automations webCoRE
, , ,
6490

Hi, I am trying to work on a core piston which turns on my lights at sunset and sets them to warm white and another one which sets my lights to daylight when good morning routine is invoked.

I am using hue and lifx bulbs. I see if I just select the lifx bulb, I get a color temperature setting option, but if I select any of the hue bulbs or lightify bulbs connected to hue hub, they don’t give me a colour temperature option to change. Can you please help me resolve this? I am sure there will be many of you who are using Hue lights with CoRE. I have 1 lifx bulb, 2 tunable white hue buls, 2 warm white hue bulbs and 3 lightify tunable white bulbs.

I have tried Hue Advanced Connect app, which gives me the options to set colour temperature, but it has a problem where it reports few lights are on even after turning off and vice versa. This is a bit unusuable as I am having to go to the hue app again to confirm if the lights are really off.

6491

Deleted. Found the answer

6492

OK Does this look correct?

2531×283 27.6 KB

6493

Missing a Turn On, before the Wait for common time.

6494

Oh, I was wrong on the “wait for common time”, it should have been “wait for custom time” so you can customize it.

6495

Yes I had figured that out about the time. I wish CoRe was a little more user friendly for us non programmers. OK how about this.

750×1334 113 KB

6496

OK, got it working when any slider is open the lights go 100% for 2 minutes then dim back down to 15%. I used 2 basic pistons, one for turning the lights on at 15% from 5pm to 7am and a 2nd piston for the sliders on at 100%. No I have to incorporate my motion sensor to trigger 100% if it sees motion.

6497

Looks good to me, but I’ve missed stuff before so you’ll just have to wait for sunset to see if it works lol. :slight_smile:

Btw, that screenshot is much easier to read than the extra wide one

6498

Yes Thanks. I hope it works, but it looks good.

6499

I’m glad to see you making progress. I’ve yet to add any motion sensors to my setup, so I don’t have a clue how those function in CoRE.

Another thing that helped me in wrapping my head around this was to first build multiple very simple pistons like you have done and then to write a new more complex piston that does everything the basic ones did. Doing them piecemeal and later combining them helped me keep everything straight in my head. I’m now more confident in starting with the more complex pistons… well, complex for me! Just don’t forget to go back and remove all the simple parts once you have a bigger piston written to handle it.

Actually, combining all the little ones into a bigger piston also help me keep things sorted out. When I open up CoRE and see tons of different pistons, I have to mentally wade through them to remember which ones interact with each other. By combining as much of a use case into a single piston as possible, I cut down on the number of dependent pistons.

6500

Good Morning,

I would like to add a piston that in short does the following:

  1. Checks if Mode has been “Away” for ‘x’ hours

and, if true,

  1. Changes thermostat setpoint.

Desired effect is to have a ‘vacation mode’, while otherwise keeping home temperature consistent if we’re only gone for a short time.

I am having trouble figuring out how to define the “only do this after ‘x’ hours” in CoRE.

Thanks!

6501

I setup a piston that will unlock my front door when my presence sensor changes to present. It waits 30 sec, unlocks the door, waits 2 minutes then relocks the door (as a safety measure). However, what was happening was that if I left the door open for the 2 minutes the lock would lock even with the door open. So I wanted to add a step to make sure the door contact sensor was closed before the 2 minute wait to lock the lock occurred. This is what I wrote, it doesn’t work. I would appreciate any suggestions.

IMG_0049.PNG414×626 12.7 KB

6502

Put the tasks all in the same sequence…

Using front door lock...
  > Wait 30
  > Unlock
  > Wait 2 minutes
  > Lock
1 Like
6503

U beat me to it!

1 Like
6504

That did it! You guys are awesome. Many Thanks.

6505

Hopefully it will happen more than just tonight since you have the whole date in there.

6506

@eibyer, thank you. I got so caught up with my train of thought on the second piston I didn’t think about just adding the logic to the first one.

1 Like
6507

I need to create a piston that will do the following.

  1. Wait for a push from a button
  2. Ignore any further button presses from that button until the piston has completed running
  3. Wait 45 minutes
  4. Send me a text

I can do #'s 1, 3, and 4, but not sure how to do #2. What do I need to do to ignore additional button presses until the piston completes?

6508

I use a variable for that, there might be other ways…

The variable buttonPushed needs to be initialized first with value of false. Give this a try.

IF
Button changes to on
AND
Variable buttonPushed is false
Using location...
  > Set boolean variable buttonPushed = true
  > Wait 45 minutes
  > Send text
  > Set boolean variable buttonPushed = false
2 Likes
6509

Is anyone using NFC tags and IFTTT to trigger pistons? I’m trying to make a “mood cube” of sorts using an old phone and NFC tags. I have a IFTTT web request written to the NFC tag, which triggers a CoRE piston when scanned. Problem is… every time I scan the tag it brings open a new tab in Chrome.

Does anyone know if there is a way to trigger a web request (or CoRE piston) via a NFC tag and not have it open a new Chrome tab every time? Thanks!