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
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
> U
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
gt; <http://weewx.com/docs/usersguide.htm#Running_directly>, post a couple
>> of archive periods of WeeWX output when running WeeWX directly.
>>
>> Gary
>> On Saturday, 18 February 2023 at 12:55:51 UTC+10 vince wrote:
>>
>>> Just for grins, log int
nment
variable for the container so it should have the right time zone as well.
On Friday, February 17, 2023 at 8:46:53 p.m. UTC-5 rae...@gmail.com wrote:
> 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 to
ything in this context.
>
> What is the exact problem? Wrong data collection, wrong representation in
> the HTML or just the strange log?
> rae...@gmail.com schrieb am Donnerstag, 16. Februar 2023 um 19:55:24
> UTC+1:
>
>> So after many years of running weewx version 3.8 I decide
So after many years of running weewx version 3.8 I decided to spin up
another docker container with the latest version and start migrating
everything over to it. I use an MQTT server that my sensors publish their
various data to and then read that using the wxMesh driver to populate in
the wee
