Re: [weewx-user] Re: New Install of WeeWx on Raspbian Bookworm - No module named 'sortedcontainers'

['John Kline' via weewx-user]

sudo apt install python3-sortedcollections is the instruction I give for WeeWX 4.  Do I need to give that instruction for package installs of WeeWX 5?On Jul 29, 2024, at 10:49 AM, Tom Keffer  wrote:Thanks, John. I figured it was something like that.Marty: you can probably fix by installing using apt:sudo apt install python3-sortedcollectionsRich: the OP used a package install, not pip install, so the best way to fix is a package install of sortedcollections.-tkOn Mon, Jul 29, 2024 at 8:04 AM 'John Kline' via weewx-user <weewx-user@googlegroups.com> wrote:I looks like he is using an extension of mine (weewx-loopdata) that requires sorted containers since weewx-loopdata v3.0.  The README states that sortedcontainers must be installed and the weewx 5 install instructions, step 1, states:Activate the virtual environment (actual syntax varies by type of WeeWX install):/home/weewx/weewx-venv/bin/activateI’m asssuming weewx 5.  If it is weewx 4, follow the WeeWX instructions for weewx 4 installs.On Jul 29, 2024, at 9:51 AM, bell...@gmail.com <bellri...@gmail.com> wrote:This is ‘due’ to pep 668 and a ‘push’ for users to use virtual environments. It is warning the person installing the python module, sortedcontainers, that they  are installing into an ‘global’ (externally-managed-environment) location. There are a few ways to solve this.Create a virtual environment, activate it, and install the module. Since WeeWX was a package install, this is not reasonable.As the message states, override the warning using the ‘--break-system-packages’ option. It would look something like this, ‘pip3 install sortedcontainers --break-system-packages’.If it exists, install the OS package. It would be something like this, ‘sudo apt install python3-sortedcontainers’Additional information:http://rptl.io/venvhttps://peps.python.org/pep-0668/https://packaging.python.org/en/latest/specifications/externally-managed-environments/#externally-managed-environmentsrichOn Monday 29 July 2024 at 10:10:36 UTC-4 Tom Keffer wrote:The user is doing a package install (the clue is paths such as '/usr/share/weewx/...'My thinking is that you are using an extension that needs 'sortedcontainers'.Please post your configuration file, /etc/weewx/weewx.conf. Make sure you look it over and remove any passwords or other sensitive information before posting. On Sun, Jul 28, 2024 at 11:41 PM Marty b <ma...@slabax.com> wrote:Should point out that I did try installing the missing module, but got the following error: $ pip3 install sortedcontainerserror: externally-managed-environment× This environment is externally managed╰─> To install Python packages system-wide, try apt install    python3-xyz, where xyz is the package you are trying to    install.    If you wish to install a non-Debian-packaged Python package,    create a virtual environment using python3 -m venv path/to/venv.    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make    sure you have python3-full installed.    For more information visit http://rptl.io/venvnote: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.On Sunday, July 28, 2024 at 11:14:11 PM UTC-7 Marty b wrote:Hello,Just built a new SD card with Raspbian bookworm 64 bit and WeeWx.  When starting weewx I get an error "No module named 'sortedcontainers'.  Please let me know how to resolve this.Thanks!Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: StdConvert target unit is 0x1Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.wxservices: StdWXCalculate will use data binding wx_bindingJul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: Archive will use data binding wx_bindingJul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: Record generation will be attempted in 'hardware'Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: Using archive interval of 300 seconds (specified by hardware)Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: StationRegistry: Registration not requested.Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: Wunderground: Posting not enabled.Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: PWSweather: Posting not enabled.Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: CWOP: Posting not enabled.Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: WOW: Posting not enabled.Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: AWEKAS: Posting not enabled.Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: 'pyephem' detected, extended almanac data is availableJul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: Caught unrecoverable exception:Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:       No module named 'sortedcontainers'Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:       Traceback (most recent 

Re: [weewx-user] Re: New Install of WeeWx on Raspbian Bookworm - No module named 'sortedcontainers'

['John Kline' via weewx-user]

I looks like he is using an extension of mine (weewx-loopdata) that requires sorted containers since weewx-loopdata v3.0.  The README states that sortedcontainers must be installed and the weewx 5 install instructions, step 1, states:Activate the virtual environment (actual syntax varies by type of WeeWX install):/home/weewx/weewx-venv/bin/activateI’m asssuming weewx 5.  If it is weewx 4, follow the WeeWX instructions for weewx 4 installs.On Jul 29, 2024, at 9:51 AM, bell...@gmail.com  wrote:This is ‘due’ to pep 668 and a ‘push’ for users to use virtual environments. It is warning the person installing the python module, sortedcontainers, that they  are installing into an ‘global’ (externally-managed-environment) location. There are a few ways to solve this.Create a virtual environment, activate it, and install the module. Since WeeWX was a package install, this is not reasonable.As the message states, override the warning using the ‘--break-system-packages’ option. It would look something like this, ‘pip3 install sortedcontainers --break-system-packages’.If it exists, install the OS package. It would be something like this, ‘sudo apt install python3-sortedcontainers’Additional information:http://rptl.io/venvhttps://peps.python.org/pep-0668/https://packaging.python.org/en/latest/specifications/externally-managed-environments/#externally-managed-environmentsrichOn Monday 29 July 2024 at 10:10:36 UTC-4 Tom Keffer wrote:The user is doing a package install (the clue is paths such as '/usr/share/weewx/...'My thinking is that you are using an extension that needs 'sortedcontainers'.Please post your configuration file, /etc/weewx/weewx.conf. Make sure you look it over and remove any passwords or other sensitive information before posting. On Sun, Jul 28, 2024 at 11:41 PM Marty b  wrote:Should point out that I did try installing the missing module, but got the following error: $ pip3 install sortedcontainerserror: externally-managed-environment× This environment is externally managed╰─> To install Python packages system-wide, try apt install    python3-xyz, where xyz is the package you are trying to    install.    If you wish to install a non-Debian-packaged Python package,    create a virtual environment using python3 -m venv path/to/venv.    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make    sure you have python3-full installed.    For more information visit http://rptl.io/venvnote: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.On Sunday, July 28, 2024 at 11:14:11 PM UTC-7 Marty b wrote:Hello,Just built a new SD card with Raspbian bookworm 64 bit and WeeWx.  When starting weewx I get an error "No module named 'sortedcontainers'.  Please let me know how to resolve this.Thanks!Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: StdConvert target unit is 0x1Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.wxservices: StdWXCalculate will use data binding wx_bindingJul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: Archive will use data binding wx_bindingJul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: Record generation will be attempted in 'hardware'Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: Using archive interval of 300 seconds (specified by hardware)Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: StationRegistry: Registration not requested.Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: Wunderground: Posting not enabled.Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: PWSweather: Posting not enabled.Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: CWOP: Posting not enabled.Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: WOW: Posting not enabled.Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: AWEKAS: Posting not enabled.Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: 'pyephem' detected, extended almanac data is availableJul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: Caught unrecoverable exception:Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:       No module named 'sortedcontainers'Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:       Traceback (most recent call last):Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:         File "/usr/share/weewx/weewxd.py", line 121, in mainJul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:           engine = weewx.engine.StdEngine(config_dict)Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:                    ^^^Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:         File "/usr/share/weewx/weewx/engine.py", line 89, in __init__Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:           self.loadServices(config_dict)Jul 28 

Re: [weewx-user] Backup sqlite file

['John Kline' via weewx-user]

> I don't know how I can make sure the database is not in the middle of a transaction when I'm attempting the copy.Do a sha1sum of the database:    sha1sum /home/weewx/archive/weewx.sdbMake the copy.Do another sha1sum of the database:    sha1sum /home/weewx/archive/weewx.sdbIf the sha1 hasn’t changed, you have a good copy.If it has changed, sleep and try again.On Jun 21, 2024, at 2:14 PM, Jeff Allison  wrote:Cron job and copy of the copy sounds like a good plan. Thanks!- Jeff On Friday, June 21, 2024 at 2:00:18 PM UTC-7 p q wrote:I run a cron job at 2am that shuts down Weewx, copies the database and restarts it. I used to then copy the backup copy to google drive, but google made the authentication impossible, so I stopped doing that part. I just manually copy it from time to time - perhaps I should do what you're doing with pscp too. Anyway, copying the copy would protect you from a conflict. On Fri, Jun 21, 2024 at 1:48 PM Jeff Allison  wrote:Hello,Just recently installed weewx and I'm looking for the best way to make regular backups. My plan is to create a Windows batch file that uses pscp to copy all the relevant files to a folder on my Windows system and schedule that to run daily. Pretty straightforward, but I'm concerned about getting a valid copy of the sqlite database file. The docs make this warning:For a SQLite configuration, do not make the copy of the database file while in the middle of a transaction! Schedule the backup for immediately after an archive record is written, and then make sure the backup completes before the next archive record arrives. I don't know how I can make sure the database is not in the middle of a transaction when I'm attempting the copy. Shutting down and restarting weewx I guess is possible using ssh commands in the batch file, but that's getting more complicated. How worried do I need to be about getting a bad backup file if I just copy the file over?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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/a7ffec0e-81ac-453c-b113-1c497e36783dn%40googlegroups.com.
-- Peter Quinn(415)794-2264




-- 
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/f0f5983d-f11f-471e-9f46-bce458053fa2n%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/E57C07F5-591C-423D-B863-96872D35FC31%40johnkline.com.

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

It’s really about being familiar with the OS.  You’re installing something in your home directory tree.  Clearly (since it works now), weewx is running as another user.  Weewx is attempting to access the tide program.  To do so, it must traverse through your home directory.  You either have to allow that, or put xtide somewhere else where the weewx user does have access.  We took the easiest path to resolve the issue.  If you did it all over again, you would have to do the same thing.  I did add the chmod 755 instruction to the readme.On Jun 20, 2024, at 2:11 PM, philip@gmail.com  wrote:Debian 12 was freshly installed onto a new sd card and then I loaded weewx v5 using Installation on Debian systems and ran it in simulator modeForecast / xtide was loaded next so wondered what could have done as far as permissions were concerned.On Thursday, June 20, 2024 at 9:52:03 PM UTC+1 philip@gmail.com wrote:phil@raspberrypi:~ $ ls -ld /home/phildrwx-- 15 phil phil 4096 Jun 20 20:31 /home/philphil@raspberrypi:~ $ chmod 755 /home/philphil@raspberrypi:~ $ ls -ld /home/phildrwxr-xr-x 15 phil phil 4096 Jun 20 20:31 /home/philand the last 3 lines from the log2024-06-20T21:45:19.234716+01:00 raspberrypi weewxd[1323]: INFO weewx.manager: Added record 2024-06-20 21:45:19 BST (1718916319) to database 'forecast.sdb'2024-06-20T21:45:20.082129+01:00 raspberrypi weewxd[1323]: INFO user.forecast: XTideThread: XTide: saved 108 forecast records2024-06-20T21:45:20.082229+01:00 raspberrypi weewxd[1323]: INFO user.forecast: XTideThread: XTide: deleted forecasts prior to 1716497120So thanks for your patience as for what weewx runs as sorry i didnt know and didnt know how to find outSo thanks againPhilOn Thursday, June 20, 2024 at 9:33:52 PM UTC+1 John Kline wrote:It’s unfortunate that you didn’t tell me what user weewx runs as.Also, you did an ‘eye-dee’ instead of an “ell-dee”.please run the following (perhaps cut and paste it):ls -ld /home/philAfter you do the ls -ld (so you can send me the answer), please run the following:chmod 755 /home/philAnd then see if the tides populate on the next run.On Jun 20, 2024, at 1:22 PM, philip@gmail.com <philip@gmail.com> wrote:Not familiar with much to do with permissions but as a starting point is this what you meantphil@raspberrypi:~ $ ls -ltotal 604drwxr-xr-x 2 phil phil   4096 Mar 15 15:05 Bookshelfdrwxr-xr-x 2 phil phil   4096 Jun 18 16:43 Desktopdrwxr-xr-x 2 phil phil   4096 Jun 18 16:43 Documentsdrwxr-xr-x 2 phil phil   4096 Jun 19 16:28 Downloadsdrwxr-xr-x 2 phil phil   4096 Jun 18 16:43 Musicdrwxr-xr-x 2 phil phil   4096 Jun 20 16:05 Picturesdrwxr-xr-x 2 phil phil   4096 Jun 18 16:43 Publicdrwxr-xr-x 2 phil phil   4096 Jun 18 16:43 Templatesdrwxr-xr-x 2 phil phil   4096 Jun 18 16:43 Videosdrwxrwxrwx 8 phil phil   4096 Jun 18 22:06 xtide-2.15.5-rw-r--r-- 1 phil phil 574972 May 11  2022 xtide-2.15.5.tar.xz phil@raspberrypi:~ $ ls -id /home/phil1046530 /home/philYou will have to talk me through anything deeperOn Thursday, June 20, 2024 at 8:38:15 PM UTC+1 John Kline wrote:The only other thing I can think of is permissions.  I assume you are running as phil when you try it manually and have it working.  What user is weewx running as?  If it isn’t phil, can you try manually as the the weewx user?  If that’s not easy for you, you can send the permission (ls -l) on file and directory that we need to access.In particular, starting with bookworm, a user’s home directory is not acessible by other users.  As such,ls -ld /home/philwould be particularly useful command to run. On Jun 20, 2024, at 12:28 PM, philip@gmail.com <philip@gmail.com> wrote:/usr/share/xtide contains harmonics-dwf-20100529-nonfree and harmonics-dwf-20191229-free-tcdand /etc/xtide.conf  has /usr/share/xtide in.On Thursday, June 20, 2024 at 7:44:52 PM UTC+1 John Kline wrote:I just installed the non-free xtide data package and set my location to Cromer, England.    [[XTide]]        location = Cromer, England        prog = /home/jkline/software/xtide-2.15.5/tideIt works perfectly:2024-06-20T11:35:03.159036-07:00 judygirldog5 weewxd[2845024]: INFO user.forecast: XTideThread: XTide: generating tides from 2024-06-20 00:00:00 PDT (1718866800) to 2024-07-18 00:00:00 PDT (1721286000)2024-06-20T11:35:03.326879-07:00 judygirldog5 weewxd[2845024]: INFO user.forecast: XTideThread: XTide: saved 109 forecast records2024-06-20T11:35:03.352681-07:00 judygirldog5 weewxd[2845024]: INFO user.forecast: XTideThread: XTide: deleted forecasts prior to 1716489303You would see your results if it could not find the harmonic data.  When you redid the setup, did you remember to create the /etc/xtide.conf file?  What are its contents?On mine, the file contains “/usr/share/xtide”In turn, /usr/share/xtide contains:harmonics-dwf-20100529-nonfree.tcd  harmonics-dwf-20191229-free.tcdOn Jun 20, 2024, at 11:25 AM, philip@gmail.com <philip@gmail.com> wrote:Changed weewx.confDeleted forecast.sdbRestarted weewxSti

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

It’s unfortunate that you didn’t tell me what user weewx runs as.Also, you did an ‘eye-dee’ instead of an “ell-dee”.please run the following (perhaps cut and paste it):ls -ld /home/philAfter you do the ls -ld (so you can send me the answer), please run the following:chmod 755 /home/philAnd then see if the tides populate on the next run.On Jun 20, 2024, at 1:22 PM, philip@gmail.com  wrote:Not familiar with much to do with permissions but as a starting point is this what you meantphil@raspberrypi:~ $ ls -ltotal 604drwxr-xr-x 2 phil phil   4096 Mar 15 15:05 Bookshelfdrwxr-xr-x 2 phil phil   4096 Jun 18 16:43 Desktopdrwxr-xr-x 2 phil phil   4096 Jun 18 16:43 Documentsdrwxr-xr-x 2 phil phil   4096 Jun 19 16:28 Downloadsdrwxr-xr-x 2 phil phil   4096 Jun 18 16:43 Musicdrwxr-xr-x 2 phil phil   4096 Jun 20 16:05 Picturesdrwxr-xr-x 2 phil phil   4096 Jun 18 16:43 Publicdrwxr-xr-x 2 phil phil   4096 Jun 18 16:43 Templatesdrwxr-xr-x 2 phil phil   4096 Jun 18 16:43 Videosdrwxrwxrwx 8 phil phil   4096 Jun 18 22:06 xtide-2.15.5-rw-r--r-- 1 phil phil 574972 May 11  2022 xtide-2.15.5.tar.xz phil@raspberrypi:~ $ ls -id /home/phil1046530 /home/philYou will have to talk me through anything deeperOn Thursday, June 20, 2024 at 8:38:15 PM UTC+1 John Kline wrote:The only other thing I can think of is permissions.  I assume you are running as phil when you try it manually and have it working.  What user is weewx running as?  If it isn’t phil, can you try manually as the the weewx user?  If that’s not easy for you, you can send the permission (ls -l) on file and directory that we need to access.In particular, starting with bookworm, a user’s home directory is not acessible by other users.  As such,ls -ld /home/philwould be particularly useful command to run. On Jun 20, 2024, at 12:28 PM, philip@gmail.com <philip@gmail.com> wrote:/usr/share/xtide contains harmonics-dwf-20100529-nonfree and harmonics-dwf-20191229-free-tcdand /etc/xtide.conf  has /usr/share/xtide in.On Thursday, June 20, 2024 at 7:44:52 PM UTC+1 John Kline wrote:I just installed the non-free xtide data package and set my location to Cromer, England.    [[XTide]]        location = Cromer, England        prog = /home/jkline/software/xtide-2.15.5/tideIt works perfectly:2024-06-20T11:35:03.159036-07:00 judygirldog5 weewxd[2845024]: INFO user.forecast: XTideThread: XTide: generating tides from 2024-06-20 00:00:00 PDT (1718866800) to 2024-07-18 00:00:00 PDT (1721286000)2024-06-20T11:35:03.326879-07:00 judygirldog5 weewxd[2845024]: INFO user.forecast: XTideThread: XTide: saved 109 forecast records2024-06-20T11:35:03.352681-07:00 judygirldog5 weewxd[2845024]: INFO user.forecast: XTideThread: XTide: deleted forecasts prior to 1716489303You would see your results if it could not find the harmonic data.  When you redid the setup, did you remember to create the /etc/xtide.conf file?  What are its contents?On mine, the file contains “/usr/share/xtide”In turn, /usr/share/xtide contains:harmonics-dwf-20100529-nonfree.tcd  harmonics-dwf-20191229-free.tcdOn Jun 20, 2024, at 11:25 AM, philip@gmail.com <philip@gmail.com> wrote:Changed weewx.confDeleted forecast.sdbRestarted weewxStill no change after about 3hrsStill no data availableOn Thursday, June 20, 2024 at 2:48:18 PM UTC+1 John Kline wrote:Philip,You are using the non-free xtide data presumably to get data for Cromer.  I don’t have that installed.Let’s first confirm if this will work for Palo Alto.  Change your weewx.conf to use location: Palo Alto Yacht Harbor, San Francisco Bay, CaliforniaWhile you are at it, remove the interval, duration and max_age lines.You’ll then have an identical set up to me.If that works, we can move on to Cromer.  BTW, when we do move on, it would be good if you compare the same thing between the command line and within weewx.  I see that you’ve used “Cromer” on the command line, but “Cromer, England” in weewx.  Just put Cromer (no quotes) in weewx.conf.On Jun 20, 2024, at 4:08 AM, philip@gmail.com <philip@gmail.com> wrote:Sorry bad wording on my part. Didnt move anything just went into different sun-directories from the terminal prompt.Have deleted forecast.sdb and get the same 2 lines every 5 min cycle and these are in the txt.file From the prompt  phil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide -l CromerI get Cromer tides so that seems to be workingThe 2 lines are in the txt file along with my weewx.conf [[xtide]] info.On Wednesday, June 19, 2024 at 11:17:50 PM UTC+1 John Kline wrote:My god.  Don’t be moving the program around.  It was built it /home/phill/xtide-2.15.5.  Leave it there and point prog to it.You need to be able to execute whatever the prog line says.  For example:In my case:prog = /home/jkline/software/xtide-2.15.5/tideSo, I need to be able to execute:/home/jkline/software/xtide-2.15.5/tideIf that works, you’ll be good to go.  ***Restart*** WeeWX and wait for it to decide to run the XTideThread again.  If you have any fu

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

The only other thing I can think of is permissions.  I assume you are running as phil when you try it manually and have it working.  What user is weewx running as?  If it isn’t phil, can you try manually as the the weewx user?  If that’s not easy for you, you can send the permission (ls -l) on file and directory that we need to access.In particular, starting with bookworm, a user’s home directory is not acessible by other users.  As such,ls -ld /home/philwould be particularly useful command to run. On Jun 20, 2024, at 12:28 PM, philip@gmail.com  wrote:/usr/share/xtide contains harmonics-dwf-20100529-nonfree and harmonics-dwf-20191229-free-tcdand /etc/xtide.conf  has /usr/share/xtide in.On Thursday, June 20, 2024 at 7:44:52 PM UTC+1 John Kline wrote:I just installed the non-free xtide data package and set my location to Cromer, England.    [[XTide]]        location = Cromer, England        prog = /home/jkline/software/xtide-2.15.5/tideIt works perfectly:2024-06-20T11:35:03.159036-07:00 judygirldog5 weewxd[2845024]: INFO user.forecast: XTideThread: XTide: generating tides from 2024-06-20 00:00:00 PDT (1718866800) to 2024-07-18 00:00:00 PDT (1721286000)2024-06-20T11:35:03.326879-07:00 judygirldog5 weewxd[2845024]: INFO user.forecast: XTideThread: XTide: saved 109 forecast records2024-06-20T11:35:03.352681-07:00 judygirldog5 weewxd[2845024]: INFO user.forecast: XTideThread: XTide: deleted forecasts prior to 1716489303You would see your results if it could not find the harmonic data.  When you redid the setup, did you remember to create the /etc/xtide.conf file?  What are its contents?On mine, the file contains “/usr/share/xtide”In turn, /usr/share/xtide contains:harmonics-dwf-20100529-nonfree.tcd  harmonics-dwf-20191229-free.tcdOn Jun 20, 2024, at 11:25 AM, philip@gmail.com <philip@gmail.com> wrote:Changed weewx.confDeleted forecast.sdbRestarted weewxStill no change after about 3hrsStill no data availableOn Thursday, June 20, 2024 at 2:48:18 PM UTC+1 John Kline wrote:Philip,You are using the non-free xtide data presumably to get data for Cromer.  I don’t have that installed.Let’s first confirm if this will work for Palo Alto.  Change your weewx.conf to use location: Palo Alto Yacht Harbor, San Francisco Bay, CaliforniaWhile you are at it, remove the interval, duration and max_age lines.You’ll then have an identical set up to me.If that works, we can move on to Cromer.  BTW, when we do move on, it would be good if you compare the same thing between the command line and within weewx.  I see that you’ve used “Cromer” on the command line, but “Cromer, England” in weewx.  Just put Cromer (no quotes) in weewx.conf.On Jun 20, 2024, at 4:08 AM, philip@gmail.com <philip@gmail.com> wrote:Sorry bad wording on my part. Didnt move anything just went into different sun-directories from the terminal prompt.Have deleted forecast.sdb and get the same 2 lines every 5 min cycle and these are in the txt.file From the prompt  phil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide -l CromerI get Cromer tides so that seems to be workingThe 2 lines are in the txt file along with my weewx.conf [[xtide]] info.On Wednesday, June 19, 2024 at 11:17:50 PM UTC+1 John Kline wrote:My god.  Don’t be moving the program around.  It was built it /home/phill/xtide-2.15.5.  Leave it there and point prog to it.You need to be able to execute whatever the prog line says.  For example:In my case:prog = /home/jkline/software/xtide-2.15.5/tideSo, I need to be able to execute:/home/jkline/software/xtide-2.15.5/tideIf that works, you’ll be good to go.  ***Restart*** WeeWX and wait for it to decide to run the XTideThread again.  If you have any further issues, send the XTideThread lines in the log.The tide forecast doesn’t run very often.  To hurry it along, you can stop weewx, delete the forecast.sdb database in the archive directory, restart weewx and wait for a 5 minute interval.  That is when the forecast xtide thread will attempt to generate the data.  Again, any issues, send the XTideThread lines in the log.You should see something like this in the logs:2024-06-19T15:15:03.495496-07:00 judygirldog5 weewxd[1638636]: INFO user.forecast: XTideThread: XTide: generating tides from 2024-06-19 00:00:00 PDT (1718780400) to 2024-07-17 00:00:00 PDT (1721199600)2024-06-19T15:15:03.563622-07:00 judygirldog5 weewxd[1638636]: INFO user.forecast: XTideThread: XTide: saved 108 forecast records2024-06-19T15:15:03.585208-07:00 judygirldog5 weewxd[1638636]: INFO user.forecast: XTideThread: XTide: deleted forecasts prior to 1716416103On Jun 19, 2024, at 2:44 PM, philip@gmail.com <philip@gmail.com> wrote:The tide program was there but I had changed the cd /home/phil/xtide-2.15.5.I put tide there it failed.If I go to the home directory and put in /home/phil/xtide-2.15.5 tide it displays the helpIf i put in /home/phil/xtide-2.15.5/tide -l Boston it displays the Info for Boston but in the logs it says No tidal available.On Wednes

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

I just installed the non-free xtide data package and set my location to Cromer, England.    [[XTide]]        location = Cromer, England        prog = /home/jkline/software/xtide-2.15.5/tideIt works perfectly:2024-06-20T11:35:03.159036-07:00 judygirldog5 weewxd[2845024]: INFO user.forecast: XTideThread: XTide: generating tides from 2024-06-20 00:00:00 PDT (1718866800) to 2024-07-18 00:00:00 PDT (1721286000)2024-06-20T11:35:03.326879-07:00 judygirldog5 weewxd[2845024]: INFO user.forecast: XTideThread: XTide: saved 109 forecast records2024-06-20T11:35:03.352681-07:00 judygirldog5 weewxd[2845024]: INFO user.forecast: XTideThread: XTide: deleted forecasts prior to 1716489303You would see your results if it could not find the harmonic data.  When you redid the setup, did you remember to create the /etc/xtide.conf file?  What are its contents?On mine, the file contains “/usr/share/xtide”In turn, /usr/share/xtide contains:harmonics-dwf-20100529-nonfree.tcd  harmonics-dwf-20191229-free.tcdOn Jun 20, 2024, at 11:25 AM, philip@gmail.com  wrote:Changed weewx.confDeleted forecast.sdbRestarted weewxStill no change after about 3hrsStill no data availableOn Thursday, June 20, 2024 at 2:48:18 PM UTC+1 John Kline wrote:Philip,You are using the non-free xtide data presumably to get data for Cromer.  I don’t have that installed.Let’s first confirm if this will work for Palo Alto.  Change your weewx.conf to use location: Palo Alto Yacht Harbor, San Francisco Bay, CaliforniaWhile you are at it, remove the interval, duration and max_age lines.You’ll then have an identical set up to me.If that works, we can move on to Cromer.  BTW, when we do move on, it would be good if you compare the same thing between the command line and within weewx.  I see that you’ve used “Cromer” on the command line, but “Cromer, England” in weewx.  Just put Cromer (no quotes) in weewx.conf.On Jun 20, 2024, at 4:08 AM, philip@gmail.com <philip@gmail.com> wrote:Sorry bad wording on my part. Didnt move anything just went into different sun-directories from the terminal prompt.Have deleted forecast.sdb and get the same 2 lines every 5 min cycle and these are in the txt.file From the prompt  phil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide -l CromerI get Cromer tides so that seems to be workingThe 2 lines are in the txt file along with my weewx.conf [[xtide]] info.On Wednesday, June 19, 2024 at 11:17:50 PM UTC+1 John Kline wrote:My god.  Don’t be moving the program around.  It was built it /home/phill/xtide-2.15.5.  Leave it there and point prog to it.You need to be able to execute whatever the prog line says.  For example:In my case:prog = /home/jkline/software/xtide-2.15.5/tideSo, I need to be able to execute:/home/jkline/software/xtide-2.15.5/tideIf that works, you’ll be good to go.  ***Restart*** WeeWX and wait for it to decide to run the XTideThread again.  If you have any further issues, send the XTideThread lines in the log.The tide forecast doesn’t run very often.  To hurry it along, you can stop weewx, delete the forecast.sdb database in the archive directory, restart weewx and wait for a 5 minute interval.  That is when the forecast xtide thread will attempt to generate the data.  Again, any issues, send the XTideThread lines in the log.You should see something like this in the logs:2024-06-19T15:15:03.495496-07:00 judygirldog5 weewxd[1638636]: INFO user.forecast: XTideThread: XTide: generating tides from 2024-06-19 00:00:00 PDT (1718780400) to 2024-07-17 00:00:00 PDT (1721199600)2024-06-19T15:15:03.563622-07:00 judygirldog5 weewxd[1638636]: INFO user.forecast: XTideThread: XTide: saved 108 forecast records2024-06-19T15:15:03.585208-07:00 judygirldog5 weewxd[1638636]: INFO user.forecast: XTideThread: XTide: deleted forecasts prior to 1716416103On Jun 19, 2024, at 2:44 PM, philip@gmail.com <philip@gmail.com> wrote:The tide program was there but I had changed the cd /home/phil/xtide-2.15.5.I put tide there it failed.If I go to the home directory and put in /home/phil/xtide-2.15.5 tide it displays the helpIf i put in /home/phil/xtide-2.15.5/tide -l Boston it displays the Info for Boston but in the logs it says No tidal available.On Wednesday, June 19, 2024 at 10:25:16 PM UTC+1 John Kline wrote:Actually, after the make, if you don’t see the tide program, do a “make tide”. And the check for the tide program.If you see it, execute it.  You should see some help info.  If you see that, then go ahead and try it in weewx.There is not point to doing anything else until you have a tide program that you can execute.On Jun 19, 2024, at 2:19 PM, John Kline <jo...@johnkline.com> wrote:When you did the make, it didn’t create tide?Do make again and then send a listing of the directory.ls -l /home/phil/xtide-2.15.5On Jun 19, 2024, at 2:17 PM, philip@gmail.com <philip@gmail.com> wrote:Added location = "Palo Alto Yacht Harbor, San Francisco Bay, California"prog = /home/phil/xtide-2.15.5/tidesud

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

Philip,You are using the non-free xtide data presumably to get data for Cromer.  I don’t have that installed.Let’s first confirm if this will work for Palo Alto.  Change your weewx.conf to use location: Palo Alto Yacht Harbor, San Francisco Bay, CaliforniaWhile you are at it, remove the interval, duration and max_age lines.You’ll then have an identical set up to me.If that works, we can move on to Cromer.  BTW, when we do move on, it would be good if you compare the same thing between the command line and within weewx.  I see that you’ve used “Cromer” on the command line, but “Cromer, England” in weewx.  Just put Cromer (no quotes) in weewx.conf.On Jun 20, 2024, at 4:08 AM, philip@gmail.com  wrote:Sorry bad wording on my part. Didnt move anything just went into different sun-directories from the terminal prompt.Have deleted forecast.sdb and get the same 2 lines every 5 min cycle and these are in the txt.file From the prompt  phil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide -l CromerI get Cromer tides so that seems to be workingThe 2 lines are in the txt file along with my weewx.conf [[xtide]] info.On Wednesday, June 19, 2024 at 11:17:50 PM UTC+1 John Kline wrote:My god.  Don’t be moving the program around.  It was built it /home/phill/xtide-2.15.5.  Leave it there and point prog to it.You need to be able to execute whatever the prog line says.  For example:In my case:prog = /home/jkline/software/xtide-2.15.5/tideSo, I need to be able to execute:/home/jkline/software/xtide-2.15.5/tideIf that works, you’ll be good to go.  ***Restart*** WeeWX and wait for it to decide to run the XTideThread again.  If you have any further issues, send the XTideThread lines in the log.The tide forecast doesn’t run very often.  To hurry it along, you can stop weewx, delete the forecast.sdb database in the archive directory, restart weewx and wait for a 5 minute interval.  That is when the forecast xtide thread will attempt to generate the data.  Again, any issues, send the XTideThread lines in the log.You should see something like this in the logs:2024-06-19T15:15:03.495496-07:00 judygirldog5 weewxd[1638636]: INFO user.forecast: XTideThread: XTide: generating tides from 2024-06-19 00:00:00 PDT (1718780400) to 2024-07-17 00:00:00 PDT (1721199600)2024-06-19T15:15:03.563622-07:00 judygirldog5 weewxd[1638636]: INFO user.forecast: XTideThread: XTide: saved 108 forecast records2024-06-19T15:15:03.585208-07:00 judygirldog5 weewxd[1638636]: INFO user.forecast: XTideThread: XTide: deleted forecasts prior to 1716416103On Jun 19, 2024, at 2:44 PM, philip@gmail.com <philip@gmail.com> wrote:The tide program was there but I had changed the cd /home/phil/xtide-2.15.5.I put tide there it failed.If I go to the home directory and put in /home/phil/xtide-2.15.5 tide it displays the helpIf i put in /home/phil/xtide-2.15.5/tide -l Boston it displays the Info for Boston but in the logs it says No tidal available.On Wednesday, June 19, 2024 at 10:25:16 PM UTC+1 John Kline wrote:Actually, after the make, if you don’t see the tide program, do a “make tide”. And the check for the tide program.If you see it, execute it.  You should see some help info.  If you see that, then go ahead and try it in weewx.There is not point to doing anything else until you have a tide program that you can execute.On Jun 19, 2024, at 2:19 PM, John Kline <jo...@johnkline.com> wrote:When you did the make, it didn’t create tide?Do make again and then send a listing of the directory.ls -l /home/phil/xtide-2.15.5On Jun 19, 2024, at 2:17 PM, philip@gmail.com <philip@gmail.com> wrote:Added location = "Palo Alto Yacht Harbor, San Francisco Bay, California"prog = /home/phil/xtide-2.15.5/tidesudo apt install xtide-dataAdded /etc/xtide.conf with /usr/share/xtide   where the harmonic isStill I get no tidal dataIf i do /home/phil/xtide-2.15.5/tide   it comes  back tide command not foundOn Tuesday, June 18, 2024 at 10:31:58 PM UTC+1 John Kline wrote:I checked your output.  It looks like configure and make succeeded.  You should be good to go.On Jun 18, 2024, at 2:16 PM, philip@gmail.com <philip@gmail.com> wrote:sorry forgot to add the txt fileOn Tuesday, June 18, 2024 at 10:13:45 PM UTC+1 philip@gmail.com wrote:It looks more promising.I haven't gone pass   make    but if  its what you expected will carry on but not until tomorrow.But thanks so farPhilOn Tuesday, June 18, 2024 at 9:52:46 PM UTC+1 John Kline wrote:OK, the difference is that you are building on the full install of bookworm and I am building on lite.  Try this for the configure step:./configure --with-x=noThat *should* build what I am building (tide, but not xtide).  I’m guessing this will work, but let me know.  If it does, I’ll update the README.On Jun 18, 2024, at 1:27 PM, philip@gmail.com <philip@gmail.com> wrote:phil@raspberrypi:~/xtide-2.15.5 $ sudo apt install libfreetype6Reading package lists... DoneBuilding dependen

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

My god.  Don’t be moving the program around.  It was built it /home/phill/xtide-2.15.5.  Leave it there and point prog to it.You need to be able to execute whatever the prog line says.  For example:In my case:prog = /home/jkline/software/xtide-2.15.5/tideSo, I need to be able to execute:/home/jkline/software/xtide-2.15.5/tideIf that works, you’ll be good to go.  ***Restart*** WeeWX and wait for it to decide to run the XTideThread again.  If you have any further issues, send the XTideThread lines in the log.The tide forecast doesn’t run very often.  To hurry it along, you can stop weewx, delete the forecast.sdb database in the archive directory, restart weewx and wait for a 5 minute interval.  That is when the forecast xtide thread will attempt to generate the data.  Again, any issues, send the XTideThread lines in the log.You should see something like this in the logs:2024-06-19T15:15:03.495496-07:00 judygirldog5 weewxd[1638636]: INFO user.forecast: XTideThread: XTide: generating tides from 2024-06-19 00:00:00 PDT (1718780400) to 2024-07-17 00:00:00 PDT (1721199600)2024-06-19T15:15:03.563622-07:00 judygirldog5 weewxd[1638636]: INFO user.forecast: XTideThread: XTide: saved 108 forecast records2024-06-19T15:15:03.585208-07:00 judygirldog5 weewxd[1638636]: INFO user.forecast: XTideThread: XTide: deleted forecasts prior to 1716416103On Jun 19, 2024, at 2:44 PM, philip@gmail.com  wrote:The tide program was there but I had changed the cd /home/phil/xtide-2.15.5.I put tide there it failed.If I go to the home directory and put in /home/phil/xtide-2.15.5 tide it displays the helpIf i put in /home/phil/xtide-2.15.5/tide -l Boston it displays the Info for Boston but in the logs it says No tidal available.On Wednesday, June 19, 2024 at 10:25:16 PM UTC+1 John Kline wrote:Actually, after the make, if you don’t see the tide program, do a “make tide”. And the check for the tide program.If you see it, execute it.  You should see some help info.  If you see that, then go ahead and try it in weewx.There is not point to doing anything else until you have a tide program that you can execute.On Jun 19, 2024, at 2:19 PM, John Kline <jo...@johnkline.com> wrote:When you did the make, it didn’t create tide?Do make again and then send a listing of the directory.ls -l /home/phil/xtide-2.15.5On Jun 19, 2024, at 2:17 PM, philip@gmail.com <philip@gmail.com> wrote:Added location = "Palo Alto Yacht Harbor, San Francisco Bay, California"prog = /home/phil/xtide-2.15.5/tidesudo apt install xtide-dataAdded /etc/xtide.conf with /usr/share/xtide   where the harmonic isStill I get no tidal dataIf i do /home/phil/xtide-2.15.5/tide   it comes  back tide command not foundOn Tuesday, June 18, 2024 at 10:31:58 PM UTC+1 John Kline wrote:I checked your output.  It looks like configure and make succeeded.  You should be good to go.On Jun 18, 2024, at 2:16 PM, philip@gmail.com <philip@gmail.com> wrote:sorry forgot to add the txt fileOn Tuesday, June 18, 2024 at 10:13:45 PM UTC+1 philip@gmail.com wrote:It looks more promising.I haven't gone pass   make    but if  its what you expected will carry on but not until tomorrow.But thanks so farPhilOn Tuesday, June 18, 2024 at 9:52:46 PM UTC+1 John Kline wrote:OK, the difference is that you are building on the full install of bookworm and I am building on lite.  Try this for the configure step:./configure --with-x=noThat *should* build what I am building (tide, but not xtide).  I’m guessing this will work, but let me know.  If it does, I’ll update the README.On Jun 18, 2024, at 1:27 PM, philip@gmail.com <philip@gmail.com> wrote:phil@raspberrypi:~/xtide-2.15.5 $ sudo apt install libfreetype6Reading package lists... DoneBuilding dependency tree... DoneReading state information... Donelibfreetype6 is already the newest version (2.12.1+dfsg-5).libfreetype6 set to manually installed.The following packages were automatically installed and are no longer required:  libcamera0.2 libraspberrypi0 libwpe-1.0-1 libwpebackend-fdo-1.0-1Use 'sudo apt autoremove' to remove them.0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.phil@raspberrypi:~/xtide-2.15.5 $ On Tuesday, June 18, 2024 at 8:01:12 PM UTC+1 John Kline wrote:Try:sudo apt install libfreetype6And then re-run configure.  Again, there is no need to run make (which you did again) if the configure ends in an error.On Jun 18, 2024, at 11:37 AM, philip@gmail.com <philip@gmail.com> wrote:This time i used the correct file but as you can see from the file Im attaching going down your readme file when I get to make it seems to fail so I didnt go any furtherOn Tuesday, June 18, 2024 at 3:49:28 PM UTC+1 philip@gmail.com wrote:OOPs  Yes I didOh well 3rd time luckOn Tuesday, June 18, 2024 at 2:42:45 PM UTC+1 John Kline wrote:> Then used  tar -zxvf xtide-2.15.5.tar.gz and changed to that directoryWhich tar did you use?  You cannot use the file I sent you.On Jun 18, 202

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

Actually, after the make, if you don’t see the tide program, do a “make tide”. And the check for the tide program.If you see it, execute it.  You should see some help info.  If you see that, then go ahead and try it in weewx.There is not point to doing anything else until you have a tide program that you can execute.On Jun 19, 2024, at 2:19 PM, John Kline  wrote:When you did the make, it didn’t create tide?Do make again and then send a listing of the directory.ls -l /home/phil/xtide-2.15.5On Jun 19, 2024, at 2:17 PM, philip@gmail.com  wrote:Added location = "Palo Alto Yacht Harbor, San Francisco Bay, California"prog = /home/phil/xtide-2.15.5/tidesudo apt install xtide-dataAdded /etc/xtide.conf with /usr/share/xtide   where the harmonic isStill I get no tidal dataIf i do /home/phil/xtide-2.15.5/tide   it comes  back tide command not foundOn Tuesday, June 18, 2024 at 10:31:58 PM UTC+1 John Kline wrote:I checked your output.  It looks like configure and make succeeded.  You should be good to go.On Jun 18, 2024, at 2:16 PM, philip@gmail.com <philip@gmail.com> wrote:sorry forgot to add the txt fileOn Tuesday, June 18, 2024 at 10:13:45 PM UTC+1 philip@gmail.com wrote:It looks more promising.I haven't gone pass   make    but if  its what you expected will carry on but not until tomorrow.But thanks so farPhilOn Tuesday, June 18, 2024 at 9:52:46 PM UTC+1 John Kline wrote:OK, the difference is that you are building on the full install of bookworm and I am building on lite.  Try this for the configure step:./configure --with-x=noThat *should* build what I am building (tide, but not xtide).  I’m guessing this will work, but let me know.  If it does, I’ll update the README.On Jun 18, 2024, at 1:27 PM, philip@gmail.com <philip@gmail.com> wrote:phil@raspberrypi:~/xtide-2.15.5 $ sudo apt install libfreetype6Reading package lists... DoneBuilding dependency tree... DoneReading state information... Donelibfreetype6 is already the newest version (2.12.1+dfsg-5).libfreetype6 set to manually installed.The following packages were automatically installed and are no longer required:  libcamera0.2 libraspberrypi0 libwpe-1.0-1 libwpebackend-fdo-1.0-1Use 'sudo apt autoremove' to remove them.0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.phil@raspberrypi:~/xtide-2.15.5 $ On Tuesday, June 18, 2024 at 8:01:12 PM UTC+1 John Kline wrote:Try:sudo apt install libfreetype6And then re-run configure.  Again, there is no need to run make (which you did again) if the configure ends in an error.On Jun 18, 2024, at 11:37 AM, philip@gmail.com <philip@gmail.com> wrote:This time i used the correct file but as you can see from the file Im attaching going down your readme file when I get to make it seems to fail so I didnt go any furtherOn Tuesday, June 18, 2024 at 3:49:28 PM UTC+1 philip@gmail.com wrote:OOPs  Yes I didOh well 3rd time luckOn Tuesday, June 18, 2024 at 2:42:45 PM UTC+1 John Kline wrote:> Then used  tar -zxvf xtide-2.15.5.tar.gz and changed to that directoryWhich tar did you use?  You cannot use the file I sent you.On Jun 18, 2024, at 6:24 AM, philip@gmail.com <philip@gmail.com> wrote:Hi JohnBuilt a fresh build using the Raspberry pi imagerLoaded weewx   All OKThen used 

tar -zxvf xtide-2.15.5.tar.gz and changed to that directorythen sudo apt-get install libpng-dev and then sudo apt-get install libtcd-dev./ configureand then make and this time gotmake  all-ammake[1]: Entering directory '/home/phil/xtide-2.15.5'make[1]: Nothing to be done for 'all-am'.make[1]: Leaving directory '/home/phil/xtide-2.15.5'so then sudo apt-get install xtide-dataand then in xtide-2.15.5 folder type tide and gotphil@raspberrypi:~/xtide-2.15.5 $ tidebash: tide: command not foundAs this didnt work I stopped as I believe you said if that does not work its no goodHave put all this in the text file I hope ??On Monday, June 17, 2024 at 7:17:49 PM UTC+1 philip@gmail.com wrote:I use the Raspberry Pi Imager with Pi5 and Pi 5 64 Bit software so Im assuming its the full package.What Im going to do is have a fresh install of Pi5 using the Raspberry Imager and load weewx again and start a fresh with your XTide-=2.15.5.tar.gzI shall copy all terminal responses to this post and see what you think.Im hoping ./configure and then make works.Will send you all terminal responses.Phil On Monday, June 17, 2024 at 6:07:01 PM UTC+1 John Kline wrote:If you try executing tide and it doesn’t work, you need not try anything further.  The problem is the path /home/jkline (my home directory) is hardcoded by configure.You need to be able to build xtide.  If you want to try again, and configure fails again, I can have a look.  Please [re-]confirm that you have installed the prerequisites.  If configure fails again, there is no point to try make.I am surprised that you can’t configure since we’re running the same OS.  I have the lite version of Bookworm 64-bit installed.  Do you have t

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

When you did the make, it didn’t create tide?Do make again and then send a listing of the directory.ls -l /home/phil/xtide-2.15.5On Jun 19, 2024, at 2:17 PM, philip@gmail.com  wrote:Added location = "Palo Alto Yacht Harbor, San Francisco Bay, California"prog = /home/phil/xtide-2.15.5/tidesudo apt install xtide-dataAdded /etc/xtide.conf with /usr/share/xtide   where the harmonic isStill I get no tidal dataIf i do /home/phil/xtide-2.15.5/tide   it comes  back tide command not foundOn Tuesday, June 18, 2024 at 10:31:58 PM UTC+1 John Kline wrote:I checked your output.  It looks like configure and make succeeded.  You should be good to go.On Jun 18, 2024, at 2:16 PM, philip@gmail.com <philip@gmail.com> wrote:sorry forgot to add the txt fileOn Tuesday, June 18, 2024 at 10:13:45 PM UTC+1 philip@gmail.com wrote:It looks more promising.I haven't gone pass   make    but if  its what you expected will carry on but not until tomorrow.But thanks so farPhilOn Tuesday, June 18, 2024 at 9:52:46 PM UTC+1 John Kline wrote:OK, the difference is that you are building on the full install of bookworm and I am building on lite.  Try this for the configure step:./configure --with-x=noThat *should* build what I am building (tide, but not xtide).  I’m guessing this will work, but let me know.  If it does, I’ll update the README.On Jun 18, 2024, at 1:27 PM, philip@gmail.com <philip@gmail.com> wrote:phil@raspberrypi:~/xtide-2.15.5 $ sudo apt install libfreetype6Reading package lists... DoneBuilding dependency tree... DoneReading state information... Donelibfreetype6 is already the newest version (2.12.1+dfsg-5).libfreetype6 set to manually installed.The following packages were automatically installed and are no longer required:  libcamera0.2 libraspberrypi0 libwpe-1.0-1 libwpebackend-fdo-1.0-1Use 'sudo apt autoremove' to remove them.0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.phil@raspberrypi:~/xtide-2.15.5 $ On Tuesday, June 18, 2024 at 8:01:12 PM UTC+1 John Kline wrote:Try:sudo apt install libfreetype6And then re-run configure.  Again, there is no need to run make (which you did again) if the configure ends in an error.On Jun 18, 2024, at 11:37 AM, philip@gmail.com <philip@gmail.com> wrote:This time i used the correct file but as you can see from the file Im attaching going down your readme file when I get to make it seems to fail so I didnt go any furtherOn Tuesday, June 18, 2024 at 3:49:28 PM UTC+1 philip@gmail.com wrote:OOPs  Yes I didOh well 3rd time luckOn Tuesday, June 18, 2024 at 2:42:45 PM UTC+1 John Kline wrote:> Then used  tar -zxvf xtide-2.15.5.tar.gz and changed to that directoryWhich tar did you use?  You cannot use the file I sent you.On Jun 18, 2024, at 6:24 AM, philip@gmail.com <philip@gmail.com> wrote:Hi JohnBuilt a fresh build using the Raspberry pi imagerLoaded weewx   All OKThen used 

tar -zxvf xtide-2.15.5.tar.gz and changed to that directorythen sudo apt-get install libpng-dev and then sudo apt-get install libtcd-dev./ configureand then make and this time gotmake  all-ammake[1]: Entering directory '/home/phil/xtide-2.15.5'make[1]: Nothing to be done for 'all-am'.make[1]: Leaving directory '/home/phil/xtide-2.15.5'so then sudo apt-get install xtide-dataand then in xtide-2.15.5 folder type tide and gotphil@raspberrypi:~/xtide-2.15.5 $ tidebash: tide: command not foundAs this didnt work I stopped as I believe you said if that does not work its no goodHave put all this in the text file I hope ??On Monday, June 17, 2024 at 7:17:49 PM UTC+1 philip@gmail.com wrote:I use the Raspberry Pi Imager with Pi5 and Pi 5 64 Bit software so Im assuming its the full package.What Im going to do is have a fresh install of Pi5 using the Raspberry Imager and load weewx again and start a fresh with your XTide-=2.15.5.tar.gzI shall copy all terminal responses to this post and see what you think.Im hoping ./configure and then make works.Will send you all terminal responses.Phil On Monday, June 17, 2024 at 6:07:01 PM UTC+1 John Kline wrote:If you try executing tide and it doesn’t work, you need not try anything further.  The problem is the path /home/jkline (my home directory) is hardcoded by configure.You need to be able to build xtide.  If you want to try again, and configure fails again, I can have a look.  Please [re-]confirm that you have installed the prerequisites.  If configure fails again, there is no point to try make.I am surprised that you can’t configure since we’re running the same OS.  I have the lite version of Bookworm 64-bit installed.  Do you have the full version?On Jun 17, 2024, at 9:36 AM, philip@gmail.com <philip@gmail.com> wrote:rm -rf xtide-2.15.5      This removed the directory OKcopied your xtide-2.15.5.tar.gz into my Downloads directory and from that directory tar -zxvf xtide-2.15.5.tar.gzwhich went ok.restarted weewxFrom the xtide-2.15.5 directory  $ tide got thisphil@raspberrypi:~ $ /

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

I checked your output.  It looks like configure and make succeeded.  You should be good to go.On Jun 18, 2024, at 2:16 PM, philip@gmail.com  wrote:sorry forgot to add the txt fileOn Tuesday, June 18, 2024 at 10:13:45 PM UTC+1 philip@gmail.com wrote:It looks more promising.I haven't gone pass   make    but if  its what you expected will carry on but not until tomorrow.But thanks so farPhilOn Tuesday, June 18, 2024 at 9:52:46 PM UTC+1 John Kline wrote:OK, the difference is that you are building on the full install of bookworm and I am building on lite.  Try this for the configure step:./configure --with-x=noThat *should* build what I am building (tide, but not xtide).  I’m guessing this will work, but let me know.  If it does, I’ll update the README.On Jun 18, 2024, at 1:27 PM, philip@gmail.com <philip@gmail.com> wrote:phil@raspberrypi:~/xtide-2.15.5 $ sudo apt install libfreetype6Reading package lists... DoneBuilding dependency tree... DoneReading state information... Donelibfreetype6 is already the newest version (2.12.1+dfsg-5).libfreetype6 set to manually installed.The following packages were automatically installed and are no longer required:  libcamera0.2 libraspberrypi0 libwpe-1.0-1 libwpebackend-fdo-1.0-1Use 'sudo apt autoremove' to remove them.0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.phil@raspberrypi:~/xtide-2.15.5 $ On Tuesday, June 18, 2024 at 8:01:12 PM UTC+1 John Kline wrote:Try:sudo apt install libfreetype6And then re-run configure.  Again, there is no need to run make (which you did again) if the configure ends in an error.On Jun 18, 2024, at 11:37 AM, philip@gmail.com <philip@gmail.com> wrote:This time i used the correct file but as you can see from the file Im attaching going down your readme file when I get to make it seems to fail so I didnt go any furtherOn Tuesday, June 18, 2024 at 3:49:28 PM UTC+1 philip@gmail.com wrote:OOPs  Yes I didOh well 3rd time luckOn Tuesday, June 18, 2024 at 2:42:45 PM UTC+1 John Kline wrote:> Then used  tar -zxvf xtide-2.15.5.tar.gz and changed to that directoryWhich tar did you use?  You cannot use the file I sent you.On Jun 18, 2024, at 6:24 AM, philip@gmail.com <philip@gmail.com> wrote:Hi JohnBuilt a fresh build using the Raspberry pi imagerLoaded weewx   All OKThen used 

tar -zxvf xtide-2.15.5.tar.gz and changed to that directorythen sudo apt-get install libpng-dev and then sudo apt-get install libtcd-dev./ configureand then make and this time gotmake  all-ammake[1]: Entering directory '/home/phil/xtide-2.15.5'make[1]: Nothing to be done for 'all-am'.make[1]: Leaving directory '/home/phil/xtide-2.15.5'so then sudo apt-get install xtide-dataand then in xtide-2.15.5 folder type tide and gotphil@raspberrypi:~/xtide-2.15.5 $ tidebash: tide: command not foundAs this didnt work I stopped as I believe you said if that does not work its no goodHave put all this in the text file I hope ??On Monday, June 17, 2024 at 7:17:49 PM UTC+1 philip@gmail.com wrote:I use the Raspberry Pi Imager with Pi5 and Pi 5 64 Bit software so Im assuming its the full package.What Im going to do is have a fresh install of Pi5 using the Raspberry Imager and load weewx again and start a fresh with your XTide-=2.15.5.tar.gzI shall copy all terminal responses to this post and see what you think.Im hoping ./configure and then make works.Will send you all terminal responses.Phil On Monday, June 17, 2024 at 6:07:01 PM UTC+1 John Kline wrote:If you try executing tide and it doesn’t work, you need not try anything further.  The problem is the path /home/jkline (my home directory) is hardcoded by configure.You need to be able to build xtide.  If you want to try again, and configure fails again, I can have a look.  Please [re-]confirm that you have installed the prerequisites.  If configure fails again, there is no point to try make.I am surprised that you can’t configure since we’re running the same OS.  I have the lite version of Bookworm 64-bit installed.  Do you have the full version?On Jun 17, 2024, at 9:36 AM, philip@gmail.com <philip@gmail.com> wrote:rm -rf xtide-2.15.5      This removed the directory OKcopied your xtide-2.15.5.tar.gz into my Downloads directory and from that directory tar -zxvf xtide-2.15.5.tar.gzwhich went ok.restarted weewxFrom the xtide-2.15.5 directory  $ tide got thisphil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide/home/phil/xtide-2.15.5/.libs/tide: error while loading shared libraries: libxtide.so.1: cannot open shared object file: No such file or directoryphil@raspberrypi:~ $copied and paste the xtide-2.15.5 directory into my home directory. restarted weewxphil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide/home/phil/xtide-2.15.5/.libs/tide: error while loading shared libraries: libxtide.so.1: cannot open shared object file: No such file or directoryphil@raspberrypi:~ $ After this the log still no tidal eventsOn Monday, June 17, 2024 at 5:00:58 PM UTC+1 John 

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

OK, the difference is that you are building on the full install of bookworm and I am building on lite.  Try this for the configure step:./configure --with-x=noThat *should* build what I am building (tide, but not xtide).  I’m guessing this will work, but let me know.  If it does, I’ll update the README.On Jun 18, 2024, at 1:27 PM, philip@gmail.com  wrote:phil@raspberrypi:~/xtide-2.15.5 $ sudo apt install libfreetype6Reading package lists... DoneBuilding dependency tree... DoneReading state information... Donelibfreetype6 is already the newest version (2.12.1+dfsg-5).libfreetype6 set to manually installed.The following packages were automatically installed and are no longer required:  libcamera0.2 libraspberrypi0 libwpe-1.0-1 libwpebackend-fdo-1.0-1Use 'sudo apt autoremove' to remove them.0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.phil@raspberrypi:~/xtide-2.15.5 $ On Tuesday, June 18, 2024 at 8:01:12 PM UTC+1 John Kline wrote:Try:sudo apt install libfreetype6And then re-run configure.  Again, there is no need to run make (which you did again) if the configure ends in an error.On Jun 18, 2024, at 11:37 AM, philip@gmail.com <philip@gmail.com> wrote:This time i used the correct file but as you can see from the file Im attaching going down your readme file when I get to make it seems to fail so I didnt go any furtherOn Tuesday, June 18, 2024 at 3:49:28 PM UTC+1 philip@gmail.com wrote:OOPs  Yes I didOh well 3rd time luckOn Tuesday, June 18, 2024 at 2:42:45 PM UTC+1 John Kline wrote:> Then used  tar -zxvf xtide-2.15.5.tar.gz and changed to that directoryWhich tar did you use?  You cannot use the file I sent you.On Jun 18, 2024, at 6:24 AM, philip@gmail.com <philip@gmail.com> wrote:Hi JohnBuilt a fresh build using the Raspberry pi imagerLoaded weewx   All OKThen used 

tar -zxvf xtide-2.15.5.tar.gz and changed to that directorythen sudo apt-get install libpng-dev and then sudo apt-get install libtcd-dev./ configureand then make and this time gotmake  all-ammake[1]: Entering directory '/home/phil/xtide-2.15.5'make[1]: Nothing to be done for 'all-am'.make[1]: Leaving directory '/home/phil/xtide-2.15.5'so then sudo apt-get install xtide-dataand then in xtide-2.15.5 folder type tide and gotphil@raspberrypi:~/xtide-2.15.5 $ tidebash: tide: command not foundAs this didnt work I stopped as I believe you said if that does not work its no goodHave put all this in the text file I hope ??On Monday, June 17, 2024 at 7:17:49 PM UTC+1 philip@gmail.com wrote:I use the Raspberry Pi Imager with Pi5 and Pi 5 64 Bit software so Im assuming its the full package.What Im going to do is have a fresh install of Pi5 using the Raspberry Imager and load weewx again and start a fresh with your XTide-=2.15.5.tar.gzI shall copy all terminal responses to this post and see what you think.Im hoping ./configure and then make works.Will send you all terminal responses.Phil On Monday, June 17, 2024 at 6:07:01 PM UTC+1 John Kline wrote:If you try executing tide and it doesn’t work, you need not try anything further.  The problem is the path /home/jkline (my home directory) is hardcoded by configure.You need to be able to build xtide.  If you want to try again, and configure fails again, I can have a look.  Please [re-]confirm that you have installed the prerequisites.  If configure fails again, there is no point to try make.I am surprised that you can’t configure since we’re running the same OS.  I have the lite version of Bookworm 64-bit installed.  Do you have the full version?On Jun 17, 2024, at 9:36 AM, philip@gmail.com <philip@gmail.com> wrote:rm -rf xtide-2.15.5      This removed the directory OKcopied your xtide-2.15.5.tar.gz into my Downloads directory and from that directory tar -zxvf xtide-2.15.5.tar.gzwhich went ok.restarted weewxFrom the xtide-2.15.5 directory  $ tide got thisphil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide/home/phil/xtide-2.15.5/.libs/tide: error while loading shared libraries: libxtide.so.1: cannot open shared object file: No such file or directoryphil@raspberrypi:~ $copied and paste the xtide-2.15.5 directory into my home directory. restarted weewxphil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide/home/phil/xtide-2.15.5/.libs/tide: error while loading shared libraries: libxtide.so.1: cannot open shared object file: No such file or directoryphil@raspberrypi:~ $ After this the log still no tidal eventsOn Monday, June 17, 2024 at 5:00:58 PM UTC+1 John Kline wrote:I got a message that the file was too large.Let’s try again:It is not what I expected.  I’ll give you the whole built directory tree:You can download it at:paloaltoweather.comFrom your home directory, remove the exiting xtide directory, then untar what you just downloaded:rm -rf xtide-2.15.5tar -zxvf xtide-2.15.5.tar.gzNow try executing tide again.  If that works, restart weewx and see if it works.On Jun 17, 2024, at 8:48 AM, John Kline <jo...@johnkline.com> wrote:It is

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

Try:sudo apt install libfreetype6And then re-run configure.  Again, there is no need to run make (which you did again) if the configure ends in an error.On Jun 18, 2024, at 11:37 AM, philip@gmail.com  wrote:This time i used the correct file but as you can see from the file Im attaching going down your readme file when I get to make it seems to fail so I didnt go any furtherOn Tuesday, June 18, 2024 at 3:49:28 PM UTC+1 philip@gmail.com wrote:OOPs  Yes I didOh well 3rd time luckOn Tuesday, June 18, 2024 at 2:42:45 PM UTC+1 John Kline wrote:> Then used  tar -zxvf xtide-2.15.5.tar.gz and changed to that directoryWhich tar did you use?  You cannot use the file I sent you.On Jun 18, 2024, at 6:24 AM, philip@gmail.com <philip@gmail.com> wrote:Hi JohnBuilt a fresh build using the Raspberry pi imagerLoaded weewx   All OKThen used 

tar -zxvf xtide-2.15.5.tar.gz and changed to that directorythen sudo apt-get install libpng-dev and then sudo apt-get install libtcd-dev./ configureand then make and this time gotmake  all-ammake[1]: Entering directory '/home/phil/xtide-2.15.5'make[1]: Nothing to be done for 'all-am'.make[1]: Leaving directory '/home/phil/xtide-2.15.5'so then sudo apt-get install xtide-dataand then in xtide-2.15.5 folder type tide and gotphil@raspberrypi:~/xtide-2.15.5 $ tidebash: tide: command not foundAs this didnt work I stopped as I believe you said if that does not work its no goodHave put all this in the text file I hope ??On Monday, June 17, 2024 at 7:17:49 PM UTC+1 philip@gmail.com wrote:I use the Raspberry Pi Imager with Pi5 and Pi 5 64 Bit software so Im assuming its the full package.What Im going to do is have a fresh install of Pi5 using the Raspberry Imager and load weewx again and start a fresh with your XTide-=2.15.5.tar.gzI shall copy all terminal responses to this post and see what you think.Im hoping ./configure and then make works.Will send you all terminal responses.Phil On Monday, June 17, 2024 at 6:07:01 PM UTC+1 John Kline wrote:If you try executing tide and it doesn’t work, you need not try anything further.  The problem is the path /home/jkline (my home directory) is hardcoded by configure.You need to be able to build xtide.  If you want to try again, and configure fails again, I can have a look.  Please [re-]confirm that you have installed the prerequisites.  If configure fails again, there is no point to try make.I am surprised that you can’t configure since we’re running the same OS.  I have the lite version of Bookworm 64-bit installed.  Do you have the full version?On Jun 17, 2024, at 9:36 AM, philip@gmail.com <philip@gmail.com> wrote:rm -rf xtide-2.15.5      This removed the directory OKcopied your xtide-2.15.5.tar.gz into my Downloads directory and from that directory tar -zxvf xtide-2.15.5.tar.gzwhich went ok.restarted weewxFrom the xtide-2.15.5 directory  $ tide got thisphil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide/home/phil/xtide-2.15.5/.libs/tide: error while loading shared libraries: libxtide.so.1: cannot open shared object file: No such file or directoryphil@raspberrypi:~ $copied and paste the xtide-2.15.5 directory into my home directory. restarted weewxphil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide/home/phil/xtide-2.15.5/.libs/tide: error while loading shared libraries: libxtide.so.1: cannot open shared object file: No such file or directoryphil@raspberrypi:~ $ After this the log still no tidal eventsOn Monday, June 17, 2024 at 5:00:58 PM UTC+1 John Kline wrote:I got a message that the file was too large.Let’s try again:It is not what I expected.  I’ll give you the whole built directory tree:You can download it at:paloaltoweather.comFrom your home directory, remove the exiting xtide directory, then untar what you just downloaded:rm -rf xtide-2.15.5tar -zxvf xtide-2.15.5.tar.gzNow try executing tide again.  If that works, restart weewx and see if it works.On Jun 17, 2024, at 8:48 AM, John Kline <jo...@johnkline.com> wrote:It is not what I expected.  Here is the whole built directory tree:From your home directory, remove the exiting xtide directory:rm -rf xtide-2.15.5tar -zxvf xtide-2.15.5.tar.gzThen try executing tide again.  If that works, restart weewx and see if it works.On Jun 17, 2024, at 8:04 AM, philip@gmail.com <philip@gmail.com> wrote:phil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide/home/phil/xtide-2.15.5/tide: error: '/home/phil/xtide-2.15.5/.libs/tide' does not existThis script is just a wrapper for tide.See the libtool documentation for more information.Is this what you expected ?On Monday, June 17, 2024 at 3:27:32 PM UTC+1 John Kline wrote:And what happens when you type:/home/phil/xtide-2.15.5/tideon the command line?Does the program run?If so, grep XTideThread in the logs and send the results.  How you look at logs will vary depending on how you have set this up (but probably journalctl).On Jun 17, 2024, at 6:52 AM, philip@gmail.com <philip@gmail.com> wrote:I

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

> Then used  tar -zxvf xtide-2.15.5.tar.gz and changed to that directoryWhich tar did you use?  You cannot use the file I sent you.On Jun 18, 2024, at 6:24 AM, philip@gmail.com  wrote:Hi JohnBuilt a fresh build using the Raspberry pi imagerLoaded weewx   All OKThen used 

tar -zxvf xtide-2.15.5.tar.gz and changed to that directorythen sudo apt-get install libpng-dev and then sudo apt-get install libtcd-dev./ configureand then make and this time gotmake  all-ammake[1]: Entering directory '/home/phil/xtide-2.15.5'make[1]: Nothing to be done for 'all-am'.make[1]: Leaving directory '/home/phil/xtide-2.15.5'so then sudo apt-get install xtide-dataand then in xtide-2.15.5 folder type tide and gotphil@raspberrypi:~/xtide-2.15.5 $ tidebash: tide: command not foundAs this didnt work I stopped as I believe you said if that does not work its no goodHave put all this in the text file I hope ??On Monday, June 17, 2024 at 7:17:49 PM UTC+1 philip@gmail.com wrote:I use the Raspberry Pi Imager with Pi5 and Pi 5 64 Bit software so Im assuming its the full package.What Im going to do is have a fresh install of Pi5 using the Raspberry Imager and load weewx again and start a fresh with your XTide-=2.15.5.tar.gzI shall copy all terminal responses to this post and see what you think.Im hoping ./configure and then make works.Will send you all terminal responses.Phil On Monday, June 17, 2024 at 6:07:01 PM UTC+1 John Kline wrote:If you try executing tide and it doesn’t work, you need not try anything further.  The problem is the path /home/jkline (my home directory) is hardcoded by configure.You need to be able to build xtide.  If you want to try again, and configure fails again, I can have a look.  Please [re-]confirm that you have installed the prerequisites.  If configure fails again, there is no point to try make.I am surprised that you can’t configure since we’re running the same OS.  I have the lite version of Bookworm 64-bit installed.  Do you have the full version?On Jun 17, 2024, at 9:36 AM, philip@gmail.com <philip@gmail.com> wrote:rm -rf xtide-2.15.5      This removed the directory OKcopied your xtide-2.15.5.tar.gz into my Downloads directory and from that directory tar -zxvf xtide-2.15.5.tar.gzwhich went ok.restarted weewxFrom the xtide-2.15.5 directory  $ tide got thisphil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide/home/phil/xtide-2.15.5/.libs/tide: error while loading shared libraries: libxtide.so.1: cannot open shared object file: No such file or directoryphil@raspberrypi:~ $copied and paste the xtide-2.15.5 directory into my home directory. restarted weewxphil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide/home/phil/xtide-2.15.5/.libs/tide: error while loading shared libraries: libxtide.so.1: cannot open shared object file: No such file or directoryphil@raspberrypi:~ $ After this the log still no tidal eventsOn Monday, June 17, 2024 at 5:00:58 PM UTC+1 John Kline wrote:I got a message that the file was too large.Let’s try again:It is not what I expected.  I’ll give you the whole built directory tree:You can download it at:paloaltoweather.comFrom your home directory, remove the exiting xtide directory, then untar what you just downloaded:rm -rf xtide-2.15.5tar -zxvf xtide-2.15.5.tar.gzNow try executing tide again.  If that works, restart weewx and see if it works.On Jun 17, 2024, at 8:48 AM, John Kline <jo...@johnkline.com> wrote:It is not what I expected.  Here is the whole built directory tree:From your home directory, remove the exiting xtide directory:rm -rf xtide-2.15.5tar -zxvf xtide-2.15.5.tar.gzThen try executing tide again.  If that works, restart weewx and see if it works.On Jun 17, 2024, at 8:04 AM, philip@gmail.com <philip@gmail.com> wrote:phil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide/home/phil/xtide-2.15.5/tide: error: '/home/phil/xtide-2.15.5/.libs/tide' does not existThis script is just a wrapper for tide.See the libtool documentation for more information.Is this what you expected ?On Monday, June 17, 2024 at 3:27:32 PM UTC+1 John Kline wrote:And what happens when you type:/home/phil/xtide-2.15.5/tideon the command line?Does the program run?If so, grep XTideThread in the logs and send the results.  How you look at logs will vary depending on how you have set this up (but probably journalctl).On Jun 17, 2024, at 6:52 AM, philip@gmail.com <philip@gmail.com> wrote:If you look at my 1015 post it has this in itcreated /etc/xtide.confAdded /usr/share/xtide   into the file Ive sent you my weewx.conf file it has prog = /home/phil/xtide-2.15.5/tide  in it I forgot to add it to my 1015 postOn Monday, June 17, 2024 at 2:26:28 PM UTC+1 John Kline wrote:I don’t see a “prog = “ line in the XTide section (per my instructions).  Did you do that?And did you create a /etc/xtide.conf file?Would you please follow the instructions line by line?On Jun 17, 2024, at 2:26 AM, philip@gmail.com <philip@gmail.com> wrote:Sorry sent to 

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

If you try executing tide and it doesn’t work, you need not try anything further.  The problem is the path /home/jkline (my home directory) is hardcoded by configure.You need to be able to build xtide.  If you want to try again, and configure fails again, I can have a look.  Please [re-]confirm that you have installed the prerequisites.  If configure fails again, there is no point to try make.I am surprised that you can’t configure since we’re running the same OS.  I have the lite version of Bookworm 64-bit installed.  Do you have the full version?On Jun 17, 2024, at 9:36 AM, philip@gmail.com  wrote:rm -rf xtide-2.15.5      This removed the directory OKcopied your xtide-2.15.5.tar.gz into my Downloads directory and from that directory tar -zxvf xtide-2.15.5.tar.gzwhich went ok.restarted weewxFrom the xtide-2.15.5 directory  $ tide got thisphil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide/home/phil/xtide-2.15.5/.libs/tide: error while loading shared libraries: libxtide.so.1: cannot open shared object file: No such file or directoryphil@raspberrypi:~ $copied and paste the xtide-2.15.5 directory into my home directory. restarted weewxphil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide/home/phil/xtide-2.15.5/.libs/tide: error while loading shared libraries: libxtide.so.1: cannot open shared object file: No such file or directoryphil@raspberrypi:~ $ After this the log still no tidal eventsOn Monday, June 17, 2024 at 5:00:58 PM UTC+1 John Kline wrote:I got a message that the file was too large.Let’s try again:It is not what I expected.  I’ll give you the whole built directory tree:You can download it at:paloaltoweather.comFrom your home directory, remove the exiting xtide directory, then untar what you just downloaded:rm -rf xtide-2.15.5tar -zxvf xtide-2.15.5.tar.gzNow try executing tide again.  If that works, restart weewx and see if it works.On Jun 17, 2024, at 8:48 AM, John Kline <jo...@johnkline.com> wrote:It is not what I expected.  Here is the whole built directory tree:From your home directory, remove the exiting xtide directory:rm -rf xtide-2.15.5tar -zxvf xtide-2.15.5.tar.gzThen try executing tide again.  If that works, restart weewx and see if it works.On Jun 17, 2024, at 8:04 AM, philip@gmail.com <philip@gmail.com> wrote:phil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide/home/phil/xtide-2.15.5/tide: error: '/home/phil/xtide-2.15.5/.libs/tide' does not existThis script is just a wrapper for tide.See the libtool documentation for more information.Is this what you expected ?On Monday, June 17, 2024 at 3:27:32 PM UTC+1 John Kline wrote:And what happens when you type:/home/phil/xtide-2.15.5/tideon the command line?Does the program run?If so, grep XTideThread in the logs and send the results.  How you look at logs will vary depending on how you have set this up (but probably journalctl).On Jun 17, 2024, at 6:52 AM, philip@gmail.com <philip@gmail.com> wrote:If you look at my 1015 post it has this in itcreated /etc/xtide.confAdded /usr/share/xtide   into the file Ive sent you my weewx.conf file it has prog = /home/phil/xtide-2.15.5/tide  in it I forgot to add it to my 1015 postOn Monday, June 17, 2024 at 2:26:28 PM UTC+1 John Kline wrote:I don’t see a “prog = “ line in the XTide section (per my instructions).  Did you do that?And did you create a /etc/xtide.conf file?Would you please follow the instructions line by line?On Jun 17, 2024, at 2:26 AM, philip@gmail.com <philip@gmail.com> wrote:Sorry sent to earlyThought that your file needs to be an executable so from the xtide-2.15.5 directorysudo chmod +x tideStill no tidal eventsOn Monday, June 17, 2024 at 10:23:15 AM UTC+1 philip@gmail.com wrote:Thought that your file needs to be an executable so from the xtide-2.15.5 directoryOn Monday, June 17, 2024 at 10:15:51 AM UTC+1 philip@gmail.com wrote:Hi JohnStill no joyUnzipped your file and loaded it into directory xtide-2.15.5 as tideIn weewx.conf under [[XTide]] prog = /home/phil/xtide-2.25.5/tideThen carried on from your readme notessudo apt install xtide-datasudp apt instal xtide-data-nonfreeBoth loaded OKcreated /etc/xtide.confAdded /usr/share/xtide   into the file The 2 harmonics exixts in /usr/share/xtide    harmonics-dwf-20100529-nonfree.tcd  and  harmonics-dwf-20191229-free.tcd In the weewx.conf under [[XTide]] added location = "Cromer, England"interval = 86400duration = 86400max_age = 86400sudo systemctl restart weewxsudo systemctl status weewx2 lines for xtideThreaduser.forecast: XTideThread: XTide: generating tides from 2024-06-17 00:00:: BST (1718578800)) to 2024-06-18 00:00:00 (1718665200)user.forecast: XTideThread: XTide: got no tidal eventsChange the location to whats in your readme noteslocation = "Palo Alto Yacht Club Harbor, San Francisco Bay, California"Still no tidal eventsPhilOn Sunday, June 16, 2024 at 9:39:16 PM UTC+1 John Kline wrote:Philip,Rather than try to walk you through building a package, attac

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

I got a message that the file was too large.Let’s try again:It is not what I expected.  I’ll give you the whole built directory tree:You can download it at:paloaltoweather.comFrom your home directory, remove the exiting xtide directory, then untar what you just downloaded:rm -rf xtide-2.15.5tar -zxvf xtide-2.15.5.tar.gzNow try executing tide again.  If that works, restart weewx and see if it works.On Jun 17, 2024, at 8:48 AM, John Kline  wrote:It is not what I expected.  Here is the whole built directory tree:From your home directory, remove the exiting xtide directory:rm -rf xtide-2.15.5tar -zxvf xtide-2.15.5.tar.gzThen try executing tide again.  If that works, restart weewx and see if it works.On Jun 17, 2024, at 8:04 AM, philip@gmail.com  wrote:phil@raspberrypi:~ $ /home/phil/xtide-2.15.5/tide/home/phil/xtide-2.15.5/tide: error: '/home/phil/xtide-2.15.5/.libs/tide' does not existThis script is just a wrapper for tide.See the libtool documentation for more information.Is this what you expected ?On Monday, June 17, 2024 at 3:27:32 PM UTC+1 John Kline wrote:And what happens when you type:/home/phil/xtide-2.15.5/tideon the command line?Does the program run?If so, grep XTideThread in the logs and send the results.  How you look at logs will vary depending on how you have set this up (but probably journalctl).On Jun 17, 2024, at 6:52 AM, philip@gmail.com <philip@gmail.com> wrote:If you look at my 1015 post it has this in itcreated /etc/xtide.confAdded /usr/share/xtide   into the file Ive sent you my weewx.conf file it has prog = /home/phil/xtide-2.15.5/tide  in it I forgot to add it to my 1015 postOn Monday, June 17, 2024 at 2:26:28 PM UTC+1 John Kline wrote:I don’t see a “prog = “ line in the XTide section (per my instructions).  Did you do that?And did you create a /etc/xtide.conf file?Would you please follow the instructions line by line?On Jun 17, 2024, at 2:26 AM, philip@gmail.com <philip@gmail.com> wrote:Sorry sent to earlyThought that your file needs to be an executable so from the xtide-2.15.5 directorysudo chmod +x tideStill no tidal eventsOn Monday, June 17, 2024 at 10:23:15 AM UTC+1 philip@gmail.com wrote:Thought that your file needs to be an executable so from the xtide-2.15.5 directoryOn Monday, June 17, 2024 at 10:15:51 AM UTC+1 philip@gmail.com wrote:Hi JohnStill no joyUnzipped your file and loaded it into directory xtide-2.15.5 as tideIn weewx.conf under [[XTide]] prog = /home/phil/xtide-2.25.5/tideThen carried on from your readme notessudo apt install xtide-datasudp apt instal xtide-data-nonfreeBoth loaded OKcreated /etc/xtide.confAdded /usr/share/xtide   into the file The 2 harmonics exixts in /usr/share/xtide    harmonics-dwf-20100529-nonfree.tcd  and  harmonics-dwf-20191229-free.tcd In the weewx.conf under [[XTide]] added location = "Cromer, England"interval = 86400duration = 86400max_age = 86400sudo systemctl restart weewxsudo systemctl status weewx2 lines for xtideThreaduser.forecast: XTideThread: XTide: generating tides from 2024-06-17 00:00:: BST (1718578800)) to 2024-06-18 00:00:00 (1718665200)user.forecast: XTideThread: XTide: got no tidal eventsChange the location to whats in your readme noteslocation = "Palo Alto Yacht Club Harbor, San Francisco Bay, California"Still no tidal eventsPhilOn Sunday, June 16, 2024 at 9:39:16 PM UTC+1 John Kline wrote:Philip,Rather than try to walk you through building a package, attached is a zip of the tide executable that you need.unzip it anywhere you like and point to it by following the instructions on the README page in github or in my email.



-- 
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/c1ba817f-198b-45a4-bfaa-96312756108en%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/985974b1-b378-4b69-845f-fa9f4cb550ffn%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/5c7d44a5-634b-4aa6-b7d8-4ca5b16fb735n%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

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

And what happens when you type:/home/phil/xtide-2.15.5/tideon the command line?Does the program run?If so, grep XTideThread in the logs and send the results.  How you look at logs will vary depending on how you have set this up (but probably journalctl).On Jun 17, 2024, at 6:52 AM, philip@gmail.com  wrote:If you look at my 1015 post it has this in itcreated /etc/xtide.confAdded /usr/share/xtide   into the file Ive sent you my weewx.conf file it has prog = /home/phil/xtide-2.15.5/tide  in it I forgot to add it to my 1015 postOn Monday, June 17, 2024 at 2:26:28 PM UTC+1 John Kline wrote:I don’t see a “prog = “ line in the XTide section (per my instructions).  Did you do that?And did you create a /etc/xtide.conf file?Would you please follow the instructions line by line?On Jun 17, 2024, at 2:26 AM, philip@gmail.com <philip@gmail.com> wrote:Sorry sent to earlyThought that your file needs to be an executable so from the xtide-2.15.5 directorysudo chmod +x tideStill no tidal eventsOn Monday, June 17, 2024 at 10:23:15 AM UTC+1 philip@gmail.com wrote:Thought that your file needs to be an executable so from the xtide-2.15.5 directoryOn Monday, June 17, 2024 at 10:15:51 AM UTC+1 philip@gmail.com wrote:Hi JohnStill no joyUnzipped your file and loaded it into directory xtide-2.15.5 as tideIn weewx.conf under [[XTide]] prog = /home/phil/xtide-2.25.5/tideThen carried on from your readme notessudo apt install xtide-datasudp apt instal xtide-data-nonfreeBoth loaded OKcreated /etc/xtide.confAdded /usr/share/xtide   into the file The 2 harmonics exixts in /usr/share/xtide    harmonics-dwf-20100529-nonfree.tcd  and  harmonics-dwf-20191229-free.tcd In the weewx.conf under [[XTide]] added location = "Cromer, England"interval = 86400duration = 86400max_age = 86400sudo systemctl restart weewxsudo systemctl status weewx2 lines for xtideThreaduser.forecast: XTideThread: XTide: generating tides from 2024-06-17 00:00:: BST (1718578800)) to 2024-06-18 00:00:00 (1718665200)user.forecast: XTideThread: XTide: got no tidal eventsChange the location to whats in your readme noteslocation = "Palo Alto Yacht Club Harbor, San Francisco Bay, California"Still no tidal eventsPhilOn Sunday, June 16, 2024 at 9:39:16 PM UTC+1 John Kline wrote:Philip,Rather than try to walk you through building a package, attached is a zip of the tide executable that you need.unzip it anywhere you like and point to it by following the instructions on the README page in github or in my email.



-- 
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/c1ba817f-198b-45a4-bfaa-96312756108en%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/985974b1-b378-4b69-845f-fa9f4cb550ffn%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/C9990148-4DCB-4EAB-B1BF-C48DD25561A2%40johnkline.com.

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

I don’t see a “prog = “ line in the XTide section (per my instructions).  Did you do that?And did you create a /etc/xtide.conf file?Would you please follow the instructions line by line?On Jun 17, 2024, at 2:26 AM, philip@gmail.com  wrote:Sorry sent to earlyThought that your file needs to be an executable so from the xtide-2.15.5 directorysudo chmod +x tideStill no tidal eventsOn Monday, June 17, 2024 at 10:23:15 AM UTC+1 philip@gmail.com wrote:Thought that your file needs to be an executable so from the xtide-2.15.5 directoryOn Monday, June 17, 2024 at 10:15:51 AM UTC+1 philip@gmail.com wrote:Hi JohnStill no joyUnzipped your file and loaded it into directory xtide-2.15.5 as tideIn weewx.conf under [[XTide]] prog = /home/phil/xtide-2.25.5/tideThen carried on from your readme notessudo apt install xtide-datasudp apt instal xtide-data-nonfreeBoth loaded OKcreated /etc/xtide.confAdded /usr/share/xtide   into the file The 2 harmonics exixts in /usr/share/xtide    harmonics-dwf-20100529-nonfree.tcd  and  harmonics-dwf-20191229-free.tcd In the weewx.conf under [[XTide]] added location = "Cromer, England"interval = 86400duration = 86400max_age = 86400sudo systemctl restart weewxsudo systemctl status weewx2 lines for xtideThreaduser.forecast: XTideThread: XTide: generating tides from 2024-06-17 00:00:: BST (1718578800)) to 2024-06-18 00:00:00 (1718665200)user.forecast: XTideThread: XTide: got no tidal eventsChange the location to whats in your readme noteslocation = "Palo Alto Yacht Club Harbor, San Francisco Bay, California"Still no tidal eventsPhilOn Sunday, June 16, 2024 at 9:39:16 PM UTC+1 John Kline wrote:Philip,Rather than try to walk you through building a package, attached is a zip of the tide executable that you need.unzip it anywhere you like and point to it by following the instructions on the README page in github or in my email.



-- 
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/c1ba817f-198b-45a4-bfaa-96312756108en%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/37F9112B-330A-4090-8F7D-71272D982CA3%40johnkline.com.

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

Philip,Rather than try to walk you through building a package, attached is a zip of the tide executable that you need.unzip it anywhere you like and point to it by following the instructions on the README page in github or in my email.



-- 
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/63D152E9-E2DA-4EDC-BC0D-57891AB513D3%40johnkline.com.
<>
Note: this executable was built for Raspberry Pi OS bookworm 64-bit.  Don’t try to use it elsewhere.On Jun 16, 2024, at 12:58 PM, John Kline  wrote:configure generates a Makefile (with no extensions).Take a look at what you sent me, configure ended in an error.  Look right before you typed make!Did you install the prerequisite packages listed?I have this running on 64-bit Raspberry OS Bookworm.On Jun 16, 2024, at 12:40 PM, philip@gmail.com  wrote:Theres a Makefile.am and Makefile.in in the xtide-2.15.5 directoryHere are the lines from the terminalOn Sunday, June 16, 2024 at 8:20:51 PM UTC+1 John Kline wrote:Also, are we sure the configure finished without error (there are dependencies you need to install as stated in my instructions)?Do you see a file named Makefile in the xtide-2.15.5 directory?On Jun 16, 2024, at 12:18 PM, John Kline <jo...@johnkline.com> wrote:> Im trying yours again John and its OK when I do ./configure but when I try   make     it > replies>make: ***No targets specified and no makefile found. Stop>I take it thats not what I should get backThat’s hard to imagine if you are in the correct directory.  Exactly what directory were you in when you typed make?On Jun 16, 2024, at 11:41 AM, philip@gmail.com <philip@gmail.com> wrote:Im trying yours again John and its OK when I do ./configure but when I try   make     it repliesmake: ***No targets specified and no makefile found. StopI take it thats not what I should get backPhilOn Sunday, June 16, 2024 at 6:44:59 PM UTC+1 philip@gmail.com wrote:Im using the latest 64bit Debian 12 Bookworm on a Pi5 and building weewx V5 on a new installation.My first extension to load was the forecast extension and when i type sudo apt-get install xtideit tells me the package is not available is only available from another source so logs are not availableI downloaded from https://github.com/chaunceygardiner/weewx-forecast John and I did try and follow your update but I couldnt get it to workIt told me NO TIDE data was available.On Sunday, June 16, 2024 at 6:18:24 PM UTC+1 vince wrote:In the absence of any logs... or console transcripts... or snippets from your weewx.conf file... sorry, nobody can help muchOn Sunday, June 16, 2024 at 10:09:59 AM UTC-7 philip@gmail.com wrote:Im loading weewx V5 from new and while installing the forecast program I notice that XTides is no longer available.Can somebody point me in the right direction please as to how I can get XTides to workThanks



-- 
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/edc25c54-ae94-4304-b6a2-8d34317b034dn%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/c5a84c9f-a94d-49e1-bf92-ef18002ffd24n%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/63D152E9-E2DA-4EDC-BC0D-57891AB513D3%40johnkline.com.

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

Yes, xtide-data installs, and is needed (per the README), but it is xtide itself that is not available.On Jun 16, 2024, at 1:23 PM, vince  wrote:On a pi5 with 64bit bookworm this worked.sudo apt-get install -y libpng-dev libtcd-dev xtide-data xtide-coastline xtide-data-nonfreewget http://deb.debian.org/debian/pool/main/x/xtide/xtide_2.15.2.orig.tar.bz2tar jxvf xtide_2.15.2.orig.tar.bz2cd xtide-2.15.2./configure --without-xmakesudo make installsudo ldconfig         # optional but doesn't hurttide -l SEATTLE(returns the tide estimates for seattle)On Sunday, June 16, 2024 at 12:58:30 PM UTC-7 John Kline wrote:configure generates a Makefile (with no extensions).Take a look at what you sent me, configure ended in an error.  Look right before you typed make!Did you install the prerequisite packages listed?I have this running on 64-bit Raspberry OS Bookworm.On Jun 16, 2024, at 12:40 PM, philip@gmail.com <philip@gmail.com> wrote:Theres a Makefile.am and Makefile.in in the xtide-2.15.5 directoryHere are the lines from the terminalOn Sunday, June 16, 2024 at 8:20:51 PM UTC+1 John Kline wrote:Also, are we sure the configure finished without error (there are dependencies you need to install as stated in my instructions)?Do you see a file named Makefile in the xtide-2.15.5 directory?On Jun 16, 2024, at 12:18 PM, John Kline <jo...@johnkline.com> wrote:> Im trying yours again John and its OK when I do ./configure but when I try   make     it > replies>make: ***No targets specified and no makefile found. Stop>I take it thats not what I should get backThat’s hard to imagine if you are in the correct directory.  Exactly what directory were you in when you typed make?On Jun 16, 2024, at 11:41 AM, philip@gmail.com <philip@gmail.com> wrote:Im trying yours again John and its OK when I do ./configure but when I try   make     it repliesmake: ***No targets specified and no makefile found. StopI take it thats not what I should get backPhilOn Sunday, June 16, 2024 at 6:44:59 PM UTC+1 philip@gmail.com wrote:Im using the latest 64bit Debian 12 Bookworm on a Pi5 and building weewx V5 on a new installation.My first extension to load was the forecast extension and when i type sudo apt-get install xtideit tells me the package is not available is only available from another source so logs are not availableI downloaded from https://github.com/chaunceygardiner/weewx-forecast John and I did try and follow your update but I couldnt get it to workIt told me NO TIDE data was available.On Sunday, June 16, 2024 at 6:18:24 PM UTC+1 vince wrote:In the absence of any logs... or console transcripts... or snippets from your weewx.conf file... sorry, nobody can help muchOn Sunday, June 16, 2024 at 10:09:59 AM UTC-7 philip@gmail.com wrote:Im loading weewx V5 from new and while installing the forecast program I notice that XTides is no longer available.Can somebody point me in the right direction please as to how I can get XTides to workThanks



-- 
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/edc25c54-ae94-4304-b6a2-8d34317b034dn%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/c5a84c9f-a94d-49e1-bf92-ef18002ffd24n%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/4fd86ba7-9694-4637-a209-9c64ec23f5e9n%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/18E5BB9D-7C7B-41C4-9224-AFFC3EA2B4A0%40johnkline.com.

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

configure generates a Makefile (with no extensions).Take a look at what you sent me, configure ended in an error.  Look right before you typed make!Did you install the prerequisite packages listed?I have this running on 64-bit Raspberry OS Bookworm.On Jun 16, 2024, at 12:40 PM, philip@gmail.com  wrote:Theres a Makefile.am and Makefile.in in the xtide-2.15.5 directoryHere are the lines from the terminalOn Sunday, June 16, 2024 at 8:20:51 PM UTC+1 John Kline wrote:Also, are we sure the configure finished without error (there are dependencies you need to install as stated in my instructions)?Do you see a file named Makefile in the xtide-2.15.5 directory?On Jun 16, 2024, at 12:18 PM, John Kline <jo...@johnkline.com> wrote:> Im trying yours again John and its OK when I do ./configure but when I try   make     it > replies>make: ***No targets specified and no makefile found. Stop>I take it thats not what I should get backThat’s hard to imagine if you are in the correct directory.  Exactly what directory were you in when you typed make?On Jun 16, 2024, at 11:41 AM, philip@gmail.com <philip@gmail.com> wrote:Im trying yours again John and its OK when I do ./configure but when I try   make     it repliesmake: ***No targets specified and no makefile found. StopI take it thats not what I should get backPhilOn Sunday, June 16, 2024 at 6:44:59 PM UTC+1 philip@gmail.com wrote:Im using the latest 64bit Debian 12 Bookworm on a Pi5 and building weewx V5 on a new installation.My first extension to load was the forecast extension and when i type sudo apt-get install xtideit tells me the package is not available is only available from another source so logs are not availableI downloaded from https://github.com/chaunceygardiner/weewx-forecast John and I did try and follow your update but I couldnt get it to workIt told me NO TIDE data was available.On Sunday, June 16, 2024 at 6:18:24 PM UTC+1 vince wrote:In the absence of any logs... or console transcripts... or snippets from your weewx.conf file... sorry, nobody can help muchOn Sunday, June 16, 2024 at 10:09:59 AM UTC-7 philip@gmail.com wrote:Im loading weewx V5 from new and while installing the forecast program I notice that XTides is no longer available.Can somebody point me in the right direction please as to how I can get XTides to workThanks



-- 
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/edc25c54-ae94-4304-b6a2-8d34317b034dn%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/c5a84c9f-a94d-49e1-bf92-ef18002ffd24n%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/64B67B7D-9F36-4B9E-84E7-5A07717CED20%40johnkline.com.

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

Also, are we sure the configure finished without error (there are dependencies you need to install as stated in my instructions)?Do you see a file named Makefile in the xtide-2.15.5 directory?On Jun 16, 2024, at 12:18 PM, John Kline  wrote:> Im trying yours again John and its OK when I do ./configure but when I try   make     it > replies>make: ***No targets specified and no makefile found. Stop>I take it thats not what I should get backThat’s hard to imagine if you are in the correct directory.  Exactly what directory were you in when you typed make?On Jun 16, 2024, at 11:41 AM, philip@gmail.com  wrote:Im trying yours again John and its OK when I do ./configure but when I try   make     it repliesmake: ***No targets specified and no makefile found. StopI take it thats not what I should get backPhilOn Sunday, June 16, 2024 at 6:44:59 PM UTC+1 philip@gmail.com wrote:Im using the latest 64bit Debian 12 Bookworm on a Pi5 and building weewx V5 on a new installation.My first extension to load was the forecast extension and when i type sudo apt-get install xtideit tells me the package is not available is only available from another source so logs are not availableI downloaded from https://github.com/chaunceygardiner/weewx-forecast John and I did try and follow your update but I couldnt get it to workIt told me NO TIDE data was available.On Sunday, June 16, 2024 at 6:18:24 PM UTC+1 vince wrote:In the absence of any logs... or console transcripts... or snippets from your weewx.conf file... sorry, nobody can help muchOn Sunday, June 16, 2024 at 10:09:59 AM UTC-7 philip@gmail.com wrote:Im loading weewx V5 from new and while installing the forecast program I notice that XTides is no longer available.Can somebody point me in the right direction please as to how I can get XTides to workThanks



-- 
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/edc25c54-ae94-4304-b6a2-8d34317b034dn%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/7AF69A6F-56DA-4645-8ADD-405B85BE12AB%40johnkline.com.

Re: [weewx-user] Re: Loading Xtides with Forecast

['John Kline' via weewx-user]

> Im trying yours again John and its OK when I do ./configure but when I try   make     it > replies>make: ***No targets specified and no makefile found. Stop>I take it thats not what I should get backThat’s hard to imagine if you are in the correct directory.  Exactly what directory were you in when you typed make?On Jun 16, 2024, at 11:41 AM, philip@gmail.com  wrote:Im trying yours again John and its OK when I do ./configure but when I try   make     it repliesmake: ***No targets specified and no makefile found. StopI take it thats not what I should get backPhilOn Sunday, June 16, 2024 at 6:44:59 PM UTC+1 philip@gmail.com wrote:Im using the latest 64bit Debian 12 Bookworm on a Pi5 and building weewx V5 on a new installation.My first extension to load was the forecast extension and when i type sudo apt-get install xtideit tells me the package is not available is only available from another source so logs are not availableI downloaded from https://github.com/chaunceygardiner/weewx-forecast John and I did try and follow your update but I couldnt get it to workIt told me NO TIDE data was available.On Sunday, June 16, 2024 at 6:18:24 PM UTC+1 vince wrote:In the absence of any logs... or console transcripts... or snippets from your weewx.conf file... sorry, nobody can help muchOn Sunday, June 16, 2024 at 10:09:59 AM UTC-7 philip@gmail.com wrote:Im loading weewx V5 from new and while installing the forecast program I notice that XTides is no longer available.Can somebody point me in the right direction please as to how I can get XTides to workThanks



-- 
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/edc25c54-ae94-4304-b6a2-8d34317b034dn%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/DD3CCA71-A033-4328-9C5C-CF760BF62DAC%40johnkline.com.

Re: [weewx-user] Loading Xtides with Forecast

['John Kline' via weewx-user]

Which version of weewx-forecast are you using?  I mention this issue and how to work around it in the README of my fork of weewx-forecast (https://github.com/chaunceygardiner/weewx-forecast):If you want tide forecasts, install xtides:
  sudo apt-get install xtide
Then determine your location:
  http://tides.mobilegeographics.com/

Note: current versions of debian (bookworm) do not include xtide.
This is perhaps true of other distributions.
You'll need to build it yourself and set the 'prog' variable in the xtide
section.
Example (building xtide)
  wget https://flaterco.com/files/xtide/xtide-2.15.5.tar.xz
  (decompress and cd to directory)
  sudo apt-get install libpng-dev
  sudo apt-get install libtcd-dev
  ./configure
  make
Example (setting prog variable t point to where you have built xtide):
[Forecast]
...
[[XTide]]
location = Palo Alto Yacht Harbor, San Francisco Bay, California
prog = /home/jkline/software/xtide-2.15.5/tide
You'll still need to install xtide-data.  Example:
apt install xtide-data
and you'll need to create an /etc/xtide.conf file to tell xtide where to find the harmonic
data you installed with xtide-data.  Example:
/etc/xtide.conf:
/usr/share/xtide
(xtide-data installs harmonic data in the /usr/share/xtide directory)
On Jun 16, 2024, at 10:10 AM, philip@gmail.com  wrote:Im loading weewx V5 from new and while installing the forecast program I notice that XTides is no longer available.Can somebody point me in the right direction please as to how I can get XTides to workThanks



-- 
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/72de0fa6-e933-4fb3-a6ef-958af37a00b7n%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/D82CF08F-CF5F-4206-A131-2CA847681879%40johnkline.com.

Re: [weewx-user] Purple-Air causes imagegenerator crash in 5.0.2 but not in 4

['John Kline' via weewx-user]

Thanks for trying it.  I’ve release v3.9.2 with the fix.On Apr 29, 2024, at 10:04 PM, Clay Jackson  wrote:This version works perfectly!On Monday, April 29, 2024 at 6:39:44 PM UTC-7 John Kline wrote:It’s my extension.  MySQL doesn’t like the select when sql_mode=only_full_group_by.clayj, please replace purple.py with the attached file.  If it works for you, I’ll release it as v3.9.2.



-- 
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/79503a55-1a42-43db-9122-3225604af037n%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/8DC9BA5D-7C85-46A0-B4B6-44A2654FC6DB%40johnkline.com.

Re: [weewx-user] Purple-Air causes imagegenerator crash in 5.0.2 but not in 4

['John Kline' via weewx-user]

It’s my extension.  MySQL doesn’t like the select when sql_mode=only_full_group_by.clayj, please replace purple.py with the attached file.  If it works for you, I’ll release it as v3.9.2.



-- 
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/2C5B0FC9-FD72-4FAF-B2E8-9C57D7D5B158%40johnkline.com.


purple.py
Description: Binary data
On Apr 29, 2024, at 4:48 PM, Tom Keffer  wrote:It looks like the "purple" extension is trying to aggregate by groups, but asking for a non-aggregated value for 'usUnits'. What extension is this? The purple air extension I see on the wiki uses the module "user.purpleair", not "user.purple".On Mon, Apr 29, 2024 at 4:37 PM Clay Jackson  wrote:I'm updating from WeeWx Version 4 to 5.0.2 and when I do, the sample dashboard for Purple causes imgagegenerator to crash - here's the output from syslog.Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine: Caught unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  (1140, "In aggregated query without GROUP BY, _expression_ #2 of SELECT list contains nonaggregated column 'weewx.archive.usUnits'; this is incompatible with sql_mode=only_full_group_by")Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  Traceback (most recent call last):Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File "/home/weewx/weewx-venv/lib/python3.10/site-packages/weewx/xtypes.py", line 109, in get_seriesApr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  return xtype.get_series(obs_type, timespan, db_manager, aggregate_type,Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  TypeError: AQI.get_series() got an unexpected keyword argument 'SKIN_ROOT'Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine: Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  During handling of the above exception, another exception occurred:Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine: Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  Traceback (most recent call last):Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File "/home/weewx/weewx-venv/lib/python3.10/site-packages/weedb/mysql.py", line 53, in guarded_fnApr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  return fn(*args, **kwargs)Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File "/home/weewx/weewx-venv/lib/python3.10/site-packages/weedb/mysql.py", line 247, in executeApr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  self.cursor.execute(mysql_string, tuple(sql_tuple))Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File "/home/weewx/weewx-venv/lib/python3.10/site-packages/pymysql/cursors.py", line 153, in executeApr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  result = self._query(query)Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File "/home/weewx/weewx-venv/lib/python3.10/site-packages/pymysql/cursors.py", line 322, in _queryApr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  conn.query(q)Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File "/home/weewx/weewx-venv/lib/python3.10/site-packages/pymysql/connections.py", line 558, in queryApr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  self._affected_rows = self._read_query_result(unbuffered=unbuffered)Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File "/home/weewx/weewx-venv/lib/python3.10/site-packages/pymysql/connections.py", line 822, in _read_query_resultApr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  result.read()Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File "/home/weewx/weewx-venv/lib/python3.10/site-packages/pymysql/connections.py", line 1200, in readApr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  first_packet = self.connection._read_packet()Apr 29 16:26:12 weewx weewxd[2282]: ERROR weewx.reportengine:  File "/home/weewx/weewx-venv/lib/python3.10/site-packages/pymysql/connections.py", line 772, in _read_packetApr 29 16:26:12 weewx python3[2282]: Traceback (most recent call last):Apr 29 16:26:12 weewx python3[2282]: File "/home/weewx/weewx-venv/lib/python3.10/site-packages/weewx/xtypes.py", line 109, in get_seriesApr 29 16:26:12 weewx python3[2282]: return xtype.get_series(obs_type, timespan, db_manager, aggregate_type,Apr 29 16:26:12 weewx python3[2282]: TypeError: AQI.get_series() got an unexpected keyword argument 'SKIN_ROOT'Apr 29 16:26:12 weewx python3[2282]: During handling of the above exception, another exception 

Re: [weewx-user] Re: Exclude list or Overwrite behaviour for RSync Report

['John Kline' via weewx-user]

The reason to have backward compatibility would be to not break people on a point release. On Apr 2, 2024, at 6:35 PM, vince  wrote:Agree that one way to do it would be ideal, unless there are backward compatibility reasons to leave the current switches 'also' valid.  I guess it would be possible to tear apart a hypothetical rsync_options="whatever here" string to not break folks, but I didn't want to write the code this time, just suggest where it might be doable to at least think about as a feature addition.On Tuesday, April 2, 2024 at 4:08:26 PM UTC-7 John Kline wrote:The problem with an rsync_options (similar to the existing ssh_options) is that the code already has rsync options specified individually (e.g., delete and compress).  It would be messy to have two ways to specify delete and compress.It might be best to add an explicit exclude option.  BTW, exclude can be specified multiple times, so the value should be an array.On Apr 2, 2024, at 11:56 AM, Chris Alemany <chri...@gmail.com> wrote:Hmm, both strategies have advantages. It'd be great if weewx had the ability to add in rsync options so that if you just wanted to do a single thing, exclude a directory, or maybe conform to a specific non-standard setting on the remote host, then you can easily do that in weewx.The extension is nice to have to create a full suite of rsync options so people can use it to backup stuff, move stuff, etc.I've created a GitHub issue/requesthttps://github.com/weewx/weewx/issues/951Thanks to you both.ChrisOn Tuesday, April 2, 2024 at 8:30:30 AM UTC-7 vince wrote:Seems complicated.  I was suggesting something like adding a general purpose 'rsync_options' variable in that section of weewx.conf, and adding the value  to the assembled rsync command in the run(self) routine in rsyncupload.py ?     Then the user could add any combination of the rsync options to the command if needed.   Perhaps something like the following (untested):pi@pi4:/tmp$ diff rsyncupload.py.orig rsyncupload.py -u--- rsyncupload.py.orig	2024-04-02 08:18:48.311469290 -0700+++ rsyncupload.py	2024-04-02 08:19:57.970078706 -0700@@ -46,6 +46,7 @@         self.delete = delete         self.port = port         self.ssh_options = ssh_options+        self.rsync_options = rsync_options   # <== new         self.compress = compress         self.log_success = log_success         self.log_failure = log_failure@@ -96,6 +97,7 @@         if self.timeout is not None:             cmd.extend(["--timeout=%s" % self.timeout])         cmd.extend(["-e"])+        cmd.extend([rsync_options])    # <=== new         cmd.extend([rsyncsshstring])         cmd.extend([rsynclocalspec])         cmd.extend([rsyncremotespec])And add a rsync_options = "whatever you want here" to the [[RSYNC]] section in weewx.conf ala:   [[RSYNC]]        delete = 0        skin = Rsync        enable = true        server = x.x.x.x         user = myremoteuser        path = /my/remote/path/here        log_success = true        log_failure = true        rsync_options = "-x -y -z whatever"       # <=== newDisclaimer - totally untested and no idea if there are security risks of doing it this way, but it would seem to be about as flexible as you can get toward supporting whatever rsync options the underlying os supports with a minimum of change to the existing uploaderOn Tuesday, April 2, 2024 at 1:17:58 AM UTC-7 Glenn McKechnie wrote:On Tue, 2 Apr 2024 at 15:00, Chris Alemany <chri...@gmail.com> wrote:Thanks for the hints Vince. I ended up looking through the old Wiki and came upon this page about backing up databases with the rsync report and how you can spit rsync into multiple skins.https://github.com/weewx/weewx/wiki/Using-the-RSYNC-skin-as-a-backup-solutionThat was a good solution for a while, until - like you - I wanted more.I eventually pulled the rsyncupload.py code from the main tree and stuffed it into a skin.The following was written a while ago. I still use it as is, but it's rough and untidy.  Really does need a clean up but I haven't and still don't have the time do that, so you get it warts and all...https://github.com/glennmckechnie/weewx-rsynctransferIt should install  *Gulp*, it should be self explanatory *Gulp* There are plenty of notes and examples in it that show it can handle the additional rsync command line options.my email address is in the code, there's the  issues tab on github and I always read this group.Cheers GlennVarious WeeWx addons athttps://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/0d2bbda5-dc2c-4075-bcae-44b6b4c01063n%40googlegroups.com.




-- 
You received this message because you are subscribed to the Go

Re: [weewx-user] Re: Exclude list or Overwrite behaviour for RSync Report

['John Kline' via weewx-user]

I should add that the way I solved this problem is to put the files outside of the reporting path (/home/weewx/public_html for me).  In that way, they aren’t swept up in the rsync report.On Apr 2, 2024, at 6:08 PM, John Kline  wrote:The problem with an rsync_options (similar to the existing ssh_options) is that the code already has rsync options specified individually (e.g., delete and compress).  It would be messy to have two ways to specify delete and compress.It might be best to add an explicit exclude option.  BTW, exclude can be specified multiple times, so the value should be an array.On Apr 2, 2024, at 11:56 AM, Chris Alemany  wrote:Hmm, both strategies have advantages. It'd be great if weewx had the ability to add in rsync options so that if you just wanted to do a single thing, exclude a directory, or maybe conform to a specific non-standard setting on the remote host, then you can easily do that in weewx.The extension is nice to have to create a full suite of rsync options so people can use it to backup stuff, move stuff, etc.I've created a GitHub issue/requesthttps://github.com/weewx/weewx/issues/951Thanks to you both.ChrisOn Tuesday, April 2, 2024 at 8:30:30 AM UTC-7 vince wrote:Seems complicated.  I was suggesting something like adding a general purpose 'rsync_options' variable in that section of weewx.conf, and adding the value  to the assembled rsync command in the run(self) routine in rsyncupload.py ?     Then the user could add any combination of the rsync options to the command if needed.   Perhaps something like the following (untested):pi@pi4:/tmp$ diff rsyncupload.py.orig rsyncupload.py -u--- rsyncupload.py.orig	2024-04-02 08:18:48.311469290 -0700+++ rsyncupload.py	2024-04-02 08:19:57.970078706 -0700@@ -46,6 +46,7 @@         self.delete = delete         self.port = port         self.ssh_options = ssh_options+        self.rsync_options = rsync_options   # <== new         self.compress = compress         self.log_success = log_success         self.log_failure = log_failure@@ -96,6 +97,7 @@         if self.timeout is not None:             cmd.extend(["--timeout=%s" % self.timeout])         cmd.extend(["-e"])+        cmd.extend([rsync_options])    # <=== new         cmd.extend([rsyncsshstring])         cmd.extend([rsynclocalspec])         cmd.extend([rsyncremotespec])And add a rsync_options = "whatever you want here" to the [[RSYNC]] section in weewx.conf ala:   [[RSYNC]]        delete = 0        skin = Rsync        enable = true        server = x.x.x.x         user = myremoteuser        path = /my/remote/path/here        log_success = true        log_failure = true        rsync_options = "-x -y -z whatever"       # <=== newDisclaimer - totally untested and no idea if there are security risks of doing it this way, but it would seem to be about as flexible as you can get toward supporting whatever rsync options the underlying os supports with a minimum of change to the existing uploaderOn Tuesday, April 2, 2024 at 1:17:58 AM UTC-7 Glenn McKechnie wrote:On Tue, 2 Apr 2024 at 15:00, Chris Alemany <chri...@gmail.com> wrote:Thanks for the hints Vince. I ended up looking through the old Wiki and came upon this page about backing up databases with the rsync report and how you can spit rsync into multiple skins.https://github.com/weewx/weewx/wiki/Using-the-RSYNC-skin-as-a-backup-solutionThat was a good solution for a while, until - like you - I wanted more.I eventually pulled the rsyncupload.py code from the main tree and stuffed it into a skin.The following was written a while ago. I still use it as is, but it's rough and untidy.  Really does need a clean up but I haven't and still don't have the time do that, so you get it warts and all...https://github.com/glennmckechnie/weewx-rsynctransferIt should install  *Gulp*, it should be self explanatory *Gulp* There are plenty of notes and examples in it that show it can handle the additional rsync command line options.my email address is in the code, there's the  issues tab on github and I always read this group.Cheers GlennVarious WeeWx addons athttps://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/0d2bbda5-dc2c-4075-bcae-44b6b4c01063n%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/5152BA43-B4F4-4620-891D-96D1F4ACE54E%40johnkline.com.

Re: [weewx-user] Re: Exclude list or Overwrite behaviour for RSync Report

['John Kline' via weewx-user]

The problem with an rsync_options (similar to the existing ssh_options) is that the code already has rsync options specified individually (e.g., delete and compress).  It would be messy to have two ways to specify delete and compress.It might be best to add an explicit exclude option.  BTW, exclude can be specified multiple times, so the value should be an array.On Apr 2, 2024, at 11:56 AM, Chris Alemany  wrote:Hmm, both strategies have advantages. It'd be great if weewx had the ability to add in rsync options so that if you just wanted to do a single thing, exclude a directory, or maybe conform to a specific non-standard setting on the remote host, then you can easily do that in weewx.The extension is nice to have to create a full suite of rsync options so people can use it to backup stuff, move stuff, etc.I've created a GitHub issue/requesthttps://github.com/weewx/weewx/issues/951Thanks to you both.ChrisOn Tuesday, April 2, 2024 at 8:30:30 AM UTC-7 vince wrote:Seems complicated.  I was suggesting something like adding a general purpose 'rsync_options' variable in that section of weewx.conf, and adding the value  to the assembled rsync command in the run(self) routine in rsyncupload.py ?     Then the user could add any combination of the rsync options to the command if needed.   Perhaps something like the following (untested):pi@pi4:/tmp$ diff rsyncupload.py.orig rsyncupload.py -u--- rsyncupload.py.orig	2024-04-02 08:18:48.311469290 -0700+++ rsyncupload.py	2024-04-02 08:19:57.970078706 -0700@@ -46,6 +46,7 @@         self.delete = delete         self.port = port         self.ssh_options = ssh_options+        self.rsync_options = rsync_options   # <== new         self.compress = compress         self.log_success = log_success         self.log_failure = log_failure@@ -96,6 +97,7 @@         if self.timeout is not None:             cmd.extend(["--timeout=%s" % self.timeout])         cmd.extend(["-e"])+        cmd.extend([rsync_options])    # <=== new         cmd.extend([rsyncsshstring])         cmd.extend([rsynclocalspec])         cmd.extend([rsyncremotespec])And add a rsync_options = "whatever you want here" to the [[RSYNC]] section in weewx.conf ala:   [[RSYNC]]        delete = 0        skin = Rsync        enable = true        server = x.x.x.x         user = myremoteuser        path = /my/remote/path/here        log_success = true        log_failure = true        rsync_options = "-x -y -z whatever"       # <=== newDisclaimer - totally untested and no idea if there are security risks of doing it this way, but it would seem to be about as flexible as you can get toward supporting whatever rsync options the underlying os supports with a minimum of change to the existing uploaderOn Tuesday, April 2, 2024 at 1:17:58 AM UTC-7 Glenn McKechnie wrote:On Tue, 2 Apr 2024 at 15:00, Chris Alemany  wrote:Thanks for the hints Vince. I ended up looking through the old Wiki and came upon this page about backing up databases with the rsync report and how you can spit rsync into multiple skins.https://github.com/weewx/weewx/wiki/Using-the-RSYNC-skin-as-a-backup-solutionThat was a good solution for a while, until - like you - I wanted more.I eventually pulled the rsyncupload.py code from the main tree and stuffed it into a skin.The following was written a while ago. I still use it as is, but it's rough and untidy.  Really does need a clean up but I haven't and still don't have the time do that, so you get it warts and all...https://github.com/glennmckechnie/weewx-rsynctransferIt should install  *Gulp*, it should be self explanatory *Gulp* There are plenty of notes and examples in it that show it can handle the additional rsync command line options.my email address is in the code, there's the  issues tab on github and I always read this group.Cheers GlennVarious WeeWx addons athttps://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/0d2bbda5-dc2c-4075-bcae-44b6b4c01063n%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/AE72C34C-BB70-4EDE-83CD-03BF9877BA24%40johnkline.com.

Re: [weewx-user] Re: Change to daylight saving time stops data update

['John Kline' via weewx-user]

> If the key is to not mess with the console time near the DST boundary, why not just arrange for> clock synchronization to only happen once a day at noon?It is not the key.  You have to get unlucky to check the time during the window.  The main problem is when time is set back one hour (leaving DST).  I’ve found the archive record code creating a timestamp from Vantage time gets it wrong in the “fall back” hour—thinking we’re still in DST, thus getting duplicates when trying to insert archive records.On Apr 1, 2024, at 11:02 AM, Tom Keffer  wrote:If the key is to not mess with the console time near the DST boundary, why not just arrange for clock synchronization to only happen once a day at noon?On Monday, April 1, 2024 at 6:34:46 AM UTC-7 jo...@johnkline.com wrote:I’ve successfully fixed the time change issue on a fork of the vantage driver:chaunceygardiner/weewx-vantagenext: VantageNext is a WeeWX driver based on the Vantage driver that ships with WeeWX.github.comIt assumes a one hour change for daylight savings and one is required to enter DST enter and exit times in the VantageNext section of weewx.conf.During the time change window, set time is a no-op (since one cannot specify whether the time is in DST or not).  Also, during the window, get time will auto correct if the time is about 1 hour off.  Lastly, when the driver converts the archive records time, it is auto-adjusted if about an hour off.I don’t recommend switching to this driver as the vantage driver in weewx is better supported; but perhaps a similar approach could be taken.  It is tricky because it is hard to test this stuff. On Apr 1, 2024, at 8:00 AM, Simon Duane  wrote:From what I've read, it involves an interaction between a Weewx service which adjusts the VP2 console clock to eliminate drift  - by default, it checks every 5 hours and applies the correction when the error is bigger than 5 seconds. I would suggest that if the error is close to 1 hour rather than a little more than 5 seconds, then the correction should simply not be applied, because of the risk of this happening. Fixing it on the next cycle will be good enough.It happened to my Weewx v 4.9.1 + VP2 (for the first time) yesterday too and, because I have that archive parameter set to hardware, clearing the datalogger memory meant I lost about a day's data.On Sunday 31 March 2024 at 23:56:23 UTC+1 Stephen wrote:I have two Davis Vantage Pro 2 weather stations at different locations. Both stations stopped updating their web pages at 2.00am last night, the moment daylight saving started.I'm running Weewx v5.0.1 at both locations.  Both Vantage Pro2 consoles are configured to automatically change to DST.There is an old thread from 2017 about this problem here https://groups.google.com/g/weewx-user/c/rM2IDREAWiI/m/oloGcj7aAAAJ.Taking the advice in that thread I've got one of the stations working again by executing  weectl device --dump.  I've left the other station as it is at the moment.This has never happened before, but I wasn't running v5.0.1 this time last year.Any idea what's going on?



-- 
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/09e0d95f-ec44-4782-989f-d4ef3217ddadn%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/241ad3cb-213d-44d3-937a-bea2dabbb441n%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/EB142EE0-83B8-43DF-A251-5574AC3EACDC%40johnkline.com.

Re: [weewx-user] weewx-purple error: no fresh concentrations to insert

['John Kline' via weewx-user]

I’ve released purple v3.9.1.  It considers readings stale at the max of 120s and 3 * poll_secs.You can put your poll_secs back to 120 after you install v3.9.1.On Mar 27, 2024, at 3:29 PM, John Kline  wrote:It’s your long poll interval interacting with my check to see how fresh the concentration is.  Change poll_secs in the Purple section of weewx.conf to something shorter.  Let’s try 30s and report back.In the meantime, I’ll look to change the check for freshness.  It doesn’t interact well with 120s poll interval.On Mar 27, 2024, at 3:15 PM, Charlie Fortner  wrote:ProblemI'm getting  Found no fresh concentrations to insert errors thrown by weewx-purple and the data is spotty:Did I change anything? I don't think so. It was working for months and months and then it seems to have stopped. I rebooted the purple air sensor several times.I'm fairly certain that the connection to the purple air sensor is OK. My home assistant reads from the same sensor and its data is continuous.SystemWeewx 4.10 running on a Debian VMWith weewx-purple extension version 3.9PurpleAir PA II Flex sensorThe log is attached.The pertinent section of weewx.config:[Purple]    poll_secs = 120    [[Proxy1]]    enable = False    hostname = proxy1    port = 8000    timeout = 5    [[Proxy2]]    enable = False    hostname = proxy2    port = 8000    timeout = 5    [[Proxy3]]    enable = False    hostname = proxy3    port = 8000    timeout = 5    [[Proxy4]]    enable = False    hostname = proxy4    port = 8000    timeout = 5    [[Sensor1]]    enable = True hostname = purpleair-c2a3.lan    #hostname = 192.168.2.173    port = 80    timeout = 10    [[Sensor2]]    enable = False    hostname = purple-air2    port = 80    timeout = 66I'd welcome any ideas about what's going on here.Charlie-- Atlanta, GA



-- 
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/d28d830d-a63e-441f-a34d-f8a0266f5ce9%40app.fastmail.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/8BAC26C6-47B7-458F-ABAD-20AD7416EC38%40johnkline.com.

Re: [weewx-user] weewx-purple error: no fresh concentrations to insert

['John Kline' via weewx-user]

It’s your long poll interval interacting with my check to see how fresh the concentration is.  Change poll_secs in the Purple section of weewx.conf to something shorter.  Let’s try 30s and report back.In the meantime, I’ll look to change the check for freshness.  It doesn’t interact well with 120s poll interval.On Mar 27, 2024, at 3:15 PM, Charlie Fortner  wrote:ProblemI'm getting  Found no fresh concentrations to insert errors thrown by weewx-purple and the data is spotty:Did I change anything? I don't think so. It was working for months and months and then it seems to have stopped. I rebooted the purple air sensor several times.I'm fairly certain that the connection to the purple air sensor is OK. My home assistant reads from the same sensor and its data is continuous.SystemWeewx 4.10 running on a Debian VMWith weewx-purple extension version 3.9PurpleAir PA II Flex sensorThe log is attached.The pertinent section of weewx.config:[Purple]    poll_secs = 120    [[Proxy1]]    enable = False    hostname = proxy1    port = 8000    timeout = 5    [[Proxy2]]    enable = False    hostname = proxy2    port = 8000    timeout = 5    [[Proxy3]]    enable = False    hostname = proxy3    port = 8000    timeout = 5    [[Proxy4]]    enable = False    hostname = proxy4    port = 8000    timeout = 5    [[Sensor1]]    enable = True hostname = purpleair-c2a3.lan    #hostname = 192.168.2.173    port = 80    timeout = 10    [[Sensor2]]    enable = False    hostname = purple-air2    port = 80    timeout = 66I'd welcome any ideas about what's going on here.Charlie-- Atlanta, GA



-- 
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/d28d830d-a63e-441f-a34d-f8a0266f5ce9%40app.fastmail.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/494CA903-AD6E-4C28-BB5D-E5B87F3525F3%40johnkline.com.

Re: [weewx-user] Wind Run in RTGD with SteelSeries Gauges

['John Kline' via weewx-user]

> On Dec 29, 2023, at 4:30 AM, 'Rory Gillies' via weewx-user 
>  wrote:
> 
> I also noticed that after a while (around 10 minutes but sometimes more) the 
> interface stops updating.

The default is to timeout after 20m unless you have passed the correct page 
update password (defaults to its-me).

Are you passing it?
http://=its-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/40650746-820A-4AF6-91A5-7AE8DABFB582%40johnkline.com.

Re: [weewx-user] CWOP data stopped showing up

['John Kline' via weewx-user]

Jim,Here’s another view of showing records are getting through.  It does show the dew point no longer being reported as of yesterday.APRS/CWOP weather report from N1ADJ – aprs.fi – live APRS mapaprs.fiOn Dec 20, 2023, at 11:33 AM, David Barto  wrote:I’m going to chime in with a “me too” on this. Strange.I’ve restarted Weewx to no effect, and all other reporting (Wunderground, PWS, my local site) are fine.     DavidOn Dec 20, 2023, at 11:04 AM, Jim Ancona  wrote:Hi,I've been happily running Weewx for a number of years. I have a Davis Vantage Pro2 and I'm running Weewx on an old Raspberry Pi 512MB Model B running Raspbian GNU/Linux 12 (bookworm). We've had power outages here this week, so the Pi has lost power and restarted multiple times. When it came back up this morning, I noticed that results didn't start showing up on my CWOP page at http://www.findu.com/cgi-bin/wxpage.cgi?call=n1adj. Here is the log from startup to the first CWOP report:Dec 20 13:21:29 weather systemd[1]: Started weewx.service - WeeWX weather system.Dec 20 13:21:32 weather python3[4296]: weewx[4296] INFO __main__: Initializing weewx version 4.10.2Dec 20 13:21:32 weather python3[4296]: weewx[4296] INFO __main__: Using Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]Dec 20 13:21:32 weather python3[4296]: weewx[4296] INFO __main__: Located at /usr/bin/python3Dec 20 13:21:32 weather python3[4296]: weewx[4296] INFO __main__: Platform Linux-6.1.0-rpi6-rpi-v6-armv6l-with-glibc2.36Dec 20 13:21:32 weather python3[4296]: weewx[4296] INFO __main__: Locale is 'en_US.UTF-8'Dec 20 13:21:32 weather python3[4296]: weewx[4296] INFO __main__: Using configuration file /etc/weewx/weewx.confDec 20 13:21:32 weather python3[4296]: weewx[4296] INFO __main__: Debug is 1Dec 20 13:21:32 weather python3[4296]: weewx[4296] DEBUG __main__: Initializing engineDec 20 13:21:32 weather python3[4296]: weewx[4296] INFO weewx.engine: Loading station type Vantage (weewx.drivers.vantage)Dec 20 13:21:32 weather python3[4296]: weewx[4296] DEBUG weewx.drivers.vantage: Driver version is 3.5.2Dec 20 13:21:32 weather python3[4296]: weewx[4296] DEBUG weewx.drivers.vantage: Option loop_request=1Dec 20 13:21:32 weather python3[4296]: weewx[4296] DEBUG weewx.drivers.vantage: Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00Dec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.drivers.vantage: Successfully woke up Vantage consoleDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.drivers.vantage: Hardware type is 16Dec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.drivers.vantage: ISS ID is 1Dec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.drivers.vantage: Hardware name: Vantage Pro2Dec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Loading service weewx.engine.StdTimeSynchDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Finished loading service weewx.engine.StdTimeSynchDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Loading service weewx.engine.StdConvertDec 20 13:21:33 weather python3[4296]: weewx[4296] INFO weewx.engine: StdConvert target unit is 0x1Dec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Finished loading service weewx.engine.StdConvertDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Loading service weewx.engine.StdCalibrateDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Finished loading service weewx.engine.StdCalibrateDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Loading service weewx.engine.StdQCDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Finished loading service weewx.engine.StdQCDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Loading service weewx.wxservices.StdWXCalculateDec 20 13:21:33 weather python3[4296]: weewx[4296] INFO weewx.wxservices: StdWXCalculate will use data binding wx_bindingDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.manager: Daily summary version is 4.0Dec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Finished loading service weewx.wxservices.StdWXCalculateDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Loading service weewx.wxxtypes.StdWXXTypesDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Finished loading service weewx.wxxtypes.StdWXXTypesDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Loading service weewx.wxxtypes.StdPressureCookerDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Finished loading service weewx.wxxtypes.StdPressureCookerDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Loading service weewx.wxxtypes.StdRainRaterDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Finished loading service weewx.wxxtypes.StdRainRaterDec 20 13:21:33 weather python3[4296]: weewx[4296] DEBUG weewx.engine: Loading 

Re: [weewx-user] Forecast extension for NWS failing

['John Kline' via weewx-user]

No issue here on 4.10.2 with that NWS config.  Sep 23 17:57:17 judygirldog64 weewx[809073] INFO user.forecast: MainThread: NWS: forecast version 3.4.0b12Sep 23 17:57:17 judygirldog64 weewx[809073] INFO user.forecast: MainThread: NWS: interval=10800 max_age=604800 lid=CAZ043 lid_desc=Miramar-San Diego CA foid=SGXSep 23 17:57:17 judygirldog64 weewx[809073] INFO user.forecast: MainThread: XTide: forecast version 3.4.0b12Sep 23 17:57:17 judygirldog64 weewx[809073] INFO user.forecast: MainThread: XTide: interval=1209600 max_age=2419200 location='Palo Alto Yacht Harbor, San Francisco Bay, California' duration=2419200Sep 23 18:00:03 judygirldog64 weewx[809073] INFO user.forecast: NWSThread: NWS: downloading forecast from 'http://forecast.weather.gov/product.php?site=NWS=PFM=txt=SGX'Sep 23 18:00:03 judygirldog64 weewx[809073] INFO user.forecast: XTideThread: XTide: generating tides from 2023-09-23 00:00:00 PDT (1695452400) to 2023-10-21 00:00:00 PDT (1697871600)Sep 23 18:00:03 judygirldog64 weewx[809073] INFO user.forecast: NWSThread: NWS: got 40 forecast records for Miramar-San Diego CA 32.87N 117.14W Elev. 482 ftSep 23 18:00:04 judygirldog64 weewx[809073] INFO user.forecast: NWSThread: NWS: saved 40 forecast recordsSep 23 18:00:04 judygirldog64 weewx[809073] INFO user.forecast: NWSThread: NWS: deleted forecasts prior to 1694912404Sep 23 18:00:04 judygirldog64 weewx[809073] INFO user.forecast: XTideThread: XTide: saved 108 forecast recordsSep 23 18:00:04 judygirldog64 weewx[809073] INFO user.forecast: XTideThread: XTide: deleted forecasts prior to 1693098004I think the next step is to do a proper bug report with a sanitized weewx.conf and a log from startup through hitting the issue.On Sep 23, 2023, at 5:46 PM, David Barto  wrote:Weewx.conf:    [[NWS]]
        lid = "CAZ043"
        foid = "SGX"
        lid_desc = "Miramar-San Diego CA"On Sep 23, 2023, at 5:44 PM, 'John Kline' via weewx-user  wrote:Send exactly what’s in the NWS section and I’ll try it.On Sep 23, 2023, at 5:12 PM, David Barto  wrote:4.10.2, fully up to date as far as I’m aware.This was working, and when I transferred to the new MacMini, I brought over all the config settings, added in the forecast information and only the NWS is failing. Wunderground worksAeris worksCould it be something in the code itself? "not enough arguments for format string” makes me think that there is a python code error. (*)	David* Not a python expert.On Sep 22, 2023, at 1:59 PM, 'John Kline' via weewx-user  wrote:What version of WeeWX?On Sep 22, 2023, at 1:52 PM, David Barto  wrote:All the bindings appear correct as noted.Stopped, removed, and started weewx as suggested.Error persists. (Dang)	DavidOn Sep 22, 2023, at 11:49 AM, 'John Kline' via weewx-user  wrote:It looks like you are trying to store a forecast in the weewx database.  What do you have for a binding in the [Forecast] section of weewx.conf?  It should look like this:data_binding = forecast_bindingAlso, under [DataBindings] in weewx.conf, you should have:    [[forecast_binding]]    manager = weewx.manager.Manager    schema = user.forecast.schema    table_name = archive    database = forecast_sqliteIf all looks correct, stop weewx, delete the forecast.sdb file in the /archive directory and start weewx.  Do you still have the issue?JohnOn Sep 22, 2023, at 10:52 AM, David Barto  wrote:I upgraded my MacMini to a newer version and installed from scratch.Getting this error for the NWS forecast:2023-09-22 02:45:16  weewx[820] ERROR user.forecast: NWSThread: NWS: forecast failure: not enough arguments for format stringThe forecast skin I used was the one Tom recommended: https://github.com/chaunceygardiner/weewx-forecastSuggestions?   David2023-09-22 02:45:16  weewx[820] DEBUG weewx.manager: Daily summary version is 4.02023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label 'CAZ043-221200'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label 'MIRAMAR-SAN DI'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label '32.87N 117.14W'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label 'DATE'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label 'DATE'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: forecast matrix: {'lid': 'CAZ043', 'desc': 'Miramar-San Diego CA', 'location': '32.87N 117.14W Elev. 482 ft', 'issued

Re: [weewx-user] Forecast extension for NWS failing

['John Kline' via weewx-user]

Send exactly what’s in the NWS section and I’ll try it.On Sep 23, 2023, at 5:12 PM, David Barto  wrote:4.10.2, fully up to date as far as I’m aware.This was working, and when I transferred to the new MacMini, I brought over all the config settings, added in the forecast information and only the NWS is failing. Wunderground worksAeris worksCould it be something in the code itself? "not enough arguments for format string” makes me think that there is a python code error. (*)	David* Not a python expert.On Sep 22, 2023, at 1:59 PM, 'John Kline' via weewx-user  wrote:What version of WeeWX?On Sep 22, 2023, at 1:52 PM, David Barto  wrote:All the bindings appear correct as noted.Stopped, removed, and started weewx as suggested.Error persists. (Dang)	DavidOn Sep 22, 2023, at 11:49 AM, 'John Kline' via weewx-user  wrote:It looks like you are trying to store a forecast in the weewx database.  What do you have for a binding in the [Forecast] section of weewx.conf?  It should look like this:data_binding = forecast_bindingAlso, under [DataBindings] in weewx.conf, you should have:    [[forecast_binding]]    manager = weewx.manager.Manager    schema = user.forecast.schema    table_name = archive    database = forecast_sqliteIf all looks correct, stop weewx, delete the forecast.sdb file in the /archive directory and start weewx.  Do you still have the issue?JohnOn Sep 22, 2023, at 10:52 AM, David Barto  wrote:I upgraded my MacMini to a newer version and installed from scratch.Getting this error for the NWS forecast:2023-09-22 02:45:16  weewx[820] ERROR user.forecast: NWSThread: NWS: forecast failure: not enough arguments for format stringThe forecast skin I used was the one Tom recommended: https://github.com/chaunceygardiner/weewx-forecastSuggestions?   David2023-09-22 02:45:16  weewx[820] DEBUG weewx.manager: Daily summary version is 4.02023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label 'CAZ043-221200'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label 'MIRAMAR-SAN DI'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label '32.87N 117.14W'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label 'DATE'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label 'DATE'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: forecast matrix: {'lid': 'CAZ043', 'desc': 'Miramar-San Diego CA', 'location': '32.87N 117.14W Elev. 482 ft', 'issued_ts': 1695328920, 'ts': [169533, 1695340800, 1695351600, 1695362400, 1695373200, 1695384000, 1695394800, 1695405600, 1695416400, 1695427200, 1695438000, 1695448800, 1695459600, 1695470400, 1695481200, 1695492000, 1695502800, 1695513600, 1695524400, 1695535200, 1695546000, 1695556800, 1695578400, 169560, 1695621600, 1695643200, 1695664800, 1695686400, 1695708000, 1695729600, 1695751200, 1695772800, 1695794400, 1695816000, 1695837600, 1695859200, 1695880800, 1695902400, 1695924000, 1695945600], 'hour': ['14', '17', '20', '23', '02', '05', '08', '11', '14', '17', '20', '23', '02', '05', '08', '11', '14', '17', '20', '23', '02', '05', '11', '17', '23', '05', '11', '17', '23', '05', '11', '17', '23', '05', '11', '17', '23', '05', '11', '17'], 'duration': [10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 10800], 'temp': ['70', '69', '64', '63', '62', '61', '62', '69', '71', '70', '65', '63', '63', '62', '63', '72', '74', '71', '63', '61', '60', '59', '71', '72', '60', '58', '72', '73', '61', '59', '71', '72', '62', '60', '73', '74', '63', '61', '72', '72'], 'dewpoint': ['60', '60', '60', '59', '59', '58', '59', '59', '59', '59', '59', '60', '60', '60', '61', '61', '61', '61', '60', '59', '59', '58', '61', '61', '59', '58', '60', '60', '59', '59', '60', '61', '59', '58', '61', '62', '61', '60', '62', '62'], 'humidity': ['71', '73', '87', '87', '90', '90', '90', '70', '66', '68', '81', '90', '90', '93', '93', '68', '64', '71', '90', '93', '96', '96', None, None, None, None, None, None, None, None, None, None, None, None, None, None, None, None, None, None], 'windDir': ['W', 'W', 'W', 'NW', 'N', 'N', 'N', 'NW', 'NW', 'NW', 'NW', 'NW', 'NW', 'N', 'N', 'NW', 'NW', 'NW', 'NW', 'NW', 'N', 'N', None, 'NW', None

Re: [weewx-user] Forecast extension for NWS failing

['John Kline' via weewx-user]

What version of WeeWX?On Sep 22, 2023, at 1:52 PM, David Barto  wrote:All the bindings appear correct as noted.Stopped, removed, and started weewx as suggested.Error persists. (Dang)	DavidOn Sep 22, 2023, at 11:49 AM, 'John Kline' via weewx-user  wrote:It looks like you are trying to store a forecast in the weewx database.  What do you have for a binding in the [Forecast] section of weewx.conf?  It should look like this:data_binding = forecast_bindingAlso, under [DataBindings] in weewx.conf, you should have:    [[forecast_binding]]    manager = weewx.manager.Manager    schema = user.forecast.schema    table_name = archive    database = forecast_sqliteIf all looks correct, stop weewx, delete the forecast.sdb file in the /archive directory and start weewx.  Do you still have the issue?JohnOn Sep 22, 2023, at 10:52 AM, David Barto  wrote:I upgraded my MacMini to a newer version and installed from scratch.Getting this error for the NWS forecast:2023-09-22 02:45:16  weewx[820] ERROR user.forecast: NWSThread: NWS: forecast failure: not enough arguments for format stringThe forecast skin I used was the one Tom recommended: https://github.com/chaunceygardiner/weewx-forecastSuggestions?   David2023-09-22 02:45:16  weewx[820] DEBUG weewx.manager: Daily summary version is 4.02023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label 'CAZ043-221200'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label 'MIRAMAR-SAN DI'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label '32.87N 117.14W'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label 'DATE'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label 'DATE'2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore label ''2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: forecast matrix: {'lid': 'CAZ043', 'desc': 'Miramar-San Diego CA', 'location': '32.87N 117.14W Elev. 482 ft', 'issued_ts': 1695328920, 'ts': [169533, 1695340800, 1695351600, 1695362400, 1695373200, 1695384000, 1695394800, 1695405600, 1695416400, 1695427200, 1695438000, 1695448800, 1695459600, 1695470400, 1695481200, 1695492000, 1695502800, 1695513600, 1695524400, 1695535200, 1695546000, 1695556800, 1695578400, 169560, 1695621600, 1695643200, 1695664800, 1695686400, 1695708000, 1695729600, 1695751200, 1695772800, 1695794400, 1695816000, 1695837600, 1695859200, 1695880800, 1695902400, 1695924000, 1695945600], 'hour': ['14', '17', '20', '23', '02', '05', '08', '11', '14', '17', '20', '23', '02', '05', '08', '11', '14', '17', '20', '23', '02', '05', '11', '17', '23', '05', '11', '17', '23', '05', '11', '17', '23', '05', '11', '17', '23', '05', '11', '17'], 'duration': [10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 10800], 'temp': ['70', '69', '64', '63', '62', '61', '62', '69', '71', '70', '65', '63', '63', '62', '63', '72', '74', '71', '63', '61', '60', '59', '71', '72', '60', '58', '72', '73', '61', '59', '71', '72', '62', '60', '73', '74', '63', '61', '72', '72'], 'dewpoint': ['60', '60', '60', '59', '59', '58', '59', '59', '59', '59', '59', '60', '60', '60', '61', '61', '61', '61', '60', '59', '59', '58', '61', '61', '59', '58', '60', '60', '59', '59', '60', '61', '59', '58', '61', '62', '61', '60', '62', '62'], 'humidity': ['71', '73', '87', '87', '90', '90', '90', '70', '66', '68', '81', '90', '90', '93', '93', '68', '64', '71', '90', '93', '96', '96', None, None, None, None, None, None, None, None, None, None, None, None, None, None, None, None, None, None], 'windDir': ['W', 'W', 'W', 'NW', 'N', 'N', 'N', 'NW', 'NW', 'NW', 'NW', 'NW', 'NW', 'N', 'N', 'NW', 'NW', 'NW', 'NW', 'NW', 'N', 'N', None, 'NW', None, 'NW', None, 'NW', None, 'NW', None, 'SW', None, 'W', None, 'S', None, 'S', None, 'S'], 'windSpeed': ['9', '9', '5', '3', '2', '2', '3', '4', '8', '10', '5', '5', '6', '6', '4', '6', '10', '10', '8', '5', '5', '4', None, None, None, None, None, None, None, None, None, None, None, None, None, None, None, None, None, None], 'clouds': ['B1', 'B1', 'B1', 'OV', 'B2', 'OV', 'OV', 'OV', 'B2', 'B2', 'B2', 'B2', 'B2', 'B1', 'B1', 'SC', 'SC', 'SC', 'SC', 'B1', 'B1', 'B1', 'B1', 'FW', 'FW', 'B1', 'B1', 'FW', 'FW', 'B1', 'B1', 'FW', 'FW', 'SC', 'B1', 'FW', 'FW', 'SC', 'SC', 'FW

Re: [weewx-user] Forecast extension for NWS failing

['John Kline' via weewx-user]

It looks like you are trying to store a forecast in the weewx database.  What 
do you have for a binding in the [Forecast] section of weewx.conf?  It should 
look like this:

data_binding = forecast_binding

Also, under [DataBindings] in weewx.conf, you should have:

[[forecast_binding]]
manager = weewx.manager.Manager
schema = user.forecast.schema
table_name = archive
database = forecast_sqlite

If all looks correct, stop weewx, delete the forecast.sdb file in the 
/archive directory and start weewx.  Do you still have the issue?

John

> On Sep 22, 2023, at 10:52 AM, David Barto  wrote:
> 
> I upgraded my MacMini to a newer version and installed from scratch.
> 
> Getting this error for the NWS forecast:
> 2023-09-22 02:45:16  weewx[820] ERROR user.forecast: NWSThread: NWS: forecast 
> failure: not enough arguments for format string
> 
> The forecast skin I used was the one Tom recommended: 
> https://github.com/chaunceygardiner/weewx-forecast
> 
> Suggestions?
> 
>David
> 
> 
> 2023-09-22 02:45:16  weewx[820] DEBUG weewx.manager: Daily summary version is 
> 4.0
> 2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore 
> label 'CAZ043-221200'
> 2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore 
> label 'MIRAMAR-SAN DI'
> 2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore 
> label '32.87N 117.14W'
> 2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore 
> label ''
> 2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore 
> label 'DATE'
> 2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore 
> label ''
> 2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore 
> label ''
> 2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore 
> label ''
> 2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore 
> label 'DATE'
> 2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore 
> label ''
> 2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: ignore 
> label ''
> 2023-09-22 02:45:16  weewx[820] DEBUG user.forecast: NWSThread: NWS: forecast 
> matrix: {'lid': 'CAZ043', 'desc': 'Miramar-San Diego CA', 'location': '32.87N 
> 117.14W Elev. 482 ft', 'issued_ts': 1695328920, 'ts': [169533, 
> 1695340800, 1695351600, 1695362400, 1695373200, 1695384000, 1695394800, 
> 1695405600, 1695416400, 1695427200, 1695438000, 1695448800, 1695459600, 
> 1695470400, 1695481200, 1695492000, 1695502800, 1695513600, 1695524400, 
> 1695535200, 1695546000, 1695556800, 1695578400, 169560, 1695621600, 
> 1695643200, 1695664800, 1695686400, 1695708000, 1695729600, 1695751200, 
> 1695772800, 1695794400, 1695816000, 1695837600, 1695859200, 1695880800, 
> 1695902400, 1695924000, 1695945600], 'hour': ['14', '17', '20', '23', '02', 
> '05', '08', '11', '14', '17', '20', '23', '02', '05', '08', '11', '14', '17', 
> '20', '23', '02', '05', '11', '17', '23', '05', '11', '17', '23', '05', '11', 
> '17', '23', '05', '11', '17', '23', '05', '11', '17'], 'duration': [10800, 
> 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 
> 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 10800, 21600, 
> 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 21600, 
> 21600, 21600, 21600, 21600, 21600, 10800], 'temp': ['70', '69', '64', '63', 
> '62', '61', '62', '69', '71', '70', '65', '63', '63', '62', '63', '72', '74', 
> '71', '63', '61', '60', '59', '71', '72', '60', '58', '72', '73', '61', '59', 
> '71', '72', '62', '60', '73', '74', '63', '61', '72', '72'], 'dewpoint': 
> ['60', '60', '60', '59', '59', '58', '59', '59', '59', '59', '59', '60', 
> '60', '60', '61', '61', '61', '61', '60', '59', '59', '58', '61', '61', '59', 
> '58', '60', '60', '59', '59', '60', '61', '59', '58', '61', '62', '61', '60', 
> '62', '62'], 'humidity': ['71', '73', '87', '87', '90', '90', '90', '70', 
> '66', '68', '81', '90', '90', '93', '93', '68', '64', '71', '90', '93', '96', 
> '96', None, None, None, None, None, None, None, None, None, None, None, None, 
> None, None, None, None, None, None], 'windDir': ['W', 'W', 'W', 'NW', 'N', 
> 'N', 'N', 'NW', 'NW', 'NW', 'NW', 'NW', 'NW', 'N', 'N', 'NW', 'NW', 'NW', 
> 'NW', 'NW', 'N', 'N', None, 'NW', None, 'NW', None, 'NW', None, 'NW', None, 
> 'SW', None, 'W', None, 'S', None, 'S', None, 'S'], 'windSpeed': ['9', '9', 
> '5', '3', '2', '2', '3', '4', '8', '10', '5', '5', '6', '6', '4', '6', '10', 
> '10', '8', '5', '5', '4', None, None, None, None, None, None, None, None, 
> None, None, None, None, None, None, None, None, None, None], 'clouds': ['B1', 
> 'B1', 'B1', 'OV', 'B2', 'OV', 'OV', 'OV', 'B2', 'B2', 'B2', 'B2', 'B2', 'B1', 
> 'B1', 'SC', 'SC', 'SC', 'SC', 'B1', 'B1', 'B1', 'B1', 'FW', 'FW', 'B1', 'B1', 
> 'FW', 'FW', 'B1', 'B1', 'FW', 'FW', 'SC', 'B1', 'FW', 'FW', 'SC', 'SC', 
> 'FW'], 'pop': 

Re: [weewx-user] Re: Weewx-rain24h addon

['John Kline' via weewx-user]

There is no need to use all that space when most loop packets will have zero rain.I just record the rainfall (non-zero rain in a loop packet) as a list of debits.  On each loop packet, I look at the top of the list to see if any have matured (24 hours later).  If so, I decrement rainfall by the amount in the entry and delete that entry.On Sep 18, 2023, at 9:00 AM, Geoff Cusick  wrote:So you’re maintaining a circular buffer of (24h/loop packet interval) rainfall samples.  Is that right?GWeb: http://www.cusick.org.ukOn 18 Sep 2023, at 16:53, 'John Kline' via weewx-user  wrote:I wrote this extension; although, I no longer use it because I have generalized the functionality to work on any observation and for any time length in my weewx-loopdata extension.What you are missing is that the plug-in operates at the loop packet level.  Other than loading from the database at start up, with archive interval precision, it does not read the database.  Rather, it keeps track of any rain recorded in loop packets such that they can be decremented from rain 24 hours later.  For example, if .01 rain occurs 87s into an archive interval; and another .01 rain occurs 20s later; the 24 hour rain will decrement (i.e., the rain24 value injected into the loop packets) when each .01 occurrence falls out of the 24 hour window; not when the archive record in the database is older than 24 hours.Of course, this is all meaningless if you are just going to use it in reports that are only generated on the archive interval; but the for insane (I resemble that remark) who want to see 24 hour rain decrement at loop interval precision on their weather sites that update on every loop packet, it is useful.JohnOn Sep 18, 2023, at 8:26 AM, Geoff Cusick  wrote:Seems a bit of a roundabout way to provide data that’s already easily available - presumably retrieving the 24h rain sum from the database, then injecting it back into the loop packets.  I’m obviously missing something.GWeb: http://www.cusick.org.ukOn 18 Sep 2023, at 16:18, kufuu  wrote:https://github.com/chaunceygardiner/weewx-rain24hOn Monday, September 18, 2023 at 7:02:06 AM UTC-4 gjr80 wrote:You might have to help us out here, what or where is the 'weewx-rain24h add on'. My quick google failed to find such an extension.GaryOn Monday, 18 September 2023 at 02:06:12 UTC+10 toef...@gmail.com wrote:I installed the weewx-rain24h add on and was wondering how to get he 24hr rain totals to display on the season skin desktop ?



-- 
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/RHdDkdSTN68/unsubscribe.
To unsubscribe from this group and all its topics, 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/9dca3a07-38df-4606-b412-a3c040159944n%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/93806518-A6D9-40B9-AA6B-6DC7C268951E%40gmail.com.




-- 
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/RHdDkdSTN68/unsubscribe.
To unsubscribe from this group and all its topics, 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/899373C3-8626-4DDF-AC9C-D7AE48600646%40johnkline.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/8ACFE559-1D1F-447F-9A6E-23A2E633E467%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/8B90242A-C8CA-4CB6-A2B7-6ED03B8942D6%40johnkline.com.

Re: [weewx-user] Re: Weewx-rain24h addon

['John Kline' via weewx-user]

I wrote this extension; although, I no longer use it because I have generalized the functionality to work on any observation and for any time length in my weewx-loopdata extension.What you are missing is that the plug-in operates at the loop packet level.  Other than loading from the database at start up, with archive interval precision, it does not read the database.  Rather, it keeps track of any rain recorded in loop packets such that they can be decremented from rain 24 hours later.  For example, if .01 rain occurs 87s into an archive interval; and another .01 rain occurs 20s later; the 24 hour rain will decrement (i.e., the rain24 value injected into the loop packets) when each .01 occurrence falls out of the 24 hour window; not when the archive record in the database is older than 24 hours.Of course, this is all meaningless if you are just going to use it in reports that are only generated on the archive interval; but the for insane (I resemble that remark) who want to see 24 hour rain decrement at loop interval precision on their weather sites that update on every loop packet, it is useful.JohnOn Sep 18, 2023, at 8:26 AM, Geoff Cusick  wrote:Seems a bit of a roundabout way to provide data that’s already easily available - presumably retrieving the 24h rain sum from the database, then injecting it back into the loop packets.  I’m obviously missing something.GWeb: http://www.cusick.org.ukOn 18 Sep 2023, at 16:18, kufuu  wrote:https://github.com/chaunceygardiner/weewx-rain24hOn Monday, September 18, 2023 at 7:02:06 AM UTC-4 gjr80 wrote:You might have to help us out here, what or where is the 'weewx-rain24h add on'. My quick google failed to find such an extension.GaryOn Monday, 18 September 2023 at 02:06:12 UTC+10 toef...@gmail.com wrote:I installed the weewx-rain24h add on and was wondering how to get he 24hr rain totals to display on the season skin desktop ?



-- 
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/RHdDkdSTN68/unsubscribe.
To unsubscribe from this group and all its topics, 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/9dca3a07-38df-4606-b412-a3c040159944n%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/93806518-A6D9-40B9-AA6B-6DC7C268951E%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/899373C3-8626-4DDF-AC9C-D7AE48600646%40johnkline.com.

Re: [weewx-user] Re: Connecting to new Davis Console model 6313

['John Kline' via weewx-user]

Previously, one had to spend an extra $225 for the USB data logger.  Now, one has to buy an Envoy ($235) and the USB data logger.I suppose the worry is that Davis will stop selling the previous console and the envoy.On Aug 8, 2023, at 4:07 PM, Greg from Oz  wrote:Looks like I won't be buying one of those!That is nearly as bad as paying subscription to use software.On Wednesday, 9 August 2023 at 02:55:32 UTC+10 Bob Rose wrote:I am in the same boat. I dropped a note to Davis support, and they confirmed that there is no local data available on the 6313. To get you data back you will need to purchase it back from Davis.On Sunday, July 30, 2023 at 7:14:36 PM UTC-7 vince wrote:Secondary might be poorly worded.  I think somebody suggested on wxforum.net the folks with old consoles could still talk to new sensors via their old dataloggers as always, and 'also' set up the new 6313 gateway/console to listen to the sensor's channel and feed Davis etc. if so inclined.  So you could get the new console with data that way while still running the old console we're all familiar with.I also noted in the manual a bit back that the new console lasts under a day through a power outage, while the old consoles last many days.   Manual is at (here) and the wxforum.net Davis group has lots of discussion about the new console.  Doesn't seem like too many people are happy so far.On Sunday, July 30, 2023 at 12:49:39 PM UTC-7 John Kline wrote:Davis still sells the old console and logger.Vince, I’m not sure what primary and secondary means.  They are all independent of one another.On Jul 30, 2023, at 11:41 AM, vince <vince...@gmail.com> wrote:I believe there are some posts suggesting the old console as the primary one and the new one as a secondary works well if you can leverage your old console and logger. You might want to give that a try.On Sunday, July 30, 2023 at 11:37:51 AM UTC-7 paul bennett wrote:Thanks, Vince.Indeed, WXForum agrees that the new 6313 console has no provision for a 3rd party API, either through the WiFi or the USB interface.  I wonder how long my old console will hold up...On Saturday, July 29, 2023 at 7:40:47 PM UTC-6 vince wrote:Did you set the ip address of the console ?  Lets see your driver stanza.You might ask on wxforum.net in the Davis forum there.  My hazy reading in the past about the new console makes me wonder if it's even possible with the new Console/logger product.On Saturday, July 29, 2023 at 3:40:14 PM UTC-7 paul bennett wrote:My 12-year old Vantage Pro 2 got destroyed by hail recently, so the insurance company bought me a new one. I now have the updated Davis 6313 console that connects via WiFi.  Unfortunately, I don't see how to interface the new console to weewx. The old console had the USB logger, which worked fine.I tried changing the interface type from "serial" to "ethernet" in weewx.conf, but it complains it can't connect to port 2. Which is no doubt true. Is it just a different port, or is it something far worse?Thanks,-paul bennett-



-- 
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/f4a44662-5f3d-45e2-be10-19149c329df1n%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/cf4914e0-4150-4d39-b2c6-d6289fc8n%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/101B1C99-1D23-4303-BE87-B29EE2340DC1%40johnkline.com.

Re: [weewx-user] Re: Connecting to new Davis Console model 6313

['John Kline' via weewx-user]

Davis still sells the old console and logger.Vince, I’m not sure what primary and secondary means.  They are all independent of one another.On Jul 30, 2023, at 11:41 AM, vince  wrote:I believe there are some posts suggesting the old console as the primary one and the new one as a secondary works well if you can leverage your old console and logger. You might want to give that a try.On Sunday, July 30, 2023 at 11:37:51 AM UTC-7 paul bennett wrote:Thanks, Vince.Indeed, WXForum agrees that the new 6313 console has no provision for a 3rd party API, either through the WiFi or the USB interface.  I wonder how long my old console will hold up...On Saturday, July 29, 2023 at 7:40:47 PM UTC-6 vince wrote:Did you set the ip address of the console ?  Lets see your driver stanza.You might ask on wxforum.net in the Davis forum there.  My hazy reading in the past about the new console makes me wonder if it's even possible with the new Console/logger product.On Saturday, July 29, 2023 at 3:40:14 PM UTC-7 paul bennett wrote:My 12-year old Vantage Pro 2 got destroyed by hail recently, so the insurance company bought me a new one. I now have the updated Davis 6313 console that connects via WiFi.  Unfortunately, I don't see how to interface the new console to weewx. The old console had the USB logger, which worked fine.I tried changing the interface type from "serial" to "ethernet" in weewx.conf, but it complains it can't connect to port 2. Which is no doubt true. Is it just a different port, or is it something far worse?Thanks,-paul bennett-



-- 
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/f4a44662-5f3d-45e2-be10-19149c329df1n%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/B5AB59C3-9231-4778-9FB1-29CA889941E5%40johnkline.com.

Re: [weewx-user] Re: Connecting to new Davis Console model 6313

['John Kline' via weewx-user]

I was going to say you need to buy the older console (or the cheaper envoy) and another USB data logger; but don’t you still have your console and data logger from your old VP2?  You can have more than one console listening to your VP2.On Jul 29, 2023, at 6:40 PM, vince  wrote:Did you set the ip address of the console ?  Lets see your driver stanza.You might ask on wxforum.net in the Davis forum there.  My hazy reading in the past about the new console makes me wonder if it's even possible with the new Console/logger product.On Saturday, July 29, 2023 at 3:40:14 PM UTC-7 paul bennett wrote:My 12-year old Vantage Pro 2 got destroyed by hail recently, so the insurance company bought me a new one. I now have the updated Davis 6313 console that connects via WiFi.  Unfortunately, I don't see how to interface the new console to weewx. The old console had the USB logger, which worked fine.I tried changing the interface type from "serial" to "ethernet" in weewx.conf, but it complains it can't connect to port 2. Which is no doubt true. Is it just a different port, or is it something far worse?Thanks,-paul bennett-



-- 
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/368d0aae-39af-4788-8612-fd0884dde301n%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/6A8546B5-AD35-4F4D-B493-572A2B08E9CA%40johnkline.com.

Re: [weewx-user] Re: Error with weewx-airlink

['John Kline' via weewx-user]

Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           no such column: pm2_5On Jul 17, 2023, at 6:12 AM, Yves Martin  wrote:wview_extended is correct here.I'm able to show the data on my main page but I've still theses errors...YMLe lundi 17 juillet 2023 à 09 h 01 min 24 s UTC-4, John Kline a écrit :Please note in the description for this extension:“weewx-airlink requires the wview_extended in WeeWX 4 that contains pm1_0, pm2_5 and pm10_0 columns.“On Jul 17, 2023, at 5:57 AM, michael.k...@gmx.at <michael.k...@gmx.at> wrote:weedb.NoColumnError: no such column: pm2_5Yves Martin schrieb am Montag, 17. Juli 2023 um 14:52:24 UTC+2:Hi,I've installe the module weewx-airlink (https://github.com/chaunceygardiner/weewx-airlink) for the Davis Air Quality, but I have this error :Jul 17 08:48:42 weewx4-raspi weewx[24741] INFO weewx.imagegenerator: Generated 18 images for report Bootstrap in 19.46 secondsJul 17 08:48:42 weewx4-raspi weewx[24741] INFO weewx.reportengine: Copied 0 files to /var/www/html/weewxJul 17 08:48:44 weewx4-raspi weewx[24741] INFO user.historygenerator: historygenerator.py: Generated 7 tables in 1.20 secondsJul 17 08:48:47 weewx4-raspi weewx[24741] INFO weewx.cheetahgenerator: Generated 10 files for report Bootstrap in 5.12 secondsJul 17 08:48:47 weewx4-raspi weewx[24741] INFO weewx.cheetahgenerator: Generated 1 files for report lastrain in 0.06 secondsJul 17 08:48:48 weewx4-raspi weewx[24741] INFO weewx.cheetahgenerator: Generated 1 files for report AirLinkReport in 0.06 secondsJul 17 08:48:48 weewx4-raspi weewx[24741] INFO user.airlink: get_scalar called where record does not contain pm2_5.  This is unexpected.Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine: Caught unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           no such column: pm2_5Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           Traceback (most recent call last):Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weewx/xtypes.py", line 101, in get_seriesJul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:               aggregate_interval, **option_dict)Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           TypeError: get_series() got an unexpected keyword argument 'SKIN_ROOT'Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:         Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           During handling of the above exception, another exception occurred:Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:         Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           Traceback (most recent call last):Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weedb/sqlite.py", line 39, in guarded_fnJul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:               return fn(*args, **kwargs)Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weedb/sqlite.py", line 233, in executeJul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:               return sqlite3.Cursor.execute(self, *args, **kwargs)Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           sqlite3.OperationalError: no such column: pm2_5Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:         Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           During handling of the above exception, another exception occurred:Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:         Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           Traceback (most recent call last):Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weewx/reportengine.py", line 197, in runJul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:               obj.start()Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weewx/reportengine.py", line 385, in startJul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:               self.run()Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weewx/imagegenerator.py", line 42, in runJul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:               self.gen_images(self.gen_ts)Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weewx/imagegenerator.py", line 109, in gen_imagesJul 17 08:48:48 weewx4-ra

Re: [weewx-user] Re: Error with weewx-airlink

['John Kline' via weewx-user]

Please note in the description for this extension:“weewx-airlink requires the wview_extended in WeeWX 4 that contains pm1_0, pm2_5 and pm10_0 columns.“On Jul 17, 2023, at 5:57 AM, michael.k...@gmx.at  wrote:weedb.NoColumnError: no such column: pm2_5Yves Martin schrieb am Montag, 17. Juli 2023 um 14:52:24 UTC+2:Hi,I've installe the module weewx-airlink (https://github.com/chaunceygardiner/weewx-airlink) for the Davis Air Quality, but I have this error :Jul 17 08:48:42 weewx4-raspi weewx[24741] INFO weewx.imagegenerator: Generated 18 images for report Bootstrap in 19.46 secondsJul 17 08:48:42 weewx4-raspi weewx[24741] INFO weewx.reportengine: Copied 0 files to /var/www/html/weewxJul 17 08:48:44 weewx4-raspi weewx[24741] INFO user.historygenerator: historygenerator.py: Generated 7 tables in 1.20 secondsJul 17 08:48:47 weewx4-raspi weewx[24741] INFO weewx.cheetahgenerator: Generated 10 files for report Bootstrap in 5.12 secondsJul 17 08:48:47 weewx4-raspi weewx[24741] INFO weewx.cheetahgenerator: Generated 1 files for report lastrain in 0.06 secondsJul 17 08:48:48 weewx4-raspi weewx[24741] INFO weewx.cheetahgenerator: Generated 1 files for report AirLinkReport in 0.06 secondsJul 17 08:48:48 weewx4-raspi weewx[24741] INFO user.airlink: get_scalar called where record does not contain pm2_5.  This is unexpected.Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine: Caught unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           no such column: pm2_5Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           Traceback (most recent call last):Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weewx/xtypes.py", line 101, in get_seriesJul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:               aggregate_interval, **option_dict)Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           TypeError: get_series() got an unexpected keyword argument 'SKIN_ROOT'Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:         Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           During handling of the above exception, another exception occurred:Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:         Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           Traceback (most recent call last):Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weedb/sqlite.py", line 39, in guarded_fnJul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:               return fn(*args, **kwargs)Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weedb/sqlite.py", line 233, in executeJul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:               return sqlite3.Cursor.execute(self, *args, **kwargs)Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           sqlite3.OperationalError: no such column: pm2_5Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:         Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           During handling of the above exception, another exception occurred:Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:         Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:           Traceback (most recent call last):Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weewx/reportengine.py", line 197, in runJul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:               obj.start()Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weewx/reportengine.py", line 385, in startJul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:               self.run()Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weewx/imagegenerator.py", line 42, in runJul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:               self.gen_images(self.gen_ts)Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weewx/imagegenerator.py", line 109, in gen_imagesJul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:               self.image_dict[timespan][plotname])Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:             File "/usr/share/weewx/weewx/imagegenerator.py", line 249, in gen_plotJul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:               **option_dict)Jul 17 08:48:48 weewx4-raspi weewx[24741] ERROR weewx.reportengine:         

Re: [weewx-user] Re: Backing up weewx.sdb

['John Kline' via weewx-user]

You might find these shell script fragments helpful.  If you call retry_backup_copy With arguments of the database to backup (weewx.sdb) and a destination file to backup to, the code will check to see if the cksum changed during the copy and also run an integrity check on the copy.  If the cksum changed or the integrity check fails, the copy is retried.make_backup_copy() {        db="$1"        tmp_db_copy="$2"        check_sum="`/usr/bin/cksum $db | cut -d ' ' -f 1`"        cp "$db" $tmp_db_copy        check_sum_after="`/usr/bin/cksum $db | cut -d ' ' -f 1`"        if [ "$check_sum" != "$check_sum_after" ]; then                echo "$db changed during cp!"                return 1        fi        integrity_check="`echo "pragma integrity_check;" | sqlite3 "$tmp_db_copy"`"        if [ "$integrity_check" != "ok" ]; then                echo "$tmp_db_copy failed integrity check!"                return 2        fi        return 0}retry_backup_copy() {    db="$1"    tmp_db_copy="$2"    retval=99    attempts=0    while [ "$retval" -ne 0 ]; do            attempts="`/usr/bin/expr $attempts + 1`"            if [ "$retval" -ne 99 ]; then                    echo "make_backup_copy attempt $attempts"            fi            make_backup_copy "$db" "$tmp_db_copy"            retval="$?"    done}On Mar 13, 2023, at 4:38 AM, michael.k...@gmx.at  wrote:I have an archive_interval of 300s, the database is usually updated within the first 20s after each 5th minute. The cron jobs that backup my sdb files run at minute 1 of every hour/day/week. I've never came across any problems, which doesn't mean this way to work will work always that smoothly. But: having an hourly backup, a daily backup, and a weekly backup done this way, chances are, I'll find a working copy anywhere :)Jonathan Ryshpan schrieb am Montag, 13. März 2023 um 08:29:00 UTC+1:My weewx database, which is on OaklandWeather,  is shared via nfs with my main system, on which key files and folders are backed up daily using rsnapshot.  The files being backed up include weewx.sdb. I have just noted this in the WeeWx User Manual:
Do not make the copy of the SQLite database while in the middle of a transaction! Schedule the backup for
immediately after an archive record is written, and then make sure the backup completes before the next
archive record arrives. Alternatively, stop WeeWX, perform the backup, then restart WeeWX.
What are the bad consequences of backing up during a transaction? Is there just one corrupt entry, or is the whole backup corrupt? Does anyone know a way to control the backup process so that this particular file in not copied during a transaction?-- Many Thanks - Jonathan Ryshpan 

	The best is the enemy of the good -- Voltaire





-- 
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/2be69d2d-c287-449a-aaa4-825b998118edn%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/007A23DB-8E01-4FA4-9717-B052A3C95E63%40johnkline.com.

Re: [weewx-user] WeeWX-Forecast 3.4.0b12 - Zambretti Update Issue

['John Kline' via weewx-user]

Zambretti generates a forecast once a day.# Zambretti Forecaster## The zambretti forecast is based upon recent weather conditions.  Supposedly# it is about 90% to 94% accurate.  It is simply a table of values based upon# the current barometric pressure, pressure trend, winter/summer, and wind# direction.  Apparently it is most accurate when used at 09:00 to provide# the forecast for the day.## The forecast is generated using data from a period of time prior to 09:00.# The forecast will be the same no matter what time of day it is requested, as# long as there are data for the period prior to 09:00.  A request for forecast# before 09:00 will return the previous day forecast.  If the forecast has# already been generated, it will not be re-generated.On Feb 10, 2023, at 6:36 AM, 'Rory Gillies' via weewx-user  wrote:Hi,I'm running WeeWX 4.8 on a RPi with Debian Bullseye (WeeWX installed via DEB package). I am using the chaunceygardiner version of weewx-forecast 3.4.0b12 with a SQLite forecast database.The forecast extension works fine with the exception of the Zambretti thread which is what I want. I have configured Aeris and it downloads the forecast every 30 minutes, however the Zambretti code is calculated once after restarting the weewx service, and then one again within the interval. After that it is not calculated again or showing up in the syslog until the weewx service is restarted.Here are the relevant sections of weewx.conf:[DataBindings]
    [[wx_binding]]
    [[forecast_binding]]
        manager = weewx.manager.Manager
        schema = user.forecast.schema
        table_name = archive
        database = forecast_sqlite[Databases]    [[forecast_sqlite]]        database_name = forecast.sdb        database_type = SQLite[Engine]    [[Services]]        archive_services = weewx.engine.StdArchive, user.forecast.ZambrettiForecast, user.forecast.AerisForecast[Forecast]    data_binding = forecast_binding    interval = 1800    [[Zambretti]]        hemisphere = NORTH    [[Aeris]]        client_id = xxx        client_secret = xxxAnd the skin.conf that I'm running (NeoWX Material):[CheetahGenerator]    search_list_extensions = user.historygenerator.MyXSearch, user.forecast.ForecastVariablesAnd the index.html.tmpl where the Zambretti forecast is called:                                #if $forecast.zambretti.code == 'A'                #if $current.radiation.raw > 0                                #else                                #end if              #else if $forecast.zambretti.code == 'B'                #if $current.radiation.raw > 0                                #else                                #end if              #else if $forecast.zambretti.code == 'C'                            #else if $forecast.zambretti.code == 'D'                            #else if $forecast.zambretti.code == 'E'                            #else if $forecast.zambretti.code == 'F'                            #else if $forecast.zambretti.code == 'G'                            #else if $forecast.zambretti.code == 'H'                            #else if $forecast.zambretti.code == 'I'                            #else if $forecast.zambretti.code == 'J'                            #else if $forecast.zambretti.code == 'K'                            #else if $forecast.zambretti.code == 'L'                            #else if $forecast.zambretti.code == 'M'                            #else if $forecast.zambretti.code == 'N'                            #else if $forecast.zambretti.code == 'O'                            #else if $forecast.zambretti.code == 'P'                            #else if $forecast.zambretti.code == 'Q'                            #else if $forecast.zambretti.code == 'R'                            #else if $forecast.zambretti.code == 'S'                            #else if $forecast.zambretti.code == 'T'                            #else if $forecast.zambretti.code == 'U'                            #else if $forecast.zambretti.code == 'V'                            #else if $forecast.zambretti.code == 'W'                            #else if $forecast.zambretti.code == 'X'                            #else if $forecast.zambretti.code == 'Y'                            #else if $forecast.zambretti.code == 'Z'                            #end if                                $forecast.label('Zambretti', $forecast.zambretti.code)## display Zambretti code for debug          $forecast.zambretti.code                              Issued at           $forecast.zambretti.issued_ts.format($Extras.Formatting.datetime_today)                  And here is the syslog after starting the weewx service:Feb 10 09:09:00 weather systemd[1]: Starting LSB: weewx weather system...Feb 10 09:09:01 weather weewx[674112] INFO __main__: Initializing weewx version 4.8.0Feb 10 09:09:01 weather weewx[674112] INFO __main__: Using Python 3.9.2 (default, Feb 28 2021, 17:03:44) #012[GCC 10.2.1 20210110]Feb 10 09:09:01 weather weewx[674112] INFO 

Re: [weewx-user] Windchill Text Value / Graph Discrepancy

['John Kline' via weewx-user]

> Tom and Gary confirmed that the VP2 hardware generated values for windchill are only available in the LOOP2 packets.I’m not sure why you think that is relevant.  The question is, whether software or hardware generated, do the loop packets have windchill.  I confirmed they do contain windchill (for my VP2) before my initial reply.On Jan 3, 2023, at 6:06 AM, Steve Schindler  wrote:Thanks for the suggestion but I don't think that's the issue with my setup.  In a previous discussion (https://groups.google.com/g/weewx-user/c/roOG0u8YPX4/m/Tc4vWnznAgAJ), Tom and Gary confirmed that the VP2 hardware generated values for windchill are only available in the LOOP2 packets.---tke...@gmail.comJul 24, 2020, 8:21:48 PMto weewx-userGeez, Gary, you're right! So, you would also have to specify LOOP2 packets. See the section [Vantage] in the User's Guide.[Vantage]  loop_request = 2-tkOn Fri, Jul 24, 2020 at 5:13 PM gjr80  wrote:Windchill is only in included in the Davis LOOP2 packet, it’s not in the LOOP packet or archive record (the defaults) from the console. So unless you have set WeeWX to use the LOOP2 packet WeeWX will never see windchill from the console, irrespective of StdWXCalculate settings.Gary---And the User's Guide states "Not all stations support LOOP2 data. You need firmware version 1.90 or later."So I don't think the loop_hilo parameter will affect the windchill value with my setup.On Saturday, December 31, 2022 at 1:07:01 PM UTC-5 jo...@johnkline.com wrote:Tom and friends will know for sure, but I believe the low you are seeing (at 07:31) is from the archive_day_windchill table.You likely have the following in your weewx.conf    # Whether to include LOOP data in hi/low statistics    loop_hilo = TrueThis tells weewx (well, it tells it to do exactly what the comment says).  Note: vantage loop packets do indeed include windchill.The archive table (produced from vantage archive records) does not include this low and the graphs are produced from archive records.I don’t think you are seeing anything *wrong*.Note: these highs and lows in the daily stats get wiped out if you run wee_database —rebuild-daily (which is unfortunate).On Dec 31, 2022, at 9:21 AM, Steve Schindler  wrote:During the recent cold weather, I noticed a discrepancy between the windchill minimum value in the table and the value/time shown on the graph. For 12-24-22, the
Low Wind Chill in the Since Midnight table is 23.6F at 07:31, but the
graph doesn't reflect that value. It shows a low of about 27F at
about 8:00. For 12-25-22, the temperature discrepancy is about the same
but time difference is greater. See the screenshots below. All other values (temp, humidity, wind) agree between the table and the graphs.
I'm using a Davis VP2 with firmware version 1.82 so WeeWX is
calculating the windchill value. Any thoughts on what's happening and how it can be corrected?
I'm in Florida so my troubleshooting/testing opportunities are limited to when a cold front passes through. However, I suspect that heat index has the same
problem and, if so, I'll have plenty of time to work on that that this summer.
:-)12-2412-25



-- 
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/183e065c-2fc6-4b2b-aaff-99ec35fa8ca1n%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/70448a2d-6bfb-4e85-9e56-97f489dbf515n%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/EB664955-0E7E-4ACC-B782-B77D93EC7C7C%40johnkline.com.

Re: [weewx-user] Windchill Test Value / Graph Discrepancy

['John Kline' via weewx-user]

Tom and friends will know for sure, but I believe the low you are seeing (at 07:31) is from the archive_day_windchill table.You likely have the following in your weewx.conf    # Whether to include LOOP data in hi/low statistics    loop_hilo = TrueThis tells weewx (well, it tells it to do exactly what the comment says).  Note: vantage loop packets do indeed include windchill.The archive table (produced from vantage archive records) does not include this low and the graphs are produced from archive records.I don’t think you are seeing anything *wrong*.Note: these highs and lows in the daily stats get wiped out if you run wee_database —rebuild-daily (which is unfortunate).On Dec 31, 2022, at 9:21 AM, Steve Schindler  wrote:During the recent cold weather, I noticed a discrepancy between the windchill minimum value in the table and the value/time shown on the graph. For 12-24-22, the
Low Wind Chill in the Since Midnight table is 23.6F at 07:31, but the
graph doesn't reflect that value. It shows a low of about 27F at
about 8:00. For 12-25-22, the temperature discrepancy is about the same
but time difference is greater. See the screenshots below. All other values (temp, humidity, wind) agree between the table and the graphs.
I'm using a Davis VP2 with firmware version 1.82 so WeeWX is
calculating the windchill value. Any thoughts on what's happening and how it can be corrected?
I'm in Florida so my troubleshooting/testing opportunities are limited to when a cold front passes through. However, I suspect that heat index has the same
problem and, if so, I'll have plenty of time to work on that that this summer.
:-)12-2412-25



-- 
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/183e065c-2fc6-4b2b-aaff-99ec35fa8ca1n%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/6C13C1D9-CCAC-4AAE-B7CB-B3B5B040B7BA%40johnkline.com.

Re: [weewx-user] Working drivers for TWI, Vaisala WXT, Peet Bros Ultimeter

['John Kline' via weewx-user]

Hi Dale,

Where are you located?

> On Nov 16, 2022, at 7:59 PM, DR  wrote:
> 
> After many years and a comfortable implementation of the Rainwise IP-100 
> driver, my Rainwise station has died, seems currently unfixable.  Despite 
> loosing most of the summer trying to get the ISS to transmit again, I've lost 
> all taht time and have to look for other inputs.
> 
> Looking through the Wiki, I see there may be three other station types for 
> which there are drivers which I might try.
> 
> 
> I have a Vaisala WXT520, a Texas Weather Instruments, and a Peet Bros 
> Ultimeter which I might try.
> 
> Having followed the messages here, I know there were updates to Python 3, 
> which required some modifications to the drivers that are on GitHub, and then 
> a recent upgrade in WeeWx itself.
> 
> 
> My question is to current users of WeeWx, do you have a station working with 
> the latest WeeWx, the latest Python and any of the three drivers mentioned 
> here?
> 
> 
> If there is success, I will focus on trying to get my WeeWx working again.
> 
> 
> I know the ultimate would be to learn enough Python to implement my own 
> driver and be able to fix it, but quite honestly, after a several month 
> illness, I find that my previous understanding which I was proud of now has 
> become fuzzy and a personal expectation to rev my mental processes up may 
> take longer than I want to be without a WeeWx running, so I'm looking for the 
> most likely path to success, and then get back on trying to get things 
> working with understanding Python.
> 
> 
> I appreciate any comments that might steer me to one of these three mentioned 
> drivers to see if I should even start down a particular path with a station 
> type.
> 
> 
> Oh, one last question:  I had some notes on a sort of universal driver which 
> was mentioned as a starting point for someone wishing to begin to learn how 
> things work.  If I recall, it took a text file of the station's readings and 
> converted it into a LOOP type input for WeeWx to ingest.  One 'only' needed 
> to get data from the weather station, format it into a list or dictionary, 
> and then give it to WeeWx.  I have been through the developer's guide and 
> hardware guide and the wiki but for the life of me cannot see the name of 
> that referenced.  Have I triggered enough recognition that someone might tell 
> me the name of the driver and I'll go study that again to start.
> 
> Thank youDale
> 
> 
> -- 
> 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/3fffddf3-df46-5491-c6f0-5fde01fb64c4%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/4BE74D10-E52F-4FDE-983D-20FE1C73FE9B%40johnkline.com.

Re: [weewx-user] Re: Rsync Help or User Help :o)

['John Kline' via weewx-user]

A trailing slash means copy the contents of the directory.Note that WeeWX code will add the slash if it is a directory.  See code snippet below.weewx/rsyncupload.py at master · weewx/weewxgithub.com        # If the source path ends with a slash, rsync interprets        # that as a request to copy all the directory's *contents*,        # whereas if it doesn't, it copies the entire directory.        # We want the former, so make it end with a slash.        # Note: Don't add the slash if local_root isn't a directory        if self.local_root.endswith(os.sep) or not os.path.isdir(self.local_root):            rsynclocalspec = self.local_root        else:            rsynclocalspec = self.local_root + os.sepOn Nov 15, 2022, at 7:33 AM, cric...@pobox.com  wrote:A couple of points about the trailing slashes.  A trailing slash means copy the contents of the directory.  The --archivemeans copy everything below the specified directory.  Not including a trailing slash means copy this directory and with--archive, everything below it.  It's not a matter of rsync not working because of the slashes, it just does two similar, butdifferent things.  The man pages for rsync are pretty good.As for the ssh keys, I'm pretty sure you can just copy the ~fiaranch/.ssh/id_rsa to ~root/.ssh.  No need to create root-specifickey pair and copy the public server's .ssh directory.  Oh, one other thing that's really important:The .ssh directory permissions are critical.  The directory itself must be chmod 0700.  The files inside it should be chmod 0600.This is true for all the .ssh directories on both ends of the connection.My setup is a little different; I rsync to another local machine that runs a web server.  Then I've got a separate script forpublishing the weewx (and a few other sites) to a public host, since the various href's need to be updated.On Tuesday, November 15, 2022 at 5:25:11 AM UTC-7 Greg Troxel wrote:
"gszla...@gmail.com"  writes:

> 1. Vince is correct. WeeWX runs as root and RSA generation must be done as 
> root.

I was sure Vince was correct to start with :-) but I think running weewx
as root is the wrong thing to do.   I run it as a non-root user, and
really there should be a dedicated weewx user that has permissions to do
what it needs (read the serial port, write the db, access credentials
for upload) and no more.

But this is really "how best to configure weewx on operating system X",
which is orthogonal to "how should I made weewx on system X already
configured as Y work".




-- 
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/a69561f5-048a-4e2f-bc8f-e009a9cc2911n%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/E14937D0-EDC4-4C7B-9500-D716F41C09B4%40johnkline.com.

Re: [weewx-user] Re: Bug with Pi OS 64 and Raspberry Zero 2w

['John Kline' via weewx-user]

I only run 64 bit on my Raspberry Pi 4s because lots/most software is no longer 
sufficiently tested on 32bits.  Even is WeeWX is well tested on 32-bits, there 
is so much more that is running, and being updated, on the Pi.  As such, I 
would not push back on that IN MOST CASES.

But this is a case where you probably shouldn’t be running it.  I *think* the 
Pi Zero only has 512MB of RAM.  What all is running on the Pi Zero?  I expect 
it might be slow (there are plenty of reports of that), but I’m surprised there 
are crashes.

> On Oct 1, 2022, at 11:46 AM, vince  wrote:
> 
> Are you trying to run a full desktop on the zero?
> And why would you run a 64 bit os on a box with 1 GB of RAM anyway ?
> 
>> On Saturday, October 1, 2022 at 11:36:42 AM UTC-7 michael.k...@gmx.at wrote:
>> I'm using weewx on a Raspberry Pi 4B with Rasperry Pi OS 64 bit without any 
>> issues.
>> 
>> remy.l...@gmail.com schrieb am Samstag, 1. Oktober 2022 um 18:44:06 UTC+2:
>>> Good morning all.
>>> I have been using weewx for 3 years with pi os 32B without any problem with 
>>> a pi zero w then 2w.
>>> Since I switched to version 64B, I have had lots of incomprehensible 
>>> crashes with the pi not responding and having to reset. weewx is not in 
>>> question.
>>> I tried to increase the swap, to switch to a 3A power supply, to go back to 
>>> the non-gl drivers, nothing helped! 
>>> 
>>> Have you noticed this kind of thing in 64 bits? is there a way to fix the 
>>> problem? thank you..
> 
> -- 
> 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/f2f85b75-b169-4a44-b189-e424684e93dbn%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/2286884E-7C9B-4A8C-B874-1CCF4B5F8F84%40johnkline.com.

Re: [weewx-user] Re: Posting data towards wunderground fails after migration to bullseye

['John Kline' via weewx-user]

I think *all* stations are showing as offline since yesterday around noon 
Pacific time.

> On Sep 20, 2022, at 7:17 AM, 'Michael Waldor' via weewx-user 
>  wrote:
> 
> 
> Sorry for my posting - the data is sent, received, and displayed by 
> wunderground. I was confused by the first fields from wunderground even 
> claiming that my station is offline. Guess that's a cookie problem with the 
> wunderground page.
> 
> Regards, Michael
> 
> 
> Michael Waldor schrieb am Dienstag, 20. September 2022 um 16:11:37 UTC+2:
>> Yesterday I've upgraded my raspberry pi3 to use the current bullseye. Thus I 
>> had to reinstall all my programs including weewx. Now weewx is using the 
>> current release 4.8.0 (formerly I was on 4.7.0) with the patched version of 
>> wh23xx driver. Everything is working, but my posts towards wunderground are 
>> not received. There is no error message within my logs (journalctl), even if 
>> checking with debug=2. I see the usual message 
>> 
>> Sep 19 13:51:31 imurr9 python3[561]: weewx[561] INFO weewx.restx: 
>> Wunderground-P
>> WS: Data for station IMURR9 will be posted
>> ...
>> Sep 20 15:50:28 imurr9 python3[5876]: weewx[5876] DEBUG weewx.restx: 
>> Ambient: ur
>> l: 
>> https://weatherstation.wunderground.com/weatherstation/updateweatherstation.p
>> hp?action=updateraw=IMURR9=XXX=weewx-4.8.0=30.2
>> 43=2022-09-20%2013%3A50%3A00=0.00=45.7=0.00
>> midity=054=62.6=318.22=3.25=244=3.1&
>> windspeedmph=1.8
>> 
>> But since I did the update ,no data are received by wunderground. Of course 
>> I've set the "correct" password/API-key from wunderground (working within 
>> buster & weewx-4.7.0).
>> 
>> I can even sent the given URL from above using firefox (with proper 
>> password), get a success, but no data are visible within wunderground.
>> 
>> Any indeas?
>> 
>> Regards, Michael
> 
> -- 
> 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/e3b7c392-780f-46fa-8a88-c36f92d9577an%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/CC7B5502-EC5B-4F73-AF52-F1E820C0BA14%40johnkline.com.

Re: [weewx-user] Lose connection to data until reboot

['John Kline' via weewx-user]

You still have the problem that something is eating all of your memory.

Assuming you got the process ID correct, something(s) else will be killed. 

> On Sep 20, 2022, at 3:40 AM, Johnnie Walker  wrote:
> 
> 
> Hi John/Tom - many thanks to you both.
> 
> On the server instance: running on normal PC hardware, 16GB RAM, Ubuntu 
> Server (think 20.04). I wrote "-1000" to /proc/PROC_ID/oom_score_adj - and 
> we'll see what happens from here. Server mainly used for internal websites, 
> also runs Ubiquiti Unifi Controller.
> 
> Tom - I had thought I needed the WLL to serve data to weewx over the LAN, so 
> figured [WeatherLinkLive] in weewx.conf. Have just now checked the file and I 
> have both [Vantage] and [WeatherLinkLive] sections configured. It sounds as 
> if I could remove the WeatherLink one? Am remembering I used a plugin 
> initially to link to the WLL, maybe that's obsolete now.
> 
> Both sections copied in below from conf file.
> 
> Thanks - JW
> 
> 
> [Vantage]
> # This section is for the Davis Vantage series of weather stations.
> 
> # Connection type: serial or ethernet
> #  serial (the classic VantagePro)
> #  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
> type = ethernet
> 
> # If the connection type is serial, a port must be specified:
> #   Debian, Ubuntu, Redhat, Fedora, and SuSE:
> # /dev/ttyUSB0 is a common USB port name
> # /dev/ttyS0   is a common serial port name
> #   BSD:
> # /dev/cuaU0   is a common serial port name
> port = /dev/ttyUSB0
> 
> # If the connection type is ethernet, an IP Address/hostname is required:
> host = 192.168.1.210
> 
> ##
> # The rest of this section rarely needs any attention.
> # You can safely leave it "as is."
> ##
> 
> # Serial baud rate (usually 19200)
> baudrate = 19200
> 
> # TCP port (when using the WeatherLinkIP)
> tcp_port = 2
> 
> # TCP send delay (when using the WeatherLinkIP):
> tcp_send_delay = 0.5
> 
> # The type of LOOP packet to request: 1 = LOOP1; 2 = LOOP2; 3 = both
> loop_request = 1
> 
> # The id of your ISS station (usually 1). If you use a wind meter 
> connected
> # to a anemometer transmitter kit, use its id
> iss_id = 1
> 
> # How long to wait for a response from the station before giving up (in
> # seconds; must be greater than 2)
> timeout = 4
> 
> # How long to wait before trying again (in seconds)
> wait_before_retry = 1.2
> 
> # How many times to try before giving up:
> max_tries = 4
> 
> # Vantage model Type: 1 = Vantage Pro; 2 = Vantage Pro2
> model_type = 2
> 
> # The driver to use:
> driver = weewx.drivers.vantage
> 
> ..
> 
> [WeatherLinkLive]
> driver = user.weatherlink_live
> host = 192.168.1.210
> polling_interval = 10
> mapping = th:1, th_indoor, baro, rain:1, wind:1, thw:1, thsw:1, 
> windchill:1
> 
> 
> On Mon, Sep 19, 2022 at 9:38 PM Tom Keffer  wrote:
>> I agree with John that this is an out-of-memory problem, but I wonder why 
>> you are getting the offset in humidity during the down time. Is this an 
>> artifact of using WeatherLinkLive? Indeed, why are you using WLL? Why not 
>> just go to the VP2 directly?
>> 
>> On Mon, Sep 19, 2022 at 6:25 PM 'John Kline' via weewx-user 
>>  wrote:
>>> Correction, the file is /proc//oom-score-adj
>>> 
>>>> On Sep 19, 2022, at 6:23 PM, John Kline  wrote:
>>>> 
>>>> 
>>>> It doesn’t look like you are losing the connection to your Vantage Pro2.  
>>>> Rather, the kernel is killing WeeWX because you’re running of of memory.
>>>> 
>>>> You could write -1000 to the /proc//oom-kill-adj 
>>>> file to keep it from killing WeeWX, but then something else will be killed 
>>>> to free up memory.
>>>> 
>>>> What are you running WeeWX on?  How much memory?  What else is running?
>>>> 
>>>>> On Sep 19, 2022, at 6:10 PM, Johnnie Walker  wrote:
>>>>> 
>>>>> Hi,
>>>>> I'd had a recurring issue for some months that the weewx service loses 
>>>>> connection to my Davis Vantage Pro2 / WeatherLink. Basic solution has 
>>>>> been to reboot which brings things back into action, although I lose the 
>>>>> data for the period during which the problem occurred. Shows up as breaks 
>>>>> 

Re: [weewx-user] Lose connection to data until reboot

['John Kline' via weewx-user]

Correction, the file is /proc//oom-score-adj

> On Sep 19, 2022, at 6:23 PM, John Kline  wrote:
> 
> 
> It doesn’t look like you are losing the connection to your Vantage Pro2.  
> Rather, the kernel is killing WeeWX because you’re running of of memory.
> 
> You could write -1000 to the /proc//oom-kill-adj file 
> to keep it from killing WeeWX, but then something else will be killed to free 
> up memory.
> 
> What are you running WeeWX on?  How much memory?  What else is running?
> 
>>> On Sep 19, 2022, at 6:10 PM, Johnnie Walker  wrote:
>>> 
>> Hi,
>> I'd had a recurring issue for some months that the weewx service loses 
>> connection to my Davis Vantage Pro2 / WeatherLink. Basic solution has been 
>> to reboot which brings things back into action, although I lose the data for 
>> the period during which the problem occurred. Shows up as breaks in the 
>> charts (for example):
>> 
>> I have some breaks that are 1-2 days or more if I was on travel and didn't 
>> realize until I returned.
>> I just took time to search /var/log/syslog for the instance that happened 
>> today - log is copied in below. And it looks like an out of memory error, so 
>> the process is killed. (Log is grep'd for "weewx" , I copied in the log info 
>> grep'd "oom" further below). The log entries around 16:12 and after are when 
>> I rebooted the server.
>> I installed weewx well over 2 years ago so can't recollect how I installed. 
>> I can post the weewx.conf file if needed.
>> Could anyone give me a pointer on how to fix, and is there a way to patch up 
>> the missing data sections?
>> Thanks very much - JW
>> 
>> "weewx"
>> 
>> Sep 19 15:38:31 sparta weewx[1081] INFO user.weatherlink_live: Emitting poll 
>> packet
>> Sep 19 15:38:31 sparta weewx[1081] INFO user.weatherlink_live: Emitting push 
>> (broadcast) packet
>> Sep 19 15:38:38 sparta weewx[1081] message repeated 4 times: [ INFO 
>> user.weatherlink_live: Emitting push (broadcast) packet]
>> Sep 19 15:38:41 sparta weewx[1081] INFO user.weatherlink_live: Emitting poll 
>> packet
>> Sep 19 15:38:41 sparta weewx[1081] INFO user.weatherlink_live: Emitting push 
>> (broadcast) packet
>> Sep 19 15:38:51 sparta weewx[1081] message repeated 4 times: [ INFO 
>> user.weatherlink_live: Emitting push (broadcast) packet]
>> Sep 19 15:38:51 sparta weewx[1081] INFO user.weatherlink_live: Emitting poll 
>> packet
>> Sep 19 15:38:53 sparta weewx[1081] INFO user.weatherlink_live: Emitting push 
>> (broadcast) packet
>> Sep 19 15:39:01 sparta weewx[1081] message repeated 3 times: [ INFO 
>> user.weatherlink_live: Emitting push (broadcast) packet]
>> Sep 19 15:39:01 sparta weewx[1081] INFO user.weatherlink_live: Emitting poll 
>> packet
>> Sep 19 15:39:02 sparta kernel: [1192066.955832] 
>> oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=23c2c8bc241e51af783d9abaf3b8008403f4099db600e63a6284359bda22502e,mems_allowed=0,global_oom,task_memcg=/system.slice/weewx.service,task=python3,pid=1081,uid=0
>> Sep 19 16:12:45 sparta systemd[1]: Starting LSB: weewx weather system...
>> Sep 19 16:12:45 sparta weewx[907]:  * Starting weewx weather system weewx
>> Sep 19 16:12:46 sparta weewx[1003] INFO __main__: Initializing weewx version 
>> 4.8.0
>> Sep 19 16:12:46 sparta weewx[1003] INFO __main__: Using Python 3.8.10 
>> (default, Jun 22 2022, 20:18:18) #012[GCC 9.4.0]
>> Sep 19 16:12:46 sparta weewx[1003] INFO __main__: Platform 
>> Linux-5.4.0-125-generic-x86_64-with-glibc2.29
>> Sep 19 16:12:46 sparta weewx[1003] INFO __main__: Locale is 'C.UTF-8'
>> Sep 19 16:12:46 sparta weewx[1003] INFO __main__: Using configuration file 
>> /etc/weewx/weewx.conf
>> Sep 19 16:12:46 sparta weewx[1003] INFO __main__: Debug is 0
>> Sep 19 16:12:46 sparta weewx[1003] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> Sep 19 16:12:46 sparta weewx[1090] INFO weewx.engine: Loading station type 
>> WeatherLinkLive (user.weatherlink_live)
>> Sep 19 16:12:46 sparta weewx[907]:...done.
>> Sep 19 16:12:46 sparta systemd[1]: Started LSB: weewx weather system.
>> 
>> "oom"
>> 
>> Sep 19 15:39:02 sparta kernel: [1192066.955659] python3 invoked oom-killer: 
>> gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
>> Sep 19 15:39:02 sparta kernel: [1192066.955672]  
>> oom_kill_process.cold+0xb/0x10
>> Sep 19 15:39:02 sparta kernel: [1192066.955745] [  pid  ]   uid  tgid 
>> total_vm  rss pgtables_bytes swapents oom_score_adj name
>> Sep 19 15:39:02 sparta kernel: [1192066.9558

Re: [weewx-user] Lose connection to data until reboot

['John Kline' via weewx-user]

It doesn’t look like you are losing the connection to your Vantage Pro2.  
Rather, the kernel is killing WeeWX because you’re running of of memory.

You could write -1000 to the /proc//oom-kill-adj file to 
keep it from killing WeeWX, but then something else will be killed to free up 
memory.

What are you running WeeWX on?  How much memory?  What else is running?

> On Sep 19, 2022, at 6:10 PM, Johnnie Walker  wrote:
> 
> Hi,
> I'd had a recurring issue for some months that the weewx service loses 
> connection to my Davis Vantage Pro2 / WeatherLink. Basic solution has been to 
> reboot which brings things back into action, although I lose the data for the 
> period during which the problem occurred. Shows up as breaks in the charts 
> (for example):
> 
> I have some breaks that are 1-2 days or more if I was on travel and didn't 
> realize until I returned.
> I just took time to search /var/log/syslog for the instance that happened 
> today - log is copied in below. And it looks like an out of memory error, so 
> the process is killed. (Log is grep'd for "weewx" , I copied in the log info 
> grep'd "oom" further below). The log entries around 16:12 and after are when 
> I rebooted the server.
> I installed weewx well over 2 years ago so can't recollect how I installed. I 
> can post the weewx.conf file if needed.
> Could anyone give me a pointer on how to fix, and is there a way to patch up 
> the missing data sections?
> Thanks very much - JW
> 
> "weewx"
> 
> Sep 19 15:38:31 sparta weewx[1081] INFO user.weatherlink_live: Emitting poll 
> packet
> Sep 19 15:38:31 sparta weewx[1081] INFO user.weatherlink_live: Emitting push 
> (broadcast) packet
> Sep 19 15:38:38 sparta weewx[1081] message repeated 4 times: [ INFO 
> user.weatherlink_live: Emitting push (broadcast) packet]
> Sep 19 15:38:41 sparta weewx[1081] INFO user.weatherlink_live: Emitting poll 
> packet
> Sep 19 15:38:41 sparta weewx[1081] INFO user.weatherlink_live: Emitting push 
> (broadcast) packet
> Sep 19 15:38:51 sparta weewx[1081] message repeated 4 times: [ INFO 
> user.weatherlink_live: Emitting push (broadcast) packet]
> Sep 19 15:38:51 sparta weewx[1081] INFO user.weatherlink_live: Emitting poll 
> packet
> Sep 19 15:38:53 sparta weewx[1081] INFO user.weatherlink_live: Emitting push 
> (broadcast) packet
> Sep 19 15:39:01 sparta weewx[1081] message repeated 3 times: [ INFO 
> user.weatherlink_live: Emitting push (broadcast) packet]
> Sep 19 15:39:01 sparta weewx[1081] INFO user.weatherlink_live: Emitting poll 
> packet
> Sep 19 15:39:02 sparta kernel: [1192066.955832] 
> oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=23c2c8bc241e51af783d9abaf3b8008403f4099db600e63a6284359bda22502e,mems_allowed=0,global_oom,task_memcg=/system.slice/weewx.service,task=python3,pid=1081,uid=0
> Sep 19 16:12:45 sparta systemd[1]: Starting LSB: weewx weather system...
> Sep 19 16:12:45 sparta weewx[907]:  * Starting weewx weather system weewx
> Sep 19 16:12:46 sparta weewx[1003] INFO __main__: Initializing weewx version 
> 4.8.0
> Sep 19 16:12:46 sparta weewx[1003] INFO __main__: Using Python 3.8.10 
> (default, Jun 22 2022, 20:18:18) #012[GCC 9.4.0]
> Sep 19 16:12:46 sparta weewx[1003] INFO __main__: Platform 
> Linux-5.4.0-125-generic-x86_64-with-glibc2.29
> Sep 19 16:12:46 sparta weewx[1003] INFO __main__: Locale is 'C.UTF-8'
> Sep 19 16:12:46 sparta weewx[1003] INFO __main__: Using configuration file 
> /etc/weewx/weewx.conf
> Sep 19 16:12:46 sparta weewx[1003] INFO __main__: Debug is 0
> Sep 19 16:12:46 sparta weewx[1003] INFO __main__: PID file is 
> /var/run/weewx.pid
> Sep 19 16:12:46 sparta weewx[1090] INFO weewx.engine: Loading station type 
> WeatherLinkLive (user.weatherlink_live)
> Sep 19 16:12:46 sparta weewx[907]:...done.
> Sep 19 16:12:46 sparta systemd[1]: Started LSB: weewx weather system.
> 
> "oom"
> 
> Sep 19 15:39:02 sparta kernel: [1192066.955659] python3 invoked oom-killer: 
> gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
> Sep 19 15:39:02 sparta kernel: [1192066.955672]  
> oom_kill_process.cold+0xb/0x10
> Sep 19 15:39:02 sparta kernel: [1192066.955745] [  pid  ]   uid  tgid 
> total_vm  rss pgtables_bytes swapents oom_score_adj name
> Sep 19 15:39:02 sparta kernel: [1192066.955832] 
> oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=23c2c8bc241e51af783d9abaf3b8008403f4099db600e63a6284359bda22502e,mems_allowed=0,global_oom,task_memcg=/system.slice/weewx.service,task=python3,pid=1081,uid=0
> Sep 19 15:39:02 sparta kernel: [1192066.955996] Out of memory: Killed process 
> 1081 (python3) total-vm:21086716kB, anon-rss:14282388kB, file-rss:0kB, 
> shmem-rss:0kB, UID:0 pgtables:36056kB oom_score_adj:0
> 
> -- 
> 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 
> 

Re: [weewx-user] Re: cannot read localization file

['John Kline' via weewx-user]

Another workaround that *should* work is to remove the following line from 
weewx.conf:
lang = en
A workaround that only works if your language is ‘en’.
The code in reportengine only looks for the file if lang is specified.

I don’t have a lang = en line in my weewx.conf and have no such messages in the 
log for my enabled Rsync skin.

> On Aug 18, 2022, at 12:17 PM, Karen K  wrote:
> 
> I guess it is not necessary to specify a language for rsync. May be there a 
> "lang = en" line direct under [StdReport]. A work around could be to create 
> an empty file with the name that is missing.
> 
> vince schrieb am Donnerstag, 18. August 2022 um 20:58:28 UTC+2:
>> In 4.8.0 I'm seeing localization debug messages in syslog for every skin 
>> etc. that I have enabled.
>> 
>> Cannot read localization file /home/weewx/skins/Rsync/lang/en.conf for 
>> report 'RSYNC': Config file not found: "/home/weewx/skins/Rsync/lang/en.conf"
>> 
>> Is there a quick way to suppress all these kinds of messages while leaving 
>> debug enabled ?
>> 
> 
> -- 
> 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/537c873f-65ca-4121-9921-9fe77c300705n%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/0F2EB739-E934-4DC2-BC70-D63F9CE6E3E4%40johnkline.com.

Re: [weewx-user] RSYNC is using IP address and not host name

['John Kline' via weewx-user]

I just examined the code in /bin/weeutil/rsyncupload.py
It contains:
if self.ssh_options:
rsyncsshstring = rsyncsshstring + " " + self.ssh_options

I don’t see a how this couldn’t be including options.  Would you send your 
entire RSYNC stanza again?

> On Aug 9, 2022, at 10:32 AM, John Kline  wrote:
> 
> 
> Did you restart weewx after changing weewx.conf?
> 
>>> On Aug 9, 2022, at 10:05 AM, Dan Jones  wrote:
>>> 
>> ssh stanza removed
>> 
>> debug on 1
>> 
>> output still the same:
>> 
>> DEBUG weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', 
>> '--stats', '-e', 'ssh', '/tmp/weather34/serverdata/', 
>> 'www-data@123.123.123.123:/var/www/html/weather34/serverdata']]
>> 
>> 
>> Still ignoring ssh_options and still using IP address rather than host name.
>> 
>> Surely ssh_options wouldn't be needed if it used the host name, and then 
>> rsync would use .ssh/config with the correct host name configuration?
>> 
>> 
>>> On Tuesday, August 9, 2022 at 5:09:51 PM UTC+1 jo...@johnkline.com wrote:
>>> Oh, I didn’t notice the SSH stanza, remove that line.  ssh_options should 
>>> be directly under RSYNC.
>>> 
>>>>> On Aug 9, 2022, at 9:01 AM, bell...@gmail.com  wrote:
>>>>> 
>>>> I don’t have a [[SSH]] stanza. Try removing that.
>>> 
>>>> rich
>>>> 
>>>>> On Tuesday, 9 August 2022 at 11:53:57 UTC-4 dan.rh...@gmail.com wrote:
>>>>> Yep, correct, its the private key. 
>>>>> 
>>>>> But it looks like that whole ssh_options bit is being ignored. I can't 
>>>>> see it in the logs when I tail them. 
>>>>> 
>>>>>> On Tuesday, August 9, 2022 at 4:52:18 PM UTC+1 jo...@johnkline.com wrote:
>>>>>> -i should refer to a file that contains a private key.  Is that the case?
>>>>>> 
>>>>>>>> On Aug 9, 2022, at 8:14 AM, Dan Jones  wrote:
>>>>>>>> 
>>>>>>> My weewx.conf contains this:
>>>>>> 
>>>>>>> 
>>>>>>> [[RSYNC]]
>>>>>>> skin = Rsync
>>>>>>> HTML_ROOT = /var/www/html
>>>>>>> server = awsbox
>>>>>>> user = www-data
>>>>>>> path = /var/www/html
>>>>>>> delete = 0
>>>>>>> ssh_options = -i /root/.ssh/aws
>>>>>>> [[SSH]]
>>>>>>>ssh_options = -i /root/.ssh/aws
>>>>>>> 
>>>>>>> I have awsbox in my host file, pointing to the correct ip address
>>>>>>> 
>>>>>>> in my .ssh/config I have:
>>>>>>> 
>>>>>>> Host awsbox
>>>>>>> user www-data
>>>>>>> IdentityFile /root/.ssh/aws
>>>>>>> 
>>>>>>> 
>>>>>>> when I start the Weewx server, I get this error 
>>>>>>> 
>>>>>>> DEBUG weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', 
>>>>>>> '--stats', '-e', 'ssh', '/tmp/weather34/serverdata/', 
>>>>>>> 'www-...@123.123.123.123:/var/www/html/weather34/serverdata']]
>>>>>>> 
>>>>>>> (IP changed for security)
>>>>>>> 
>>>>>>> I can't see where the ip address is coming from. Is weewx or rsync 
>>>>>>> converting it from the host file?
>>>>>>> 
>>>>>>> Also, It seems to be ignoring the ssh_options parameter (though I could 
>>>>>>> be using the wrong) But I hope that it isn't required, as I guess that 
>>>>>>> rsync should be using the config in .ssh/config
>>>>>>> 
>>>>>>> Any help would be greatly appreciated
>>>>>>> 
>>>>>>> This is all on the latest version of 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+...@googlegroups.com.
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/weewx-user/e84797ff-e452-4099-bac1-e032a1f6d903n%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/7a2e36e8-00fe-491e-acd7-01fca28be7a0n%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/6ce83cde-458e-4058-917c-f8b6b10d44d6n%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/540444EA-03F2-4A72-BCD0-D36E73A5D5F4%40johnkline.com.

Re: [weewx-user] RSYNC is using IP address and not host name

['John Kline' via weewx-user]

Did you restart weewx after changing weewx.conf?

> On Aug 9, 2022, at 10:05 AM, Dan Jones  wrote:
> 
> ssh stanza removed
> 
> debug on 1
> 
> output still the same:
> 
> DEBUG weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', 
> '--stats', '-e', 'ssh', '/tmp/weather34/serverdata/', 
> 'www-data@123.123.123.123:/var/www/html/weather34/serverdata']]
> 
> 
> Still ignoring ssh_options and still using IP address rather than host name.
> 
> Surely ssh_options wouldn't be needed if it used the host name, and then 
> rsync would use .ssh/config with the correct host name configuration?
> 
> 
>> On Tuesday, August 9, 2022 at 5:09:51 PM UTC+1 jo...@johnkline.com wrote:
>> Oh, I didn’t notice the SSH stanza, remove that line.  ssh_options should be 
>> directly under RSYNC.
>> 
 On Aug 9, 2022, at 9:01 AM, bell...@gmail.com  wrote:
 
>>> I don’t have a [[SSH]] stanza. Try removing that.
>> 
>>> rich
>>> 
 On Tuesday, 9 August 2022 at 11:53:57 UTC-4 dan.rh...@gmail.com wrote:
 Yep, correct, its the private key. 
 
 But it looks like that whole ssh_options bit is being ignored. I can't see 
 it in the logs when I tail them. 
 
> On Tuesday, August 9, 2022 at 4:52:18 PM UTC+1 jo...@johnkline.com wrote:
> -i should refer to a file that contains a private key.  Is that the case?
> 
>>> On Aug 9, 2022, at 8:14 AM, Dan Jones  wrote:
>>> 
>> My weewx.conf contains this:
> 
>> 
>> [[RSYNC]]
>> skin = Rsync
>> HTML_ROOT = /var/www/html
>> server = awsbox
>> user = www-data
>> path = /var/www/html
>> delete = 0
>> ssh_options = -i /root/.ssh/aws
>> [[SSH]]
>>ssh_options = -i /root/.ssh/aws
>> 
>> I have awsbox in my host file, pointing to the correct ip address
>> 
>> in my .ssh/config I have:
>> 
>> Host awsbox
>> user www-data
>> IdentityFile /root/.ssh/aws
>> 
>> 
>> when I start the Weewx server, I get this error 
>> 
>> DEBUG weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', 
>> '--stats', '-e', 'ssh', '/tmp/weather34/serverdata/', 
>> 'www-...@123.123.123.123:/var/www/html/weather34/serverdata']]
>> 
>> (IP changed for security)
>> 
>> I can't see where the ip address is coming from. Is weewx or rsync 
>> converting it from the host file?
>> 
>> Also, It seems to be ignoring the ssh_options parameter (though I could 
>> be using the wrong) But I hope that it isn't required, as I guess that 
>> rsync should be using the config in .ssh/config
>> 
>> Any help would be greatly appreciated
>> 
>> This is all on the latest version of 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/e84797ff-e452-4099-bac1-e032a1f6d903n%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/7a2e36e8-00fe-491e-acd7-01fca28be7a0n%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/6ce83cde-458e-4058-917c-f8b6b10d44d6n%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/AE34A74C-F383-4D53-9A98-DE0812E22BDD%40johnkline.com.

Re: [weewx-user] RSYNC is using IP address and not host name

['John Kline' via weewx-user]

Oh, I didn’t notice the SSH stanza, remove that line.  ssh_options should be 
directly under RSYNC.

> On Aug 9, 2022, at 9:01 AM, bell...@gmail.com  wrote:
> 
> I don’t have a [[SSH]] stanza. Try removing that.
> rich
> 
>> On Tuesday, 9 August 2022 at 11:53:57 UTC-4 dan.rh...@gmail.com wrote:
>> Yep, correct, its the private key. 
>> 
>> But it looks like that whole ssh_options bit is being ignored. I can't see 
>> it in the logs when I tail them. 
>> 
>>> On Tuesday, August 9, 2022 at 4:52:18 PM UTC+1 jo...@johnkline.com wrote:
>>> -i should refer to a file that contains a private key.  Is that the case?
>>> 
> On Aug 9, 2022, at 8:14 AM, Dan Jones  wrote:
> 
 My weewx.conf contains this:
>>> 
 
 [[RSYNC]]
 skin = Rsync
 HTML_ROOT = /var/www/html
 server = awsbox
 user = www-data
 path = /var/www/html
 delete = 0
 ssh_options = -i /root/.ssh/aws
 [[SSH]]
ssh_options = -i /root/.ssh/aws
 
 I have awsbox in my host file, pointing to the correct ip address
 
 in my .ssh/config I have:
 
 Host awsbox
 user www-data
 IdentityFile /root/.ssh/aws
 
 
 when I start the Weewx server, I get this error 
 
 DEBUG weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', 
 '--stats', '-e', 'ssh', '/tmp/weather34/serverdata/', 
 'www-...@123.123.123.123:/var/www/html/weather34/serverdata']]
 
 (IP changed for security)
 
 I can't see where the ip address is coming from. Is weewx or rsync 
 converting it from the host file?
 
 Also, It seems to be ignoring the ssh_options parameter (though I could be 
 using the wrong) But I hope that it isn't required, as I guess that rsync 
 should be using the config in .ssh/config
 
 Any help would be greatly appreciated
 
 This is all on the latest version of 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+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/e84797ff-e452-4099-bac1-e032a1f6d903n%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/7a2e36e8-00fe-491e-acd7-01fca28be7a0n%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/CBB32A30-AB6D-4EEC-934E-1485CD416627%40johnkline.com.

Re: [weewx-user] RSYNC is using IP address and not host name

['John Kline' via weewx-user]

Also, add:
debug = 1
In your weewx.conf file and restart WeeWX.

Your log will then contain output of the form:
rsyncupload: cmd: 

That will tell you if -i is being passed (likely it is) and also let you try it 
from the command line.

> On Aug 9, 2022, at 8:55 AM, John Kline  wrote:
> 
> 
> Just to double check, it’s the private key and not the directory that 
> contains the private key?
> 
>>> On Aug 9, 2022, at 8:54 AM, Dan Jones  wrote:
>>> 
>> Yep, correct, its the private key. 
>> 
>> But it looks like that whole ssh_options bit is being ignored. I can't see 
>> it in the logs when I tail them. 
>> 
>>> On Tuesday, August 9, 2022 at 4:52:18 PM UTC+1 jo...@johnkline.com wrote:
>>> -i should refer to a file that contains a private key.  Is that the case?
>>> 
>>>>> On Aug 9, 2022, at 8:14 AM, Dan Jones  wrote:
>>>>> 
>>>> My weewx.conf contains this:
>>> 
>>>> 
>>>> [[RSYNC]]
>>>> skin = Rsync
>>>> HTML_ROOT = /var/www/html
>>>> server = awsbox
>>>> user = www-data
>>>> path = /var/www/html
>>>> delete = 0
>>>> ssh_options = -i /root/.ssh/aws
>>>> [[SSH]]
>>>>ssh_options = -i /root/.ssh/aws
>>>> 
>>>> I have awsbox in my host file, pointing to the correct ip address
>>>> 
>>>> in my .ssh/config I have:
>>>> 
>>>> Host awsbox
>>>> user www-data
>>>> IdentityFile /root/.ssh/aws
>>>> 
>>>> 
>>>> when I start the Weewx server, I get this error 
>>>> 
>>>> DEBUG weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', 
>>>> '--stats', '-e', 'ssh', '/tmp/weather34/serverdata/', 
>>>> 'www-...@123.123.123.123:/var/www/html/weather34/serverdata']]
>>>> 
>>>> (IP changed for security)
>>>> 
>>>> I can't see where the ip address is coming from. Is weewx or rsync 
>>>> converting it from the host file?
>>>> 
>>>> Also, It seems to be ignoring the ssh_options parameter (though I could be 
>>>> using the wrong) But I hope that it isn't required, as I guess that rsync 
>>>> should be using the config in .ssh/config
>>>> 
>>>> Any help would be greatly appreciated
>>>> 
>>>> This is all on the latest version of 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+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/e84797ff-e452-4099-bac1-e032a1f6d903n%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/2240d22e-6787-4ac6-a6ba-7a4fb231da96n%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/9C7EF1B6-814D-4009-99B6-F3090A869D49%40johnkline.com.

Re: [weewx-user] RSYNC is using IP address and not host name

['John Kline' via weewx-user]

Just to double check, it’s the private key and not the directory that contains 
the private key?

> On Aug 9, 2022, at 8:54 AM, Dan Jones  wrote:
> 
> Yep, correct, its the private key. 
> 
> But it looks like that whole ssh_options bit is being ignored. I can't see it 
> in the logs when I tail them. 
> 
>> On Tuesday, August 9, 2022 at 4:52:18 PM UTC+1 jo...@johnkline.com wrote:
>> -i should refer to a file that contains a private key.  Is that the case?
>> 
 On Aug 9, 2022, at 8:14 AM, Dan Jones  wrote:
 
>>> My weewx.conf contains this:
>> 
>>> 
>>> [[RSYNC]]
>>> skin = Rsync
>>> HTML_ROOT = /var/www/html
>>> server = awsbox
>>> user = www-data
>>> path = /var/www/html
>>> delete = 0
>>> ssh_options = -i /root/.ssh/aws
>>> [[SSH]]
>>>ssh_options = -i /root/.ssh/aws
>>> 
>>> I have awsbox in my host file, pointing to the correct ip address
>>> 
>>> in my .ssh/config I have:
>>> 
>>> Host awsbox
>>> user www-data
>>> IdentityFile /root/.ssh/aws
>>> 
>>> 
>>> when I start the Weewx server, I get this error 
>>> 
>>> DEBUG weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', 
>>> '--stats', '-e', 'ssh', '/tmp/weather34/serverdata/', 
>>> 'www-...@123.123.123.123:/var/www/html/weather34/serverdata']]
>>> 
>>> (IP changed for security)
>>> 
>>> I can't see where the ip address is coming from. Is weewx or rsync 
>>> converting it from the host file?
>>> 
>>> Also, It seems to be ignoring the ssh_options parameter (though I could be 
>>> using the wrong) But I hope that it isn't required, as I guess that rsync 
>>> should be using the config in .ssh/config
>>> 
>>> Any help would be greatly appreciated
>>> 
>>> This is all on the latest version of 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/e84797ff-e452-4099-bac1-e032a1f6d903n%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/2240d22e-6787-4ac6-a6ba-7a4fb231da96n%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/DF74191E-EC21-495C-A048-DCB46C1A205C%40johnkline.com.

Re: [weewx-user] Forecast stopped working

['John Kline' via weewx-user]

You are running a version of the forecast extension that is incompatible with with WeeWX 4/Python 3.Please install this version:https://github.com/chaunceygardiner/weewx-forecastOn Aug 5, 2022, at 5:15 PM, Mike Hutchins  wrote:
  

  
  
I did not upgrade. I installed it in January and took a few days
  to get it going. Everything was running until July 1. I do not
  believe I changed anything but possible. It's running on a pi 3+
  along with PIHOLE.

mylog attached.
Thanks

On 8/5/2022 6:37 PM, 'John Kline' via
  weewx-user wrote:


  
  

Hmmm.  Did you upgrade WeeWX from 3.x to 4.x?


Rather than going back and forth with questions,
  please follow the instructions here:
https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user
so that we can see what versions of everything
  you are using.

  On Aug 5, 2022, at 4:01 PM, MikeH
 wrote:

  


  
PYTHONPATH=/usr/share/weewx python3
  /usr/share/weewx/user/forecast.py --method=NWS --foid=FWD
  --lid=TXZ118


Returns

  Traceback (most recent call last):
    File "/usr/share/weewx/user/forecast.py", line 5132, in
  
      main()
    File "/usr/share/weewx/user/forecast.py", line 5070, in
  main
      lines = NWSExtractLocation(fcast, options.lid)
    File "/usr/share/weewx/user/forecast.py", line 1807, in
  NWSExtractLocation
      if line.startswith(lid):
  TypeError: startswith first arg must be bytes or a tuple
  of bytes, not str


  On Friday, August 5,
2022 at 5:07:09 PM UTC-5 an oldman wrote:
  
  
you could try
PYTHONPATH=/usr/share/weewx python
  /usr/share/weewx/user/forecast.py --method=NWS
  --foid=FWD --lid=TXZ118
to see if that will works.


  On Friday, August
5, 2022 at 3:04:50 PM UTC-5 MikeH wrote:
  
  What is the
latest version and where is it?  All I see on gethub
is 3.4.0b1


  On Friday,
August 5, 2022 at 11:50:37 AM UTC-5 jo...@johnkline.com
wrote:
  


  

  

  


  

  
One last thing, you are using
  a rather old version of forecast.  Using
  an up-to-date version will let us
  eliminate the version as the cause.

  On Aug 5, 2022, at
        9:44 AM, John Kline <jo...@johnkline.com>
wrote:

  


  

  

  


  

  

  
It’s done every three
  hours by default (10800 seconds).  You
  can hurry it along by temporarily
  adding a shorter interval of 5 minutes
  (300 seconds) in weewx.conf and
  restarting weewx:



  [Forecast]
      data_binding =
forecast_binding
      [[NWS]]
          lid = TXZ118
          foid = FWD
          interval = 300



BTW, I just tried this
 

Re: [weewx-user] Forecast stopped working

['John Kline' via weewx-user]

Hmmm.  Did you upgrade WeeWX from 3.x to 4.x?

Rather than going back and forth with questions, please follow the instructions 
here:
https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user
so that we can see what versions of everything you are using.

> On Aug 5, 2022, at 4:01 PM, MikeH  wrote:
> 
> PYTHONPATH=/usr/share/weewx python3 /usr/share/weewx/user/forecast.py 
> --method=NWS --foid=FWD --lid=TXZ118
> 
> Returns
> 
> Traceback (most recent call last):
>   File "/usr/share/weewx/user/forecast.py", line 5132, in 
> main()
>   File "/usr/share/weewx/user/forecast.py", line 5070, in main
> lines = NWSExtractLocation(fcast, options.lid)
>   File "/usr/share/weewx/user/forecast.py", line 1807, in NWSExtractLocation
> if line.startswith(lid):
> TypeError: startswith first arg must be bytes or a tuple of bytes, not str
> On Friday, August 5, 2022 at 5:07:09 PM UTC-5 an oldman wrote:
>> you could try
>> PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/forecast.py 
>> --method=NWS --foid=FWD --lid=TXZ118
>> to see if that will works.
>> 
>> On Friday, August 5, 2022 at 3:04:50 PM UTC-5 MikeH wrote:
>>> What is the latest version and where is it?  All I see on gethub is 3.4.0b1
>>> 
>>> On Friday, August 5, 2022 at 11:50:37 AM UTC-5 jo...@johnkline.com wrote:
>>>> 
>>> 
>>>> One last thing, you are using a rather old version of forecast.  Using an 
>>>> up-to-date version will let us eliminate the version as the cause.
>>>> 
>>>>> On Aug 5, 2022, at 9:44 AM, John Kline  wrote:
>>>>> 
>>> 
>>>>> It’s done every three hours by default (10800 seconds).  You can hurry it 
>>>>> along by temporarily adding a shorter interval of 5 minutes (300 seconds) 
>>>>> in weewx.conf and restarting weewx:
>>>>> 
>>>>> [Forecast]
>>>>> data_binding = forecast_binding
>>>>> [[NWS]]
>>>>> lid = TXZ118
>>>>> foid = FWD
>>>>> interval = 300
>>>>> 
>>>>> BTW, I just tried this and had no problem downloading your forecast.
>>>>> 
>>>>>> On Aug 5, 2022, at 9:30 AM, MikeH  wrote:
>>>>>> Also this sorry.
>>>>>> 
>>>>>> Aug  5 11:15:48 PIHOLE weewx[12658] DEBUG weewx.engine: Loading service 
>>>>>> user.forecast.NWSForecast
>>>>>> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: forecast 
>>>>>> version 3.4.0b1
>>>>>> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: last forecast 
>>>>>> issued 2022-07-01 05:07:00 CDT (1656670020), requested 2022-07-01 
>>>>>> 09:45:32 CDT (1656686732)
>>>>>> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: 
>>>>>> interval=10800 max_age=604800 lid=TXZ118 foid=FWD
>>>>>> Aug  5 11:15:48 PIHOLE weewx[12658] DEBUG weewx.engine: Finished loading 
>>>>>> service user.forecast.NWSForecast
>>>>>> 
>>>>>> On Friday, August 5, 2022 at 10:45:21 AM UTC-5 jo...@johnkline.com wrote:
>>>>>>> Your log snippet doesn’t show any attempts to download the forecast.  
>>>>>>> 
>>>>>>> Would you look at your logs for entries of the form below (of course, 
>>>>>>> not exactly the same as this is for my forecast) and send them?
>>>>>>> 
>>>>>>> INFO user.forecast: NWSThread: NWS: downloading forecast from 
>>>>>>> 'http://forecast.weather.gov/product.php?site=NWS=PFM=txt=MTR'
>>>>>>> 
>>>>>>>> On Aug 5, 2022, at 6:57 AM, MikeH  wrote:
>>>>>>>> Around July 1 my forecast from NWS stopped working. I tried 
>>>>>>>> reinstalling and still cannot get data. Logs show it running and 
>>>>>>>> generating pages but they all show Now forecast data for NWS. I am 
>>>>>>>> using lid=TXZ118 foid=FWD.
>>>>>>> 
>>>>>>>> 
>>>>>>>> Not sure where to look if I am actually getting data from nws or not.
>>>>>>>> 
>>>>>>>> Files and logs attached.
>>>>>>>> 
>>>>>>>> Thanks
>>>>>>> 
>>>>>>>> -- 
>>>>>>>> You received this mes

Re: [weewx-user] Forecast stopped working

['John Kline' via weewx-user]

One last thing, you are using a rather old version of forecast.  Using an 
up-to-date version will let us eliminate the version as the cause.

> On Aug 5, 2022, at 9:44 AM, John Kline  wrote:
> 
> It’s done every three hours by default (10800 seconds).  You can hurry it 
> along by temporarily adding a shorter interval of 5 minutes (300 seconds) in 
> weewx.conf and restarting weewx:
> 
> [Forecast]
> data_binding = forecast_binding
> [[NWS]]
> lid = TXZ118
> foid = FWD
> interval = 300
> 
> BTW, I just tried this and had no problem downloading your forecast.
> 
>> On Aug 5, 2022, at 9:30 AM, MikeH  wrote:
>> Also this sorry.
>> 
>> Aug  5 11:15:48 PIHOLE weewx[12658] DEBUG weewx.engine: Loading service 
>> user.forecast.NWSForecast
>> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: forecast version 
>> 3.4.0b1
>> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: last forecast 
>> issued 2022-07-01 05:07:00 CDT (1656670020), requested 2022-07-01 09:45:32 
>> CDT (1656686732)
>> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: interval=10800 
>> max_age=604800 lid=TXZ118 foid=FWD
>> Aug  5 11:15:48 PIHOLE weewx[12658] DEBUG weewx.engine: Finished loading 
>> service user.forecast.NWSForecast
>> 
>> On Friday, August 5, 2022 at 10:45:21 AM UTC-5 jo...@johnkline.com wrote:
>>> Your log snippet doesn’t show any attempts to download the forecast.  
>>> 
>>> Would you look at your logs for entries of the form below (of course, not 
>>> exactly the same as this is for my forecast) and send them?
>>> 
>>> INFO user.forecast: NWSThread: NWS: downloading forecast from 
>>> 'http://forecast.weather.gov/product.php?site=NWS=PFM=txt=MTR'
>>> 
>>>> On Aug 5, 2022, at 6:57 AM, MikeH  wrote:
>>>> Around July 1 my forecast from NWS stopped working. I tried reinstalling 
>>>> and still cannot get data. Logs show it running and generating pages but 
>>>> they all show Now forecast data for NWS. I am using lid=TXZ118 foid=FWD.
>>> 
>>>> 
>>>> Not sure where to look if I am actually getting data from nws or not.
>>>> 
>>>> Files and logs attached.
>>>> 
>>>> 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+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/b95d50a9-082c-40e9-9ec8-925748304776n%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/d4d6f56e-8b14-4765-a4dc-9368b49282fan%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/B362244E-89E9-473E-A80E-6E7F23A340ED%40johnkline.com.

Re: [weewx-user] Forecast stopped working

['John Kline' via weewx-user]

It’s done every three hours by default (10800 seconds).  You can hurry it along 
by temporarily adding a shorter interval of 5 minutes (300 seconds) in 
weewx.conf and restarting weewx:

[Forecast]
data_binding = forecast_binding
[[NWS]]
lid = TXZ118
foid = FWD
interval = 300

BTW, I just tried this and had no problem downloading your forecast.

> On Aug 5, 2022, at 9:30 AM, MikeH  wrote:
> 
> Also this sorry.
> 
> Aug  5 11:15:48 PIHOLE weewx[12658] DEBUG weewx.engine: Loading service 
> user.forecast.NWSForecast
> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: forecast version 
> 3.4.0b1
> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: last forecast 
> issued 2022-07-01 05:07:00 CDT (1656670020), requested 2022-07-01 09:45:32 
> CDT (1656686732)
> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: interval=10800 
> max_age=604800 lid=TXZ118 foid=FWD
> Aug  5 11:15:48 PIHOLE weewx[12658] DEBUG weewx.engine: Finished loading 
> service user.forecast.NWSForecast
> 
>> On Friday, August 5, 2022 at 10:45:21 AM UTC-5 jo...@johnkline.com wrote:
>> Your log snippet doesn’t show any attempts to download the forecast.  
>> 
>> Would you look at your logs for entries of the form below (of course, not 
>> exactly the same as this is for my forecast) and send them?
>> 
>> INFO user.forecast: NWSThread: NWS: downloading forecast from 
>> 'http://forecast.weather.gov/product.php?site=NWS=PFM=txt=MTR'
>> 
 On Aug 5, 2022, at 6:57 AM, MikeH  wrote:
 
>>> Around July 1 my forecast from NWS stopped working. I tried reinstalling 
>>> and still cannot get data. Logs show it running and generating pages but 
>>> they all show Now forecast data for NWS. I am using lid=TXZ118 foid=FWD.
>> 
>>> 
>>> Not sure where to look if I am actually getting data from nws or not.
>>> 
>>> Files and logs attached.
>>> 
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/b95d50a9-082c-40e9-9ec8-925748304776n%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/d4d6f56e-8b14-4765-a4dc-9368b49282fan%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/C869C2DD-6781-48CE-B631-BFB1E1057C46%40johnkline.com.

Re: [weewx-user] Forecast stopped working

['John Kline' via weewx-user]

Your log snippet doesn’t show any attempts to download the forecast.  Would you look at your logs for entries of the form below (of course, not exactly the same as this is for my forecast) and send them?INFO user.forecast: NWSThread: NWS: downloading forecast from 'http://forecast.weather.gov/product.php?site=NWS=PFM=txt=MTR'On Aug 5, 2022, at 6:57 AM, MikeH  wrote:Around July 1 my forecast from NWS stopped working. I tried reinstalling and still cannot get data. Logs show it running and generating pages but they all show Now forecast data for NWS. I am using lid=TXZ118 foid=FWD.Not sure where to look if I am actually getting data from nws or not.Files and logs attached.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/b95d50a9-082c-40e9-9ec8-925748304776n%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/BD84C608-A9BF-4313-896D-A0778F1314F3%40johnkline.com.
messages

4 17:53:31 PIHOLE /weewxd: forecast: MainThread: Zambretti: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: Zambretti: interval=600 
max_age=604800 winddir_period=1800 pressure_period=10800 hemisphere=NORTH 
lower_pressure=950.0 upper_pressure=1050.0
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: NWS: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: NWS: interval=10800 
max_age=604800 lid=TXZ118 foid=FWD
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: WU: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: OWM: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: UKMO: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: Aeris: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: WWO: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: DS: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: XTide: forecast version 
3.4.0b1


syslog
--
4 17:55:33 PIHOLE /weewxd: forecast: MainThread: Zambretti: starting thread
Aug  4 17:55:33 PIHOLE /weewxd: forecast: MainThread: NWS: starting thread
Aug  4 17:55:33 PIHOLE weewx[12959] DEBUG weewx.reportengine: Running reports 
for latest time in the database.
Aug  4 17:55:33 PIHOLE weewx[12959] DEBUG weewx.reportengine: Running report 
'SeasonsReport'
Aug  4 17:55:33 PIHOLE weewx[12959] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 'SeasonsReport'
Aug  4 17:55:33 PIHOLE weewx[12959] DEBUG weewx.cheetahgenerator: Using search 
list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'weewx.cheetahgenerator.JSONHelpers']
Aug  4 17:55:33 PIHOLE weewx[12959] DEBUG weewx.manager: Daily summary version 
is 4.0
Aug  4 17:55:38 PIHOLE weewx[12959] INFO weewx.cheetahgenerator: Generated 8 
files for report SeasonsReport in 4.64 seconds
Aug  4 17:55:38 PIHOLE weewx[12959] DEBUG weewx.manager: Daily summary version 
is 4.0
Aug  4 17:55:39 PIHOLE weewx[12959] INFO weewx.imagegenerator: Generated 15 
images for report SeasonsReport in 1.27 seconds
Aug  4 17:55:39 PIHOLE weewx[12959] INFO weewx.reportengine: Copied 5 files to 
/var/www/html/weewx
Aug  4 17:55:39 PIHOLE weewx[12959] DEBUG weewx.reportengine: Running report 
'SmartphoneReport'
Aug  4 17:55:39 PIHOLE weewx[12959] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Smartphone/skin.conf for report 
'SmartphoneReport'
Aug  4 17:55:39 PIHOLE weewx[12959] DEBUG weewx.cheetahgenerator: Using search 
list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'weewx.cheetahgenerator.JSONHelpers']
Aug  4 17:55:39 PIHOLE weewx[12959] DEBUG weewx.manager: Daily summary version 
is 4.0
Aug  4 17:55:40 PIHOLE weewx[12959] INFO weewx.cheetahgenerator: Generated 6 
files for report SmartphoneReport in 0.34 seconds
Aug  4 17:55:40 PIHOLE weewx[12959] DEBUG weewx.manager: Daily summary version 
is 4.0
Aug  4 17:55:40 PIHOLE weewx[12959] INFO weewx.imagegenerator: Generated 6 
images for report SmartphoneReport in 0.47 seconds
Aug  4 17:55:40 PIHOLE weewx[12959] INFO weewx.reportengine: Copied 6 files to 

Re: [weewx-user] Re: National Weather Service location IDs

['John Kline' via weewx-user]

> The newer api.weather.gov can return a lot of detailed forecast information 
> for quite specific locations using gridpoints, but that's not integrated into 
> weewx AFAIK.


https://github.com/chaunceygardiner/weewx-nws

> On Jul 9, 2022, at 11:22 AM, wfs...@gmail.com  wrote:
> 
> Yes, Mike I think you're right.  The weewx forecasting extension looks to be 
> scraping those PFM reports for its data, so you can only choose from those 
> zones where a PFM is generated.
> The newer api.weather.gov can return a lot of detailed forecast information 
> for quite specific locations using gridpoints, but that's not integrated into 
> weewx AFAIK.
> 
> Walt
> 
>> On Friday, July 8, 2022 at 10:56:16 AM UTC-5 MikeQ wrote:
>> Does someone here understand how the NWS generates a forecast for a specific 
>> location?  I used the API link above and it says my forecast zone is IDZ033. 
>>  When I put this in weewx I get the following error:
>> 
>> Jul  8 09:30:20 weatherpi weewxd: forecast: NWSThread: NWS: no PFM found for 
>> IDZ033 in forecast from BOI
>> Jul  8 09:30:20 weatherpi weewxd: forecast: NWSThread: NWS: terminating 
>> thread
>> 
>> If I go to the PFM link above, there are only 5 PFMs for the BOI forecast 
>> office all located at airports.  If I go to weather.gov, put in my zip code, 
>> and click on the map, it puts my lat/lon in URL and generates a forecast for 
>> that location.  The forecast for the closest PFM, which is over 90 miles 
>> away, is different than the one generated on the forecast web page.  I would 
>> like the more accurate forecast, but it doesn't look like the forecast 
>> module in weewx supports anything other than PFMs?
>> 
>>> On Friday, July 8, 2022 at 6:18:51 AM UTC-6 mcu...@gmail.com wrote:
>>> I appreciate the helpthank you
>>> 
>>> 
 On Wednesday, July 6, 2022 at 10:45:51 PM UTC-4 an oldman wrote:
 if you are looking for the pfm try this address
 https://forecast.weather.gov/product_sites.php?site=NWS=PFM
 it list all the pfms
 
> On Wednesday, July 6, 2022 at 9:11:39 PM UTC-5 vince wrote:
> That is a GREAT find.   Comes up right on the money for me.
> 
> Forecast office is SEW(foid in weewx.conf)
> Forecast zone is WAZ558   (lid in weewx.conf)
> 
>> On Wednesday, July 6, 2022 at 6:33:23 PM UTC-7 wfs...@gmail.com wrote:
>> if you plug your lat and lon into the weather.gov api, a la
>> https://api.weather.gov/points/39.7832,-89.6644
>> you'll get a bunch of info back that might contain what you're looking 
>> for.  I'm not familiar with the terms LID and FOID
>> In my case it tells me
>> my forecast office is ILX
>> my grid coordinates are 46,54
>> my forecast zone is ILZ051
>> my county zone is ILC167
>> my fire weather zone is ILZ051
>> 
>> api documentation at 
>> API Web Service (weather.gov)
>> 
>>> On Wednesday, July 6, 2022 at 3:41:56 PM UTC-5 mcu...@gmail.com wrote:
>>> I have been relentlessly searching for a list of NWS LIDs for the 
>>> forecast module and cannot even find a mention of them on their site or 
>>> Wikican somone push me in the right direction I am trying to get 
>>> the Foid and lid for Columbia SC.  I beleive the Foid to be CAE but the 
>>> 6 digit ID is the problem. 
>>> Thank-you
> 
> -- 
> 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/e00b92d8-e852-47f3-b50c-185ecf3aa945n%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/4A05B1A1-A8B5-4C66-87BC-97DAE7A4D648%40johnkline.com.

Re: [weewx-user] Re: Help with forecast

['John Kline' via weewx-user]

Our emails crossed.  I’m glad you got it working.

> On Jun 15, 2022, at 7:53 AM, John Kline  wrote:
> 
> 
> It sure looks like your forecast.sdb archive table got created as a weewx 
> archive table.  If so, it wasn’t the forecast extension that did it.  Perhaps 
> the binding were misconfigured when forecast.sdb was created.
> 
> Before we delete it, let’s have a look at it.
> 
> Please paste the output of (adjusting the path of forecast.sdb as necessary):
> 
> $ sqlite3 /home/weewx/archive/forecast.sdb 
> SQLite version 3.34.1 2021-01-20 14:10:07
> Enter ".help" for usage hints.
> sqlite> PRAGMA table_info(archive);
> 
> 
> If so, delete your forecast.sdb file and restart weewx.
> 
>>> On Jun 15, 2022, at 7:09 AM, Timothy Reaves  
>>> wrote:
>>> 
>> 
>> I'm going to start looking more at the python code now.
>> 
>> [DataBindings]
>> 
>>   [[wx_binding]]
>> # The database must match one of the sections in [Databases].
>> # This is likely to be the only option you would want to change.
>> database = archive_sqlite
>> # The name of the table within the database
>> table_name = archive
>> # The manager handles aggregation of data for historical summaries
>> manager = weewx.manager.DaySummaryManager
>> # The schema defines the structure of the database.
>> # It is *only* used when the database is created.
>> schema = schemas.wview_extended.schema
>> 
>>   [[forecast_binding]]
>> manager = weewx.manager.Manager
>> schema = user.forecast.schema
>> table_name = archive
>> database = forecast_sqlite
>> 
>> ##
>> 
>> #   This section defines various databases.
>> 
>> [Databases]
>> 
>>   # A SQLite database is simply a single file
>>   [[archive_sqlite]]
>> database_name = weewx.sdb
>> database_type = SQLite
>>   
>>   [[forecast_sqlite]]
>> database_type = SQLite
>> database_name = forecast.sdb
>> 
>> 
>>> On Wednesday, June 15, 2022 at 8:22:37 AM UTC-4 jo...@johnkline.com wrote:
>>> This looks like a clear case of forecast being pointed to the wrong 
>>> database.
>>> 
>>> Please send the data_binding line in the [forecast[ section of weewx.conf.
>>> Also send the [DataBindings] section of weewx.conf.
>>> 
>>>>> On Jun 13, 2022, at 6:49 AM, Timothy Reaves  
>>>>> wrote:
>>>>> 
>>>> Thank you both for the responses.
>>> 
>>>> 
>>>> Doug, that is the extension I wrote this post about.  I have followed the 
>>>> instructions, and receive the error I'd posted. So I have all of the 
>>>> configuration that the plugin lists.  When I enable the archive_service, I 
>>>> get the error.  So for some reason it doesn't seem to be connecting to the 
>>>> correct database.  Here is the snippet from my configuration regarding the 
>>>> databases:
>>>> 
>>>> [Databases]
>>>> 
>>>> # A SQLite database is simply a single file
>>>> [[archive_sqlite]]
>>>> database_name = weewx.sdb
>>>> database_type = SQLite
>>>> 
>>>> # MySQL
>>>> [[archive_mysql]]
>>>> database_name = weewx
>>>> database_type = MySQL
>>>> 
>>>> [[forecast_sqlite]]
>>>> database_type = SQLite
>>>> database_name = forecast.sdb
>>>> 
>>>> [[forecast_mysql]]
>>>> database_type = MySql
>>>> database_name = forecast
>>>> 
>>>>>> On Friday, June 10, 2022 at 11:22:26 AM UTC-4 do...@dougjenkins.com 
>>>>>> wrote:
>>>>>> Tim:
>>>>>> 
>>>>>> The forecast module uses a completely different schema and database. 
>>>>>> What you need to do is configure the module to a separate database and 
>>>>>> in your skin, bring in the data to be presented.
>>>>>> 
>>>>>> I personally use John Kline's weewx forecast driver ( GitHub - 
>>>>>> chaunceygardiner/weewx-forecast: forecasting extension for weewx) as it 
>>>>>> is being maintained and it works with the latest version of WeeWX 
>>>>>> (v4.8). You will need to look at the sample page

Re: [weewx-user] Re: Help with forecast

['John Kline' via weewx-user]

It sure looks like your forecast.sdb archive table got created as a weewx 
archive table.  If so, it wasn’t the forecast extension that did it.  Perhaps 
the binding were misconfigured when forecast.sdb was created.

Before we delete it, let’s have a look at it.

Please paste the output of (adjusting the path of forecast.sdb as necessary):

$ sqlite3 /home/weewx/archive/forecast.sdb 
SQLite version 3.34.1 2021-01-20 14:10:07
Enter ".help" for usage hints.
sqlite> PRAGMA table_info(archive);


If so, delete your forecast.sdb file and restart weewx.

> On Jun 15, 2022, at 7:09 AM, Timothy Reaves  
> wrote:
> 
> 
> I'm going to start looking more at the python code now.
> 
> [DataBindings]
> 
>   [[wx_binding]]
> # The database must match one of the sections in [Databases].
> # This is likely to be the only option you would want to change.
> database = archive_sqlite
> # The name of the table within the database
> table_name = archive
> # The manager handles aggregation of data for historical summaries
> manager = weewx.manager.DaySummaryManager
> # The schema defines the structure of the database.
> # It is *only* used when the database is created.
> schema = schemas.wview_extended.schema
> 
>   [[forecast_binding]]
> manager = weewx.manager.Manager
> schema = user.forecast.schema
> table_name = archive
> database = forecast_sqlite
> 
> ##
> 
> #   This section defines various databases.
> 
> [Databases]
> 
>   # A SQLite database is simply a single file
>   [[archive_sqlite]]
> database_name = weewx.sdb
> database_type = SQLite
>   
>   [[forecast_sqlite]]
> database_type = SQLite
> database_name = forecast.sdb
> 
> 
>> On Wednesday, June 15, 2022 at 8:22:37 AM UTC-4 jo...@johnkline.com wrote:
>> This looks like a clear case of forecast being pointed to the wrong database.
>> 
>> Please send the data_binding line in the [forecast[ section of weewx.conf.
>> Also send the [DataBindings] section of weewx.conf.
>> 
 On Jun 13, 2022, at 6:49 AM, Timothy Reaves  
 wrote:
 
>>> Thank you both for the responses.
>> 
>>> 
>>> Doug, that is the extension I wrote this post about.  I have followed the 
>>> instructions, and receive the error I'd posted. So I have all of the 
>>> configuration that the plugin lists.  When I enable the archive_service, I 
>>> get the error.  So for some reason it doesn't seem to be connecting to the 
>>> correct database.  Here is the snippet from my configuration regarding the 
>>> databases:
>>> 
>>> [Databases]
>>> 
>>> # A SQLite database is simply a single file
>>> [[archive_sqlite]]
>>> database_name = weewx.sdb
>>> database_type = SQLite
>>> 
>>> # MySQL
>>> [[archive_mysql]]
>>> database_name = weewx
>>> database_type = MySQL
>>> 
>>> [[forecast_sqlite]]
>>> database_type = SQLite
>>> database_name = forecast.sdb
>>> 
>>> [[forecast_mysql]]
>>> database_type = MySql
>>> database_name = forecast
>>> 
> On Friday, June 10, 2022 at 11:22:26 AM UTC-4 do...@dougjenkins.com wrote:
> Tim:
> 
> The forecast module uses a completely different schema and database. What 
> you need to do is configure the module to a separate database and in your 
> skin, bring in the data to be presented.
> 
> I personally use John Kline's weewx forecast driver ( GitHub - 
> chaunceygardiner/weewx-forecast: forecasting extension for weewx) as it 
> is being maintained and it works with the latest version of WeeWX (v4.8). 
> You will need to look at the sample pages that accompany the driver and 
> integrate the cheetah template code into your skin. 
> 
> Best practice is to copy your existing skin folder (eg seasons) to a 
> separate folder (seasons-forecast) and make the modifications there. I 
> usually use the wee_reports utility to generate the html when I make 
> changes to the skin.
> 
> Please let us know if you have any questions.
> 
> Doug
> www.largoweather.com
> 
> 
>> On Friday, June 10, 2022 at 10:22:59 AM UTC-4 RobbH wrote:
>> This is certainly not what you are looking for, but it is what I use to 
>> get NWS forecasts.
>> 
>> Here is a url for a forecast for a randomly selected location:
>> 
>> https://forecast.weather.gov/MapClick.php?lat=41.177010=-73.141963=0=english=text=2
>> 
>> Note where latitude and longitude are inserted. "TextType=2" at the end 
>> tells the server to include forecast graphics.
>> 
>> Several times a day, a cron job uses PhantomJS to retrieve that page and 
>> create an jpeg of the forecast graphics, which is then displayed on my 
>> weewx home page.
>> 
>> It usually works well enough for my purposes, but there are times when 
>> the forecast 

Re: [weewx-user] Re: Help with forecast

['John Kline' via weewx-user]

This looks like a clear case of forecast being pointed to the wrong database.

Please send the data_binding line in the [forecast[ section of weewx.conf.
Also send the [DataBindings] section of weewx.conf.

> On Jun 13, 2022, at 6:49 AM, Timothy Reaves  
> wrote:
> 
> Thank you both for the responses.
> 
> Doug, that is the extension I wrote this post about.  I have followed the 
> instructions, and receive the error I'd posted. So I have all of the 
> configuration that the plugin lists.  When I enable the archive_service, I 
> get the error.  So for some reason it doesn't seem to be connecting to the 
> correct database.  Here is the snippet from my configuration regarding the 
> databases:
> 
> [Databases]
> 
> # A SQLite database is simply a single file
> [[archive_sqlite]]
> database_name = weewx.sdb
> database_type = SQLite
> 
> # MySQL
> [[archive_mysql]]
> database_name = weewx
> database_type = MySQL
> 
> [[forecast_sqlite]]
> database_type = SQLite
> database_name = forecast.sdb
> 
> [[forecast_mysql]]
> database_type = MySql
> database_name = forecast
> 
>> On Friday, June 10, 2022 at 11:22:26 AM UTC-4 do...@dougjenkins.com wrote:
>> Tim:
>> 
>> The forecast module uses a completely different schema and database. What 
>> you need to do is configure the module to a separate database and in your 
>> skin, bring in the data to be presented.
>> 
>> I personally use John Kline's weewx forecast driver ( GitHub - 
>> chaunceygardiner/weewx-forecast: forecasting extension for weewx) as it is 
>> being maintained and it works with the latest version of WeeWX (v4.8). You 
>> will need to look at the sample pages that accompany the driver and 
>> integrate the cheetah template code into your skin. 
>> 
>> Best practice is to copy your existing skin folder (eg seasons) to a 
>> separate folder (seasons-forecast) and make the modifications there. I 
>> usually use the wee_reports utility to generate the html when I make changes 
>> to the skin.
>> 
>> Please let us know if you have any questions.
>> 
>> Doug
>> www.largoweather.com
>> 
>> 
>>> On Friday, June 10, 2022 at 10:22:59 AM UTC-4 RobbH wrote:
>>> This is certainly not what you are looking for, but it is what I use to get 
>>> NWS forecasts.
>>> 
>>> Here is a url for a forecast for a randomly selected location:
>>> 
>>> https://forecast.weather.gov/MapClick.php?lat=41.177010=-73.141963=0=english=text=2
>>> 
>>> Note where latitude and longitude are inserted. "TextType=2" at the end 
>>> tells the server to include forecast graphics.
>>> 
>>> Several times a day, a cron job uses PhantomJS to retrieve that page and 
>>> create an jpeg of the forecast graphics, which is then displayed on my 
>>> weewx home page.
>>> 
>>> It usually works well enough for my purposes, but there are times when the 
>>> forecast page is down, so I end up with a blank rectangle on the weewx page.
>>> 
>>> 
>>> 
 On Wednesday, June 8, 2022 at 12:16:33 PM UTC-4 Timothy Reaves wrote:
 Hello all.  I'm using the latest version running on a Pi 4, with a Davis 
 Vantage Pro.  I've had my site configured to use Aeris for forecasting, 
 and have never really liked it.  It just isn't as accurate as the NWS.  
 But I stuck with it.  Then last week, the Aeris forecast for my sight 
 started diverging significantly not only from the NWS, but also from the 
 actual Aeris site (which following the forecast link).  I don't know 
 what's going on, so I thought I'd jut stop using it.
 
 So I installed the Forecast user module.  When I start weewx now, it fails 
 to load with the error below.  In looking at the code, the database schema 
 isn't matching the extensions in-memory schema.  Don't know why.
 
 Has anyone an example of using NWS forecasts instead of Aeris?  Or can 
 provide any other ideas to troubleshoot?
 
 Thanks.
 
 Jun  8 10:12:34 pi4home weewx[12748] CRITICAL __main__:   
 Exception: NWS: schema mismatch: ['dateTime', 'usUnits', 'interval', 
 'altimeter', 'appTemp', 'appTemp1', 'barometer', 'batteryStatus1', 
 'batteryStatus2', 'batteryStatus3', 'batteryStatus4', 'batteryStatus5', 
 'batteryStatus6', 'batteryStatus7', 'batteryStatus8', 'cloudbase', 'co', 
 'co2', 'consBatteryVoltage', 'dewpoint', 'dewpoint1', 'ET', 'extraHumid1', 
 'extraHumid2', 'extraHumid3', 'extraHumid4', 'extraHumid5', 'extraHumid6', 
 'extraHumid7', 'extraHumid8', 'extraTemp1', 'extraTemp2', 'extraTemp3', 
 'extraTemp4', 'extraTemp5', 'extraTemp6', 'extraTemp7', 'extraTemp8', 
 'forecast', 'hail', 'hailBatteryStatus', 'hailRate', 'heatindex', 
 'heatindex1', 'heatingTemp', 'heatingVoltage', 'humidex', 'humidex1', 
 'inDewpoint', 'inHumidity', 'inTemp', 'inTempBatteryStatus', 'leafTemp1', 
 'leafTemp2', 'leafWet1', 'leafWet2', 'lightning_distance', 
 

Re: [weewx-user] Problem with weewx-airlink

['John Kline' via weewx-user]

Well, first, the subject of this thread is not accurate.  The problem is not 
with weewx-airlink.

I had a look at Davis’ Airlink manual and this case isn’t covered.  I suggest 
you contact Davis Technical Support:
supp...@davisinstruments.com
(510) 732-7814
Monday - Friday, 7:00 a.m. - 5:30 p.m. Pacific Time.

> On May 30, 2022, at 4:09 AM, anc...@gmail.com  wrote:
> 
> Hi,
> that page gives me
> curl http://192.168.0.196/v1/current_conditions
> { "data": { "did": "001D0A100829", "name": "IIS Ceccano", "ts": 506449, 
> "conditions": [{ "lsid": 522424, "data_structure_type": 6, "temp": 86.1, 
> "hum": 43.5, "dew_point": 61.3, "wet_bulb": 66.5, "heat_index": 86.5, 
> "pm_1_last": 2, "pm_2p5_last": 3, "pm_10_last": 3, "pm_1": null, "pm_2p5": 
> null, "pm_2p5_last_1_hour": null, "pm_2p5_last_3_hours": null, 
> "pm_2p5_last_24_hours": null, "pm_2p5_nowcast": null, "pm_10": null, 
> "pm_10_last_1_hour": null, "pm_10_last_3_hours": null, "pm_10_last_24_hours": 
> null, "pm_10_nowcast": null, "last_report_time": 506449, 
> "pct_pm_data_last_1_hour": null, "pct_pm_data_last_3_hours": null, 
> "pct_pm_data_nowcast": null, "pct_pm_data_last_24_hours": null }] }, "error": 
> null }
> 
> So it seems it has not neither good timestamp neither good concentrations. 
> How can I fix this?
> 
> 
> Il giorno mercoledì 25 maggio 2022 alle 19:30:40 UTC+2 jo...@johnkline.com ha 
> scritto:
>> You’re getting this because the timestamp is bad:
>> 'ts': 85460
>> 
>> The specific message: user.airlink: last_report_time must be time since 
>> boot: 85441 seconds.
>> is worded that way because I found airlink was reporting time since reboot 
>> (rather than time since epoch).  I observed this behavior until the airlink 
>> started reporting concentrations.  I specifically check for pm1 to determine 
>> this state.  In the case below, pm_1 is missing ('pm_1': None).
>> 
>> I wouldn’t try to get this running in weewx until you have good data.  In a 
>> browser, go to:
>> http:///v1/current_conditions
>> 
>> You need a good timestamp to show up here (e.g., right now, "ts": 
>> 1653499667) and good concentrations (rather than None); e.g., "pm_1": 5.16
>> 
>> Since it’s finding no valid concentrations, you are seeing the message 
>> “Could not get concentrations from any source.”
>> 
>> John
>> 
 On May 25, 2022, at 8:24 AM, anc...@gmail.com  wrote:
 
>>> Hi guys,
>> 
>>> I just installed for the first time a Davis Airlink and I want to integrate 
>>> it in WeeWX with which my Davis VP2 already works. I followed the 
>>> instructions on the weewx-airlink page, but for some reason it is not 
>>> working . Here is some log:
>>> 
>>> May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
>>> Could not get concentrations from any source.
>>> May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
>>> Found no concentrations to insert.
>>> May 25 16:11:03 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
>>> Found no concentrations to insert.
>>> May 25 16:11:05 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
>>> Found no concentrations to insert.
>>> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
>>> last_report_time must be time since boot: 85441 seconds.  Record: {'data': 
>>> {'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85441, 'conditions': 
>>> [{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.0, 'hum': 26.5, 
>>> 'dew_point': 52.7, 'wet_bulb': 60.0, 'heat_index': 89.8, 'pm_1_last': 4, 
>>> 'pm_2p5_last': 5, 'pm_10_last': 5, 'pm_1': None, 'pm_2p5': None, 
>>> 'pm_2p5_last_1_hour': None, 'pm_2p5_last_3_hours': None, 
>>> 'pm_2p5_last_24_hours': None, 'pm_2p5_nowcast': None, 'pm_10': None, 
>>> 'pm_10_last_1_hour': None, 'pm_10_last_3_hours': None, 
>>> 'pm_10_last_24_hours': None, 'pm_10_nowcast': None, 'last_report_time': 
>>> 85441, 'pct_pm_data_last_1_hour': None, 'pct_pm_data_last_3_hours': None, 
>>> 'pct_pm_data_nowcast': None, 'pct_pm_data_last_24_hours': None}]}, 'error': 
>>> None}
>>> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
>>> Could not get concentrations from any source.
>>> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
>>> Found no concentrations to insert.
>>> May 25 16:11:09 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
>>> Found no concentrations to insert.
>>> May 25 16:11:11 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
>>> Found no concentrations to insert.
>>> May 25 16:11:12 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
>>> last_report_time must be time since boot: 85446 seconds.  Record: {'data': 
>>> {'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85446, 'conditions': 
>>> [{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.1, 'hum': 26.7, 
>>> 'dew_point': 53.0, 'wet_bulb': 60.3, 'heat_index': 89.9, 'pm_1_last': 4, 
>>> 'pm_2p5_last': 4, 'pm_10_last': 4, 'pm_1': None, 'pm_2p5': None, 
>>> 'pm_2p5_last_1_hour': 

Re: [weewx-user] weewx migration

['John Kline' via weewx-user]

I’m sure someone can help if you send a log.
See: https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user

> On May 28, 2022, at 5:51 AM, hajsek...@gmail.com  
> wrote:
> 
> 
> Thank you
> I now manage to start weewx and it looks like it populate weewx database in 
> mysql.
> But it doesn't update my html files
> I use a observer driver to get data from my froggit HP1000 weather station
> I seton weather station to send data to my external  ip 123.123.123.123 on 
> port 9000
> this is server where I have installed weewx.
> but when I setup observer it doesn't work I get errors
> now I setup interceptor but still web page doesn't update.
> what I am missing here?
> 
> ##
> [Observer]
> # This section is for the Observer weather stations.
> 
> # The driver to use
> #driver = user.observer
> 
> # How often to poll the device, in seconds
> poll_interval = 60
> 
> ##
> 
> [Interceptor]
> # This section is for the network traffic interceptor driver.
> 
> # The driver to use:
> # device_type = observer
> driver = user.interceptor
> device_type = ecowitt-client
> 
> # Specify the hardware device to capture.  Options include:
> #   acurite-bridge - acurite internet bridge, smarthub, or access
> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
> #   lw30x - oregon scientific LW301/LW302
> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
> #   ecowitt-client - any hardware that uses the ecowitt protocol
> #   wu-client - any hardware that uses the weather underground protocol
> # device_type = acurite-bridge
> mode = listen
> port = 9900
> [[sensor_map_extensions]]
> inTemp = temperature_1
> inHumidity = humidity_1
> outTemp = temperature_4
> outHumidity = humidity_4
> ##
> 
> 
> sobota, 28. maj 2022 ob 03:00:56 UTC+2 je oseba jo...@johnkline.com napisala:
>> 
>> 
>> 
>> After you follow Gary’s advice to install the current version of 
>> readltime_gauge-data, you’ll hit a problem with your version of 
>> weewx-forecast, as it hasn’t been updated for Python3.  To fix this, you can 
>> install a fork that has been ported:
>> https://github.com/chaunceygardiner/weewx-forecast/releases/download/v3.4.0b11/weewx-forecast-3.4.0b11.zip
>> 
 On May 27, 2022, at 5:37 PM, gjr80  wrote:
 
>>> 
>> 
>>> It look like you are using the realtime_gauge-data v0.3.7 or earlier. The 
>>> current version is v0.5.5 - you will need to upgrade as python3 support was 
>>> not added until v0.4.0. Use the latest version - it is available on GitHub 
>>> here.
>>> 
>>> Gary
>>> 
 On Saturday, 28 May 2022 at 08:11:59 UTC+10 hajsek...@gmail.com wrote:
 I use python3 version
 weewex is installed by this guide and I use centos 8
 http://weewx.com/docs/redhat.htm
 weewx interceptor is this one 
 https://github.com/matthewwall/weewx-interceptor
 weewx forecast is this one
 https://codeload.github.com/matthewwall/weewx-forecast/zip/refs/heads/master/weewx-forecast-master.zip
 I set debug = 2
 this is log
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
   self.loadServices(config_dict)
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
 File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
   obj = weeutil.weeutil.get_object(svc)(self, config_dict)
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
 File "/usr/share/weewx/weeutil/weeutil.py", line 1150, in 
 get_object
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
   mod = __import__(module)
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
 File "/usr/share/weewx/user/rtgd.py", line 1234
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
   except Exception, e:
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
   ^
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
   SyntaxError: invalid syntax
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
   Exiting.
 May 28 00:09:37 web systemd[1]: Started Session 5 of user root.
 May 28 00:09:37 web systemd-logind[1010]: New session 5 of user root.
 May 28 00:09:41 web systemd[1]: Stopping SYSV: start and stop the weewx 
 weather system...
 May 28 00:09:41 web weewx[19416]: Shutting down weewx: [  V redu  ]
 May 28 00:09:41 web 

[weewx-user] weewx migration

['John Kline' via weewx-user]



After you follow Gary’s advice to install the current version of 
readltime_gauge-data, you’ll hit a problem with your version of weewx-forecast, 
as it hasn’t been updated for Python3.  To fix this, you can install a fork 
that has been ported:
https://github.com/chaunceygardiner/weewx-forecast/releases/download/v3.4.0b11/weewx-forecast-3.4.0b11.zip

> On May 27, 2022, at 5:37 PM, gjr80  wrote:
> 
> It look like you are using the realtime_gauge-data v0.3.7 or earlier. The 
> current version is v0.5.5 - you will need to upgrade as python3 support was 
> not added until v0.4.0. Use the latest version - it is available on GitHub 
> here.
> 
> Gary
> 
> On Saturday, 28 May 2022 at 08:11:59 UTC+10 hajsek...@gmail.com wrote:
>> I use python3 version
>> weewex is installed by this guide and I use centos 8
>> http://weewx.com/docs/redhat.htm
>> weewx interceptor is this one 
>> https://github.com/matthewwall/weewx-interceptor
>> weewx forecast is this one
>> https://codeload.github.com/matthewwall/weewx-forecast/zip/refs/heads/master/weewx-forecast-master.zip
>> I set debug = 2
>> this is log
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>  self.loadServices(config_dict)
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>  obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>File "/usr/share/weewx/weeutil/weeutil.py", line 1150, in get_object
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>  mod = __import__(module)
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>File "/usr/share/weewx/user/rtgd.py", line 1234
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>  except Exception, e:
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>  ^
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>  SyntaxError: invalid syntax
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>  Exiting.
>> May 28 00:09:37 web systemd[1]: Started Session 5 of user root.
>> May 28 00:09:37 web systemd-logind[1010]: New session 5 of user root.
>> May 28 00:09:41 web systemd[1]: Stopping SYSV: start and stop the weewx 
>> weather system...
>> May 28 00:09:41 web weewx[19416]: Shutting down weewx: [  V redu  ]
>> May 28 00:09:41 web systemd[1]: weewx.service: Succeeded.
>> May 28 00:09:41 web systemd[1]: Stopped SYSV: start and stop the weewx 
>> weather system.
>> May 28 00:09:41 web systemd[1]: Starting SYSV: start and stop the weewx 
>> weather system...
>> May 28 00:09:42 web journal[19440]: weewx[19440] INFO __main__: Initializing 
>> weewx version 4.8.0
>> May 28 00:09:42 web journal[19440]: weewx[19440] INFO __main__: Using Python 
>> 3.6.8 (default, Apr 29 2022, 13:46:02) #012[GCC 8.5.0 20210514 (Red Hat 
>> 8.5.0-10)]
>> May 28 00:09:42 web journal[19440]: weewx[19440] INFO __main__: Platform 
>> Linux-4.18.0-372.9.1.el8.x86_64-x86_64-with-almalinux-8.6-Sky_Tiger
>> May 28 00:09:42 web journal[19440]: weewx[19440] INFO __main__: Locale is 
>> 'sl_SI.UTF-8'
>> May 28 00:09:42 web journal[19440]: weewx[19440] INFO __main__: Using 
>> configuration file /etc/weewx/weewx.conf
>> May 28 00:09:42 web journal[19440]: weewx[19440] INFO __main__: Debug is 2
>> May 28 00:09:42 web journal[19440]: weewx[19440] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> May 28 00:09:42 web journal[19444]: weewx[19444] INFO weewx.engine: Loading 
>> station type Interceptor (user.interceptor)
>> May 28 00:09:42 web weewx[19431]: Starting weewx: [  V redu  ]
>> May 28 00:09:42 web systemd[1]: Started SYSV: start and stop the weewx 
>> weather system.
>> May 28 00:09:42 web journal[19444]: weewx[19444] INFO user.interceptor: 
>> driver version is 0.53
>> May 28 00:09:42 web journal[19444]: weewx[19444] INFO user.interceptor: 
>> device type: observer
>> May 28 00:09:42 web journal[19444]: weewx[19444] INFO user.interceptor: mode 
>> is listen
>> May 28 00:09:42 web journal[19444]: weewx[19444] INFO user.interceptor: 
>> listen on :9900
>> May 28 00:09:42 web journal[19444]: weewx[19444] INFO user.interceptor: 
>> sensor map: {'pressure': 'pressure', 'barometer': 'barometer', 
>> 'outHumidity': 'humidity_out', 'inHumidity': 'humidity_in', 'outTemp': 
>> 'temperature_out', 'inTemp': 'temperature_in', 'windSpeed': 'wind_speed', 
>> 'windGust': 'wind_gust', 'windDir': 'wind_dir', 'windGustDir': 
>> 'wind_gust_dir', 'radiation': 'solar_radiation', 'dewpoint': 'dewpoint', 
>> 'windchill': 'windchill', 'rain': 'rain', 'rainRate': 'rain_rate', 'UV': 
>> 'uv', 'txBatteryStatus': 'battery', 'extraTemp1': 

Re: [weewx-user] weewx migration

['John Kline' via weewx-user]

Your log snippet shows an error in  weewx-realtime_gauge-data, probably because 
it’s an old version that doesn’t work with Python3.  What version of  
weewx-realtime_gauge-data have you installed?

Also, since you are want to get the forecast extension working, what version 
are you using of that?

And what python version are you running?

Lastly, it would be good if you included the log as it would answer these 
questions.  See: https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user

> On May 27, 2022, at 7:46 AM, hajsek...@gmail.com  
> wrote:
> 
> 
> I have migrated weewx to another server, but have a problem.
> First I copied old files to new server and try to start it and didn't worked.
> Than i Have new installation of weex and after that I have installed driver 
> observer when I start weewx it was ok. But after that I have installed 
> forecast.zip and try to start weewx and all stopped.
> I use before version 4.8 and don't know if I migrate do I need to install 
> wewx first and than install observer driver and forecast.
> after that copy old weewx.conf into /etc/weewx
> and restore mysql database and it should work, but doesn't.
> when I start weewx I get this error.
> May 27 16:23:58 web journal[6058]: weewx[6058] INFO weewx.restx: 
> StationRegistry: Registration not requested.
> May 27 16:23:58 web journal[6058]: weewx[6058] INFO weewx.restx: PWSweather: 
> Posting not enabled.
> May 27 16:23:58 web journal[6058]: weewx[6058] INFO weewx.restx: CWOP: 
> Posting not enabled.
> May 27 16:23:58 web journal[6058]: weewx[6058] INFO weewx.restx: WOW: Posting 
> not enabled.
> May 27 16:23:58 web journal[6058]: weewx[6058] INFO weewx.restx: AWEKAS: 
> Posting not enabled.
> May 27 16:23:58 web journal[6058]: weewx[6058] INFO weewx.engine: 'pyephem' 
> detected, extended almanac data is available
> May 27 16:23:58 web journal[6058]: weewx[6058] INFO user.interceptor: 
> shutting down server thread
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: Caught 
> unrecoverable exception:
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__:   
> invalid syntax (rtgd.py, line 1234)
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__:   
> Traceback (most recent call last):
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
> File "/usr/share/weewx/weewxd", line 147, in main
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
>   engine = weewx.engine.StdEngine(config_dict)
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/engine.py", line 93, in __init__
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
>   self.loadServices(config_dict)
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
>   obj = weeutil.weeutil.get_object(svc)(self, config_dict)
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
> File "/usr/share/weewx/weeutil/weeutil.py", line 1150, in get_object
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
>   mod = __import__(module)
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
> File "/usr/share/weewx/user/rtgd.py", line 1234
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
>   except Exception, e:
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
>   ^
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__:   
> SyntaxError: invalid syntax
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__:   
> Exiting.
> -- 
> 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/57148ec2-5516-40e6-b02f-896df88d13e9n%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/2C1F3C01-96DF-4ECC-9042-CE56FBF4BFEB%40johnkline.com.

Re: [weewx-user] Problem with weewx-airlink

['John Kline' via weewx-user]

You’re getting this because the timestamp is bad:
'ts': 85460

The specific message: user.airlink: last_report_time must be time since boot: 
85441 seconds.
is worded that way because I found airlink was reporting time since reboot 
(rather than time since epoch).  I observed this behavior until the airlink 
started reporting concentrations.  I specifically check for pm1 to determine 
this state.  In the case below, pm_1 is missing ('pm_1': None).

I wouldn’t try to get this running in weewx until you have good data.  In a 
browser, go to:
http:///v1/current_conditions

You need a good timestamp to show up here (e.g., right now, "ts": 1653499667) 
and good concentrations (rather than None); e.g., "pm_1": 5.16

Since it’s finding no valid concentrations, you are seeing the message “Could 
not get concentrations from any source.”

John

> On May 25, 2022, at 8:24 AM, anc...@gmail.com  wrote:
> 
> Hi guys,
> I just installed for the first time a Davis Airlink and I want to integrate 
> it in WeeWX with which my Davis VP2 already works. I followed the 
> instructions on the weewx-airlink page, but for some reason it is not working 
> . Here is some log:
> 
> May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Could not get concentrations from any source.
> May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:03 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:05 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
> last_report_time must be time since boot: 85441 seconds.  Record: {'data': 
> {'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85441, 'conditions': 
> [{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.0, 'hum': 26.5, 
> 'dew_point': 52.7, 'wet_bulb': 60.0, 'heat_index': 89.8, 'pm_1_last': 4, 
> 'pm_2p5_last': 5, 'pm_10_last': 5, 'pm_1': None, 'pm_2p5': None, 
> 'pm_2p5_last_1_hour': None, 'pm_2p5_last_3_hours': None, 
> 'pm_2p5_last_24_hours': None, 'pm_2p5_nowcast': None, 'pm_10': None, 
> 'pm_10_last_1_hour': None, 'pm_10_last_3_hours': None, 'pm_10_last_24_hours': 
> None, 'pm_10_nowcast': None, 'last_report_time': 85441, 
> 'pct_pm_data_last_1_hour': None, 'pct_pm_data_last_3_hours': None, 
> 'pct_pm_data_nowcast': None, 'pct_pm_data_last_24_hours': None}]}, 'error': 
> None}
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Could not get concentrations from any source.
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:09 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:11 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:12 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
> last_report_time must be time since boot: 85446 seconds.  Record: {'data': 
> {'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85446, 'conditions': 
> [{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.1, 'hum': 26.7, 
> 'dew_point': 53.0, 'wet_bulb': 60.3, 'heat_index': 89.9, 'pm_1_last': 4, 
> 'pm_2p5_last': 4, 'pm_10_last': 4, 'pm_1': None, 'pm_2p5': None, 
> 'pm_2p5_last_1_hour': None, 'pm_2p5_last_3_hours': None, 
> 'pm_2p5_last_24_hours': None, 'pm_2p5_nowcast': None, 'pm_10': None, 
> 'pm_10_last_1_hour': None, 'pm_10_last_3_hours': None, 'pm_10_last_24_hours': 
> None, 'pm_10_nowcast': None, 'last_report_time': 85446, 
> 'pct_pm_data_last_1_hour': None, 'pct_pm_data_last_3_hours': None, 
> 'pct_pm_data_nowcast': None, 'pct_pm_data_last_24_hours': None}]}, 'error': 
> None}
> May 25 16:11:12 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Could not get concentrations from any source.
> May 25 16:11:13 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:15 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] INFO weewx.manager: 
> Added record 2022-05-25 16:11:00 CEST (1653487860) to database 'weewx.sdb'
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] INFO weewx.manager: 
> Added record 2022-05-25 16:11:00 CEST (1653487860) to daily summary in 
> 'weewx.sdb'
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:17 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:19 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
> collect_data: Attempt to fetch from: 192.168.0.196 failed: 
> HTTPConnectionPool(host='192.168.0.196', port=80): Max retries exceeded with 
> url: /v1/current_conditions 

Re: [weewx-user] Re: Realtime-_gauge-data.txt

['John Kline' via weewx-user]

That rsync command you listed, it is in root’s crontab?
And why aren’t you doing the rsync in weewx?

> On May 23, 2022, at 1:15 PM, philip@gmail.com  
> wrote:
> 
> Im using rsync to copy the public_html folder to my server using a cron job 
> every 10mins = rsync -a /home/weewx/public_html/ lushe...@192.xxx.x.xxx 
> etc etc
> Then thought I would use rsync in rtgd, from weewx.conf to update the gauges 
> in real time.
> OS is Buster 10 using a Raspberry Pi
> 
> 
>> On Monday, May 23, 2022 at 8:28:18 PM UTC+1 jo...@johnkline.com wrote:
>> I’m curious, are you using rsync to publish weewx?  I’m asking because rtgd 
>> is calling the same weewx method.
>> 
>> If you are using rsync to publish weewx, please send that section of your 
>> weewx.conf.  There must be some difference.
>> 
>> Also, what OS are you using?  I’m worried that it is Windows from your 
>> paths.  If it is, I’m unlikely to be able to debug this.
>> 
>>>> On May 23, 2022, at 10:56 AM, philip@gmail.com  
>>>> wrote:
>>>> 
>>> Im using LushEr21 for both and ssh LushEr21@server-ip-address logs on to 
>>> the server without a password
>> 
>>> 
>>> 
>>>> On Monday, May 23, 2022 at 4:39:47 PM UTC+1 jo...@johnkline.com wrote:
>>>> 
>>>> 
>>>> I’m assuming that  in ssh-copy-id -i ~/.ssh/id_rsa.pub 
>>>> @ - is:
>>>> LushEr21
>>>> Since that what you specified in weewx.conf.
>>>> 
>>>> Please confirm that the following works (i.e., you are logged in to 
>>>>  as LushEr21 without having to enter a password or an 
>>>> [empty] passphrase:
>>>> (As root:)
>>>> ssh LushEr21@
>>>> 
>>>>>> On May 23, 2022, at 7:00 AM, philip@gmail.com  
>>>>>> wrote:
>>>>>> 
>>>>> For ssh 
>>>> 
>>>>> I used when I was root
>>>>> ssh-keygen -f C:\Users\\.ssh\id_rsa -t rsa -P ""
>>>>> ssh-copy-id -i ~/.ssh/id_rsa.pub @ -o 
>>>>> StrictHostKeyChecking=No
>>>>> Should I have a file /usr/bin/ssh-askpass
>>>>> Sorry to be a pain
>>>>> Phil
>>>>> 
>>>>> 
>>>>>> On Monday, May 23, 2022 at 1:39:10 PM UTC+1 jo...@johnkline.com wrote:
>>>>>> I don’t recommend extending the timeout.  It’s there so that requests 
>>>>>> don’t build up.
>>>>>> Are you sure you have ssh set up correctly?  In particular, did you set 
>>>>>> it up for the same user as weewx is running as?  That’s often root.  If 
>>>>>> weewx is running as root for you, please try to ssh in without a 
>>>>>> password when you are logged in as root.
>>>>>> 
>>>>>>>> On May 23, 2022, at 3:13 AM, philip@gmail.com 
>>>>>>>>  wrote:
>>>>>>>> 
>>>>>>> Thanks John
>>>>>>>  I now get 
>>>>>>> May 23 10:59:03 raspberrypi weewx-weewx[1438] ERROR 
>>>>>>> weeutil.rsyncupload: [['rsync', '--archive', '--stats', '--timeout=4', 
>>>>>>> '-e ssh -o ConnectTimeout=1', '/home/weewx/public_html/gauge-data.txt', 
>>>>>>> 'lush...@192.xxx.x.xxx:/volume1/web/SheringhamDDNS/gaugedata/gauge-data.txt']]
>>>>>>>  reported errors: ssh_askpass: exec(/usr/bin/ssh-askpass): No such file 
>>>>>>> or directory. [sender] io timeout after 4 seconds -- exiting. rsync 
>>>>>>> error: timeout in data send/receive (code 30) at io.c(204) 
>>>>>>> [sender=3.1.3]
>>>>>>> May 23 10:59:03 raspberrypi weewx-weewx[1438] INFO weeutil.rsyncupload: 
>>>>>>> rsync executed in 6.03 seconds
>>>>>>> I had to extend the Timeout = 4 as it would time out.
>>>>>>> I dont appear to have a file usr/bin/ssh_askpass When the passwordless 
>>>>>>> key was set up I believe it saved the info to ssh-keygen
>>>>>>> 
>>>>>>> rsync -v /home/weewx/public_html/gauge-data.txt 
>>>>>>> lush...@192.xxx.x.xxx:/volume1/web/SheringhamDDNS works OK in a cron job
>>>>>>> Phil
>>>>>>>> On Sunday, May 22, 2022 at 6:24:58 PM UTC+1 jo...@johnkline.com wrote:
>>>>>>>> OK, you could also replace rtgd.py (in weewx’s bin/user directory) 
>>>>>>&g

Re: [weewx-user] Re: Realtime-_gauge-data.txt

['John Kline' via weewx-user]

I’m curious, are you using rsync to publish weewx?  I’m asking because rtgd is 
calling the same weewx method.

If you are using rsync to publish weewx, please send that section of your 
weewx.conf.  There must be some difference.

Also, what OS are you using?  I’m worried that it is Windows from your paths.  
If it is, I’m unlikely to be able to debug this.

> On May 23, 2022, at 10:56 AM, philip@gmail.com  
> wrote:
> 
> Im using LushEr21 for both and ssh LushEr21@server-ip-address logs on to the 
> server without a password
> 
>> On Monday, May 23, 2022 at 4:39:47 PM UTC+1 jo...@johnkline.com wrote:
>> 
>> 
>> I’m assuming that  in ssh-copy-id -i ~/.ssh/id_rsa.pub 
>> @ - is:
>> LushEr21
>> Since that what you specified in weewx.conf.
>> 
>> Please confirm that the following works (i.e., you are logged in to 
>>  as LushEr21 without having to enter a password or an 
>> [empty] passphrase:
>> (As root:)
>> ssh LushEr21@
>> 
>>>> On May 23, 2022, at 7:00 AM, philip@gmail.com  
>>>> wrote:
>>>> 
>>> For ssh 
>> 
>>> I used when I was root
>>> ssh-keygen -f C:\Users\\.ssh\id_rsa -t rsa -P ""
>>> ssh-copy-id -i ~/.ssh/id_rsa.pub @ -o 
>>> StrictHostKeyChecking=No
>>> Should I have a file /usr/bin/ssh-askpass
>>> Sorry to be a pain
>>> Phil
>>> 
>>> 
>>>> On Monday, May 23, 2022 at 1:39:10 PM UTC+1 jo...@johnkline.com wrote:
>>>> I don’t recommend extending the timeout.  It’s there so that requests 
>>>> don’t build up.
>>>> Are you sure you have ssh set up correctly?  In particular, did you set it 
>>>> up for the same user as weewx is running as?  That’s often root.  If weewx 
>>>> is running as root for you, please try to ssh in without a password when 
>>>> you are logged in as root.
>>>> 
>>>>>> On May 23, 2022, at 3:13 AM, philip@gmail.com  
>>>>>> wrote:
>>>>>> 
>>>>> Thanks John
>>>>>  I now get 
>>>>> May 23 10:59:03 raspberrypi weewx-weewx[1438] ERROR weeutil.rsyncupload: 
>>>>> [['rsync', '--archive', '--stats', '--timeout=4', '-e ssh -o 
>>>>> ConnectTimeout=1', '/home/weewx/public_html/gauge-data.txt', 
>>>>> 'lush...@192.xxx.x.xxx:/volume1/web/SheringhamDDNS/gaugedata/gauge-data.txt']]
>>>>>  reported errors: ssh_askpass: exec(/usr/bin/ssh-askpass): No such file 
>>>>> or directory. [sender] io timeout after 4 seconds -- exiting. rsync 
>>>>> error: timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
>>>>> May 23 10:59:03 raspberrypi weewx-weewx[1438] INFO weeutil.rsyncupload: 
>>>>> rsync executed in 6.03 seconds
>>>>> I had to extend the Timeout = 4 as it would time out.
>>>>> I dont appear to have a file usr/bin/ssh_askpass When the passwordless 
>>>>> key was set up I believe it saved the info to ssh-keygen
>>>>> 
>>>>> rsync -v /home/weewx/public_html/gauge-data.txt 
>>>>> lush...@192.xxx.x.xxx:/volume1/web/SheringhamDDNS works OK in a cron job
>>>>> Phil
>>>>>> On Sunday, May 22, 2022 at 6:24:58 PM UTC+1 jo...@johnkline.com wrote:
>>>>>> OK, you could also replace rtgd.py (in weewx’s bin/user directory) with 
>>>>>> the file at:
>>>>>> https://github.com/chaunceygardiner/weewx-realtime_gauge-data/blob/master/bin/user/rtgd.py
>>>>>> 
>>>>>> I’ve also sent Gary a PR at:
>>>>>> https://github.com/gjr80/weewx-realtime_gauge-data/pull/28
>>>>>> 
>>>>>> 
>>>>>>>> On May 22, 2022, at 10:07 AM, John Kline  wrote:
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>>> Never mind.  I installed it and found the issue.  It’s been broken 
>>>>>>> since it was refactored.
>>>>>>> 
>>>>>>> Below is the patch to get it working.  I’ll also follow up with a URL 
>>>>>>> to grab the file from github; as well as a PR to Gary (who may take it 
>>>>>>> if he notices it).
>>>>>>> 
>>>>>>> diff --git a/bin/user/rtgd.py b/bin/user/rtgd.py
>>>>>>> index 9f631c9..09ddd24 100644
>>>>>>> --- a/bin/user/rtgd.py
>>>>>>> +++ b/bin/user/rtgd.py
>>>>>>> @@ -1300,7 

Re: [weewx-user] Re: Realtime-_gauge-data.txt

['John Kline' via weewx-user]


I’m assuming that  in ssh-copy-id -i ~/.ssh/id_rsa.pub 
@ - is:
LushEr21
Since that what you specified in weewx.conf.

Please confirm that the following works (i.e., you are logged in to 
 as LushEr21 without having to enter a password or an 
[empty] passphrase:
(As root:)
ssh LushEr21@

> On May 23, 2022, at 7:00 AM, philip@gmail.com  
> wrote:
> For ssh 
> I used when I was root
> ssh-keygen -f C:\Users\\.ssh\id_rsa -t rsa -P ""
> ssh-copy-id -i ~/.ssh/id_rsa.pub @ -o 
> StrictHostKeyChecking=No
> Should I have a file /usr/bin/ssh-askpass
> Sorry to be a pain
> Phil
> 
> 
> On Monday, May 23, 2022 at 1:39:10 PM UTC+1 jo...@johnkline.com wrote:
>> I don’t recommend extending the timeout.  It’s there so that requests don’t 
>> build up.
>> Are you sure you have ssh set up correctly?  In particular, did you set it 
>> up for the same user as weewx is running as?  That’s often root.  If weewx 
>> is running as root for you, please try to ssh in without a password when you 
>> are logged in as root.
>> 
>>> On May 23, 2022, at 3:13 AM, philip@gmail.com  
>>> wrote:
>> 
>>> Thanks John
>>>  I now get 
>>> May 23 10:59:03 raspberrypi weewx-weewx[1438] ERROR weeutil.rsyncupload: 
>>> [['rsync', '--archive', '--stats', '--timeout=4', '-e ssh -o 
>>> ConnectTimeout=1', '/home/weewx/public_html/gauge-data.txt', 
>>> 'lush...@192.xxx.x.xxx:/volume1/web/SheringhamDDNS/gaugedata/gauge-data.txt']]
>>>  reported errors: ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or 
>>> directory. [sender] io timeout after 4 seconds -- exiting. rsync error: 
>>> timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
>>> May 23 10:59:03 raspberrypi weewx-weewx[1438] INFO weeutil.rsyncupload: 
>>> rsync executed in 6.03 seconds
>>> I had to extend the Timeout = 4 as it would time out.
>>> I dont appear to have a file usr/bin/ssh_askpass When the passwordless key 
>>> was set up I believe it saved the info to ssh-keygen
>>> 
>>> rsync -v /home/weewx/public_html/gauge-data.txt 
>>> lush...@192.xxx.x.xxx:/volume1/web/SheringhamDDNS works OK in a cron job
>>> Phil
>>> On Sunday, May 22, 2022 at 6:24:58 PM UTC+1 jo...@johnkline.com wrote:
>>>> OK, you could also replace rtgd.py (in weewx’s bin/user directory) with 
>>>> the file at:
>>>> https://github.com/chaunceygardiner/weewx-realtime_gauge-data/blob/master/bin/user/rtgd.py
>>>> 
>>>> I’ve also sent Gary a PR at:
>>>> https://github.com/gjr80/weewx-realtime_gauge-data/pull/28
>>>> 
>>>> 
>>>>> On May 22, 2022, at 10:07 AM, John Kline  wrote:
>>>>> 
>>>> 
>>>>> Never mind.  I installed it and found the issue.  It’s been broken since 
>>>>> it was refactored.
>>>>> 
>>>>> Below is the patch to get it working.  I’ll also follow up with a URL to 
>>>>> grab the file from github; as well as a PR to Gary (who may take it if he 
>>>>> notices it).
>>>>> 
>>>>> diff --git a/bin/user/rtgd.py b/bin/user/rtgd.py
>>>>> index 9f631c9..09ddd24 100644
>>>>> --- a/bin/user/rtgd.py
>>>>> +++ b/bin/user/rtgd.py
>>>>> @@ -1300,7 +1300,7 @@ class HttpPostExport(object):
>>>>>  # response text from remote URL if post was successful
>>>>>  self.response = post_config_dict.get('response_text', None)
>>>>>  
>>>>> -def export(self, data):
>>>>> +def export(self, data, dateTime):
>>>>>  """Post the data."""
>>>>>  
>>>>>  self.post_data(data)
>>>>> @@ -1419,10 +1419,11 @@ class RsyncExport(object):
>>>>>  self.rsync_skip_if_older_than = 
>>>>> to_int(rsync_config_dict.get('rsync_skip_if_older_than',
>>>>>   4))
>>>>>  
>>>>> -def export(self, data):
>>>>> +def export(self, data, dateTime):
>>>>>  """Rsync the data."""
>>>>>  
>>>>> -packet_time = datetime.datetime.fromtimestamp(data['dateTime'])
>>>>> +log.info("export: data: %r" % data)
>>>>> +packet_time = datetime.datetime.fromtimestamp(dateTime)
>>>>>  self.rsync_data(packet_time)

Re: [weewx-user] Re: Realtime-_gauge-data.txt

['John Kline' via weewx-user]

I don’t recommend extending the timeout.  It’s there so that requests don’t 
build up.
Are you sure you have ssh set up correctly?  In particular, did you set it up 
for the same user as weewx is running as?  That’s often root.  If weewx is 
running as root for you, please try to ssh in without a password when you are 
logged in as root.

> On May 23, 2022, at 3:13 AM, philip@gmail.com  
> wrote:
> 
> Thanks John
>  I now get 
> May 23 10:59:03 raspberrypi weewx-weewx[1438] ERROR weeutil.rsyncupload: 
> [['rsync', '--archive', '--stats', '--timeout=4', '-e ssh -o 
> ConnectTimeout=1', '/home/weewx/public_html/gauge-data.txt', 
> 'lushe...@192.xxx.x.xxx:/volume1/web/SheringhamDDNS/gaugedata/gauge-data.txt']]
>  reported errors: ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or 
> directory. [sender] io timeout after 4 seconds -- exiting. rsync error: 
> timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
> May 23 10:59:03 raspberrypi weewx-weewx[1438] INFO weeutil.rsyncupload: rsync 
> executed in 6.03 seconds
> I had to extend the Timeout = 4 as it would time out.
> I dont appear to have a file usr/bin/ssh_askpass When the passwordless key 
> was set up I believe it saved the info to ssh-keygen
> 
> rsync -v /home/weewx/public_html/gauge-data.txt 
> lushe...@192.xxx.x.xxx:/volume1/web/SheringhamDDNS works OK in a cron job
> Phil
>> On Sunday, May 22, 2022 at 6:24:58 PM UTC+1 jo...@johnkline.com wrote:
>> OK, you could also replace rtgd.py (in weewx’s bin/user directory) with the 
>> file at:
>> https://github.com/chaunceygardiner/weewx-realtime_gauge-data/blob/master/bin/user/rtgd.py
>> 
>> I’ve also sent Gary a PR at:
>> https://github.com/gjr80/weewx-realtime_gauge-data/pull/28
>> 
>> 
>>>> On May 22, 2022, at 10:07 AM, John Kline  wrote:
>>>> 
>>> 
>> 
>>> Never mind.  I installed it and found the issue.  It’s been broken since it 
>>> was refactored.
>>> 
>>> Below is the patch to get it working.  I’ll also follow up with a URL to 
>>> grab the file from github; as well as a PR to Gary (who may take it if he 
>>> notices it).
>>> 
>>> diff --git a/bin/user/rtgd.py b/bin/user/rtgd.py
>>> index 9f631c9..09ddd24 100644
>>> --- a/bin/user/rtgd.py
>>> +++ b/bin/user/rtgd.py
>>> @@ -1300,7 +1300,7 @@ class HttpPostExport(object):
>>>  # response text from remote URL if post was successful
>>>  self.response = post_config_dict.get('response_text', None)
>>>  
>>> -def export(self, data):
>>> +def export(self, data, dateTime):
>>>  """Post the data."""
>>>  
>>>  self.post_data(data)
>>> @@ -1419,10 +1419,11 @@ class RsyncExport(object):
>>>  self.rsync_skip_if_older_than = 
>>> to_int(rsync_config_dict.get('rsync_skip_if_older_than',
>>>   4))
>>>  
>>> -def export(self, data):
>>> +def export(self, data, dateTime):
>>>  """Rsync the data."""
>>>  
>>> -packet_time = datetime.datetime.fromtimestamp(data['dateTime'])
>>> +log.info("export: data: %r" % data)
>>> +packet_time = datetime.datetime.fromtimestamp(dateTime)
>>>  self.rsync_data(packet_time)
>>>  
>>>  def rsync_data(self, packet_time):
>>> @@ -1900,7 +1901,7 @@ class RealtimeGaugeDataThread(threading.Thread):
>>>  self.last_write = time.time()
>>>  # export gauge-data.txt if we have an exporter object
>>>  if self.exporter:
>>> -self.exporter.export(data)
>>> +self.exporter.export(data, packet['dateTime'])
>>>  # log the generation
>>>  if weewx.debug == 2:
>>>  log.info("gauge-data.txt (%s) generated in %.5f 
>>> seconds" % (cached_packet['dateTime'],
>>> 
>>>>> On May 22, 2022, at 6:08 AM, John Kline  wrote:
>>>>> 
>>>> 
>>>> Oh, yes, two brackets.  What failures did you get with two brackets?
>>>> 
>>>>>> On May 22, 2022, at 2:59 AM, philip@gmail.com  
>>>>>> wrote:
>>>>>> 
>>>>> Thanks John
>>>>> Can I just confirm how many bracket Rsync would have please 
>>>>> Have tried 

Re: [weewx-user] Re: Realtime-_gauge-data.txt

['John Kline' via weewx-user]

OK, you could also replace rtgd.py (in weewx’s bin/user directory) with the 
file at:
https://github.com/chaunceygardiner/weewx-realtime_gauge-data/blob/master/bin/user/rtgd.py

I’ve also sent Gary a PR at:
https://github.com/gjr80/weewx-realtime_gauge-data/pull/28


> On May 22, 2022, at 10:07 AM, John Kline  wrote:
> 
> 
> Never mind.  I installed it and found the issue.  It’s been broken since it 
> was refactored.
> 
> Below is the patch to get it working.  I’ll also follow up with a URL to grab 
> the file from github; as well as a PR to Gary (who may take it if he notices 
> it).
> 
> diff --git a/bin/user/rtgd.py b/bin/user/rtgd.py
> index 9f631c9..09ddd24 100644
> --- a/bin/user/rtgd.py
> +++ b/bin/user/rtgd.py
> @@ -1300,7 +1300,7 @@ class HttpPostExport(object):
>  # response text from remote URL if post was successful
>  self.response = post_config_dict.get('response_text', None)
>  
> -def export(self, data):
> +def export(self, data, dateTime):
>  """Post the data."""
>  
>  self.post_data(data)
> @@ -1419,10 +1419,11 @@ class RsyncExport(object):
>  self.rsync_skip_if_older_than = 
> to_int(rsync_config_dict.get('rsync_skip_if_older_than',
>   4))
>  
> -def export(self, data):
> +def export(self, data, dateTime):
>  """Rsync the data."""
>  
> -packet_time = datetime.datetime.fromtimestamp(data['dateTime'])
> +log.info("export: data: %r" % data)
> +packet_time = datetime.datetime.fromtimestamp(dateTime)
>  self.rsync_data(packet_time)
>  
>  def rsync_data(self, packet_time):
> @@ -1900,7 +1901,7 @@ class RealtimeGaugeDataThread(threading.Thread):
>  self.last_write = time.time()
>  # export gauge-data.txt if we have an exporter object
>  if self.exporter:
> -self.exporter.export(data)
> +self.exporter.export(data, packet['dateTime'])
>  # log the generation
>  if weewx.debug == 2:
>  log.info("gauge-data.txt (%s) generated in %.5f 
> seconds" % (cached_packet['dateTime'],
> 
>>> On May 22, 2022, at 6:08 AM, John Kline  wrote:
>>> 
>> 
>> Oh, yes, two brackets.  What failures did you get with two brackets?
>> 
>>>> On May 22, 2022, at 2:59 AM, philip@gmail.com 
>>>>  wrote:
>>>> 
>>> Thanks John
>>> Can I just confirm how many bracket Rsync would have please 
>>> Have tried 1 bracket and got lots of log failures and then tried it with 2 
>>> brackets as [[StringFormats]] below has 2 brackets , and got a different 
>>> failures.
>>> Both were critical errors and stopped RTGD from working.
>>> In both cases the line raspberrypi weewx-weewx[352] INFO user.rtgd: 
>>> gauge-data.txt will not be exported. had gone.
>>> Phil
>>> 
>>>> On Saturday, May 21, 2022 at 7:01:24 PM UTC+1 jo...@johnkline.com wrote:
>>>> BTW, this is the commit that moved the rsync parms (and, it looks like 
>>>> HTTP post parms) into a separate section:
>>>> https://github.com/gjr80/weewx-realtime_gauge-data/commit/534032cef8f1bfba45b90cf7ef939c16084a5b2e0
>>>> 
>>>> The README should probably change to match.
>>>> 
>>>> 
>>>>>> On May 21, 2022, at 6:48 AM, John Kline  wrote:
>>>>>> 
>>>>> 
>>>> 
>>>>> I believe the rsync_xxx entries need to be under an Rsync section:
>>>>> [RealtimeGaugeData]
>>>>> .
>>>>> .
>>>>> .
>>>>>   [Rsync]
>>>>> rsync_server=xxx
>>>>> Rsync_user=LushEr21
>>>>> etc.
>>>>> 
>>>>> If that doesn’t work, I will install the extension and get it working.
>>>>> 
>>>>>>> On May 21, 2022, at 3:18 AM, philip@gmail.com 
>>>>>>>  wrote:
>>>>>>> 
>>>>>> [RealtimeGaugeData]
>>>>>> date_format = %Y.%m.%d %H:%M
>>>>>> rtgd_path = /home/weewx/public_html
>>>>>> min_interval = 15
>>>>>> response_text = success
>>>>>> rsync_server = xxx.xxx.x.xxx
>>>>>> rsync_user = LushEr21
>>>>>> rsync_remote_rtgd_dir = /volu

Re: [weewx-user] Re: Realtime-_gauge-data.txt

['John Kline' via weewx-user]

Never mind.  I installed it and found the issue.  It’s been broken since it was 
refactored.

Below is the patch to get it working.  I’ll also follow up with a URL to grab 
the file from github; as well as a PR to Gary (who may take it if he notices 
it).

diff --git a/bin/user/rtgd.py b/bin/user/rtgd.py
index 9f631c9..09ddd24 100644
--- a/bin/user/rtgd.py
+++ b/bin/user/rtgd.py
@@ -1300,7 +1300,7 @@ class HttpPostExport(object):
 # response text from remote URL if post was successful
 self.response = post_config_dict.get('response_text', None)
 
-def export(self, data):
+def export(self, data, dateTime):
 """Post the data."""
 
 self.post_data(data)
@@ -1419,10 +1419,11 @@ class RsyncExport(object):
 self.rsync_skip_if_older_than = 
to_int(rsync_config_dict.get('rsync_skip_if_older_than',
  4))
 
-def export(self, data):
+def export(self, data, dateTime):
 """Rsync the data."""
 
-packet_time = datetime.datetime.fromtimestamp(data['dateTime'])
+log.info("export: data: %r" % data)
+packet_time = datetime.datetime.fromtimestamp(dateTime)
 self.rsync_data(packet_time)
 
 def rsync_data(self, packet_time):
@@ -1900,7 +1901,7 @@ class RealtimeGaugeDataThread(threading.Thread):
 self.last_write = time.time()
 # export gauge-data.txt if we have an exporter object
 if self.exporter:
-self.exporter.export(data)
+self.exporter.export(data, packet['dateTime'])
 # log the generation
 if weewx.debug == 2:
 log.info("gauge-data.txt (%s) generated in %.5f 
seconds" % (cached_packet['dateTime'],

> On May 22, 2022, at 6:08 AM, John Kline  wrote:
> 
> 
> Oh, yes, two brackets.  What failures did you get with two brackets?
> 
>>> On May 22, 2022, at 2:59 AM, philip@gmail.com 
>>>  wrote:
>>> 
>> Thanks John
>> Can I just confirm how many bracket Rsync would have please 
>> Have tried 1 bracket and got lots of log failures and then tried it with 2 
>> brackets as [[StringFormats]] below has 2 brackets , and got a different 
>> failures.
>> Both were critical errors and stopped RTGD from working.
>> In both cases the line raspberrypi weewx-weewx[352] INFO user.rtgd: 
>> gauge-data.txt will not be exported. had gone.
>> Phil
>> 
>>> On Saturday, May 21, 2022 at 7:01:24 PM UTC+1 jo...@johnkline.com wrote:
>>> BTW, this is the commit that moved the rsync parms (and, it looks like HTTP 
>>> post parms) into a separate section:
>>> https://github.com/gjr80/weewx-realtime_gauge-data/commit/534032cef8f1bfba45b90cf7ef939c16084a5b2e0
>>> 
>>> The README should probably change to match.
>>> 
>>> 
>>>>> On May 21, 2022, at 6:48 AM, John Kline  wrote:
>>>>> 
>>>> 
>>> 
>>>> I believe the rsync_xxx entries need to be under an Rsync section:
>>>> [RealtimeGaugeData]
>>>> .
>>>> .
>>>> .
>>>>   [Rsync]
>>>> rsync_server=xxx
>>>> Rsync_user=LushEr21
>>>> etc.
>>>> 
>>>> If that doesn’t work, I will install the extension and get it working.
>>>> 
>>>>>> On May 21, 2022, at 3:18 AM, philip@gmail.com  
>>>>>> wrote:
>>>>>> 
>>>>> [RealtimeGaugeData]
>>>>> date_format = %Y.%m.%d %H:%M
>>>>> rtgd_path = /home/weewx/public_html
>>>>> min_interval = 15
>>>>> response_text = success
>>>>> rsync_server = xxx.xxx.x.xxx
>>>>> rsync_user = LushEr21
>>>>> rsync_remote_rtgd_dir = /volume1/web/SheringhamDDNS
>>>>> rsync_compress = False
>>>>> rsync_log_success = True
>>>>> rsync_ssh_options = "-o ConnectTimeout=1"
>>>>> rsync_timeout = 1
>>>>> rsync_skip_if_older_than = 4
>>>>> 
>>>>> The key/passwordless to the server works with
>>>>> rsync -v /home/weewx/public_html/gauge-data.txt 
>>>>> lush...@xxx.xxx.x.xxx:/volume1/web/SheringhamDDNS so the key/passwordless 
>>>>> so am assuming the above works
>>>>> Thanks for your help
>>>>> Phil
>>>>> 
>>>>> 
>>>>>> On Thursday, May 19, 2022 at 4:27:5

Re: [weewx-user] Re: Realtime-_gauge-data.txt

['John Kline' via weewx-user]

Oh, yes, two brackets.  What failures did you get with two brackets?

> On May 22, 2022, at 2:59 AM, philip@gmail.com  
> wrote:
> 
> Thanks John
> Can I just confirm how many bracket Rsync would have please 
> Have tried 1 bracket and got lots of log failures and then tried it with 2 
> brackets as [[StringFormats]] below has 2 brackets , and got a different 
> failures.
> Both were critical errors and stopped RTGD from working.
> In both cases the line raspberrypi weewx-weewx[352] INFO user.rtgd: 
> gauge-data.txt will not be exported. had gone.
> Phil
> 
>> On Saturday, May 21, 2022 at 7:01:24 PM UTC+1 jo...@johnkline.com wrote:
>> BTW, this is the commit that moved the rsync parms (and, it looks like HTTP 
>> post parms) into a separate section:
>> https://github.com/gjr80/weewx-realtime_gauge-data/commit/534032cef8f1bfba45b90cf7ef939c16084a5b2e0
>> 
>> The README should probably change to match.
>> 
>> 
>>>> On May 21, 2022, at 6:48 AM, John Kline  wrote:
>>>> 
>>> 
>> 
>>> I believe the rsync_xxx entries need to be under an Rsync section:
>>> [RealtimeGaugeData]
>>> .
>>> .
>>> .
>>>   [Rsync]
>>> rsync_server=xxx
>>> Rsync_user=LushEr21
>>> etc.
>>> 
>>> If that doesn’t work, I will install the extension and get it working.
>>> 
>>>>> On May 21, 2022, at 3:18 AM, philip@gmail.com  
>>>>> wrote:
>>>>> 
>>>> [RealtimeGaugeData]
>>>> date_format = %Y.%m.%d %H:%M
>>>> rtgd_path = /home/weewx/public_html
>>>> min_interval = 15
>>>> response_text = success
>>>> rsync_server = xxx.xxx.x.xxx
>>>> rsync_user = LushEr21
>>>> rsync_remote_rtgd_dir = /volume1/web/SheringhamDDNS
>>>> rsync_compress = False
>>>> rsync_log_success = True
>>>> rsync_ssh_options = "-o ConnectTimeout=1"
>>>> rsync_timeout = 1
>>>> rsync_skip_if_older_than = 4
>>>> 
>>>> The key/passwordless to the server works with
>>>> rsync -v /home/weewx/public_html/gauge-data.txt 
>>>> lush...@xxx.xxx.x.xxx:/volume1/web/SheringhamDDNS so the key/passwordless 
>>>> so am assuming the above works
>>>> Thanks for your help
>>>> Phil
>>>> 
>>>> 
>>>>> On Thursday, May 19, 2022 at 4:27:56 PM UTC+1 jo...@johnkline.com wrote:
>>>>> You need to specify the rsync parameters in the RealtimeGaugeData section 
>>>>> of weewx.conf.  Are you doing that?  Perhaps send the RealtimeGaugeData 
>>>>> section of weewx.conf so we can have a look.  From your previous emails, 
>>>>> it isn’t clear that you have the parameters in the correct section.  I 
>>>>> can tell you that this worked for me for a long time (in fact, I 
>>>>> submitted the pull request for this functionality).
>>>>> 
>>>>> # Fill out the following fields:
>>>>> #   rsync_server : The server to which gauge-data.txt will be 
>>>>> copied.
>>>>> #   rsync_user   : The userid on rsync_server with write
>>>>> #  permission to rsync_remote_rtgd_dir.
>>>>> #   rsync_remote_rtgd_dir: The directory on rsync_server where
>>>>> #  gauge-data.txt will be copied.
>>>>> #   rsync_compress   : True to compress the file before sending.
>>>>> #  Default is False.
>>>>> #   rsync_log_success: True to write success with timing messages 
>>>>> to
>>>>> #  the log (for debugging).  Default is False.
>>>>> #   rsync_ssh_options: ssh options Default is '-o 
>>>>> ConnectTimeout=1'
>>>>> #  (When connecting, time out in 1 second.)
>>>>> #   rsync_timeout: I/O timeout. Default is 1.  (When sending,
>>>>> #  timeout in 1 second.)
>>>>> #   rsync_skip_if_older_than : Don't bother to rsync if greater than this
>>>>> #  number of seconds.  Default is 4.  (Skip 
>>>>> this
>>>>> #  and move on to the next if this data is 
>>>>> older
>>>>> #   

Re: [weewx-user] Re: Realtime-_gauge-data.txt

['John Kline' via weewx-user]

BTW, this is the commit that moved the rsync parms (and, it looks like HTTP 
post parms) into a separate section:
https://github.com/gjr80/weewx-realtime_gauge-data/commit/534032cef8f1bfba45b90cf7ef939c16084a5b2e0

The README should probably change to match.


> On May 21, 2022, at 6:48 AM, John Kline  wrote:
> 
> 
> I believe the rsync_xxx entries need to be under an Rsync section:
> [RealtimeGaugeData]
> .
> .
> .
>   [Rsync]
> rsync_server=xxx
> Rsync_user=LushEr21
> etc.
> 
> If that doesn’t work, I will install the extension and get it working.
> 
>>> On May 21, 2022, at 3:18 AM, philip@gmail.com 
>>>  wrote:
>>> 
>> [RealtimeGaugeData]
>> date_format = %Y.%m.%d %H:%M
>> rtgd_path = /home/weewx/public_html
>> min_interval = 15
>> response_text = success
>> rsync_server = xxx.xxx.x.xxx
>> rsync_user = LushEr21
>> rsync_remote_rtgd_dir = /volume1/web/SheringhamDDNS
>> rsync_compress = False
>> rsync_log_success = True
>> rsync_ssh_options = "-o ConnectTimeout=1"
>> rsync_timeout = 1
>> rsync_skip_if_older_than = 4
>> 
>> The key/passwordless to the server works with
>> rsync -v /home/weewx/public_html/gauge-data.txt 
>> lushe...@xxx.xxx.x.xxx:/volume1/web/SheringhamDDNS so the key/passwordless 
>> so am assuming the above works
>> Thanks for your help
>> Phil
>> 
>> 
>>> On Thursday, May 19, 2022 at 4:27:56 PM UTC+1 jo...@johnkline.com wrote:
>>> You need to specify the rsync parameters in the RealtimeGaugeData section 
>>> of weewx.conf.  Are you doing that?  Perhaps send the RealtimeGaugeData 
>>> section of weewx.conf so we can have a look.  From your previous emails, it 
>>> isn’t clear that you have the parameters in the correct section.  I can 
>>> tell you that this worked for me for a long time (in fact, I submitted the 
>>> pull request for this functionality).
>>> 
>>> # Fill out the following fields:
>>> #   rsync_server : The server to which gauge-data.txt will be 
>>> copied.
>>> #   rsync_user   : The userid on rsync_server with write
>>> #  permission to rsync_remote_rtgd_dir.
>>> #   rsync_remote_rtgd_dir: The directory on rsync_server where
>>> #  gauge-data.txt will be copied.
>>> #   rsync_compress   : True to compress the file before sending.
>>> #  Default is False.
>>> #   rsync_log_success: True to write success with timing messages to
>>> #  the log (for debugging).  Default is False.
>>> #   rsync_ssh_options: ssh options Default is '-o ConnectTimeout=1'
>>> #  (When connecting, time out in 1 second.)
>>> #   rsync_timeout: I/O timeout. Default is 1.  (When sending,
>>> #  timeout in 1 second.)
>>> #   rsync_skip_if_older_than : Don't bother to rsync if greater than this
>>> #  number of seconds.  Default is 4.  (Skip this
>>> #  and move on to the next if this data is older
>>> #  than 4 seconds.
>>> 
>>>>> On May 19, 2022, at 6:37 AM, philip@gmail.com  
>>>>> wrote:
>>>>> 
>>>> Just to update
>>> 
>>>> Have a cron job working Ok with
>>>> rsync -v /home/weewx/public_html/gauge-data.txt 
>>>> lush...@xxx.xxx.x.xxx:/volume1/web/SheringhamDDNS so the key/passwordless 
>>>> is working
>>>> Changed
>>>>  rsync_server = xxx.xxx.x.xxx
>>>>  rsync_user = LushEr21
>>>> And it still doesnt work
>>>> If somebody has tried this and got it to work your ideas on why I cant get 
>>>> rsync to work with RTGD would be most welcome
>>>> Thanks 
>>>> 
>>>> 
>>>> 
>>>>>> On Tuesday, May 17, 2022 at 12:00:44 PM UTC+1 philip@gmail.com wrote:
>>>>>> Hi Guys
>>>>>> Ive tried and failed to get the rsync to work using realtimeguagedata
>>>>>> 
>>>>>> I never get passed gauge-data.txt file will not be exported.
>>>>>> Here is an extract of the log.
>>>>>> May 17 11:38:34 raspberrypi weewx-weewx[352] INFO user.rtgd: version is 
>>>>>> 0.5.5
>>>>>> May 17 11:38:34 raspbe

Re: [weewx-user] Re: Realtime-_gauge-data.txt

['John Kline' via weewx-user]

I believe the rsync_xxx entries need to be under an Rsync section:
[RealtimeGaugeData]
.
.
.
  [Rsync]
rsync_server=xxx
Rsync_user=LushEr21
etc.

If that doesn’t work, I will install the extension and get it working.

> On May 21, 2022, at 3:18 AM, philip@gmail.com  
> wrote:
> 
> [RealtimeGaugeData]
> date_format = %Y.%m.%d %H:%M
> rtgd_path = /home/weewx/public_html
> min_interval = 15
> response_text = success
> rsync_server = xxx.xxx.x.xxx
> rsync_user = LushEr21
> rsync_remote_rtgd_dir = /volume1/web/SheringhamDDNS
> rsync_compress = False
> rsync_log_success = True
> rsync_ssh_options = "-o ConnectTimeout=1"
> rsync_timeout = 1
> rsync_skip_if_older_than = 4
> 
> The key/passwordless to the server works with
> rsync -v /home/weewx/public_html/gauge-data.txt 
> lushe...@xxx.xxx.x.xxx:/volume1/web/SheringhamDDNS so the key/passwordless so 
> am assuming the above works
> Thanks for your help
> Phil
> 
> 
>> On Thursday, May 19, 2022 at 4:27:56 PM UTC+1 jo...@johnkline.com wrote:
>> You need to specify the rsync parameters in the RealtimeGaugeData section of 
>> weewx.conf.  Are you doing that?  Perhaps send the RealtimeGaugeData section 
>> of weewx.conf so we can have a look.  From your previous emails, it isn’t 
>> clear that you have the parameters in the correct section.  I can tell you 
>> that this worked for me for a long time (in fact, I submitted the pull 
>> request for this functionality).
>> 
>> # Fill out the following fields:
>> #   rsync_server : The server to which gauge-data.txt will be 
>> copied.
>> #   rsync_user   : The userid on rsync_server with write
>> #  permission to rsync_remote_rtgd_dir.
>> #   rsync_remote_rtgd_dir: The directory on rsync_server where
>> #  gauge-data.txt will be copied.
>> #   rsync_compress   : True to compress the file before sending.
>> #  Default is False.
>> #   rsync_log_success: True to write success with timing messages to
>> #  the log (for debugging).  Default is False.
>> #   rsync_ssh_options: ssh options Default is '-o ConnectTimeout=1'
>> #  (When connecting, time out in 1 second.)
>> #   rsync_timeout: I/O timeout. Default is 1.  (When sending,
>> #  timeout in 1 second.)
>> #   rsync_skip_if_older_than : Don't bother to rsync if greater than this
>> #  number of seconds.  Default is 4.  (Skip this
>> #  and move on to the next if this data is older
>> #  than 4 seconds.
>> 
 On May 19, 2022, at 6:37 AM, philip@gmail.com  
 wrote:
 
>>> Just to update
>> 
>>> Have a cron job working Ok with
>>> rsync -v /home/weewx/public_html/gauge-data.txt 
>>> lush...@xxx.xxx.x.xxx:/volume1/web/SheringhamDDNS so the key/passwordless 
>>> is working
>>> Changed
>>>  rsync_server = xxx.xxx.x.xxx
>>>  rsync_user = LushEr21
>>> And it still doesnt work
>>> If somebody has tried this and got it to work your ideas on why I cant get 
>>> rsync to work with RTGD would be most welcome
>>> Thanks 
>>> 
>>> 
>>> 
> On Tuesday, May 17, 2022 at 12:00:44 PM UTC+1 philip@gmail.com wrote:
> Hi Guys
> Ive tried and failed to get the rsync to work using realtimeguagedata
> 
> I never get passed gauge-data.txt file will not be exported.
> Here is an extract of the log.
> May 17 11:38:34 raspberrypi weewx-weewx[352] INFO user.rtgd: version is 
> 0.5.5
> May 17 11:38:34 raspberrypi weewx-weewx[352] INFO user.rtgd: 
> RealTimeGaugeData scroller text will use a fixed string
> May 17 11:38:34 raspberrypi weewx-tides[363] INFO weewx.engine: Using 
> archive interval of 600 seconds (specified in weewx configuration)
> May 17 11:38:34 raspberrypi weewx-weewx[352] INFO user.rtgd: 
> gauge-data.txt will not be exported.
> May 17 11:38:34 raspberrypi weewx-weewx[352] INFO user.rtgd: 
> '/home/weewx/public_html/gauge-data.txt' will be generated. min_interval 
> is 15 seconds
> 
> I have the following in the weewx.conf file
>  rsync_server = SynLusher
>   rsync_user = guest
>   rsync_remote_rtgd_dir = /volume1/web/SheringhamDDNS
>rsync_log_success = True
> 
> weewx is version 4.5.1
> 
> The HTTP POST is not being used.
> 
> I have set debug = 0, 1, 2 and 3 to try and find where it might be 
> failing but its always the same.
> The server is a Synology NAS and I can copy from the rasberry pi to the 
> rtgd_dir OK
> Just wondered if its possible to get more logs so give me a clue to where 
> is failing
> Thanks
> Phil
> 
> 
 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "weewx-user" 

Re: [weewx-user] Re: Realtime-_gauge-data.txt

['John Kline' via weewx-user]

You need to specify the rsync parameters in the RealtimeGaugeData section of 
weewx.conf.  Are you doing that?  Perhaps send the RealtimeGaugeData section of 
weewx.conf so we can have a look.  From your previous emails, it isn’t clear 
that you have the parameters in the correct section.  I can tell you that this 
worked for me for a long time (in fact, I submitted the pull request for this 
functionality).

# Fill out the following fields:
#   rsync_server : The server to which gauge-data.txt will be 
copied.
#   rsync_user   : The userid on rsync_server with write
#  permission to rsync_remote_rtgd_dir.
#   rsync_remote_rtgd_dir: The directory on rsync_server where
#  gauge-data.txt will be copied.
#   rsync_compress   : True to compress the file before sending.
#  Default is False.
#   rsync_log_success: True to write success with timing messages to
#  the log (for debugging).  Default is False.
#   rsync_ssh_options: ssh options Default is '-o ConnectTimeout=1'
#  (When connecting, time out in 1 second.)
#   rsync_timeout: I/O timeout. Default is 1.  (When sending,
#  timeout in 1 second.)
#   rsync_skip_if_older_than : Don't bother to rsync if greater than this
#  number of seconds.  Default is 4.  (Skip this
#  and move on to the next if this data is older
#  than 4 seconds.

> On May 19, 2022, at 6:37 AM, philip@gmail.com  
> wrote:
> 
> Just to update
> Have a cron job working Ok with
> rsync -v /home/weewx/public_html/gauge-data.txt 
> lushe...@xxx.xxx.x.xxx:/volume1/web/SheringhamDDNS so the key/passwordless is 
> working
> Changed
>  rsync_server = xxx.xxx.x.xxx
>  rsync_user = LushEr21
> And it still doesnt work
> If somebody has tried this and got it to work your ideas on why I cant get 
> rsync to work with RTGD would be most welcome
> Thanks 
> 
> 
> 
>> On Tuesday, May 17, 2022 at 12:00:44 PM UTC+1 philip@gmail.com wrote:
>> Hi Guys
>> Ive tried and failed to get the rsync to work using realtimeguagedata
>> 
>> I never get passed gauge-data.txt file will not be exported.
>> Here is an extract of the log.
>> May 17 11:38:34 raspberrypi weewx-weewx[352] INFO user.rtgd: version is 0.5.5
>> May 17 11:38:34 raspberrypi weewx-weewx[352] INFO user.rtgd: 
>> RealTimeGaugeData scroller text will use a fixed string
>> May 17 11:38:34 raspberrypi weewx-tides[363] INFO weewx.engine: Using 
>> archive interval of 600 seconds (specified in weewx configuration)
>> May 17 11:38:34 raspberrypi weewx-weewx[352] INFO user.rtgd: gauge-data.txt 
>> will not be exported.
>> May 17 11:38:34 raspberrypi weewx-weewx[352] INFO user.rtgd: 
>> '/home/weewx/public_html/gauge-data.txt' will be generated. min_interval is 
>> 15 seconds
>> 
>> I have the following in the weewx.conf file
>>  rsync_server = SynLusher
>>   rsync_user = guest
>>   rsync_remote_rtgd_dir = /volume1/web/SheringhamDDNS
>>rsync_log_success = True
>> 
>> weewx is version 4.5.1
>> 
>> The HTTP POST is not being used.
>> 
>> I have set debug = 0, 1, 2 and 3 to try and find where it might be failing 
>> but its always the same.
>> The server is a Synology NAS and I can copy from the rasberry pi to the 
>> rtgd_dir OK
>> Just wondered if its possible to get more logs so give me a clue to where is 
>> failing
>> Thanks
>> Phil
>> 
>> 
> 
> -- 
> 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/39fff649-3aa4-4a7b-aab5-cd6628080faen%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/A7DAC9D4-D175-4337-98A7-04C60B2061A2%40johnkline.com.

Re: [weewx-user] Setup Forecast in BelcherTown Skin

['John Kline' via weewx-user]

Use:
https://github.com/chaunceygardiner/weewx-forecast

> On May 12, 2022, at 7:25 PM, Barry  wrote:
> 
> Hi, I’m new to all this weewx stuff, and I am running into some setup 
> issues, any help would be appreciated.
> I apologise that this particular post is a duplicate of one I made a few 
> hours ago in a different thread, but I had issues with Groups quarantining my 
> messages. Anyway here is the request in its own thread.
> 
> Situation so far, Davis Vantage Pro 2 died, so has been replaced with a 
> WeatherFlow Tempest.
> 
> Using:
> Linux Mint 20.3
> Weewx v4.8
> BelcherTown v1.2
> WeatherFlow-UDP v1.1
> 
> I am attempting to get the Forecast displayed on the main page of the 
> Belchertown skin.
> This is what I’ve done so far:
> 
> Got the “stock” BelcherTown skin. Weewx and WeatherFlow-UDP all playing 
> nicely together and uploading data to my weather page.
> 
> Setup PSW account and got an API key
> Setup forwarding to PSW
> [[PWSWeather]
> enable = true
> station = STRANDHERDMEADOWS
> password = x
> PWS receives and displays my data
> 
> Setup Aeris weather account and got both the ID and Secret key
> 
> Downloaded the forecast extension “weewx-forecast-master.zip” from
> https://github.com/matthewwall/weewx-forecast
> Then installed it
> sudo wee_extension --install weewx-forecast-master.zip
> There were no errors on install.
> 
> At this point when I restart weewx it seems to go through a cycle of data 
> collection and then the syslog records this and weewx stops.:
> 
> May 12 18:07:18 linux /weewxd: weatherflowudp: MainThread: raw packet: 
> {'serial_number': 'ST-00062106', 'type': 'rapid_wind', 'hub_sn': 
> 'HB-00071538', 'ob': [1652393236, 1.24, 196]}
> May 12 18:07:18 linux weewx[545399] INFO weewx.manager: Added record 
> 2022-05-12 18:07:00 EDT (1652393220) to database 'weewx.sdb'
> May 12 18:07:18 linux weewx[545399] INFO weewx.manager: Added record 
> 2022-05-12 18:07:00 EDT (1652393220) to daily summary in 'weewx.sdb'
> May 12 18:07:18 linux weewx[545399] INFO weewx.engine: Main loop exiting. 
> Shutting engine down.
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: Caught unrecoverable 
> exception:
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__:   '>' not 
> supported between instances of 'float' and 'NoneType'
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__:   Traceback 
> (most recent call last):
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 214, in run
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__:   
> self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__:   
> callback(event)
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 634, in check_loop
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__:   raise 
> BreakLoop
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__:   
> weewx.engine.BreakLoop
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__:   
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__:   During 
> handling of the above exception, another exception occurred:
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__:   
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__:   Traceback 
> (most recent call last):
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 650, in post_loop
> May 12 18:07:18 linux weewx[545399] CRITICAL __main__:   
> self._catchup(self.engine.console.genArchiveRecords)
> 
>  Anyone any thoughts on what the problem may be, I have never done any 
> programming with Python, which is where the errors appear to be coming from. 
> Even better, is there an idiots guide to installing the forecast capability 
> out there.
> Many thanks,
> 
> Barry
> 
> -- 
> 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/74bb835e-8255-4475-8ee9-7a768c1f890en%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/8ABB2363-8AC9-4CBC-8913-3AC4AC532896%40johnkline.com.

Re: [weewx-user] Re: Davis Data Logger - Issue

['John Kline' via weewx-user]

Hi Tom,

You don’t need to restart or try a wake up.  You just need to return from 
genDavisLoopPackets so another request is made for packets.

Below is what I have been running.  You can simplify it as the bad_read 
variable is not necessary since it has NEVER occurred that two bad reads 
happened in a row.  Returning from genDavisLoopPackets on this error always 
results in the next read working (of course, the loop command is reissued first 
since genDavisLoopPackets is called again).

I have never sent this change because I’m running a copy of the vantage driver 
with many other changes.  If the excerpts below don’t make sense, you can see 
the whole driver at: https://github.com/chaunceygardiner/weewx-vantagenext

Declare an exception:
class ShortReadIOError(weewx.WeeWxIOError):
"""Exception raised when too few bytes read from serial port."""

In read, raise the exception if too few bytes are read:
N = len(_buffer)
if N != chars:
raise ShortReadIOError("Expected %d chars; got %d" % (chars, N))

And, in genDavisLoopPackets, catch the ShortReadIOError and simply return:
   try:
loop_packet = self._get_packet()
log.debug('%s: Loop packet success!' % 
weeutil.weeutil.timestamp_to_string(loop_packet['dateTime']))
except ShortReadIOError as e:
log.info('get_packet: %s. (%d)' % (e, self.pkt_count))
# If already on a bad read, log that fact.
if self.on_bad_read:
log.info('genDavisLoopPackets: repeated bad read.')
self.on_bad_read = True
return
except weewx.WeeWxIOError as e:
log.error("LOOP try #%d; error: %s", count + 1, e)
time.sleep(self.port.wait_before_retry)
else:
self.on_bad_read = False
self.pkt_count += 1
yield loop_packet
break

> On May 8, 2022, at 2:02 PM, Tom Keffer  wrote:
> 
> Now that I think about it, there is an experiment I've been meaning to try. 
> Right now, the Vantage driver tries 3 times, then gives up and restarts the 
> program from the top.
> 
> The experiment would be to do something not quite so drastic. Rather than 
> restart the program, try a Vantage "wake up" sequence instead.
> 
> I've never tried this strategy because there hasn't been a logger regularly 
> showing this error that I could test. But it appears yours does. I'm tied up 
> with something else, but give me a few days to come up with a solution.
> 
> In the meantime, I've posted issue #772.
> 
> On Sun, May 8, 2022 at 1:03 PM Dave McCreath  wrote:
>> Spoke too soon.  The error appears to back back up, is this a data logger 
>> issue?:
>> 
>> May  8 20:55:18 raspberrypi weewx[8172] INFO weewx.restx: AWEKAS: Published 
>> record 2022-05-08 20:55:00 BST (1652039700)
>> May  8 20:55:18 raspberrypi weewx[8172] INFO weewx.restx: PWSWeather: 
>> Published record 2022-05-08 20:55:00 BST (1652039700)
>> May  8 20:55:18 raspberrypi weewx[8172] INFO weewx.restx: Wunderground-PWS: 
>> Published record 2022-05-08 20:55:00 BST (1652039700)
>> May  8 20:55:19 raspberrypi weewx[8172] INFO weewx.cheetahgenerator: 
>> Generated 8 files for report SeasonsReport in 1.07 seconds
>> May  8 20:55:21 raspberrypi weewx[8172] INFO weewx.imagegenerator: Generated 
>> 30 images for report SeasonsReport in 2.44 seconds
>> May  8 20:55:21 raspberrypi weewx[8172] INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx
>> May  8 20:55:28 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
>> try #1; error: Expected to read 99 chars; got 0 instead
>> May  8 20:55:32 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
>> try #2; error: Expected to read 99 chars; got 0 instead
>> May  8 20:55:36 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
>> try #3; error: Expected to read 99 chars; got 0 instead
>> May  8 20:55:40 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
>> try #4; error: Expected to read 99 chars; got 0 instead
>> May  8 20:55:40 raspberrypi weewx[8172] ERROR weewx.drivers.vantage: LOOP 
>> max tries (4) exceeded.
>> May  8 20:55:40 raspberrypi weewx[8172] INFO weewx.engine: Main loop 
>> exiting. Shutting engine down.
>> May  8 20:55:40 raspberrypi weewx[8172] INFO weewx.engine: Shutting down 
>> StdReport thread
>> May  8 20:55:40 raspberrypi weewx[8172] CRITICAL __main__: Caught 
>> WeeWxIOError: Max tries exceeded while getting LOOP data.
>> May  8 20:55:40 raspberrypi weewx[8172] CRITICAL __main__:   Waiting 
>> 60 seconds then retrying...
>> May  8 20:56:40 raspberrypi weewx[8172] INFO __main__: retrying...
>> May  8 20:56:40 raspberrypi weewx[8172] INFO __main__: Using configuration 
>> file /etc/weewx/weewx.conf
>> May  8 20:56:40 raspberrypi weewx[8172] INFO __main__: Debug is 0
>> May  8 

Re: [weewx-user] weewx stopped creating new data after power outage

['John Kline' via weewx-user]

Have a look at this wiki article WeeWX generates HTML pages, but it does not 
update them

> On Apr 19, 2022, at 8:34 PM, iams...@gmail.com  wrote:
> 
> I have been using weewx 4.5.1 more or less continuously since late 2019, 
> running on a Pi zero. I have had occasional problems, but they always seem to 
> be resolved by a restart or a system reboot.  There was a power outage 
> yesterday that shut down the power for several hours. After the power came 
> back, I have had no new data stored or displayed. Data during the power 
> outage was recovered though. Syslog indicates that weewx was very busy after 
> power was restored uploading the missing data to Wunderground, but once that 
> was done, it stopped creating new data. Every 5 minutes, it creates a new 
> report, but there is no new data in the database, no data upload to 
> Wundergound and no change to the images used to create the report locally.
> 
> It is as if the Vantage Pro weather station has stopped working, but as far 
> as I can tell, it is fine. I had the server in debug mode before this 
> happened, so it seems like there should be a smoking gun in Syslog, but I 
> don't see it. 
> 
> Any ideas on what I should try to get back up and running? See below for a 
> Google drive link to the syslog file.  Thanks!
> 
> https://drive.google.com/file/d/1uRIm29J9T8Dv2tAg7M1G6P7fKmaXpaCy/view?usp=sharing
> -- 
> 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/b74c92af-08ea-45ac-bdb3-1d40a4773700n%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/11CC2ABD-E216-45F0-A920-143287A067DE%40johnkline.com.

Re: [weewx-user] Publishing Issue

['John Kline' via weewx-user]

> Yeah, I can't figure out why WU updates every few seconds
WU has a rapid fire setting:
See:
https://weewx.com/docs/usersguide.htm#Wunderground
PWSweather has no such equivalent

> If I can figure out how to adjust the Vantage pro hardware setting…
See:
https://weewx.com/docs/hardware.htm#vantage_notes
wee_device --set-interval=MINUTES [config_file] [-y]


> On Apr 19, 2022, at 5:46 PM, Douglas Cote  wrote:
> 
> Yeah, I can't figure out why WU updates every few seconds, but PWS waits for 
> the archive every 30 mins. If the PWS update is specifically tied to the 
> hardware archive interval then that makes sense. I guess I didn't notice what 
> the hardware might have been set to when PWS was updating more frequently. If 
> I can figure out how to adjust the Vantage pro hardware setting that might 
> get things back to how they behaved previously. Thanks for all the assistance.
> 
>> On Sunday, April 17, 2022 at 10:12:58 PM UTC-4 jo...@johnkline.com wrote:
>> You must have been using a shorter archive interval when you observed more 
>> frequent PWS updates.  The updates happen, at most, every archive interval.  
>> There is an option to make them less frequent, by setting post_interval 
>> (see: https://weewx.com/docs/usersguide.htm#%5B%5BPWSweather%5D%5D).
>> 
 On Apr 17, 2022, at 6:56 PM, Douglas Cote  wrote:
 
>>> Previously, I was getting conditions posted to my PWSweather page every 
>>> minute or so. Now it only updates every 30 minutes, which appears to 
>>> coincide with the 30 minute archive interval. So, it's at least posting new 
>>> data to the site but not at the frequency I was expecting. The attached is 
>>> a filtered syslog showing the PWS publishing events today. I was going to 
>>> try changing the record_generation parameter to software to see if it makes 
>>> a difference. Thanks.
>> 
>>> 
>>> 
 On Sunday, April 17, 2022 at 6:31:20 PM UTC-4 tke...@gmail.com wrote:
 I'm not following. What is the odd behavior? That all sounds normal. 
 
> On Sun, Apr 17, 2022 at 11:31 AM Douglas Cote  wrote:
> Thanks very much. I got it to send updates to PWS but still seeing some 
> odd behavior. I think the 30 minute interval is the default in the VPro2 
> and have no need to change it. The other thing I noticed is the PWS 
> update will only send when archive processing runs. Thanks again.
> 
>> On Saturday, April 16, 2022 at 1:31:00 PM UTC-4 tke...@gmail.com wrote:
>> This is a good example of why it's so important to include the log.
>> 
>> Your problem is corrupted memory in your Vantage logger. It has nothing 
>> to do with PWSWeather. If you take a close look, you'll see that your 
>> HTML pages are not getting updated either. 
>> 
>> To fix, see the wiki section WeeWX generates HTML pages, but it does not 
>> update them.
>> 
>> Incidentally, your archive interval is 30 minutes. Did you want it that 
>> long?
>> 
>> -tk
>> 
>>> On Sat, Apr 16, 2022 at 9:32 AM Douglas Cote  wrote:
>>> Attached an updated log. The most recent start events are around 12:21 
>>> PM ET. I can see it reference posting to PWSweather but doesn't seem to 
>>> actually do it. Thanks.
>>> 
 On Saturday, April 16, 2022 at 10:37:28 AM UTC-4 tke...@gmail.com 
 wrote:
 Everything looks normal.
 
 How about a little more of the system log? Make sure debug=1, then 
 stop and restart weewxd. Wait until the first reporting cycle is 
 finished (usually 5 or 10 minutes), then post the log from startup. 
 
> On Sat, Apr 16, 2022 at 6:46 AM Douglas Cote  
> wrote:
> Thanks. I can't see where the issue is but I've attached debug output 
> and a bit of syslog. 
> 
>> On Thursday, April 14, 2022 at 6:39:38 AM UTC-4 tke...@gmail.com 
>> wrote:
>> Hard to debug without seeing the log. 
>> 
>> Most likely you have a configuration problem. Take a careful look at 
>> the [StdRESTful] section of weewx.conf. In particular, the 
>> [[PWSweather]] subsection. Is it enabled? Is the station and 
>> password correct? 
>> 
>> Also, make sure you have the number of brackets "[[..]]" correct. Is 
>> it running on into the next subsection?
>> 
>> -tk
>> 
>>> On Wed, Apr 13, 2022 at 7:44 PM Douglas Cote  
>>> wrote:
>>> After upgrading to weewx 4.7.0, it seems I can only publish to 
>>> Weather Underground whereas before I was publishing to PWSweather 
>>> as well. I thought maybe because I had tried to add OpenWeatherMap 
>>> as another publishing location it broke the PWS RESTful service. 
>>> When I commented out the user.owm.OpenWeatherMap RESTful service 
>>> definition and restarted weewx it was still refusing to publish to 
>>> PWS. I 

Re: [weewx-user] Re: Weewx service stops randomly

['John Kline' via weewx-user]

You really should get to the bottom of why weewx is dying.  Logs are your 
friend.

I don’t have a watchdog for weewx, but I have such jobs for other software.  
Here’s a simplified script that should do the job.  If you have mail set up, 
you should add a line to mail you that weewx had to be restarted.  Also, 
replace ‘/home/weewx/bin/weewxd’ with the location of your weewxd.   Assuming 
weewx is running a root, you’ll need to add the cron entry for root.

#!/bin/sh
# If we just started up, allow some time for the process to start.
if [ `cat /proc/uptime | cut -f1 -d '.'` -le  30 ]; then
  sleep 20
fi
ps aux | grep "/home/weewx/bin/weewxd" | grep -v grep > /dev/null
if [ $? -ne 0 ]; then
/usr/shin/service weewx restart
fi

> On Apr 18, 2022, at 9:12 PM, mup...@gmail.com  wrote:
> 
> Has someone worked out a cron job that will periodically check to see that 
> weewx is running and issue a restart if it is not?
> I have been getting notified (email) about once per week letting me know that 
> weewx stopped sending data.
> 
>> On Thursday, November 25, 2021 at 12:57:32 PM UTC-8 Clyde wrote:
>> I'm running weewx 4.5.1 with a Belchertown skin on a Raspberry pi. All was 
>> working fine, but recently the service randomly stops. There is nothing in 
>> the /var/log/messages other than normal reports. Restarting the service 
>> (`service weewx restart`) resumes normal operation until the next time. The 
>> failures are happening maybe once a week, but not on any regular schedule.
>> 
>> Any ideas on how to troubleshoot this?
> 
> -- 
> 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/9b174589-69e8-4937-a9e2-8eb79de8a024n%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/EF481611-C62C-44AA-895A-12DEBA96A84F%40johnkline.com.

Re: [weewx-user] Publishing Issue

['John Kline' via weewx-user]

You must have been using a shorter archive interval when you observed more frequent PWS updates.  The updates happen, at most, every archive interval.  There is an option to make them less frequent, by setting post_interval (see: https://weewx.com/docs/usersguide.htm#%5B%5BPWSweather%5D%5D).On Apr 17, 2022, at 6:56 PM, Douglas Cote  wrote:Previously, I was getting conditions posted to my PWSweather page every minute or so. Now it only updates every 30 minutes, which appears to coincide with the 30 minute archive interval. So, it's at least posting new data to the site but not at the frequency I was expecting. The attached is a filtered syslog showing the PWS publishing events today. I was going to try changing the record_generation parameter to software to see if it makes a difference. Thanks.On Sunday, April 17, 2022 at 6:31:20 PM UTC-4 tke...@gmail.com wrote:I'm not following. What is the odd behavior? That all sounds normal. On Sun, Apr 17, 2022 at 11:31 AM Douglas Cote  wrote:Thanks very much. I got it to send updates to PWS but still seeing some odd behavior. I think the 30 minute interval is the default in the VPro2 and have no need to change it. The other thing I noticed is the PWS update will only send when archive processing runs. Thanks again.On Saturday, April 16, 2022 at 1:31:00 PM UTC-4 tke...@gmail.com wrote:This is a good example of why it's so important to include the log.Your problem is corrupted memory in your Vantage logger. It has nothing to do with PWSWeather. If you take a close look, you'll see that your HTML pages are not getting updated either. To fix, see the wiki section WeeWX generates HTML pages, but it does not update them.Incidentally, your archive interval is 30 minutes. Did you want it that long?-tkOn Sat, Apr 16, 2022 at 9:32 AM Douglas Cote  wrote:Attached an updated log. The most recent start events are around 12:21 PM ET. I can see it reference posting to PWSweather but doesn't seem to actually do it. Thanks.On Saturday, April 16, 2022 at 10:37:28 AM UTC-4 tke...@gmail.com wrote:Everything looks normal.How about a little more of the system log? Make sure debug=1, then stop and restart weewxd. Wait until the first reporting cycle is finished (usually 5 or 10 minutes), then post the log from startup. On Sat, Apr 16, 2022 at 6:46 AM Douglas Cote  wrote:Thanks. I can't see where the issue is but I've attached debug output and a bit of syslog. On Thursday, April 14, 2022 at 6:39:38 AM UTC-4 tke...@gmail.com wrote:Hard to debug without seeing the log. Most likely you have a configuration problem. Take a careful look at the [StdRESTful] section of weewx.conf. In particular, the [[PWSweather]] subsection. Is it enabled? Is the station and password correct? Also, make sure you have the number of brackets "[[..]]" correct. Is it running on into the next subsection?-tkOn Wed, Apr 13, 2022 at 7:44 PM Douglas Cote  wrote:After upgrading to weewx 4.7.0, it seems I can only publish to Weather Underground whereas before I was publishing to PWSweather as well. I thought maybe because I had tried to add OpenWeatherMap as another publishing location it broke the PWS RESTful service. When I commented out the user.owm.OpenWeatherMap RESTful service definition and restarted weewx it was still refusing to publish to PWS. I did have debug = 3 set for a bit but when looking at the output, weewx isn't even attempting to publish to PWSweather...it's ignoring it completely. Anyone see this behavior before?Thanks,Doug



-- 
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/c16fea41-b95f-4956-9efd-55cd03e9019bn%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/be6099b7-f84c-4738-9300-d5e475649230n%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/631a7bca-ed25-4181-a39b-14f082492b0en%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 

Re: [weewx-user] Opening a SQLite session on my Rasp Pi 4 to look around in the WeeWx database

['John Kline' via weewx-user]

You can browse without shutting down weewx.  Just pass sqlite3 the location of 
your weewx database (for me, that’s in /home/weewx/archive).

$ sqlite3 /home/weewx/archive/weewx.sdb 
SQLite version 3.34.1 2021-01-20 14:10:07
Enter ".help" for usage hints.
sqlite> select dateTime, outTemp from archive order by dateTime desc limit 1;
1649078100|48.6

> On Apr 4, 2022, at 6:04 AM, DR  wrote:
> 
> I have been looking for some way to open a command line or browser driven 
> version of SQLite to snoop around inside the WeeWx database just to become 
> more familiar with the layout.  I'm not trying to correct any errors (I am 
> not that worried about the way I use WeeWx mainly to capture the day and 
> generate graphs which get posted to my web server), but just want to look 
> around.  Using the latest WeeWx install on a Rasp 400 to play and start to 
> try to customize a bit.
> 
> 
> I have, obviously SQLite3 on the system, running or I don't think that WeeWx 
> would function.  I have found the directory where the database exists based 
> on the documentation in the User Guide.  I can't find any documentation as to 
> how to trigger SQLite so I can uses command lines, and while there  are a few 
> things for Linux that say they allow you to open a browser like window to 
> look at the database, once I download them, I don't find where they are 
> installed or how to trigger them to open up.  I assume from the screen shots 
> of them that there is a way to change directories until I get to the WeeWx 
> database, but  can't even try doing that.
> 
> 
> Oh, once I get to be able to do this, do I have to shut down WeeWx while I 
> look around, or can WeeWx continue to access the SQLite database at the same 
> time to keep updating it when it needs to?  Or is there a collision and it 
> will require a restart of WeeWx to pickup again once I'm done peeking inside?
> 
> Dale
> 
> 
> -- 
> 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/6791f34e-ce65-d411-a7f0-511f58e02c26%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/3FEE78FC-DEFF-429D-A57A-FA71A5B04CB3%40johnkline.com.

Re: [weewx-user] Error generating loop-data.txt with 4.6.2

['John Kline' via weewx-user]

Yes, you must be running WeeWX 4.6.x.  Install the latest release of loopdata 
(which is version 2.10).

> On Feb 21, 2022, at 6:49 PM, Marty b  wrote:
> 
> 
> Hello everyone,
> 
> My loop-data generation recently stopped working.  Here is a section from my 
> syslog that shows the error:
> 
> Feb 21 00:35:14 WeeWx2021 weewx[560] INFO user.rtgd: 
> '/dev/shm/weewx/gauge-data.txt' wil be generated. min_interval is None
> Feb 21 00:35:14 WeeWx2021 weewx[560] INFO user.loopdata: Service version is 
> 2.7.2.
> Feb 21 00:35:14 WeeWx2021 weewx[560] ERROR user.loopdata: Could not find 
> target_report: LoopDataReport.  LoopData is exiting. Exception: missing 
> option "minute_label"  in interpolation.
> Feb 21 00:35:14 WeeWx2021 weewx[560] INFO __main__: Starting up weewx version 
> 4.6.2
> F
> 
> Any suggestion on resolving this?
> 
> Thanks,
> Marty
> -- 
> 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/8228f6ce-270e-400f-a559-5320a59f13c4n%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/07B3E1D3-FFDD-41F8-8B34-344CDAB15648%40johnkline.com.

Re: [weewx-user] RTLDavis windRun calculation and rain records

['John Kline' via weewx-user]

Thanks, Tom.

I don’t think that’s the problem as I add an interval to the (copy of) the 
packet.  That is needed because I keep my own set of accumulators so that 
loopdata can write out observations on every loop packet (in its own thread) 
and never have to access the database.  I can add an interval because the user 
specifies a LoopFrequency in seconds.

Indeed, on my VantagePro2 and RainWise weewx installs, I have no problem with 
windrun in loopdata.

I’ve seen issues at startup when I’ve tried the WeatherLinkUDP driver and I 
have code not checked in to catch and ignore errors to make it pass the 
startup, but I worry that loopdata won’t be accurate for drivers where loop 
packets don’t always contain all the data.  It’s not something I am likely to 
tackle anytime soon.

I’m guessing this driver is one of those cases, where loops don’t contain all 
the observations.  If so, it’s not a good candidate to use loopdata (at least, 
not at this time).

To the original OP, does everything work fine without loopdata?  Furthermore, 
does loopdata break the operation of weewx?  I’d be surprised if this is true 
as the loopdata thread should just die.


> On Feb 21, 2022, at 4:09 PM, Tom Keffer  wrote:
> 
> 
> loopdata is trying to calculate windrun, which requires a value for 
> 'interval'. You need it to multiply against velocity to get distance. 
> Unfortunately, 'interval' is not available in loop packets because they come 
> at irregular intervals. 
> 
> The source for loopdata could be modified to only calculate windrun if 
> possible. For example, this patch should work (NOT TESTED):
> 
> Index: bin/user/loopdata.py
> ===
> diff --git a/bin/user/loopdata.py b/bin/user/loopdata.py
> --- a/bin/user/loopdata.py (revision 0ee9d2ba94c53888154363aa412f1d5d5002ff12)
> +++ b/bin/user/loopdata.py (date 1645488401429)
> @@ -807,11 +807,14 @@
>  pkt_time: int   = to_int(pkt['dateTime'])
>  pkt['interval'] = self.cfg.loop_frequency / 60.0
>  
> -windrun_val = 
> weewx.wxxtypes.WXXTypes.calc_windrun('windrun', pkt)
> -pkt['windrun'] = windrun_val[0]
> -if windrun_val[0] > 0.00 and 'windDir' in pkt and 
> pkt['windDir'] is not None:
> -bkt = LoopProcessor.get_windrun_bucket(pkt['windDir'])
> -pkt['windrun_%s' % windrun_bucket_suffixes[bkt]] = 
> windrun_val[0]
> +try:
> +windrun_val = 
> weewx.wxxtypes.WXXTypes.calc_windrun('windrun', pkt)
> +pkt['windrun'] = windrun_val[0]
> +if windrun_val[0] > 0.00 and 'windDir' in pkt and 
> pkt['windDir'] is not None:
> +bkt = 
> LoopProcessor.get_windrun_bucket(pkt['windDir'])
> +pkt['windrun_%s' % windrun_bucket_suffixes[bkt]] = 
> windrun_val[0]
> +except weewx.CannotCalculate:
> +pass
>  
>  beaufort_val = 
> weewx.wxxtypes.WXXTypes.calc_beaufort('beaufort', pkt)
>  pkt['beaufort'] = beaufort_val[0]
> 
> 
>> On Sun, Feb 20, 2022 at 7:57 AM Andrew Roberts  
>> wrote:
>> Hi,
>> I'm after a steer as to where to look to fix/block this issue. I'm running 
>> RTLDavis with a Vantage Vue and weewx 4.6.1. The indoor temperature and 
>> pressure (BMP280) is coming through as a data service over a serial link.
>> 
>> When I start up weewx and use loopdata, syslog shows:
>> 
>> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:  
>>  Traceback (most recent call last):
>> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:  
>>File "/usr/share/weewx/user/loopdata.py", line 810, in process_queue
>> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:  
>>  windrun_val = weewx.wxxtypes.WXXTypes.calc_windrun('windrun', pkt)
>> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:  
>>File "/usr/share/weewx/weewx/wxxtypes.py", line 303, in calc_windrun
>> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:  
>>  raise weewx.CannotCalculate(key)
>> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:  
>>  weewx.CannotCalculate: windrun
>> 
>> 1. Looking into the code it seems to be a lack of interval data. I can not 
>> find a way of sorting this in weewx.conf and close inspection of the 
>> RTLDavis DEBUG data  in Syslog (attached) doesn't have any interval data in 
>> it.
>> 
>> 2. In spite of it raining, the console reporting rain and after tipping a 
>> cup of water into the bucket I'm not reliably getting rain data from the 
>> ISS. the DEBUG (all three debug options set to 3) log records:
>> 
>> DEBUG user.rtldavis:  data_pkt: {'channel': 1, 'bat_iss': 0, 
>> 'wind_speed_ec': 15, 'wind_speed_raw': 14, 'wind_dir': 273.9486166007905, 
>> 'wind_speed': 

Re: [weewx-user] Anyone else seeing Wunderground Rapid Fire down?

['John Kline' via weewx-user]

The problem was on the wunderground side.  It’s back now.

> On Feb 6, 2022, at 6:00 PM, Nate Bargmann  wrote:
> 
> It looks like Wunderground Rapid Fire upload has been down for about an
> hour.  Even restarting WeeWX 4.5.1 did not resolve the issue.  Network
> connectivity seems to be okay as I can ping wunderground.com.
> 
> - Nate
> 
> -- 
> "The optimist proclaims that we live in the best of all
> possible worlds.  The pessimist fears this is true."
> Web: https://www.n0nb.us
> Projects: https://github.com/N0NB
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
> 
> -- 
> 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/20220207020030.ycii4x6vjxkl2pud%40n0nb.us.

-- 
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/31EF8D9E-A267-4FD9-B0B5-B0C1F0FC2242%40johnkline.com.

Re: [weewx-user] Re: Chill Hours Extension

['John Kline' via weewx-user]

Another example:

https://github.com/chaunceygardiner/weewx-purple/blob/e7f214539b63281d74af9e90810045dd8d1b7b80/bin/user/purple.py#L538

> On Jan 21, 2022, at 2:01 PM, Seth Ratner  wrote:
> 
> It looks like there is an example in the  weewx-xaggs repository. I'm about 
> to dive in, but from a cursory look, unlike with the scalar, I'm going to 
> have to figure out how to use dbmanager to pull the outtemps from the 
> database then iterate through each one, determine which ones are chill hours, 
> and then add those together, correct?
> 
>> On Friday, January 21, 2022 at 3:49:33 PM UTC-6 tke...@gmail.com wrote:
>> Let me see if I can come up with something. Give me some time.
>> 
>>> On Fri, Jan 21, 2022 at 1:37 PM Seth Ratner  wrote:
>>> Oh boy...
>>> 
>>> I cant find any examples for that. If one exists, it will greatly reduce 
>>> the number of questions I have...
>>> 
 On Friday, January 21, 2022 at 3:24:07 PM UTC-6 tke...@gmail.com wrote:
 You're getting close!
 
 You're going to have to implement get_aggregate(), as well as get_scalar().
 
 The xtypes framework has no way of taking the calculation for get_scalar() 
 and using it to calculate an aggregate. You're going to have to do it.  
 The good news is that once you've done it, then the framework can use that 
 to calculate a series on its own. This is where we will find out how fast 
 the calculation is.
 
 -tk
 
> On Fri, Jan 21, 2022 at 12:51 PM Seth Ratner  wrote:
> Getting Closer, but still getting errors. 
> 
> I can now see the result in the archive loop (gets sent over MQTT). But 
> with the seasons skin attempts to make a chart with it, I get:
> 
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine: 
> Caught unrecoverable exception in generator 
> 'weewx.imagegenerator.ImageGenerator'
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine:  
>  chillHours
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine:  
>  Traceback (most recent call last):
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine:  
>File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine:  
>  obj.start()
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine:  
>File "/usr/share/weewx/weewx/reportengine.py", line 281, in 
> start
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine:  
>  self.run()
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine:  
>File "/usr/share/weewx/weewx/imagegenerator.py", line 41, in 
> run
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine:  
>  self.genImages(self.gen_ts)
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine:  
>File "/usr/share/weewx/weewx/imagegenerator.py", line 177, in 
> genImages
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine:  
>  start_vec_t, stop_vec_t ,data_vec_t = 
> weewx.xtypes.get_series(var_type,
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine:  
>File "/usr/share/weewx/weewx/xtypes.py", line 94, in get_series
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine:  
>  raise weewx.UnknownType(obs_type)
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine:  
>  weewx.UnknownType: chillHours
> Jan 21 14:40:39 Ratner-Orchard weewx[3122] ERROR weewx.reportengine:  
>  Generator terminated
> 
> Here's the block I added in skin.conf
> 
> [[[yearchill]]]
> plot_type = bar
> chillHours
> aggregate_type = cumulative
> aggregate_interval = day
> 
> 
>> On Friday, January 21, 2022 at 2:14:11 PM UTC-6 Seth Ratner wrote:
>> I'm close, I think, except now I'm getting this every loop or report 
>> generation.
>> 
>> DEBUG weewx.wxservices: Unknown extensible type 'chillHours'
>> 
>> There are a couple things I'm unsure of that might be causing this
>> 
>> - I used the group type group_elapsed because it seemed like the best fit
>> - The last line of the python file, modeled after the VaporPressure.py 
>> example, is not part of either class, so I'm not sure what runs it. 
>> 
>> Here's the code: 
>> https://github.com/lordratner/weewx_chillHours/blob/main/chill_hours.py
>> 
>> It's been added to weewx.conf engine section in xtypes, and I've 
>> confirmed the service is loading. 
>> 
>> Thoughts?
>> 
>> 
>>> On 

Re: [weewx-user] Vanage Pro 2 crashes WeeWx daily

['John Kline' via weewx-user]

I don’t the time syncs are an issue.  I believe the time syncs after DHCP 
adverts are because of the following file:

/etc/dhcp/dhclient-exit-hooks.d/timesyncd

On each DHCP renewal, this script is called which causes a restart with the NTP 
servers passed by DHCP (which probably haven’t changed).  It’s not the greatest 
for stable time, but it’s good enough for most.  I’ve ripped this out on my 
machines.

> On Jan 13, 2022, at 1:49 PM, vince  wrote:
> 
> Change one thing at a time please.
> 
>> On Thursday, January 13, 2022 at 1:37:21 PM UTC-8 timot...@gmail.com wrote:
>> 
>> Sorry Tom, didn't see your question.  The logger is a USB logger not a 
>> serial with a USB adaptor.
>> 
>> I'll try the pi4 and see if we can maybe eliminate the pi(s) as being the 
>> culprits.  I am also trying to locate another logger.
>> 
>> Don't know what to say about the network time synchronizations.
>> 
>> Thanks again you guys..
>> 
>> Tim
>>> On Thursday, January 13, 2022 at 10:42:25 AM UTC-10 vince wrote:
>>> All I can suggest is that if you can swap in a different pi/SD/power-supply 
>>> and it goes away, that would point to the pi3 being the problem.  If the 
>>> problem continues with a different computer, that would point to your 
>>> datalogger probably.
>>> 
>>> Your logger will save a week of readings, so there's little risk of losing 
>>> readings if you swap in a different pi temporarily for a couple days.
>>> 
>>> You didn't answer Tom's question - is it a Davis USB logger, or a serial 
>>> logger and serial2usb adaptor ?
>>> 
> 
> -- 
> 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/614627b7-692c-4db3-af74-1973267627ean%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/64A79A3F-00D7-43B4-B2F8-6A615E95D401%40johnkline.com.

Re: [weewx-user] Re: Determine source of metric which fails QC

['John Kline' via weewx-user]

Hi Joel,

The purple extension does NOT insert pressure into the loop packet.  You can 
see that for yourself if you look at new_loop_packet in the plugin.  Are you 
modifying the extension to add it?

> On Dec 17, 2021, at 2:49 AM, gjr80  wrote:
> 
> There are many ways to handle unit conversion, some more sophisticated than 
> others. Here are a couple of fairly basic approaches 
> https://github.com/matthewwall/weewx-maxbotix/blob/master/bin/user/maxbotix.py#L142
>  and 
> https://gitlab.com/wjcarpenter/bme280wx/-/blob/master/bin/user/bme280wx.py#L82
> 
> Gary
> 
>> On Friday, 17 December 2021 at 20:30:03 UTC+10 jbar...@gmail.com wrote:
>> Thanks!  You mind pointing me at a reference implementation of a service 
>> class that does this all correctly?  I'm likely able to get it working on my 
>> own if I see how it is to be done.
>> 
>>> On Friday, December 17, 2021 at 2:11:13 AM UTC-8 gjr80 wrote:
>>> Any values have to be analysed in context of the unit system of the packet 
>>> into which they are inserted. The unit system of packets emitted by the sdr 
>>> driver when reading acurite devices is either US customary or metric 
>>> depending on the sensors being read. As far as I can tell the purple air 
>>> extension you are using does not perform any check of the unit system of 
>>> the loop packet (loop packet field usUnits) to which pressure is added, but 
>>> I could be wrong. Normally you would find something in the method of the 
>>> service class that is bound to the NEW_LOOP_PACKET event (in this case 
>>> Purple.new_loop_packet()) that checks usUnits and converts pressures, 
>>> temperature, speeds etc to match the packet units. Or if not in that method 
>>> in the code called by that method. 
>>> 
>>> I’m not about to try to debug someone else’s extension, especially one as 
>>> complex as this. John, the author, frequents the forums so give it a day or 
>>> so and see if he comments. Otherwise I suggest you raise an issue in his 
>>> repo.
>>> 
>>> Gary
>>> 
 On Friday, 17 December 2021 at 19:16:38 UTC+10 jbar...@gmail.com wrote:
 Well,  I have basically two sources: acurite sensors via sdr and the 
 purple api via a purple api plugin.  The acurite sensors don't expose 
 pressure and the rtl433 logs never indicate that a pressure is detected in 
 the acurite information.  
 
 The purple api does expose pressure and it comes in as millibars: 
 200 success
 {
   "api_version" : "V1.0.10-0.0.12",
   "time_stamp" : 1639725648,
   "data_time_stamp" : 1639725596,
   "sensor" : {
 "sensor_index" : 81961,
 "pressure" : 1018.5
   }
 }
 
 That said there are log lines that indicate the pressure was read from 
 purple and included as inHg in the result.
 
 weewx[1] DEBUG user.purple: Inserted packet[pressure]: 30.096963 into 
 packet.
 
 I've run the purple plugin locally and verified that is is converted to 
 inHg.  The conversion happens here: 
 https://github.com/chaunceygardiner/weewx-purple/blob/e7f214539b63281d74af9e90810045dd8d1b7b80/bin/user/purple.py#L266.
   Is this the proper way of doing it?  If not, can you point me to an 
 example of doing it properly in a plugin?
 
 
 
 
 
> On Friday, December 17, 2021 at 12:39:29 AM UTC-8 gjr80 wrote:
> What driver are you using and what is the source of the pressure value? 
> This sounds very much like a service is being used to add one or more of 
> the three pressure fields (altimeter, barometer or pressure) to 
> packets/records from the driver and the unit system of the packet/record 
> is not being checked and followed. This can result in fields being added 
> to packets/records in the wrong units which eventually results in a 
> double unit conversion.
> 
> The answer will almost certainly be related to the source of one of the 
> three pressure fields.
> 
> Gary
>> On Friday, 17 December 2021 at 17:56:10 UTC+10 jbar...@gmail.com wrote:
>> BTW, running on Develop
>> 
>>> On Thursday, December 16, 2021 at 11:54:46 PM UTC-8 Joel Baranick wrote:
>>> What is the best way to determine the source of a metric which fails 
>>> QC?  The failure in this case is the "pressure" metrics which is 
>>> expected to be in inHq.  The QC error is: `LOOP value 'pressure' 
>>> 0.8885885448234093 outside limits (24.0, 34.5)`.  It seems like the 
>>> pressure is converted to inHq correctly: `Inserted packet[pressure]: 
>>> 30.091057 into packet.`. But, it seems like the  30.091057 is being be 
>>> fed back into the conversion function.
> 
> -- 
> 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 
>