Weather Updates Every 5 Minutes

[Evil_Attorney]

Not sure if this entirely belongs here, but after upgrading to V9 I noticed in the log that the weather seems to be updating every 5 minutes. Is that normal? I don't recall seeing that frequency prior to V9. Using Google Weather 2.0.3 and the latest version of Phoenix.

Mon 3/6 17:22:37.521 [Fork-XJXYO-750@1b3304e] Updating weather
Mon 3/6 17:22:37.523 [Fork-XJXYO-750@1b3304e] For location '', found instance= sage.google.weather.WeatherUnderground@1b5a285
Mon 3/6 17:22:37.524 [Fork-XJXYO-750@1b3304e] instance for '' = sage.google.weather.WeatherUnderground@1b5a285

[Narflex]

That looks like it might be getting triggered by a plugin since the UID of the STV developer who is spawning that thread is XJKYO and those of us who worked at SageTV set our UIDs to be something recognizable.

[Evil_Attorney]

Thanks. Looks like it is probably Phoenix. I'll inquire in the appropriate Phoenix forum about this.

[Evil_Attorney]

Cross post from here: https://forums.sagetv.com/forums/sho...537#post602537

It appears that Phoenix was asking for a weather update every 5 minutes. I think this has been going on for several months, but I didn't really notice it because it wasn't causing any specific issues. I uninstalled the Google weather plugin, deleted the Weather Underground cache file, then reinstalled GW, which appears to have stopped all weather updates, except by the Sage software itself, I assume since the WU cache was repopulated and I haven't seen Phoenix asking for any more updates yet.

What should the normal behavior for this be? Does Phoenix need different data than what Sage gets? How often should it update apart from Sage asking for updates?

Mon 3/6 17:22:37.521 [Fork-XJXYO-750@1b3304e] Updating weather
Mon 3/6 17:22:37.523 [Fork-XJXYO-750@1b3304e] For location '', found instance= sage.google.weather.WeatherUnderground@1b5a285
Mon 3/6 17:22:37.524 [Fork-XJXYO-750@1b3304e] instance for '' = sage.google.weather.WeatherUnderground@1b5a285

* merged topics *

[Opus4]

It would be normal for the STV to check for a weather update every 5 minutes, but the weather plugin should only actually perform an update at a longer interval. Looking at my logs for the default STV + weather plugin, that is what is happening.

If your customized STV is using my weather plugin and somehow getting it to actually download the weather data every 5 minutes, I would wonder how the weather plugin is getting used in that way because the log should be saying "Not time to update weather yet" for most of those every-5-minute checks.

If someone else's weather plugin is being used, then ignore my post.

Andy

[Evil_Attorney]

Ok, it is back to frequent updates, as seen below (possibly more frequently than before). This can't be normal, can it? why would weather updates be needed so frequently? First, I'm assuming that the XJXYO tag denotes that it is Phoenix requesting the weather. I have no idea whether Phoenix gets the weather by itself or through the Google Weather plugin.

