[weewx-user] Re: Setting up rtldavis - where to get?

[storm...@gmail.com]

Take a look here:

https://github.com/lheijst/weewx-rtldavis

On Monday, August 22, 2022 at 11:42:38 PM UTC-4 f4n...@gmail.com wrote:

> Hi, does anyone have the installation files for rtldavis? It seems to be 
> archived (https://github.com/bemasher/rtldavis) and not longer available 
> in the repository if I try to install it with golang.
>
> Is anyone having long term experience and still running it? How stable is 
> the signal with a R820T/T2 chip? Does it get every 2.5s wind packet?
>
> Thanks for any advice,
> fankyy
>

-- 
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/95e5ed49-9007-4fc4-9985-da5cc2ba7a54n%40googlegroups.com.

[weewx-user] Setting up rtldavis - where to get?

[f4n...@gmail.com]

Hi, does anyone have the installation files for rtldavis? It seems to be 
archived (https://github.com/bemasher/rtldavis) and not longer available in 
the repository if I try to install it with golang.

Is anyone having long term experience and still running it? How stable is 
the signal with a R820T/T2 chip? Does it get every 2.5s wind packet?

Thanks for any advice,
fankyy

-- 
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/a3ae65c0-9ef8-4ab2-85bc-f8092cd20583n%40googlegroups.com.

Re: [weewx-user] Re: Power outage without RTC module

[Paul R Anderson]

fake-hwclock is just plain silly, by design it sets the OS time to a known
wrong state with the premise that it's a better than nothing choice.
Funny the further down the rabbit hole I go the more I see that I don't
like.  Such as debian setting NTPD or timesyncd to use debian.pool.ntp.org
ntp servers.
I certainly don't trust their list of rotating servers to all be accurate.
Always set systems to use known highly available servers I trust.
It's a jungle out there a minimum you need, Belt, Suspenders, and of
course a good quality Tin Foil Hat.

Paul









so strange that a simple thing lige starting

On Mon, Aug 22, 2022 at 5:28 PM vince  wrote:

> On Monday, August 22, 2022 at 10:12:59 AM UTC-7 pa...@pauland.net wrote:
>
>> Problem I've seen in the past was that on a Rasberry Pi installrd NTP ,
>> like I have on every system I've installed since 2004, yet after a power
>> outage weeWx started with a bad Os Time. Investigated and found that if I
>> removed purged fake-hwclock the expected wait for ntp worked. Now on some
>> systems I install ntp others I don't, if it's a PI remove fake-hwclock and
>> even if the machine has a RTC I enable systemd-time-wait-sync.
>>
>
> Yes - but be careful there.  Lots of os now have that blasted fake-hwclock
> kludge.
>
> I remove fake-hwclock and install/enable ntpd everywhere and it's nice and
> simple and reliable.  No need to edit anything in weewx at all, which is an
> added plus.
>
> The pi time-related details are in the FAQ
>  and wiki
> .
>
>
>
> --
> 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/221eacc6-2833-420d-ad00-0d6cb4d56c00n%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/CAOAVAec%2B%2BvLaDmERcpg%2Bum8EP0A5T1K1myebemUpgPn7KVvd0Q%40mail.gmail.com.

Re: [weewx-user] Re: Power outage without RTC module

[vince]

On Monday, August 22, 2022 at 10:12:59 AM UTC-7 pa...@pauland.net wrote:

> Problem I've seen in the past was that on a Rasberry Pi installrd NTP , 
> like I have on every system I've installed since 2004, yet after a power 
> outage weeWx started with a bad Os Time. Investigated and found that if I 
> removed purged fake-hwclock the expected wait for ntp worked. Now on some 
> systems I install ntp others I don't, if it's a PI remove fake-hwclock and 
> even if the machine has a RTC I enable systemd-time-wait-sync.
>

Yes - but be careful there.  Lots of os now have that blasted fake-hwclock 
kludge.

I remove fake-hwclock and install/enable ntpd everywhere and it's nice and 
simple and reliable.  No need to edit anything in weewx at all, which is an 
added plus.

The pi time-related details are in the FAQ 
 and wiki 
.



-- 
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/221eacc6-2833-420d-ad00-0d6cb4d56c00n%40googlegroups.com.

[weewx-user] Re: Losing Weewx DB data

[vince]

On Monday, August 22, 2022 at 11:05:13 AM UTC-7 rklud...@gmail.com wrote:

> So my question comes down to how do I backup and restore just the data? 
> Are there specific files or if there are a huge number of foreign keys is 
> it much more complicated...? Is it just the date pure database or is it 
> also related configuration or log files? I am currently using the default 
> database with no changes that comes with weewx... 
>
>
There are 'many' threads here about how to do this, along with pointers to 
scripts and best practices folks have used on their setups.  Do a little 
google searching of the group archives

Short answer:

   - you need your db
   - you need your weewx.conf
   - ideally you keep a record of which extensions/skins you installed (run 
   'wee_extension --list')
   - you can restore everything given the above


What I do here:

   - back up my databases (plural) nightly via cron
   - weekly copy the latest to Dropbox to have a copy offsite
   - I also have a full copy of /home/weewx in Dropbox for safekeeping
   - I rsync my public_html to my AWS Lightsail VM so that has my latest 
   public_html tree offsite there

-- 
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/9b5fb52e-71c9-4940-9b8b-6da76ccf84fbn%40googlegroups.com.

Re: [weewx-user] Re: problem with INDEX.HTML file version

[Doug Jenkins]

Can you confirm on the target of the website that seasons.css file is
there? Matt responded earlier that if you use the developer tools in your
browser, you will see that the seasons.css file is missing on your apache
web server directory.

Since you are FTP'ing the files, verify that you are grabbing all the files
from the source directory. It should include .js, .css, and .png, and .html
files.

DDJ

On Mon, Aug 22, 2022 at 3:34 PM Eric Gammeter  wrote:

> I have WEEWX running on the Rpi3; also on that Rpi is Apache web server.
> From there, all I know of is the WEEWX ftp process to upload files to my
> web site.  I access my web site file manager and see all (37?) files
> there.  So- the only mirroring I know of is WEEWX ftp'ing up to the web
> site.   I installed WEEWX using the DEB package.
>
> On Monday, August 22, 2022 at 11:16:27 AM UTC-4 matthew wall wrote:
>
>> the seasons.js and seasons.css files are not on your public-facing web
>> server.  so whatever mechanism you use to mirror your pi to n8aay.net is
>> not copying all of the files.
>>
>> use the 'developer tools' option in your web browser to diagnose this
>> kind of problem.  that will provide lots of information about which files
>> are loaded, which css attributes are applied (or not), javascript errors,
>> etc.
>>
>> On Monday, August 22, 2022 at 9:58:25 AM UTC-4 n8a...@gmail.com wrote:
>>
>>> Just to reiterate my situation:  When I view my local Rpi ip address:
>>> 192.168.1.38/weewx) I see the full graphic-laden screen.  That is
>>> good!  When I view my internet source (https://www.n8aay.net) I see
>>> only the text-only version.
>>>
>>
>> [image: no-js-css.png]
>>
> --
> 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/c8a13bf2-af31-486e-8382-1cc0e0b922a3n%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/CACC0i0yDf%3DQjn27qRHJ6%3D%2BqEAsjh8wBPRcvGRnosdPe6M3BZLA%40mail.gmail.com.

Re: [weewx-user] Re: problem with INDEX.HTML file version

[Eric Gammeter]

I have WEEWX running on the Rpi3; also on that Rpi is Apache web server.  
>From there, all I know of is the WEEWX ftp process to upload files to my 
web site.  I access my web site file manager and see all (37?) files 
there.  So- the only mirroring I know of is WEEWX ftp'ing up to the web 
site.   I installed WEEWX using the DEB package. 

On Monday, August 22, 2022 at 11:16:27 AM UTC-4 matthew wall wrote:

> the seasons.js and seasons.css files are not on your public-facing web 
> server.  so whatever mechanism you use to mirror your pi to n8aay.net is 
> not copying all of the files.
>
> use the 'developer tools' option in your web browser to diagnose this kind 
> of problem.  that will provide lots of information about which files are 
> loaded, which css attributes are applied (or not), javascript errors, etc.
>
> On Monday, August 22, 2022 at 9:58:25 AM UTC-4 n8a...@gmail.com wrote:
>
>> Just to reiterate my situation:  When I view my local Rpi ip address: 
>> 192.168.1.38/weewx) I see the full graphic-laden screen.  That is good!  
>> When I view my internet source (https://www.n8aay.net) I see only the 
>> text-only version. 
>>
>
> [image: no-js-css.png] 
>

-- 
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/c8a13bf2-af31-486e-8382-1cc0e0b922a3n%40googlegroups.com.

Re: [weewx-user] Losing Weewx DB data

['Rainer Lang' via weewx-user]

Many ways lead to Rome ...

I'm running two weewx installations on two separate RPi4Bs in parallel. 
They are mirrors.
If one has to go down or just goes down, I can later on copy the 
database over from the still running installation.
Each installation is backed up to an external HDD every five minutes 
after the archiving interval. Thi minimizes the potential data loss.
Every two days a housekeeping script will only keep the midnight backups 
and delete the others to free space on the disk.

This setup/strategy has kept me safe through all incidents so far.
My weather consoles, the WiFi router and the RPis are protected by a UPS 
(uninterrupted power supply).

Like this Blackouts less than one hour do not impact my weather hardware.

Am 22.08.2022 um 20:05 schrieb Kruse Ludington:
From time to time when I back up my weewx setup I then have to later 
restore it when things go south. (This has happened from time to time 
as all this is running on a Raspberry pi which also has a lot of other 
things running in containers such as home assistant etc.)


When this happens of course I lose the weewx data between the date of 
the backup and the date of the restore.


Therefore I'd like to backup the data on a daily basis such that when 
I restore the entire system from an old backup, I can as a last step, 
then overlay that with the database backup made within the last 24 
hours, to minimize the data lost.


So my question comes down to how do I backup and restore just the 
data? Are there specific files or if there are a huge number of 
foreign keys is it much more complicated...? Is it just the date pure 
database or is it also related configuration or log files? I am 
currently using the default database with no changes that comes with 
weewx...


Thank you for your help!

Best Regards,

-R. Kruse Ludington

📱(M): +1.201.925.4410
📞(O): +1.862.308.7040
📞(H): +1.201.857.8307
📠(F): +1.201.857.7188
Weather & Forecast 


--
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/182c6babc98.29af.c5c13ad976ec84a62e2892bf98a0657b%40gmail.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/dad91d81-ba94-4f02-7be1-3d3877371119%40gmail.com.

[weewx-user] Losing Weewx DB data

[Kruse Ludington]

From time to time when I back up my weewx setup I then have to later 
restore it when things go south. (This has happened from time to time as 
all this is running on a Raspberry pi which also has a lot of other things 
running in containers such as home assistant etc.)


When this happens of course I lose the weewx data between the date of the 
backup and the date of the restore.


Therefore I'd like to backup the data on a daily basis such that when I 
restore the entire system from an old backup, I can as a last step, then 
overlay that with the database backup made within the last 24 hours, to 
minimize the data lost.


So my question comes down to how do I backup and restore just the data? Are 
there specific files or if there are a huge number of foreign keys is it 
much more complicated...? Is it just the date pure database or is it also 
related configuration or log files? I am currently using the default 
database with no changes that comes with weewx...


Thank you for your help!

Best Regards,

-R. Kruse Ludington

📱(M): +1.201.925.4410
📞(O): +1.862.308.7040
📞(H): +1.201.857.8307
📠(F): +1.201.857.7188
Weather & Forecast

--
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/182c6babc98.29af.c5c13ad976ec84a62e2892bf98a0657b%40gmail.com.

Re: [weewx-user] Re: Power outage without RTC module

[Paul R Anderson]

Problem I've seen in the past was that on a Rasberry Pi installrd NTP ,
like I have on every system I've installed since 2004, yet after a power
outage weeWx started with a bad Os Time. Investigated and found that if I
removed purged fake-hwclock the expected wait for ntp worked. Now on some
systems I install ntp others I don't, if it's a PI remove fake-hwclock and
even if the machine has a RTC I enable systemd-time-wait-sync.
Also change weewx.service to:

Requires=systemd-time-wait-sync.service
After=systemd-time-wait-sync.service

Many ways to get there

On Mon, Aug 22, 2022 at 12:02 PM vince  wrote:

> Easier yet - just install ntp and use that instead, and systemd won't do
> anything time related.
>
> FWIW - I've found ntp handles drift better by far, and I've been using it
> happily everywhere for well over 20 years across all unixy platforms of all
> vintages so I know what I'm getting.  You never know what systemd is going
> to do or change os to os and version to version.  You gotta fight the
> systemd borg whenever possible :-)
>
> Here's the logs from a pi4 using ntp that I am running the simulator on
> which was powered down overnight.  Note how the system boots up initial
> with a Mar-26 date and weewx waits gracefully for the system to get the
> correct date+time before proceeding.  You'll see the syslog show the system
> switch to today's date when ntpd updates things and weewx starts up pretty
> much immediately after.
>
> Mar 26 22:42:16 pi4 kernel: [0.00] Booting Linux on physical CPU
> 0x0
> Mar 26 22:42:16 pi4 kernel: [0.00] Linux version 5.15.56-v7l+
> (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1)
> 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1575 SMP Fri Jul 22 20:29:46
> BST 2022
> Mar 26 22:42:16 pi4 kernel: [0.00] CPU: ARMv7 Processor [410fd083]
> revision 3 (ARMv7), cr=30c5383d
> Mar 26 22:42:16 pi4 kernel: [0.00] CPU: div instructions
> available: patching division code
> Mar 26 22:42:16 pi4 kernel: [0.00] CPU: PIPT / VIPT nonaliasing
> data cache, PIPT instruction cache
> Mar 26 22:42:16 pi4 kernel: [0.00] OF: fdt: Machine model:
> Raspberry Pi 4 Model B Rev 1.1
> [...]
> Mar 26 22:42:16 pi4 kernel: [7.491386] uart-pl011 fe201000.serial: no
> DMA platform data
> Mar 26 22:42:16 pi4 kernel: [7.806915] Adding 102396k swap on
> /var/swap.  Priority:-2 extents:1 across:102396k SSFS
> Mar 26 22:42:17 pi4 kernel: [8.223906] brcmfmac:
> brcmf_cfg80211_set_power_mgmt: power save enabled
> Mar 26 22:42:17 pi4 kernel: [8.590674] bcmgenet fd58.ethernet:
> configuring instance for external RGMII (RX delay)
> Mar 26 22:42:17 pi4 kernel: [8.592910] bcmgenet fd58.ethernet
> eth0: Link is Down
>
>
>
>
>
>
> *Mar 26 22:42:17 pi4 weewx[415] INFO __main__: Initializing weewx version
> 4.8.0Mar 26 22:42:17 pi4 weewx[415] INFO __main__: Using Python 3.9.2
> (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]Mar 26 22:42:17
> pi4 weewx[415] INFO __main__: Platform
> Linux-5.15.56-v7l+-armv7l-with-glibc2.31Mar 26 22:42:17 pi4 weewx[415] INFO
> __main__: Locale is 'en_US.UTF-8'Mar 26 22:42:17 pi4 weewx[415] INFO
> __main__: Using configuration file /home/weewx/weewx.confMar 26 22:42:17
> pi4 weewx[415] INFO __main__: Debug is 0Mar 26 22:42:17 pi4 weewx[415] INFO
> __main__: Waiting for sane time. Current time is 2022-03-26 22:42:17 PDT
> (1648359737)*
> Mar 26 22:42:23 pi4 kernel: [   14.316585] IPv6: ADDRCONF(NETDEV_CHANGE):
> wlan0: link becomes ready
> Mar 26 22:42:23 pi4 kernel: [   14.383527] Bluetooth: Core ver 2.22
> Mar 26 22:42:23 pi4 kernel: [   14.383597] NET: Registered PF_BLUETOOTH
> protocol family
> [...]
> Mar 26 22:42:23 pi4 kernel: [   14.700205] Bluetooth: BNEP socket layer
> initialized
> Mar 26 22:42:23 pi4 kernel: [   14.714801] NET: Registered PF_ALG protocol
> family
> Mar 26 22:42:23 pi4 kernel: [   14.735599] cryptd: max_cpu_qlen set to 1000
>
>
>
> *Aug 22 08:34:37 pi4 kernel: [   31.832505] cam-dummy-reg: disablingAug 22
> 08:34:37 pi4 weewx[415] INFO weewx.engine: Loading station type Simulator
> (weewx.drivers.simulator)Aug 22 08:34:37 pi4 weewx[415] INFO
> user.MQTTSubscribe: (Service) Version is 2.1.0*Aug 22 08:34:37 pi4
> weewx[415] INFO user.MQTTSubscribe: (Service) Log level: 0
> Aug 22 08:34:37 pi4 weewx[415] INFO user.MQTTSubscribe: (Service) Log
> debug setting: 0
> Aug 22 08:34:37 pi4 weewx[415] INFO user.MQTTSubscribe: (Service) Log
> console: False
> Aug 22 08:34:37 pi4 weewx[415] INFO user.MQTTSubscribe: (Service) Log
> file: None
>
>
> --
> 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/0d091386-1e68-4f64-9c7b-44e67de544afn%40googlegroups.com
> 

Re: [weewx-user] Re: Power outage without RTC module

[vince]

Easier yet - just install ntp and use that instead, and systemd won't do 
anything time related. 

FWIW - I've found ntp handles drift better by far, and I've been using it 
happily everywhere for well over 20 years across all unixy platforms of all 
vintages so I know what I'm getting.  You never know what systemd is going 
to do or change os to os and version to version.  You gotta fight the 
systemd borg whenever possible :-)

