Belchertown v1.1 with weewx 4.1.0 on Pi3 8day forecast date format

71 views
Skip to first unread message

Neville Davis

unread,
Jun 1, 2020, 3:05:23 AM6/1/20
to weewx-user
My Pi3 has local setup for Australia the only date issue I have is with the Darksky forecast headed with for example 6/1 instead of our 1/6 . All other dates seem OK.

In the index template we just load forecast I can see no where I can configure it.

The main header for this section is 8 Day Forecast Last Updated on 1 June 2020 4:40 PM...I have Mon 6/01 on the daily forecast.

My locale config

LANG=en_AU.UTF-8

LANGUAGE=en_AU.UTF-8

LC_CTYPE="en_AU.UTF-8"

LC_NUMERIC="en_AU.UTF-8"

LC_TIME="en_AU.UTF-8"

LC_COLLATE="en_AU.UTF-8"

LC_MONETARY="en_AU.UTF-8"

LC_MESSAGES="en_AU.UTF-8"

LC_PAPER="en_AU.UTF-8"

LC_NAME="en_AU.UTF-8"

LC_ADDRESS="en_AU.UTF-8"

LC_TELEPHONE="en_AU.UTF-8"

LC_MEASUREMENT="en_AU.UTF-8"

LC_IDENTIFICATION="en_AU.UTF-8"

LC_ALL=


Do I have to set something in the dark sky settings in weewx.conf?


Neville


 11%
 3 | 10 km

Neville Davis

unread,
Jun 1, 2020, 7:39:38 AM6/1/20
to weewx-user
I have tried weewx.conf belchertown_locale = “en_AU.UTF-8” and also set to “auto” neither corrected the date configuration of the forecast elements.

Pat

unread,
Jun 1, 2020, 8:20:00 AM6/1/20
to weewx-user

Pat

unread,
Jun 1, 2020, 8:21:36 AM6/1/20
to weewx-user
In skin.conf, you're probably looking at this option to change. You'll need to restart weewx when you've made the change

        time_forecast_date                      = "ddd M/DD"

Neville Davis

unread,
Jun 1, 2020, 7:20:16 PM6/1/20
to weewx-user
Pat
Thanks very much, fixed the issue.
In my defence I have been rebuilding my system up from the ground with i2C and 1wire sensors with defaulted python3 with weewx 4.1 and a Pi that simply would not enable my locales. My system would only behave with US locales installed, could not install AU locales without the US also installed, and it would not let be default to AU.......searches revealed this problem is not isolated but is the first time I have seen it and I have multiple Pi's.
My solution (after all other suggestions failed and 36 hrs later) was to install US, GB, AU..then edit ?etc/default/locale ( gets edited by update-locale) to

  File generated by update-locale

LANG=en_AU.UTF-8

#LC_ALL=en_US.UTF-8

LANGUAGE=en_AU.UTF-8

#LC_TIME="en_AU.UTF-8"


Problem fixed until I rebuild :) just need to keep notes. Anyway I thought the skin date problems were a hangover from this issue and I should have read the full readme....


It's looking good and I really like the live update. I have  DarkSky active (my previous build used it) so good for a little while...I have had no experience with the other potential candidates.


Once again thanks very much

Neville 
Reply all
Reply to author
Forward
0 new messages