No good news for this problem.
This is the call done to WU to get the almanc data , were –your key– is your WU api key
http://api.wunderground.com/api/--your--key/almanac/lang:EN/q/39.95495,-76.66004.xml
This is the data returned:
<response>
<version>0.1</version>
<termsofService>http://www.wunderground.com/weather/api/d/terms.html</termsofService>
<features>
<feature>almanac</feature>
</features>
<almanac>
<airport_code>KTHV</airport_code>
<temp_high>
<normal>
<F>0</F>
<C>-17</C>
</normal>
<record>
<F>89</F>
<C>31</C>
</record>
<recordyear>2008</recordyear>
</temp_high>
<temp_low>
<normal>
<F></F>
<C></C>
</normal>
<record>
<F>42</F>
<C>5</C>
</record>
<recordyear>2001</recordyear>
</temp_low>
</almanac>
</response>
For your location there is no usable almanac data returned. A normal high of 0 for today seems not correct to me, same for a normal low of of . The METAR (airport) used by WU is the same as in your settings and when it is directly called, it returns the same information.
I have to adapt the script to not display these errors, or better to make a setting to not display that “normals” line.
WU returns a message when there is no data, the script reacts to that, but this is incomplete data.
===
QUESTION: Is there another, nearby airport, which more or less the same weather-conditions as your place?
Wim