[weewx-user] Re: Working drivers for TWI, Vaisala WXT, Peet Bros Ultimeter

[storm...@gmail.com]

Dale

Hopefully you are feeling better. Could the driver be "fileparser".  

Storm

On Wednesday, November 16, 2022 at 10:59:18 PM UTC-5 wxe...@gmail.com wrote:

> After many years and a comfortable implementation of the Rainwise IP-100 
> driver, my Rainwise station has died, seems currently unfixable.  
> Despite loosing most of the summer trying to get the ISS to transmit 
> again, I've lost all taht time and have to look for other inputs.
>
> Looking through the Wiki, I see there may be three other station types 
> for which there are drivers which I might try.
>
>
> I have a Vaisala WXT520, a Texas Weather Instruments, and a Peet Bros 
> Ultimeter which I might try.
>
> Having followed the messages here, I know there were updates to Python 
> 3, which required some modifications to the drivers that are on GitHub, 
> and then a recent upgrade in WeeWx itself.
>
>
> My question is to current users of WeeWx, do you have a station working 
> with the latest WeeWx, the latest Python and any of the three drivers 
> mentioned here?
>
>
> If there is success, I will focus on trying to get my WeeWx working again.
>
>
> I know the ultimate would be to learn enough Python to implement my own 
> driver and be able to fix it, but quite honestly, after a several month 
> illness, I find that my previous understanding which I was proud of now 
> has become fuzzy and a personal expectation to rev my mental processes 
> up may take longer than I want to be without a WeeWx running, so I'm 
> looking for the most likely path to success, and then get back on trying 
> to get things working with understanding Python.
>
>
> I appreciate any comments that might steer me to one of these three 
> mentioned drivers to see if I should even start down a particular path 
> with a station type.
>
>
> Oh, one last question:  I had some notes on a sort of universal driver 
> which was mentioned as a starting point for someone wishing to begin to 
> learn how things work.  If I recall, it took a text file of the 
> station's readings and converted it into a LOOP type input for WeeWx to 
> ingest.  One 'only' needed to get data from the weather station, format 
> it into a list or dictionary, and then give it to WeeWx.  I have been 
> through the developer's guide and hardware guide and the wiki but for 
> the life of me cannot see the name of that referenced.  Have I triggered 
> enough recognition that someone might tell me the name of the driver and 
> I'll go study that again to start.
>
> Thank youDale
>
>
>

-- 
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/121f42cd-f61f-4f17-802c-0e2064fb6ea3n%40googlegroups.com.

Re: [weewx-user] Working drivers for TWI, Vaisala WXT, Peet Bros Ultimeter

['John Kline' via weewx-user]

Hi Dale,

Where are you located?

> On Nov 16, 2022, at 7:59 PM, DR  wrote:
> 
> After many years and a comfortable implementation of the Rainwise IP-100 
> driver, my Rainwise station has died, seems currently unfixable.  Despite 
> loosing most of the summer trying to get the ISS to transmit again, I've lost 
> all taht time and have to look for other inputs.
> 
> Looking through the Wiki, I see there may be three other station types for 
> which there are drivers which I might try.
> 
> 
> I have a Vaisala WXT520, a Texas Weather Instruments, and a Peet Bros 
> Ultimeter which I might try.
> 
> Having followed the messages here, I know there were updates to Python 3, 
> which required some modifications to the drivers that are on GitHub, and then 
> a recent upgrade in WeeWx itself.
> 
> 
> My question is to current users of WeeWx, do you have a station working with 
> the latest WeeWx, the latest Python and any of the three drivers mentioned 
> here?
> 
> 
> If there is success, I will focus on trying to get my WeeWx working again.
> 
> 
> I know the ultimate would be to learn enough Python to implement my own 
> driver and be able to fix it, but quite honestly, after a several month 
> illness, I find that my previous understanding which I was proud of now has 
> become fuzzy and a personal expectation to rev my mental processes up may 
> take longer than I want to be without a WeeWx running, so I'm looking for the 
> most likely path to success, and then get back on trying to get things 
> working with understanding Python.
> 
> 
> I appreciate any comments that might steer me to one of these three mentioned 
> drivers to see if I should even start down a particular path with a station 
> type.
> 
> 
> Oh, one last question:  I had some notes on a sort of universal driver which 
> was mentioned as a starting point for someone wishing to begin to learn how 
> things work.  If I recall, it took a text file of the station's readings and 
> converted it into a LOOP type input for WeeWx to ingest.  One 'only' needed 
> to get data from the weather station, format it into a list or dictionary, 
> and then give it to WeeWx.  I have been through the developer's guide and 
> hardware guide and the wiki but for the life of me cannot see the name of 
> that referenced.  Have I triggered enough recognition that someone might tell 
> me the name of the driver and I'll go study that again to start.
> 
> Thank youDale
> 
> 
> -- 
> 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/3fffddf3-df46-5491-c6f0-5fde01fb64c4%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 an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4BE74D10-E52F-4FDE-983D-20FE1C73FE9B%40johnkline.com.

[weewx-user] Working drivers for TWI, Vaisala WXT, Peet Bros Ultimeter

[DR]

After many years and a comfortable implementation of the Rainwise IP-100 
driver, my Rainwise station has died, seems currently unfixable.  
Despite loosing most of the summer trying to get the ISS to transmit 
again, I've lost all taht time and have to look for other inputs.


Looking through the Wiki, I see there may be three other station types 
for which there are drivers which I might try.



I have a Vaisala WXT520, a Texas Weather Instruments, and a Peet Bros 
Ultimeter which I might try.


Having followed the messages here, I know there were updates to Python 
3, which required some modifications to the drivers that are on GitHub, 
and then a recent upgrade in WeeWx itself.



My question is to current users of WeeWx, do you have a station working 
with the latest WeeWx, the latest Python and any of the three drivers 
mentioned here?



If there is success, I will focus on trying to get my WeeWx working again.


I know the ultimate would be to learn enough Python to implement my own 
driver and be able to fix it, but quite honestly, after a several month 
illness, I find that my previous understanding which I was proud of now 
has become fuzzy and a personal expectation to rev my mental processes 
up may take longer than I want to be without a WeeWx running, so I'm 
looking for the most likely path to success, and then get back on trying 
to get things working with understanding Python.



I appreciate any comments that might steer me to one of these three 
mentioned drivers to see if I should even start down a particular path 
with a station type.



Oh, one last question:  I had some notes on a sort of universal driver 
which was mentioned as a starting point for someone wishing to begin to 
learn how things work.  If I recall, it took a text file of the 
station's readings and converted it into a LOOP type input for WeeWx to 
ingest.  One 'only' needed to get data from the weather station, format 
it into a list or dictionary, and then give it to WeeWx.  I have been 
through the developer's guide and hardware guide and the wiki but for 
the life of me cannot see the name of that referenced.  Have I triggered 
enough recognition that someone might tell me the name of the driver and 
I'll go study that again to start.


Thank you    Dale


--
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/3fffddf3-df46-5491-c6f0-5fde01fb64c4%40gmail.com.

Re: [weewx-user] Shortly after upgrading to 4.9.1 I have a weird issue - sending empry data but...?

[Kruse Ludington]

I have the fix. I realized that I was actually sending EMPTY messages to 
ALL of these from WEEWX - WindGuru is THE ONLY SITE that rejects the empty 
messages of all of the below! LOL

Met WOW
Windy
PWSWeather
Wunderground
WindGuru
Awekas
OWM
Meteoservices
WeatherCloud
Weather365
CWOP

When I originally set up weewx a couple years ago and I had this issue and 
this was the original fix - I was bummed that my complaints about it had 
never been addressed. The source code I include in the .zip file below is 
an older version from Matt I think it was .54b or the like...

Having remembered the issue is an old problem with the interceptor driver - 
I haven't had the chance to debug it yet but will at some point - in any 
event, note the attached zip file which has a readme included I wrote which 
states:

"This is a workaround/fix for an issue with intercepting AmbientWeather 
console messages using the Interceptor driver for the WS-2902C model 
weather (and possibly similar models):

The latest interceptor integration has a file which I have renamed 
interceptor.py.new.bad, a copy is in this .zip file. This ends up
causing all of the data sent to various weather web sites to actually 
be an empty message! The older interceptor.py file which is included 
here (renamed to interceptor.py.old.good), still works.

Just rename the interceptor.py.old.good file as interceptor.py and 
place it in:

"/usr/share/weewx/user"  (that last directory is NOT misspelled)

(You might want to rename the old (newer) interceptor.py that 
is already there on your machine first for your comfort level).

Note, there will be several messages in the log about "unrecognized
parameters" when using this driver, but those are the more esoteric 
weather station details that are typically not used - and those 
messages can be ignored, unless you want to update weewx and the 
DB schema to also handle those."

On Monday, November 14, 2022 at 3:30:48 PM UTC-5 gjr80 wrote:

> I agree with Tom, the WindGuru uploader is not part of WeeWX so the 
> problem should be taken up with the WindGuru uploader author. But
>
> It would be worthwhile seeing the full story rather than just a few small 
> extracts. Interceptor based installs can be complex and you can sometimes 
> see some (seemingly) unusual behaviour. Does the WindGuru issue occur every 
> archive record or just occasionally? It would be worthwhile seeing the 
> WeeWX startup and an extended log extract. I would suggest editing 
> weewx.conf and setting debug = 2. Restart WeeWX. Let WeeWX run until at 
> least a couple of WindGuru errors occur. Take a log extract showing the 
> full WeeWX startup sequence, do not alter/filter anything in the log. This 
> will give us a clear picture of your WeeWX config. Also include a log 
> extract showing the WindGuru errors, make sure you include at least two 
> full archive periods before the WindGuru error. Again don't alter/filter 
> anything in the log. With debug = 2, the interceptor driver and multiple 
> uploads the log extract will likely be lengthy, but it will give the full 
> picture as to what is going on.
>
> Gary
>
> On Tuesday, 15 November 2022 at 03:06:50 UTC+10 tke...@gmail.com wrote:
>
>> On Mon, Nov 14, 2022 at 8:49 AM Kruse Ludington  
>> wrote:
>>
>>> Here's an example of data received every 16 seconds form the 
>>> AmbientWeather WS-2902C using the Interceptor driver:
>>>
>>> Nov 14 11:30:14 kruse-pi homeassistant[821]: #033[32m2022-11-14 
>>> 11:30:14.951 INFO (MainThread) [aioambient] Received packet MESSAGE data 
>>> 2["data",{"dateutc":166844340,"tempinf":76.3,"humidityin":33,"baromrelin":30.154,"baromabsin":30.281,"tempf":42.3,"battout":1,"humidity":50,"winddir":313,"windspeedmph":6.3,"windgustmph":8.1,"maxdailygust":17.2,"hourlyrainin":0,"eventrainin":0,"dailyrainin":0,"weeklyrainin":0.091,"monthlyrainin":1.701,"totalrainin":15.63,"solarradiation":390.55,"uv":3,"temp1f":69.6,"humidity1":49,"batt1":1,"batt_co2":1,"feelsLike":38.31,"dewPoint":25,"feelsLike1":68.6,"dewPoint1":49.6,"feelsLikein":75.2,"dewPointin":45.1,"lastRain":"2022-11-13T13:35:00.000Z","tz":"America/New_York","date":"2022-11-14T16:30:00.000Z","macAddress":"E8:DB:84:E6:D0:B0"}]#033[0m
>>>
>>
>> None of these observation types are in the normal WeeWX schema. Perhaps 
>> the interceptor station map is wrong or inoperative?
>>
>> I don't have an explanation for why they would work for other upload 
>> sites. Perhaps they just don't report an error?
>>
>> -tk
>>
>

