Problem with realtimegauges

[falkunmalti]

Hi

I had been running cumulusMX for a while under stretch with no problems. I use realltimegauges to display my weather at *.*.*.*:8999 and my website at www.laferla.ca/weather. But recently, and I think this coincided with my change to buster, I am missing some gauges in the locaL display. The gauges displayed on my website www.laferla.ca/weather appear to be correct without missing gauges, but my local display at :8999 shows the following two lines instead of the gauges:

false Low temperature false High temperature false Temp rising false Temp falling false Rain false Rain rate Data stopped false Low pressure false High pressure false Press rising false Press dropping false Wind gust false Wind speed false Sensor contact false Battery low

What could be wrong? I don't think I missed any steps. Appreciate help please.

Joe
VA3JLF

[PaulMy]

Hi,
Is there anything in your MXdiags file that might give a clue? Maybe need to turn on Debug and Data logging.

Enjoy,
Paul

[sfws]

What could be wrong?

In the browser where you are running the admin interface, select "Web Developer" "web console" on the tools menu if you are using Firefox, or a similar functionality in other browsers. Control and shift and K might work for you. Anyway, it should be possible somewhere to see messages about what has successfully loaded and what required files were not found.

Maybe somebody else will recognise which file is missing to bring up that text instead. I'm pretty sure it is one of the files ending in ".js", but that is as far as I can help:

<!-- jquery -->
<script src="lib/jquery/jquery-latest.min.js"></script>
<script src="lib/jquery/jquery.tmpl.js"></script>

<script src="lib/bootstrap/js/bootstrap.min.js"></script>

<!-- SteelSeries -->
<script src="lib/steelseries/scripts/steelseries_tween.min.js"></script>
<script src="lib/steelseries/scripts/language.min.js"></script>
<script src="lib/steelseries/scripts/RGraph.common.core.min.js"></script>
<script src="lib/steelseries/scripts/RGraph.rose.min.js"></script>
<script src="lib/steelseries/scripts/gauges.js"></script>

<script src="js/gaugefeed.js"></script>

[falkunmalti]

I just noticed something which might give a hint. The problem only occurs under the Dashboard selection of the interface. When I click on Gauges, all 12 gauges show up. It's been so long I don't recall how to turn on Debug and data logging for MXDiag!

I looked through the Developer Tools but could not spot anything that I could recognize.

I'm afraid, I am not being much help.

Joe

[sfws]

The problem only occurs under the Dashboard selection of the interface.

I'm afraid, I am not being much help.

Actually, that is very helpful. Ignore my last post, I thought you were talking about the gauges page in the admin interface not working.

The only relevant script in the dashboard page of the admin interface is CumulusMX\interface\js\dashboard.js. Can you check that file exists for you? Try copying it in again from the unzipped download, it last changed at MX version 3.5.4. It is just a co-incidence, of course but one of my plots with "wind barbs" in my customised web page has just stopped working, and I don't understand why as the relevant .js file calling the highcharts that does this plot has not changed. Script files do sometimes appear to be temperamental.

The other difference for the dashboard web page is a different application programming interface "api/data/currentdata". Put simply, this api sends data to the web page in json format, I don't pretend to have learnt this api yet. I doubt if this is giving you a problem as the other api are working for other pages to work, anyway I believe it would flag a message in that developer tools. But selecting debug logging would confirm this api is working.

Both gauges and the current conditions (now) page use a different api.

It's been so long I don't recall how to turn on Debug and data logging for MXDiag!

In admin interface Settings tab, station settings, Options section, select debug logging. This adds a lot of extra information to the log designed to help answer questions when someone has a problem.
There is an alternative way (to have full debugging turned on as MX starts):

Code: Select all

sudo mono CumulusMX.exe -debug

[falkunmalti]

HI

I checked dashboard.js and the file date for that is 22/4/20. File properties does not give a version number. Is this the version?

Joe

[falkunmalti]

I have not yet had any more help for my issue. It still is not resolved. Does anyone have any assistance?

Joe

[sfws]

HI

I checked dashboard.js and the file date for that is 22/4/20. File properties does not give a version number. Is this the version?

Joe

yes, file has not changed since that date.

