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

[Pierre-Yves]

Hi,

FYI, the line  put 
in the  section of the Belchertown header.html.tmpl file do perfectly 
the job.
In my case  makes the page to be 
automatically refreshed every 5 minutes.

Thanks for the tip

Pierre-Yves

Le mardi 7 mai 2024 à 00:19:23 UTC+2, Dan Chant a écrit :

> Hi Tom,
>
> That has worked a treat, thank you so much for your help and quick 
> response, I really appreciate it.
>
> Thanks,
>
> Dan
>
> On Monday 6 May 2024 at 22:11:49 UTC+1 Tom Keffer wrote:
>
>> The webpages in the Seasons skin do not auto refresh. However, it's easy 
>> enough to add. In the file index.html.tmpl, in the  section add this
>>
>> 
>>
>> where *refresh_interval* is how often to refresh in seconds.
>>
>> On Mon, May 6, 2024 at 2:00 PM Dan Chant  wrote:
>>
>>> Hi,
>>>
>>> I've successfully setup Weewx 5.0.2 using WeatherflowUDP extension on a 
>>> Raspberry Pi 4 running bookworm. I'm hosting the Weewx webpage using nginx 
>>> which displays the weewx webpage successfully but doesn't automatically 
>>> update the page forcing me to manually refresh the page every time I need 
>>> to view an update of the page.
>>>
>>> Does this sound like an issue with Weewx or Nginx? 
>>>
>>> Any help or guidance you are able to offer would be greatly appreciated.
>>>
>>> Thanks,
>>> Dan
>>>
>>>  sudo journalctl -u weewx
>>> May 06 21:14:46 pi4 systemd[1]: Started weewx.service - WeeWX.
>>> May 06 21:14:46 pi4 weewxd[3365]: INFO __main__: Initializing weewxd 
>>> version 5.0.2
>>> May 06 21:14:46 pi4 weewxd[3365]: INFO __main__: Command line: 
>>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>>> May 06 21:14:46 pi4 weewxd[3365]: INFO __main__: Using Python 3.11.2 
>>> (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]
>>> May 06 21:14:46 pi4 weewxd[3365]: INFO __main__: Located at 
>>> /usr/bin/python3
>>> May 06 21:14:46 pi4 weewxd[3365]: INFO __main__: Platform 
>>> Linux-6.6.28+rpt-rpi-v8-aarch64-with-glibc2.36
>>> May 06 21:14:46 pi4 weewxd[3365]: INFO __main__: Locale: 'en_GB.UTF-8'
>>> May 06 21:14:46 pi4 weewxd[3365]: INFO __main__: Entry path: 
>>> /usr/share/weewx/weewxd.py
>>> May 06 21:14:46 pi4 weewxd[3365]: INFO __main__: WEEWX_ROOT: /etc/weewx
>>> May 06 21:14:46 pi4 weewxd[3365]: INFO __main__: Configuration file: 
>>> /etc/weewx/weewx.conf
>>> May 06 21:14:46 pi4 weewxd[3365]: INFO __main__: User module: 
>>> /etc/weewx/bin/user
>>> May 06 21:14:46 pi4 weewxd[3365]: INFO __main__: Debug: 1
>>> May 06 21:14:46 pi4 weewxd[3365]: DEBUG __main__: Initializing engine
>>> May 06 21:14:46 pi4 weewxd[3365]: INFO weewx.engine: Loading station 
>>> type WeatherFlowUDP (user.weatherflowudp)
>>> May 06 21:14:46 pi4 weewxd.py[3365]: weatherflowudp: MainThread: driver 
>>> version is 1.10
>>> May 06 21:14:46 pi4 weewxd.py[3365]: weatherflowudp: MainThread: sensor 
>>> map is {'outTemp': 'air_temperature.ST-00048813.obs_st', 'outHumidity': 
>>> 'relative_humidity.ST-00048813.obs_st', 'pressure': 
>>> 'station_pressure.ST->May 06 21:14:46 pi4 weewxd.py[3365]: weatherflowudp: 
>>> MainThread: *** Sensor names per packet type
>>> May 06 21:14:46 pi4 weewxd.py[3365]: weatherflowudp: MainThread: packet 
>>> obs_air: ('time_epoch', 'station_pressure', 'air_temperature', 
>>> 'relative_humidity', 'lightning_strike_count', 
>>> 'lightning_strike_avg_distance', 'b>May 06 21:14:46 pi4 weewxd.py[3365]: 
>>> weatherflowudp: MainThread: packet obs_sky: ('time_epoch', 'illuminance', 
>>> 'uv', 'rain_accumulated', 'wind_lull', 'wind_avg', 'wind_gust', 
>>> 'wind_direction', 'battery', 'report_inter>May 06 21:14:46 pi4 
>>> weewxd.py[3365]: weatherflowudp: MainThread: packet rapid_wind: 
>>> ('time_epoch', 'wind_speed', 'wind_direction')
>>> May 06 21:14:46 pi4 weewxd.py[3365]: weatherflowudp: MainThread: packet 
>>> evt_precip: time_epoch
>>> May 06 21:14:46 pi4 weewxd.py[3365]: weatherflowudp: MainThread: packet 
>>> evt_strike: ('time_epoch', 'distance', 'energy')
>>> May 06 21:14:46 pi4 weewxd.py[3365]: weatherflowudp: MainThread: packet 
>>> obs_st: ('time_epoch', 'wind_lull', 'wind_avg'

[weewx-user] Re: Permission denied opening serial USB port

[Pierre-Yves]

Hi Barry,
Maybe you should look at 
https://github.com/weewx/weewx/wiki/Understanding-permissions
PY

Le mercredi 5 juin 2024 à 17:21:16 UTC+2, barry manilow a écrit :

> Just installed Weewx 5 and new install of Bookworm 32 bit on Raspberry pi 
> 4. I'm using a USB Serial interface with my Davis Vantage Vue, which has 
> worked perfectly for the past few years.
> After completing setup I started with sudo service weewx start. 
> No data appeared to be sent, so checked weewx status and got this error:
>
>  $ sudo service weewx status
> × weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; preset: 
> enabled)
>  Active: failed (Result: exit-code) since Wed 2024-06-05 16:07:17 BST; 
> 53s ago
>Duration: 299ms
>Docs: https://weewx.com/docs
> Process: 1733 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
> status=4)
>Main PID: 1733 (code=exited, status=4)
> CPU: 299ms
>
> Jun 05 16:07:17 raspberrypi weewxd[1733]: CRITICAL weewx.engine:  
> 
> ^
> Jun 05 16:07:17 raspberrypi weewxd[1733]: CRITICAL weewx.engine:  
>File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 244, in 
> __init__
> Jun 05 16:07:17 raspberrypi weewxd[1733]: CRITICAL weewx.engine:  
>  self.open()
> Jun 05 16:07:17 raspberrypi weewxd[1733]: CRITICAL weewx.engine:  
>File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 325, 
> in open
> Jun 05 16:07:17 raspberrypi weewxd[1733]: CRITICAL weewx.engine:  
>  raise SerialException(msg.errno, "could not open port {}: 
> {}".format(self._port, msg))
> Jun 05 16:07:17 raspberrypi weewxd[1733]: CRITICAL weewx.engine:  
>  serial.serialutil.SerialException: [Errno 13] could not open port 
> /dev/ttyUSB0: [Errno 13] Permission denied: '/dev/ttyUSB0'
> Jun 05 16:07:17 raspberrypi weewxd[1733]: CRITICAL __main__: Unable to 
> load driver: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] 
> Permission denied: '/dev/ttyUSB0'
> Jun 05 16:07:17 raspberrypi weewxd[1733]: CRITICAL __main__:  
>  Exiting...
> Jun 05 16:07:17 raspberrypi systemd[1]: weewx.service: Main process 
> exited, code=exited, status=4/NOPERMISSION
> Jun 05 16:07:17 raspberrypi systemd[1]: weewx.service: Failed with result 
> 'exit-code'
>
> Something has changed with permissions I think, but no idea what. 
> Any ideas on what has happened? 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/ccbd0fd7-ea86-4eaf-8b46-934c7fad82a1n%40googlegroups.com.

Re: [weewx-user] Problem after downgrading

[Pierre-Yves]

Hello George,
Maybe try:
sudo usermod -aG i2c weewx
and 
sudo usermod -aG gpio weewx"

I my case, that fixed the problems I had with the BME280 and as3935 
extensions
PY
Le lundi 18 mars 2024 à 15:52:57 UTC+1, George Nimrodel a écrit :

> I'm making progress...
>
> The last upgrade/downgrade relocated my device's driver (BCRobotics) and 
> extensions file to a new User folder.
>
>  I returned them to the primary User folder. However, upon doing so, I 
> encountered the same error I experienced when I upgraded to version 5.0.2.
>
> Subsequently, I attempted another upgrade to version 5.0.2, and the error 
> persisted:
>
> Mar 18 16:23:41 edessa /weewxd.py[414]: BCRobo: MainThread: W1ThermSensor 
> setup fine.
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: Caught OSError: 
> [Errno 13] Permission denied: '/dev/i2c-1'
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:   Traceback 
> (most recent call last):
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/share/weewx/weewxd.py", line 160, in main
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  engine = weewx.engine.StdEngine(config_dict)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 77, in __init__
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  self.setupStation(config_dict)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 104, in setupStation
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  __import__(driver)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/etc/weewx/bin/user/BCRobotics.py", line 80, in 
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:   i2c = 
> busio.I2C(board.SCL, board.SDA)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/local/lib/python3.7/dist-packages/busio.py", line 32, in __init__
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  self.init(scl, sda, frequency)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/local/lib/python3.7/dist-packages/busio.py", line 107, in init
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  self._i2c = _I2C(portId, mode=_I2C.MASTER, baudrate=frequency)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/local/lib/python3.7/dist-packages/adafruit_blinka/microcontroller/generic_linux/i2c.py",
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  self._i2c_bus = smbus.SMBus(bus_num)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/local/lib/python3.7/dist-packages/Adafruit_PureIO/smbus.py", line 
> 125, in __init__
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  self.open(bus)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__: File 
> "/usr/local/lib/python3.7/dist-packages/Adafruit_PureIO/smbus.py", line 
> 151, in open
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  self._device = open("/dev/i2c-{0}".format(bus), "r+b", buffering=0)
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:  
>  PermissionError: [Errno 13] Permission denied: '/dev/i2c-1'
> Mar 18 16:23:41 edessa weewxd[414]: CRITICAL __main__:   Waiting 
> 10 seconds then retrying... 
>
> I added the weewx user to the group defined on the device.
>
> Station is running but I still get errors from some sensors:
>
> Mar 18 16:47:51 edessa /weewxd.py[416]: BCRobo: MainThread: Error setting 
> up GPIO 17: No access to /dev/mem.  Try running as root!
>
> Another thing I don't understand is how the station reverted to Simulator 
> mode despite keeping the .conf file intact.
>
> On Monday, March 18, 2024 at 3:18:47 PM UTC+2 George Nimrodel wrote:
>
>> Hello again,
>>
>> even after debug=1 I don't see any more information:
>>
>> Mar 18 14:49:45 edessa systemd[1]: Started WeeWX.
>> Mar 18 14:49:48 edessa weewxd[411]: Traceback (most recent call last):
>> Mar 18 14:49:48 edessa weewxd[411]:   File "/usr/share/weewx/weewxd", 
>> line 29, in 
>> Mar 18 14:49:48 edessa weewxd[411]: import user.extensions
>> Mar 18 14:49:48 edessa weewxd[411]: ModuleNotFoundError: No module named 
>> 'user.extensions'
>> Mar 18 14:49:48 edessa systemd[1]: weewx.service: Main process exited, 
>> code=exited, status=1/FAILURE
>> Mar 18 14:49:48 edessa systemd[1]: weewx.service: Failed with result 
>> 'exit-code'.
>>
>> On Monday, March 18, 2024 at 1:13:31 AM UTC+2 Tom Keffer wrote:
>>
>>> Please set debug=1, then restart weewx. Post the log from startup to 
>>> crash.
>>>
>>> The startup gives important clues on where weewxd thinks things are 
>>> located.
>>>
>>> -tk
>>>
>>> On Sun, Mar 17, 2024 at 12:08 PM George Nimrodel  
>>> wrote:
>>>
 Hello everyone,

Re: [weewx-user] Re: Weewx 5.0.2, saving sql-backups on a usb stick fails.

[Pierre-Yves]

Hi Glenn,

I prepared a USB drive formatted as ext4 and did all the steps you 
described. That worked except I had to run an additional "sudo chown 
weewx:weewx /mnt/sqlbackup" after "sudo mount /dev/sdb1 /mnt/sqlbackup" in 
order to have the right group and user (weewx:weewx).

Finally, I succeded to write a backup on the drive.

A strange behavior however: if I umount the drive and mount it again, I do 
not see anymore the backup sub-folder in the file manager but, if I run a 
"ls -al   /mnt/sqlbackup", I can see it on the terminal... File manager 
indicates no sub-folder in sqlbackup directory

pi@raspberrypi:~ $ ls -al   /mnt/sqlbackup
total 28
drwxr-xr-x 4 weewx weewx  4096  4 mars  14:20 .
drwxr-xr-x 3 root  root   4096  4 mars  13:33 ..
drwxr-xr-x 2 weewx weewx  4096  4 mars  14:20 20240304
drwx-- 2 root  root  16384  4 mars  13:22 lost+found

If I connect the USB drive to another computer, the backup folder including 
the 2 usual files is present (visible)...

If I stop weewx and restart the Rpi, I recover a normal behavior and the 
File manager shows all files and folder.

As a conclusion I would say that the problem seems to be fixed, though I 
found the solution a bit complicated and fastidious. I would never have 
found myself how to proceed.

Thanks a lot for your help.

Cheers,
Pierre-Yves

Le lundi 4 mars 2024 à 13:06:41 UTC+1, Glenn McKechnie a écrit :

> And that research will benefit you, so it's worth doing - always.
>
> But as you've found this issue, and as I need to add some notes to the 
> README for weewx-sqlbackup - that cover this new issue. You get the first 
> draft and if it needs adjusting, tell me.
>
> So; In brief, and as the root user (or sudo it) .
>
> *mkdir   /mnt/sqlbackup*
> *chown weewx:weewx   /mnt/sqlbackup *(or chmod whatever)
>
> plug your usb drive in, ( and hopefully the system auto mount will get out 
> of our way).
> Use *dmesg* to identify the partition on this backup drive, then use *fdisk 
> -l* to confirm it (optional). 
> This example uses */dev/sd?1* - you will have something more meaningful.
>
> test it by mounting the drive.
>
> *mount   /dev/sd?1   /mnt/sqlbackup*
> *ls -al   /mnt/sqlbackup*
>
> All okay? Is it what you expect? Then ...
>
> *umount   /mnt/sqlbackup.*
>
> Now, add the following line to your */etc/fstab*  file; perhaps with an 
> appropriate comment
>
> # added a weewx sql backup drive. RTFM with *man fstab*
> */dev/sd?1   /mnt/sqlbackup   ext4   errors=remount-ro   0   0*
>
> Save the file and mount it (and everything else - redundantly) with
> *  mount -a*
>
> I'm assuming it's formatted as *ext4* - adjust as required; and I've 
> specified* 0 0* on that fstab entry to remind me that there are no file / 
> boot up checks on that drive.
>
> That's the gist of it. Tweak as you like.
>
> Ah, and change the skin.conf entry to point to it.
>
>
>
> Cheers
>  Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>
> On Mon, 4 Mar 2024 at 22:13, Pierre-Yves  wrote:
>
>> Thanks a lot Glenn.
>> I need to dig a little deeper into this story of connection under mnt and 
>> mounting via fstab. My knowledge of these tools is a little limited ;-)
>> Pierre-Yves
>>
>> Le lundi 4 mars 2024 à 10:54:26 UTC+1, Glenn McKechnie a écrit :
>>
>>>
>>> On Mon, 4 Mar 2024 at 19:07, Pierre-Yves  wrote:
>>>
>>>> [...]
>>>
>>>
>>>>
>>>> pi@raspberrypi:~ $ ps -adelf | grep [Ww]eewxd
>>>> 4 S *weewx*14866 1  2  80   0 - 26178 -  mars03 ?   
>>>> 00:14:55 python3 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>>>>
>>>> ls -al '/media/pi/WEEWX-BU' returns:
>>>>
>>>> pi@raspberrypi:~ $ ls -al '/media/pi/WEEWX-BU'
>>>> total 273976
>>>> *drwxr-xr-x   5 pi   pi4096  1 janv.  1970  .*
>>>> *drwxrwxrwx+  3 root root  4096  3 mars  17:59  ..*
>>>> -rw-r--r--   1 pi   pi8622 22 déc.  16:46 
>>>> 'as3935(min_strikes).py'
>>>> drwxr-xr-x  12 pi   pi4096  2 mars  14:18  Belchertown
>>>> drwxr-xr-x  12 pi   pi4096  1 mars  18:27  Belchertown-old
>>>> -rw-r--r--   1 pi   pi4156  6 févr. 23:27  bme280wx.py
>>>> -rw-r--r--   1 pi   pi1616  7 févr. 00:00 
>>>>  Commandes-usuelles.txt
>>>> -rw-r--r--   1 pi   pi   40148  1 mars  21:50  graphs.conf
>>>> -rw-r--r--   1 pi   pi  148331 28 juin   2023 'sdr(last).py'
>>>> drwxr-xr-x   5 pi   pi4096

Re: [weewx-user] Re: Weewx 5.0.2, saving sql-backups on a usb stick fails.

[Pierre-Yves]

Thanks a lot Glenn.
I need to dig a little deeper into this story of connection under mnt and 
mounting via fstab. My knowledge of these tools is a little limited ;-)
Pierre-Yves

Le lundi 4 mars 2024 à 10:54:26 UTC+1, Glenn McKechnie a écrit :

