Re: [weewx-user] Re: Restore weewx Database from Ecowitt.net

[Marlon]

Hi Tim
I recently pushed a PR to that repo, which isn't merged yet which got 
things working for me.
With this, I managed to extract my ecowitt data and then used *wee_import* 
to bring it into weewx.
https://github.com/notnullxyz/ecowitt2weewx - a fork from @comes with my 
fixes and his latest changes from yesterday
I hope that this will help you. It's for me really, but if anyone else find 
it useful, that's cool.



On Wednesday, 01 November 2023 at 08:29:50 UTC+2 Tim Tuck wrote:

> HI Vince,
>
> I might do that.
>
> But I've posted here since this was script originally announced here so 
> the developer should see this anyway.
>
> Also there are many weewx user who have Ecowitt kit and repopulating the 
> db from the Ecowitt server is something that others may have done, hence 
> my question :)
>
> regards
>
> Tim
>
> On 1/11/23 16:04, vince wrote:
> > Perhaps you might open a github issue at the repo you mentioned..,,
> >
> >
>

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

Re: [weewx-user] Re: Restore weewx Database from Ecowitt.net

[Tim Tuck]

HI Vince,

I might do that.

But I've posted here since this was script originally announced here so 
the developer should see this anyway.


Also there are many weewx user who have Ecowitt kit and repopulating the 
db from the Ecowitt server is something that others may have done, hence 
my question :)


regards

Tim

On 1/11/23 16:04, vince wrote:

Perhaps you might open a github issue at the repo you mentioned..,,




--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5dbc394b-4cf3-45ae-80b0-4d48404193e7%40skybase.net.

[weewx-user] Re: Restore weewx Database from Ecowitt.net

[vince]

Perhaps you might open a github issue at the repo you mentioned..,,

On Tuesday, October 31, 2023 at 9:23:33 PM UTC-7 Tim Tuck wrote:

> Hi all,
>
> For the life of me I cannot get this to work :(
>
>
> https://github.com/comes/ecowitt2weewx#restore-weewx-database-from-ecowittnet
>
> I've poked around and paths are just not where they are expected to be i.e.
>
> __DIR__.'/vendor/autoload.php' which I think expands to {current 
> directory}/vendor/autoload.php
>
> when it is actually in  ~/.config/composer/vendor/autoload.php
>
> I'm not a coder so just getting here has caused me grief. I shouldn't 
> have to install anything beyond php to run a script let-alone composer 
> and Laravel ( wtf? why all this just for a script!! )
>
> It would be really nice if this was just a standalone script that didn't 
> require anything more than php
>
> Some nice straight forward instructions about how to get it to run would 
> be greatly appreciated.
>
> or some other method to retrieve my records from the Ecowitt DB in a 
> sensible fashion for import.
>
> Any help appreciated.
>
> thanks
>
> Tim
>
>
>
>
>
>

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

[weewx-user] Restore weewx Database from Ecowitt.net

[Tim Tuck]

Hi all,

For the life of me I cannot get this to work :(

https://github.com/comes/ecowitt2weewx#restore-weewx-database-from-ecowittnet

I've poked around and paths are just not where they are expected to be i.e.

__DIR__.'/vendor/autoload.php' which I think expands to {current 
directory}/vendor/autoload.php


when it is actually in  ~/.config/composer/vendor/autoload.php

I'm not a coder so just getting here has caused me grief. I shouldn't 
have to install anything beyond php to run a script let-alone composer 
and Laravel ( wtf? why all this just for a script!! )


It would be really nice if this was just a standalone script that didn't 
require anything more than php


Some nice straight forward instructions about how to get it to run would 
be greatly appreciated.


or some other method to retrieve my records from the Ecowitt DB in a 
sensible fashion for import.


Any help appreciated.

thanks

Tim





--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/83e3b85d-0a6b-45a8-94cd-aecc23bc0d2d%40skybase.net.

Re: [weewx-user] Rsyc Error

[Tom -KQ5S]

I guess I installed V5.  The config file shows version = 4.10.2.  I 
followed the install instructions 
at https://weewx.com/docs/5.0/quickstarts/debian/.

On Tuesday, October 31, 2023 at 8:20:16 PM UTC-5 Tom -KQ5S wrote:

> As a follow-up I did a clean install of bookworm and WeeWX 5, using 
> apt-get,  on my Pi.  I did nothing else except set up Rsync and I am 
> getting the same sporadic errors as before.  No crons.  No extensions.  
> Nothing was added to the base install.
>
> On Monday, October 30, 2023 at 8:19:09 AM UTC-5 Tom -KQ5S wrote:
>
>> Thanks to Vince and Chris for the help.  At this point I am giving up. 
>>  I'll try a fresh install and see what happens. 
>>
>> Tom.  
>>
>> On Sunday, October 29, 2023 at 9:20:23 PM UTC-5 vince wrote:
>>
>>> Tom - I'm at a loss at this point as to why you're not working (or 
>>> failing) consistently.
>>>
>>> I did a setup of rsync over ssh on a clean pi and here are the steps.
>>> Worked first time for me :-)
>>>
>>> (this example uses weewx v5.0b15 as user 'pi')
>>>
>>> # reimaged a raspberry pi
>>> # installed rsyslog to get traditional syslogging rather than systemd
>>> sudo apt-get install -y rsyslog
>>>
>>> # logged into the pi as unprivileged user pi (for this example)
>>>
>>> # installed weewx with the simulator driver
>>>
>>> # created a new ssh keypair for the user pi
>>> # taking the defaults to make a passwordless keypair
>>> # which will be ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub
>>> ssh-keygen
>>>
>>> # added this key to the appropriate user@host for my server host
>>> ssh-copy-id vince@nuc2
>>>
>>> # verified I could log into the remote server
>>> ssh vince@nuc2
>>> # at this point ssh is known to work using the new ssh key
>>>
>>> # edited weewx.conf to set debug=1 for more verbose logging
>>>
>>> # edited weewx.conf to configure the RSYNC uploader
>>> # so this will upload the default public_html to the specified path
>>>
>>>[[RSYNC]]
>>> skin = Rsync
>>> enable = true
>>> server = nuc2
>>> user = vince
>>> path = /home/vince/weehtml
>>> log_success = true
>>> log_failure = true
>>> delete = 0
>>>
>>> # restarted weewx, waited 5 minutes, I see the successful rsync of the 
>>> Seasons skin in syslog
>>>
>>> 2023-10-29T19:00:20.236994-07:00 raspberrypi weewx[2416] DEBUG 
>>> weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', '--stats', 
>>> '-e', 'ssh', '/home/pi/weewx-data/public_html/', 
>>> 'vince@nuc2:/home/vince/weehtml']]
>>>
>>> 2023-10-29T19:00:20.680310-07:00 raspberrypi weewx[2416] INFO 
>>> weeutil.rsyncupload: rsync'd 73 files (526,454 bytes) in 0.44 seconds
>>>
>>> # Notes:
>>> #  - no /home/pi/.ssh/config file was needed on a pi as long as the 
>>> specified 'server' resolves
>>> #   because ssh on the pi defaults to using ~/.ssh/id_rsa as the 
>>> private key
>>> #  - weewx assumes the local user is the one it is running as
>>> #  - weewx uses the RSYNC 'user' as the remote user it connects to
>>>
>>>
>>>

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

Re: [weewx-user] Rsyc Error

[Tom -KQ5S]

As a follow-up I did a clean install of bookworm and WeeWX 5, using 
apt-get,  on my Pi.  I did nothing else except set up Rsync and I am 
getting the same sporadic errors as before.  No crons.  No extensions.  
Nothing was added to the base install.

On Monday, October 30, 2023 at 8:19:09 AM UTC-5 Tom -KQ5S wrote:

> Thanks to Vince and Chris for the help.  At this point I am giving up. 
>  I'll try a fresh install and see what happens. 
>
> Tom.  
>
> On Sunday, October 29, 2023 at 9:20:23 PM UTC-5 vince wrote:
>
>> Tom - I'm at a loss at this point as to why you're not working (or 
>> failing) consistently.
>>
>> I did a setup of rsync over ssh on a clean pi and here are the steps.
>> Worked first time for me :-)
>>
>> (this example uses weewx v5.0b15 as user 'pi')
>>
>> # reimaged a raspberry pi
>> # installed rsyslog to get traditional syslogging rather than systemd
>> sudo apt-get install -y rsyslog
>>
>> # logged into the pi as unprivileged user pi (for this example)
>>
>> # installed weewx with the simulator driver
>>
>> # created a new ssh keypair for the user pi
>> # taking the defaults to make a passwordless keypair
>> # which will be ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub
>> ssh-keygen
>>
>> # added this key to the appropriate user@host for my server host
>> ssh-copy-id vince@nuc2
>>
>> # verified I could log into the remote server
>> ssh vince@nuc2
>> # at this point ssh is known to work using the new ssh key
>>
>> # edited weewx.conf to set debug=1 for more verbose logging
>>
>> # edited weewx.conf to configure the RSYNC uploader
>> # so this will upload the default public_html to the specified path
>>
>>[[RSYNC]]
>> skin = Rsync
>> enable = true
>> server = nuc2
>> user = vince
>> path = /home/vince/weehtml
>> log_success = true
>> log_failure = true
>> delete = 0
>>
>> # restarted weewx, waited 5 minutes, I see the successful rsync of the 
>> Seasons skin in syslog
>>
>> 2023-10-29T19:00:20.236994-07:00 raspberrypi weewx[2416] DEBUG 
>> weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', '--stats', 
>> '-e', 'ssh', '/home/pi/weewx-data/public_html/', 
>> 'vince@nuc2:/home/vince/weehtml']]
>>
>> 2023-10-29T19:00:20.680310-07:00 raspberrypi weewx[2416] INFO 
>> weeutil.rsyncupload: rsync'd 73 files (526,454 bytes) in 0.44 seconds
>>
>> # Notes:
>> #  - no /home/pi/.ssh/config file was needed on a pi as long as the 
>> specified 'server' resolves
>> #   because ssh on the pi defaults to using ~/.ssh/id_rsa as the 
>> private key
>> #  - weewx assumes the local user is the one it is running as
>> #  - weewx uses the RSYNC 'user' as the remote user it connects to
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b226eed0-523f-42ab-8d32-4b16330e847cn%40googlegroups.com.

