Re: [weewx-user] Periodic incorrect date from a Davis Vantage Pro 2

[Tom Keffer]

Be sure to read the wiki notes on *Moving the wview database
*.

Welcome to WeeWX! You may be the last of the wview users!

On Sat, May 11, 2024 at 8:42 PM P Black  wrote:

> Tom,
>
> Thank you.  It gives me some hope that the time warp will not be an issue
> with the new system.  The old used a Raspberry PI 3B with an added clock
> and the new is a RP5 with built-in clock.  I do use a battery backup and
> have not noticed any correlation to voltage drops and the date mix-up.
> Should have some time in the next couple weeks to load the software and
> begin transitioning the database.
>
> Thanks,
> Pat
>
> On Friday, May 10, 2024 at 4:36:09 PM UTC-4 Tom Keffer wrote:
>
>> I have never seen the Vantage emit a bad date. What does happen is either
>>
>> 1. The computer lacks a clock, so it synchronizes the Vantage to the
>> wrong time. There is a check in WeeWX to avoid starting up with a clock
>> that's really off, but the best protection is to install a real-time clock
>> in the computer.
>>
>> 2. The logger memory gets corrupted. This is pretty rare, but seems to be
>> triggered by power outages (although not always). The symptom is that WeeWX
>> fails to download any new data, so your webpage doesn't change. See the
>> Wiki article *Wiki generates HTML pages, but does not update them
>> *
>>  for
>> details. This sounds the closest to the situation you describe, but with
>> WeeWX it does not result in a record being downloaded with a bad date.
>> Perhaps wview does something different in this situation. The problem can
>> always be solved by clearing the logger memory. If you do a memory dump
>> first, it does not result in loss of data.
>>
>> Hope that answers your question.
>>
>>
>> On Fri, May 10, 2024 at 11:37 AM P Black  wrote:
>>
>>> Hello,
>>>
>>> I am in the process of migrating from wview to weewx.  Yes I know I am
>>> very late to the game.
>>>
>>> The issue I have with wview is that the Davis Vantage Pro 2 periodically
>>> generates a future date that then hangs any further data collection.  The
>>> fix usually involves:
>>>
>>>  sudo service wview stop
>>>  vpconfig /dev/ttyUSB0 cleararchive
>>> remove the bad data from the sqlite and mysql databases
>>>  sudo service wview start
>>>
>>> Then if I am late to catch this issue, I have a lot of missing data.
>>>
>>> I plan to start installing weewx in the next few days on a raspberry pi
>>> 5 with a 1TB NVMe and run using the mysql (mariadb) database choice after
>>> migrating my existing database to the new setup.
>>>
>>> Assuming that the date issue is a Davis glitch and not wview, is there a
>>> software check in weewx to determine if the date is wrong and either delete
>>> the data for that time or correct it to the correct time and then log?  I
>>> assume that the clear archive would also have to be automatically performed
>>> (how is that done by software)
>>>
>>> PS: I have tried the usual shutdown the Davis, remove batteries and
>>> still the bad date occasionally occurs.  The Davis is the wireless version
>>> purchased 2011.  Also, it must know when I am not around as the bad event
>>> occurs during my away times.
>>>
>>> Stay healthy,
>>> Pat
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/fe2e2e08-bf5b-4da4-a511-7926ede968afn%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/0ba660b1-cb93-4efb-aeb8-189a7266aa6dn%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEAghACNcs10YDwMJ%3Dacpn1%2Bv5chTkLf5fJGzSYuOb%3Dk2w%40mail.gmail.com.

Re: [weewx-user] Periodic incorrect date from a Davis Vantage Pro 2

[P Black]

Tom,

Thank you.  It gives me some hope that the time warp will not be an issue 
with the new system.  The old used a Raspberry PI 3B with an added clock 
and the new is a RP5 with built-in clock.  I do use a battery backup and 
have not noticed any correlation to voltage drops and the date mix-up.  
Should have some time in the next couple weeks to load the software and 
begin transitioning the database.

Thanks,
Pat

On Friday, May 10, 2024 at 4:36:09 PM UTC-4 Tom Keffer wrote:

> I have never seen the Vantage emit a bad date. What does happen is either
>
> 1. The computer lacks a clock, so it synchronizes the Vantage to the wrong 
> time. There is a check in WeeWX to avoid starting up with a clock that's 
> really off, but the best protection is to install a real-time clock in the 
> computer.
>
> 2. The logger memory gets corrupted. This is pretty rare, but seems to be 
> triggered by power outages (although not always). The symptom is that WeeWX 
> fails to download any new data, so your webpage doesn't change. See the 
> Wiki article *Wiki generates HTML pages, but does not update them 
> *
>  for 
> details. This sounds the closest to the situation you describe, but with 
> WeeWX it does not result in a record being downloaded with a bad date. 
> Perhaps wview does something different in this situation. The problem can 
> always be solved by clearing the logger memory. If you do a memory dump 
> first, it does not result in loss of data.
>
> Hope that answers your question.
>
>
> On Fri, May 10, 2024 at 11:37 AM P Black  wrote:
>
>> Hello,
>>
>> I am in the process of migrating from wview to weewx.  Yes I know I am 
>> very late to the game.
>>
>> The issue I have with wview is that the Davis Vantage Pro 2 periodically 
>> generates a future date that then hangs any further data collection.  The 
>> fix usually involves:
>>
>>  sudo service wview stop
>>  vpconfig /dev/ttyUSB0 cleararchive
>> remove the bad data from the sqlite and mysql databases
>>  sudo service wview start
>>
>> Then if I am late to catch this issue, I have a lot of missing data.
>>
>> I plan to start installing weewx in the next few days on a raspberry pi 5 
>> with a 1TB NVMe and run using the mysql (mariadb) database choice after 
>> migrating my existing database to the new setup.
>>
>> Assuming that the date issue is a Davis glitch and not wview, is there a 
>> software check in weewx to determine if the date is wrong and either delete 
>> the data for that time or correct it to the correct time and then log?  I 
>> assume that the clear archive would also have to be automatically performed 
>> (how is that done by software)
>>
>> PS: I have tried the usual shutdown the Davis, remove batteries and still 
>> the bad date occasionally occurs.  The Davis is the wireless version 
>> purchased 2011.  Also, it must know when I am not around as the bad event 
>> occurs during my away times.
>>
>> Stay healthy,
>> Pat
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/fe2e2e08-bf5b-4da4-a511-7926ede968afn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0ba660b1-cb93-4efb-aeb8-189a7266aa6dn%40googlegroups.com.

Re: [weewx-user] Periodic incorrect date from a Davis Vantage Pro 2

[Tom Keffer]

I have never seen the Vantage emit a bad date. What does happen is either

1. The computer lacks a clock, so it synchronizes the Vantage to the wrong
time. There is a check in WeeWX to avoid starting up with a clock that's
really off, but the best protection is to install a real-time clock in the
computer.

2. The logger memory gets corrupted. This is pretty rare, but seems to be
triggered by power outages (although not always). The symptom is that WeeWX
fails to download any new data, so your webpage doesn't change. See the
Wiki article *Wiki generates HTML pages, but does not update them
*
for
details. This sounds the closest to the situation you describe, but with
WeeWX it does not result in a record being downloaded with a bad date.
Perhaps wview does something different in this situation. The problem can
always be solved by clearing the logger memory. If you do a memory dump
first, it does not result in loss of data.

Hope that answers your question.


On Fri, May 10, 2024 at 11:37 AM P Black  wrote:

> Hello,
>
> I am in the process of migrating from wview to weewx.  Yes I know I am
> very late to the game.
>
> The issue I have with wview is that the Davis Vantage Pro 2 periodically
> generates a future date that then hangs any further data collection.  The
> fix usually involves:
>
>  sudo service wview stop
>  vpconfig /dev/ttyUSB0 cleararchive
> remove the bad data from the sqlite and mysql databases
>  sudo service wview start
>
> Then if I am late to catch this issue, I have a lot of missing data.
>
> I plan to start installing weewx in the next few days on a raspberry pi 5
> with a 1TB NVMe and run using the mysql (mariadb) database choice after
> migrating my existing database to the new setup.
>
> Assuming that the date issue is a Davis glitch and not wview, is there a
> software check in weewx to determine if the date is wrong and either delete
> the data for that time or correct it to the correct time and then log?  I
> assume that the clear archive would also have to be automatically performed
> (how is that done by software)
>
> PS: I have tried the usual shutdown the Davis, remove batteries and still
> the bad date occasionally occurs.  The Davis is the wireless version
> purchased 2011.  Also, it must know when I am not around as the bad event
> occurs during my away times.
>
> Stay healthy,
> Pat
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/fe2e2e08-bf5b-4da4-a511-7926ede968afn%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEAZgmewZQDDjs1GVLbSZ4CbFi4H0_P%2BK8RMqrKra9kUYA%40mail.gmail.com.

[weewx-user] Periodic incorrect date from a Davis Vantage Pro 2

[P Black]

Hello,

I am in the process of migrating from wview to weewx.  Yes I know I am very 
late to the game.

The issue I have with wview is that the Davis Vantage Pro 2 periodically 
generates a future date that then hangs any further data collection.  The 
fix usually involves:

 sudo service wview stop
 vpconfig /dev/ttyUSB0 cleararchive
remove the bad data from the sqlite and mysql databases
 sudo service wview start

Then if I am late to catch this issue, I have a lot of missing data.

I plan to start installing weewx in the next few days on a raspberry pi 5 
with a 1TB NVMe and run using the mysql (mariadb) database choice after 
migrating my existing database to the new setup.

Assuming that the date issue is a Davis glitch and not wview, is there a 
software check in weewx to determine if the date is wrong and either delete 
the data for that time or correct it to the correct time and then log?  I 
assume that the clear archive would also have to be automatically performed 
(how is that done by software)

PS: I have tried the usual shutdown the Davis, remove batteries and still 
the bad date occasionally occurs.  The Davis is the wireless version 
purchased 2011.  Also, it must know when I am not around as the bad event 
occurs during my away times.

Stay healthy,
Pat

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/fe2e2e08-bf5b-4da4-a511-7926ede968afn%40googlegroups.com.

[weewx-user] WDC skin date format

[Greg from Oz]

Hi,

I have noticed the date format in the headings when I select day, 
yesterday,week,month,year are correct to how I want them. IE dd/mm/yyy

Like this:
Monthly Weather Conditions
01/08/23 00:00:00 - 31/08/23 23:59:59 

But if I go to the Archive and NOAA sidebar and pick something then the 
date format changes to the US format mm/dd/yyy
Like this:
Monthly Weather Conditions 
01/01/2023 12:00:00 AM - 01/31/2023 11:59:59 PM

I have looked through the skin and tmpl files but cannot see anything that 
I can change.
I have noticed it looks like it picks up the date formatting from daily_archive 
= %Y-%m-%d in the skin but if that is so I would have expected the format 
to be /mm/dd which I would like as it is international ISO standard.

Where is the format for the date set?

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b9dc2360-6284-48d0-857a-14cadaa01d04n%40googlegroups.com.

Re: [weewx-user] Time and date format in Weewx database

[Tom Keffer]

Not to be too terribly pedantic, but unix time does deal with leap seconds.
It's just that it deals with them using a discontinuity at midnight. The
result is that if you calculate the difference in unix epoch time between,
say, 23:55 and 00:10, it will *always* be 900 seconds, even if a leap
second was inserted in there. However, if you were to calculate the
difference in UTC, it would be 901 seconds if a leap second occurred.

99.9% of the time, this is what you want. It's a brilliant solution to a
difficult problem. The only problem is that every couple of years or so,
there will be a unit timestamp that is ambiguous. There will be two times
with the same timestamp.



On Fri, Nov 4, 2022 at 3:35 AM Greg Troxel  wrote:

>
> Phillip Fischer  writes:
>
> > Thank You! I am fairly new to the world of linux and learning new things
> > each day! I appreciate your time to answer my question.
>
> This is likely beyond what you care about, but note that the time values
> are the number of seconds since January 1, 1970 UTC **as if there were
> no leap seconds**.
>
> But with weather data every 15 minuts, that just means that occasionally
> those timestamps that differ from 900 will be 901 (or maybe in the
> future 899 seconds apart).  And, surely your weather station doesn't
> have leap second support, and your computer doesn't have a network
> connection.
>
>
> But seriously, I don't know how you are dealing with time, and probably
> you want to have a GPS receiver and run ntpd to sync the RPI's clock,
> and understand how that relates to the weather station's clock.
>
> You probably also want to run the RPI in UTC, and also the weather
> stations, so that there is no daylight savings time confusion.  weewx
> does not as far as I know support "operate in UTC but produce
> graphs/summaries in local time (meaning "today" as a 24h period,
> min/max, etc.)".  But you are just going to process the weewx.sdb
> elsewhere.
>
> I would also put a USB SSD or stick in the Pi and back up the weewx.sdb
> to that daily, in a way that doesn't overwrite the previous backups.
> And a UPS (even a Pi UPS with a battery, but beware of lithium batteries
> below freezing).
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/rmimt9757os.fsf%40s1.lexort.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEAJxSXy1dOwePPPWDVXuSoPGdfYVUx9R4kvk%2Bpm%3DDsSsg%40mail.gmail.com.

Re: [weewx-user] Time and date format in Weewx database

[Greg Troxel]

Phillip Fischer  writes:

> Thank You! I am fairly new to the world of linux and learning new things 
> each day! I appreciate your time to answer my question.

This is likely beyond what you care about, but note that the time values
are the number of seconds since January 1, 1970 UTC **as if there were
no leap seconds**.

But with weather data every 15 minuts, that just means that occasionally
those timestamps that differ from 900 will be 901 (or maybe in the
future 899 seconds apart).  And, surely your weather station doesn't
have leap second support, and your computer doesn't have a network
connection.


But seriously, I don't know how you are dealing with time, and probably
you want to have a GPS receiver and run ntpd to sync the RPI's clock,
and understand how that relates to the weather station's clock.

You probably also want to run the RPI in UTC, and also the weather
stations, so that there is no daylight savings time confusion.  weewx
does not as far as I know support "operate in UTC but produce
graphs/summaries in local time (meaning "today" as a 24h period,
min/max, etc.)".  But you are just going to process the weewx.sdb
elsewhere.

I would also put a USB SSD or stick in the Pi and back up the weewx.sdb
to that daily, in a way that doesn't overwrite the previous backups.
And a UPS (even a Pi UPS with a battery, but beware of lithium batteries
below freezing).

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/rmimt9757os.fsf%40s1.lexort.com.