>
> On Mon, 4 Mar 2024 at 19:07, Pierre-Yves  wrote:
>
>> [...]
>
>
>>
>> pi@raspberrypi:~ $ ps -adelf | grep [Ww]eewxd
>> 4 S *weewx*14866 1  2  80   0 - 26178 -  mars03 ?   
>> 00:14:55 python3 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>>
>> ls -al '/media/pi/WEEWX-BU' returns:
>>
>> pi@raspberrypi:~ $ ls -al '/media/pi/WEEWX-BU'
>> total 273976
>> *drwxr-xr-x   5 pi   pi4096  1 janv.  1970  .*
>> *drwxrwxrwx+  3 root root  4096  3 mars  17:59  ..*
>> -rw-r--r--   1 pi   pi8622 22 déc.  16:46 'as3935(min_strikes).py'
>> drwxr-xr-x  12 pi   pi4096  2 mars  14:18  Belchertown
>> drwxr-xr-x  12 pi   pi4096  1 mars  18:27  Belchertown-old
>> -rw-r--r--   1 pi   pi4156  6 févr. 23:27  bme280wx.py
>> -rw-r--r--   1 pi   pi1616  7 févr. 00:00  Commandes-usuelles.txt
>> -rw-r--r--   1 pi   pi   40148  1 mars  21:50  graphs.conf
>> -rw-r--r--   1 pi   pi  148331 28 juin   2023 'sdr(last).py'
>> drwxr-xr-x   5 pi   pi4096 28 oct.  18:04  Seasons202310281704
>> -rw-r--r--   1 pi   pi   40047  1 mars  21:28  skin.conf
>> -rw-r--r--   1 pi   pi   36467  1 mars  09:00  weewx.conf
>> -rw-r--r--   1 pi   pi   280235008  2 mars  15:26  weewx.sdb.backup
>>
>> PS: I use also this usb drive for manually saving various files and 
>> folders without any problem (skins, database...)
>>
>> It seems, in view of the table above, that the drive is not properly 
>> mounted with regards to the weewx 5.0.2 rules. I tried to change using 
>> chown, but I got an "operation denied"...
>>
>
> This has me perplexed.
>
> The /media directory seems to be treated differently by the system. I've 
> tried to change ownership / permissions on a test drive and it's not 
> behaving as I expect. 
> I'm able to make those same changes under /mnt so I'm missing something. I 
> need an up-slap to the back of the head, a far stronger cup of coffee or 
> probably just a hefty dose of RTFM. In the meantime, I'll blame systemd :P
>
> If you don't want to relocate that drive (understandable), and you have a 
> spare USB slot then I'd be plugging a fresh drive in under /mnt and 
> mounting it via fstab. You can then manually set the permissions to weewx 
> and they'll stick.
>
> And, if someone knows the answer. I'm all ears
>
> Cheers
>  Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie 
>

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

Re: [weewx-user] Re: Weewx 5.0.2, saving sql-backups on a usb stick fails.

[Pierre-Yves]

Thanks Glenn for feedback.

Below the results:

- Even after a restart of the Pi, I still have the same error.

- ps -adelf | grep [Ww]eewxd returns:

pi@raspberrypi:~ $ ps -adelf | grep [Ww]eewxd
4 S *weewx*14866 1  2  80   0 - 26178 -  mars03 ?   
00:14:55 python3 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf

ls -al '/media/pi/WEEWX-BU' returns:

pi@raspberrypi:~ $ ls -al '/media/pi/WEEWX-BU'
total 273976
*drwxr-xr-x   5 pi   pi4096  1 janv.  1970  .*
*drwxrwxrwx+  3 root root  4096  3 mars  17:59  ..*
-rw-r--r--   1 pi   pi8622 22 déc.  16:46 'as3935(min_strikes).py'
drwxr-xr-x  12 pi   pi4096  2 mars  14:18  Belchertown
drwxr-xr-x  12 pi   pi4096  1 mars  18:27  Belchertown-old
-rw-r--r--   1 pi   pi4156  6 févr. 23:27  bme280wx.py
-rw-r--r--   1 pi   pi1616  7 févr. 00:00  Commandes-usuelles.txt
-rw-r--r--   1 pi   pi   40148  1 mars  21:50  graphs.conf
-rw-r--r--   1 pi   pi  148331 28 juin   2023 'sdr(last).py'
drwxr-xr-x   5 pi   pi4096 28 oct.  18:04  Seasons202310281704
-rw-r--r--   1 pi   pi   40047  1 mars  21:28  skin.conf
-rw-r--r--   1 pi   pi   36467  1 mars  09:00  weewx.conf
-rw-r--r--   1 pi   pi   280235008  2 mars  15:26  weewx.sdb.backup

PS: I use also this usb drive for manually saving various files and folders 
without any problem (skins, database...)

It seems, in view of the table above, that the drive is not properly 
mounted with regards to the weewx 5.0.2 rules. I tried to change using 
chown, but I got an "operation denied"...

Cheers,
Pierre-Yves


Le lundi 4 mars 2024 à 00:47:48 UTC+1, Glenn McKechnie a écrit :

> As the author of sql-backup, I should probably step up here.
>
> I haven't been able to set up a V5 installation yet, so therefore I'm 
> unfamiliar with the changes required but that group change Vince mentioned 
> should be enough - the disk needs rw (read write) for the weewx user, or 
> dialout group.
>
> Did you login/logout to set the group changes that vince mentioned. 
>
>
> https://github.com/weewx/weewx/wiki/Understanding-permissions#how-to-fix-device-permissions
>
> further comments inline below...
>
>
> On Mon, 4 Mar 2024 at 09:39, Pierre-Yves  wrote:
>
>> Thanks Vince for feedback but I remember I already sent this comment. 
>> However, I sent it again. Same result...
>>
>> How can I check I am running weewx as user weewx ?
>>
>
>   ps -adelf | grep [Ww]eewxd
>
> The 3rd column will show the user.
>
>
> Pierre-Yves
>>
>> Mar  3 23:30:31 raspberrypi weewxd[13195]: INFO user.sqlbackup: version 
>> is 0.5
>> Mar  3 23:30:31 raspberrypi weewxd[13195]: DEBUG user.sqlbackup: 
>>  starting from 2024-02-25 23:15:31
>> Mar  3 23:30:31 raspberrypi weewxd[13195]: DEBUG user.sqlbackup: 
>>  databases, sqlite 1 named ['weewx.sdb']
>> Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR user.sqlbackup: [Errno 
>> 13] Permission non accordée: '/media/pi/WEEWX-BU'
>>
>
>
>
> and also,  what's the details for the USB drive 
>   ls -al '/media/pi/WEEWX-BU'
>
> You could always manually mount that drive as the weewx user under (for 
> eg:) /mnt/sql-backup and add an entry to fstab - with suitable permissions. 
> And reflect that change in the skin.conf file
> p.s. I found thumb drives unreliable for backups. They eventually go 
> read-only - the Sans-disk ones I had did that.
>  
>
>> Mar  3 23:30:31 raspberrypi weewxd[13195]: DEBUG weewx.manager: Daily 
>> summary version is 4.0
>>
> [...]
>>
>
>  
>
>> Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
>>   return os.stat(filename).st_mtime
>> Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
>>   FileNotFoundError: [Errno 2] Aucun fichier ou dossier de ce type: 
>> '/tmp/sqlbackup/syslinks.inc'
>>
>
> That error should disappear after the first run - it's due to the manual 
> steps in configuration. 
>
>
> Cheers
>  Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>

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

[weewx-user] Re: Weewx 5.0.2, saving sql-backups on a usb stick fails.

[Pierre-Yves]

Thanks Vince for feedback but I remember I already sent this comment. 
However, I sent it again. Same result...

How can I check I am running weewx as user weewx ?

Pierre-Yves

