I have my lat long set up in the weewx.conf. It's very strange. I don't
really know where it's getting the UTC from or should say not picking up
the TZ...all the involved containers have the correct TZ set up. I'm using
the SQL database that's in the same container as Weewx and obviously I wa
I think I figured it out.
Make sure you are setting your lat/lon in weewx.conf
If you leave it 0.00 for both you'll get UTC sunrise/sunset on the equator.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop rec
I do not have this problem with Seasons in 4.9.1 using the Simulator driver
under an Alpine base os.
docker-compose logs:
weealpine | weewx[1] INFO weewx.manager: Added record 2023-02-27
14:05:00 PST (1677535500) to database 'weewx.sdb'
weealpine | weewx[1] INFO weewx.manager: Added reco
No ideas? Anyone else run into this issue?
On Wednesday, February 22, 2023 at 9:15:18 AM UTC-5 rae...@gmail.com wrote:
> Another oddity I just noticed in the Seasons skin it understands that I'm
> in the EST time zone but is reporting the sunset and sunrise (and moon) in
> UTC:
>
>
>
> On Wedn
Another oddity I just noticed in the Seasons skin it understands that I'm
in the EST time zone but is reporting the sunset and sunrise (and moon) in
UTC:
On Wednesday, February 22, 2023 at 8:46:39 a.m. UTC-5 rae...@gmail.com
wrote:
> Thanks guys, I already checked this, also already set the
Thanks guys, I already checked this, also already set the TZ env variable
to EST for all my containers and issuing a date command yields all the
correct timestamps for my time zone so I have no idea where the cheetah
script that generates the images is getting that I'm in UTC.
On Saturday, Febr
You need to configure your container instance's timezone to be what you
want.
Docker host:
vince@nuc2:~$ date
Sat Feb 18 11:34:30 PST 2023
Debian10 image on that host:
vince@nuc2:~$ docker run -it --rm debian:10 date
Sat Feb 18 19:34:28 UTC 2023
Conclusion - the default debian:1
A few observations:
- WeeWX obtains timezone info from the underlying operating system, it
has nothing to do with WeeWX lat/long. I could setup my WeeWX system in
Paris and if my OS is set to AEST WeeWX will display timestamps in
Australian Eastern Standard Time.
- WeeWX records/
Just for grins, log into the container and see what it thinks the TZ is
On Friday, February 17, 2023 at 5:53:12 PM UTC-8 rae...@gmail.com wrote:
> Also the logs on my old weewx container are consistent, loop data and
> archive data has the same timezone, and the new weewx container is
> sub
Also the logs on my old weewx container are consistent, loop data and
archive data has the same timezone, and the new weewx container is
subscribed to the same mqtt data. So it's definitely something wrong with
the new weewx config, but I cannot find it. I have set the TZ environment
variable
This is in a container in my docker swarm so it's not 2 daemons running.
Really the only annoyance is the time in the html at the top left corner of
the seasons skin is displaying UTC and I cannot find where to change that.
On Friday, February 17, 2023 at 6:18:31 a.m. UTC-5 michael.k...@gmx.at
Strange log. Are there two deamons running? One (weewxd[1954]) is logging
EST, the other one (weewxd, without pid?) is logging UTC? The archive
records are not in EST, but in UTC (seconds since 01/01/1970 00:00 UTC).
Setting lat/lon won't affect anything in this context.
What is the exact probl
12 matches
Mail list logo