Thu 3/9 23:19:42.516 [Fork-XJXYO-750@3122b9] Updating weather
Thu 3/9 23:19:42.518 [Fork-XJXYO-750@3122b9] For location '', found instance= sage.google.weather.WeatherUnderground@942884
Thu 3/9 23:19:42.519 [Fork-XJXYO-750@3122b9] instance for '' = sage.google.weather.WeatherUnderground@942884
Thu 3/9 23:19:42.521 [Fork-XJXYO-750@3122b9] Full Weather Update string URL = http://api.wunderground.com/api/conditions/forecast10day/astronomy/alerts/q/90292.xml
Thu 3/9 23:19:42.522 [Fork-XJXYO-750@3122b9] downloading from:http://api.wunderground.com/api/conditions/forecast10day/astronomy/alerts/q/90292.xml
Thu 3/9 23:20:57.054 [Fork-XJXYO-750@9f83fc] Updating weather
Thu 3/9 23:20:57.056 [Fork-XJXYO-750@9f83fc] For location '', found instance= sage.google.weather.WeatherUnderground@942884
Thu 3/9 23:20:57.057 [Fork-XJXYO-750@9f83fc] instance for '' = sage.google.weather.WeatherUnderground@942884
Thu 3/9 23:20:57.059 [Fork-XJXYO-750@9f83fc] Full Weather Update string URL = http://api.wunderground.com/api/conditions/forecast10day/astronomy/alerts/q/90292.xml
Thu 3/9 23:20:57.060 [Fork-XJXYO-750@9f83fc] downloading from:http://api.wunderground.com/api/conditions/forecast10day/astronomy/alerts/q/90292.xml
Thu 3/9 23:21:00.318 [Ministry@171a695] Ministry is waiting for 180 sec
Thu 3/9 23:21:45.525 [Fork-XJXYO-750@5b8f2c] Updating weather
Thu 3/9 23:21:45.527 [Fork-XJXYO-750@5b8f2c] For location '', found instance= sage.google.weather.WeatherUnderground@942884
Thu 3/9 23:21:45.528 [Fork-XJXYO-750@5b8f2c] instance for '' = sage.google.weather.WeatherUnderground@942884
Thu 3/9 23:21:45.530 [Fork-XJXYO-750@5b8f2c] Full Weather Update string URL = http://api.wunderground.com/api/conditions/forecast10day/astronomy/alerts/q/90292.xml
Thu 3/9 23:21:45.531 [Fork-XJXYO-750@5b8f2c] downloading from:http://api.wunderground.com/api/conditions/forecast10day/astronomy/alerts/q/90292.xml
Thu 3/9 23:24:00.319 [Ministry@171a695] Ministry is waiting for 180 sec
Thu 3/9 23:24:42.811 [Fork-XJXYO-750@3122b9] Updating weather
Thu 3/9 23:24:42.813 [Fork-XJXYO-750@3122b9] For location '', found instance= sage.google.weather.WeatherUnderground@942884
Thu 3/9 23:24:42.814 [Fork-XJXYO-750@3122b9] instance for '' = sage.google.weather.WeatherUnderground@942884
Thu 3/9 23:24:42.816 [Fork-XJXYO-750@3122b9] Full Weather Update string URL = http://api.wunderground.com/api/conditions/forecast10day/astronomy/alerts/q/90292.xml
Thu 3/9 23:24:42.817 [Fork-XJXYO-750@3122b9] downloading from:http://api.wunderground.com/api/conditions/forecast10day/astronomy/alerts/q/90292.xml
Thu 3/9 23:25:57.264 [Fork-XJXYO-750@9f83fc] Updating weather
Thu 3/9 23:25:57.266 [Fork-XJXYO-750@9f83fc] For location '', found instance= sage.google.weather.WeatherUnderground@942884
Thu 3/9 23:25:57.267 [Fork-XJXYO-750@9f83fc] instance for '' = sage.google.weather.WeatherUnderground@942884
Thu 3/9 23:25:57.269 [Fork-XJXYO-750@9f83fc] Full Weather Update string URL = http://api.wunderground.com/api/conditions/forecast10day/astronomy/alerts/q/90292.xml
Thu 3/9 23:25:57.270 [Fork-XJXYO-750@9f83fc] downloading from:http://api.wunderground.com/api/conditions/forecast10day/astronomy/alerts/q/90292.xml
Thu 3/9 23:26:45.784 [Fork-XJXYO-750@5b8f2c] Updating weather
Thu 3/9 23:26:45.785 [Fork-XJXYO-750@5b8f2c] For location '', found instance= sage.google.weather.WeatherUnderground@942884
Thu 3/9 23:26:45.785 [Fork-XJXYO-750@5b8f2c] instance for '' = sage.google.weather.WeatherUnderground@942884
Thu 3/9 23:26:45.786 [Fork-XJXYO-750@5b8f2c] Full Weather Update string URL = http://api.wunderground.com/api/conditions/forecast10day/astronomy/alerts/q/90292.xml
Thu 3/9 23:26:45.786 [Fork-XJXYO-750@5b8f2c] downloading from:http://api.wunderground.com/api/conditions/forecast10day/astronomy/alerts/q/90292.xml