Mar  3 23:30:31 raspberrypi weewxd[13195]: INFO user.sqlbackup: version is 
0.5
Mar  3 23:30:31 raspberrypi weewxd[13195]: DEBUG user.sqlbackup:  starting 
from 2024-02-25 23:15:31
Mar  3 23:30:31 raspberrypi weewxd[13195]: DEBUG user.sqlbackup: 
 databases, sqlite 1 named ['weewx.sdb']
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR user.sqlbackup: [Errno 13] 
Permission non accordée: '/media/pi/WEEWX-BU'
Mar  3 23:30:31 raspberrypi weewxd[13195]: DEBUG weewx.manager: Daily 
summary version is 4.0
Mar  3 23:30:31 raspberrypi weewxd[13195]: 
/usr/lib/python3/dist-packages/Cheetah/Compiler.py:1686: UserWarning: You 
supplied an empty string for the source!
Mar  3 23:30:31 raspberrypi weewxd[13195]:   warnings.warn("You supplied an 
empty string for the source!", )
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
Evaluation of template /etc/weewx/skins/sqlbackup/index.html.tmpl failed 
with exception ''
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
 Ignoring template /etc/weewx/skins/sqlbackup/index.html.tmpl
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
 Reason: [Errno 2] Aucun fichier ou dossier de ce type: 
'/tmp/sqlbackup/syslinks.inc'
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
  Traceback (most recent call last):
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
File "/usr/share/weewx/weewx/cheetahgenerator.py", line 334, in 
generate
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
  unicode_string = compiled_template.respond()
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
File "_etc_weewx_skins_sqlbackup_index_html_tmpl.py", line 202, in 
respond
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
1685, in _handleCheetahInclude
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
  nestedTemplateClass = compiler.compile(source=source,
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
738, in compile
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
  fileHash += str(os.path.getmtime(file))
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
File "/usr/lib/python3.9/genericpath.py", line 55, in getmtime
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
  return os.stat(filename).st_mtime
Mar  3 23:30:31 raspberrypi weewxd[13195]: ERROR weewx.cheetahgenerator: 
  FileNotFoundError: [Errno 2] Aucun fichier ou dossier de ce type: 
'/tmp/sqlbackup/syslinks.inc'
Mar  3 23:30:31 raspberrypi weewxd[13195]: INFO weewx.cheetahgenerator: 
Generated 0 files for report sqlbackup in 0.06 seconds
Mar  3 23:30:31 raspberrypi weewxd[13195]: INFO weewx.reportengine: Copied 
4 files to /var/www/html/weewx/sqlbackup

Le dimanche 3 mars 2024 à 23:04:56 UTC+1, vince a écrit :

> Permission non accordée: '/media/pi/WEEWX-BU'
>
> You need to give the user running the weewx process to write to the usb 
> stick.   This has come up many many times regarding usb devices and v5.
>
> The command is likely "sudo usermod -aG dialout weewx" if your weewx is 
> running as user 'weewx'.
>
> On Sunday, March 3, 2024 at 1:57:05 PM UTC-8 Pierre-Yves wrote:
>
>> Hello,
>> I am running Weewx on a Rpi4-2GB (user.sdr driver + BME280 and as3935 
>> extensions). That works very well.
>> I am able to save sql-backups on the default directory (/var/tmp/backups) 
>> but I fail to save to a USB stick connected to the Pi USB2 port, with an 
>> [errno 13] error Permission denied: '/media/pi/WEEWX-BU'
>> The same configuration was working properly with Weewx 4.10.2
>>
>> I read and followed the Github wiki but have still the same error.
>>
>> Below, the log, the first part of the sql-backup skin.conf and details on 
>> the usb disk connected.
>>
>> Any clue ?
>>
>> Thanks,
>>
>> Pierre-Yves
>
>

-- 
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/54f3d89e-b14a-436c-b8cb-74d69d1693c3n%40googlegroups.com.

[weewx-user] Weewx 5.0.2, saving sql-backups on a usb stick fails.

[Pierre-Yves]

Hello,
I am running Weewx on a Rpi4-2GB (user.sdr driver + BME280 and as3935 
extensions). That works very well.
I am able to save sql-backups on the default directory (/var/tmp/backups) 
but I fail to save to a USB stick connected to the Pi USB2 port, with an 
[errno 13] error Permission denied: '/media/pi/WEEWX-BU'
The same configuration was working properly with Weewx 4.10.2

I read and followed the Github wiki but have still the same error.

Below, the log, the first part of the sql-backup skin.conf and details on 
the usb disk connected.

Any clue ?

Thanks,

Pierre-Yves

-- 
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/d1062d04-c9ef-4f73-bf23-543b90e6e801n%40googlegroups.com.


sql-backup-log
Description: Binary data

Re: [weewx-user] CRITICAL __main__: Caught WeeWxIOError: rtl_433 process is not running

[Pierre-Yves]

Hello Charlie,

Don't you have in weewx.conf ,[sdr] section, a "sudo" at the beginning of 
your rtl_433 command line ? If yes, try to remove it.

That fixed the problem in my case

Pierre-Yves

Le dimanche 25 février 2024 à 16:20:30 UTC+1, Tom Keffer a écrit :

> I'm not seeing the log. Just the status output from systemctl.
>
> There are many threads about this error in weewx-user. Here's one 
> <https://groups.google.com/g/weewx-user/c/5BuR3BSQfeY/m/liOVdD2xAAAJ>. 
> Try the suggestions in that thread.
>
>
>
> On Sun, Feb 25, 2024 at 6:27 AM Charlie T  wrote:
>
>> *Here's the log...what am I doing wrong?*
>>
>> ● weewx.service - WeeWX
>>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
>> preset: enabled)
>>  Active: active (running) since Sun 2024-02-25 07:21:25 CST; 54min ago
>>Docs: https://weewx.com/docs
>>Main PID: 505 (python3)
>>   Tasks: 1 (limit: 1595)
>> CPU: 3min 44.239s
>>  CGroup: /system.slice/weewx.service
>>  └─505 python3 /usr/share/weewx/weewxd.py 
>> /etc/weewx/weewx.conf
>>
>> Feb 25 08:15:07 raspberrypi weewxd[505]: for line in 
>> iter(self._fd.readline, ''):
>> Feb 25 08:15:07 raspberrypi weewxd[505]: ValueError: 
>> PyMemoryView_FromBuffer(): info->buf must not be NULL
>> Feb 25 08:15:07 raspberrypi weewxd[505]:   File 
>> "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
>> Feb 25 08:15:07 raspberrypi weewxd[505]: self.run()
>> Feb 25 08:15:07 raspberrypi weewxd[505]:   File 
>> "/etc/weewx/bin/user/sdr.py", line 198, in run
>> Feb 25 08:15:07 raspberrypi weewxd[505]: for line in 
>> iter(self._fd.readline, ''):
>> Feb 25 08:15:07 raspberrypi weewxd[505]: ValueError: 
>> PyMemoryView_FromBuffer(): info->buf must not be NULL
>> Feb 25 08:15:07 raspberrypi weewxd[505]: INFO user.sdr: shutdown complete
>> Feb 25 08:15:07 raspberrypi weewxd[505]: CRITICAL __main__: Caught 
>> WeeWxIOError: rtl_433 process is not running
>> Feb 25 08:15:07 raspberrypi weewxd[505]: CRITICAL __main__:  
>>  Waiting 60.0 seconds then retrying...
>>
>> -- 
>> 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/435fd56e-0a1b-4c3d-a333-1eb108ef0432n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/435fd56e-0a1b-4c3d-a333-1eb108ef0432n%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/81561729-c5b1-4e11-a01d-e9d5a87dafd5n%40googlegroups.com.

Re: [weewx-user] Your hardware experience (for running WeeWX, the service)

[Pierre-Yves]

My setup:

RPi4-2GB
Argon-one-M2 case (
https://argon40.com/products/argon-one-m-2-case-for-raspberry-pi-4)
Liteon 16GB M.2 2242 SSD
RTC module integrated into the housing
Homemade ~ 2hrs UPS (5.2 V, 2.5 A)
Bresser WSX3001 (7in1), user.sdr driver
BME280 + AS3935 extensions connected to i2c port

It has been working without problems for 2 years.
A small SSD capacity (16 GB) makes easier regular full disk image backups.
Not sure that a UPS is essential since the Argon-one restarts automatically 
after a power outage (POs very infrequent and always of short duration).

PYB

Le vendredi 23 février 2024 à 15:44:08 UTC+1, Warren Gill a écrit :

> I have been running weewx on a (now discontinued) Odroid HC2 
> https://ameridroid.com/products/odroid-hc2 for several years now, 
> connected to a Vantage Envoy, that collects data from the Vantage Pro . 
> Since it can move its all but the initial uBoot code to SSD it's been super 
> reliable. I would choose Odroid again... the XU4 uses eMMC, or a Lenovo 
> Tiny PC and also use it for Home Assistant and other automation tasks.
>
> On Fri, Feb 23, 2024 at 12:25 AM 'michael.k...@gmx.at' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> I'm curious what hardware you are running WeeWX on, and your experience 
>> with it. So, this is not about the weather station and the sensors, but the 
>> device which is running the service. The reason I ask this here, is because 
>> the issues I experienced with my hardware might be related to weewx and 
>> writing it's logs, and we all know the first rule for posting a question 
>> here :D
>>
>> Since my first WeeWX installation in 2015, I've been using every 
>> generation of the RaspberryPi B, except for the 5th. But looking back it, 
>> has sometimes has been a royal PITA. It's not that I consider the Pi being 
>> bad at all, but I've been having issues with whatever storage I've been 
>> using. SD-Cards were a total disaster, USB flash drives were slightly 
>> better, USB attached SSDs, at least, lasted more than two years before 
>> being attached to the Pi killed them. The only type that didn't fail so 
>> far, was a NFS provided by a QNAP NAS, but this Kind of setup is a bit 
>> complex to maintain, and starting the NAS over, means quite a bit of 
>> downtime for the Pi also.
>>
>> The Pi never was intended to be a server running 24/7, considering this, 
>> it's success in being used as such, is beyond imagination. Anyway, my 
>> experience for the Pi being a storage killer, doesn't seem to be uncommon. 
>> It's original intention was satisfied: I learned a lot about how not to 
>> lose data with unreliable hardware. Since 2015, my database isn't missing 
>> more than one archive value a day in average and the longest gap is about 
>> two hours back in early 2016, using the standard interval of 5 minutes.
>>
>> What hardware are you using, what is your experience?
>> Can you suggest hardware with low power consumption as a requirement?
>> What about the newest generation, like Intel n100 based systems? 
>>
>> -- 
>> 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/69220248-dd7a-4e8a-a7bb-f3251017e0f5n%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/b634ba6d-0b05-42fe-a16e-19736aa34dfcn%40googlegroups.com.

Re: [weewx-user] Re: Weewx Version: 5.0.2-1 issues post upgrade

[Pierre-Yves]

Ok Jeff nice. Sure, it couldn't work with a bad i2c address ;-)

PY

Le jeudi 22 février 2024 à 16:01:08 UTC+1, Pierre-Yves a écrit :

>
> I read this on your log: OSError: "[Errno 121] Remote I/O error"...
>
> Prior installing the BME280 extension, I installed the AS3935 one and I had 
> also to add gpio to weewx group to make my AS3935 lightining detector 
> working.
>
> Maybe try this: "sudo usermod -a -G gpio weewx"
>
> Pierre-Yves
>
>
>
>
>
>
> Le jeudi 22 février 2024 à 14:41:09 UTC+1, Jeff Chabot a écrit :
>
>> Hi Pierre-Yves,
>>
>> Thanks for the suggestion, I just ran that command, uninstalled the 
>> extension and reinstalled it.  Unfortunately, either it didn't help or I am 
>> seeing new issues.  Here are the new errors I am seeing when installing the 
>> bme280wx-master.zip extension:
>>
>> 2024-02-22T08:24:09.936591-05:00 raspberrypi weewxd[861]: Exception in 
>> thread stdout-thread:
>> 2024-02-22T08:24:09.937508-05:00 raspberrypi weewxd[861]: Traceback (most 
>> recent call last):
>> 2024-02-22T08:24:09.937920-05:00 raspberrypi weewxd[861]:   File 
>> "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
>> 2024-02-22T08:24:09.939853-05:00 raspberrypi weewxd[861]: self.run()
>> 2024-02-22T08:24:09.940435-05:00 raspberrypi weewxd[861]:   File 
>> "/etc/weewx/bin/user/sdr.py", line 198, in run
>> 2024-02-22T08:24:09.940815-05:00 raspberrypi weewxd[861]: Exception in 
>> thread stderr-thread:
>> 2024-02-22T08:24:09.941172-05:00 raspberrypi weewxd[861]: Traceback (most 
>> recent call last):
>> 2024-02-22T08:24:09.941502-05:00 raspberrypi weewxd[861]:   File 
>> "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
>> 2024-02-22T08:24:09.942416-05:00 raspberrypi weewxd[861]: for line in 
>> iter(self._fd.readline, ''):
>> 2024-02-22T08:24:09.943319-05:00 raspberrypi weewxd[861]: ValueError: 
>> PyMemoryView_FromBuffer(): info->buf must not be NULL
>> 2024-02-22T08:24:09.944357-05:00 raspberrypi weewxd[861]: self.run()
>> 2024-02-22T08:24:09.945285-05:00 raspberrypi weewxd[861]:   File 
>> "/etc/weewx/bin/user/sdr.py", line 198, in run
>> 2024-02-22T08:24:09.946172-05:00 raspberrypi weewxd[861]: for line in 
>> iter(self._fd.readline, ''):
>> 2024-02-22T08:24:09.946998-05:00 raspberrypi weewxd[861]: ValueError: 
>> PyMemoryView_FromBuffer(): info->buf must not be NULL
>> 2024-02-22T08:24:09.947862-05:00 raspberrypi weewxd[861]: INFO user.sdr: 
>> shutdown complete
>> 2024-02-22T08:24:09.948348-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__: Caught OSError: [Errno 121] Remote I/O error
>> 2024-02-22T08:24:09.952604-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:   Traceback (most recent call last):
>> 2024-02-22T08:24:09.953116-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__: File "/usr/share/weewx/weewxd.py", line 160, in main
>> 2024-02-22T08:24:09.953514-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:   engine = weewx.engine.StdEngine(config_dict)
>> 2024-02-22T08:24:09.953891-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:    ^^^
>> 2024-02-22T08:24:09.954261-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__: File "/usr/share/weewx/weewx/engine.py", line 89, in 
>> __init__
>> 2024-02-22T08:24:09.954633-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:   self.loadServices(config_dict)
>> 2024-02-22T08:24:09.955000-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__: File "/usr/share/weewx/weewx/engine.py", line 157, in 
>> loadServices
>> 2024-02-22T08:24:09.955366-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:   obj = weeutil.weeutil.get_object(svc)(self, 
>> config_dict)
>> 2024-02-22T08:24:09.955737-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:    
>>  ^^
>> 2024-02-22T08:24:09.956185-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__: File "/etc/weewx/bin/user/bme280wx.py", line 61, in 
>> __init__
>> 2024-02-22T08:24:09.956573-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:   self.calibration_params = 
>> bme280.load_calibration_params(self.bus, self.address)
>> 2024-02-22T08:24:09.956997-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:    
>> 

Re: [weewx-user] Re: Weewx Version: 5.0.2-1 issues post upgrade

[Pierre-Yves]

I read this on your log: OSError: "[Errno 121] Remote I/O error"...

Prior installing the BME280 extension, I installed the AS3935 one and I had 
also to add gpio to weewx group to make my AS3935 lightining detector 
working.

Maybe try this: "sudo usermod -a -G gpio weewx"

Pierre-Yves






Le jeudi 22 février 2024 à 14:41:09 UTC+1, Jeff Chabot a écrit :

> Hi Pierre-Yves,
>
> Thanks for the suggestion, I just ran that command, uninstalled the 
> extension and reinstalled it.  Unfortunately, either it didn't help or I am 
> seeing new issues.  Here are the new errors I am seeing when installing the 
> bme280wx-master.zip extension:
>
> 2024-02-22T08:24:09.936591-05:00 raspberrypi weewxd[861]: Exception in 
> thread stdout-thread:
> 2024-02-22T08:24:09.937508-05:00 raspberrypi weewxd[861]: Traceback (most 
> recent call last):
> 2024-02-22T08:24:09.937920-05:00 raspberrypi weewxd[861]:   File 
> "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
> 2024-02-22T08:24:09.939853-05:00 raspberrypi weewxd[861]: self.run()
> 2024-02-22T08:24:09.940435-05:00 raspberrypi weewxd[861]:   File 
> "/etc/weewx/bin/user/sdr.py", line 198, in run
> 2024-02-22T08:24:09.940815-05:00 raspberrypi weewxd[861]: Exception in 
> thread stderr-thread:
> 2024-02-22T08:24:09.941172-05:00 raspberrypi weewxd[861]: Traceback (most 
> recent call last):
> 2024-02-22T08:24:09.941502-05:00 raspberrypi weewxd[861]:   File 
> "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
> 2024-02-22T08:24:09.942416-05:00 raspberrypi weewxd[861]: for line in 
> iter(self._fd.readline, ''):
> 2024-02-22T08:24:09.943319-05:00 raspberrypi weewxd[861]: ValueError: 
> PyMemoryView_FromBuffer(): info->buf must not be NULL
> 2024-02-22T08:24:09.944357-05:00 raspberrypi weewxd[861]: self.run()
> 2024-02-22T08:24:09.945285-05:00 raspberrypi weewxd[861]:   File 
> "/etc/weewx/bin/user/sdr.py", line 198, in run
> 2024-02-22T08:24:09.946172-05:00 raspberrypi weewxd[861]: for line in 
> iter(self._fd.readline, ''):
> 2024-02-22T08:24:09.946998-05:00 raspberrypi weewxd[861]: ValueError: 
> PyMemoryView_FromBuffer(): info->buf must not be NULL
> 2024-02-22T08:24:09.947862-05:00 raspberrypi weewxd[861]: INFO user.sdr: 
> shutdown complete
> 2024-02-22T08:24:09.948348-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__: Caught OSError: [Errno 121] Remote I/O error
> 2024-02-22T08:24:09.952604-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:   Traceback (most recent call last):
> 2024-02-22T08:24:09.953116-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__: File "/usr/share/weewx/weewxd.py", line 160, in main
> 2024-02-22T08:24:09.953514-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:   engine = weewx.engine.StdEngine(config_dict)
> 2024-02-22T08:24:09.953891-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:    ^^^
> 2024-02-22T08:24:09.954261-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__: File "/usr/share/weewx/weewx/engine.py", line 89, in 
> __init__
> 2024-02-22T08:24:09.954633-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:   self.loadServices(config_dict)
> 2024-02-22T08:24:09.955000-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__: File "/usr/share/weewx/weewx/engine.py", line 157, in 
> loadServices
> 2024-02-22T08:24:09.955366-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:   obj = weeutil.weeutil.get_object(svc)(self, 
> config_dict)
> 2024-02-22T08:24:09.955737-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:    
>  ^^
> 2024-02-22T08:24:09.956185-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__: File "/etc/weewx/bin/user/bme280wx.py", line 61, in 
> __init__
> 2024-02-22T08:24:09.956573-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:   self.calibration_params = 
> bme280.load_calibration_params(self.bus, self.address)
> 2024-02-22T08:24:09.956997-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:    
>  ^^
> 2024-02-22T08:24:09.957365-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__: File 
> "/usr/lib/python3/dist-packages/bme280/__init__.py", line 154, in 
> load_calibration_params
> 2024-02-22T08:24:09.957686-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:   compensation_params.dig_T1 = 
> read.unsigned_short(0x88)
> 2024-02-22T08:24:09.958039-05:00 raspberrypi w

[weewx-user] Re: Weewx Version: 5.0.2-1 issues post upgrade

[Pierre-Yves]

Hello Jeff,

For having my BME280 working properly with Weewx 5.0.2.1, I had to add this 
permission: "sudo usermod -aG i2c weewx".
Did you add it already ?

Pierre-Yves

Le jeudi 22 février 2024 à 08:12:08 UTC+1, meteo219 a écrit :

> Hello Weewx Users,
>
> I upgraded weewx tonight on my raspberry pi to version 5.0.2-1 and since 
> doing so, I had some major reconfiguration issues to get things working 
> again.  I upgraded via apt upgrade -y and then choose Y when asked if I 
> wanted to upgrade weewx.conf.  I am thinking that I should have gone with 
> the default of N there.
>
> That said, I was able to fix most things myself by following instructions 
> I found here:
>
>
> https://github.com/weewx/weewx/wiki/Understanding-permissions#the-weewx-user
>
> I am using SDR for most of my data and BME280 for pressure.
>
> The code that I am using for those products in /etc/weewx.conf looks like 
> this:
>
> [SDR]
> # This section is for the software-defined radio driver.
>
> # The driver to use
> driver = user.sdr
>
> cmd = /usr/bin/rtl_433 -M utc -F json -R 40
>
> [[sensor_map]]
> outTemp = temperature.04A5.Acurite5n1PacketV2
> outHumidity = humidity.04A5.Acurite5n1PacketV2
> windDir = wind_dir.04A5.Acurite5n1PacketV2
> windSpeed = wind_speed.04A5.Acurite5n1PacketV2
> rain_total = rain_total.04A5.Acurite5n1PacketV2
>
> [Bme280wx]
> i2c_port = 1
> i2c_address = 0x77
> usUnits = US
> temperatureKeys = inTemp
> temperature_must_have = ""
> pressureKeys = pressure
> pressure_must_have = outTemp
> humidityKeys = inHumidity
> humidity_must_have = ""
>
> I already installed modules using apt:
>
> apt install python3-smbus2
> apt install python3-bme280
>
> That said, I am not seeing any pressure data from bme280.  I ran weectl 
> extension install  bme280wx-master.zip and that added under [[Services]] 
> this line:
>
> data_services = user.bme280wx.Bme280wx
>
> When I restart weewx, I see these errors with debug on:
>
> 2024-02-22T01:52:50.936407-05:00  weewxd[11578]: CRITICAL __main__: 
> File "/etc/weewx/bin/user/bme280wx.py", line 58, in __init__
> 2024-02-22T01:53:00.940567-05:00  weewxd[11578]: DEBUG weewx.engine: 
> Loading service user.bme280wx.Bme280wx
> 2024-02-22T01:53:00.941284-05:00 weewxd.py: bme280: bme280wx configuration 
> {'i2c_port': '1', 'i2c_address': '0x77', 'usUnits': 'US', 
> 'temperatureKeys': 'inTemp', 'temperature_must_have': '', 'pressureKeys': 
> 'pressure', 'pressure_must_have': 'outTemp', 'humidityKeys': 'inHumidity', 
> 'humidity_must_have': ''}
>
> Line 58 of the above file is: self.bus = smbus2.SMBus(self.port) if that 
> helps.
>
> i2c
>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00: -- -- -- -- -- -- -- --
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 70: -- -- -- -- -- -- -- 77
>
> Any ideas on this one?  Things were working great before this upgrade.  I 
> am thinking that I need an updated version of the bme280 script but not 
> sure what is wrong.
>
> Thanks,
>
> Jeff
>
>
>

-- 
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/37300b2e-8d98-4a48-8a38-6314b736a5acn%40googlegroups.com.

[weewx-user] Re: SOLVED as3935 lightining module not detected by I2c on a Rpi4

[Pierre-Yves]

Thanks Karen,
Yes, it is what I understood.
As I explain in my last post, I fixed the problem by extending the range to 
0x03 to 0x77 by the command  sudo i2cdetect -a -y 1 0x03 0x77.
That works perfectly now
PY

Le samedi 17 février 2024 à 08:04:00 UTC+1, Karen K a écrit :

> May be you want to try option -a:
>
> sudo i2cdetect -a -y 1
>
> Adresses below 0x8 are reserved at Raspberry Pi 4. But the lightning 
> module can address 0x0, 0x1, 0x2, or 0x3 only.
>
>

-- 
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/0e8e7602-46d9-4ca8-80e0-f448ee217541n%40googlegroups.com.

[weewx-user] Re: SOLVED as3935 lightining module not detected by I2c on a Rpi4

[Pierre-Yves]

Finally, I succeeded to make the weewx running and capturing AS3935 
lightning detector data

For that, I had to force the detection of the i2c addresses from 0x03 to 
0x77 instead of 0x08 to 0x77 with the command:
sudo i2cdetect -a -y 1 0x03 0x77

I had also to add gpio to weewx group:
sudo usermod -a -G gpio weewx

PYB
Le vendredi 16 février 2024 à 21:30:08 UTC+1, Pierre-Yves a écrit :

> Hello All,
>
> Maybe a bit off-topic. But just in case someone would have faced to this 
> strange behavior of a Raspberry i2c address map.
>
>
> Rpi4-1: usual address map from 0x03 to 7x76.
> Config.:
> Weewx 4.10.2,
> Bresser 7in1,
> sdr driver,
> RTC clock (UU),
> BME280 (0x76) (pressure, temperature, humidity)
> AS3935 (0x03) (lightning detector)
>
> Weewx on Rpi4-1 running without any error.
>
> pi@weewx:~ $ sudo i2cdetect -y 1
>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00:  03 -- -- -- -- -- -- -- -- -- -- -- -- 
> 10: -- -- -- -- -- -- -- -- -- -- 1a -- -- -- -- -- 
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
> 70: -- -- -- -- -- -- 76 -- 
> pi@weewx:~ $ 
>
> Rpi4-2: "abnormal" map with addresses 0x03 to 0x07 non selectable.
> Config.:
> Weewx 5.0.2,
> Bresser 7in1,
> RTC clock (UU),
> AS3935 (??)
>
> Weewx on Rpi4-2 failing : File "/etc/weewx/bin/user/as3935.py", line 182, 
> in __init__GPIO.setup(self.pin, GPIO.IN (see log below)
>
> pi@raspberrypi:~ $ sudo i2cdetect -y 1
>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00: -- -- -- -- -- -- -- -- 
> 10: -- -- -- -- -- -- -- -- -- -- 1a -- -- -- -- -- 
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
> 60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
> 70: -- -- -- -- -- -- -- -- 
> pi@raspberrypi:~ $
>
> Clearly, the AS3935 is not identified because the 0x03 to 0x07 address 
> range is not active. This AS3935 module works on the Rpi4-1
>
> Any idea on where this problem of misconfiguration could come from, 
> firmware, kernel ?
> Is there a way to reset the I2c address map ? 
>
> Thanks,
>
> Pierre-Yves
>

-- 
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/e6f844cb-245c-412e-8e91-6c5d17e3711fn%40googlegroups.com.

[weewx-user] as3935 lightining module not detected by I2c on a Rpi4

[Pierre-Yves]

Hello All,

Maybe a bit off-topic. But just in case someone would have faced to this 
strange behavior of a Raspberry i2c address map.


Rpi4-1: usual address map from 0x03 to 7x76.
Config.:
Weewx 4.10.2,
Bresser 7in1,
sdr driver,
RTC clock (UU),
BME280 (0x76) (pressure, temperature, humidity)
AS3935 (0x03) (lightning detector)

Weewx on Rpi4-1 running without any error.

pi@weewx:~ $ sudo i2cdetect -y 1
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:  03 -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- 1a -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- 76 -- 
pi@weewx:~ $ 

Rpi4-2: "abnormal" map with addresses 0x03 to 0x07 non selectable.
Config.:
Weewx 5.0.2,
Bresser 7in1,
RTC clock (UU),
AS3935 (??)

Weewx on Rpi4-2 failing : File "/etc/weewx/bin/user/as3935.py", line 182, 
in __init__GPIO.setup(self.pin, GPIO.IN (see log below)

pi@raspberrypi:~ $ sudo i2cdetect -y 1
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- 1a -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- -- 
pi@raspberrypi:~ $

Clearly, the AS3935 is not identified because the 0x03 to 0x07 address 
range is not active. This AS3935 module works on the Rpi4-1

Any idea on where this problem of misconfiguration could come from, 
firmware, kernel ?
Is there a way to reset the I2c address map ? 

Thanks,

Pierre-Yves

-- 
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/84bae39e-6dc2-4efa-b6c5-a8d87d03e1bfn%40googlegroups.com.


I2c-address-map-bug-log
Description: Binary data

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

[Pierre-Yves]

Wahoo Gary ! You are a genius ;-) Thanks a lot

I would never have searched the bug here. it works perfectly now.

Thanks to all you guys too, who patiently answered my posts

Pierre-Yves

Le mercredi 14 février 2024 à 10:30:40 UTC+1, gjr80 a écrit :

> WeeWX is being run just fine, the error is in the [SDR] stanza in 
> weewx.conf. As is often the case the clue is in the log:
>
> Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown process 
> sudo 
> /usr/local/bin/rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k -R 
> 173 - R 172 -R 42 -M utc -F json
>
> Almost certainly the command to run rtl_433 at the cmd setting includes 
> sudo. Remove the sudo and it should be fine.
>
> Gary
>
>

-- 
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/e30461d2-1e1c-4354-98c6-93ed89e0c59bn%40googlegroups.com.

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

[Pierre-Yves]

Just an idea...

Could the problem come from the fact I installed rtl-sdr and rtl_433 prior 
to install weewx 5.0.2 ?

PY

Le mercredi 14 février 2024 à 10:02:54 UTC+1, Pierre-Yves a écrit :

> hello Dominic,
>
> Thanks for feedback.
>
> Unfortunately, I don't see any "sudo" in the file 
> "/lib/systemd/system/weewx.service". See below:
>
> # systemd service configuration file for WeeWX
>
> [Unit]
> Description=WeeWX
> Documentation=https://weewx.com/docs
> Requires=time-sync.target
> After=time-sync.target
> Wants=network-online.target
> After=network-online.target
>
> [Service]
> ExecStart=weewxd /etc/weewx/weewx.conf
> StandardOutput=null
> StandardError=journal+console
> RuntimeDirectory=weewx
> RuntimeDirectoryMode=775
> User=weewx
> Group=weewx
>
> [Install]
> WantedBy=multi-user.target
>
> Pierre-Yves
>
> Le mercredi 14 février 2024 à 09:33:15 UTC+1, Dominic Reich a écrit :
>
>> Hello, i replied inline. 
>>
>> Pierre-Yves  wrote: 
>>
>> >Thanks Vince 
>> > 
>> >I found in rtl-sdr. rules a rule corresponding to my SDR stick : 
>> > 
>> >SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", 
>> ENV 
>> >{ID_SOFTWARE_RADIO}="1", MODE="0660", GROUP="plugdev" 
>> > 
>> >I added the weewx user to that group: "sudo usermod -aG plugdev weewx" 
>> > 
>> >I still can start weewx with the  "sudo weewd" command as before but I 
>> can't 
>> >run weewx in daemon mode. "sudo  systemctl start weewx" gives still the 
>> same 
>> >error : 
>> > 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Starting 
>> main 
>> >packet loop. 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: Nous espérons 
>> que 
>> >vous avez reçu de votre administrateur système local 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: les consignes 
>> >traditionnelles. Généralement, elles se concentrent sur ces trois 
>> éléments : 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #1) 
>> Respectez la 
>> >vie privée des autres. 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #2) 
>> Réfléchissez 
>> >avant d'utiliser le clavier. 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #3) De 
>> grands 
>> >pouvoirs confèrent de grandes responsabilités. 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: un 
>> terminal est 
>> >requis pour lire le mot de passe; utilisez soit l'option -S pour lire 
>> depuis 
>> >l'entrée standard ou configurez un outil askpass de demande de mot de 
>> passe 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: il est 
>> >nécessaire de saisir un mot de passe 
>>
>> I don't speak french, but it looks like you still have a sudo command 
>> somewhere in your unit file. 
>>
>> Would you please show us the contents of your running unit file 
>>
>> systemctl show -P FragmentPath weewx.service 
>>
>> will get you the path of that file. cat that file and paste it here or 
>> if you are confident remove the sudo statement in there somwhere at 
>> ExecStart...="sudo /usr.." 
>>
>> because you should not need sudo when you added weewx to the plugdev 
>> group. 
>>
>> That file contains usually also the information what user runs the 
>> daemon in the end. 
>>
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Main loop 
>> exiting. 
>> >Shutting engine down. 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown 
>> process sudo 
>> >/usr/local/bin/rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k 
>> -R 173 
>> >-R 172 -R 42 -M utc -F json 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stdout 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stderr 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread 
>> stdout-thread: 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown 
>> >stdout-thread 
>> >Feb 14 08:49:54 raspberrypi weewxd[5

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

[Pierre-Yves]

hello Dominic,

Thanks for feedback.

Unfortunately, I don't see any "sudo" in the file 
"/lib/systemd/system/weewx.service". See below:

# systemd service configuration file for WeeWX

[Unit]
Description=WeeWX
Documentation=https://weewx.com/docs
Requires=time-sync.target
After=time-sync.target
Wants=network-online.target
After=network-online.target

[Service]
ExecStart=weewxd /etc/weewx/weewx.conf
StandardOutput=null
StandardError=journal+console
RuntimeDirectory=weewx
RuntimeDirectoryMode=775
User=weewx
Group=weewx

[Install]
WantedBy=multi-user.target

Pierre-Yves

Le mercredi 14 février 2024 à 09:33:15 UTC+1, Dominic Reich a écrit :

> Hello, i replied inline.
>
> Pierre-Yves  wrote:
>
> >Thanks Vince
> >
> >I found in rtl-sdr. rules a rule corresponding to my SDR stick :
> >
> >SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", ENV
> >{ID_SOFTWARE_RADIO}="1", MODE="0660", GROUP="plugdev"
> >
> >I added the weewx user to that group: "sudo usermod -aG plugdev weewx"
> >
> >I still can start weewx with the  "sudo weewd" command as before but I 
> can't
> >run weewx in daemon mode. "sudo  systemctl start weewx" gives still the 
> same
> >error :
> >
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Starting main
> >packet loop.
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: Nous espérons 
> que
> >vous avez reçu de votre administrateur système local
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: les consignes
> >traditionnelles. Généralement, elles se concentrent sur ces trois 
> éléments :
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #1) 
> Respectez la
> >vie privée des autres.
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #2) 
> Réfléchissez
> >avant d'utiliser le clavier.
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #3) De 
> grands
> >pouvoirs confèrent de grandes responsabilités.
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: un 
> terminal est
> >requis pour lire le mot de passe; utilisez soit l'option -S pour lire 
> depuis
> >l'entrée standard ou configurez un outil askpass de demande de mot de 
> passe
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: il est
> >nécessaire de saisir un mot de passe
>
> I don't speak french, but it looks like you still have a sudo command
> somewhere in your unit file.
>
> Would you please show us the contents of your running unit file
>
> systemctl show -P FragmentPath weewx.service
>
> will get you the path of that file. cat that file and paste it here or
> if you are confident remove the sudo statement in there somwhere at
> ExecStart...="sudo /usr.."
>
> because you should not need sudo when you added weewx to the plugdev
> group.
>
> That file contains usually also the information what user runs the
> daemon in the end.
>
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Main loop 
> exiting.
> >Shutting engine down.
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown process 
> sudo
> >/usr/local/bin/rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k 
> -R 173
> >-R 172 -R 42 -M utc -F json
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stdout
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stderr
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread 
> stdout-thread:
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown
> >stdout-thread
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call 
> last):
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread 
> stderr-thread:
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call 
> last):
> >Feb 14 08:49:54 raspberrypi weewxd[5905]:   File "/usr/lib/python3.9/
> >threading.py", line 954, in _bootstrap_inner
> >Feb 14 08:49:54 raspberrypi weewxd[5905]:   File "/usr/lib/python3.9/
> >threading.py", line 954, in _bootstrap_inner
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: self.run()
> >Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
> "/etc/weewx/bin/user/sdr.py",
> >line 198, in run
> >Feb 14 08:49:5

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

[Pierre-Yves]

To complete the post above, I tested the command : "sudo systemctl restart 
udev weewx"

ps aux|grep weewxd issues now:

pi@raspberrypi:~ $ ps aux|grep weewxd
weewx11862  7.0  0.9  46012 18772 ?Ss   09:26   0:00 python3 
/usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
pi   11883  0.0  0.0   7460   572 pts/3S+   09:26   0:00 grep 
--color=auto weewxd

But weewx still fails to start with the same error...

Le mercredi 14 février 2024 à 09:13:48 UTC+1, Pierre-Yves a écrit :

> Thanks Vince
>
> I found in rtl-sdr. rules a rule corresponding to my SDR stick : 
>
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="*0bda*", ATTRS{idProduct}=="*2838*", 
> ENV{ID_SOFTWARE_RADIO}="1", MODE="0660", GROUP="*plugdev*"
>
> I added the weewx user to that group: "sudo usermod -aG plugdev weewx"
>
> I still can start weewx with the  "sudo weewd" command as before but I 
> can't run weewx in daemon mode. "sudo  systemctl start weewx" gives still 
> the same error :
>
> Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Starting main 
> packet loop.
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: Nous espérons 
> que vous avez reçu de votre administrateur système local
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: les consignes 
> traditionnelles. Généralement, elles se concentrent sur ces trois éléments :
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #1) 
> Respectez la vie privée des autres.
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #2) 
> Réfléchissez avant d'utiliser le clavier.
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #3) De 
> grands pouvoirs confèrent de grandes responsabilités.
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: un 
> terminal est requis pour lire le mot de passe; utilisez soit l'option -S 
> pour lire depuis l'entrée standard ou configurez un outil askpass de 
> demande de mot de passe
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: il est 
> nécessaire de saisir un mot de passe
> Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Main loop 
> exiting. Shutting engine down.
> Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown process 
> sudo /usr/local/bin/rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 
> 1024k -R 173 -R 172 -R 42 -M utc -F json
> Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stdout
> Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stderr
> Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread 
> stdout-thread:
> Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown 
> stdout-thread
> Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call 
> last):
> Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread 
> stderr-thread:
> Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call 
> last):
> Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
> "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
> Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
> "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
> Feb 14 08:49:54 raspberrypi weewxd[5905]: self.run()
> Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
> "/etc/weewx/bin/user/sdr.py", line 198, in run
> Feb 14 08:49:54 raspberrypi weewxd[5905]: self.run()
> Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
> "/etc/weewx/bin/user/sdr.py", line 198, in run
> Feb 14 08:49:54 raspberrypi weewxd[5905]: for line in 
> iter(self._fd.readline, ''):
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ValueError: 
> PyMemoryView_FromBuffer(): info->buf must not be NULL
> Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown 
> stderr-thread
> Feb 14 08:49:54 raspberrypi weewxd[5905]: for line in 
> iter(self._fd.readline, ''):
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ValueError: 
> PyMemoryView_FromBuffer(): info->buf must not be NULL
> Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown complete
> Feb 14 08:49:54 raspberrypi weewxd[5905]: CRITICAL __main__: *Caught 
> WeeWxIOError: rtl_433 process is not running*
> Feb 14 08:49:54 raspberrypi weewxd[5905]: CRITICAL __main__:  
>  Waiting 60.0 seconds then retrying...
> Feb 14 08:50:03 raspberrypi weewxd[5905]: INFO __main__: Received signal 
> TERM (15).
> Feb 14 08:50:03 

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