signature.asc
Description: PGP signature

Re: [weewx-user] Time and date format in Weewx database

[Phillip Fischer]

Thank You! I am fairly new to the world of linux and learning new things 
each day! I appreciate your time to answer my question.

I've successfully converted the time and date stamps!

On Friday, 4 November 2022 at 11:33:50 UTC+2 peterq...@gmail.com wrote:

> A little more background. It's a unix epoch datetime. The number of 
> seconds since 1970 iirc. Google unix epoch.
>
> On Fri, Nov 4, 2022, 10:14 AM Glenn McKechnie  
> wrote:
>
>> unixepoch, epochtime, unixtime
>>
>> from a linux terminal...
>>
>> $ date -d now +'%s'
>> 1667553105
>>
>> $ date -d @1667553105
>> Fri 04 Nov 2022 20:11:45 AEDT
>>
>> man date
>>
>> within a mysql (mariadb)...
>> SELECT FROM_UNIXTIME(datetime, '%d-%m-%Y %H:%i') from archive WHERE
>> dateTime = 166734;
>>
>> there'll be something similar for sqlite
>>
>> On 04/11/2022, Phillip Fischer  wrote:
>> > I hope that someone would be able to point me in the right direction.
>> >
>> > I am aiming to use Weewx to log data from a weather station console of a
>> > station that is set up in a remote, out of the way area as part of my
>> > research. Due to an oversight in Station specs, I was given a station 
>> that
>> > will need to be downloaded every two weeks or else the data is 
>> overwritten,
>> >
>> > but getting to the site every two weeks is not going to happen!
>> >
>> > I've got the station running, connected to a Raspberry Pi Zero 2 and it 
>> is
>> > working and logging data without issue.
>> >
>> > It is easy to get into the .sdb and convert the data to .csv for export 
>> to
>> > analyse the data off site. There is no cell signal, wifi or any other 
>> way
>> > of connectivity at the site so the data needs to be physically 
>> downloaded.
>> >
>> > I am however a bit stumped as I cannot figure out in what format the 
>> date
>> > and time is stored as. It seems to be a serial number, but I am not sure
>> > how to convert that back to Date and Time.
>> >
>> > Does anyone perhaps have an idea on how to get the conversion done? I
>> > cannot find any explanation in the documentation about the units of the
>> > database values.
>> >
>> > dateTime
>> > 1667481600
>> > 1667481900
>> > 1667483700
>> > 1667484000
>> > 1667484300
>> > 1667484600
>> > 1667484900
>> > 1667485200
>> > 1667485500
>> > 1667485800
>> > 1667486100
>> >
>> > --
>> > You received this message because you are subscribed to the Google 
>> Groups
>> > "weewx-user" group.
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> an
>> > email to weewx-user+...@googlegroups.com.
>> > To view this discussion on the web visit
>> > 
>> https://groups.google.com/d/msgid/weewx-user/88e58150-35a5-4841-bea2-452d573b6f6dn%40googlegroups.com
>> .
>> >
>>
>>
>> -- 
>>
>>
>> Cheers
>>  Glenn
>>
>> rorpi - read only raspberry pi & various weewx addons
>> https://github.com/glennmckechnie
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/CAAraAzi8A02nYOkcwdDuz0ig_omcGZpWEKdTr%2B1fy9Oda1Pvog%40mail.gmail.com
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9a6f9434-8477-46d1-a9c3-bd6197ba1990n%40googlegroups.com.

Re: [weewx-user] Time and date format in Weewx database

[p q]

A little more background. It's a unix epoch datetime. The number of seconds
since 1970 iirc. Google unix epoch.

On Fri, Nov 4, 2022, 10:14 AM Glenn McKechnie 
wrote:

> unixepoch, epochtime, unixtime
>
> from a linux terminal...
>
> $ date -d now +'%s'
> 1667553105
>
> $ date -d @1667553105
> Fri 04 Nov 2022 20:11:45 AEDT
>
> man date
>
> within a mysql (mariadb)...
> SELECT FROM_UNIXTIME(datetime, '%d-%m-%Y %H:%i') from archive WHERE
> dateTime = 166734;
>
> there'll be something similar for sqlite
>
> On 04/11/2022, Phillip Fischer  wrote:
> > I hope that someone would be able to point me in the right direction.
> >
> > I am aiming to use Weewx to log data from a weather station console of a
> > station that is set up in a remote, out of the way area as part of my
> > research. Due to an oversight in Station specs, I was given a station
> that
> > will need to be downloaded every two weeks or else the data is
> overwritten,
> >
> > but getting to the site every two weeks is not going to happen!
> >
> > I've got the station running, connected to a Raspberry Pi Zero 2 and it
> is
> > working and logging data without issue.
> >
> > It is easy to get into the .sdb and convert the data to .csv for export
> to
> > analyse the data off site. There is no cell signal, wifi or any other way
> > of connectivity at the site so the data needs to be physically
> downloaded.
> >
> > I am however a bit stumped as I cannot figure out in what format the date
> > and time is stored as. It seems to be a serial number, but I am not sure
> > how to convert that back to Date and Time.
> >
> > Does anyone perhaps have an idea on how to get the conversion done? I
> > cannot find any explanation in the documentation about the units of the
> > database values.
> >
> > dateTime
> > 1667481600
> > 1667481900
> > 1667483700
> > 1667484000
> > 1667484300
> > 1667484600
> > 1667484900
> > 1667485200
> > 1667485500
> > 1667485800
> > 1667486100
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "weewx-user" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to weewx-user+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/weewx-user/88e58150-35a5-4841-bea2-452d573b6f6dn%40googlegroups.com
> .
> >
>
>
> --
>
>
> Cheers
>  Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAAraAzi8A02nYOkcwdDuz0ig_omcGZpWEKdTr%2B1fy9Oda1Pvog%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAA1SM225DWn9ySN0QBtJ_2nF%2Ba8%2B55G-MTBwWj5Sj3k60OLezg%40mail.gmail.com.

Re: [weewx-user] Time and date format in Weewx database

[Glenn McKechnie]

unixepoch, epochtime, unixtime

from a linux terminal...

$ date -d now +'%s'
1667553105

$ date -d @1667553105
Fri 04 Nov 2022 20:11:45 AEDT

man date

within a mysql (mariadb)...
SELECT FROM_UNIXTIME(datetime, '%d-%m-%Y %H:%i') from archive WHERE
dateTime = 166734;

there'll be something similar for sqlite

On 04/11/2022, Phillip Fischer  wrote:
> I hope that someone would be able to point me in the right direction.
>
> I am aiming to use Weewx to log data from a weather station console of a
> station that is set up in a remote, out of the way area as part of my
> research. Due to an oversight in Station specs, I was given a station that
> will need to be downloaded every two weeks or else the data is overwritten,
>
> but getting to the site every two weeks is not going to happen!
>
> I've got the station running, connected to a Raspberry Pi Zero 2 and it is
> working and logging data without issue.
>
> It is easy to get into the .sdb and convert the data to .csv for export to
> analyse the data off site. There is no cell signal, wifi or any other way
> of connectivity at the site so the data needs to be physically downloaded.
>
> I am however a bit stumped as I cannot figure out in what format the date
> and time is stored as. It seems to be a serial number, but I am not sure
> how to convert that back to Date and Time.
>
> Does anyone perhaps have an idea on how to get the conversion done? I
> cannot find any explanation in the documentation about the units of the
> database values.
>
> dateTime
> 1667481600
> 1667481900
> 1667483700
> 1667484000
> 1667484300
> 1667484600
> 1667484900
> 1667485200
> 1667485500
> 1667485800
> 1667486100
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/88e58150-35a5-4841-bea2-452d573b6f6dn%40googlegroups.com.
>


-- 


Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAAraAzi8A02nYOkcwdDuz0ig_omcGZpWEKdTr%2B1fy9Oda1Pvog%40mail.gmail.com.

Re: [weewx-user] Time and date format in Weewx database

[Stephen Hocking]

Hi Phillip,

It's in Unix Epoch time - this website will help you on how to convert it
to a sensible date & time.

https://www.epochconverter.com/#:~:text=The%20Unix%20epoch%20(or%20Unix,01T00%3A00%3A00Z)
.

On Fri, 4 Nov 2022 at 19:38, Phillip Fischer  wrote:

> I hope that someone would be able to point me in the right direction.
>
> I am aiming to use Weewx to log data from a weather station console of a
> station that is set up in a remote, out of the way area as part of my
> research. Due to an oversight in Station specs, I was given a station that
> will need to be downloaded every two weeks or else the data is overwritten,
> but getting to the site every two weeks is not going to happen!
>
> I've got the station running, connected to a Raspberry Pi Zero 2 and it is
> working and logging data without issue.
>
> It is easy to get into the .sdb and convert the data to .csv for export to
> analyse the data off site. There is no cell signal, wifi or any other way
> of connectivity at the site so the data needs to be physically downloaded.
>
> I am however a bit stumped as I cannot figure out in what format the date
> and time is stored as. It seems to be a serial number, but I am not sure
> how to convert that back to Date and Time.
>
> Does anyone perhaps have an idea on how to get the conversion done? I
> cannot find any explanation in the documentation about the units of the
> database values.
>
> dateTime
> 1667481600
> 1667481900
> 1667483700
> 1667484000
> 1667484300
> 1667484600
> 1667484900
> 1667485200
> 1667485500
> 1667485800
> 1667486100
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/88e58150-35a5-4841-bea2-452d573b6f6dn%40googlegroups.com
> 
> .
>


-- 

  "I and the public know
  what all schoolchildren learn
  Those to whom evil is done
  Do evil in return"W.H. Auden, "September 1, 1939"

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CA%2BxzKjBVSYm%2BqFuK%3Ds0mfbu2B0Y5gYmDeTOdWk2fyE_4dFi8Bw%40mail.gmail.com.

[weewx-user] Time and date format in Weewx database

[Phillip Fischer]

I hope that someone would be able to point me in the right direction.

I am aiming to use Weewx to log data from a weather station console of a 
station that is set up in a remote, out of the way area as part of my 
research. Due to an oversight in Station specs, I was given a station that 
will need to be downloaded every two weeks or else the data is overwritten, 
but getting to the site every two weeks is not going to happen!

I've got the station running, connected to a Raspberry Pi Zero 2 and it is 
working and logging data without issue.

It is easy to get into the .sdb and convert the data to .csv for export to 
analyse the data off site. There is no cell signal, wifi or any other way 
of connectivity at the site so the data needs to be physically downloaded.

I am however a bit stumped as I cannot figure out in what format the date 
and time is stored as. It seems to be a serial number, but I am not sure 
how to convert that back to Date and Time.

Does anyone perhaps have an idea on how to get the conversion done? I 
cannot find any explanation in the documentation about the units of the 
database values.

dateTime
1667481600
1667481900
1667483700
1667484000
1667484300
1667484600
1667484900
1667485200
1667485500
1667485800
1667486100

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/88e58150-35a5-4841-bea2-452d573b6f6dn%40googlegroups.com.

[weewx-user] Re: wee_import date/time specifications

[gjr80]

Thanks Les, QC is obviously lacking at weewx.com at the moment.

I have revised the relevant stanzas in the wee_import section of the 
Utilities Guide and added a brief explanatory note as you suggest. Have 
also reworked the weeimport.py comments. Issue 652 
 and commits 402db1f 

 
and 26f2594 

 
refer. Long story but at the moment those changes will only be visible come 
the next release, in the meantime I will get relevant changes made to the 
on-line documentation over the next day or so.

Gary
On Thursday, 25 February 2021 at 06:47:40 UTC+10 ln77 wrote:

> The documentation for wee_import says that the --from and --to date/times 
> are inclusive and exclusive, respectively.  But what is reported when an 
> import is run, and what the code actually implements, is the other way 
> around: the --from is exclusive and the --to is inclusive. (To further 
> the confusion, the comment at line 187 in weeimport.py implies that both 
> are inclusive.)  The way it is implemented makes sense given that the 
> timestamp points to the end of the archive interval, but the disparity is 
> confusing.  Assuming I’m understanding this correctly, I’d suggest the 
> utilities guide be corrected, perhaps including a brief explanation of why 
> exclusive/inclusive is the appropriate choice.
>
> That said, I’m very happy to find that wee_import does exactly what I need 
> to recover a bunch of data.  Saved me several hours of work!
>
>   -Les
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/831d2e68-6f2e-4e81-ad8d-5cfae7adb72an%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

After a month of trial and error, I'm still struggling with this issue.
I've changed my VM from turnkey linux to a full ubuntu server, didn't help. 
Tried minimal installations, mysql vs sqlite, no joy. My date is being 
messed up somehow.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c130bebe-ae49-4064-9a76-1d441d57a20eo%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

As an update, I didn't restart or modified anything since my last message, 
and it just started working.
I really don't understand what happened, now I'm afraid now to stop/restart 
it.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a8c7a43d-9c27-4931-8a5f-751a03a8ccc7%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

I'm confident that the date/time will jump. I'm going to leave it run for 
the night.
I went through Matthew's wiki/how to/issues multiple times, and this is the 
best what I was able to do. I wasn't able to make interceptor listen to my 
network traffic and sniff out the communication between my PWS and WU.
If nothing helps, I'm going to clean up my database, export it, set up 
another virtual machine and install weewx.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4e47eabe-e605-46e8-8d7e-de963637e28e%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[gjr80]

Well I am stumped. 

The repeat packets seem to be in a reasonably regular routine, a few HTTP GETs 
followed by  a HTTP POST. I can accept that since you are fooling your station 
into thinking the interceptor driver is WU your weather station may not be 
seeing the exact response it expects and that causes it to resend the data or 
try HTTP POST. 

Looking at that last log extract I can see the 8pm archive record being saved, 
so that accounts for 8pm appearing on your page. The interceptor started 
deeming some of those duplicate packets as out of order and discarding them 
(interceptor accepts packets if the timestamp is greater than or equal to the 
last packets timestamp, anything else is dropped). I can’t see why it suddenly 
started dropping packets. Since no packets are getting through (after 8pm) no 
archive records are generated and hence no report cycle and the generated 
Seasons page doesn’t change. I expect that later some packets will be accepted 
and things will seem to work for a while. Noteworthy that this is a different 
symptom to yesterday where the page date-time was jumping ahead.

Would be good to get Matthew’s view (interceptor author) but I know he is busy 
with other things.

