Weewx 5.0 with Rpi4 bookworm 64bit

[Stefanos Kalaitzis]

Hi to all and many thanks to creators and to all that contribute to have the best weather software by far

I have already running weewx 4.10.2 (2 stations , one sdr and the other gw1000) with no problem at all and i am very happy . Today i had free time so i decided to try an installation in an other sd card everything from the beginning (rasbian OS ,weewx 5, etc)

I follow the steps of debian installation (apt)  as described in official weewx page and after step 2 i had the following error :

sudo apt update
sudo apt install weewx

Hit:1 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease                          
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease        
Hit:4 http://deb.debian.org/debian bookworm-updates InRelease                  
Get:5 https://weewx.com/apt/python3 buster InRelease [3614 B]        
Err:5 https://weewx.com/apt/python3 buster InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ED444FCCF0E2B09E
Reading package lists... Done
W: GPG error: https://weewx.com/apt/python3 buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ED444FCCF0E2B09E
E: The repository 'https://weewx.com/apt/python3 buster InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package weewx

I hope that i didnt miss something . As i wrote above because i have already running weewx i am not in a hurry so if someone knows what i am doing wrong i would be appreciated

Thank you in advanced

[vince]

As always, look up your exact error message "NO_PUBKEY ED444FCCF0E2B09E" in the group archives, which points you to.....

https://groups.google.com/g/weewx-user/c/AJlPGe61xVU/m/AuOh3oiZAAAJ

Looks like the keys.html file mentioned in the docs still has issues.   I got this error too on a clean deb12 install attempt just now.

[Stefanos Kalaitzis]

Oh 😱 ..!! First of all thank you for the quick reply ... The truth is that i made several searches but not with the key value ..!! I apologise for that !!

Also Something  else ... a question to Gary ...
In weewx saratoga extension the wind and wind gust are always the same .. probably the extension pass wind value to wind gust ! I have the 0.1.7 version . All the others are working fine . See the last messages https://groups.google.com/g/weewx-user/c/DiR9FEVYnb4
Thanks again

--
You received this message because you are subscribed 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/a9f195da-f8a7-4fdb-a6c1-39acb9f9cb2cn%40googlegroups.com.

[matthew wall]

On Wednesday, January 24, 2024 at 12:48:33 PM UTC-5 stefanos...@gmail.com wrote:

  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ED444FCCF0E2B09E

Reading package lists... Done
W: GPG error: https://weewx.com/apt/python3 buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ED444FCCF0E2B09E

sorry about that.  i rearranged the key files before i finished the rest of the release.  keys have been restored.

for future reference: the current keys will always be in https://weewx.com/keys.html, while all of the keys (current and all previous keys) will be in https://weewx.com/keys-old.html.  if you need to install an older deb/rpm that was signed by an older key, use keys-old.  use keys.html for recent systems, since they will probably reject the older keys we used to sign things before 2024.

m

[Stefanos Kalaitzis]

Hi Matthew ... keys still have error ... with keys-old everything is fine

Also what i noticed : when i was trying to install sdr driver even though i was able to run the driver directly , with

PYTHONPATH=/usr/share/weewx python /etc/weewx/bin/user/sdr.py --cmd="rtl_433 -M utc -F json -f 868.2M -R 172"

when i started weewx i had this error:

raspberrypi weewxd[2999]:   File "/etc/weewx/bin/user/sdr.py", line 198, in run
Ιαν 25 19:57:11 raspberrypi weewxd[2999]:     for line in iter(self._fd.readline, ''):
Ιαν 25 19:57:11 raspberrypi weewxd[2999]: ValueError: PyMemoryView_FromBuffer(): info->buf must not be NULL
Ιαν 25 19:57:11 raspberrypi weewxd[2999]:     self.run()
Ιαν 25 19:57:11 raspberrypi weewxd[2999]:   File "/etc/weewx/bin/user/sdr.py", line 198, in run
Ιαν 25 19:57:11 raspberrypi weewxd[2999]:     for line in iter(self._fd.readline, ''):
Ιαν 25 19:57:11 raspberrypi weewxd[2999]: ValueError: PyMemoryView_FromBuffer(): info->buf must not be NULL
Ιαν 25 19:57:11 raspberrypi weewxd[2999]: INFO user.sdr: shutdown complete
Ιαν 25 19:57:11 raspberrypi weewxd[2999]: CRITICAL __main__: Caught WeeWxIOError: rtl_433 process is not running                                                                  
Ιαν 25 19:57:11 raspberrypi weewxd[2999]: CRITICAL __main__:     ****  Waiting 60.0 seconds then retrying... 

The problem solved by reading this:

https://www.instructables.com/rtl-sdr-on-Ubuntu/

and making udev rules

now everyhting working as it should be 

[Paul L. McCord Jr.]

I am also having this issue...

weewx@weewx:~ $ sudo apt update
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease                                  
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease                                            
Get:4 https://weewx.com/apt/python3 buster InRelease [3,614 B]                      
Hit:5 http://archive.raspberrypi.com/debian bookworm InRelease                                
Err:4 https://weewx.com/apt/python3 buster InRelease

  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ED444FCCF0E2B09E
Reading package lists... Done
W: GPG error: https://weewx.com/apt/python3 buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ED444FCCF0E2B09E

E: The repository 'https://weewx.com/apt/python3 buster InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

[vince]

Again - please read Matthew's reply.  When you see that specific message just import the keys-old.html file and it'll work.  Really.

[Paul L. McCord Jr.]

Wow! I stared at this all day and it went right over my head. I did it and it worked. Thank you you both,