Re: [weewx-user] List of conf parameters for skin.conf

[Tom Keffer]

Remy has it right: look in the Customization Guide. You just need the link:
https://www.weewx.com/docs/customizing.htm

On Tue, Oct 31, 2023 at 4:08 PM jmltech  wrote:

> Hi,
> I’m using the Season skin 4.9.1, under Weewx 4.10.2
>
> In reading through the group messgaes, and looking at the skin.conf, I see
> a lot of configuration and override settings that can be made.   Parameters
> such as:
>
> yscale =
> x_label_format =
> bottom_label_format =
> color =
> fill_color =
> chart_line_color =
>
> Are these config and override parameters documented somewhere?  I have
> looked on the weewx wiki, as well as the group messages, and don’t see
> where all of the opions are listed and explained?
>
> 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/f0eb5301-96e2-44d0-ba17-760495586985n%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/CAPq0zEAqmHZu3q4st%2BLqkHY23X2%2BUFNCxnFciHTwWXWVyQoj0A%40mail.gmail.com.

Re: [weewx-user] List of conf parameters for skin.conf

[Remy LAVABRE]

Hello,
Weewx documentation, customisation guide
The Image generator

Le mer. 1 nov. 2023, 00:08, jmltech  a écrit :

> Hi,
> I’m using the Season skin 4.9.1, under Weewx 4.10.2
>
> In reading through the group messgaes, and looking at the skin.conf, I see
> a lot of configuration and override settings that can be made.   Parameters
> such as:
>
> yscale =
> x_label_format =
> bottom_label_format =
> color =
> fill_color =
> chart_line_color =
>
> Are these config and override parameters documented somewhere?  I have
> looked on the weewx wiki, as well as the group messages, and don’t see
> where all of the opions are listed and explained?
>
> 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/f0eb5301-96e2-44d0-ba17-760495586985n%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/CADhm9YdL-Jwd-ygktT%3DFQu791bc53FVUEdxmqPqMx%3D6x%2B7znDQ%40mail.gmail.com.

[weewx-user] List of conf parameters for skin.conf

[jmltech]

Hi,
I’m using the Season skin 4.9.1, under Weewx 4.10.2

In reading through the group messgaes, and looking at the skin.conf, I see 
a lot of configuration and override settings that can be made.   Parameters 
such as:

yscale =
x_label_format =
bottom_label_format =
color =
fill_color =
chart_line_color =

Are these config and override parameters documented somewhere?  I have 
looked on the weewx wiki, as well as the group messages, and don’t see 
where all of the opions are listed and explained?

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/f0eb5301-96e2-44d0-ba17-760495586985n%40googlegroups.com.

[weewx-user] Re: No Weewx charts on public server

[Pete AndDebbie]

Fixed!  Thanks!
Discovered that the "not working - charts" web/ftp site was missing 3 
filesseasons.css and season.js and faivon.ico  in the root directory of 
the web server!!
All good now.  Just needed to know (thanks to you) "where to look" to ID 
the problem.
-pete

On Tuesday, October 31, 2023 at 3:54:55 PM UTC-5 vince wrote:

> Without a description of your setup, or seeing any log snippets or seeing 
> your weewx.conf contents (hint - we can't read minds)it is difficult to 
> guess much, but at a minimum it looks like you didn't copy all the 
> public_html tree up in your ftp configuration somehow.  You certainly look 
> like you're missing the css files at a minimum.
>
> On Tuesday, October 31, 2023 at 1:45:18 PM UTC-7 Pete AndDebbie wrote:
>
>> Strange...
>>
>> Local (network 10.0.254.83/weewx) Weewx web server works perfectly.
>> All graphs and charts. Yet, FTPing from that Rpi based weewx web server 
>> to the public FTP server does not post the charts on the public home page.
>>
>> Double checked FTP to public web serverworkingyet NO CHARTS.
>>
>> Problem Seen Here: https://PandionTempest.rf.gd
>>
>> I'm stumped...any hints to the fix?
>>
>> Thanks,
>>
>> -pete
>>
>

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

[weewx-user] Re: No Weewx charts on public server

[vince]

Without a description of your setup, or seeing any log snippets or seeing 
your weewx.conf contents (hint - we can't read minds)it is difficult to 
guess much, but at a minimum it looks like you didn't copy all the 
public_html tree up in your ftp configuration somehow.  You certainly look 
like you're missing the css files at a minimum.

On Tuesday, October 31, 2023 at 1:45:18 PM UTC-7 Pete AndDebbie wrote:

> Strange...
>
> Local (network 10.0.254.83/weewx) Weewx web server works perfectly.
> All graphs and charts. Yet, FTPing from that Rpi based weewx web server to 
> the public FTP server does not post the charts on the public home page.
>
> Double checked FTP to public web serverworkingyet NO CHARTS.
>
> Problem Seen Here: https://PandionTempest.rf.gd
>
> I'm stumped...any hints to the fix?
>
> Thanks,
>
> -pete
>

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

[weewx-user] No Weewx charts on public server

[Pete AndDebbie]

Strange...

Local (network 10.0.254.83/weewx) Weewx web server works perfectly.
All graphs and charts. Yet, FTPing from that Rpi based weewx web server to 
the public FTP server does not post the charts on the public home page.

Double checked FTP to public web serverworkingyet NO CHARTS.

Problem Seen Here: https://PandionTempest.rf.gd

I'm stumped...any hints to the fix?

Thanks,

-pete

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

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

[kufuu]

Im thinking that on mqtt that rapidfire is only going to post what it gets, 
Rich I increased the archive_interval to 360 and it has been posting every 
reading now, even tipped the rain and it recorded it to WU and to the db. 
will keep an eye on it to see if that stays. thks you guys

On Tuesday, October 31, 2023 at 3:24:05 PM UTC-4 kufuu wrote:

> I did a rain test, weewx is getting the payload and it didnt write it to 
> the db or send it to WU 
>
> Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
> retain: 0, payload: b'{"readings": {"pressure": 950.67, "rain": 0.5588, 
> "wind_speed": 0, "temperature": 7.35, "humidity": 78.11, "wind_direction": 
> 90, "rain_per_second": 0.001856478, "luminance": 81.54}, "nickname": 
> "river-wx", "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
> "2023-10-31T18:40:05Z"}'
> Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
> TopicManager data-> incoming enviro/river-wx: 'luminance': '81.54', 
> 'outHumidity': '78.11', 'outTemp': '7.35', 'pressure': '950.67', 'rain': 
> '0.5588', 'rainPersecond': '0.001856478', 'windDir': '90.0', 'windSpeed': 
> '0.0'
> Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
> '1698777608.1629858', 'luminance': '81.54', 'outHumidity': '78.11', 
> 'outTemp': '7.35', 'pressure': '950.67', 'rain': '0.5588', 'rainPersecond': 
> '0.001856478', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
> Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
> data-> final loop packet is enviro/river-wx 2023-10-31 14:40:08 EDT 
> (1698777608): 'dateTime': '1698777608.1629858', 'luminance': '81.54', 
> 'outHumidity': '78.11', 'outTemp': '7.35', 'pressure': '950.67', 'rain': 
> '0.5588', 'rainPersecond': '0.001856478', 'usUnits': '17', 'windDir': 
> '90.0', 'windSpeed': '0.0'
> Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) No 
> archive topic configured.
> Oct 31 14:40:09 zero-wx weewx[21762] INFO weewx.restx: Wunderground-RF: 
> Published record 2023-10-31 14:40:08 EDT (1698777608)
> Oct 31 14:40:09 zero-wx weewx[21762] INFO weewx.manager: Added record 
> 2023-10-31 14:40:00 EDT (1698777600) to database 'weewx.sdb'
> Oct 31 14:40:09 zero-wx weewx[21762] INFO weewx.manager: Added record 
> 2023-10-31 14:40:00 EDT (1698777600) to daily summary in 'weewx.sdb'
> Oct 31 14:40:09 zero-wx weewx[21762] DEBUG weewx.reportengine: Running 
> reports for latest time in the database.
> Oct 31 14:40:09 zero-wx weewx[21762] DEBUG weewx.reportengine: Running 
> report 'SeasonsReport'
> Oct 31 14:40:10 zero-wx weewx[21762] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Seasons/skin.conf for report 
> 'SeasonsReport'
> Oct 31 14:40:10 zero-wx weewx[21762] DEBUG weewx.cheetahgenerator: Using 
> search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.DisplayOptions', 
> 'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext', 
> 'weewx.cheetahgenerator.JSONHelpers', 'weewx.cheetahgenerator.PlotInfo', 
> 'weewx.cheetahgenerator.SkinInfo', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo']
> Oct 31 14:40:10 zero-wx weewx[21762] DEBUG weewx.manager: Daily summary 
> version is 4.0
> Oct 31 14:40:24 zero-wx weewx[21762] INFO weewx.cheetahgenerator: 
> Generated 8 files for report SeasonsReport in 13.95 seconds
> Oct 31 14:40:24 zero-wx weewx[21762] DEBUG weewx.manager: Daily summary 
> version is 4.0
> Oct 31 14:40:31 zero-wx weewx[21762] INFO weewx.imagegenerator: Generated 
> 8 images for report SeasonsReport in 7.06 seconds
> Oct 31 14:40:31 zero-wx weewx[21762] INFO weewx.reportengine: Copied 0 
> files to /var/weewx/reports
> Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
> 'SmartphoneReport' not enabled. Skipping.
> Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
> 'MobileReport' not enabled. Skipping.
> Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
> 'StandardReport' not enabled. Skipping.
> Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
> 'FTP' not enabled. Skipping.
> Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
> 'RSYNC' not enabled. Skipping.
>
> On Tuesday, October 31, 2023 at 3:16:29 PM UTC-4 vince wrote:
>
>> You might have pain running rapidfire on a pi zero due to how slow it is.
>>
>> See some of the comparative benchmarks at 
>> https://github.com/weewx/weewx/wiki/Benchmarks-of-file-and-image-generation 
>> for 
>> details.
>>
>> On Tuesday, October 31, 2023 at 11:29:56 AM UTC-7 kufuu wrote:
>>
>>> I enabled rapidfire for WU and its sending out the data every reading 
>>> now, as far as the season skin every other packet, I can live with that 
>

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