[Pierre-Yves]

, another exception occurred:
Feb 14 08:50:03 raspberrypi weewxd[5905]: Traceback (most recent call last):
Feb 14 08:50:03 raspberrypi weewxd[5905]:   File 
"/usr/share/weewx/weewxd.py", line 265, in 
Feb 14 08:50:03 raspberrypi weewxd[5905]: main()
Feb 14 08:50:03 raspberrypi weewxd[5905]:   File 
"/usr/share/weewx/weewxd.py", line 193, in main
Feb 14 08:50:03 raspberrypi weewxd[5905]: time.sleep(wait_time)
Feb 14 08:50:03 raspberrypi weewxd[5905]:   File 
"/usr/share/weewx/weewxd.py", line 260, in sigTERMhandler
Feb 14 08:50:03 raspberrypi weewxd[5905]: raise Terminate
Feb 14 08:50:03 raspberrypi weewxd[5905]: __main__.Terminate
Feb 14 08:50:04 raspberrypi systemd[1]: weewx.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 14 08:50:04 raspberrypi systemd[1]: weewx.service: Failed with result 
'exit-code'.
Feb 14 08:50:04 raspberrypi systemd[1]: Stopped WeeWX.


When I start weewx again with "sudo weewxd", ps aux|grep weewxd gives:

pi@raspberrypi:~ $ ps aux|grep weewxd
*root * 8308  0.3  0.2  13112  4268 pts/1S+   09:02   0:00 sudo 
weewxd
*root*  8309  3.4  0.9  46004 18724 pts/1Sl+  09:02   0:00 python3 
/usr/share/weewx/weewxd.py
pi8347  0.0  0.0   7460   560 pts/3S+   09:03   0:00 grep 
--color=auto weewxd

Here, I am stuck...

Pierre-Yves




Le mardi 13 février 2024 à 23:49:36 UTC+1, vince a écrit :

> You want to look for 'rtl' or 'sdr' and adding the weewx user to the 
> appropriate group that has permissions to access the hardware.
>
> https://groups.google.com/g/weewx-user/c/7CIRRoo6Qdk/m/8dwn6EBiAQAJ is 
> one link.   Note that 'plugdev' is correct for that example.  We cannot 
> predict what 'your' system will require.
>
> On Tuesday, February 13, 2024 at 1:49:27 PM UTC-8 Pierre-Yves wrote:
>
>> I haven't found any thread related to the creation of weewx user and 
>> group...
>> PY
>>
>> Le mardi 13 février 2024 à 22:14:40 UTC+1, Pierre-Yves a écrit :
>>
>>> Thanks Vince.
>>> I'll try to find the way to do that
>>>
>>> Le mardi 13 février 2024 à 22:05:10 UTC+1, vince a écrit :
>>>
>>>> oops, I meant running as 'weewx' or 'pi' or 'something else'
>>>>
>>>> The reason I'm asking is that your systemctl log shows a sudo error 
>>>> that means that the account you are trying to use sudo under is not 
>>>> permitted to do so.  The default dpkg installation creates a weewx user 
>>>> and 
>>>> group but does not create a /etc/sudoers.d file for that user.  So the 
>>>> weewx user is not going to be able to sudo if you specify that.
>>>>
>>>> Butyou should be able to add the weewx user to the correct group(s) 
>>>> that can access your hardware.  I think there are other threads related to 
>>>> how to do that.
>>>>
>>>> On Tuesday, February 13, 2024 at 12:57:21 PM UTC-8 vince wrote:
>>>>
>>>>> On Tuesday, February 13, 2024 at 12:31:54 PM UTC-8 Pierre-Yves wrote:
>>>>>
>>>>> Weewx and webserver are perfectly working in simulator mode with "sudo 
>>>>> systemctl start weewx" command
>>>>>
>>>>>
>>>>> Good.  That means your problem appears to be related to getting weewx 
>>>>> as a non-privileged user to access your RTL-STR hardware.
>>>>>
>>>>> When running weewx using the Simulator does "ps aux|grep weewxd" show 
>>>>> it running as weewxd ?  Or pi ?  Or something else ?
>>>>>
>>>>>  
>>>>>
>>>>

-- 
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/cea6b4c6-5b5f-49f8-b6fc-fa7e317c36ddn%40googlegroups.com.

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

[Pierre-Yves]

I haven't found any thread related to the creation of weewx user and 
group...
PY

Le mardi 13 février 2024 à 22:14:40 UTC+1, Pierre-Yves a écrit :

> Thanks Vince.
> I'll try to find the way to do that
>
> Le mardi 13 février 2024 à 22:05:10 UTC+1, vince a écrit :
>
>> oops, I meant running as 'weewx' or 'pi' or 'something else'
>>
>> The reason I'm asking is that your systemctl log shows a sudo error that 
>> means that the account you are trying to use sudo under is not permitted to 
>> do so.  The default dpkg installation creates a weewx user and group but 
>> does not create a /etc/sudoers.d file for that user.  So the weewx user is 
>> not going to be able to sudo if you specify that.
>>
>> Butyou should be able to add the weewx user to the correct group(s) 
>> that can access your hardware.  I think there are other threads related to 
>> how to do that.
>>
>> On Tuesday, February 13, 2024 at 12:57:21 PM UTC-8 vince wrote:
>>
>>> On Tuesday, February 13, 2024 at 12:31:54 PM UTC-8 Pierre-Yves wrote:
>>>
>>> Weewx and webserver are perfectly working in simulator mode with "sudo 
>>> systemctl start weewx" command
>>>
>>>
>>> Good.  That means your problem appears to be related to getting weewx as 
>>> a non-privileged user to access your RTL-STR hardware.
>>>
>>> When running weewx using the Simulator does "ps aux|grep weewxd" show it 
>>> running as weewxd ?  Or pi ?  Or something else ?
>>>
>>>  
>>>
>>

-- 
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/1af5eb92-a0d1-41f9-8881-2e3b69045775n%40googlegroups.com.

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

[Pierre-Yves]

Thanks Vince.
I'll try to find the way to do that

Le mardi 13 février 2024 à 22:05:10 UTC+1, vince a écrit :

> oops, I meant running as 'weewx' or 'pi' or 'something else'
>
> The reason I'm asking is that your systemctl log shows a sudo error that 
> means that the account you are trying to use sudo under is not permitted to 
> do so.  The default dpkg installation creates a weewx user and group but 
> does not create a /etc/sudoers.d file for that user.  So the weewx user is 
> not going to be able to sudo if you specify that.
>
> Butyou should be able to add the weewx user to the correct group(s) 
> that can access your hardware.  I think there are other threads related to 
> how to do that.
>
> On Tuesday, February 13, 2024 at 12:57:21 PM UTC-8 vince wrote:
>
>> On Tuesday, February 13, 2024 at 12:31:54 PM UTC-8 Pierre-Yves wrote:
>>
>> Weewx and webserver are perfectly working in simulator mode with "sudo 
>> systemctl start weewx" command
>>
>>
>> Good.  That means your problem appears to be related to getting weewx as 
>> a non-privileged user to access your RTL-STR hardware.
>>
>> When running weewx using the Simulator does "ps aux|grep weewxd" show it 
>> running as weewxd ?  Or pi ?  Or something else ?
>>
>>  
>>
>