Only other suggestion I have is to maybe reconfigure your network to have your 
weather station update WU and have WeeWX use the interceptor driver to sniff 
the packets being sent to WU. Haven’t done that myself so I am not sure how 
feasible it is.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ae8daaaf-ceab-4e82-b52f-9b141b8ff3af%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Here's the log -> https://pastebin.com/B2zFhnje

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d0ad85c0-ef6a-4b9c-ba7b-9fe6467cdc37%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[gjr80]

Ok, the multiple duplicate timestamped packets are still there as are the POST 
and GET. Your system stuck at 8pm but you log extract went to 7:59pm, would be 
useful seeing 7:55 to say 8:15.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/18a4d495-3d74-4fbc-a4d3-612bf7d6efb6%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

We have 8:22PM, it stopped at last report wast generated at 8PM.
Here's the log of the first 30 minutes, of the actual run
https://pastebin.com/uhyCkPvX

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/02730962-94ae-4b07-ac7b-8612c286aceb%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[gjr80]

How about a log from startup for about 30 minutes, we should be able to see if 
those duplicate packets are gone.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a48ca79e-b9f3-4b74-824d-eb907535e7c0%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Disabling WU didn't help.
>
> May 23 15:00:19 weewx weewx[10289] DEBUG user.interceptor: raw packet: {
'wind_speed': 2.0, 'humidity_in': 46.0, 'temperature_in': 72.9, 
'solar_radiation': 134.81, 'windchill': 54.9, 'dewpoint': 47.8, 
'humidity_out': 77.0, 'uv': 1.0, 'rain': 0.0, 'dateTime': 1590242400, 
'pressure': 30.11, 'temperature_out': 54.9, 'wind_dir': 61.0, 'barometer': 
30.071, 'rain_total': 0.0, 'usUnits': 1, 'wind_gust': 3.4}

I thought using pcap filter is better than in my case.
Switched to "address = 192.168.2.41", cleaned the database, deleted the 
html and started weewx.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/116e2a0f-bcaa-483c-aa5b-e67b76f7b862%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[gjr80]

OK, starting to test the limits of my networking knowledge. One last thing 
to try, let's make sure the interceptor is listening to the correct IP 
address (and only the correct IP address). In weewx.conf under [Interceptor] 
can you add and the address = 192,168.2.41, ie:

[Interceptor]

device_type = observer
address = 192.168.2.41


Save and restart WeeWX. 

I see you have now disabled WeeWX posting to WU, that may well fix the 
issue of the multiple duplicate packets but of course you have now lost the 
ability of posting to WU. If disabling WU in WeeWX settles things down you 
might want to try the adding the address setting above and enabling WU (but 
lets leave RF aside for now).

Taking a log extract from startup for a couple of archive periods should 
soon show if we are on track or not.

Gary

On Saturday, 23 May 2020 09:33:14 UTC+10, Zsolt Máté wrote:
>
> Right now I've disabled MQTT in weewx.conf, cleaned the future records 
> from the database, dropped and rebuild the daily stats. Last HTML generated 
> is more than 30 minutes old.
>
> To paint a picture of my setup:
> I'm running this weather station -> 
> https://www.jaycar.co.nz/7-inch-colour-wireless-weather-station/p/XC0370 - 
> IP address 192.168.2.60 that sends data to WU (intercepted)
> weewx is running in a proxmox container with the IP's 192.168.2.40 and 
> 192.168.2.41, 41 being the interceptor.
> On my router (openwrt), I've set up a rule, that the traffic from my PWS 
> should be forwarded to 192.168.2.41.
> iptables -t nat -A PREROUTING -s 192.168.2.60 -p tcp --dport 80 -j DNAT 
> --to-destination 192.168.2.41:80
> iptables -t nat -A POSTROUTING -j MASQUERADE
> Weewx is forwarding the intercepted data to WU.
> MQTT is used for the Belchertown skin (right now uninstalled) and to 
> integrate my weather data into Home Assistant.
>
>
> On Saturday, May 23, 2020 at 10:57:43 AM UTC+12, gjr80 wrote:
>>
>> Thanks. I am trying to get my head around what is going on here. There 
>> seems to be a lot of double handling (posting) of records, for example the 
>> 22 May 19:50:20 record is published by the MQTT uploader six times:
>>
>> May 22 19:50:28 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
>> record 2020-05-22 19:50:20 NZST (1590133820)
>> ...
>> May 22 19:50:29 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
>> record 2020-05-22 19:50:20 NZST (1590133820)
>> ...
>> May 22 19:50:44 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
>> record 2020-05-22 19:50:20 NZST (1590133820)
>> ...
>> May 22 19:50:50 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
>> record 2020-05-22 19:50:20 NZST (1590133820)
>> ...
>> May 22 19:51:00 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
>> record 2020-05-22 19:50:20 NZST (1590133820)
>> ...
>> May 22 19:51:16 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
>> record 2020-05-22 19:50:20 NZST (1590133820)
>>
>> I also see the interceptor is picking up a lot of what appears to be 
>> duplicate records some of which are HTTP POST and others HTTP GET. Can you 
>> clarrify your configuration? From the wee_debug report you have WeeWX 
>> uploading to WU both normal (every archive record) updates and rapid fire 
>> and you have WeeWX uploading to a MQTT broker every archive record and loop 
>> packet. Do you have your weather station uploading to WU? I am thinking it 
>> might be time to pare back to a bare bones setup by turning off a few 
>> services.
>>
>> Gary
>>
>> On Friday, 22 May 2020 18:36:29 UTC+10, Zsolt Máté wrote:
>>>
>>> It stopped updating the html at local 08:00PM, and in the log I see an 
>>> MQTT message dated tomorrow.
>>> It's MQTT related: May 22 20:00:20 weewx weewx[5569] INFO weewx.restx: 
>>> MQTT: Published record 2020-05-23 07:00:00 NZST (1590174000)
>>>
>>> Log from 10 minutes before until 10 minutes after 8PM -> 
>>> https://pastebin.com/K7s8e60V
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b7541bae-0b2b-4218-9151-1bf9824b2824%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Update, disabling MQTT didn't help. My time just jumped 10 hours in 
advance. From 12PM to 10PM.
>
> Log 10 minutes +/- 12PM -> https://pastebin.com/FjkM7Mg8
Problem occurs here
May 23 12:00:19 weewx weewx[9805] DEBUG user.interceptor: raw packet: {
'wind_speed': 1.8, 'humidity_in': 46.0, 'temperature_in': 71.2, 
'solar_radiation': 296.66, 'windchill': 55.8, 'dewpoint': 48.6, 
'humidity_out': 77.0, 'uv': 3.0, 'rain': 0.0, 'dateTime': 1590231600, 
'pressure': 30.207, 'temperature_out': 55.8, 'wind_dir': 74.0, 'barometer': 
30.169, 'rain_total': 0.0, 'usUnits': 1, 'wind_gust': 2.2}

Right now I've disabled WU in my weewx.conf, deleted html and cleaned the 
database.
Let's see.

>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/aecadd5c-0ea6-4da5-8be2-782b8b256b5a%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Right now I've disabled MQTT in weewx.conf, cleaned the future records from 
the database, dropped and rebuild the daily stats. Last HTML generated is 
more than 30 minutes old.

To paint a picture of my setup:
I'm running this weather station -> 
https://www.jaycar.co.nz/7-inch-colour-wireless-weather-station/p/XC0370 - 
IP address 192.168.2.60 that sends data to WU (intercepted)
weewx is running in a proxmox container with the IP's 192.168.2.40 and 
192.168.2.41, 41 being the interceptor.
On my router (openwrt), I've set up a rule, that the traffic from my PWS 
should be forwarded to 192.168.2.41.
iptables -t nat -A PREROUTING -s 192.168.2.60 -p tcp --dport 80 -j DNAT 
--to-destination 192.168.2.41:80
iptables -t nat -A POSTROUTING -j MASQUERADE
Weewx is forwarding the intercepted data to WU.
MQTT is used for the Belchertown skin (right now uninstalled) and to 
integrate my weather data into Home Assistant.


On Saturday, May 23, 2020 at 10:57:43 AM UTC+12, gjr80 wrote:
>
> Thanks. I am trying to get my head around what is going on here. There 
> seems to be a lot of double handling (posting) of records, for example the 
> 22 May 19:50:20 record is published by the MQTT uploader six times:
>
> May 22 19:50:28 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
> record 2020-05-22 19:50:20 NZST (1590133820)
> ...
> May 22 19:50:29 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
> record 2020-05-22 19:50:20 NZST (1590133820)
> ...
> May 22 19:50:44 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
> record 2020-05-22 19:50:20 NZST (1590133820)
> ...
> May 22 19:50:50 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
> record 2020-05-22 19:50:20 NZST (1590133820)
> ...
> May 22 19:51:00 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
> record 2020-05-22 19:50:20 NZST (1590133820)
> ...
> May 22 19:51:16 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
> record 2020-05-22 19:50:20 NZST (1590133820)
>
> I also see the interceptor is picking up a lot of what appears to be 
> duplicate records some of which are HTTP POST and others HTTP GET. Can you 
> clarrify your configuration? From the wee_debug report you have WeeWX 
> uploading to WU both normal (every archive record) updates and rapid fire 
> and you have WeeWX uploading to a MQTT broker every archive record and loop 
> packet. Do you have your weather station uploading to WU? I am thinking it 
> might be time to pare back to a bare bones setup by turning off a few 
> services.
>
> Gary
>
> On Friday, 22 May 2020 18:36:29 UTC+10, Zsolt Máté wrote:
>>
>> It stopped updating the html at local 08:00PM, and in the log I see an 
>> MQTT message dated tomorrow.
>> It's MQTT related: May 22 20:00:20 weewx weewx[5569] INFO weewx.restx: 
>> MQTT: Published record 2020-05-23 07:00:00 NZST (1590174000)
>>
>> Log from 10 minutes before until 10 minutes after 8PM -> 
>> https://pastebin.com/K7s8e60V
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f157cdae-64f3-4c7c-9a3f-d2b0b73141a0%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[gjr80]

Thanks. I am trying to get my head around what is going on here. There 
seems to be a lot of double handling (posting) of records, for example the 
22 May 19:50:20 record is published by the MQTT uploader six times:

May 22 19:50:28 weewx weewx[5569] INFO weewx.restx: MQTT: Published record 
2020-05-22 19:50:20 NZST (1590133820)
...
May 22 19:50:29 weewx weewx[5569] INFO weewx.restx: MQTT: Published record 
2020-05-22 19:50:20 NZST (1590133820)
...
May 22 19:50:44 weewx weewx[5569] INFO weewx.restx: MQTT: Published record 
2020-05-22 19:50:20 NZST (1590133820)
...
May 22 19:50:50 weewx weewx[5569] INFO weewx.restx: MQTT: Published record 
2020-05-22 19:50:20 NZST (1590133820)
...
May 22 19:51:00 weewx weewx[5569] INFO weewx.restx: MQTT: Published record 
2020-05-22 19:50:20 NZST (1590133820)
...
May 22 19:51:16 weewx weewx[5569] INFO weewx.restx: MQTT: Published record 
2020-05-22 19:50:20 NZST (1590133820)

I also see the interceptor is picking up a lot of what appears to be 
duplicate records some of which are HTTP POST and others HTTP GET. Can you 
clarrify your configuration? From the wee_debug report you have WeeWX 
uploading to WU both normal (every archive record) updates and rapid fire 
and you have WeeWX uploading to a MQTT broker every archive record and loop 
packet. Do you have your weather station uploading to WU? I am thinking it 
might be time to pare back to a bare bones setup by turning off a few 
services.

Gary

On Friday, 22 May 2020 18:36:29 UTC+10, Zsolt Máté wrote:
>
> It stopped updating the html at local 08:00PM, and in the log I see an 
> MQTT message dated tomorrow.
> It's MQTT related: May 22 20:00:20 weewx weewx[5569] INFO weewx.restx: 
> MQTT: Published record 2020-05-23 07:00:00 NZST (1590174000)
>
> Log from 10 minutes before until 10 minutes after 8PM -> 
> https://pastebin.com/K7s8e60V
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d131a940-cf72-4718-82b9-cac874943b52%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

It stopped updating the html at local 08:00PM, and in the log I see an MQTT 
message dated tomorrow.
It's MQTT related: May 22 20:00:20 weewx weewx[5569] INFO weewx.restx: 
MQTT: Published record 2020-05-23 07:00:00 NZST (1590174000)

Log from 10 minutes before until 10 minutes after 8PM -> 
https://pastebin.com/K7s8e60V

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e07a45fc-c8ea-4706-875d-b44916f9cf91%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Weird, I really don't know what's happening. This morning, I've deleted 
everything related to the past day from the database.

1. done
2. deleted two records, see attached image 
3. I've deleted all the files from /var/www/html/weewx/
4. ran wee_database --drop-daily and --rebuild-daily
5. debug is set to 1
6. restart WeeWX
7. as soon as the web pages are generated, the date and time is correct.

I've started weewx right now, let's see what's happening.

What I've noticed today, the www data wasn't updated every 5 minutes, 
sometimes the website got updated only after 10-15 or even 30 minutes.

debug info here -> https://pastebin.com/k519Squx

Thanks for trying to help me.


PS, now that I've finished writing this reply, I noticed that the date and 
time below the plots is already wrong. Date and time in the top left corner 
is still OK.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1518e2d9-e9b8-434f-829e-bbaace17c6ab%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[gjr80]

Just looked at your sire and you are now showing 0300 23 May so it has 
jumped again. If you look at the wind direction and wind vector plots you 
can clearly see individual points at around 0100 and 0300. It is hard to 
see but I believe all of the other plots have individual points at the same 
times (interestingly your plots only seem to have points every one hour, 
hence the lack of jointing lines, I am sure yesterday there were many more 
data points being shown, I would expect there to be points every archive 
interval, in your case 5 minutes). So for some reason you are picking up at 
least one bogus future dated loop packet every so often. I had a quick look 
at the interceptor driver last night and it protects you against receiving 
a packet that is earlier than the last packet in the database but there is 
no protection for packets that are timestamped later than the current 
system clock, so a future dated packet could quite conceivably be emitted 
by the driver and accepted by WeeWX. 

Before we look at how to fix the problem it would be good to understand the 
exact circumstances when future data records are received. Could I suggest:

1. stop WeeWX
2. delete all future dated records from the archive
3. optional step, delete all plot files on the WeeWX machine. Aware you had 
an issue with this yesterday, note these must be the plots generated by 
WeeWX and not copies that have been uploaded to a web server or elsewhere 
on the WeeWX machine otherwise the old, incorrect plots are copied next 
time rather than all being regnerated
4. optional step, using the wee_database utility drop the daily summary 
tables using --drop-daily then rebuild the daily summaries using 
--rebuild-daily
5. ensure debug = 1 in weewx.conf
6. restart WeeWX
7. confirm the date-time in the top left hand corner of the main page 
returns to the current date-time

I say 3. and 4. are optional, they will tidy up your incorrect data but 
since we know it will happen again it is up to you whether you want to 
bother going through those steps now. You will have to do the same steps 
later anyway.

Let WeeWX run and when you next notice the current date-time in the top 
left corner has jumped forward look through the log since the restart to 
find the future dated record, if your time jumped to 0300 23 May 2020 then 
you would be looking for something like:

May 21 17:10:29 weewx weewx[7776] INFO weewx.manager: Added record 2020-05-
23 03:00:00 NZST (1590159600) to database 'weewx'
May 21 17:10:29 weewx weewx[7776] INFO weewx.manager: Added record 2020-05-
23 03:00:00 NZST (1590159600) to daily summary in 'weewx'

Once you find that entry it would be worthwhile seeing the log for say 10 
minutes either side of that entry.

You could also go through your current logs looking for bogus future dated 
records that are timstamped with the same (future dated) date-time that you 
have been seeing in the top left hand corner of your main page (I think you 
mentioned 10pm and 6am?), up to you which way you go, we just want to see 
what is going on around those times.

One final thing, could you post a wee_debug report 
. This will give us 
a succinct picture of your WeeWX config. Just be careful to check the 
wee_debug report for sensitive info before posting; wee_debug should 
obfuscate passords, user names, api keys etc but it is not perfect.

Gary


On Friday, 22 May 2020 06:03:15 UTC+10, Zsolt Máté wrote:
>
> Update, without any intervention time jumped to 6PM. 10hrs ahead.
>
> On Friday, May 22, 2020 at 7:22:48 AM UTC+12, Zsolt Máté wrote:
>>
>> Sorry, my bad. New Zealand is UTC+12.
>>
>> My issue didn't disappear. Now is showing the time is showing 2PM and not 
>> updating, but local time is 07:15AM.
>> Data in the plots is scattered.
>>
>> I've double checked the date/time on my PWS and is correct.
>>
>> On Thursday, May 21, 2020 at 10:41:21 PM UTC+12, Jacques Terrettaz wrote:
>>>
>>> Hi,
>>>
>>> You said on your top message that  your timezone is UTC - 12
>>>
>>> But below I see UTC + 12
>>>
>>> Could it be the problem ?
>>>
>>>
>>> Le jeudi 21 mai 2020 10:08:43 UTC+2, Zsolt Máté a écrit :

 Your time zone: Friday, 22 May 2020 6:00:00 AM GMT+12:00



-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c056c674-5ca2-4cf8-aa38-fe057a5f%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Update, without any intervention time jumped to 6PM. 10hrs ahead.

On Friday, May 22, 2020 at 7:22:48 AM UTC+12, Zsolt Máté wrote:
>
> Sorry, my bad. New Zealand is UTC+12.
>
> My issue didn't disappear. Now is showing the time is showing 2PM and not 
> updating, but local time is 07:15AM.
> Data in the plots is scattered.
>
> I've double checked the date/time on my PWS and is correct.
>
> On Thursday, May 21, 2020 at 10:41:21 PM UTC+12, Jacques Terrettaz wrote:
>>
>> Hi,
>>
>> You said on your top message that  your timezone is UTC - 12
>>
>> But below I see UTC + 12
>>
>> Could it be the problem ?
>>
>>
>> Le jeudi 21 mai 2020 10:08:43 UTC+2, Zsolt Máté a écrit :
>>>
>>> Your time zone: Friday, 22 May 2020 6:00:00 AM GMT+12:00
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b114c35f-1695-4f0f-b3be-2b0ea30473bb%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Sorry, my bad. New Zealand is UTC+12.

My issue didn't disappear. Now is showing the time is showing 2PM and not 
updating, but local time is 07:15AM.
Data in the plots is scattered.

I've double checked the date/time on my PWS and is correct.

On Thursday, May 21, 2020 at 10:41:21 PM UTC+12, Jacques Terrettaz wrote:
>
> Hi,
>
> You said on your top message that  your timezone is UTC - 12
>
> But below I see UTC + 12
>
> Could it be the problem ?
>
>
> Le jeudi 21 mai 2020 10:08:43 UTC+2, Zsolt Máté a écrit :
>>
>> Your time zone: Friday, 22 May 2020 6:00:00 AM GMT+12:00
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3adc91ad-f4ce-4146-b4da-791540908c20%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Jacques Terrettaz]

Hi,

You said on your top message that  your timezone is UTC - 12

But below I see UTC + 12

Could it be the problem ?


Le jeudi 21 mai 2020 10:08:43 UTC+2, Zsolt Máté a écrit :
>
> Your time zone: Friday, 22 May 2020 6:00:00 AM GMT+12:00
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5019989a-ca42-4ecd-bf33-9a6a96c6ae94%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Tried, twice.

On Thursday, May 21, 2020 at 8:54:18 PM UTC+12, gjr80 wrote:
>
> Just force all your plots to be regenerated by deleting them from your 
> WeeWX machine.
>
> Gary
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/116a2884-3258-431d-b03e-a5a648087bd1%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[gjr80]

Just force all your plots to be regenerated by deleting them from your WeeWX 
machine.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1b461357-3149-4516-add1-ad99681386ba%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Thank you, it worked. Interestingly that rogue spike is still showing up at 
the wind vector plot.

On Thursday, May 21, 2020 at 8:42:17 PM UTC+12, gjr80 wrote:
>
> No, —check just checks a couple of unrelated things, will not help you at 
> all. You need to use —drop-daily before —rebuild-daily. 
>
> Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4cdb3cdd-94c3-4f62-9beb-9c86bc0ea978%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[gjr80]

No, —check just checks a couple of unrelated things, will not help you at all. 
You need to use —drop-daily before —rebuild-daily.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/50c8edf9-3ad4-49bd-8551-1faac790ec34%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

wee_database --check runs OK (I assume), but --rebuild-daily return an error

root@weewx:~# wee_database --check
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_mysql'
Checking daily summary tables version...
Daily summary tables are at version 2.0
Interval Weighting Fix is not required.
Daily summary tables version check completed in 0.02 seconds.
Preparing Null String Fix, this may take a while...
 Checking record: 135849; Timestamp: 2020-05-21 19:00:00 NZST (1590044400)
No null strings found.
Completed Null String Check in 12.25 seconds.
root@weewx:~# ^C
root@weewx:~# wee_database --rebuild-daily
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_mysql'
All daily summaries will be rebuilt.
Proceed (y/n)? y
Rebuilding daily summaries in database 'weewx' ...
Traceback (most recent call last):
  File "/usr/share/weewx/wee_database", line 974, in 
main()
  File "/usr/share/weewx/wee_database", line 169, in main
rebuildDaily(config_dict, db_binding, options)
  File "/usr/share/weewx/wee_database", line 275, in rebuildDaily
trans_days=20)
  File "/usr/share/weewx/weewx/manager.py", line 1012, in 
backfill_day_summary
timestamp_to_string(lastRecord)))
weewx.ViolatedPrecondition: lastUpdate(2020-05-22 06:00:00 NZST 
(1590084000)) > lastRecord(2020-05-21 19:00:00 NZST (1590044400))

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a65c193b-9b19-4253-b5a7-625002268ac1%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[gjr80]

Did you use wee_database to rebuild the daily summaries? Probably safest to 
drop them first then rebuild.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/73c027e4-ebb6-4fb8-8581-398aba75e66c%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

It looks like I messed up something. I've deleted the two rows from the 
"future", but now weewx wont start.
root@weewx:~# service weewx restart
root@weewx:~# tail -f /var/log/syslog
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 158, in run
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__:   
self.dispatchEvent(weewx.Event(weewx.STARTUP))
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__:   
callback(event)
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 522, in startup
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__:   _nrecs, 
_ndays = dbmanager.backfill_day_summary()
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 1012, in backfill_day_summary
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__:   
timestamp_to_string(lastRecord)))
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__:   
ViolatedPrecondition: lastUpdate(2020-05-22 06:00:00 NZST (1590084000)) > 
lastRecord(2020-05-21 19:00:00 NZST (1590044400))
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__:   Exiting.


On Thursday, May 21, 2020 at 8:22:31 PM UTC+12, gjr80 wrote:
>
> Brain fade on my part, I should have tweaked earlier. I would go in and 
> delete the future records from the archive then rebuild the daily 
> summaries. You could just let it be and it will (seemingly) fix itself come 
> 6am tomorrow (albeit with a couple of duplicate index errors in the log) 
> but those bogus records will remain.
>
> Gary
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f7ffb497-286f-47da-bb8d-37215eebdfa6%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[gjr80]

Brain fade on my part, I should have tweaked earlier. I would go in and delete 
the future records from the archive then rebuild the daily summaries. You could 
just let it be and it will (seemingly) fix itself come 6am tomorrow (albeit 
with a couple of duplicate index errors in the log) but those bogus records 
will remain.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/bda9f9b1-55d1-4b9b-854f-97abab531a01%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Nice catch.
I'm using mysql as database. Via phpmyadmin I've managed to sort the 
database to date, max is 1590084000, converted:
GMT: Thursday, 21 May 2020 6:00:00 PM
Your time zone: Friday, 22 May 2020 6:00:00 AM GMT+12:00
Relative: In 10 hours

On Thursday, May 21, 2020 at 7:32:26 PM UTC+12, gjr80 wrote:
>
> Aha, look at your wind direction and wind vector plots, you have a wind 
> direction dot at midnight and likewise a vector. Are you using SQLite? If 
> so try the following (you may have to install the sqlite3 package first if 
> sqlite3 is not found - just use sudo apt-get install sqlite3):
>
> $ sqlite /var/lib/weewx/weewx.sdb
> > SELECT MAX(datetime(dateTime,'unixepoch','localtime')) FROM archive;
>
> (.q to exit the sqlite3 command prompt)
>
> What does that show?
>
> Gary
>
>
> I suspect There will be a data point in your archive for direction 
>
> On Thursday, 21 May 2020 16:43:47 UTC+10, Zsolt Máté wrote:
>>
>> I've ruled out browser cache. Tested on multiple devices within my 
>> network and even asked friends abroad to test. You can give it a try, as 
>> well. https://weather.zmate.nz
>>
>> 1. 22nd of May, 12:00:00 is not changing.
>> 2. I've deleted the contents of the www and it has been automatically 
>> regenerated, without forcing it.
>> 3. plots are being generated correctly, and the hour/minute looks correct.
>> 4. the timestamp below the plots is showing 05/22/2020 12:00:00 AM - good 
>> that you asked.
>> On Thursday, May 21, 2020 at 6:13:44 PM UTC+12, gjr80 wrote:
>>>
>>> Thanks, that is bizarre, I expectedt to see something in the log about 
>>> record timestamps being less than the last, but no everything is normal. 
>>> Archive records are bing generated with the correct timestamps, reports are 
>>> being generated without issue. I can't see it being a browser cache issue, 
>>> it would be stuck in the past not the future. A few (random) things to 
>>> check:
>>>
>>> 1. does the time change or is it always 22 May 00:00 (guessing it stays 
>>> put).
>>> 2. is the Seasons skin index.html file being generated every 5 minutes 
>>> (ie does its timestamp change) (again guessing it does as Seasons should 
>>> generate eight report files each report cycle and that is what it is doing)
>>> 3. do the current observations on the Seasons page change and are they 
>>> correct.
>>> 4. do the timestamps below the plots on the Seasons 'Day' tab show the 
>>> correct current time.
>>>
>>> Gary
>>>
>>> On Thursday, 21 May 2020 15:44:02 UTC+10, Zsolt Máté wrote:

 Thanks for the fast reply Gary.
 Here's the log -> https://pastebin.com/4zNJEJea

 On Thursday, May 21, 2020 at 5:07:37 PM UTC+12, gjr80 wrote:
>
> Hi,
>
> Could be any one of a number of causes, should be easily diagnosed 
> with a debug log extract 
>  
> from WeeWX startup.
>
> Gary
>
> On Thursday, 21 May 2020 14:53:35 UTC+10, Zsolt Máté wrote:
>>
>> My current conditions are "frozen".
>>
>> Date is waaay in the future. I'm located in NZ, local time/date is 
>> 4:47PM, the 21st of May.
>> Since we're UTC-12, nobody passed the dateline yet.
>>
>> I've checkt the date/time and timezone and these are correct on my 
>> server.
>>
>> The graphs are correct.
>>
>> What could cause this?
>>
>> [image: 2020-05-21 16_50_44 chrome_4YMd0jl6nZ.png]
>> I'm running weewx 4.0.0 and capturing my data using interceptor.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/92e5453b-3715-41ae-ae8a-a96cba42a3ec%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[gjr80]

Aha, look at your wind direction and wind vector plots, you have a wind 
direction dot at midnight and likewise a vector. Are you using SQLite? If 
so try the following (you may have to install the sqlite3 package first if 
sqlite3 is not found - just use sudo apt-get install sqlite3):

$ sqlite /var/lib/weewx/weewx.sdb
> SELECT MAX(datetime(dateTime,'unixepoch','localtime')) FROM archive;

(.q to exit the sqlite3 command prompt)

What does that show?

Gary


I suspect There will be a data point in your archive for direction 