[kufuu]

I did a rain test, weewx is getting the payload and it didnt write it to 
the db or send it to WU 

Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
retain: 0, payload: b'{"readings": {"pressure": 950.67, "rain": 0.5588, 
"wind_speed": 0, "temperature": 7.35, "humidity": 78.11, "wind_direction": 
90, "rain_per_second": 0.001856478, "luminance": 81.54}, "nickname": 
"river-wx", "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
"2023-10-31T18:40:05Z"}'
Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
TopicManager data-> incoming enviro/river-wx: 'luminance': '81.54', 
'outHumidity': '78.11', 'outTemp': '7.35', 'pressure': '950.67', 'rain': 
'0.5588', 'rainPersecond': '0.001856478', 'windDir': '90.0', 'windSpeed': 
'0.0'
Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
'1698777608.1629858', 'luminance': '81.54', 'outHumidity': '78.11', 
'outTemp': '7.35', 'pressure': '950.67', 'rain': '0.5588', 'rainPersecond': 
'0.001856478', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) 
data-> final loop packet is enviro/river-wx 2023-10-31 14:40:08 EDT 
(1698777608): 'dateTime': '1698777608.1629858', 'luminance': '81.54', 
'outHumidity': '78.11', 'outTemp': '7.35', 'pressure': '950.67', 'rain': 
'0.5588', 'rainPersecond': '0.001856478', 'usUnits': '17', 'windDir': 
'90.0', 'windSpeed': '0.0'
Oct 31 14:40:08 zero-wx weewx[21762] DEBUG user.MQTTSubscribe: (Driver) No 
archive topic configured.
Oct 31 14:40:09 zero-wx weewx[21762] INFO weewx.restx: Wunderground-RF: 
Published record 2023-10-31 14:40:08 EDT (1698777608)
Oct 31 14:40:09 zero-wx weewx[21762] INFO weewx.manager: Added record 
2023-10-31 14:40:00 EDT (1698777600) to database 'weewx.sdb'
Oct 31 14:40:09 zero-wx weewx[21762] INFO weewx.manager: Added record 
2023-10-31 14:40:00 EDT (1698777600) to daily summary in 'weewx.sdb'
Oct 31 14:40:09 zero-wx weewx[21762] DEBUG weewx.reportengine: Running 
reports for latest time in the database.
Oct 31 14:40:09 zero-wx weewx[21762] DEBUG weewx.reportengine: Running 
report 'SeasonsReport'
Oct 31 14:40:10 zero-wx weewx[21762] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Oct 31 14:40:10 zero-wx weewx[21762] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.DisplayOptions', 
'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext', 
'weewx.cheetahgenerator.JSONHelpers', 'weewx.cheetahgenerator.PlotInfo', 
'weewx.cheetahgenerator.SkinInfo', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo']
Oct 31 14:40:10 zero-wx weewx[21762] DEBUG weewx.manager: Daily summary 
version is 4.0
Oct 31 14:40:24 zero-wx weewx[21762] INFO weewx.cheetahgenerator: Generated 
8 files for report SeasonsReport in 13.95 seconds
Oct 31 14:40:24 zero-wx weewx[21762] DEBUG weewx.manager: Daily summary 
version is 4.0
Oct 31 14:40:31 zero-wx weewx[21762] INFO weewx.imagegenerator: Generated 8 
images for report SeasonsReport in 7.06 seconds
Oct 31 14:40:31 zero-wx weewx[21762] INFO weewx.reportengine: Copied 0 
files to /var/weewx/reports
Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. Skipping.
Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
'StandardReport' not enabled. Skipping.
Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 'FTP' 
not enabled. Skipping.
Oct 31 14:40:31 zero-wx weewx[21762] DEBUG weewx.reportengine: Report 
'RSYNC' not enabled. Skipping.

On Tuesday, October 31, 2023 at 3:16:29 PM UTC-4 vince wrote:

> You might have pain running rapidfire on a pi zero due to how slow it is.
>
> See some of the comparative benchmarks at 
> https://github.com/weewx/weewx/wiki/Benchmarks-of-file-and-image-generation 
> for 
> details.
>
> On Tuesday, October 31, 2023 at 11:29:56 AM UTC-7 kufuu wrote:
>
>> I enabled rapidfire for WU and its sending out the data every reading 
>> now, as far as the season skin every other packet, I can live with that 
>> unless its not writing to the DB, I ll have to wait and see about the rain 
>> if its working right.  Thanks again
>>
>> On Tuesday, October 31, 2023 at 1:54:49 PM UTC-4 bell...@gmail.com wrote:
>>
>>> The short answer is that your archive_interval is too short for how 
>>> frequently the weather data is published. In the snippet below you can 
>>> infer that the weather data is published every 5 minutes and the 
>>> archive_interval is probably also 5 minutes. This is resulting in some 
>>> ar

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

[vince]

You might have pain running rapidfire on a pi zero due to how slow it is.

See some of the comparative benchmarks at 
https://github.com/weewx/weewx/wiki/Benchmarks-of-file-and-image-generation for 
details.

On Tuesday, October 31, 2023 at 11:29:56 AM UTC-7 kufuu wrote:

> I enabled rapidfire for WU and its sending out the data every reading now, 
> as far as the season skin every other packet, I can live with that unless 
> its not writing to the DB, I ll have to wait and see about the rain if its 
> working right.  Thanks again
>
> On Tuesday, October 31, 2023 at 1:54:49 PM UTC-4 bell...@gmail.com wrote:
>
>> The short answer is that your archive_interval is too short for how 
>> frequently the weather data is published. In the snippet below you can 
>> infer that the weather data is published every 5 minutes and the 
>> archive_interval is probably also 5 minutes. This is resulting in some 
>> archival intervals not receiving a loop packet.
>>
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:00:09 EDT
>>
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:05:09 EDT
>>
>> Oct 30 19:05:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>> Oct 30 19:05:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>>
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:10:09 EDT
>>
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:15:09 EDT
>>
>> Oct 30 19:15:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>> Oct 30 19:15:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>>
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:20:08 EDT
>>
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:25:08 EDT
>>
>> Oct 30 19:25:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>>
>> Oct 30 19:25:11 zero-wx weewx[6949] INFO weewx.manager: Added record
>>
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:30:08 EDT
>>
>> Note, this is a greatly simplified explanation. WeeWX uses the received 
>> loop packet, archive_interval, and archive_delay to determine when to 
>> create an archive record from the received loop packets.
>>
>> Net, either publish the data more frequently or increase your 
>> archive_interval.
>>
>> rich
>> On Monday, 30 October 2023 at 19:35:07 UTC-4 kufuu wrote:
>>
>>> Ok, this is what I found happening, the other day when I reset the 
>>> weather station pico enviro weather it was sending the payload at 5 min 
>>> intervals example 20:06:09 and it was writing to db and sending the data to 
>>> weather underground every reading, now the clock resets ever so often on 
>>> the weather station and now its example 20:05:09 and its only recording and 
>>> sending to WU every other reading. weewx is up to date and running on a pi 
>>> zero w. Any clues ? Heres a copy of the log
>>>
>>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>>> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
>>> retain: 0, payload: b'{"readings": {"pressure": 950.45, "rain": 0, 
>>> "wind_speed": 0, "temperature": 10.73, "humidity": 86.41, "wind_direction": 
>>> 90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
>>> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
>>> "2023-10-30T23:00:05Z"}'
>>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>>> TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
>>> 'outHumidity': '86.41', 'outTemp': '10.73', 'pressure': '950.45', 'rain': 
>>> '0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
>>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>>> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
>>> '1698706809.1511908', 'luminance': '0.0', 'outHumidity': '86.41', 
>>> 'outTemp': '10.73', 'pressure': '950.45', 'rain': '0.0', 'rainPersecond': 
>>> '0.0', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
>>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>>> data-> final loop packet is enviro/river-wx 2023-10-30 19:00:09 EDT 
>>> (1698706809): 'dateTime': '1698706809.1511908', 'luminance': '0.0', 
>>> 'outHumidity': '86.41', 'outTemp': '10.73', 'pressure': '950.45', 'rain': 
>>> '0.0', 'rainPersecond': '0.0', 'usUnits': '17', 'windDir': '90.0', 
>>> 'windSpeed': '0.0'
>>> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>>> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
>>> retain: 0, payload: b'{"readings": {"pressure": 950.54, "rain": 0, 
>>> "wind_speed": 0, "temperature": 10.58, "humidity": 89.15, "wind_direction": 
>>> 90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
>>> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
>>> "2023-10-30T23:05:05Z"}'
>>> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>>> TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
>>> 'outHumidity': '89.15', 'o

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

[kufuu]

I enabled rapidfire for WU and its sending out the data every reading now, 
as far as the season skin every other packet, I can live with that unless 
its not writing to the DB, I ll have to wait and see about the rain if its 
working right.  Thanks again

On Tuesday, October 31, 2023 at 1:54:49 PM UTC-4 bell...@gmail.com wrote:

> The short answer is that your archive_interval is too short for how 
> frequently the weather data is published. In the snippet below you can 
> infer that the weather data is published every 5 minutes and the 
> archive_interval is probably also 5 minutes. This is resulting in some 
> archival intervals not receiving a loop packet.
>
> data-> final loop packet is enviro/river-wx 2023-10-30 19:00:09 EDT
>
> data-> final loop packet is enviro/river-wx 2023-10-30 19:05:09 EDT
>
> Oct 30 19:05:10 zero-wx weewx[6949] INFO weewx.manager: Added record
> Oct 30 19:05:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>
> data-> final loop packet is enviro/river-wx 2023-10-30 19:10:09 EDT
>
> data-> final loop packet is enviro/river-wx 2023-10-30 19:15:09 EDT
>
> Oct 30 19:15:10 zero-wx weewx[6949] INFO weewx.manager: Added record
> Oct 30 19:15:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>
> data-> final loop packet is enviro/river-wx 2023-10-30 19:20:08 EDT
>
> data-> final loop packet is enviro/river-wx 2023-10-30 19:25:08 EDT
>
> Oct 30 19:25:10 zero-wx weewx[6949] INFO weewx.manager: Added record
>
> Oct 30 19:25:11 zero-wx weewx[6949] INFO weewx.manager: Added record
>
> data-> final loop packet is enviro/river-wx 2023-10-30 19:30:08 EDT
>
> Note, this is a greatly simplified explanation. WeeWX uses the received 
> loop packet, archive_interval, and archive_delay to determine when to 
> create an archive record from the received loop packets.
>
> Net, either publish the data more frequently or increase your 
> archive_interval.
>
> rich
> On Monday, 30 October 2023 at 19:35:07 UTC-4 kufuu wrote:
>
>> Ok, this is what I found happening, the other day when I reset the 
>> weather station pico enviro weather it was sending the payload at 5 min 
>> intervals example 20:06:09 and it was writing to db and sending the data to 
>> weather underground every reading, now the clock resets ever so often on 
>> the weather station and now its example 20:05:09 and its only recording and 
>> sending to WU every other reading. weewx is up to date and running on a pi 
>> zero w. Any clues ? Heres a copy of the log
>>
>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
>> retain: 0, payload: b'{"readings": {"pressure": 950.45, "rain": 0, 
>> "wind_speed": 0, "temperature": 10.73, "humidity": 86.41, "wind_direction": 
>> 90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
>> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
>> "2023-10-30T23:00:05Z"}'
>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>> TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
>> 'outHumidity': '86.41', 'outTemp': '10.73', 'pressure': '950.45', 'rain': 
>> '0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
>> '1698706809.1511908', 'luminance': '0.0', 'outHumidity': '86.41', 
>> 'outTemp': '10.73', 'pressure': '950.45', 'rain': '0.0', 'rainPersecond': 
>> '0.0', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
>> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>> data-> final loop packet is enviro/river-wx 2023-10-30 19:00:09 EDT 
>> (1698706809): 'dateTime': '1698706809.1511908', 'luminance': '0.0', 
>> 'outHumidity': '86.41', 'outTemp': '10.73', 'pressure': '950.45', 'rain': 
>> '0.0', 'rainPersecond': '0.0', 'usUnits': '17', 'windDir': '90.0', 
>> 'windSpeed': '0.0'
>> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
>> retain: 0, payload: b'{"readings": {"pressure": 950.54, "rain": 0, 
>> "wind_speed": 0, "temperature": 10.58, "humidity": 89.15, "wind_direction": 
>> 90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
>> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
>> "2023-10-30T23:05:05Z"}'
>> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>> TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
>> 'outHumidity': '89.15', 'outTemp': '10.58', 'pressure': '950.54', 'rain': 
>> '0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
>> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
>> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
>> '1698707109.1076276', 'luminance': '0.0', 'outHumidity': '89.15', 
>> 'outTemp': '10.58', 'pressure': '9

Re: [weewx-user] Problem with Weewx since 2023-10-31 00H00

[Tom Keffer]

One option is to do "30 days ago", or "4 weeks ago".

On Tue, Oct 31, 2023 at 10:14 AM Remy Lavabre 
wrote:

> Yes well seen Tom (as usual...) and thank you!
> I would NEVER have thought of that on my own! :-(
>
> On the other hand, I put what is below to have the maximum wind speed over
> the past month and the total rain for the month.
>
> What should I put instead to avoid this 31 day problem?
>   Thanks again Tom!
>
>   size="-2">$current($timestamp=$span($month_delta=1).windGust.maxtime.raw).windDir.ordinal_compass
> ($current($span($month_delta=1).windGust.maxtime.raw).windDir) - $span($mon>
> and $month.rain.sum
> Le mardi 31 octobre 2023 à 17:55:17 UTC+1, Tom Keffer a écrit :
>
>> This happens with unwary skins that try to calculate something from "a
>> month ago", when a month has 31 days and the previous month had 30. What is
>> "a month ago" from 31 October? Not 31 September --- it doesn't exist.
>>
>> See Issue #436 .
>>
>> On Tue, Oct 31, 2023 at 9:43 AM Remy Lavabre  wrote:
>>
>>> Hello, Weewx 4.5.2 worked perfectly until 2023-10-30 23:55:00
>>>
>>> Since this date, the Seasons2 skin no longer updates the index.html
>>> file. The Raspberry is not crashed, the database continues to fill normally
>>> and all graphs are generated normally.
>>> The log trace gives the error below.
>>> Does anyone have an idea of what happened at 00:00 on 10/31 and why
>>> there has been this error since then?
>>> thank you
>>>
>>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine:
>>> StdConvert target unit is 0x1
>>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.wxservices:
>>> StdWXCalculate will use data binding wx_binding
>>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Archive
>>> will use data binding wx_binding
>>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Record
>>> generation will be attempted in 'hardware'
>>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Using
>>> archive interval of 300 seconds (specified by hardware)
>>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx:
>>> StationRegistry: Station will be registered.
>>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx:
>>> Wunderground-PWS: Data for station IMILLA3 will be posted
>>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx:
>>> PWSweather: Posting not enabled.
>>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: CWOP:
>>> Posting not enabled.
>>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: WOW:
>>> Posting not enabled.
>>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: AWEKAS:
>>> Posting not enabled.
>>> Oct 31 17:30:27 localhost wee_reports[59221] INFO user.wcloud: service
>>> version is 0.13
>>> Oct 31 17:30:27 localhost wee_reports[59221] INFO user.wcloud: Data will
>>> be uploaded for id=ad400d4705decc9d
>>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine:
>>> 'pyephem' detected, extended almanac data is available
>>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi:
>>> Alarm set for expression 0: "inTemp is not None and inTemp <= 23.0"
>>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi:
>>> Alarm set for expression 1: "inTemp is not None and inTemp <= 64.0"
>>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi:
>>> Alarm set for expression 2: "outTemp is not None and outTemp <= 34.0 and
>>> outTemp > 23.0"
>>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi:
>>> Alarm set for expression 3: "outTemp is not None and outTemp <= 23.0"
>>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi:
>>> Alarm set for expression 4: "outTemp is not None and outTemp <= 14.0"
>>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi:
>>> Alarm set for expression 5: "outTemp is not None and outTemp >= 100.0"
>>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi:
>>> Alarm set for expression 6: "rainRate is not None and rainRate > 0 and
>>> rainRate < 0.59"
>>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi:
>>> Alarm set for expression 7: "rainRate is not None and rainRate >= 0.59 and
>>> rainRate < 0.98"
>>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi:
>>> Alarm set for expression 8: "rainRate is not None and rainRate >= 0.98"
>>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi:
>>> Alarm set for expression 9: "windGust is not None and windGust >= 15.5 and
>>> windGust < 27.7"
>>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi:
>>> Alarm set for expression 10: "windGust is not None and windGust >= 27.7 and
>>> windGust < 31.0"
>>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi:
>>> Alarm set for expression 11: "windGust is not None and windGust >= 31.0 and
>>> windGust < 37.28"
>>> Oct 31 17:30:34 localho

Re: [weewx-user] Having problems with weewx not wrighting all the rain into reports.

[bell...@gmail.com]

The short answer is that your archive_interval is too short for how 
frequently the weather data is published. In the snippet below you can 
infer that the weather data is published every 5 minutes and the 
archive_interval is probably also 5 minutes. This is resulting in some 
archival intervals not receiving a loop packet.

data-> final loop packet is enviro/river-wx 2023-10-30 19:00:09 EDT
data-> final loop packet is enviro/river-wx 2023-10-30 19:05:09 EDT
Oct 30 19:05:10 zero-wx weewx[6949] INFO weewx.manager: Added record
Oct 30 19:05:10 zero-wx weewx[6949] INFO weewx.manager: Added record
data-> final loop packet is enviro/river-wx 2023-10-30 19:10:09 EDT
data-> final loop packet is enviro/river-wx 2023-10-30 19:15:09 EDT
Oct 30 19:15:10 zero-wx weewx[6949] INFO weewx.manager: Added record
Oct 30 19:15:10 zero-wx weewx[6949] INFO weewx.manager: Added record
data-> final loop packet is enviro/river-wx 2023-10-30 19:20:08 EDT
data-> final loop packet is enviro/river-wx 2023-10-30 19:25:08 EDT
Oct 30 19:25:10 zero-wx weewx[6949] INFO weewx.manager: Added record
Oct 30 19:25:11 zero-wx weewx[6949] INFO weewx.manager: Added record
data-> final loop packet is enviro/river-wx 2023-10-30 19:30:08 EDT

Note, this is a greatly simplified explanation. WeeWX uses the received 
loop packet, archive_interval, and archive_delay to determine when to 
create an archive record from the received loop packets.

Net, either publish the data more frequently or increase your 
archive_interval.

rich
On Monday, 30 October 2023 at 19:35:07 UTC-4 kufuu wrote:

> Ok, this is what I found happening, the other day when I reset the weather 
> station pico enviro weather it was sending the payload at 5 min intervals 
> example 20:06:09 and it was writing to db and sending the data to weather 
> underground every reading, now the clock resets ever so often on the 
> weather station and now its example 20:05:09 and its only recording and 
> sending to WU every other reading. weewx is up to date and running on a pi 
> zero w. Any clues ? Heres a copy of the log
>
> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
> retain: 0, payload: b'{"readings": {"pressure": 950.45, "rain": 0, 
> "wind_speed": 0, "temperature": 10.73, "humidity": 86.41, "wind_direction": 
> 90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
> "2023-10-30T23:00:05Z"}'
> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
> 'outHumidity': '86.41', 'outTemp': '10.73', 'pressure': '950.45', 'rain': 
> '0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
> '1698706809.1511908', 'luminance': '0.0', 'outHumidity': '86.41', 
> 'outTemp': '10.73', 'pressure': '950.45', 'rain': '0.0', 'rainPersecond': 
> '0.0', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
> Oct 30 19:00:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> data-> final loop packet is enviro/river-wx 2023-10-30 19:00:09 EDT 
> (1698706809): 'dateTime': '1698706809.1511908', 'luminance': '0.0', 
> 'outHumidity': '86.41', 'outTemp': '10.73', 'pressure': '950.45', 'rain': 
> '0.0', 'rainPersecond': '0.0', 'usUnits': '17', 'windDir': '90.0', 
> 'windSpeed': '0.0'
> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
> retain: 0, payload: b'{"readings": {"pressure": 950.54, "rain": 0, 
> "wind_speed": 0, "temperature": 10.58, "humidity": 89.15, "wind_direction": 
> 90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
> "2023-10-30T23:05:05Z"}'
> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
> 'outHumidity': '89.15', 'outTemp': '10.58', 'pressure': '950.54', 'rain': 
> '0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
> '1698707109.1076276', 'luminance': '0.0', 'outHumidity': '89.15', 
> 'outTemp': '10.58', 'pressure': '950.54', 'rain': '0.0', 'rainPersecond': 
> '0.0', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
> Oct 30 19:05:09 zero-wx weewx[6949] DEBUG user.MQTTSubscribe: (Driver) 
> data-> final loop packet is enviro/river-wx 2023-10-30 19:05:09 EDT 
> (1698707109): 'dateTime': '1698707109.1076276', 'luminance': '0.0', 
> 'outHumidity': '89.15', 'outTemp': '10.58', 'pressure': '950.54', 'rain': 
> '0.0', 'rainPersecond': '0.0', 'usUnits': '17', 'w

