Re: [weewx-user] Wlink doesn't run

[Tom Keffer]

It looks like the wlink extension was never ported to Python 3.

On Wed, May 15, 2024 at 3:35 AM Justin Wenk  wrote:

> Hi everyone! I have the following problem: I want to use the “Wlink”
> extension (https://github.com/weewx/weewx/wiki/wlink). I followed the
> instructions but I always get an error. I use WeeWX on macOS (Sonoma
> 14.13.1).
>
> *Log:*
>
> 2024-05-15 12:01:32 weewxd[2676]: INFO weewxd: Initializing weewxd version
> 5.0.2
> 2024-05-15 12:01:32 weewxd[2676]: INFO weewxd: Command line:
> /Users/justin/weewx-venv/bin/weewxd
> 2024-05-15 12:01:32 weewxd[2676]: INFO weewxd: Using Python 3.12.3
> (v3.12.3:f6650f9ad7, Apr  9 2024, 08:18:47) [Clang 13.0.0
> (clang-1300.0.29.30)]
> 2024-05-15 12:01:32 weewxd[2676]: INFO weewxd: Located at
> /Users/justin/weewx-venv/bin/python3
> 2024-05-15 12:01:33 weewxd[2676]: INFO weewxd: Platform
> macOS-14.3.1-arm64-arm-64bit
> 2024-05-15 12:01:33 weewxd[2676]: INFO weewxd: Locale: 'de_DE.UTF-8'
> 2024-05-15 12:01:33 weewxd[2676]: INFO weewxd: Entry path:
> /Users/justin/weewx-venv/lib/python3.12/site-packages/weewxd.py
> 2024-05-15 12:01:33 weewxd[2676]: INFO weewxd: WEEWX_ROOT:
> /Users/justin/weewx-data
> 2024-05-15 12:01:33 weewxd[2676]: INFO weewxd: Configuration file:
> /Users/justin/weewx-data/weewx.conf
> 2024-05-15 12:01:33 weewxd[2676]: INFO weewxd: User module:
> /Users/justin/weewx-data/bin/user
> 2024-05-15 12:01:33 weewxd[2676]: INFO weewxd: Debug: 1
> 2024-05-15 12:01:33 weewxd[2676]: DEBUG weewxd: Initializing engine
> 2024-05-15 12:01:33 weewxd[2676]: INFO weewx.engine: Loading station type
> WeatherLink (user.wlink)
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd: Caught unrecoverable
> exception:
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:   multiple
> exception types must be parenthesized (wlink.py, line 180)
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:   Traceback
> (most recent call last):
>
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd: File
> "/Users/justin/weewx-venv/lib/python3.12/site-packages/weewxd.py", line
> 160, in main
>
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:   engine =
> weewx.engine.StdEngine(config_dict)
>
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd: 
> ^^^
>
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd: File
> "/Users/justin/weewx-venv/lib/python3.12/site-packages/weewx/engine.py",
> line 77, in __init__
>
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd: 
>  self.setupStation(config_dict)
>
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd: File
> "/Users/justin/weewx-venv/lib/python3.12/site-packages/weewx/engine.py",
> line 104, in setupStation
>
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd: 
>  __import__(driver)
>
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd: File
> "/Users/justin/weewx-data/bin/user/wlink.py", line 180
>
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:   except
> (urllib2.URLError, socket.error,
>
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd: 
> ^
>
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:   SyntaxError:
> multiple exception types must be parenthesized
>
> 2024-05-15 12:01:33 weewxd[2676]: CRITICAL weewxd:   Exiting.
>
>
>
>
>
>
>
> 
> Wlink.py is located in the /weewx-data/bin/user folder.
>
> *A part from the weewx.conf:*
>
>
> ##
>
> #   This section is for information about the station.
>
> [Station]
>
> # Description of the station location, such as your town.
> location = HalleWetter
>
> # Latitude in decimal degrees. Negative for southern hemisphere.
> latitude = 51.52
> # Longitude in decimal degrees. Negative for western hemisphere.
> longitude = 11.85
>
> # Altitude of the station, with the unit it is in. This is used only
> # if the hardware cannot supply a value.
> altitude = 94, meter# Choose 'foot' or 'meter' for unit
>
> # Set to type of station hardware. There must be a corresponding stanza
> # in this file, which includes a value for the 'driver' option.
> station_type = WeatherLink
>
> # If you have a website, you may specify an URL. The URL is required
> if you
> # intend to register your station. The URL must include the scheme, for
> # example, "http://; or "https://;
> #station_url = https://www.example.com
>
> # The start of the rain year (1=January; 10=October, etc.). This is
> # downloaded from the station if the hardware supports it.
> rain_year_start = 1
>
> # Start of week (0=Monday, 6=Sunday)
> week_start = 6
>
>
> 

Re: [weewx-user] Update 4.10.2 -> 5.0.2, strange problem with reports

[Tom Keffer]

Don't really understand the error because the tag "$current.dateTime"
occurs only in the titlebar.inc template and the rss.xml.tmpl template, not
in index.html.tmpl, nor in statistics.html.tmpl.

Two things:

1. What version of Cheetah? You can get this with

*python3 -c "import Cheetah;print(Cheetah.Version)"*


2. Could you please create a tarball of your copy of the Seasons skin and
send it to me? Email is tkef...@gmail.com. I'm thinking there may be a BOM
or something in there...

*tar cvfz seasons.tar.gz /etc/weewx/skins/Seasons*




On Mon, May 13, 2024 at 12:48 PM 'Wolfgang Bosswick' via weewx-user <
weewx-user@googlegroups.com> wrote:

> I had a running 4.10.2 installation with a modified Seasons skin on ubuntu
> desktop 22.10 which worked fine until it stopped updating the sensor
> reports anymore (I assume hanging USB port at the weather station unit).
> Resetting the weather station unit did not solve the problem (Bus 003
> Device 003: ID 1941:8021 Dream Link WH1080 Weather Station / USB Missile
> Launcher).
> Meanwhile I reolaced the weather station since the humidity sensor stopped
> working some months ago anyway (I learned that these sensor need to be
> replaced around 2 yrs of use).
> The new station worked fine, however it did not update the statistics
> report, all sensor reports are fine up to date. Syslog claimed an ERROR -
> weewx.cheetahgenerator: Evaluation of template
> /etc/weewx/skins/Seasons/statistics.html.tmpl failed with exception ' 'SyntaxError'>', in line 1, string not terminated.
> Checked the template, everything seems fine, there had been mande no
> changes anyway.
> I updated to 5.0.2 (yes, stupid move updating a broken system...)
> Now I have the strange result that the website is updated with the sensor
> reports perfectly, but the statistics part is not updated. The same error
> is now in several other reports which went through without errors before.
> Due to the switch to 5.0.2, I changed access rights for the user weewx and
> group weewx to r/w, ownership root. See the related loc section below.
>
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: INFO weewx.manager: Added
> record 2024-05-13 19:55:00 CEST (1715622900) to database 'weewx.sdb'
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: INFO weewx.manager: Added
> record 2024-05-13 19:55:00 CEST (1715622900) to daily summary in 'weewx.sdb'
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator: Evaluation of template
> /etc/weewx/skins/Seasons/index.html.tmpl failed with exception ' 'SyntaxError'>'
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator:  Ignoring template
> /etc/weewx/skins/Seasons/index.html.tmpl
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator:  Reason: unterminated string literal (detected
> at line 1) (, line 1)
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator:   Traceback (most recent call last):
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 334, in generate
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator:   unicode_string =
> compiled_template.respond()
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator: File
> "_etc_weewx_skins_Seasons_index_html_tmpl.py", line 205, in respond
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator: File
> "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1708, in
> _handleCheetahInclude
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator: 
>  self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator: File
> "_etc_weewx_skins_Seasons_titlebar_inc.py", line 134, in respond
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator: File
> "_etc_weewx_skins_Seasons_titlebar_inc.py", line 78, in __errorCatcher2
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator: File "", line 1
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator: 
>  VFN(VFFSL(SL,"current.dateTime",True),"format",False)("Zuletzt
> Aktualisiert:
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator: 
>  ^
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator:   SyntaxError: unterminated string literal
> (detected at line 1)
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator: Evaluation of template
> /etc/weewx/skins/Seasons/statistics.html.tmpl failed with exception ' 'SyntaxError'>'
> May 13 19:55:38 wolfgang-desktop weewxd[37274]: ERROR
> weewx.cheetahgenerator:  Ignoring template
> 

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

[Tom Keffer]

Be sure to read the wiki notes on *Moving the wview database
<https://github.com/weewx/weewx/wiki/Moving-the-wview-database#mysql>*.

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

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

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

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

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

[Tom Keffer]

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

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

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

Hope that answers your question.


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

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

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

Re: [weewx-user] Re: Vantage Vue: how to override humidity sensor values

[Tom Keffer]

On Wed, May 8, 2024 at 1:28 AM Lieven Hollevoet 
wrote:

>
> I did find back this thread:
> https://www.mail-archive.com/weewx-user@googlegroups.com/msg47494.html
> where I extracted the following correction formula:
>
> outHumidity = extraHumid1 if 'extraHumid1' in locals() else None
>

Of course! Totally forgot about that solution!

-- 
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/CAPq0zECa7ikWHYOuRsOkS6jd9pV0Fk3wxZ01_RjRks%3DLECjp6A%40mail.gmail.com.

Re: [weewx-user] HTML – files are not updated!

[Tom Keffer]

Impossible to say without seeing the log. See Help! Posting to weewx-user
 for how
to get a good log.

On Tue, May 7, 2024 at 5:38 AM Albin von Moos 
wrote:

> Post translated from German to English with Google Translate! Hello I run
> WeeWX on a Raspberry 4 with the latest operating system. Since I switched
> to new WeeWX 5.X. My homepage is only updated the first time it is
> started and then no longer. Previously the update was approximately every
> 10 minutes. You can see the link to my weather data: Sachseln, Central
> Switzerland (albin-ow.ch) Interestingly, the station data is updated! Station
> data♦ Hardware Vantage Pro2 geogr. Latitude 46° 52.43' N geogr. Longitude
> 008° 14.67' E height above NN 500 m Server runtime 0 days, 23 hours, 20
> minutes WeeWX duration 0 days, 21 hours, 17 minutes WeeWX version 5.0.2 Skin
> Seasons 5.0.2 Even if I restart the program nothing is updated. I have to
> switch off the Raspberry for a few days (de-energize it) and then restart
> it. Now the data is being transferred. That means the transmission works
> (I haven't changed anything about it). I hope someone can help me. I'm
> very unhappy with the situation.
>
> Thanks Albin
>
> --
> 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/e50539c4-8207-4c16-862b-81d85fcd9bb3n%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/CAPq0zEBrQNoeE7fUYT3%3D%3D1-Kt6wnkNCtenWapZSjgVVEEyA4mA%40mail.gmail.com.

Re: [weewx-user] Re: Upgraded to V5 - will not run automaticly

[Tom Keffer]

A major change between V4 and V5 is daemon and file ownerships. By default,
V5 runs as user "weewx", not "root."

Be sure to check the Upgrade Guide
!


On Mon, May 6, 2024 at 3:41 PM G7LTT  wrote:

> And that's one of the issues. No logs are being written. /var/log/syslog
> has nothing and neither does/var/log/weewx/weexd.log. The debug=1 setting
> is set.
>
> This was working just fine under V4 so I can't believe its to do with
> things like perms.
>
> "running a somewhat unusual setup"? I assume you have no other users
> runing weewx in a container? Makes total sense to do it that way when you
> think about it. Even on an RPi. Why waste a whole machine on such a trivial
> task?
>
> I'll take another swing at it. see if I can't get some logging going.
>
> Mark
>
> On Sunday, May 5, 2024 at 4:53:16 PM UTC-4 vince wrote:
>
>> We can't read minds.   Need to see actual logs with debug=1 set in
>> weewx.conf and ideally your weewx.conf file as well.
>>
>> The usual error tends to be permissions accessing the hardware or the
>> network itself.   Considering you're running a somewhat unusual setup you
>> might want to provide a way for folks to try to look at what you might be
>> missing within your container image.
>>
>>
>> On Sunday, May 5, 2024 at 12:39:03 PM UTC-7 G7LTT wrote:
>>
>>> So I upgraded to V5.0.4 from 4.whatever and it looked like everything
>>> went ok. But then about an hour later I noticed that the web pages were not
>>> being updated.  Off to the logs I go - nothing in the logs.
>>>
>>> Hmmnnn. OK, time to run it manually at the command line to see if it
>>> spews anything out. Nope, works perfectly. I can leave "weewxd" running for
>>> hours without any error. And the pages get updated/uploaded etc etc etc.
>>> What gives?
>>>
>>> I am running Weewx in an LXC container on Proxmox in my homelab system.
>>> I have the Ambient WS2000 API installed (rather than talk to the station it
>>> collects the station data from Ambient themselves).
>>>
>>> V4 was running as expected in daemon mode. It would survive a
>>> reboot/restart of the machine and the container. V5? Not so much. But there
>>> are no entries in the log files for it which is making me suspicious.
>>>
>>> Any ideas?
>>>
>>>
>>>
>> --
> 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/0a125bbf-e4ca-429a-a7ea-6af232e67bb7n%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/CAPq0zEBb4tz%3D%3DsD73inoAVnOPt%2BC58c%2B-YGioqm0iRUK4sG%3D-Q%40mail.gmail.com.

Re: [weewx-user] Weewx 5.0.2 webpage isn't updating automatically requiring manual refresh

[Tom Keffer]

 weatherflowudp: MainThread: Listening
> for UDP broadcasts to IP address 0.0.0.0 on port 50222, with timeout 90 and
> share_socket False...
> May 06 21:15:18 pi4 weewxd[3365]: DEBUG weewx.reportengine: Running report
> 'SeasonsReport'
> May 06 21:15:18 pi4 weewxd[3365]: DEBUG weewx.reportengine: Found
> configuration file /etc/weewx/skins/Seasons/skin.conf for report
> 'SeasonsReport'
> May 06 21:15:18 pi4 weewxd[3365]: DEBUG weewx.reportengine: Running
> generators for report 'SeasonsReport' in directory
> '/etc/weewx/skins/Seasons'
> May 06 21:15:19 pi4 weewxd[3365]: DEBUG weewx.cheetahgenerator: Using
> search list ['weewx.cheetahgenerator.Almanac',
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.DisplayOptions',
> 'weewx.cheetahgenerator.E>May 06 21:15:19 pi4 weewxd[3365]: DEBUG
> weewx.manager: Daily summary version is 4.0
> May 06 21:15:20 pi4 weewxd[3365]: DEBUG weewx.manager: Daily summary
> version is 4.0
> May 06 21:15:21 pi4 weewxd[3365]: DEBUG weewx.reportengine: Report
> 'SmartphoneReport' not enabled. Skipping.
> May 06 21:15:21 pi4 weewxd[3365]: DEBUG weewx.reportengine: Report
> 'MobileReport' not enabled. Skipping.
> May 06 21:15:21 pi4 weewxd[3365]: DEBUG weewx.reportengine: Report
> 'StandardReport' not enabled. Skipping.
> May 06 21:15:21 pi4 weewxd[3365]: DEBUG weewx.reportengine: Report 'FTP'
> not enabled. Skipping.
> May 06 21:15:21 pi4 weewxd[3365]: DEBUG weewx.reportengine: Report 'RSYNC'
> not enabled. Skipping.
>
> Copy of weewx.conf
> # WEEWX CONFIGURATION FILE
> #
> # Copyright (c) 2009-2024 Tom Keffer 
> # See the file LICENSE.txt for your rights.
>
>
> ##
>
> # This section is for general configuration information.
>
> # Set to 1 for extra debug info, otherwise comment it out or set to zero.
> debug = 1
>
> # Whether to log successful operations. May get overridden below.
> log_success = False
>
> # Whether to log unsuccessful operations. May get overridden below.
> log_failure = True
>
> # This configuration file was created by ...
> version = 5.0.2
>
>
> ##
>
> #   This section is for information about the station.
>
> [Station]
>
> # Description of the station location
> location = "Ashton on Mersey - Weather Station, Sale, UK"
>
> # Latitude in decimal degrees. Negative for southern hemisphere
> latitude = 53.42532
> # Longitude in decimal degrees. Negative for western hemisphere.
> longitude = -2.34762
>
> # Altitude of the station, with unit it is in. This is downloaded from
> # from the station if the hardware supports it.
> altitude = 22, meter
>
> # Set to type of station hardware. There must be a corresponding stanza
> # in this file with a 'driver' parameter indicating the driver to be
> used.
> station_type = WeatherFlowUDP
>
> # If you have a website, you may specify an URL
> station_url = http://tempestwx.com/station/56524
>
> # The start of the rain year (1=January; 10=October, etc.). This is
> # downloaded from the station if the hardware supports it.
> rain_year_start = 1
>
> # Start of week (0=Monday, 6=Sunday)
> week_start = 0
>
>
>
> ##
>
> [Simulator]
> # This section is for the weewx weather station simulator.
>
> # The time (in seconds) between LOOP packets.
> #loop_interval = 2.5
>
> # The simulator mode can be either 'simulator' or 'generator'.
> # Real-time simulator. Sleep between each LOOP packet.
> #mode = simulator
> # Generator.  Emit LOOP packets as fast as possible (useful for
> testing).
> #mode = generator
>
> # The start time. Format is -mm-ddTHH:MM. If not specified, the
> # default is to use the present time.
> #start = 2011-01-01T00:00
>
> # The driver to use.
> #driver = weewx.drivers.simulator
>
>
> ##
>
>
> ##
>
> [WeatherFlowUDP]
> driver = user.weatherflowudp
> log_raw_packets = False
> udp_address = 0.0.0.0
> # udp_address = 0.0.0.0
> # udp_address = 255.255.255.255
> udp_port = 50222
> udp_timeout = 90
> share_socket = False
>
> [[sensor_map]]
> outTemp = air_temperature.ST-00048813.obs_st
> outHumidity = relative_humidity.ST-00048813.obs_st
> pressure = station_

Re: [weewx-user] Vantage Vue: how to override humidity sensor values

[Tom Keffer]

You could try

outHumidity = extraHumid1 if extraHumid1 is not None else None

I don't know if this will work, but I'm thinking that for the packets that
do not include extraHumid1, you will get a NameError exception, which WeeWX
ignores. So, outHumidity will be None unless there's a value for
extraHumid1.

Give it a try...

On Mon, May 6, 2024 at 1:21 AM Lieven Hollevoet 
wrote:

> Hello fellow weewx-users,
>
> I am happily running weewx in combination with a Davis Vantage Vue station
> since 2018.
>
> Recently, the humidity sensor of my station has developed a problem in
> which it sometimes report 'sane' values and sometimes it reports a 0 or 1%
> relative humidity. This of course results in very wonky dewpoint
> calculations and so I set out to fix it.
> Replacement sensors are no longer available, soldering a new sensor in the
> station is not an option.
>
> I don't want to replace the complete sensor suite in the outdoor unit as
> all other sensors are still working fine. I opted to setup a new relative
> humidity sensor. I attached a Bosch BME280 sensor to the Luftdaten air
> quality sensor that I have running near the weather station to measure
> valid relative humidity values.
>
> I am pulling the BME280 relative humidity sensor values via Home Assistant
> from the Luftdaten sensor and I am posting it to an MQTT broker. WeeWX
> reads the relative humidity sensor values from the BME280 using the
> MQTTSubscribeService. The new relative humidity sensor value are reported
> in the extraHumid1 sensor in WeeWX.
>
> This is all working as expected.
>
> The question I have: is there a way to override the standard 'outHumidity'
> readings that come from the LOOP packets that are read from the Vantage
> station with the valid readings from the extraHumid1 sensor?
>
> I tried using the [StdCalibrate] > [[Corrections]] setting in the
> configuration but the problem is that the LOOP packets from the Vantage
> station with the invalid relative humidity readings are much more
> frequently received than the updates from the MQTT service that only
> updates the sensor value every 2 minutes. So the override with the
> corrections only happens when a new MQTT message is received, all the other
> intermediate loop pakets still contain the invalid relative humidity
> readings from the Vantage driver (the 'outHumidity' sensor).
>
> I searched the documentation but I did not find a way to implement what I
> try to do. Does somebody have a pointer that I can follow to solve this
> issue?
>
> For your reference: my weather data with the invalid and the valid
> relative humidity sensor can be found on http://weer.lika.be
>
> Thanks in advance,
>  Lieven.
>
> --
> 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/0270db27-4a43-4f55-99f3-b67eb4273200n%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/CAPq0zEAyH-%2B%2BcUaXtVMCY9docPbXDUND6z5wp15LW4cyXZDXWw%40mail.gmail.com.

Re: [weewx-user] No primary key on archive

[Tom Keffer]

But, there is a primary key: field dateTime. It should be defined as
"INTEGER NOT NULL UNIQUE PRIMARY KEY".

You're not seeing that?

On Tue, Apr 30, 2024 at 9:39 PM Clay Jackson  wrote:

> I'm importing weewx data from a mariadb  database to a percona xtradb  and
> it has strict primary key enforcement turned on.  Is there a reason there's
> a key but not a primary key defined for the archive table?
>
> --
> 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/5c4a39f8-5517-4c26-9a79-98ac3df11b6fn%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/CAPq0zEDn_A0BBk3Jhd1i9jLzrt3Abu3R0rQdjQ_iH1_-_nSt7Q%40mail.gmail.com.

Re: [weewx-user] Re: Remove/update archive (history) data

[Tom Keffer]

Perhaps you're looking at an old HTML file? If you delete them all, weewx
will regenerate at the next reporting cycle using the new data.

On Tue, Apr 30, 2024 at 10:19 PM 'Tomasz Lewicki' via weewx-user <
weewx-user@googlegroups.com> wrote:

> OK, sorry for a noise. I found instructions on the wiki:
> https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data
>
> But it's strange that I see April's values in history section despite
> weewx.sdb oldest data is 2024-05-01 00:00:00.
>
> środa, 1 maja 2024 o 06:55:45 UTC+2 Tomasz Lewicki napisał(a):
>
>> Dear Weewx users.
>>
>> My station was in "test mode" until midnight May 1. Now I want to remove
>> all data before this date. SQLite database is modified and has only data
>> after May 1, 00:00:00. But in my archive (history) data on website I see
>> earlier months and max/min values too. How to get rid of them? I suppose
>> some 'weectl database' command but which one?
>>
> --
> 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/53cec26d-06c5-4bab-be0e-6b67054cab74n%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/CAPq0zEAd%2BH8e8XKg2er39ZkOkz%3DZqP%3DB_KysEdSb05Reuewo2Q%40mail.gmail.com.

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

[Tom Keffer]

Vince, Redhat doesn't necessarily allow socket access for ports over 1024?

On Tue, Apr 30, 2024 at 4:57 PM vince  wrote:

> Marco are you running with selinux in enforcing mode ? Can you check for
> selinux errors in your logs or perhaps temporarily run with selinux
> disabled to see if that helps ?
>
> Sorry but I’m away from a computer so I can’t give you the precise
> commands, but selinux can rather quietly stop things from working in some
> configurations. It would be helpful to eliminate that possibility.
>
> Other possibility is that your weewx user isn’t in a group with network
> access. What does ‘groups weewx’ return ?
> On Tuesday, April 30, 2024 at 11:39:51 AM UTC-7 Tom Keffer wrote:
>
>> I am not that familiar with the IP logger, but I assume you would obey
>> the same echo TEST as a regular logger. If it doesn't, then it sounds like
>> there is a connectivity problem.
>>
>> Yes, it worked under WeeWX V3.8, but you have also changed servers since
>> then.
>>
>> Double check any firewalls. For example, do you use iptables? Does your
>> router prevent indiscriminate traffic between ports?
>>
>>
>>
>> On Tue, Apr 30, 2024 at 10:45 AM Marco Citossi  wrote:
>>
>>> I've tried to change weewx.service but without results.
>>> Telent doesn't echo anything.
>>> The network should work because the old weewx (3.8.xxx) on the other
>>> webserver is working.
>>>
>>> Il giorno martedì 30 aprile 2024 alle 19:03:43 UTC+2 Tom Keffer ha
>>> scritto:
>>>
>>>> I am wondering whether the network is up and running by the time weewxd
>>>> tries to access it. Try editing your weewx systemd service file (normally
>>>> located in /lib/systemd/system/weewx.service) so it looks something like
>>>> the following:
>>>>
>>>> [Unit]
>>>> Description=WeeWX
>>>> Documentation=https://weewx.com/docs
>>>> Requires=time-sync.target
>>>> After=time-sync.target
>>>> After=network-online.target
>>>> Requires=network-online.target
>>>>
>>>> Then
>>>>
>>>> *sudo systemctl daemon-reload*
>>>> *sudo systemctl restart weewx*
>>>>
>>>> If that doesn't work, we can try putting a sleep command in the startup.
>>>>
>>>> Also, can you telnet to the logger and perform the logger TEST
>>>> function? The IP address of your logger got cut off in the log, but it
>>>> would look something like this (replace 140.105.xxx.yyy with the IP
>>>> address):
>>>>
>>>> telnet 140.105.xxx.yyy 2
>>>> press  a few times.
>>>> Then type "TEST", all caps. It will not echo.
>>>> then 
>>>> The logger should respond with "TEST".
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Apr 30, 2024 at 9:21 AM Marco Citossi 
>>>> wrote:
>>>>
>>>>> Yes it's ethernet.
>>>>>
>>>>> Here it is the log:
>>>>>
>>>>>
>>>>> apr 30 18:07:10 web4.xxx systemd[1]: Started WeeWX.
>>>>>
>>>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Initializing
>>>>> weewxd version 5.0.2
>>>>>
>>>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Command line:
>>>>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>>>>>
>>>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Using Python
>>>>> 3.6.8 (default, Jan 16 2024, 02:08:59)
>>>>>
>>>>>  [GCC 8.5.0 20210514
>>>>> (Red Hat 8.5.0-20.0.1)]
>>>>>
>>>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Located at
>>>>> /usr/bin/python3
>>>>>
>>>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Platform
>>>>> Linux-5.4.17-2136.330.7.1.el8uek.x86_64-x86_64-with-oracle-8.9
>>>>>
>>>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Locale:
>>>>> 'en_US.UTF-8'
>>>>>
>>>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Entry path:
>>>>> /usr/share/weewx/weewxd.py
>>>>>
>>>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: WEEWX_ROOT:
>>>>> /etc/weewx
>>>>>
>>>>> apr 30 18:07:10 web4.xxx weewxd[22596

Re: [weewx-user] Celestial tab time format

[Tom Keffer]

That's a different format, called DeltaFormats. Unfortunately, it's not
documented, but it would look something like this:

[StdReport]
  ...
  [[Defaults]]
...
[[[Units]]]
  ...
  DeltaTimeFormats
hour= "%(minute)dm %(second)ds"
day = "%(hour)dh %(minute)dm %(second)ds"

On Tue, Apr 30, 2024 at 4:44 PM n7uv...@gmail.com 
wrote:

> Hi Tom -
>
> Perhaps this answers the question I'm about to ask, but am unsure. When I
> see
>
> [image: Screenshot 2024-04-30 164027.png]
> this on my Celestial tab, I'd much prefer Total daylight 13:30:55 or 13h
> 30m 55s and
> same for the delta sunlight 01:46 or 01m 46s
>
> It doesn't look like the above weewx.conf mods will do what I want. How do
> I change the format?
>
> Cheers - Jon N7UV
>
> On Tuesday, April 30, 2024 at 8:59:18 AM UTC-7 Tom Keffer wrote:
>
>> It's under TimeFormats
>> <https://www.weewx.com/docs/5.0/reference/skin-options/units/#timeformats>
>> .
>>
>> Best to change it in weewx.conf:
>>
>> [StdReport]
>>   ...
>>   [[Defaults]]
>> ...
>> [[[Units]]]
>>   ...
>>   TimeFormats
>> ...
>> ephem_day = %I:%M %p
>> ephem_year = %d-%b-%Y %I:%M %p
>>
>>
>>
>> On Tue, Apr 30, 2024 at 4:50 AM bhouseski  wrote:
>>
>>> where do I go to change the time format in the celestial tab?  I am not
>>> a 24 time fan, and would like to change to AM/PM.
>>>
>>> Mike
>>>
>>> --
>>> 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/f565645d-1e14-4b63-9af2-38586a420b84n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/f565645d-1e14-4b63-9af2-38586a420b84n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/31201972-d652-4741-8628-b6562dd6c552n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/31201972-d652-4741-8628-b6562dd6c552n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEBUPAYeKVOiE7TZx%3Dd3pciTpvUQQj1KJZv-ifu6m0UqiA%40mail.gmail.com.

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

[Tom Keffer]

I am not that familiar with the IP logger, but I assume you would obey the
same echo TEST as a regular logger. If it doesn't, then it sounds like
there is a connectivity problem.

Yes, it worked under WeeWX V3.8, but you have also changed servers since
then.

Double check any firewalls. For example, do you use iptables? Does your
router prevent indiscriminate traffic between ports?



On Tue, Apr 30, 2024 at 10:45 AM Marco Citossi  wrote:

> I've tried to change weewx.service but without results.
> Telent doesn't echo anything.
> The network should work because the old weewx (3.8.xxx) on the other
> webserver is working.
>
> Il giorno martedì 30 aprile 2024 alle 19:03:43 UTC+2 Tom Keffer ha scritto:
>
>> I am wondering whether the network is up and running by the time weewxd
>> tries to access it. Try editing your weewx systemd service file (normally
>> located in /lib/systemd/system/weewx.service) so it looks something like
>> the following:
>>
>> [Unit]
>> Description=WeeWX
>> Documentation=https://weewx.com/docs
>> Requires=time-sync.target
>> After=time-sync.target
>> After=network-online.target
>> Requires=network-online.target
>>
>> Then
>>
>> *sudo systemctl daemon-reload*
>> *sudo systemctl restart weewx*
>>
>> If that doesn't work, we can try putting a sleep command in the startup.
>>
>> Also, can you telnet to the logger and perform the logger TEST function?
>> The IP address of your logger got cut off in the log, but it would look
>> something like this (replace 140.105.xxx.yyy with the IP address):
>>
>> telnet 140.105.xxx.yyy 2
>> press  a few times.
>> Then type "TEST", all caps. It will not echo.
>> then 
>> The logger should respond with "TEST".
>>
>>
>>
>>
>> On Tue, Apr 30, 2024 at 9:21 AM Marco Citossi  wrote:
>>
>>> Yes it's ethernet.
>>>
>>> Here it is the log:
>>>
>>>
>>> apr 30 18:07:10 web4.xxx systemd[1]: Started WeeWX.
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Initializing
>>> weewxd version 5.0.2
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Command line:
>>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Using Python
>>> 3.6.8 (default, Jan 16 2024, 02:08:59)
>>>
>>>  [GCC 8.5.0 20210514
>>> (Red Hat 8.5.0-20.0.1)]
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Located at
>>> /usr/bin/python3
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Platform
>>> Linux-5.4.17-2136.330.7.1.el8uek.x86_64-x86_64-with-oracle-8.9
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Locale:
>>> 'en_US.UTF-8'
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Entry path:
>>> /usr/share/weewx/weewxd.py
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: WEEWX_ROOT:
>>> /etc/weewx
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Configuration
>>> file: /etc/weewx/weewx.conf
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: User module:
>>> /etc/weewx/bin/user
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Debug: 1
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: DEBUG __main__: Initializing
>>> engine
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: INFO weewx.engine: Loading
>>> station type Vantage (weewx.drivers.vantage)
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: DEBUG weewx.drivers.vantage:
>>> Driver version is 3.6.2
>>>
>>> apr 30 18:07:10 web4.xxx weewxd[22596]: DEBUG weewx.drivers.vantage:
>>> Option loop_request=1
>>>
>>> apr 30 18:07:14 web4.xxx weewxd[22596]: ERROR weewx.drivers.vantage:
>>> Socket error while opening port 2 to ethernet host 140.105.>
>>>
>>> apr 30 18:07:14 web4.xxx weewxd[22596]: ERROR weewx.engine: Import of
>>> driver failed: timed out ()
>>>
>>> apr 30 18:07:14 web4.xxx weewxd[22596]: CRITICAL weewx.engine: 
>>> Traceback (most recent call last):
>>>
>>> apr 30 18:07:14 web4.xxx weewxd[22596]: CRITICAL weewx.engine: 
>>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 35>
>>>
>>> apr 30 18:07:14 web4.xxx weewxd[2

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

[Tom Keffer]

CAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 53>
>
> apr 30 18:07:14 web4.xxx weewxd[22596]: CRITICAL weewx.engine: 
>   self.port.openPort()
>
> apr 30 18:07:14 web4.xxx weewxd[22596]: CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 35>
>
> apr 30 18:07:14 web4.xxx weewxd[22596]: CRITICAL weewx.engine: 
>   raise weewx.WeeWxIOError(ex)
>
> apr 30 18:07:14 web4.xxx weewxd[22596]: CRITICAL weewx.engine: 
> weewx.WeeWxIOError: timed out
>
> apr 30 18:07:14 web4.xxx weewxd[22596]: CRITICAL __main__: Unable to load
> driver: timed out
>
> apr 30 18:07:14 web4.xxx weewxd[22596]: CRITICAL __main__: 
> Exiting...
>
> apr 30 18:07:14 web4.xxx systemd[1]: weewx.service: Main process exited,
> code=exited, status=4/NOPERMISSION
>
> apr 30 18:07:14 web4.xxx systemd[1]: weewx.service: Failed with result
> 'exit-code'.
>
> Il giorno martedì 30 aprile 2024 alle 16:54:54 UTC+2 Tom Keffer ha scritto:
>
>> Apologies. You have an ethernet device, right? So, it's going to connect
>> to a network port, not a USB port.
>>
>> Could you please post the full log? The systemctl status reports are very
>> brief and don't give line numbers.
>>
>> Set debug=1, then try restarting weewx. Post the log.
>>
>> Thanks.
>>
>> On Tue, Apr 30, 2024 at 4:28 AM Marco Citossi  wrote:
>>
>>> the problem is that if I stop the service and I restart it works for
>>> just a glimpse. I try again status and I get the error.
>>>
>>> weewx.service - WeeWX
>>>
>>>Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled;
>>> vendor preset: disabled)
>>>
>>>Active: active (running) since Tue 2024-04-30 12:00:53 CEST; 4s ago
>>>
>>>  Docs: https://weewx.com/docs
>>>
>>>  Main PID: 19495 (python3)
>>>
>>> Tasks: 1 (limit: 48736)
>>>
>>>Memory: 9.1M
>>>
>>>CGroup: /system.slice/weewx.service
>>>
>>>└─19495 python3 /usr/share/weewx/weewxd.py
>>> /etc/weewx/weewx.conf
>>>
>>>
>>>
>>>
>>>
>>> Il giorno martedì 30 aprile 2024 alle 09:57:26 UTC+2 Marco Citossi ha
>>> scritto:
>>>
>>>> The device has an ethernet port. Now it is working in another webserver.
>>>> I've also tried to stop the service in the other web server but the
>>>> result is the same.
>>>> If I do lsusb I don't get anything.
>>>>
>>>> Il giorno lunedì 29 aprile 2024 alle 20:14:20 UTC+2 Tom Keffer ha
>>>> scritto:
>>>>
>>>>> It seems that your device is not being recognized by the udev rule,
>>>>> perhaps because it is has an ethernet port.
>>>>>
>>>>> Check the vendor and product ID of your logger with the command
>>>>> "lsusb". It will output something like
>>>>>
>>>>> Bus 001 Device 003: ID 18e8:6238 Qcom
>>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>>> Bus 002 Device 002: ID 10c4:ea60 Cygnal Integrated Products, Inc.
>>>>> CP2102/CP2109 UART Bridge Controller [CP210x family]
>>>>> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>>>>
>>>>> In this case, 10c4 is the vendor ID and ea60 is the product id.
>>>>> Substitute whatever values you get for the "idVendor" and "idProduct"
>>>>> fields, respectively, in the rules file. Then unplug the logger and plug 
>>>>> it
>>>>> back in again.
>>>>>
>>>>> See what you get for ownership after that.
>>>>>
>>>>> -tk
>>>>>
>>>>>
>>>>> On Mon, Apr 29, 2024 at 10:05 AM Marco Citossi 
>>>>> wrote:
>>>>>
>>>>>> Hi!
>>>>>>
>>>>>> I've checked the article you suggested and looking the permissions in
>>>>>> /etc/udev/rules.d/60-weewx.rules I see in the file:
>>>>>>
>>>>>>
>>>>>> *# davis vantage via usb-serial*
>>>>>>
>>>>>>
>>>>>> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="ea60",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>>>>>>
>>>>>>
>

Re: [weewx-user] Celestial tab time format

[Tom Keffer]

It's under TimeFormats
.

Best to change it in weewx.conf:

[StdReport]
  ...
  [[Defaults]]
...
[[[Units]]]
  ...
  TimeFormats
...
ephem_day = %I:%M %p
ephem_year = %d-%b-%Y %I:%M %p



On Tue, Apr 30, 2024 at 4:50 AM bhouseski  wrote:

> where do I go to change the time format in the celestial tab?  I am not a
> 24 time fan, and would like to change to AM/PM.
>
> Mike
>
> --
> 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/f565645d-1e14-4b63-9af2-38586a420b84n%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/CAPq0zEBrW0O5mQ%2BXo%3DgdMfT9uDH%2BMfmN3BFjpaCJm2LPc1aX1Q%40mail.gmail.com.

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

[Tom Keffer]

Apologies. You have an ethernet device, right? So, it's going to connect to
a network port, not a USB port.

Could you please post the full log? The systemctl status reports are very
brief and don't give line numbers.

Set debug=1, then try restarting weewx. Post the log.

Thanks.

On Tue, Apr 30, 2024 at 4:28 AM Marco Citossi  wrote:

> the problem is that if I stop the service and I restart it works for just
> a glimpse. I try again status and I get the error.
>
> weewx.service - WeeWX
>
>Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor
> preset: disabled)
>
>Active: active (running) since Tue 2024-04-30 12:00:53 CEST; 4s ago
>
>  Docs: https://weewx.com/docs
>
>  Main PID: 19495 (python3)
>
> Tasks: 1 (limit: 48736)
>
>Memory: 9.1M
>
>CGroup: /system.slice/weewx.service
>
>└─19495 python3 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>
>
>
>
>
> Il giorno martedì 30 aprile 2024 alle 09:57:26 UTC+2 Marco Citossi ha
> scritto:
>
>> The device has an ethernet port. Now it is working in another webserver.
>> I've also tried to stop the service in the other web server but the
>> result is the same.
>> If I do lsusb I don't get anything.
>>
>> Il giorno lunedì 29 aprile 2024 alle 20:14:20 UTC+2 Tom Keffer ha scritto:
>>
>>> It seems that your device is not being recognized by the udev rule,
>>> perhaps because it is has an ethernet port.
>>>
>>> Check the vendor and product ID of your logger with the command "lsusb".
>>> It will output something like
>>>
>>> Bus 001 Device 003: ID 18e8:6238 Qcom
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 002 Device 002: ID 10c4:ea60 Cygnal Integrated Products, Inc.
>>> CP2102/CP2109 UART Bridge Controller [CP210x family]
>>> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>>
>>> In this case, 10c4 is the vendor ID and ea60 is the product id.
>>> Substitute whatever values you get for the "idVendor" and "idProduct"
>>> fields, respectively, in the rules file. Then unplug the logger and plug it
>>> back in again.
>>>
>>> See what you get for ownership after that.
>>>
>>> -tk
>>>
>>>
>>> On Mon, Apr 29, 2024 at 10:05 AM Marco Citossi 
>>> wrote:
>>>
>>>> Hi!
>>>>
>>>> I've checked the article you suggested and looking the permissions in
>>>> /etc/udev/rules.d/60-weewx.rules I see in the file:
>>>>
>>>>
>>>> *# davis vantage via usb-serial*
>>>>
>>>>
>>>> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="ea60",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>>>>
>>>>
>>>> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTR{idProduct}=="ea61",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>>>>
>>>>
>>>> It seems already ok.
>>>>
>>>>
>>>> If I try with ls -l /dev/ttyS0 I get:
>>>>
>>>>
>>>> crw-rw 1 root dialout 4, 64 28 apr 23.12 /dev/ttyS0
>>>>
>>>>
>>>> and it seems ok.
>>>>
>>>>
>>>>
>>>>
>>>> Il giorno lunedì 29 aprile 2024 alle 18:52:45 UTC+2 Tom Keffer ha
>>>> scritto:
>>>>
>>>>> Looks like a permissions issue accessing the port. See the wiki
>>>>> article How to fix device permissions
>>>>> <https://github.com/weewx/weewx/wiki/Understanding-permissions#how-to-fix-device-permissions>
>>>>>  and
>>>>> see if that helps.
>>>>>
>>>>> On Mon, Apr 29, 2024 at 9:48 AM Marco Citossi 
>>>>> wrote:
>>>>>
>>>>>> Hi! I've installed weewx in Oracle Linux 8.9 following the guide for
>>>>>> RedHat.
>>>>>>
>>>>>> The installation has completed without errors. It has been installed
>>>>>> in default folders,  in /var/www/html/weewx (weewx:weewx), 
>>>>>> /usr/share/weewx
>>>>>> (root:root) and /etc/weewx (weewx:weewx) for bin and weewx.conf
>>>>>>
>>>>>> Only weewx.conf is root:weewx.
>>>>>>
>>>>>> Device driver is VantagePro2 , ethernet port.
>>>>>

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

[Tom Keffer]

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_series
> Apr 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_fn
> Apr 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 execute
> Apr 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 execute
> Apr 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 _query
> Apr 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 query
> Apr 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_result
> Apr 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 read
> Apr 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_packet
> Apr 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_series
> Apr 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 occurred:
> Apr 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/weedb/mysql.py", line
> 53, in guarded_fn
> Apr 29 16:26:12 weewx python3[2282]: return fn(*args, **kwargs)
> Apr 29 16:26:12 weewx python3[2282]: File
> "/home/weewx/weewx-venv/lib/python3.10/site-packages/weedb/mysql.py", line
> 

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

[Tom Keffer]

It seems that your device is not being recognized by the udev rule, perhaps
because it is has an ethernet port.

Check the vendor and product ID of your logger with the command "lsusb". It
will output something like

Bus 001 Device 003: ID 18e8:6238 Qcom
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 10c4:ea60 Cygnal Integrated Products, Inc.
CP2102/CP2109 UART Bridge Controller [CP210x family]
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

In this case, 10c4 is the vendor ID and ea60 is the product id. Substitute
whatever values you get for the "idVendor" and "idProduct" fields,
respectively, in the rules file. Then unplug the logger and plug it back in
again.

See what you get for ownership after that.

-tk


On Mon, Apr 29, 2024 at 10:05 AM Marco Citossi  wrote:

> Hi!
>
> I've checked the article you suggested and looking the permissions in
> /etc/udev/rules.d/60-weewx.rules I see in the file:
>
>
> *# davis vantage via usb-serial*
>
>
> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="ea60",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>
>
> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTR{idProduct}=="ea61",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>
>
> It seems already ok.
>
>
> If I try with ls -l /dev/ttyS0 I get:
>
>
> crw-rw 1 root dialout 4, 64 28 apr 23.12 /dev/ttyS0
>
>
> and it seems ok.
>
>
>
>
> Il giorno lunedì 29 aprile 2024 alle 18:52:45 UTC+2 Tom Keffer ha scritto:
>
>> Looks like a permissions issue accessing the port. See the wiki article How
>> to fix device permissions
>> <https://github.com/weewx/weewx/wiki/Understanding-permissions#how-to-fix-device-permissions>
>>  and
>> see if that helps.
>>
>> On Mon, Apr 29, 2024 at 9:48 AM Marco Citossi  wrote:
>>
>>> Hi! I've installed weewx in Oracle Linux 8.9 following the guide for
>>> RedHat.
>>>
>>> The installation has completed without errors. It has been installed in
>>> default folders,  in /var/www/html/weewx (weewx:weewx), /usr/share/weewx
>>> (root:root) and /etc/weewx (weewx:weewx) for bin and weewx.conf
>>>
>>> Only weewx.conf is root:weewx.
>>>
>>> Device driver is VantagePro2 , ethernet port.
>>>
>>> Old installation (3.8.0a1) in old web server is working.
>>>
>>>
>>>
>>> When I try to start weewx, it starts for a while then I get this error:
>>>
>>>
>>> ● weewx.service - WeeWX
>>>
>>>Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled;
>>> vendor preset: disabled)
>>>
>>>Active: failed (Result: exit-code) since Mon 2024-04-29 18:23:46
>>> CEST; 14s ago
>>>
>>>  Docs: https://weewx.com/docs
>>>
>>>   Process: 11571 ExecStart=/usr/bin/weewxd /etc/weewx/weewx.conf
>>> (code=exited, status=4)
>>>
>>>  Main PID: 11571 (code=exited, status=4)
>>>
>>>
>>> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL weewx.engine: **
>>> Vantage.*__init__*(self, **config_d>
>>>
>>> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL weewx.engine: **
>>>   File "/usr/share/weewx/weewx/driver>
>>>
>>> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL weewx.engine: **
>>> self.port.openPort()
>>>
>>> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL weewx.engine: **
>>>   File "/usr/share/weewx/weewx/driver>
>>>
>>> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL weewx.engine: **
>>> raise weewx.WeeWxIOError(ex)
>>>
>>> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL weewx.engine: **
>>> weewx.WeeWxIOError: timed out
>>>
>>> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL *__main__*: Unable to
>>> load driver: timed out
>>>
>>> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL *__main__*: **
>>> Exiting...
>>>
>>> apr 29 18:23:46 web4.xxx systemd[1]: weewx.service: Main process exited,
>>> code=exited, status=4/NOPERMISSION
>>>
>>> apr 29 18:23:46 web4.xxx systemd[1]: weewx.service: Failed with result
>>> 'exit-code'.
>>>
>>>
>>> If I do a restart for a while I get:
>>>
>>>
>>> weewx.service - WeeWX
>>>
>>>Loaded: loaded (/usr/lib/systemd/system/wee

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

[Tom Keffer]

Looks like a permissions issue accessing the port. See the wiki article How
to fix device permissions

and
see if that helps.

On Mon, Apr 29, 2024 at 9:48 AM Marco Citossi  wrote:

> Hi! I've installed weewx in Oracle Linux 8.9 following the guide for
> RedHat.
>
> The installation has completed without errors. It has been installed in
> default folders,  in /var/www/html/weewx (weewx:weewx), /usr/share/weewx
> (root:root) and /etc/weewx (weewx:weewx) for bin and weewx.conf
>
> Only weewx.conf is root:weewx.
>
> Device driver is VantagePro2 , ethernet port.
>
> Old installation (3.8.0a1) in old web server is working.
>
>
>
> When I try to start weewx, it starts for a while then I get this error:
>
>
> ● weewx.service - WeeWX
>
>Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor
> preset: disabled)
>
>Active: failed (Result: exit-code) since Mon 2024-04-29 18:23:46 CEST;
> 14s ago
>
>  Docs: https://weewx.com/docs
>
>   Process: 11571 ExecStart=/usr/bin/weewxd /etc/weewx/weewx.conf
> (code=exited, status=4)
>
>  Main PID: 11571 (code=exited, status=4)
>
>
> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL weewx.engine: **
> Vantage.*__init__*(self, **config_d>
>
> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL weewx.engine: **
>   File "/usr/share/weewx/weewx/driver>
>
> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL weewx.engine: **
> self.port.openPort()
>
> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL weewx.engine: **
>   File "/usr/share/weewx/weewx/driver>
>
> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL weewx.engine: **
> raise weewx.WeeWxIOError(ex)
>
> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL weewx.engine: **
> weewx.WeeWxIOError: timed out
>
> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL *__main__*: Unable to
> load driver: timed out
>
> apr 29 18:23:46 web4.xxx weewxd[11571]: CRITICAL *__main__*: **
> Exiting...
>
> apr 29 18:23:46 web4.xxx systemd[1]: weewx.service: Main process exited,
> code=exited, status=4/NOPERMISSION
>
> apr 29 18:23:46 web4.xxx systemd[1]: weewx.service: Failed with result
> 'exit-code'.
>
>
> If I do a restart for a while I get:
>
>
> weewx.service - WeeWX
>
>Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor
> preset: disabled)
>
>Active: active (running) since Mon 2024-04-29 18:32:53 CEST; 3s ago
>
>  Docs: https://weewx.com/docs
>
>  Main PID: 11671 (python3)
>
> Tasks: 1 (limit: 48736)
>
>Memory: 11.3M
>
>CGroup: /system.slice/weewx.service
>
>└─11671 python3 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>
>
> apr 29 18:32:53 web4.xxx weewxd[11671]: INFO *__main__*: Locale:
> 'en_US.UTF-8'
>
> apr 29 18:32:53 web4.xxx weewxd[11671]: INFO *__main__*: Entry path:
> /usr/share/weewx/weewxd.py
>
> apr 29 18:32:53 web4.xxx weewxd[11671]: INFO *__main__*: WEEWX_ROOT:
> /etc/weewx
>
> apr 29 18:32:53 web4.xxx weewxd[11671]: INFO *__main__*: Configuration
> file: /etc/weewx/weewx.conf
>
> apr 29 18:32:53 web4.xxx weewxd[11671]: INFO *__main__*: User module:
> /etc/weewx/bin/user
>
> apr 29 18:32:53 web4.xxx weewxd[11671]: INFO *__main__*: Debug: 1
>
> apr 29 18:32:53 web4.xxx weewxd[11671]: DEBUG *__main__*: Initializing
> engine
>
> apr 29 18:32:53 web4.xxx weewxd[11671]: INFO weewx.engine: Loading station
> type Vantage (weewx.drivers.vantage)
>
> apr 29 18:32:53 web4.xxx weewxd[11671]: DEBUG weewx.drivers.vantage:
> Driver version is 3.6.2
>
> apr 29 18:32:53 web4.xxx weewxd[11671]: DEBUG weewx.drivers.vantage:
> Option loop_request=1
>
> --
> 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/68ba097e-fc7d-4812-bd1c-64e0b2266f68n%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/CAPq0zEBaM_XDBVZCeKYitkUKbqjFe3az9_65o3cHU-D3CKy_1Q%40mail.gmail.com.

Re: [weewx-user] Noob question about curly braces - only peripheral to weewx

[Tom Keffer]

You are looking at a CSS file, not a Python file. In a CSS file, the hash
mark (#) is an *ID Selector*, not a comment.

So, a CSS entry of

#my-heading h1 {
  font-weight: bold;
}


would use a bold font for the entity with id "my-heading":

This is my heading


The hash mark (#) is used because it's analogous to an anchor reference .

Comments are C-style. They use surrounding /* and */;

/* This is a comment */


Hope that helps.

-tk

On Sun, Apr 28, 2024 at 3:51 PM n7uv...@gmail.com 
wrote:

> I have no idea what I'm talking about here. However, while tweaking
> various .html.tmpl and .inc files, I saw this in celestial.html.tmpl
> [image: Screenshot 2024-04-28 154723.png]
> The leading curly brace is commented out, while the trailing mate is not.
> Obviously, it seems to work. Is this because (I think) Python relies upon
> indentation, not braces?
>
> I removed the hashes, and it runs the same.
>
> Cheers -- Jon N7UV
>
> --
> 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/f4326510-ea85-4aaf-af9d-591340389614n%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/CAPq0zEDpLZhO6eY1qsx5bSqjGnCGFvfrh%3DpNKH5vH1C6wKAPWA%40mail.gmail.com.

Re: [weewx-user] module 'serial' has no attribute 'Serial'

[Tom Keffer]

I've seen this error before. Did you by any chance do a pip install of
"serial", instead of "pyserial"? The former is for serializing JSON, the
latter for communicating with serial ports.

On Sun, Apr 28, 2024 at 12:28 PM Adam Ellsworth  wrote:

> Hello, I've been running weewx smoothly for years, recently there was a
> power outage and when it came back up, weewx won't start.
>
> I assume something got updated and broke.. something? In an attempt to fix
> it I installed the latest weewx 5.0.1... It's using python 3.8.10 says the
> log. I re-ran station reconfigure to see if the driver was obsolete.
>
> Any ideas? Log below. Thank you for any suggestions! Usually I'm better at
> Google than this, but I'm also pretty unfamiliar with python.
>
> Apr 28 10:51:35 homebox weewxd[326279]: INFO weewx.engine: Loading station
> type Vantage (weewx.drivers.vantage)
> Apr 28 10:51:36 homebox weewxd[326279]: ERROR weewx.engine: Import of
> driver failed: module 'serial' has no attribute 'Serial' ( 'AttributeError'>)
> Apr 28 10:51:36 homebox weewxd[326279]: CRITICAL weewx.engine: 
>  Traceback (most recent call last):
> Apr 28 10:51:36 homebox weewxd[326279]: CRITICAL weewx.engine: 
>  File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
> Apr 28 10:51:36 homebox weewxd[326279]: CRITICAL weewx.engine: 
>self.console = loader_function(config_dict, self)
> Apr 28 10:51:36 homebox weewxd[326279]: CRITICAL weewx.engine: 
>  File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
> Apr 28 10:51:36 homebox weewxd[326279]: CRITICAL weewx.engine: 
>return VantageService(engine, config_dict)
> Apr 28 10:51:36 homebox weewxd[326279]: CRITICAL weewx.engine: 
>  File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in __init__
> Apr 28 10:51:36 homebox weewxd[326279]: CRITICAL weewx.engine: 
>Vantage.__init__(self, **config_dict[DRIVER_NAME])
> Apr 28 10:51:36 homebox weewxd[326279]: CRITICAL weewx.engine: 
>  File "/usr/share/weewx/weewx/drivers/vantage.py", line 536, in __init__
> Apr 28 10:51:36 homebox weewxd[326279]: CRITICAL weewx.engine: 
>self.port.openPort()
> Apr 28 10:51:36 homebox weewxd[326279]: CRITICAL weewx.engine: 
>  File "/usr/share/weewx/weewx/drivers/vantage.py", line 319, in openPort
> Apr 28 10:51:36 homebox weewxd[326279]: CRITICAL weewx.engine: 
>self.serial_port = serial.Serial(self.port, self.baudrate,
> timeout=self.timeout)
> Apr 28 10:51:36 homebox weewxd[326279]: CRITICAL weewx.engine: 
>  AttributeError: module 'serial' has no attribute 'Serial'
> Apr 28 10:51:36 homebox weewxd[326279]: CRITICAL __main__: Unable to load
> driver: module 'serial' has no attribute 'Serial'
> Apr 28 10:51:36 homebox weewxd[326279]: 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/06f878e5-0950-4b34-9ce9-1573ab380c64n%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/CAPq0zEAuW46XN-K4m6QfkA3DaCi85T7fODqw7Bfe_2G%3DjrDDqw%40mail.gmail.com.

Re: [weewx-user] Problem switching from weewx 4.x -> 5.X

[Tom Keffer]

With a pip install, any user modules are normally located in
~/weewx-data/bin/user.

You didn't post a copy of the log, but I suspect somewhere in your
configuration file weewx.conf you have a reference to an extension as
"bin.user.something" instead of "user.something". Take a look.

If you can't find it, use the tool weectl debug
 to post a copy of
your configuration file. Be sure to also set debug=1, restart, then post a
copy of the log. It will have important startup clues.


On Thu, Apr 25, 2024 at 8:30 AM Remy Lavabre  wrote:

> Good morning,
>
> My configuration under weewx 4.10.2 works perfectly with a custom driver.
>
> I'm "desperately" trying to upgrade to weewx 5 under virtual environment.
>
> -> Configuration with the basic driver simulating the data works ok.
> -> When I try with my driver, I get the following response:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *(weewx-venv) ---@server:~/weewx-data $ weewxdTraceback (most recent call
> last):  File "/home//weewx-venv/bin/weewxd", line 8, in 
> sys.exit(main()) ^^  File
> "/home//weewx-venv/lib/python3.11/site-packages/weewxd.py", line 160,
> in mainengine = weewx.engine.StdEngine(config_dict)
>  ^^^  File
> "/home//weewx-venv/lib/python3.11/site-packages/weewx/engine.py", line
> 89, in __init__self.loadServices(config_dict)  File
> "/home//weewx-venv/lib/python3.11/site-packages/weewx/engine.py", line
> 157, in loadServicesobj = weeutil.weeutil.get_object(svc)(self,
> config_dict)  ^^^  File
> "/home//weewx-venv/lib/python3.11/site-packages/weeutil/weeutil.py",
> line 1404, in get_objectmodule = importlib.import_module(module_name)
>  File
> "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>    File " importlib._bootstrap>", line 1206, in _gcd_import  File " importlib._bootstrap>", line 1178, in _find_and_load  File " importlib._bootstrap>", line 1128, in _find_and_load_unlocked  File
> "", line 241, in _call_with_frames_removed
> File "", line 1206, in _gcd_import  File
> "", line 1178, in _find_and_load  File
> "", line 1128, in _find_and_load_unlocked
> File "", line 241, in
> _call_with_frames_removed  File "", line 1206,
> in _gcd_import  File "", line 1178, in
> _find_and_load  File "", line 1142, in
> _find_and_load_unlockedModuleNotFoundError: No module named 'bin'*
>
> What is the problem ??
>
> --
> 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/909b9a5c-952a-4846-9910-458aaec91616n%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/CAPq0zEAhbUmyp3i0NMWfJ_SUyugOpNT6N83Zp%3D-8U-hYCpna9w%40mail.gmail.com.

Re: [weewx-user] weewx no longer starts after restart, reinstallation stops

[Tom Keffer]

What happens when you try to start weewx? Post the log, please.

On Tue, Apr 23, 2024 at 7:54 AM J. H.  wrote:

> Exactly, the log shows nothing and the installation hangs or the start
> does not work.
>
> Tom Keffer schrieb am Dienstag, 23. April 2024 um 16:35:26 UTC+2:
>
>> I am not sure what we're looking at here. Did the installation hang, and
>> not proceed, at this point?
>>
>> What is in the log?
>>
>> On Tue, Apr 23, 2024 at 2:00 AM J. H.  wrote:
>>
>>> Linux s2 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64
>>> GNU/Linux
>>>
>>>
>>>
>>> 1 nicht vollständig installiert oder entfernt.
>>> Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
>>> Möchten Sie fortfahren? [J/n] j
>>> weewx (5.0.2-1) wird eingerichtet ...
>>> Using weewx:weewx as user:group
>>> Saving old defaults to /etc/default/weewx-20240423105229
>>> Creating /etc/default/weewx
>>> Using configuration file /etc/weewx/weewx.conf
>>> Processing configuration file /etc/weewx/weewx.conf
>>> Saving configuration file /etc/weewx/weewx.conf
>>> User r7598 is already in group weewx
>>> Installing systemd units
>>> Installing udev rules
>>> Configuring database directory /var/lib/weewx
>>> Configuring reporting directory /var/www/html/weewx
>>> Setting permissions weewx:weewx on /etc/weewx
>>> Enabling startup using systemd
>>> Starting weewxd using systemd
>>>
>>> Fortschritt: [ 33%]
>>> [##...
>>>
>>> --
>>> 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/98dfefb0-a0e8-4d4c-92d0-ad4a727109cen%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/98dfefb0-a0e8-4d4c-92d0-ad4a727109cen%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/e97cf2ba-9e2d-47ee-ae97-b855af650673n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/e97cf2ba-9e2d-47ee-ae97-b855af650673n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEBtTcskd%2BJyLbgzhGuZr7JRLO%3Duapxo%3DftaJmLTYpJSCA%40mail.gmail.com.

Re: [weewx-user] weewx no longer starts after restart, reinstallation stops

[Tom Keffer]

I am not sure what we're looking at here. Did the installation hang, and
not proceed, at this point?

What is in the log?

On Tue, Apr 23, 2024 at 2:00 AM J. H.  wrote:

> Linux s2 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64
> GNU/Linux
>
>
>
> 1 nicht vollständig installiert oder entfernt.
> Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
> Möchten Sie fortfahren? [J/n] j
> weewx (5.0.2-1) wird eingerichtet ...
> Using weewx:weewx as user:group
> Saving old defaults to /etc/default/weewx-20240423105229
> Creating /etc/default/weewx
> Using configuration file /etc/weewx/weewx.conf
> Processing configuration file /etc/weewx/weewx.conf
> Saving configuration file /etc/weewx/weewx.conf
> User r7598 is already in group weewx
> Installing systemd units
> Installing udev rules
> Configuring database directory /var/lib/weewx
> Configuring reporting directory /var/www/html/weewx
> Setting permissions weewx:weewx on /etc/weewx
> Enabling startup using systemd
> Starting weewxd using systemd
>
> Fortschritt: [ 33%]
> [##...
>
> --
> 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/98dfefb0-a0e8-4d4c-92d0-ad4a727109cen%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/CAPq0zEDWNFiRpYrS_kwtBHGHS-Givp6XxxUNj9TbYVomrd075g%40mail.gmail.com.

Re: [weewx-user] Accessing Database From Service Extension

[Tom Keffer]

Take a look at the section *Programming interface
* in
the documentation and see if that answers your question.

On Sun, Apr 21, 2024 at 9:17 AM carter.hu...@gmail.com <
carter.humphrey...@gmail.com> wrote:

> I have PM 2.5 data being feed into WeeWx via a custom service extension.
> What I want to do is calculate the air quality index (AQI) based on the
> PM2.5 data. The EPA references the correct way of doing this as using the
> 24-hour average PM2.5.
>
> So my question is, is there a way for an extension to access the weewx
> database a pull the average value of a variable over the last 24 hours?
>
> --
> 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/03f80a01-a1ab-4ee7-9ae1-244312a74115n%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/CAPq0zEBEiF2KHNFBvzSmVWd_V%3DjmYbN7g4X4aNo%2Bm1kbJwtkqQ%40mail.gmail.com.

Re: [weewx-user] skin "unknown unknown"

[Tom Keffer]

That looks more like the "Seasons" skin, not the Standard skin.

The display under "About this station" is normally set by the values of
SKIN_NAME and SKIN_VERSION in the configuration file, skin.conf. They must
be missing from your copy. I don't quite understand how you ended up with
the display, but not the values, but somehow that's the way it turned out.

Either delete the display from about.inc, or add the values. To add the
values, go into Seasons/skin.conf and add them at the very top. Something
like

SKIN_NAME = Seasons
SKIN_VERSION = 5.0.2

-tk


On Sun, Apr 21, 2024 at 7:26 AM Christoph Reich 
wrote:

> I am using the Standard skin. In the section "about this station" the skin
> shows unknown unkown. I guess that should be filled automatically with the
> default naming of the skin (e.g. Standard). Howerver, I can not find how to
> fix.
>
> --
> 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/08b8b4e8-50b7-4bc1-bcc8-769b8b13190bn%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/CAPq0zEBbRvTUERqeLyWYnJFz37y30Jc1duk8DqLS6SipnLbixg%40mail.gmail.com.

Re: [weewx-user] Re: New weewx woes

[Tom Keffer]

You did not include very much of the log, so it's hard to say. But, given
that you're using a Vantage station, the odds are that the logger's memory
has become corrupted. Try the procedure under *Corrupt station memory
*
and
see if that helps.

If not, include the log from weewx startup through the first reporting
cycle and we'll take another look.

On Fri, Apr 19, 2024 at 8:23 PM n7uv...@gmail.com 
wrote:

> Also, seeing this occasionally with systemctl status weewx.service:
>
> Apr 19 20:21:20 rpi-weewx weewxd[1263]: DEBUG weewx.drivers.vantage:
> Retrieving 513 page(s); starting index= 1
> *Apr 19 20:21:21 rpi-weewx weewxd[1263]: DEBUG weewx.drivers.vantage:
> DMPAFT complete: page timestamp 2024-04-18 01:30:00 MST (1713429000) less
> than final timestamp 2024-04-19 19:35:00 MST (1713580500)*
> Apr 19 20:21:21 rpi-weewx weewxd[1263]: DEBUG weewx.drivers.vantage: Catch
> up complete.
>
> Perhaps I screwed up the database time?
>
> Cheers - Jon N7UV
> On Friday, April 19, 2024 at 8:19:24 PM UTC-7 n7uv...@gmail.com wrote:
>
>> Good evening all -
>>
>> I have finally gotten around to updating my 3-yo weewx station running on
>> RPi.
>> New build: RPi 4B, 64-bit Bookworm with desktop
>> Besides weewx and apache2 webserver, nothing else was installed.
>> Forgot to change local time in raspi-config, so the first hour or so was
>> running BST %^(
>> Changed to MST (Phoenix) about 1900 hours, seemed to reboot fine, and
>> updated the local apache and ftp'd to my webserver
>> jonadams.com/pages/weewx.
>>
>> At around 1935, it appears to have stopped updating either the local or
>> the distant webserver. Trying to resolve that now. Here's an output from
>> systemctl status:
>>
>> jta@rpi-weewx:/var/www/html/weewx $ systemctl status weewx.service
>> ● weewx.service - WeeWX
>>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; preset:
>> enabled)
>>  Active: active (running) since Fri 2024-04-19 19:47:58 MST; 15min ago
>>Docs: https://weewx.com/docs
>>Main PID: 1263 (python3)
>>   Tasks: 1 (limit: 3910)
>> CPU: 22.820s
>>  CGroup: /system.slice/weewx.service
>>  └─1263 python3 /usr/share/weewx/weewxd.py
>> /etc/weewx/weewx.conf
>>
>> Apr 19 20:02:23 rpi-weewx weewxd[1263]: ERROR weewx.drivers.vantage: LOOP
>> batch try #1; error: No  received from Vantage console
>> Apr 19 20:02:23 rpi-weewx weewxd[1263]: DEBUG weeutil.ftpupload: 0
>> ./index.html
>> 1ee0d0a57c964e821245a1ca3955fbb9bb40b71b88824331040a4dc4328c3823
>> Apr 19 20:02:23 rpi-weewx weewxd[1263]: DEBUG weeutil.ftpupload: Uploaded
>> file /var/www/html/weewx/index.html to /jonadams/pages/weewx/index.html
>> Apr 19 20:02:23 rpi-weewx weewxd[1263]: DEBUG weeutil.ftpupload: 1
>> ./telemetry.html
>> dc9834d1f7c371e384a3c894ffceacf58fe0cb89c097c81e668576c5b22adf68
>> Apr 19 20:02:24 rpi-weewx weewxd[1263]: DEBUG weeutil.ftpupload: Uploaded
>> file /var/www/html/weewx/telemetry.html to
>> /jonadams/pages/weewx/telemetry.html
>> Apr 19 20:02:24 rpi-weewx weewxd[1263]: INFO weewx.reportengine:
>> ftpgenerator: Ftp'd 2 files in 1.07 seconds
>> Apr 19 20:02:24 rpi-weewx weewxd[1263]: DEBUG weewx.reportengine: Report
>> 'RSYNC' not enabled. Skipping.
>> Apr 19 20:02:24 rpi-weewx weewxd[1263]: DEBUG weewx.drivers.vantage:
>> Successfully woke up Vantage console
>> Apr 19 20:03:14 rpi-weewx weewxd[1263]: DEBUG weewx.drivers.vantage:
>> Getting archive packets since 2024-04-19 19:35:00 MST (1713580500)
>> Apr 19 20:03:16 rpi-weewx weewxd[1263]: DEBUG weewx.drivers.vantage:
>> Successfully woke up Vantage console
>> jta@rpi-weewx:/var/www/html/weewx $
>>
>> I'm not sure what I did that caused it to stop updating the pages. And it
>> used to be sending 30-40 files to the remote webserver, but now only two,
>> index.html and telemetry.html. Both are stuck at 1935 hours MST.
>>
>> What am I doing wrong?
>>
>> Cheers - Jon N7UV
>>
> --
> 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/da495605-2572-4ee7-a027-65f1cebaddadn%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/CAPq0zED4nX%3DiqyrqA78kUYaTdUmfW%3DOr46NuKGb4cBk014ACBw%40mail.gmail.com.

Re: [weewx-user] Missing observations - wind & rain

[Tom Keffer]

You might have better luck contacting the author of the extension.

On Fri, Apr 19, 2024 at 4:59 AM John Walker  wrote:

> Hi - would anyone have suggestions on where I could further to try and
> solve the below problem? I can't find anything in documentation that
> relates to the "not a broadcast packet" error.
> Many thanks,
> JW
>
> On Sat, Apr 13, 2024 at 2:02 PM John Walker  wrote:
>
>> Hi, a few days ago I started to lose wind speed, wind direction and rain
>> data. Everything else is coming through ok and the charts are all updating
>> fine. But the wind and rain ones are blank after a certain point. Syslog
>> excerpt at bottom, I did find some rows indicating 'not a broadcast packet'
>> and 'not in record' applying to wind/rain.
>>
>> About the time I started to lose the data I was installing another server
>> application, not related to weewx. Weewx is the latest version (see below).
>> And I just updated the weatherlink driver today (and before the log file
>> excerpt below) - it was fairly recent anyway, think beginning Feb on last
>> update.
>>
>> Any pointers on how to solve this? Possibly an issue at the device head
>> (which is remote)?
>>
>> Thanks - JW
>>
>> weewx:
>>   Installed: 4.9.1-1
>>   Candidate: 4.9.1-1
>>   Version table:
>>  *** 4.9.1-1 100
>> 100 /var/lib/dpkg/status
>>
>> *SYSLOG (debug set to 1):*
>>
>> Apr 13 13:52:54 sparta weewx[96085] DEBUG
>> user.weatherlink_live.scheduler: 100 scheduler ticks until next push refresh
>> Apr 13 13:52:54 sparta weewx[96085] DEBUG
>> user.weatherlink_live.scheduler: Next scheduler tick at 2024-04-13 17:53:04
>> Z
>> Apr 13 13:52:55 sparta weewx[96085] WARNING user.weatherlink_live.driver:
>> No data since 1 iterations
>> Apr 13 13:52:55 sparta weewx[96085] DEBUG user.weatherlink_live.driver:
>> Waiting for new packet
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG
>> user.weatherlink_live.scheduler: Scheduler tick
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG
>> user.weatherlink_live.scheduler: Notifying poll callback
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG urllib3.connectionpool:
>> Starting new HTTP connection (1): 192.168.1.6:80
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG urllib3.connectionpool:
>> http://192.168.1.6:80 "GET /v1/current_conditions HTTP/1.1" 200 None
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.packets:
>> Trying to create HTTP conditions packet
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG
>> user.weatherlink_live.data_host: Polled current conditions
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> THMapping['1']: Mapped: outTemp=47.6
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> THMapping['1']: Mapped: outHumidity=69.3
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> THMapping['1']: Mapped: dewpoint=38.0
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> THMapping['1']: Mapped: heatindex=47.5
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> THMapping['1']: Mapped: wetbulb=42.3
>>
>>
>> *Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> RainMapping['1']: Mapping not responsible: Not a broadcast packetApr 13
>> 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> WindMapping['1']: Mapping not responsible: Not a broadcast packet*Apr 13
>> 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> WindChillMapping['1']: Mapped: windchill=47.0
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> ThwMapping['1', 'appTemp']: Mapped: thw=46.9
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> ThwMapping['1', 'appTemp']: Mapped: appTemp=46.9
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> THIndoorMapping: Mapped: inTemp=68.1
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> THIndoorMapping: Mapped: inHumidity=40.3
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> THIndoorMapping: Mapped: inDewpoint=43.1
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> THIndoorMapping: Mapped: inHeatindex=66.1
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> BaroMapping: Mapped: pressure=29.255
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> BaroMapping: Mapped: altimeter=29.549
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG user.weatherlink_live.mappers:
>> BatteryStatusMapping['1']: Mapped: batteryStatus1=0
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG
>> user.weatherlink_live.scheduler: 113 scheduler ticks until next push refresh
>> Apr 13 13:53:00 sparta weewx[96085] DEBUG
>> user.weatherlink_live.scheduler: Next scheduler tick at 2024-04-13 17:53:10
>> Z
>> Apr 13 13:53:00 sparta weewx[96085] INFO user.weatherlink_live.driver:
>> Emitting poll packet
>> *Apr 13 13:53:00 sparta 

Re: [weewx-user] Own Driver

[Tom Keffer]

I am not sure if I am understanding correctly, but yes, you absolutely need
the function genLoopPackets(). See the documentation on writing a driver
.

On Thu, Apr 18, 2024 at 9:06 AM michae...@gmail.com 
wrote:

> Hello, I have my own driver based on Filepraser. Now I keep getting the
> following error message. The function is not created. 1: Do you need them
> in the driver? 2: if yes: what should the task be?
>
> Apr 18 18:00:43 raspberrypi weewxd[16522]: Exception ignored in:
> 
> Apr 18 18:00:43 raspberrypi weewxd[16522]: Traceback (most recent call
> last):
> Apr 18 18:00:43 raspberrypi weewxd[16522]:   File
> "/usr/share/weewx/weewx/engine.py", line 210, in run
> Apr 18 18:00:43 raspberrypi weewxd[16522]:
> self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
> Apr 18 18:00:43 raspberrypi weewxd[16522]: RuntimeError: generator ignored
> GeneratorExit
>
> Best 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/fc354ad5-0543-4391-bd73-7dc6483a439dn%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/CAPq0zEBS6OHt1LgRX80HaXmSkxNE85u5bn%3De0ggqXg0UrgN%2B9Q%40mail.gmail.com.

Re: [weewx-user] Fileparse Installation

[Tom Keffer]

You're trying to install the documentation, not the actual code.

Try

*weectl extension install /etc/weewx/examples/fileparse*



On Mon, Apr 15, 2024 at 8:19 AM Craig Benson 
wrote:

> Hello -
>
> I'm building a weather station from scratch and I will need to use the
> fileparse driver to consume a data file.  However, when I run the command
> in the fileparse readme file [sudo weectl extension install
> /usr/share/doc/weewx/examples/fileparse], I get the error shown in the
> attachment.  Since the fileparse example is in the /etc directory, is there
> a newer script that will run the install?
>
> Thanks in advance for any help.
> Craig
>
>
>
> --
> 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/8edf5c4f-be21-4708-9f94-73a97d7267acn%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/CAPq0zEDsS--zAr%2BMrFhuG25FrJJXLuYaeWWPS_-KETePaJ%3D6Ag%40mail.gmail.com.

Re: [weewx-user] Problem with weewx after power failure

[Tom Keffer]

You're not giving us much information. At the very least, what kind of
weather station? Better yet, include the log. See the wiki article *Help!
Posting to weewx-user
* for how
to get a good log.

The wlan0 entries are probably red herrings.

-tk

On Fri, Apr 12, 2024 at 5:38 PM Monica Mulholland 
wrote:

> My Rpi with weewx has been running very successfully for many
> years.until we had a power failure recently. I can still get into my
> Rpi from my desktop and see that it is runningbut nothing is been
> updating on my website. It is still stuck at the time the power came back
> on. I suppose it could be the battery on the external weather station but
> that was changed recently and it the signal strength on the last webpage is
> not showing any problem. When I look at the log, I get a stream of these.
>
> Apr 13 12:25:28 WeatherPi dhcpcd[349]: wlan0: Router Advertisement from
> fe80::724f:57ff:feb7:82a1
> Apr 13 12:25:28 WeatherPi dhcpcd[349]: wlan0: soliciting a DHCPv6 lease
>
> Can somebody who knows more about these things than me, please tell me
> what is going on and how I can sort this out,
>
> Thanks in anticipation.
>
> --
> 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/e75c2ddf-368e-4e45-b0c9-e238058eeb4cn%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/CAPq0zEAobmP7beSg4Nw4i%2BqM%2B9pui1SV9_25Zu8xChwjs-XwKg%40mail.gmail.com.

Re: [weewx-user] Launching Weewx

[Tom Keffer]

Yes, you can leave it on. It will mean a lot of log entries, but storage is
cheap these days.



On Fri, Apr 12, 2024 at 6:43 AM DR  wrote:

> Tom,
>
> THE most often made comment from the developers is to turn on debug and
> then furnish the log.
>
> Question:  Is there a down side to just leaving debug on? Doesn't the
> buffer for it just overwrite, and not cause the program to stop once it
> is full?  I know that the SD cards don't seem to have the problem with
> exceeding their write cycles, so saving the writes to the card doesn't
> seem to be as much of a factor.  And I don't gather that a performance
> hit of doing all that logging is much of a factor.
>
>
> I'm for neat, efficient, focused code, but until an installation has run
> perfectly for a few weeks, can we just leave Debug on for awhile?  Just
> curious.
>
> 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/14e96a89-da15-41de-9414-86e27b5c6119%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/CAPq0zECORYCDTMYp%3D9d0TvZ%2BLycV%2Be7Pv9c3EChv-YDt_TM-6g%40mail.gmail.com.

Re: [weewx-user] Launching Weewx

[Tom Keffer]

Impossible to say without seeing the log. To get a good log, see the wiki
article Help! Posting to weewx-user
.

On Fri, Apr 12, 2024 at 1:08 AM Marie-Laure TERRIENNE <
rouillard4...@gmail.com> wrote:

> Hello everybody,
>
> I have installed WeeWX 5.0.2 on my PC running under Ubuntu 22.04.4 LTS 64
> bits.
>
> My weather station belongs to the recognized stations : Fine offset WH1081.
>
> I can't launch weewx correctly. What I'm doing :
>
>
>1. I open the "file browser" and looking for
>/var/www/html/weewx/index.html (the icon has a small padlock) and I
>click on this file : the web browser opens and tells me : File not found
>Firefox cannot find the file at /var/www/html/weewx/index.html.
>2. I open the web browser (Firefox) and with the "Open a file" menu,
>I'm looking for var/www/html/weewx/index.html and I click on this
>name. This time a window opens and shows a text file with data from my
>weather station. But I don't have a graphical presentation. In addition, if
>I click on one of the available links (for example: statistics), I come
>across the message : File not found Firefox cannot find the file at
>/var/www/html/weewx/statistics.html.
>
>
> So, is there something wrong or what to do to correctly launch weewx ?
>
> Sincerely your.
>
> Pierre.
>
>
>
> --
> 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/5e31005d-77dc-48a0-a40e-54e256798ab5n%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/CAPq0zEAwLzsUZLVmCBa%2BLSpWpMb%3DMJZJwGqz%3D-qJnS9WNjqAfA%40mail.gmail.com.

Re: [weewx-user] Updates from Davis Envoy have stopped

[Tom Keffer]

Judging from your log file, you used the package installer on Debian.

On Thu, Apr 11, 2024 at 8:16 PM Peter Tuft  wrote:

> Fixed!!  Thanks so much.  I'm delighted.
>
> This exercise has prompted one other query:  despite my "ain't broke,
> don't fix it" approach perhaps it's time I updated to a more recent version
> of WeeWX.  The upgrade page cautions strongly that I should use the same
> method as the original installation, but that was over 3 years ago and I
> don't remember.  Is there a way of identifying the original install method?
>
> Thanks again,
> Peter T.
>
>
> On Friday, April 12, 2024 at 11:05:18 AM UTC+10 Tom Keffer wrote:
>
>> You can accomplish the same thing by using the old v4 utilities
>> <https://www.weewx.com/docs/4.10/hardware.htm#vantage_notes>.
>>
>> wee_device --dump
>> wee_device --clear-memory
>>
>> On Thu, Apr 11, 2024 at 6:01 PM Peter Tuft  wrote:
>>
>>> Tom,
>>>
>>> Many thanks - I've done as you suggested, log attached.  It does show
>>> discrepancies in the times.  I tried the  weectl device commands to
>>> dump and clear the memory but my Pi says "command not found".  Where do I
>>> find that?
>>>
>>> Because I believe in "ain't broke, don't fix it" I'm running old
>>> software - Weewx 4.5.1 under Raspbian 10.  But maybe it's "broke" - do I
>>> need to update to access weectl device?
>>>
>>> Thanks,
>>> Peter T.
>>>
>>> On Friday, April 12, 2024 at 1:35:19 AM UTC+10 Tom Keffer wrote:
>>>
>>>> Odds are it's a problem with corrupted memory
>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory>,
>>>> but this time, just to be sure, could you set debug=1, restart, then post
>>>> the log through the first reporting cycle.
>>>>
>>>>
>>>>
>>>> On Thu, Apr 11, 2024 at 6:41 AM Peter Tuft  wrote:
>>>>
>>>>> A couple of days ago I disconnected/reconnected the USB power and
>>>>> serial data cables between my Raspberry Pi and Davis Envoy.  Since then
>>>>> weewx seems to have stopped receiving updates from the Envoy - it just
>>>>> reports old data.  I've tested the connection using minicom as described
>>>>> here:
>>>>> https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station.
>>>>> That seemed to work OK.  That page also suggested powering down the Envoy
>>>>> for a few minutes then restarting which didn't help either.
>>>>>
>>>>> So I'm at a loss.  Attached is a log of events since my most recent
>>>>> restart of weewx.  The system updates every 10 minutes and you can see two
>>>>> cycles of that at the end of the log.  That same pattern continues
>>>>> indefinitely, but the FTP upload is always of the same old data from a
>>>>> couple of days ago.
>>>>>
>>>>> I'll be most grateful for any advice.
>>>>>
>>>>> Thanks,
>>>>> Peter T.
>>>>>
>>>>> --
>>>>> 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/091560c7-e85f-46d0-b8eb-6e9201d7ab5bn%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/weewx-user/091560c7-e85f-46d0-b8eb-6e9201d7ab5bn%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>> --
>>> 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/4b24d477-3e5b-496b-95b8-5b29360678e2n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/4b24d477-3e5b-496b-95b8-5b29360678e2n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/ee3af9b5-88c4-4065-b5e2-89b124478e2an%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/ee3af9b5-88c4-4065-b5e2-89b124478e2an%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zECYiX-WGnCu_DOO4mcysmD2CE6u0pFQ3Sb7fgtL1Zp%3DKw%40mail.gmail.com.

Re: [weewx-user] Updates from Davis Envoy have stopped

[Tom Keffer]

You can accomplish the same thing by using the old v4 utilities
<https://www.weewx.com/docs/4.10/hardware.htm#vantage_notes>.

wee_device --dump
wee_device --clear-memory

On Thu, Apr 11, 2024 at 6:01 PM Peter Tuft  wrote:

> Tom,
>
> Many thanks - I've done as you suggested, log attached.  It does show
> discrepancies in the times.  I tried the  weectl device commands to dump
> and clear the memory but my Pi says "command not found".  Where do I find
> that?
>
> Because I believe in "ain't broke, don't fix it" I'm running old software
> - Weewx 4.5.1 under Raspbian 10.  But maybe it's "broke" - do I need to
> update to access weectl device?
>
> Thanks,
> Peter T.
>
> On Friday, April 12, 2024 at 1:35:19 AM UTC+10 Tom Keffer wrote:
>
>> Odds are it's a problem with corrupted memory
>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory>,
>> but this time, just to be sure, could you set debug=1, restart, then post
>> the log through the first reporting cycle.
>>
>>
>>
>> On Thu, Apr 11, 2024 at 6:41 AM Peter Tuft  wrote:
>>
>>> A couple of days ago I disconnected/reconnected the USB power and serial
>>> data cables between my Raspberry Pi and Davis Envoy.  Since then weewx
>>> seems to have stopped receiving updates from the Envoy - it just reports
>>> old data.  I've tested the connection using minicom as described here:
>>> https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station.
>>> That seemed to work OK.  That page also suggested powering down the Envoy
>>> for a few minutes then restarting which didn't help either.
>>>
>>> So I'm at a loss.  Attached is a log of events since my most recent
>>> restart of weewx.  The system updates every 10 minutes and you can see two
>>> cycles of that at the end of the log.  That same pattern continues
>>> indefinitely, but the FTP upload is always of the same old data from a
>>> couple of days ago.
>>>
>>> I'll be most grateful for any advice.
>>>
>>> Thanks,
>>> Peter T.
>>>
>>> --
>>> 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/091560c7-e85f-46d0-b8eb-6e9201d7ab5bn%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/091560c7-e85f-46d0-b8eb-6e9201d7ab5bn%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/4b24d477-3e5b-496b-95b8-5b29360678e2n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/4b24d477-3e5b-496b-95b8-5b29360678e2n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEDLGxr%2B4vX29%2B_5BuDX-PRyijFhqXnXEiJM60BoMjcztQ%40mail.gmail.com.

Re: [weewx-user] change locale for html.tmpl with weewx 5.0.2

[Tom Keffer]

I'm not sure whether it would work, but you could try not localizing the
results. For example,

*$monthoutTemp.max.format(localize=False)*

See if that works.




On Thu, Apr 11, 2024 at 10:37 AM Juan Antonio Mosquera Casais <
juan.antonio.mosquera.cas...@gmail.com> wrote:

> I read doc but i dont know this>
>
> I use Belchertown skin, and in skin.conf i generate a
> meteoclimatic.html.tmpl >
>
> *UPD=$current.dateTime.format("%d-%m-%Y %H:%M")
> *TMP=$current.outTemp.formatted
> *WND=$current.windSpeed.formatted
> *AZI=$current.windDir.formatted
> *BAR=$current.barometer.formatted
> *HUM=$current.outHumidity.formatted
> *SUN=$current.radiation.formatted
> *UVI=$current.UV.formatted
> *DHTM=$day.outTemp.max.formatted
> *DLTM=$day.outTemp.min.formatted
> *DHHM=$day.outHumidity.max.formatted
> *DLHM=$day.outHumidity.min.formatted
> *DHBR=$day.barometer.max.formatted
> *DLBR=$day.barometer.min.formatted
> *DGST=$day.windGust.max.formatted
> *DSUN=$day.radiation.max.formatted
> *DHUV=$day.UV.max.formatted
> *DPCP=$day.rain.sum.formatted
> *WRUN=
> *MHTM=$month.outTemp.max.formatted
> *MLTM=$month.outTemp.min.formatted
> *MHHM=$month.outHumidity.max.formatted
> *MLHM=$month.outHumidity.min.formatted
> *MHBR=$month.barometer.max.formatted
> *MLBR=$month.barometer.min.formatted
> *MGST=$month.windGust.max.formatted
> *MSUN=$month.radiation.max.formatted
> *MHUV=$month.UV.max.formatted
> *MPCP=$month.rain.sum.formatted
> *YHTM=$year.outTemp.max.formatted
> *YLTM=$year.outTemp.min.formatted
> *YHHM=$year.outHumidity.max.formatted
> *YLHM=$year.outHumidity.min.formatted
> *YHBR=$year.barometer.max.formatted
> *YLBR=$year.barometer.min.formatted
> *YGST=$year.windGust.max.formatted
> *YSUN=$year.radiation.max.formatted
> *YHUV=$year.UV.max.formatted
> *YPCP=$year.rain.sum.formatted
> *EOT*
>
> My locale is es_ES but, this meteoclimatic.html.tmpl i want en_US, is
> posible?
>
> --
> 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/7c828d07-e48f-42e2-a34e-9c21636d3051n%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/CAPq0zECdN2mp%3Df1sqa53Rz1JThrUsYRTC2OgWyBSOi0vk15c%3DA%40mail.gmail.com.

Re: [weewx-user] Updates from Davis Envoy have stopped

[Tom Keffer]

Odds are it's a problem with corrupted memory
,
but this time, just to be sure, could you set debug=1, restart, then post
the log through the first reporting cycle.



On Thu, Apr 11, 2024 at 6:41 AM Peter Tuft  wrote:

> A couple of days ago I disconnected/reconnected the USB power and serial
> data cables between my Raspberry Pi and Davis Envoy.  Since then weewx
> seems to have stopped receiving updates from the Envoy - it just reports
> old data.  I've tested the connection using minicom as described here:
> https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station.
> That seemed to work OK.  That page also suggested powering down the Envoy
> for a few minutes then restarting which didn't help either.
>
> So I'm at a loss.  Attached is a log of events since my most recent
> restart of weewx.  The system updates every 10 minutes and you can see two
> cycles of that at the end of the log.  That same pattern continues
> indefinitely, but the FTP upload is always of the same old data from a
> couple of days ago.
>
> I'll be most grateful for any advice.
>
> Thanks,
> Peter T.
>
> --
> 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/091560c7-e85f-46d0-b8eb-6e9201d7ab5bn%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/CAPq0zEDqm6tGNjtEDRZ6JS%3DdaG9%3DxbJiNdry9zkXUbnfWQQ64g%40mail.gmail.com.

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

[Tom Keffer]

I suspect this may be a permissions issue. What do you get for the
following commands?

*ls -l /home/weewx*
*ls -l /home/weewx/examples*


Make sure everything in the directory "/home/weewx" is writable by user
"pi". Usually, it's easiest just to have everything under /home/weewx owned
by user "pi":

*sudo chown -R pi:pi /home/weewx*



On Wed, Apr 10, 2024 at 9:49 PM Juan Antonio Mosquera Casais <
juan.antonio.mosquera.cas...@gmail.com> wrote:

> Ok, thanks, sorry, this step i reply N, if i reply Y>
>
> pi@raspberrypi:/home/weewx $  source ~/weewx-venv/bin/activate
> (weewx-venv) pi@raspberrypi:/home/weewx $  weectl station upgrade
> --config=/home/weewx/weewx.conf
> Using configuration file /home/weewx/weewx.conf
>
> Upgrade examples, utility files in /home/weewx (Y/n)?
> Removing example directory /home/weewx/examples
> Copying examples into /home/weewx/examples
> Traceback (most recent call last):
>   File "/home/pi/weewx-venv/bin/weectl", line 8, in 
> sys.exit(main())
>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weectl.py", line
> 66, in main
> namespace.func(namespace)
>   File
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/__init__.py",
> line 121, in dispatch
> namespace.action_func(config_dict, namespace)
>   File
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_cmd.py",
> line 333, in upgrade_station
> weectllib.station_actions.station_upgrade(config_dict=config_dict,
>   File
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py",
> line 802, in station_upgrade
> examples_dir = copy_examples(config_dict, examples_root=examples_root,
>   File
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py",
> line 618, in copy_examples
> shutil.copytree(examples_resources, examples_dir)
>   File "/usr/lib/python3.9/shutil.py", line 557, in copytree
> return _copytree(entries=entries, src=src, dst=dst, symlinks=symlinks,
>   File "/usr/lib/python3.9/shutil.py", line 458, in _copytree
> os.makedirs(dst, exist_ok=dirs_exist_ok)
>   File "/usr/lib/python3.9/os.py", line 225, in makedirs
> mkdir(name, mode)
> FileExistsError: [Errno 17] File exists: '/home/weewx/examples'
>
> Thanks.
>
> El jueves, 11 de abril de 2024 a las 0:12:37 UTC+2, Tom Keffer escribió:
>
>> Juan, your service file, weewx.service, looks like the old V4.10 service
>> file. The new V5.0 file has a few more entries.
>>
>> Double check that you did step #2: upgrade the old examples and utility
>> files.
>>
>> On Wed, Apr 10, 2024 at 12:27 PM Juan Antonio Mosquera Casais <
>> juan.antonio.m...@gmail.com> wrote:
>>
>>> pi@raspberrypi:/etc $ cat /etc/systemd/system/weewx.service
>>> # systemd unit configuration file for WeeWX
>>> #
>>> # For information about running WeeWX under systemd,
>>> # be sure to read https://github.com/weewx/weewx/wiki/systemd
>>> #
>>> [Unit]
>>> Description=WeeWX weather system
>>> Documentation=https://weewx.com/docs
>>>
>>> Requires=time-sync.target
>>> After=time-sync.target
>>> RequiresMountsFor=/home
>>>
>>> [Service]
>>> ExecStart=/home/weewx/bin/weewxd /home/weewx/weewx.conf
>>> StandardOutput=null
>>> # To run as a non-root user, uncomment and set username and group here:
>>> #User=weewx
>>> #Group=weewx
>>>
>>> [Install]
>>> WantedBy=multi-user.target
>>>
>>>
>>> El miércoles, 10 de abril de 2024 a las 19:46:01 UTC+2, vince escribió:
>>>
>>>> Check to see if you have multiple weewx.service files on your system.
>>>> It's possible you have one under /etc and a different one under /usr and
>>>> systemd is using the old one.
>>>>
>>>> If that is not the case, post your /etc/systemd/system/weewx.service
>>>> file please.
>>>>
>>>> On Wednesday, April 10, 2024 at 10:42:39 AM UTC-7 Juan Antonio Mosquera
>>>> Casais wrote:
>>>>
>>>>> Thanks... but... step 4 done>
>>>>>
>>>>> history
>>>>>
>>>>>  1323  sudo cp /home/weewx/util/systemd/weewx.service
>>>>> /etc/systemd/system
>>>>>  1324  sudo systemctl daemon-reload
>>>>>  1325  sudo systemctl enable weewx
>>>>>  1326  sudo systemctl start weewx
>>>>>
>>>>>
>>>>>
>>

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

[Tom Keffer]

Juan, your service file, weewx.service, looks like the old V4.10 service
file. The new V5.0 file has a few more entries.

Double check that you did step #2: upgrade the old examples and utility
files.

On Wed, Apr 10, 2024 at 12:27 PM Juan Antonio Mosquera Casais <
juan.antonio.mosquera.cas...@gmail.com> wrote:

> pi@raspberrypi:/etc $ cat /etc/systemd/system/weewx.service
> # systemd unit configuration file for WeeWX
> #
> # For information about running WeeWX under systemd,
> # be sure to read https://github.com/weewx/weewx/wiki/systemd
> #
> [Unit]
> Description=WeeWX weather system
> Documentation=https://weewx.com/docs
>
> Requires=time-sync.target
> After=time-sync.target
> RequiresMountsFor=/home
>
> [Service]
> ExecStart=/home/weewx/bin/weewxd /home/weewx/weewx.conf
> StandardOutput=null
> # To run as a non-root user, uncomment and set username and group here:
> #User=weewx
> #Group=weewx
>
> [Install]
> WantedBy=multi-user.target
>
>
> El miércoles, 10 de abril de 2024 a las 19:46:01 UTC+2, vince escribió:
>
>> Check to see if you have multiple weewx.service files on your system.
>> It's possible you have one under /etc and a different one under /usr and
>> systemd is using the old one.
>>
>> If that is not the case, post your /etc/systemd/system/weewx.service file
>> please.
>>
>> On Wednesday, April 10, 2024 at 10:42:39 AM UTC-7 Juan Antonio Mosquera
>> Casais wrote:
>>
>>> Thanks... but... step 4 done>
>>>
>>> history
>>>
>>>  1323  sudo cp /home/weewx/util/systemd/weewx.service /etc/systemd/system
>>>  1324  sudo systemctl daemon-reload
>>>  1325  sudo systemctl enable weewx
>>>  1326  sudo systemctl start weewx
>>>
>>>
>>>
>>>
>>>
>>> El miércoles, 10 de abril de 2024 a las 13:16:55 UTC+2, Tom Keffer
>>> escribió:
>>>
>>>> You did not update your weewx service file,
>>>> /etc/systemd/system/weewx.service. This is step #4 in the instructions.
>>>>
>>>>
>>>>
>>>> On Wed, Apr 10, 2024 at 1:05 AM Juan Antonio Mosquera Casais <
>>>> juan.antonio.m...@gmail.com> wrote:
>>>>
>>>>> Hello, I have weewx 4.10.2 installed via setup.py, and I followed the
>>>>> instructions at https://github.com/weewx/weewx/wiki/v5-upgrade but
>>>>> when trying to start the service I get this error:
>>>>>
>>>>> Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed to
>>>>> locate executable /home/weewx/bin/weewxd: No such file or directory
>>>>> Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed at
>>>>> step EXEC spawning /home/weewx/bin/weewxd: No such file or directory
>>>>> Apr 10 07:39:51 raspberrypi systemd[1]: Started WeeWX weather system.
>>>>> Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Main process
>>>>> exited, code=exited, status=203/EXEC
>>>>> Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Failed with
>>>>> result 'exit-code'.
>>>>>
>>>>> It is because in the instructions the bin has to be moved to bin.old,
>>>>> if I put the bin back it works, but with version 4.10.2. How can I update
>>>>> to version 5.0.2 and keep my old configuration? 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+...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/weewx-user/689f6dd3-1de9-4d6b-90b2-1c7fc0b36fc7n%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/weewx-user/689f6dd3-1de9-4d6b-90b2-1c7fc0b36fc7n%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>> --
> 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/ccdd2474-9966-482c-9fde-41f66891841en%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/ccdd2474-9966-482c-9fde-41f66891841en%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEDkqoEmWG6_CvNHgyXSqhs%2BpeDiOcet7C9Sma%2B4wS_AZA%40mail.gmail.com.

Re: [weewx-user] Failed to update 4.10.2 to 5.0.2 with setup.py old installation

[Tom Keffer]

You did not update your weewx service file,
/etc/systemd/system/weewx.service. This is step #4 in the instructions.



On Wed, Apr 10, 2024 at 1:05 AM Juan Antonio Mosquera Casais <
juan.antonio.mosquera.cas...@gmail.com> wrote:

> Hello, I have weewx 4.10.2 installed via setup.py, and I followed the
> instructions at https://github.com/weewx/weewx/wiki/v5-upgrade but when
> trying to start the service I get this error:
>
> Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed to locate
> executable /home/weewx/bin/weewxd: No such file or directory
> Apr 10 07:39:51 raspberrypi systemd[1225]: weewx.service: Failed at step
> EXEC spawning /home/weewx/bin/weewxd: No such file or directory
> Apr 10 07:39:51 raspberrypi systemd[1]: Started WeeWX weather system.
> Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Main process
> exited, code=exited, status=203/EXEC
> Apr 10 07:39:51 raspberrypi systemd[1]: weewx.service: Failed with result
> 'exit-code'.
>
> It is because in the instructions the bin has to be moved to bin.old, if I
> put the bin back it works, but with version 4.10.2. How can I update to
> version 5.0.2 and keep my old configuration? 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/689f6dd3-1de9-4d6b-90b2-1c7fc0b36fc7n%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/CAPq0zECT_fZ5fY6YapuJQAcuEcCFP%3DVmF2%2B%2BH3TixTCEdDcBEQ%40mail.gmail.com.

Re: [weewx-user] Re: Unexpected weewx stop: ERROR weewx.engine: Import of driver failed

[Tom Keffer]

Done.

Some of the issues are packaging issues, so we'd best wait.

On Tue, Apr 9, 2024 at 5:07 PM vince  wrote:

> Cool - thanks.   Would it be possible to add the log.info() to always log
> its settings ?  That might make some more "did you set this true" support
> threads a little quicker.
>
> Also given Matthew is kinda out of pocket for personal/work reasons, would
> it be possible to get a 5.0.next out there for pip users ?  Or does the
> to-do list include code as well as packaging things ?
>
> On Tuesday, April 9, 2024 at 4:58:52 PM UTC-7 Tom Keffer wrote:
>
>> Yes, there was a bug, but it was fixed by Gary back in February. PR #935
>> <https://github.com/weewx/weewx/pull/935>. To appear whenever we get a
>> new version out.
>>
>> -tk
>>
>>
>> On Tue, Apr 9, 2024 at 4:22 PM vince  wrote:
>>
>>> I was thinking systemd would be a more general purpose way, but maybe
>>> that's just frustration here with loop_on_init not working.
>>>
>>> In poking around more I think there's a bug in weewxd.py - I can't find
>>> an incantation that actually sets loop_on_init to what's set in the .conf
>>> file.  I added some log.info around the statements in weewxd.py and it
>>> always gets set False no matter what I do.
>>>
>>> This patch works though...
>>>
>>> #-
>>> ###
>>> #### If no command line --loop-on-init was specified, look in the
>>> config file.
>>> ###if namespace.loop_on_init is None:
>>> ###loop_on_init = to_bool(config_dict.get('loop_on_init', False))
>>> ###else:
>>> ###loop_on_init = namespace.loop_on_init
>>> ###
>>> #-
>>>
>>> # If command line --loop-on-init was specified use that
>>> if namespace.loop_on_init is True:
>>> loop_on_init = namespace.loop_on_init
>>> else:
>>> # look in the config file, failing safe to False
>>>  loop_on_init = to_bool(config_dict.get('loop_on_init', False))
>>>
>>> # always log its setting
>>> log.info("loop_on_init: %s", loop_on_init)
>>>
>>> #-
>>>
>>>
>>> On Tuesday, April 9, 2024 at 2:55:32 PM UTC-7 gjr80 wrote:
>>>
>>>> The more I think of it the more I don't see the benefit of this
>>>> approach over using loop_on_init in weewx.conf in dealing with this
>>>> type of problem. Setting loop_on_init = True will cause WeeWX to
>>>> reload the driver after (the default) three consecutive attempts to contact
>>>> the gateway device fail; WeeWX continues running the entire time. Perhaps
>>>> if some sort of network or device initialisation sat in the WeeWX core
>>>> there might be a benefit, but all of that sits solely in the driver (as far
>>>> as I am aware this is the case with all drivers). If the network or the
>>>> device is in such a state that communication with the device via the API is
>>>> not possible then no amount of WeeWX restarts or driver reloads will
>>>> correct the situation.
>>>>
>>>> It seems to me that forcing a WeeWX restart via systemd is a somewhat
>>>> heavy handed approach.
>>>>
>>>> My opinion only and I expect others will have a different view.
>>>>
>>>> Gary
>>>>
>>>> On Wednesday 10 April 2024 at 06:00:37 UTC+10 vince wrote:
>>>>
>>>>> update - my ecowitt instance crashed out on me during a several minute
>>>>> network outage while I was updating firmware on the router/switch/ap so 
>>>>> I'm
>>>>> trying this solution to see how well that works.  Thanks.
>>>>>
>>>>> (not a bug in the gw1000 driver - it did exactly what it's configured
>>>>> to do.  It tried 3x with 2 sec in between.  An alternate workaround would
>>>>> be to try 1000x with a minute in between to basically get through any
>>>>> reasonable network outages for the LAN, but I want to try the systemd
>>>>> method as a more generic fix)
>>>>>
>>>>> On Tuesday, March 26, 2024 at 7:56:12 AM UTC-7 gary@gmail.com
>>>>> wrote:
>>>>>
>>>>>> I have added these lines to my weewx service file for just such an
>>>>>> instance.
>>>>>> Add under StandardError=journal+console entry in the [Service] stanza
>>>>>>
>>>>>> 

Re: [weewx-user] Re: Unexpected weewx stop: ERROR weewx.engine: Import of driver failed

[Tom Keffer]

Yes, there was a bug, but it was fixed by Gary back in February. PR #935
. To appear whenever we get a new
version out.

-tk


On Tue, Apr 9, 2024 at 4:22 PM vince  wrote:

> I was thinking systemd would be a more general purpose way, but maybe
> that's just frustration here with loop_on_init not working.
>
> In poking around more I think there's a bug in weewxd.py - I can't find an
> incantation that actually sets loop_on_init to what's set in the .conf
> file.  I added some log.info around the statements in weewxd.py and it
> always gets set False no matter what I do.
>
> This patch works though...
>
> #-
> ###
> #### If no command line --loop-on-init was specified, look in the
> config file.
> ###if namespace.loop_on_init is None:
> ###loop_on_init = to_bool(config_dict.get('loop_on_init', False))
> ###else:
> ###loop_on_init = namespace.loop_on_init
> ###
> #-
>
> # If command line --loop-on-init was specified use that
> if namespace.loop_on_init is True:
> loop_on_init = namespace.loop_on_init
> else:
> # look in the config file, failing safe to False
>  loop_on_init = to_bool(config_dict.get('loop_on_init', False))
>
> # always log its setting
> log.info("loop_on_init: %s", loop_on_init)
>
> #-
>
>
> On Tuesday, April 9, 2024 at 2:55:32 PM UTC-7 gjr80 wrote:
>
>> The more I think of it the more I don't see the benefit of this approach
>> over using loop_on_init in weewx.conf in dealing with this type of
>> problem. Setting loop_on_init = True will cause WeeWX to reload the
>> driver after (the default) three consecutive attempts to contact the
>> gateway device fail; WeeWX continues running the entire time. Perhaps if
>> some sort of network or device initialisation sat in the WeeWX core there
>> might be a benefit, but all of that sits solely in the driver (as far as I
>> am aware this is the case with all drivers). If the network or the device
>> is in such a state that communication with the device via the API is not
>> possible then no amount of WeeWX restarts or driver reloads will correct
>> the situation.
>>
>> It seems to me that forcing a WeeWX restart via systemd is a somewhat
>> heavy handed approach.
>>
>> My opinion only and I expect others will have a different view.
>>
>> Gary
>>
>> On Wednesday 10 April 2024 at 06:00:37 UTC+10 vince wrote:
>>
>>> update - my ecowitt instance crashed out on me during a several minute
>>> network outage while I was updating firmware on the router/switch/ap so I'm
>>> trying this solution to see how well that works.  Thanks.
>>>
>>> (not a bug in the gw1000 driver - it did exactly what it's configured to
>>> do.  It tried 3x with 2 sec in between.  An alternate workaround would be
>>> to try 1000x with a minute in between to basically get through any
>>> reasonable network outages for the LAN, but I want to try the systemd
>>> method as a more generic fix)
>>>
>>> On Tuesday, March 26, 2024 at 7:56:12 AM UTC-7 gary@gmail.com wrote:
>>>
 I have added these lines to my weewx service file for just such an
 instance.
 Add under StandardError=journal+console entry in the [Service] stanza

 Restart=on-failure
 RestartSec=30

 Restarts weewx after waiting for 30 seconds to allow whatever
 interfered to (hopefully) clear.

 On Monday, March 25, 2024 at 6:26:44 PM UTC-4 vince wrote:

> Perhaps this setting (link)
> 
>  is
> something to try if you want to experiment and let us know if it works…
>
> On Monday, March 25, 2024 at 3:11:41 PM UTC-7 Thomas Hackler wrote:
>
>> thank you for the answer, then it was maybe soemthing wrong with the
>> wifi
>>
>> does it make sense to increase the attempts before exit ?
>>
>> I try to find something to check if the process is running
>> I have some experience with monit, so maybe I find an example or
>> anything else
>>
>>
>> vince schrieb am Montag, 25. März 2024 um 22:09:58 UTC+1:
>>
>>> I have also seen my gw1000 weewx setup abort on the pi4 occasionally
>>> when the wifi network bounces for some reason.  Mine's been up for 6 
>>> weeks
>>> now so it is definitely a transient kind of thing.
>>>
>>> Writing yourself a little cron job to look for the weewxd process
>>> and if it's not there restart it wouldn't be too tough to do.   Perhaps
>>> there is some systemd configuration magic that is possible, but I'm not
>>> sure there what a safe+effective way to leverage systemd would look 
>>> like.
>>> I know how cron works :-)
>>>
>>> On Monday, March 25, 2024 at 1:56:10 PM UTC-7 Thomas Hackler wrote:
>>>
 Hello,
 my weewx stopped yesterday unexpected. The last logs are attached.
 It 

Re: [weewx-user] Re: AWEKAS Upload & Healthchecks.io both stop working this morning

[Tom Keffer]

Classic case of corrupt memory in the Vantage logger. See *Corrupt station
memory
*
in
the wiki.

On Tue, Apr 9, 2024 at 1:31 PM Dave Piehl  wrote:

> Let's try again. This is the link to the log:
> https://pastebin.com/aZ05aSLW
>
> On Tuesday, April 9, 2024 at 5:58:43 AM UTC-5 Dave Piehl wrote:
>
>> Try the link again. I left it unlisted by mistake. Thanks!
>>
>> On Monday, April 8, 2024 at 9:19:50 PM UTC-5 gjr80 wrote:
>>
>>> Don't know if I'm getting special treatment or not, but your link
>>> doesn't work for me. Just paste the log here, I'm sure Google has
>>> sufficient spare storage.
>>>
>>> Gary
>>>
>>> On Tuesday 9 April 2024 at 11:07:57 UTC+10 david...@gmail.com wrote:
>>>
 I moved to Weewx 5 on my Raspberry Pi several weeks ago and all has
 seemed fine. Suddenly this morning after a restart due to a problem with my
 Vantage Console relay, both have stopped working.

 Here's a debug log for about 10 minutes this evening:
 https://pastebin.com/passmailer

 On start up both a still showing as starting but nothing after that.

 I did notice "sudo weectl extension list" returns a strange response
 for Healthchecks even after uninstalling and reinstalling the extension:

 Using configuration file /etc/weewx/weewx.conf
 Extension NameVersion   Description
 Belchertown   1.3.1 A clean modern skin with real time
 streaming updates and interactive charts. Modeled after
 BelchertownWeather.com

 *Healthchecks  ???   Cannot find 'install' module in
 /etc/weewx/bin/user/installer/Healthchecks*mqtt  0.24
  Upload weather data to MQTT server.
 owm   0.9   Upload weather data to OpenWeatherMap.
 windy 0.7   Upload weather data to Windy.

 I'd appreciate any help or direction to getting to the source of these
 issues. 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/22a06545-3682-48e8-a31a-811a9f8599een%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/CAPq0zEA94k68Nyo3m-uoEc%3DP6XmtBJiJs3UAtO1X-we5kpGoqg%40mail.gmail.com.

Re: [weewx-user] After a power loss three days ago, graphs do not update but current data and day's statistic are valid.

[Tom Keffer]

Sylvain, glad it's working for you now!

But, honestly, we can't know what you tried unless you tell us.

For the future: at any time, you can delete all the graphs and HTML files
and WeeWX will regenerate them at the next reporting cycle.

On Sun, Apr 7, 2024 at 5:20 PM Sylvain Gagnon 
wrote:

> I did run wee_reports before making that post and it had no effects.
> However, several hours later, the graphs came back after I rebooted again
> (with debug=1). Now that it's fine, I've reset debug to 0.
>
> Le dimanche 7 avril 2024 à 18 h 38 min 16 s UTC-4, Tom Keffer a écrit :
>
> Sure. Use wee_reports
> <https://www.weewx.com/docs/4.10/utilities.htm#wee_reports_utility>.
>
> However, it sounds like there is an issue with your station. You should
> post a log
> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user#include-the-log>
> .
>
> On Sun, Apr 7, 2024 at 2:53 PM Sylvain Gagnon 
> wrote:
>
> Hi, like the subject says, after a power loss three days ago, graphs do
> not update but current data and day's statistics is valid. Is there a way
> to force a refresh of the graphs? Running WeeWX 4.10.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+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/64f2270a-1377-4ea9-afaf-c1747be20e43n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/64f2270a-1377-4ea9-afaf-c1747be20e43n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> --
> 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/b993b3e1-75cb-453c-8eb6-b032ca85ef83n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/b993b3e1-75cb-453c-8eb6-b032ca85ef83n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEDB%3DuxPbutw0gJ%2BxQsrtUCSNFyJaNAX-4inKVD_176nQw%40mail.gmail.com.

Re: [weewx-user] After a power loss three days ago, graphs do not update but current data and day's statistic are valid.

[Tom Keffer]

Sure. Use wee_reports
.

However, it sounds like there is an issue with your station. You should
post a log

.

On Sun, Apr 7, 2024 at 2:53 PM Sylvain Gagnon 
wrote:

> Hi, like the subject says, after a power loss three days ago, graphs do
> not update but current data and day's statistics is valid. Is there a way
> to force a refresh of the graphs? Running WeeWX 4.10.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/64f2270a-1377-4ea9-afaf-c1747be20e43n%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/CAPq0zEAG5t%2BgYkxpzV%3D2_fiJ-P8pm89VhYAU41D57eSvk%3DYOMQ%40mail.gmail.com.

[weewx-user] Re: REMINDER: upgrade from V5.0.0!

[Tom Keffer]

There are still a handful of stations running V5.0.0.

Please upgrade and avoid getting hit by the bug in V5.0.0!

On Sat, Mar 9, 2024 at 9:46 AM Tom Keffer  wrote:

> I see that there are still MANY users running V5.0.0!
>
> This version has a serious bug that can *damage your operating system* if
> you try to remove an extension.
>
> Please upgrade ASAP!
>
> -tk
>

-- 
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/CAPq0zEBY%3DaJZVt1cRB3NTLNxNausAgKn8FFQdVocxA-pdCe1aw%40mail.gmail.com.

Re: [weewx-user] weewxctl debug error

[Tom Keffer]

What version of Python are you using? The nullcontext requires v3.7 or
greater (which breaks our supposed claim of supporting v3.6 or later).

If you are using v3.6, you can specify an explicit path and get the results
you need:

*weectl debug --output=/tmp/debug.txt*





On Sat, Apr 6, 2024 at 1:14 PM Chris Eidem  wrote:

> I'm trying to find out why rsync isn't sending to my web server and while
> attempting to debug that, i tried running 'weewxctl debug' and got the
> following output:
>
> [weewx@rocky1 ~]$ weectl debug
> Using configuration file /etc/weewx/weewx.conf
> Traceback (most recent call last):
>   File "/usr/share/weewx/weectl.py", line 74, in 
> main()
>   File "/usr/share/weewx/weectl.py", line 66, in main
> namespace.func(namespace)
>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
> namespace.action_func(config_dict, namespace)
>   File "/usr/share/weewx/weectllib/debug_cmd.py", line 54, in debug
> weectllib.debug_actions.debug(config_dict, output=namespace.output)
>   File "/usr/share/weewx/weectllib/debug_actions.py", line 52, in debug
> sink = contextlib.nullcontext(sys.stdout)
> AttributeError: module 'contextlib' has no attribute 'nullcontext'
> [weewx@rocky1 ~]$
>
> The /var/log/messages that showed up at the time:
>
> Apr  6 15:08:38 rocky1 weectl[17297]: INFO weectllib: Initializing weectl
> version 5.0.2
> Apr  6 15:08:38 rocky1 weectl[17297]: INFO weectllib: Command line:
> /usr/share/weewx/weectl.py debug
>
> I have no clue why it's failing. This is from an upgraded weewx on a Rocky
> Linux server.
>
> --
> 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/235d7bad-0802-4ccf-be89-d3029b8f4308n%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/CAPq0zEAviB%3Dp97kLVAhTZm-THtY7ZANFCEqJeqcJ%2BWkvJC_CwA%40mail.gmail.com.

Re: [weewx-user] Re: Weewx und Renkforce WH2315

[Tom Keffer]

I was just going to point that out!

With V5, it's actually easiest to install directly from the URL:

*weectl extension
install https://github.com/EdwinGH/weewx-wh23xx/archive/master.zip
<https://github.com/EdwinGH/weewx-wh23xx/archive/master.zip>*



On Fri, Apr 5, 2024 at 10:53 PM Günther Wrana  wrote:

> Hello, I think I have solved the problem.
> The driver from the following link wget -O weewx-wh23xx.zip
> https://github.com/EdwinGH/weewx-wh23xx/archive/master.zip
> works, at least there is no error message when reconfiguring the weather
> cities.
>
> Thanks for the help and I'll definitely need something from YOU again soon.
>  Another nice day from Austria
>
>
> Hallo ich glaube ich habe das Problem gelöst.
> Der Treiber von folgendem Link wget -O weewx-wh23xx.zip
> https://github.com/EdwinGH/weewx-wh23xx/archive/master.zip
> funktioniert zumindest kommt keine Fehlermeldung bei der Rekonfiguration
> der Wetterstadtionen.
>
> Danke für die Hilfe und ich brauche sicher bald wieder etwas von EUCH.
> Noch einen schönen Tag aus Österreich
>
>
>
> 64GB@64GB:~/Downloads $ rm weewx-wh23xx.zip
> 64GB@64GB:~/Downloads $ wget -O weewx-wh23xx.zip
> https://github.com/EdwinGH/weewx-wh23xx/archive/master.zip
> --2024-04-06 07:40:19--
> https://github.com/EdwinGH/weewx-wh23xx/archive/master.zip
> Resolving github.com (github.com)... 140.82.121.4
> Connecting to github.com (github.com)|140.82.121.4|:443... connected.
> HTTP request sent, awaiting response... 302 Found
> Location:
> https://codeload.github.com/EdwinGH/weewx-wh23xx/zip/refs/heads/master
> [following]
> --2024-04-06 07:40:20--
> https://codeload.github.com/EdwinGH/weewx-wh23xx/zip/refs/heads/master
> Resolving codeload.github.com (codeload.github.com)... 140.82.121.10
> Connecting to codeload.github.com (codeload.github.com)|140.82.121.10|:443...
> connected.
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [application/zip]
> Saving to: ‘weewx-wh23xx.zip’
>
> weewx-wh23xx.zip[ <=>]  24.88K  --.-KB/sin
> 0.03s
>
> 2024-04-06 07:40:20 (739 KB/s) - ‘weewx-wh23xx.zip’ saved [25472]
>
> 64GB@64GB:~/Downloads $ dir
> weewx-wh23xx.zip
> 64GB@64GB:~/Downloads $ weectl extension install weewx-wh23xx.zip
> Using configuration file /etc/weewx/weewx.conf
> Install extension 'weewx-wh23xx.zip' (y/n)? y
> Extracting from zip archive weewx-wh23xx.zip
> Saving installer file to /etc/weewx/bin/user/installer/wh23xx
> Finished installing extension wh23xx from weewx-wh23xx.zip
> 64GB@64GB:~/Downloads $ weectl station reconfigure
> Using configuration file /etc/weewx/weewx.conf
> Processing configuration file /etc/weewx/weewx.conf
>
> Give a description of the station. This will be used for the title of
> reports.
> description [2243 Matzen,Österreich Niederösterreich ]:
>
> Specify altitude, with units 'foot' or 'meter'.  For example:
>   35, foot
>   12, meter
> altitude [199, meter]:
>
> Specify latitude in decimal degrees, negative for south.
> latitude [48.401826]:
> Specify longitude in decimal degrees, negative for west.
> longitude [16.686539]:
>
> Choose a unit system for the reports. Later, you can modify
> your choice, or choose a combination of units. Unit systems
> include:
>   us (ºF, inHg, in, mph)
>   metricwx   (ºC, mbar, mm, m/s)
>   metric (ºC, mbar, cm, km/h)
> unit system [metricwx]:
>
> Choose a driver. Installed drivers include:
>   0) WH23xx  (user.wh23xx)
>   1) AcuRite (weewx.drivers.acurite)
>   2) CC3000  (weewx.drivers.cc3000)
>   3) FineOffsetUSB   (weewx.drivers.fousb)
>   4) Simulator   (weewx.drivers.simulator)
>   5) TE923   (weewx.drivers.te923)
>   6) Ultimeter   (weewx.drivers.ultimeter)
>   7) Vantage (weewx.drivers.vantage)
>   8) WMR100  (weewx.drivers.wmr100)
>   9) WMR300  (weewx.drivers.wmr300)
>  10) WMR9x8  (weewx.drivers.wmr9x8)
>  11) WS1 (weewx.drivers.ws1)
>  12) WS23xx  (weewx.drivers.ws23xx)
>  13) WS28xx  (weewx.drivers.ws28xx)
> driver [4]: 0
>
> You can register the station on weewx.com, where it will be included in a
> map. If you choose to register, you will also need a unique URL to
> identify
> the station (such as a website, or a WeatherUnderground link).
> register this station (y/n)? [y] y
>
> Now give a unique URL for the station. A Weather Underground
> URL such as https://www.wunderground.com/dashboard/pws/KORPORT12 will do.
> Unique URL [http://guentherwrana.ddns.net]:
> Saving configuration file /etc/weewx/weewx.conf
> Saved old configuration file as /etc/weewx/weewx.conf.20240406074122
> 64GB@64GB:~/D

Re: [weewx-user] Is there a way to cache station data values until they change?

[Tom Keffer]

Frankly, WU's rapidfire is very flaky, so that could well be the problem.

What do you see if you set debug=3?

What exact values are missing?

You can try setting archive_post=true as well. Might work.

-tk

On Fri, Apr 5, 2024 at 5:45 PM Kevin Key  wrote:

> Thanks. I've tried that, but then wind_gust, barometer, and a few other
> values go missing from Weather Underground.
>
> On Fri, Apr 5, 2024 at 5:27 PM Tom Keffer  wrote:
>
>> Just set rapidfire=true
>> <https://www.weewx.com/docs/5.0/reference/weewx-options/stdrestful/#rapidfire>
>> .
>>
>> Try it. You won't hurt anything.
>>
>> On Fri, Apr 5, 2024 at 5:20 PM Kevin Key  wrote:
>>
>>> Cool. How do I make use of it?
>>>
>>> On Friday, April 5, 2024 at 2:59:56 PM UTC-7 Tom Keffer wrote:
>>>
>>>> The WU Rapidfire code already has something like that in it. Set
>>>> debug=3 to see it in action.
>>>>
>>>> On Fri, Apr 5, 2024 at 12:13 PM Kevin Key  wrote:
>>>>
>>>>> I'd like to do rapid-fire with my Acurite Atlas and a separate
>>>>> pressure sensor, but the sensors don't deliver all the data at the same
>>>>> time. Is it possible - via the config file - to keep all data in the loop
>>>>> until the data changes?
>>>>>
>>>>> --
>>>>> 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/7542ab11-f14b-4c50-85db-62edcb72bd6dn%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/weewx-user/7542ab11-f14b-4c50-85db-62edcb72bd6dn%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>> --
>>> 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/3efb4c4d-a82a-4e9a-9914-28e157c47301n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/3efb4c4d-a82a-4e9a-9914-28e157c47301n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> 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/cptTpMoeH_k/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/CAPq0zEBssdS%2Bn1AyR8Mt%2B9Q%2Bp8ToYe58u%2ByxYB%2BhVdJSjvnS2w%40mail.gmail.com
>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEBssdS%2Bn1AyR8Mt%2B9Q%2Bp8ToYe58u%2ByxYB%2BhVdJSjvnS2w%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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/CAK3LaRrnZEPU1fEGdXaMd4rzQF4FDTsWctGWHM%2B6s-r2xF22LA%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAK3LaRrnZEPU1fEGdXaMd4rzQF4FDTsWctGWHM%2B6s-r2xF22LA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zED%3DC%3Dk8wVtEvLPG%3DwHBQh0btymdjvVfE9eYVK2kokcqwA%40mail.gmail.com.

Re: [weewx-user] Is there a way to cache station data values until they change?

[Tom Keffer]

Just set rapidfire=true
<https://www.weewx.com/docs/5.0/reference/weewx-options/stdrestful/#rapidfire>
.

Try it. You won't hurt anything.

On Fri, Apr 5, 2024 at 5:20 PM Kevin Key  wrote:

> Cool. How do I make use of it?
>
> On Friday, April 5, 2024 at 2:59:56 PM UTC-7 Tom Keffer wrote:
>
>> The WU Rapidfire code already has something like that in it. Set debug=3
>> to see it in action.
>>
>> On Fri, Apr 5, 2024 at 12:13 PM Kevin Key  wrote:
>>
>>> I'd like to do rapid-fire with my Acurite Atlas and a separate pressure
>>> sensor, but the sensors don't deliver all the data at the same time. Is it
>>> possible - via the config file - to keep all data in the loop until the
>>> data changes?
>>>
>>> --
>>> 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/7542ab11-f14b-4c50-85db-62edcb72bd6dn%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/7542ab11-f14b-4c50-85db-62edcb72bd6dn%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/3efb4c4d-a82a-4e9a-9914-28e157c47301n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/3efb4c4d-a82a-4e9a-9914-28e157c47301n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEBssdS%2Bn1AyR8Mt%2B9Q%2Bp8ToYe58u%2ByxYB%2BhVdJSjvnS2w%40mail.gmail.com.

Re: [weewx-user] Is there a way to cache station data values until they change?

[Tom Keffer]

The WU Rapidfire code already has something like that in it. Set debug=3 to
see it in action.

On Fri, Apr 5, 2024 at 12:13 PM Kevin Key  wrote:

> I'd like to do rapid-fire with my Acurite Atlas and a separate pressure
> sensor, but the sensors don't deliver all the data at the same time. Is it
> possible - via the config file - to keep all data in the loop until the
> data changes?
>
> --
> 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/7542ab11-f14b-4c50-85db-62edcb72bd6dn%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/CAPq0zECxSZrnAr0MGc3W0QhxS-yMrw-m5e7yYZ357iVHx6cQxA%40mail.gmail.com.

Re: [weewx-user] Re: Weewx und Renkforce WH2315

[Tom Keffer]

Günther?

On Mon, Apr 1, 2024 at 9:19 AM Tom Keffer  wrote:

> Two things:
>
> 1. You are still using the original version of the driver. You want my
> patched version at  https://github.com/tkeffer/weewx-wh23xx
> 2. What version of weewx are you using? Early beta versions of v5.0 could
> not recognize a zip file, but current releases do.
>
> *weectl --version*
>
>
> On Mon, Apr 1, 2024 at 8:48 AM Günther Wrana  wrote:
>
>> Hello, this is the message when I install the driver and try to select
>> when reconfiguring
>>
>> Thanks Günther
>>
>> Hallo das ist die Meldung wenn ich den Treiber installiere und versuche
>> bei der Rekonfiguration auszuwählen
>>
>> Danke Günther
>>
>>
>>
>> 64GB@64GB:~/Downloads $ wget -O weewx-wh23xx.zip
>> https://github.com/matthewwall/weewx-wh23xx/archive/master.zip
>> --2024-04-01 17:27:53--
>> https://github.com/matthewwall/weewx-wh23xx/archive/master.zip
>> Resolving github.com (github.com)... 140.82.121.3
>> Connecting to github.com (github.com)|140.82.121.3|:443... connected.
>> HTTP request sent, awaiting response... 302 Found
>> Location:
>> https://codeload.github.com/matthewwall/weewx-wh23xx/zip/refs/heads/master
>> [following]
>> --2024-04-01 17:27:53--
>> https://codeload.github.com/matthewwall/weewx-wh23xx/zip/refs/heads/master
>> Resolving codeload.github.com (codeload.github.com)... 140.82.121.9
>> Connecting to codeload.github.com (codeload.github.com)|140.82.121.9|:443...
>> connected.
>> HTTP request sent, awaiting response... 200 OK
>> Length: unspecified [application/zip]
>> Saving to: ‘weewx-wh23xx.zip’
>>
>> weewx-wh23xx.zip[ <=>]  23.64K  --.-KB/sin
>> 0.03s
>>
>> 2024-04-01 17:27:54 (837 KB/s) - ‘weewx-wh23xx.zip’ saved [24210]
>>
>> 64GB@64GB:~/Downloads $ weectl extension install weewx-wh23xx-master.zip
>> Using configuration file /etc/weewx/weewx.conf
>> Install extension 'weewx-wh23xx-master.zip' (y/n)? y
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/weectl.py", line 74, in 
>> main()
>>   File "/usr/share/weewx/weectl.py", line 66, in main
>> namespace.func(namespace)
>>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
>> namespace.action_func(config_dict, namespace)
>>   File "/usr/share/weewx/weectllib/extension_cmd.py", line 116, in
>> install_extension
>> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>>   File "/usr/share/weewx/weecfg/extension.py", line 143, in
>> install_extension
>> raise InstallError(f"Unrecognized type for {extension_path}")
>> weecfg.extension.InstallError: Unrecognized type for
>> weewx-wh23xx-master.zip
>> 64GB@64GB:~/Downloads $ weectl station reconfigure
>> Using configuration file /etc/weewx/weewx.conf
>> Processing configuration file /etc/weewx/weewx.conf
>>
>> Give a description of the station. This will be used for the title of
>> reports.
>> description [2243 Matzen,Österreich Niederösterreich ]:
>>
>> Specify altitude, with units 'foot' or 'meter'.  For example:
>>   35, foot
>>   12, meter
>> altitude [199, meter]:
>>
>> Specify latitude in decimal degrees, negative for south.
>> latitude [48.401826]:
>> Specify longitude in decimal degrees, negative for west.
>> longitude [16.686539]:
>>
>> Choose a unit system for the reports. Later, you can modify
>> your choice, or choose a combination of units. Unit systems
>> include:
>>   us (ºF, inHg, in, mph)
>>   metricwx   (ºC, mbar, mm, m/s)
>>   metric (ºC, mbar, cm, km/h)
>> unit system [metricwx]:
>>
>> Choose a driver. Installed drivers include:
>>   0) ?   (user.wh23xx) invalid syntax (wh23xx.py,
>> line 427)
>>   1) AcuRite (weewx.drivers.acurite)
>>   2) CC3000  (weewx.drivers.cc3000)
>>   3) FineOffsetUSB   (weewx.drivers.fousb)
>>   4) Simulator   (weewx.drivers.simulator)
>>   5) TE923   (weewx.drivers.te923)
>>   6) Ultimeter   (weewx.drivers.ultimeter)
>>   7) Vantage (weewx.drivers.vantage)
>>   8) WMR100  (weewx.drivers.wmr100)
>>   9) WMR300  (weewx.drivers.wmr300)
>>  10) WMR9x8  (weewx.drivers.wmr9x8)
>>  11) WS1 (weewx.drivers.ws1)
>>  12) WS23xx  (weewx.drivers.ws23xx)
>>  13) WS28xx  (weewx.drivers.ws28xx)
>> driver [4]:
>>
&g

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

