date:20240306

You could git clone the repo and build your own from the makefile. Looks 
like it calls rpmbuild -ba so it should build the srpm hopefully.

On Wednesday, March 6, 2024 at 9:55:19 PM UTC-8 John wrote:

> Not withstanding all of that below Is there a weewx-5.0.2 source rpm 
> (.srpm)
> anywhere public?
>
> I'm a Mageia user who's been installing the Fedora rpms for years (2009) 
> without
> having dependency issues and I'm keen to condition the tradition :-)
>
> Cheers
>
> John in NZ
>
>
> On 7/03/24 04:32, Tom Keffer wrote:
> > See issue #940 .
> >
> > On Wed, Mar 6, 2024 at 3:57 AM Mark Jenks  wrote:
> >
> > Good morning!
> >
> > I was going to do PIP for the new 5.x install, instead of using
> > the setup.py like I have for years.
> > Then I saw the RPM, and figured I was take a look at that, except
> > the rpm doesn't work for Fedora.
> > Fedora is not Enterprise Linux, so you can not install EPEL-Repo
> > for it, but all packages that are in the EPEL, are already avail
> > for Fedora.
> >
> > Looking at the RPM, epel-release is a dependency which is required
> > by the RPM.  So either you create a new RPM for Fedora only, or
> > the dependency needs to be removed.
> >
> > -Mark
> >
> > #
> > dnf install weewx
> > Last metadata expiration check: 0:25:37 ago on Wed 06 Mar 2024
> > 05:30:57 AM CST.
> > Dependencies resolved.
> >
> >  Problem: cannot install the best candidate for the job
> >   - nothing provides epel-release needed by
> > weewx-5.0.2-1.el9.noarch from weewx
> > 
> >
> > rpm -qpR weewx-5.0.2-1.el9.noarch.rpm
> > /bin/sh
> > /bin/sh
> > /bin/sh
> > /usr/bin/getent
> > /usr/sbin/groupadd
> > /usr/sbin/useradd
> > *epel-release*
> > python3
> > python3-cheetah
> > python3-configobj
> > python3-pillow
> > python3-pyserial
> > python3-pyusb
> > rpmlib(CompressedFileNames) <= 3.0.4-1
> > rpmlib(FileDigests) <= 4.6.0-1
> > rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> > rpmlib(PayloadIsXz) <= 5.2-1
> > -- 
> > 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/b8af8921-dcb7-4bfa-9e21-dfdbfb26682cn%40googlegroups.com
> > <
> https://groups.google.com/d/msgid/weewx-user/b8af8921-dcb7-4bfa-9e21-dfdbfb26682cn%40googlegroups.com?utm_medium=email_source=footer
> >.
> >
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "weewx-user" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> > an email to weewx-user+...@googlegroups.com.
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEAf7aEay_sUddjZeR-wMwrL5BR5T0N%3DfLfiyo7Dnhy7fQ%40mail.gmail.com
>  
> > <
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEAf7aEay_sUddjZeR-wMwrL5BR5T0N%3DfLfiyo7Dnhy7fQ%40mail.gmail.com?utm_medium=email_source=footer
> >.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e2896b36-4345-4bc1-986c-0fe65f6ea322n%40googlegroups.com.

Re: [weewx-user] Fedora Weewx RPM install

2024-03-06 Thread John

Not withstanding all of that below Is there a weewx-5.0.2 source rpm (.srpm)
anywhere public?

I'm a Mageia user who's been installing the Fedora rpms for years (2009)
without

having dependency issues and I'm keen to condition the tradition :-)

Cheers

John in NZ

On 7/03/24 04:32, Tom Keffer wrote:

See issue #940 .

On Wed, Mar 6, 2024 at 3:57 AM Mark Jenks wrote:

Good morning!

I was going to do PIP for the new 5.x install, instead of using
the setup.py like I have for years.
Then I saw the RPM, and figured I was take a look at that, except
the rpm doesn't work for Fedora.
Fedora is not Enterprise Linux, so you can not install EPEL-Repo
for it, but all packages that are in the EPEL, are already avail
for Fedora.

Looking at the RPM, epel-release is a dependency which is required
by the RPM. So either you create a new RPM for Fedora only, or
the dependency needs to be removed.

-Mark

#
dnf install weewx
Last metadata expiration check: 0:25:37 ago on Wed 06 Mar 2024
05:30:57 AM CST.
Dependencies resolved.

Problem: cannot install the best candidate for the job
- nothing provides epel-release needed by
weewx-5.0.2-1.el9.noarch from weewx

rpm -qpR weewx-5.0.2-1.el9.noarch.rpm
/bin/sh
/bin/sh
/bin/sh
/usr/bin/getent
/usr/sbin/groupadd
/usr/sbin/useradd
*epel-release*
python3
python3-cheetah
python3-configobj
python3-pillow
python3-pyserial
python3-pyusb
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
--
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/b8af8921-dcb7-4bfa-9e21-dfdbfb26682cn%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/CAPq0zEAf7aEay_sUddjZeR-wMwrL5BR5T0N%3DfLfiyo7Dnhy7fQ%40mail.gmail.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/6ec8ffc2-52d1-4708-b970-3c67180797d8%40gmail.com.

Re: [weewx-user] Raddy L7 Weather Station: XML of Current Conditions-How to Feed WeeWx?

2024-03-06 Thread Graham Eddy

Jsonpath is good for plucking specific values on the subscribe/inward side, but 
it doesn’t help with the publish/outward side (or at least i couldn’t think of 
one). i am still using the eval(expr, weewx-packet or json-message) approach in 
my mqtt implementation
⊣GE⊢

> On 7 Mar 2024, at 11:05 am, Rich Bell  wrote:
> 
> Cool. I’ll check it out. 
> Thanks for the link!
> 
> On Wed, Mar 6, 2024 at 6:33 PM 'Ian Millard' via weewx-user 
> mailto:weewx-user@googlegroups.com>> wrote:
>> FWIW here you can find a very good online json path finder and validator 
>> which is very useful in helping to work out a parsing scheme which can be 
>> adapted for various computer languages: -
>> 
>> JSONPath Finder and Evaluator
>> site24x7.com
>> 
>>  JSONPath 
>> Finder and Evaluator 
>> 
>> site24x7.com  
>>  
>> 
>> 
>>> On 6 Mar 2024, at 21:59, Rich Bell >> > wrote:
>>> 
>>> I have not tried parsing this via MQTTSubscribe, but I have my doubts that 
>>> it currently handles it.
>>> rich
>>> 
>>> On Wed, Mar 6, 2024 at 3:33 PM vince >> > wrote:
 You have some pretty hideously formatted JSON to parse, but here's what it 
 looks like in a more readable format after piping it through 'jq' and 
 doing a little hand editing for readability
 
 {
 
   "sensor": [
 {
   "title": "Indoor",
   "list": [
 [ "Temperature", "68.9", "Â°F" ],
 [ "Humidity", "38", "%" ] ]
 },
 {
   "title": "Outdoor",
   "list": [
 [ "Temperature", "61.7", "Â°F" ],
 [ "Humidity", "29", "%" ] ]
 },
 {
   "title": "Pressure", "list": [
 [ "Absolute", "26.76", "inhg" ],
 [ "Relative", "29.84", "inhg" ] ]
 },
 {
   "title": "Wind Speed",
   "list": [
 [ "Max Daily Gust", "5.1", "mph" ],
 [ "Wind", "1.1", "mph" ],
 [ "Gust", "1.6", "mph" ],
 [ "Direction", "123", "Â°" ],
 [ "Wind Average 2 Minute", "0.4", "mph" ],
 [ "Direction Average 2 Minute", "111", "Â°" ],
 [ "Wind Average 10 Minute", "1.3", "mph" ],
 [ "Direction Average 10 Minute", "134", "Â°" ]
   ]
 },
 {
   "title": "Rainfall",
   "list": [
 [ "Rate", "0.0", "inch/hr" ],
 [ "Hour", "0.0", "inch", "43" ],
 [ "Day", "0.0", "inch", "44" ],
 [ "Week", "0.0", "inch", "45" ],
 [ "Month", "0.0", "inch", "46" ],
 [ "Year", "5.72", "inch", "47" ],
 [ "Total", "10.65", "inch", "48" ]
   ],
   "range": "Range: 0inch to 393.7inch."
 },
 {
   "title": "Solar",
   "list": [
 [ "Light", "261.36", "w/mÂ²" ],
 [ "UVI", "1.2", "" ]
   ]
 }
   ],
   "battery": {
 "title": "Battery",
 "list": [ "All battery are ok" ]
   }
 }
 
 
 On Wednesday, March 6, 2024 at 11:59:36 AM UTC-8 Michael wrote:
> I have officially given up on getting interceptor to work in sniffing 
> mode on Phython3.  
> 
> On Wednesday, March 6, 2024 at 11:17:39 AM UTC-7 matthew wall wrote:
>> it looks like the raddy L7 can upload to wundgerground, so if you are 
>> using the raddy's wifi, you should be able to use the interceptor driver 
>> to capture or directly receive the wunderground output.  setting up the 
>> interceptor is not trivial, but there are many examples.
>> 
>> it would be nice if there were a generic json driver, analogous to the 
>> fileparse driver.  but the json structure varies a lot from one device 
>> to another, and the mechanism for obtaining that json output also 
>> varies.  for example, the tempest broadcasts json data, whereas the 
>> ruddy emits json as a response to http request.  so i understand why no 
>> one has written one yet.
>> 
>> 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/421d1ce1-9dcf-4148-827d-b97c92a4495cn%40googlegroups.com
  
 .
>>> 
>>> 
>> 
>>> -- 
>>> You received

[weewx-user] Re: weewx-sdr howto document available on git hub

2024-03-06 Thread bell...@gmail.com

I only hesitate to share because I know just enough about systemd to be 
dangerous. One should NOT use these as a template but as additional 
information to learn from.
The rtl_433 file. There is additional lines because  I use 
https://pushover.net to monitor things related to WeeWX
# systemd unit configuration file for rtl_433
#

[Unit]
Description=rtl_433 service
Documentation=https://github.com/merbanan/rtl_433/README.md
# StartLimitIntervalSec=5
After=syslog.target network.target

StartLimitIntervalSec=500
StartLimitBurst=5

[Service]
Environment=UUID=replace_me
Restart=on-failure
RestartSec=5s

# Type=exec
#ExecStart=/usr/local/bin/rtl_433 -M utc -F json -F 
mqtt://localhost:1883,retain=0,devices=rtl_433[/host]/devices[/type][/model][/subtype][/channel][/id]
ExecStart=/usr/local/bin/rtl_433 -M utc -F 
mqtt://localhost:1883,retain=0,devices=rtl_433[/host]/devices[/type][/model][/subtype][/channel][/id]

## ExecStartPre runs before, the "-" in the beginning is to let systemd 
continue even on non-zero exit
ExecStartPre=-/bin/bash -c "curl -fsS -m 10 --retry 5 -o /dev/null 
https://hc-ping.com/$UUID;

## ExecStopPost runs after, no matter if ExecStart was success or not. The 
"-" in the beginning is like ExecStartPre
ExecStopPost=-/bin/bash -c "curl -fsS -m 10 --retry 5 -o /dev/null 
https://hc-ping.com/$UUID/fail;


# Restart script if stopped
#Restart=always
# Wait 30s before restart
#RestartSec=30s

# Tag things in the log
# View with: sudo journalctl -f -u rtl_433 -o cat
#SyslogIdentifier=rtl_433


# NOTE: only works in systemd v236+
#   Debain "stretch" includes v232, "buster" includes v239
# Note also the user must be able to create the file and logrotate must be 
amended to rote the log.
StandardOutput=file:/var/log/rtl_433.log
StandardError=file:/var/log/rtl_433.log

#StandardOutput=syslog
#StandardOutput=null
#StandardError=syslog

# To run as a non-root user, uncomment and set username and group here:
#User=pi
#Group=pi

[Install]
WantedBy=multi-user.target  


My WeeWX file. I hacked this up in 4.x. I would think 5.x would work just 
fine.

# source bellrichm-configs weewx/multi/systemd
[Unit]
Description=WeeWX gather %i data 
Documentation=https://weewx.com/docs

Requires=time-sync.target
After=time-sync.target
RequiresMountsFor=/home

[Service]
ExecStart=/home/weewx/bin/weewxd --log-label=weewx-%i  /home/weewx/%i.conf
StandardOutput=null
# To run as a non-root user, uncomment and set username and group here:
User=pi
Group=pi

[Install]
WantedBy=multi-user.target

Yup MQTTSubscribe runs as either driver or service. Nothing special to 
running as a driver.
rich

On Wednesday 6 March 2024 at 17:20:42 UTC-5 vince wrote:

> Nice.  Lets see your system service file(s) to match !
>
> How would you use that way as a driver and not even need to user weewx-sdr 
> ?  Not remembering if MQTT subscribe can run as a driver.  I just run it as 
> an extension.
>
> On Wednesday, March 6, 2024 at 2:06:27 PM UTC-8 bell...@gmail.com wrote:
>
>> Vince,
>> Nice write up.
>> Begin shameless plug…
>> Since I am heavily invested in reading things from MQTT, I just run 
>> rtl_433 as a separate service and subscribe to the topic. I did this 
>> primarily to get the data in a service and secondarily to get sensors that 
>> were not ’mapped’.
>> The service invocation, ‘ExecStart=/usr/local/bin/rtl_433 -M utc -F 
>> mqtt://localhost:1883,retain=0,devices=rtl_433[/host]/devices[/type][/model][/subtype][/channel][/id]’
>> And one topic config looks like this
>> [[topics]]
>> ignore = True
>> [[[message]]] type = individual # Upright freezer (basement) 
>> [[[rtl_433/weather-data/devices/Acurite-606TX/77/temperature_C]]] ignore = 
>> False unit_system = METRIC name = extraTemp8 
>>
>> It may seem more complicated, but since I was invested in MQTT, it 
>> actually simplified it. This was primarily because I could treat rtl_433 as 
>> a separate service
>>
>> End plug
>>
>> On Wednesday 6 March 2024 at 16:14:25 UTC-5 vince wrote:
>>
>>> In working with another weewx user to help him gets his SDR station 
>>> online, it was clear that lots of people (like me) have some problems 
>>> really understanding some of the rtl-433 and sdr documentation that is out 
>>> there.
>>>
>>> After working through it end-to-end a few times on both ubuntu and on a 
>>> raspberry pi, I wrote up the whole setup as a howto with examples mainly 
>>> for future-me but I thought it might be of general interest.  At worst a 
>>> google search should find it for future folks trying to battle SDR into 
>>> submission :-)
>>>
>>> The howto and a small github repo with a patched/enhanced fork of the 
>>> SDR driver is at https://github.com/vinceskahan/sdr-howto if you have 
>>> interest.  Start with the toplevel readme file then read the howto.txt file 
>>> for how I got it working here.
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving

Re: [weewx-user] Re: new install weewx on a new RPi 4b

Patrick - when the sun comes around again in France and you get back to 
this, I did more research and updated the permissions wiki page.  Check out 
the new section at the bottom of the page (link) 

 which 
hopefully explains better.  I got this information from the debian wiki and 
a few blogs and other documents available online in recent years.

On Wednesday, March 6, 2024 at 2:06:03 PM UTC-8 salinois wrote:

> OK Vince,
>
> this is new with the version 5.
>
> I'm going to watch the link "github' and I comme back to you.
>
> good night from France.
>
> Patrick
> Le 06/03/2024 à 22:52, vince a écrit :
>
> 4.9 runs as root so you do not see permission issues there. 
>
> 5.x runs as user 'weewx' so you have to add that user to the correct 
> group(s) to access hardware
>
>
> https://github.com/weewx/weewx/wiki/WeeWX-Frequently-Asked-Questions#why-do-i-get-permission-denied
>
> On Wednesday, March 6, 2024 at 1:46:44 PM UTC-8 salinois wrote:
>
>> I understand that you say me, but why I don't have this issue with 
>> version weewx 4.9 ?
>>
>> the only difference is RPi 3b and now RPi 4b with bulleyes.
>>
>> Weewx 4.9 on RPi 3b with Buster
>>
>> Weewx 5.0.2 on RPi 4b with bulleyes "error"
>>
>> I am watching the link "robotics"
>>
>> Patrick
>>
>>
>>
>> Le 06/03/2024 à 22:31, vince a écrit :
>>
>> You need to work through googling your exact error message. 
>> "SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>> software (error was: [Errno 13] Permission" 
>>
>> See if https://roboticsbackend.com/raspberry-pi-hardware-permissions/ 
>> helps any.   It might be group 'spi' that you need to add the user to.
>>
>> Rather than changing things randomly please read the link end to end to 
>> understand it.
>>
>>
>> On Wednesday, March 6, 2024 at 1:25:20 PM UTC-8 salinois wrote:
>>
>>> Yes, Vince, I took as you said me.
>>>
>>>  $ getent group gpio
>>> gpio:x:997:pi,weewx
>>>
>>> but it is always the same things, this error come , only when I restart 
>>> weewx. !!!
>>>
>>> patrick
>>> Le 06/03/2024 à 22:15, vince a écrit :
>>>
>>> patrick - as I said earlier, 
>>> " /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
>>> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>>> software (error was: [Errno 13] Permission non accordée)" clearly indicates 
>>> a permission issue. 
>>>
>>> add the weewx user to group gpio.  Really.
>>>
>>> On Wednesday, March 6, 2024 at 1:12:57 PM UTC-8 salinois wrote:
>>>
 yes, I took that.

 ls -ail /etc/weewx/bin/user/
 total 36
 526359 drwxrwsr-x 3 weewx weewx  4096  6 mars  21:52 .


 526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
 524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05 byows.py
 526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15 extensions.py
 526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15 __init__.py

 655698 drwxr-sr-x 2 weewx weewx  4096  6 mars  21:54 __pycache__
 524317 -rw-r--r-- 1 piweewx  4052  6 mars  21:52 stats.py

 This is again better.

 [Mar  6 21:57:13 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
 value: 0.0
 Mar  6 21:57:15 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
 value: 0.0
 Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
 record 2024-03-06 21:57:00 CET (1709758620) to database 'weewx.sdb'
 Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
 record 2024-03-06 21:57:00 CET (1709758620) to daily summary in 'weewx.sdb'
 Mar  6 21:57:16 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
 value: 0.0
 Mar  6 21:57:17 raspberrypi weewxd[31835]: INFO weewx.cheetahgenerator: 
 Generated 8 files for report SeasonsReport in 1.26 seconds
 Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.imagegenerator: 
 Generated 15 images for report SeasonsReport in 0.65 seconds
 Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.reportengine: 
 Copied 0 files to /var/www/html/weewx
 Mar  6 21:57:18 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
 value: 0.0]

 Weird, I don't use statistics in my driver !!!

 but I had just an error When I restart weewx 

 Mar  6 22:05:16 raspberrypi weewxd[32027]: 
 /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
 SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
 software (error was: [Errno 13] Permission non accordée)
 Mar  6 22:05:16 raspberrypi weewxd[32027]: 

   warnings.warn(

 My command that say "OK"

  sudo pip3 install gpiozero
 Looking in indexes: https://pypi.org/simple, 
 https://www.piwheels.org/simple
 Requirement already satisfied: gpiozero in 
 /usr/lib/python3/dist-packages (1.6.2)


 patrick


 Le

Re: [weewx-user] Raddy L7 Weather Station: XML of Current Conditions-How to Feed WeeWx?

2024-03-06 Thread Rich Bell

Cool. I’ll check it out.
Thanks for the link!

On Wed, Mar 6, 2024 at 6:33 PM 'Ian Millard' via weewx-user <
weewx-user@googlegroups.com> wrote:

> FWIW here you can find a very good online json path finder and validator
> which is very useful in helping to work out a parsing scheme which can be
> adapted for various computer languages: -
>
> JSONPath Finder and Evaluator
> 
> site24x7.com
> 
> [image: site24x7-fav.ico]
> 
> 
>
>
> On 6 Mar 2024, at 21:59, Rich Bell  wrote:
>
> I have not tried parsing this via MQTTSubscribe, but I have my doubts that
> it currently handles it.
> rich
>
> On Wed, Mar 6, 2024 at 3:33 PM vince  wrote:
>
>> You have some pretty hideously formatted JSON to parse, but here's what
>> it looks like in a more readable format after piping it through 'jq' and
>> doing a little hand editing for readability
>>
>> {
>>
>>   "sensor": [
>> {
>>   "title": "Indoor",
>>   "list": [
>> [ "Temperature", "68.9", "Â°F" ],
>> [ "Humidity", "38", "%" ] ]
>> },
>> {
>>   "title": "Outdoor",
>>   "list": [
>> [ "Temperature", "61.7", "Â°F" ],
>> [ "Humidity", "29", "%" ] ]
>> },
>> {
>>   "title": "Pressure", "list": [
>> [ "Absolute", "26.76", "inhg" ],
>> [ "Relative", "29.84", "inhg" ] ]
>> },
>> {
>>   "title": "Wind Speed",
>>   "list": [
>> [ "Max Daily Gust", "5.1", "mph" ],
>> [ "Wind", "1.1", "mph" ],
>> [ "Gust", "1.6", "mph" ],
>> [ "Direction", "123", "Â°" ],
>> [ "Wind Average 2 Minute", "0.4", "mph" ],
>> [ "Direction Average 2 Minute", "111", "Â°" ],
>> [ "Wind Average 10 Minute", "1.3", "mph" ],
>> [ "Direction Average 10 Minute", "134", "Â°" ]
>>   ]
>> },
>> {
>>   "title": "Rainfall",
>>   "list": [
>> [ "Rate", "0.0", "inch/hr" ],
>> [ "Hour", "0.0", "inch", "43" ],
>> [ "Day", "0.0", "inch", "44" ],
>> [ "Week", "0.0", "inch", "45" ],
>> [ "Month", "0.0", "inch", "46" ],
>> [ "Year", "5.72", "inch", "47" ],
>> [ "Total", "10.65", "inch", "48" ]
>>   ],
>>   "range": "Range: 0inch to 393.7inch."
>> },
>> {
>>   "title": "Solar",
>>   "list": [
>> [ "Light", "261.36", "w/mÂ²" ],
>> [ "UVI", "1.2", "" ]
>>   ]
>> }
>>   ],
>>   "battery": {
>> "title": "Battery",
>> "list": [ "All battery are ok" ]
>>   }
>> }
>>
>>
>> On Wednesday, March 6, 2024 at 11:59:36 AM UTC-8 Michael wrote:
>>
>>> I have officially given up on getting interceptor to work in sniffing
>>> mode on Phython3.
>>>
>>> On Wednesday, March 6, 2024 at 11:17:39 AM UTC-7 matthew wall wrote:
>>>
 it looks like the raddy L7 can upload to wundgerground, so if you are
 using the raddy's wifi, you should be able to use the interceptor driver to
 capture or directly receive the wunderground output.  setting up the
 interceptor is not trivial, but there are many examples.

 it would be nice if there were a generic json driver, analogous to the
 fileparse driver.  but the json structure varies a lot from one device to
 another, and the mechanism for obtaining that json output also varies.  for
 example, the tempest broadcasts json data, whereas the ruddy emits json as
 a response to http request.  so i understand why no one has written one 
 yet.

 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/421d1ce1-9dcf-4148-827d-b97c92a4495cn%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/CAG4CQqyqTkcda9a5EWe6DVbz2oPJtnqf_9Q2kbG%3DWCksxKgsvw%40mail.gmail.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

Re: [weewx-user] Raddy L7 Weather Station: XML of Current Conditions-How to Feed WeeWx?

2024-03-06 Thread 'Ian Millard' via weewx-user

FWIW here you can find a very good online json path finder and validator which 
is very useful in helping to work out a parsing scheme which can be adapted for 
various computer languages: -

https://www.site24x7.com/tools/jsonpath-finder-validator.html

> On 6 Mar 2024, at 21:59, Rich Bell  wrote:
> 
> I have not tried parsing this via MQTTSubscribe, but I have my doubts that it 
> currently handles it.
> rich
> 
> On Wed, Mar 6, 2024 at 3:33 PM vince  > wrote:
>> You have some pretty hideously formatted JSON to parse, but here's what it 
>> looks like in a more readable format after piping it through 'jq' and doing 
>> a little hand editing for readability
>> 
>> {
>> 
>>   "sensor": [
>> {
>>   "title": "Indoor",
>>   "list": [
>> [ "Temperature", "68.9", "Â°F" ],
>> [ "Humidity", "38", "%" ] ]
>> },
>> {
>>   "title": "Outdoor",
>>   "list": [
>> [ "Temperature", "61.7", "Â°F" ],
>> [ "Humidity", "29", "%" ] ]
>> },
>> {
>>   "title": "Pressure", "list": [
>> [ "Absolute", "26.76", "inhg" ],
>> [ "Relative", "29.84", "inhg" ] ]
>> },
>> {
>>   "title": "Wind Speed",
>>   "list": [
>> [ "Max Daily Gust", "5.1", "mph" ],
>> [ "Wind", "1.1", "mph" ],
>> [ "Gust", "1.6", "mph" ],
>> [ "Direction", "123", "Â°" ],
>> [ "Wind Average 2 Minute", "0.4", "mph" ],
>> [ "Direction Average 2 Minute", "111", "Â°" ],
>> [ "Wind Average 10 Minute", "1.3", "mph" ],
>> [ "Direction Average 10 Minute", "134", "Â°" ]
>>   ]
>> },
>> {
>>   "title": "Rainfall",
>>   "list": [
>> [ "Rate", "0.0", "inch/hr" ],
>> [ "Hour", "0.0", "inch", "43" ],
>> [ "Day", "0.0", "inch", "44" ],
>> [ "Week", "0.0", "inch", "45" ],
>> [ "Month", "0.0", "inch", "46" ],
>> [ "Year", "5.72", "inch", "47" ],
>> [ "Total", "10.65", "inch", "48" ]
>>   ],
>>   "range": "Range: 0inch to 393.7inch."
>> },
>> {
>>   "title": "Solar",
>>   "list": [
>> [ "Light", "261.36", "w/mÂ²" ],
>> [ "UVI", "1.2", "" ]
>>   ]
>> }
>>   ],
>>   "battery": {
>> "title": "Battery",
>> "list": [ "All battery are ok" ]
>>   }
>> }
>> 
>> 
>> On Wednesday, March 6, 2024 at 11:59:36 AM UTC-8 Michael wrote:
>>> I have officially given up on getting interceptor to work in sniffing mode 
>>> on Phython3.  
>>> 
>>> On Wednesday, March 6, 2024 at 11:17:39 AM UTC-7 matthew wall wrote:
 it looks like the raddy L7 can upload to wundgerground, so if you are 
 using the raddy's wifi, you should be able to use the interceptor driver 
 to capture or directly receive the wunderground output.  setting up the 
 interceptor is not trivial, but there are many examples.
 
 it would be nice if there were a generic json driver, analogous to the 
 fileparse driver.  but the json structure varies a lot from one device to 
 another, and the mechanism for obtaining that json output also varies.  
 for example, the tempest broadcasts json data, whereas the ruddy emits 
 json as a response to http request.  so i understand why no one has 
 written one yet.
 
 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/421d1ce1-9dcf-4148-827d-b97c92a4495cn%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/CAG4CQqyqTkcda9a5EWe6DVbz2oPJtnqf_9Q2kbG%3DWCksxKgsvw%40mail.gmail.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/4AC3D106-F4E4-479A-804D-C374DCEB94EA%40btinternet.com.

[weewx-user] Re: weewx-sdr howto document available on git hub

Nice.  Lets see your system service file(s) to match !

How would you use that way as a driver and not even need to user weewx-sdr 
?  Not remembering if MQTT subscribe can run as a driver.  I just run it as 
an extension.

On Wednesday, March 6, 2024 at 2:06:27 PM UTC-8 bell...@gmail.com wrote:

> Vince,
> Nice write up.
> Begin shameless plug…
> Since I am heavily invested in reading things from MQTT, I just run 
> rtl_433 as a separate service and subscribe to the topic. I did this 
> primarily to get the data in a service and secondarily to get sensors that 
> were not ’mapped’.
> The service invocation, ‘ExecStart=/usr/local/bin/rtl_433 -M utc -F 
> mqtt://localhost:1883,retain=0,devices=rtl_433[/host]/devices[/type][/model][/subtype][/channel][/id]’
> And one topic config looks like this
> [[topics]]
> ignore = True
> [[[message]]] type = individual # Upright freezer (basement) 
> [[[rtl_433/weather-data/devices/Acurite-606TX/77/temperature_C]]] ignore = 
> False unit_system = METRIC name = extraTemp8 
>
> It may seem more complicated, but since I was invested in MQTT, it 
> actually simplified it. This was primarily because I could treat rtl_433 as 
> a separate service
>
> End plug
>
> On Wednesday 6 March 2024 at 16:14:25 UTC-5 vince wrote:
>
>> In working with another weewx user to help him gets his SDR station 
>> online, it was clear that lots of people (like me) have some problems 
>> really understanding some of the rtl-433 and sdr documentation that is out 
>> there.
>>
>> After working through it end-to-end a few times on both ubuntu and on a 
>> raspberry pi, I wrote up the whole setup as a howto with examples mainly 
>> for future-me but I thought it might be of general interest.  At worst a 
>> google search should find it for future folks trying to battle SDR into 
>> submission :-)
>>
>> The howto and a small github repo with a patched/enhanced fork of the SDR 
>> driver is at https://github.com/vinceskahan/sdr-howto if you have 
>> interest.  Start with the toplevel readme file then read the howto.txt file 
>> for how I got it working here.
>>
>>

-- 
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/030139c5-c82b-4bb5-8bbf-540f66bf6579n%40googlegroups.com.

[weewx-user] Re: weewx-sdr howto document available on git hub

2024-03-06 Thread bell...@gmail.com

Vince,
Nice write up.
Begin shameless plug…
Since I am heavily invested in reading things from MQTT, I just run rtl_433 
as a separate service and subscribe to the topic. I did this primarily to 
get the data in a service and secondarily to get sensors that were not 
’mapped’.
The service invocation, ‘ExecStart=/usr/local/bin/rtl_433 -M utc -F 
mqtt://localhost:1883,retain=0,devices=rtl_433[/host]/devices[/type][/model][/subtype][/channel][/id]’
And one topic config looks like this
[[topics]]
ignore = True
[[[message]]] type = individual # Upright freezer (basement) 
[[[rtl_433/weather-data/devices/Acurite-606TX/77/temperature_C]]] ignore = 
False unit_system = METRIC name = extraTemp8 

It may seem more complicated, but since I was invested in MQTT, it actually 
simplified it. This was primarily because I could treat rtl_433 as a 
separate service

End plug

