alltime.ini

[colsceg]

in alltime.ini the value for the hightempvalue will allways be overriden to the actual temp of the actual day.
I copied the alltime.ini from Cumulus1 (changed comma to period).

hightempvalue=38.4
highttemptime=02.07.2015 16:42:10

and after the next update

hightempvalue=27.4 (this was the highest value of today)
highttemptime=06.07.2015 18:37:16

the lowtempvalue stays as it was

what could be the reason, where did it get the value for the comparison to decide if it is higher or not?

colsceg

[steve]

The most likely reason would be that it couldn't read the original 38.4 value from the file correctly. Please could you attach the alltime.ini after you have copied and modified it (MX will have taken a backup when you started it after you first put the copied and modified file into place), and also the alltimelog.txt file.

[colsceg]

I attached the both files alltime.ini and alltimelog.txt from the backup directory and the actual alltime.ini from the data Directory.

[steve]

It has been unable to read any of the values from alltime.ini which have a decimal point. Using MX here on a PC with UK locale, and on a Pi with German locale, and your attached alltime.ini file, it reads the values OK. If you stop it now and start it again, does the same thing happen? The high temp record reverts to the current temperature straight away? Is this on a Raspberry Pi, and if so, what locale are you using, and what version of Mono? Could you please zip up the MXdiags folder and attach it.

[colsceg]

I have started it several times and it always happens that the hightemp reverts to the current temprature.
It runs on a Raspberry PI and I start it with -lang de-DE, I changed the commas with the Windows Editor to periods, as I copied the file from Cumulus1 which runs on Windows Vista, btw I had copied it two or three times as I thought there could be something wrong with this file.
Then I deleted the alltime.ini and let the programm create a new one. Then I stopped the programm changed the value withe the nano editor on Raspberry, started the program again and it changed the value again to the current temp.
The mono version is 3.2.8

[steve]

There are a number of known issues with Mono and non-English locales, but it's odd that I can't reproduce this particular problem on my Pi. The only difference I can see with what I'm doing is that I'm not supplying the port on the command line - you don't need to do that as 8998 is the default. It's unlikely to help, but it's worth trying without that. I haven't actually set the Pi itself to German, presumably you have?

Note that you will have issues anyway with decimal commas on the Pi, as highlighted in the FAQ.

[steve]

I can reproduce the problem by setting my Pi's locale to German. It's presumably caused by one of the bugs in Mono with non-English locales. Reading the ini files works OK if the Pi is set to English but MX is run with -lang de-DE, but changing the Pi locale to German means that neither commas nor 'points' work for decimals in the ini files.