[Opus4]

Just a note: the STV should be able to call the weather updater as often as it wants, but the weather system is supposed to be tracking its own property to know when the last actual downloaded update occurred so the next download won't be for at least 30 minutes or more. At this point, I don't know whether there is something in Phoenix or elsewhere that might be bypassing that time limit property check.

Andy

[bialio]

The P3 UI does query for updated weather on a 5 minute interval.

In that snippet of log it seems like somehow there are two weather threads running. That's not normal, but not overly worrisome either.

I think phoenix uses it's own weather provider and NOT Opus4's (i.e. the one that the default STV uses), although @stuckless or one of the gemstone guys probably knows better than I do. If there's any kind of throttling etc.

btl.

[stuckless]

Phoenix, itself, does not have a weather thread, and updates are initiated via the UI.

Something that I noticed some time ago using Phoenix v2 was that it created multiple threads that would check for weather. ie, multiple extender connections would create new threads, etc, and the most troubling thing that I found was that these threads would never die (at least they'd appear to live even after the cliient connection was ended, based on enabling STV logging).

Internally, Phoenix has 2 weather plugins, Yahoo and Weather Underground. Each of these plugins have their own internal check interval set to 180 minutes and 15 minutes respectively. So, calling Update() on the weather within those time should prevent it from actually updating at all.

I'm in the process of updating weather (based on this topic) to include some extra configuration options (is check interval exposed).

Also if you set Phoenix logging to Debug, you see all the weather requests in the phoenix logs.

[jusjoken]

Originally Posted by stuckless

Phoenix, itself, does not have a weather thread, and updates are initiated via the UI.

Something that I noticed some time ago using Phoenix v2 was that it created multiple threads that would check for weather. ie, multiple extender connections would create new threads, etc, and the most troubling thing that I found was that these threads would never die (at least they'd appear to live even after the cliient connection was ended, based on enabling STV logging).

Internally, Phoenix has 2 weather plugins, Yahoo and Weather Underground. Each of these plugins have their own internal check interval set to 180 minutes and 15 minutes respectively. So, calling Update() on the weather within those time should prevent it from actually updating at all.

I'm in the process of updating weather (based on this topic) to include some extra configuration options (is check interval exposed).

Also if you set Phoenix logging to Debug, you see all the weather requests in the phoenix logs.

And it should be noted that the Weather Underground provider in phoenix is a wrapper of the sage.google.weather jar that Opus4 wrote.

k

[stuckless]

I'll be pushing out some weather updates this morning. I've updated the API to include some extra features...

1. While each provider can have it's own update check interval, the main API will one as well (configurable) and any attempt to Update() the weather during this interval will be ignored.

2. The API will ignore changes that are the same. ie, setting same provider over and over, or setting the same units or locations, etc, will just be ignored, and not passed to the implementation.

3. The weather configuration can be "locked" (in BMT Weather Configuration). ie, if you have weather set to Yahoo with a location and units, you can "lock" it so that any API request to change this this will be ignored. I did this mainly because of a bug in Gemstore where it keeps changing my weather provider and units.

[Evil_Attorney]

It appears that with the new update of Phoenix, I am seeing weather requests in the Sage log at about 30 minute intervals. Not exactly sure how to kick up Phoenix logging to the debug level. Is this a setting in the Sage properties file?

[stuckless]

Originally Posted by Evil_Attorney

It appears that with the new update of Phoenix, I am seeing weather requests in the Sage log at about 30 minute intervals. Not exactly sure how to kick up Phoenix logging to the debug level. Is this a setting in the Sage properties file?

Not sure if you were asking about the update interval setting or logging settings...

The update interval will be in the Sage.properties

phoenix/weather/updateInterval=1800

It's the number of seconds that must pass between allowed update requests. (default is 1800 seconds or 30 minutes).

The actual provider may actually use another value... for example Weather Underground defaults to 1.5 hours. This value is there is prevent passing on weather requests to the "real" provider until at least a certain amount of time has passed.

The value can be changes in the BMT config as well.