[Tom Keffer]

I can do it the same way the MySQL driver handles extra parameters: you
list them with the others. The code strips off the ones it recognizes, then
passes the rest on to the rsync command.

On Tue, Apr 2, 2024 at 4:08 PM 'John Kline' via weewx-user <
weewx-user@googlegroups.com> 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/request
> https://github.com/weewx/weewx/issues/951
>
> Thanks to you both.
> Chris
> On 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"   # <=== new
>>
>> Disclaimer - 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 uploader
>>
>> On 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-solution

>>>
>>> That 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-rsynctransfer
>>>
>>> It 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
>>>  Glenn
>>>
>>> Various WeeWx addons at
>>> https://github.com/glennmckechnie
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/0d2bbda5-dc2c-4075-bcae-44b6b4c01063n%40googlegroups.com
> 

Re: [weewx-user] Re: New 5.0.2 Installation - SystemCtl can't start it, invalid argument

[Tom Keffer]

Discussed this with Matthew. Could you post the contents of a few things
for us?

1. Contents of /usr/lib/systemd/system/weewx.service
2. Contents of /etc/default/weewx.
3. Does /etc/systemd/system/weewx.service exist? If so, what does it
contain?
4. Contents of /usr/bin/weewxd
5. Contents of /etc/os-release

Please note any changes you have made since the install.


