⭐ Weather.com

[TallShultzy]

I've tried all the fixes with no luck. The error log shows multiple errors with only the info inside the [] changing.
Invalid TimeStampFormat: %Y-%m-%dT%H:%M:%S (Weather.com\Weather.com.ini - [@CurrentSunsetTime])

[jsmorley]

I've tried all the fixes with no luck. The error log shows multiple errors with only the info inside the [] changing.
Invalid TimeStampFormat: %Y-%m-%dT%H:%M:%S (Weather.com\Weather.com.ini - [@CurrentSunsetTime])

Yeah, I haven't had any luck with it today either. I'll keep an eye on it today to see if I can spot some kind of trend. I can deal with whatever they end up with, it certainly would be nice if it would just settle down one way or the other.

[Wim]

There's no specific trick to get it working other than exiting rm, deleting cookies en starting rm again. You sometimes have to try it a couple of times. It also works on a pretty random basis; sometimes everything works and sometimes nothing and sometimes some stuff works and some stuff doesn't.

Here's a screenshot from this morning's episode. The two skins on the left are down, the one top right works properly and the one bottom right only partially. This is after i restarted it. When i again had completed exiting rm/deleting cookies en restarting rm they were all down, but a refresh on each got 'm all going again.

It's very inconsistent.

WeatherSkins.PNG

[Yincognito]

Yeah, I haven't had any luck with it today either. I'll keep an eye on it today to see if I can spot some kind of trend. I can deal with whatever they end up with, it certainly would be nice if it would just settle down one way or the other.

Quick question, jsmorley: does Rainmeter's PCRE Regex support branch reset groups (i.e. in (?|(a)|(b)) both groups - a and b - would be counted as group \1), from what you're aware of? Cause if it does, that would be of tremendous help in designing an adaptive regex.

[jsmorley]

Quick question, jsmorley: does Rainmeter's PCRE Regex support branch reset groups (i.e. in (?|(a)|(b)) both groups - a and b - would be counted as group \1), from what you're aware of? Cause if it does, that would be of tremendous help in designing an adaptive regex.

I really don't know. I think you will have to just test it.

[Yincognito]

I really don't know. I think you will have to just test it.

Yep, it appears it does - just tested.
For example, something like below should capture all the forecast data (which can be then split up in smaller pieces using StringIndex and StringIndex2 in WebParser), irrespective of what version (V2 or V3) is the structure of the page source:

Code: Select all

DailyForecast="(?siU).*(?|"DailyForecast":.*".*geocode:.*".*"data":.*{((?:[^}]*{){2}.*(?:}[^{]*){2})}.*|"getSunV3DailyForecastUrlConfig":.*".*15day;geocode:.*".*"data":.*{((?:[^}]*{){1}.*(?:}[^{]*){1})}.*|"v3-wx-forecast-daily-15day":.*{((?:[^}]*{){0}.*(?:}[^{]*){0})}.*)"

Another quick question, if you don't mind: does WebParser support parent nesting? In other words, can a WebParser child measure (which takes its data from an actual parent parsing the URL) be a parent for another WebParser child measure, so that one can use StringIndex and StringIndex2 options in both measures?

[fonpaolo]

Hi all.
I came here to ask for something different, then I saw this, so I'm asking what's happening...

When did this problem start?
Are you all using the same code?
I guess you're all using it from different countries, am I right?
How often do you "hit" the site, more or less than 30 minutes?

Now that I've finally fixed my skin, I wouldn't want to start over, even if nothing has happened to me yet.

[jsmorley]

Hi all.
I came here to ask for something different, then I saw this, so I'm asking what's happening...

When did this problem start?
Are you all using the same code?
I guess you're all using it from different countries, am I right?
How often do you "hit" the site, more or less than 30 minutes?

Now that I've finally fixed my skin, I wouldn't want to start over, even if nothing has happened to me yet.

The problem started about a week ago more or less. I would expect, or at least hope, that everyone replying in this particular thread is using the same @Include files distributed in the .rmskin in the first post. However, it seems like anyone who is parsing the weather.com JSON code in any way is having the same intermittent problems. It doesn't seem to at all be related to where in the world you are, or where in the world your location code points to. I hit the site every 10 minutes, but I don't see that as a factor.

I'm not thrilled about the thought of re-parsing all this again, it's a fair amount of work. However, if the site ever settles down to one approach, where I can be relatively certain what format any given user is going to get, I'll certainly do it.

In the meantime, I think all we can do is wait to see where this is heading.

[fonpaolo]

Well, I'm asking, just because I don't use your method, and I'm doubtful if maybe I'm just lucky...

Anyway, can you please try this as RegExp code, instead of the usual "(?siU)^(.*)$", and see if it works for you?

Code: Select all

(?siU)^.*,"CmsStates":{"env:prod:locale:global":{.*,"data":{.*},"ttl":.*,"date":.*}},(.*)}},"ContentMediaQuery":{.*$

[jsmorley]

Well, I'm asking, just because I don't use your method, and I'm doubtful if maybe I'm just lucky...

Anyway, can you please try this as RegExp code, instead of the usual "(?siU)^(.*)$", and see if it works for you?

Code: Select all

(?siU)^.*,"CmsStates":{"env:prod:locale:global":{.*,"data":{.*},"ttl":.*,"date":.*}},(.*)}},"ContentMediaQuery":{.*$

This is just not the right thread for this.

To be honest, I'm just not willing to put any time into this at all, until things settle down and we see where weather.com is going to end up on this.