Page 1 of 1

No live data

Posted: Fri 08 Apr 2016 3:31 pm
by crablab
Hi,

Having a few problems with Cumulus MX/my weather station and can't seem to find any help on my specific issues...

Running the latest version on a Pi2 and connecting to a Davis Vue

#1) Sometimes the station crashes when you start MX, the console shows a connection to the station but the Vue freezes up
#2) Assuming we actual get both the Vue and Pi talking to each other, there is some data coming back as I get the high temperatures for stuff and highest QFE etc. but no live data at all. Dashboard, Gauges and Now have nothing showing (well, dials with no data), but interestingly graphs are plotted.

I'd be interested to hear your thoughts on this.

Diags:
https://transfer.sh/U3wOE/diags.zip

Re: No live data

Posted: Fri 08 Apr 2016 4:44 pm
by steve
Davis stations freeze when archive data is being downloaded. Perhaps you don't have the Cumulus logger interval set to the same as the Vue logger interval, and hence the Vue sends all of the archive data on occasion, which can take a long time to download.

The pages you mention as having no data use web sockets on port 8002, so either your browser doesn't support web sockets, or you have a firewall issue.

Re: No live data

Posted: Fri 08 Apr 2016 4:56 pm
by crablab
steve wrote:Davis stations freeze when archive data is being downloaded. Perhaps you don't have the Cumulus logger interval set to the same as the Vue logger interval, and hence the Vue sends all of the archive data on occasion, which can take a long time to download.

The pages you mention as having no data use web sockets on port 8002, so either your browser doesn't support web sockets, or you have a firewall issue.
That could well be it - I'll check that tomorrow.
Thanks; problem is I'm accessing remotely and that port isn't being forwarded.

Is there any documentation for web socket? I'd quite like to use it as an API and get the raw data out without using FTP - possible?

Re: No live data

Posted: Fri 08 Apr 2016 5:03 pm
by steve
You'd have to look at the supplied code and view the returned data to work out how to use it - I don't have time to document it at the the moment, sorry. Note that you can get the same data using an HTTP 'get', and there is an option in the supplied code to to switch to using this instead of web sockets - see the announcements.