On Tue, Apr 2, 2024 at 2:02 PM crecre9  wrote:

> That's what my service file looked like. i was getting the error saying
> the path wasn't absolute, so i removed the "weewxd" portion from the
> ExecStart line, but as i mentioned, i don't have any idea how to fix that
> file. I have no idea why it wouldn't work out of the box either. The only
> thing i can think of is the removal of older versions of weewx were
> incomplete somehow and is somehow interfering.
>
> On Tuesday, April 2, 2024 at 2:18:26 PM UTC-5 vince wrote:
>
>> Are you running an unusual os on the pi ?
>>  Did you do something to edit the weewx.service file ?
>>
>>  A clean pi running raspios installs+works just fine here with the
>> apt-get dpkg.
>> The vanilla service file looks like:
>>
>> pi@raspberrypi:~ $ cat /usr/lib/systemd/system/weewx.service
>> # systemd service configuration file for WeeWX
>>
>> [Unit]
>> Description=WeeWX
>> Documentation=https://weewx.com/docs
>> Requires=time-sync.target
>> After=time-sync.target
>> Wants=network-online.target
>> After=network-online.target
>>
>> [Service]
>> ExecStart=weewxd /etc/weewx/weewx.conf
>> StandardOutput=null
>> StandardError=journal+console
>> RuntimeDirectory=weewx
>> RuntimeDirectoryMode=775
>> User=weewx
>> Group=weewx
>>
>> [Install]
>> WantedBy=multi-user.target
>>
>> On Tuesday, April 2, 2024 at 11:50:36 AM UTC-7 crecre9 wrote:
>>
>>> I have a fresh 5.0.2 install using apt-get. The program won't run as a
>>> service:
>>>
>>> ● weewx.service - WeeWX
>>>Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor
>>> preset: en
>>>Active: failed (Result: exit-code) since Tue 2024-04-02 13:26:02 -05;
>>> 1min 2s
>>>  Docs: https://weewx.com/docs
>>>   Process: 2178 ExecStart=/etc/weewx/weewx.conf (code=exited,
>>> status=203/EXEC)
>>>  Main PID: 2178 (code=exited, status=203/EXEC)
>>>
>>> Apr 02 13:26:02 rpi systemd[1]: Started WeeWX.
>>> Apr 02 13:26:02 rpi systemd[1]: weewx.service: Main process exited,
>>> code=exited,
>>> Apr 02 13:26:02 rpi systemd[1]: weewx.service: Unit entered failed state.
>>> Apr 02 13:26:02 rpi systemd[1]: weewx.service: Failed with result
>>> 'exit-code'.
>>>
>>> And when I look at status:
>>>
>>> Apr 02 13:28:28 rpi systemd[1]:
>>> [/usr/lib/systemd/system/weewx.service:12] Executable path is not absolute,
>>> ignoring: weewxd /etc/weewx/weewx.conf
>>> Apr 02 13:28:28 rpi systemd[1]: weewx.service: Service lacks both
>>> ExecStart= and ExecStop= setting. Refusing.
>>>
>>>
>>> Any ideas? Its like the installation files improperly set up the daemon
>>> service.
>>>
>>>
>>> -Joseph
>>>
>> --
> 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/9965cf0f-391b-4d22-ab92-5f16edc03369n%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/CAPq0zEA1w%2BpmVA2gG948m570mWA-sJSQ9S7CpoYNC%3DMNQehDuQ%40mail.gmail.com.