-- 
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/9e85cf8d-d9ce-4490-8260-f075e81b2757n%40googlegroups.com.

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

[Pierre-Yves]

Yes
With simulator, ps aux|grep weewxd shows that weewx user exixts...

pi@raspberrypi:~ $ ps aux|grep weewxd
weewx17482  1.0  1.6  52056 32100 ?Ss   21:28   0:06 python3 
/usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
pi   19150  0.0  0.0   7460   592 pts/1S+   21:38   0:00 grep 
--color=auto weewxd

PY
Le mardi 13 février 2024 à 21:57:21 UTC+1, vince a écrit :

> On Tuesday, February 13, 2024 at 12:31:54 PM UTC-8 Pierre-Yves wrote:
>
> Weewx and webserver are perfectly working in simulator mode with "sudo 
> systemctl start weewx" command
>
>
> Good.  That means your problem appears to be related to getting weewx as a 
> non-privileged user to access your RTL-STR hardware.
>
> When running weewx using the Simulator does "ps aux|grep weewxd" show it 
> running as weewxd ?  Or pi ?  Or something else ?
>
>  
>

-- 
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/125925e2-f2a6-4e8c-99e0-d1e0b26c0ebfn%40googlegroups.com.

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

[Pierre-Yves]

Thanks Vince for feedback.

Weewx and webserver are perfectly working in simulator mode with "sudo 
systemctl start weewx" command

Feb 13 21:28:23 raspberrypi systemd[1]: Started WeeWX.
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Initializing 
weewxd version 5.0.2
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Command line: 
/usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Using Python 
3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Located at 
/usr/bin/python3
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Platform 
Linux-6.1.21-v8+-aarch64-with-glibc2.31
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Locale: 
'fr_FR.UTF-8'
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Entry path: 
/usr/share/weewx/weewxd.py
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: WEEWX_ROOT: 
/etc/weewx
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Configuration 
file: /etc/weewx/weewx.conf
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: User module: 
/etc/weewx/bin/user
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Debug: 1
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG __main__: Initializing 
engine
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO weewx.engine: Loading 
station type Simulator (weewx.drivers.simulator)
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading 
service weewx.engine.StdTimeSynch
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished 
loading service weewx.engine.StdTimeSynch
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: No services 
in service group data_services
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading 
service weewx.engine.StdConvert
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO weewx.engine: StdConvert 
target unit is 0x1
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished 
loading service weewx.engine.StdConvert
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading 
service weewx.engine.StdCalibrate
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished 
loading service weewx.engine.StdCalibrate
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading 
service weewx.engine.StdQC
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished 
loading service weewx.engine.StdQC
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading 
service weewx.wxservices.StdWXCalculate
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO weewx.wxservices: 
StdWXCalculate will use data binding wx_binding
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.manager: Daily 
summary version is 4.0
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished 
loading service weewx.wxservices.StdWXCalculate
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading 
service weewx.wxxtypes.StdWXXTypes
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished 
loading service weewx.wxxtypes.StdWXXTypes
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading 
service weewx.wxxtypes.StdPressureCooker
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished 
loading service weewx.wxxtypes.StdPressureCooker
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading 
service weewx.wxxtypes.StdRainRater
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished 
loading service weewx.wxxtypes.StdRainRater
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading 
service weewx.wxxtypes.StdDelta
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished 
loading service weewx.wxxtypes.StdDelta
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading 
service weewx.engine.StdArchive
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO weewx.engine: Archive will 
use data binding wx_binding
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO weewx.engine: Record 
generation will be attempted in 'hardware'
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO weewx.engine: Using archive 
interval of 300 seconds (specified in weewx configuration)
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Use LOOP 
data in hi/low calculations: 1
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished 
loading service weewx.engine.StdArchive
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading 
service weewx.restx.StdStationRegistry
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO weewx.restx: 
StationRegistry: Registration not requested.
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished 
loading service weewx.restx.StdStationRegistry
Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading 
service weewx.restx.StdWunderground
Feb 13 21:28:23 

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

[Pierre-Yves]

Contents of several files to complete the previous post:

/etc/default/weewx :

WEEWX_PYTHON=python3
WEEWX_BINDIR=/usr/share/weewx

/etc/systemd/system/weewx.service : 

no file named weewx.service

/etc/init.d/weewx

no file named weewx

PYB

Le mardi 13 février 2024 à 20:31:29 UTC+1, Pierre-Yves a écrit :

> Hello,
>
> I experience very similar behavior to that described above.
>
> Recently, I failed to upgrade my Weewx 4.10 to Weewx 5.0.x.
> I reverted "temporarily" to 4.10 and decided to make a fresh install on a 
> spare set Pi4 + SDR stick.
>
> I installed RTL_433 and sdr-rtl following the 
> https://github.com/weewx/weewx/wiki/sdr-rpi-recipe tutorial. I then 
> installed weewx 5.0.3 and the sdr driver
>
> I finally replaced the weewx.conf by the one coming from my 4.10 setup.
>
> I tried several commands :
>  
> - rtl_433 -> ok
>
> - rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k -R 173 -R 172 
> -R 42 -M utc -F json -> ok
>
> - sudo PYTHONPATH=/usr/share/weewx python3 /etc/weewx/bin/user/sdr.py 
> --cmd="rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k -R 173 -R 
> 172 -R 42 -M utc -F json" -> ok
>  
>  But "weewxd" fails : problem of permission error (see "weewxd log")
>  
>
> And "sudo systemctl start weewx" fails too (see "sudo systemctl start 
> weewx log")
>
> Finally I tried "sudo weewd" that works and writes data to 
> /var/www/html/weewx ...
>
> ps aux|grep weewxd gives : 
>
> pi@raspberrypi:~ $ ps aux|grep weewxd
> pi   31049  0.0  0.0   7460   548 pts/1S+   19:23   0:00 grep 
> --color=auto weewxd
>
> It seems that weewx user doesn't exist !
>
> ls -la /var/www/html/weewx gives : 
>
>  pi@raspberrypi:~ $ ls -la /var/www/html/weewx
> total 824
> drwxrwsrwx 4 weewx weewx  4096 13 févr. 19:20 .
> drwxr-xr-x 3 root  root   4096 13 févr. 14:57 ..
> -rw-r--r-- 1 root  weewx  5628 13 févr. 19:20 celestial.html
> -rw-r--r-- 1 weewx weewx 10018 13 févr. 19:20 daybarometer.png
> -rw-r--r-- 1 weewx weewx  7875 13 févr. 19:20 dayET.png
> -rw-r--r-- 1 weewx weewx  8068 13 févr. 19:20 dayhumext.png
> -rw-r--r-- 1 weewx weewx  7226 13 févr. 19:20 dayhumin.png
> -rw-r--r-- 1 weewx weewx  8086 13 févr. 19:20 dayhum.png
> -rw-r--r-- 1 weewx weewx  6884 13 févr. 09:21 daylightning.png
> -rw-r--r-- 1 weewx weewx  8608 13 févr. 19:20 dayradiation.png
> -rw-r--r-- 1 weewx weewx  7004 13 févr. 19:20 dayrain.png
> -rw-r--r-- 1 weewx weewx  6490 13 févr. 19:20 dayrx.png
> -rw-r--r-- 1 weewx weewx  9330 13 févr. 19:20 daytempdew.png
> -rw-r--r-- 1 weewx weewx  8071 13 févr. 19:20 daytempext.png
> -rw-r--r-- 1 weewx weewx  8923 13 févr. 19:20 daytempfeel.png
> -rw-r--r-- 1 weewx weewx  8125 13 févr. 19:20 daytempin.png
> -rw-r--r-- 1 weewx weewx  6225 13 févr. 19:20 dayUV.png
> -rw-r--r-- 1 weewx weewx 11508 13 févr. 19:20 dayvolt.png
> -rw-r--r-- 1 weewx weewx  8087 13 févr. 19:20 daywinddir.png
> -rw-r--r-- 1 weewx weewx  9878 13 févr. 19:20 daywind.png
> -rw-r--r-- 1 weewx weewx  8503 13 févr. 19:20 daywindvec.png
> -rw-r--r-- 1 weewx weewx  1150 13 févr. 19:20 favicon.ico
> drwxr-sr-x 2 weewx weewx  4096 13 févr. 09:21 font
> -rw-r--r-- 1 root  weewx 31797 13 févr. 19:20 index.html
> -rw-r--r-- 1 weewx weewx  7702 13 févr. 18:00 monthbarometer.png
> -rw-r--r-- 1 weewx weewx  8532 13 févr. 18:00 monthET.png
> -rw-r--r-- 1 weewx weewx  8006 13 févr. 18:00 monthhumext.png
> -rw-r--r-- 1 weewx weewx  7446 13 févr. 18:00 monthhumin.png
> -rw-r--r-- 1 weewx weewx  7328 13 févr. 18:00 monthhum.png
> -rw-r--r-- 1 weewx weewx  7383 13 févr. 09:21 monthlightning.png
> -rw-r--r-- 1 weewx weewx  8135 13 févr. 18:00 monthradiation.png
> -rw-r--r-- 1 weewx weewx  7181 13 févr. 18:00 monthrain.png
> -rw-r--r-- 1 weewx weewx  6503 13 févr. 18:00 monthrx.png
> -rw-r--r-- 1 weewx weewx  7870 13 févr. 18:00 monthtempdew.png
> -rw-r--r-- 1 weewx weewx  7357 13 févr. 18:00 monthtempext.png
> -rw-r--r-- 1 weewx weewx  9012 13 févr. 18:00 monthtempfeel.png
> -rw-r--r-- 1 weewx weewx  7911 13 févr. 18:00 monthtempin.png
> -rw-r--r-- 1 weewx weewx  6574 13 févr. 18:00 monthUV.png
> -rw-r--r-- 1 weewx weewx 11055 13 févr. 18:00 monthvolt.png
> -rw-r--r-- 1 weewx weewx  6080 13 févr. 18:00 monthwinddir.png
> -rw-r--r-- 1 weewx weewx  7732 13 févr. 18:00 monthwind.png
> -rw-r--r-- 1 weewx weewx  6752 13 févr. 18:00 monthwindvec.png
> drwxr-sr-x 2 weewx weewx 12288 13 févr. 19:20 NOAA
> -rw-r--r-- 1 root  weewx 11717 13 févr. 19:20 rss.xml
> -rw-r--r-- 1 weewx weewx  5406 13 févr. 19:20 seasons.css
> -rw-r--r-- 1 weewx weewx  6404 13 févr. 19:20 seasons.js
> -rw-r--r-- 1 root  weewx 23189 13 févr. 19:20 statistics.html
> -rw-r--r-- 1 root  weewx  1461 1

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

[Pierre-Yves]

- 1 weewx weewx  8105 13 févr. 19:20 weektempfeel.png
-rw-r--r-- 1 weewx weewx  7566 13 févr. 19:20 weektempin.png
-rw-r--r-- 1 weewx weewx  6136 13 févr. 19:20 weekUV.png
-rw-r--r-- 1 weewx weewx 11665 13 févr. 19:20 weekvolt.png
-rw-r--r-- 1 weewx weewx  6919 13 févr. 19:20 weekwinddir.png
-rw-r--r-- 1 weewx weewx  8827 13 févr. 19:20 weekwind.png
-rw-r--r-- 1 weewx weewx  7495 13 févr. 19:20 weekwindvec.png
-rw-r--r-- 1 weewx weewx  9525 13 févr. 09:21 yearbarometer.png
-rw-r--r-- 1 weewx weewx  7754 13 févr. 09:21 yearET.png
-rw-r--r-- 1 weewx weewx 13773 13 févr. 09:21 yearhumext.png
-rw-r--r-- 1 weewx weewx  8247 13 févr. 09:21 yearhumin.png
-rw-r--r-- 1 weewx weewx 10196 13 févr. 09:21 yearhum.png
-rw-r--r-- 1 weewx weewx  7123 13 févr. 09:21 yearlightning.png
-rw-r--r-- 1 weewx weewx  9078 13 févr. 09:21 yearradiation.png
-rw-r--r-- 1 weewx weewx  7971 13 févr. 09:21 yearrain.png
-rw-r--r-- 1 weewx weewx  6105 13 févr. 09:25 yearrx.png
-rw-r--r-- 1 weewx weewx 11713 13 févr. 09:21 yeartempdew.png
-rw-r--r-- 1 weewx weewx 11726 13 févr. 09:21 yeartempext.png
-rw-r--r-- 1 weewx weewx 11084 13 févr. 09:21 yeartempfeel.png
-rw-r--r-- 1 weewx weewx  8401 13 févr. 09:21 yeartempin.png
-rw-r--r-- 1 weewx weewx  8797 13 févr. 09:21 yearUV.png
-rw-r--r-- 1 weewx weewx 10464 13 févr. 09:25 yearvolt.png
-rw-r--r-- 1 weewx weewx  9513 13 févr. 09:21 yearwinddir.png
-rw-r--r-- 1 weewx weewx 11318 13 févr. 09:21 yearwind.png
-rw-r--r-- 1 weewx weewx 10569 13 févr. 09:21 yearwindvec.png

I applied the differrent fixe proposals from 
https://github.com/weewx/weewx/wiki/Understanding-permissions. But no change

Any clue to solve this problem ? 

Thanks,

Pierre-Yves

Le mardi 13 février 2024 à 15:44:05 UTC+1, matthew wall a écrit :

> On Tuesday, February 13, 2024 at 9:11:14 AM UTC-5 wagr...@gmail.com wrote:
>
>
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.imagegenerator: Unable to 
> save to file '/var/www/html/weewx/yearrx.png' [Errno 13] Keine 
> Berechtigung: '/var/www/html/weewx/yearrx.png':
> Feb 13 12:40:54 hp weewxd[4425]: INFO weewx.imagegenerator: Generated 0 
> images for report SeasonsReport in 3.97 seconds
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine: Caught 
> unrecoverable exception in generator 'weewx.reportengine.CopyGenerator'
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:  
>  [Errno 13] Keine Berechtigung: '/var/www/html/weewx'
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:  
>  Traceback (most recent call last):
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>  File "/usr/share/weewx/weewx/reportengine.py", line 220, in run
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>obj.start()
> Feb 13 12:40:54 hp weewxd[4425]: Traceback (most recent call last):
> Feb 13 12:40:54 hp weewxd[4425]:   File 
> "/usr/share/weewx/weewx/reportengine.py", line 220, in run
> Feb 13 12:40:54 hp weewxd[4425]: obj.start()
> Feb 13 12:40:54 hp weewxd[4425]:   File 
> "/usr/share/weewx/weewx/reportengine.py", line 409, in start
> Feb 13 12:40:54 hp weewxd[4425]: self.run()
> Feb 13 12:40:54 hp weewxd[4425]:   File 
> "/usr/share/weewx/weewx/reportengine.py", line 560, in run
> Feb 13 12:40:54 hp weewxd[4425]: ncopy += 
> weeutil.weeutil.deep_copy_path(path, html_dest_dir)
> Feb 13 12:40:54 hp weewxd[4425]:   File 
> "/usr/share/weewx/weeutil/weeutil.py", line 1807, in deep_copy_path
> Feb 13 12:40:54 hp weewxd[4425]: os.makedirs(d, exist_ok=True)
> Feb 13 12:40:54 hp weewxd[4425]:   File "/usr/lib/python3.9/os.py", line 
> 225, in makedirs
> Feb 13 12:40:54 hp weewxd[4425]: mkdir(name, mode)
> Feb 13 12:40:54 hp weewxd[4425]: PermissionError: [Errno 13] Keine 
> Berechtigung: '/var/www/html/weewx'
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>  File "/usr/share/weewx/weewx/reportengine.py", line 409, in start
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>self.run()
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>  File "/usr/share/weewx/weewx/reportengine.py", line 560, in run
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>ncopy += weeutil.weeutil.deep_copy_path(path, html_dest_dir)
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>  File "/usr/share/weewx/weeutil/weeutil.py", line 1807, in deep_copy_path
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>os.makedirs(d, exist_ok=True)
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>  File "/usr/lib/pyth

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Pierre-Yves]

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  wrote:
>>
>>> I'll add "plughw" to the troubleshooting section.
>>>
>>> -tk
>>>
>>> On Wed, Feb 7, 2024 at 8:16 AM Steve Gee  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  
>>>>> 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/841fd8c5-0d2c-4007-a34c-7077d2fbae7cn%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Pierre-Yves]

@ Mks Mk,
Which command did you use to perform the downgrade from v5to v4.10.2 ?
I tried "sudo apt install weewx=4.10.2" and "sudo apt install weewx 4.10.2" 
but none of these work...

Thanks, Pierre-Yves

Le mardi 6 février 2024 à 19:44:41 UTC+1, Mks Mk a écrit :

