Here’s a strange one: I had a Vera crash recently which MCV tech support sorted for me but since then, although Datamine seems to be working perfectly when accessed from Vera UI, when I try to access a graph externally via a browser using “http:///dm/graph.html?ref=temps” for example, I just get a spinning cog.
The graph.html script seems to stop at the line “loadError(“Error communicating with Vera!”);”, but “http:///dm” or “http:///dm/index.html” take me to the Datamine graphing page, so comms with Vera are fine.
I’ve tried deleting and re-installing Datamine, without success.
I know the developer is no longer active on the forum but any pointers would be gratefully received!
Hi
what happens if you save a new graph in datamine with a new name and try to access that new graph.
Hi
just thinking what could be the possible cause, as you also wrote you had a recent vera crash. Calling the graph from a browser, other than calling via de datamine gui, could cause timing issues?
do you run DM on a usb on vera?
Solved! Eventually tracked it down to a corrupt sunrise/sunset text file on Vera! Unfortunately the only error message in graph.html is ‘Could not communicate with Vera’ - rather misleading in this case!
Thanks for your thoughts though Otje 
Intresting…
thanks for sharing the issue
I believe I have gotten more or less the exact same issue…
My VeraEdge was also acting up, among other things one of my scenes, that contains a rather large lua script, stopped doing its job.
Going into edit mode and simply re-save the scene (no changes done whatsoever) resolved that part, but as for DM I’m stuck…
So, my question;
How should I proceed from this? I’m not that familiar with the OS-side of things, so I currently have no idea how I should go about looking for corrupted files…
What commands can/should I use after SSH’ing in?
The file causing my problem was sunriseSunset.txt in the dataMine folder on Vera.
sunriseSunset looks good, I also did a test by simply renaming it, and that indeed removed the night-shading while showing graphs in dm directly (worked again after renaming it back), but graph.html still failed in both situations…
I have issued a ticket now though, as I guess this must be related to the scene that gets messed up when rebooting…
Hopefully whatever they find related to that will also fix DM…
I’ll report back here whenever I have anything to report.