[weewx-user] Re: Error with NOAA reports, aggregate type meanmax

[gjr80]

It is possible the error is to do with the first records in your archive 
rather than the latest, though this would only likely be the case if your 
NOAA format files have never been generated (otherwise the 2023 NOAA year 
would currently be being generated, and since you are using WeeWX v3.9.2 I 
assume you have data from 2022 or earlier). Let's hold of making changes to 
your data just yet.

Could you stop WeeWX, edit weewx.conf, set debug = 1 then save weewx.conf. 
Then delete all of the neowx generated NOAA format files (*.txt) on your 
WeeWX system, they should be somewhere under /var/www/html/weewx, possibly 
under neowx/NOAA (this depends on the neowx skin). This will force WeeWX to 
regenerate all of the neowx NOAA format files. Finally, restart WeeWX and 
take a log extract showing the full WeeWX startup and the first few report 
generation cycles - capturing the full WeeWX startup is important, it 
contains a lot of WeeWX config info. This wiki page 

 
has tips on how to get a good (and complete) log extract if you are having 
problems.

Gary
On Wednesday, 7 June 2023 at 13:26:45 UTC+2 mihec wrote:

> I agree with you, maybe there was some date misalignment after fresh 
> install. I've attached the syslog just after the weewx start.
> I do have 1-minute archiving interval.
> Is it possible to simply remove first few entries in the database perhaps? 
> I don't mind losing first few hours.
>
> Thanks.
> torek, 6. junij 2023 ob 13:04:00 UTC+2 je oseba gjr80 napisala:
>
>> I am away from home so cannot help with the locale issue, Tom or others 
>> may have some insights. It does not appear to be related to the 
>> meanmax/wind issue.
>>
>> I still think that something is causing WeeWX to see future dated 
>> records, or more precisely, the current record during a report cycle is not 
>> being seen as the most recent record. If 20:43 was the time of your most 
>> recent archive record I am guessing you are using a very short archive 
>> period, say one minute? From the short log extract it appears that WeeWX is 
>> handling this OK, but it would be better to see a longer log extract, 
>> preferably following a WeeWX restart so we can see the full WeeWX startup. 
>> Could you restart WeeWX and then post a log extract showing the full WeeWX 
>> startup and then say, at least 10 or so archive intervals.
>>
>> Gary
>>
>> On Monday, 5 June 2023 at 20:52:36 UTC+2 mihec wrote:
>>
>>> Hi Gary,
>>> thanks for you quick response!
>>> I checked for the latest date in my database and it seems I have no such 
>>> records:
>>>
>>> pi@raspberrypi:~/database $ sqlite3 weewx.sdb 
>>> SQLite version 3.16.2 2017-01-06 16:32:41
>>> Enter ".help" for usage hints.
>>>
>>> sqlite> SELECT datetime(MAX(dateTime), 'unixepoch', 'localtime') FROM 
>>> archive;
>>> 2023-06-05 20:43:00
>>> sqlite> .q
>>>
>>> I tried to do a rebuild-daily:
>>>
>>> pi@raspberrypi:~/database $  wee_database --rebuild-daily
>>>
>>> Traceback (most recent call last):
>>>   File "/usr/bin/wee_database", line 18, in 
>>> import user.extensions  #@UnusedImport
>>>   File "/usr/share/weewx/user/extensions.py", line 18, in 
>>> locale.setlocale(locale.LC_ALL, '')
>>>   File "/usr/lib/python2.7/locale.py", line 581, in setlocale
>>> return _setlocale(category, locale)
>>> locale.Error: unsupported locale setting
>>>
>>> Something in my configuration doesn't seem ok... Probably not related to 
>>> original post.
>>>
>>> Thanks for any further hint.
>>> ponedeljek, 5. junij 2023 ob 20:02:53 UTC+2 je oseba gjr80 napisala:
>>>
 Something appears to be forcing some of your aggregates that should be 
 calculated on the daily summaries to be instead calculated on the archive. 
 is there any chance you have some future dated records in your archive? 
 Try 
 the following to check:

 1. open your database with sqlite3:
 $ sqlite3 /var/lib/weewx/weewx.sdb
 (if sqlite3 is not found you will need to install it using something 
 like sudo apt install sqlite3 and then try again)

 2. obtain the timestamp of the last record in the archive in human 
 readable form:
 sqlite> SELECT datetime(MAX(dateTime), 'unixepoch', 'localtime') FROM 
 archive;
 This should display something like:
 2023-06-05 03:05:00

 3. exit sqlite3:
 sqlite> .q

 If the date at step 2 above is in the future you have some future dated 
 records in your archive. To remove these:

 1. stop WeeWX
 $ sudo systemctl stop weewx

 2. make a backup of your WeeWX database:
 $ cp /var/lib/weewx/weewx.sdb /var/lib/weewx/weewx_backup.sdb

 3. open your database with sqlite3:
 $ sqlite3 /var/lib/weewx/weewx.sdb

 4. delete all future dated archive records:
 sqlite> DELETE FROM archive WHERE dateTime>STRFTIME('%s');

 5. check there are no more future dated records:
 sqli