-- 
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/764b3df5-0308-44b6-94c6-c9246d12d07cn%40googlegroups.com.
<>

[weewx-user] Re: WeeWX 4.6.2 Working Well

[gary....@gmail.com]

No, no need for anything other than the in-built driver.
Pretty self explanatory once you config with the Davis driver.

##

[Vantage]
# This section is for the Davis Vantage series of weather stations.

# Connection type: serial or ethernet 
#  serial (the classic VantagePro)
#  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
type = ethernet

# If the connection type is serial, a port must be specified:
#   Debian, Ubuntu, Redhat, Fedora, and SuSE:
# /dev/ttyUSB0 is a common USB port name
# /dev/ttyS0   is a common serial port name
#   BSD:
# /dev/cuaU0   is a common serial port name
port = /dev/ttyUSB0

# If the connection type is ethernet, an IP Address/hostname is 
required:
host = 10.10.10.10

##
# The rest of this section rarely needs any attention. 
# You can safely leave it "as is."
##

# Serial baud rate (usually 19200)
baudrate = 19200

# TCP port (when using the WeatherLinkIP)
tcp_port = 2

# TCP send delay (when using the WeatherLinkIP):
tcp_send_delay = 0.5

# The type of LOOP packet to request: 1 = LOOP1; 2 = LOOP2; 3 = both
loop_request = 3

# The id of your ISS station (usually 1). If you use a wind meter 
connected
# to a anemometer transmitter kit, use its id
iss_id = 1

# How long to wait for a response from the station before giving up (in
# seconds; must be greater than 2)
timeout = 4

# How long to wait before trying again (in seconds)
wait_before_retry = 1.2

# How many times to try before giving up:
max_tries = 4

# Vantage model Type: 1 = Vantage Pro; 2 = Vantage Pro2
model_type = 2

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

##
On Wednesday, November 16, 2022 at 12:30:00 PM UTC-5 Kev D wrote:

> Hi Gary,
>
> I have just upgraded my setup to  VP2, WifiLogger2, and Belchertown skin 
> as well. Would you mind sharing your configuration setup in weewx to grab 
> data from the WifiLogger2? Are you also using the interceptor driver for 
> this config?
>
> Thanks!
>
> On Friday, February 11, 2022 at 9:00:57 AM UTC-5 gary@gmail.com wrote:
>
>> With the rapid succession of releases, I just wanted to say that my 
>> upgrade to 4.6.2 went well and all is working with the VP2, WifiLogger2, 
>> and Belchertown skin.
>>
>> Thanks for an amazing system!
>>
>

-- 
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/ac88d0b0-6adf-4048-8359-b031954f188an%40googlegroups.com.

[weewx-user] Re: Calculating rain delta

[gjr80]

I'm guessing by 4.9.2 you really meant 4.2.0? Support for StdWXCalculate 
calculation 
of deltas was added in v4.2.0, but the necessary XType was not loaded by 
weewx.conf (under a default install). This was corrected in v4.3.0.

I agree there is not much information describing the use of deltas in 
StdWXCalculate, I was looking for some information myself for another issue 
recently and all I found was the comments in the Delta XType declaration 
. 
The comments agree with your understanding, though I must confess to not 
having actually used a delta as yet. I will look to include something on 
StdWXCalculate deltas somewhere in the documentation.

Gary
On Wednesday, 16 November 2022 at 23:18:13 UTC+10 bell...@gmail.com wrote:

> MQTTSubscribe has support for calculating the delta value of an 
> observation from the total. I know WeeWX added this support and want to 
> move people to use the built-in support (or at least have new users use 
> it). I wasn’t able to find much information on it, so just looking to 
> verify some information.
>
>1. This was added in 4.9.2 (issue #491)
>2. To use it, the following needs to be added to weewx.conf (with the 
>correct ‘input name’).
>
>[StdWXCalculate]
>
>  [[Delta]]
>
> [[[rain]]]
>
> input = totalRain
>
> Thanks. rich
>

-- 
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/aba80761-7028-4bef-a9c5-52226fc8cce3n%40googlegroups.com.

Re: [weewx-user] Re: calculate rainRate for second rain gauge...?

[Glenn McKechnie]

Hi Gary,

Thanks for that.
I can appreciate that other things can often rank higher on the ever
changing ToDo list; such is its nature.

Will bookmark #813, and happy to test any code.
I can probably fire up a separate instance of weewx with another ow
adapter and rain ( hail / snow) counter if need be.

Hope you (and others) are high and dry in this wet summer we are
having. Seems odd to be in the middle of fire preparations but Aus
really is a country of extremes.


On 17/11/2022, gjr80  wrote:
> Glenn,
>
> Other things and a need to reacquaint myself with #491
>  have delayed me getting back to
>
> you. You are correct that StdWXCalculate cannot calculate rate based fields
>
> other than rainRate. #491 considered a number of approaches for calculating
>
> delta fields from total fields (the case in hand being field rain from a
> rain total field) and a number of approaches were considered, these
> approaches impacted on some of the other StdWXCalculate functions and I
> suspect my comment earlier in this thread was based on some of the early
> development code written under #491. As it turned out the final #491
> solution resulted in the current hard coded rainRate approach.
>
> Happy you look at generalising rate based calculation in StdWXCalculate and
>
> I have raised issue #813  to
> track this. Should have some time in the next week to work on this.
>
> Gary
>
> On Sunday, 13 November 2022 at 16:16:11 UTC+10 Glenn McKechnie wrote:
>
>> On 29/06/2020, gjr80 <...> wrote:
>> > I would not worry about raising anything Christian, the code I am
>> working on
>> > would allow something like a rate based field to be calculated from
>> > some
>> > other (user specified) field. You still have to add any necessary extra
>> > fields to your database yourself, but StdWXCalculate could be configured
>> >
>> to
>> > create the rate based field. No guarantees as it needs the Tom-tick but
>> >
>> it
>> > looks good so far.
>>
>> Breathing life into an old thread...
>>
>> Did this idea get the "Tom-tick"?
>>
>> I'm using hail and hailrate.
>>
>> I've had a look at issue #491 and the new wxxtypes and wondering if
>> that is what was being referenced here. I can't see a way to make hail
>> (or snow!) work with it (RainRater) though. Hopefully some simple
>> stanza under [StdWXCalculate] [[WXXTypes]]?
>>
>> I co-opted the hail field a while ago and have 5 years of data
>> supplied via a modified OWFS driver.
>>
>> It would be helpful to have the hailrate to compare with the rainrate
>> from the original rain gauge as I'm cleaning up some extreme rain
>> values; which also means that issue #787 (wee_database --calc-missing
>> does not correctly calculate rainRate) bites if I want the historical
>> values?
>> --
>>
>>
>> Cheers
>> Glenn
>>
>> rorpi - read only raspberry pi & various weewx addons
>> https://github.com/glennmckechnie
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/1e8d4083-e7ae-4c9c-bc54-36efb147c886n%40googlegroups.com.
>


-- 


Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAAraAzh%2BniajXu5%2B4eAumU_Rp4F%2BiUKb0XxTB%2BNPSb-qLrJhUw%40mail.gmail.com.

Re: [weewx-user] Missing values after upgrade to 4.9.1

[Tom Keffer]

Apologies. You need to set debug=2 in weewx.conf to get this extra
information. Please set to 2, then restart weewxd, post the log through the
first reporting cycle.

On Wed, Nov 16, 2022 at 8:20 AM ris...@gmail.com  wrote:

> Here:
>
> Nov 16 17:53:09 weewxberry systemd[1]: Started WeeWX weather system.
> Nov 16 17:53:11 weewxberry weewx[8109] INFO __main__: Initializing weewx
> version 4.9.1
> Nov 16 17:53:11 weewxberry weewx[8109] INFO __main__: Using Python 3.9.2
> (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
> Nov 16 17:53:11 weewxberry weewx[8109] INFO __main__: Located at
> /usr/bin/python3
> Nov 16 17:53:11 weewxberry weewx[8109] INFO __main__: Platform
> Linux-5.15.76+-armv6l-with-glibc2.31
> Nov 16 17:53:11 weewxberry weewx[8109] INFO __main__: Locale is
> 'en_GB.UTF-8'
> Nov 16 17:53:11 weewxberry weewx[8109] INFO __main__: Using configuration
> file /home/weewx/weewx.conf
> Nov 16 17:53:11 weewxberry weewx[8109] INFO __main__: Debug is 1
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG __main__: Initializing engine
> Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.engine: Loading station
> type FineOffsetUSB (weewx.drivers.fousb)
> Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.drivers.fousb: driver
> version is 1.20
> Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.drivers.fousb: polling
> mode is PERIODIC
> Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.drivers.fousb: polling
> interval is 60
> Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.drivers.fousb: found
> station on USB bus= device=
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service
> weewx.engine.StdTimeSynch
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished
> loading service weewx.engine.StdTimeSynch
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service
> weewx.engine.StdConvert
> Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.engine: StdConvert
> target unit is 0x1
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished
> loading service weewx.engine.StdConvert
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service
> weewx.engine.StdCalibrate
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished
> loading service weewx.engine.StdCalibrate
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service
> weewx.engine.StdQC
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished
> loading service weewx.engine.StdQC
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service
> weewx.wxservices.StdWXCalculate
> Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.wxservices:
> StdWXCalculate will use data binding wx_binding
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.manager: Daily summary
> version is 1.0
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished
> loading service weewx.wxservices.StdWXCalculate
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service
> weewx.wxxtypes.StdWXXTypes
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished
> loading service weewx.wxxtypes.StdWXXTypes
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service
> weewx.wxxtypes.StdPressureCooker
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished
> loading service weewx.wxxtypes.StdPressureCooker
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service
> weewx.wxxtypes.StdRainRater
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished
> loading service weewx.wxxtypes.StdRainRater
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service
> weewx.wxxtypes.StdDelta
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished
> loading service weewx.wxxtypes.StdDelta
> Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service
> weewx.engine.StdArchive
> Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.engine: Archive will use
> data binding wx_binding
> Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.engine: Record
> generation will be attempted in 'hardware'
> Nov 16 17:53:12 weewxberry weewx[8109] INFO weewx.engine: Using archive
> interval of 300 seconds (specified by hardware)
> Nov 16 17:53:12 weewxberry weewx[8109] DEBUG weewx.engine: Use LOOP data
> in hi/low calculations: 1
> Nov 16 17:53:12 weewxberry weewx[8109] DEBUG weewx.engine: Finished
> loading service weewx.engine.StdArchive
> Nov 16 17:53:12 weewxberry weewx[8109] DEBUG weewx.engine: Loading service
> weewx.restx.StdStationRegistry
> Nov 16 17:53:13 weewxberry weewx[8109] INFO weewx.restx: StationRegistry:
> Registration not requested.
> Nov 16 17:53:13 weewxberry weewx[8109] DEBUG weewx.engine: Finished
> loading service weewx.restx.StdStationRegistry
> Nov 16 17:53:13 weewxberry weewx[8109] DEBUG weewx.engine: Loading service
> weewx.restx.StdWunderground
> Nov 16 17:53:13 weewxberry weewx[8109] DEBUG weewx.restx: 

Re: [weewx-user] Re: calculate rainRate for second rain gauge...?

[gjr80]

Glenn,

Other things and a need to reacquaint myself with #491 
 have delayed me getting back to 
you. You are correct that StdWXCalculate cannot calculate rate based fields 
other than rainRate. #491 considered a number of approaches for calculating 
delta fields from total fields (the case in hand being field rain from a 
rain total field) and a number of approaches were considered, these 
approaches impacted on some of the other StdWXCalculate functions and I 
suspect my comment earlier in this thread was based on some of the early 
development code written under #491. As it turned out the final #491 
solution resulted in the current hard coded rainRate approach.

Happy you look at generalising rate based calculation in StdWXCalculate and 
I have raised issue #813  to 
track this. Should have some time in the next week to work on this.

Gary

On Sunday, 13 November 2022 at 16:16:11 UTC+10 Glenn McKechnie wrote:

> On 29/06/2020, gjr80 <...> wrote:
> > I would not worry about raising anything Christian, the code I am 
> working on
> > would allow something like a rate based field to be calculated from some
> > other (user specified) field. You still have to add any necessary extra
> > fields to your database yourself, but StdWXCalculate could be configured 
> to
> > create the rate based field. No guarantees as it needs the Tom-tick but 
> it
> > looks good so far.
>
> Breathing life into an old thread...
>
> Did this idea get the "Tom-tick"?
>
> I'm using hail and hailrate.
>
> I've had a look at issue #491 and the new wxxtypes and wondering if
> that is what was being referenced here. I can't see a way to make hail
> (or snow!) work with it (RainRater) though. Hopefully some simple
> stanza under [StdWXCalculate] [[WXXTypes]]?
>
> I co-opted the hail field a while ago and have 5 years of data
> supplied via a modified OWFS driver.
>
> It would be helpful to have the hailrate to compare with the rainrate
> from the original rain gauge as I'm cleaning up some extreme rain
> values; which also means that issue #787 (wee_database --calc-missing
> does not correctly calculate rainRate) bites if I want the historical
> values?
> -- 
>
>
> Cheers
> Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>

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

Re: [weewx-user] Re: installing belchertown extension

[Alex Vanuxem]

Thx dude.

In short o got confussed with the setup.py install and the direct one.

Took me some time to figure it out.

The setyp.py doesnt work in a virtual env.

The direct one works only under /etc/weewx.

For none experts in linux the how to should be rewritten. I am glad to help
in it.

Please view my 4 websites i have made this year


www.sint-katelijne-waver-meteo.be/pwsWD
Www.sint-katelijne-waver-meteo.be/Cumulus
www.sint-katelijne-waver-meteo.be/template
www.sint-katelijne-waver-meteo.be/weewx


Enjoy.


And thank you for learning a lot about linux.


Cheers...

Op wo 16 nov. 2022 21:34 schreef Stefanos Kalaitzis <
stefanoskalait...@gmail.com>:

> Also i think by default the belchertown skin its published in
> public_html/Belchertown ... So if you want it to be your main page change
> it to HTML_ROOT = public_html
>
> Here is my configuration in weewx.conf
> [[Belchertown]]
> enable = true
> log_success = False
> log_failure = True
> skin = Belchertown
> HTML_ROOT = public_html
>
> Στις Τετ, 16 Νοε 2022, 20:39 ο χρήστης vince 
> έγραψε:
>
>> On Wednesday, November 16, 2022 at 9:57:59 AM UTC-8 vanuxe...@gmail.com
>> wrote:
>>
>>> Did uninstall and instal a few times. And i always use sudo.
>>>
>>
>> Download a new copy of the Belchertown skin and try installing that.
>>
>> --
>> 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/a21f0316-99a8-4263-9a1b-4eb7d21f602cn%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/CAERekb-UN7rFjdQCv8rZgHJ%2BsDRPu4SDtyuuGyUoc9u6q%2BJFoQ%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/CAHaYyoKMqrkwr3WjGV3xp00he76PjSzekXQWsPHc%2BeAoDwTnAw%40mail.gmail.com.

Re: [weewx-user] Re: Rsync Help or User Help :o)

[cric...@pobox.com]

Important detail:

What is important with the slashes and the path are related to the SOURCE 
path.  It doesn't matter if
the destination does or doesn't have a trailing slash.  It does matter if 
the destination specifies a file rather than
a directory, though.

On Tuesday, November 15, 2022 at 9:51:30 AM UTC-7 FIA Ranch wrote:

> Okay.. Thanks all for the thoughts and comments.
>
> For the sake of anyone fighting this same issue somewhere in the future, 
> let me get this refocused, clarified, up to date.
>
> Baseline Info
> --
> 1) Host Machine is a hosting company
> 2) The host machine is a shared Linux based machine
> 3) I own the domain and rent the hosting
> 4) In the absolute path... home3/fiaranch/ - everything under and 
> past 'fiaranch' I have full control of
>
> 5) Client Machine is mine and is a private machine to be used and abused 
> as I see fit. :o)
>
> Users Question - Closed
> With regards to this issue with WeeWX, all activity will be with my root 
> hat on.
>
> SSH Keys Issue - Closed
> Thanks to Vince I learned that user and root keys are independant.  Now 
> both root and user have their own keys and they have been tested.
>
> SSH Port Question - Closed
> The hosting company states two ports as follows:
> SSH - 22
> SSH Shared/Reseller Servers - 
> NOTE - Command line Rsync actually works with both
>
>
> Question of "/" placement - Closed
>
> Thank you cric...@pobox.com for the definition of differentiation.
>
> File placement on the host is absolute path 
> /home3/fiaranch/public_html/weather/*.*
>
> Using command line, Rsync will accept both, which makes sense based on 
> what cric...@pobox.com stated.
>
> Command (WITH trailing '/') - root@weather:~# rsync -avhze ssh --progress 
> --update --stats  /var/www/html/ --delete 
> fiar...@fiaranch.com:/home3/fiaranch/public_html/weather/
>
> Result (without all the superfulous data)
> sent 595.67K bytes  received 17.85K bytes  31.46K bytes/sec
> total size is 1.79M  speedup is 2.91
>
> Command (WITHOUT trailing '/') - root@weather:~# rsync -avhze ssh 
> --progress --update --stats  /var/www/html/ --delete 
> fiar...@fiaranch.com:/home3/fiaranch/public_html/weather
>
> Result (without all the superfulous data)
> sent 309.53K bytes  received 12.20K bytes  71.49K bytes/sec
> total size is 1.86M  speedup is 5.77
>
> Note - The result difference is mainly a time difference.  However, based 
> on differentiation cric...@pobox.com stated, I am going to go forward 
> without the trailing '/'.
>
> So that brings me to WeeWX config discussion.
>
> The WeeWX Config is now as follows:
> skin = Rsync
> enable = true
> server = fiaranch.com
> user = fiaranch
> path = /home3/fiaranch/public_html/weather
> port = 
> log_success = true
> log_failure = true
> HTML_ROOT = /var/www/html
> delete = 1
>
> Notes:
> 1) The two log entries I added from what Vince posted.  Just to see if 
> that provides any additional information.
> 2) Removed the trailing '/' from the path.
>
> Results
> Nov 15 09:34:23 weather weewx[5274] DEBUG weewx.reportengine: Running 
> report 'RSYNC'
> Nov 15 09:34:23 weather weewx[5274] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Rsync/skin.conf for report 'RSYNC'
> Nov 15 09:34:23 weather weewx[5274] DEBUG weewx.reportengine: Cannot read 
> localization file /etc/weewx/skins/Rsync/lang/en.conf for report 'RSYNC': 
> Config file not found: "/etc/weewx/skins/Rsync/lang/en.conf".
> Nov 15 09:34:23 weather weewx[5274] DEBUG weewx.reportengine:  Using 
> defaults instead.
> Nov 15 09:34:23 weather weewx[5274] DEBUG weeutil.rsyncupload: 
> rsyncupload: cmd: [['rsync', '--archive', '--stats', '--delete', '-e', 'ssh 
> -p ', '/var/www/html/', 
> 'fiar...@fiaranch.com:/home3/fiaranch/public_html/weather']]
> Nov 15 09:34:26 weather weewx[5274] INFO weeutil.rsyncupload: rsync'd 56 
> files (1,093,360 bytes) in 2.42 seconds
>
> WHAT !
>
> All said and done the failures can be attributed to two things:
> 1) SSH Keys must be paired under root, not user - Thank You Vince
> 2) No trailing '/' in the path.  Even though it will work in a command 
> line Rsync, it will not work in WeeWX.
>
> Discussion Closed
>
> Thanks to all for the comments, ideas, assistance, and sharing your 
> experience!
>
> Now going to play with Rsync options to see if I can break it again!! 
>  LMFAO
>
>
>
>
>
>
>
> On Tuesday, November 15, 2022 at 9:17:55 AM UTC-7 jo...@johnkline.com 
> wrote:
>
>> A trailing slash means copy the contents of the directory.
>>
>> Note that WeeWX code will add the slash if it is a directory.  See code 
>> snippet below.
>>
>> [image: weewx.png]
>>
>> weewx/rsyncupload.py at master · weewx/weewx 
>> 
>> github.com 
>> 
>> 
>>
>> # If the source path ends 

Re: [weewx-user] Re: installing belchertown extension

[Stefanos Kalaitzis]

Also i think by default the belchertown skin its published in
public_html/Belchertown ... So if you want it to be your main page change
it to HTML_ROOT = public_html

Here is my configuration in weewx.conf
[[Belchertown]]
enable = true
log_success = False
log_failure = True
skin = Belchertown
HTML_ROOT = public_html

Στις Τετ, 16 Νοε 2022, 20:39 ο χρήστης vince  έγραψε:

> On Wednesday, November 16, 2022 at 9:57:59 AM UTC-8 vanuxe...@gmail.com
> wrote:
>
>> Did uninstall and instal a few times. And i always use sudo.
>>
>
> Download a new copy of the Belchertown skin and try installing that.
>
> --
> 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/a21f0316-99a8-4263-9a1b-4eb7d21f602cn%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/CAERekb-UN7rFjdQCv8rZgHJ%2BsDRPu4SDtyuuGyUoc9u6q%2BJFoQ%40mail.gmail.com.

Re: [weewx-user] Re: installing belchertown extension

[Alex Vanuxem]

Sorted . Had a mixup of ubuntu install and python install. Learning. Thx.
Thread is closed as solved.

Op wo 16 nov. 2022 19:39 schreef vince :

> On Wednesday, November 16, 2022 at 9:57:59 AM UTC-8 vanuxe...@gmail.com
> wrote:
>
>> Did uninstall and instal a few times. And i always use sudo.
>>
>
> Download a new copy of the Belchertown skin and try installing that.
>
> --
> 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/a21f0316-99a8-4263-9a1b-4eb7d21f602cn%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/CAHaYyoJQrUfP%2BmquQiktHRf%2Btv0-_qQxXKmWT6hkw6dt%2BYJVYg%40mail.gmail.com.

Re: [weewx-user] Re: WeeWX-MQTTSubscribe - Filter unwanted devices

[Bryan Parke]

Thanks again.  My mistake was using this:

rtl_433 -F json -M utc -d:0002 -f 915.00M | mosquitto_pub -t
weather/radio -h localhost -l

instead of this:

rtl_433 -F "mqtt://localhost:1883,devices=rtl_433[/id]"

Now I'm seeing each separate device as its own topic whereas before they
were all landing in weather/radio and I didn't have (or know) a way to
filter.  Now I can just ignore anything with device ID 2849 for the wind
data.

Thanks again!
Bryan

On Wed, Nov 16, 2022 at 1:30 PM vince  wrote:

> On Wednesday, November 16, 2022 at 10:06:05 AM UTC-8 bryan...@gmail.com
> wrote:
>
>> Thanks for the reply, however, if I ignore it, it will ignore it
>> entirely, not just for the one with bad data.  Maybe you didn't see that
>> part of my question.  2 stations are reporting weather data with the same
>> field name *wind_avg_km_h * which I map to windSpeed.  One of the
>> stations, with ID 2849 has a bad wind sensor so I want to ignore only the
>> wind data from that station, but want to continue to receive and map the
>> wind data from the other station with ID 3522.
>>
>
> No, I read your question.
>
> What I did here was publish to a different topic from each station. That
> made it easy to ignore the one I wanted to.
>
> For me, it was something like "weather/radio/12345678" for device id
> 12345678, as an example.   Each device publishing to MQTT used its unique
> device id to publish to a device-specific topic.  Then I'd subscribe to
> only the ones I wanted.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/yzk4qXDa87o/unsubscribe.
> To unsubscribe from this group and all its topics, 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/b8eabcf1-36f4-42c0-8cce-5c3e383469efn%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/CAPXDAYZWsLAagHc_rkgbPUN%2BBwD78FdZXWZhv%3D__ctiMJ6Teng%40mail.gmail.com.

Re: [weewx-user] Re: installing belchertown extension

[vince]

On Wednesday, November 16, 2022 at 9:57:59 AM UTC-8 vanuxe...@gmail.com 
wrote:

> Did uninstall and instal a few times. And i always use sudo. 
>

Download a new copy of the Belchertown skin and try installing that.

-- 
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/a21f0316-99a8-4263-9a1b-4eb7d21f602cn%40googlegroups.com.

Re: [weewx-user] Re: WeeWX-MQTTSubscribe - Filter unwanted devices

[Bryan Parke]

This is brilliant! Thank you!  I'll give it a shot.

On Wed, Nov 16, 2022 at 1:15 PM bell...@gmail.com 
wrote:

> I use ''rtl_433 -F mqtt://localhost:1883' and it publishes directly to the
> following topics:
>  rtl_433//devices[/type][/model][/subtype][/channel][/id]
>  rtl_433//events
>  rtl_433//states
> I then subscribe to
> 'rtl_433//devices[/type][/model][/subtype][/channel][/id]' as
> 'type = individual'.
>
> If you want/need to continue piping to mosquitto_pub, look at
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring-additional-options#msg_id_field.
> Then you can use the 'ignore' option with the appended 'id'.
>
> rich
>
> On Wednesday, 16 November 2022 at 12:48:36 UTC-5 bryan...@gmail.com wrote:
>
>> I'm currently running Weewx 4.9.1 and using WeeWX-MQTTSubscribe to
>> capture data from 2 separate RTL SDR's.  One of the RTL-SDR devices is
>> listening on 433.92 and is picking up weather data from a couple nearby
>> weather stations.  One of the weather stations I'm listening to has a bad
>> wind sensor, so I do not want the wind data from that station, the other
>> station has good wind data so I do want that data.  These two stations are
>> from the same manufacturer and fall under the same device decoding protocol
>> ( [40] Acurite 592TXR Temp/Humidity, 5n1 Weather Station, 6045 Lightning,
>> 899 Rain, 3N1, Atlas).
>>
>> The other RTL-SDR is listening on 915.00 in order to pick up pressure
>> data from another sensor.
>>
>> When using
>> `rtl_433 -F json -M utc -R 40 | mosquitto_pub -t weather/radio -h
>> localhost -l`
>>
>> I receive all packets from both stations and pass that to the
>> WeeWX-MQTTSubscribe driver where I have set up the various fields and map
>> them to weewx.  For example, the wind data:
>>
>>  [[topics]]
>> unit_system = US
>> [[[weather/radio]]]
>>
>> ... snip ...
>> *wind_avg_km_h*
>> name = windSpeed
>>
>> *wind_dir_deg*
>> name = windDir
>>
>> ... snip ...
>>
>> since both stations emit, for example, 'wind_avg_km_h', I don't have a
>> way to filter out one of them (the bad one) so I end up getting some
>> garbage data in the mix with good data.
>>
>> My question is this: since these two stations are the same 'device
>> decoding protocol' (40) is there a way to differentiate between the json
>> data coming from the one vs the other?  The both have different id
>> fields, the one I want has an ID of 3522 and the one I don't want wind data
>> from is ID 2849.
>>
>> Essentially I want to keep data from both devices but exclude just the
>> wind data from one of them.
>>
>> Thanks much for any help you all can provide.
>>
>> Bryan
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/yzk4qXDa87o/unsubscribe.
> To unsubscribe from this group and all its topics, 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/ef1bfb7c-0204-425d-84bf-b6b13a56bb57n%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/CAPXDAYZh26%2BH80uPf_oMvo-EpBAYT6MWj2V-pkQ5brdGN5N7EA%40mail.gmail.com.

Re: [weewx-user] Re: WeeWX-MQTTSubscribe - Filter unwanted devices

[vince]

On Wednesday, November 16, 2022 at 10:06:05 AM UTC-8 bryan...@gmail.com 
wrote:

> Thanks for the reply, however, if I ignore it, it will ignore it entirely, 
> not just for the one with bad data.  Maybe you didn't see that part of my 
> question.  2 stations are reporting weather data with the same field name 
> *wind_avg_km_h * which I map to windSpeed.  One of the stations, with ID 
> 2849 has a bad wind sensor so I want to ignore only the wind data from that 
> station, but want to continue to receive and map the wind data from the 
> other station with ID 3522.
>

No, I read your question.  

What I did here was publish to a different topic from each station. That 
made it easy to ignore the one I wanted to.

For me, it was something like "weather/radio/12345678" for device id 
12345678, as an example.   Each device publishing to MQTT used its unique 
device id to publish to a device-specific topic.  Then I'd subscribe to 
only the ones I wanted.

-- 
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/b8eabcf1-36f4-42c0-8cce-5c3e383469efn%40googlegroups.com.

Re: [weewx-user] Re: installing belchertown extension

[Stefanos Kalaitzis]

Check weewx.conf to enable skin


enable = true

Στις Τετ, 16 Νοε 2022, 19:57 ο χρήστης Alex Vanuxem 
έγραψε:

> Did uninstall and instal a few times. And i always use sudo.
>
> Op wo 16 nov. 2022 18:55 schreef vince :
>
>> Just install it again and remember to use 'sudo'.  Sheesh.
>>
>> On Wednesday, November 16, 2022 at 9:34:17 AM UTC-8 vanuxe...@gmail.com
>> wrote:
>>
>>> Hi
>>>
>>> Thanks for your answer.
>>>
>>> Unfortunately nothing is there.
>>>
>>> The skins folder is also not updated to show belchertown.
>>>
>>> Please advise.
>>>
>>> Thx
>>>
>>> Alex
>>>
>>> Op di 15 nov. 2022 21:37 schreef vince :
>>>
 Look for Belchertown with an upper case 'B'.

 You should see a long stanza for Belchertown in the StdReport section
 of weewx.conf

 On Tuesday, November 15, 2022 at 11:30:05 AM UTC-8 vanuxe...@gmail.com
 wrote:

> Hi all,
>
> I installed the belchertown skin into the wee_extension.
>
> if i do a --list the belchertown is listed
>
> i have a setup.py install
>
> and running weewx under a virtual box environment.
>
> normally i guess the weewx.conf should be updated with this extension?
> but it's not ...
>
> do I miss something?
>
> thx
>
> grtz
>
> alex
>
 --
 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/af8576b1-2575-4117-b043-2cc7946e1e2cn%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/1d9b8920-cef8-4085-a9de-5395c54868cbn%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/CAHaYyoK9ATNG5YioqgRz_L2HkB6CxcTR7OPmY3cQJZN_25B5-Q%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/CAERekb8uyFLpaKtkrpBQf4O%3DKRdOF-k2jzgfjRM0ZAA%2BKCgBEw%40mail.gmail.com.

[weewx-user] Re: WeeWX-MQTTSubscribe - Filter unwanted devices

[bell...@gmail.com]

I use ''rtl_433 -F mqtt://localhost:1883' and it publishes directly to the 
following topics:
 rtl_433//devices[/type][/model][/subtype][/channel][/id]
 rtl_433//events
 rtl_433//states
I then subscribe to 
'rtl_433//devices[/type][/model][/subtype][/channel][/id]' as 
'type = individual'.

If you want/need to continue piping to mosquitto_pub, look at 
https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring-additional-options#msg_id_field.
 
Then you can use the 'ignore' option with the appended 'id'.

rich

On Wednesday, 16 November 2022 at 12:48:36 UTC-5 bryan...@gmail.com wrote:

> I'm currently running Weewx 4.9.1 and using WeeWX-MQTTSubscribe to capture 
> data from 2 separate RTL SDR's.  One of the RTL-SDR devices is listening on 
> 433.92 and is picking up weather data from a couple nearby weather 
> stations.  One of the weather stations I'm listening to has a bad wind 
> sensor, so I do not want the wind data from that station, the other station 
> has good wind data so I do want that data.  These two stations are from the 
> same manufacturer and fall under the same device decoding protocol ( [40] 
> Acurite 592TXR Temp/Humidity, 5n1 Weather Station, 6045 Lightning, 899 
> Rain, 3N1, Atlas).
>
> The other RTL-SDR is listening on 915.00 in order to pick up pressure data 
> from another sensor.
>
> When using 
> `rtl_433 -F json -M utc -R 40 | mosquitto_pub -t weather/radio -h 
> localhost -l`
>
> I receive all packets from both stations and pass that to the 
> WeeWX-MQTTSubscribe driver where I have set up the various fields and map 
> them to weewx.  For example, the wind data:
>
>  [[topics]]
> unit_system = US
> [[[weather/radio]]]
>
> ... snip ...
> *wind_avg_km_h*
> name = windSpeed
>
> *wind_dir_deg*
> name = windDir
>
> ... snip ...
>
> since both stations emit, for example, 'wind_avg_km_h', I don't have a way 
> to filter out one of them (the bad one) so I end up getting some garbage 
> data in the mix with good data.
>
> My question is this: since these two stations are the same 'device 
> decoding protocol' (40) is there a way to differentiate between the json 
> data coming from the one vs the other?  The both have different id 
> fields, the one I want has an ID of 3522 and the one I don't want wind data 
> from is ID 2849. 
>
> Essentially I want to keep data from both devices but exclude just the 
> wind data from one of them.
>
> Thanks much for any help you all can provide.
>
> Bryan
>

-- 
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/ef1bfb7c-0204-425d-84bf-b6b13a56bb57n%40googlegroups.com.

Re: [weewx-user] Re: WeeWX-MQTTSubscribe - Filter unwanted devices

[Bryan Parke]

Thanks for the reply, however, if I ignore it, it will ignore it entirely,
not just for the one with bad data.  Maybe you didn't see that part of my
question.  2 stations are reporting weather data with the same field name
*wind_avg_km_h * which I map to windSpeed.  One of the stations, with ID
2849 has a bad wind sensor so I want to ignore only the wind data from that
station, but want to continue to receive and map the wind data from the
other station with ID 3522.

On Wed, Nov 16, 2022 at 12:58 PM vince  wrote:

> Add ignore=true to the ones you want to.ignore...
>
> [[[ecowitt/loop]]]
> outTemp_F
> name = extraTemp1
> units = degree_F
> extraTemp5_F
> name = extraTemp5
> units = degree_F
> dateTime
> ignore = True
> usUnits
> ignore = True
>
>
> On Wednesday, November 16, 2022 at 9:48:36 AM UTC-8 bryan...@gmail.com
> wrote:
>
>> I'm currently running Weewx 4.9.1 and using WeeWX-MQTTSubscribe to
>> capture data from 2 separate RTL SDR's.  One of the RTL-SDR devices is
>> listening on 433.92 and is picking up weather data from a couple nearby
>> weather stations.  One of the weather stations I'm listening to has a bad
>> wind sensor, so I do not want the wind data from that station, the other
>> station has good wind data so I do want that data.  These two stations are
>> from the same manufacturer and fall under the same device decoding protocol
>> ( [40] Acurite 592TXR Temp/Humidity, 5n1 Weather Station, 6045 Lightning,
>> 899 Rain, 3N1, Atlas).
>>
>> The other RTL-SDR is listening on 915.00 in order to pick up pressure
>> data from another sensor.
>>
>> When using
>> `rtl_433 -F json -M utc -R 40 | mosquitto_pub -t weather/radio -h
>> localhost -l`
>>
>> I receive all packets from both stations and pass that to the
>> WeeWX-MQTTSubscribe driver where I have set up the various fields and map
>> them to weewx.  For example, the wind data:
>>
>>  [[topics]]
>> unit_system = US
>> [[[weather/radio]]]
>>
>> ... snip ...
>> *wind_avg_km_h*
>> name = windSpeed
>>
>> *wind_dir_deg*
>> name = windDir
>>
>> ... snip ...
>>
>> since both stations emit, for example, 'wind_avg_km_h', I don't have a
>> way to filter out one of them (the bad one) so I end up getting some
>> garbage data in the mix with good data.
>>
>> My question is this: since these two stations are the same 'device
>> decoding protocol' (40) is there a way to differentiate between the json
>> data coming from the one vs the other?  The both have different id
>> fields, the one I want has an ID of 3522 and the one I don't want wind data
>> from is ID 2849.
>>
>> Essentially I want to keep data from both devices but exclude just the
>> wind data from one of them.
>>
>> Thanks much for any help you all can provide.
>>
>> Bryan
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/yzk4qXDa87o/unsubscribe.
> To unsubscribe from this group and all its topics, 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/08d74afd-f68a-4f0a-a808-666498b6b4d2n%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/CAPXDAYYomuoBf-2QA98yUF-MmufPMyz1AGMO7E6frCtiyTqx1A%40mail.gmail.com.

[weewx-user] Re: WeeWX-MQTTSubscribe - Filter unwanted devices

[vince]

Add ignore=true to the ones you want to.ignore...

[[[ecowitt/loop]]]
outTemp_F
name = extraTemp1
units = degree_F
extraTemp5_F 
name = extraTemp5
units = degree_F
dateTime
ignore = True
usUnits
ignore = True


On Wednesday, November 16, 2022 at 9:48:36 AM UTC-8 bryan...@gmail.com 
wrote:

> I'm currently running Weewx 4.9.1 and using WeeWX-MQTTSubscribe to capture 
> data from 2 separate RTL SDR's.  One of the RTL-SDR devices is listening on 
> 433.92 and is picking up weather data from a couple nearby weather 
> stations.  One of the weather stations I'm listening to has a bad wind 
> sensor, so I do not want the wind data from that station, the other station 
> has good wind data so I do want that data.  These two stations are from the 
> same manufacturer and fall under the same device decoding protocol ( [40] 
> Acurite 592TXR Temp/Humidity, 5n1 Weather Station, 6045 Lightning, 899 
> Rain, 3N1, Atlas).
>
> The other RTL-SDR is listening on 915.00 in order to pick up pressure data 
> from another sensor.
>
> When using 
> `rtl_433 -F json -M utc -R 40 | mosquitto_pub -t weather/radio -h 
> localhost -l`
>
> I receive all packets from both stations and pass that to the 
> WeeWX-MQTTSubscribe driver where I have set up the various fields and map 
> them to weewx.  For example, the wind data:
>
>  [[topics]]
> unit_system = US
> [[[weather/radio]]]
>
> ... snip ...
> *wind_avg_km_h*
> name = windSpeed
>
> *wind_dir_deg*
> name = windDir
>
> ... snip ...
>
> since both stations emit, for example, 'wind_avg_km_h', I don't have a way 
> to filter out one of them (the bad one) so I end up getting some garbage 
> data in the mix with good data.
>
> My question is this: since these two stations are the same 'device 
> decoding protocol' (40) is there a way to differentiate between the json 
> data coming from the one vs the other?  The both have different id 
> fields, the one I want has an ID of 3522 and the one I don't want wind data 
> from is ID 2849. 
>
> Essentially I want to keep data from both devices but exclude just the 
> wind data from one of them.
>
> Thanks much for any help you all can provide.
>
> Bryan
>

-- 
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/08d74afd-f68a-4f0a-a808-666498b6b4d2n%40googlegroups.com.

Re: [weewx-user] Re: installing belchertown extension

[Alex Vanuxem]

Did uninstall and instal a few times. And i always use sudo.

Op wo 16 nov. 2022 18:55 schreef vince :

> Just install it again and remember to use 'sudo'.  Sheesh.
>
> On Wednesday, November 16, 2022 at 9:34:17 AM UTC-8 vanuxe...@gmail.com
> wrote:
>
>> Hi
>>
>> Thanks for your answer.
>>
>> Unfortunately nothing is there.
>>
>> The skins folder is also not updated to show belchertown.
>>
>> Please advise.
>>
>> Thx
>>
>> Alex
>>
>> Op di 15 nov. 2022 21:37 schreef vince :
>>
>>> Look for Belchertown with an upper case 'B'.
>>>
>>> You should see a long stanza for Belchertown in the StdReport section of
>>> weewx.conf
>>>
>>> On Tuesday, November 15, 2022 at 11:30:05 AM UTC-8 vanuxe...@gmail.com
>>> wrote:
>>>
 Hi all,

 I installed the belchertown skin into the wee_extension.

 if i do a --list the belchertown is listed

 i have a setup.py install

 and running weewx under a virtual box environment.

 normally i guess the weewx.conf should be updated with this extension?
 but it's not ...

 do I miss something?

 thx

 grtz

 alex

>>> --
>>> 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/af8576b1-2575-4117-b043-2cc7946e1e2cn%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/1d9b8920-cef8-4085-a9de-5395c54868cbn%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/CAHaYyoK9ATNG5YioqgRz_L2HkB6CxcTR7OPmY3cQJZN_25B5-Q%40mail.gmail.com.

Re: [weewx-user] Re: installing belchertown extension

[vince]

Just install it again and remember to use 'sudo'.  Sheesh.

On Wednesday, November 16, 2022 at 9:34:17 AM UTC-8 vanuxe...@gmail.com 
wrote:

> Hi 
>
> Thanks for your answer. 
>
> Unfortunately nothing is there.
>
> The skins folder is also not updated to show belchertown.
>
> Please advise.
>
> Thx
>
> Alex
>
> Op di 15 nov. 2022 21:37 schreef vince :
>
>> Look for Belchertown with an upper case 'B'.
>>
>> You should see a long stanza for Belchertown in the StdReport section of 
>> weewx.conf
>>
>> On Tuesday, November 15, 2022 at 11:30:05 AM UTC-8 vanuxe...@gmail.com 
>> wrote:
>>
>>> Hi all,
>>>
>>> I installed the belchertown skin into the wee_extension.
>>>
>>> if i do a --list the belchertown is listed
>>>
>>> i have a setup.py install
>>>
>>> and running weewx under a virtual box environment.
>>>
>>> normally i guess the weewx.conf should be updated with this extension?
>>> but it's not ...
>>>
>>> do I miss something?
>>>
>>> thx
>>>
>>> grtz
>>>
>>> alex
>>>
>> -- 
>> 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/af8576b1-2575-4117-b043-2cc7946e1e2cn%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/1d9b8920-cef8-4085-a9de-5395c54868cbn%40googlegroups.com.

[weewx-user] WeeWX-MQTTSubscribe - Filter unwanted devices

[bryan...@gmail.com]

I'm currently running Weewx 4.9.1 and using WeeWX-MQTTSubscribe to capture 
data from 2 separate RTL SDR's.  One of the RTL-SDR devices is listening on 
433.92 and is picking up weather data from a couple nearby weather 
stations.  One of the weather stations I'm listening to has a bad wind 
sensor, so I do not want the wind data from that station, the other station 
has good wind data so I do want that data.  These two stations are from the 
same manufacturer and fall under the same device decoding protocol ( [40] 
Acurite 592TXR Temp/Humidity, 5n1 Weather Station, 6045 Lightning, 899 
Rain, 3N1, Atlas).

The other RTL-SDR is listening on 915.00 in order to pick up pressure data 
from another sensor.

When using 
`rtl_433 -F json -M utc -R 40 | mosquitto_pub -t weather/radio -h localhost 
-l`

I receive all packets from both stations and pass that to the 
WeeWX-MQTTSubscribe driver where I have set up the various fields and map 
them to weewx.  For example, the wind data:

 [[topics]]
unit_system = US
[[[weather/radio]]]

... snip ...
*wind_avg_km_h*
name = windSpeed

*wind_dir_deg*
name = windDir

... snip ...

since both stations emit, for example, 'wind_avg_km_h', I don't have a way 
to filter out one of them (the bad one) so I end up getting some garbage 
data in the mix with good data.

My question is this: since these two stations are the same 'device decoding 
protocol' (40) is there a way to differentiate between the json data coming 
from the one vs the other?  The both have different id fields, the 
one I want has an ID of 3522 and the one I don't want wind data from is ID 
2849. 

Essentially I want to keep data from both devices but exclude just the wind 
data from one of them.

Thanks much for any help you all can provide.

Bryan

-- 
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/4340abf8-f2fa-4ec8-97ad-bc1fe6999fe6n%40googlegroups.com.

Re: [weewx-user] Re: Neowx skin sample site

[Günther Wrana]

Hallo ich schreibe einmal auf deutsch und dann die übersetzung ins 
Englische.
Ich habe nicht gewusst das man in der weewx.conf das so wie oben 
beschrieben rein schreiben muss.
Darum habe ich es so wie in meiner weewx.conf ausgeführt.
Mittlerweile funktioniert es auch mit neowx.
Ebenso bin ich kein Forum oder Gruppen Kenner darum habe ich keinen neuen 
Thread gemacht.
Ich entschuldige mich für die Umstände und danke für die Hilfe!

Danke sehr Günther


Hello I write once on german and then the translation into English.
I didn't know that you have to write in the weewx.conf as described above.
That's why I ran it as in my weewx.conf.
Meanwhile, it also works with neowx.
Likewise, I'm not a forum or group connoisseur so I didn't make a new 
thread.
I apologize for the inconvenience and thank you for the help!

Thank you very much Günther
lang@googlemail.com schrieb am Montag, 14. November 2022 um 22:45:54 
UTC+1:

> I don't know why you couldn't change or add the neowx-material skin to 
> your weewx installation.
> Probably because you didn't install the skin - or at least didn't modify 
> weewx.conf accordingly.
> That's what your weewx.conf is saying - there is no proper entry for the 
> neowx-material skin in the [StdReport] stanza.
>
> What you have obviously done is to mix up skins - made a neowx-material 
> entry inside the [[Seasons]] stanza - which won't work.
> What you are trying to do is to convert a Mercedes car into a BMW car by 
> changing the name on the car tail.
>
> What you need to have are the following entries in weewx.conf:
>
>  -- start excerpt weewx.conf [StdReport] stanza --
>
> [[neowx]]
> skin = neowx-material
> enable = true
> HTML_ROOT = /var/www/html/weewx/neowx
>
> [[SeasonsReport]]
> # The SeasonsReport uses the 'Seasons' skin, which contains the
> # images, templates and plots for the report.
> skin = Seasons
> enable = true
>
>  -- end excerpt weewx.conf [StdReport] stanza --
>
> Then you can have the seasons skin with 
> http://IP-address/weewx
> and the neowx-material skin with
> http://IP-address/weewx/neowx
>
>
> On 14.11.2022 22:28, Günther Wrana wrote:
>
> Hi 
>
> I have the .conf and a little bit from the syslog file send.
>
> Why could i not my skin canch to neowx?
>
> Thank you for all your help
>
> Günther Wrana schrieb am Donnerstag, 12. März 2020 um 07:40:18 UTC+1:
>
>>
>>  Hello this is my page http://guentherwrana.ddns.net/weewx/ but for me 
>> no values ​​are shown on the curves.
>> I would also be interested in how I change the language.
>> Could you give me a tip?
>> On the weewx.com site I have not yet figured out how to change the 
>> language of the skins.
>> Thanks Günther
>>
>>
>> Am Mittwoch, 30. Januar 2019 13:39:34 UTC+1 schrieb Alan Jackson: 
>>>
>>> I just installed it. http://www.ajackson.org/weewx
>>
>> -- 
> 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/91db6e74-6d3c-4f1a-989a-dd21517ea972n%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/5c520625-6a0a-4108-8fb1-782d2dcf2ea3n%40googlegroups.com.

Re: [weewx-user] Re: installing belchertown extension

[Alex Vanuxem]

Hi

Thanks for your answer.

Unfortunately nothing is there.

The skins folder is also not updated to show belchertown.

Please advise.

Thx

Alex

Op di 15 nov. 2022 21:37 schreef vince :

> Look for Belchertown with an upper case 'B'.
>
> You should see a long stanza for Belchertown in the StdReport section of
> weewx.conf
>
> On Tuesday, November 15, 2022 at 11:30:05 AM UTC-8 vanuxe...@gmail.com
> wrote:
>
>> Hi all,
>>
>> I installed the belchertown skin into the wee_extension.
>>
>> if i do a --list the belchertown is listed
>>
>> i have a setup.py install
>>
>> and running weewx under a virtual box environment.
>>
>> normally i guess the weewx.conf should be updated with this extension?
>> but it's not ...
>>
>> do I miss something?
>>
>> thx
>>
>> grtz
>>
>> alex
>>
> --
> 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/af8576b1-2575-4117-b043-2cc7946e1e2cn%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/CAHaYyoLhAHF-%3DPuV1baDscCkjESKwT078zptz63Qg7Sb5-BNfQ%40mail.gmail.com.

[weewx-user] Re: WeeWX 4.6.2 Working Well

[Kev D]

Hi Gary,

I have just upgraded my setup to  VP2, WifiLogger2, and Belchertown skin as 
well. Would you mind sharing your configuration setup in weewx to grab data 
from the WifiLogger2? Are you also using the interceptor driver for this 
config?

Thanks!

On Friday, February 11, 2022 at 9:00:57 AM UTC-5 gary@gmail.com wrote:

> With the rapid succession of releases, I just wanted to say that my 
> upgrade to 4.6.2 went well and all is working with the VP2, WifiLogger2, 
> and Belchertown skin.
>
> Thanks for an amazing system!
>

-- 
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/2b9cc941-ecbb-448f-b00b-893968eb59b3n%40googlegroups.com.

Re: [weewx-user] Missing values after upgrade to 4.9.1

[ris...@gmail.com]

Here:

Nov 16 17:53:09 weewxberry systemd[1]: Started WeeWX weather system.
Nov 16 17:53:11 weewxberry weewx[8109] INFO __main__: Initializing weewx 
version 4.9.1
Nov 16 17:53:11 weewxberry weewx[8109] INFO __main__: Using Python 3.9.2 
(default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
Nov 16 17:53:11 weewxberry weewx[8109] INFO __main__: Located at 
/usr/bin/python3
Nov 16 17:53:11 weewxberry weewx[8109] INFO __main__: Platform 
Linux-5.15.76+-armv6l-with-glibc2.31
Nov 16 17:53:11 weewxberry weewx[8109] INFO __main__: Locale is 
'en_GB.UTF-8'
Nov 16 17:53:11 weewxberry weewx[8109] INFO __main__: Using configuration 
file /home/weewx/weewx.conf
Nov 16 17:53:11 weewxberry weewx[8109] INFO __main__: Debug is 1
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG __main__: Initializing engine
Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.engine: Loading station 
type FineOffsetUSB (weewx.drivers.fousb)
Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.drivers.fousb: driver 
version is 1.20
Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.drivers.fousb: polling 
mode is PERIODIC
Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.drivers.fousb: polling 
interval is 60
Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.drivers.fousb: found 
station on USB bus= device=
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdTimeSynch
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.engine: StdConvert target 
unit is 0x1
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdConvert
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdCalibrate
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service 
weewx.engine.StdQC
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdQC
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.wxservices: 
StdWXCalculate will use data binding wx_binding
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.manager: Daily summary 
version is 1.0
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdWXXTypes
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdWXXTypes
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdPressureCooker
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdPressureCooker
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdRainRater
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdRainRater
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdDelta
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdDelta
Nov 16 17:53:11 weewxberry weewx[8109] DEBUG weewx.engine: Loading service 
weewx.engine.StdArchive
Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.engine: Archive will use 
data binding wx_binding
Nov 16 17:53:11 weewxberry weewx[8109] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Nov 16 17:53:12 weewxberry weewx[8109] INFO weewx.engine: Using archive 
interval of 300 seconds (specified by hardware)
Nov 16 17:53:12 weewxberry weewx[8109] DEBUG weewx.engine: Use LOOP data in 
hi/low calculations: 1
Nov 16 17:53:12 weewxberry weewx[8109] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdArchive
Nov 16 17:53:12 weewxberry weewx[8109] DEBUG weewx.engine: Loading service 
weewx.restx.StdStationRegistry
Nov 16 17:53:13 weewxberry weewx[8109] INFO weewx.restx: StationRegistry: 
Registration not requested.
Nov 16 17:53:13 weewxberry weewx[8109] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdStationRegistry
Nov 16 17:53:13 weewxberry weewx[8109] DEBUG weewx.engine: Loading service 
weewx.restx.StdWunderground
Nov 16 17:53:13 weewxberry weewx[8109] DEBUG weewx.restx: Wunderground: 
Data will not be posted: Missing option 'station'
Nov 16 17:53:13 weewxberry weewx[8109] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdWunderground
Nov 16 17:53:13 weewxberry weewx[8109] DEBUG weewx.engine: Loading service 
weewx.restx.StdPWSweather
Nov 16 17:53:13 weewxberry weewx[8109] DEBUG weewx.restx: PWSweather: Data 
will not 

Re: [weewx-user] Missing values after upgrade to 4.9.1

[Tom Keffer]

I wish you'd supplied more data, but it appears that you have at least
station pressure. NB: this is the raw pressure measured by the sensor. To
calculate "barometer" requires altitude and the outside temperature, which
you seem to have. See this article
 on
the different kinds of pressure.

That leaves one possibility: that weewx is not being directed to calculate
"barometer". Please restart weewxd, then post the log from startup through
the first reporting interval. This will give us an insight into your
configuration.

On Wed, Nov 16, 2022 at 7:23 AM ris...@gmail.com  wrote:

> Thanks. Started it from command line (debug=0) and after some time got
> several lines like (more LOOPs, occasional RECs, the value for delay seems
> to vary between 0 and 5):
>
> LOOP:   2022-11-16 17:06:09 EET (1668611169) 'dateTime': '1668611169',
> 'delay': '0', 'inHumidity': '54.0', 'inTemp': '72.14', 'outHumidity':
> '32.0', 'outTemp': '32.72', 'outTempBatteryStatus': '0', 'pressure':
> '31.0360168625', 'ptr': '13984', 'radiation': 'None', 'rain': '0.0',
> 'rainTotal': '9.81', 'rxCheckPercent': '100', 'status': '0', 'usUnits':
> '1', 'UV': 'None', 'windDir': '45.0', 'windGust': '6.039743000236122',
> 'windSpeed': '4.473883703878609'
> REC:2022-11-16 17:05:04 EET (1668611104) 'dateTime': '1668611104',
> 'delay': '5', 'inHumidity': '54.0', 'inTemp': '72.14', 'interval': '5',
> 'outHumidity': '32.0', 'outTemp': '32.72', 'outTempBatteryStatus': '0',
> 'pressure': '31.03306386375', 'ptr': '13968', 'radiation': 'None', 'rain':
> '0.0', 'rainTotal': '9.81', 'rxCheckPercent': '100', 'status': '0',
> 'usUnits': '1', 'UV': 'None', 'windDir': '45.0', 'windGust':
> '5.368660444654331', 'windSpeed': '3.802801148296818'
> LOOP:   2022-11-16 17:06:17 EET (1668611177) 'dateTime': '1668611177',
> 'delay': '1', 'inHumidity': '54.0', 'inTemp': '72.14', 'outHumidity':
> '32.0', 'outTemp': '32.72', 'outTempBatteryStatus': '0', 'pressure':
> '31.0360168625', 'ptr': '13984', 'radiation': 'None', 'rain': '0.0',
> 'rainTotal': '9.81', 'rxCheckPercent': '100', 'status': '0', 'usUnits':
> '1', 'UV': 'None', 'windDir': '45.0', 'windGust': '7.605602296593636',
> 'windSpeed': '5.368660444654331'
>
> And then lines like:
> /usr/lib/python3/dist-packages/Cheetah/Compiler.py:1686: UserWarning: You
> supplied an empty string for the source!
>   warnings.warn("You supplied an empty string for the source!", )
> after which more REC and LOOP data.
>
> Interestingly the values for barometer is shown ('pressure':
> '31.0360168625')...
>
> Then I restarted it with setting DEBUG=1, but the output on the screen was
> the same. Log entries as before.
>
> //rkv
>
>
>
>
> keskiviikko 16. marraskuuta 2022 klo 15.21.57 UTC+2 tke...@gmail.com
> kirjoitti:
>
>> It is odd that the record was recorded in the main archive table at
>> 22:12:03, but it took another 3-1/2 minutes to record it in the daily
>> summary (at 22:15:45). That would suggest something going on with the
>> database connection.
>>
>> To see if there are data values for barometer (and others), run weewxd 
>> directly
>> from the command line
>> . It will
>> print all LOOP packets and archive records. Let us know what it says.
>>
>> On Wed, Nov 16, 2022 at 1:04 AM ris...@gmail.com 
>> wrote:
>>
>>> Had a perfectly working weewx-setup on version 3.8.0 but due to other
>>> issues not disclosing now I had to move the station to another RPi device
>>> and decided to upgrade weewx to 4.9.1. Finally got it working but now some
>>> of the sensor data – e.g barometer pressure, rain fall –  is not showing
>>> any more.
>>>
>>> More details:
>>> - station FineOffset WH1080
>>> - platform Raspberry Pi 0 W (was RPi 2 B which was taken to another use)
>>> - weewx version 4.9.1 (was 3.8.0 and worked fine)
>>> - upgrade = new installation of 4.9.1 using setup.py onto /home/weewx +
>>> weewx.conf and skins copied from the old installation
>>> - data stored on a mysql DB on another server (as before)
>>> - rsync upload to local web server plus to
>>> http://www.myrskyt.org/rouhunsaa/
>>> - debug log shows no errors during report creation (see below)
>>> - missing values for barometer and rain, dew point, possibly others, the
>>> report(s) shows N/A for them, in & outTemp, total rain, wind are shown as
>>> before
>>> - e.g. the barometer value IS shown on the FineOffset display so the
>>> device is measuring it
>>>
>>> I'm a bit lost what to do next? How to see if there is actual data for
>>> e.g. barometer values coming from the station etc?  I'm quite confident
>>> that the reason must be very simple, I just can't figure it out... Or
>>> should I downgrade the sw back to 3.8.0? Any ideas?
>>>
>>> I've also noticed that the RPi 0 is a bit underpowered for the job (the
>>> log states 'another report thread running') but don't think that is the
>>> reason behind these missing values, though.

Re: [weewx-user] Missing values after upgrade to 4.9.1

[ris...@gmail.com]

Thanks. Started it from command line (debug=0) and after some time got 
several lines like (more LOOPs, occasional RECs, the value for delay seems 
to vary between 0 and 5):

LOOP:   2022-11-16 17:06:09 EET (1668611169) 'dateTime': '1668611169', 
'delay': '0', 'inHumidity': '54.0', 'inTemp': '72.14', 'outHumidity': 
'32.0', 'outTemp': '32.72', 'outTempBatteryStatus': '0', 'pressure': 
'31.0360168625', 'ptr': '13984', 'radiation': 'None', 'rain': '0.0', 
'rainTotal': '9.81', 'rxCheckPercent': '100', 'status': '0', 'usUnits': 
'1', 'UV': 'None', 'windDir': '45.0', 'windGust': '6.039743000236122', 
'windSpeed': '4.473883703878609'
REC:2022-11-16 17:05:04 EET (1668611104) 'dateTime': '1668611104', 
'delay': '5', 'inHumidity': '54.0', 'inTemp': '72.14', 'interval': '5', 
'outHumidity': '32.0', 'outTemp': '32.72', 'outTempBatteryStatus': '0', 
'pressure': '31.03306386375', 'ptr': '13968', 'radiation': 'None', 'rain': 
'0.0', 'rainTotal': '9.81', 'rxCheckPercent': '100', 'status': '0', 
'usUnits': '1', 'UV': 'None', 'windDir': '45.0', 'windGust': 
'5.368660444654331', 'windSpeed': '3.802801148296818'
LOOP:   2022-11-16 17:06:17 EET (1668611177) 'dateTime': '1668611177', 
'delay': '1', 'inHumidity': '54.0', 'inTemp': '72.14', 'outHumidity': 
'32.0', 'outTemp': '32.72', 'outTempBatteryStatus': '0', 'pressure': 
'31.0360168625', 'ptr': '13984', 'radiation': 'None', 'rain': '0.0', 
'rainTotal': '9.81', 'rxCheckPercent': '100', 'status': '0', 'usUnits': 
'1', 'UV': 'None', 'windDir': '45.0', 'windGust': '7.605602296593636', 
'windSpeed': '5.368660444654331'

And then lines like:
/usr/lib/python3/dist-packages/Cheetah/Compiler.py:1686: UserWarning: You 
supplied an empty string for the source!
  warnings.warn("You supplied an empty string for the source!", )
after which more REC and LOOP data.

Interestingly the values for barometer is shown ('pressure': 
'31.0360168625')...

Then I restarted it with setting DEBUG=1, but the output on the screen was 
the same. Log entries as before.

//rkv




keskiviikko 16. marraskuuta 2022 klo 15.21.57 UTC+2 tke...@gmail.com 
kirjoitti:

> It is odd that the record was recorded in the main archive table at 
> 22:12:03, but it took another 3-1/2 minutes to record it in the daily 
> summary (at 22:15:45). That would suggest something going on with the 
> database connection.
>
> To see if there are data values for barometer (and others), run weewxd 
> directly 
> from the command line 
> . It will 
> print all LOOP packets and archive records. Let us know what it says.
>
> On Wed, Nov 16, 2022 at 1:04 AM ris...@gmail.com  wrote:
>
>> Had a perfectly working weewx-setup on version 3.8.0 but due to other 
>> issues not disclosing now I had to move the station to another RPi device 
>> and decided to upgrade weewx to 4.9.1. Finally got it working but now some 
>> of the sensor data – e.g barometer pressure, rain fall –  is not showing 
>> any more. 
>>
>> More details:
>> - station FineOffset WH1080
>> - platform Raspberry Pi 0 W (was RPi 2 B which was taken to another use)
>> - weewx version 4.9.1 (was 3.8.0 and worked fine)
>> - upgrade = new installation of 4.9.1 using setup.py onto /home/weewx + 
>> weewx.conf and skins copied from the old installation
>> - data stored on a mysql DB on another server (as before)
>> - rsync upload to local web server plus to 
>> http://www.myrskyt.org/rouhunsaa/
>> - debug log shows no errors during report creation (see below)
>> - missing values for barometer and rain, dew point, possibly others, the 
>> report(s) shows N/A for them, in & outTemp, total rain, wind are shown as 
>> before
>> - e.g. the barometer value IS shown on the FineOffset display so the 
>> device is measuring it
>>
>> I'm a bit lost what to do next? How to see if there is actual data for 
>> e.g. barometer values coming from the station etc?  I'm quite confident 
>> that the reason must be very simple, I just can't figure it out... Or 
>> should I downgrade the sw back to 3.8.0? Any ideas?
>>
>> I've also noticed that the RPi 0 is a bit underpowered for the job (the 
>> log states 'another report thread running') but don't think that is the 
>> reason behind these missing values, though.
>>
>> Log excerpt:
>> Nov 15 22:11:06 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: get 631 
>> records since 2022-11-15 20:08:30
>> Nov 15 22:11:06 weewxberry weewx[4685] INFO weewx.drivers.fousb: 
>> synchronising to the weather station (quality=1)
>> Nov 15 22:11:45 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: status 
>> {'rain_overflow': 0, 'lost_connection': 0, 'unknown': 0} (0)
>> Nov 15 22:11:46 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: avoid 
>> 5.853596448898315
>> Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: new data
>> Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: packet 
>> timestamp is 20:11:49
>> Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: 

Re: [weewx-user] Missing values after upgrade to 4.9.1

[Tom Keffer]

It is odd that the record was recorded in the main archive table at
22:12:03, but it took another 3-1/2 minutes to record it in the daily
summary (at 22:15:45). That would suggest something going on with the
database connection.

To see if there are data values for barometer (and others), run weewxd directly
from the command line
. It will print
all LOOP packets and archive records. Let us know what it says.

On Wed, Nov 16, 2022 at 1:04 AM ris...@gmail.com  wrote:

> Had a perfectly working weewx-setup on version 3.8.0 but due to other
> issues not disclosing now I had to move the station to another RPi device
> and decided to upgrade weewx to 4.9.1. Finally got it working but now some
> of the sensor data – e.g barometer pressure, rain fall –  is not showing
> any more.
>
> More details:
> - station FineOffset WH1080
> - platform Raspberry Pi 0 W (was RPi 2 B which was taken to another use)
> - weewx version 4.9.1 (was 3.8.0 and worked fine)
> - upgrade = new installation of 4.9.1 using setup.py onto /home/weewx +
> weewx.conf and skins copied from the old installation
> - data stored on a mysql DB on another server (as before)
> - rsync upload to local web server plus to
> http://www.myrskyt.org/rouhunsaa/
> - debug log shows no errors during report creation (see below)
> - missing values for barometer and rain, dew point, possibly others, the
> report(s) shows N/A for them, in & outTemp, total rain, wind are shown as
> before
> - e.g. the barometer value IS shown on the FineOffset display so the
> device is measuring it
>
> I'm a bit lost what to do next? How to see if there is actual data for
> e.g. barometer values coming from the station etc?  I'm quite confident
> that the reason must be very simple, I just can't figure it out... Or
> should I downgrade the sw back to 3.8.0? Any ideas?
>
> I've also noticed that the RPi 0 is a bit underpowered for the job (the
> log states 'another report thread running') but don't think that is the
> reason behind these missing values, though.
>
> Log excerpt:
> Nov 15 22:11:06 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: get 631
> records since 2022-11-15 20:08:30
> Nov 15 22:11:06 weewxberry weewx[4685] INFO weewx.drivers.fousb:
> synchronising to the weather station (quality=1)
> Nov 15 22:11:45 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: status
> {'rain_overflow': 0, 'lost_connection': 0, 'unknown': 0} (0)
> Nov 15 22:11:46 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: avoid
> 5.853596448898315
> Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: new data
> Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: packet
> timestamp is 20:11:49
> Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: log
> timestamp is 20:11:01
> Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb:
> synchronised to 2022-11-15 20:11:01 for ptr 0x2860
> Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: found 1
> archive records
> Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb:
> returning archive record 1668543061
> Nov 15 22:12:03 weewxberry weewx[4685] INFO weewx.manager: Added record
> 2022-11-15 22:11:01 EET (1668543061) to database 'weewxdb'
> Nov 15 22:15:45 weewxberry weewx[4685] INFO weewx.manager: Added record
> 2022-11-15 22:11:01 EET (1668543061) to daily summary in 'weewxdb'
> Nov 15 22:15:45 weewxberry weewx[4685] DEBUG weewx.reportengine: Running
> reports for latest time in the database.
> Nov 15 22:15:45 weewxberry weewx[4685] DEBUG weewx.reportengine: Running
> report 'StandardReport'
> Nov 15 22:15:46 weewxberry weewx[4685] DEBUG weewx.reportengine: Found
> configuration file /home/weewx/skins/Rouhunsaa/skin.conf for report
> 'StandardReport'
> Nov 15 22:15:46 weewxberry weewx[4685] DEBUG weewx.cheetahgenerator: Using
> search list ['weewx.cheetahgenerator.Almanac',
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.DisplayOptions',
> 'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext',
> 'weewx.cheetahgenerator.JSONHelpers', 'weewx.cheetahgenerator.PlotInfo',
> 'weewx.cheetahgenerator.SkinInfo', 'weewx.cheetahgenerator.Station',
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo']
> Nov 15 22:15:46 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: avoid
> 5.997039079666138
> Nov 15 22:15:46 weewxberry weewx[4685] DEBUG weewx.manager: Daily summary
> version is 1.0
> Nov 15 22:15:53 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: get 631
> records since 2022-11-15 20:13:31
> Nov 15 22:15:53 weewxberry weewx[4685] INFO weewx.drivers.fousb:
> synchronising to the weather station (quality=1)
> Nov 15 22:15:57 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: status
> {'rain_overflow': 0, 'lost_connection': 0, 'unknown': 0} (0)
> Nov 15 22:15:57 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: avoid
> 5.782605409622192
> Nov 15 22:16:03 weewxberry weewx[4685] DEBUG 

[weewx-user] Calculating rain delta

[bell...@gmail.com]

MQTTSubscribe has support for calculating the delta value of an observation 
from the total. I know WeeWX added this support and want to move people to 
use the built-in support (or at least have new users use it). I wasn’t able 
to find much information on it, so just looking to verify some information.

   1. This was added in 4.9.2 (issue #491)
   2. To use it, the following needs to be added to weewx.conf (with the 
   correct ‘input name’).

   [StdWXCalculate]

 [[Delta]]

[[[rain]]]

input = totalRain

Thanks. rich

-- 
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/d05b7ec6-b861-4549-aeef-1d9e7e47f088n%40googlegroups.com.

[weewx-user] Evaporation Belchertown Skin

['Sebastian Eckelmann' via weewx-user]

Hello everyone, 

I have a question. My weather station or weewx Season Skin shows me the 
evaporation. How can I make this visible in the Belchertown skin? I would 
be very grateful for help and information. 

Greetings Sebastian

-- 
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/dbe7f1bc-443b-400d-9bc4-42627d8ad9b1n%40googlegroups.com.

[weewx-user] Missing values after upgrade to 4.9.1

[ris...@gmail.com]

Had a perfectly working weewx-setup on version 3.8.0 but due to other 
issues not disclosing now I had to move the station to another RPi device 
and decided to upgrade weewx to 4.9.1. Finally got it working but now some 
of the sensor data – e.g barometer pressure, rain fall –  is not showing 
any more. 

More details:
- station FineOffset WH1080
- platform Raspberry Pi 0 W (was RPi 2 B which was taken to another use)
- weewx version 4.9.1 (was 3.8.0 and worked fine)
- upgrade = new installation of 4.9.1 using setup.py onto /home/weewx + 
weewx.conf and skins copied from the old installation
- data stored on a mysql DB on another server (as before)
- rsync upload to local web server plus to http://www.myrskyt.org/rouhunsaa/
- debug log shows no errors during report creation (see below)
- missing values for barometer and rain, dew point, possibly others, the 
report(s) shows N/A for them, in & outTemp, total rain, wind are shown as 
before
- e.g. the barometer value IS shown on the FineOffset display so the device 
is measuring it

I'm a bit lost what to do next? How to see if there is actual data for e.g. 
barometer values coming from the station etc?  I'm quite confident that the 
reason must be very simple, I just can't figure it out... Or should I 
downgrade the sw back to 3.8.0? Any ideas?

I've also noticed that the RPi 0 is a bit underpowered for the job (the log 
states 'another report thread running') but don't think that is the reason 
behind these missing values, though.

Log excerpt:
Nov 15 22:11:06 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: get 631 
records since 2022-11-15 20:08:30
Nov 15 22:11:06 weewxberry weewx[4685] INFO weewx.drivers.fousb: 
synchronising to the weather station (quality=1)
Nov 15 22:11:45 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: status 
{'rain_overflow': 0, 'lost_connection': 0, 'unknown': 0} (0)
Nov 15 22:11:46 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: avoid 
5.853596448898315
Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: new data
Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: packet 
timestamp is 20:11:49
Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: log 
timestamp is 20:11:01
Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: 
synchronised to 2022-11-15 20:11:01 for ptr 0x2860
Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: found 1 
archive records
Nov 15 22:11:52 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: returning 
archive record 1668543061
Nov 15 22:12:03 weewxberry weewx[4685] INFO weewx.manager: Added record 
2022-11-15 22:11:01 EET (1668543061) to database 'weewxdb'
Nov 15 22:15:45 weewxberry weewx[4685] INFO weewx.manager: Added record 
2022-11-15 22:11:01 EET (1668543061) to daily summary in 'weewxdb'
Nov 15 22:15:45 weewxberry weewx[4685] DEBUG weewx.reportengine: Running 
reports for latest time in the database.
Nov 15 22:15:45 weewxberry weewx[4685] DEBUG weewx.reportengine: Running 
report 'StandardReport'
Nov 15 22:15:46 weewxberry weewx[4685] DEBUG weewx.reportengine: Found 
configuration file /home/weewx/skins/Rouhunsaa/skin.conf for report 
'StandardReport'
Nov 15 22:15:46 weewxberry weewx[4685] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.DisplayOptions', 
'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext', 
'weewx.cheetahgenerator.JSONHelpers', 'weewx.cheetahgenerator.PlotInfo', 
'weewx.cheetahgenerator.SkinInfo', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo']
Nov 15 22:15:46 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: avoid 
5.997039079666138
Nov 15 22:15:46 weewxberry weewx[4685] DEBUG weewx.manager: Daily summary 
version is 1.0
Nov 15 22:15:53 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: get 631 
records since 2022-11-15 20:13:31
Nov 15 22:15:53 weewxberry weewx[4685] INFO weewx.drivers.fousb: 
synchronising to the weather station (quality=1)
Nov 15 22:15:57 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: status 
{'rain_overflow': 0, 'lost_connection': 0, 'unknown': 0} (0)
Nov 15 22:15:57 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: avoid 
5.782605409622192
Nov 15 22:16:03 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: new ptr: 
002880 (002870)
Nov 15 22:16:04 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: packet 
timestamp is 20:16:00
Nov 15 22:16:04 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: 
synchronised to 2022-11-15 20:16:00 for ptr 0x2870
Nov 15 22:16:04 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: found 1 
archive records
Nov 15 22:16:04 weewxberry weewx[4685] DEBUG weewx.drivers.fousb: returning 
archive record 1668543360
Nov 15 22:16:04 weewxberry weewx[4685] INFO weewx.manager: Added record 
2022-11-15 22:16:00 EET (1668543360) to database 'weewxdb'
Nov 15 22:16:04 weewxberry weewx[4685] INFO weewx.manager: Added