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

[Tom Keffer]

Yes, you have a permissions problem. Try the suggestions in the thread I
linked to earlier.

Also, take a look at the wiki article Understanding permissions
, in
particular the section *Example: add the weewx user to group in a udev rule
*
.

On Sun, Feb 25, 2024 at 9:55 AM Charlie T  wrote:

> *Here is the log file:*
>
> eb 25 11:39:09 raspberrypi weewxd[3688]: INFO weewx.engine: Starting main
> packet loop.
> Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: rtl_433 version
> unknown inputs file rtl_tcp RTL-SDR SoapySDR
> Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: Use -h for usage
> help and see https://triq.org/ for documentation.
> Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: Trying conf file
> at "rtl_433.conf"...
> Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: Trying conf file
> at "/var/lib/weewx/.config/rtl_433/rtl_433.conf"...
> Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: Trying conf file
> at "/usr/local/etc/rtl_433/rtl_433.conf"...
> Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: Trying conf file
> at "/etc/rtl_433/rtl_433.conf"...
> Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: Registered 145
> out of 175 device decoding protocols [ 1-4 8 11-12 15-17 19-21 23 25-26
> 29-36 38-60 63 67-71 73-100 102-105 108-116 119 121 124-128 130-149 151-161
> 163-168 170-175 ]
> Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: usb_open error -3
> Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: Please fix the
> device permissions, e.g. by installing the udev rules file rtl-sdr.rules
> Feb 25 11:39:12 raspberrypi weewxd[3688]: INFO weewx.engine: Main loop
> exiting. Shutting engine down.
> Feb 25 11:39:12 raspberrypi weewxd[3688]: INFO user.sdr: shutdown process
> rtl_433 -M utc -F json
> Feb 25 11:39:12 raspberrypi weewxd[3688]: Exception in thread
> stdout-thread:
> Feb 25 11:39:12 raspberrypi weewxd[3688]: Exception in thread
> stderr-thread:
> Feb 25 11:39:12 raspberrypi weewxd[3688]: Traceback (most recent call
> last):
> Feb 25 11:39:12 raspberrypi weewxd[3688]: Traceback (most recent call
> last):
> Feb 25 11:39:12 raspberrypi weewxd[3688]:   File
> "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
> Feb 25 11:39:12 raspberrypi weewxd[3688]:   File
> "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
> Feb 25 11:39:12 raspberrypi weewxd[3688]: self.run()
> Feb 25 11:39:12 raspberrypi weewxd[3688]:   File
> "/etc/weewx/bin/user/sdr.py", line 198, in run
> Feb 25 11:39:12 raspberrypi weewxd[3688]: self.run()
> Feb 25 11:39:12 raspberrypi weewxd[3688]:   File
> "/etc/weewx/bin/user/sdr.py", line 198, in run
> Feb 25 11:39:12 raspberrypi weewxd[3688]: for line in
> iter(self._fd.readline, ''):
> Feb 25 11:39:12 raspberrypi weewxd[3688]: for line in
> iter(self._fd.readline, ''):
> Feb 25 11:39:12 raspberrypi weewxd[3688]: ValueError:
> PyMemoryView_FromBuffer(): info->buf must not be NULL
> Feb 25 11:39:12 raspberrypi weewxd[3688]: ValueError:
> PyMemoryView_FromBuffer(): info->buf must not be NULL
> Feb 25 11:39:12 raspberrypi weewxd[3688]: INFO user.sdr: shutdown complete
> Feb 25 11:39:12 raspberrypi weewxd[3688]: CRITICAL __main__: Caught
> WeeWxIOError: rtl_433 process is not running
> Feb 25 11:39:12 raspberrypi weewxd[3688]: CRITICAL __main__: 
>  Waiting 60.0 seconds then retrying...
>
>
> On Sunday, February 25, 2024 at 9:20:30 AM UTC-6 Tom Keffer wrote:
>
>> 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
>> .
>> 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 

Re: [weewx-user] Reinstalling weewx

[Neville Davis]

I have a Pi4 with external SSD and I did exactly what Tom has suggested 
without any problems.

I have done this every time I have had a new hardware config to ensure all 
is well.

Nev

On Monday, February 26, 2024 at 1:02:08 AM UTC+10 Tom Keffer wrote:

> Move a temporary database into position, then set it aside when you're 
> satisfied.
>
> On Sun, Feb 25, 2024 at 3:39 AM Bill Petheram  
> wrote:
>
>> I had to reinstall weewx due to a bad system upgrade on a Raspberry Pi 
>> with an external SSD.
>>
>> I wanted to check my installation was OK. I found that weewx started to 
>> read data from my station before I was sure everything was setup properly.
>>
>> It would be nice to be able to turnoff data download at startup to check 
>> that the installation works OK and files are in the correct positions. Then 
>> turn on data loading.
>>
>> This I guess is less of a problem on Rpi 4 as you can boot from USB. I am 
>> using Rpi 3B so I have to use symbolic links.
>>
>> -- 
>> 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/38bba562-b306-4d76-86f6-7ebc31bad1bfn%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/49305bc4-29e4-40fd-a93d-fe2f20cc6ed4n%40googlegroups.com.

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Tom Keffer]

>From your description, you're installing it in the correct spot, however
you're not giving us much information. Instead of just showing the single
error line, it would be helpful to see the log from startup. The reason is
that it will log the location of the user directory.

Set debug=1, then restart weewxd. Post the log *from startup* through the
error.

On Sun, Feb 25, 2024 at 10:55 AM Remy Lavabre 
wrote:

> Hello,
>
> weewx is installed in virtual PIP mode -> ~/weewx-data/... and
> ~/weewx-venv/...
> I manually added the xxx.py driver for my weather station in the
> ~/weewx-data/bin/user directory.
> It is declared in weewx.conf as "driver = usr.xxx", as was done in version
> 4.x
>
> When launching weewxd, I get the message:
>File "/home/pi/weewx-venv/lib/python3.8/site-packages/weewx/engine.py",
> line 104, in setupStation
>  __import__(driver)
> ModuleNotFoundError: *No module named 'usr'*
>
> I tried "driver = xxx.py" without success
>
> if I put my driver in
> ~/weewx-venv/lib/python3.8/site-packages/weewx/drivers/xxx.py and I put
> driver = xxx.py in weewx.conf there is no longer the error.
>
> Moral: Would it be possible to tell me the exact location where to put my
> driver in the user directory and how to declare it in weewx.conf ?
>
> Thank you...
>
> --
> 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/a6fe6217-0ad7-45b0-8dae-74c94db83fbdn%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/CAPq0zEBr%2BYP_ch%2ButQWFxOZ2gQW%3DzzO3xyGWK6q3j_KOQdh98w%40mail.gmail.com.

Re: [weewx-user] Difference between aggregation types has_data and not_null

[bell...@gmail.com]

Well I am pretty sure that at some point in time I needed the ‘is_null’ 
method. I’ve decided to keep my implementation because I can implement a 
more efficient/specific one. I’ve started to prepend my XType so its 
implementation is used instead of XTypeTable.  (As an aside, it feels like 
XTypeTable should always be the last XType in the list.)

On Friday 23 February 2024 at 18:00:07 UTC-5 Tom Keffer wrote:

> You should not have to implement either.
>
> The implementation of has_data runs a not_null query over the aggregation 
> period. In turn not_null either consults the database or, if it's an xtype, 
> runs get_scalar() over the aggregation period. The first non-null value 
> seen causes it to return True.
>
> Of course, that's a fairly compute intensive way of checking for non-null 
> xtype values, but it will work for any xtype. One could optimize the 
> calculation with a specialized version for your type, but so far I haven't 
> heard of a case where it's needed.
>
> -tk
>
>
> On Fri, Feb 23, 2024 at 7:48 AM Karen K  wrote:
>
>> Do I have to implement both the not_null and has_data aggregation in an 
>> XType extension?
>>
>>
>> Tom Keffer schrieb am Freitag, 23. Februar 2024 um 14:01:45 UTC+1:
>>
>> The aggregation not_null does not check first to see if the type exists. 
>> If you know the type exists, it's slightly faster. 
>>
>> In practice, I don't think it's very useful. I may remove it from the 
>> documentation.
>>
>> On Fri, Feb 23, 2024 at 3:48 AM Karen K  wrote:
>>
>> What is the difference between the aggregation types has_data and 
>> not_null according to the documentation in 
>> http://weewx.com/docs/5.0/reference/aggtypes/.
>>
>> -- 
>>
> 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/8abfecfb-7fe5-4e6c-aace-540ed933ea8en%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/a672e629-cd8c-4d29-b159-4be45961f8efn%40googlegroups.com.

Re: [weewx-user] I'm desperate to fix my NOAA reports. Can I please pay someone to help fix my database and recover this data?