To go back to my earlier post, have you enabled debugging as Paul and I suggested yet?

I can't see your admin interface, so i cannot tell what is going on unless I can look at the full debugging log zipped up as instructed at https://cumuluswiki.org/a/Cumulus_MX#Wh ... _a_problem

The only other suggestion I made as before is you use F12 to switch on the console tool, enable full or all outputs in that and can give me a screenshot to look at what that says.

Maybe someone else can go further, but I'm stuck.

[PaulMy]

Hi Joe,

I had been running cumulusMX for a while under stretch with no problems.

I don't know "stretch" so can't help if that is the issue.

The local Dashboard has not been an issue that I recall.
How do you do CumulusMX program updates, full new install or only selected files?

There have been some changes in the Interface files in recent version updates. Updating to latest version may be helpful, including the Interface files. You can reuse your existing Cumulus.ini, and Data and Reports folders so won't loose anything (Always have a good backup!)

If the issue still persists, the MXdiags may give some clues. Make sure Debug and Data logging is turned on in settings, then after a bit of time zip up the latest MXdiags file.

Enjoy,
Paul

[falkunmalti]

Hi

I bit late in replying , so apologies. I did turn on debug and am attaching the mxdiags.

The file cumulus on win10.txt shows the last two lines of the dashboard on chrome on win10 and cumulus on rp1 chromium.txt shows the same lines on the chromiun browser on the rpi3. Obviously a difference in rendering on win10 and raspbian. My raspbian OS is buster and I don't recall this happening when I used the previous OS version stretch.

Joe

[HansR]

If I may jump in the discussion, I have the following questions.
If I understand well:

1. We talk about the local interface, the black one with the 12 blocks where the gauges should be on the second line. Do you see any blocks at all or do you just see the line you describe?:

   Code: Select all

   false Low temperature false High temperature false Temp rising false Temp falling false Rain false Rain rate Data stopped false Low pressure false High pressure false Press rising false Press dropping false Wind gust false Wind speed false Sensor contact false Battery low
   

2. Could you make a screenshot of what you actually see and post that here to clarify what we are talking about?
3. Point is, that what you describe seems to be only the alarm footer information without markup and where everything is false (no alarms set I assume). So my question would be: where is the rest of the page? If that info is really on the place of the three gauges while the rest of the info is OK, then something has been drastically changed to the index file I suppose.

But anyway, would like to see what you see first.

[falkunmalti]

HI

I will mkae a screenshot in a while as I am tied up at the moment. Thanks for your quick response.

Joe

[PaulMy]

Likely not the cause of your issue but noticed in MXdiags -
2020-06-10 17:32:45.554 Error at line 419 of data/dayfile.txt : Input string was not in the correct format
2020-06-10 17:32:45.555 Please edit the file to correct the error
2020-06-10 17:32:45.555 Loaded 0 entries to daily data list
which you should correct.

Also it shows
2020-06-10 17:32:43.471 Debug logging is disabled
2020-06-10 17:32:43.471 Data logging is disabled

Enjoy,
Paul

[falkunmalti]

Hi

Here is my screenshot. I do have 4 test alarms set temp below, temp above, pressure falling, sensor lost.

In answer to the earlier question whether I was seeing all the squares, the screenshot answers that. I have never had problems with the other squares in the dashboard. The same two lines at the bottom are displayed even when I have no alarms.

Hope this helps. Please let me know if I can provide more clarification.

PaulMy,
Likely not the cause of your issue but noticed in MXdiags -
2020-06-10 17:32:45.554 Error at line 419 of data/dayfile.txt : Input string was not in the correct format
2020-06-10 17:32:45.555 Please edit the file to correct the error
2020-06-10 17:32:45.555 Loaded 0 entries to daily data list
which you should correct.

Could you please help me with this. I found a datafile.txt but could not find the string you refer to. Also I do not have a day.txt file that I could find. Please point out the error so that I can correct it.

Also, I am sure I had debug logging enabled when I did this although I have since turned both off.

Joe

[water01]

The file is dayfile.txt and it is in the Data directory.

Load this into a good quality editor (not Notepad, but like NotePad++) and edit line 490 where the error is. It should be obvious if you compare it to the lines above and below it.