Cumulus Support

Hi,

I upgraded yesterday from 3160 to 3183, and got a very small but visible problem to my website index page. On the barometer it shows current pressure and pressure change values properly, but instead of ”falling, steady, rising etc” it just shows ”Pressure trend”.

My system is Rpi4 with bullseye with finnish locale, station is fine offset.

If it makes any difference, I have localised the barometer texts via strings.ini and it has worked properly on previous builds. Standard logging does not show any errors or other clues about any problem. Any tips how to proceed from here? Anyone else noticed same behaviour?

I just checked my "live" install and the <#presstrend> tag seems to be working OK...

http://<CMX_IP>:8998/api/tags/process.json?presstrend

Hi,
Mine seems to be showing correctly - i.e. http://komokaweather.com/cumulusmx/

Pressure (sea level)
Barometer 1022.9 hPa Falling slowly -0.3 hPa/hr

Enjoy,
Paul

mcrossley wrote: ↑Mon 09 May 2022 4:50 pm I just checked my "live" install and the <#presstrend> tag seems to be working OK...

http://<CMX_IP>:8998/api/tags/process.json?presstrend

This api call works for me too, responds properly with

{"presstrend":"Putoaa"}

So why it is not getting to website anymore?

OK, that shows that the web tag is working as expected.

So now you need to check the file that is being used to send the data to your web site.

Are you using the Cumulus supplied web site or some other template?

I use the default website, except that I have made a big work with localizing major parts of it to finnish. @mark I can pm you my website url, but rather not put it public in here because of my hosting transfer limits.

You can PM your link, but the first thing to check is the websitedata.json file in your <cmx>/web folder. Does that have any obvious errors? Probably not as that would stop all your data updating!

OK, so your websitedata.json file contains...

presstrend: "Pressure trend"

You need to check the websitedataT.json file, at line 79 that should have...

presstrend: "<#presstrend>"

Well this was interesting. I compared the file on my running CMX with the 3183 distribution zip, and no difference encountered. For a moment I was very puzzled. But then I noticed it...

My running instance websitedataT.json had windows-formatted CR-LF instead of unix LF. This does not show itself when running powershell compare-object (gc file1) (gc file2). Instead it needed Notepad++.

The problem with the website was sorted after replacing the file with correct one. Anyway I find it quite strange, that this difference broke processing of just that one webtag and not the others like wind description which also comes from strings.ini.

Of course this is all my fault, since I have been implementing your version updates to my localized website files by comparing differences between builds. Somehow I have managed to screw the linefeeds while retaining proper utf8-encoding.

Thank you and sorry.

Sami

Well, it seems I spoke too soon. If I click "FTP Now" the websitedata.json is updated properly. But when CMX runs normal interval update, then the "Pressure trend" makes a reappearance. Now this really goes over my head. I even restarted CMX to rule out possible caching of the template file, but no luck. What to check next?

You don't have another copy of websitedata being uploaded by extra files do you?

Nope, extra web files setting pages are empty except that ftp is ticked on every row on all 7 pages.

Please switch on debug logging and post the latest log file after it has run for say an hour.

You seem to have a rogue copy of the file somewhere!

Last logfile attaced, however nothing to see there I'm afraid.

Debug logging started 10.5. around 20.00 and switched off around 21.20. I also ran the Ftp now at around 21.03 to see if it would produce anything interesting, but no. The strangest thing is, that today also triggering website update with ftp now does not update the website with proper information. Strange...

Any ideas how to resolve this?