FWIW - I’ve found that the “Dark” colors in CoRE (e.g., “Dark Red”, “Dark Blue”, etc.) are better…
Might give them another try.
Yesterday using different colours to test with I found that the colour I picked wouldn’t always appear.
Got some weird results.
Thats why I ended up with putting in hue, saturation etc. Seemed to work then.
Out of curiosity, which DTH are you using?
According to @ady624, “Set Color” sets the hue, saturation, and level, so I think that your initial approach was overkill and likely experiencing race conditions that made the behavior somewhat random. Setting color, then setting level to ensure you get the brightness you want should do it.
Also, note that “Set Color” to “Random” sets all three - hue, saturation, and level - to random values. So, I’ve got one of those, followed by a “Set Level” to set the brightness, too.
For the record, I use a simple piston and put the Wait and Off commands in the ELSE condition, rather than put them in the way you have.
1 Like
I’m using one called “Improved Zigbee Hue Bulb MA”.
Cannot find the link now but can post the code if you wish.
I put the same request out in another post as to what are people using as a DTH but got no responses.
@chickwebb is right.
Can someone explain the new IFTTT functionality and provide a possible use case.
Much appreciated!
My use case:
I set up a geofence around my office and when I exit that geofence I send a web request to CoRE.
CoRE triggers off this event and if the time is between 4:00-6:00 pm on weekdays I adjust my nest to the appropriate temperature point.
This is all so the house is cool by time I get home.
The IFTTT recipe is “IF iOS Location THEN Maker”.
In the past this use case required a virtual switch that CoRE would trigger off of. But now we can eliminate the middle man.
4 Likes
Maybe I’m using this app wrong, but here’s what’s happening. I am using this with hue bulbs. When I set the bulbs to a color and the a brightness, the bulb first turns on at max brightness and then reduces to the level I set.
What I am expecting to happen is the bulb to turn on at the brightness I specify. Am I thinking about this wrong?
The way color bulbs work, they produce the specified color as a combination of hue (the color), saturation (how colorful) and brightness. Dark blue is the same as blue, but at a lower brightness (level in the ST world). So when you ask your Hue to change to a certain color, you are already asking it to go to a certain level. You have two options:
a) choose a color variant that is closest to what you need/expect and don’t use the level anymore
b) instead of choosing a color, ignore that field and provide the hue, saturation and level yourself. Hue is 0-360, saturation and level are 0-100.
I’m pretty new to Smartthings, only had my hub a couple of weeks. When it comes to CoRE I’m a bit overwhelmed. I tried to create a basic Piston with no success. I just want to have my garage door (linear gd00z-4) close if open longer than 3 minutes.
Anton,
Here is what I would suggest trying, although I am not an expert nor do I have such a device to test with
If "Door"
Stays open for x mins
Using Door, close
If that doesn’t work, there will be someone else along to better assist
Rick
1 Like
Is there a way to have a piston send a txt message with the current values so I know what my scene is currently set at? I have no idea what I need to have.
Edit:
Better yet is there a way to capture the current state of a group of bulbs and hold it in a persistent variable?
I don’t want to have to keep setting the variable again if smartThings decides to flake out.
There is a save attribute to local state, along with its load counterpart
I saw that, but won’t that variable clear if smartThings has a problem? (Sorry. I have a midlevel understanding of the smartThings infrastructure) I was hoping it would be more like a configuration which is held and maintained until the app is removed.
If you ask a device to set to a certain hue/saturation/level in one task, wouldn’t that be static and persistent? You’d always set it to that color when the action ran…
The issue isn’t setting the value, it’s knowing what each value is. I don’t know what hue, saturation, and level is for the bulbs after I set them through the app, and it would take me a really long time with the trial and error method. It would be awesome if there was a way to capture the state of each hue Scene and save it to a piston/task. This way it would set the hue, saturation, and level for you.
Does that make sense?
Just rolling this around in my head and really have no clue as to “how-to”.
Would like to have something to indicate door/window sensors are closed at/after certain time. Sort of a SHM - without SHM.
Could use siren or indicator lights (but that part s EZ) , it’s the logic of if any open at , or between whenever.
There may even be a better or other app - but I have not looked at setting modes or SHM alternatives.
Thanks all.
Slight cautionary note on this. I have not been able to make capture/restore state to local store work. I believe you suggested that doing a capture and immediately trying to do a restore would have inconsistent effect due to the capture not completing before the restore was attempted. I’m not sure if adding a delay would help. What do you think?
FYI, the workaround I’ve come up with is to use a local variable to save the state, and loading from that.
Is there anyway for me to troubleshoot why my core dash board isn’t working. I just get a blank page. I’ve been retrying, but it never gives me any display.