Its available in a few categories. Switches, dimmable light (I believe what it called), but It’s just a ZigBee bulb. 
Every object in the ST IDE has this STATUS value, Just want to know if I can reach it through CoRE?
Ah, ok, so to start with, check if this gives the ONLINE/OFFLINE value
IF
Basement Hall Potlight status changes
> Send push notification Status: {$currentEventValue}Try changing the Condition from a trigger to is.
Nice! Will do!
Logan
[https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/eibyer/45/27702_1.png] eibyerhttps://community.smartthings.com/users/eibyer Rey Mhttps://community.smartthings.com/users/eibyer
November 29
Ah, ok, so to start with, check if this gives the ONLINE/OFFLINE value
IF
Basement Hall Potlight status changes
We’re do you type that in? In the mobile app smart app section?
[image1.PNG]
Logan
[https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/eibyer/45/27702_1.png] eibyerhttps://community.smartthings.com/users/eibyer Rey Mhttps://community.smartthings.com/users/eibyer
November 29
Ah, ok, so to start with, check if this gives the ONLINE/OFFLINE value
IF
Basement Hall Potlight status changes
Looking to see if there’s a way to have a piston use a custom sound from another location like a public URL. I can get this to work with the normal Notify with Sound sonos app, but I have some dependent pistons that I’m currently using for a speech-to-text in CoRE. Looking to change that to a custom file.
Hi all, looking for a bit of assistance. I’m hoping that somebody has already done something similar.
I’ve got 3 smart plugs with power monitoring. I’ve got them attached to my Washing Machine, Tumble Dryer and Dishwasher. I’m looking to have $Device cycle has started, and $Device cycle has ended notifications.
I’ve tried a simply if $Device power stays greater than 10W for 1 minute, then notification. Unfortunately the power can drop a couple of times throughout a cycle and technically re-issue before the cycle has actually finished.
I’ve gone for a if $Device power stays less than 10W for 3 minutes for the $Device cycle has ended notifications. Again though this can happen a couple of times through the cycle.
I want to keep the delay between the event and the notification as short as possible, but obviously don’t want false positives either. I’d also like some kind of logic whereby the “cycle has ended” notification can only happen if a prior “device has started” has happened.
As an example, the dishwasher typically stays above the wattage threshold throughout the cycle, until it hits cooling phase. Unfortunately it cools anywhere between 50-70 minutes, then a final pump brings it above the wattage threshold. Issuing a notification after e.g. 55 minutes is useless because it may not have technically finished (pump could also run at 54 minutes, throwing the whole thing off) . Issuing a notification after 3 minutes is also useless because it would also run after the cool down starts.
Hopefully this all makes sense and you’ll all have some great ideas on how I can accomplish this.
I had a short mp3 hosted on a pi webserver in my local network and I used the local url to call it http://local_ip/ding.mp3 until I moved it to where the vlc server is installed.
THEN...
Using VLCServer1...
► Wait 1 seconds
► Play track "ding.mp3" at volume 100 and resume
► Wait 2 seconds
► Speak text "{@textMessage}" at volume 80 and resumeYou could create the piston to do this…
If power changes to above X watts
> set variable for $now1
> set variable for $power_used1
> wait X minutes (length of longest possible run time
> set variable for $now2
> set variable for $power_used2
> do some math to subtract X2-X1 (time ran total) and set result to variable X3
> do some math to subtract P2-P1 (total power used) and set result to variable P3.
> send sms "The dishwasher has completed a '${X3}' minute cycle, which used '${P3}' watts of power".
There is probably some more to add in there… But that gives you an idea of where to start.
1 Like
Screenshots of a time restriction as created in CoRE and as it appears in the Dashboard. Why the 1-hour difference, and what time will this actually be able to run? (Actually, last night the offset changed to 1:01, as seen here - before that, it was exactly an hour.)
Check your PC time… just a guess.
I am trying to get a tone generator to beep when any door is opened. I found that trying to set it up as when “any of: x,y,z contact sensors” changed in the last 1 minute, do something. However, the “changed” condition is never true.
If I set this up for when a motion sensor changed instead, it works perfectly. If I set it up for when any of the contact sensors is open or is closed, it works perfectly. Im at a loss. Even when I set it to changed in the last 360 minutes, it does not work.
Any ideas?
I have my oem smartthing multi sensors set as such in the api. (SmartSense multi sensor)
Bingo. Works like a charm! As always, thanks for the quick and reliable response!
1 Like
Do you have a graph of power consumption during a full cycle? Anything particular during the last power surge before the cycle ends? Thinking about a certain power level/length to watch for before waiting for the low power mode. Use a latching piston to make it all work and voila… depends on your graph though…
When I want to set up a routine as a trigger why does Core sometimes not populate the list of routines?
hello all, I am very new to core, and I’m having an issue. I set up 2 pistons (below). however, xmas worked for about 60 seconds, not properly, and now it’s stacked on red. 2nd piston (Hue xmas) is not working at all.
any advice?
Put the follow up piston direction in line with the rest of the directions.
I have one that does some thing similar, just using a switch not time.
Also SmartThings can get upset if too many commands are sent over 20 seconds, normally for something to change the minimum should be 30 seconds.
How do I cancel a piston completely? My scenario is that I am using an Iris keypad (with User Lock Manager and the DTH provided by that developer) and CoRE to beep the keypad as a countdown to my alarm siren. When I disarm the alarm, I turn off my “IsAlarmPending” variable. The piston restrictions do prevent any further beeping and my siren (good), but the dashboard still shows the countdown to each beeping task continuing until they become pending.