On Thursday, 21 May 2020 16:43:47 UTC+10, Zsolt Máté wrote:
>
> I've ruled out browser cache. Tested on multiple devices within my network 
> and even asked friends abroad to test. You can give it a try, as well. 
> https://weather.zmate.nz
>
> 1. 22nd of May, 12:00:00 is not changing.
> 2. I've deleted the contents of the www and it has been automatically 
> regenerated, without forcing it.
> 3. plots are being generated correctly, and the hour/minute looks correct.
> 4. the timestamp below the plots is showing 05/22/2020 12:00:00 AM - good 
> that you asked.
> On Thursday, May 21, 2020 at 6:13:44 PM UTC+12, gjr80 wrote:
>>
>> Thanks, that is bizarre, I expectedt to see something in the log about 
>> record timestamps being less than the last, but no everything is normal. 
>> Archive records are bing generated with the correct timestamps, reports are 
>> being generated without issue. I can't see it being a browser cache issue, 
>> it would be stuck in the past not the future. A few (random) things to 
>> check:
>>
>> 1. does the time change or is it always 22 May 00:00 (guessing it stays 
>> put).
>> 2. is the Seasons skin index.html file being generated every 5 minutes 
>> (ie does its timestamp change) (again guessing it does as Seasons should 
>> generate eight report files each report cycle and that is what it is doing)
>> 3. do the current observations on the Seasons page change and are they 
>> correct.
>> 4. do the timestamps below the plots on the Seasons 'Day' tab show the 
>> correct current time.
>>
>> Gary
>>
>> On Thursday, 21 May 2020 15:44:02 UTC+10, Zsolt Máté wrote:
>>>
>>> Thanks for the fast reply Gary.
>>> Here's the log -> https://pastebin.com/4zNJEJea
>>>
>>> On Thursday, May 21, 2020 at 5:07:37 PM UTC+12, gjr80 wrote:

 Hi,

 Could be any one of a number of causes, should be easily diagnosed with 
 a debug log extract 
  from 
 WeeWX startup.

 Gary

 On Thursday, 21 May 2020 14:53:35 UTC+10, Zsolt Máté wrote:
>
> My current conditions are "frozen".
>
> Date is waaay in the future. I'm located in NZ, local time/date is 
> 4:47PM, the 21st of May.
> Since we're UTC-12, nobody passed the dateline yet.
>
> I've checkt the date/time and timezone and these are correct on my 
> server.
>
> The graphs are correct.
>
> What could cause this?
>
> [image: 2020-05-21 16_50_44 chrome_4YMd0jl6nZ.png]
> I'm running weewx 4.0.0 and capturing my data using interceptor.
>


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f8a58dce-354e-4f02-9b0f-09b2755f4ec9%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

I've ruled out browser cache. Tested on multiple devices within my network 
and even asked friends abroad to test. You can give it a try, as well. 
https://weather.zmate.nz

1. 22nd of May, 12:00:00 is not changing.
2. I've deleted the contents of the www and it has been automatically 
regenerated, without forcing it.
3. plots are being generated correctly, and the hour/minute looks correct.
4. the timestamp below the plots is showing 05/22/2020 12:00:00 AM - good 
that you asked.
On Thursday, May 21, 2020 at 6:13:44 PM UTC+12, gjr80 wrote:
>
> Thanks, that is bizarre, I expectedt to see something in the log about 
> record timestamps being less than the last, but no everything is normal. 
> Archive records are bing generated with the correct timestamps, reports are 
> being generated without issue. I can't see it being a browser cache issue, 
> it would be stuck in the past not the future. A few (random) things to 
> check:
>
> 1. does the time change or is it always 22 May 00:00 (guessing it stays 
> put).
> 2. is the Seasons skin index.html file being generated every 5 minutes 
> (ie does its timestamp change) (again guessing it does as Seasons should 
> generate eight report files each report cycle and that is what it is doing)
> 3. do the current observations on the Seasons page change and are they 
> correct.
> 4. do the timestamps below the plots on the Seasons 'Day' tab show the 
> correct current time.
>
> Gary
>
> On Thursday, 21 May 2020 15:44:02 UTC+10, Zsolt Máté wrote:
>>
>> Thanks for the fast reply Gary.
>> Here's the log -> https://pastebin.com/4zNJEJea
>>
>> On Thursday, May 21, 2020 at 5:07:37 PM UTC+12, gjr80 wrote:
>>>
>>> Hi,
>>>
>>> Could be any one of a number of causes, should be easily diagnosed with 
>>> a debug log extract 
>>>  from 
>>> WeeWX startup.
>>>
>>> Gary
>>>
>>> On Thursday, 21 May 2020 14:53:35 UTC+10, Zsolt Máté wrote:

 My current conditions are "frozen".

 Date is waaay in the future. I'm located in NZ, local time/date is 
 4:47PM, the 21st of May.
 Since we're UTC-12, nobody passed the dateline yet.

 I've checkt the date/time and timezone and these are correct on my 
 server.

 The graphs are correct.

 What could cause this?

 [image: 2020-05-21 16_50_44 chrome_4YMd0jl6nZ.png]
 I'm running weewx 4.0.0 and capturing my data using interceptor.

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b1f2edb8-eb4a-49e7-bd96-08aa362ae943%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[gjr80]

Thanks, that is bizarre, I expectedt to see something in the log about 
record timestamps being less than the last, but no everything is normal. 
Archive records are bing generated with the correct timestamps, reports are 
being generated without issue. I can't see it being a browser cache issue, 
it would be stuck in the past not the future. A few (random) things to 
check:

1. does the time change or is it always 22 May 00:00 (guessing it stays 
put).
2. is the Seasons skin index.html file being generated every 5 minutes (ie 
does its timestamp change) (again guessing it does as Seasons should 
generate eight report files each report cycle and that is what it is doing)
3. do the current observations on the Seasons page change and are they 
correct.
4. do the timestamps below the plots on the Seasons 'Day' tab show the 
correct current time.

Gary

On Thursday, 21 May 2020 15:44:02 UTC+10, Zsolt Máté wrote:
>
> Thanks for the fast reply Gary.
> Here's the log -> https://pastebin.com/4zNJEJea
>
> On Thursday, May 21, 2020 at 5:07:37 PM UTC+12, gjr80 wrote:
>>
>> Hi,
>>
>> Could be any one of a number of causes, should be easily diagnosed with a 
>> debug 
>> log extract 
>>  from 
>> WeeWX startup.
>>
>> Gary
>>
>> On Thursday, 21 May 2020 14:53:35 UTC+10, Zsolt Máté wrote:
>>>
>>> My current conditions are "frozen".
>>>
>>> Date is waaay in the future. I'm located in NZ, local time/date is 
>>> 4:47PM, the 21st of May.
>>> Since we're UTC-12, nobody passed the dateline yet.
>>>
>>> I've checkt the date/time and timezone and these are correct on my 
>>> server.
>>>
>>> The graphs are correct.
>>>
>>> What could cause this?
>>>
>>> [image: 2020-05-21 16_50_44 chrome_4YMd0jl6nZ.png]
>>> I'm running weewx 4.0.0 and capturing my data using interceptor.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/cb04ebd9-5c66-4b7b-8947-111578b98058%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Thanks for the fast reply Gary.
Here's the log -> https://pastebin.com/4zNJEJea

On Thursday, May 21, 2020 at 5:07:37 PM UTC+12, gjr80 wrote:
>
> Hi,
>
> Could be any one of a number of causes, should be easily diagnosed with a 
> debug 
> log extract 
>  from 
> WeeWX startup.
>
> Gary
>
> On Thursday, 21 May 2020 14:53:35 UTC+10, Zsolt Máté wrote:
>>
>> My current conditions are "frozen".
>>
>> Date is waaay in the future. I'm located in NZ, local time/date is 
>> 4:47PM, the 21st of May.
>> Since we're UTC-12, nobody passed the dateline yet.
>>
>> I've checkt the date/time and timezone and these are correct on my server.
>>
>> The graphs are correct.
>>
>> What could cause this?
>>
>> [image: 2020-05-21 16_50_44 chrome_4YMd0jl6nZ.png]
>> I'm running weewx 4.0.0 and capturing my data using interceptor.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/94f3ce14-f8d0-4ed1-a48d-72a825a41bed%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[gjr80]

Hi,

Could be any one of a number of causes, should be easily diagnosed with a debug 
log extract 
 from 
WeeWX startup.

Gary

On Thursday, 21 May 2020 14:53:35 UTC+10, Zsolt Máté wrote:
>
> My current conditions are "frozen".
>
> Date is waaay in the future. I'm located in NZ, local time/date is 4:47PM, 
> the 21st of May.
> Since we're UTC-12, nobody passed the dateline yet.
>
> I've checkt the date/time and timezone and these are correct on my server.
>
> The graphs are correct.
>
> What could cause this?
>
> [image: 2020-05-21 16_50_44 chrome_4YMd0jl6nZ.png]
> I'm running weewx 4.0.0 and capturing my data using interceptor.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ec6c43a5-6d35-42c7-9cb9-746ddd39a0b4%40googlegroups.com.

Re: [weewx-user] Modifying pyephem Date format on Celestial page?

[Thomas Keffer]

Hello, Pete

See section [[TimeFormats]]
 in the
Customizing Guide. In particular, options ephem_day and ephem_year.

On Fri, Apr 3, 2020 at 9:38 AM pbartko  wrote:

> Longtime weewx user, but just reinstalled weewx 3.9.2 on Raspberry pi due
> to hardware failure on my previous server.  I'm using the Seasons skin and
> installed pyephem.
>
> Everything is working well, but I can not figure out one thing.  How to
> change the date format of the Solstice, Equinox, Full moon and New moon?
> I'm in the US and we always try to be confusing by having things like our
> dates different the the rest of the world.  I'd like the those dates to be
> in MM/DD/ format instead of DD/MM/ format.  I was able to modify
> the report generator and image generator to change the date formats, but
> I'm stumped with the Celestial data from pyephem.
>
> site is here: http://www.boxhillweather.com
>
>
> Thanks
>
> Pete
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/4e1f9a72-b163-4293-ae33-9c14c6da7751%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEA5sKchP%2BvoS2wNggLORFEL3WJVbmAFhKRABNOP1knXBQ%40mail.gmail.com.

[weewx-user] Modifying pyephem Date format on Celestial page?

[pbartko]

Longtime weewx user, but just reinstalled weewx 3.9.2 on Raspberry pi due 
to hardware failure on my previous server.  I'm using the Seasons skin and 
installed pyephem.

Everything is working well, but I can not figure out one thing.  How to 
change the date format of the Solstice, Equinox, Full moon and New moon?  
I'm in the US and we always try to be confusing by having things like our 
dates different the the rest of the world.  I'd like the those dates to be 
in MM/DD/ format instead of DD/MM/ format.  I was able to modify 
the report generator and image generator to change the date formats, but 
I'm stumped with the Celestial data from pyephem.

site is here: http://www.boxhillweather.com


Thanks

Pete

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4e1f9a72-b163-4293-ae33-9c14c6da7751%40googlegroups.com.

[weewx-user] View specific date, or range

[comatose1978]

I'd like to view a specific date of data, or even a range, with graphs. 
Now I can only see last "week" , "Month" , "Year". 
I'd want to see week of 1/10/20 in week view, or even detailed view of 
1/10/20.
Want am I missing? 
Thanks in advance. 

Brandon. 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4f14b8ca-7929-40f6-8cb5-995dacdf8bf3%40googlegroups.com.

[weewx-user] Re: time/date issue in my INDEX.HTML file

[Eric Gammeter]

Operation is back to normal!  All I see is I am missing daily data from 
July 1 thru 7...but I can live with that for sure.  Thanks so much for your 
assistance guys.  
/Eric 



On Friday, July 5, 2019 at 3:58:01 PM UTC-4, Eric Gammeter wrote:
>
> Hi-  My INDEX.HTML file is being produced each half hour as it should 
> be...but the timestamp (in the file) is incorrect!  The report (attached) 
> shows it is 8/6/2036 @ 08:22:00PM.  
>
> I can see that the reports fire off every 30 mins- and that a new (correct 
> time stamp) INDEX.HTML file is created in the /var/www/html/weewx 
> filesystem-- but that file's info is incorrect.  
>
> I tested (with minicom) and that TEST's fine.
>
> I have shutdown and rebooted the VantageVue station to no avail.  
>
> Thanks for reading!  
>
> /Eric 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f57f3580-18f5-420a-84cb-f04a7096319c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: time/date issue in my INDEX.HTML file

[Eric Gammeter]

Thank you Tom!  That cleared-up the log error I was getting.  So far the 
timestamp on my index.html report shows 7/1/2019- but that is much better 
than what I was getting before.  I will let it run for a while to see how 
it shakes-out.  Your utilities are fantastic!
/Eric




On Friday, July 5, 2019 at 3:58:01 PM UTC-4, Eric Gammeter wrote:
>
> Hi-  My INDEX.HTML file is being produced each half hour as it should 
> be...but the timestamp (in the file) is incorrect!  The report (attached) 
> shows it is 8/6/2036 @ 08:22:00PM.  
>
> I can see that the reports fire off every 30 mins- and that a new (correct 
> time stamp) INDEX.HTML file is created in the /var/www/html/weewx 
> filesystem-- but that file's info is incorrect.  
>
> I tested (with minicom) and that TEST's fine.
>
> I have shutdown and rebooted the VantageVue station to no avail.  
>
> Thanks for reading!  
>
> /Eric 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6d87b4ed-1872-4b4a-90c5-e5150ec2cbb8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: time/date issue in my INDEX.HTML file

[Thomas Keffer]

While Andrew offers helpful information on how to delete records from your
archive, I would NOT start there. Most likely, your data are fine. Just
drop, then rebuild, the daily summaries. Then run weewx. If all is good,
you're done. Otherwise, we'll take on the more complicated stuff.

On Mon, Jul 8, 2019 at 6:26 AM Andrew Milner 
wrote:

> do you use phpliteadmin to browse the database or do you just retrieve
> records using sqlite3?
>
> only you can determine the datetime of the last good archive record - let
> us say it is 987654321
>
> then to delete all records later than that
> use sqlite 3
> delete from archive where dateTime > 987654321;
> would delete additional archive records
>
> then to sort out the daily summaries use wee_database to
> 1) drop daily
> 2) rebuild daily
>
> if your NOAA summary data is looking corrupted just delete the NOAA files
> and weewx will recreate them on the next report cycle.
>
>
> On Monday, 8 July 2019 16:08:40 UTC+3, Eric Gammeter wrote:
>>
>> Still at this...  Is there any way to determine the last-good db record
>> and then delete everything after that in order to salvage my WX year
>> history?
>>
>>
>> root@raspberrypi:/var/lib/weewx# /etc/init.d/weewx status
>> ● weewx.service - LSB: weewx weather system
>>Loaded: loaded (/etc/init.d/weewx; generated; vendor preset: enabled)
>>Active: active (exited) since Mon 2019-07-08 08:52:59 EDT; 10min ago
>>  Docs: man:systemd-sysv-generator(8)
>>   Process: 2872 ExecStop=/etc/init.d/weewx stop (code=exited,
>> status=0/SUCCESS)
>>   Process: 3049 ExecStart=/etc/init.d/weewx start (code=exited,
>> status=0/SUCCESS)
>>
>> Jul 08 08:53:00 raspberrypi weewx[3064]: File
>> "/usr/share/weewx/weewx/engine.py", line 142, in loadServices
>> Jul 08 08:53:00 raspberrypi weewx[3064]: 
>> self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
>> Jul 08 08:53:00 raspberrypi weewx[3064]: File
>> "/usr/share/weewx/weewx/engine.py", line 500, in __init__
>> Jul 08 08:53:00 raspberrypi weewx[3064]: 
>> self.setup_database(config_dict)
>> Jul 08 08:53:00 raspberrypi weewx[3064]: File
>> "/usr/share/weewx/weewx/engine.py", line 617, in setup_database
>> Jul 08 08:53:00 raspberrypi weewx[3064]:   _nrecs, _ndays =
>> dbmanager.backfill_day_summary() # @UnusedVariable
>> Jul 08 08:53:00 raspberrypi weewx[3064]: File
>> "/usr/share/weewx/weewx/manager.py", line 1447, in backfill_day_summary
>> Jul 08 08:53:00 raspberrypi weewx[3064]: 
>> timestamp_to_string(lastRecord)))
>> Jul 08 08:53:00 raspberrypi weewx[3064]:   ViolatedPrecondition:
>> lastUpdate(2036-08-06 20:22:00 EDT (2101681320)) > lastRecord(2019-07-01
>> 00:00:00 EDT (1561953600))
>> Jul 08 08:53:00 raspberrypi weewx[3064]:   Exiting.
>> root@raspberrypi:/var/lib/weewx#
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Friday, July 5, 2019 at 3:58:01 PM UTC-4, Eric Gammeter wrote:
>>>
>>> Hi-  My INDEX.HTML file is being produced each half hour as it should
>>> be...but the timestamp (in the file) is incorrect!  The report (attached)
>>> shows it is 8/6/2036 @ 08:22:00PM.
>>>
>>> I can see that the reports fire off every 30 mins- and that a new
>>> (correct time stamp) INDEX.HTML file is created in the /var/www/html/weewx
>>> filesystem-- but that file's info is incorrect.
>>>
>>> I tested (with minicom) and that TEST's fine.
>>>
>>> I have shutdown and rebooted the VantageVue station to no avail.
>>>
>>> Thanks for reading!
>>>
>>> /Eric
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/c8efbf47-494f-4286-b926-ef573eb4a140%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zED74Y3zETH1qiJAxfCojY2WeiS1XcUjRn7mVX-_-Z2fYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: time/date issue in my INDEX.HTML file

[Andrew Milner]

do you use phpliteadmin to browse the database or do you just retrieve 
records using sqlite3?

only you can determine the datetime of the last good archive record - let 
us say it is 987654321

then to delete all records later than that
use sqlite 3
delete from archive where dateTime > 987654321; 
would delete additional archive records

then to sort out the daily summaries use wee_database to 
1) drop daily
2) rebuild daily

if your NOAA summary data is looking corrupted just delete the NOAA files 
and weewx will recreate them on the next report cycle.


On Monday, 8 July 2019 16:08:40 UTC+3, Eric Gammeter wrote:
>
> Still at this...  Is there any way to determine the last-good db record 
> and then delete everything after that in order to salvage my WX year 
> history?
>
>
> root@raspberrypi:/var/lib/weewx# /etc/init.d/weewx status
> ● weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx; generated; vendor preset: enabled)
>Active: active (exited) since Mon 2019-07-08 08:52:59 EDT; 10min ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 2872 ExecStop=/etc/init.d/weewx stop (code=exited, 
> status=0/SUCCESS)
>   Process: 3049 ExecStart=/etc/init.d/weewx start (code=exited, 
> status=0/SUCCESS)
>
> Jul 08 08:53:00 raspberrypi weewx[3064]: File 
> "/usr/share/weewx/weewx/engine.py", line 142, in loadServices
> Jul 08 08:53:00 raspberrypi weewx[3064]:   
> self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
> Jul 08 08:53:00 raspberrypi weewx[3064]: File 
> "/usr/share/weewx/weewx/engine.py", line 500, in __init__
> Jul 08 08:53:00 raspberrypi weewx[3064]:   
> self.setup_database(config_dict)
> Jul 08 08:53:00 raspberrypi weewx[3064]: File 
> "/usr/share/weewx/weewx/engine.py", line 617, in setup_database
> Jul 08 08:53:00 raspberrypi weewx[3064]:   _nrecs, _ndays = 
> dbmanager.backfill_day_summary() # @UnusedVariable
> Jul 08 08:53:00 raspberrypi weewx[3064]: File 
> "/usr/share/weewx/weewx/manager.py", line 1447, in backfill_day_summary
> Jul 08 08:53:00 raspberrypi weewx[3064]:   
> timestamp_to_string(lastRecord)))
> Jul 08 08:53:00 raspberrypi weewx[3064]:   ViolatedPrecondition: 
> lastUpdate(2036-08-06 20:22:00 EDT (2101681320)) > lastRecord(2019-07-01 
> 00:00:00 EDT (1561953600))
> Jul 08 08:53:00 raspberrypi weewx[3064]:   Exiting.
> root@raspberrypi:/var/lib/weewx# 
>
>
>
>
>
>
>
>
>
>
> On Friday, July 5, 2019 at 3:58:01 PM UTC-4, Eric Gammeter wrote:
>>
>> Hi-  My INDEX.HTML file is being produced each half hour as it should 
>> be...but the timestamp (in the file) is incorrect!  The report (attached) 
>> shows it is 8/6/2036 @ 08:22:00PM.  
>>
>> I can see that the reports fire off every 30 mins- and that a new 
>> (correct time stamp) INDEX.HTML file is created in the /var/www/html/weewx 
>> filesystem-- but that file's info is incorrect.  
>>
>> I tested (with minicom) and that TEST's fine.
>>
>> I have shutdown and rebooted the VantageVue station to no avail.  
>>
>> Thanks for reading!  
>>
>> /Eric 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c8efbf47-494f-4286-b926-ef573eb4a140%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: time/date issue in my INDEX.HTML file

[Thomas Keffer]

I'm lost where you are in the process. Let's take it from the top:

1. Stop weewx

*sudo systemctl stop weewx*


2. Clear the memory of your logger

*sudo wee_device --clear-memory*


3. Delete the daily summaries. Normally this step isn't necessary, but
yours seems to have gotten messed up somehow.

*sudo wee_database --drop-daily*


4. Rebuild the daily summaries. Depending on the size of your database,
this could take a little time.

*sudo wee_database --rebuild-daily*


5. Restart weewx

*sudo systemctl start weewx*


-tk

On Mon, Jul 8, 2019 at 6:08 AM Eric Gammeter  wrote:

> Still at this...  Is there any way to determine the last-good db record
> and then delete everything after that in order to salvage my WX year
> history?
>
>
> root@raspberrypi:/var/lib/weewx# /etc/init.d/weewx status
> ● weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx; generated; vendor preset: enabled)
>Active: active (exited) since Mon 2019-07-08 08:52:59 EDT; 10min ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 2872 ExecStop=/etc/init.d/weewx stop (code=exited,
> status=0/SUCCESS)
>   Process: 3049 ExecStart=/etc/init.d/weewx start (code=exited,
> status=0/SUCCESS)
>
> Jul 08 08:53:00 raspberrypi weewx[3064]: File
> "/usr/share/weewx/weewx/engine.py", line 142, in loadServices
> Jul 08 08:53:00 raspberrypi weewx[3064]: 
> self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
> Jul 08 08:53:00 raspberrypi weewx[3064]: File
> "/usr/share/weewx/weewx/engine.py", line 500, in __init__
> Jul 08 08:53:00 raspberrypi weewx[3064]: 
> self.setup_database(config_dict)
> Jul 08 08:53:00 raspberrypi weewx[3064]: File
> "/usr/share/weewx/weewx/engine.py", line 617, in setup_database
> Jul 08 08:53:00 raspberrypi weewx[3064]:   _nrecs, _ndays =
> dbmanager.backfill_day_summary() # @UnusedVariable
> Jul 08 08:53:00 raspberrypi weewx[3064]: File
> "/usr/share/weewx/weewx/manager.py", line 1447, in backfill_day_summary
> Jul 08 08:53:00 raspberrypi weewx[3064]: 
> timestamp_to_string(lastRecord)))
> Jul 08 08:53:00 raspberrypi weewx[3064]:   ViolatedPrecondition:
> lastUpdate(2036-08-06 20:22:00 EDT (2101681320)) > lastRecord(2019-07-01
> 00:00:00 EDT (1561953600))
> Jul 08 08:53:00 raspberrypi weewx[3064]:   Exiting.
> root@raspberrypi:/var/lib/weewx#
>
>
>
>
>
>
>
>
>
>
> On Friday, July 5, 2019 at 3:58:01 PM UTC-4, Eric Gammeter wrote:
>>
>> Hi-  My INDEX.HTML file is being produced each half hour as it should
>> be...but the timestamp (in the file) is incorrect!  The report (attached)
>> shows it is 8/6/2036 @ 08:22:00PM.
>>
>> I can see that the reports fire off every 30 mins- and that a new
>> (correct time stamp) INDEX.HTML file is created in the /var/www/html/weewx
>> filesystem-- but that file's info is incorrect.
>>
>> I tested (with minicom) and that TEST's fine.
>>
>> I have shutdown and rebooted the VantageVue station to no avail.
>>
>> Thanks for reading!
>>
>> /Eric
>>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/8cfcd9af-70cc-4f05-8af2-cb4633c921a3%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEA19kszLAGPPjNSEgK7Cn71QZc3qMvMj4gmhNNcCyT2Mw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: time/date issue in my INDEX.HTML file

[Eric Gammeter]

Still at this...  Is there any way to determine the last-good db record and 
then delete everything after that in order to salvage my WX year history?


root@raspberrypi:/var/lib/weewx# /etc/init.d/weewx status
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated; vendor preset: enabled)
   Active: active (exited) since Mon 2019-07-08 08:52:59 EDT; 10min ago
 Docs: man:systemd-sysv-generator(8)
  Process: 2872 ExecStop=/etc/init.d/weewx stop (code=exited, 
status=0/SUCCESS)
  Process: 3049 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)

Jul 08 08:53:00 raspberrypi weewx[3064]: File 
"/usr/share/weewx/weewx/engine.py", line 142, in loadServices
Jul 08 08:53:00 raspberrypi weewx[3064]:   
self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
Jul 08 08:53:00 raspberrypi weewx[3064]: File 
"/usr/share/weewx/weewx/engine.py", line 500, in __init__
Jul 08 08:53:00 raspberrypi weewx[3064]:   
self.setup_database(config_dict)
Jul 08 08:53:00 raspberrypi weewx[3064]: File 
"/usr/share/weewx/weewx/engine.py", line 617, in setup_database
Jul 08 08:53:00 raspberrypi weewx[3064]:   _nrecs, _ndays = 
dbmanager.backfill_day_summary() # @UnusedVariable
Jul 08 08:53:00 raspberrypi weewx[3064]: File 
"/usr/share/weewx/weewx/manager.py", line 1447, in backfill_day_summary
Jul 08 08:53:00 raspberrypi weewx[3064]:   
timestamp_to_string(lastRecord)))
Jul 08 08:53:00 raspberrypi weewx[3064]:   ViolatedPrecondition: 
lastUpdate(2036-08-06 20:22:00 EDT (2101681320)) > lastRecord(2019-07-01 
00:00:00 EDT (1561953600))
Jul 08 08:53:00 raspberrypi weewx[3064]:   Exiting.
root@raspberrypi:/var/lib/weewx# 










On Friday, July 5, 2019 at 3:58:01 PM UTC-4, Eric Gammeter wrote:
>
> Hi-  My INDEX.HTML file is being produced each half hour as it should 
> be...but the timestamp (in the file) is incorrect!  The report (attached) 
> shows it is 8/6/2036 @ 08:22:00PM.  
>
> I can see that the reports fire off every 30 mins- and that a new (correct 
> time stamp) INDEX.HTML file is created in the /var/www/html/weewx 
> filesystem-- but that file's info is incorrect.  
>
> I tested (with minicom) and that TEST's fine.
>
> I have shutdown and rebooted the VantageVue station to no avail.  
>
> Thanks for reading!  
>
> /Eric 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8cfcd9af-70cc-4f05-8af2-cb4633c921a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: time/date issue in my INDEX.HTML file

[Thomas Keffer]

I was referring to running wee_device (not sqlite3).

Stop weewxd, then clear the memory.

Then restart weewxd.

-tk

On Sun, Jul 7, 2019 at 5:08 AM Eric Gammeter  wrote:

>
> No joy-  It is stopped.
>
> pi@raspberrypi:/var/lib/weewx $ sqlite3 /var/lib/weewx/weewx.sdb
> SQLite version 3.16.2 2017-01-06 16:32:41
> Enter ".help" for usage hints.
> sqlite> delete from archive where dateTime > x;
> Error: no such column: x
> sqlite>
>
>
>
>
>
>
>
> On Friday, July 5, 2019 at 3:58:01 PM UTC-4, Eric Gammeter wrote:
>>
>> Hi-  My INDEX.HTML file is being produced each half hour as it should
>> be...but the timestamp (in the file) is incorrect!  The report (attached)
>> shows it is 8/6/2036 @ 08:22:00PM.
>>
>> I can see that the reports fire off every 30 mins- and that a new
>> (correct time stamp) INDEX.HTML file is created in the /var/www/html/weewx
>> filesystem-- but that file's info is incorrect.
>>
>> I tested (with minicom) and that TEST's fine.
>>
>> I have shutdown and rebooted the VantageVue station to no avail.
>>
>> Thanks for reading!
>>
>> /Eric
>>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/1965823f-b442-45cd-a875-84974d65bec2%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zECAeoNTmGtjg%2B2tOGuzJ_FtN%3DQVMtQq-nDnK1JaUFKaBA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: time/date issue in my INDEX.HTML file

[Andrew Milner]

you need to replace x with an actual epoch date time value!

so, for example:
delete from archive where dateTime > 1561983540;

to convert a date / time into an epoch date use a site such as:  
https://www.freeformatter.com/epoch-timestamp-to-date-converter.html



On Sunday, 7 July 2019 15:08:15 UTC+3, Eric Gammeter wrote:

>
> No joy-  It is stopped.  
>
> pi@raspberrypi:/var/lib/weewx $ sqlite3 /var/lib/weewx/weewx.sdb
> SQLite version 3.16.2 2017-01-06 16:32:41
> Enter ".help" for usage hints.
> sqlite> delete from archive where dateTime > x;
> Error: no such column: x
> sqlite> 
>
>
>
>
>
>
>
> On Friday, July 5, 2019 at 3:58:01 PM UTC-4, Eric Gammeter wrote:
>>
>> Hi-  My INDEX.HTML file is being produced each half hour as it should 
>> be...but the timestamp (in the file) is incorrect!  The report (attached) 
>> shows it is 8/6/2036 @ 08:22:00PM.  
>>
>> I can see that the reports fire off every 30 mins- and that a new 
>> (correct time stamp) INDEX.HTML file is created in the /var/www/html/weewx 
>> filesystem-- but that file's info is incorrect.  
>>
>> I tested (with minicom) and that TEST's fine.
>>
>> I have shutdown and rebooted the VantageVue station to no avail.  
>>
>> Thanks for reading!  
>>
>> /Eric 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/cb6da8fc-c972-4d41-a48e-5aee0ceab63c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: time/date issue in my INDEX.HTML file

[Eric Gammeter]

No joy-  It is stopped.  

pi@raspberrypi:/var/lib/weewx $ sqlite3 /var/lib/weewx/weewx.sdb
SQLite version 3.16.2 2017-01-06 16:32:41
Enter ".help" for usage hints.
sqlite> delete from archive where dateTime > x;
Error: no such column: x
sqlite> 







On Friday, July 5, 2019 at 3:58:01 PM UTC-4, Eric Gammeter wrote:
>
> Hi-  My INDEX.HTML file is being produced each half hour as it should 
> be...but the timestamp (in the file) is incorrect!  The report (attached) 
> shows it is 8/6/2036 @ 08:22:00PM.  
>
> I can see that the reports fire off every 30 mins- and that a new (correct 
> time stamp) INDEX.HTML file is created in the /var/www/html/weewx 
> filesystem-- but that file's info is incorrect.  
>
> I tested (with minicom) and that TEST's fine.
>
> I have shutdown and rebooted the VantageVue station to no avail.  
>
> Thanks for reading!  
>
> /Eric 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1965823f-b442-45cd-a875-84974d65bec2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: time/date issue in my INDEX.HTML file

[Eric Gammeter]

Yes-  I did.

My mistake!  I did not.  Doing that now.  


On Friday, July 5, 2019 at 3:58:01 PM UTC-4, Eric Gammeter wrote:
>
> Hi-  My INDEX.HTML file is being produced each half hour as it should 
> be...but the timestamp (in the file) is incorrect!  The report (attached) 
> shows it is 8/6/2036 @ 08:22:00PM.  
>
> I can see that the reports fire off every 30 mins- and that a new (correct 
> time stamp) INDEX.HTML file is created in the /var/www/html/weewx 
> filesystem-- but that file's info is incorrect.  
>
> I tested (with minicom) and that TEST's fine.
>
> I have shutdown and rebooted the VantageVue station to no avail.  
>
> Thanks for reading!  
>
> /Eric 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/dd9028ff-8e73-4914-9395-60af0c44cfdb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: time/date issue in my INDEX.HTML file

[Thomas Keffer]

Did you stop weewx before running wee_device?

On Sat, Jul 6, 2019 at 1:02 PM Eric Gammeter  wrote:

> Not making any progress Tom:
>
> root@raspberrypi:/var/lib/weewx# ls -l
> total 9084
> -rw-r--r-- 1 root root 4648960 Jul  4 02:30 weewx.sdb
> -rw-r--r-- 1 root root 4648960 Jul  6 15:00 weewx.sdb.backup
> root@raspberrypi:/var/lib/weewx# sqlite3 weewx.sdb
> SQLite version 3.16.2 2017-01-06 16:32:41
> Enter ".help" for usage hints.
> sqlite> delete from archive where dateTime > x;
> Error: no such column: x
> sqlite>
> root@raspberrypi:/var/lib/weewx#
>
>
> root@raspberrypi:/var/lib/weewx# wee_device --clear-memory
> Using configuration file /etc/weewx/weewx.conf
> Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
> Traceback (most recent call last):
>   File "/usr/bin/wee_device", line 66, in 
> main()
>   File "/usr/bin/wee_device", line 62, in main
> device.configure(config_dict)
>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
> self.do_options(options, parser, config_dict, prompt)
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1972, in
> do_options
> station = Vantage(**config_dict[DRIVER_NAME])
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 488, in __init__
> self._setup()
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1289, in _setup
> unit_bits  = self._getEEPROM_value(0x29)[0]
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1375, in
> _getEEPROM_value
> raise weewx.RetriesExceeded("While getting EEPROM data value at
> address 0x%X" % offset)
> weewx.RetriesExceeded: While getting EEPROM data value at address 0x29
> root@raspberrypi:/var/lib/weewx#
>
>
>
>
>
> On Friday, July 5, 2019 at 3:58:01 PM UTC-4, Eric Gammeter wrote:
>>
>> Hi-  My INDEX.HTML file is being produced each half hour as it should
>> be...but the timestamp (in the file) is incorrect!  The report (attached)
>> shows it is 8/6/2036 @ 08:22:00PM.
>>
>> I can see that the reports fire off every 30 mins- and that a new
>> (correct time stamp) INDEX.HTML file is created in the /var/www/html/weewx
>> filesystem-- but that file's info is incorrect.
>>
>> I tested (with minicom) and that TEST's fine.
>>
>> I have shutdown and rebooted the VantageVue station to no avail.
>>
>> Thanks for reading!
>>
>> /Eric
>>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/60ddaa7f-3668-4787-aa34-32291f09c474%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEAGLmL3ujZNBNPfJ5SxuJaFcXX%2B13zCp%3DVnOHqNd%2B0onA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: time/date issue in my INDEX.HTML file

[Eric Gammeter]

Not making any progress Tom:  

root@raspberrypi:/var/lib/weewx# ls -l
total 9084
-rw-r--r-- 1 root root 4648960 Jul  4 02:30 weewx.sdb
-rw-r--r-- 1 root root 4648960 Jul  6 15:00 weewx.sdb.backup
root@raspberrypi:/var/lib/weewx# sqlite3 weewx.sdb
SQLite version 3.16.2 2017-01-06 16:32:41
Enter ".help" for usage hints.
sqlite> delete from archive where dateTime > x;
Error: no such column: x
sqlite> 
root@raspberrypi:/var/lib/weewx# 


root@raspberrypi:/var/lib/weewx# wee_device --clear-memory
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
Traceback (most recent call last):
  File "/usr/bin/wee_device", line 66, in 
main()
  File "/usr/bin/wee_device", line 62, in main
device.configure(config_dict)
  File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
self.do_options(options, parser, config_dict, prompt)
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1972, in do_options
station = Vantage(**config_dict[DRIVER_NAME])
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 488, in __init__
self._setup()
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1289, in _setup
unit_bits  = self._getEEPROM_value(0x29)[0]
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1375, in 
_getEEPROM_value
raise weewx.RetriesExceeded("While getting EEPROM data value at address 
0x%X" % offset)
weewx.RetriesExceeded: While getting EEPROM data value at address 0x29
root@raspberrypi:/var/lib/weewx# 





On Friday, July 5, 2019 at 3:58:01 PM UTC-4, Eric Gammeter wrote:
>
> Hi-  My INDEX.HTML file is being produced each half hour as it should 
> be...but the timestamp (in the file) is incorrect!  The report (attached) 
> shows it is 8/6/2036 @ 08:22:00PM.  
>
> I can see that the reports fire off every 30 mins- and that a new (correct 
> time stamp) INDEX.HTML file is created in the /var/www/html/weewx 
> filesystem-- but that file's info is incorrect.  
>
> I tested (with minicom) and that TEST's fine.
>
> I have shutdown and rebooted the VantageVue station to no avail.  
>
> Thanks for reading!  
>
> /Eric 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/60ddaa7f-3668-4787-aa34-32291f09c474%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] On this date

[Leon Shaner]

Hey, Robin,

I don't know the weewx way, but here is a sql way that may lead some smart 
person to a better solution.  :-/
I used the system date command up front to get the month-day, which is to avoid 
asking SQLite to do that computation for every row within the query.

$ today=$(date +%\m-%\d); sqlite3 -header /var/lib/weewx/weewx.sdb "select 
date(dateTime, 'unixepoch', 'localtime') as day, min, max from 
archive_day_outTemp where strftime('%m-%d', day)='$today' group by day;"
day|min|max
2017-05-11|46.9|70.0
2018-05-11|43.5|54.9
2019-05-11|39.02|52.7

Oh, and in case outTemp is not the name of your sensor per archive_day_outTemp, 
above, you can glean the table you need from here:

$ sqlite3 /var/lib/weewx/weewx.sdb ".tables"

And of course to see the column names available, it's:

$ sqlite3 /var/lib/weewx/weewx.sdb ".schema archive_day_outTemp"
CREATE TABLE archive_day_outTemp (dateTime INTEGER NOT NULL UNIQUE PRIMARY KEY, 
min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count INTEGER, 
wsum REAL, sumtime INTEGER);

Or the more human readable way:

$ sqlite3 -header /var/lib/weewx/weewx.sdb "select * from archive_day_outTemp 
limit 1;"
dateTime|min|mintime|max|maxtime|sum|count|wsum|sumtime
1325394000|0.0|0|0.0|0

HTH.  =D

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)

> On May 11, 2019, at 9:30 AM, Robin  wrote:
> 
> I apologise if this has been asked before or if there is a simple and obvious 
> way to do this, but I can't see it.
> 
> I want to display the temperature (min,max) for today's date for each year 
> since we started keeping records.
> 
> Can somebody point me in the right direction?
> 
> Thanks people.
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/75abaada-5cb6-47ec-9d3e-0b3046f4f9a3%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/A548DC9B-FF2C-4C11-ABE2-F99F13EF8640%40isylum.org.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] On this date

[Leon Shaner]

Hey, Robin!

I just posted a reply, but the alias didn't echo it back to my inbox.
I think it must have been eaten by the AEther.  :-(
If it doesn't show up soon, I'll try posting it via the web interface to 
googlegroups.com

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)

> On May 11, 2019, at 9:30 AM, Robin  wrote:
> 
> I apologise if this has been asked before or if there is a simple and obvious 
> way to do this, but I can't see it.
> 
> I want to display the temperature (min,max) for today's date for each year 
> since we started keeping records.
> 
> Can somebody point me in the right direction?
> 
> Thanks people.
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/75abaada-5cb6-47ec-9d3e-0b3046f4f9a3%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/017227BA-D43B-4BDE-B103-48550B0C956C%40isylum.org.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] On this date

[Leon Shaner]

Hey, Robin!

I just posted a reply to the group (via e-mail), but didn't echo it back to my 
inbox.
I think it must have been eaten by the AEther.  :-(
Then I tried a more simple message and it didn't post, either.
So now I am trying from the web interface to google groups.
Something seems to be wrong with the alias, or is it just me?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/76b5886d-ccb6-4671-a318-9fc00d40a68e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] On this date

[Leon Shaner]

Posting from the web interface did get echoed to my inbox.  So whatever is 
wrong is on the e-mail reply side.
Here is my original reply.  Hopefully we don't get a duplicate whenever Google 
fixes whatever is wrong with the e-mail interface to the Group.  :-/

FWD:

Hey, Robin,

I don't know the weewx way, but here is a sql way that may lead some smart 
person to a better solution.  :-/
I used the system date command up front to get the month-day, which is to avoid 
asking SQLite to do that computation for every row within the query.

$ today=$(date +%\m-%\d); sqlite3 -header /var/lib/weewx/weewx.sdb "select 
date(dateTime, 'unixepoch', 'localtime') as day, min, max from 
archive_day_outTemp where strftime('%m-%d', day)='$today' group by day;"
day|min|max
2017-05-11|46.9|70.0
2018-05-11|43.5|54.9
2019-05-11|39.02|52.7

Oh, and in case outTemp is not the name of your sensor per archive_day_outTemp, 
above, you can glean the table you need from here:

$ sqlite3 /var/lib/weewx/weewx.sdb ".tables"

And of course to see the column names available, it's:

$ sqlite3 /var/lib/weewx/weewx.sdb ".schema archive_day_outTemp"
CREATE TABLE archive_day_outTemp (dateTime INTEGER NOT NULL UNIQUE PRIMARY KEY, 
min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count INTEGER, 
wsum REAL, sumtime INTEGER);

Or the more human readable way:

$ sqlite3 -header /var/lib/weewx/weewx.sdb "select * from archive_day_outTemp 
limit 1;"
dateTime|min|mintime|max|maxtime|sum|count|wsum|sumtime
1325394000|0.0|0|0.0|0

HTH.  =D

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b9d8a97c-17db-4a7b-80aa-7d3354e97485%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] On this date

[Robin]

I apologise if this has been asked before or if there is a simple and 
obvious way to do this, but I can't see it.

I want to display the temperature (min,max) for today's date for each year 
since we started keeping records.

Can somebody point me in the right direction?

Thanks people.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/75abaada-5cb6-47ec-9d3e-0b3046f4f9a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Custom date range graphs

[Thomas Keffer]

In addition to what Gary says, you can also use the utility wee_reports
 to plot a
general date by using a timestamp as a parameter.

-tk

On Sun, Apr 14, 2019 at 5:41 AM gjr80  wrote:

> Hi,
>
> There are some extensions that use 3rd party packages to produce plots but
> they are not really standalone extensions that you just 'add in' wherever
> you like. So not really conducive to making changes to the Seasons skin.
> Given the limitations of the current plot engine you are fairly much
> limited to changing the time_length config option (either varying
> existing plots or adding new ones) under [ImageGenerator] in the Season
> skin skin.conf.
>
> Gary
>
> On Sunday, 14 April 2019 15:54:39 UTC+10, Praveen Chandrasekaran wrote:
>>
>> Is there any extension available to plot graphs over custom date range? I
>> am using Seasons skin.
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Custom date range graphs

[gjr80]

Hi,

There are some extensions that use 3rd party packages to produce plots but 
they are not really standalone extensions that you just 'add in' wherever 
you like. So not really conducive to making changes to the Seasons skin. 
Given the limitations of the current plot engine you are fairly much 
limited to changing the time_length config option (either varying existing 
plots or adding new ones) under [ImageGenerator] in the Season skin 
skin.conf.

Gary

On Sunday, 14 April 2019 15:54:39 UTC+10, Praveen Chandrasekaran wrote:
>
> Is there any extension available to plot graphs over custom date range? I 
> am using Seasons skin. 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Time/date display format on weewx pages