Re: [weewx-user] How to use last non-null value in loop?

[Tom Keffer]

The aggregation ".last" will return the last non-null value in the
aggregation period. So, for example, you could use $day.pressure.last

On Tue, Apr 2, 2024 at 2:08 PM Kevin Key  wrote:

> Hi,
>
> How do I get Weewx to always report the last non-null value?
>
> I've tried...
>
> [StdCalibrate]
> [[Corrections]]
> pressure = last.pressure
>
> and also
>
> pressure = last(pressure)
>
>
> with no luck.
>
> What am I doing wrong?
>
> --
> 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/611aedb8-a5a6-435f-a67b-c0b04ae42ac1n%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/CAPq0zEA6ExD8iOi5x2R__zUD12VsqjLmcWtNA6ON297UEjGaqA%40mail.gmail.com.

Re: [weewx-user] Re: Move WeeWx database to external drive

[Tom Keffer]

It's really very simple. Just set SQLITE_ROOT to the directory where you
want the database to be saved. You'll find it under [[SQLite]]

[DatabaseTypes]
  ...
  [[SQLite]]
...
SQLITE_ROOT = /path/to/your/sqlite/dir



On Tue, Apr 2, 2024 at 4:13 AM Ben W.  wrote:

> Hi, John!
> Yes that is exactly what I'm trying to do as with your NAS, but with an
> external drive USB-connected to the RPi. It's mounted and I can write to
> it. I just haven't quite figured out (or found the resource yet) to update
> the appropriate weewx conf file to tell weewx to use the directory on the
> drive rather than the current (default ?) directory that is used.
>
> Thanks!
>
> On Monday, April 1, 2024 at 8:11:18 AM UTC-5 Jon Fear wrote:
>
>> I am doing something similar using my NAS.
>>
>> I have mounted the NAS and then created symbolic links to the
>> appropriately named folders or directories on the NAS. When mounting the
>> NAS, I needed to make sure that the permissions were correct for weewx
>> which was eventually quite simple to achieve. If you are mounting the
>> complete drive via say USB then it should be simple, just remember to
>> create the appropriate directories and make sure the permissions are set
>> correctly.
>>
>> Best of luck..
>>
>> Jon
>>
>> On Monday 1 April 2024 at 13:54:43 UTC+1 Ben W. wrote:
>>
>>> Hello!
>>>
>>> My setup is slowly coming together. Currently, I am able to see the data
>>> on my local network via browser at 192.168.7.201/weewx. I feel pretty
>>> accomplished so far, but I know I have a long ways to go. Before I get too
>>> far, my intent is to use my attached external hard drive to store the data
>>> for WeeWx. I'm pretty sure the data is being saved to the microSD card
>>> right now.
>>>
>>> Would someone be able to direct me on how to move the database to my
>>> external drive and instruct WeeWx to use that location going forward?
>>>
>>> I installed WeeWX V5 using 'apt' and the instructions here:
>>> https://weewx.com/docs/5.0/quickstarts/debian/
>>>
>>> What I'm using:
>>> Ambient Weather WS-5000 weather station
>>> Ecowitt GW1100 hub
>>> RPi 5 8GB "headless"
>>> 2TB HDD drive
>>>
>>>
>>> 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/1c310abb-7b22-45ef-8ad1-39a6d45aa01en%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/CAPq0zEDBVGz50kREn4Ykv-XFX7s4DrfvW7XR8upmMf_oy0p5Ww%40mail.gmail.com.