On Wednesday 6 March 2024 at 16:14:25 UTC-5 vince wrote:

> In working with another weewx user to help him gets his SDR station 
> online, it was clear that lots of people (like me) have some problems 
> really understanding some of the rtl-433 and sdr documentation that is out 
> there.
>
> After working through it end-to-end a few times on both ubuntu and on a 
> raspberry pi, I wrote up the whole setup as a howto with examples mainly 
> for future-me but I thought it might be of general interest.  At worst a 
> google search should find it for future folks trying to battle SDR into 
> submission :-)
>
> The howto and a small github repo with a patched/enhanced fork of the SDR 
> driver is at https://github.com/vinceskahan/sdr-howto if you have 
> interest.  Start with the toplevel readme file then read the howto.txt file 
> for how I got it working here.
>
>

-- 
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/e3c6f100-f5b0-422d-a361-58d12d8438ban%40googlegroups.com.

Re: [weewx-user] Re: new install weewx on a new RPi 4b


OK Vince,

this is new with the version 5.

I'm going to watch the link "github' and I comme back to you.

good night from France.

Patrick

Le 06/03/2024 à 22:52, vince a écrit :

4.9 runs as root so you do not see permission issues there.

5.x runs as user 'weewx' so you have to add that user to the correct 
group(s) to access hardware


https://github.com/weewx/weewx/wiki/WeeWX-Frequently-Asked-Questions#why-do-i-get-permission-denied

On Wednesday, March 6, 2024 at 1:46:44 PM UTC-8 salinois wrote:

I understand that you say me, but why I don't have this issue with
version weewx 4.9 ?

the only difference is RPi 3b and now RPi 4b with bulleyes.

Weewx 4.9 on RPi 3b with Buster

Weewx 5.0.2 on RPi 4b with bulleyes "error"

I am watching the link "robotics"

Patrick



Le 06/03/2024 à 22:31, vince a écrit :

