Cumulus Support

It was suggested that as an alternative to logging into C MX from afar, via the internet, uploading to one or more of the online weather systems like WOW would work, except I am struggling to get it to work.

I have the R Pi configured with its own unique fixed IP on my LAN, via my dhcpcd.conf settings including the router's IP and the router's IP for DHCP.

I have a WOW account set up. I have configured the account details into C MX, set it to send every 5 minutes, configured my correct Lat/Long yet I am not appearing on the WOW map.

Looking at the text files in MXdiags they seem to be repeatedly complaining about an 'error at line 8622 of data/jul18log.txt' and every few minutes in the log, I see....
2018-07-19 11:58:29.619 Error connecting ftp - Connection refused
2018-07-19 11:58:30.044 Error uploading web/realtimegauges.txt to realtimegauges.txt : Connection refused

Ignoring the 8622 error for now - I have not made any configuration changes at all to my router, since setting up the Pi, do I need to?

None of those errors are relevant = turn off the realtimegauges.txt setting to stop that error message.

I think it just takes a while for you to appear on the map. Did you restart MX after applying the WOW config?

steve wrote:None of those errors are relevant = turn off the realtimegauges.txt setting to stop that error message.

I think it just takes a while for you to appear on the map. Did you restart MX after applying the WOW config?

I am not sure how/where to turn off realtimegauges.txt ?

No I didn't restart MX yesterday evening after setting it up, but the the Pi is set up to do an automatic full reboot at 02:58, in the early hours. My station has still not appeared 13 hours later..

Does this snippet from MXdiags/20180719-192131.txt give any clue as to what is going wrong please?

2018-07-19 19:21:40.082 http://wow.metoffice.gov.uk/automaticre ... =updateraw
2018-07-19 19:21:40.083 End processing history data
2018-07-19 19:21:40.091 Start Timers
2018-07-19 19:21:40.091 Starting 1-minute timer
2018-07-19 19:21:40.093 Starting Realtime timer, interval = 30 seconds
2018-07-19 19:21:40.098 Uploading WOW archive #1
2018-07-19 19:21:40.580 WOW Response: BadRequest: Bad Request

harrym1byt wrote:Does this snippet from MXdiags/20180719-192131.txt give any clue as to what is going wrong please?

2018-07-19 19:21:40.082 http://wow.metoffice.gov.uk/automaticre ... =updateraw
2018-07-19 19:21:40.083 End processing history data
2018-07-19 19:21:40.091 Start Timers
2018-07-19 19:21:40.091 Starting 1-minute timer
2018-07-19 19:21:40.093 Starting Realtime timer, interval = 30 seconds
2018-07-19 19:21:40.098 Uploading WOW archive #1
2018-07-19 19:21:40.580 WOW Response: BadRequest: Bad Request

I already had a Weather Underground account from way back, so I set MX up to try that. It produces exactly the same complaint from WU as it did/does from WOW. Obviously, an issue common to both sites problem???

I have tested my WU login details and it is fine.

You appear to be using your WOW username rather than your site ID.

steve wrote:You appear to be using your WOW username rather than your site ID.

I am - I assumed it (MX) needed username and password to upload the data . I used username for WU too, which might explain that problem.

Where do I find my site ID?

WOW (and WU) create the IDs when you register your station. I can't remember how you find them if you don't know them (and the systems have probably changed considerably since I last used them).

Now working via WU - thank you very much for the help Steve...