Concerning my v4 update process I should add some clarification: My Raspi crashed due to a SD card failure, which suddenly change it to read only mode completely. Thus I had an "unerasable backup copy". I took a brand new SD card, installed a brand new Raspian image with Bookworm lite and installed a brand new Weewx (among others, such as lighttpd, docker-home assiastant, and mosquitto). I removed the zigbee gpio extension board, as the raspi had to move into another room, where the Zigbee signal is not available and therefore an original Ikea gateway had to be installed.) Thus I do not need the GPIO any longer, I thought. So I don't know, what the gpio thing is actually good for, concerning Weewx. After installation of Weewx I stopped it and restored weewx data as excellently described in the user's guide weewx.com/docs/4.10/usersguide.htm#Restoring_from_backup. After this, I realized, that I had installed version 5.0.0 now. So I read the version 5 guide, and was afraid, that I messed up with my setup. I then manually copied the user data to /etc/weewx/bin/user, and btw downloaded gw1000.py to the latest version, and checked all /etc/weewx files for weewx.weewx permission. I diffed weewx.conf with weewx.conf-5.0.0 and adopted all changes. I removed the mqtt plugin, because of the paho error (I know, there is a solution for it) and as I do not use it any longer, because there is an addon in home assistant to read Ecowitt data directly. So, everything worked without any problems. Now, when v5.0.1 came out, I upgraded and, again, it worked without any problems. I checked the permissions, which are set to weewx.weewx for all files in /etc/weewx and subfolders and also for the the folder /var/lib/weewx and its files forecast.sdb and weewx.sdb. I have seen, that the "old" user folder was renamed to user-<DateTime> and the new folder is used now. Once again, I edited weewx.conf, version = 5.0.*1* as it still said 5.0.0. Previously this was updated automagically.
Guessing to add weewx to all groups, pi has joined: It is a whole bunch!!! Would it be ok, to add it to the users and gpio group? Thanks Peter vince schrieb am Donnerstag, 8. Februar 2024 um 23:32:03 UTC+1: > See if https://forums.raspberrypi.com/viewtopic.php?t=345917 helps any > for your gpio issue. > > Again here, what user and group is weewx running as? That user needs > correct permissions to be able to access your attached hardware. My guess > is that you need to add the weewx user to the same groups the default pi > user is in. > On Thursday, February 8, 2024 at 1:57:38 PM UTC-8 Vetti52 wrote: > >> After updating to from v5.0.0 to v5-0.1I got this log entry: >> Feb 05 14:59:07 raspbee systemd[1]: weewx.service: Deactivated >> successfully. >> Feb 05 14:59:07 raspbee systemd[1]: Stopped weewx.service - WeeWX. >> Feb 05 14:59:07 raspbee systemd[1]: weewx.service: Consumed 27min 28.104s >> CPU time. >> Feb 05 14:59:39 raspbee systemd[1]: Started weewx.service - WeeWX. >> Feb 05 14:59:45 raspbee weewxd.py[7015]: windy: version is 0.6 >> Feb 05 14:59:45 raspbee weewxd.py[7015]: windy: Data will be uploaded to >> https://stations.windy.com/pws/update >> Feb 05 15:00:25 raspbee weewxd[7015]: 2024-02-05 15:00:25 xCreatePipe: >> Can't set permissions (436) for //.lgd-nfy0, Die Operation ist nicht erlaubt >> Feb 05 15:00:25 raspbee weewxd[7015]: >> /usr/lib/python3/dist-packages/gpiozero/devices.py:295: PinFactoryFallback: >> Falling back from lgpio: [Errno 2] Datei oder Verzeichnis nicht gefunden: >> '.> >> Feb 05 15:00:25 raspbee weewxd[7015]: warnings.warn( >> Feb 05 15:00:26 raspbee weewxd.py[7015]: historygenerator.py: Generated 5 >> tables in 0.15 seconds >> >> Although since then Weewx runs fine, I doubt, that everything works ok. >> After reading this thread, I decided to chown root.weewx for .lgd.nfy0. >> Hope, that is, what it should be. >> I did my upgrade from v4.10.2 according to the user guide for version 4, >> thus install weewx, stop it, copy all files and directories back, as listed >> in the user guide, just edited weewx.conf to match my old configuration >> and started weewx. However, after detecting the "new" user guide for >> version 5, I was no longer sure, that this was the proper way. With the >> latest update to v5.0.1 there is some hope, that at least the permissions >> are clean now. Except of this one. >> Pierre-Yves schrieb am Donnerstag, 8. Februar 2024 um 11:00:36 UTC+1: >> >>> Thanks a lot, very interesting ! >>> >>> Yesterday, as I failed to have weewx 5.1 working properly, I reverted to >>> 4.10.2. >>> >>> My configuration is very similar : >>> - BME280 sensor >>> - AS3953 lightning sensor >>> - SDR driver >>> - Seasons skin >>> - Belchertown skin >>> >>> I am tempted to give a new try... >>> >>> Pierre-Yves >>> >>> Le jeudi 8 février 2024 à 10:40:18 UTC+1, Mks Mk a écrit : >>> >>>> today tried to update my other raspberry pi to weewx v5.01 and this pi >>>> is different than the main weather pi that we use: >>>> 1-bme280 sensor. >>>> 2-sdr >>>> 3-weewx-wxobs skin. >>>> >>>> >>>> after the weewx update we did the following: >>>> sudo usermod -aG dialout weewx >>>> sudo usermod -aG plugdev weewx >>>> sudo systemctl restart udev weewx >>>> >>>> but weewx v5.01 failed with following errors: >>>> -PermissionError: [Errno 13] Permission denied: '/dev/i2c-1', this >>>> error related to bme280 sensor >>>> running this command "sudo usermod -aG i2c weewx" fixed the issue. >>>> >>>> -PermissionError: [Errno 13] Permission denied: >>>> '/usr/share/php/wxobs_weewx.inc', this error related to weewx-wxobs >>>> skin >>>> we are using apache2, doing these changes fixed the issue (thanks to >>>> *glennmckechnie*) >>>> mkdir /etc/weewx/wxobs-tmp >>>> chown weewx.weewx /etc/weewx/wxobs-tmp >>>> edited skin.conf located in /etc/weewx/skins/wxobs/ and uncommenting >>>> line #30 and changing include_path = '/tmp' to become include_path = >>>> '/etc/weewx/wxobs-tmp' >>>> >>>> weewx v5.01 is running ok now on this raspberry pi, hoping the above >>>> step may help someone during the upgrade to weewx v5.01 >>>> >>>> On Wednesday, February 7, 2024 at 7:59:59 PM UTC+3 Tom Keffer wrote: >>>> >>>>> https://www.weewx.com/docs/5.0/upgrade/#weewx-runs-as-the-weewx-user >>>>> >>>>> >>>>> On Wed, Feb 7, 2024 at 8:58 AM Tom Keffer <tke...@gmail.com> wrote: >>>>> >>>>>> I'll add "plughw" to the troubleshooting section. >>>>>> >>>>>> -tk >>>>>> >>>>>> On Wed, Feb 7, 2024 at 8:16 AM Steve Gee <steve...@gmail.com> wrote: >>>>>> >>>>>>> I ended up adding the weewx user to the plughw group which fixed the >>>>>>> problem with rtl_433 not starting: >>>>>>> >>>>>>> sudo adduser weewx plughw >>>>>>> sudo systemctl restart weewx.service >>>>>>> >>>>>>> On Wednesday, February 7, 2024 at 2:14:41 AM UTC-5 František >>>>>>> Slimařík wrote: >>>>>>> >>>>>>>> @Matthew: >>>>>>>> >>>>>>>> That makes sense yep. Thanks a lot for detailed explanation. I >>>>>>>> cannot change port 80 on my hardware so I will review other options :) >>>>>>>> >>>>>>>> st 7. 2. 2024 v 8:08 odesílatel matthew wall <mwall...@gmail.com> >>>>>>>> napsal: >>>>>>>> >>>>>>>>> another option is to put a proxy in front of interceptor. >>>>>>>>> configure interceptor to listen on a high port, say 8080, then run >>>>>>>>> nginx >>>>>>>>> binding to port 80 as a reverse proxy to interceptor, proxying all >>>>>>>>> traffic >>>>>>>>> or just specific requests. >>>>>>>>> >>>>>>>>> m >>>>>>>>> >>>>>>>>> -- >>>>>>>>> You received this message because you are subscribed to a topic in >>>>>>>>> the Google Groups "weewx-user" group. >>>>>>>>> To unsubscribe from this topic, visit >>>>>>>>> https://groups.google.com/d/topic/weewx-user/5BuR3BSQfeY/unsubscribe >>>>>>>>> . >>>>>>>>> To unsubscribe from this group and all its topics, send an email >>>>>>>>> to weewx-user+...@googlegroups.com. >>>>>>>>> To view this discussion on the web visit >>>>>>>>> https://groups.google.com/d/msgid/weewx-user/e8a748e8-5008-4ecc-b5f2-59fad26e8b67n%40googlegroups.com >>>>>>>>> >>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/e8a748e8-5008-4ecc-b5f2-59fad26e8b67n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>> . >>>>>>>>> >>>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "weewx-user" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to weewx-user+...@googlegroups.com. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/weewx-user/3239d8e8-5e87-420a-a660-74666b1847ben%40googlegroups.com >>>>>>> >>>>>>> <https://groups.google.com/d/msgid/weewx-user/3239d8e8-5e87-420a-a660-74666b1847ben%40googlegroups.com?utm_medium=email&utm_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/cb618e49-b109-43b4-9add-0341037b777dn%40googlegroups.com.