You need to work through googling your exact error message.
"SPISoftwareFallback: failed to initialize hardware SPI, falling
back to software (error was: [Errno 13] Permission"

See if
https://roboticsbackend.com/raspberry-pi-hardware-permissions/
helps any.   It might be group 'spi' that you need to add the
user to.

Rather than changing things randomly please read the link end to
end to understand it.


On Wednesday, March 6, 2024 at 1:25:20 PM UTC-8 salinois wrote:

Yes, Vince, I took as you said me.

 $ getent group gpio
gpio:x:997:pi,weewx

but it is always the same things, this error come , only when
I restart weewx. !!!

patrick

Le 06/03/2024 à 22:15, vince a écrit :

patrick - as I said earlier,
" /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153:
SPISoftwareFallback: failed to initialize hardware SPI,
falling back to software (error was: [Errno 13] Permission
non accordée)" clearly indicates a permission issue.

add the weewx user to group gpio.  Really.

On Wednesday, March 6, 2024 at 1:12:57 PM UTC-8 salinois wrote:

yes, I took that.

ls -ail /etc/weewx/bin/user/
total 36
526359 drwxrwsr-x 3 weewx weewx  4096  6 mars  21:52 .


526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05
byows.py
526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15
extensions.py
526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15
__init__.py

655698 drwxr-sr-x 2 weewx weewx  4096  6 mars  21:54
__pycache__
524317 -rw-r--r-- 1 pi    weewx  4052  6 mars  21:52
stats.py

This is again better.

[Mar  6 21:57:13 raspberrypi weewxd.py: BYOWS RPi:
Unknown Wind Vane value: 0.0
Mar  6 21:57:15 raspberrypi weewxd.py: BYOWS RPi:
Unknown Wind Vane value: 0.0
Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO
weewx.manager: Added record 2024-03-06 21:57:00 CET
(1709758620) to database 'weewx.sdb'
Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO
weewx.manager: Added record 2024-03-06 21:57:00 CET
(1709758620) to daily summary in 'weewx.sdb'
Mar  6 21:57:16 raspberrypi weewxd.py: BYOWS RPi:
Unknown Wind Vane value: 0.0
Mar  6 21:57:17 raspberrypi weewxd[31835]: INFO
weewx.cheetahgenerator: Generated 8 files for report
SeasonsReport in 1.26 seconds
Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO
weewx.imagegenerator: Generated 15 images for report
SeasonsReport in 0.65 seconds
Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO
weewx.reportengine: Copied 0 files to /var/www/html/weewx
Mar  6 21:57:18 raspberrypi weewxd.py: BYOWS RPi:
Unknown Wind Vane value: 0.0]

Weird, I don't use statistics in my driver !!!

but I had just an error When I restart weewx

Mar  6 22:05:16 raspberrypi weewxd[32027]:
/usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153:
SPISoftwareFallback: failed to initialize hardware SPI,
falling back to software (error was: [Errno 13]
Permission non accordée)
Mar  6 22:05:16 raspberrypi weewxd[32027]:

  warnings.warn(

My command that say "OK"

 sudo pip3 install gpiozero
Looking in indexes: https://pypi.org/simple,
https://www.piwheels.org/simple
Requirement already satisfied: gpiozero in
/usr/lib/python3/dist-packages (1.6.2)


patrick


Le 06/03/2024 à 21:43, Tom Keffer a écrit :

You are missing a search list extension called "stats".
I suspect that this is the old stats module that came

[weewx-user] Re: Raddy L7 Weather Station: XML of Current Conditions-How to Feed WeeWx?

2024-03-06 Thread bell...@gmail.com


Considering the format could be any valid json, it is a bit of a challenge. 
I haven’t had a chance to see if MQTTSubscribe could handle this, but when 
I get some time I plan to
rich
On Wednesday 6 March 2024 at 13:17:39 UTC-5 matthew wall wrote:

> it looks like the raddy L7 can upload to wundgerground, so if you are 
> using the raddy's wifi, you should be able to use the interceptor driver to 
> capture or directly receive the wunderground output.  setting up the 
> interceptor is not trivial, but there are many examples.
>
> it would be nice if there were a generic json driver, analogous to the 
> fileparse driver.  but the json structure varies a lot from one device to 
> another, and the mechanism for obtaining that json output also varies.  for 
> example, the tempest broadcasts json data, whereas the ruddy emits json as 
> a response to http request.  so i understand why no one has written one yet.
>
> 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/c08038e2-ea30-4afe-8282-76c1b46ab885n%40googlegroups.com.

Re: [weewx-user] Re: Raddy L7 Weather Station: XML of Current Conditions-How to Feed WeeWx?

2024-03-06 Thread Rich Bell

I have not tried parsing this via MQTTSubscribe, but I have my doubts that
it currently handles it.
rich

On Wed, Mar 6, 2024 at 3:33 PM vince  wrote:

> You have some pretty hideously formatted JSON to parse, but here's what it
> looks like in a more readable format after piping it through 'jq' and doing
> a little hand editing for readability
>
> {
>
>   "sensor": [
> {
>   "title": "Indoor",
>   "list": [
> [ "Temperature", "68.9", "Â°F" ],
> [ "Humidity", "38", "%" ] ]
> },
> {
>   "title": "Outdoor",
>   "list": [
> [ "Temperature", "61.7", "Â°F" ],
> [ "Humidity", "29", "%" ] ]
> },
> {
>   "title": "Pressure", "list": [
> [ "Absolute", "26.76", "inhg" ],
> [ "Relative", "29.84", "inhg" ] ]
> },
> {
>   "title": "Wind Speed",
>   "list": [
> [ "Max Daily Gust", "5.1", "mph" ],
> [ "Wind", "1.1", "mph" ],
> [ "Gust", "1.6", "mph" ],
> [ "Direction", "123", "Â°" ],
> [ "Wind Average 2 Minute", "0.4", "mph" ],
> [ "Direction Average 2 Minute", "111", "Â°" ],
> [ "Wind Average 10 Minute", "1.3", "mph" ],
> [ "Direction Average 10 Minute", "134", "Â°" ]
>   ]
> },
> {
>   "title": "Rainfall",
>   "list": [
> [ "Rate", "0.0", "inch/hr" ],
> [ "Hour", "0.0", "inch", "43" ],
> [ "Day", "0.0", "inch", "44" ],
> [ "Week", "0.0", "inch", "45" ],
> [ "Month", "0.0", "inch", "46" ],
> [ "Year", "5.72", "inch", "47" ],
> [ "Total", "10.65", "inch", "48" ]
>   ],
>   "range": "Range: 0inch to 393.7inch."
> },
> {
>   "title": "Solar",
>   "list": [
> [ "Light", "261.36", "w/mÂ²" ],
> [ "UVI", "1.2", "" ]
>   ]
> }
>   ],
>   "battery": {
> "title": "Battery",
> "list": [ "All battery are ok" ]
>   }
> }
>
>
> On Wednesday, March 6, 2024 at 11:59:36 AM UTC-8 Michael wrote:
>
>> I have officially given up on getting interceptor to work in sniffing
>> mode on Phython3.
>>
>> On Wednesday, March 6, 2024 at 11:17:39 AM UTC-7 matthew wall wrote:
>>
>>> it looks like the raddy L7 can upload to wundgerground, so if you are
>>> using the raddy's wifi, you should be able to use the interceptor driver to
>>> capture or directly receive the wunderground output.  setting up the
>>> interceptor is not trivial, but there are many examples.
>>>
>>> it would be nice if there were a generic json driver, analogous to the
>>> fileparse driver.  but the json structure varies a lot from one device to
>>> another, and the mechanism for obtaining that json output also varies.  for
>>> example, the tempest broadcasts json data, whereas the ruddy emits json as
>>> a response to http request.  so i understand why no one has written one yet.
>>>
>>> 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/421d1ce1-9dcf-4148-827d-b97c92a4495cn%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/CAG4CQqyqTkcda9a5EWe6DVbz2oPJtnqf_9Q2kbG%3DWCksxKgsvw%40mail.gmail.com.

Re: [weewx-user] RSS - FEED

2024-03-06 Thread Fjordey

Thanks Tom, I will make the changes, and look at the rain further in the 
next few days..

On Wednesday, March 6, 2024 at 3:12:16 PM UTC-5 Tom Keffer wrote:

> A template file is a not-very-obvious mix of HTML and Cheetah tags. To get 
> the formatting you need, change this
>
> #for $x in $observations
>   #if $getattr($current, $x).has_data
> #if $x == 'windSpeed'
> $obs.label.wind: $current.windSpeed $gettext("from") 
> $current.windDir;
> #else
> $obs.label[$x]: $getattr($current, $x);
> #end if
>   #end if
> #end for
>
> to this
>
> #for $x in $observations
>   #if $getattr($current, $x).has_data
> #if $x == 'windSpeed'
> $obs.label.wind: $current.windSpeed $gettext("from") 
> $current.windDir;
>
> #else
> $obs.label[$x]: $getattr($current, $x);
> #end if
>   #end if
> #end for
>
> The "rain" tag under "Weather Conditions" is the rain that fell during the 
> last archive period, which is generally only 5-30 minutes. If you want rain 
> since midnight, you can find that under "Daily summary".
>
>
>
>
>
>
>
> On Wed, Mar 6, 2024 at 7:08 AM Fjordey  wrote:
>
>> I realize not many are using the RSS feed, yet I am to just get a quick 
>> check of things while sorting through my news feeds... regaurdless the 
>> reason I need help if possible...
>>
>> I'm not an expert by any means, but can fumble my way through the coding 
>> most times.
>>
>> #1 I edited the template to only provide the current conditions. That 
>> works.
>> #2 I was trying to format the returned data:
>>
>> Wind: 0 mph from N/A; Rain: 0.00 
>>
>> trying to remove the ";" and put Rain: 0.00 on the next line.. (have not 
>> figured that out)
>>
>> #3 I have noticed that my rain total is 0.00 when it should show 0.80 for 
>> toal rain.
>> Note: the rain total and text formating were not working before I edited 
>> the template.
>>
>> any help would be apreciated... Hopefully I'm just overlooking something 
>> simple.
>>
>> https://weather.3utilities.icu/rss.xml 
>>
>> my current rss.xml.tmpl:
>>
>> 
>> >   xmlns:content="http://purl.org/rss/1.0/modules/content/;
>>   xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#; >
>>
>> #set $timespans = [{"span": $day, "label": $gettext("Daily summary as 
>> of")}, {"span": $month, "label": $gettext("Monthly summary as of")}, 
>> {"span": $year, "label": $gettext("Yearly summary as of")}]
>>
>> #set $observations = $to_list($DisplayOptions.get('observations_rss', 
>> ['outTemp', 'inTemp', 'barometer', 'windSpeed', 'rain', 'rainRate']))
>> #set $obs_type_sum = $to_list($DisplayOptions.get('obs_type_sum', 
>> ['rain']))
>> #set $obs_type_max = $to_list($DisplayOptions.get('obs_type_max', 
>> ['rainRate']))
>>
>>   
>> $gettext("Weather Conditions") : $station.location
>> $station.station_url
>> $gettext("Current conditions, and daily, monthly, and 
>> yearly summaries")
>> "$lang"
>> $current.dateTime.format("%a, %d %b %Y %H:%M:%S 
>> %Z")
>>
>> $current.dateTime.format("%a, %d %b %Y %H:%M:%S 
>> %Z")
>> http://blogs.law.harvard.edu/tech/rss
>> weewx $station.version
>> $current.interval.string('')
>>
>> 
>>   $gettext("Weather Conditions at") $current.dateTime
>>   $station.station_url
>>   
>> #for $x in $observations
>>   #if $getattr($current, $x).has_data
>> #if $x == 'windSpeed'
>> $obs.label.wind: $current.windSpeed $gettext("from") 
>> $current.windDir;
>> #else
>> $obs.label[$x]: $getattr($current, $x);
>> #end if
>>   #end if
>> #end for
>>   
>>   $current.dateTime.format("%a, %d %b %Y %H:%M:%S 
>> %Z")
>>   
>> 
>>
>>   
>> 
>>
>> -- 
>> 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/eba24381-6fbf-437b-ad2f-a09fffa01fe0n%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/c2f2c6ea-16aa-414f-a3b6-50255d0aa2d0n%40googlegroups.com.

Re: [weewx-user] Re: new install weewx on a new RPi 4b

4.9 runs as root so you do not see permission issues there.

5.x runs as user 'weewx' so you have to add that user to the correct 
group(s) to access hardware

https://github.com/weewx/weewx/wiki/WeeWX-Frequently-Asked-Questions#why-do-i-get-permission-denied

On Wednesday, March 6, 2024 at 1:46:44 PM UTC-8 salinois wrote:

> I understand that you say me, but why I don't have this issue with version 
> weewx 4.9 ?
>
> the only difference is RPi 3b and now RPi 4b with bulleyes.
>
> Weewx 4.9 on RPi 3b with Buster
>
> Weewx 5.0.2 on RPi 4b with bulleyes "error"
>
> I am watching the link "robotics"
>
> Patrick
>
>
>
> Le 06/03/2024 à 22:31, vince a écrit :
>
> You need to work through googling your exact error message. 
> "SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
> software (error was: [Errno 13] Permission" 
>
> See if https://roboticsbackend.com/raspberry-pi-hardware-permissions/ 
> helps any.   It might be group 'spi' that you need to add the user to.
>
> Rather than changing things randomly please read the link end to end to 
> understand it.
>
>
> On Wednesday, March 6, 2024 at 1:25:20 PM UTC-8 salinois wrote:
>
>> Yes, Vince, I took as you said me.
>>
>>  $ getent group gpio
>> gpio:x:997:pi,weewx
>>
>> but it is always the same things, this error come , only when I restart 
>> weewx. !!!
>>
>> patrick
>> Le 06/03/2024 à 22:15, vince a écrit :
>>
>> patrick - as I said earlier, 
>> " /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
>> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>> software (error was: [Errno 13] Permission non accordée)" clearly indicates 
>> a permission issue. 
>>
>> add the weewx user to group gpio.  Really.
>>
>> On Wednesday, March 6, 2024 at 1:12:57 PM UTC-8 salinois wrote:
>>
>>> yes, I took that.
>>>
>>> ls -ail /etc/weewx/bin/user/
>>> total 36
>>> 526359 drwxrwsr-x 3 weewx weewx  4096  6 mars  21:52 .
>>>
>>>
>>> 526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
>>> 524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05 byows.py
>>> 526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15 extensions.py
>>> 526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15 __init__.py
>>>
>>> 655698 drwxr-sr-x 2 weewx weewx  4096  6 mars  21:54 __pycache__
>>> 524317 -rw-r--r-- 1 piweewx  4052  6 mars  21:52 stats.py
>>>
>>> This is again better.
>>>
>>> [Mar  6 21:57:13 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>>> value: 0.0
>>> Mar  6 21:57:15 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>>> value: 0.0
>>> Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
>>> record 2024-03-06 21:57:00 CET (1709758620) to database 'weewx.sdb'
>>> Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
>>> record 2024-03-06 21:57:00 CET (1709758620) to daily summary in 'weewx.sdb'
>>> Mar  6 21:57:16 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>>> value: 0.0
>>> Mar  6 21:57:17 raspberrypi weewxd[31835]: INFO weewx.cheetahgenerator: 
>>> Generated 8 files for report SeasonsReport in 1.26 seconds
>>> Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.imagegenerator: 
>>> Generated 15 images for report SeasonsReport in 0.65 seconds
>>> Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.reportengine: 
>>> Copied 0 files to /var/www/html/weewx
>>> Mar  6 21:57:18 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>>> value: 0.0]
>>>
>>> Weird, I don't use statistics in my driver !!!
>>>
>>> but I had just an error When I restart weewx 
>>>
>>> Mar  6 22:05:16 raspberrypi weewxd[32027]: 
>>> /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
>>> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>>> software (error was: [Errno 13] Permission non accordée)
>>> Mar  6 22:05:16 raspberrypi weewxd[32027]: 
>>>
>>>   warnings.warn(
>>>
>>> My command that say "OK"
>>>
>>>  sudo pip3 install gpiozero
>>> Looking in indexes: https://pypi.org/simple, 
>>> https://www.piwheels.org/simple
>>> Requirement already satisfied: gpiozero in 
>>> /usr/lib/python3/dist-packages (1.6.2)
>>>
>>>
>>> patrick
>>>
>>>
>>> Le 06/03/2024 à 21:43, Tom Keffer a écrit :
>>>
>>> You are missing a search list extension called "stats". I suspect that 
>>> this is the old stats module that came with WeeWX until v4.6. 
>>>
>>> If that's the case, I've attached it. Put it in /etc/weewx/bin/user
>>>
>>> If it came from somewhere else, I have no idea what it is. Or, perhaps 
>>> you don't use it at all.
>>>
>>> On Wed, Mar 6, 2024 at 12:32 PM salinois  wrote:
>>>
 OK, I took that, thanks.

 but I use this command:

 # Reconfigure to use your hardware*weectl station reconfigure

 *watch:

 [weectl station reconfigure
 Using configuration file /etc/weewx/weewx.conf
 Processing configuration file /etc/weewx/weewx.conf

 Give a description of the station. This will be used for the title of 
 reports.
 description [Loulle,

Re: [weewx-user] Re: new install weewx on a new RPi 4b

I understand that you say me, but why I don't have this issue with 
version weewx 4.9 ?


the only difference is RPi 3b and now RPi 4b with bulleyes.

Weewx 4.9 on RPi 3b with Buster

Weewx 5.0.2 on RPi 4b with bulleyes "error"

I am watching the link "robotics"

Patrick



Le 06/03/2024 à 22:31, vince a écrit :
You need to work through googling your exact error message. 
"SPISoftwareFallback: failed to initialize hardware SPI, falling back 
to software (error was: [Errno 13] Permission"


See if https://roboticsbackend.com/raspberry-pi-hardware-permissions/ 
helps any.   It might be group 'spi' that you need to add the user to.


Rather than changing things randomly please read the link end to end 
to understand it.



On Wednesday, March 6, 2024 at 1:25:20 PM UTC-8 salinois wrote:

Yes, Vince, I took as you said me.

 $ getent group gpio
gpio:x:997:pi,weewx

but it is always the same things, this error come , only when I
restart weewx. !!!

patrick

Le 06/03/2024 à 22:15, vince a écrit :

patrick - as I said earlier,
" /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153:
SPISoftwareFallback: failed to initialize hardware SPI, falling
back to software (error was: [Errno 13] Permission non accordée)"
clearly indicates a permission issue.

add the weewx user to group gpio.  Really.

On Wednesday, March 6, 2024 at 1:12:57 PM UTC-8 salinois wrote:

yes, I took that.

ls -ail /etc/weewx/bin/user/
total 36
526359 drwxrwsr-x 3 weewx weewx  4096  6 mars 21:52 .


526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05 byows.py
526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15
extensions.py
526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15 __init__.py

655698 drwxr-sr-x 2 weewx weewx  4096  6 mars 21:54 __pycache__
524317 -rw-r--r-- 1 pi    weewx  4052  6 mars 21:52 stats.py

This is again better.

[Mar  6 21:57:13 raspberrypi weewxd.py: BYOWS RPi: Unknown
Wind Vane value: 0.0
Mar  6 21:57:15 raspberrypi weewxd.py: BYOWS RPi: Unknown
Wind Vane value: 0.0
Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO
weewx.manager: Added record 2024-03-06 21:57:00 CET
(1709758620) to database 'weewx.sdb'
Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO
weewx.manager: Added record 2024-03-06 21:57:00 CET
(1709758620) to daily summary in 'weewx.sdb'
Mar  6 21:57:16 raspberrypi weewxd.py: BYOWS RPi: Unknown
Wind Vane value: 0.0
Mar  6 21:57:17 raspberrypi weewxd[31835]: INFO
weewx.cheetahgenerator: Generated 8 files for report
SeasonsReport in 1.26 seconds
Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO
weewx.imagegenerator: Generated 15 images for report
SeasonsReport in 0.65 seconds
Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO
weewx.reportengine: Copied 0 files to /var/www/html/weewx
Mar  6 21:57:18 raspberrypi weewxd.py: BYOWS RPi: Unknown
Wind Vane value: 0.0]

Weird, I don't use statistics in my driver !!!

but I had just an error When I restart weewx

Mar  6 22:05:16 raspberrypi weewxd[32027]:
/usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153:
SPISoftwareFallback: failed to initialize hardware SPI,
falling back to software (error was: [Errno 13] Permission
non accordée)
Mar  6 22:05:16 raspberrypi weewxd[32027]:

  warnings.warn(

My command that say "OK"

 sudo pip3 install gpiozero
Looking in indexes: https://pypi.org/simple,
https://www.piwheels.org/simple
Requirement already satisfied: gpiozero in
/usr/lib/python3/dist-packages (1.6.2)


patrick


Le 06/03/2024 à 21:43, Tom Keffer a écrit :

You are missing a search list extension called "stats". I
suspect that this is the old stats module that came with
WeeWX until v4.6.

If that's the case, I've attached it. Put it in
/etc/weewx/bin/user

If it came from somewhere else, I have no idea what it is.
Or, perhaps you don't use it at all.

On Wed, Mar 6, 2024 at 12:32 PM salinois 
wrote:

OK, I took that, thanks.

but I use this command:

|# Reconfigure to use your hardware
*weectlstationreconfigure *watch: [weectl station
reconfigure Using configuration file
/etc/weewx/weewx.conf Processing configuration file
/etc/weewx/weewx.conf Give a description of the station.
This will be used for the title of reports. description
[Loulle, Jura (France)]: Specify altitude, with units
'foot' or 'meter'. For example: 35, foot 12, meter
altitude [700, meter]:

Re: [weewx-user] Re: new install weewx on a new RPi 4b

You need to work through googling your exact error message. 
"SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
software (error was: [Errno 13] Permission"

See if https://roboticsbackend.com/raspberry-pi-hardware-permissions/ helps 
any.   It might be group 'spi' that you need to add the user to.

Rather than changing things randomly please read the link end to end to 
understand it.


On Wednesday, March 6, 2024 at 1:25:20 PM UTC-8 salinois wrote:

> Yes, Vince, I took as you said me.
>
>  $ getent group gpio
> gpio:x:997:pi,weewx
>
> but it is always the same things, this error come , only when I restart 
> weewx. !!!
>
> patrick
> Le 06/03/2024 à 22:15, vince a écrit :
>
> patrick - as I said earlier, 
> " /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
> software (error was: [Errno 13] Permission non accordée)" clearly indicates 
> a permission issue. 
>
> add the weewx user to group gpio.  Really.
>
> On Wednesday, March 6, 2024 at 1:12:57 PM UTC-8 salinois wrote:
>
>> yes, I took that.
>>
>> ls -ail /etc/weewx/bin/user/
>> total 36
>> 526359 drwxrwsr-x 3 weewx weewx  4096  6 mars  21:52 .
>>
>>
>> 526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
>> 524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05 byows.py
>> 526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15 extensions.py
>> 526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15 __init__.py
>>
>> 655698 drwxr-sr-x 2 weewx weewx  4096  6 mars  21:54 __pycache__
>> 524317 -rw-r--r-- 1 piweewx  4052  6 mars  21:52 stats.py
>>
>> This is again better.
>>
>> [Mar  6 21:57:13 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>> value: 0.0
>> Mar  6 21:57:15 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>> value: 0.0
>> Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
>> record 2024-03-06 21:57:00 CET (1709758620) to database 'weewx.sdb'
>> Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
>> record 2024-03-06 21:57:00 CET (1709758620) to daily summary in 'weewx.sdb'
>> Mar  6 21:57:16 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>> value: 0.0
>> Mar  6 21:57:17 raspberrypi weewxd[31835]: INFO weewx.cheetahgenerator: 
>> Generated 8 files for report SeasonsReport in 1.26 seconds
>> Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.imagegenerator: 
>> Generated 15 images for report SeasonsReport in 0.65 seconds
>> Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.reportengine: 
>> Copied 0 files to /var/www/html/weewx
>> Mar  6 21:57:18 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
>> value: 0.0]
>>
>> Weird, I don't use statistics in my driver !!!
>>
>> but I had just an error When I restart weewx 
>>
>> Mar  6 22:05:16 raspberrypi weewxd[32027]: 
>> /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
>> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
>> software (error was: [Errno 13] Permission non accordée)
>> Mar  6 22:05:16 raspberrypi weewxd[32027]: 
>>
>>   warnings.warn(
>>
>> My command that say "OK"
>>
>>  sudo pip3 install gpiozero
>> Looking in indexes: https://pypi.org/simple, 
>> https://www.piwheels.org/simple
>> Requirement already satisfied: gpiozero in /usr/lib/python3/dist-packages 
>> (1.6.2)
>>
>>
>> patrick
>>
>>
>> Le 06/03/2024 à 21:43, Tom Keffer a écrit :
>>
>> You are missing a search list extension called "stats". I suspect that 
>> this is the old stats module that came with WeeWX until v4.6. 
>>
>> If that's the case, I've attached it. Put it in /etc/weewx/bin/user
>>
>> If it came from somewhere else, I have no idea what it is. Or, perhaps 
>> you don't use it at all.
>>
>> On Wed, Mar 6, 2024 at 12:32 PM salinois  wrote:
>>
>>> OK, I took that, thanks.
>>>
>>> but I use this command:
>>>
>>> # Reconfigure to use your hardware*weectl station reconfigure
>>>
>>> *watch:
>>>
>>> [weectl station reconfigure
>>> Using configuration file /etc/weewx/weewx.conf
>>> Processing configuration file /etc/weewx/weewx.conf
>>>
>>> Give a description of the station. This will be used for the title of 
>>> reports.
>>> description [Loulle, Jura (France)]:
>>>
>>> Specify altitude, with units 'foot' or 'meter'.  For example:
>>>   35, foot
>>>   12, meter
>>> altitude [700, meter]:
>>>
>>> Specify latitude in decimal degrees, negative for south.
>>> latitude [46.2539]:
>>> Specify longitude in decimal degrees, negative for west.
>>> longitude [5.3168]:
>>>
>>> Choose a unit system for the reports. Later, you can modify
>>> your choice, or choose a combination of units. Unit systems
>>> include:
>>>   us (ºF, inHg, in, mph)
>>>   metricwx   (ºC, mbar, mm, m/s)
>>>   metric (ºC, mbar, cm, km/h)
>>> unit system [us]:
>>>
>>> Choose a driver. Installed drivers include:
>>>   0) BYOWS   (user.byows)
>>>   1) AcuRite (weewx.drivers.acurite)
>>>   2) BYOWS   (weewx.drivers.byows)
>>>   3)

Re: [weewx-user] Re: new install weewx on a new RPi 4b


Yes, Vince, I took as you said me.

 $ getent group gpio
gpio:x:997:pi,weewx

but it is always the same things, this error come , only when I restart 
weewx. !!!


patrick

Le 06/03/2024 à 22:15, vince a écrit :
patrick - as I said earlier, 
" /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
SPISoftwareFallback: failed to initialize hardware SPI, falling back 
to software (error was: [Errno 13] Permission non accordée)" clearly 
indicates a permission issue.


add the weewx user to group gpio.  Really.

On Wednesday, March 6, 2024 at 1:12:57 PM UTC-8 salinois wrote:

yes, I took that.

ls -ail /etc/weewx/bin/user/
total 36
526359 drwxrwsr-x 3 weewx weewx  4096  6 mars  21:52 .


526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05 byows.py
526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15 extensions.py
526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15 __init__.py

655698 drwxr-sr-x 2 weewx weewx  4096  6 mars  21:54 __pycache__
524317 -rw-r--r-- 1 pi    weewx  4052  6 mars  21:52 stats.py

This is again better.

[Mar  6 21:57:13 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind
Vane value: 0.0
Mar  6 21:57:15 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind
Vane value: 0.0
Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager:
Added record 2024-03-06 21:57:00 CET (1709758620) to database
'weewx.sdb'
Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager:
Added record 2024-03-06 21:57:00 CET (1709758620) to daily summary
in 'weewx.sdb'
Mar  6 21:57:16 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind
Vane value: 0.0
Mar  6 21:57:17 raspberrypi weewxd[31835]: INFO
weewx.cheetahgenerator: Generated 8 files for report SeasonsReport
in 1.26 seconds
Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO
weewx.imagegenerator: Generated 15 images for report SeasonsReport
in 0.65 seconds
Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO
weewx.reportengine: Copied 0 files to /var/www/html/weewx
Mar  6 21:57:18 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind
Vane value: 0.0]

Weird, I don't use statistics in my driver !!!

but I had just an error When I restart weewx

Mar  6 22:05:16 raspberrypi weewxd[32027]:
/usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153:
SPISoftwareFallback: failed to initialize hardware SPI, falling
back to software (error was: [Errno 13] Permission non accordée)
Mar  6 22:05:16 raspberrypi weewxd[32027]:

  warnings.warn(

My command that say "OK"

 sudo pip3 install gpiozero
Looking in indexes: https://pypi.org/simple,
https://www.piwheels.org/simple
Requirement already satisfied: gpiozero in
/usr/lib/python3/dist-packages (1.6.2)


patrick


Le 06/03/2024 à 21:43, Tom Keffer a écrit :

You are missing a search list extension called "stats". I suspect
that this is the old stats module that came with WeeWX until v4.6.

If that's the case, I've attached it. Put it in /etc/weewx/bin/user

If it came from somewhere else, I have no idea what it is. Or,
perhaps you don't use it at all.

On Wed, Mar 6, 2024 at 12:32 PM salinois  wrote:

OK, I took that, thanks.

but I use this command:

|# Reconfigure to use your hardware *weectlstationreconfigure
*watch: [weectl station reconfigure Using configuration file
/etc/weewx/weewx.conf Processing configuration file
/etc/weewx/weewx.conf Give a description of the station. This
will be used for the title of reports. description [Loulle,
Jura (France)]: Specify altitude, with units 'foot' or
'meter'. For example: 35, foot 12, meter altitude [700,
meter]: Specify latitude in decimal degrees, negative for
south. latitude [46.2539]: Specify longitude in decimal
degrees, negative for west. longitude [5.3168]: Choose a unit
system for the reports. Later, you can modify your choice, or
choose a combination of units. Unit systems include: us (ºF,
inHg, in, mph) metricwx (ºC, mbar, mm, m/s) metric (ºC, mbar,
cm, km/h) unit system [us]: Choose a driver. Installed
drivers include: 0) BYOWS (user.byows) 1) AcuRite
(weewx.drivers.acurite) 2) BYOWS (weewx.drivers.byows) 3)
CC3000 (weewx.drivers.cc3000) 4) FineOffsetUSB
(weewx.drivers.fousb) 5) Simulator (weewx.drivers.simulator)
6) TE923 (weewx.drivers.te923) 7) Ultimeter
(weewx.drivers.ultimeter) 8) Vantage (weewx.drivers.vantage)
9) WMR100 (weewx.drivers.wmr100) 10) WMR300
(weewx.drivers.wmr300) 11) WMR9x8 (weewx.drivers.wmr9x8) 12)
WS1 (weewx.drivers.ws1) 13) WS23xx (weewx.drivers.ws23xx) 14)
WS28xx (weewx.drivers.ws28xx) driver: 0 You can register the
station on weewx.com , where it will be