Re: [weewx-user] Cascading errors for the Seasons base skin.

[Sylvain M]

It's not joy.
I no longer have access to my Wunderground data with a 401 error message 
like this:

#* ./maj_meteo.sh*













*Using WeeWX configuration file /home/sylvain/weewx-data/weewx.confStarting 
wee_import...Observation history for Weather Underground station 'I*' 
will be imported.Using database binding 'wx_binding', which is bound to 
database 'weewx'Destination table 'archive' unit system is '0x11' 
(METRICWX).Missing derived observations will be calculated.Observations 
timestamped after 2023-10-31 00:05:00 CET (1698707100) and up to 
andincluding 2023-10-31 12:15:00 CET (1698750900) will be imported.Starting 
import...Records covering multiple periods have been identified for 
import.Unable to open Weather Underground station I* or HTTP Error 401: 
Unauthorized Unable to load config file.HTTP Error 401: 
UnauthorizedNothing done, exiting.*

I sent an email to the Feeback service to ask the cause of this blockage 
since there is no quota imposed when the API key is provided to us.
I also requested the restoration of access to my data, explaining that I 
was not a flow vacuum cleaner. Just an amateur tweaking his weather 
software.
I am waiting for a response and action.

Have there ever been flow blockages before?

Furthermore, I still have this duplicate primary key error but in 2022, 
which is the first day of sending data from my weather station. So every 5 
minutes I get these errors that I have absolutely no idea how to resolve. 
I'll only paste the last 10 lines:
#* journalctl -u weewx.service -p err -b -f --since today*
.








