[weewx-user] locale FTP template and belchertown theme

Hello, I have installed the latest version of stable weewx, belchertown theme on Raspberry (raspbian). I have a problem with coding, I want to be able to generate templates like FTP with en_US coding and belchertown with es_ES coding (the Belchertown configuration allows it). But having

Re: [weewx-user] locale FTP template and belchertown theme

Thanks Tom, but it doesn't work. The strange thing is that the first generation of the template is correct (en_US) but the second and subsequent ones are again es_ES, does the Belchertown configuration somehow prevail globally?. I don't understand how the first generation is correct. El

[weewx-user] change locale for html.tmpl with weewx 5.0.2

I read doc but i dont know this> I use Belchertown skin, and in skin.conf i generate a meteoclimatic.html.tmpl > *UPD=$current.dateTime.format("%d-%m-%Y %H:%M") *TMP=$current.outTemp.formatted *WND=$current.windSpeed.formatted *AZI=$current.windDir.formatted *BAR=$current.barometer.formatted

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

Yes, i found, thanks El jueves, 11 de abril de 2024 a las 15:45:43 UTC+2, Juan Antonio Mosquera Casais escribió: > Ok Tom, this is de problem, thanks... > > I updated to 5.0.2... but other question, i need modify rsyncupdaload.py, > where is now? > > Thanks! > > El jue

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

> > *sudo chown -R pi:pi /home/weewx* > > > > On Wed, Apr 10, 2024 at 9:49 PM Juan Antonio Mosquera Casais < > juan.antonio.m...@gmail.com> wrote: > >> Ok, thanks, sorry, this step i reply N, if i reply Y> >> >> pi@raspberrypi:/home/weewx $ source ~/

[weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

Hello, I have weewx 4.10.2 installed via setup.py, and I followed the instructions at https://github.com/weewx/weewx/wiki/v5-upgrade but when trying to start the service I get this error: Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed to locate executable

[weewx-user] Update 4.10.2 to 5.0.2 failed, not start service

I follow this instructions https://github.com/weewx/weewx/wiki/v5-upgrade And now, not start service: Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed to locate executable /home/weewx/bin/weewxd: No such file or directory Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service:

Re: [weewx-user] change locale for html.tmpl with weewx 5.0.2

try not localizing the > results. For example, > > *$monthoutTemp.max.format(localize=False)* > > See if that works. > > > > > On Thu, Apr 11, 2024 at 10:37 AM Juan Antonio Mosquera Casais < > juan.antonio.m...@gmail.com> wrote: > >> I read doc

Re: [weewx-user] change locale for html.tmpl with weewx 5.0.2

Hi, Perfect, this works: *TMP=$current.outTemp.format(localize=False, add_label=False) Thanks Tom and Karen for your support and patience El viernes, 12 de abril de 2024 a las 7:21:33 UTC+2, Karen K escribió: > Juan Antonio Mosquera Casais schrieb am Freitag, 12. April 2024 um > 07:03:

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

fer escribió: > You did not update your weewx service file, > /etc/systemd/system/weewx.service. This is step #4 in the instructions. > > > > On Wed, Apr 10, 2024 at 1:05 AM Juan Antonio Mosquera Casais < > juan.antonio.m...@gmail.com> wrote: > >> Hello, I have wee

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

post your /etc/systemd/system/weewx.service file > please. > > On Wednesday, April 10, 2024 at 10:42:39 AM UTC-7 Juan Antonio Mosquera > Casais wrote: > >> Thanks... but... step 4 done> >> >> history >> >> 1323 sudo cp /home/weewx/util/systemd/we

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

home/weewx/examples' Thanks. El jueves, 11 de abril de 2024 a las 0:12:37 UTC+2, Tom Keffer escribió: > Juan, your service file, weewx.service, looks like the old V4.10 service > file. The new V5.0 file has a few more entries. > > Double check that you did step #2: upgrade