Carbon Quality - Phone Call/SMS: Get a call and text when carbon quality is dirty
Start today
Other popular ComEd workflows and automations
-
- Connect ComEd to WeMo to unlock powerful experiences
- Average Price Change - Honeywell - Part 2: Resume Honeywell schedule when price comes down
- Carbon Quality - WeMo: Turn off my appliance when carbon threshold is exceeded
- Carbon Quality - Ecobee - Part 2: Resume Ecobee schedule when carbon quality is clean
- Peak Time Savings (PTS) - iOS reminder: Add iOS task reminder when ComEd PTS Hours are announced
2 - Connect ComEd to Honeywell to unlock powerful experiences
- Peak Time Savings (PTS) - ecobee - Part 2: Set temperature for start of PTS Hours on my ecobee 5
- Average Price Change - Ecobee - Part 2: Resume Ecobee schedule when price comes down 10
Useful ComEd and Zubie integrations
Triggers (If this)
Vehicle arrives at a placeThis trigger fires every time a vehicle arrives at a specific place such as Home or Work (defined within Zubie).- Change in Average PriceThis trigger fires for an account that is on a dynamic pricing plan such as the Residential Hourly Pricing program or other real time market rates whenever the average price changes.
- Vehicle leaves a placeThis Trigger fires every time a vehicle leaves a place.
- Carbon QualityIndicates whether the carbon is clean or dirty
- Trip startedThis Trigger fires every time a vehicle starts a trip, indicated by the ignition being turned on.
- Peak Time Savings - Savings Hours AnnouncedThis trigger activates whenever Peak Time Savings Hours are announced and during various stages of an event.
- Trip endedThis Trigger fires at the end of every vehicle trip, as indicated by the Ignition being turned off.
- Manage your Carbon Footprint - Change in carbon intensityThis trigger fires whenever the carbon intensity changes for the ComEd service territory, use this trigger to help lower your carbon footprint by reducing your energy during high carbon times
- Check engine light is on for any vehicleThis Trigger fires when ANY vehicle's Check Engine light has been activated, caused by a Diagnostic Trouble Code (DTC).
- Low battery condition for any vehicleThis Trigger fires when battery levels fall below normal levels for any vehicle in your account. The vehicle ingredient specifies the name of the vehicle with the problem.
- Vehicle driven between hoursThis Trigger fires when a vehicle trip ends during a selected time frame.
- Vehicle out of rangeThis Triggers when your vehicle is further than an allowed distance from a specific location.
- Long-distance tripThis Trigger fires when a trip is completed that is longer than a specified distance.
- Hard braking detectedTriggers when a vehicle detects a hard brake event.
- Hard acceleration detectedTriggers when your vehicle has a hard-acceleration event.
- High speed driving detectedTriggers when your vehicle is driven at speeds above a safe level (configured within Zubie).
Queries (With)
- History of trip endsThis query returns a list of the end of every vehicle trip, as indicated by the Ignition being turned off.
- History of when hard acceleration was detectedThis query returns a list of when your vehicle was a hard-acceleration event.
- History of vehicle driven between hoursThis query returns a list of when a vehicle trip ends during a selected time frame.
- History of when Check engine light was on for any vehicleThis query returns a list of when ANY vehicle's Check Engine light was been activated, caused by a Diagnostic Trouble Code (DTC).
- History of vehicle out of rangeThis query returns a list of when your vehicle was further than an allowed distance from a specified location.
- History of instances a vehicle left a placeThis query returns a list of instances when a vehicle left a place.
- History of vehicle arriving at a placeThis query returns a list of when a vehicle arrived at a specific place such as Home or Work (defined within Zubie).
IFTTT helps all your apps and devices work better together