Here's the logs from a pi4 using ntp that I am running the simulator on 
which was powered down overnight.  Note how the system boots up initial 
with a Mar-26 date and weewx waits gracefully for the system to get the 
correct date+time before proceeding.  You'll see the syslog show the system 
switch to today's date when ntpd updates things and weewx starts up pretty 
much immediately after.

Mar 26 22:42:16 pi4 kernel: [0.00] Booting Linux on physical CPU 0x0
Mar 26 22:42:16 pi4 kernel: [0.00] Linux version 5.15.56-v7l+ 
(dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 
8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1575 SMP Fri Jul 22 20:29:46 
BST 2022
Mar 26 22:42:16 pi4 kernel: [0.00] CPU: ARMv7 Processor [410fd083] 
revision 3 (ARMv7), cr=30c5383d
Mar 26 22:42:16 pi4 kernel: [0.00] CPU: div instructions available: 
patching division code
Mar 26 22:42:16 pi4 kernel: [0.00] CPU: PIPT / VIPT nonaliasing 
data cache, PIPT instruction cache
Mar 26 22:42:16 pi4 kernel: [0.00] OF: fdt: Machine model: 
Raspberry Pi 4 Model B Rev 1.1
[...]
Mar 26 22:42:16 pi4 kernel: [7.491386] uart-pl011 fe201000.serial: no 
DMA platform data
Mar 26 22:42:16 pi4 kernel: [7.806915] Adding 102396k swap on 
/var/swap.  Priority:-2 extents:1 across:102396k SSFS
Mar 26 22:42:17 pi4 kernel: [8.223906] brcmfmac: 
brcmf_cfg80211_set_power_mgmt: power save enabled
Mar 26 22:42:17 pi4 kernel: [8.590674] bcmgenet fd58.ethernet: 
configuring instance for external RGMII (RX delay)
Mar 26 22:42:17 pi4 kernel: [8.592910] bcmgenet fd58.ethernet eth0: 
Link is Down






*Mar 26 22:42:17 pi4 weewx[415] INFO __main__: Initializing weewx version 
4.8.0Mar 26 22:42:17 pi4 weewx[415] INFO __main__: Using Python 3.9.2 
(default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]Mar 26 22:42:17 
pi4 weewx[415] INFO __main__: Platform 
Linux-5.15.56-v7l+-armv7l-with-glibc2.31Mar 26 22:42:17 pi4 weewx[415] INFO 
__main__: Locale is 'en_US.UTF-8'Mar 26 22:42:17 pi4 weewx[415] INFO 
__main__: Using configuration file /home/weewx/weewx.confMar 26 22:42:17 
pi4 weewx[415] INFO __main__: Debug is 0Mar 26 22:42:17 pi4 weewx[415] INFO 
__main__: Waiting for sane time. Current time is 2022-03-26 22:42:17 PDT 
(1648359737)*
Mar 26 22:42:23 pi4 kernel: [   14.316585] IPv6: ADDRCONF(NETDEV_CHANGE): 
wlan0: link becomes ready
Mar 26 22:42:23 pi4 kernel: [   14.383527] Bluetooth: Core ver 2.22
Mar 26 22:42:23 pi4 kernel: [   14.383597] NET: Registered PF_BLUETOOTH 
protocol family
[...]
Mar 26 22:42:23 pi4 kernel: [   14.700205] Bluetooth: BNEP socket layer 
initialized
Mar 26 22:42:23 pi4 kernel: [   14.714801] NET: Registered PF_ALG protocol 
family
Mar 26 22:42:23 pi4 kernel: [   14.735599] cryptd: max_cpu_qlen set to 1000



*Aug 22 08:34:37 pi4 kernel: [   31.832505] cam-dummy-reg: disablingAug 22 
08:34:37 pi4 weewx[415] INFO weewx.engine: Loading station type Simulator 
(weewx.drivers.simulator)Aug 22 08:34:37 pi4 weewx[415] INFO 
user.MQTTSubscribe: (Service) Version is 2.1.0*Aug 22 08:34:37 pi4 
weewx[415] INFO user.MQTTSubscribe: (Service) Log level: 0
Aug 22 08:34:37 pi4 weewx[415] INFO user.MQTTSubscribe: (Service) Log debug 
setting: 0
Aug 22 08:34:37 pi4 weewx[415] INFO user.MQTTSubscribe: (Service) Log 
console: False
Aug 22 08:34:37 pi4 weewx[415] INFO user.MQTTSubscribe: (Service) Log file: 
None


-- 
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/0d091386-1e68-4f64-9c7b-44e67de544afn%40googlegroups.com.

Re: [weewx-user] Re: problem with INDEX.HTML file version

[matthew wall]

the seasons.js and seasons.css files are not on your public-facing web 
server.  so whatever mechanism you use to mirror your pi to n8aay.net is 
not copying all of the files.

use the 'developer tools' option in your web browser to diagnose this kind 
of problem.  that will provide lots of information about which files are 
loaded, which css attributes are applied (or not), javascript errors, etc.

On Monday, August 22, 2022 at 9:58:25 AM UTC-4 n8a...@gmail.com wrote:

> Just to reiterate my situation:  When I view my local Rpi ip address: 
> 192.168.1.38/weewx) I see the full graphic-laden screen.  That is good!  
> When I view my internet source (https://www.n8aay.net) I see only the 
> text-only version. 
>

[image: no-js-css.png] 

-- 
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/9e9dce55-b205-41df-a035-6035e4d664c1n%40googlegroups.com.

Re: [weewx-user] Re: problem with INDEX.HTML file version

[Eric Gammeter]

Well-  I admit I am not that proficient with linux- enough for me to check 
permissions on things (web server)-  I have now cleared my browser 
(Firefox) cache: no joy.  I have had WEEWX up and running for a number of 
years now- and I have managed to upgrade it from 1 version to the next 
version.  Perhaps there is a way I could re-install WEEWX?  As long as I 
maintain my WEEWX.SDB database file!  I want to retain all my WX history.  
Just to reiterate my situation:  When I view my local Rpi ip address: 
192.168.1.38/weewx) I see the full graphic-laden screen.  That is good!  
When I view my internet source (https://www.n8aay.net) I see only the 
text-only version.  I can tell that this is a "situation" with the 
INDEX.HTML file.  In both situations the files are updated with the correct 
current time/date.  I have tried this on 2 different PC's here at home on 
my LAN- with the same result.  I also tried it on my smart phone browser 
when I was away from my home LAN: no joy there.  
The only 'thing' I have done recently is to upgrade from the previous WEEWX 
version- to the newest version (4.8.0); and even after I upgraded to 4.8.0 
it was working just fine; nominally.  I appreciate your assistance.  
 /EricG 

On Sunday, August 21, 2022 at 1:30:04 PM UTC-4 do...@dougjenkins.com wrote:

> The other thing to check is make sure you have the permissions set 
> correctly for your web server account to access the subdirectories that are 
> published. One thing I do is make sure the target public_html directly has 
> read/write permissions for the weewx account and read permissions that are 
> inheritable by the webserver account.
>
> Once that is set, I clear the public_html directly completely (all files 
> and folders) and restart weewx. it will recreate everything (including the 
> folders) with the correct permissions.
>
>
>
> On Sun, Aug 21, 2022 at 12:17 PM Eric Gammeter  wrote:
>
>> Aug 21 12:00:55 raspberrypi3WEEWX weewx[606] DEBUG weeutil.ftpupload: 56 
>> ./index.html 
>> 522bce22f22f09c2ee428a8373f9f8d72f490b88a1463d82971d8ff3630fa1d2
>> Aug 21 12:00:55 raspberrypi3WEEWX weewx[606] DEBUG weeutil.ftpupload: 
>> Uploaded file /var/www/html/weewx/index.html to /weather/4.8/index.html
>>
>>  
>>
>> [[SeasonsReport]]
>>
>> # The SeasonsReport uses the 'Seasons' skin, which contains the
>>
>> # images, templates and plots for the report.
>>
>> skin = Seasons
>>
>> enable = true
>>
>>  
>>
>> [[SmartphoneReport]]
>>
>> # The SmartphoneReport uses the 'Smartphone' skin, and the 
>> images and
>>
>> # files are placed in a dedicated subdirectory.
>>
>> skin = Smartphone
>>
>> enable = true
>>
>> HTML_ROOT = /var/www/html/weewx/smartphone
>>
>>  
>>
>> [[MobileReport]]
>>
>> # The MobileReport uses the 'Mobile' skin, and the images and 
>> files
>>
>> # are placed in a dedicated subdirectory.
>>
>> skin = Mobile
>>
>> enable = true
>>
>> HTML_ROOT = /var/www/html/weewx/mobile
>>
>>  
>>
>> [[StandardReport]]
>>
>> # This is the old "Standard" skin. By default, it is not enabled.
>>
>> skin = Standard
>>
>> enable = false
>>
>>  
>>
>>
>> Station uses VANTAGE weather station.  
>>
>>
>> Version:  4.8.0
>>
>> On Sunday, August 21, 2022 at 11:51:22 AM UTC-4 Eric Gammeter wrote:
>>
>>> both of the INDEX.HTML files referred to above are updating every 30 
>>> minutes.
>>>
>>> On Sunday, August 21, 2022 at 11:49:11 AM UTC-4 Eric Gammeter wrote:
>>>
 Seemingly out of the blue I have a problem with the INDEX.HTML.  IE:  
 When I look at my Rpi (192.168.1.38/weewx) in a browser locally-  the 
 correct report formatting is there and it looks fine (has all it's 
 graphs); 
 however when I go to the web address (http://www.n8aay.net) the index 
 file that I see there is only "formatted for RSS" (that is:  no graphics, 
 only text).  I did recently upgrade to v 4.8.0  
 ?   /Thanks, EG

>>> -- 
>>
> 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/0c23f1d6-4c73-4dd8-8f01-d1fe1705d1e0n%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/572c91b6-d5f5-40f6-8e32-2e7033adcaf4n%40googlegroups.com.

Re: [weewx-user] Re: Power outage without RTC module

[Paul R Anderson]

By the way there is an easy solution to stop this whole calamity of events
from occurring.
In the case that for some reason you can not install a RTC, which is
very desirable, and highly recommended.
You can enable the systemd-time-wait-sync service on your system.
sudo systemctl status systemd-time-wait-sync
sudo systemctl start systemd-time-wait-sync

The systemd service for weewx located at  /util/systemd/weewx.service
Has this in it:
Requires=time-sync.target
After=time-sync.target
The problem is that time-sync.target starts thes ynchronization process ,
but doesn't wait for it to complete, so WeeWx starts before the OS
clock gets synchronized .
Once you enable systemd-time-wait-sync Service
systemd-time-wait-sync will wait infinitely till it can synchronize time.
Now services that depend on time-sync target , such as WeeWx ,will not
start until the OS time is synchronized.

Which all means that now when the power comes back on the system starts, It
tries to synchronize system OS time,
It might need to wait for a Wi-Fi connection, a router to start, an
internet connection or something else.
Until the OS time get's synchronized WeeWx won't start.
Meanwhile your davis logger , if running on batteries during the whole
power outage , will continue to log data.
Once WeeWx starts it will get all the data from the logger for the period
of the power outage to present .
All should be well and looking at the WeeWx data, you would never know
there was a power outage.

Hope this helps, and is't to confusing to follow.

Paul







On Mon, Aug 22, 2022 at 8:29 AM Paul R Anderson  wrote:

> For hardware that supports WeeWx can set the onboard clock of the hardware.
> In your case the davis data logger supports setting of its onboard clock.
>
> This is controlled in the  [StdTimeSynch] section of weewx.config
> I believe WeeWx ships with this as default:
>
> ##
>
> #   For hardware that supports it, this section controls how often the
> #   onboard clock gets updated.
>
> [StdTimeSynch]
>
> # How often to check the weather station clock for drift (in seconds)
> clock_check = 14400
>
> # How much it can drift before we will correct it (in seconds)
> max_drift = 5
>
>
> ##
> So unless you changed it most likely WeeWx set the davis datalogger
> onboard clock, while your OS was running with the incorrect time.
>
> On Mon, Aug 22, 2022 at 6:15 AM Andrea Di Saverio <
> disaverio.and...@gmail.com> wrote:
>
>> I was able to restore all the data, doing as I planned: (i) the records
>> collected during the power outage have been recovered from davis data
>> logger, (ii) the subsequent records were already in the database but with
>> wrong dateTime, so I just fixed its value shifting it 118m in the future.
>> Then, as solid definitive solution for the future, I have also bought an
>> RTC module for the rasp.
>>
>> What is still puzzling me, is how is possible that the same wrong data
>> (the wrong time value) was in the davis datalogger as well, for all the
>> records in the period from after the power outage to the restoration of the
>> correct time.
>>
>>
>> Il giorno domenica 21 agosto 2022 alle 19:50:23 UTC+2 MikeQ ha scritto:
>>
>>> I have had a similar issue twice but not since January 2021.  I have my
>>> Davis console on wall power plus batteries, assuming the batteries would
>>> work like a UPS but that might not be reliable.
>>>
>>> Look at the weewx wiki:
>>>
>>> https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#weewx-generates-html-pages-but-it-does-not-update-them
>>>
>>> I shut down weewx and inspected my database using DB Browser for SQLite
>>> on a desktop and there are no issues in the DB so clock slew was not my
>>> issue.
>>>
>>> If I follow the instructions in 'Corrupt station memory' using debug
>>> mode i see exactly the same results as the wiki shows with the DMPACT
>>> command indicating the download is complete while I still have 197 pages in
>>> the datalogger.
>>>
>>> Rebooting the console did not work for me and I had to use the dump &
>>> clear commands.  That resulted in the loss of records for a 25 minute
>>> period the last time around.
>>>
>>>
>>>
>>> On Saturday, August 20, 2022 at 4:46:11 PM UTC-6 disaveri...@gmail.com
>>> wrote:
>>>
 Today I had a power outage, from the 06:01 CEST to the 07:51 CEST.
 So the last record added by weewx before the outage was at 06:01 CEST.
 From logs (reporting here only last two lines):

 pi@raspberrypi:~ $ journalctl -b -1
 Aug 20 06:01:14 raspberrypi python3[16243]: weewx[16243] INFO
 weewx.manager: Added record 2022-08-20 06:01:00 CEST (1660968060) to
 database 'weewx.sdb'
 Aug 20 06:01:14 raspberrypi python3[16243]: weewx[16243] INFO
 weewx.manager: Added record 2022-08-20 06:01:00 CEST (1660968060) to daily
 

Re: [weewx-user] Re: Power outage without RTC module

[Paul R Anderson]

For hardware that supports WeeWx can set the onboard clock of the hardware.
In your case the davis data logger supports setting of its onboard clock.

This is controlled in the  [StdTimeSynch] section of weewx.config
I believe WeeWx ships with this as default:
##

#   For hardware that supports it, this section controls how often the
#   onboard clock gets updated.

[StdTimeSynch]

# How often to check the weather station clock for drift (in seconds)
clock_check = 14400

# How much it can drift before we will correct it (in seconds)
max_drift = 5

##
So unless you changed it most likely WeeWx set the davis datalogger
onboard clock, while your OS was running with the incorrect time.

On Mon, Aug 22, 2022 at 6:15 AM Andrea Di Saverio <
disaverio.and...@gmail.com> wrote:

> I was able to restore all the data, doing as I planned: (i) the records
> collected during the power outage have been recovered from davis data
> logger, (ii) the subsequent records were already in the database but with
> wrong dateTime, so I just fixed its value shifting it 118m in the future.
> Then, as solid definitive solution for the future, I have also bought an
> RTC module for the rasp.
>
> What is still puzzling me, is how is possible that the same wrong data
> (the wrong time value) was in the davis datalogger as well, for all the
> records in the period from after the power outage to the restoration of the
> correct time.
>
>
> Il giorno domenica 21 agosto 2022 alle 19:50:23 UTC+2 MikeQ ha scritto:
>
>> I have had a similar issue twice but not since January 2021.  I have my
>> Davis console on wall power plus batteries, assuming the batteries would
>> work like a UPS but that might not be reliable.
>>
>> Look at the weewx wiki:
>>
>> https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#weewx-generates-html-pages-but-it-does-not-update-them
>>
>> I shut down weewx and inspected my database using DB Browser for SQLite
>> on a desktop and there are no issues in the DB so clock slew was not my
>> issue.
>>
>> If I follow the instructions in 'Corrupt station memory' using debug mode
>> i see exactly the same results as the wiki shows with the DMPACT command
>> indicating the download is complete while I still have 197 pages in the
>> datalogger.
>>
>> Rebooting the console did not work for me and I had to use the dump &
>> clear commands.  That resulted in the loss of records for a 25 minute
>> period the last time around.
>>
>>
>>
>> On Saturday, August 20, 2022 at 4:46:11 PM UTC-6 disaveri...@gmail.com
>> wrote:
>>
>>> Today I had a power outage, from the 06:01 CEST to the 07:51 CEST.
>>> So the last record added by weewx before the outage was at 06:01 CEST.
>>> From logs (reporting here only last two lines):
>>>
>>> pi@raspberrypi:~ $ journalctl -b -1
>>> Aug 20 06:01:14 raspberrypi python3[16243]: weewx[16243] INFO
>>> weewx.manager: Added record 2022-08-20 06:01:00 CEST (1660968060) to
>>> database 'weewx.sdb'
>>> Aug 20 06:01:14 raspberrypi python3[16243]: weewx[16243] INFO
>>> weewx.manager: Added record 2022-08-20 06:01:00 CEST (1660968060) to daily
>>> summary in 'weewx.s>
>>>
>>> When the power came back, the wifi was not available, so the raspberry's
>>> time (I have no RTC module) was automatically set to a previously recorded
>>> timestamp: 05:53:32 CEST (118 mins before real time).
>>> So when weewx re-started recording, it discarded first 8 samples and
>>> then started going. From logs:
>>>
>>> Aug 20 06:01:19 raspberrypi python3[600]: weewx[600] ERROR
>>> weewx.manager: Unable to add record 2022-08-20 05:54:00 CEST (1660967640)
>>> to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
>>> Aug 20 06:01:19 raspberrypi python3[600]: weewx[600] ERROR
>>> weewx.manager: Unable to add record 2022-08-20 05:55:00 CEST (1660967700)
>>> to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
>>> Aug 20 06:01:19 raspberrypi python3[600]: weewx[600] ERROR
>>> weewx.manager: Unable to add record 2022-08-20 05:56:00 CEST (1660967760)
>>> to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
>>> Aug 20 06:01:19 raspberrypi python3[600]: weewx[600] ERROR
>>> weewx.manager: Unable to add record 2022-08-20 05:57:00 CEST (1660967820)
>>> to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
>>> Aug 20 06:01:19 raspberrypi python3[600]: weewx[600] ERROR
>>> weewx.manager: Unable to add record 2022-08-20 05:58:00 CEST (1660967880)
>>> to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
>>> Aug 20 06:01:19 raspberrypi python3[600]: weewx[600] ERROR
>>> weewx.manager: Unable to add record 2022-08-20 05:59:00 CEST (1660967940)
>>> to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
>>> Aug 20 06:01:19 raspberrypi python3[600]: w

[weewx-user] Re: Power outage without RTC module

[Andrea Di Saverio]

I was able to restore all the data, doing as I planned: (i) the records 
collected during the power outage have been recovered from davis data 
logger, (ii) the subsequent records were already in the database but with 
wrong dateTime, so I just fixed its value shifting it 118m in the future.
Then, as solid definitive solution for the future, I have also bought an 
RTC module for the rasp.

What is still puzzling me, is how is possible that the same wrong data (the 
wrong time value) was in the davis datalogger as well, for all the records 
in the period from after the power outage to the restoration of the correct 
time.


Il giorno domenica 21 agosto 2022 alle 19:50:23 UTC+2 MikeQ ha scritto:

> I have had a similar issue twice but not since January 2021.  I have my 
> Davis console on wall power plus batteries, assuming the batteries would 
> work like a UPS but that might not be reliable.
>
> Look at the weewx wiki:
>
> https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#weewx-generates-html-pages-but-it-does-not-update-them
>
> I shut down weewx and inspected my database using DB Browser for SQLite on 
> a desktop and there are no issues in the DB so clock slew was not my issue.
>
> If I follow the instructions in 'Corrupt station memory' using debug mode 
> i see exactly the same results as the wiki shows with the DMPACT command 
> indicating the download is complete while I still have 197 pages in the 
> datalogger.
>
> Rebooting the console did not work for me and I had to use the dump & 
> clear commands.  That resulted in the loss of records for a 25 minute 
> period the last time around. 
>
>
>
> On Saturday, August 20, 2022 at 4:46:11 PM UTC-6 disaveri...@gmail.com 
> wrote:
>
>> Today I had a power outage, from the 06:01 CEST to the 07:51 CEST.
>> So the last record added by weewx before the outage was at 06:01 CEST. 
>> From logs (reporting here only last two lines):
>>
>> pi@raspberrypi:~ $ journalctl -b -1
>> Aug 20 06:01:14 raspberrypi python3[16243]: weewx[16243] INFO 
>> weewx.manager: Added record 2022-08-20 06:01:00 CEST (1660968060) to 
>> database 'weewx.sdb'
>> Aug 20 06:01:14 raspberrypi python3[16243]: weewx[16243] INFO 
>> weewx.manager: Added record 2022-08-20 06:01:00 CEST (1660968060) to daily 
>> summary in 'weewx.s>
>>
>> When the power came back, the wifi was not available, so the raspberry's 
>> time (I have no RTC module) was automatically set to a previously recorded 
>> timestamp: 05:53:32 CEST (118 mins before real time).
>> So when weewx re-started recording, it discarded first 8 samples and then 
>> started going. From logs:
>>
>> Aug 20 06:01:19 raspberrypi python3[600]: weewx[600] ERROR 
>> weewx.manager: Unable to add record 2022-08-20 05:54:00 CEST (1660967640) 
>> to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
>> Aug 20 06:01:19 raspberrypi python3[600]: weewx[600] ERROR 
>> weewx.manager: Unable to add record 2022-08-20 05:55:00 CEST (1660967700) 
>> to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
>> Aug 20 06:01:19 raspberrypi python3[600]: weewx[600] ERROR 
>> weewx.manager: Unable to add record 2022-08-20 05:56:00 CEST (1660967760) 
>> to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
>> Aug 20 06:01:19 raspberrypi python3[600]: weewx[600] ERROR 
>> weewx.manager: Unable to add record 2022-08-20 05:57:00 CEST (1660967820) 
>> to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
>> Aug 20 06:01:19 raspberrypi python3[600]: weewx[600] ERROR 
>> weewx.manager: Unable to add record 2022-08-20 05:58:00 CEST (1660967880) 
>> to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
>> Aug 20 06:01:19 raspberrypi python3[600]: weewx[600] ERROR 
>> weewx.manager: Unable to add record 2022-08-20 05:59:00 CEST (1660967940) 
>> to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
>> Aug 20 06:01:19 raspberrypi python3[600]: weewx[600] ERROR 
>> weewx.manager: Unable to add record 2022-08-20 06:00:00 CEST (1660968000) 
>> to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
>> Aug 20 06:01:19 raspberrypi python3[600]: weewx[600] ERROR 
>> weewx.manager: Unable to add record 2022-08-20 06:01:00 CEST (1660968060) 
>> to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
>> Aug 20 06:02:16 raspberrypi python3[600]: weewx[600] INFO 
>> weewx.manager: Added record 2022-08-20 06:02:00 CEST (1660968120) to 
>> database 'weewx.sdb'
>> Aug 20 06:02:16 raspberrypi python3[600]: weewx[600] INFO 
>> weewx.manager: Added record 2022-08-20 06:02:00 CEST (1660968120) to daily 
>> summary in 'weewx.sdb'
>>
>> But, and this is a bit surprising, it also discarded records collected in 
>> the davis datalogger.
>> They are 110 lines, from 1660968120 (06:02:00 CEST) and 1660974660 
>> (07:51:00 CEST) (The power outage didn't affect the davis station: it is 
>> battery powered).
>> From log