Is there a high temperature weather forecast tile?

[JoeC (Joe)]

I feel like I work for @JoeC who…

Ha, I lol’d. @keithcroshaw , I think you are my biggest fan and I really appreciate it. You’re doing a way better job of making people aware of the rule builder than I am.

BTW @JoeC you need some adds on there to make some revenue or something wink

I’m just happy that people get use out of it. Maybe someday though.

[Pilotrose (Casey)]

Hey everyone,

Thanks a lot for the help. I’ve got the rule builder installed. It seems pretty cool and is much more like the programming I am used to. One thing though… Where can I get the forecast high temperature value from to input into the “these conditions are met” field?

[keithcroshaw]

That’s a toughie… perhaps you can buy @JoeC a beer to integrate the weather tile and all of it’s capabilities.

I would probably read up on writing SmartApps and write one that toggles a “Virtual Switch” when the condition is met or not then use that in the rule builder.

[sidjohn1]

@Pilotrose Forecast High / Low is not exposed by the default weather tile, but i had a slow day at work so check out ForecastHighLowTrigger.groovy. It awaits your Virtual Switch.

sidjohn1/smartthings/blob/master/ForecastHighLowTrigger.groovy

[Pilotrose (Casey)]

That’s awesome! Only issue is I have no idea how to get this code into a smartapp form on my device. I did some looking around and had no luck. Any pointers?

[JDRoberts]

@Pilotrose

That’s awesome! Only issue is I have no idea how to get this code into a smartapp form on my device. I did some looking around and had no luck. Any pointers?

See if this helps:

FAQ: An Overview of Using Custom Code in SmartThings (SmartThings Classic, Groovy Code)

So you’re new to SmartThings, you asked a question, and someone suggested “custom code” as an answer. Or you were browsing the forums, and you found something that sounded like it would be perfect for what you wanted, but again, “uses custom code.” What does that mean, how hard is it to do, and what’s the difference between a “SmartApp” and a “Device Type Handler”? (Note: the official terminology has changed a couple of times. “device type handler,” “device handler,” “DTH,” and “device type” all mean the same thing, and you will find all these terms used in the forums.) SECTION I: SMARTAPPS AND DEVICE HANDLERS: WHAT THEY ARE SmartAPPS: Tiny Programs to decide what a specific device should do when, or to collect the information from a specific device SmartApps, including the various f…

[Pilotrose (Casey)]

Well how about that… Someone had a tutorial just for folks like me

I’ve got it installed, thanks a lot. I’m going to test it out and see if it turns on my virtual device at 3:00 AM tomorrow.

I’ll let you know how that goes. Then the next step will be to probably use that rule creator to only allow the heat to be turned on IF it’s not going to be a hot day…

[JDRoberts]

I can’t easily read Groovy code because I rely on a text to speech reader, but I see that @sidjohn1 said his trigger smartapp requires a virtual switch.

Just in case you need the FAQ on creating virtual switches as well, here it is:

FAQ: Creating a virtual Device

Need a FAQ for the simplest version of this: a virtual on/off switch. Maybe even two FAQs, one for why you would want one with use case examples and one step by step how to for creating one in ST. Thanks! 2021 Update Since groovy will be going away soon, so will groovy virtual switches. One community member has written a new virtual switch creator Edge Driver for the new platform called VEdge Creator. Since edge drivers themselves are still in Beta, so is this code, but it’s worth following. Note also that while groovy virtual devices could be used without a SmartThings hub, Edge drivers will require one. [ST Edge] vEdge Creator: a virtual device generator for end users

You may have already figured that one out, a lot of people do, but for future readers we’ll include it just to cover all the bases.

[sidjohn1]

[quote=“JDRoberts, post:13, topic:20566”]
I can’t easily read Groovy code because I rely on a text to speech reader, but I see that @sidjohn1 said his trigger smartapp requires a virtual switch.
[/quote] Naw… virtual or physical… the smart app doesn’t care. I wrote it to support as many use cases as possible.

[quote=“Pilotrose, post:12, topic:20566”]
I’ll let you know how that goes. Then the next step will be to probably use that rule creator to only allow the heat to be turned on IF it’s not going to be a hot day…
[/quote] No additional code should be needed with the smart app, if you want something turned on / off at a set time or when the forecast is updated (midnight) based off the forecasted hi’s / lows of the day that smartapp will get you there.

[Pilotrose (Casey)]

I configured your smartapp to turn on a virtual switch if the high for the day was over 70F. I had it set to do it at 3:00AM. For some reason this didn’t happen. I also set the smartapp to turn off the switch after 1,320 minutes so that it was in the off position the next time the app runs.

I’ll change the time around and do some more testing.

