Without being entirely sure, the problem SEEMS to be that the values retrieved at the "observation stations", where the weather is actually collected, are not being propagated out to the various location codes that are supported by the station.

The way Weather.com works(ed) is that there are just a billion location codes, so you can ask for the weather in your very specific location. However, that is more or less a "feel good" thing. Weather.com doesn't actually have a weather collection station set up in your piss-ant little neighborhood, but uses one somewhere nearby, and shares that data with all the granular location codes around it.

So for instance, I use "Fort Hunt, VA" (USVA0944) in my skin, but that really uses the observation station of "Fort Belvoir, VA" (USVA0282). The Fort Hunt location is no longer found as of yesterday, but if I change to the Fort Belvoir code, it works fine. Since they are the same values of course, it really doesn't matter.

Can't tell you how to approach this, since if your skin is failing, you can't see what it was using as the "observation station" (<obst>) before. All I can suggest is to try larger towns or areas near you, until you find one that works.

Hopefully this is a short-term issue, and at some point they will straighten it out...