Re: [weewx-user] Re: new install weewx on a new RPi 4b

patrick - as I said earlier, 
" /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
software (error was: [Errno 13] Permission non accordée)" clearly indicates 
a permission issue.

add the weewx user to group gpio.  Really.

On Wednesday, March 6, 2024 at 1:12:57 PM UTC-8 salinois wrote:

> yes, I took that.
>
> ls -ail /etc/weewx/bin/user/
> total 36
> 526359 drwxrwsr-x 3 weewx weewx  4096  6 mars  21:52 .
>
>
> 526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
> 524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05 byows.py
> 526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15 extensions.py
> 526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15 __init__.py
>
> 655698 drwxr-sr-x 2 weewx weewx  4096  6 mars  21:54 __pycache__
> 524317 -rw-r--r-- 1 piweewx  4052  6 mars  21:52 stats.py
>
> This is again better.
>
> [Mar  6 21:57:13 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
> value: 0.0
> Mar  6 21:57:15 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane value: 
> 0.0
> Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
> record 2024-03-06 21:57:00 CET (1709758620) to database 'weewx.sdb'
> Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
> record 2024-03-06 21:57:00 CET (1709758620) to daily summary in 'weewx.sdb'
> Mar  6 21:57:16 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane value: 
> 0.0
> Mar  6 21:57:17 raspberrypi weewxd[31835]: INFO weewx.cheetahgenerator: 
> Generated 8 files for report SeasonsReport in 1.26 seconds
> Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.imagegenerator: 
> Generated 15 images for report SeasonsReport in 0.65 seconds
> Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.reportengine: Copied 
> 0 files to /var/www/html/weewx
> Mar  6 21:57:18 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane value: 
> 0.0]
>
> Weird, I don't use statistics in my driver !!!
>
> but I had just an error When I restart weewx 
>
> Mar  6 22:05:16 raspberrypi weewxd[32027]: 
> /usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
> SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
> software (error was: [Errno 13] Permission non accordée)
> Mar  6 22:05:16 raspberrypi weewxd[32027]: 
>
>   warnings.warn(
>
> My command that say "OK"
>
>  sudo pip3 install gpiozero
> Looking in indexes: https://pypi.org/simple, 
> https://www.piwheels.org/simple
> Requirement already satisfied: gpiozero in /usr/lib/python3/dist-packages 
> (1.6.2)
>
>
> patrick
>
>
> Le 06/03/2024 à 21:43, Tom Keffer a écrit :
>
> You are missing a search list extension called "stats". I suspect that 
> this is the old stats module that came with WeeWX until v4.6. 
>
> If that's the case, I've attached it. Put it in /etc/weewx/bin/user
>
> If it came from somewhere else, I have no idea what it is. Or, perhaps you 
> don't use it at all.
>
> On Wed, Mar 6, 2024 at 12:32 PM salinois  wrote:
>
>> OK, I took that, thanks.
>>
>> but I use this command:
>>
>> # Reconfigure to use your hardware*weectl station reconfigure
>>
>> *watch:
>>
>> [weectl station reconfigure
>> Using configuration file /etc/weewx/weewx.conf
>> Processing configuration file /etc/weewx/weewx.conf
>>
>> Give a description of the station. This will be used for the title of 
>> reports.
>> description [Loulle, Jura (France)]:
>>
>> Specify altitude, with units 'foot' or 'meter'.  For example:
>>   35, foot
>>   12, meter
>> altitude [700, meter]:
>>
>> Specify latitude in decimal degrees, negative for south.
>> latitude [46.2539]:
>> Specify longitude in decimal degrees, negative for west.
>> longitude [5.3168]:
>>
>> Choose a unit system for the reports. Later, you can modify
>> your choice, or choose a combination of units. Unit systems
>> include:
>>   us (ºF, inHg, in, mph)
>>   metricwx   (ºC, mbar, mm, m/s)
>>   metric (ºC, mbar, cm, km/h)
>> unit system [us]:
>>
>> Choose a driver. Installed drivers include:
>>   0) BYOWS   (user.byows)
>>   1) AcuRite (weewx.drivers.acurite)
>>   2) BYOWS   (weewx.drivers.byows)
>>   3) CC3000  (weewx.drivers.cc3000)
>>   4) FineOffsetUSB   (weewx.drivers.fousb)
>>   5) Simulator   (weewx.drivers.simulator)
>>   6) TE923   (weewx.drivers.te923)
>>   7) Ultimeter   (weewx.drivers.ultimeter)
>>   8) Vantage (weewx.drivers.vantage)
>>   9) WMR100  (weewx.drivers.wmr100)
>>  10) WMR300  (weewx.drivers.wmr300)
>>  11) WMR9x8  (weewx.drivers.wmr9x8)
>>  12) WS1 (weewx.drivers.ws1)
>>  13) WS23xx  (weewx.drivers.ws23xx)
>>  14) WS28xx  (weewx.drivers.ws28xx)
>> driver: 0
>>
>> You can register the station on weewx.com, where it will be included in a
>> map. If you choose to register, you will also need a unique URL to identify
>> the station (such as a website, or a WeatherUnderground link).
>> register this station (y/n)? [n]
>>

[weewx-user] weewx-sdr howto document available on git hub

In working with another weewx user to help him gets his SDR station online, 
it was clear that lots of people (like me) have some problems really 
understanding some of the rtl-433 and sdr documentation that is out there.

After working through it end-to-end a few times on both ubuntu and on a 
raspberry pi, I wrote up the whole setup as a howto with examples mainly 
for future-me but I thought it might be of general interest.  At worst a 
google search should find it for future folks trying to battle SDR into 
submission :-)

The howto and a small github repo with a patched/enhanced fork of the SDR 
driver is at https://github.com/vinceskahan/sdr-howto if you have interest. 
 Start with the toplevel readme file then read the howto.txt file for how I 
got it working here.

-- 
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/ceae74e5-6194-4c88-b079-603746e2cc7en%40googlegroups.com.

Re: [weewx-user] Re: new install weewx on a new RPi 4b


yes, I took that.

ls -ail /etc/weewx/bin/user/
total 36
526359 drwxrwsr-x 3 weewx weewx  4096  6 mars  21:52 .
526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05 byows.py
526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15 extensions.py
526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15 __init__.py
655698 drwxr-sr-x 2 weewx weewx  4096  6 mars  21:54 __pycache__
524317 -rw-r--r-- 1 pi    weewx  4052  6 mars  21:52 stats.py

This is again better.

[Mar  6 21:57:13 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
value: 0.0
Mar  6 21:57:15 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
value: 0.0
Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
record 2024-03-06 21:57:00 CET (1709758620) to database 'weewx.sdb'
Mar  6 21:57:15 raspberrypi weewxd[31835]: INFO weewx.manager: Added 
record 2024-03-06 21:57:00 CET (1709758620) to daily summary in 'weewx.sdb'
Mar  6 21:57:16 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
value: 0.0
Mar  6 21:57:17 raspberrypi weewxd[31835]: INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 1.26 seconds
Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.imagegenerator: 
Generated 15 images for report SeasonsReport in 0.65 seconds
Mar  6 21:57:18 raspberrypi weewxd[31835]: INFO weewx.reportengine: 
Copied 0 files to /var/www/html/weewx
Mar  6 21:57:18 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane 
value: 0.0]


Weird, I don't use statistics in my driver !!!

but I had just an error When I restart weewx

Mar  6 22:05:16 raspberrypi weewxd[32027]: 
/usr/lib/python3/dist-packages/gpiozero/pins/pi.py:153: 
SPISoftwareFallback: failed to initialize hardware SPI, falling back to 
software (error was: [Errno 13] Permission non accordée)

Mar  6 22:05:16 raspberrypi weewxd[32027]:

  warnings.warn(

My command that say "OK"

 sudo pip3 install gpiozero
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: gpiozero in 
/usr/lib/python3/dist-packages (1.6.2)



patrick


Le 06/03/2024 à 21:43, Tom Keffer a écrit :
You are missing a search list extension called "stats". I suspect that 
this is the old stats module that came with WeeWX until v4.6.


If that's the case, I've attached it. Put it in /etc/weewx/bin/user

If it came from somewhere else, I have no idea what it is. Or, perhaps 
you don't use it at all.


On Wed, Mar 6, 2024 at 12:32 PM salinois  wrote:

OK, I took that, thanks.

but I use this command:

|# Reconfigure to use your hardware *weectlstationreconfigure
*watch: [weectl station reconfigure Using configuration file
/etc/weewx/weewx.conf Processing configuration file
/etc/weewx/weewx.conf Give a description of the station. This will
be used for the title of reports. description [Loulle, Jura
(France)]: Specify altitude, with units 'foot' or 'meter'. For
example: 35, foot 12, meter altitude [700, meter]: Specify
latitude in decimal degrees, negative for south. latitude
[46.2539]: Specify longitude in decimal degrees, negative for
west. longitude [5.3168]: Choose a unit system for the reports.
Later, you can modify your choice, or choose a combination of
units. Unit systems include: us (ºF, inHg, in, mph) metricwx (ºC,
mbar, mm, m/s) metric (ºC, mbar, cm, km/h) unit system [us]:
Choose a driver. Installed drivers include: 0) BYOWS (user.byows)
1) AcuRite (weewx.drivers.acurite) 2) BYOWS (weewx.drivers.byows)
3) CC3000 (weewx.drivers.cc3000) 4) FineOffsetUSB
(weewx.drivers.fousb) 5) Simulator (weewx.drivers.simulator) 6)
TE923 (weewx.drivers.te923) 7) Ultimeter (weewx.drivers.ultimeter)
8) Vantage (weewx.drivers.vantage) 9) WMR100
(weewx.drivers.wmr100) 10) WMR300 (weewx.drivers.wmr300) 11)
WMR9x8 (weewx.drivers.wmr9x8) 12) WS1 (weewx.drivers.ws1) 13)
WS23xx (weewx.drivers.ws23xx) 14) WS28xx (weewx.drivers.ws28xx)
driver: 0 You can register the station on weewx.com
, where it will be included in a map. If you
choose to register, you will also need a unique URL to identify
the station (such as a website, or a WeatherUnderground link).
register this station (y/n)? [n] Saving configuration file
/etc/weewx/weewx.conf Saved old configuration file as
/etc/weewx/weewx.conf.20240306210700] And this is better. sudo
systemctl restart weewx.service pi@raspberrypi:~/Documents $ sudo
systemctl status weewx.service ● weewx.service - WeeWX Loaded:
loaded (/lib/systemd/system/weewx.service; enabled; vendor preset:
enabled) Active: active (running) since Wed 2024-03-06 21:07:54
CET; 2s ago Docs: https://weewx.com/docs Main PID: 30869 (python3)
Tasks: 4 (limit: 4915) CPU: 577ms CGroup:
/system.slice/weewx.service └─30869 python3
/usr/share/weewx/weewxd.py /etc/weewx/weewx.conf mars 06 21:07:54
raspberrypi weewxd[30869]: INFO

Re: [weewx-user] Re: new install weewx on a new RPi 4b

You are missing a search list extension called "stats". I suspect that this
is the old stats module that came with WeeWX until v4.6.

If that's the case, I've attached it. Put it in /etc/weewx/bin/user

If it came from somewhere else, I have no idea what it is. Or, perhaps you
don't use it at all.

On Wed, Mar 6, 2024 at 12:32 PM salinois  wrote:

> OK, I took that, thanks.
>
> but I use this command:
>
> # Reconfigure to use your hardware*weectl station reconfigure
>
> *watch:
>
> [weectl station reconfigure
> Using configuration file /etc/weewx/weewx.conf
> Processing configuration file /etc/weewx/weewx.conf
>
> Give a description of the station. This will be used for the title of reports.
> description [Loulle, Jura (France)]:
>
> Specify altitude, with units 'foot' or 'meter'.  For example:
>   35, foot
>   12, meter
> altitude [700, meter]:
>
> Specify latitude in decimal degrees, negative for south.
> latitude [46.2539]:
> Specify longitude in decimal degrees, negative for west.
> longitude [5.3168]:
>
> Choose a unit system for the reports. Later, you can modify
> your choice, or choose a combination of units. Unit systems
> include:
>   us (ºF, inHg, in, mph)
>   metricwx   (ºC, mbar, mm, m/s)
>   metric (ºC, mbar, cm, km/h)
> unit system [us]:
>
> Choose a driver. Installed drivers include:
>   0) BYOWS   (user.byows)
>   1) AcuRite (weewx.drivers.acurite)
>   2) BYOWS   (weewx.drivers.byows)
>   3) CC3000  (weewx.drivers.cc3000)
>   4) FineOffsetUSB   (weewx.drivers.fousb)
>   5) Simulator   (weewx.drivers.simulator)
>   6) TE923   (weewx.drivers.te923)
>   7) Ultimeter   (weewx.drivers.ultimeter)
>   8) Vantage (weewx.drivers.vantage)
>   9) WMR100  (weewx.drivers.wmr100)
>  10) WMR300  (weewx.drivers.wmr300)
>  11) WMR9x8  (weewx.drivers.wmr9x8)
>  12) WS1 (weewx.drivers.ws1)
>  13) WS23xx  (weewx.drivers.ws23xx)
>  14) WS28xx  (weewx.drivers.ws28xx)
> driver: 0
>
> You can register the station on weewx.com, where it will be included in a
> map. If you choose to register, you will also need a unique URL to identify
> the station (such as a website, or a WeatherUnderground link).
> register this station (y/n)? [n]
> Saving configuration file /etc/weewx/weewx.conf
> Saved old configuration file as /etc/weewx/weewx.conf.20240306210700]
>
> And this is better.
>
> sudo systemctl restart weewx.service
> pi@raspberrypi:~/Documents $ sudo systemctl status weewx.service
> ● weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
> preset: enabled)
>  Active: active (running) since Wed 2024-03-06 21:07:54 CET; 2s ago
>Docs: https://weewx.com/docs
>Main PID: 30869 (python3)
>   Tasks: 4 (limit: 4915)
> CPU: 577ms
>  CGroup: /system.slice/weewx.service
>  └─30869 python3 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>
> mars 06 21:07:54 raspberrypi weewxd[30869]: INFO weewx.restx: CWOP: Posting 
> not enabled.
> mars 06 21:07:54 raspberrypi weewxd[30869]: INFO weewx.restx: WOW: Posting 
> not enabled.
> mars 06 21:07:54 raspberrypi weewxd[30869]: INFO weewx.restx: AWEKAS: Posting 
> not enabled.
> mars 06 21:07:54 raspberrypi weewxd[30869]: INFO weewx.engine: 'pyephem' 
> detected, extended almanac data is available
> mars 06 21:07:54 raspberrypi weewxd[30869]: INFO __main__: Starting up weewx 
> version 5.0.2
> mars 06 21:07:54 raspberrypi weewxd[30869]: INFO weewx.engine: Using binding 
> 'wx_binding' to database 'weewx.sdb'
> mars 06 21:07:54 raspberrypi weewxd[30869]: INFO weewx.manager: Starting 
> backfill of daily summaries
> mars 06 21:07:54 raspberrypi weewxd[30869]: INFO weewx.manager: Daily 
> summaries up to date
> mars 06 21:07:54 raspberrypi weewxd[30869]: INFO weewx.engine: Starting main 
> packet loop.
> mars 06 21:07:54 raspberrypi weewxd.py[30869]: BYOWS RPi: Unknown Wind Vane 
> value: 0.0
> but I have again these ERRORS !!!
>
> [Mar  6 21:30:16 raspberrypi weewxd[31170]: INFO weewx.manager: Added record 
> 2024-03-06 21:30:00 CET (1709757000) to database 'weewx.sdb'
> Mar  6 21:30:16 raspberrypi weewxd[31170]: INFO weewx.manager: Added record 
> 2024-03-06 21:30:00 CET (1709757000) to daily summary in 'weewx.sdb'
> Mar  6 21:30:16 raspberrypi weewxd.py: BYOWS RPi: Unknown Wind Vane value: 0.0
> Mar  6 21:30:17 raspberrypi weewxd[31170]: INFO weewx.cheetahgenerator: 
> Generated 8 files for report SeasonsReport in 1.26 seconds
> Mar  6 21:30:18 raspberrypi weewxd[31170]: INFO weewx.imagegenerator: 
> Generated 15 images for report SeasonsReport in 0.69 seconds
> Mar  6 21:30:18 raspberrypi weewxd[31170]: INFO weewx.reportengine: Copied 0 
> files to /var/www/html/weewx
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine: Caught 
> unrecoverable exception in generator 'weewx.cheetahgenerator.CheetahGenerator'
> Mar  6 21:30:18 raspberrypi weewxd[31170]: ERROR

[weewx-user] Re: Raddy L7 Weather Station: XML of Current Conditions-How to Feed WeeWx?

You have some pretty hideously formatted JSON to parse, but here's what it 
looks like in a more readable format after piping it through 'jq' and doing 
a little hand editing for readability

{
  "sensor": [
{
  "title": "Indoor",
  "list": [
[ "Temperature", "68.9", "Â°F" ],
[ "Humidity", "38", "%" ] ]
},
{
  "title": "Outdoor",
  "list": [
[ "Temperature", "61.7", "Â°F" ],
[ "Humidity", "29", "%" ] ]
},
{
  "title": "Pressure", "list": [
[ "Absolute", "26.76", "inhg" ],
[ "Relative", "29.84", "inhg" ] ]
},
{
  "title": "Wind Speed",
  "list": [
[ "Max Daily Gust", "5.1", "mph" ],
[ "Wind", "1.1", "mph" ],
[ "Gust", "1.6", "mph" ],
[ "Direction", "123", "Â°" ],
[ "Wind Average 2 Minute", "0.4", "mph" ],
[ "Direction Average 2 Minute", "111", "Â°" ],
[ "Wind Average 10 Minute", "1.3", "mph" ],
[ "Direction Average 10 Minute", "134", "Â°" ]
  ]
},
{
  "title": "Rainfall",
  "list": [
[ "Rate", "0.0", "inch/hr" ],
[ "Hour", "0.0", "inch", "43" ],
[ "Day", "0.0", "inch", "44" ],
[ "Week", "0.0", "inch", "45" ],
[ "Month", "0.0", "inch", "46" ],
[ "Year", "5.72", "inch", "47" ],
[ "Total", "10.65", "inch", "48" ]
  ],
  "range": "Range: 0inch to 393.7inch."
},
{
  "title": "Solar",
  "list": [
[ "Light", "261.36", "w/mÂ²" ],
[ "UVI", "1.2", "" ]
  ]
}
  ],
  "battery": {
"title": "Battery",
"list": [ "All battery are ok" ]
  }
}


On Wednesday, March 6, 2024 at 11:59:36 AM UTC-8 Michael wrote:

> I have officially given up on getting interceptor to work in sniffing mode 
> on Phython3.  
>
> On Wednesday, March 6, 2024 at 11:17:39 AM UTC-7 matthew wall wrote:
>
>> it looks like the raddy L7 can upload to wundgerground, so if you are 
>> using the raddy's wifi, you should be able to use the interceptor driver to 
>> capture or directly receive the wunderground output.  setting up the 
>> interceptor is not trivial, but there are many examples.
>>
>> it would be nice if there were a generic json driver, analogous to the 
>> fileparse driver.  but the json structure varies a lot from one device to 
>> another, and the mechanism for obtaining that json output also varies.  for 
>> example, the tempest broadcasts json data, whereas the ruddy emits json as 
>> a response to http request.  so i understand why no one has written one yet.
>>
>> 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/421d1ce1-9dcf-4148-827d-b97c92a4495cn%40googlegroups.com.

Re: [weewx-user] Re: new install weewx on a new RPi 4b


OK, I took that, thanks.

but I use this command:

|# Reconfigure to use your hardware *weectlstationreconfigure *watch: 
[weectl station reconfigure Using configuration file 
/etc/weewx/weewx.conf Processing configuration file 
/etc/weewx/weewx.conf Give a description of the station. This will be 
used for the title of reports. description [Loulle, Jura (France)]: 
Specify altitude, with units 'foot' or 'meter'. For example: 35, foot 
12, meter altitude [700, meter]: Specify latitude in decimal degrees, 
negative for south. latitude [46.2539]: Specify longitude in decimal 
degrees, negative for west. longitude [5.3168]: Choose a unit system for 
the reports. Later, you can modify your choice, or choose a combination 
of units. Unit systems include: us (ºF, inHg, in, mph) metricwx (ºC, 
mbar, mm, m/s) metric (ºC, mbar, cm, km/h) unit system [us]: Choose a 
driver. Installed drivers include: 0) BYOWS (user.byows) 1) AcuRite 
(weewx.drivers.acurite) 2) BYOWS (weewx.drivers.byows) 3) CC3000 
(weewx.drivers.cc3000) 4) FineOffsetUSB (weewx.drivers.fousb) 5) 
Simulator (weewx.drivers.simulator) 6) TE923 (weewx.drivers.te923) 7) 
Ultimeter (weewx.drivers.ultimeter) 8) Vantage (weewx.drivers.vantage) 
9) WMR100 (weewx.drivers.wmr100) 10) WMR300 (weewx.drivers.wmr300) 11) 
WMR9x8 (weewx.drivers.wmr9x8) 12) WS1 (weewx.drivers.ws1) 13) WS23xx 
(weewx.drivers.ws23xx) 14) WS28xx (weewx.drivers.ws28xx) driver: 0 You 
can register the station on weewx.com, where it will be included in a 
map. If you choose to register, you will also need a unique URL to 
identify the station (such as a website, or a WeatherUnderground link). 
register this station (y/n)? [n] Saving configuration file 
/etc/weewx/weewx.conf Saved old configuration file as 
/etc/weewx/weewx.conf.20240306210700] And this is better. sudo systemctl 
restart weewx.service pi@raspberrypi:~/Documents $ sudo systemctl status 
weewx.service ● weewx.service - WeeWX Loaded: loaded 
(/lib/systemd/system/weewx.service; enabled; vendor preset: enabled) 
Active: active (running) since Wed 2024-03-06 21:07:54 CET; 2s ago Docs: 
https://weewx.com/docs Main PID: 30869 (python3) Tasks: 4 (limit: 4915) 
CPU: 577ms CGroup: /system.slice/weewx.service └─30869 python3 
/usr/share/weewx/weewxd.py /etc/weewx/weewx.conf mars 06 21:07:54 
raspberrypi weewxd[30869]: INFO weewx.restx: CWOP: Posting not enabled. 
mars 06 21:07:54 raspberrypi weewxd[30869]: INFO weewx.restx: WOW: 
Posting not enabled. mars 06 21:07:54 raspberrypi weewxd[30869]: INFO 
weewx.restx: AWEKAS: Posting not enabled. mars 06 21:07:54 raspberrypi 
weewxd[30869]: INFO weewx.engine: 'pyephem' detected, extended almanac 
data is available mars 06 21:07:54 raspberrypi weewxd[30869]: INFO 
__main__: Starting up weewx version 5.0.2 mars 06 21:07:54 raspberrypi 
weewxd[30869]: INFO weewx.engine: Using binding 'wx_binding' to database 
'weewx.sdb' mars 06 21:07:54 raspberrypi weewxd[30869]: INFO 
weewx.manager: Starting backfill of daily summaries mars 06 21:07:54 
raspberrypi weewxd[30869]: INFO weewx.manager: Daily summaries up to 
date mars 06 21:07:54 raspberrypi weewxd[30869]: INFO weewx.engine: 
Starting main packet loop. mars 06 21:07:54 raspberrypi 
weewxd.py[30869]: BYOWS RPi: Unknown Wind Vane value: 0.0 but I have 
again these ERRORS !!! [Mar 6 21:30:16 raspberrypi weewxd[31170]: INFO 
weewx.manager: Added record 2024-03-06 21:30:00 CET (1709757000) to 
database 'weewx.sdb' Mar 6 21:30:16 raspberrypi weewxd[31170]: INFO 
weewx.manager: Added record 2024-03-06 21:30:00 CET (1709757000) to 
daily summary in 'weewx.sdb' Mar 6 21:30:16 raspberrypi weewxd.py: BYOWS 
RPi: Unknown Wind Vane value: 0.0 Mar 6 21:30:17 raspberrypi 
weewxd[31170]: INFO weewx.cheetahgenerator: Generated 8 files for report 
SeasonsReport in 1.26 seconds Mar 6 21:30:18 raspberrypi weewxd[31170]: 
INFO weewx.imagegenerator: Generated 15 images for report SeasonsReport 
in 0.69 seconds Mar 6 21:30:18 raspberrypi weewxd[31170]: INFO 
weewx.reportengine: Copied 0 files to /var/www/html/weewx Mar 6 21:30:18 
raspberrypi weewxd[31170]: ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 
'weewx.cheetahgenerator.CheetahGenerator' Mar 6 21:30:18 raspberrypi 
weewxd[31170]: ERROR weewx.reportengine:  No module named 
'user.stats' Mar 6 21:30:18 raspberrypi weewxd[31170]: ERROR 
weewx.reportengine:  Traceback (most recent call last): Mar 6 
21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine:  File 
"/usr/share/weewx/weewx/reportengine.py", line 220, in run Mar 6 
21:30:18 raspberrypi weewxd[31170]: ERROR weewx.reportengine:  
obj.start() Mar 6 21:30:18 raspberrypi weewxd[31170]: ERROR 
weewx.reportengine:  File "/usr/share/weewx/weewx/reportengine.py", 
line 409, in start Mar 6 21:30:18 raspberrypi weewxd[31170]: ERROR 
weewx.reportengine:  self.run() Mar 6 21:30:18 raspberrypi 
weewxd[31170]: ERROR weewx.reportengine:  File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 163, in run Mar

Re: [weewx-user] Re: new install weewx on a new RPi 4b

It should be

driver = user.byows

On Wed, Mar 6, 2024 at 11:29 AM salinois  wrote:

> ok Tom,
>
> this is a fresh install, not upgrade, but When I put my other sd card with
> 4.9 version, it is ok, so, it is not a issue with GPIO, I think.
>
> And yes, the driver is here:
>
> [ls -ail /etc/weewx/bin/user/
> total 32
> 526359 drwxrwsr-x 3 weewx weewx  4096  6 mars  18:32 .
> 526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
> 524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05 byows.py
> 526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15 extensions.py
> 526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15 __init__.py
> 655698 drwxr-sr-x 2 weewx weewx  4096  6 mars  18:32 __pycache__]
>
>
> and the lines for the driver in weewx.conf are:
>
>
> *[Station]*
>
> # Description of the station location, such as your town.
> location = "Loulle, Jura (France)"
>
> # Latitude in decimal degrees. Negative for southern hemisphere.
> latitude = 46.2539
> # Longitude in decimal degrees. Negative for western hemisphere.
> longitude = 5.3168
>
> # Altitude of the station, with the unit it is in. This is used only
> # if the hardware cannot supply a value.
> altitude = 700, 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 = BYOWS*
>
> and next
>
>
>
>
>
> *#
> [BYOWS]* # This section is for the Raspberry Pi Bring Your Own
> Weather Station driver.
>
> # The driver to use
> * driver = byows ===> is it the good syntax ? *in version 4.9 I have
> user.byows
>
> but now, there no more errors:
>
> [ sudo systemctl status weewx.service
> ● weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor
> preset: enabled)
>  Active: failed (Result: exit-code) since Wed 2024-03-06 20:21:34 CET;
> 3s ago
>Docs: https://weewx.com/docs
> Process: 29896 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited,
> status=1/FAILURE)
>Main PID: 29896 (code=exited, status=1/FAILURE)
> CPU: 337ms
>
> mars 06 20:21:34 raspberrypi weewxd[29896]:
> self.setupStation(config_dict)
> mars 06 20:21:34 raspberrypi weewxd[29896]:   File
> "/usr/share/weewx/weewx/engine.py", line 104, in setupStation
> mars 06 20:21:34 raspberrypi weewxd[29896]: __import__(driver)
> mars 06 20:21:34 raspberrypi weewxd[29896]: ModuleNotFoundError: *No
> module named 'byows'*
> mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__: 
> File "/usr/share/weewx/weewx/engine.py", line 104, in setupStation
> mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__:
>   __import__(driver)
> mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__: 
> ModuleNotFoundError: No module named 'byows'
> mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__: 
> Exiting.
> mars 06 20:21:34 raspberrypi systemd[1]: weewx.service: Main process
> exited, code=exited, status=1/FAILURE
> mars 06 20:21:34 raspberrypi systemd[1]: weewx.service: Failed with result
> 'exit-code'.]
>
> Patrick
>
>
>
>
> Le 06/03/2024 à 19:23, Tom Keffer a écrit :
>
> If you did a package install, the driver byows.py should go in
> /etc/weewx/bin/user. But, frankly, this should have been done for you if
> you did an upgrade from V4 to V5. Take a look in /etc/weewx/bin/user and
> see if it's in there.
>
> But, the error in the little snippet from your status report is a
> different one. For some reason, your installation thinks it is not running
> on a Raspberry Pi, so it cannot access the gpio pins. I'm not an expert on
> that, but it may be due to a missing installation package.
>
> On Wed, Mar 6, 2024 at 10:13 AM salinois  wrote:
>
>> again me
>>
>> perhaps , I found
>>
>> Should I use this method now?
>>
>> [weectl extension install /home/pi/byows.py]
>>
>> and after:
>>
>> weectl station reconfigures --no-prompt --driver=weewx.drivers.byows
>>
>>
>> Patrick
>> Le 06/03/2024 à 18:47, salinois a écrit :
>>
>> hello,
>>
>> I restart my installation with version weewx 5.0.1 and I have these
>> errors:
>>
>> on my version which works in 4.10.2, my "byows.py" driver is located
>> here: [/usr/share/weewx/user/] but I saw that the tree structure has
>> changed; where should I put my driver now?
>>
>> watch these errors:
>>
>> sudo systemctl status weewx.service
>> ● weewx.service - WeeWX
>>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor
>> preset: enabled)
>>  Active: failed (Result: exit-code) since Wed 2024-03-06 18:32:05
>> CET; 2s ago
>>Docs: https://weewx.com/docs
>> Process: 11182 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited,
>> status=4)
>>Main PID: 11182 (code=exited, status=4)
>> CPU: 682ms
>>
>> mars 06 18:32:05 raspberrypi