Re: [weewx-user] show old nooa data in pulldown

[Tom Keffer]

Skins are updated only if you update them explicitly.

See the documentation for weectl station upgrade
<https://www.weewx.com/docs/5.0/utilities/weectl-station/#upgrade-an-existing-station>
.

On Mon, Apr 1, 2024 at 9:35 AM WindnFog  wrote:

> I'm modifying titlebar.inc for a different reason. I'm curious if it will
> be overwritten in subsequent pip weewx updates or treated like weewx.conf,
> etc. Does the user decide which version to keep if these .inc files are
> user modified?
>
> On Sunday, March 31, 2024 at 10:23:45 AM UTC-3 Tom Keffer wrote:
>
>> Unfortunately, there is no easy way to do this. The list of months is
>> generated dynamically when the reports are run.
>>
>> If you are familiar with HTML, something you could do is modify the
>> select statement in the template titlebar.inc to include the extra dates.
>> For example, say you had extra months 2010-08 and 2010-09, contained in
>> files NOAA/NOAA-2010-08.txt and  NOAA/NOAA-2010-09.txt, respectively. When
>> done, this would look like (NOT TESTED):
>>
>> 
>>   2010-08
>>   2010-09
>>   #for $monthYear in $SummaryByMonth
>>   $monthYear
>>   #end for
>>   - $gettext("select month") -
>> 
>>
>> This would make the extra dates available in the drop down list.
>>
>> On Sun, Mar 31, 2024 at 4:12 AM simon  wrote:
>>
>>> hello all, i have old nooa txt files with datas which are not in the
>>> database.
>>> is it possible to bring the old files into the pulldown menu to select
>>> them ?[image: weewx nooa.png]
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/4d41dea9-4785-43d9-b67e-2c7c34c659b8n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/4d41dea9-4785-43d9-b67e-2c7c34c659b8n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/26bed7e3-3b1e-4887-804f-8731ff408eb3n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/26bed7e3-3b1e-4887-804f-8731ff408eb3n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zECZzetoD0gmKB9b6YO6j97yastQrKiCtuQvauTQpMbE0w%40mail.gmail.com.

Re: [weewx-user] Re: Weewx und Renkforce WH2315

[Tom Keffer]

Two things:

1. You are still using the original version of the driver. You want my
patched version at  https://github.com/tkeffer/weewx-wh23xx
2. What version of weewx are you using? Early beta versions of v5.0 could
not recognize a zip file, but current releases do.

*weectl --version*


On Mon, Apr 1, 2024 at 8:48 AM Günther Wrana  wrote:

> Hello, this is the message when I install the driver and try to select
> when reconfiguring
>
> Thanks Günther
>
> Hallo das ist die Meldung wenn ich den Treiber installiere und versuche
> bei der Rekonfiguration auszuwählen
>
> Danke Günther
>
>
>
> 64GB@64GB:~/Downloads $ wget -O weewx-wh23xx.zip
> https://github.com/matthewwall/weewx-wh23xx/archive/master.zip
> --2024-04-01 17:27:53--
> https://github.com/matthewwall/weewx-wh23xx/archive/master.zip
> Resolving github.com (github.com)... 140.82.121.3
> Connecting to github.com (github.com)|140.82.121.3|:443... connected.
> HTTP request sent, awaiting response... 302 Found
> Location:
> https://codeload.github.com/matthewwall/weewx-wh23xx/zip/refs/heads/master
> [following]
> --2024-04-01 17:27:53--
> https://codeload.github.com/matthewwall/weewx-wh23xx/zip/refs/heads/master
> Resolving codeload.github.com (codeload.github.com)... 140.82.121.9
> Connecting to codeload.github.com (codeload.github.com)|140.82.121.9|:443...
> connected.
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [application/zip]
> Saving to: ‘weewx-wh23xx.zip’
>
> weewx-wh23xx.zip[ <=>]  23.64K  --.-KB/sin
> 0.03s
>
> 2024-04-01 17:27:54 (837 KB/s) - ‘weewx-wh23xx.zip’ saved [24210]
>
> 64GB@64GB:~/Downloads $ weectl extension install weewx-wh23xx-master.zip
> Using configuration file /etc/weewx/weewx.conf
> Install extension 'weewx-wh23xx-master.zip' (y/n)? y
> Traceback (most recent call last):
>   File "/usr/share/weewx/weectl.py", line 74, in 
> main()
>   File "/usr/share/weewx/weectl.py", line 66, in main
> namespace.func(namespace)
>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
> namespace.action_func(config_dict, namespace)
>   File "/usr/share/weewx/weectllib/extension_cmd.py", line 116, in
> install_extension
> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>   File "/usr/share/weewx/weecfg/extension.py", line 143, in
> install_extension
> raise InstallError(f"Unrecognized type for {extension_path}")
> weecfg.extension.InstallError: Unrecognized type for
> weewx-wh23xx-master.zip
> 64GB@64GB:~/Downloads $ weectl station reconfigure
> Using configuration file /etc/weewx/weewx.conf
> Processing configuration file /etc/weewx/weewx.conf
>
> Give a description of the station. This will be used for the title of
> reports.
> description [2243 Matzen,Österreich Niederösterreich ]:
>
> Specify altitude, with units 'foot' or 'meter'.  For example:
>   35, foot
>   12, meter
> altitude [199, meter]:
>
> Specify latitude in decimal degrees, negative for south.
> latitude [48.401826]:
> Specify longitude in decimal degrees, negative for west.
> longitude [16.686539]:
>
> Choose a unit system for the reports. Later, you can modify
> your choice, or choose a combination of units. Unit systems
> include:
>   us (ºF, inHg, in, mph)
>   metricwx   (ºC, mbar, mm, m/s)
>   metric (ºC, mbar, cm, km/h)
> unit system [metricwx]:
>
> Choose a driver. Installed drivers include:
>   0) ?   (user.wh23xx) invalid syntax (wh23xx.py,
> line 427)
>   1) AcuRite (weewx.drivers.acurite)
>   2) CC3000  (weewx.drivers.cc3000)
>   3) FineOffsetUSB   (weewx.drivers.fousb)
>   4) Simulator   (weewx.drivers.simulator)
>   5) TE923   (weewx.drivers.te923)
>   6) Ultimeter   (weewx.drivers.ultimeter)
>   7) Vantage (weewx.drivers.vantage)
>   8) WMR100  (weewx.drivers.wmr100)
>   9) WMR300  (weewx.drivers.wmr300)
>  10) WMR9x8  (weewx.drivers.wmr9x8)
>  11) WS1 (weewx.drivers.ws1)
>  12) WS23xx  (weewx.drivers.ws23xx)
>  13) WS28xx      (weewx.drivers.ws28xx)
> driver [4]:
>
> Tom Keffer schrieb am Sonntag, 31. März 2024 um 17:48:37 UTC+2:
>
>> I did a quick port of the driver. It has *not* been tested!
>>
>> Find it here: https://github.com/tkeffer/weewx-wh23xx
>>
>> If it works for you, I'll ask Matthew to incorporate the changes.
>>
>> -tk
>>
>> On Sun, Mar 31, 2024 at 2:12 AM Tom Keffer  wrote:
>>
>>> It appears that the wh23xx driver has not been ported to Python 2.
>>>
>>> On Sun, M

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

[Tom Keffer]

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:
> [image: weewx-vantagenext.png]
>
> chaunceygardiner/weewx-vantagenext: VantageNext is a WeeWX driver based on 
> the Vantage driver that ships with WeeWX. 
> 
> github.com 
> 
>
> It 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.

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

[Tom Keffer]

Issue #247  explains the problem.

On Sun, Mar 31, 2024 at 3:56 PM 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/bc83e9f6-5231-4702-8afc-758c645061cdn%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/CAPq0zECcKRqXSxuna25pV%3Dd%2Brz-WzTWLmS8GQjeTr46ZXybzmg%40mail.gmail.com.

Re: [weewx-user] show old nooa data in pulldown

[Tom Keffer]

Unfortunately, there is no easy way to do this. The list of months is
generated dynamically when the reports are run.

If you are familiar with HTML, something you could do is modify the select
statement in the template titlebar.inc to include the extra dates. For
example, say you had extra months 2010-08 and 2010-09, contained in files
NOAA/NOAA-2010-08.txt and  NOAA/NOAA-2010-09.txt, respectively. When done,
this would look like (NOT TESTED):


  2010-08
  2010-09
  #for $monthYear in $SummaryByMonth
  $monthYear
  #end for
  - $gettext("select month") -


This would make the extra dates available in the drop down list.

On Sun, Mar 31, 2024 at 4:12 AM simon  wrote:

> hello all, i have old nooa txt files with datas which are not in the
> database.
> is it possible to bring the old files into the pulldown menu to select
> them ?[image: weewx nooa.png]
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/4d41dea9-4785-43d9-b67e-2c7c34c659b8n%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/CAPq0zEAjEVyJjfrjeLD4w-ifdu5nrh6wMbut5_3obYyLWcH0sQ%40mail.gmail.com.

Re: [weewx-user] wind metric units, change to kph or kilometers per hour?

[Tom Keffer]

Look in weewx.conf. Add options for group_speed and group_speed2 as follows:

[StdReport]
...
[[Defaults]]
...
[[[Units]]]
   ...
   Groups
   ...
   group_speed = km_per_hour
   group_speed2 = km_per_hour2


On Wed, Mar 27, 2024 at 11:54 AM Gord Snarr (GSFarm) 
wrote:

> Setting metricwx or metric in weewx.conf gives me a reading with M/s wind
> speed. Is there a simple way to change that to KPH?
> I don't see a wind-group in the units/groups in the .conf file.
>
> I do have the software running nicely now after updating a bunch of
> permissions.
>
> -Gord.
>
> --
> 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/e723cd70-2f16-49d8-adfe-1518f0c329cen%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/CAPq0zEAHz%3D8jarJxskbDC5CcfpXRO_-Z8-unCYOJ5yt%2BGv2gtA%40mail.gmail.com.

Re: [weewx-user] Unable to find WeeWX log messages

[Tom Keffer]

Take a look at the wiki guide *View logs
*.

You didn't say what kind of operating system you are using, but odds are
your system is using journald, so pay particular attention to that section
.

On Tue, Mar 26, 2024 at 5:43 AM Ben W.  wrote:

> Hello!
> New/noob user and slowly getting everything together. I have weather
> sensors feeding into an Ecowitt GW1100 hub. Over the past day, I worked on
> getting WeeWx installed on my RPi 5. I feel I'm almost there, but not quite.
>
> When I run the "weewxd" command, I get results so that tells me the
> connection is there. It polls/refreshes every 20 seconds. But that is it.
> That's as far as I can get.
>
> I want to view the data and build a report (I believe you call them
> skins(?)), but cannot seem to find any of the folders/directories where the
> data should be.
>
> To find the logs, I run, "sudo grep weewxd /var/log/syslog" or "sudo grep
> weewxd /var/log/messages" but then a "no such file or directory" is
> returned.
>
> Any pointers or directing me to the resource that I missed/overlooked
> would be great!
>
> What I'm using:
> Ambient Weather WS-5000 weather station
> Ecowitt GW1100 hub
> RPi 5 8 GB Headless (no monitor/ command line only)
> 2TB HDD drive (that I want to use to store the WeeWx data - to do later)
>
> 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/2453539d-caaf-4454-b62c-7eade552e443n%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/CAPq0zEDtZ1nN-Gq0%2B2KLsT_FSpnfZCCN_4SD3xbp%3D860zPrUCA%40mail.gmail.com.

Re: [weewx-user] How Remove Telemetry HTML

[Tom Keffer]

If you don't want it to appear at all, comment out the widget that is
responsible for displaying it. Go into file Seasons/index.html.tmpl and
change this:


  #include "current.inc"
  #include "sunmoon.inc"
  #include "hilo.inc"
  #include "sensors.inc"
  #include "about.inc"
  #include "radar.inc"
  #include "satellite.inc"
  #include "map.inc"


to this:


  #include "current.inc"
  #include "sunmoon.inc"
  #include "hilo.inc"
  ##include "sensors.inc"
  #include "about.inc"
  #include "radar.inc"
  #include "satellite.inc"
  #include "map.inc"


In summary, the hash mark "#" becomes a double hash "##" in order to
comment something out.

-tk

On Mon, Mar 25, 2024 at 10:04 AM Wayne  wrote:

> Hello -  Am running weewx V 5.0.2 on a RPi 4 (DEB install) currently
> running the simulator driver.  My weather station is hardwired and
> therefore I have no need to display sensor signal, voltage, or battery
> status in reports.  For the Seasons skin how do I remove the "Sensor
> Status" html from being generated?  This info appears on left side of the
> Seasons default web page.  Tried commenting-out what I thought was the
> responsible section in skins.conf but that did not work.
>
> So I'm guessing the lines below from skins.conf are responsible.  Do I
> delete all values to the right of "=" for sensor_connections,
> sensor_batteries, and sensor_voltages?  Comment out these lines entirely?
> Something else?
>
> Guidance please.  Thank you.
>
> ==
> # The sensor status information is used in the sensor pages.  These
> lists
> # determine which database fields will be shown, as well as the order
> in
> # which they will be displayed.
> sensor_connections = rxCheckPercent, signal1, signal2, signal3,
> signal4, signal5, signal6, signal7, signal8
> sensor_batteries = outTempBatteryStatus, inTempBatteryStatus,
> rainBatteryStatus, hailBatteryStatus, snowBatteryStatus, windBatteryStatus,
> uvBatteryStatus, txBatteryStatus, batteryStatus1, batteryStatus2,
> batteryStatus3, batteryStatus4, batteryStatus5, batteryStatus6,
> batteryStatus7, batteryStatus8
> sensor_voltages = consBatteryVoltage, heatingVoltage, supplyVoltage,
> referenceVoltage
>
>
> ==
>
>
> --
> 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/c313baf6-1aa2-46e5-a1fa-f36035da3380%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/CAPq0zEBsyUJK4jjD6YwxhGBNSraC1e-zvAJZnQvpTjB8dvDPOQ%40mail.gmail.com.

Re: [weewx-user] Wunderground uploads using wunderfixer

[Tom Keffer]

If someone wants to take it on as a project, we could put it in its own
repository.

On Mon, Mar 25, 2024 at 10:47 AM 'Andy Peterman' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Actually, I've had this work for entries even older.  I just had it update
> entries from the previous day and it seems to have worked.
>
> Let's keep wunderfixer around!
>
> On Friday, March 22, 2024 at 5:52:04 AM UTC-7 Tom Keffer wrote:
>
>> Good to know! So, it appears the WU will allow postdating of up to 4
>> hours.
>>
>> On Thu, Mar 21, 2024 at 7:42 PM 'Andy Peterman' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>>> Strange, I'm still running 4.10.2 and just used wunderfixer
>>> successfully.  Our Internet was down for about 3 hours, I ran wunderfixer,
>>> and it filled in the entire period.  Also, last weekend weewx hung right
>>> after the time change (not sure why, but that's another problem) and when I
>>> got it going again, I had about a 4 hour gap.  Once again, I ran
>>> wunderfixer and it filled in the 20+ entries that were missing.  It was a
>>> while before the data showed up, but I checked and it's definitely there.
>>>
>>> Are you sure that Weather Underground has removed this feature?
>>>
>>> On Tuesday, October 10, 2023 at 5:33:19 PM UTC-7 Tom Keffer wrote:
>>>
>>>> Thanks for verifying what we've always suspected. I'm actually
>>>> surprised they responded at all!
>>>>
>>>> For just this reason we've dropped wunderfixer from V5.
>>>>
>>>> On Tue, Oct 10, 2023 at 2:16 PM Ernest Jillson 
>>>> wrote:
>>>>
>>>>> Good afternoon group.
>>>>>
>>>>> I emailed Weather Underground support yesterday about backfilling
>>>>> observations after having no internet for two days. Here was the response:
>>>>>
>>>>> "Thank you for being so kind as to want to backfill your station's
>>>>> data.  But because of the quality control process we have in place, data
>>>>> that is more than an hour old is discarded.  So the upload is a success,
>>>>> but it will never appear on the site.
>>>>>
>>>>> Please let me know if you have any additional questions.  Thank you
>>>>> for being part of the Weather Underground community!
>>>>>
>>>>> --Victoria"
>>>>>
>>>>> While I did reply back and ask if that feature would be restored at
>>>>> any time in the future, I think we can call this process dead. It sounds
>>>>> like wunderfixer will still work, though, for data less than 1 hour old.
>>>>>
>>>>> Ernie
>>>>>
>>>>> --
>>>>> 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/CAC5oUmOeLccyR-Jng%2BZCQBXbfixHNnZCevPJd_0CrwK4GjF%3DRw%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/weewx-user/CAC5oUmOeLccyR-Jng%2BZCQBXbfixHNnZCevPJd_0CrwK4GjF%3DRw%40mail.gmail.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>> --
>>> 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/b4276305-cc25-4271-a7ce-0762b1d8c2c5n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/b4276305-cc25-4271-a7ce-0762b1d8c2c5n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/caa70ba6-93a0-4471-a13d-143b97dbbc22n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/caa70ba6-93a0-4471-a13d-143b97dbbc22n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEDvk1fG7evTAVZCx5Nr84R4wKK8OEq8RfrgoJWMa2x0Dg%40mail.gmail.com.

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

[Tom Keffer]

Many years ago, Luc Heijst started a thread on how the Davis frequency
hopping works:
https://groups.google.com/g/weewx-user/c/ZjDVbSmwmZY/m/Sm8AHCu3CAAJ

On Sun, Mar 24, 2024 at 8:05 AM bgra...@umw.edu  wrote:

> Vince,
> According to Davis for the Vantage Pro 2:
> Operates on frequency-hopping spread spectrum of 902 to 928 MHz. Vantage
> Pro units operated at 916.5 MHz
>
> *Does the rtldavis take care of this? Is it able to scan for spread
> spectrum data? I don’t know a lot about this.*
> *Thanks.*
>
> *Bob*
> On Saturday, March 23, 2024 at 3:09:10 PM UTC-4 vince wrote:
>
>> Sorry - late reply.  I don't understand the frequency hopping question.
>> The rtldavis just kinda works and hears the ISS just fine.  I didn't do an
>> exhaustive test but I did run it for a couple three days and it was nice
>> and stable here.
>>
>> On Sunday, March 10, 2024 at 6:56:07 AM UTC-7 bgra...@umw.edu wrote:
>>
>>>
>>> Hello,
>>> I need some help setting up a VantagePro2 with this. Vince’s How To was
>>> helpful but doesn’t address the VP2 and its frequency hopping. Could
>>> someone running a successful setup post details? I’m running Bookworm on an
>>> RPI5. Thanks in advance.
>>> Bob
>>>
>>> On Sunday, March 10, 2024 at 3:12:55 AM UTC-4 mihec wrote:
>>>
 Hi,
 I need help setting up the rtldavis as well. Currently I'm using
 Ubuntu22.04 (as a test polygon) and latest weewx version (5.0x). I did
 follow up instructions from the github link but got stuck at step 4) where
 I should reconfigure the driver. The new "weectl" binary does not seem to
 have this option but I was assuming it might do it with "weectl extension
 install" already?
 The next issue is with the build. I don't understand 5b): Since I am
 supposed to "cd" into a directory, it should have already exist. But when
 was the "$GOPATH/src/github.com/lheijst/rtldavis" created?
 I managed to compile some code (honestly don't know how :-) ), I have a
 rtldavis binary which seems to recognize my Realtek RTLSDR dongle. I then
 try step 7) but it fails with
 File "/etc/weewx/bin/user/rtldavis.py", line 93, in 
   import weewx.drivers
 ModuleNotFoundError: No module named 'weewx'

 Can you please help with this?
 Thank you.
 torek, 23. avgust 2022 ob 05:56:50 UTC+2 je oseba storm...@gmail.com
 napisala:

> Take a look here:
>
> https://github.com/lheijst/weewx-rtldavis
>
> On Monday, August 22, 2022 at 11:42:38 PM UTC-4 f4n...@gmail.com
> wrote:
>
>> Hi, does anyone have the installation files for rtldavis? It seems to
>> be archived (https://github.com/bemasher/rtldavis) and not longer
>> available in the repository if I try to install it with golang.
>>
>> Is anyone having long term experience and still running it? How
>> stable is the signal with a R820T/T2 chip? Does it get every 2.5s wind
>> packet?
>>
>> Thanks for any advice,
>> fankyy
>>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/b3e3420c-61c8-43fa-8879-9399f4fbc5d4n%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/CAPq0zEBZt1RcLSdi-K10CTtr-zUadJ%3DVw6Be8BMEnMyQeB7ygg%40mail.gmail.com.

Re: [weewx-user] Permission denied: '/etc/weewx/weewx.conf.

[Tom Keffer]

It looks like you are trying to run "weectl station reconfigure". Is that
right? And, you're getting a permissions error.

You didn't say which version of v5.0 you are using, but I'll assume v5.0.2.
With this version, all files in /etc/weewx should be owned by user "weewx",
group "weewx". Check to make sure that this is so. Here is what I get when
I check on an Ubuntu virtual machine:

*ubuntu@fit-bushbuck*:*~*$ ls -al /etc/weewx

total 88

drwxrwsr-x 12 weewx weewx  4096 Mar 23 14:33 *.*

drwxr-xr-x 96 root  root   4096 Mar 23 14:33 *..*

drwxrwsr-x  3 weewx weewx  4096 Mar 23 14:33 *bin*

drwxrwsr-x  8 weewx weewx  4096 Mar 23 14:33 *examples*

drwxrwsr-x  2 weewx weewx  4096 Mar 23 14:33 *import*

drwxrwsr-x  2 weewx weewx  4096 Mar 23 14:33 *init.d*

drwxrwsr-x  2 weewx weewx  4096 Mar 23 14:33 *logrotate.d*

drwxrwsr-x  4 weewx weewx  4096 Mar 23 14:33 *logwatch*

drwxrwsr-x  2 weewx weewx  4096 Mar 23 14:33 *rsyslog.d*

drwxrwsr-x  8 weewx weewx  4096 Mar 23 14:33 *skins*

drwxrwsr-x  2 weewx weewx  4096 Mar 23 14:33 *systemd*

drwxrwsr-x  2 weewx weewx  4096 Mar 23 14:33 *udev*

-rw-rw-r--  1 weewx weewx 19467 Mar 23 14:33 weewx.conf

-rw-rw-r--  1 weewx weewx 19463 Feb  9 23:03 weewx.conf-5.0.2

Note how all files are owned by user "weewx", group "weewx". Because of
this, they can be modified by anyone in the group "weewx". The install
process makes sure that you are in that group. To check: just type
"groups". Here's what I get when I try it in the Ubuntu virtual machine:

*ubuntu@fit-bushbuck*:*~*$ groups

ubuntu adm dialout cdrom floppy sudo audio dip video plugdev netdev lxd
weewx

Note the user weewx at the end. See if you get something similar. If not,
try logging back out, then back in.

Then try your reconfigure again.

-tk

On Sat, Mar 23, 2024 at 2:26 PM Daniel Fourlas  wrote:

> You can register the station on weewx.com, where it will be included in a
> map. If you choose to register, you will also need a unique URL to
> identify
> the station (such as a website, or a WeatherUnderground link).
> register this station (y/n)? [n] n
> Saving configuration file /etc/weewx/weewx.conf
> Traceback (most recent call last):
>   File "/usr/lib/python3.9/shutil.py", line 806, in move
> os.rename(src, real_dst)
> PermissionError: [Errno 13] Permission denied: '/etc/weewx/weewx.conf' ->
> '/etc/weewx/weewx.conf.20240323232454'
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/usr/share/weewx/weectl.py", line 74, in 
> main()
>   File "/usr/share/weewx/weectl.py", line 66, in main
> namespace.func(namespace)
>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
> namespace.action_func(config_dict, namespace)
>   File "/usr/share/weewx/weectllib/station_cmd.py", line 311, in
> reconfigure_station
> weectllib.station_actions.station_reconfigure(config_dict=config_dict,
>   File "/usr/share/weewx/weectllib/station_actions.py", line 183, in
> station_reconfigure
> backup_path = weecfg.save(config_dict, config_dict['config_path'], not
> no_backup)
>   File "/usr/share/weewx/weecfg/__init__.py", line 224, in save
> backup_path = weeutil.weeutil.move_with_timestamp(config_path)
>   File "/usr/share/weewx/weeutil/weeutil.py", line 1697, in
> move_with_timestamp
> shutil.move(path, newpath)
>   File "/usr/lib/python3.9/shutil.py", line 820, in move
> copy_function(src, real_dst)
>   File "/usr/lib/python3.9/shutil.py", line 435, in copy2
> copyfile(src, dst, follow_symlinks=follow_symlinks)
>   File "/usr/lib/python3.9/shutil.py", line 264, in copyfile
> with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
> PermissionError: [Errno 13] Permission denied:
> '/etc/weewx/weewx.conf.20240323232454'
>
> --
> 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/c79ed39a-c813-4253-b225-89d8db8dd568n%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/CAPq0zEA-7q0cn%3DN%3DO69za73udZ82Cf%2B14O9qyTgp3ONuX-HOwg%40mail.gmail.com.

Re: [weewx-user] Wunderground uploads using wunderfixer

[Tom Keffer]

Good to know! So, it appears the WU will allow postdating of up to 4 hours.

On Thu, Mar 21, 2024 at 7:42 PM 'Andy Peterman' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Strange, I'm still running 4.10.2 and just used wunderfixer
> successfully.  Our Internet was down for about 3 hours, I ran wunderfixer,
> and it filled in the entire period.  Also, last weekend weewx hung right
> after the time change (not sure why, but that's another problem) and when I
> got it going again, I had about a 4 hour gap.  Once again, I ran
> wunderfixer and it filled in the 20+ entries that were missing.  It was a
> while before the data showed up, but I checked and it's definitely there.
>
> Are you sure that Weather Underground has removed this feature?
>
> On Tuesday, October 10, 2023 at 5:33:19 PM UTC-7 Tom Keffer wrote:
>
>> Thanks for verifying what we've always suspected. I'm actually surprised
>> they responded at all!
>>
>> For just this reason we've dropped wunderfixer from V5.
>>
>> On Tue, Oct 10, 2023 at 2:16 PM Ernest Jillson  wrote:
>>
>>> Good afternoon group.
>>>
>>> I emailed Weather Underground support yesterday about backfilling
>>> observations after having no internet for two days. Here was the response:
>>>
>>> "Thank you for being so kind as to want to backfill your station's
>>> data.  But because of the quality control process we have in place, data
>>> that is more than an hour old is discarded.  So the upload is a success,
>>> but it will never appear on the site.
>>>
>>> Please let me know if you have any additional questions.  Thank you for
>>> being part of the Weather Underground community!
>>>
>>> --Victoria"
>>>
>>> While I did reply back and ask if that feature would be restored at any
>>> time in the future, I think we can call this process dead. It sounds like
>>> wunderfixer will still work, though, for data less than 1 hour old.
>>>
>>> Ernie
>>>
>>> --
>>> 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/CAC5oUmOeLccyR-Jng%2BZCQBXbfixHNnZCevPJd_0CrwK4GjF%3DRw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/weewx-user/CAC5oUmOeLccyR-Jng%2BZCQBXbfixHNnZCevPJd_0CrwK4GjF%3DRw%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/b4276305-cc25-4271-a7ce-0762b1d8c2c5n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/b4276305-cc25-4271-a7ce-0762b1d8c2c5n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEBZ_Se3MDa0NYS4sxCy2Liyh%3DKV2PDrMdyLqF%3DPkuNsPw%40mail.gmail.com.

Re: [weewx-user] Power failure on the Raspberry

[Tom Keffer]

>From the log, it looks like the Vantage driver is not downloading new data
from the logger. This is usually the sign of corrupt memory in the logger.

See the section *Corrupt station memory
*
in
the wiki for how to clear it.

On Wed, Mar 20, 2024 at 11:02 AM geni08...@gmail.com <
geni0815.0...@gmail.com> wrote:

> The wrong time when switching on has caused a problem.
> How can I fix this?
> Debug log is attached
> I have stopped the service
>
>
> --
> 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/f0b17e2f-151b-4fea-938f-0d1423ee7914n%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/CAPq0zEC-JMZpaEVJ7nq6%3DjCq%2B%2B4wDEbMjfCOEQzMM9tZfB1C5g%40mail.gmail.com.

Re: [weewx-user] Re: Failed new install

[Tom Keffer]

I think Michael is on the right track. You may have typed "feet" instead of
"foot".

Debian remembers your prior responses, so now you have a bad response in
its database and that's why your stuck. To purge the database, do this


*  sudo echo PURGE | debconf-communicate weewx*

then start all over.


On Wed, Mar 20, 2024 at 11:54 AM 'michael.k...@gmx.at' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Just guessing by the error message:
>
> weectl.py: error: unrecognized arguments: feet,foot
>
> https://weewx.com/docs/5.0/reference/skin-options/units/?h=singular#groups
> Note that the measurement unit is always specified in the singular. That
> is, specify degree_C or foot, not degrees_C or feet.
>
>
>
> Ron Walker schrieb am Mittwoch, 20. März 2024 um 19:24:41 UTC+1:
>
>> I have been through the forum looking for this issue , but have not seen
>> this issue addressed.
>>
>> I;m trying to install weewx 5.02 on a fresh install of Debian Buster on a
>> Raspberry Pi 3.  When I attempt to install weewx, I get the following:
>>
>> ron@WeatherPi5:~ $ wget -qO - https://weewx.com/apt/weewx-python3.list |
>> sudo tee /etc/apt/sources.list.d/weewx.list
>> deb [arch=all] http://weewx.com/apt/python3 buster main
>> ron@WeatherPi5:~ $ sudo apt update
>> Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
>> Get:2 http://weewx.com/apt/python3 buster InRelease [4,252 B]
>>
>> Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
>>
>> Get:4 http://weewx.com/apt/python3 buster/main all Packages [4,988 B]
>> Fetched 9,240 B in 2s (5,992 B/s)
>> Reading package lists... Done
>> Building dependency tree... Done
>> Reading state information... Done
>> All packages are up to date.
>> ron@WeatherPi5:~ $ sudo apt install weewx
>> Reading package lists... Done
>> Building dependency tree... Done
>> Reading state information... Done
>> The following package was automatically installed and is no longer
>> required:
>>   libfuse2
>> Use 'sudo apt autoremove' to remove it.
>> The following additional packages will be installed:
>>   python3-cheetah python3-configobj python3-ephem python3-usb
>> Suggested packages:
>>   python-cheetah-doc python3-markdown python3-memcache
>> python-configobj-doc
>>   sqlite ftp httpd
>> The following NEW packages will be installed:
>>   python3-cheetah python3-configobj python3-ephem python3-usb weewx
>> 0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
>> Need to get 2,370 kB of archives.
>> After this operation, 9,616 kB of additional disk space will be used.
>> Do you want to continue? [Y/n] y
>> Get:2 http://weewx.com/apt/python3 buster/main all weewx all 5.0.2-1
>> [1,556 kB]
>> Get:1 http://mirror.us.leaseweb.net/raspbian/raspbian bullseye/main
>> armhf python3-configobj all 5.0.6-4 [35.8 kB]
>> Get:3 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf
>> python3-cheetah armhf 3.2.6-1+b1 [142 kB]
>> Get:4 http://mirror.us.leaseweb.net/raspbian/raspbian bullseye/main
>> armhf python3-usb all 1.0.2-2 [38.9 kB]
>> Get:5 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf
>> python3-ephem armhf 3.7.7.1-1+b1 [596 kB]
>> Fetched 2,370 kB in 2s (1,376 kB/s)
>> Preconfiguring packages ...
>> Selecting previously unselected package python3-configobj.
>> (Reading database ... 173112 files and directories currently installed.)
>> Preparing to unpack .../python3-configobj_5.0.6-4_all.deb ...
>> Unpacking python3-configobj (5.0.6-4) ...
>> Selecting previously unselected package python3-cheetah.
>> Preparing to unpack .../python3-cheetah_3.2.6-1+b1_armhf.deb ...
>> Unpacking python3-cheetah (3.2.6-1+b1) ...
>> Selecting previously unselected package python3-usb.
>> Preparing to unpack .../python3-usb_1.0.2-2_all.deb ...
>> Unpacking python3-usb (1.0.2-2) ...
>> Selecting previously unselected package python3-ephem.
>> Preparing to unpack .../python3-ephem_3.7.7.1-1+b1_armhf.deb ...
>> Unpacking python3-ephem (3.7.7.1-1+b1) ...
>> Selecting previously unselected package weewx.
>> Preparing to unpack .../archives/weewx_5.0.2-1_all.deb ...
>> Unpacking weewx (5.0.2-1) ...
>> Setting up python3-usb (1.0.2-2) ...
>> Setting up python3-ephem (3.7.7.1-1+b1) ...
>> Setting up python3-cheetah (3.2.6-1+b1) ...
>> Setting up python3-configobj (5.0.6-4) ...
>> Setting up weewx (5.0.2-1) ...
>> Using weewx:weewx as user:group
>> Creating /etc/default/weewx
>> usage: weectl.py -v|--version
>>weectl.py -h|--help
>>weectl.py database --help
>>weectl.py debug --help
>>weectl.py device --help
>>weectl.py extension --help
>>weectl.py import --help
>>weectl.py report --help
>>weectl.py station --help
>> weectl.py: error: unrecognized arguments: feet,foot
>> dpkg: error processing package weewx (--configure):
>>  installed weewx package post-installation script subprocess returned
>> error exit
>>  status 2
>> Processing triggers for man-db (2.9.4-2) ...
>> Errors were encountered while processing:
>>  

Re: [weewx-user] Re: Problem during fixing of potential corrupt database

[Tom Keffer]

If you say the problem is in the database and the database cannot be
recovered, I'm not sure there is anything we can offer. What are you
looking for from the group?

Hopefully you have a backup database.

On Wed, Mar 20, 2024 at 5:55 AM 'Michael Waldor' via weewx-user <
weewx-user@googlegroups.com> wrote:

> weewx itself works without problems - it can add new entries into
> weewx.sdb, and it'S running  right now.
>
> But when trying to manually tweak weewx.sdb using sqlite3 commands,
> sqlite3 complains. Using .recover seems to make it worse - its sql output
> contains some completely broken lines with datetime being 7 or 74 or
> unprintable bnary data. Clearly weewxd rejects to use that "recovered"
> weewx.sdb.
>
> Currently I try to follow
> https://groups.google.com/g/weewx-user/c/PJuWj35o8TM
> Luckily the transformation process should run for ~30min (data is stored
> on a SSD).
>
> But howto identify the location of a broken weewx.sdb? E.g. if I try to
> run the sqlite3 command
> select date(datetime, 'unixepoch', 'localtime') from archive;
> It outputs data till 2018-03-31. And then there is an sqlite3 error
> message. Only the date conversion seems to fail. If I stay with integer
> datetime all data seems to be accessible.
>
> Tom Keffer schrieb am Mittwoch, 20. März 2024 um 13:28:57 UTC+1:
>
>> This could be anything. We will need to see more of the log to tell. For
>> example, you could be asking for a date one month after January 30.
>>
>> Set debug=1, restart weewxd, post the log from startup through the error.
>>
>> On Wed, Mar 20, 2024 at 3:57 AM 'Michael Waldor' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>>> Sadly those mysterious rows only appear AFTER .recover,  they appear
>>> within weewx.sql.
>>> The failing command is
>>>
>>> SELECT count(*)
>>> FROM archive
>>> WHERE
>>>   date(datetime, 'unixepoch', 'localtime')
>>>   between '2024-03-15' and '2024-03-15';
>>>
>>> But that command works fine AFTER .recover.
>>>
>>> The error message from weewxd clearly indicates wrong datetime:
>>>
>>> Mär 20 11:34:37 imurr9 weewxd[15172]: CRITICAL __main__: 
>>>  last_d = datetime.date.fromtimestamp(weeutil.weeutil.startOfArchiveDay(
>>> Mär 20 11:34:37 imurr9 weewxd[15172]: time_dt =
>>> datetime.datetime.fromtimestamp(time_ts)
>>> Mär 20 11:34:37 imurr9 weewxd[15172]: OverflowError: timestamp out of
>>> range for platform time_t
>>> Mär 20 11:34:37 imurr9 weewxd[15172]: CRITICAL __main__: 
>>>  File "/usr/share/weewx/weeutil/weeutil.py", line 1196, in startOfArchiveDay
>>> Mär 20 11:34:37 imurr9 weewxd[15172]: CRITICAL __main__: 
>>>  time_dt = datetime.datetime.fromtimestamp(time_ts)
>>> Mär 20 11:34:37 imurr9 weewxd[15172]: CRITICAL __main__: 
>>>  OverflowError: timestamp out of range for platform time_t
>>> Mär 20 11:34:37 imurr9 weewxd[15172]: CRITICAL __main__: 
>>>  Exiting
>>> Michael Waldor schrieb am Mittwoch, 20. März 2024 um 10:43:13 UTC+1:
>>>
>>>> I do have a first idea: There are entries within weewx.sdb where
>>>> datetime is 0 or 7. Those values clearly are no valid timestamps.
>>>> I'll proceed in that direction ...
>>>>
>>>> Michael Waldor schrieb am Mittwoch, 20. März 2024 um 10:04:57 UTC+1:
>>>>
>>>>> Some days ago I've stopped weewx for roughly one day (I did change the
>>>>> GPIO connections of my raspberry pi4). Now I wanted to insert some data
>>>>> into my weewx.sdb from that timespan.
>>>>>
>>>>> When trying some sqlite3 commands (on a local copy of weewx.sdb - as
>>>>> an exercise a simple count) sqlite3 failed with corrupt database. OK, can
>>>>> imagine that that might have happened sometimes during the last 5 years.
>>>>> Thus I tried to rebuild my database by
>>>>>
>>>>> mv weewx.sdb weewx_corrupt.sdb
>>>>> sqlite3 weewx_corrupt.sdb .recover > weewx.sql
>>>>> sqlite3 weewx.sdb < weewx.sql
>>>>>
>>>>> Now my sqlite3 commands worked as expected, i.e. the newly created
>>>>> weewx.sdb seemed to be fixed. Keep in mind that I did not modify 
>>>>> weewx.sql.
>>>>> Thus a potential error might still have "survived" within the newly 
>>>>> created
>>>>> weewx.sdb.
>>>>>
>>>>> I then checked the modified weew

Re: [weewx-user] Re: Problem during fixing of potential corrupt database

[Tom Keffer]

This could be anything. We will need to see more of the log to tell. For
example, you could be asking for a date one month after January 30.

Set debug=1, restart weewxd, post the log from startup through the error.

On Wed, Mar 20, 2024 at 3:57 AM 'Michael Waldor' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Sadly those mysterious rows only appear AFTER .recover,  they appear
> within weewx.sql.
> The failing command is
>
> SELECT count(*)
> FROM archive
> WHERE
>   date(datetime, 'unixepoch', 'localtime')
>   between '2024-03-15' and '2024-03-15';
>
> But that command works fine AFTER .recover.
>
> The error message from weewxd clearly indicates wrong datetime:
>
> Mär 20 11:34:37 imurr9 weewxd[15172]: CRITICAL __main__: 
>  last_d = datetime.date.fromtimestamp(weeutil.weeutil.startOfArchiveDay(
> Mär 20 11:34:37 imurr9 weewxd[15172]: time_dt =
> datetime.datetime.fromtimestamp(time_ts)
> Mär 20 11:34:37 imurr9 weewxd[15172]: OverflowError: timestamp out of
> range for platform time_t
> Mär 20 11:34:37 imurr9 weewxd[15172]: CRITICAL __main__: File
> "/usr/share/weewx/weeutil/weeutil.py", line 1196, in startOfArchiveDay
> Mär 20 11:34:37 imurr9 weewxd[15172]: CRITICAL __main__: 
>  time_dt = datetime.datetime.fromtimestamp(time_ts)
> Mär 20 11:34:37 imurr9 weewxd[15172]: CRITICAL __main__: 
>  OverflowError: timestamp out of range for platform time_t
> Mär 20 11:34:37 imurr9 weewxd[15172]: CRITICAL __main__:   Exiting
> Michael Waldor schrieb am Mittwoch, 20. März 2024 um 10:43:13 UTC+1:
>
>> I do have a first idea: There are entries within weewx.sdb where datetime
>> is 0 or 7. Those values clearly are no valid timestamps.
>> I'll proceed in that direction ...
>>
>> Michael Waldor schrieb am Mittwoch, 20. März 2024 um 10:04:57 UTC+1:
>>
>>> Some days ago I've stopped weewx for roughly one day (I did change the
>>> GPIO connections of my raspberry pi4). Now I wanted to insert some data
>>> into my weewx.sdb from that timespan.
>>>
>>> When trying some sqlite3 commands (on a local copy of weewx.sdb - as an
>>> exercise a simple count) sqlite3 failed with corrupt database. OK, can
>>> imagine that that might have happened sometimes during the last 5 years.
>>> Thus I tried to rebuild my database by
>>>
>>> mv weewx.sdb weewx_corrupt.sdb
>>> sqlite3 weewx_corrupt.sdb .recover > weewx.sql
>>> sqlite3 weewx.sdb < weewx.sql
>>>
>>> Now my sqlite3 commands worked as expected, i.e. the newly created
>>> weewx.sdb seemed to be fixed. Keep in mind that I did not modify weewx.sql.
>>> Thus a potential error might still have "survived" within the newly created
>>> weewx.sdb.
>>>
>>> I then checked the modified weewx.sdb copied into /var/lib/weewx (weewx
>>> itself was NOT running) with
>>>
>>> weectl database check
>>>
>>> and got no error messages. But weewxd did not like that modified
>>> weewx.sdb. It reports "OverflowError: timestamp out of range for ..." when
>>> starting weewx.
>>>
>>> To me it's difficult to tell
>>> 1. whether my original weewx.sdb is corrupt at all (weewxd works fine)
>>> 2. if it's corrupt howto fix it.
>>>
>>> Hope somebody might have a suggestion, 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/b00628cf-ebf4-4fc2-a8bb-a193447e9476n%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/CAPq0zEBB5V2gC5P9wHoCp2%3D6XWNHjpyGf1OQGSHx8P7Xqf-3jA%40mail.gmail.com.

Re: [weewx-user] Problem after downgrading

[Tom Keffer]

Please set debug=1, then restart weewx. Post the log from startup to crash.

The startup gives important clues on where weewxd thinks things are located.

-tk

On Sun, Mar 17, 2024 at 12:08 PM George Nimrodel <
george.tselepi...@gmail.com> wrote:

> Hello everyone,
>
> I encountered an issue with my installation following an update from
> version 4.10.2 to 5.0.2 (unfortunately, no logs were retained).
> Consequently, I attempted to revert to the previous version.
>
> However, even after the downgrade, I still encountered difficulties:
>
> ● weewx.service - WeeWX
>Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor
> preset: enabled)
>Active: failed (Result: exit-code) since Sat 2024-03-16 12:24:07 EET; 1
> day 6h ago
>  Docs: https://weewx.com/docs
>   Process: 411 ExecStart=/usr/bin/weewxd /etc/weewx/weewx.conf
> (code=exited, status=1/FAILURE)
>  Main PID: 411 (code=exited, status=1/FAILURE)
>
>
> Mar 17 18:43:50 edessa weewxd[419]: Traceback (most recent call last):
> Mar 17 18:43:50 edessa weewxd[419]:   File "/usr/share/weewx/weewxd", line
> 29, in 
> Mar 17 18:43:50 edessa weewxd[419]: import user.extensions
> Mar 17 18:43:50 edessa weewxd[419]: ModuleNotFoundError: No module named
> 'user.extensions'
> Mar 17 18:43:50 edessa systemd[1]: weewx.service: Main process exited,
> code=exited, status=1/FAILURE
> Mar 17 18:43:50 edessa systemd[1]: weewx.service: Failed with result
> 'exit-code'.
>
> This occurred on a Raspberry Pi 3b+ running version 4.10.2 with the BCRobotics
> driver .
>
> Any assistance would be greatly appreciated. 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/70b373c6-8597-487f-a8f8-457275c3a510n%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/CAPq0zECYLMxB_WYaXrLbSvoi5TAjMP1cT_eBU8ZsJFu-8v1C%3DQ%40mail.gmail.com.

Re: [weewx-user] How to handle sensor data that doesn't come at set times

[Tom Keffer]

You have many single data points, separated with long stretches of nulls
--- no lines. That's why line_gap_fraction isn't working.

By design, WeeWX drivers don't cache data. See the guidelines
<https://www.weewx.com/docs/5.0/custom/drivers/#general-guidelines> for
writing drivers.

However, you could write a simple service that retains the last value and
uses it if a null value is seen. Perhaps up to a maximum time. But, there's
nothing like that in WeeWX.

On Thu, Mar 14, 2024 at 6:54 PM Greg from Oz  wrote:

> Here is a snippet of the database:
> select dateTime ,inTemp, inHumidity, pressure from archive where dateTime
> >= 1710459900 ;
> ++++---+
> | dateTime   | inTemp | inHumidity | pressure  |
> ++++---+
> | 1710459900 |  23.99 | 54.016 | 968.35003 |
> | 1710460200 |   NULL |   NULL | 968.3142857142858 |
> | 1710460500 |   NULL |   NULL | 968.31667 |
> | 1710460800 |   NULL |   NULL | 968.21667 |
> | 1710461100 |   NULL |   NULL | 968.15834 |
> | 1710461400 |  24.26 |  53.23 | 968.10001 |
> | 1710461700 |   24.5 |  53.34 | 968.08335 |
> | 1710462000 |   NULL |   NULL | 968.14168 |
> | 1710462300 |   NULL |   NULL | 968.09167 |
> | 1710462600 |   NULL |   NULL | 968.1285714285715 |
> | 1710462900 |   NULL |   NULL |   968.225 |
> | 1710463200 |  25.01 | 52.795 | 968.1 |
> | 1710463500 |   NULL |   NULL | 968.10835 |
> | 1710463800 |  25.52 | 51.7549995 | 968.1357142857144 |
> | 1710464100 |   NULL |   NULL | 968.10832 |
> | 1710464400 |   NULL |   NULL | 968.09167 |
> | 1710464700 |   NULL |   NULL | 968.00832 |
> | 1710465000 |  25.82 |  50.49 | 968.0142857142857 |
> | 1710465300 |  26.03 | 50.535 | 967.95834 |
> | 1710465600 |   NULL |   NULL | 967.83335 |
> | 1710465900 |   NULL |   NULL | 967.80001 |
> | 1710466200 |   NULL |   NULL |967.75 |
> | 1710466500 |  26.54 | 50.095 | 967.68334 |
> | 1710466800 |   NULL |   NULL | 967.69166 |
> | 1710467100 |   NULL |   NULL | 967.6 |
> | 1710467400 |   NULL |   NULL | 967.75001 |
> +++--------+---+
> 26 rows in set (0.000 sec)
>
> On Friday 15 March 2024 at 08:39:12 UTC+11 Tom Keffer wrote:
>
>> You may just have the option line_gap_fraction
>> <https://www.weewx.com/docs/5.0/reference/skin-options/imagegenerator/#line_gap_fraction>
>> set too low.
>>
>> On Thu, Mar 14, 2024 at 2:18 PM Greg from Oz  wrote:
>>
>>> Hi,
>>> I have removed my fineoffset usb and replaced it with SDR but the
>>> outside fine offset station doesn't sent inside temperature, inside
>>> humidity or barometer.
>>>
>>> I have added a BME280 sensor and can get the barometer readings every 30
>>> seconds and that is working and graphing OK.
>>>
>>> I have a zigbee battery powered device that I am using to get the inside
>>> temperature and inside humidity but I cannot get the graphs to show a solid
>>> line nor can I get the readings to consistently show on my web page because
>>> those readings come in a random times.
>>>
>>> Is there any way to make the readings "stick" until a new reading is
>>> received so the graphs look right and the readings are always on the web
>>> page?
>>>
>>> Look at the inside temperature graph on my web page to see what I mean:
>>> https://weather.ubeaut.work/
>>>
>>> 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/555c8101-8f4f-45ad-8dc7-03a7b2fbb7ean%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/555c8101-8f4f-45ad-8dc7-03a7b2fbb7ean%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group

Re: [weewx-user] WeeWx 5.0 problem on Ubuntu 23.10 after upgrade

[Tom Keffer]

Hello,

What version were you upgrading from? It appears to be an older version
that does not have a [[Defaults]] section (introduced V3.9).

On Fri, Mar 15, 2024 at 4:38 AM danvill...@bcsdk12.org <
danville.sc...@bcsdk12.org> wrote:

> *I am not able to upgrade after upgrading Weewx 5.0 on Ubuntu 23.10*
> *Any thoughts are greatly appreciated!*
>
> Setting up weewx (5.0.2-1) ...
> Using weewx:weewx as user:group
> Saving old defaults to /etc/default/weewx-20240315073503
> Creating /etc/default/weewx
> Using debconf configuration values from previous install
> Using configuration file /etc/weewx/weewx.conf
> Processing configuration file /etc/weewx/weewx.conf
> Traceback (most recent call last):
>   File "/usr/share/weewx/weectl.py", line 74, in 
> main()
>   File "/usr/share/weewx/weectl.py", line 66, in main
> namespace.func(namespace)
>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
> namespace.action_func(config_dict, namespace)
>   File "/usr/share/weewx/weectllib/station_cmd.py", line 311, in
> reconfigure_station
> weectllib.station_actions.station_reconfigure(config_dict=config_dict,
>   File "/usr/share/weewx/weectllib/station_actions.py", line 164, in
> station_reconfigure
> config_config(config_dict,
>   File "/usr/share/weewx/weectllib/station_actions.py", line 206, in
> config_config
> config_units(config_dict, unit_system=unit_system, no_prompt=no_prompt)
>   File "/usr/share/weewx/weectllib/station_actions.py", line 384, in
> config_units
> config_dict['StdReport']['Defaults']['unit_system'] = final_unit_system
> 
>   File "/usr/lib/python3/dist-packages/configobj/__init__.py", line 553,
> in __getitem__
> val = dict.__getitem__(self, key)
>   ^^^
> KeyError: 'Defaults'
> dpkg: error processing package weewx (--configure):
>  installed weewx package post-installation script subprocess returned
> error exit status 1
> Errors were encountered while processing:
>  weewx
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> --
> 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/5c62a643-04e9-4a16-9826-12dbb00c0de0n%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/CAPq0zEAvBzL7gNygSEREc%2BT8-2fvcBCn%2BO_pmdn7E1C39bGeyQ%40mail.gmail.com.

Re: [weewx-user] How to handle sensor data that doesn't come at set times

[Tom Keffer]

You may just have the option line_gap_fraction

set too low.

On Thu, Mar 14, 2024 at 2:18 PM Greg from Oz  wrote:

> Hi,
> I have removed my fineoffset usb and replaced it with SDR but the outside
> fine offset station doesn't sent inside temperature, inside humidity or
> barometer.
>
> I have added a BME280 sensor and can get the barometer readings every 30
> seconds and that is working and graphing OK.
>
> I have a zigbee battery powered device that I am using to get the inside
> temperature and inside humidity but I cannot get the graphs to show a solid
> line nor can I get the readings to consistently show on my web page because
> those readings come in a random times.
>
> Is there any way to make the readings "stick" until a new reading is
> received so the graphs look right and the readings are always on the web
> page?
>
> Look at the inside temperature graph on my web page to see what I mean:
> https://weather.ubeaut.work/
>
> 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/555c8101-8f4f-45ad-8dc7-03a7b2fbb7ean%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/CAPq0zEB%3DKszGQfznMQHuvmHcPmQJiX7yYVh-%2BqfWfj5ZDucWMg%40mail.gmail.com.

Re: [weewx-user] USB/Serial permissions

[Tom Keffer]

Most likely you need to add the user "weewx" to the "dialout" group. See
the wiki section *add the weewx user to group defined on a device
.*


On Mon, Mar 11, 2024 at 4:13 PM Gord Snarr (GSFarm) 
wrote:

> New install on a fresh RPI4B, new card etc.
>
> Installation seems to go fine, but there seems to be a permissions issue
> with the USB0 port I am using for the USB -> serial adapter to the serial
> console on the Davis VP.
>
> Log as follows:
>
> × weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; preset:
> enabled)
>  Active: failed (Result: exit-code) since Mon 2024-03-11 17:10:35 CDT;
> 38min ago
>Duration: 342ms
>Docs: https://weewx.com/docs
> Process: 2511 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited,
> status=4)
>Main PID: 2511 (code=exited, status=4)
> CPU: 343ms
>
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL weewx.engine: 
>
> ^
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL weewx.engine: 
>File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 244, in
> __init__
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL weewx.engine: 
>  self.open()
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL weewx.engine: 
>File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 325,
> in open
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL weewx.engine: 
>  raise SerialException(msg.errno, "could not open port {}:
> {}".format(self._port, msg))
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL weewx.engine: 
>  serial.serialutil.SerialException: [Errno 13] could not open port
> /dev/ttyUSB0: [Errno 13] Permission denied: '/dev/ttyUSB0'
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL __main__: Unable to
> load driver: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13]
> Permission denied: '/dev/ttyUSB0'
> Mar 11 17:10:35 raspberrypi weewxd[2511]: CRITICAL __main__: 
>  Exiting...
> Mar 11 17:10:35 raspberrypi systemd[1]: weewx.service: Main process
> exited, code=exited, status=4/NOPERMISSION
> Mar 11 17:10:35 raspberrypi systemd[1]: weewx.service: Failed with result
> 'exit-code'.
> ~
>
> VER:
> Linux raspberrypi 6.6.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1
> (2024-03-07) aarch64
>
> HRDWR
> RPI-4B
> Davis Vantage Pro (not the II).
> Weewx version (what ever downloaded today using "apt install weewx").
> Think it's 5.0.2.
>
> What should the permissions be set to the port, or user added? Is it
> weewxd, root, pi?
> SHould I change the user in the weewx.conf, or change the chmod the port?
>
> Maybe I should have started with an older weewx version and upgraded? This
> may have been sorted out already previously.
> Thankx in advance,
> -G.
>
> --
> 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/da82a39f-9cad-4b52-941f-b6529efb7c05n%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/CAPq0zECgoSW2MGbtBtuXfbP61S%2B%2BoQMLv_-R9iY525X6vySbeg%40mail.gmail.com.

Re: [weewx-user] No column extraHumid3, though Interceptor maps to this column

[Tom Keffer]

See the manual section on weectl database add-column

.

On Mon, Mar 11, 2024 at 12:53 PM Invisible Man 
wrote:

> Hi,
> In WeeWx, if I inspect the archive table, there is an extraTemp3, but no
> extraHumid3.
> Why is that? And is it possible to get a extraHumid3? Indeed, I have a
> sensor 3 which provides both temperature and humidity.
>
> ```
> sqlite> .schema archive
> CREATE TABLE archive (`dateTime` INTEGER NOT NULL UNIQUE PRIMARY KEY,
> `usUnits` INTEGER NOT NULL, `interval` INTEGER NOT NULL, `barometer` REAL,
> `pressure` REAL, `altimeter` REAL, `inTemp` REAL, `outTemp` REAL,
> `inHumidity` REAL, `outHumidity` REAL, `windSpeed` REAL, `windDir` REAL,
> `windGust` REAL, `windGustDir` REAL, `rainRate` REAL, `rain` REAL,
> `dewpoint` REAL, `windchill` REAL, `heatindex` REAL, `ET` REAL, `radiation`
> REAL, `UV` REAL, `extraTemp1` REAL, `extraTemp2` REAL, `extraTemp3` REAL,
> `soilTemp1` REAL, `soilTemp2` REAL, `soilTemp3` REAL, `soilTemp4` REAL,
> `leafTemp1` REAL, `leafTemp2` REAL, `extraHumid1` REAL, `extraHumid2` REAL,
> `soilMoist1` REAL, `soilMoist2` REAL, `soilMoist3` REAL, `soilMoist4` REAL,
> `leafWet1` REAL, `leafWet2` REAL, `rxCheckPercent` REAL, `txBatteryStatus`
> REAL, `consBatteryVoltage` REAL, `hail` REAL, `hailRate` REAL,
> `heatingTemp` REAL, `heatingVoltage` REAL, `supplyVoltage` REAL,
> `referenceVoltage` REAL, `windBatteryStatus` REAL, `rainBatteryStatus`
> REAL, `outTempBatteryStatus` REAL, `inTempBatteryStatus` REAL);
> ```
>
> Note I am using WeeWx 4.10.2 with Interceptor.
> My weather station provides a humidity_3 (63%) which gets mapped by
> Interceptor to extraHumid3 (see below).
>
>
> Mar 11 20:49:37 vegan weewx[21485] DEBUG user.interceptor: raw packet:
> {'dateTime': 1710186576, 'usUnits': 1, 'temperature_in': 69.1,
> 'humidity_in': 63.0, 'pressure': 29.477, 'temperature_out': 46.6,
> 'humidity_out': 98.0, 'wind_dir': 333.0, 'wind_speed': 0.67, 'wind_gust':
> 1.12, 'solar_radiation': 0.0, 'uv': 0.0, 'rain_rate': 0.0, 'rain_total':
> 22.039, 'temperature_3': 68.4, 'humidity_3': 63.0, 'soil_moisture_1': 50.0,
> 'wn34_temperature_1': 51.1, 'wh65_battery': 0.0, 'wh25_battery': 0.0,
> 'battery_3': 0.0, 'soil_battery_1': 1.4, 'rain': 0.0}
> Mar 11 20:49:37 vegan weewx[21485] DEBUG user.interceptor: mapped packet:
> {'dateTime': 1710186576, 'usUnits': 1, 'pressure': 29.477, 'outHumidity':
> 98.0, 'inHumidity': 63.0, 'outTemp': 46.6, 'inTemp': 69.1, 'windSpeed':
> 0.67, 'windGust': 1.12, 'windDir': 333.0, 'radiation': 0.0, 'rain': 0.0,
> 'rainRate': 0.0, 'UV': 0.0, 'extraTemp2': 51.1, 'extraTemp3': 68.4,
> 'soilMoist1': 50.0, 'extraHumid3': 63.0}
>
> 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/43c77503-a0c6-467d-80a9-857af0ddb84cn%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/CAPq0zECtFWbGndqyJKJZKcn5Q18aUw1FvFuTBP8DJ4y5QGNj4A%40mail.gmail.com.

Re: [weewx-user] Re: Upgraded to 5.0.1, DB is updating but not reflecting

[Tom Keffer]

If I'm understanding correctly, you wish to publish to /var/www/html
directly, not /var/www/html/weewx. Without a log, it's hard to say what the
problem is, but I would guess it's  a permissions issue. On the theory that
it is, try this:

1. You've asked the report engine to generate *both* SeasonsReport
*and* Belchertown.
I doubt this is what you want. Disable the Seasons skin by setting
"enable=false" under [[SeasonsReport]].

2. Under [Belchertown], set

HTML=/var/www/html

3. Change permissions. By default, user 'weewx' owns /var/www/html/weewx,
*not* /var/www/html. To change:

*sudo chown -R weewx:weewx /var/www/html*

4. Restart weewx

If that doesn't work, you will have to include a log. See the wiki
article *Help!
Posting to weewx-user
* for how
to get a good log.

On Sun, Mar 10, 2024 at 8:15 PM Matt Johnson  wrote:

> Ok, update. I did a clean install of weewx 5.0.2 on new hardware, as it
> was time and if I am going to set this up for several more years of trouble
> free service this is the right way to do it.
>
> Anyway, I have everything working with Belchertown and mqtt EXCEPT I can't
> get WeeWx to publish Belchertown skin to var/www/html so it is accessible
> on port 80 for my website. For http://shakerweather.com I just get the
> NGINX confirmation page, which is in that folder as well as the weewx
> folder that has belchertown.
>
> I followed Pat's instructions to modify the weewx.conf so that HTML_ROOT =
> var/www/html but it simply won't generate the files there. In fact, I'm not
> sure where it publishes when I change the HTML_ROOT to var/www/html.
> According to Pat's instructions they should just generate at the next
> archive interval. When I make this change the directory at
> /weewx/belchertown stops updating as well unless I put the HTML_ROOT =
> var/www/html/weex/belchertown
>
> The only way I can see everything is by going to
> http://shakerweather.com/weewx/belchertown
>
> There must be something simple I am missing here. Anyone have any ideas?
>
> Here is my weewx conf that works publishing to
> http://shakerweather.com/weewx/belchertown. Again, if I make Pat's
> modifications to set the Belchertown HTML_ROOT to /var/www/html/ nothing
> happens.
>
>
> --
> #   This section specifies what reports, using which skins, to generate.
>
> [StdReport]
>
> # Where the skins reside, relative to WEEWX_ROOT
> SKIN_ROOT = skins
>
> # Where the generated reports should go, relative to WEEWX_ROOT
> HTML_ROOT = /var/www/html/weewx
>
> # Uncomment and change to override logging for reports.
> # log_success = True
> # log_failure = True
>
> # The database binding indicates which data should be used in reports.
> data_binding = wx_binding
>
> # Each of the following subsections defines a report that will be run.
> # See the customizing guide to change the units, plot types and line
> # colors, modify the fonts, display additional sensor data, and other
> # customizations. Many of those changes can be made here by overriding
> # parameters, or by modifying templates within the skin itself.
>
> [[SeasonsReport]]
> # The SeasonsReport uses the 'Seasons' skin, which contains the
> # images, templates and plots for the report.
> skin = Seasons
> enable = true
>
> [[SmartphoneReport]]
> # The SmartphoneReport uses the 'Smartphone' skin, and the images
> and
> # files are placed in a dedicated subdirectory.
> skin = Smartphone
> enable = false
> HTML_ROOT = /var/www/html/weewx/smartphone
>
> [[MobileReport]]
> # The MobileReport uses the 'Mobile' skin, and the images and files
> # are placed in a dedicated subdirectory.
> skin = Mobile
> enable = false
> HTML_ROOT = /var/www/html/weewx/mobile
>
> [[StandardReport]]
> # This is the old "Standard" skin. By default, it is not enabled.
> skin = Standard
> enable = false
>
> [[Belchertown]]
> skin = Belchertown
> HTML_ROOT = /var/www/html/weewx/belchertown
> enable = true
>
>
>
>
> On Wednesday, March 6, 2024 at 7:02:35 AM UTC-5 Matt Johnson wrote:
>
>> So 12 hours later it seems my site's 
>> Belchertown skin is not updating any of the data, it is all stuck in time
>> at 6:20pm last night when I did the update - forecast, almanac, charts all
>> frozen there. MQTT shows real time data for some elements. Database is
>> still updating leading me to believe the skin is simply not reflecting any
>> updates. I'll generate a log to see if it helps.
>>
>> On Tuesday, March 5, 2024 at 11:40:14 PM UTC-5 gjr80 wrote:
>>
>>> The first thing to do is to post a log extract so we can see exactly
>>> what is/is not going on. This wiki page
>>> 
>>> will help you to get 

Re: [weewx-user] Daily rain total and daylight saving time error.

[Tom Keffer]

op time (%d)"
> % (args[0], args[1]))
> Mar 10 03:00:17 weewx-server weewxd[4645]: ERROR weewx.cheetahgenerator:
>   ValueError: start time (1710057000) is greater than stop time
> (1710054000)
> Mar 10 03:00:17 weewx-server weewxd[4645]: INFO weewx.cheetahgenerator:
> Generated 0 files for report WEEWXtagsReport in 0.63 seconds
> Mar 10 03:00:18 weewx-server weewxd[4645]: INFO weewx.imagegenerator:
> Generated 21 images for report WEEWXtagsReport in 1.02 seconds
> Mar 10 03:00:18 weewx-server weewxd[4645]: INFO user.stackedwindrose:
> Generated 1 images for WEEWXtagsReport in 0.03 seconds
> Mar 10 03:00:20 weewx-server weewxd[4645]: INFO weewx.restx: PWSWeather:
> Published record 2024-03-10 03:00:00 EDT (1710054000)
> Mar 10 03:00:20 weewx-server weewxd[4645]: INFO weewx.cheetahgenerator:
> Generated 3 files for report ClientrawReport in 2.16 seconds
> Mar 10 03:00:24 weewx-server weewxd[4645]: INFO weewx.restx: WeatherCloud:
> Published record 2024-03-10 03:00:00 EDT (1710054000)
> Mar 10 03:00:34 weewx-server weewxd[4645]: INFO weewx.reportengine:
> ftpgenerator: Ftp'd 44 files in 13.57 seconds
>
>
>
> On Sunday, March 10, 2024 at 8:36:26 PM UTC-4 Tom Keffer wrote:
>
>> Let's see what's in the database. I don't know what kind of install you
>> did, but for a package install do this (you type *bold* text):
>>
>> *sqlite3 /var/lib/weewx/weewx.sdb*
>>
>>
>> for a pip install
>>
>> *sqlite3 ~/weewx-data/archive/weewx.sdb*
>>
>>
>> then see how much rain is in the archive records:
>>
>> sqlite> *select datetime(dateTime,'unixepoch','localtime'), rain from
>> archive where date(dateTime,'unixepoch','localtime')='2024-03-10';*
>>
>>
>> Do they look reasonable?
>>
>> Also, check the total amount of rain in both the main archive table, and
>> in the daily summaries:
>>
>> sqlite> *select sum(rain) from archive where
>> date(dateTime,'unixepoch','localtime')='2024-03-10';*
>> sqlite> *select sum from archive_day_rain where
>> date(dateTime,'unixepoch','localtime')='2024-03-10';*
>>
>>
>> What are the values? Do they match?
>>
>>
>> On Sun, Mar 10, 2024 at 10:00 AM Russell Swan 
>> wrote:
>>
>>> Hi, daylight saving time happened last night and my rain total
>>> ($day.rain.sum) for the day does not equal that on the Davis Vantage Pro2.
>>> The console reads 0.73" and weewx puts out 0.52". Interestingly, my Steel
>>> Gauges indicate the correct 0.73". I think an hour of rain was dropped.
>>>
>>> weewx version 5.02
>>>
>>> --
>>> 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/2a443e7a-da18-4a65-9eb2-b73f0e4744fan%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/2a443e7a-da18-4a65-9eb2-b73f0e4744fan%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/425b3e5c-1ddf-4b70-afc7-923fe668400dn%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/425b3e5c-1ddf-4b70-afc7-923fe668400dn%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEC%2BNemU6A%3DMEt_8B6wxapj2uKb7yyFwHyf0-Ko3YuiQhg%40mail.gmail.com.

Re: [weewx-user] Daily rain total and daylight saving time error.

[Tom Keffer]

Let's see what's in the database. I don't know what kind of install you
did, but for a package install do this (you type *bold* text):

*sqlite3 /var/lib/weewx/weewx.sdb*


for a pip install

*sqlite3 ~/weewx-data/archive/weewx.sdb*


then see how much rain is in the archive records:

sqlite> *select datetime(dateTime,'unixepoch','localtime'), rain from
archive where date(dateTime,'unixepoch','localtime')='2024-03-10';*


Do they look reasonable?

Also, check the total amount of rain in both the main archive table, and in
the daily summaries:

sqlite> *select sum(rain) from archive where
date(dateTime,'unixepoch','localtime')='2024-03-10';*
sqlite> *select sum from archive_day_rain where
date(dateTime,'unixepoch','localtime')='2024-03-10';*


What are the values? Do they match?


On Sun, Mar 10, 2024 at 10:00 AM Russell Swan 
wrote:

> Hi, daylight saving time happened last night and my rain total
> ($day.rain.sum) for the day does not equal that on the Davis Vantage Pro2.
> The console reads 0.73" and weewx puts out 0.52". Interestingly, my Steel
> Gauges indicate the correct 0.73". I think an hour of rain was dropped.
>
> weewx version 5.02
>
> --
> 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/2a443e7a-da18-4a65-9eb2-b73f0e4744fan%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/CAPq0zECpmqYhOj9hMJLV1ae7hLEOftJ4v51FN-vQ03tVyu7UfA%40mail.gmail.com.

Re: [weewx-user] [StdCalibrate][[Corrections]] check if obs_type is present

[Tom Keffer]

Honestly, with an expression that complicated, I would write a simple WeeWX
service.

On Sun, Mar 10, 2024 at 3:51 AM 'michael.k...@gmx.at' via weewx-user <
weewx-user@googlegroups.com> wrote:

> This one seems way better:
> [StdCalibrate]
>
> [[Corrections]]
> windSpeed = ws90_windSpeed if 'windSpeed' not in locals() else
> windSpeed if 'ws90_windSpeed' not in locals() else ws90_windSpeed if
> ws90_windSpeed > windSpeed else windSpeed
> windGust = ws90_windGust if 'windGust' not in locals() else
> windGust if 'ws90_windGust' not in locals() else ws90_windGust if
> ws90_windGust > windGust else windGust
> windDir = ws90_windDir if 'ws90_windDir' in locals() and
> ws90_windDir is not None else windDir
> michael.k...@gmx.at schrieb am Samstag, 9. März 2024 um 08:37:01 UTC+1:
>
>> Anyway, thank you for helping me with this one!
>>
>> For the record:
>>
>> I have two pieces of hardware, one is using a classic anemometer with
>> cups, the other one is an ultrasonic device. With very low wind speeds, the
>> classic one shows zero wind, while the ultrasonic one shows low, but very
>> plausible values. The ultrasonic one also doesn't freeze or gets blocked by
>> snow, because is has a heating. On the other hand, the ultrasonic device
>> often misses wind gusts and lacks accuracy in wet conditions.
>> In short, the closes approach to represent reality is: always use the
>> values from the sensor, which is showing the higher reading.
>> Also, the Wind direction of the ultrasonic device has a better resolution
>> and no vane that sometimes doesn't move, even in wind speeds, the classic
>> anemometer is rotating.
>> So the second thing is: always use windDir from the ultrasonic device.
>>
>> Both readings arrive in the same loop packet, their names are "windSpeed"
>> and "ws90_windSpeed" (the latter ultrasonic), together with their gust
>> speed and direction, except for situations, the sensor's data cannot be
>> received by the console. So my first approach
>>
>> [StdCalibrate]
>> [[Corrections]]
>> windSpeed = ws90_windSpeed if ws90 if ws90_windSpeed > windSpeed
>> else windSpeed
>> windGust = ws90_windGust if ws90_windGust > windGust else
>> windGust
>> windDir = ws90_windDir if ws90_windDir is not None else windDir
>>
>> is working, but only in cases, both of the readings are present.
>>
>> Yesterday, windSpeed (from the classic device) was missing, where
>> ws90_windSpeed was there. The result was, no windSpeed was recorded as at
>> all, due to a python NameError, which was silently ignored.
>>
>> try:
>> event.record[obs_type] = eval(self.corrections[obs_type], {'math': math},
>>   event.record)
>> except (TypeError, NameError):
>> pass
>>
>> So, if this should work as intended, we need to check if windSpeed is
>> there, or not.
>>
>> What I want is to
>>
>>- store whatever wind speed/gust is the higher, if both are present
>>- store whatever wind speed/gust, when only one is present
>>- store the ultrasonic wind direction if present, or else the other
>>one
>>
>> For now, I use these expressions, and the loop packets look good, and
>> there shouldn't be a need to check for both being present:
>>
>> [StdCalibrate]
>>
>> [[Corrections]]
>> # For each type, an arbitrary calibration expression can be
>> given.
>> # It should be in the units defined in the StdConvert section.
>> # Example:
>> #foo = foo + 0.2
>> windSpeed = ws90_windSpeed if 'windSpeed' not in locals() or
>> ws90_windSpeed > windSpeed else windSpeed
>> windGust = ws90_windGust if 'windGust' not in locals() or
>> ws90_windGust > windGust else windGust
>> windDir = ws90_windDir if 'ws90_windDir' in locals() and
>> ws90_windDir is not None else windDir
>>
>> I think this way I think I get my desired results, but after a long week
>> my brain is a bit overloaded. So if anybody with cognitive capacities left
>> could check if my expressions really make that much sense: very much
>> appreciated :)
>>
>> michael.k...@gmx.at schrieb am Samstag, 9. März 2024 um 08:15:24 UTC+1:
>>
>>> Actually
>>>
>>> *outTemp = 44 if outTemp in locals() else None*
>>>
>>>
>>> yields *None* when *outTemp * is there.
>>>
>>> Since we are looking for the key '*outTemp' *and not it'

Re: [weewx-user] PID file not created in version 5.0.2

[Tom Keffer]

I don't know what I can add to the comments I already made on the issues
list: the --pidfile option is only used if you use the --daemon option.

On Sat, Mar 9, 2024 at 2:19 PM silke  wrote:

> Hello,
>
> I recently made the switch to v5 and overall the migration was working
> quite smoothly, despite running many extensions and skins. I'm on Ubuntu
> and use DEB installation.
>
> The one thing that is not working yet is my weewx process health
> monitoring which is based on PID file. I cannot get weewx to create a PID
> file whatever I try. (in v4 this worked out of the box)
>
> I'm adding the --pidfile option to the systemd file, and it shows
> correctly in the process list:
>
> weewx 941451 51.1  8.7 1921212 1415068 ? Ssl  23:00   3:23 python3
> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf --pidfile
> /run/weewx/weewx.pid
>
> the folder /run/weewx is owned by weewx:weewx
>
> silke@enterprise:/etc/weewx$ ls -la /run/weewx/
> total 0
> drwxrwxr-x  2 weewx weewx   40 Mär  9 23:00 .
> drwxr-xr-x 50 root  root  1420 Mär  9 23:00 ..
>
> but still, no file is getting created upon restart.
>
> Anyone having an idea what I'm doing wrong?
>
> Thanks a lot, Silke
>
> --
> 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/fb454ef9-ae53-4211-bf15-283bd067c567n%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/CAPq0zEBDW6poBOygS%3D5eYNzFUe-jcP5EF7ETO%3D9XGjxcixRi2Q%40mail.gmail.com.

[weewx-user] REMINDER: upgrade from V5.0.0!

[Tom Keffer]

I see that there are still MANY users running V5.0.0!

This version has a serious bug that can *damage your operating system* if
you try to remove an extension.

Please upgrade ASAP!

-tk

-- 
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/CAPq0zEAzotgTwaAcvS0_JgeCtZLF3K8UOihxsxj2bzH%3D%2Bwfffw%40mail.gmail.com.

Re: [weewx-user] Weather Display and weewx

[Tom Keffer]

Nice station.

Did you try Matthew Wall's driver?
https://github.com/matthewwall/weewx-wxt5x0

Also, if it has an MQTT interface, you could integrate it into WeeWX that
way.

On Sat, Mar 9, 2024 at 6:42 AM 'Jon Fear' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Hi folks
>
> It is time for the silly question to be asked.
>
> I have a Vaisala WXT536 which is well supported under Weather Display
> whereas the support is limited here under weewx. Not a criticism given it
> is such a unique high value device which will have limited appeal.
>
> Is there a way of taking the WD output and using it in Weewx? There, It
> was a silly question!
>
> I don't really want to run a VM with WD on it but may have too. Either
> that or swap the Vaisala for something like a VP2...
>
> Thoughts?
>
> Jon , in the UK, an incredibly thick 2nd line engineer!
>
> --
> 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/1ce985cf-d298-45ac-80ef-ba336777f9f0n%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/CAPq0zEBVBS_iFVbLZhAYTe9HUWULX3Yb-Yd_p-pzo5JdQ8Ej1g%40mail.gmail.com.

Re: [weewx-user] [StdCalibrate][[Corrections]] check if obs_type is present

[Tom Keffer]

The facility uses the Python function eval
. A dictionary with
key 'math' and value the math module is passed in for *globals*. The record
is passed in for *locals*. So, you could use the expression

*outTemp = 44 if outTemp in locals() else None*




On Fri, Mar 8, 2024 at 3:33 PM Graham Eddy  wrote:

> oops, python syntax would be: expr if ops_tye in globals() else None
> *⊣GE⊢*
>
> On 9 Mar 2024, at 10:31 am, Graham Eddy  wrote:
>
> i think ' if obs_type in globals() then expr else None ' would work
> *⊣GE⊢*
>
> On 9 Mar 2024, at 9:13 am, 'michael.k...@gmx.at' via weewx-user <
> weewx-user@googlegroups.com> wrote:
>
> I think I remember that this has been asked before, how to check with an
> expression in Corrections, if an obs_type is present?
>
> --
> 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/ae1bbcf8-23b1-475e-8749-62286df24fb0n%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/0507D046-7EED-4A96-8F28-038B70BECEC7%40geddy.au
> 
> .
>

-- 
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/CAPq0zEAuuP-SCAMux5dsvxKPUDxP0b_W7gwH0zzf44xWcQb5uw%40mail.gmail.com.

Re: [weewx-user] [StdCalibrate][[Corrections]] check if obs_type is present

[Tom Keffer]

You can't check, but if the observation type is not present, the resultant
NameError exception is ignored.

On Fri, Mar 8, 2024 at 2:13 PM 'michael.k...@gmx.at' via weewx-user <
weewx-user@googlegroups.com> wrote:

> I think I remember that this has been asked before, how to check with an
> expression in Corrections, if an obs_type is present?
>
> --
> 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/ae1bbcf8-23b1-475e-8749-62286df24fb0n%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/CAPq0zEBBmY4FejrdGOkGxRtFD0whTVD8Hh8dUzSjYRpADQPucw%40mail.gmail.com.

Re: [weewx-user] Re: new install weewx on a new RPi 4b

[Tom Keffer]

> Mar  6 21:30:18 raspberrypi weewxd[31170]: INFO weewx.reportengine: Copied 0 
> files to /var/www/html/weewx
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: Caught 
> unrecoverable exception in generator 'weewx.cheetahgenerator.CheetahGenerator'
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
>   No module named 'user.stats'
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
>   Traceback (most recent call last):
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/reportengine.py", line 220, in run
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
>   obj.start()
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/reportengine.py", line 409, in start
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
>   self.run()
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 163, in run
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
>   self.init_extensions(gen_dict[section_name])
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 194, in 
> init_extensions
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
>   klass = weeutil.weeutil.get_object(x)
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
> File "/usr/share/weewx/weeutil/weeutil.py", line 1404, in get_object
> Mar  6 21:30:18 raspberrypi weewxd[31170]: Traceback (most recent call last):
> Mar  6 21:30:18 raspberrypi weewxd[31170]:   File 
> "/usr/share/weewx/weewx/reportengine.py", line 220, in run
> Mar  6 21:30:18 raspberrypi weewxd[31170]: obj.start()
> Mar  6 21:30:18 raspberrypi weewxd[31170]:   File 
> "/usr/share/weewx/weewx/reportengine.py", line 409, in start
> Mar  6 21:30:18 raspberrypi weewxd[31170]: self.run()
> Mar  6 21:30:18 raspberrypi weewxd[31170]:   File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 163, in run
> Mar  6 21:30:18 raspberrypi weewxd[31170]: 
> self.init_extensions(gen_dict[section_name])
> Mar  6 21:30:18 raspberrypi weewxd[31170]:   File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 194, in init_extensions
> Mar  6 21:30:18 raspberrypi weewxd[31170]: klass = 
> weeutil.weeutil.get_object(x)
> Mar  6 21:30:18 raspberrypi weewxd[31170]:   File 
> "/usr/share/weewx/weeutil/weeutil.py", line 1404, in get_object
> Mar  6 21:30:18 raspberrypi weewxd[31170]: module = 
> importlib.import_module(module_name)
> Mar  6 21:30:18 raspberrypi weewxd[31170]:   File 
> "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
> Mar  6 21:30:18 raspberrypi weewxd[31170]: return 
> _bootstrap._gcd_import(name[level:], package, level)
> Mar  6 21:30:18 raspberrypi weewxd[31170]:   File " importlib._bootstrap>", line 1030, in _gcd_import
> Mar  6 21:30:18 raspberrypi weewxd[31170]:   File " importlib._bootstrap>", line 1007, in _find_and_load
> Mar  6 21:30:18 raspberrypi weewxd[31170]:   File " importlib._bootstrap>", line 984, in _find_and_load_unlocked
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ModuleNotFoundError: No module 
> named 'user.stats'
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
>   module = importlib.import_module(module_name)
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
> File "/usr/lib/python3.9/importlib/__init__.py", line 127, in 
> import_module
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
>   return _bootstrap._gcd_import(name[level:], package, level)
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
> File "", line 1030, in _gcd_import
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
> File "", line 1007, in _find_and_load
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
> File "", line 984, in 
> _find_and_load_unlocked
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 
>   ModuleNotFoundError: No module named 'user.stats'
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: 

Re: [weewx-user] Re: new install weewx on a new RPi 4b

[Tom Keffer]

It should be

driver = user.byows

On Wed, Mar 6, 2024 at 11:29 AM salinois  wrote:

> ok Tom,
>
> this is a fresh install, not upgrade, but When I put my other sd card with
> 4.9 version, it is ok, so, it is not a issue with GPIO, I think.
>
> And yes, the driver is here:
>
> [ls -ail /etc/weewx/bin/user/
> total 32
> 526359 drwxrwsr-x 3 weewx weewx  4096  6 mars  18:32 .
> 526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
> 524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05 byows.py
> 526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15 extensions.py
> 526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15 __init__.py
> 655698 drwxr-sr-x 2 weewx weewx  4096  6 mars  18:32 __pycache__]
>
>
> and the lines for the driver in weewx.conf are:
>
>
> *[Station]*
>
> # Description of the station location, such as your town.
> location = "Loulle, Jura (France)"
>
> # Latitude in decimal degrees. Negative for southern hemisphere.
> latitude = 46.2539
> # Longitude in decimal degrees. Negative for western hemisphere.
> longitude = 5.3168
>
> # Altitude of the station, with the unit it is in. This is used only
> # if the hardware cannot supply a value.
> altitude = 700, meter# Choose 'foot' or 'meter' for unit
>
> # Set to type of station hardware. There must be a corresponding stanza
> # in this file, which includes a value for the 'driver' option.
>* station_type = BYOWS*
>
> and next
>
>
>
>
>
> *#
> [BYOWS]* # This section is for the Raspberry Pi Bring Your Own
> Weather Station driver.
>
> # The driver to use
> * driver = byows ===> is it the good syntax ? *in version 4.9 I have
> user.byows
>
> but now, there no more errors:
>
> [ sudo systemctl status weewx.service
> ● weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor
> preset: enabled)
>  Active: failed (Result: exit-code) since Wed 2024-03-06 20:21:34 CET;
> 3s ago
>Docs: https://weewx.com/docs
> Process: 29896 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited,
> status=1/FAILURE)
>Main PID: 29896 (code=exited, status=1/FAILURE)
> CPU: 337ms
>
> mars 06 20:21:34 raspberrypi weewxd[29896]:
> self.setupStation(config_dict)
> mars 06 20:21:34 raspberrypi weewxd[29896]:   File
> "/usr/share/weewx/weewx/engine.py", line 104, in setupStation
> mars 06 20:21:34 raspberrypi weewxd[29896]: __import__(driver)
> mars 06 20:21:34 raspberrypi weewxd[29896]: ModuleNotFoundError: *No
> module named 'byows'*
> mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__: 
> File "/usr/share/weewx/weewx/engine.py", line 104, in setupStation
> mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__:
>   __import__(driver)
> mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__: 
> ModuleNotFoundError: No module named 'byows'
> mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__: ****
> Exiting.
> mars 06 20:21:34 raspberrypi systemd[1]: weewx.service: Main process
> exited, code=exited, status=1/FAILURE
> mars 06 20:21:34 raspberrypi systemd[1]: weewx.service: Failed with result
> 'exit-code'.]
>
> Patrick
>
>
>
>
> Le 06/03/2024 à 19:23, Tom Keffer a écrit :
>
> If you did a package install, the driver byows.py should go in
> /etc/weewx/bin/user. But, frankly, this should have been done for you if
> you did an upgrade from V4 to V5. Take a look in /etc/weewx/bin/user and
> see if it's in there.
>
> But, the error in the little snippet from your status report is a
> different one. For some reason, your installation thinks it is not running
> on a Raspberry Pi, so it cannot access the gpio pins. I'm not an expert on
> that, but it may be due to a missing installation package.
>
> On Wed, Mar 6, 2024 at 10:13 AM salinois  wrote:
>
>> again me
>>
>> perhaps , I found
>>
>> Should I use this method now?
>>
>> [weectl extension install /home/pi/byows.py]
>>
>> and after:
>>
>> weectl station reconfigures --no-prompt --driver=weewx.drivers.byows
>>
>>
>> Patrick
>> Le 06/03/2024 à 18:47, salinois a écrit :
>>
>> hello,
>>
>> I restart my installation with version weewx 5.0.1 and I have these
>> errors:
>>
>> on my version which works in 4.10.2, my "byows.py" driver is located
>> here: [/usr/share/weewx/user/] but I saw that the tree structure has
>> changed; where should I put my driver now?
>>
>> 

