Cumulus Support

Hi Frank,
Your webite has a nice layout !
Congratulations!
For theCMX UI site, realtimegauges.txt is not found and should be in the same path than realtime-x.txt which is OK.

Frank G wrote: ↑Mon 20 Apr 2020 11:30 am Hi, thanks for the fast reply.
I did a (quick) new basic installation, just set the timezone (nothing else), but the result is the same ...

I can confirm ...having the same result: NaN for Temperature and also sometimes NaN for APPARENT TEMP and Pressure ...but only sometimes.

What I did is:
1. I stopped Cumulusmx
2. I connected to the FTP Server and opened the file realtime-x.txt
20.04.20~19:07:18~13,5~30~-3,8~10~28~315~0,0~0,0~1022,8~NW~2~km/h~C~hPa~mm~1........................
In bold you can see the temperature
When I change the temperature from 13,5 to 13.5 - the NaN goes away.
20.04.20~19:07:18~13.5~30~-3,8~10~28~315~0,0~0,0~1022,8~NW~2~km/h~C~hPa~mm~1........................

If you want to verify......here is my live webpage: https://wetter.jankreutzer.de this page should show the NaN value for Temperature
A static webpage with modified realtime-x.txt can be found here https://wetter.jankreutzer.de/_static/index.php

the config file looks like this:
var decimalComma = true; // =false for '.' as decimal point, = true for ',' (comma) as decimal point

Btw: very good work ....template looks very good.

Jan

For theCMX UI site, realtimegauges.txt is not found and should be in the same path than realtime-x.txt which is OK.

Thanks, yes, I forgot to copy the realtimegauges.txt in the CMX-UI binder. Now done ...
Now I have a "JpGraph error", but this is another story ...

20.04.20~19:07:18~13,5~30~-3,8~10~28~315~0,0~0,0~1022,8~NW~2~km/h~C~hPa~mm~1........................
In bold you can see the temperature
When I change the temperature from 13,5 to 13.5 - the NaN goes away.
20.04.20~19:07:18~13.5~30~-3,8~10~28~315~0,0~0,0~1022,8~NW~2~km/h~C~hPa~mm~1........................

I did the same "investigation" with the same result as Jan figgured out. It seems, that it is a "comma" issue of the current temperature.
And, another point, If I changed from "dot" to "comma" (ajaxCUmx.js), during the refresh the values remain "white", just the values for the current temperature change to "green". (Perhaps it helps ...)

Ajax is effectively an implementation of JavaScript, Frank, that language does not recognise anything other than full stop for the symbol between integer and decimal parts of a real number. So if your locale uses comma, then the text file has to be generated from the remove comma versions of web tags. The problem only occurs sometimes, Jank, because Cumulus will output (for example) 3 rather than 3,0 with a standard web tag.

Well,
1. If the only thing you set was the timezone then you have not completed the configuration steps required.
2. If the install is that basic how come you have German text on the dashboard?

Or did you do this install basic install somewhere else we can't see?

Please help us to help you.

One thing appeals to me: Frank and Jank both have German as their language
Not sure it's related.
They have comma as decimal point and there are full stop in the date separator

20.04.20~19:07:18~13,5~30~-3,8~10~2

Mine look like this :

20/04/20~23:10:05~13.7~54~4.5~4.3~3

Frank G wrote: ↑Mon 20 Apr 2020 7:39 pm ..
Now I have a "JpGraph error", but this is another story ...

The *.json files are no found. they should also be in the same path than the realtime...etc it is for the same reason that the charts do not work!

Answer deleted

Updated Files sets in First post.
Enjoy !!

@sfws
What about people who want decimal commas and not decimal points?

@sfws: @BCJkiwi:
It is time it is decided whether 1) the webtags are Cumulus internal data to be processed by the client or 2) are server processed data which actually are part of the display layer. The realtime.txt files should definitely be raw data to be read by the client which converts and output data to the user as the user wants. To accommodate that mechanism on all places in the world you have to apply the locale as late as possible.

This comes close to the discussion sfws started in my CumulusUtils thread but which I kindly cut off. Yet it may be necessary to complete this discussion somewhere because I think it is necessary to avoid confusion as described here just before. There must be true clarity on where the formatting takes place (where the locale becomes the rule).

If I understand it well, there is a V4 of cumulus being built which is much stricter, but those limits are not clear and have not been published yet.
Before getting there we might set some rules for system limits interfaces between Cumulus and surrounding tools.
If I read the discussion here, those rules are not clear and confusing.

BCJKiwi wrote: ↑Tue 21 Apr 2020 4:28 am Updated Files sets in First post.

Hello BCJKiwi , should this update fix the "comma seperator" problems ?
Jan

The Ajax is just JavaScript and it can only take input where all real values use full stops. Therefore the file being processed at real time interval must contain decimal points.

If you want to display decimal commas, then you can do that as you can format any output however the user wants, and in this case according to the locale used by client.

jank wrote: ↑Tue 21 Apr 2020 6:19 am should this update fix the "comma seperator" problems ?

The problem is that not all the web tags required by these web pages are available in RC format in Cumulus 1, and this web page package is intended to work with both flavours.

Please note you will find all changes listed for any release by him in files, within the distribution, like UIwebsiteMX\Changelog2020Apr20.txt (and the equivalent for C1).

sfws wrote: ↑Tue 21 Apr 2020 7:11 am

jank wrote: ↑Tue 21 Apr 2020 6:19 am should this update fix the "comma seperator" problems ?

I don't think that has been addressed yet, it is not easy to solve, I imagine BCJkiwi will be still thinking about it.

Thank you for the answer ....I am currently thinking about to change my locale to english....also converting all data files from , to .
.....but this is just an idea
...I just checked .....and yes, this would solve the problem with this UI

But what impact will this have, changing the locale ? I don't care if the seperator is a comma or a full stop in the dashboard......is there any other disadvantage ?
Jan