I noticed the native weather/temperature is not working for me either. Looks like since the end of last week. I was using the Ambient Weather service plug in for a long time and switched to the native service during the migration.
I have a weather station that reports to Ambient Weather. How can I use that?
I was using Kurt Sanders DH but I believe he moved his work to Hubitat and it stopped working after the migration.
Can you post a screen shot of the routine?
The routine for my Shop A/C is a little more complex (don’t turn on if doors are open, etc) but still uses ambient temperature as the on/off trigger.
With the Groovy platform being phased out there is probably no way to use Ambient Weather anymore.
There appear to be 3 current choices.
- Use the built in weather function in your routines.
- Use @TAustin 's yet another weather app. This has several possible weather sources. The down side is you need a constantly running computer or RPi to work. WeatherUnderground and WeatherFlow Tempest have some private weather stations integrated. I don’t know if yours would work with either.
- Buy and use a ST compatible temperature and humidity sensor. This would be Z-Wave, ZigBee or possibly WiFi.
Thanks for all of the options/info. I’ve been using the native ST weather app with no issues until last Friday. I guess I’m not ready to give up on it as the other options both have drawbacks for me.
I’ve reported the issue to ST tech support. I’m a long time user and have NEVER had any luck with them. All of my only solutions have come from this forum so my hopes are limited (in regards to ST support). Is there anyone here that filled Brad_ST’s shoes?
I am using the built in weather function (temp) to control a meross switch. The issue seems to be that changes in temp are not tripping the routine. If the other condition changes the temp does get used correctly though. Is there another way to force a polling of the states?
I did some testing and had the same results. Changes in temperature using the built-in weather function are NOT causing routines to fire.
I’m experimenting now with a virtual switch that will function as a 10 min timer to force the routine to fire…
Sounds like it’s not just me…
Just received the standard response from ST tech support: Delete the app, reinstall, delete the routine, recreate… I noted this isn’t an isolated instance, yet they treat it as such…
Just confirmed with a test routine that I’m also seeing this problem.
I don’t know how many reports it takes for ST to realize they have an issue, but, has everyone reported this? Maybe that will save us from weeks of ST tech support trying to fix the user end when, in fact, it’s not us. Is there someone here we can tag?
Just reported it. Support request #1471777.
Anyone receive any resolution to this?
My test Routine using Weather worked yesterday. Will see in 5 more degrees of warming if it works today…
I apologize up front if I missed it but, what is your “test routine” testing? Testing to see if the native ST weather is triggering routines (i.e. problem solved) or something different?
Yes, it uses the temperature from the standard weather conditions. And I just got the notification when the temperature rose above the condition, so temperature at least seems to be working again.
I did some additional testing today and automations using changes in temperature via the built-in weather function are working again.