Re: [weewx-user] RSS - FEED

[Tom Keffer]

A template file is a not-very-obvious mix of HTML and Cheetah tags. To get
the formatting you need, change this

#for $x in $observations
  #if $getattr($current, $x).has_data
#if $x == 'windSpeed'
$obs.label.wind: $current.windSpeed $gettext("from")
$current.windDir;
#else
$obs.label[$x]: $getattr($current, $x);
#end if
  #end if
#end for

to this

#for $x in $observations
  #if $getattr($current, $x).has_data
#if $x == 'windSpeed'
$obs.label.wind: $current.windSpeed $gettext("from")
$current.windDir;
#else
$obs.label[$x]: $getattr($current, $x);
#end if
  #end if
#end for

The "rain" tag under "Weather Conditions" is the rain that fell during the
last archive period, which is generally only 5-30 minutes. If you want rain
since midnight, you can find that under "Daily summary".







On Wed, Mar 6, 2024 at 7:08 AM Fjordey  wrote:

> I realize not many are using the RSS feed, yet I am to just get a quick
> check of things while sorting through my news feeds... regaurdless the
> reason I need help if possible...
>
> I'm not an expert by any means, but can fumble my way through the coding
> most times.
>
> #1 I edited the template to only provide the current conditions. That
> works.
> #2 I was trying to format the returned data:
>
> Wind: 0 mph from N/A; Rain: 0.00
>
> trying to remove the ";" and put Rain: 0.00 on the next line.. (have not
> figured that out)
>
> #3 I have noticed that my rain total is 0.00 when it should show 0.80 for
> toal rain.
> Note: the rain total and text formating were not working before I edited
> the template.
>
> any help would be apreciated... Hopefully I'm just overlooking something
> simple.
>
> https://weather.3utilities.icu/rss.xml
>
> my current rss.xml.tmpl:
>
> 
>xmlns:content="http://purl.org/rss/1.0/modules/content/;
>   xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#; >
>
> #set $timespans = [{"span": $day, "label": $gettext("Daily summary as
> of")}, {"span": $month, "label": $gettext("Monthly summary as of")},
> {"span": $year, "label": $gettext("Yearly summary as of")}]
>
> #set $observations = $to_list($DisplayOptions.get('observations_rss',
> ['outTemp', 'inTemp', 'barometer', 'windSpeed', 'rain', 'rainRate']))
> #set $obs_type_sum = $to_list($DisplayOptions.get('obs_type_sum',
> ['rain']))
> #set $obs_type_max = $to_list($DisplayOptions.get('obs_type_max',
> ['rainRate']))
>
>   
> $gettext("Weather Conditions") : $station.location
> $station.station_url
> $gettext("Current conditions, and daily, monthly, and
> yearly summaries")
> "$lang"
> $current.dateTime.format("%a, %d %b %Y %H:%M:%S %Z")
>
> $current.dateTime.format("%a, %d %b %Y %H:%M:%S
> %Z")
> http://blogs.law.harvard.edu/tech/rss
> weewx $station.version
> $current.interval.string('')
>
> 
>   $gettext("Weather Conditions at") $current.dateTime
>   $station.station_url
>   
> #for $x in $observations
>   #if $getattr($current, $x).has_data
> #if $x == 'windSpeed'
> $obs.label.wind: $current.windSpeed $gettext("from")
> $current.windDir;
> #else
> $obs.label[$x]: $getattr($current, $x);
> #end if
>   #end if
> #end for
>   
>   $current.dateTime.format("%a, %d %b %Y %H:%M:%S
> %Z")
>   
> 
>
>   
> 
>
> --
> 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/eba24381-6fbf-437b-ad2f-a09fffa01fe0n%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/CAPq0zECOE5RQnbJ8ndHj5AfuFko_9rscmpSrzzziSXqAPa7U3g%40mail.gmail.com.

Re: [weewx-user] Re: new install weewx on a new RPi 4b

[Tom Keffer]

If you did a package install, the driver byows.py should go in
/etc/weewx/bin/user. But, frankly, this should have been done for you if
you did an upgrade from V4 to V5. Take a look in /etc/weewx/bin/user and
see if it's in there.

But, the error in the little snippet from your status report is a different
one. For some reason, your installation thinks it is not running on a
Raspberry Pi, so it cannot access the gpio pins. I'm not an expert on that,
but it may be due to a missing installation package.

On Wed, Mar 6, 2024 at 10:13 AM salinois  wrote:

> again me
>
> perhaps , I found
>
> Should I use this method now?
>
> [weectl extension install /home/pi/byows.py]
>
> and after:
>
> weectl station reconfigures --no-prompt --driver=weewx.drivers.byows
>
>
> Patrick
> Le 06/03/2024 à 18:47, salinois a écrit :
>
> hello,
>
> I restart my installation with version weewx 5.0.1 and I have these errors:
>
> on my version which works in 4.10.2, my "byows.py" driver is located here:
> [/usr/share/weewx/user/] but I saw that the tree structure has changed; where
> should I put my driver now?
>
> watch these errors:
>
> sudo systemctl status weewx.service
> ● weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor
> preset: enabled)
>  Active: failed (Result: exit-code) since Wed 2024-03-06 18:32:05 CET;
> 2s ago
>Docs: https://weewx.com/docs
> Process: 11182 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited,
> status=4)
>Main PID: 11182 (code=exited, status=4)
> CPU: 682ms
>
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine:
>   pin = self.pin_factory.pin(pin)
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine:
> File "/usr/lib/python3/dist-packages/gpiozero/pins/pi.py", line
> 103, in pin
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine:
>   pin = self.pin_class(self, n)
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine:
> File "/usr/lib/python3/dist-packages/gpiozero/pins/rpigpio.py",
> line 111, in __init__
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine:
>   GPIO.setup(self.number, GPIO.IN, self.GPIO_PULL_UPS[self._pull])
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine:
>   RuntimeError: Not running on a RPi!
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL __main__:* Unable to
> load driver: Not running on a RPi!*
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL __main__: 
> Exiting...
> mars 06 18:32:05 raspberrypi systemd[1]: weewx.service: Main process
> exited, code=exited, status=4/NOPERMISSION
> mars 06 18:32:05 raspberrypi systemd[1]: weewx.service: Failed with result
> 'exit-code'.
>
> Patrick
> Le 08/02/2024 à 08:59, salinois a écrit :
>
> hello Matthew
>
> OK I understand if that works
>
> thanks also to vince.
>
> Now , I must to try the 5.0.0 version
>
> Patrick
> Le 07/02/2024 à 23:06, matthew wall a écrit :
>
> On Wednesday, February 7, 2024 at 3:36:55 PM UTC-5 sali...@gmail.com
> wrote:
>
> pi@raspberrypi:~ $ wget -qO - https://weewx.com/apt/weewx-python3.list |
> sudo tee /etc/apt/sources.list.d/weewx.list
> *deb [arch=all] http://weewx.com/apt/python3
>  buster main ==> why Buster*
>
>
> 'buster' (i.e., debian 10) is the oldest release on which the deb package
> will install.
>
> if you look at the python2 configuration, it uses the label 'squeeze'
> (debian 6)
>
> the weewx packages are *really* stable with respect to dependencies, so
> the same package that works with debian 10 also works with debian 11 and
> debian 12.  besides, i am too old and lazy to build a new deb and new apt
> repository for every major debian release that comes out :)
>
> --
> 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/ca7d09e7-acd7-4115-ae62-7ac60a1ef82bn%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/320351a0-1a0a-4474-9c39-de81a0e01011%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 