> we just tried the upgrade again to weewx  v5.0.1 (sudo apt update) and it 
> worked this time.
> (we have not done any changes to the system after the downgrade to 
> v4.10.2) 
>
> On Tuesday, February 6, 2024 at 8:32:36 PM UTC+3 Pierre-Yves wrote:
>
>> @ Matthew, thanks. I need now to "digest" all this information, it's a 
>> bit high level for me ;-)
>>
>> @ Stefanos, thanks too, I tested my USB SDR key and obtain the same 
>> result as yours : "Bus 003 Device 003: ID 0bda:2838 Realtek Semiconductor 
>> Corp. RTL2838 DVB-T"
>>
>> Pierre-Yves
>> Le mardi 6 février 2024 à 18:17:07 UTC+1, Stefanos Kalaitzis a écrit :
>>
>>> i forgot to write in my last message  that when you finished you must 
>>> restart udev or restart the device you using( p.c , rpi ,... etc)
>>>
>>> On Tuesday, February 6, 2024 at 7:11:07 PM UTC+2 matthew wall wrote:
>>>
>>>> On Tuesday, February 6, 2024 at 11:38:24 AM UTC-5 Pierre-Yves wrote:
>>>>
>>>> It seems to be a problem of rules change. In fact, I first upgraded 
>>>> from 4.10.2 to 5.0.0 and weewx worked perfectly. 
>>>>
>>>>
>>>> weewx was running as root:root. weewx 5.0.0 did not modify any 
>>>> permissions when it upgraded from 4.10.2.
>>>>  
>>>>
>>>> Then I went from 5.0.0 to 5.0.1 an weewx failed to start.
>>>>
>>>>
>>>> weewx was running as weewx:weewx.  weewx 5.0.1 converts from root:root 
>>>> permissions to weewx:weewx permissions, and runs the daemon as weewx.
>>>>  
>>>>
>>>> For Weewx,, I did a deb/rpm install and, as far I remember, I installed 
>>>> rtl-sdr following your Git (https://github.com/matthewwall/weewx-sdr).
>>>>
>>>> I tried the command you proposed (sudo usermod -aG plugdev weewx) but 
>>>> that doesn't solve the problem.
>>>>
>>>>
>>>> is there a udev rules file for sdr?  (it is a separate step when you 
>>>> build rtl-sdr from source)
>>>> if there is a udev rules file for sdr, how are the permissions set?
>>>> did the usermod for weewx succeed?
>>>> is weewx in the plugdev group?  (grep weewx /etc/group)
>>>> did you restart weewxd after putting weewx into the plugdev group?
>>>>  
>>>>
>>>> Regarding the rtl-sdr rules, I have a doubt. I installed the file in 
>>>> /etc/weewx/udev/rules.d. Maybe it is a wrong place... I read in another 
>>>> thread that it should be in /usr/lib/udev/rules.d... What about ?
>>>>
>>>>
>>>> packages install to /usr/lib/udev/rules.d
>>>>
>>>> system administrators (or end-users acting as system administrators) 
>>>> put things in /etc/udev/rules.d
>>>>
>>>> that way you can override whatever a package installs, and your changes 
>>>> will not be overwritten by the package when you upgrade/update.
>>>>  
>>>>
>>>

-- 
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/9fad728e-e665-4db7-a99b-8b3c129ea164n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Pierre-Yves]

@ Matthew, thanks. I need now to "digest" all this information, it's a bit 
high level for me ;-)

@ Stefanos, thanks too, I tested my USB SDR key and obtain the same result 
as yours : "Bus 003 Device 003: ID 0bda:2838 Realtek Semiconductor Corp. 
RTL2838 DVB-T"

Pierre-Yves
Le mardi 6 février 2024 à 18:17:07 UTC+1, Stefanos Kalaitzis a écrit :

> i forgot to write in my last message  that when you finished you must 
> restart udev or restart the device you using( p.c , rpi ,... etc)
>
> On Tuesday, February 6, 2024 at 7:11:07 PM UTC+2 matthew wall wrote:
>
>> On Tuesday, February 6, 2024 at 11:38:24 AM UTC-5 Pierre-Yves wrote:
>>
>> It seems to be a problem of rules change. In fact, I first upgraded from 
>> 4.10.2 to 5.0.0 and weewx worked perfectly. 
>>
>>
>> weewx was running as root:root. weewx 5.0.0 did not modify any 
>> permissions when it upgraded from 4.10.2.
>>  
>>
>> Then I went from 5.0.0 to 5.0.1 an weewx failed to start.
>>
>>
>> weewx was running as weewx:weewx.  weewx 5.0.1 converts from root:root 
>> permissions to weewx:weewx permissions, and runs the daemon as weewx.
>>  
>>
>> For Weewx,, I did a deb/rpm install and, as far I remember, I installed 
>> rtl-sdr following your Git (https://github.com/matthewwall/weewx-sdr).
>>
>> I tried the command you proposed (sudo usermod -aG plugdev weewx) but 
>> that doesn't solve the problem.
>>
>>
>> is there a udev rules file for sdr?  (it is a separate step when you 
>> build rtl-sdr from source)
>> if there is a udev rules file for sdr, how are the permissions set?
>> did the usermod for weewx succeed?
>> is weewx in the plugdev group?  (grep weewx /etc/group)
>> did you restart weewxd after putting weewx into the plugdev group?
>>  
>>
>> Regarding the rtl-sdr rules, I have a doubt. I installed the file in 
>> /etc/weewx/udev/rules.d. Maybe it is a wrong place... I read in another 
>> thread that it should be in /usr/lib/udev/rules.d... What about ?
>>
>>
>> packages install to /usr/lib/udev/rules.d
>>
>> system administrators (or end-users acting as system administrators) put 
>> things in /etc/udev/rules.d
>>
>> that way you can override whatever a package installs, and your changes 
>> will not be overwritten by the package when you upgrade/update.
>>  
>>
>

-- 
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/329d0ee7-1c59-4d7c-be42-45d5957ced69n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Pierre-Yves]

@ Matthew,

Thanks a lot for the feedback.

It seems to be a problem of rules change. In fact, I first upgraded from 
4.10.2 to 5.0.0 and weewx worked perfectly. Then I went from 5.0.0 to 5.0.1 
an weewx failed to start.

For Weewx,, I did a deb/rpm install and, as far I remember, I installed 
rtl-sdr following your Git (https://github.com/matthewwall/weewx-sdr).

I tried the command you proposed (sudo usermod -aG plugdev weewx) but that 
doesn't solve the problem.

Regarding the rtl-sdr rules, I have a doubt. I installed the file in 
/etc/weewx/udev/rules.d. Maybe it is a wrong place... I read in another 
thread that it should be in /usr/lib/udev/rules.d... What about ?

Pierre-Yves



Le mardi 6 février 2024 à 17:09:36 UTC+1, Tom Hogland a écrit :

> In case anyone else runs into this - my Ubuntu server/Davis VP2 and serial 
> datalogger had ownership set to root:dialout, so I had to add the weewx 
> user to the dialout group for things to work. 
>
> On Tuesday, February 6, 2024 at 6:23:15 AM UTC-9 matthew wall wrote:
>
>> when you install rtl-sdr, it typically, but not always, installs udev 
>> rules for *many* sdr devices.  the udev rules that it installs make it 
>> possible for anyone in the 'plugdev' group to read/write to the sdr 
>> device.  (this is true when you install rtl-sdr from source - if you 
>> install rtl-sdr from a deb/rpm package, it might be different - anyone with 
>> this configuration please let us know)
>>
>> weewx v4 runs as root:root, so it has access to the sdr device no matter 
>> what the udev rules might be
>>
>> weewx v5 runs as weewx:weewx (for a deb/rpm install) or as a regular 
>> non-root user (for pip installs).  so udev rules are required.
>>
>> btw, weewx 5.0.1 *always* converts to weewx:weewx, whereas 5.0.0 did not 
>> (it would continue to run as root - we changed in 5.0.1 because overall 
>> security and best practice)
>>
>> the udev rules installed by rtl-sdr will not help for a deb/rpm install, 
>> since the user 'weewx' is not in the plugdev group.  you can either added 
>> the user weewx to the plugdev group, or modify the udev rules to use 
>> 'weewx' instead of 'plugdev' as the group.  this is how to do the former:
>>
>> sudo usermod -aG plugdev weewx
>>
>> for a pip install, be sure that the user running weewx is in the 
>> 'plugdev' group.
>>
>> restart of the weewxd daemon is almost certainly required so that the 
>> daemon process has the right group.  reboot is not necessary.
>>
>> m
>>
>

-- 
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/851d8cfc-0ce2-4758-b160-22a983dbd897n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Pierre-Yves]

Hello all,

I just upgraded from 4.10 .2 to 5.0.1 and I seem to experiment a similar 
behavior. I run weewx on a RPi4.

As Tom explained above, I put rtl-sdr.rules in udev directory and restarted 
but no change
 
I tried to downgrade using "sudo apt install weewx=4.10.2" but that doesn't 
work :

:~ $ sudo apt install weewx=4.10.2
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances   
Lecture des informations d'état... Fait
E: La version « 4.10.2 » de « weewx » n'a pu être trouvée ??

Now I am stuck

Below the log when weewx 5.0.1 is started.

Any idea ?

Thanks, Pierre-Yves


Le mardi 6 février 2024 à 14:35:19 UTC+1, Tom Keffer a écrit :

> If you look in your log, you'll see that the rtl_433 process failed to run 
> because of permissions problems. The log also suggests fixing the problem 
> by installing the udev rules file "rtl-sir:rules". You can find this rules 
> file in the rtl-sdr repository: 
> https://raw.githubusercontent.com/osmocom/rtl-sdr/master/rtl-sdr.rules
>
> V4.10 ran as user "root". Fresh V5 installs run as user "weewx", which may 
> not have the permissions necessary to access your device. The rules file 
> gives it these permissions.
>
> Alternatively, you could change your install to run under "root".
>
> On Tue, Feb 6, 2024 at 1:29 AM Mks Mk  wrote:
>
>> The system was running weewx v5.0.0 with no issue then we did the upgrade 
>> to v5.0.1 (sudo apt update) and weewx failed to run.
>> we downgraded weewx to v5.0.0 but it did not work this time, so we went 
>> back to v4.10.2 and it run just fine.
>> did the upgrade again and got the same error.so we are back to v4.10.2
>> we tested the sdr hardware using rtl_433 and it is working fine.
>> we are not sure of what to do next!
>>
>> log:
>> weewxd[2386]: INFO __main__: Starting up weewx version 5.0.1
>> weewxd[2386]: INFO weewx.engine: Using binding 'wx_binding' to database 
>> 'weewx.sdb'
>> weewxd[2386]: INFO weewx.manager: Starting backfill of daily summaries
>> weewxd[2386]: INFO weewx.manager: Daily summaries up to date
>> weewxd[2386]: INFO weewx.engine: Starting main packet loop.
>> weewxd[2386]: ERROR user.sdr: rtl_433 version 23.11-41-g06b03b7a branch 
>> master at 202402051043 inputs file rtl_tcp RTL-SDR
>> weewxd[2386]: ERROR user.sdr: Use "-F log" if you want any messages, 
>> warnings, and errors in the console.
>> weewxd[2386]: ERROR user.sdr: usb_open error -3
>> weewxd[2386]: ERROR user.sdr: Please fix the device permissions, e.g. by 
>> installing the udev rules file rtl-sdr.rules
>> weewxd[2386]: INFO weewx.engine: Main loop exiting. Shutting engine down.
>> weewxd[2386]: INFO user.sdr: shutdown process rtl_433 -f 433.7M -s 1024k 
>> -R 40
>> weewxd[2386]: Exception in thread stdout-thread:
>> weewxd[2386]: Traceback (most recent call last):
>> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in 
>> _bootstrap_inner
>> weewxd[2386]: Exception in thread stderr-thread:
>> weewxd[2386]: Traceback (most recent call last):
>> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in 
>> _bootstrap_inner
>> weewxd[2386]: self.run()
>> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
>> weewxd[2386]: for line in iter(self._fd.readline, ''):
>> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not 
>> be NULL
>> weewxd[2386]: self.run()
>> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
>> weewxd[2386]: for line in iter(self._fd.readline, ''):
>> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not 
>> be NULL
>> weewxd[2386]: INFO user.sdr: shutdown complete
>> weewxd[2386]: CRITICAL __main__: Caught WeeWxIOError: rtl_433 process is 
>> not running
>> weewxd[2386]: CRITICAL __main__:   Waiting 60.0 seconds then 
>> retrying...
>>
>> -- 
>>
> 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/4c62d6c3-d690-49e8-8151-8b9af8dd5b43n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/4c62d6c3-d690-49e8-8151-8b9af8dd5b43n%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/2fe00d3b-9f50-4bae-90c4-98c9f57298f6n%40googlegroups.com.


upgrade 4-10-2 to 5-0-1-log
Description: Binary data

Re: [weewx-user] weewx.UnknownType: extraHumid3" error

[Pierre-Yves]

@ Tom,

Tested, approved. Great thanks !

Attached, the schema after drop-daily, add column and rebuild-daily

pyb

Le mardi 10 octobre 2023 à 09:01:16 UTC+2, Pierre-Yves a écrit :

> Thanks Tom, I'll make a backup and give a try. I keep you in touch.
>
> Regarding the provenance of the base, if I remember well, I installed 
> Weewx in 2018, starting with an empty database. Previously I was using 
> WsWin32. Some months after, I decided to import from WU the about 8 years 
> data I had, and I merged them to the Weewx SDB. Maybe the base was altered 
> (corrupted) at that time...
>
> pyb
>
> Le lundi 9 octobre 2023 à 19:52:06 UTC+2, Tom Keffer a écrit :
>
>> I don't know how it happened, but your database has multiple entries in 
>> the daily summaries, including extraHumid3, that are not in the main 
>> archive table.
>>
>> I've never seen this before, so I'm not quite sure how to recover. Do you 
>> remember the provenance of the database?
>>
>> You could try dropping all the daily summaries, then add the missing 
>> columns to the archive table, then rebuilding the database. I don't know 
>> how facile you are with SQL, but the workflow would look something like 
>> this (NOT TESTED):
>>
>> *cd /var/lib/weewx*
>> *sudo wee_database --drop-daily*
>>
>> *sudo cp weewx.sdb weewx.sdb.backup*
>> *sudo sqlite3 weewx.sdb*
>> sqlite>* ALTER TABLE archive ADD COLUMN extraHumid3;*
>> sqlite>*  (add any other missing columns)*
>> sqlite>* .quit*
>> *sudo wee_database --rebuild-daily*
>>
>> Or, perhaps you have a backup that has the missing columns.
>>
>> -tk
>>
>> On Mon, Oct 9, 2023 at 10:00 AM Pierre-Yves  wrote:
>>
>>> Thanks Tom for the feedback.
>>>
>>> I don't think I have a problem of typo or aggregate type, as I use a 
>>> copy/past of the extraTemp2/extraHumid2 that works fine
>>> [[extra]]
>>> title = Température/humidité ch.Vincent
>>> [[[extraTemp2]]]
>>> yAxis_tickInterval = 1
>>> connectNulls = true
>>> name = T_ch_Vincent
>>> [[[extraHumid2]]]
>>> yAxis = 1
>>> yAxis_min = 25
>>> yAxis_max = 75
>>> y_label = "Hrel"
>>> connectNulls = true
>>> name = Humidité relative
>>> color = "#90ed7d"
>>> [[extra2]]
>>> title = Température/humidité cave
>>> [[[extraTemp3]]]
>>> yAxis_tickInterval = 1
>>> connectNulls = true
>>> name = T_cave
>>> [[[extraHumid3]]]
>>> yAxis = 1
>>> yAxis_min = 25
>>> yAxis_max = 90
>>> y_label = "Hrel"
>>> connectNulls = true
>>> name = Humidité relative
>>> color = "#90ed7d"
>>>
>>> Attached, the result of *echo ".schema" | sqlite3 
>>> /var/lib/weewx/weewx.sdb*
>>>
>>> Pierre-Yves
>>> Le lundi 9 octobre 2023 à 17:03:47 UTC+2, Tom Keffer a écrit :
>>>
>>>> We should also look at the schema in your database. Please post the 
>>>> results of
>>>>
>>>> *echo ".schema" | sqlite3 /var/lib/weewx/weewx.sdb*
>>>>
>>>>
>>>> On Mon, Oct 9, 2023 at 7:59 AM Tom Keffer  wrote:
>>>>
>>>>> This error can be misleading. The problem could also be caused by an 
>>>>> unknown aggregation type. Look through your [ImageGenerator] section of 
>>>>> the 
>>>>> Belchertown skin and make sure there isn't a typo or something for 
>>>>> "aggregate_type".
>>>>>
>>>>> On Mon, Oct 9, 2023 at 6:29 AM Pierre-Yves  wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I am running Weewx 4.10.2, catching data from various sensors (433 
>>>>>> MHz and 868 MHz), via the user.SDR driver.
>>>>>> All was perfectly working till I decide to add a new 
>>>>>> temperature/humidity sensor to the sensor map (extraTemp3 and 
>>>>>> extraHumid3). 
>>>>>> See below the sensor map.
>>>>>>
>>>>>> [SDR]
>>>>>> # This section is for the software-defined radio driver.
>>>>>>
>>>>>> # The station model, e.g., 'Meade TE923W&

Re: [weewx-user] weewx.UnknownType: extraHumid3" error

[Pierre-Yves]

Thanks Tom, I'll make a backup and give a try. I keep you in touch.

Regarding the provenance of the base, if I remember well, I installed Weewx 
in 2018, starting with an empty database. Previously I was using WsWin32. 
Some months after, I decided to import from WU the about 8 years data I 
had, and I merged them to the Weewx SDB. Maybe the base was altered 
(corrupted) at that time...

pyb

Le lundi 9 octobre 2023 à 19:52:06 UTC+2, Tom Keffer a écrit :