Re: [weewx-user] RSS - FEED

A template file is a not-very-obvious mix of HTML and Cheetah tags. To get
the formatting you need, change this

#for $x in $observations
  #if $getattr($current, $x).has_data
#if $x == 'windSpeed'
$obs.label.wind: $current.windSpeed $gettext("from")
$current.windDir;
#else
$obs.label[$x]: $getattr($current, $x);
#end if
  #end if
#end for

to this

#for $x in $observations
  #if $getattr($current, $x).has_data
#if $x == 'windSpeed'
$obs.label.wind: $current.windSpeed $gettext("from")
$current.windDir;
#else
$obs.label[$x]: $getattr($current, $x);
#end if
  #end if
#end for

The "rain" tag under "Weather Conditions" is the rain that fell during the
last archive period, which is generally only 5-30 minutes. If you want rain
since midnight, you can find that under "Daily summary".







On Wed, Mar 6, 2024 at 7:08 AM Fjordey  wrote:

> I realize not many are using the RSS feed, yet I am to just get a quick
> check of things while sorting through my news feeds... regaurdless the
> reason I need help if possible...
>
> I'm not an expert by any means, but can fumble my way through the coding
> most times.
>
> #1 I edited the template to only provide the current conditions. That
> works.
> #2 I was trying to format the returned data:
>
> Wind: 0 mph from N/A; Rain: 0.00
>
> trying to remove the ";" and put Rain: 0.00 on the next line.. (have not
> figured that out)
>
> #3 I have noticed that my rain total is 0.00 when it should show 0.80 for
> toal rain.
> Note: the rain total and text formating were not working before I edited
> the template.
>
> any help would be apreciated... Hopefully I'm just overlooking something
> simple.
>
> https://weather.3utilities.icu/rss.xml
>
> my current rss.xml.tmpl:
>
> 
>xmlns:content="http://purl.org/rss/1.0/modules/content/;
>   xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#; >
>
> #set $timespans = [{"span": $day, "label": $gettext("Daily summary as
> of")}, {"span": $month, "label": $gettext("Monthly summary as of")},
> {"span": $year, "label": $gettext("Yearly summary as of")}]
>
> #set $observations = $to_list($DisplayOptions.get('observations_rss',
> ['outTemp', 'inTemp', 'barometer', 'windSpeed', 'rain', 'rainRate']))
> #set $obs_type_sum = $to_list($DisplayOptions.get('obs_type_sum',
> ['rain']))
> #set $obs_type_max = $to_list($DisplayOptions.get('obs_type_max',
> ['rainRate']))
>
>   
> $gettext("Weather Conditions") : $station.location
> $station.station_url
> $gettext("Current conditions, and daily, monthly, and
> yearly summaries")
> "$lang"
> $current.dateTime.format("%a, %d %b %Y %H:%M:%S %Z")
>
> $current.dateTime.format("%a, %d %b %Y %H:%M:%S
> %Z")
> http://blogs.law.harvard.edu/tech/rss
> weewx $station.version
> $current.interval.string('')
>
> 
>   $gettext("Weather Conditions at") $current.dateTime
>   $station.station_url
>   
> #for $x in $observations
>   #if $getattr($current, $x).has_data
> #if $x == 'windSpeed'
> $obs.label.wind: $current.windSpeed $gettext("from")
> $current.windDir;
> #else
> $obs.label[$x]: $getattr($current, $x);
> #end if
>   #end if
> #end for
>   
>   $current.dateTime.format("%a, %d %b %Y %H:%M:%S
> %Z")
>   
> 
>
>   
> 
>
> --
> 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/eba24381-6fbf-437b-ad2f-a09fffa01fe0n%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/CAPq0zECOE5RQnbJ8ndHj5AfuFko_9rscmpSrzzziSXqAPa7U3g%40mail.gmail.com.

[weewx-user] Re: Raddy L7 Weather Station: XML of Current Conditions-How to Feed WeeWx?

2024-03-06 Thread Michael

I have officially given up on getting interceptor to work in sniffing mode 
on Phython3.  

On Wednesday, March 6, 2024 at 11:17:39 AM UTC-7 matthew wall wrote:

> it looks like the raddy L7 can upload to wundgerground, so if you are 
> using the raddy's wifi, you should be able to use the interceptor driver to 
> capture or directly receive the wunderground output.  setting up the 
> interceptor is not trivial, but there are many examples.
>
> it would be nice if there were a generic json driver, analogous to the 
> fileparse driver.  but the json structure varies a lot from one device to 
> another, and the mechanism for obtaining that json output also varies.  for 
> example, the tempest broadcasts json data, whereas the ruddy emits json as 
> a response to http request.  so i understand why no one has written one yet.
>
> 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/cf89836d-ec83-4325-9600-6b0630ee68fdn%40googlegroups.com.

Re: [weewx-user] Re: new install weewx on a new RPi 4b


ok Tom,

this is a fresh install, not upgrade, but When I put my other sd card 
with 4.9 version, it is ok, so, it is not a issue with GPIO, I think.


And yes, the driver is here:

[ls -ail /etc/weewx/bin/user/
total 32
526359 drwxrwsr-x 3 weewx weewx  4096  6 mars  18:32 .
526358 drwxrwsr-x 3 weewx weewx  4096  7 févr. 22:15 ..
524298 -rw-r--r-- 1 weewx weewx 10990  8 févr. 13:05 byows.py
526361 -rw-rw-r-- 1 weewx weewx   541  7 févr. 22:15 extensions.py
526360 -rw-rw-r-- 1 weewx weewx   306  7 févr. 22:15 __init__.py
655698 drwxr-sr-x 2 weewx weewx  4096  6 mars  18:32 __pycache__]


and the lines for the driver in weewx.conf are:


*[Station]*

    # Description of the station location, such as your town.
    location = "Loulle, Jura (France)"

    # Latitude in decimal degrees. Negative for southern hemisphere.
    latitude = 46.2539
    # Longitude in decimal degrees. Negative for western hemisphere.
    longitude = 5.3168

    # Altitude of the station, with the unit it is in. This is used only
    # if the hardware cannot supply a value.
    altitude = 700, 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 = BYOWS*

and next*
*

*#


[BYOWS]
* # This section is for the Raspberry Pi Bring Your Own Weather Station 
driver.


    # The driver to use*
    driver = byows ===> is it the good syntax ? *in version 4.9 I have 
user.byows


but now, there no more errors:

[ sudo systemctl status weewx.service
● weewx.service - WeeWX
 Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Wed 2024-03-06 20:21:34 
CET; 3s ago

   Docs: https://weewx.com/docs
    Process: 29896 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
status=1/FAILURE)

   Main PID: 29896 (code=exited, status=1/FAILURE)
    CPU: 337ms

mars 06 20:21:34 raspberrypi weewxd[29896]: self.setupStation(config_dict)
mars 06 20:21:34 raspberrypi weewxd[29896]:   File 
"/usr/share/weewx/weewx/engine.py", line 104, in setupStation

mars 06 20:21:34 raspberrypi weewxd[29896]: __import__(driver)
mars 06 20:21:34 raspberrypi weewxd[29896]: ModuleNotFoundError: *No 
module named 'byows'*
mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__:     
File "/usr/share/weewx/weewx/engine.py", line 104, in setupStation
mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__:   
__import__(driver)
mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__:   
ModuleNotFoundError: No module named 'byows'
mars 06 20:21:34 raspberrypi weewxd[29896]: CRITICAL __main__:   
Exiting.
mars 06 20:21:34 raspberrypi systemd[1]: weewx.service: Main process 
exited, code=exited, status=1/FAILURE
mars 06 20:21:34 raspberrypi systemd[1]: weewx.service: Failed with 
result 'exit-code'.]*

*

Patrick*
*

*
*

*
*


Le 06/03/2024 à 19:23, Tom Keffer a écrit :
If you did a package install, the driver byows.py should go in 
/etc/weewx/bin/user. But, frankly, this should have been done for you 
if you did an upgrade from V4 to V5. Take a look in 
/etc/weewx/bin/user and see if it's in there.


But, the error in the little snippet from your status report is a 
different one. For some reason, your installation thinks it is not 
running on a Raspberry Pi, so it cannot access the gpio pins. I'm not 
an expert on that, but it may be due to a missing installation package.


On Wed, Mar 6, 2024 at 10:13 AM salinois  wrote:

again me

perhaps , I found

Should I use this method now?

[weectl extension install /home/pi/byows.py]

and after:

weectl station reconfigures --no-prompt --driver=weewx.drivers.byows


Patrick

Le 06/03/2024 à 18:47, salinois a écrit :


hello,

I restart my installation with version weewx 5.0.1 and I have
these errors:

on my version which works in 4.10.2, my "byows.py" driver is
located here: [/usr/share/weewx/user/] but I saw that the tree
structure has changed; where should I put my driver now?

watch these errors:

sudo systemctl status weewx.service
● weewx.service - WeeWX
 Loaded: loaded (/lib/systemd/system/weewx.service; enabled;
vendor preset: enabled)
 Active: failed (Result: exit-code) since Wed 2024-03-06
18:32:05 CET; 2s ago
   Docs: https://weewx.com/docs
    Process: 11182 ExecStart=weewxd /etc/weewx/weewx.conf
(code=exited, status=4)
   Main PID: 11182 (code=exited, status=4)
    CPU: 682ms

mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL
weewx.engine:   pin = self.pin_factory.pin(pin)
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL
weewx.engine:     File
"/usr/lib/python3/dist-packages/gpiozero/pins/pi.py", line

Re: [weewx-user] Re: new install weewx on a new RPi 4b

I did find some google links where this message appears due to permission 
problems accessing the hardware. If you look at your error it also says 
NOPERMISSION.  Try adding the user weewx runs as to group gpio via ‘sudo 
usermod -aG gpio weewx’ and see if it works now.

On Wednesday, March 6, 2024 at 10:23:59 AM UTC-8 Tom Keffer wrote:

> If you did a package install, the driver byows.py should go in 
> /etc/weewx/bin/user. But, frankly, this should have been done for you if 
> you did an upgrade from V4 to V5. Take a look in /etc/weewx/bin/user and 
> see if it's in there.
>
> But, the error in the little snippet from your status report is a 
> different one. For some reason, your installation thinks it is not running 
> on a Raspberry Pi, so it cannot access the gpio pins. I'm not an expert on 
> that, but it may be due to a missing installation package. 
>
> On Wed, Mar 6, 2024 at 10:13 AM salinois  wrote:
>
>> again me
>>
>> perhaps , I found
>>
>> Should I use this method now?
>>
>> [weectl extension install /home/pi/byows.py]
>>
>> and after: 
>>
>> weectl station reconfigures --no-prompt --driver=weewx.drivers.byows
>>
>>
>> Patrick
>> Le 06/03/2024 à 18:47, salinois a écrit :
>>
>> hello,
>>
>> I restart my installation with version weewx 5.0.1 and I have these 
>> errors:
>>
>> on my version which works in 4.10.2, my "byows.py" driver is located 
>> here: [/usr/share/weewx/user/] but I saw that the tree structure has 
>> changed; where should I put my driver now?
>>
>> watch these errors:
>>
>> sudo systemctl status weewx.service
>> ● weewx.service - WeeWX
>>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
>> preset: enabled)
>>  Active: failed (Result: exit-code) since Wed 2024-03-06 18:32:05 
>> CET; 2s ago
>>Docs: https://weewx.com/docs
>> Process: 11182 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
>> status=4)
>>Main PID: 11182 (code=exited, status=4)
>> CPU: 682ms
>>
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
>>   pin = self.pin_factory.pin(pin)
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
>> File "/usr/lib/python3/dist-packages/gpiozero/pins/pi.py", line 
>> 103, in pin
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
>>   pin = self.pin_class(self, n)
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
>> File "/usr/lib/python3/dist-packages/gpiozero/pins/rpigpio.py", 
>> line 111, in __init__
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
>>   GPIO.setup(self.number, GPIO.IN, 
>> self.GPIO_PULL_UPS[self._pull])
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
>>   RuntimeError: Not running on a RPi!
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL __main__:* Unable 
>> to load driver: Not running on a RPi!*
>> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL __main__:   
>> Exiting...
>> mars 06 18:32:05 raspberrypi systemd[1]: weewx.service: Main process 
>> exited, code=exited, status=4/NOPERMISSION
>> mars 06 18:32:05 raspberrypi systemd[1]: weewx.service: Failed with 
>> result 'exit-code'.
>>
>> Patrick
>> Le 08/02/2024 à 08:59, salinois a écrit :
>>
>> hello Matthew
>>
>> OK I understand if that works
>>
>> thanks also to vince.
>>
>> Now , I must to try the 5.0.0 version
>>
>> Patrick
>> Le 07/02/2024 à 23:06, matthew wall a écrit :
>>
>> On Wednesday, February 7, 2024 at 3:36:55 PM UTC-5 sali...@gmail.com 
>> wrote: 
>>
>> pi@raspberrypi:~ $ wget -qO - https://weewx.com/apt/weewx-python3.list | 
>> sudo tee /etc/apt/sources.list.d/weewx.list 
>> *deb [arch=all] http://weewx.com/apt/python3 
>>  buster main ==> why Buster*
>>
>>
>> 'buster' (i.e., debian 10) is the oldest release on which the deb package 
>> will install.
>>
>> if you look at the python2 configuration, it uses the label 'squeeze' 
>> (debian 6)
>>
>> the weewx packages are *really* stable with respect to dependencies, so 
>> the same package that works with debian 10 also works with debian 11 and 
>> debian 12.  besides, i am too old and lazy to build a new deb and new apt 
>> repository for every major debian release that comes out :) 
>>  
>> -- 
>> 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/ca7d09e7-acd7-4115-ae62-7ac60a1ef82bn%40googlegroups.com
>>  
>> 
>> .
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this

