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.
• If you want a clean retry after correcting the file, units, timezone, or date range, stop the import if it is active. Then select Remove in Data sources → Import history to remove its records before starting again.

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. Meteobreeze maps the station's availability and only fetches days with data, but a long backfill can still take several days. It resumes 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 has gaps, check the preview's availability summary. This usually reflects what Weather Underground holds rather than an import problem.

Cumulus archive problems

• Upload one ZIP containing standard monthly *log.txt files. dayfile.txt and specialist sensor logs are not imported.
• Check that the archive is no larger than 150 MB, is not password-protected, and contains no more than 600 monthly logs.
• If values look wrong, select the same temperature, wind, pressure, and rain units that Cumulus used when it wrote the logs.
• If older timestamps are shifted, select the timezone in which Cumulus wrote those date-and-time-based logs. CumulusMX v5 Unix timestamps do not need this adjustment.

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
• Import from Cumulus

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