Hi @Jsnavely,

Try stopping the map, and then starting the map.  What do you get for a result?

Thanks,

Bill

same. Tried null out all the lights but one. Just to see if one would work. They all still flashed multiple colors when run map was selected.

I sometimes have this happen. I'll shutoff the map at night and return the next day with LED 0 on.

My guess is that you will find that its a wiring issue. Be sure the power supply for the RPI and the power supply for the LED's are both grounded together. If that's correct, then if you are using a Breadboard, move the ground pins to another hole and if necessary do the same for the digital signal pin going to the LED's. Breadboard holes can be intermittent, so try a different one. - Mark

Got my map almost completed and running a few tests.  I have the system go out every 20 minutes to get the update and have noticed that randomly one or more airports come back with not reporting the weather on each cycle.  Do you know if there is a fix for that?

FYI - there is an error with the "show weather reported as snow" buttons...

thanks..

Good catch on the Snow button.  I'll get that corrected. Regarding the no weather status, you can manually check this by appending the airport ID in question to this URL;

 https://www.aviationweather.gov/adds/dataserver_current/httpparam?dataSource=metars&requestType=retrieve&format=xml&hoursBeforeNow=1.5&stationString=KFLG 

You can see that my home airport is there and the resulting response looks like this;

<response xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XML-Schema-instance" version="1.2" xsi:noNamespaceSchemaLocation="http://aviationweather.gov/adds/schema/metar1_2.xsd">
<request_index>65346808</request_index>
<data_source name="metars"/>
<request type="retrieve"/>
<errors/>
<warnings/>
<time_taken_ms>4</time_taken_ms>
<data num_results="3">
<METAR>
<raw_text>
KFLG 232157Z 25010G21KT 10SM SCT015 BKN020 OVC050 04/02 A3004 RMK AO2 RAE57 SLP153 P0000 T00440017
</raw_text>
<station_id>KFLG</station_id>
<observation_time>2020-03-23T21:57:00Z</observation_time>
<latitude>35.13</latitude>
<longitude>-111.67</longitude>
<temp_c>4.4</temp_c>
<dewpoint_c>1.7</dewpoint_c>
<wind_dir_degrees>250</wind_dir_degrees>
<wind_speed_kt>10</wind_speed_kt>
<wind_gust_kt>21</wind_gust_kt>
<visibility_statute_mi>10.0</visibility_statute_mi>
<altim_in_hg>30.041338</altim_in_hg>
<sea_level_pressure_mb>1015.3</sea_level_pressure_mb>
<quality_control_flags>
<auto_station>TRUE</auto_station>
</quality_control_flags>
<sky_condition sky_cover="SCT" cloud_base_ft_agl="1500"/>
<sky_condition sky_cover="BKN" cloud_base_ft_agl="2000"/>
<sky_condition sky_cover="OVC" cloud_base_ft_agl="5000"/>
<flight_category>MVFR</flight_category>
<precip_in>0.005</precip_in>
<metar_type>METAR</metar_type>
<elevation_m>2134.0</elevation_m>
</METAR>

If after entering your airport instead of KFLG you don't see a tag starting <METAR> then for some reason FAA is not reporting data for that airport for some reason. There is parameter on the config editor called 'Age of Metar =' that you can lengthen to capture older data to display. I have mine set at 2.5 hours, but you can set it up to 6 hours old. Give that a try and let us know. - Mark