Troubleshooting Imports and Live Sources

Use this page when an import or live source does not behave the way you expect.

Import problems

• If the import will not continue, confirm that a timestamp column is mapped.
• If values look incorrect, check the source units and timestamp timezone.
• If the preview shows fewer rows than expected, make sure the selected date range includes the records you want.
• If a CSV import fails unexpectedly, check for blank timestamps, malformed rows, or unusual delimiters.

MeteoTemplate problems

• If the connection fails, check the MySQL URL, credentials, database name, and table name.
• If no rows are found, confirm that the table actually contains weather observations.
• If the date range looks wrong, check the DateTime values in the source database.

Weather Underground problems

• If the API key is rejected, check that you copied the whole key and that the station ID is the ICAO-style code from your dashboard, not your username.
• If no recent observations are found, confirm your station is still uploading to Weather Underground.
• If the import stops with a message about the daily API limit, nothing is wrong. Weather Underground allows about 1,500 requests per day and each request covers one day of history, so a long backfill takes several days. Meteobreeze resumes it automatically.
• If an import shows as Partly imported, check whether auto-resume is still on. If it was turned off, run the import again with the same settings.
• Re-running a Weather Underground import is safe. Days that are already fully imported are skipped without using an API call.
• If the history goes back less far than you expected, that usually reflects what Weather Underground holds rather than an import problem.

Live source problems

• If no packets appear, confirm that the device or script is still sending requests.
• If the source is disabled, re-enable it in the data sources panel.
• If the source shows an error, use the error message as the first clue.
• If values are wrong, re-check the source units or the parameter names used in the request.

CumulusMX

• If no request arrives, check that the Custom HTTP seconds/minutes interval is non-zero and that you saved the Internet settings.
• Do not open the generated URL directly. CumulusMX must expand <#timeJavaScript> and the other webtags before making the request.
• If Last error mentions a decimal comma, regenerate the URL and replace the older one in CumulusMX. Current generated numeric tags use rc=y.
• If values are converted incorrectly, match all four CumulusMX Station settings units in Meteobreeze, save them, and replace the generated URL. Existing data is not rewritten.
• Enable CumulusMX enhanced debug logging when you need to see the Custom HTTP response.

Quick checks

1. Confirm the ingest URL is correct.
2. Confirm the source is enabled.
3. Confirm the timestamp is valid.
4. Confirm the units match the source.
5. Confirm the data sources panel shows a recent packet.

FAQ

• Should I fix the source or the import file first? Start with the source or file, then retry the import.
• Can I change units after packets have started arriving? Yes, but it only affects future live packets.

Related pages

• Units
• Map fields, units, and timestamps
• Check whether data is arriving
• Import from Weather Underground

Image needed: a checklist graphic or annotated screenshot showing the most common places to inspect when something fails.