> I don't know how it happened, but your database has multiple entries in 
> the daily summaries, including extraHumid3, that are not in the main 
> archive table.
>
> I've never seen this before, so I'm not quite sure how to recover. Do you 
> remember the provenance of the database?
>
> You could try dropping all the daily summaries, then add the missing 
> columns to the archive table, then rebuilding the database. I don't know 
> how facile you are with SQL, but the workflow would look something like 
> this (NOT TESTED):
>
> *cd /var/lib/weewx*
> *sudo wee_database --drop-daily*
>
> *sudo cp weewx.sdb weewx.sdb.backup*
> *sudo sqlite3 weewx.sdb*
> sqlite>* ALTER TABLE archive ADD COLUMN extraHumid3;*
> sqlite>*  (add any other missing columns)*
> sqlite>* .quit*
> *sudo wee_database --rebuild-daily*
>
> Or, perhaps you have a backup that has the missing columns.
>
> -tk
>
> On Mon, Oct 9, 2023 at 10:00 AM Pierre-Yves  wrote:
>
>> Thanks Tom for the feedback.
>>
>> I don't think I have a problem of typo or aggregate type, as I use a 
>> copy/past of the extraTemp2/extraHumid2 that works fine
>> [[extra]]
>> title = Température/humidité ch.Vincent
>> [[[extraTemp2]]]
>> yAxis_tickInterval = 1
>> connectNulls = true
>> name = T_ch_Vincent
>> [[[extraHumid2]]]
>> yAxis = 1
>> yAxis_min = 25
>> yAxis_max = 75
>> y_label = "Hrel"
>> connectNulls = true
>> name = Humidité relative
>> color = "#90ed7d"
>> [[extra2]]
>> title = Température/humidité cave
>> [[[extraTemp3]]]
>> yAxis_tickInterval = 1
>> connectNulls = true
>> name = T_cave
>> [[[extraHumid3]]]
>> yAxis = 1
>> yAxis_min = 25
>> yAxis_max = 90
>> y_label = "Hrel"
>> connectNulls = true
>> name = Humidité relative
>> color = "#90ed7d"
>>
>> Attached, the result of *echo ".schema" | sqlite3 
>> /var/lib/weewx/weewx.sdb*
>>
>> Pierre-Yves
>> Le lundi 9 octobre 2023 à 17:03:47 UTC+2, Tom Keffer a écrit :
>>
>>> We should also look at the schema in your database. Please post the 
>>> results of
>>>
>>> *echo ".schema" | sqlite3 /var/lib/weewx/weewx.sdb*
>>>
>>>
>>> On Mon, Oct 9, 2023 at 7:59 AM Tom Keffer  wrote:
>>>
>>>> This error can be misleading. The problem could also be caused by an 
>>>> unknown aggregation type. Look through your [ImageGenerator] section of 
>>>> the 
>>>> Belchertown skin and make sure there isn't a typo or something for 
>>>> "aggregate_type".
>>>>
>>>> On Mon, Oct 9, 2023 at 6:29 AM Pierre-Yves  wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I am running Weewx 4.10.2, catching data from various sensors (433 MHz 
>>>>> and 868 MHz), via the user.SDR driver.
>>>>> All was perfectly working till I decide to add a new 
>>>>> temperature/humidity sensor to the sensor map (extraTemp3 and 
>>>>> extraHumid3). 
>>>>> See below the sensor map.
>>>>>
>>>>> [SDR]
>>>>> # This section is for the software-defined radio driver.
>>>>>
>>>>> # The station model, e.g., 'Meade TE923W' or 'TFA Nexus'
>>>>> model = Bresser WSX3001
>>>>> 
>>>>> # The driver to use
>>>>> driver = user.sdr
>>>>> 
>>>>> cmd = sudo /usr/local/bin/rtl_433 -f 868.3M -f 433.92M -H 90 -Y 
>>>>> autolevel -s 1024k -R 173 -R 172 -R 42 -M utc -F json
>>>>> 
>>>>> [[sensor_map]]
>>>>> 
>>>>> iroxwindDir = wind_dir.4:None.HidekiWindPacket
>>>>> iroxwindGust = wind_gust.4:None.Hideki

Re: [weewx-user] weewx.UnknownType: extraHumid3" error

[Pierre-Yves]

Thanks Tom for the feedback.

I don't think I have a problem of typo or aggregate type, as I use a 
copy/past of the extraTemp2/extraHumid2 that works fine
[[extra]]
title = Température/humidité ch.Vincent
[[[extraTemp2]]]
yAxis_tickInterval = 1
connectNulls = true
name = T_ch_Vincent
[[[extraHumid2]]]
yAxis = 1
yAxis_min = 25
yAxis_max = 75
y_label = "Hrel"
connectNulls = true
name = Humidité relative
color = "#90ed7d"
[[extra2]]
title = Température/humidité cave
[[[extraTemp3]]]
yAxis_tickInterval = 1
connectNulls = true
name = T_cave
[[[extraHumid3]]]
yAxis = 1
yAxis_min = 25
yAxis_max = 90
y_label = "Hrel"
connectNulls = true
name = Humidité relative
color = "#90ed7d"

Attached, the result of *echo ".schema" | sqlite3 /var/lib/weewx/weewx.sdb*

Pierre-Yves
Le lundi 9 octobre 2023 à 17:03:47 UTC+2, Tom Keffer a écrit :

> We should also look at the schema in your database. Please post the 
> results of
>
> *echo ".schema" | sqlite3 /var/lib/weewx/weewx.sdb*
>
>
> On Mon, Oct 9, 2023 at 7:59 AM Tom Keffer  wrote:
>
>> This error can be misleading. The problem could also be caused by an 
>> unknown aggregation type. Look through your [ImageGenerator] section of the 
>> Belchertown skin and make sure there isn't a typo or something for 
>> "aggregate_type".
>>
>> On Mon, Oct 9, 2023 at 6:29 AM Pierre-Yves  wrote:
>>
>>> Hello,
>>>
>>> I am running Weewx 4.10.2, catching data from various sensors (433 MHz 
>>> and 868 MHz), via the user.SDR driver.
>>> All was perfectly working till I decide to add a new 
>>> temperature/humidity sensor to the sensor map (extraTemp3 and extraHumid3). 
>>> See below the sensor map.
>>>
>>> [SDR]
>>> # This section is for the software-defined radio driver.
>>>
>>> # The station model, e.g., 'Meade TE923W' or 'TFA Nexus'
>>> model = Bresser WSX3001
>>> 
>>> # The driver to use
>>> driver = user.sdr
>>> 
>>> cmd = sudo /usr/local/bin/rtl_433 -f 868.3M -f 433.92M -H 90 -Y 
>>> autolevel -s 1024k -R 173 -R 172 -R 42 -M utc -F json
>>> 
>>> [[sensor_map]]
>>> 
>>> iroxwindDir = wind_dir.4:None.HidekiWindPacket
>>> iroxwindGust = wind_gust.4:None.HidekiWindPacket
>>> iroxwindSpeed = wind_speed.4:None.HidekiWindPacket
>>> iroxwindBatteryStatus = battery.4:None.HidekiWindPacket
>>> iroxoutTemp = temperature.1:12.HidekiTS04Packet  
>>> iroxoutHumidity = humidity.1:12.HidekiTS04Packet
>>> iroxoutBatteryStatus = battery.1:12.HidekiTS04Packet
>>> extraTemp2 = temperature.5:1.HidekiTS04Packet
>>> extraHumid2 = humidity.5:1.HidekiTS04Packet   
>>> *extraTemp3 = temperature.2:15.HidekiTS04Packet*# Temp_Cave
>>> *extraHumid3 = humidity.2:15.HidekiTS04Packet*# Hum_Cave
>>> extraBatteryStatus2 = battery.5:1.HidekiTS04Packet
>>> # rain_total = rain_total.4:None.HidekiRainPacket
>>> # rainBatteryStatus = battery.4:None.HidekiRainPacket
>>> 
>>> outTemp = temperature.43576.Bresser7in1Packet
>>> outHumidity = humidity.43576.Bresser7in1Packet
>>> rain_total = rain_total.43576.Bresser7in1Packet
>>> windDir = wind_dir.43576.Bresser7in1Packet
>>> windSpeed = wind_speed.43576.Bresser7in1Packet
>>> windGust = wind_gust.43576.Bresser7in1Packet
>>> UV = uv.43576.Bresser7in1Packet
>>> radiation = light.43576.Bresser7in1Packet
>>> windBatteryStatus = battery.43576.Bresser7in1Packet
>>> inTemp = temperature.-1859570394.Bresser6in1Packet# capteur 
>>> thermo-hygro externe
>>> inHumidity = humidity.-1859570394.Bresser6in1Packet
>>> inTempBatteryStatus = battery.-1859570394.Bresser6in1Packet
>>> 
>>> I actually succeeded to add a graph of extraTemp3 but I failed to add 
>>> extraHumid3. weewx.reportengine gets an "weewx.UnknownType: extraHumid3" 
>>> error.
>>>
>>> Oct  9 12:35:26 raspberrypi weewx[2125] INFO weewx.manager: Added record 
>>> 2023-10-09 12:35:00 CEST (1696847700) to database 'weewx.sdb'
>>> Oct  9 1

[weewx-user] weewx.UnknownType: extraHumid3" error

[Pierre-Yves]

erminated
Oct  9 12:35:29 raspberrypi weewx[2125] INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx
Oct  9 12:35:32 raspberrypi weewx[2125] INFO weewx.cheetahgenerator: 
Generated 11 files for report Belchertown in 3.30 seconds
Oct  9 12:35:32 raspberrypi weewx[2125] INFO weewx.reportengine: Copied 2 
files to /var/www/html/weewx/belchertown

I tried to add a column to the database but I got this error : 
"weedb.TableExistsError: table archive_day_extraHumid3 already exists" (see 
below)

pi@raspberrypi:~ $ wee_database --add-column=extraHumid3
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_sqlite'
Add new column 'extraHumid3' of type 'REAL' to database (y/n)? y
Traceback (most recent call last):
  File "/usr/share/weewx/weedb/sqlite.py", line 39, in guarded_fn
return fn(*args, **kwargs)
  File "/usr/share/weewx/weedb/sqlite.py", line 233, in execute
return sqlite3.Cursor.execute(self, *args, **kwargs)
*sqlite3.OperationalError: table archive_day_extraHumid3 already exists*

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/weewx/wee_database", line 1168, in 
main()
  File "/usr/share/weewx/wee_database", line 220, in main
addColumn(config_dict, db_binding, options.add_column, options.type)
  File "/usr/share/weewx/wee_database", line 632, in addColumn
dbm.add_column(column_name, column_type)
  File "/usr/share/weewx/weewx/manager.py", line 623, in add_column
self._add_column(column_name, column_type, cursor)
  File "/usr/share/weewx/weewx/manager.py", line 1136, in _add_column
self._initialize_day_table(column_name, 'scalar', cursor)
  File "/usr/share/weewx/weewx/manager.py", line 1130, in 
_initialize_day_table
cursor.execute(sql_create_str)
  File "/usr/share/weewx/weedb/sqlite.py", line 49, in guarded_fn
raise weedb.TableExistsError(e)

*weedb.TableExistsError: table archive_day_extraHumid3 already exists*
At the opposite, if I try to drop a possible extraHumid3 column, i get the 
following :

pi@raspberrypi:~ $ wee_database --drop-column=extraHumid3
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_sqlite'
Drop column(s) 'extraHumid3' from the database (y/n)? y
This may take a while...
*Cannot DROP 'extraHumid3'; column does not exist.*
Nothing done.

Now, even if I comment the extraTemp3 and extraHumid3 lines in the sensor 
map, I still get the same syslog errors.

At that point I am a bit stuck.

Any clue ?

Have a nice day

Pierre-Yves

-- 
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/31697f77-feca-4821-bcb9-40f7f5cca562n%40googlegroups.com.

[weewx-user] Re: ft0345 weather station with weewx

[Pierre-Yves]

Hi Mohammed,

See this Thread : 
https://groups.google.com/g/weewx-user/c/mqKzFV8wW8U/m/W5WkrMSUAwAJ

Also : https://github.com/matthewwall/weewx-sdr/issues/148

or : https://github.com/merbanan/rtl_433/issues/1664

PY

Le vendredi 9 juin 2023 à 16:05:35 UTC+2, Mohammed Buti a écrit :

> can any one help me 
>
> On Monday, 10 April 2023 at 04:30:54 UTC+4 Mohammed Buti wrote:
>
>> ello there i was amazed about  this  program weewx and got intersted in 
>> it and i want to sset up 
>> APRS  weather station and im runing my i gate andd dipetar allredy and 
>> want to add it to my APRS station  but with no luck
>> my weather station is form aliexpres ft0345 weather station but when i 
>> decode my  weather station via RTL 433  the model is cotech-367959 ID is 
>> 206 protocol is 153 im lost now so i want to run this ft0345 weather 
>> station with weewx 
>> i instald weewx om my rpi useing WeeWX: Installation on Debian-based 
>> systems
>> sudo apt-get update  sudo apt-get install weewx
>> so can any one help me with my problem???
>>
>

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

Re: [weewx-user] WeatherUnderground Not Publishing

[Pierre-Yves]

Hi Stefan,
Thanks a lot for this advice.
I replaced my WU password by the device key and I do not have upload 
problems anymore.
Pierre-Yves

Le vendredi 23 septembre 2022 à 14:59:48 UTC+2, stefa...@gmail.com a écrit :