[weewx-user] Re: Raddy L7 Weather Station: XML of Current Conditions-How to Feed WeeWx?

Something like the purpleair or davis airlink extensions could perhaps be 
modified. Query the endpoint and map it to weewx db elements. Or query 
periodically and feed MQTT.  SHOULD BE DOABLE.

On Wednesday, March 6, 2024 at 10:17:39 AM UTC-8 matthew wall wrote:

> it looks like the raddy L7 can upload to wundgerground, so if you are 
> using the raddy's wifi, you should be able to use the interceptor driver to 
> capture or directly receive the wunderground output.  setting up the 
> interceptor is not trivial, but there are many examples.
>
> it would be nice if there were a generic json driver, analogous to the 
> fileparse driver.  but the json structure varies a lot from one device to 
> another, and the mechanism for obtaining that json output also varies.  for 
> example, the tempest broadcasts json data, whereas the ruddy emits json as 
> a response to http request.  so i understand why no one has written one yet.
>
> 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/7c67d0fb-91c1-477d-9e98-9b580d735eben%40googlegroups.com.

Re: [weewx-user] Re: new install weewx on a new RPi 4b

If you did a package install, the driver byows.py should go in
/etc/weewx/bin/user. But, frankly, this should have been done for you if
you did an upgrade from V4 to V5. Take a look in /etc/weewx/bin/user and
see if it's in there.

But, the error in the little snippet from your status report is a different
one. For some reason, your installation thinks it is not running on a
Raspberry Pi, so it cannot access the gpio pins. I'm not an expert on that,
but it may be due to a missing installation package.

On Wed, Mar 6, 2024 at 10:13 AM salinois  wrote:

> again me
>
> perhaps , I found
>
> Should I use this method now?
>
> [weectl extension install /home/pi/byows.py]
>
> and after:
>
> weectl station reconfigures --no-prompt --driver=weewx.drivers.byows
>
>
> Patrick
> Le 06/03/2024 à 18:47, salinois a écrit :
>
> hello,
>
> I restart my installation with version weewx 5.0.1 and I have these errors:
>
> on my version which works in 4.10.2, my "byows.py" driver is located here:
> [/usr/share/weewx/user/] but I saw that the tree structure has changed; where
> should I put my driver now?
>
> watch these errors:
>
> sudo systemctl status weewx.service
> ● weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor
> preset: enabled)
>  Active: failed (Result: exit-code) since Wed 2024-03-06 18:32:05 CET;
> 2s ago
>Docs: https://weewx.com/docs
> Process: 11182 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited,
> status=4)
>Main PID: 11182 (code=exited, status=4)
> CPU: 682ms
>
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine:
>   pin = self.pin_factory.pin(pin)
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine:
> File "/usr/lib/python3/dist-packages/gpiozero/pins/pi.py", line
> 103, in pin
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine:
>   pin = self.pin_class(self, n)
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine:
> File "/usr/lib/python3/dist-packages/gpiozero/pins/rpigpio.py",
> line 111, in __init__
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine:
>   GPIO.setup(self.number, GPIO.IN, self.GPIO_PULL_UPS[self._pull])
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine:
>   RuntimeError: Not running on a RPi!
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL __main__:* Unable to
> load driver: Not running on a RPi!*
> mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL __main__: 
> Exiting...
> mars 06 18:32:05 raspberrypi systemd[1]: weewx.service: Main process
> exited, code=exited, status=4/NOPERMISSION
> mars 06 18:32:05 raspberrypi systemd[1]: weewx.service: Failed with result
> 'exit-code'.
>
> Patrick
> Le 08/02/2024 à 08:59, salinois a écrit :
>
> hello Matthew
>
> OK I understand if that works
>
> thanks also to vince.
>
> Now , I must to try the 5.0.0 version
>
> Patrick
> Le 07/02/2024 à 23:06, matthew wall a écrit :
>
> On Wednesday, February 7, 2024 at 3:36:55 PM UTC-5 sali...@gmail.com
> wrote:
>
> pi@raspberrypi:~ $ wget -qO - https://weewx.com/apt/weewx-python3.list |
> sudo tee /etc/apt/sources.list.d/weewx.list
> *deb [arch=all] http://weewx.com/apt/python3
>  buster main ==> why Buster*
>
>
> 'buster' (i.e., debian 10) is the oldest release on which the deb package
> will install.
>
> if you look at the python2 configuration, it uses the label 'squeeze'
> (debian 6)
>
> the weewx packages are *really* stable with respect to dependencies, so
> the same package that works with debian 10 also works with debian 11 and
> debian 12.  besides, i am too old and lazy to build a new deb and new apt
> repository for every major debian release that comes out :)
>
> --
> 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/ca7d09e7-acd7-4115-ae62-7ac60a1ef82bn%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/320351a0-1a0a-4474-9c39-de81a0e01011%40gmail.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

[weewx-user] Re: Raddy L7 Weather Station: XML of Current Conditions-How to Feed WeeWx?

2024-03-06 Thread matthew wall

it looks like the raddy L7 can upload to wundgerground, so if you are using 
the raddy's wifi, you should be able to use the interceptor driver to 
capture or directly receive the wunderground output.  setting up the 
interceptor is not trivial, but there are many examples.

it would be nice if there were a generic json driver, analogous to the 
fileparse driver.  but the json structure varies a lot from one device to 
another, and the mechanism for obtaining that json output also varies.  for 
example, the tempest broadcasts json data, whereas the ruddy emits json as 
a response to http request.  so i understand why no one has written one yet.

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/2a762062-0efc-4cc8-b77c-908d78132504n%40googlegroups.com.

Re: [weewx-user] Re: new install weewx on a new RPi 4b


again me

perhaps , I found

Should I use this method now?

[weectl extension install /home/pi/byows.py]

and after:

weectl station reconfigures --no-prompt --driver=weewx.drivers.byows


Patrick

Le 06/03/2024 à 18:47, salinois a écrit :


hello,

I restart my installation with version weewx 5.0.1 and I have these 
errors:


on my version which works in 4.10.2, my "byows.py" driver is located 
here: [/usr/share/weewx/user/] but I saw that the tree structure has 
changed; where should I put my driver now?


watch these errors:

sudo systemctl status weewx.service
● weewx.service - WeeWX
 Loaded: loaded (/lib/systemd/system/weewx.service; enabled; 
vendor preset: enabled)
 Active: failed (Result: exit-code) since Wed 2024-03-06 18:32:05 
CET; 2s ago

   Docs: https://weewx.com/docs
    Process: 11182 ExecStart=weewxd /etc/weewx/weewx.conf 
(code=exited, status=4)

   Main PID: 11182 (code=exited, status=4)
    CPU: 682ms

mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
  pin = self.pin_factory.pin(pin)
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
    File "/usr/lib/python3/dist-packages/gpiozero/pins/pi.py", 
line 103, in pin
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
  pin = self.pin_class(self, n)
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
    File 
"/usr/lib/python3/dist-packages/gpiozero/pins/rpigpio.py", line 111, 
in __init__
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
  GPIO.setup(self.number, GPIO.IN, self.GPIO_PULL_UPS[self._pull])
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
  RuntimeError: Not running on a RPi!
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL __main__:*Unable 
to load driver: Not running on a RPi!*
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL __main__: 
  Exiting...
mars 06 18:32:05 raspberrypi systemd[1]: weewx.service: Main process 
exited, code=exited, status=4/NOPERMISSION
mars 06 18:32:05 raspberrypi systemd[1]: weewx.service: Failed with 
result 'exit-code'.


Patrick

Le 08/02/2024 à 08:59, salinois a écrit :


hello Matthew

OK I understand if that works

thanks also to vince.

Now , I must to try the 5.0.0 version

Patrick

Le 07/02/2024 à 23:06, matthew wall a écrit :
On Wednesday, February 7, 2024 at 3:36:55 PM UTC-5 sali...@gmail.com 
wrote:


pi@raspberrypi:~ $ wget -qO -
https://weewx.com/apt/weewx-python3.list | sudo tee
/etc/apt/sources.list.d/weewx.list
*/_deb [arch=all] http://weewx.com/apt/python3 buster main_ ==>
_why Buster_/*


'buster' (i.e., debian 10) is the oldest release on which the deb 
package will install.


if you look at the python2 configuration, it uses the label 
'squeeze' (debian 6)


the weewx packages are *really* stable with respect to dependencies, 
so the same package that works with debian 10 also works with debian 
11 and debian 12. besides, i am too old and lazy to build a new deb 
and new apt repository for every major debian release that comes out :)

--
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/ca7d09e7-acd7-4115-ae62-7ac60a1ef82bn%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/320351a0-1a0a-4474-9c39-de81a0e01011%40gmail.com.

Re: [weewx-user] Re: new install weewx on a new RPi 4b


hello,

I restart my installation with version weewx 5.0.1 and I have these errors:

on my version which works in 4.10.2, my "byows.py" driver is located 
here: [/usr/share/weewx/user/] but I saw that the tree structure has 
changed; where should I put my driver now?


watch these errors:

sudo systemctl status weewx.service
● weewx.service - WeeWX
 Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Wed 2024-03-06 18:32:05 
CET; 2s ago

   Docs: https://weewx.com/docs
    Process: 11182 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
status=4)

   Main PID: 11182 (code=exited, status=4)
    CPU: 682ms

mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
  pin = self.pin_factory.pin(pin)
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
    File "/usr/lib/python3/dist-packages/gpiozero/pins/pi.py", line 
103, in pin
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
  pin = self.pin_class(self, n)
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
    File "/usr/lib/python3/dist-packages/gpiozero/pins/rpigpio.py", 
line 111, in __init__
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
  GPIO.setup(self.number, GPIO.IN, self.GPIO_PULL_UPS[self._pull])
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL weewx.engine: 
  RuntimeError: Not running on a RPi!
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL __main__:*Unable to 
load driver: Not running on a RPi!*
mars 06 18:32:05 raspberrypi weewxd[11182]: CRITICAL __main__:   
Exiting...
mars 06 18:32:05 raspberrypi systemd[1]: weewx.service: Main process 
exited, code=exited, status=4/NOPERMISSION
mars 06 18:32:05 raspberrypi systemd[1]: weewx.service: Failed with 
result 'exit-code'.


Patrick

Le 08/02/2024 à 08:59, salinois a écrit :


hello Matthew

OK I understand if that works

thanks also to vince.

Now , I must to try the 5.0.0 version

Patrick

Le 07/02/2024 à 23:06, matthew wall a écrit :
On Wednesday, February 7, 2024 at 3:36:55 PM UTC-5 sali...@gmail.com 
wrote:


pi@raspberrypi:~ $ wget -qO -
https://weewx.com/apt/weewx-python3.list | sudo tee
/etc/apt/sources.list.d/weewx.list
*/_deb [arch=all] http://weewx.com/apt/python3 buster main_ ==>
_why Buster_/*


'buster' (i.e., debian 10) is the oldest release on which the deb 
package will install.


if you look at the python2 configuration, it uses the label 'squeeze' 
(debian 6)


the weewx packages are *really* stable with respect to dependencies, 
so the same package that works with debian 10 also works with debian 
11 and debian 12.  besides, i am too old and lazy to build a new deb 
and new apt repository for every major debian release that comes out :)

--
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/ca7d09e7-acd7-4115-ae62-7ac60a1ef82bn%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/8aaea7b9-af63-4449-8dd3-8e952a43c3b7%40gmail.com.

[weewx-user] Re: Raddy L7 Weather Station: XML of Current Conditions-How to Feed WeeWx?

2024-03-06 Thread 'michael.k...@gmx.at' via weewx-user

Fwiw, it is JSON, not XML. If you can get your device to emit these values 
as MQTT messages, you probably can get along 
with https://github.com/bellrichm/WeeWX-MQTTSubscribe and some configs.
Michael schrieb am Mittwoch, 6. März 2024 um 18:02:47 UTC+1:

> Hello,
>
> First I am not a developer, so pardon my ignorance. 
>
> I have a Raddy L7 LoRa WX station.  I found that on the local 
> configuration screen of the device, you can enter /client?command=record 
> and get an XML output of current conditions.  Just wondering what getting 
> this data to feed into WeeWx would entail?  
>
> {"sensor":[ 
> {"title":"Indoor","list":[["Temperature","68.9","Â°F"],["Humidity","38","%"]]},{"title":"Outdoor","list":[["Temperature","61.7","Â°F"],["Humidity","29","%"]]},{"title":"Pressure","list":[["Absolute","26.76","inhg"],["Relative","29.84","inhg"]]},{"title":"Wind
>  
> Speed","list":[["Max Daily 
> Gust","5.1","mph"],["Wind","1.1","mph"],["Gust","1.6","mph"],["Direction","123","Â°"],["Wind
>  
> Average 2 Minute","0.4","mph"],["Direction Average 2 
> Minute","111","Â°"],["Wind Average 10 Minute","1.3","mph"],["Direction 
> Average 10 
> Minute","134","Â°"]]},{"title":"Rainfall","list":[["Rate","0.0","inch/hr"],["Hour","0.0","inch","43"],["Day","0.0","inch","44"],["Week","0.0","inch","45"],["Month","0.0","inch","46"],["Year","5.72","inch","47"],["Total","10.65","inch","48"]],"range":"Range:
>  
> 0inch to 
> 393.7inch."},{"title":"Solar","list":[["Light","261.36","w/mÂ²"],["UVI","1.2",""]]}],"battery":{"title":"Battery","list":["All
>  
> battery are ok"]}}
>

-- 
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/35cecc00-debc-4f43-b7c4-c8ac07ca68f0n%40googlegroups.com.

[weewx-user] Raddy L7 Weather Station: XML of Current Conditions-How to Feed WeeWx?

2024-03-06 Thread Michael

Hello,

First I am not a developer, so pardon my ignorance. 

I have a Raddy L7 LoRa WX station.  I found that on the local configuration 
screen of the device, you can enter /client?command=record and get an XML 
output of current conditions.  Just wondering what getting this data to 
feed into WeeWx would entail?  

{"sensor":[ 
{"title":"Indoor","list":[["Temperature","68.9","Â°F"],["Humidity","38","%"]]},{"title":"Outdoor","list":[["Temperature","61.7","Â°F"],["Humidity","29","%"]]},{"title":"Pressure","list":[["Absolute","26.76","inhg"],["Relative","29.84","inhg"]]},{"title":"Wind
 
Speed","list":[["Max Daily 
Gust","5.1","mph"],["Wind","1.1","mph"],["Gust","1.6","mph"],["Direction","123","Â°"],["Wind
 
Average 2 Minute","0.4","mph"],["Direction Average 2 
Minute","111","Â°"],["Wind Average 10 Minute","1.3","mph"],["Direction 
Average 10 
Minute","134","Â°"]]},{"title":"Rainfall","list":[["Rate","0.0","inch/hr"],["Hour","0.0","inch","43"],["Day","0.0","inch","44"],["Week","0.0","inch","45"],["Month","0.0","inch","46"],["Year","5.72","inch","47"],["Total","10.65","inch","48"]],"range":"Range:
 
0inch to 
393.7inch."},{"title":"Solar","list":[["Light","261.36","w/mÂ²"],["UVI","1.2",""]]}],"battery":{"title":"Battery","list":["All
 
battery are ok"]}}

-- 
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/fd92564e-8dee-4042-b6c3-938d82b0n%40googlegroups.com.

Re: [weewx-user] Fedora Weewx RPM install