[vince]

This has come up a lot of times vs. the Seasons skin if that's what you're 
referring to.  v5 calculates things it expects are available in the db as 
needed, which is slow.  In most cases adding the columns to the schema 
makes the problem go away.  This seems to be coming up for folks starting 
in v3 weewx who are using the original wview-compatible schema rather than 
the wview_extended bigger schema that first appeared in v4 weewx.

You can check to see if you're already running the extended schema in your 
db already by just counting the number of fields:
 echo "SELECT count() FROM PRAGMA_TABLE_INFO('archive');" | sqlite3 
weewx.sdb

The extended schema will return a count of 114.   The original schema had 
around 53 or so if I recall correctly.  If you're weewx 3.x you are 
probably going to see 53 as your answer.

If you are running the small original schema you can either figure out 
which columns are missing and add just those, or update your db to the 
newer/bigger schema and not worry it.  Given you have a fast PC to do this 
on, personally I'd upgrade the db to the big one.  Doesn't take that long 
if you throw some compute at it.

On Sunday, February 25, 2024 at 11:30:14 AM UTC-8 loeriver wrote:

> Sorry for this late question:
>
> I went through this performance issue also and to have an apples to apples 
> comparison I set up weewx 4.10.2 and 5.0.2 on the same computer and had it 
> running with a large db (280MB). 
>
> For 4.10.2 file generation takes around 0.3s, for 5.0.2 it takes 13s (on a 
> well-equipped PC, on my Raspi-type system it is >100s).
>
> Following the explanation from Tom Keffer ("... In V4, this would not have 
> even been attempted." ...) I would expect that in the output for v4.10.2 
> some data should be missing / empty or different compared to the 5.0.2 
> output. But this I do not see: Can somebody point me to the data I should 
> compare for this?
>
> WindnFog schrieb am Samstag, 20. Januar 2024 um 14:14:08 UTC+1:
>
>> Rewording Tom's post to align with one of my professors decades ago, 
>> "That will work, but let's do it the right way." Using 'weectl database' 
>> (followed by the proper parameters) is the right way. Humidex is now stored 
>> in the database, and '$alltime.humidex.max' takes a split second to return 
>> the correct result. My Rube Goldberg software machine has been dismantled.
>>
>> - Paul VE1DX
>>
>> On Friday, January 19, 2024 at 10:55:50 AM UTC-4 Tom Keffer wrote:
>>
>>> I mean this in the gentlest way, but this is basically what the SQLite 
>>> database is doing for you: saving various values in a file where they can 
>>> be retrieved via a general query statement.
>>>
>>> On Fri, Jan 19, 2024 at 6:16 AM WindnFog  wrote:
>>>
 I encountered the same problem trying to calculate the all time humidex 
 in the index.html.tmpl template.  This was taking about 3 minutes on a Pi 
 4. Rather than add humidex to the database (probably the best solution), I 
 calculated all-time humidex once a day using a small program and invoking 
 it with cron. I saved it in a text file that I could then use the Cheetah 
 include statement to read it into index.the html.tmpl template.  This runs 
 in 2 seconds on a Pi 4 and 1 second on a pi 5; if you have an algorithm 
 for 
 appTemp, a similar approach might work.  I was not comfortable with 
 modifying the database because that's not my area of expertise:

 #!/usr/bin/env python3
 # -*- coding: utf-8 -*-

 """
 Program:WeeWX Humidex calculator
 Author: Paul M Dunphy
 Date:   12 December 2023
 Version:1.0.0
 Description:This script sweeps through the Weewx database and 
 calculates the 
 derived parameter humidex for each record.  It then 
 returns the
 maximum humidex and the date/time when it occured.  
 This takes
 about 1.5 seconds on a 900,000 record database as 
 opposed to 3.5
 minutes by the WeeWX system if the recommended 
 aggregate values
 are implemented in the Standard/index.html.tmpl file:
 
 $alltime.humidex.max ($alltime.humidex.max.degree_F) 
 $alltime.humidex.maxtime.format($ALLTIMEFMT)

 It's not clear why the weeWX system takes so long.  
 Possibly
 because it's doing many other things at the same time.  

 This runs on a Raspberry Pi 4B (4 GB Ram) using Debian 
 12
 """

 # Required Libraries

 import sqlite3
 import math
 from datetime import datetime
 import pytz
 from pytz import timezone


 def calculate_humidex(temperature, dewpoint):
 # Constants for the formula
 k = 273.15  # Conversion factor for Celsius to Kelvin

 # Convert temperatures to 

[weewx-user] Re: Problem with WeeWX5 "driver" directory

[vince]

You should install your driver with "weectl extension install" if it is 
packaged correctly to support that. 
 See https://github.com/weewx/weewx/wiki/Weewx-Driver-Development-Tips for 
how and use any of the available drivers as examples if you are packaging a 
driver you wrote.

But to answer, you add user things under ~/weewx-data so it would be 
~/weewx-data/bin/user/xxx.py if you copy it into place manually.

On Sunday, February 25, 2024 at 10:58:55 AM UTC-8 Remy Lavabre wrote:

> Sorry, small error on my part, it's not "usr" that should be read but 
> "user"
>
> Le dimanche 25 février 2024 à 19:55:27 UTC+1, Remy Lavabre a écrit :
>
>> Hello,
>>
>> weewx is installed in virtual PIP mode -> ~/weewx-data/... and 
>> ~/weewx-venv/...
>> I manually added the xxx.py driver for my weather station in the 
>> ~/weewx-data/bin/user directory.
>> It is declared in weewx.conf as "driver = usr.xxx", as was done in 
>> version 4.x
>>
>> When launching weewxd, I get the message:
>>File 
>> "/home/pi/weewx-venv/lib/python3.8/site-packages/weewx/engine.py", line 
>> 104, in setupStation
>>  __import__(driver)
>> ModuleNotFoundError: *No module named 'usr'*
>>
>> I tried "driver = xxx.py" without success
>>
>> if I put my driver in 
>> ~/weewx-venv/lib/python3.8/site-packages/weewx/drivers/xxx.py and I put 
>> driver = xxx.py in weewx.conf there is no longer the error.
>>
>> Moral: Would it be possible to tell me the exact location where to put my 
>> driver in the user directory and how to declare it in weewx.conf ?
>>
>> Thank you...
>>
>>

-- 
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/27da7703-c374-47ee-8243-2df16421cc41n%40googlegroups.com.

Re: [weewx-user] I'm desperate to fix my NOAA reports. Can I please pay someone to help fix my database and recover this data?

[loeriver]

Sorry for this late question:

I went through this performance issue also and to have an apples to apples 
comparison I set up weewx 4.10.2 and 5.0.2 on the same computer and had it 
running with a large db (280MB). 

For 4.10.2 file generation takes around 0.3s, for 5.0.2 it takes 13s (on a 
well-equipped PC, on my Raspi-type system it is >100s).

Following the explanation from Tom Keffer ("... In V4, this would not have 
even been attempted." ...) I would expect that in the output for v4.10.2 
some data should be missing / empty or different compared to the 5.0.2 
output. But this I do not see: Can somebody point me to the data I should 
compare for this?

WindnFog schrieb am Samstag, 20. Januar 2024 um 14:14:08 UTC+1:

> Rewording Tom's post to align with one of my professors decades ago, "That 
> will work, but let's do it the right way." Using 'weectl database' 
> (followed by the proper parameters) is the right way. Humidex is now stored 
> in the database, and '$alltime.humidex.max' takes a split second to return 
> the correct result. My Rube Goldberg software machine has been dismantled.
>
> - Paul VE1DX
>
> On Friday, January 19, 2024 at 10:55:50 AM UTC-4 Tom Keffer wrote:
>
>> I mean this in the gentlest way, but this is basically what the SQLite 
>> database is doing for you: saving various values in a file where they can 
>> be retrieved via a general query statement.
>>
>> On Fri, Jan 19, 2024 at 6:16 AM WindnFog  wrote:
>>
>>> I encountered the same problem trying to calculate the all time humidex 
>>> in the index.html.tmpl template.  This was taking about 3 minutes on a Pi 
>>> 4. Rather than add humidex to the database (probably the best solution), I 
>>> calculated all-time humidex once a day using a small program and invoking 
>>> it with cron. I saved it in a text file that I could then use the Cheetah 
>>> include statement to read it into index.the html.tmpl template.  This runs 
>>> in 2 seconds on a Pi 4 and 1 second on a pi 5; if you have an algorithm for 
>>> appTemp, a similar approach might work.  I was not comfortable with 
>>> modifying the database because that's not my area of expertise:
>>>
>>> #!/usr/bin/env python3
>>> # -*- coding: utf-8 -*-
>>>
>>> """
>>> Program:WeeWX Humidex calculator
>>> Author: Paul M Dunphy
>>> Date:   12 December 2023
>>> Version:1.0.0
>>> Description:This script sweeps through the Weewx database and 
>>> calculates the 
>>> derived parameter humidex for each record.  It then 
>>> returns the
>>> maximum humidex and the date/time when it occured.  This 
>>> takes
>>> about 1.5 seconds on a 900,000 record database as 
>>> opposed to 3.5
>>> minutes by the WeeWX system if the recommended aggregate 
>>> values
>>> are implemented in the Standard/index.html.tmpl file:
>>> 
>>> $alltime.humidex.max ($alltime.humidex.max.degree_F) 
>>> $alltime.humidex.maxtime.format($ALLTIMEFMT)
>>>
>>> It's not clear why the weeWX system takes so long.  
>>> Possibly
>>> because it's doing many other things at the same time.  
>>>
>>> This runs on a Raspberry Pi 4B (4 GB Ram) using Debian 12
>>> """
>>>
>>> # Required Libraries
>>>
>>> import sqlite3
>>> import math
>>> from datetime import datetime
>>> import pytz
>>> from pytz import timezone
>>>
>>>
>>> def calculate_humidex(temperature, dewpoint):
>>> # Constants for the formula
>>> k = 273.15  # Conversion factor for Celsius to Kelvin
>>>
>>> # Convert temperatures to Kelvin
>>> temperature + k
>>> dewpoint_k = dewpoint + k
>>>
>>> # Calculate vapor pressure in hPa
>>> vapor_pressure = 6.112 * math.exp(5417.7530 * ((1 / 273.16) - (1 / 
>>> dewpoint_k)))
>>>
>>> # Humidex calculation
>>> humidex = temperature + ((vapor_pressure - 10) * 0.)
>>> return humidex
>>>
>>>
>>> def get_max_humidex(database_path):
>>> # Connect to the WeeWX database
>>> conn = sqlite3.connect(database_path)
>>> cursor = conn.cursor()
>>>
>>> # Query for temperature, dewpoint, and dateTime for all records
>>> query = "SELECT outTemp, dewpoint, dateTime FROM archive"
>>> cursor.execute(query)
>>>
>>> # Variables to track the maximum humidex and its date
>>> maximum_humidex = None
>>> maximum_humidex_date = None
>>>
>>> for row in cursor:
>>> temperature, dewpoint, date_time = row
>>> if temperature is not None and dewpoint is not None:
>>> humidex = calculate_humidex(temperature, dewpoint)
>>> if maximum_humidex is None or humidex > maximum_humidex:
>>> maximum_humidex = humidex
>>> maximum_humidex_date = date_time
>>>
>>> conn.close()
>>> return maximum_humidex, maximum_humidex_date
>>>
>>>
>>> def convert_utc_to_ast_adt(utc_datetime):
>>> """
>>> Convert a UTC

[weewx-user] Re: Problem with WeeWX5 "driver" directory

[Remy Lavabre]

Sorry, small error on my part, it's not "usr" that should be read but "user"

Le dimanche 25 février 2024 à 19:55:27 UTC+1, Remy Lavabre a écrit :

> Hello,
>
> weewx is installed in virtual PIP mode -> ~/weewx-data/... and 
> ~/weewx-venv/...
> I manually added the xxx.py driver for my weather station in the 
> ~/weewx-data/bin/user directory.
> It is declared in weewx.conf as "driver = usr.xxx", as was done in version 
> 4.x
>
> When launching weewxd, I get the message:
>File "/home/pi/weewx-venv/lib/python3.8/site-packages/weewx/engine.py", 
> line 104, in setupStation
>  __import__(driver)
> ModuleNotFoundError: *No module named 'usr'*
>
> I tried "driver = xxx.py" without success
>
> if I put my driver in 
> ~/weewx-venv/lib/python3.8/site-packages/weewx/drivers/xxx.py and I put 
> driver = xxx.py in weewx.conf there is no longer the error.
>
> Moral: Would it be possible to tell me the exact location where to put my 
> driver in the user directory and how to declare it in weewx.conf ?
>
> Thank you...
>
>

-- 
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/6e41bfdc-59cc-454e-b684-3c012745f412n%40googlegroups.com.

[weewx-user] Problem with WeeWX5 "driver" directory

[Remy Lavabre]

Hello,

weewx is installed in virtual PIP mode -> ~/weewx-data/... and 
~/weewx-venv/...
I manually added the xxx.py driver for my weather station in the 
~/weewx-data/bin/user directory.
It is declared in weewx.conf as "driver = usr.xxx", as was done in version 
4.x

When launching weewxd, I get the message:
   File "/home/pi/weewx-venv/lib/python3.8/site-packages/weewx/engine.py", 
line 104, in setupStation
 __import__(driver)
ModuleNotFoundError: *No module named 'usr'*

I tried "driver = xxx.py" without success

if I put my driver in 
~/weewx-venv/lib/python3.8/site-packages/weewx/drivers/xxx.py and I put 
driver = xxx.py in weewx.conf there is no longer the error.

Moral: Would it be possible to tell me the exact location where to put my 
driver in the user directory and how to declare it in weewx.conf ?

Thank you...

-- 
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/a6fe6217-0ad7-45b0-8dae-74c94db83fbdn%40googlegroups.com.

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

[Charlie T]

*Here is the log file:*

eb 25 11:39:09 raspberrypi weewxd[3688]: INFO weewx.engine: Starting main 
packet loop.
Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: rtl_433 version 
unknown inputs file rtl_tcp RTL-SDR SoapySDR
Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: Use -h for usage 
help and see https://triq.org/ for documentation.
Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: Trying conf file 
at "rtl_433.conf"...
Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: Trying conf file 
at "/var/lib/weewx/.config/rtl_433/rtl_433.conf"...
Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: Trying conf file 
at "/usr/local/etc/rtl_433/rtl_433.conf"...
Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: Trying conf file 
at "/etc/rtl_433/rtl_433.conf"...
Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: Registered 145 
out of 175 device decoding protocols [ 1-4 8 11-12 15-17 19-21 23 25-26 
29-36 38-60 63 67-71 73-100 102-105 108-116 119 121 124-128 130-149 151-161 
163-168 170-175 ]
Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: usb_open error -3
Feb 25 11:39:12 raspberrypi weewxd[3688]: ERROR user.sdr: Please fix the 
device permissions, e.g. by installing the udev rules file rtl-sdr.rules
Feb 25 11:39:12 raspberrypi weewxd[3688]: INFO weewx.engine: Main loop 
exiting. Shutting engine down.
Feb 25 11:39:12 raspberrypi weewxd[3688]: INFO user.sdr: shutdown process 
rtl_433 -M utc -F json
Feb 25 11:39:12 raspberrypi weewxd[3688]: Exception in thread stdout-thread:
Feb 25 11:39:12 raspberrypi weewxd[3688]: Exception in thread stderr-thread:
Feb 25 11:39:12 raspberrypi weewxd[3688]: Traceback (most recent call last):
Feb 25 11:39:12 raspberrypi weewxd[3688]: Traceback (most recent call last):
Feb 25 11:39:12 raspberrypi weewxd[3688]:   File 
"/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
Feb 25 11:39:12 raspberrypi weewxd[3688]:   File 
"/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
Feb 25 11:39:12 raspberrypi weewxd[3688]: self.run()
Feb 25 11:39:12 raspberrypi weewxd[3688]:   File 
"/etc/weewx/bin/user/sdr.py", line 198, in run
Feb 25 11:39:12 raspberrypi weewxd[3688]: self.run()
Feb 25 11:39:12 raspberrypi weewxd[3688]:   File 
"/etc/weewx/bin/user/sdr.py", line 198, in run
Feb 25 11:39:12 raspberrypi weewxd[3688]: for line in 
iter(self._fd.readline, ''):
Feb 25 11:39:12 raspberrypi weewxd[3688]: for line in 
iter(self._fd.readline, ''):
Feb 25 11:39:12 raspberrypi weewxd[3688]: ValueError: 
PyMemoryView_FromBuffer(): info->buf must not be NULL
Feb 25 11:39:12 raspberrypi weewxd[3688]: ValueError: 
PyMemoryView_FromBuffer(): info->buf must not be NULL
Feb 25 11:39:12 raspberrypi weewxd[3688]: INFO user.sdr: shutdown complete
Feb 25 11:39:12 raspberrypi weewxd[3688]: CRITICAL __main__: Caught 
WeeWxIOError: rtl_433 process is not running
Feb 25 11:39:12 raspberrypi weewxd[3688]: CRITICAL __main__:  
 Waiting 60.0 seconds then retrying...


On Sunday, February 25, 2024 at 9:20:30 AM UTC-6 Tom Keffer wrote:

> 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 
> . 
> 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 

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 
> . 
> 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
>>  
>> 
>> .
>>
>

-- 
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] CRITICAL __main__: Caught WeeWxIOError: rtl_433 process is not running

[Tom Keffer]

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
. 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+unsubscr...@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
> 
> .
>

-- 
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/CAPq0zED%2BBG72T3%3DxMYXA3orTnuj67xtemDXR23O0npaTiTix3w%40mail.gmail.com.

Re: [weewx-user] Reinstalling weewx

[Tom Keffer]

Move a temporary database into position, then set it aside when you're
satisfied.

On Sun, Feb 25, 2024 at 3:39 AM Bill Petheram 
wrote:

> I had to reinstall weewx due to a bad system upgrade on a Raspberry Pi
> with an external SSD.
>
> I wanted to check my installation was OK. I found that weewx started to
> read data from my station before I was sure everything was setup properly.
>
> It would be nice to be able to turnoff data download at startup to check
> that the installation works OK and files are in the correct positions. Then
> turn on data loading.
>
> This I guess is less of a problem on Rpi 4 as you can boot from USB. I am
> using Rpi 3B so I have to use symbolic links.
>
> --
> 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/38bba562-b306-4d76-86f6-7ebc31bad1bfn%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/CAPq0zECTHovaw0fi2FSqWW73fGaxjVjqiiQZqjqvY5Q7TJZ-pw%40mail.gmail.com.

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

[Charlie T]

*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+unsubscr...@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.

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

[Charlie T]

I'm having issues with weewx-sdr...any help appreciated

I can run rtl_433 manually and see my sensors out therebut when running 
weewx I get this error message:

root@raspberrypi:/etc/udev# systemctl status weewx
● 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8ec0ecfa-567a-4b7d-b899-c30d36645e28n%40googlegroups.com.

[weewx-user] Reinstalling weewx

[Bill Petheram]

I had to reinstall weewx due to a bad system upgrade on a Raspberry Pi with 
an external SSD.

I wanted to check my installation was OK. I found that weewx started to 
read data from my station before I was sure everything was setup properly.

It would be nice to be able to turnoff data download at startup to check 
that the installation works OK and files are in the correct positions. Then 
turn on data loading.

This I guess is less of a problem on Rpi 4 as you can boot from USB. I am 
using Rpi 3B so I have to use symbolic links.

-- 
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/38bba562-b306-4d76-86f6-7ebc31bad1bfn%40googlegroups.com.

Re: [weewx-user] Interceptor + weewx + Bresser

[sc.lep...@gmail.com]

Re Bonjour  
 
juste pour info   2 parametres que Interceptor  ne reconnait pas  : 

Feb 25 10:58:03 meteo-Ubuntu weewx-BRESSER[91157] INFO user.interceptor: 
unrecognized parameter rainin=0
Feb 25 10:58:03 meteo-Ubuntu weewx-BRESSER[91157] INFO user.interceptor: 
unrecognized parameter soilmoisture=58

Stephane 

Le samedi 24 février 2024 à 18:47:13 UTC+1, sc.lep...@gmail.com a écrit :

> En effet je ne comprends pas pourquoi  je ne recupere pas "soil_moist1"  
> (surtout que c'est la sonde fournie avec la station  !)  la 2eme est celle 
> venant de mon ancienne station  FROGGIT WH-6000
>
> Feb 24 17:36:14 meteo-Ubuntu weewx-BRESSER[78539] DEBUG user.interceptor: 
> GET: ID=X&PASSWORD=&action=updateraww
> &realtime=1
> &rtfreq=5
> &dateutc=now
> &baromin=30.16
> &tempf=48.9
> &humidity=67
> &windspeedmph=3.5
> &windgustmph=4.0
> &winddir=348
> &dewptf=38.3
> &rainin=0
> &dailyrainin=0.110
> &indoortempf=68.0
> &indoorhumidity=56
> &UV=0
> &solarradiation=53.1100
> &soiltempf=67.1
> &soilmoisture=59
> &soiltemp2f=70.8
> &soilmoisture2=60
>
> Voici les data du broker MQTT Mosquitto  : je les récupère bien  :) 
>
>
> {
> "dateTime": "1708796739.0",
> "barometer_mbar": "1022.0119463308273",
> "outHumidity": "75.0",
> "inHumidity": "56.0",
> "outTemp_C": "7.665",
> "inTemp_C": "19.886",
> "windSpeed_kph": "0.0",
> "windGust_kph": "0.0",
> "radiation_Wpm2": "3.72",
> "dewpoint_C": "3.4982",
> "rain_cm": "0.0",
> "UV": "0.0",
> "extraTemp1_C": "19.557",
> "extraTemp2_C": "21.5",
> "extraHumid2": "60.0",
> "soilTemp1_C": "19.557",
> "soilTemp2_C": "21.5",
> "soilMoist2_centibar": "60.0",
> "pressure_mbar": "1016.6418288107507",
> "altimeter_mbar": "1021.9243498035909",
> "appTemp_C": "6.258531406558916",
> "cloudbase_meter": "560.1920276267181",
> "heatindex_C": "6.447222",
> "humidex_C": "7.665",
> "inDewpoint_C": "10.846055159346296",
> "maxSolarRad_Wpm2": "0.004647852952143922",
> "rainRate_cm_per_hour": "0.0",
> "windchill_C": "7.665",
> "hourRain_cm": "0.0",
> "rain24_cm": "0.2794",
> "dayRain_cm": "0.2794",
> "usUnits": "16.0"
> }
>
>
> Le samedi 24 février 2024 à 17:01:50 UTC+1, Remy LAVABRE a écrit :
>
>> Ok;.. Va pour la version FR.
>>
>> 1/ Dans le paquet généré il y a bien un "soil_most2" mais je ne vois pas 
>> de "soil_moist1". Dans le RAW c'est la même chose : 'soil_moisture_2' mais 
>> pas vu de 'soil_moisture_1'
>> Avant d'aller plus loin, il y a peut-être déjà là quelque chose à 
>> regarder qui ne marche pas bien... ?
>>
>> 2/ Dans la config de weewx, une fois résolu le point 1/, dans la section 
>> [interceptor], j'aurais tendance à essayer la chose suivante :
>>
>> [Interceptor]
>> driver = user.interceptor
>> device_type = x
>> ...
>> [[sensor_map_extensions]]
>>...
>> extraTemp1 = soil_temperature_1
>> extraTemp2 = soil_temperature_2
>> extraHumid1 = soil_moisture_1
>> extraHumid2 = soil_moisture_2
>>
>> 3/ Si vous avez des sondes de température et hygrométrie *de sol*, ok 
>> pas de problème. En revanche si vous avez des sondes de température 
>> extérieures indiquant la température et l'hygrométrie de l'air ambiant, 
>> c'est curieux que le nom récupéré soit "soil_xxx".
>> Mais comme je vous l'indiquais, sur Awekas, quand je récupère via 
>> l'API les données envoyées par la base Bresser, les températures des sondes 
>> extérieures sont dans les bons champs, en revanche les hygrométries sont 
>> rentrées dans des hygrométries de sonde de sol..
>> C'est très curieux, et dixit le SAV de Bresser France, je ne suis pas 
>> le seul à avoir signalé la chose !
>> Côté Bresser "teutons", la chose ne semble pas trop leur poser de 
>> problème métaphysiques... A moins que la modification du firmware de la 
>> base de la station ne soit pas une de leurs priorités !
>>
>> *Rémy LAVABRE*
>>
>>
>> Le sam. 24 févr. 2024 à 10:54, sc.lep...@gmail.com  
>> a écrit :
>>
>>> Hello Remy (... et bonjour en Français  :) 
>>>  On va le faire en Français  c'est plus simple  : 
>>>  je récupère les data  via  interceptor en Wifi sur Weewx ... Toutes mes 
>>> datas je les récupère correctement.
>>> la valeur inTemp est celle de la base ca  ok .
>>> mais  j'ai 2 sondes  en plus  et je voudrais également récupérer ces 
>>> données  (soilTemp1 et soilTemp2) et ma question était comment paramétrer 
>>> le driver interceptor
>>> Sur le repo  github  ce n'est pas très clair...
>>>
>>> Mon site est ici  :  https://meteo-pontscorff.fr/ (il y a mes 
>>> coordonnées mail) 
>>> Merci  !
>>> Stéphane
>>>
>>> Le samedi 24 février 2024 à 05:49:39 UTC+1, Remy LAVABRE a écrit :
>>>
 stephane hello,
 I said something stupid to you previously. interceptor intercepts at 
 the wifi level and not as I thought at the 400 or 800 Mhz radio level... 
 sorry!

 so normal that you have inTemp and barometer! :-)

 I too have a Bresser stat