> Just in case anyone else is still having WU issues, make sure you are 
> using the "Key" in your WU profile instead of your WU account password in 
> weewx.conf.
> Login to your wunderground.com account and go to "My Devices" under "My 
> Profile". Next to your Station ID, you will see "Key" and in my case, it is 
> 8 characters. Use that Key for your password in weewx.conf. This is not the 
> same as the "API Key".
>
> [[Wunderground]] 
> # This section is for configuring posts to the Weather Underground. 
>
> # If you wish to post to the Weather Underground, set the option 'enable' 
> to true, then 
> # specify a station (e.g., 'KORHOODR3') and password. To guard against 
> parsing errors, put 
> # the password in quotes. 
> enable = true 
> station =* your station id*  
> password = "*key *" 
>
> # If you plan on using wunderfixer, set the following 
> # to your API key: 
> api_key = *your API Key*
>
> Hope this helps as this was my issue. 
>
> Stefan 
> On Friday, 23 September 2022 at 00:39:35 UTC-4 nileg...@guitar-o-rama.com 
> wrote:
>
>> My weather station is still offline.  Given the number of posts here I'm 
>> assuming it's a Weather Underground issue.
>>
>> On Thursday, September 22, 2022 at 11:17:21 AM UTC-7 tast...@gmail.com 
>> wrote:
>>
>>> Same -- back as of 1310ish ET.
>>>
>>> On Thursday, September 22, 2022 at 1:54:41 PM UTC-4 pgeenhuizen wrote:
>>>
>>>> Mine is back also as of 13:10:25 EDT
>>>>
>>>>
>>>> On 9/22/22 13:17, Tom Keffer wrote:
>>>>
>>>> Mine is back online as well. Wonder what that was all about?
>>>>
>>>> On Thu, Sep 22, 2022 at 10:15 AM Dave Webb KB1PVH  
>>>> wrote:
>>>>
>>>>> Mine is back online as of 13:14 EDT.
>>>>>
>>>>> Dave - KB1PVH
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Sent from my Galaxy S21
>>>>>
>>>>> On Thu, Sep 22, 2022, 12:43 PM Del Merritt  
>>>>> wrote:
>>>>>
>>>>>> I am seeing no errors publishing (rapid fire) to wunderground, e.g.:
>>>>>> Sep 22 12:38:49 weewx[15535] INFO weewx.restx: Wunderground-RF: 
>>>>>> Published record 2022-09-22 12:38:50 EDT (1663864730)
>>>>>> Sep 22 12:38:51 weewx[15535] INFO weewx.restx: Wunderground-RF: 
>>>>>> Published record 2022-09-22 12:38:52 EDT (1663864732)
>>>>>> Sep 22 12:38:53 weewx[15535] INFO weewx.restx: Wunderground-RF: 
>>>>>> Published record 2022-09-22 12:38:54 EDT (1663864734)
>>>>>> Sep 22 12:38:55 weewx[15535] INFO weewx.restx: Wunderground-RF: 
>>>>>> Published record 2022-09-22 12:38:56 EDT (1663864736)
>>>>>> Sep 22 12:38:57 weewx[15535] INFO weewx.restx: Wunderground-RF: 
>>>>>> Published record 2022-09-22 12:38:58 EDT (1663864738)
>>>>>> Sep 22 12:38:59 weewx[15535] INFO weewx.restx: Wunderground-RF: 
>>>>>> Published record 2022-09-22 12:39:00 EDT (1663864740)
>>>>>> Sep 22 12:39:01 weewx[15535] INFO weewx.restx: Wunderground-RF: 
>>>>>> Published record 2022-09-22 12:39:02 EDT (1663864742)
>>>>>>
>>>>>> WeeWX 4.8.0, Davis Vantage Pro2. Running on a RaspberryPI.
>>>>>>
>>>>>> Cheers,
>>>>>> -Del
>>>>>>
>>>>>>
>>>>>> On Thu, Sep 22, 2022 at 12:36 PM Pete Geenhuizen  
>>>>>> wrote:
>>>>>>
>>>>>>> Seeing the same thing since 1300 Sept 21.
>>>>>>>
>>>>>>> On 9/22/22 11:49, Tom Stewart wrote:
>>>>>>>
>>>>>>> Nothing since 9/21 @ 10:55 a.m. ET. :-( 
>>>>>>>
>>>>>>> getting errors like the following in the log:
>>>>>>>
>>>>>>> Sep 22 09:50:39 woodypi weewx[575] ERROR weewx.restx: 
>>>>>>> Wunderground-PWS: Failed to publish record 2022-09-22 09:50:00 EDT 
>>>>>>> (1663854600): Failed upload after 3 tries
>>>>>>>
>>>>>>> similar to Tyler's
&g

Re: [weewx-user] French translation

[Pierre-Yves]

Hi,
Another nice translation could be "Ephéméride(s)". It is what I chose for 
my Seasons and Belchertown web pages.
Pierre-Yves

Le dimanche 4 septembre 2022 à 08:35:09 UTC+2, Karystos a écrit :

> Ok "Dans le ciel" is acceptable It seems that this commit is not yet 
> active . Thanks to all
>
> Le samedi 3 septembre 2022 à 15:29:44 UTC+3, tke...@gmail.com a écrit :
>
>> You're not the first to notice! The translation was changed in May in 
>> commit f31b9b6 
>> <https://github.com/weewx/weewx/commit/f31b9b616b08ccab7942673a9f54e7eba58d>
>>  to 
>> "*Dans le ciel*" . I hope that's acceptable.
>>
>> On Fri, Sep 2, 2022 at 11:53 PM Karystos  wrote:
>>
>>>
>>> Hi every body.
>>> weewx is wonderful !!! I have been using it for 8 years.
>>> Recently updated my os on Raspberry PI2, and discovered skin Sasons.  
>>> Ouahhh!
>>> And what a suprise good translation of the skin EXCEPT 
>>> Celestial wich is translated Astrologie  Very funny because ASTROLOGIE 
>>> is the scence of prediction/divination and has nothing to do with science 
>>> of stars which is ASTRONOMIE
>>>
>>> Sorry for the remark, it's just to improve translation. Go on guys, go 
>>> on !
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/979b0d29-c256-412c-80aa-dd5b3ffc1f06n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/979b0d29-c256-412c-80aa-dd5b3ffc1f06n%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/8fd01e60-cd7d-45cc-8902-b086888da4a3n%40googlegroups.com.

[weewx-user] Re: Weewx - Belchertown and 24 hour time format

[Pierre-Yves]

Here is the TimeFormats of my weewx.conf :

TimeFormats
# day= %H:%M
# week   = %H:%M on %A
# month  = %d-%b-%Y %H:%M
# year   = %d-%b-%Y %H:%M
# rainyear   = %d-%b-%Y %H:%M
# current= %d-%b-%Y %H:%M
# ephem_day  = %H:%M
# ephem_year = %d-%b-%Y %H:%M
# The following line is used to keep the above lines 
indented properly.
# It can be ignored.
unused = unused
I don't have made any changes compare to the original one.

PY

Le jeudi 5 mai 2022 à 16:27:50 UTC+2, wix...@gmail.com a écrit :

> Thanks Pierre-Yves, that is exactly what I have on my Pi4! Have you made 
> any changes to weewx.conf in the TimeFormats section?
>
> Barry
>
> On Thursday, May 5, 2022 at 10:06:21 a.m. UTC-4 Pierre-Yves wrote:
>
>> Hi Barry,
>>
>> I live in France and use the 24h format. Weewx is installed on a Pi4.
>>
>> Below, the relevant part of the *skin.conf* file located in the *Belchertown 
>> skin folder*. When I installed the Belchertown skin few years ago, I 
>> didn't do any modification to have the right format.
>>
>> [Units]
>> # This section is for managing the selection and formatting of units.
>>
>> [[Groups]]
>> #...
>>
>> [[StringFormats]]
>> # ...
>>
>> [[Labels]]
>> # ...
>>
>> [[TimeFormats]]
>> # This section sets the string format to be used for each time 
>> scale.
>> # The values below will work in every locale, but may not look
>> # particularly attractive. See the Customization Guide for 
>> alternatives.
>>
>> day= %X
>> week   = %X (%A)
>> month  = %x %X
>> year   = %x %X
>> rainyear   = %x %X
>> current= %x %X
>> ephem_day  = %X
>> ephem_year = %x %X
>>
>> Pierre-Yves
>>
>> Le jeudi 5 mai 2022 à 14:32:09 UTC+2, wix...@gmail.com a écrit :
>>
>>> Well, just for the "fun" of it, I did a complete re-install of Linux and 
>>> Weewx (at the moment the computer is only being used to play with Weewx). 
>>> From a clean install I am still not able to change to the 24hr format for 
>>> Weewx. Not that it should matter, but Linux is set to the 24hr format. The 
>>> 4  that surround TimeFormats has come up in the clean install, so I 
>>> guess it was nothing I did!!  Immediately before  TimeFormats in 
>>> the weewx.conf is Groups and any changes I make there are actioned. 
>>> It's not the end of the world that the time is in the 12 hr format, it's 
>>> now become a battle of (old) man against machine! If anyone has the 24hr 
>>> time format running ok could they post the relevant parts of their config 
>>> file??
>>>
>>> Barry
>>>
>>> On Wednesday, May 4, 2022 at 4:49:14 p.m. UTC-4 vince wrote:
>>>
>>>> naaah - no need to do a full install.  You're close enough that this 
>>>> one is just tweaking something (TBD) into the right config file (TBD).
>>>>
>>>> On Wednesday, May 4, 2022 at 1:34:06 PM UTC-7 wix...@gmail.com wrote:
>>>>
>>>>> Thanks for the pointer to more reference material Vince. Being new at 
>>>>> this I have been gathering as much info as possible, unfortunately I miss 
>>>>> some, and others are contradictory. I have no idea where the 4  came 
>>>>> from, probably one of my desperate cut and paste attempts!
>>>>> I think the safest path now is to sort out all my notes and start from 
>>>>> scratch with a new install, at least it gives me practice playing with 
>>>>> Linux.
>>>>> Barry
>>>>>
>>>>> On Wednesday, May 4, 2022 at 3:22:06 p.m. UTC-4 vince wrote:
>>>>>
>>>>>> For time formats, the weewx customization guide points you to the 
>>>>>> python date/time formatting options (link) 
>>>>>> <https://docs.python.org/3/library/datetime.html#strftime-strptime-behavior>
>>>>>>  saying 
>>>>>> %A is the day of the week (ie, Monday).  The Belchertown docs (link) 
>>>>>> <https://github.com/poblabs/weewx-belchertown#a-note-about-date-and-time-formatting-in-your-locale>
>>>>>>  do 
>>>>>> read a little different

[weewx-user] Re: Weewx - Belchertown and 24 hour time format

[Pierre-Yves]

Hi Barry,

I live in France and use the 24h format. Weewx is installed on a Pi4.

Below, the relevant part of the *skin.conf* file located in the *Belchertown 
skin folder*. When I installed the Belchertown skin few years ago, I didn't 
do any modification to have the right format.

[Units]
# This section is for managing the selection and formatting of units.

[[Groups]]
#...
   
[[StringFormats]]
# ...

[[Labels]]
# ...

[[TimeFormats]]
# This section sets the string format to be used for each time 
scale.
# The values below will work in every locale, but may not look
# particularly attractive. See the Customization Guide for 
alternatives.

day= %X
week   = %X (%A)
month  = %x %X
year   = %x %X
rainyear   = %x %X
current= %x %X
ephem_day  = %X
ephem_year = %x %X

Pierre-Yves

Le jeudi 5 mai 2022 à 14:32:09 UTC+2, wix...@gmail.com a écrit :

> Well, just for the "fun" of it, I did a complete re-install of Linux and 
> Weewx (at the moment the computer is only being used to play with Weewx). 
> From a clean install I am still not able to change to the 24hr format for 
> Weewx. Not that it should matter, but Linux is set to the 24hr format. The 
> 4  that surround TimeFormats has come up in the clean install, so I 
> guess it was nothing I did!!  Immediately before  TimeFormats in 
> the weewx.conf is Groups and any changes I make there are actioned. 
> It's not the end of the world that the time is in the 12 hr format, it's 
> now become a battle of (old) man against machine! If anyone has the 24hr 
> time format running ok could they post the relevant parts of their config 
> file??
>
> Barry
>
> On Wednesday, May 4, 2022 at 4:49:14 p.m. UTC-4 vince wrote:
>
>> naaah - no need to do a full install.  You're close enough that this one 
>> is just tweaking something (TBD) into the right config file (TBD).
>>
>> On Wednesday, May 4, 2022 at 1:34:06 PM UTC-7 wix...@gmail.com wrote:
>>
>>> Thanks for the pointer to more reference material Vince. Being new at 
>>> this I have been gathering as much info as possible, unfortunately I miss 
>>> some, and others are contradictory. I have no idea where the 4  came 
>>> from, probably one of my desperate cut and paste attempts!
>>> I think the safest path now is to sort out all my notes and start from 
>>> scratch with a new install, at least it gives me practice playing with 
>>> Linux.
>>> Barry
>>>
>>> On Wednesday, May 4, 2022 at 3:22:06 p.m. UTC-4 vince wrote:
>>>
>>>> For time formats, the weewx customization guide points you to the 
>>>> python date/time formatting options (link) 
>>>> <https://docs.python.org/3/library/datetime.html#strftime-strptime-behavior>
>>>>  saying 
>>>> %A is the day of the week (ie, Monday).  The Belchertown docs (link) 
>>>> <https://github.com/poblabs/weewx-belchertown#a-note-about-date-and-time-formatting-in-your-locale>
>>>>  do 
>>>> read a little differently, pointing to the moment.js way to select a time 
>>>> format, and his example in skin.conf really confuses me completely.
>>>>
>>>> See if "day = HH:MM" works perhaps
>>>> (untested)
>>>>
>>>> It's not clear where you're editing things though.  The number of  
>>>>  pairs looks possibly wrong, which can break things.
>>>>
>>>> On Wednesday, May 4, 2022 at 11:47:20 AM UTC-7 wix...@gmail.com wrote:
>>>>
>>>>> Hi all, I'm new to all this configurtion stuff after using a Vantage 
>>>>> Pro 2 and Ambient s/w for the last 15+ years! I now have a Weatherflow 
>>>>> Tempest using Weewx with the Belchertown skin on a RPi4. So far I have 
>>>>> pretty much persuded it to do what I want with the exception of 
>>>>> displaying 
>>>>> tome in the 24 hour format. Regardless of all the changes I have made it 
>>>>> insists on displaying any time in the AM / PM format i.e. 2:20:00PM 
>>>>> instead 
>>>>> of 14:20. 
>>>>>
>>>>> From what I have read I need to make changes in:
>>>>> [Belchertown]
>>>>> TimeFormats
>>>>>  day =  %HH:MM
>>>>>   week =  %HH:MM on %A (what is the %A)::
>>>>>   etc.
>>>>>   etc.
>>>>>
>>>>> I have t

[weewx-user] Re: WeeWx 4.7.0 and TE923 weather station running on a Pi4. Problem when restarting (sudo /etc/init.d/weewx restart or Pi reboot)

[Pierre-Yves]

Thanks Gary for feedback.
The config archive interval is correct.
[StdArchive]

# If the station hardware supports data logging then the archive 
interval
# will be downloaded from the station. Otherwise, specify it (in 
seconds).
archive_interval = 300

I don't where this '129' value come from
the weewx.conf is attached
PY

Le mardi 19 avril 2022 à 15:23:04 UTC+2, gary@gmail.com a écrit :

> You are going to need to post your weewx.conf, but the error says the 
> archive interval is 129, which is apparently not a supported value. Change 
> that to 300 (for 5 minutes) and see what transpires.
>
> Follow this link on how to post a help request:
> https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user
>
> On Tuesday, April 19, 2022 at 6:17:11 AM UTC-4 Pierre-Yves wrote:
>
>> Hello,
>>
>> After having made a small change to the weewx.conf (station website 
>> registration), I experienced problems for restarting, typing "sudo 
>> /etc/init.d/weewx restart". Same result when rebooting the PI4.
>> About 20 times, the restart failed with the following syslog messages :
>>
>> Apr 18 19:12:50 weewx weewx[2225] ERROR weewx.drivers.te923: Unrecognized 
>> archive interval '129'
>> Apr 18 19:12:50 weewx weewx[2225] INFO weewx.engine: Main loop exiting. 
>> Shutting engine down.
>> Apr 18 19:12:50 weewx weewx[2225] CRITICAL __main__: Caught WeeWxIOError: 
>> Unrecognized archive interval '129'
>> Apr 18 19:12:50 weewx weewx[2225] CRITICAL __main__:   Waiting 60 
>> seconds then retrying...
>>
>> Finally at 19:37:29, weewx restart succeeded and since works fine.
>>
>> I noticed also this syslog line :
>>
>> Apr 18 19:12:50 weewx weewx[2225] INFO weewx.drivers.te923: station time 
>> is 1650236400.0, computer time is 1650301970
>>
>> I do not understand why the station and computer timestamps are so 
>> different.
>>
>> Syslog is attached
>>
>> Any idea on what could cause that behavior ?
>>
>> Thanks a lot,
>>
>> Pierre-Yves
>
>

-- 
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/8a4f57c1-5e1d-4c10-a2cc-16bf5244bf45n%40googlegroups.com.
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2021 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 0

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 4.7.0

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = Roncière 91680 Courson-Monteloup

# Latitude in decimal degrees. Negative for southern hemisphere
latitude = 48.6001
# Longitude in decimal degrees. Negative for western hemisphere.
longitude = 2.1572

# Altitude of the station, with the unit it is in. This is used only
# if the hardware cannot supply a value.
altitude = 87, meter# Choose 'foot' or 'meter' for unit

# Set to type of station hardware. There must be a corresponding stanza
# in this file, which includes a value for the 'driver' option.
station_type = TE923

# If you have a website, you may specify an URL. This is required if you
# intend to register your station.
station_url = 
http://pybeauvais.free.fr/Meteo-Ronciere/belchertown/index.html

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 0

##

[TE923]
# This section is for the Hideki TE923 series of weather stations.

# The station model, e.g., 'Meade TE923W' or 'TFA Nexus'
model = IROX Pro X

# The driver to use:
driver = weewx.drivers.te923

[[sensor_map]]
outTemp = t_1

[weewx-user] WeeWx 4.7.0 and TE923 weather station running on a Pi4. Problem when restarting (sudo /etc/init.d/weewx restart or Pi reboot)

[Pierre-Yves]

Hello,

After having made a small change to the weewx.conf (station website 
registration), I experienced problems for restarting, typing "sudo 
/etc/init.d/weewx restart". Same result when rebooting the PI4.
About 20 times, the restart failed with the following syslog messages :

Apr 18 19:12:50 weewx weewx[2225] ERROR weewx.drivers.te923: Unrecognized 
archive interval '129'
Apr 18 19:12:50 weewx weewx[2225] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Apr 18 19:12:50 weewx weewx[2225] CRITICAL __main__: Caught WeeWxIOError: 
Unrecognized archive interval '129'
Apr 18 19:12:50 weewx weewx[2225] CRITICAL __main__:   Waiting 60 
seconds then retrying...

Finally at 19:37:29, weewx restart succeeded and since works fine.

I noticed also this syslog line :

Apr 18 19:12:50 weewx weewx[2225] INFO weewx.drivers.te923: station time is 
1650236400.0, computer time is 1650301970

I do not understand why the station and computer timestamps are so 
different.

Syslog is attached

Any idea on what could cause that behavior ?

Thanks a lot,

Pierre-Yves

-- 
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/4fa76929-7611-408a-acd3-b967cf810b29n%40googlegroups.com.
pi@weewx:~ $ tail -f /var/log/syslog

"Normal operation..."

Apr 18 19:05:16 weewx weewx[635] INFO weewx.manager: Added record 2022-04-18 
19:05:00 CEST (1650301500) to database 'weewx.sdb'
Apr 18 19:05:16 weewx weewx[635] INFO weewx.manager: Added record 2022-04-18 
19:05:00 CEST (1650301500) to daily summary in 'weewx.sdb'
Apr 18 19:05:19 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 8 files 
for report SeasonsReport in 2.31 seconds
Apr 18 19:05:21 weewx weewx[635] INFO weewx.imagegenerator: Generated 28 images 
for report SeasonsReport in 2.45 seconds
Apr 18 19:05:21 weewx weewx[635] INFO weewx.reportengine: Copied 5 files to 
/var/www/html/weewx
Apr 18 19:05:21 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 6 files 
for report SmartphoneReport in 0.20 seconds
Apr 18 19:05:22 weewx weewx[635] INFO weewx.imagegenerator: Generated 12 images 
for report SmartphoneReport in 0.78 seconds
Apr 18 19:05:22 weewx weewx[635] INFO weewx.reportengine: Copied 6 files to 
/var/www/html/weewx/smartphone
Apr 18 19:05:22 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 1 files 
for report MobileReport in 0.07 seconds
Apr 18 19:05:22 weewx weewx[635] INFO weewx.imagegenerator: Generated 4 images 
for report MobileReport in 0.15 seconds
Apr 18 19:05:22 weewx weewx[635] INFO weewx.reportengine: Copied 2 files to 
/var/www/html/weewx/mobile
Apr 18 19:05:23 weewx weewx[635] INFO user.belchertown: version 1.2
Apr 18 19:05:28 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 11 
files for report Belchertown in 5.61 seconds
Apr 18 19:05:28 weewx weewx[635] INFO weewx.reportengine: Copied 37 files to 
/var/www/html/weewx/belchertown
Apr 18 19:06:27 weewx weewx[635] INFO weewx.reportengine: ftpgenerator: Ftp'd 
82 files in 5.43 seconds

Apr 18 19:10:21 weewx weewx[635] INFO weewx.manager: Added record 2022-04-18 
19:10:00 CEST (1650301800) to database 'weewx.sdb'
Apr 18 19:10:21 weewx weewx[635] INFO weewx.manager: Added record 2022-04-18 
19:10:00 CEST (1650301800) to daily summary in 'weewx.sdb'
Apr 18 19:10:21 weewx weewx[635] INFO weewx.restx: AWEKAS: Published record 
2022-04-18 19:10:00 CEST (1650301800)
Apr 18 19:10:22 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 7 files 
for report SeasonsReport in 1.30 seconds
Apr 18 19:10:23 weewx weewx[635] INFO weewx.imagegenerator: Generated 14 images 
for report SeasonsReport in 0.64 seconds
Apr 18 19:10:23 weewx weewx[635] INFO weewx.reportengine: Copied 0 files to 
/var/www/html/weewx
Apr 18 19:10:23 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 6 files 
for report SmartphoneReport in 0.07 seconds
Apr 18 19:10:23 weewx weewx[635] INFO weewx.imagegenerator: Generated 6 images 
for report SmartphoneReport in 0.20 seconds
Apr 18 19:10:23 weewx weewx[635] INFO weewx.reportengine: Copied 0 files to 
/var/www/html/weewx/smartphone
Apr 18 19:10:23 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 1 files 
for report MobileReport in 0.03 seconds
Apr 18 19:10:23 weewx weewx[635] INFO weewx.imagegenerator: Generated 4 images 
for report MobileReport in 0.15 seconds
Apr 18 19:10:23 weewx weewx[635] INFO weewx.reportengine: Copied 0 files to 
/var/www/html/weewx/mobile
Apr 18 19:10:26 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 11 
files for report Belchertown in 2.73 seconds
Apr 18 19:10:26 weewx weewx[635] INFO weewx.reportengine: Copied 2 files to 
/var/www/html/weewx/belchertown
Apr 18 1