Edit: I just realized the app looks to see if the high is at or BELOW the set temperature. That is probably why it didn’t work. I will reconfigure the virtual switch to turn on if it is a cold day instead of a hot day and it should work.
__

In regards to the additional code, I felt it was needed for what I intend to do. The hotday virtual switch is turned on by your app if it’s going to be a hot day. Then when the mode is changed to HOME, the thermostat is set to 70F for heat instead of 55F (night time and away setting). If the virtual hotday switch is on, the thermostat will remain at 55F and the heater will not turn on.

[sidjohn1]

Edit: I just realized the app looks to see if the high is at or BELOW the set temperature. That is probably why it didn’t work. I will reconfigure the virtual switch to turn on if it is a cold day instead of a hot day and it should work.

It will do both at or BELOW or at or Above, there is a toggle to change that.

[quote=“Pilotrose, post:15, topic:20566”]
In regards to the additional code, I felt it was needed for what I intend to do. The hotday virtual switch is turned on by your app if it’s going to be a hot day. Then when the mode is changed to HOME, the thermostat is set to 70F for heat instead of 55F (night time and away setting). If the virtual hotday switch is on, the thermostat will remain at 55F and the heater will not turn on.
[/quote]Unless i’m missing something it seams that it would be easier to skip the virtual switch and just go straight to the thermostat. i.e. if the forecast high is greater than 70, then set the thermostat mode to heat and set heat to 55.

[Pilotrose (Casey)]

Ahah I didn’t catch that the app could toggle between above or below. That’s great.

Well the application worked. It turned the virtual switch on.

I think your idea of skipping the virtual switch and adjusting the thermostat is perfect. Could you edit the application to allow a thermostat to be set?

Ideally, I would like the application to run anytime the MODE changes from any other mode to HOME. So when waking up (NIGHT > HOME) or coming back home (AWAY > HOME), the application would check the high for the day, then if it’s a cold day, it’d set the thermostat to 70F. If it’s a hot day, it’d set the thermostat to 55F.

I’d then keep the settings I have where activating AWAY or NIGHT mode sets the thermostat to 55F so the heater doesn’t turn on.

[JDRoberts]

The one reason for keeping the virtual switch step would be if you wanted to trigger other non-smartthings events at the same time, for example using IFTTT.

[sidjohn1]

[quote=“Pilotrose, post:17, topic:20566”]
I think your idea of skipping the virtual switch and adjusting the thermostat is perfect. Could you edit the application to allow a thermostat to be set?
[/quote]I was planning on adding thermostat anyway, cause then i would use it too. I’m just waiting for another slow day at work.

[quote=“Pilotrose, post:17, topic:20566”]
Ideally, I would like the application to run anytime the MODE changes from any other mode to HOME. So when waking up (NIGHT > HOME) or coming back home (AWAY > HOME), the application would check the high for the day, then if it’s a cold day, it’d set the thermostat to 70F. If it’s a hot day, it’d set the thermostat to 55F.
[/quote]While the app doesn’t use mode as a trigger, it is mode aware. The “Set for specific mode(s)” option at the bottom will limit the app to run only for that mode. if you want it to do different things in different modes, just run a separate copy and configure it uniquely for each mode. Same goes with most other smartapps.

[Pilotrose (Casey)]

Oh that’s great! I’m glad it’s something you could use too.

If mode change could be added as a trigger option instead of using time, that’d be amazing. Let me know! If not I may have to dive into some programming. 8)

[robinogi (Robin)]

This is a great idea. I have it installed, but when I try to configure it in the ST app, when I try to toggle “High” on, it takes me to a blank page where there is nothing to input. If I click “Done” on that page it says “Error saving unnamed page. Please contact SmartApp developer”. Any idea what’s up?

[cozdabuch (Cosmo)]

So this thread has been resurrected and hopefully after all this time since it started someone might have some info/ideas

I need a device type that will display the high and low forecast temps for the day. I need this for running thermostat programming routines with webCore. I can get away with just a high temp for the day. Is there anything someone has created to pull Hi temp forecast for the day?

Is there a smartapp that can do it and assign it to a virtual temp sensor, or a source that can can assign a value to device or variable with webcore?

ideas guys?

[ady624 (I hate Mondays)]

You should be able to do that in webCoRE directly using the $weather composite variable. Use the daily feature (look up Weather underground API for the daily feature. Others can help you figure it out, on my phone right now

[cozdabuch (Cosmo)]

@ady624
In the WU API, The forecast is simply an html link, it is not individual data points like all the current data is.

[ady624 (I hate Mondays)]

Nah, they have various data features you can call. Which one are you calling? One of them is called “forecast” - it’s not the .forecast property that contains an URL, it’s a whole different data feature. You can call it in the SmartApp with app.getWeatherFeature(‘forecast’) or you can do your own API with your own key.