For anyone using Griddy as their electricity provider, I’ve put together a basic SmartApp / Device Handler to display the current wholesale electricity price. The device handler is implemented as an Energy Meter since there are no other capabilities for representing something that is monitoring a price. The idea is to be able to write routines / rules / CoRE pistons than can control your smart devices in reaction to the current electricity price.
great concept - enabling peak shaving at the residential level. Like changing the setpoint based on price - you could produce a fuzzy-logic score set by price history and comfort.
Came across this after trying the new Griddy IFTTT integration which doesn’t seem to be stable (honestly nothing I do in IFTTT seems to work as I want). I’ve been able to pull the price into my app but don’t see anyway to use the price as a trigger to turn on/off lights, AC or pool pump. As I’m just getting into this there may be an easy reason why I haven’t figured this out but just asking if this has been taken to the next step to be used to control?
p.s. Love using Griddy and keeping my all-in-price below 8cents. Working now to bring it lower by turning off High power items during the power spikes.
I’m in Houston and an early adopter of Griddy. I’ve been after Griddy for IFTTT applet feature and I currently have support ticket in with them as i can’t get IFTTT to trigger on price. My plan is to have IFTTT trigger when cost per KWH goes over 0.10$. A ewelink sonoff device to on/off my pool pump and a couple of Zooz Zen switches attached to my AC units. The power spikes I normally see last no longer than 30 minutes so shutting down my high power items should keep my costs low without impacting the family. When cost per KWH falls below 0.10$ then turn everything back on. As IFTTT wasn’t working properly I found this excellent code to pull Griddy into Smartthings with the hope i could trigger off of the energy meter. At this point it doesn’t work that way. (at least not yet)
Experimenting with Trent’s code. Changed in DeviceHandler the type to be power from energy. Everywhere in the code where it said energy I changed to power and the units to w from c. It reads the cost from Griddy as watts instead of cents now. Ie. Current price is 1.818W (s/b cents). Now using the energy monitor smartrules I can say when the Watt usage is above 10W (10c) then turn off…
Experimenting but working so far.
To be clear – the hard work was by Trent. Thanks Man for the foundation.
Interesting tweak! I am also considering switching to WebCore for my rules instead of IFTTT. I also wouldn’t mind tweaking this to show actual price versus just the wholesale price per kWh.
Hi trentfoley, I am also in Texas and use both of your SmartApps, Griddy and Nexia Thermostat Manager. Awesome work. Unfortunately, I am unable to turn the Thermostat on/off with Griddy through IFTTT. I can see the Thermostat on/off switch but I believe it controls the zwave repeater (not sure)? Is there any way to tweak the code to make the Griddy/IFTTT integration turn the Thermostat on/off? Thanks.
Hey Trent. I posted a reply on your Tesla integration thread as well, but I’m thinking this may be the better place to ask the question. I have your Griddy SmartApp and device handler working along with your Tesla Connect SmartApp and device handler. Both are working flawlessly and I can see price updates and can control basic Tesla functions. What I’d like to do is stop charging my Tesla if prices surge past a certain threshold or start charging it should they drop below something like 1¢/kWh. Is that possible using the Tesla Connect integration? I can’t see an action that I would call to start or stop charging.
Thanks for all of your work on both projects and in advance for any insight you can provide on this.
I actually got this figured out using webCoRE. There’s no way to use the built-in SmartThings automation to execute the “StopCharging” action, but webCoRE does it pretty easily. Now, whenever prices spike above 5 ¢/kWh, my webCoRE piston is triggered and it stops charging my Tesla and sets my Nest thermostats to a high temperature. The only other thing I’d like to be able to stop during power price spikes is the pump on my pool, and I think I’ll be able to automate that as well, since it’s all managed by a Jandy iAqualink system. Thanks again for the Griddy and Tesla SmartApps. It made the process pretty simple.
Can someone please direct me to the step by step how to install such a “smart app” and perhasp suggestions how to enable core scripts, e.g. if price increases above x then turn off AC.
Been meaning to update. My setup with Griddy is working well, based off the original work of Trent Foley. I’ve modified the original code to work for my needs, too update the price within Smartthings and also to ActionTiles. The monitor keeps an eye on the price and when the price exceeds my set point (currently 8c/kwh) it turns off my high power usage or extra power items such as the pool pump, AC (I don’t have a smartthermostat yet), freezer, extra fridge…
Works very well. I’ve managed to set it easily to change my AC settings if the Electricity Price goes above a certain price. Thanks for this piece of art @trentfoley.
Hi - I’m new here but was wanting to see if the community could point me in the right direction.
Background:
Griddy has gotten a bit of bad press the last week or so being Texas has had unprecented price spikes ($9/kWh). I’ve gotten bit a couple times so far: I’ve had a $183 day last week and another at $119. Griddy’s recommendation is to watch the prices, adjust the thermostat during spikes, and pre-cool the house when high demands (and prices are expected).
Since then, pre-cooling has worked very well for me. We usually run at 72 deg, but bumping that down to 68 before the heat of the day sets in allows me to shut down the AC from around 1PM to 6PM and keep the house comfortable AND I’m not getting hammered on the bill.
I’ve had the IFTTT integration for a while now, but there’s a problem: I can only shut down for a few hours because I have dogs inside - I don’t want them to get too warm, so I kick things back on when the house hits a upper threshold.
Question
Here’s what I’d like: I want an automation solution that will look not only at currently pricing, but at projected prices. My Griddy app shows this, so the data should be available. Next, using this data, allow me to set up pre-cooling rules:
if in the next [12] hours, there are > [4] hours of projected prices more than [5] cents/kWh and current price is < [3] cents/kWh, begin to pre-cool the house to [current setting] minus [5] deg.
All values in brackets are configurable. The goal is to never hit that upper threshold which kicks the AC back on no matter what the current price is.