Cumulus Support

After a period away from weather logging due to WMR968 weather station failure and general apathy, I have just reinstalled CumulusMX (current version) with a VP2 as a clean install on a PC (rather than the previous Pi).
I have created a Met office Wow account, configured CMX up with the correct Site id generated by Met office WOW and used the 6 digit authentication code i provided, yet WOW says there's no observations against the ID.
If i look in MXdiags, recent log file i can see that a series of WOW URLs are created along the lines of:
2020-06-02 10:35:24.185 Creating WOW URL #11
2020-06-02 10:35:24.185 http://wow.metoffice.gov.uk/automaticre ... =updateraw

However, when the uploads are initiated I see the following:
2020-06-02 10:35:24.848 Uploading WOW archive #1
2020-06-02 10:35:25.430 WOW Response: BadRequest: Bad Request
I see the same response for each of the 11 attempted uploads of archives.

Updates to WU are going fine...
2020-06-02 10:35:24.185 Creating WU URL #11
2020-06-02 10:35:24.185 http://weatherstation.wunderground.com/ ... =updateraw
2020-06-02 10:35:26.795 Uploading WU archive #11
2020-06-02 10:35:26.980 WU Response: OK: OK
2020-06-02 10:35:26.980 End of WU archive upload

Anyone got any ideas?

are you uploading data with less that 5 minute intervals?

Hi Simon,
No, it is set at 15 minute update to Met WOW.
VP2 datalogger is set at 10 minutes, as are local web file updates.

You usually get a bad request if your authentication data is incorrect. I would double-check what Cumulus is using.

Have a look at your Cumulus.ini file starting at Line 951 and make sure the data is correct. (ID and Password) You cant see the passwrd / pin on the Cumulus settings page. You can also see if its enabled, interval etc.

Silly question ...... but have you checked your ID on the WOW website to see its set up or correct.
Go to https://wow.metoffice.gov.uk/ and enter your 9-digit ID in the search box and hit the search icon.

BTW, the WOW pages are very slow at the moment.

After double checking, I had used my user ID rather than the station ID of 949b6063-52a4-ea11-8b71-0003ff59a5f8, which shares the same last 20 characters. As it is a site added later to WOW, this is a newer format of ID according to WOW help. I didn't look clearly enough at the complete string and only compared the last few characters..
There is current data shown now, but nothing historic. So I am not sure if it will catch up on the previous couple of days since logging began?

Thanks all for the input..