Re: [weewx-user] Re: WDC Skin

[Greg from Oz]

Hi,

I am testing the wdc skin and have set the html document root to 
/var/www/html/weather/wdc
If I go to https://weather.ubeaut.work/wdc/ (because I am testing and want 
to leave my other webpages) it shows the wdc index.html which is good.
If I click on any of the menu items eg Today  week month it takes me to my 
other web page. Yesterday doesn't work because on my other webpage there 
isn't a yesterday web page.
I suspect it is because of the $get_base_path which would be 
https://weather.ubeaut.work in this case.
How or where can I change this to be https://weather.ubeaut.work/wdc so I 
can test it out?

Thanks


On Monday, 3 April 2023 at 00:31:31 UTC+10 gary@gmail.com wrote:

> Version 3.1.1 has been released and this is now one of the nicest skins 
> I've used.
> Clear text, excellent graphs, histograms, live data from MQTT.
> Scales well to tablets.
> For my needs, replaced the Belchertown skin.
> On Friday, August 5, 2022 at 10:43:52 AM UTC-4 Andrea Di Saverio wrote:
>
>> Sorry for my late replay.
>>
>> Yes, the suggestion solved my problem. I was not installing as root user.
>> Thank you.
>>
>> Il giorno giovedì 4 agosto 2022 alle 01:46:26 UTC+2 david@gmail.com 
>> ha scritto:
>>
>>> @disaveri Did this solve your problem?
>>>
>>> Btw: I released 2.0.1 which resolves the "non-web-root"-issue, the 
>>> "Pressure diagram with inHg unit"-issue and includes a few other bugfixes: 
>>> https://github.com/Daveiano/weewx-wdc/releases/tag/v2.0.1
>>>
>>> Thanks for your input!
>>>
>>> vince schrieb am Dienstag, 2. August 2022 um 00:54:05 UTC+2:
>>>
 On Monday, August 1, 2022 at 3:32:23 PM UTC-7 disaveri...@gmail.com 
 wrote:

>  the root cause is possibly something else?
>

 Yes.  The 'root' cause indeed. 

 See the  FAQ - 
 https://github.com/weewx/weewx/wiki/faq-permission-denied
  

>>>

-- 
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/9d6e0159-83d8-4a06-8ebc-e30af3842d96n%40googlegroups.com.

Re: [weewx-user] Re: WDC Skin

[David Bätge]

Hi Greg!  Please set the base_path in skin.conf to '/wdc/':

base_path = /wdc/

See 
https://github.com/Daveiano/weewx-wdc/wiki/WeeWX-related#setting-html_root-and-basepath
 
and https://github.com/Daveiano/weewx-wdc/wiki/Configuration#extras. This 
should resolve the problem.
Greg from Oz schrieb am Donnerstag, 8. Juni 2023 um 10:53:53 UTC+2:

> Hi,
>
> I am testing the wdc skin and have set the html document root to 
> /var/www/html/weather/wdc
> If I go to https://weather.ubeaut.work/wdc/ (because I am testing and 
> want to leave my other webpages) it shows the wdc index.html which is good.
> If I click on any of the menu items eg Today  week month it takes me to my 
> other web page. Yesterday doesn't work because on my other webpage there 
> isn't a yesterday web page.
> I suspect it is because of the $get_base_path which would be 
> https://weather.ubeaut.work in this case.
> How or where can I change this to be https://weather.ubeaut.work/wdc so I 
> can test it out?
>
> Thanks
>
>
> On Monday, 3 April 2023 at 00:31:31 UTC+10 gary@gmail.com wrote:
>
>> Version 3.1.1 has been released and this is now one of the nicest skins 
>> I've used.
>> Clear text, excellent graphs, histograms, live data from MQTT.
>> Scales well to tablets.
>> For my needs, replaced the Belchertown skin.
>> On Friday, August 5, 2022 at 10:43:52 AM UTC-4 Andrea Di Saverio wrote:
>>
>>> Sorry for my late replay.
>>>
>>> Yes, the suggestion solved my problem. I was not installing as root user.
>>> Thank you.
>>>
>>> Il giorno giovedì 4 agosto 2022 alle 01:46:26 UTC+2 david@gmail.com 
>>> ha scritto:
>>>
 @disaveri Did this solve your problem?

 Btw: I released 2.0.1 which resolves the "non-web-root"-issue, the 
 "Pressure diagram with inHg unit"-issue and includes a few other bugfixes: 
 https://github.com/Daveiano/weewx-wdc/releases/tag/v2.0.1

 Thanks for your input!

 vince schrieb am Dienstag, 2. August 2022 um 00:54:05 UTC+2:

> On Monday, August 1, 2022 at 3:32:23 PM UTC-7 disaveri...@gmail.com 
> wrote:
>
>>  the root cause is possibly something else?
>>
>
> Yes.  The 'root' cause indeed. 
>
> See the  FAQ - 
> https://github.com/weewx/weewx/wiki/faq-permission-denied
>  
>


-- 
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/211b9bac-f1ce-4ea3-9aae-0cc91af870a8n%40googlegroups.com.

Re: [weewx-user] Re: WDC Skin

[Greg from Oz]

Yes that works.
I did a grep of the whole directory and sub directories looking for that 
and missed it.
But I was looking for get_base_path and not just base_path

Thanks again.

On Thursday, 8 June 2023 at 19:05:48 UTC+10 David Bätge wrote:

> Hi Greg!  Please set the base_path in skin.conf to '/wdc/':
>
> base_path = /wdc/
>
> See 
> https://github.com/Daveiano/weewx-wdc/wiki/WeeWX-related#setting-html_root-and-basepath
>  
> and https://github.com/Daveiano/weewx-wdc/wiki/Configuration#extras. This 
> should resolve the problem.
> Greg from Oz schrieb am Donnerstag, 8. Juni 2023 um 10:53:53 UTC+2:
>
>> Hi,
>>
>> I am testing the wdc skin and have set the html document root to 
>> /var/www/html/weather/wdc
>> If I go to https://weather.ubeaut.work/wdc/ (because I am testing and 
>> want to leave my other webpages) it shows the wdc index.html which is good.
>> If I click on any of the menu items eg Today  week month it takes me to 
>> my other web page. Yesterday doesn't work because on my other webpage there 
>> isn't a yesterday web page.
>> I suspect it is because of the $get_base_path which would be 
>> https://weather.ubeaut.work in this case.
>> How or where can I change this to be https://weather.ubeaut.work/wdc so 
>> I can test it out?
>>
>> Thanks
>>
>>
>> On Monday, 3 April 2023 at 00:31:31 UTC+10 gary@gmail.com wrote:
>>
>>> Version 3.1.1 has been released and this is now one of the nicest skins 
>>> I've used.
>>> Clear text, excellent graphs, histograms, live data from MQTT.
>>> Scales well to tablets.
>>> For my needs, replaced the Belchertown skin.
>>> On Friday, August 5, 2022 at 10:43:52 AM UTC-4 Andrea Di Saverio wrote:
>>>
 Sorry for my late replay.

 Yes, the suggestion solved my problem. I was not installing as root 
 user.
 Thank you.

 Il giorno giovedì 4 agosto 2022 alle 01:46:26 UTC+2 david@gmail.com 
 ha scritto:

> @disaveri Did this solve your problem?
>
> Btw: I released 2.0.1 which resolves the "non-web-root"-issue, the 
> "Pressure diagram with inHg unit"-issue and includes a few other 
> bugfixes: 
> https://github.com/Daveiano/weewx-wdc/releases/tag/v2.0.1
>
> Thanks for your input!
>
> vince schrieb am Dienstag, 2. August 2022 um 00:54:05 UTC+2:
>
>> On Monday, August 1, 2022 at 3:32:23 PM UTC-7 disaveri...@gmail.com 
>> wrote:
>>
>>>  the root cause is possibly something else?
>>>
>>
>> Yes.  The 'root' cause indeed. 
>>
>> See the  FAQ - 
>> https://github.com/weewx/weewx/wiki/faq-permission-denied
>>  
>>
>

-- 
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/d690e4ea-439a-4772-8b83-64527824bedfn%40googlegroups.com.

Re: [weewx-user] New install of Weewx, Raspberry Pi, Apache 2.4.56 - 403 Forbidden

[kufuu]

Hello , I installed weewx on a Pi zero-w using nginx last year running a 
Lacrosse 2315 ws, I kept getting the same 403 error, what I did find out 
after redoing the software several times is that it takes several minutes 
to load the weather data after the pi zero has been restarted and it has 
worked just fine since I found that out.

On Monday, May 22, 2023 at 2:02:46 PM UTC-4 Rainer Lang wrote:

> what do you get when you enter just the RaspberryPi IP address in your 
> browser ?
> you should get the standard webserver page (Apache2 Debian Default Page)
> does this work ?
>
> if so, has the folder /var/www/html/weewx been created in the first place ?
> can you see the folder in the Raspi File Manager ?
> has weewx written the skin files into that directory ? (there should be a 
> lot of .png files and the index.html file)
> On 22.05.2023 19:53, Peter Hurn wrote:
>
> Thanks I tried the  sudo chmod -R 755 /var/www/html/weewx suggested, 
> still the same issue unfortunately  
> You don't have permission to access this resource.
>
> On Friday, 19 May 2023 at 13:50:17 UTC+1 Rainer Lang wrote:
>
>> did you change the permissions for weewx web folder
>>
>> /var/www/html/weewx
>>
>> or
>>
>> /home/weewx/public_html
>>
>> whichever you are using ?
>>
>> The example for the first path would be
>>
>> sudo chmod -R 755 /var/www/html/weewx
>>
>> only then the Apache webserver has the permission to read (and display) 
>> the /var/www/html/weewx folder content
>>
>> (for a /home/weewx installation the command would be: 
>> sudo chmod -R 755 /home/weewx/public_html  )
>> On 18.05.2023 23:48, Peter Hurn wrote:
>>
>> Hello, 
>>
>> I am trying to install Weewx fresh on a Raspberry PI, running Debian 
>> Bullseye,
>> I would like to host the website internally from the Pi,
>> I have installed Apache 2.4.56 and checked the default Apache page 
>> displays correctly, which it does.
>>
>> I then followed the Weewx installation which installed.
>>
>> I then followed the instructions from the wiki article *Configure a web 
>> server (Apache, NGINX or lighttpd)* 
>> 
>>  
>>
>> The section for Apache 2.4 worked however when I try to navigate to the 
>> server address/weewx/ I now receive the following error.
>>
>> --
>>
>> Forbidden
>> You don't have permission to access this resource.
>>
>> Apache/2.4.56 (Raspbian) Server at (IP) Port 80
>>
>> -
>>
>> I have searched but don't seem to be having much luck resolving the 
>> issue, any thoughts?
>>
>> Kind regards,
>>
>> Peter.
>>
>> -- 
>> 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/b43bca91-0b12-42c0-b4db-dc06cfcf1fe0n%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+...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/eb612886-cc2a-4d0d-9c06-1486203b4c13n%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/50e31823-f70d-4bd2-8fa6-bd60a9311d0fn%40googlegroups.com.

