Re: [weewx-user] 4.6.x RPMs fail PGP signature validation

[mbat...@gmail.com]

Lucky SO(?)!


On Monday, February 21, 2022 at 7:34:25 AM UTC-6 tke...@gmail.com wrote:

> Matthew Wall signed the last couple of releases. He may have used a 
> different signature. If he did, I don't have access to it, and he is on a 
> small boat in the Caribbean until the end of the month. I'll see if I can 
> contact him.
>
> -tk
>
> On Mon, Feb 21, 2022 at 12:24 AM Scott Shambarger  
> wrote:
>
>> Hi,
>>
>> FYI, all the 4.6.x rpms fail PGP signature validation. The tkeffer key on 
>> weewx.com/keys.html (keyid a0cb255b75bf977c) has signed all previous 
>> releases, but rpms since 4.6.0 are all signed with an unpublished keyid of 
>> 50abae5f15306a67.
>>
>> With a yum/dnf repo configured with gpgcheck=1 this prevents new releases 
>> from passing validation.  Is there a new source for the signing key?
>>
>> Thanks,
>> Scott
>>
>> -- 
>> You received this message because you are subscribed 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/570ff1e2-6bbc-482f-9dea-e2a2f279511cn%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/269855e0-287e-4503-bcbf-4348d734189en%40googlegroups.com.

Re: [weewx-user] logrotate permissions problem

[mbat...@gmail.com]

More info: updated to commit 34ce4e0 and problem returned (corrected with 
chmod after install).  Devuan installed WITHOUT systemd support, I'm using 
sysvinit.
On Saturday, December 18, 2021 at 7:00:35 AM UTC-6 mbat...@gmail.com wrote:

> I upgraded weewx from 4.5.1 to 4.6.0b7 (I use the setup.py method, not the 
> debian package).
>
> On Friday, December 17, 2021 at 1:57:46 PM UTC-6 tke...@gmail.com wrote:
>
>> I think this was fixed in V3.9. What version did you upgrade from?
>>
>> On Fri, Dec 17, 2021 at 9:33 AM mbat...@gmail.com  
>> wrote:
>>
>>> After upgrading my devuan distro to v4, logrotate is now v3.18.0-2, and 
>>> complains that 
>>> /home/weewx/util/logrotate.d/weewx has group write permissions.
>>>
>>>  ls -l shows:
>>>   -rw-rw-r-- 1 root root 810 Nov  1 17:26 
>>> /home/weewx/util/logrotate.d/weewx
>>>
>>> "chmod 644" fixes the problem.
>>>
>>> Thanks!
>>> P
>>>
>>>
>>>
>>> -- 
>>> You received this message because you are subscribed 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/5e1fb815-40f9-48aa-9543-2828e387bb44n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/5e1fb815-40f9-48aa-9543-2828e387bb44n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>

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

Re: [weewx-user] logrotate permissions problem

[mbat...@gmail.com]

I upgraded weewx from 4.5.1 to 4.6.0b7 (I use the setup.py method, not the 
debian package).

On Friday, December 17, 2021 at 1:57:46 PM UTC-6 tke...@gmail.com wrote:

> I think this was fixed in V3.9. What version did you upgrade from?
>
> On Fri, Dec 17, 2021 at 9:33 AM mbat...@gmail.com  
> wrote:
>
>> After upgrading my devuan distro to v4, logrotate is now v3.18.0-2, and 
>> complains that 
>> /home/weewx/util/logrotate.d/weewx has group write permissions.
>>
>>  ls -l shows:
>>   -rw-rw-r-- 1 root root 810 Nov  1 17:26 
>> /home/weewx/util/logrotate.d/weewx
>>
>> "chmod 644" fixes the problem.
>>
>> Thanks!
>> P
>>
>>
>>
>> -- 
>> You received this message because you are subscribed 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/5e1fb815-40f9-48aa-9543-2828e387bb44n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/5e1fb815-40f9-48aa-9543-2828e387bb44n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

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

[weewx-user] logrotate permissions problem

[mbat...@gmail.com]

After upgrading my devuan distro to v4, logrotate is now v3.18.0-2, and 
complains that 
/home/weewx/util/logrotate.d/weewx has group write permissions.

 ls -l shows:
  -rw-rw-r-- 1 root root 810 Nov  1 17:26 /home/weewx/util/logrotate.d/weewx

"chmod 644" fixes the problem.

Thanks!
P
   


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

[weewx-user] Re: Help getting Tempest setup with Weewx on Pi running Debian

[mbat...@gmail.com]

I'm using https://github.com/jjvdgeer/weatherflow-udp


On Sunday, May 23, 2021 at 4:27:25 PM UTC-5 corey...@gmail.com wrote:

> Hello 
>
> Apologies it has been twenty years since I have used Unix so these may be 
> dumb questions.
>
> I have successfully installed the Weewx software onto my PI using Debian 
> Ver 10. Using the SUDO command brings back memories! 
>
> Can anyone recommend a stable driver for the Tempest? I have tried this 
> one https://github.com/captain-coredump/weatherflow-udp. And not much 
> luck. I am assuming that you put the IP address in weatherflow-udp.py in 
> the usr file. I have added it there and it times out. I can't find anywhere 
> to put the IP address in the weewx.conf file. Perhaps I am putting it in 
> the wrong area? If someone could tell me what driver and what line that 
> would be of help.
>
> I would rather pull the data from the Tempest API but could not find a 
> driver. 
>
> Any help appreciated. I have burned about 5 hours on this today. 
>
> Essentially I am trying to get my Tempest to connect directly to CWOP. I 
> know Tempest already pushed to CWOP through its API. I desire to have this 
> eventually publish to a website that my son can utilise for a project that 
> he is working on that would pull the data from CWOP.
>
> Many 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/66a88432-fd53-4898-97a5-f53a7ec52a61n%40googlegroups.com.

[weewx-user] Re: Importing Weatherflow data

[mbat...@gmail.com]

Please keep "us" in the loop... I'm sure I'm going to want to duplicate 
these efforts for my station...
Thanks!

Paul

On Tuesday, February 23, 2021 at 4:06:39 AM UTC-6 gjr80 wrote:

> Hi,
>
> You more or less have it. CSV imports require a header row so that 
> wee_import can identify the source data fields and map them to WeeWX 
> field as per the field map. If the data you intend to import has no header 
> row then you can add one, the field names are not important, the important 
> part is making sure you use the correct field name in the field map.
>
> There is no --test, I think you mean --dry-run instead. Best thing is to 
> work through the CSV import step-by-step instructions 
>  in the 
> Utilities Guide, but I would also revise all of the CSV related sections as 
> well.
>
> In terms of checking the import results, that really comes down to you and 
> how much confirmation you require. In order of increasing complexity you 
> might consider the following:
>
> 1. did the import executed without error?
> 2. did the reported number of records processed and imported match your 
> expectations?
> 3. were there any errors in the log?
> 4. were there any unexplained failures to save a record to database in the 
> log? (a record may not be saved to database because a record for that 
> timestamp already exists)
> 5. do the NOAA month and year reports for the period imported have 
> sensible/expected values?
> 6. did the number of records saved to database match your expectation? 
> (the only way to confirm the number of records saved to database is to 
> count the success 'record added' messga ein the log, unfortunately 
> wee_import is unable to determine how many records are actually saved to 
> database, it can only tell how many records it processed and attempted to 
> save to database)
> 7. does each field of the imported data in the database match the 
> corresponding field/record in the source? (this one is for hardcore users, 
> there are no tools for doing this it is a manual process)
>
> I would do 1-5 but 6 and 7, well that depends on how hard core you are :)
>
> Gary
>
>
> On Tuesday, 23 February 2021 at 16:37:29 UTC+10 david.a@gmail.com 
> wrote:
>
>> sorry, my touchpad has caused early posting!
>> To continue, 
>> 5. Edit the import file to include the field names.
>> 6. run wee-import --test only
>> 7. evaluate results, make corrections
>> 8. run final import
>> 9. restart weewx
>>
>> any way to verify success?
>>
>>
>> On Monday, February 22, 2021 at 10:27:44 PM UTC-8 David Prellwitz wrote:
>>
>>> I'm trying to import (wee_import) two weeks of data from my tempest 
>>> repository held at Weatherflow. The API page example of my data shows no 
>>> header in the csv file. How should i handle this import? should i edit the 
>>> file by adding the first reacord and inserting the proper field names?
>>> i assume the normal approach is to:
>>> 1. create the import config file.
>>> 2. extract the WeatherFlow data use their API.
>>> 3. stop weewx, 
>>> 4. copy current db as backup, 
>>> 5. edit 
>>> 6. 
>>>
>>>

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

Re: [weewx-user] Problem with extension install (SyntaxError: Non-ASCII character)

[mbat...@gmail.com]

UDP broadcasts are not routed between subnets, so unless your weewx host 
has a presence on the weatherlink hub's net, it won't "hear" the hub.

There are a couple of ways (besides "multi-homing" the weewx box) to deal 
with the problem. Ass u me ing your home firewall / router is a Linux box, 
and that you have administrative control of it, one solution is to install 
a UDP replicator (such as this one 
) on your home router.  
Another method (same assumptions) is to use port forwarding, which is 
described here 

.

On Saturday, February 20, 2021 at 12:55:10 PM UTC-6 michael.s...@gmail.com 
wrote:

> should the pi and weatherlink live be on the same subnetwork, because i 
>> dont get data
>>
>
> Yes, to receive the live 2.5 second push updates (wind, rain) both devices 
> must be on the same subnet. They work using UDP broadcasts. The "complete" 
> data set (HTTP) doesn't technically require it, though I haven't tested 
> whether the driver works fine if it never receives a push update (it 
> should).
>
>
> why should i switch to WLL schema, i loose specific data, when i dont do 
>> it?
>>
>  
> The following columns are added in the WLL schema:
>
>- dewpoint and heatindex for up to 9 sensors (default only for 2)
>- wetbulb temperature
>- THW and THSW index ("feels like" temperature)
>- indoor heatindex 
>- "rainCount": how often your rain sensor's spoon got tripped since 
>the last update
>- "rainCountRate": the current rate of spoon tripping
>- "rainSize": the size of the rain sensor spoon *in inches *(as 
>configured in the WLL app or the WeatherLink.com website)
>
> Additionally, daily summaries and units are configured for all new columns 
> (except the last one).
>
>
> regards, Michael
>

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