*Oct 31 16:49:35 gandalf python3[1297]: weewx[1297] ERROR weewx.manager: 
Unable to add record 2022-07-12 05:45:00 CEST (1657597500) to database 
'weewx': (1062, " Duplicate entry '1657597500' for key 'PRIMARY'")Oct 31 
16:54:35 gandalf python3[1297]: weewx[1297] ERROR weewx.manager: Unable to 
add record 2022-07-12 05:50:00 CEST (1657597800) to database 'weewx': 
(1062, " Duplicate entry '1657597800' for key 'PRIMARY'")Oct 31 16:59:36 
gandalf python3[1297]: weewx[1297] ERROR weewx.manager: Unable to add 
record 2022-07-12 05:55:00 CEST (1657598100) to database 'weewx': (1062, " 
Duplicate entry '1657598100' for key 'PRIMARY'")Oct 31 17:04:36 gandalf 
python3[1297]: weewx[1297] ERROR weewx.manager: Unable to add record 
2022-07-12 06:00:00 CEST (1657598400) to database 'weewx': (1062, " 
Duplicate entry '1657598400' for key 'PRIMARY'")Oct 31 17:09:36 gandalf 
python3[1297]: weewx[1297] ERROR weewx.manager: Unable to add record 
2022-07-12 06:05:00 CEST (1657598700) to database 'weewx': (1062, " 
Duplicate entry '1657598700' for key 'PRIMARY'")Oct 31 17:14:36 gandalf 
python3[1297]: weewx[1297] ERROR weewx.manager: Unable to add record 
2022-07-12 06:10:00 CEST (1657599000) to database 'weewx': (1062, " 
Duplicate entry '1657599000' for key 'PRIMARY'")Oct 31 17:19:37 gandalf 
python3[1297]: weewx[1297] ERROR weewx.manager: Unable to add record 
2022-07-12 06:15:00 CEST (1657599300) to database 'weewx': (1062, " 
Duplicate entry '1657599300' for key 'PRIMARY'")Oct 31 17:24:37 gandalf 
python3[1297]: weewx[1297] ERROR weewx.manager: Unable to add record 
2022-07-12 06:20:00 CEST (1657599600) to database 'weewx': (1062, " 
Duplicate entry '1657599600' for key 'PRIMARY'")Oct 31 17:29:37 gandalf 
python3[1297]: weewx[1297] ERROR weewx.manager: Unable to add record 
2022-07-12 06:25:00 CEST (1657599900) to database 'weewx': (1062, " 
Duplicate entry '1657599900' for key 'PRIMARY'")*
Oct 31 17:34:37 gandalf python3[1297]: weewx[1297] ERROR weewx.manager: 
Unable to add record 2022-07-12 06:30:00 CEST (1657600200) to database 
'weewx': (1062, " Duplicate entry '1657600200' for key 'PRIMARY'")

If you have an explanation and a solution to resolve this error, it would 
be appreciated?

Thank you for your help.

Le lundi 30 octobre 2023 à 21:29:43 UTC+1, gjr80 a écrit :

> When importing records with wee_import primary key duplicate entry log 
> entries indicate a record with the timestamp of the current imported record 
> already exists in the database. This most commonly occurs if the import 
> period overlaps with existing database data. This is normal and not 
> considered an error. In such cases the imported record is discarded and no 
> database changes are made. If the imported record is required rather than 
> the corresponding record in the database, the database record must be 
> deleted and the import performed again. If the database record is to be 
> retained then nothing need be done.
>
> Gary
>
> On Tuesday, 31 October 2023 at 04:50:45 UTC+10 sylvain...@gmail.com wrote:
>
>> Hello Gary.
>>
>> Thank you very much for your work !
>> I updated the weeimport.py file at 6:50 p.m.
>>
>> I created a small bash script (I'm not a programmer) to download my WU 
>> data every hour (I didn't dare to be more greedy). The script is triggered 
>> by the crontab.
>> My script retrieves the last timestamp from the mysql database and uses 
>> it 

Re: [weewx-user] WeeWX in an RV?

[Karen K]

Stefan Gliessmann schrieb am Samstag, 28. Oktober 2023 um 14:53:30 UTC+2:

How can I change the use of latitude & longitude from the stanze [Station] to 
current values from the weewx.sdb $latitude and $longitude for weather 
forecasting? I want to use the most current poisition for forecasting 
either thru Belchertown AerisWeather or weewx-DWD dwd-mosix WeatherService 
with openmeteo.


After some discussion there are some ideas on the weewx-DWD wiki page 
"Wettervorhersage im Wohnmobil" 
.

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

Re: [weewx-user] Problem with Weewx since 2023-10-31 00H00

[Remy Lavabre]

Yes well seen Tom (as usual...) and thank you!
I would NEVER have thought of that on my own! :-(

On the other hand, I put what is below to have the maximum wind speed over 
the past month and the total rain for the month.

What should I put instead to avoid this 31 day problem?
  Thanks again Tom!

 $current($timestamp=$span($month_delta=1).windGust.maxtime.raw).windDir.ordinal_compass
 
($current($span($month_delta=1).windGust.maxtime.raw).windDir) - $span($mon>
and $month.rain.sum
Le mardi 31 octobre 2023 à 17:55:17 UTC+1, Tom Keffer a écrit :

> This happens with unwary skins that try to calculate something from "a 
> month ago", when a month has 31 days and the previous month had 30. What is 
> "a month ago" from 31 October? Not 31 September --- it doesn't exist.
>
> See Issue #436 .
>
> On Tue, Oct 31, 2023 at 9:43 AM Remy Lavabre  wrote:
>
>> Hello, Weewx 4.5.2 worked perfectly until 2023-10-30 23:55:00
>>
>> Since this date, the Seasons2 skin no longer updates the index.html file. 
>> The Raspberry is not crashed, the database continues to fill normally and 
>> all graphs are generated normally.
>> The log trace gives the error below.
>> Does anyone have an idea of what happened at 00:00 on 10/31 and why there 
>> has been this error since then?
>> thank you
>>
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: 
>> StdConvert target unit is 0x1
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.wxservices: 
>> StdWXCalculate will use data binding wx_binding
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Archive 
>> will use data binding wx_binding
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Record 
>> generation will be attempted in 'hardware'
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Using 
>> archive interval of 300 seconds (specified by hardware)
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: 
>> StationRegistry: Station will be registered.
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: 
>> Wunderground-PWS: Data for station IMILLA3 will be posted
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: 
>> PWSweather: Posting not enabled.
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: CWOP: 
>> Posting not enabled.
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: WOW: 
>> Posting not enabled.
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: AWEKAS: 
>> Posting not enabled.
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO user.wcloud: service 
>> version is 0.13
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO user.wcloud: Data will 
>> be uploaded for id=ad400d4705decc9d
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: 'pyephem' 
>> detected, extended almanac data is available
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 0: "inTemp is not None and inTemp <= 23.0"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 1: "inTemp is not None and inTemp <= 64.0"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 2: "outTemp is not None and outTemp <= 34.0 and outTemp 
>> > 23.0"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 3: "outTemp is not None and outTemp <= 23.0"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 4: "outTemp is not None and outTemp <= 14.0"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 5: "outTemp is not None and outTemp >= 100.0"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 6: "rainRate is not None and rainRate > 0 and rainRate < 
>> 0.59"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 7: "rainRate is not None and rainRate >= 0.59 and 
>> rainRate < 0.98"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 8: "rainRate is not None and rainRate >= 0.98"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 9: "windGust is not None and windGust >= 15.5 and 
>> windGust < 27.7"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 10: "windGust is not None and windGust >= 27.7 and 
>> windGust < 31.0"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 11: "windGust is not None and windGust >= 31.0 and 
>> windGust < 37.28"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 12: "windGust is not None and windGust >= 37.28"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.

Re: [weewx-user] Pillow and textsize/textwidth

[Denny Page]

That’s got it, thanks.


> On Oct 31, 2023, at 09:50, Tom Keffer  wrote:
> 
> Sorry about that. Commit 2482eebf also needed to be cherry-picked. Try HEAD 
> now.
> 
> On Tue, Oct 31, 2023 at 9:25 AM Greg Troxel  > wrote:
>> ANTIALIAS was also removed in 10:
>> 
>>   https://pillow.readthedocs.io/en/stable/deprecations.html
>> 
>> I suggest:
>> 
>>   don't set anti_alias
>> 
>>   change the code per the above page
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/rmi8r7ihi8y.fsf%40s1.lexort.com.

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

Re: [weewx-user] Problem with Weewx since 2023-10-31 00H00

[Tom Keffer]

This happens with unwary skins that try to calculate something from "a
month ago", when a month has 31 days and the previous month had 30. What is
"a month ago" from 31 October? Not 31 September --- it doesn't exist.

See Issue #436 .

On Tue, Oct 31, 2023 at 9:43 AM Remy Lavabre  wrote:

> Hello, Weewx 4.5.2 worked perfectly until 2023-10-30 23:55:00
>
> Since this date, the Seasons2 skin no longer updates the index.html file.
> The Raspberry is not crashed, the database continues to fill normally and
> all graphs are generated normally.
> The log trace gives the error below.
> Does anyone have an idea of what happened at 00:00 on 10/31 and why there
> has been this error since then?
> thank you
>
> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: StdConvert
> target unit is 0x1
> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.wxservices:
> StdWXCalculate will use data binding wx_binding
> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Archive
> will use data binding wx_binding
> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Record
> generation will be attempted in 'hardware'
> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Using
> archive interval of 300 seconds (specified by hardware)
> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx:
> StationRegistry: Station will be registered.
> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx:
> Wunderground-PWS: Data for station IMILLA3 will be posted
> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: PWSweather:
> Posting not enabled.
> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: CWOP:
> Posting not enabled.
> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: WOW:
> Posting not enabled.
> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: AWEKAS:
> Posting not enabled.
> Oct 31 17:30:27 localhost wee_reports[59221] INFO user.wcloud: service
> version is 0.13
> Oct 31 17:30:27 localhost wee_reports[59221] INFO user.wcloud: Data will
> be uploaded for id=ad400d4705decc9d
> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: 'pyephem'
> detected, extended almanac data is available
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 0: "inTemp is not None and inTemp <= 23.0"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 1: "inTemp is not None and inTemp <= 64.0"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 2: "outTemp is not None and outTemp <= 34.0 and outTemp
> > 23.0"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 3: "outTemp is not None and outTemp <= 23.0"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 4: "outTemp is not None and outTemp <= 14.0"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 5: "outTemp is not None and outTemp >= 100.0"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 6: "rainRate is not None and rainRate > 0 and rainRate <
> 0.59"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 7: "rainRate is not None and rainRate >= 0.59 and
> rainRate < 0.98"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 8: "rainRate is not None and rainRate >= 0.98"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 9: "windGust is not None and windGust >= 15.5 and
> windGust < 27.7"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 10: "windGust is not None and windGust >= 27.7 and
> windGust < 31.0"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 11: "windGust is not None and windGust >= 31.0 and
> windGust < 37.28"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 12: "windGust is not None and windGust >= 37.28"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 13: "extraTemp6 is not None and extraTemp6 >= 133.0 and
> extraTemp6 < 140.0"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 14: "extraTemp6 is not None and extraTemp6 >= 140.0"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 15: "barometer is not None and barometer < 29.53"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 16: "extraTemp3 is not None and extraTemp3 <= 37.0"
> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm
> set for expression 17: "extraTemp3 is 

Re: [weewx-user] Pillow and textsize/textwidth

[Tom Keffer]

Sorry about that. Commit 2482eebf also needed to be cherry-picked. Try HEAD
now.

On Tue, Oct 31, 2023 at 9:25 AM Greg Troxel  wrote:

> ANTIALIAS was also removed in 10:
>
>   https://pillow.readthedocs.io/en/stable/deprecations.html
>
> I suggest:
>
>   don't set anti_alias
>
>   change the code per the above page
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/rmi8r7ihi8y.fsf%40s1.lexort.com
> .
>

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

[weewx-user] Problem with Weewx since 2023-10-31 00H00

[Remy Lavabre]

Hello, Weewx 4.5.2 worked perfectly until 2023-10-30 23:55:00

Since this date, the Seasons2 skin no longer updates the index.html file. 
The Raspberry is not crashed, the database continues to fill normally and 
all graphs are generated normally.
The log trace gives the error below.
Does anyone have an idea of what happened at 00:00 on 10/31 and why there 
has been this error since then?
thank you

Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: StdConvert 
target unit is 0x1
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.wxservices: 
StdWXCalculate will use data binding wx_binding
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Archive 
will use data binding wx_binding
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Record 
generation will be attempted in 'hardware'
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Using 
archive interval of 300 seconds (specified by hardware)
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: 
StationRegistry: Station will be registered.
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: 
Wunderground-PWS: Data for station IMILLA3 will be posted
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: PWSweather: 
Posting not enabled.
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: CWOP: 
Posting not enabled.
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: WOW: Posting 
not enabled.
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: AWEKAS: 
Posting not enabled.
Oct 31 17:30:27 localhost wee_reports[59221] INFO user.wcloud: service 
version is 0.13
Oct 31 17:30:27 localhost wee_reports[59221] INFO user.wcloud: Data will be 
uploaded for id=ad400d4705decc9d
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: 'pyephem' 
detected, extended almanac data is available
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 0: "inTemp is not None and inTemp <= 23.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 1: "inTemp is not None and inTemp <= 64.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 2: "outTemp is not None and outTemp <= 34.0 and outTemp 
> 23.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 3: "outTemp is not None and outTemp <= 23.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 4: "outTemp is not None and outTemp <= 14.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 5: "outTemp is not None and outTemp >= 100.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 6: "rainRate is not None and rainRate > 0 and rainRate < 
0.59"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 7: "rainRate is not None and rainRate >= 0.59 and 
rainRate < 0.98"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 8: "rainRate is not None and rainRate >= 0.98"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 9: "windGust is not None and windGust >= 15.5 and 
windGust < 27.7"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 10: "windGust is not None and windGust >= 27.7 and 
windGust < 31.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 11: "windGust is not None and windGust >= 31.0 and 
windGust < 37.28"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 12: "windGust is not None and windGust >= 37.28"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 13: "extraTemp6 is not None and extraTemp6 >= 133.0 and 
extraTemp6 < 140.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 14: "extraTemp6 is not None and extraTemp6 >= 140.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 15: "barometer is not None and barometer < 29.53"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 16: "extraTemp3 is not None and extraTemp3 <= 37.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 17: "extraTemp3 is not None and extraTemp3 <= 30.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 18: "extraTemp3 is not None and extraTemp3 >= 80.6"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.healthchecks: 
healthchecks: Using url 
https://hc-ping.com/UKc6fHh3r6GrAGmST3bSpw/weewx-record
Oct 31 17:30:35 localhost wee_reports[59221] INFO user.historygenerator: 
historygenerator.py: Generated 6 tables in 0.34

Re: [weewx-user] Pillow and textsize/textwidth

[Greg Troxel]

ANTIALIAS was also removed in 10:

  https://pillow.readthedocs.io/en/stable/deprecations.html

I suggest:

  don't set anti_alias

  change the code per the above page
  

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

Re: [weewx-user] Pillow and textsize/textwidth

[Denny Page]

With this version against pillow 10.0.1, I am receiving an error for the 
antialias use:

 Caught unrecoverable exception in generator 
'weewx.imagegenerator.ImageGenerator'

   module 'PIL.Image' has no attribute 'ANTIALIAS'

   Traceback (most recent call last):

 File "/home/weewx/bin/weewx/reportengine.py", line 197, in 
run

   obj.start()

 File "/home/weewx/bin/weewx/reportengine.py", line 385, in 
start

   self.run()

 File "/home/weewx/bin/weewx/imagegenerator.py", line 42, 
in run

   self.gen_images(self.gen_ts)

 File "/home/weewx/bin/weewx/imagegenerator.py", line 114, 
in gen_images

   image = plot.render()

   ^

 File "/home/weewx/bin/weeplot/genplot.py", line 230, in 
render

   image.thumbnail((self.image_width / self.anti_alias, 
self.image_height / self.anti_alias), Image.ANTIALIAS)

    
  ^^^

   AttributeError: module 'PIL.Image' has no attribute 
'ANTIALIAS'

   Generator terminated



On Monday, October 30, 2023 at 6:23:27 AM UTC-7 Tom Keffer wrote:

> I've done exactly this. The fix is in the master branch.
>
> Cat22: replace your version of genplot.py with this one 
> 
> .
>
> I'm curious why you can't rollback your version of Pillow. 
>
> On Mon, Oct 30, 2023 at 5:28 AM Greg Troxel  wrote:
>
>> [top posting repaired]
>>
>> Cat22  writes:
>>
>> > On Tuesday, October 24, 2023 at 9:43:55 AM UTC-7 Greg Troxel wrote:
>> >
>> >> Tom Keffer  writes:
>> >>
>> >> > This was fixed in commit dc4ab54
>> >> > <
>> >> 
>> https://github.com/weewx/weewx/commit/dc4ab54b9a5935e7334dc0e9de97e5854204d6e7
>> >> >,
>> >> > to appear in V5.
>> >>
>> >> I did a cherry-pick of this onto master, which succeeded with no
>> >> conflicts. Rerunning setup.py build/install, and then reinstalling
>> >> Pillow 10.0.1 (updating it from 9.x), I am able to run wee_reports with
>> >> no issues.
>> >>
>> >> I rebooted and waited for a new archive interval, and I am getting new
>> >> graphs reliably, as far as I can tell.
>> >>
>> >> So cherry-pick/push on master should be safe.
>>
>> > How do i get this fix? and how do i install it so it only upgrades my 
>> weewx 
>> > without loss of configuration data?
>> > I don't have the option to roll back pillow and I am currently on 
>> pillow 
>> > 10.0.1-1
>> >
>>
>> Ideally, someone who can write the repo would cherry-pick and push to
>> the stable branch, and then you'd just check that out and build.
>> Until then, you'll need to clone the repo, and
>> ```
>> git cherry-pick dc4ab54b9a5935e7334dc0e9de97e5854204d6e7
>> ```
>> and then build.
>>
>> If this sounds mysterious, read this book carefully, and then it will
>> make sense:
>>
>>   https://git-scm.com/book/en/v2
>>
>>
>>
>>
>> -- 
>> You received this message because you are subscribed 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/rmibkcgnvkk.fsf%40s1.lexort.com
>> .
>>
>

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

Re: [weewx-user] Weewx 5.0.0 b13 ftp error 553 Could not create file.

[Tom Keffer]

While you may not have changed anything on the client side, it's quite
possible things have changed on the server side. 553 errors are usually
server-side.

Things to try:

1. Double check that you have write permissions on the server for the
directories that you will be ftp'ing into.
2. Try an FTP client, such as filezilla. Does it get the same errors?
3. While using the FTP client, take a note of the FTP server. What type is
it? Has it had a recent "upgrade"?

If all else fails, post your [[FTP]] section, taking care to obfuscate any
passwords.

-tk


On Mon, Oct 30, 2023 at 10:48 PM Maarten Weerman 
wrote:

> Hi all,
>
> I'm running weewx 5.0.0 build 13 together with Fine Offset WH 3080 and
> both worked fine until this evening.
>
> The wh3080 is known for having a usb lockup every now and then (can be
> anything from 3 days to 4 weeks if all goes well) and today it was that
> time again. So i did what i always do, stopping weewx, resetting the
> station and starting weewx again. After an hour or so i looked up the data
> on my website realizing that it is still not updating.
>
> Taking a look on the error log, i noticed that i get an error 553
> everytime ftpgenerator wanted to upload a file.
> Ftp username, password and server name are correct and i haven't changed
> anything in the weewx.conf
>
> Any ideas what i can do?
>
> Here's the error log
>
> Oct 30 21:00:12 raspberrypi dbus-daemon[1044]: [session uid=1000 pid=1044]
> Activating via systemd: service name='org.gtk.vfs.Metadata'
> unit='gvfs-metadata.service' requested by ':1.10' (uid=1000 pid=1219
> comm="pcmanfm --desktop --profile LXDE-pi ")
> Oct 30 21:00:12 raspberrypi systemd[713]: Starting Virtual filesystem
> metadata service...
> Oct 30 21:00:13 raspberrypi dbus-daemon[1044]: [session uid=1000 pid=1044]
> Successfully activated service 'org.gtk.vfs.Metadata'
> Oct 30 21:00:13 raspberrypi systemd[713]: Started Virtual filesystem
> metadata service.
> Oct 30 21:00:14 raspberrypi dbus-daemon[390]: [system] Activating via
> systemd: service name='org.freedesktop.PackageKit'
> unit='packagekit.service' requested by ':1.48' (uid=1000 pid=1216
> comm="lxpanel --profile LXDE-pi ")
> Oct 30 21:00:14 raspberrypi systemd[1]: Starting PackageKit Daemon...
> Oct 30 21:00:14 raspberrypi PackageKit: daemon start
> Oct 30 21:00:17 raspberrypi dbus-daemon[390]: [system] Successfully
> activated service 'org.freedesktop.PackageKit'
> Oct 30 21:00:17 raspberrypi systemd[1]: Started PackageKit Daemon.
> Oct 30 21:00:23 raspberrypi PackageKit: refresh-cache transaction
> /1684_ceecddcd from uid 1000 finished with success after 6239ms
> +Oct 30 21:00:32 raspberrypi PackageKit: get-updates transaction
> /1686_acbebeae from uid 1000 finished with success after 8775ms
> Oct 30 21:00:51 raspberrypi weewx[1841] INFO weewxd: Initializing weewx
> version 5.0.0b13
> Oct 30 21:00:51 raspberrypi weewx[1841] INFO weewxd: Using Python 3.9.2
> (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
> Oct 30 21:00:51 raspberrypi weewx[1841] INFO weewxd: Located at
> /usr/bin/python3
> Oct 30 21:00:51 raspberrypi weewx[1841] INFO weewxd: Platform
> Linux-5.15.32-v7+-armv7l-with-glibc2.31
> Oct 30 21:00:51 raspberrypi weewx[1841] INFO weewxd: Locale is
> 'de_DE.UTF-8'
> Oct 30 21:00:51 raspberrypi weewx[1841] INFO weewxd: Entry path:
> /usr/local/lib/python3.9/dist-packages/weewxd.py
> Oct 30 21:00:51 raspberrypi weewx[1841] INFO weewxd: Using configuration
> file /home/weewx/weewx.conf
> Oct 30 21:00:51 raspberrypi weewx[1841] INFO weewxd: Debug is 0
> Oct 30 21:00:51 raspberrypi weewx[1841] INFO weewx.engine: Loading station
> type FineOffsetUSB (weewx.drivers.fousb)
> Oct 30 21:00:51 raspberrypi weewx[1841] INFO weewx.drivers.fousb: driver
> version is 1.3
> Oct 30 21:00:51 raspberrypi weewx[1841] INFO weewx.drivers.fousb: polling
> mode is PERIODIC
> Oct 30 21:00:51 raspberrypi weewx[1841] INFO weewx.drivers.fousb: polling
> interval is 60
> Oct 30 21:00:52 raspberrypi weewx[1841] INFO weewx.drivers.fousb: found
> station on USB bus= device=
> Oct 30 21:00:52 raspberrypi weewx[1841] INFO weewx.engine: StdConvert
> target unit is 0x1
> Oct 30 21:00:52 raspberrypi weewx[1841] INFO weewx.wxservices:
> StdWXCalculate will use data binding wx_binding
> Oct 30 21:00:52 raspberrypi weewx[1841] INFO weewx.engine: Archive will
> use data binding wx_binding
> Oct 30 21:00:52 raspberrypi weewx[1841] INFO weewx.engine: Record
> generation will be attempted in 'software'
> Oct 30 21:00:52 raspberrypi weewx[1841] INFO weewx.engine: Using archive
> interval of 300 seconds (software record generation)
> Oct 30 21:00:52 raspberrypi weewx[1841] INFO weewx.restx: StationRegistry:
> Station will be registered.
> Oct 30 21:00:52 raspberrypi weewx[1841] INFO weewx.restx: Wunderground:
> Posting not enabled.
> Oct 30 21:00:52 raspberrypi weewx[1841] INFO weewx.restx: PWSweather:
> Posting not enabled.
> Oct 30 21:00:52 raspberrypi weewx[1841] INFO weewx.restx: CWOP: Posting
> not enabled.

[weewx-user] Re: Rain Underreading: Discrepancies even when importing from csv

[gjr80]

It can be tricky to maintain identical readings at all destinations for 
stations that post to multiple sources, ran in particular can be tricky due 
to it being a (typically) cumulative value whereas other observations are 
typically averages. Small changes or the loss of a single reading usually 
have little effect of weather obs average values but loss of a mm or two of 
rain is noticeable. Timing differences can also cause discrepancies.

You say that 'it underreads rain by a few millimeters everytime' - what 
does that mean, is every packet received by WeeWX under or is every day, 
week or month under? How often is your station posting to ecowitt.net and 
WeeWX? It would be good to see a startup log extract with debug = 1 so we 
can see your station config. If using your station custom posting/upload 
you should be seeing regular intercepts from your station in the WeeWX log, 
are you seeing all posts from your station or are some missing, do all have 
a rain value or are some missing? Sorry but there is likely going to be a 
lot of log analysis to track this down.

In terms of wee_import what does your csv file contain, does it contain 
cumulative rain value or per-archive period values? What does you import 
config file contain? There is a 'rain' config option in the CSV import 
config file  that 
determines how rain values are handled - it needs to be set correctly. if 
the source data is correct tracking down CSV import issues should be very 
straightforward once we have the data and the config being used. Feel free 
to post your CSV source data and import config file here or email to me at 
gjroderick at gmail dot com and I will run through them. 

Gary
On Tuesday, 31 October 2023 at 17:34:53 UTC+10 marlo...@gmail.com wrote:

> I nuked the DB, extracted all the data from ecowitt using @comes 
> https://github.com/comes/ecowitt2weewx
> I then imported it all back in. The data from ecowitt seems correct, 
> still. My yearly rain so far is 824.1mm as per my station 
> https://www.ecowitt.net/home/index?id=68712
>
> After all of this, I still get about half the rainfall in weewx. (490.3mm) 
> https://weewx.simple-earth.org/reports/?yr=2023
>
> It's likely there is a weird field mapping, or table that I just don't 
> understand. Looking at the amount of rain related issues, I'm not alone. 
> Would like to beat this. 
> Please help me save my brain. It's breaking.
>
> On Monday, 30 October 2023 at 13:12:46 UTC+2 Marlon wrote:
>
>> Oct 30 13:08:42 goatbox weewx[116207] DEBUG weewx.reportengine: Report 
>> 'FTP' not enabled. Skipping.
>> Oct 30 13:08:42 goatbox weewx[116207] DEBUG weewx.reportengine: Report 
>> 'RSYNC' not enabled. Skipping.
>> Oct 30 13:08:49 goatbox weewx[116207] DEBUG user.interceptor: empty queue
>> Oct 30 13:08:59 goatbox weewx[116207] DEBUG user.interceptor: empty queue
>> Oct 30 13:09:01 goatbox weewx[116207] DEBUG user.interceptor: POST: 
>> b'PASSKEY=&stationtype=EasyWeatherV1.6.6&dateutc=2023-10-30+11:08:59&tempinf=76.6&humidityin=46&baromrelin=29.661&baromabsin=29.723&tempf=71.6&humidity=44&winddir=72&windspeedmph=3.1&windgustmph=4.5&maxdailygust=15.9&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.008&monthlyrainin=1.118&yearlyrainin=32.445&totalrainin=32.445&solarradiation=831.15&uv=8&wh65batt=0&freq=868M&model=WS2900_V2.01.08'
>> Oct 30 13:09:01 goatbox weewx[116207] DEBUG user.interceptor: raw data: 
>> b'PASSKEY=660D031A3A77C1332DFA76B2C975573C&stationtype=EasyWeatherV1.6.6&dateutc=2023-10-30+11:08:59&tempinf=76.6&humidityin=46&baromrelin=29.661&baromabsin=29.723&tempf=71.6&humidity=44&winddir=72&windspeedmph=3.1&windgustmph=4.5&maxdailygust=15.9&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.008&monthlyrainin=1.118&yearlyrainin=32.445&totalrainin=32.445&solarradiation=831.15&uv=8&wh65batt=0&freq=868M&model=WS2900_V2.01.08'
>> Oct 30 13:09:01 goatbox weewx[116207] DEBUG user.interceptor: using 
>> rain_total 32.445 from yearlyrainin
>> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
>> parameter b'PASSKEY=660D031A3A77C1332DFA76B2C975573C
>> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
>> parameter stationtype=EasyWeatherV1.6.6
>> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
>> parameter baromrelin=29.661
>> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
>> parameter maxdailygust=15.9
>> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
>> parameter rainratein=0.000
>> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
>> parameter eventrainin=0.000
>> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
>> parameter hourlyrainin=0.000
>> Oct 30 13:09:01 goatbox weewx[116207] DEBUG user.interceptor: ignored 
>> parameter weeklyrainin=0.008
>> Oct 30 13:09:01 

[weewx-user] Re: ws28xx: run weewx as non-root user?

[michael.k...@gmx.at]

If the user weewxd is running doesn't have sufficient permissions to access 
the device, you get this error Message:

ERROR weewx.engine: Import of driver failed: The device has no langid 
(permission issue, no string descriptors supported or device error) ()

To fix this, I've added an udev rule.

First, find out vendor and device id:

*pi@rpi:**~$* lsusb
Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Ultra Fit
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
*Bus 001 Device 004: ID : Prototype product Vendor ID Weather 
Direct Light Wireless Device*
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Vendor Id is , device Id is 

Then, create and edit a file with the udev rules:

*pi@rpi:**~$* sudo nano /etc/udev/rules.d/99-ws28xx.rules

The content of the file:

SUBSYSTEM=="usb", ATTR{idVendor}=="", ATTR{idProduct}=="", 
MODE="666"

Restart udev and unplug/replug the device (or restart the machine)

I don't know if there is a better way or if there is any other issue with 
doing it this way, but this gets things working on Raspberry Pi OS :)
vince schrieb am Montag, 30. Oktober 2023 um 22:29:36 UTC+1:

> Yes.  Maybe. What device does it use ?
>
> If you are on a pi using user 'pi' you are a member of group 'dialout' 
> which can access the serial/usb port ala /dev/ttyUSB0 without making any 
> changes.  That's how my VP2 using a serial2usb converter works.
>
> On Monday, October 30, 2023 at 2:20:38 PM UTC-7 michael.k...@gmx.at wrote:
>
>> Can I run weewx as non-root user using the ws28xx driver?
>>
>> I am on raspianOS, is there a device I have to change access rights or is 
>> there a group to add the user to, or some other rule to let unprivileged 
>> users access the device?
>>
>

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

[weewx-user] Re: Rain Underreading: Discrepancies even when importing from csv

[Marlon]

I nuked the DB, extracted all the data from ecowitt using 
@comes https://github.com/comes/ecowitt2weewx
I then imported it all back in. The data from ecowitt seems correct, still. 
My yearly rain so far is 824.1mm as per my 
station https://www.ecowitt.net/home/index?id=68712

After all of this, I still get about half the rainfall in weewx. 
(490.3mm) https://weewx.simple-earth.org/reports/?yr=2023

It's likely there is a weird field mapping, or table that I just don't 
understand. Looking at the amount of rain related issues, I'm not alone. 
Would like to beat this. 
Please help me save my brain. It's breaking.

On Monday, 30 October 2023 at 13:12:46 UTC+2 Marlon wrote:

> Oct 30 13:08:42 goatbox weewx[116207] DEBUG weewx.reportengine: Report 
> 'FTP' not enabled. Skipping.
> Oct 30 13:08:42 goatbox weewx[116207] DEBUG weewx.reportengine: Report 
> 'RSYNC' not enabled. Skipping.
> Oct 30 13:08:49 goatbox weewx[116207] DEBUG user.interceptor: empty queue
> Oct 30 13:08:59 goatbox weewx[116207] DEBUG user.interceptor: empty queue
> Oct 30 13:09:01 goatbox weewx[116207] DEBUG user.interceptor: POST: 
> b'PASSKEY=&stationtype=EasyWeatherV1.6.6&dateutc=2023-10-30+11:08:59&tempinf=76.6&humidityin=46&baromrelin=29.661&baromabsin=29.723&tempf=71.6&humidity=44&winddir=72&windspeedmph=3.1&windgustmph=4.5&maxdailygust=15.9&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.008&monthlyrainin=1.118&yearlyrainin=32.445&totalrainin=32.445&solarradiation=831.15&uv=8&wh65batt=0&freq=868M&model=WS2900_V2.01.08'
> Oct 30 13:09:01 goatbox weewx[116207] DEBUG user.interceptor: raw data: 
> b'PASSKEY=660D031A3A77C1332DFA76B2C975573C&stationtype=EasyWeatherV1.6.6&dateutc=2023-10-30+11:08:59&tempinf=76.6&humidityin=46&baromrelin=29.661&baromabsin=29.723&tempf=71.6&humidity=44&winddir=72&windspeedmph=3.1&windgustmph=4.5&maxdailygust=15.9&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.008&monthlyrainin=1.118&yearlyrainin=32.445&totalrainin=32.445&solarradiation=831.15&uv=8&wh65batt=0&freq=868M&model=WS2900_V2.01.08'
> Oct 30 13:09:01 goatbox weewx[116207] DEBUG user.interceptor: using 
> rain_total 32.445 from yearlyrainin
> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
> parameter b'PASSKEY=660D031A3A77C1332DFA76B2C975573C
> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
> parameter stationtype=EasyWeatherV1.6.6
> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
> parameter baromrelin=29.661
> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
> parameter maxdailygust=15.9
> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
> parameter rainratein=0.000
> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
> parameter eventrainin=0.000
> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
> parameter hourlyrainin=0.000
> Oct 30 13:09:01 goatbox weewx[116207] DEBUG user.interceptor: ignored 
> parameter weeklyrainin=0.008
> Oct 30 13:09:01 goatbox weewx[116207] DEBUG user.interceptor: ignored 
> parameter monthlyrainin=1.118
> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
> parameter totalrainin=32.445
> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
> parameter wh65batt=0
> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
> parameter freq=868M
> Oct 30 13:09:01 goatbox weewx[116207] INFO user.interceptor: unrecognized 
> parameter model=WS2900_V2.01.08'
> Oct 30 13:09:01 goatbox weewx[116207] DEBUG user.interceptor: raw packet: 
> {'dateTime': 1698664139, 'usUnits': 1, 'rain_total': 32.445, 
> 'temperature_in': 76.6, 'humidity_in': 46.0, 'pressure': 29.723, 
> 'temperature_out': 71.6, 'humidity_out': 44.0, 'wind_dir': 72.0, 
> 'wind_speed': 3.1, 'wind_gust': 4.5, 'solar_radiation': 831.15, 'uv': 8.0, 
> 'rain': 0.0}
> Oct 30 13:09:01 goatbox weewx[116207] DEBUG user.interceptor: mapped 
> packet: {'dateTime': 1698664139, 'usUnits': 1, 'pressure': 29.723, 
> 'outHumidity': 44.0, 'inHumidity': 46.0, 'outTemp': 71.6, 'inTemp': 76.6, 
> 'windSpeed': 3.1, 'windGust': 4.5, 'windDir': 72.0, 'radiation': 831.15, 
> 'rain': 0.0, 'UV': 8.0}
> Oct 30 13:09:01 goatbox weewx[116207] INFO weewx.manager: Added record 
> 2023-10-30 13:08:30 SAST (1698664110) to database 'weewx'
> Oct 30 13:09:01 goatbox weewx[116207] INFO weewx.manager: Added record 
> 2023-10-30 13:08:30 SAST (1698664110) to daily summary in 'weewx'
>
> On Monday, 30 October 2023 at 12:53:37 UTC+2 Marlon wrote:
>
>> Hello
>> I recently started using weewx to collect my own weather data (instead of 
>> relying on external sites). The problem is strange. I tried for days, 
>> exhaustively, to fix this - wanted to avoid another support issue here that 
>> wastes your time, but alas.
>>
>> My station is a froggit WH3000 and has always (still does)