Re: [weewx-user] Re: Problemas para publicar mqtt

[jose riaño]

 11:34:22 raspberrypi systemd[1]: Stopping LSB: weewx weather system...
Jun  8 11:34:22 raspberrypi weewx[9085]: engine: Received signal TERM (15).
Jun  8 11:34:22 raspberrypi weewx[9085]: engine: Main loop exiting.
Shutting engine down.
Jun  8 11:34:26 raspberrypi weewx[9085]: restx: MQTT: Failed to connect to
MQTT server (mqtt://...): timed out
Jun  8 11:34:26 raspberrypi weewx[9085]: restx: MQTT: Failed to connect to
MQTT server (mqtt://): timed out
Jun  8 11:34:26 raspberrypi weewx[9085]: restx: MQTT: Failed to publish
record 2023-06-08 11:34:00 -05 (1686242040): MQTT client not available
Jun  8 11:34:26 raspberrypi weewx[9085]: restx: MQTT: Failed to publish
record 2023-06-08 11:34:00 -05 (1686242040): MQTT client not available
Jun  8 11:34:26 raspberrypi weewx[9085]: restx: Shut down MQTT thread.
Jun  8 11:34:26 raspberrypi weewx[9085]: engine: Shutting down StdReport
thread
Jun  8 11:34:26 raspberrypi weewx[9085]: engine: StdReport thread has been
terminated
Jun  8 11:34:26 raspberrypi weewx[9085]: restx: Shut down MQTT thread.
Jun  8 11:34:26 raspberrypi weewx[9085]: engine: Terminating weewx version
3.9.2
Jun  8 11:34:27 raspberrypi weewx[9085]:   Traceback (most recent
call last):
Jun  8 11:34:27 raspberrypi weewx[9085]: File
"/usr/share/weewx/weewx/engine.py", line 894, in main
Jun  8 11:34:27 raspberrypi weewx[9085]:   engine.run()
Jun  8 11:34:27 raspberrypi weewx[9085]: File
"/usr/share/weewx/weewx/engine.py", line 188, in run
Jun  8 11:34:27 raspberrypi weewx[9085]:   for packet in
self.console.genLoopPackets():
Jun  8 11:34:27 raspberrypi weewx[9085]: File
"/usr/share/weewx/weewx/drivers/vantage.py", line 508, in genLoopPackets
Jun  8 11:34:27 raspberrypi weewx[9085]:   for _loop_packet in
self.genDavisLoopPackets(200):
Jun  8 11:34:27 raspberrypi weewx[9085]: File
"/usr/share/weewx/weewx/drivers/vantage.py", line 535, in
genDavisLoopPackets
Jun  8 11:34:27 raspberrypi weewx[9085]:   _buffer =
self.port.read(99)
Jun  8 11:34:27 raspberrypi weewx[9085]: File
"/usr/share/weewx/weewx/drivers/vantage.py", line 256, in read
Jun  8 11:34:27 raspberrypi weewx[9085]:   _buffer =
self.serial_port.read(chars)
Jun  8 11:34:27 raspberrypi weewx[9085]: File
"/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 483, in read
Jun  8 11:34:27 raspberrypi weewx[9085]:   ready, _, _ =
select.select([self.fd, self.pipe_abort_read_r], [], [],
timeout.time_left())
Jun  8 11:34:27 raspberrypi weewx[9085]: File
"/usr/share/weewx/weewx/engine.py", line 812, in sigTERMhandler
Jun  8 11:34:27 raspberrypi weewx[9085]:   raise Terminate
Jun  8 11:34:27 raspberrypi weewx[9085]:   Terminate
Jun  8 11:34:27 raspberrypi weewx[9685]: Stopping weewx weather system:
weewx..
Jun  8 11:34:27 raspberrypi systemd[1]: weewx.service: Succeeded.
Jun  8 11:34:27 raspberrypi systemd[1]: Stopped LSB: weewx weather system.



 Tengo esta salida pero no se me ayudan por favor ???

El vie, 26 may 2023 a las 13:30, jose riaño () escribió:

> no nada ya lo hice y me sigue el error ??? que podrá ser
>
> El jueves, 25 de mayo de 2023 a las 19:59:14 UTC-5, vince escribió:
>
>> Pre-Requisites Install the MQTT python bindings For python3: sudo pip3
>> install paho-mqtt For python2: sudo pip install paho-mqtt
>>
>>
>> On Thursday, May 25, 2023 at 3:59:44 PM UTC-4 jose riaño wrote:
>>
>>> me muestra este  error:
>>>
>>> May 25 14:55:37 raspberrypi weewx[1500]: restx: MQTT: Failed to connect
>>> to MQTT server (URL): timed out
>>> May 25 14:55:37 raspberrypi weewx[1500]: restx: MQTT: Failed to publish
>>> record 2023-05-25 14:55:00 -05 (1685044500): MQTT client not available
>>>
>> --
> 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/ff84bfd7-fdbe-48b9-922d-7ea9a59730d4n%40googlegroups.com
> 
> .
>


-- 
*Ing. JOSE JUAQUIN RIAÑO BECERRA.*
*10942678013153125203*

-- 
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/CAJ%2BHrV4kGuzqqP4uKL1jCBz%2Bt26K_CLDFJ6cy5unG1BGS4-tnA%40mail.gmail.com.

[weewx-user] Use old database in new weeWX install.

[Patrick Mendiuk]

I am trying to use an existing database with a new weeWX install.  I copied 
the existing database into /var/lib/weewx and restarted weeWX.  I then ran 
wee_debug --info and I see: 

Archive info
  Database name:weewx.sdb
  Table name:   archive
  Version   4.0
  Unit system:  1 (US)
  First good timestamp: 2023-06-07 13:00:00 PDT (1686168000)
  Last good timestamp:  2023-06-08 15:15:00 PDT (1686262500)
  Number of records:311
  weewx (weewx.conf) is set to use an archive interval of 300 seconds.
  The station hardware was not interrogated in determining archive interval.

On the original weeWX install I see this when I run wee_debug:

Archive info
  Database name:weewx.sdb
  Table name:   archive
  Version   2.0
  Unit system:  1 (US)
  First good timestamp: 1969-12-31 16:01:00 PST (60)
  Last good timestamp:  2023-06-08 15:37:00 PDT (1686263820)
  Number of records:2160656
  weewx (weewx.conf) is set to use an archive interval of 60 seconds.
  The station hardware was not interrogated in determining archive interval.

Is there a way I can convert the old database and have all the old history 
visible in the new weeWX install?


-- 
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/3486b127-ef6c-498c-80d1-686cbaad4ecfn%40googlegroups.com.

Re: [weewx-user] Use old database in new weeWX install.

[Tom Keffer]

Obviously, this is not the same database. Double check your steps. You can
also start weewxd, then look at the log. Perhaps it's not using the
database you think it is using?

Your original database has some bad timestamps, probably from a bad clock.
It's easy enough to get rid of them. See the wiki guide *Deleting unwanted
records
*
.



On Thu, Jun 8, 2023 at 3:43 PM Patrick Mendiuk  wrote:

> I am trying to use an existing database with a new weeWX install.  I
> copied the existing database into /var/lib/weewx and restarted weeWX.  I
> then ran wee_debug --info and I see:
>
> Archive info
>   Database name:weewx.sdb
>   Table name:   archive
>   Version   4.0
>   Unit system:  1 (US)
>   First good timestamp: 2023-06-07 13:00:00 PDT (1686168000)
>   Last good timestamp:  2023-06-08 15:15:00 PDT (1686262500)
>   Number of records:311
>   weewx (weewx.conf) is set to use an archive interval of 300 seconds.
>   The station hardware was not interrogated in determining archive
> interval.
>
> On the original weeWX install I see this when I run wee_debug:
>
> Archive info
>   Database name:weewx.sdb
>   Table name:   archive
>   Version   2.0
>   Unit system:  1 (US)
>   First good timestamp: 1969-12-31 16:01:00 PST (60)
>   Last good timestamp:  2023-06-08 15:37:00 PDT (1686263820)
>   Number of records:2160656
>   weewx (weewx.conf) is set to use an archive interval of 60 seconds.
>   The station hardware was not interrogated in determining archive
> interval.
>
> Is there a way I can convert the old database and have all the old history
> visible in the new weeWX install?
>
>
> --
> 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/3486b127-ef6c-498c-80d1-686cbaad4ecfn%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/CAPq0zEAnZ2zPJDR35NeF4G3%2BKW1yyyjibBFtM5KQKQ8mkD0a3w%40mail.gmail.com.

Re: [weewx-user] Use old database in new weeWX install.

[Patrick Mendiuk]

Thanks,
I had to change permissions on the file and directory.  I see the correct 
number of records now.  Now I need to figure out how to get the Belchertown 
skin records to use the entire database. 

On Thursday, June 8, 2023 at 4:09:02 PM UTC-7 Tom Keffer wrote:

> Obviously, this is not the same database. Double check your steps. You can 
> also start weewxd, then look at the log. Perhaps it's not using the 
> database you think it is using?
>
> Your original database has some bad timestamps, probably from a bad clock. 
> It's easy enough to get rid of them. See the wiki guide *Deleting 
> unwanted records 
> *
> .
>
>
>
> On Thu, Jun 8, 2023 at 3:43 PM Patrick Mendiuk  wrote:
>
>> I am trying to use an existing database with a new weeWX install.  I 
>> copied the existing database into /var/lib/weewx and restarted weeWX.  I 
>> then ran wee_debug --info and I see: 
>>
>> Archive info
>>   Database name:weewx.sdb
>>   Table name:   archive
>>   Version   4.0
>>   Unit system:  1 (US)
>>   First good timestamp: 2023-06-07 13:00:00 PDT (1686168000)
>>   Last good timestamp:  2023-06-08 15:15:00 PDT (1686262500)
>>   Number of records:311
>>   weewx (weewx.conf) is set to use an archive interval of 300 seconds.
>>   The station hardware was not interrogated in determining archive 
>> interval.
>>
>> On the original weeWX install I see this when I run wee_debug:
>>
>> Archive info
>>   Database name:weewx.sdb
>>   Table name:   archive
>>   Version   2.0
>>   Unit system:  1 (US)
>>   First good timestamp: 1969-12-31 16:01:00 PST (60)
>>   Last good timestamp:  2023-06-08 15:37:00 PDT (1686263820)
>>   Number of records:2160656
>>   weewx (weewx.conf) is set to use an archive interval of 60 seconds.
>>   The station hardware was not interrogated in determining archive 
>> interval.
>>
>> Is there a way I can convert the old database and have all the old 
>> history visible in the new weeWX install?
>>
>>
>> -- 
>> 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/3486b127-ef6c-498c-80d1-686cbaad4ecfn%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/6ce83702-41cf-4b92-b50d-07c1c9a59c1bn%40googlegroups.com.