Re: [weewx-user] Fedora Weewx RPM install

[Tom Keffer]

See issue #940 .

On Wed, Mar 6, 2024 at 3:57 AM Mark Jenks  wrote:

> Good morning!
>
> I was going to do PIP for the new 5.x install, instead of using the
> setup.py like I have for years.
> Then I saw the RPM, and figured I was take a look at that, except the rpm
> doesn't work for Fedora.
> Fedora is not Enterprise Linux, so you can not install EPEL-Repo for it,
> but all packages that are in the EPEL, are already avail for Fedora.
>
> Looking at the RPM, epel-release is a dependency which is required by the
> RPM.  So either you create a new RPM for Fedora only, or the dependency
> needs to be removed.
>
> -Mark
>
> #
> dnf install weewx
> Last metadata expiration check: 0:25:37 ago on Wed 06 Mar 2024 05:30:57 AM
> CST.
> Dependencies resolved.
>
>  Problem: cannot install the best candidate for the job
>   - nothing provides epel-release needed by weewx-5.0.2-1.el9.noarch from
> weewx
> 
>
> rpm -qpR weewx-5.0.2-1.el9.noarch.rpm
> /bin/sh
> /bin/sh
> /bin/sh
> /usr/bin/getent
> /usr/sbin/groupadd
> /usr/sbin/useradd
> *epel-release*
> python3
> python3-cheetah
> python3-configobj
> python3-pillow
> python3-pyserial
> python3-pyusb
> rpmlib(CompressedFileNames) <= 3.0.4-1
> rpmlib(FileDigests) <= 4.6.0-1
> rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> rpmlib(PayloadIsXz) <= 5.2-1
>
> --
> 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/b8af8921-dcb7-4bfa-9e21-dfdbfb26682cn%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/CAPq0zEAf7aEay_sUddjZeR-wMwrL5BR5T0N%3DfLfiyo7Dnhy7fQ%40mail.gmail.com.

Re: [weewx-user] Upgrade to 5.0 from 4.10 the Graphs are not being created

[Tom Keffer]

If you look closely at your configuration file weewx.conf, the very last
line, you'll see that a stray backquote snuck in there. It reads

`report_services = weewx.engine.StdPrint, weewx.engine.StdReport

when it should read

report_services = weewx.engine.StdPrint, weewx.engine.StdReport

Fix that and your problems will go away.


On Tue, Mar 5, 2024 at 3:09 AM Francis Greaves 
wrote:

> Attached a longer log.
>
> On Tuesday 5 March 2024 at 10:57:29 UTC Graham Eddy wrote:
>
>> your archive interval is set to 10 mins, and the log is truncated just
>> where it started getting interesting. collect log data for two complete
>> cycles at least, in your case 20 mins
>> *⊣GE⊢*
>>
>> On 5 Mar 2024, at 8:03 pm, Francis Greaves  wrote:
>>
>> Thanks Tom for the suggestions.
>> I upgraded to 5.0.2 and rebooted to be on the safe side.
>> I noticed that the user running the service is now weewx so I changed the
>> permissions on the graphs folder to this:
>>
>> *drwxrwsr-x weewx weewx  *
>>
>> But the graphs are not being updated. They are still dated 1st March when
>> I did the upgrade from version 4.10
>>
>> I attach the log as you suggest and my config file.
>>
>> On Monday 4 March 2024 at 18:48:35 UTC Tom Keffer wrote:
>>
>>> First suggestion is to update to v5.0.2. Version 5.0.0 has a serious bug
>>> in it. There have also been some subtle bug fixes in how permissions are
>>> handled.
>>>
>>> When you're done, double check that /etc/systemd/system/weewx.service
>>> has the user set as you expect. Also, check /var/www/html permissions.
>>>
>>> If you still have problems after that, set debug=1, restart weewxd, post
>>> the log through the first reporting cycle.
>>>
>>> -tk
>>>
>>> On Mon, Mar 4, 2024 at 10:41 AM Francis Greaves 
>>> wrote:
>>>
>>>> I am using a Raspberry Pi running Raspbian 10 (buster). and a Vantage
>>>> Pro 2 Station.
>>>> I upgraded my Pi and Weewx upgrade to version 5. on 1st March.
>>>> The settings in the config file remain unchanged. In particular the
>>>> location of the HTML folder is the same, and the permissions are 775 for
>>>> root:root on that folder.
>>>> I have kept the system running as root user.
>>>> Weewx is working (I changed to systemd service startup today) the data
>>>> is downloaded.
>>>> I am not getting any graphs created.
>>>> I have looked through the documentation, but I cannot find out why.
>>>> I have set the debug to level 1 and enabled log_success as well as
>>>> log_failure
>>>> I attach the Log File which shows no errors.
>>>> Any ideas?
>>>>
>>>>
>>>> --
>>>> 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/d09dbae9-dce8-46d2-8d05-6a773a16da71n%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/weewx-user/d09dbae9-dce8-46d2-8d05-6a773a16da71n%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>
>> --
>> 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/4b739bbf-777a-4082-b551-f0524c94b1c3n%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/4b739bbf-777a-4082-b551-f0524c94b1c3n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> 
>>
>>
>> --
> 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/3c822864-8f82-40b1-8679-a5c7dc5134ffn%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/3c822864-8f82-40b1-8679-a5c7dc5134ffn%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEDhiO2mN%3DV6ftBBnz3HB4f88xsZD_ztDey86x-ZXCYeWg%40mail.gmail.com.

Re: [weewx-user] Upgrade to 5.0 from 4.10 the Graphs are not being created

[Tom Keffer]

First suggestion is to update to v5.0.2. Version 5.0.0 has a serious bug in
it. There have also been some subtle bug fixes in how permissions are
handled.

When you're done, double check that /etc/systemd/system/weewx.service has
the user set as you expect. Also, check /var/www/html permissions.

If you still have problems after that, set debug=1, restart weewxd, post
the log through the first reporting cycle.

-tk

On Mon, Mar 4, 2024 at 10:41 AM Francis Greaves 
wrote:

> I am using a Raspberry Pi running Raspbian 10 (buster). and a Vantage Pro
> 2 Station.
> I upgraded my Pi and Weewx upgrade to version 5. on 1st March.
> The settings in the config file remain unchanged. In particular the
> location of the HTML folder is the same, and the permissions are 775 for
> root:root on that folder.
> I have kept the system running as root user.
> Weewx is working (I changed to systemd service startup today) the data is
> downloaded.
> I am not getting any graphs created.
> I have looked through the documentation, but I cannot find out why.
> I have set the debug to level 1 and enabled log_success as well as
> log_failure
> I attach the Log File which shows no errors.
> Any ideas?
>
> --
> 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/d09dbae9-dce8-46d2-8d05-6a773a16da71n%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/CAPq0zEDyjaHNGSswZ-KGWa5eEuwEekx8BXpKUodkxCvqsR64%3Dg%40mail.gmail.com.

Re: [weewx-user] Re: Horror upgrade from 4.10 to 5.0.2

[Tom Keffer]

>From what I see in the log, the upgrade ran perfectly. The problem was that
you tried to use the old V4 utility "wee_extension" to install an extension
in a V5 environment. As explained in the Upgrade Guide, you need to use
"weectl extension install".

I would not dismiss an upgrade as a "horror" if you haven't read the
instructions.

On Sun, Mar 3, 2024 at 7:54 AM Invisible Man 
wrote:

> Nice, no, that was exactly what I was looking for :)  Thanks! That'll help
> very much.
>
> Just a pity that the upgrade went so bad. You expect an "apt upgrade" to
> run without any issue...
>
>
> On Sunday, March 3, 2024 at 4:25:14 PM UTC+1 Tom Keffer wrote:
>
>> It's all in the Upgrade Guide <https://www.weewx.com/docs/5.0/upgrade/>.
>> Did you read it?
>>
>> On Sun, Mar 3, 2024 at 7:22 AM Invisible Man 
>> wrote:
>>
>>> I downgraded back to 4.10. I will look into v5 later and calmly. This is
>>> not just "some small upgrade that'll work out of the box". So many things
>>> have changed like it's no longer wee_extension I see but weectl, and the
>>> daemon is running as weewx.
>>> Is there an upgrade procedure from 4.10 to v5 somewhere? + like all the
>>> changes and new habits I should move to?
>>>
>>> sudo apt install weewx=4.10.2-1
>>> sudo apt-mark hold weewx
>>>
>>> Thanks.
>>>
>>>
>>> On Sunday, March 3, 2024 at 3:44:44 PM UTC+1 Invisible Man wrote:
>>>
>>>> I used to have weewx 4.10 running smoothly with Interceptor driver. I
>>>> upgraded to 5.0.2
>>>> There are the logs, and I believe I have tons of issues.
>>>> I add the upgrading logs at the end.
>>>>
>>>> First issue partially solved: the upgrade did not handle my
>>>> /etc/default/weewx file and wasn't loading my config file. I fixed the
>>>> /etc/default/weewx with this:
>>>>
>>>> WEEWX_PYTHON=python3
>>>> WEEWX_BINDIR=/usr/share/weewx
>>>> WEEWX_CFG=/etc/weewx/weewx.conf
>>>> WEEWX_BIN=/usr/bin/weewx
>>>>
>>>> Now, at least it's trying to do something. But it complains that No
>>>> module named 'user'. I think that's because it is trying to run weewx as
>>>> weewx user? Is that right?
>>>>
>>>> So, I thought I needed to install the interceptor driver in the weewx
>>>> user account.
>>>> The command is ./wee_extension --install interceptor.zip, except I only
>>>> have wee_extension in /etc/weewx/scripts and those were scripts but without
>>>> the +x executable permission... I added it.
>>>>
>>>> It's not working.
>>>>
>>>> $ ./wee_extension --install ~axelle/weewx-interceptor.zip
>>>> python3: can't open file '/usr/share/weewx/wee_extension': [Errno 2] No
>>>> such file or directory
>>>>
>>>> I'm no longer understanding where weewx has put its new files, thus my
>>>> /etc/default/weewx file probably not correctly set. It's horrible mess.
>>>> Where are things meant to be?
>>>>
>>>> Thanks
>>>>
>>>>
>>>>
>>>> Unpacking weewx (5.0.2-1) over (4.10.2-1) ...
>>>> dpkg: warning: unable to delete old directory '/usr/share/weewx/user':
>>>> Directory not empty
>>>> dpkg: warning: unable to delete old directory
>>>> '/etc/weewx/udev/rules.d': Directory not empty
>>>> dpkg: warning: unable to delete old directory
>>>> '/etc/weewx/skins/Standard/smartphone/icons': Directory no
>>>> t empty
>>>> dpkg: warning: unable to delete old directory
>>>> '/etc/weewx/skins/Standard/smartphone': Directory not empt
>>>> y
>>>> dpkg: warning: unable to delete old directory
>>>> '/etc/weewx/skins/Standard/lang': Directory not empty
>>>> dpkg: warning: unable to delete old directory
>>>> '/etc/weewx/skins/Standard/backgrounds': Directory not emp
>>>> ty
>>>> dpkg: warning: unable to delete old directory
>>>> '/etc/weewx/skins/Standard/RSS': Directory not empty
>>>> dpkg: warning: unable to delete old directory
>>>> '/etc/weewx/skins/Standard/NOAA': Directory not empty
>>>> dpkg: warning: unable to delete old directory
>>>> '/etc/weewx/skins/Standard': Directory not empty
>>>> dpkg: warning: unable to delete old directory
>>>> '/etc/weewx/skins/Smartphone/lang': Directory not empty
>>>&

Re: [weewx-user] Re: Horror upgrade from 4.10 to 5.0.2

[Tom Keffer]

It's all in the Upgrade Guide .
Did you read it?

On Sun, Mar 3, 2024 at 7:22 AM Invisible Man 
wrote:

> I downgraded back to 4.10. I will look into v5 later and calmly. This is
> not just "some small upgrade that'll work out of the box". So many things
> have changed like it's no longer wee_extension I see but weectl, and the
> daemon is running as weewx.
> Is there an upgrade procedure from 4.10 to v5 somewhere? + like all the
> changes and new habits I should move to?
>
> sudo apt install weewx=4.10.2-1
> sudo apt-mark hold weewx
>
> Thanks.
>
>
> On Sunday, March 3, 2024 at 3:44:44 PM UTC+1 Invisible Man wrote:
>
>> I used to have weewx 4.10 running smoothly with Interceptor driver. I
>> upgraded to 5.0.2
>> There are the logs, and I believe I have tons of issues.
>> I add the upgrading logs at the end.
>>
>> First issue partially solved: the upgrade did not handle my
>> /etc/default/weewx file and wasn't loading my config file. I fixed the
>> /etc/default/weewx with this:
>>
>> WEEWX_PYTHON=python3
>> WEEWX_BINDIR=/usr/share/weewx
>> WEEWX_CFG=/etc/weewx/weewx.conf
>> WEEWX_BIN=/usr/bin/weewx
>>
>> Now, at least it's trying to do something. But it complains that No
>> module named 'user'. I think that's because it is trying to run weewx as
>> weewx user? Is that right?
>>
>> So, I thought I needed to install the interceptor driver in the weewx
>> user account.
>> The command is ./wee_extension --install interceptor.zip, except I only
>> have wee_extension in /etc/weewx/scripts and those were scripts but without
>> the +x executable permission... I added it.
>>
>> It's not working.
>>
>> $ ./wee_extension --install ~axelle/weewx-interceptor.zip
>> python3: can't open file '/usr/share/weewx/wee_extension': [Errno 2] No
>> such file or directory
>>
>> I'm no longer understanding where weewx has put its new files, thus my
>> /etc/default/weewx file probably not correctly set. It's horrible mess.
>> Where are things meant to be?
>>
>> Thanks
>>
>>
>>
>> Unpacking weewx (5.0.2-1) over (4.10.2-1) ...
>> dpkg: warning: unable to delete old directory '/usr/share/weewx/user':
>> Directory not empty
>> dpkg: warning: unable to delete old directory '/etc/weewx/udev/rules.d':
>> Directory not empty
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/skins/Standard/smartphone/icons': Directory no
>> t empty
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/skins/Standard/smartphone': Directory not empt
>> y
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/skins/Standard/lang': Directory not empty
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/skins/Standard/backgrounds': Directory not emp
>> ty
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/skins/Standard/RSS': Directory not empty
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/skins/Standard/NOAA': Directory not empty
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/skins/Standard': Directory not empty
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/skins/Smartphone/lang': Directory not empty
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/skins/Smartphone/icons': Directory not empty
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/skins/Smartphone': Directory not empty
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/skins/Seasons/lang': Directory not empty
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/skins/Seasons/font': Directory not empty
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/skins/Seasons/NOAA': Directory not empty
>> dpkg: warning: unable to delete old directory '/etc/weewx/skins/Seasons':
>> Directory not empty
>> dpkg: warning: unable to delete old directory '/etc/weewx/skins/Rsync':
>> Directory not empty
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/skins/Mobile/lang': Directory not empty
>> dpkg: warning: unable to delete old directory '/etc/weewx/skins/Mobile':
>> Directory not empty
>> dpkg: warning: unable to delete old directory '/etc/weewx/skins/Ftp':
>> Directory not empty
>> dpkg: warning: unable to delete old directory '/etc/weewx/skins':
>> Directory not empty
>> dpkg: warning: unable to delete old directory '/etc/weewx/scripts':
>> Directory not empty
>> dpkg: warning: unable to delete old directory '/etc/weewx/apache/conf.d':
>> Directory not empty
>> dpkg: warning: unable to delete old directory
>> '/etc/weewx/apache/conf-available': Directory not empty
>> dpkg: warning: unable to delete old directory '/etc/weewx/apache':
>> Directory not empty
>> Setting up python3-ephem (3.7.6.0-7+b1) ...
>> Setting up weewx (5.0.2-1) ...
>> Installing new version of config file /etc/weewx/import/csv-example.conf
>> ...
>> Installing new version of config file
>> /etc/weewx/import/cumulus-example.conf ...
>> Installing new version of config file /etc/weewx/import/wd-example.conf
>> ...

Re: [weewx-user] weectl extension install ~/Downloads/weewx-steelseries-master.zip

[Tom Keffer]

You haven't done anything wrong.

For some reason, the SteelSeries repository
 is missing the skin!

I will follow up with Gary.

On Sun, Mar 3, 2024 at 5:16 AM philip@gmail.com <
philip.c.ow...@gmail.com> wrote:

> Hi
> Using a Pi5 with a clean install of all software (Debian 12 bookworn).
> Loaded weewx v5.0.2 using Installation on Debian based systems all OK
> Then tried loading extensions using weectl which all worked OK until I
> tried
> weectl extension install ~/Downloads/weewx-steelseries-master.zip.
> It failed with
>  weectl extension install ~/Downloads/weewx-steelseries-master.zip
> Using configuration file /etc/weewx/weewx.conf
> Install extension '/home/phil/Downloads/weewx-steelseries-master.zip'
> (y/n)? y
> Extracting from zip archive
> /home/phil/Downloads/weewx-steelseries-master.zip
> Traceback (most recent call last):
>   File "/usr/share/weewx/weectl.py", line 74, in 
> main()
>   File "/usr/share/weewx/weectl.py", line 66, in main
> namespace.func(namespace)
>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
> namespace.action_func(config_dict, namespace)
>   File "/usr/share/weewx/weectllib/extension_cmd.py", line 116, in
> install_extension
> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>   File "/usr/share/weewx/weecfg/extension.py", line 138, in
> install_extension
> extension_name = self._install_from_file(extension_path, filetype)
>  ^
>   File "/usr/share/weewx/weecfg/extension.py", line 168, in
> _install_from_file
> extension_name = self.install_from_dir(extension_dir)
>  
>   File "/usr/share/weewx/weecfg/extension.py", line 185, in
> install_from_dir
> self._install_files(installer['files'], extension_dir)
>   File "/usr/share/weewx/weecfg/extension.py", line 269, in _install_files
> shutil.copy(source_path, destination_path)
>   File "/usr/lib/python3.11/shutil.py", line 419, in copy
> copyfile(src, dst, follow_symlinks=follow_symlinks)
>   File "/usr/lib/python3.11/shutil.py", line 256, in copyfile
> with open(src, 'rb') as fsrc:
>  ^^^
> FileNotFoundError: [Errno 2] No such file or directory:
> '/tmp/tmpyald28op/weewx-steelseries-master/skins/ss/gauge-data.txt.tmpl'
>
> Just wondered what I may have done wrong
> 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/17a8db89-0641-49da-b015-17a43f6bc579n%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/CAPq0zEDwyPrasiZNBYbnOBbC1hxCmCZBkHNG%3Dg5U1F0GfQASJg%40mail.gmail.com.

Re: [weewx-user] Using Meteo-Pi-Ethernet Logger now get 'Unable to wake up Vantage console'

[Tom Keffer]

I doubt a reinstall will make any difference, unless the Zero has some kind
of weird intermittent firewall set up.

On Sat, Mar 2, 2024 at 6:34 PM Curtis Esac  wrote:

> Thanks Tom, that will be my next thing to try contacting Meteo-Pi.
>
> I also just got a new Raspberry Pi 5 (currently weewx is on a Raspberry Pi
> Zeor 2 W), so I'm going to put weewx 5 on it and start fresh and see if
> that works.
>
> Thanks!
>
> On Saturday, March 2, 2024 at 6:28:56 PM UTC-8 Tom Keffer wrote:
>
>> From the small log snippet that you provided it looks like weewx was able
>> to successfully download at least one record. Then it failed. So, this is
>> an intermittent problem? If so, the --loop-on-init flag won't make any
>> difference.
>>
>> Could be anything. I don't have any experience with the Meteo-Pi logger.
>> Have you asked the Meteo people?
>>
>> -tk
>>
>>
>>
>> On Sat, Mar 2, 2024 at 6:20 PM Curtis Esac  wrote:
>>
>>> I have had weewx  4.10.2  working fine with my Meteo-Pi-Ethernet Logger,
>>> now  after starting weewx I get:
>>>
>>> pi@raspberrypi:~ $ sudo systemctl status weewx
>>> ● weewx.service - LSB: weewx weather system
>>>  Loaded: loaded (/etc/init.d/weewx; generated)
>>>  Active: active (running) since Sat 2024-03-02 17:29:09 PST; 1min
>>> 13s ago
>>>Docs: man:systemd-sysv-generator(8)
>>> Process: 13802 ExecStart=/etc/init.d/weewx start (code=exited,
>>> status=0/SUCCESS)
>>>   Tasks: 2 (limit: 414)
>>> CPU: 5.703s
>>>  CGroup: /system.slice/weewx.service
>>>  └─13815 python3 /usr/share/weewx/weewxd --daemon
>>> --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf --loop-on-init
>>>
>>> Mar 02 17:29:23 raspberrypi python3[13815]: weewx[13815] INFO
>>> weewx.manager: Added record 2024-03-02 17:25:00 PST (1709429100) to
>>> database 'weewx.sdb'
>>> Mar 02 17:29:23 raspberrypi python3[13815]: weewx[13815] INFO
>>> weewx.restx: PWSWeather: Published record 2024-03-02 17:20:00 PST
>>> (1709428800)
>>> Mar 02 17:29:23 raspberrypi python3[13815]: weewx[13815] INFO
>>> weewx.manager: Added record 2024-03-02 17:25:00 PST (1709429100) to daily
>>> summary in 'weewx.sdb'
>>> Mar 02 17:29:23 raspberrypi python3[13815]: weewx[13815] INFO
>>> weewx.engine: Starting main packet loop.
>>> Mar 02 17:29:23 raspberrypi python3[13815]: weewx[13815] INFO
>>> weewx.restx: PWSWeather: Published record 2024-03-02 17:25:00 PST
>>> (1709429100)
>>> Mar 02 17:30:01 raspberrypi python3[13815]: weewx[13815] ERROR
>>> weewx.drivers.vantage: ip-read error: timed out
>>> Mar 02 17:30:01 raspberrypi python3[13815]: weewx[13815] ERROR
>>> weewx.drivers.vantage: LOOP batch try #1; error: timed out
>>> Mar 02 17:30:06 raspberrypi python3[13815]: weewx[13815] ERROR
>>> weewx.drivers.vantage: ip-read error: timed out
>>> Mar 02 17:30:13 raspberrypi python3[13815]: weewx[13815] ERROR
>>> weewx.drivers.vantage: ip-read error: timed out
>>> Mar 02 17:30:20 raspberrypi python3[13815]: weewx[13815] ERROR
>>> weewx.drivers.vantage: ip-read error: timed out
>>> Mar 02 17:30:26 raspberrypi python3[13815]: weewx[13815] ERROR
>>> weewx.drivers.vantage: ip-read error: timed out
>>> Mar 02 17:30:27 raspberrypi python3[13815]: weewx[13815] ERROR
>>> weewx.drivers.vantage: Unable to wake up Vantage console
>>> Mar 02 17:30:27 raspberrypi python3[13815]: weewx[13815] ERROR
>>> weewx.drivers.vantage: LOOP batch try #2; error: Unable to wake up Vantage
>>> console
>>>
>>> With my web-browser I can view the Meteo-Pi_Ethernet Logger web page
>>> directly and it is working and gives current wx data.  Since it stopped
>>> working I have added '--loop-on-init' to 'DAEMON_ARGS' in /etc/init.d/weewx
>>> and also 'loop_on_init = True' near the top of /etc/weewx/weewx.conf.
>>>
>>> I don't mess with weewx much, it has just worked, so I am a noob at
>>> trying to track this down.
>>>
>>> Thanks for any help.
>>>
>>> --
>>> 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/ca757666-ec15-4828-9414-27022c70f8d5n%40googlegroups.com
>>> <https:/

Re: [weewx-user] Using Meteo-Pi-Ethernet Logger now get 'Unable to wake up Vantage console'

[Tom Keffer]

>From the small log snippet that you provided it looks like weewx was able
to successfully download at least one record. Then it failed. So, this is
an intermittent problem? If so, the --loop-on-init flag won't make any
difference.

Could be anything. I don't have any experience with the Meteo-Pi logger.
Have you asked the Meteo people?

-tk



On Sat, Mar 2, 2024 at 6:20 PM Curtis Esac  wrote:

> I have had weewx  4.10.2  working fine with my Meteo-Pi-Ethernet Logger,
> now  after starting weewx I get:
>
> pi@raspberrypi:~ $ sudo systemctl status weewx
> ● weewx.service - LSB: weewx weather system
>  Loaded: loaded (/etc/init.d/weewx; generated)
>  Active: active (running) since Sat 2024-03-02 17:29:09 PST; 1min 13s
> ago
>Docs: man:systemd-sysv-generator(8)
> Process: 13802 ExecStart=/etc/init.d/weewx start (code=exited,
> status=0/SUCCESS)
>   Tasks: 2 (limit: 414)
> CPU: 5.703s
>  CGroup: /system.slice/weewx.service
>  └─13815 python3 /usr/share/weewx/weewxd --daemon
> --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf --loop-on-init
>
> Mar 02 17:29:23 raspberrypi python3[13815]: weewx[13815] INFO
> weewx.manager: Added record 2024-03-02 17:25:00 PST (1709429100) to
> database 'weewx.sdb'
> Mar 02 17:29:23 raspberrypi python3[13815]: weewx[13815] INFO weewx.restx:
> PWSWeather: Published record 2024-03-02 17:20:00 PST (1709428800)
> Mar 02 17:29:23 raspberrypi python3[13815]: weewx[13815] INFO
> weewx.manager: Added record 2024-03-02 17:25:00 PST (1709429100) to daily
> summary in 'weewx.sdb'
> Mar 02 17:29:23 raspberrypi python3[13815]: weewx[13815] INFO
> weewx.engine: Starting main packet loop.
> Mar 02 17:29:23 raspberrypi python3[13815]: weewx[13815] INFO weewx.restx:
> PWSWeather: Published record 2024-03-02 17:25:00 PST (1709429100)
> Mar 02 17:30:01 raspberrypi python3[13815]: weewx[13815] ERROR
> weewx.drivers.vantage: ip-read error: timed out
> Mar 02 17:30:01 raspberrypi python3[13815]: weewx[13815] ERROR
> weewx.drivers.vantage: LOOP batch try #1; error: timed out
> Mar 02 17:30:06 raspberrypi python3[13815]: weewx[13815] ERROR
> weewx.drivers.vantage: ip-read error: timed out
> Mar 02 17:30:13 raspberrypi python3[13815]: weewx[13815] ERROR
> weewx.drivers.vantage: ip-read error: timed out
> Mar 02 17:30:20 raspberrypi python3[13815]: weewx[13815] ERROR
> weewx.drivers.vantage: ip-read error: timed out
> Mar 02 17:30:26 raspberrypi python3[13815]: weewx[13815] ERROR
> weewx.drivers.vantage: ip-read error: timed out
> Mar 02 17:30:27 raspberrypi python3[13815]: weewx[13815] ERROR
> weewx.drivers.vantage: Unable to wake up Vantage console
> Mar 02 17:30:27 raspberrypi python3[13815]: weewx[13815] ERROR
> weewx.drivers.vantage: LOOP batch try #2; error: Unable to wake up Vantage
> console
>
> With my web-browser I can view the Meteo-Pi_Ethernet Logger web page
> directly and it is working and gives current wx data.  Since it stopped
> working I have added '--loop-on-init' to 'DAEMON_ARGS' in /etc/init.d/weewx
> and also 'loop_on_init = True' near the top of /etc/weewx/weewx.conf.
>
> I don't mess with weewx much, it has just worked, so I am a noob at trying
> to track this down.
>
> Thanks for any help.
>
> --
> 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/ca757666-ec15-4828-9414-27022c70f8d5n%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/CAPq0zEA9dMYiL4UKdiVQ%2ByL%3D2O6-NTf-uqnT2Fti1c9-xiyRAg%40mail.gmail.com.