[gjr80]

Hi,

Assuming here that you are referring to the Standard skin (or another well 
behaved skin generated page) the simplest approach is to change the 
[[TimeFormats]] settings in the skin's skin.conf. Have a look at 
[[TimeFormats]]  
in the Customization Guide. Note that the default date-time formats used 
are locale dependent so if you are in a locale that uses mdy and you want 
to see dmy then you will need to move away from using locale dependent 
formats and force a particular format. The link to the strftime() formats 
will give you a definitive list of format codes supported (you will find 
the format codes right at the very bottom of the linked page).

You could also override 

 
the [[TimeFormats]] settings for that particular skin from weewx.conf, this 
is of benefit in that you keep your customizations if the underlying skin 
templates might be changed/upgraded in the future.

Gary

On Sunday, 25 March 2018 04:32:31 UTC+10, Dan'l B wrote:
>
> Can someone point me to how I can alter the time/date display on the top 
> of each page? Mine currently displays in US format (as per attached image) 
> and I would prefer the dd/mm/ & 24 hour format. I'm running on an RPi3 
> and VP2; is that format inherited from the VP2 or the Pi. My weewx setup 
> uses US weather notation.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Manual date entry

[Charles Ross]

Thanks Gary, I'll give it a go!

Much appreciated,

Chuck

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Manual date entry

[gjr80]

Hi,

Assuming you are using weeWX 3.6.0 or later the easiest approach will be to 
enter your misisng data in a file in CSV format and then import the data 
using the wee_import 
 utility. Have a 
good read through the wee_import documentation, in particular the section 
Importing 
from CSV files 
, you should 
find everything there you need to correctly format your data for import. Do 
make sure you make a backup of your database and do a dry run before doing 
any actual import in case things go awry.

Oh, if you are using an earlier version of weeWX, upgrade to 3.6.0 or later 
and then use wee_import :-)

Gary

On Saturday, 22 July 2017 09:22:03 UTC+10, Charles Ross wrote:
>
> Sorry, title should read manual data entry.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Niculskin - Date and time Formatting.

[John Rye]

On Saturday, 21 January 2017 22:24:08 UTC+13, John Rye wrote:
>
> Hi All,
>
> Replying to self - Bad form :-)
>

After suffering from a severe storm and a series of very quick power 
interruptions which KILLED the computer running weewx I have finally got 
things running again.

I have realised my problem was more than likely that I followed the 
instructions on Nico's github pages and installed by manually copying the 
code into place. To be honest I really no idea that was the reason either.

At this point my default installation is at: http://newall-wx.gen.nz.

On a separate machine on my network I've installed and configured weewx and 
and then used wee_extension to install the Niculskin. I have now got it 
working reliably using the simulator engine after a great many hours of 
tweeking along the lines indicated by Gary.

So is it now simply a matter of copying the entire weewx codebase from the 
simulator setup to the live system and running wee_config --reconfigure?

There are a couple of weird displays on the test setup that I haven't been 
able to resolve but I'll address that in another thread.

Cheers (I think)

John in NZ

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Niculskin - Date and time Formatting.

[Darryn Capes-Davis]

John,

I have done a bit of thinking and testing on my Ubuntu setup. Three things 
here.

1. Missing LC_ALL is an issue. Find your favourite information to fix on 
Google.
2. Missing LC_ALL will mean "%x %X" will give what you are seeing on 
index.html
3. I expect that Niculskin code for localising strings is giving havoc to 
weewx ConfigObj code and making weewx.conf override skin.conf (just a 
guess).

Fixes?

A. Fix LC_ALL (Looks like setting in /etc/environment is best bet). Can 
test by running in python interpreter .

You will see for me, where I also have the LC_ALL issue, I get the wrong 
format with "%x %X", even though the rest of my LC_X and en_AU.

>>> import datetime
>>> datetime.datetime.now().strftime("%x %X")
'01/22/17 19:16:00'

 B. Since you don't need Niculskin localisation, you can not use the 
Niculskin binaries CheetahGeneratorTranslated. Revert back to 
weewx.cheetahgenerator.CheetahGenerator.

Good luck.

Cheers

Darryn

On Sunday, January 22, 2017 at 3:07:11 PM UTC+11, gjr80 wrote:

> You did stop/start or reload weewx after making changes to weewx.conf? 
> Not required for changes to skin.conf but is required for weewx.conf 
> changes.
>
> Gary
>
> On Sunday, 22 January 2017 00:56:30 UTC+10, John Rye wrote:
>
>>
>>
>> On Sunday, 22 January 2017 01:08:11 UTC+13, Darryn Capes-Davis wrote:
>>>
>>> John,
>>>
>>> > What locale is your server? 
>>>
>>
>> [lists@amd64 ~]$ locale
>> LANG=en_NZ.UTF-8
>> LC_CTYPE="en_NZ.UTF-8"
>> LC_NUMERIC="en_NZ.UTF-8"
>> LC_TIME="en_NZ.UTF-8"
>> LC_COLLATE="en_NZ.UTF-8"
>> LC_MONETARY="en_NZ.UTF-8"
>> LC_MESSAGES="en_NZ.UTF-8"
>> LC_PAPER="en_NZ.UTF-8"
>> LC_NAME="en_NZ.UTF-8"
>> LC_ADDRESS="en_NZ.UTF-8"
>> LC_TELEPHONE="en_NZ.UTF-8"
>> LC_MEASUREMENT="en_NZ.UTF-8"
>> LC_IDENTIFICATION="en_NZ.UTF-8"
>> LC_ALL=
>> [lists@amd64 ~]$ 
>>
>>   So physically in New Zealand as is the server.
>>  
>>
>>> > I ask as the only way you would be getting the display on your site 
>>> would be from the format string "%x %X" on a US locale server. 
>>>
>>
>>  Agreed. However I have altered all the time format strings in weewx.conf 
>> in line with what is shown in 
>> http://weewx.com/docs/customizing.htm#Units_TimeFormats. I don't see any 
>> point in going further and custominsing as per strftime - it shouldn't be 
>> necessary
>>
>>>
>>> > However I can't see how the format "%x %X" would be being used?
>>>
>>
>> I'm beginning to wonder if its hard-coded in the javascript (/me 
>> shudders) because I'm fairly sure I was able to alter the formatting in the 
>> Standard skin.
>>
>> Cheers
>>
>> John in NZ
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Niculskin - Date and time Formatting.

[gjr80]

You did stop/start or reload weewx after making changes to weewx.conf? Not 
required for changes to skin.conf but is required for weewx.conf changes.

Gary

On Sunday, 22 January 2017 00:56:30 UTC+10, John Rye wrote:
>
>
>
> On Sunday, 22 January 2017 01:08:11 UTC+13, Darryn Capes-Davis wrote:
>>
>> John,
>>
>> > What locale is your server? 
>>
>
> [lists@amd64 ~]$ locale
> LANG=en_NZ.UTF-8
> LC_CTYPE="en_NZ.UTF-8"
> LC_NUMERIC="en_NZ.UTF-8"
> LC_TIME="en_NZ.UTF-8"
> LC_COLLATE="en_NZ.UTF-8"
> LC_MONETARY="en_NZ.UTF-8"
> LC_MESSAGES="en_NZ.UTF-8"
> LC_PAPER="en_NZ.UTF-8"
> LC_NAME="en_NZ.UTF-8"
> LC_ADDRESS="en_NZ.UTF-8"
> LC_TELEPHONE="en_NZ.UTF-8"
> LC_MEASUREMENT="en_NZ.UTF-8"
> LC_IDENTIFICATION="en_NZ.UTF-8"
> LC_ALL=
> [lists@amd64 ~]$ 
>
>   So physically in New Zealand as is the server.
>  
>
>> > I ask as the only way you would be getting the display on your site 
>> would be from the format string "%x %X" on a US locale server. 
>>
>
>  Agreed. However I have altered all the time format strings in weewx.conf 
> in line with what is shown in 
> http://weewx.com/docs/customizing.htm#Units_TimeFormats. I don't see any 
> point in going further and custominsing as per strftime - it shouldn't be 
> necessary
>
>>
>> > However I can't see how the format "%x %X" would be being used?
>>
>
> I'm beginning to wonder if its hard-coded in the javascript (/me shudders) 
> because I'm fairly sure I was able to alter the formatting in the Standard 
> skin.
>
> Cheers
>
> John in NZ
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: [weewx-user] Re: Niculskin - Date and time Formatting.

[Carlingford Weather]

John,

A thought. Are you using wee_reports external or just allowing weewx to 
generate the reports per archive interval?

Darryn

From: gjr80<mailto:gjroder...@gmail.com>
Sent: Sunday, 22 January 2017 2:12 PM
To: weewx-user<mailto:weewx-user@googlegroups.com>
Subject: [weewx-user] Re: Niculskin - Date and time Formatting.

John,

I was intrigued as niculskin is not that complex and in its index.html.tmpl 
template it just uses plain $current.dateTime (line 39) to display 'Last 
updated'. So it should be respecting the standard date/time formats in 
niculskin/skin.conf (there are no overrides in weewx.conf - unless the user had 
some there before the niculskin install). Still intrigued I fired up a debain 
VM running weewx/simulator and installed niculskin using wee_extension. I don't 
know whether you encountered any runtime errors after install but I had to (1) 
manually install the skins/niculskin/RSS directory and (2) edit 
niculskin/skin.conf and under [niculskinLabels] [[conditions]] I had to change 
extra_1_temp_humidity to extra1_temp_humidity and extra_2_temp_humidity to 
extra2_temp_humidity. None of these should affect date-time formats though.

When run out of the box (with the aforementioned changes and language =  in 
niculskin/skin.conf) the 'Last updated' line in index.html was (sorry VM is not 
publicly accessible):

 Last updated 22/01/17 12:50:00

When I make the following change to /niculskin/skin.conf:

[Units]
[[TimeFormats]]
current = %d %b %Y

I get:

 Last updated 22-Jan-2017 12:40

As it should be. Not that it matters but my locale is coming up AU:

LANG=en_AU.UTF-8
LANGUAGE=en_AU:en
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=

Seems to me that everything is working as it should, I cannot find fault with 
niculskin. Personally I don't like making the change skin = niculskin under 
[StdReport] [[StandardReport]] in weewwx.conf as the [[StandardReport]] will 
tend to lead some people to skins/Standard/skin.conf (rather than 
skins/niculskin/skin.conf) if they want to change something like a date or time 
format but again that is just an ease of use issue and would not change the 
date-time format.

I'll give it some more thought but I am tending to think it is something 
peculiar to your install.

Gary

On Sunday, 22 January 2017 01:27:06 UTC+10, John Rye wrote:


On Sunday, 22 January 2017 03:56:30 UTC+13, John Rye wrote:


And replying to self ...

Reverted to Standard skin ... Guess what?  Dates are in dd/mm/yy format

The "problem" does not seem to lay with Weewx  but with underlaying code in the 
Nico's skin somehow ignoring or overriding weewx.conf.

A pity because I really like that skin ...

John in NZ


--
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/lOgABRVqDcs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com<mailto:weewx-user+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Niculskin - Date and time Formatting.

[gjr80]

John,

I was intrigued as niculskin is not that complex and in its index.html.tmpl 
template it just uses plain $current.dateTime (line 39) to display 'Last 
updated'. So it should be respecting the standard date/time formats in 
niculskin/skin.conf (there are no overrides in weewx.conf - unless the user 
had some there before the niculskin install). Still intrigued I fired up a 
debain VM running weewx/simulator and installed niculskin using 
wee_extension. I don't know whether you encountered any runtime errors 
after install but I had to (1) manually install the skins/niculskin/RSS 
directory and (2) edit niculskin/skin.conf and under [niculskinLabels] 
[[conditions]] I had to change extra_1_temp_humidity to extra1_temp_humidity 
and extra_2_temp_humidity to extra2_temp_humidity. None of these should 
affect date-time formats though.

When run out of the box (with the aforementioned changes and language =  in 
niculskin/skin.conf) the 'Last updated' line in index.html was (sorry VM is 
not publicly accessible):

 Last updated 22/01/17 12:50:00

When I make the following change to /niculskin/skin.conf:

[Units]
[[TimeFormats]]
current = %d %b %Y

I get:

 Last updated 22-Jan-2017 12:40

As it should be. Not that it matters but my locale is coming up AU:

LANG=en_AU.UTF-8
LANGUAGE=en_AU:en
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=

Seems to me that everything is working as it should, I cannot find fault 
with niculskin. Personally I don't like making the change skin = niculskin 
under [StdReport] [[StandardReport]] in weewwx.conf as the 
[[StandardReport]] will tend to lead some people to skins/Standard/skin.conf 
(rather than skins/niculskin/skin.conf) if they want to change something 
like a date or time format but again that is just an ease of use issue and 
would not change the date-time format.

I'll give it some more thought but I am tending to think it is something 
peculiar to your install.

Gary

On Sunday, 22 January 2017 01:27:06 UTC+10, John Rye wrote:
>
>
>
> On Sunday, 22 January 2017 03:56:30 UTC+13, John Rye wrote:
>>
>>
>>
>> And replying to self ...
>>
>
> Reverted to Standard skin ... Guess what?  Dates are in dd/mm/yy format
>
> The "problem" does not seem to lay with Weewx  but with underlaying code 
> in the Nico's skin somehow ignoring or overriding weewx.conf.
>
> A pity because I really like that skin ...
>
> John in NZ
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Niculskin - Date and time Formatting.

[Darryn Capes-Davis]

John,

What locale is your server? I ask as the only way you would be getting the 
display on your site would be from the format string "%x %X" on a US locale 
server. 

However I can't see how the format "%x %X" would be being used?

Darryn

On Saturday, January 21, 2017 at 8:24:08 PM UTC+11, John Rye wrote:

> Hi All,
>
> A while ago I installed Nico Gulen's Niculskin and overall I'm really
> happy with it. (http:/newall-wx.gen.nz)
>
> However ... (isn't there always one or two of these )
>
> However #1: How or where are the date and time displays actually
> configured? 
>
> It appears to me that the settings in both /etc/weewx/weewx.conf
> and /etc/weewx/skins/niculskin/skin.conf are being ignored. 
>
> This can be seen in the site where all dates are displayed in
> month-day-year format and and times in 12-hour format.
>
> I have attached both /etc/weewx/weewx.conf and niculskin/skin.conf.
>
> Cheers
>
> John in NZ
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.