[weewx-user] GW-1000 driver error Critical self.get_live_sensor_data

[Larry]

My weewx using GW-1000 on Pi Zero W worked fine for years  until last 
update of Weewx. I couldn't seem to get all the issues figured out so I 
just made a fresh install of newest Bullseye lite ( no desktop) and set it 
all up for Weewx , Apache2, and the latest GW-1000 driver . I couldnt' get 
the real time clock to work on Pi following instructions I used to use so 
it is just with normal Pi clock now. Not sure if errors are from time issue 
? 
I get the following errors 
Any ideas on how I should resolve this  ? 

Thanks 


Mar  5 22:23:38 weewx weewx[726] CRITICAL user.gw1000:  
 queue_data = self.get_live_sensor_data()
Mar  5 22:23:38 weewx weewx[726] CRITICAL user.gw1000: File 
"/usr/share/weewx/user/gw1000.py", line 2510, in get_live_sensor_data
Mar  5 22:23:38 weewx weewx[726] CRITICAL user.gw1000:  
 raw_data = self.station.get_livedata()
Mar  5 22:23:38 weewx weewx[726] CRITICAL user.gw1000: File 
"/usr/share/weewx/user/gw1000.py", line 3434, in get_livedata
Mar  5 22:23:38 weewx weewx[726] CRITICAL user.gw1000:   if not 
self.rediscover():
Mar  5 22:23:38 weewx weewx[726] CRITICAL user.gw1000: File 
"/usr/share/weewx/user/gw1000.py", line 3928, in rediscover
Mar  5 22:23:38 weewx weewx[726] CRITICAL user.gw1000:  
 gw1000_str = ', '.join([':'.join(['%s:%d' % b]) for b in device_list])
Mar  5 22:23:38 weewx weewx[726] CRITICAL user.gw1000: File 
"/usr/share/weewx/user/gw1000.py", line 3928, in 
Mar  5 22:23:38 weewx weewx[726] CRITICAL user.gw1000:  
 gw1000_str = ', '.join([':'.join(['%s:%d' % b]) for b in device_list])
Mar  5 22:23:38 weewx weewx[726] CRITICAL user.gw1000:   TypeError: 
not enough arguments for format string
Mar  5 22:41:45 weewx systemd[1]: Started Session 5 of user pi.
Mar  5 22:42:01 weewx systemd[1]: Started Session 6 of user pi.

-- 
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/8f178c34-0d50-48c7-87d9-ed5453a4e04bn%40googlegroups.com.

[weewx-user] Re: Monitoring WeeWX with Nagios

[Rob Cranfill]

I would like to monitor WeeWX with Nagios, too, but find the referenced 
page no longer there ("This site can't be reached"). If this isn't just a 
temporary outage, does anyone know where else this code might be found? I 
think I found his GitHub page but it's not there, I think.

On Saturday, May 23, 2020 at 7:15:25 PM UTC-7 Xant wrote:

> Update
>
> Matthew Wall nagios plugin works.
>

-- 
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/43399498-06ab-466c-b26a-3998f8278e98n%40googlegroups.com.

[weewx-user] Re: How to get both lux and radiation values in the report?

[gjr80]

The same general approach can be applied to any driver; (1) configure the 
driver to provide whatever observations you require (in the case of SDR 
this involves setting up the sensor map, likewise for the interceptor 
driver, other drivers you may need to do nothing) (2) if WeeWX cannot 
calculate your derived observation using StdWxCalculate 
 you can use  
StdCalibrate to calculate simple derived observations.

I can't say what you need to put in the interceptor driver sensor map, this 
depends on how you are using the interceptor driver (it operates in a 
number of modes) and what hardware you are intercepting. Once you have the 
observation data being emitted from the interceptor driver just use that 
field name in StdCalibrate.

C to F is a little different, WeeWX knows how to convert from C to F and F 
to C but it does not know how to convert between W/m2 and lux. For 
temperature you can just use a tag in a report to specify whether you want 
C or F and WeeWX will automatically handle the conversion, formatting and 
labeling, so you could use:

$current.outTemp.degree_C ($current.outTemp.degree_F)

to display something like:

35.2 C (95.4 F)

Since WeeWX does not know how to convert between W/m2 and lux to do the 
same for radiation and luminosity you need to calculate luminosity 
yourself, either through StdCalibrate or some other method (a service or an 
xtype), and then add luminosity to a unit group (the extensions.py 
additions mentioned earlier) and then you could use something like:

$current.radiation ($current.luminosity)

to display something like

520 W/m2 (65884 lux)

In this case WeeWX is really just handling the formatting and labeling.

Gary
On Saturday, 5 March 2022 at 22:26:36 UTC+10 f4n...@gmail.com wrote:

> Thanks a lot Gary, this was somehow better to understand for me than in 
> the Customization Guide.
>
> And it works, now the zeros behind the dot are gone. My SDR setup is 
> displaying both lx and w/m2 fine now. This was rather easy to do with just 
> adding it a second time to the sensor map and adding the right conversions, 
> but now I wonder how I could achieve this on the Interceptor driver 
> instance too?  
>
> Could I just add radiation = radiation, as well as luminosity = 
> radiation*126,7 to the corrections section or is there more needed to 
> generate a second plot for it? Kind of like when someone would want to 
> output the temperature both in celsius and farenheit, how is this done?
>
> gjr80 schrieb am Samstag, 5. März 2022 um 00:50:21 UTC+1:
>
>> Before I answer a quick WeeWX units 101. The WeeWX unit system is the 
>> core that allows WeeWX to convert between units (eg C to F), format 
>> observation data in reports and add unit labels. The system is predicated 
>> on each observation being allocated to a unit group (eg outTemp, inTemp, 
>> dewpoint etc are allocated to group_temperature). In essence this tells 
>> WeeWX that each of these observations are a temperature, so WeeWX knows how 
>> to convert to other temperature units, format the numeric data and what 
>> unit labels to use.
>>
>> There is a bit of history to light related observations in WeeWX. Without 
>> going into the details the WeeWX extended schema includes a field named 
>> illuminance that belongs to group_illuminance which uses the unit lux. 
>> There is no field named luminosity in the WeeWX extended schema. 
>> Consequently, when you use a field named luminosity in reports and plots 
>> etc WeeWX will still happily display the data but you don't get any unit 
>> labels, formatting of numeric values, unit conversion etc. So how to fix? 
>> Simple, you need to tell WeeWX about the data in field luminosity. This 
>> is covered to a certain extent in the Customization Guide under the section 
>> Customizing 
>> units and unit groups 
>> . In your case 
>> though the preferred approach would be to add a couple of lines to 
>> extensions.py 
>> (located in /home/weewx/bin/user or /usr/share/weewx/user depending on 
>> your WeeWX install), something like the following should work (untested): 
>>
>> import weewx.units
>> weewx.units.obs_group_dict['luminosity'] = 'group_illuminance'
>>
>> Save extensions.py and restart WeeWX. Your plots and reports should now 
>> contain properly formatted/labelled luminosity data.
>>
>> Gary
>> On Thursday, 3 March 2022 at 21:36:16 UTC+10 f4n...@gmail.com wrote:
>>
>>> It was the skin.conf, now they appear, thanks!
>>>
>>> Is there a way to add "lux" to the lux reading in the graph and current 
>>> conditions list? Could i just add it in weewx.conf?
>>>
>>> In the current conditions list, the lux number reads like this 
>>> "70070.00". 
>>> Can i add something like lux = %.1f to weewx.conf?
>>>
>>>
>>>
>>>
>>> gjr80 schrieb am Mittwoch, 2. März 2022 um 00:27:57 UTC+1:
>>>
 The only real definitive way of determining what schema you are 

Re: [weewx-user] Customizing WeeWX Webpage

[Tom Keffer]

What skin are you using? The *Seasons* skin should autoconfigure for things
like that.

Also, did you take a look through the *Customization Guide
*?

On Sat, Mar 5, 2022 at 10:53 AM 'Frank Pioch' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Hi,
>
> I've started yesterday night with weewx and sdr.py after my Bresser 5in1
> arrived, after updating sdr.py to latest version, it's working nicely.
> Thanks to all that made it possible.
>
> But now I'm stuck in customizing the web-pageI've read the
> https://weewx.com/docs/usersguide.htm...but I'm totaly confused and
> frustrated.
>
> Where is the howto guid to do that?
> The bresser 5 in1 does not have UV, does not have baro, has not indoor
> temperature, in dorr humidtiyhow to blank it out?
> There are nice showcases...but no expample how to manage it?
>
> best regards
> Frank
>
> --
> 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/99b556f3-1886-4aa6-a6c7-809211a6a2c5n%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/CAPq0zEBOqvjVKbnNKFd59n%3DmfRFRqFy_yWR%2BbS%2B72DuTGG5RgA%40mail.gmail.com.

Re: [weewx-user] Weewx 4.7.0 & Weewx -WD

[Tom Keffer]

See if this thread helps:
https://groups.google.com/g/weewx-user/c/rnLNpNoX0U0/m/stFp0t_MEAAJ

On Sat, Mar 5, 2022 at 8:41 AM Stefanos Kalaitzis <
stefanoskalait...@gmail.com> wrote:

> Hi everyone...I am running weewx with sdr driver  I decided to update from
> weewx 4.2.0 to 4.7.0 and i have several errors in Clientraw skinIt
> doesnt generate the clientraw.txt but all the others clientrawhour,-daily -
> extra are generated.In the 4.2.0 version evrything was flawless .I also
> made a clean install of weewx 4.7.0 and the errors are the same ... I kept
> the log from 4.7.0 and i downgraded again to the old version. If someone
> knows whats going on i would appreciate it.
>  I didnt make any change to weewx.conf after the update .
>
> Thank you in advanced
>
> --
> 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/b200d823-4ee6-4e64-8164-b531a227d54bn%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/CAPq0zEDR-MbT_t6cPQw1tMpqr4V6t%3DuHHVuB6m6VSpArGRKx4g%40mail.gmail.com.

Re: [weewx-user] no rain data available

[Tom Keffer]

No offense!

We're waiting for Matthew to take a look.

On Sat, Mar 5, 2022 at 11:18 AM jschoonh  wrote:

> Hey Tom,
> I don't mean to offend you, but may I ask if anything is known? Or can I
> do something?
>
> Op woensdag 2 maart 2022 om 23:39:31 UTC+3 schreef jschoonh:
>
>> I do understand and I'm happy that there is support. Hope to "speak" to
>> you soon
>> Op woensdag 2 maart 2022 om 22:40:01 UTC+3 schreef tke...@gmail.com:
>>
>>> I think we're going to have to wait for Matthew to return. Sorry I
>>> couldn't be of more help!
>>>
>>> On Wed, Mar 2, 2022 at 11:14 AM jschoonh  wrote:
>>>
 hey tom,
 I quickly made a kind of skin. The first line is from the tmpl file.
 The 2 lines below the result before water entered the rain gauge and after.
 The time is there. According to the console, about 1.5 mm of rain has
 entered the rain gauge. all "rain.sum" variants have not changed the
 "$hour,rain.sum" remains empty even after 10 minutes those values will not
 changed.
 Below terminal log, The rainTotal value from 68.116 has
 changed to 68,272 = 0.155 a values I don't quite understand could be a
 decimal error?. "rain" remains "none" "rainrate" = 0.155.
 At the time of the "rec" loop I see 'rain': 'None', 'rainRate': '0.0',
 'rainTotal': '94.0688' and the time 2 minutes back?
 Next loop 'rain': 'None', 'rainRate': '0.155', 'rainTotal': '68.272'

 the last dabase record is the same time as "rec" loop 2022-03-02
 21:18:21 no change in the "rain = null"  rainrate = 0.0


 -
 neerslag , $hour.rain.sum.raw , $span($day_delta=1).rain.sum.raw ,
 $day.rain.sum.raw , $day.rain.sum.raw , $rainyear.rain.sum.raw

 tijd , 21:08 , 02.03.2022
 neerslag ,  , 21.2379886 , 21.2379886 ,
 21.2379886 , 496.762006

 tijd , 21:18 , 02.03.2022
 neerslag ,  , 21.2379886 , 21.2379886 ,
 21.2379886 , 496.762006


 

 REC:2022-03-02 21:13:08 +03 (1646244788) 'altimeter':
 '1001.8299536233475', 'appTemp': '16.656587610543724', 'barometer':
 '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime':
 '1646244788', 'dewpoint': '9.363369846724652', 'ET': 'None', 'heatindex':
 '16.542223', 'humidex': '18.189898859284828', 'inDewpoint':
 '14.573533344814903', 'inHumidity': '57.0', 'inTemp': '23.6', 'interval':
 '5', 'maxSolarRad': 'None', 'outHumidity': '60', 'outTemp':
 '17.203', 'pressure': '993.2', 'rain': 'None', 'rainRate':
 '0.0', 'rainTotal': '93.9134', 'usUnits': '16', 'windchill':
 '17.203', 'windDir': '67.5', 'windGust': 'None', 'windGustDir':
 'None', 'windrun': '0.18002', 'windSpeed': '2.16'
 LOOP:   2022-03-02 21:16:11 +03 (1646244971) 'altimeter':
 '1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer':
 '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime':
 '1646244971', 'dewpoint': '9.38', 'ET': 'None', 'heatindex':
 '16.545', 'humidex': '18.189898859284824', 'inDewpoint':
 '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7',
 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2',
 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal':
 '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir':
 'None', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None',
 'windSpeed': '0.0'
 LOOP:   2022-03-02 21:16:20 +03 (1646244980) 'altimeter':
 '1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer':
 '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime':
 '1646244980', 'dewpoint': '9.38', 'ET': 'None', 'heatindex':
 '16.545', 'humidex': '18.189898859284824', 'inDewpoint':
 '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7',
 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2',
 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal':
 '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir':
 'None', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None',
 'windSpeed': '0.0'
 LOOP:   2022-03-02 21:16:32 +03 (1646244992) 'altimeter':
 '1001.8299536233475', 'appTemp': '16.51658761043172', 'barometer':
 '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime':
 '1646244992', 'dewpoint': '9.38', 'ET': 'None', 'heatindex':
 '16.545', 'humidex': '18.189898859284824', 'inDewpoint':
 '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7',
 'maxSolarRad': 'None', 'outHumidity': 

Re: [weewx-user] no rain data available

[jschoonh]

Hey Tom,
I don't mean to offend you, but may I ask if anything is known? Or can I do 
something?

Op woensdag 2 maart 2022 om 23:39:31 UTC+3 schreef jschoonh:

> I do understand and I'm happy that there is support. Hope to "speak" to 
> you soon
> Op woensdag 2 maart 2022 om 22:40:01 UTC+3 schreef tke...@gmail.com:
>
>> I think we're going to have to wait for Matthew to return. Sorry I 
>> couldn't be of more help!
>>
>> On Wed, Mar 2, 2022 at 11:14 AM jschoonh  wrote:
>>
>>> hey tom,
>>> I quickly made a kind of skin. The first line is from the tmpl file. The 
>>> 2 lines below the result before water entered the rain gauge and after. The 
>>> time is there. According to the console, about 1.5 mm of rain has entered 
>>> the rain gauge. all "rain.sum" variants have not changed the 
>>> "$hour,rain.sum" remains empty even after 10 minutes those values will not 
>>> changed.
>>> Below terminal log, The rainTotal value from 68.116 has 
>>> changed to 68,272 = 0.155 a values I don't quite understand could be a 
>>> decimal error?. "rain" remains "none" "rainrate" = 0.155.
>>> At the time of the "rec" loop I see 'rain': 'None', 'rainRate': '0.0', 
>>> 'rainTotal': '94.0688' and the time 2 minutes back?
>>> Next loop 'rain': 'None', 'rainRate': '0.155', 'rainTotal': '68.272'
>>>
>>> the last dabase record is the same time as "rec" loop 2022-03-02 
>>> 21:18:21 no change in the "rain = null"  rainrate = 0.0
>>>
>>>
>>> -
>>> neerslag , $hour.rain.sum.raw , $span($day_delta=1).rain.sum.raw , 
>>> $day.rain.sum.raw , $day.rain.sum.raw , $rainyear.rain.sum.raw
>>>
>>> tijd , 21:08 , 02.03.2022
>>> neerslag ,  , 21.2379886 , 21.2379886 , 
>>> 21.2379886 , 496.762006
>>>
>>> tijd , 21:18 , 02.03.2022
>>> neerslag ,  , 21.2379886 , 21.2379886 , 
>>> 21.2379886 , 496.762006
>>>
>>>
>>> 
>>>
>>> REC:2022-03-02 21:13:08 +03 (1646244788) 'altimeter': 
>>> '1001.8299536233475', 'appTemp': '16.656587610543724', 'barometer': 
>>> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
>>> '1646244788', 'dewpoint': '9.363369846724652', 'ET': 'None', 'heatindex': 
>>> '16.542223', 'humidex': '18.189898859284828', 'inDewpoint': 
>>> '14.573533344814903', 'inHumidity': '57.0', 'inTemp': '23.6', 'interval': 
>>> '5', 'maxSolarRad': 'None', 'outHumidity': '60', 'outTemp': 
>>> '17.203', 'pressure': '993.2', 'rain': 'None', 'rainRate': 
>>> '0.0', 'rainTotal': '93.9134', 'usUnits': '16', 'windchill': 
>>> '17.203', 'windDir': '67.5', 'windGust': 'None', 'windGustDir': 
>>> 'None', 'windrun': '0.18002', 'windSpeed': '2.16'
>>> LOOP:   2022-03-02 21:16:11 +03 (1646244971) 'altimeter': 
>>> '1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer': 
>>> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
>>> '1646244971', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
>>> '16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
>>> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
>>> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
>>> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
>>> '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir': 
>>> 'None', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None', 
>>> 'windSpeed': '0.0'
>>> LOOP:   2022-03-02 21:16:20 +03 (1646244980) 'altimeter': 
>>> '1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer': 
>>> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
>>> '1646244980', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
>>> '16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
>>> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
>>> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
>>> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
>>> '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir': 
>>> 'None', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None', 
>>> 'windSpeed': '0.0'
>>> LOOP:   2022-03-02 21:16:32 +03 (1646244992) 'altimeter': 
>>> '1001.8299536233475', 'appTemp': '16.51658761043172', 'barometer': 
>>> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
>>> '1646244992', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
>>> '16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
>>> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
>>> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
>>> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
>>> '68.116999', 'usUnits': '16', 

Re: [weewx-user] no rain data available

[jschoonh]

Hey Ton,
I don't mean to offend you, but may I ask if anything is known? Or can I do 
something?

Op woensdag 2 maart 2022 om 23:39:31 UTC+3 schreef jschoonh:

> I do understand and I'm happy that there is support. Hope to "speak" to 
> you soon
> Op woensdag 2 maart 2022 om 22:40:01 UTC+3 schreef tke...@gmail.com:
>
>> I think we're going to have to wait for Matthew to return. Sorry I 
>> couldn't be of more help!
>>
>> On Wed, Mar 2, 2022 at 11:14 AM jschoonh  wrote:
>>
>>> hey tom,
>>> I quickly made a kind of skin. The first line is from the tmpl file. The 
>>> 2 lines below the result before water entered the rain gauge and after. The 
>>> time is there. According to the console, about 1.5 mm of rain has entered 
>>> the rain gauge. all "rain.sum" variants have not changed the 
>>> "$hour,rain.sum" remains empty even after 10 minutes those values will not 
>>> changed.
>>> Below terminal log, The rainTotal value from 68.116 has 
>>> changed to 68,272 = 0.155 a values I don't quite understand could be a 
>>> decimal error?. "rain" remains "none" "rainrate" = 0.155.
>>> At the time of the "rec" loop I see 'rain': 'None', 'rainRate': '0.0', 
>>> 'rainTotal': '94.0688' and the time 2 minutes back?
>>> Next loop 'rain': 'None', 'rainRate': '0.155', 'rainTotal': '68.272'
>>>
>>> the last dabase record is the same time as "rec" loop 2022-03-02 
>>> 21:18:21 no change in the "rain = null"  rainrate = 0.0
>>>
>>>
>>> -
>>> neerslag , $hour.rain.sum.raw , $span($day_delta=1).rain.sum.raw , 
>>> $day.rain.sum.raw , $day.rain.sum.raw , $rainyear.rain.sum.raw
>>>
>>> tijd , 21:08 , 02.03.2022
>>> neerslag ,  , 21.2379886 , 21.2379886 , 
>>> 21.2379886 , 496.762006
>>>
>>> tijd , 21:18 , 02.03.2022
>>> neerslag ,  , 21.2379886 , 21.2379886 , 
>>> 21.2379886 , 496.762006
>>>
>>>
>>> 
>>>
>>> REC:2022-03-02 21:13:08 +03 (1646244788) 'altimeter': 
>>> '1001.8299536233475', 'appTemp': '16.656587610543724', 'barometer': 
>>> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
>>> '1646244788', 'dewpoint': '9.363369846724652', 'ET': 'None', 'heatindex': 
>>> '16.542223', 'humidex': '18.189898859284828', 'inDewpoint': 
>>> '14.573533344814903', 'inHumidity': '57.0', 'inTemp': '23.6', 'interval': 
>>> '5', 'maxSolarRad': 'None', 'outHumidity': '60', 'outTemp': 
>>> '17.203', 'pressure': '993.2', 'rain': 'None', 'rainRate': 
>>> '0.0', 'rainTotal': '93.9134', 'usUnits': '16', 'windchill': 
>>> '17.203', 'windDir': '67.5', 'windGust': 'None', 'windGustDir': 
>>> 'None', 'windrun': '0.18002', 'windSpeed': '2.16'
>>> LOOP:   2022-03-02 21:16:11 +03 (1646244971) 'altimeter': 
>>> '1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer': 
>>> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
>>> '1646244971', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
>>> '16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
>>> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
>>> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
>>> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
>>> '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir': 
>>> 'None', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None', 
>>> 'windSpeed': '0.0'
>>> LOOP:   2022-03-02 21:16:20 +03 (1646244980) 'altimeter': 
>>> '1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer': 
>>> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
>>> '1646244980', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
>>> '16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
>>> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
>>> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
>>> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
>>> '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir': 
>>> 'None', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None', 
>>> 'windSpeed': '0.0'
>>> LOOP:   2022-03-02 21:16:32 +03 (1646244992) 'altimeter': 
>>> '1001.8299536233475', 'appTemp': '16.51658761043172', 'barometer': 
>>> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
>>> '1646244992', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
>>> '16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
>>> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
>>> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
>>> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
>>> '68.116999', 'usUnits': '16', 

[weewx-user] Customizing WeeWX Webpage

['Frank Pioch' via weewx-user]

Hi,

I've started yesterday night with weewx and sdr.py after my Bresser 5in1 
arrived, after updating sdr.py to latest version, it's working nicely. 
Thanks to all that made it possible.

But now I'm stuck in customizing the web-pageI've read the 
https://weewx.com/docs/usersguide.htm...but I'm totaly confused and 
frustrated.

Where is the howto guid to do that? 
The bresser 5 in1 does not have UV, does not have baro, has not indoor 
temperature, in dorr humidtiyhow to blank it out? 
There are nice showcases...but no expample how to manage it?

best regards
Frank

-- 
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/99b556f3-1886-4aa6-a6c7-809211a6a2c5n%40googlegroups.com.

Re: [weewx-user] weewx writing too much to systemd journal

[Cat22]

Now I am running 4.7.0 and still log_success = false works and I can enable 
StdPrint and I am still good to go
I updated the service file:
[Unit] 
Description=weewx weather system 
Requires=time-sync.target 
After=time-sync.target 

[Service] 
ExecStart=/usr/local/bin/weewx/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid   /usr/local/bin/weewx/weewx.conf 
ExecReload=/usr/bin/killall -TERM $MAINPID 
Type=forking 
PIDFile=/var/run/weewx.pid 
Restart=on-failure 
RestartSec=100s 

[Install] 
WantedBy=multi-user.target

and it starts and runs great# /usr/local/bin/weewx/bin/weewxd --version 
4.7.0
But i still have StdPrint disabled

I will let it run and check back after an hour or so to be sure it is still 
quiet, but I think it will be
On Wednesday, March 2, 2022 at 10:08:04 AM UTC-8 Cat22 wrote:

> I was mistaken, when i use --daemon it crashes - always
> The import serial thing, i did that on the cmd line.
> I removed StdPrint and --daemon and it works without excess logging 
> I am in the process of upgrading to 4.7 now
>
>
> On Wednesday, March 2, 2022 at 9:52:33 AM UTC-8 tke...@gmail.com wrote:
>
>> I'm glad things are working, but just for my edification, what did we 
>> fix? I thought the --daemon flag fixed the problem of LOOP packet data 
>> appearing in the log. Why was it necessary to comment out StdPrint?
>>
>> And, what fixed the problem with the importation of "serial"?
>>
>> On Wed, Mar 2, 2022 at 9:28 AM Cat22  wrote:
>>
>>> python3 -c "import serial"
>>> that works, return code is 0 (echo $?)
>>>
>>> On Wednesday, March 2, 2022 at 9:26:20 AM UTC-8 Cat22 wrote:
>>>
 I made this change and it worked! At least it looks like it worked, I 
 need to watch it for awhile to be sure
 #report_services = *weewx.engine.StdPrint*, weewx.engine.StdReport, 
 user.lowBattery.BatteryAlarm
 report_services = weewx.engine.StdReport, user.lowBattery.BatteryAlarm

 On Wednesday, March 2, 2022 at 9:04:04 AM UTC-8 Cat22 wrote:

> That's basically what i did. When i add --daemon and restart i see 
> this:
> Mar 02 08:53:52 pc2 systemd[1]: weewx.service: Current command 
> vanished from the unit file, execution of the command list won't be 
> resumed.
> followed by some weather data then this:
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: 
> Initializing weewx version 4.0.0
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Using 
> Python 3.8.8 (default, Feb 19 2021, 16:53:21) [GCC]
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: 
> Platform Linux-5.8.11-x86_64-with-glibc2.2.5
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Locale 
> is 'en_US.UTF-8'
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: PID 
> file is /var/run/weewx.pid
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Using 
> configuration file /usr/local/bin/weewx/weewx.conf
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO weewx.engine: 
> Loading station type Vantage (weewx.drivers.vantage)
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: 
> Received signal TERM (15).
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] ERROR weewx.engine: 
> Import of driver failed:  ()
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
>   Traceback (most recent call last):
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "/usr/local/bin/weewx/bin/weewx/engine.py", line 103, in 
> setupStation
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
>   self.console = loader_function(config_dict, self)
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", 
> line 
> 39, in loader
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
>   return VantageService(engine, config_dict)
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", 
> line 
> 1897, in __init__
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", 
> line 
> 511, in __init__
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
>   self.port.openPort()
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", 
> line 
> 305, in openPort
> Mar 02 08:54:10 pc2 python[16604]: 

Re: [weewx-user] Re: WeeWX WebP image plot test

[Paul R Anderson]

Hi Vince,
Thanks for trying. So I see from the can I use site that Safari is a
problem for sure.
 15.3 - Partial support in Safari  limited to macOS 11 Big Sur and later
So there's that. :)
Thanks,
Paul

On Sat, Mar 5, 2022 at 11:57 AM vince  wrote:

> I get no images shown in Safari 15.3 on an Intel MacBook Air.
>
> --
> 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/1a681fa7-a449-4311-aa8e-ee38c51d4134n%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/CAOAVAecLLFCZchCCN_CAJsjKFDd_TCZtuuQVe%2BBRTU9hzONgUA%40mail.gmail.com.

Re: [weewx-user] Re: weewx-multi performance combined with multiple skins on RPi3/4

[Tom Keffer]

Nope. Won't work. Unfortunately, the state machine is tangled up in the
archiving service. For example, the decision on when to pause the LOOP
packets and generate archive records is done by StdArchive. Having two
instances would probably result in chaos.

They really should be separated, but that's a scary project that could lead
to a lot of subtle bugs.

On Sat, Mar 5, 2022 at 8:16 AM matthew wall  wrote:

> On Saturday, March 5, 2022 at 10:33:26 AM UTC-5 f4n...@gmail.com wrote:
>
>> I had an Idea: If I understand the strategies wiki right: can I save to
>> the local sqlite database and to an external mysql database simultaneously?
>>
>
> weewx is designed to save to only one database
>
> i have no idea whether this would work, but you might try putting two
> instances of StdArchive into the service list.  that *might* let you save
> to two different databases.  create your own archiving service by deriving
> from the StdArchive class, and put it in the weewx user directory.  should
> not be necessary to define any methods.  then refer to it in your weewx
> config file:
>
> archive_services = weewx.engine.StdArchive, user.MyArchive
>
> If so, I could send it to a mysql database on my webhosting and then
>> access it with another weewx installation on another computer and let the
>> heavier skins run there?  So:
>>
>> raspberry Pi A [sqlite local reports] --> webserver [mysql] <-->
>> raspberry Pi B (or other computer) [skin reports]
>>
>> Could I access the mysql database simultaneously with weewx on system B?
>> Would it run reports automatically without an attached weather station?
>>
>
> this is the 'standard' way to do it.  make weewx save to a mysql database,
> either on the computer doing the collection, or on the computer doing the
> aggregated reports.  then make the reporting instance of weewx pull data
> from the mysql database.
>
>
> --
> 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/e2c101ac-464c-412d-8daa-e32752e98effn%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/CAPq0zEC0pJqrbYDuLPCzR6LFF2FxLYCV0uVfeC3g8%2BzowEnHfg%40mail.gmail.com.

[weewx-user] Re: WeeWX WebP image plot test

[vince]

I get no images shown in Safari 15.3 on an Intel MacBook Air.

-- 
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/1a681fa7-a449-4311-aa8e-ee38c51d4134n%40googlegroups.com.

[weewx-user] Weewx 4.7.0 & Weewx -WD

[Stefanos Kalaitzis]

Hi everyone...I am running weewx with sdr driver  I decided to update from 
weewx 4.2.0 to 4.7.0 and i have several errors in Clientraw skinIt 
doesnt generate the clientraw.txt but all the others clientrawhour,-daily - 
extra are generated.In the 4.2.0 version evrything was flawless .I also 
made a clean install of weewx 4.7.0 and the errors are the same ... I kept 
the log from 4.7.0 and i downgraded again to the old version. If someone 
knows whats going on i would appreciate it.
 I didnt make any change to weewx.conf after the update .

Thank you in advanced 

-- 
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/b200d823-4ee6-4e64-8164-b531a227d54bn%40googlegroups.com.
Mar  5 16:47:58 raspberrypi weewx[685] INFO weewx.restx: AWEKAS: Published 
record 2022-03-05 16:47:30 EET (1646491650)
Mar  5 16:47:58 raspberrypi weewx[685] INFO user.belchertown: version 1.2
Mar  5 16:47:58 raspberrypi weewx[685] INFO weewx.restx: StationRegistry: 
Published record 2022-03-05 16:47:30 EET (1646491650)
Mar  5 16:48:00 raspberrypi weewx[685] INFO user.belchertown: New forecast file 
downloaded to /home/weewx/public_html/json/forecast.json
Mar  5 16:48:15 raspberrypi weewx[685] INFO weewx.cheetahgenerator: Generated 
39 files for report Belchertown in 17.63 seconds
Mar  5 16:48:15 raspberrypi weewx[685] INFO weewx.reportengine: Copied 37 files 
to /home/weewx/public_html
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: Evaluation 
of template /home/weewx/skins/Testtags/testtags.php.tmpl failed with exception 
''
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:  
Ignoring template /home/weewx/skins/Testtags/testtags.php.tmpl
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:  
Reason: 'trend'
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
Traceback (most recent call last):
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: 
File "/home/weewx/bin/weewx/cheetahgenerator.py", line 348, in generate
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
unicode_string = compiled_template.respond()
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: 
File "_home_weewx_skins_Testtags_testtags_php_tmpl.py", line 1062, in respond
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: 
File "/home/weewx/bin/weewx/tags.py", line 65, in trend
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
time_grace = to_int(self.option_dict['trend'].get('time_grace', 300))
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
KeyError: 'trend'
Mar  5 16:48:20 raspberrypi weewx[685] INFO weewx.cheetahgenerator: Generated 0 
files for report wdTesttags in 3.23 seconds
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: Evaluation 
of template /home/weewx/skins/Clientraw/clientraw.txt.tmpl failed with 
exception ''
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:  
Ignoring template /home/weewx/skins/Clientraw/clientraw.txt.tmpl
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:  
Reason: 'trend'
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
Traceback (most recent call last):
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: 
File "/home/weewx/bin/weewx/cheetahgenerator.py", line 348, in generate
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
unicode_string = compiled_template.respond()
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: 
File "_home_weewx_skins_Clientraw_clientraw_txt_tmpl.py", line 330, in respond
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: 
File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1458, in 
varExists
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
varName.replace('$', ''), autoCall)
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator: 
File "/home/weewx/bin/weewx/tags.py", line 63, in trend
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
time_delta = to_int(self.option_dict['trend'].get('time_delta', 10800))
Mar  5 16:48:20 raspberrypi weewx[685] ERROR weewx.cheetahgenerator:   
KeyError: 'trend'
Mar  5 16:48:20 raspberrypi weewx[685] INFO weewx.cheetahgenerator: Generated 0 
files for report wdClientraw in 0.50 seconds

[weewx-user] Re: weewx-multi performance combined with multiple skins on RPi3/4

[matthew wall]

On Saturday, March 5, 2022 at 10:33:26 AM UTC-5 f4n...@gmail.com wrote:

> I had an Idea: If I understand the strategies wiki right: can I save to 
> the local sqlite database and to an external mysql database simultaneously? 
>

weewx is designed to save to only one database

i have no idea whether this would work, but you might try putting two 
instances of StdArchive into the service list.  that *might* let you save 
to two different databases.  create your own archiving service by deriving 
from the StdArchive class, and put it in the weewx user directory.  should 
not be necessary to define any methods.  then refer to it in your weewx 
config file:

archive_services = weewx.engine.StdArchive, user.MyArchive

If so, I could send it to a mysql database on my webhosting and then access 
> it with another weewx installation on another computer and let the heavier 
> skins run there?  So:
>
> raspberry Pi A [sqlite local reports] --> webserver [mysql] <--> raspberry 
> Pi B (or other computer) [skin reports]
>
> Could I access the mysql database simultaneously with weewx on system B? 
> Would it run reports automatically without an attached weather station?
>

this is the 'standard' way to do it.  make weewx save to a mysql database, 
either on the computer doing the collection, or on the computer doing the 
aggregated reports.  then make the reporting instance of weewx pull data 
from the mysql database.
 

-- 
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/e2c101ac-464c-412d-8daa-e32752e98effn%40googlegroups.com.

[weewx-user] Re: WeeWX WebP image plot test

[Tom Hogland]

Looks fine for me - Ubuntu x64, tested with Chrome, Firefox, Brave and 
Opera.

On Friday, March 4, 2022 at 1:45:42 PM UTC-9 pa...@pauland.net wrote:

>  What is WebP ?
>
> An image format developed by Google in 2010. Quote from Google “WebP is a 
> modern image format that provides superior lossless and lossy compression 
> for images on the web. Using WebP, webmasters and web developers can create 
> smaller, richer images that make the web faster.” WebP adoption has been 
> slow but as of now in 2022 it appears that around 95% of user devices such 
> as desktop PC’s and phones support the file format. One article here has 
> some data on supporting browsers https://caniuse.com/webp
>
> Given the adoption rate I thought it was time to see if WeeWX could 
> produce plots in WebP format. It was very easy to get WeeWX to produce WebP 
> format plots. Results were an average file size reduction of 50% percent, 
> with little if any discernible image quality differences.
>
> Been using only WebP plot images on my very low traffic website for a few 
> days and haven’t heard any complaints. Would love if you could take some to 
> try to view the site and let me know of any browser, device issues. Also 
> what you think of image quality, to me they look like normal WeeWX plots.
>
> Site:
>
> https://pauland.net
>
> Thank You,
>
> Paul
>

-- 
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/0d425536-de4f-4f3c-9c4a-706bd4a07856n%40googlegroups.com.

[weewx-user] Re: weewx-multi performance combined with multiple skins on RPi3/4

[f4n...@gmail.com]

Thanks maybe I will try this out sometime.

I had an Idea: If I understand the strategies wiki right: can I save to the 
local sqlite database and to an external mysql database simultaneously? If 
so, I could send it to a mysql database on my webhosting and then access it 
with another weewx installation on another computer and let the heavier 
skins run there?  So:

raspberry Pi A [sqlite local reports] --> webserver [mysql] <--> raspberry 
Pi B (or other computer) [skin reports]

Could I access the mysql database simultaneously with weewx on system B? 
Would it run reports automatically without an attached weather station?

matthew wall schrieb am Freitag, 4. März 2022 um 17:18:37 UTC+1:

> On Friday, March 4, 2022 at 9:51:16 AM UTC-5 f4n...@gmail.com wrote:
>
>> Is Influx and grafana easy to learn? I'm really not much of a developer, 
>> as html, css and lets say the weewx config files already are enough of a 
>> hassle for me, if I make some error somewhere :D 
>>
>
> they are pretty easy to install for individual use, but it gets rather 
> complicated if you intend to run them in any public-facing situation.  both 
> grafana and influx have cloud-based services, so you could use the cloud 
> version without having to install anything yourself.
>
> use the weewx-influx extension to send data to influx, then use grafana to 
> browse and display the data. i have attached a screenshot of a basic 
> weather dashboard from a weewx+influx+grafana installation.
>  
>
>> Option a: sounds interesting too, so could i save to an additional mysql 
>> database on an external device/storage and run wee_reports periodically on 
>> that device?
>>
>
> i have updated the 'strategies for publishing data from weeWX' to include 
> this as scenario 7.
>
> https://github.com/weewx/weewx/wiki/dashboards
>
>
>  
>

-- 
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/eb1535bb-4bdc-4745-90dc-b066cebe0d2dn%40googlegroups.com.

Re: [weewx-user] update to 4.7 weewx-multi

[Joachim Puttkammer]

Thanks, the update was successful.
After the normal WeeWX upgrade, there was an error message:

See "systemctl status weewx.service" and "journalctl -xe" for details.
invoke-rc.d: initscript weewx, action "start" failed.
● weewx.service - LSB: weewx-multi
 Loaded: loaded (/etc/init.d/weewx; generated)
 Active: failed (Result: exit-code) since Sat 2022-03-05 13:44:34 CET; 
21ms ago
   Docs: man:systemd-sysv-generator(8)
Process: 72952 ExecStart=/etc/init.d/weewx start (code=exited, 
status=1/FAILURE)
  Tasks: 2 (limit: 8987)
CPU: 1.649s
 CGroup: /system.slice/weewx.service
 ├─72966 python /usr/share/weewx/weewxd --daemon --log-label 
weewx-dav --pidfile=/var/run/weewx-dav.pid /etc/weewx/dav.conf
 └─72976 python /usr/share/weewx/weewxd --daemon --log-label 
weewx-eco --pidfile=/var/run/weewx-eco.pid /etc/weewx/eco.conf

After :
sudo wee_config --upgrade --config=/etc/weewx/dav.conf 
--dist-config=/etc/weewx/weewx.conf.dist
and
sudo wee_config --upgrade --config=/etc/weewx/eco.conf 
--dist-config=/etc/weewx/weewx.conf.dist

there was no error .

gjr80 schrieb am Donnerstag, 3. März 2022 um 14:56:47 UTC+1:

> I have a dual instance setup running and it's basically as Tom said, you 
> just upgrade WeeWX as normal. A WeeWX upgrade only upgrades weewx.conf so 
> once the upgrade is done I run the following command on each instance 
> config file (neither of my config files is named weewx.conf - if you do 
> use weewx.conf for one instance then of course it is upgraded as part of 
> the WeeWX upgrade so no need to 'upgrade' it again) to upgrade the instance 
> config files:
>
> $ cd /home/weewx
> $ ./bin/wee_config instance.conf --dist-config=weewx.conf.X.Y.Z --upgrade
>
> I run a setup.py install so for a package install the paths will be 
> different. sudo may also be required depending on your setup.
>
> Gary 
> On Thursday, 3 March 2022 at 23:14:26 UTC+10 tke...@gmail.com wrote:
>
>> Not sure what you're asking. If all instances are using the same code 
>> base, just update the code base. 
>>
>> On Thu, Mar 3, 2022 at 4:59 AM Joachim Puttkammer  
>> wrote:
>>
>>> How should I proceed with the update for weewx-multi (2 instances)?
>>>  
>>>
>>> -- 
>>> 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/0c64229c-974c-4d8a-acb6-d53b27d2c352n%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/418bb4ce-1dbf-467f-9981-028d208fd61an%40googlegroups.com.

[weewx-user] Re: Weather34

[Matthieu Devigne]

1) I have a difference between weewx and weather 34 :

For today with weewx, I have gust wind max at 12km/hh and weather34 
 43.2km/h.

On my weather station him : 12km/k

2) All the charts are stopped for history (when I choose a date) : 


Le vendredi 4 mars 2022 à 21:56:31 UTC+1, steep...@gmail.com a écrit :

> 1) according to your realtime file, the wind is calm at the moment
> 2) Most charts are working perfectly for me. You will need to wait for a 
> while for the weekly reports to be run.
>
> Also, you need to activate a free account with Aeris Weather to get your 
> weather warnings working correctly.
>
> Aeris Weather will also give far more detail for your weather forecasts 
> compard with your current choice of Weather Underground. 
>
> On Friday, March 4, 2022 at 8:25:49 PM UTC matthieu89...@gmail.com wrote:
>
>> Yes, the data are in live. Thanks. 
>>
>> 1) I see that the wind gust and wind speed are not the true data. Why ?
>>
>> 2) And, the data history data on charts is not run (all the charts) :
>>
>> With a error message
>>
>> Le jeudi 3 mars 2022 à 22:54:08 UTC+1, steep...@gmail.com a écrit :
>>
>>> You need to change the path to serverdata/w34realtime.txt
>>>
>>> On Thursday, March 3, 2022 at 7:53:21 PM UTC matthieu89...@gmail.com 
>>> wrote:
>>>
 I didn't have change the setting 
 (/var/www/html/weewx/weather34/serverdata/w34realtime.txt) : 

 Le mercredi 2 mars 2022 à 22:39:30 UTC+1, steep...@gmail.com a écrit :

> You need to change the setting for your live data in the settings 
> page: -
>
> [image: Screenshot 2022-03-02 at 21.32.47.png]
>
> On Wednesday, March 2, 2022 at 7:36:20 PM UTC matthieu89...@gmail.com 
> wrote:
>
>> With weather 34 : www.meteo-champignyonne.fr/weather34
>>
>> Le mercredi 2 mars 2022 à 20:35:52 UTC+1, Matthieu Devigne a écrit :
>>
>>> Hi,
>>>
>>> Yes, weewx is running.
>>>
>>> My URL : www.meteo-champignyonne.fr
>>>
>>> Le mercredi 2 mars 2022 à 12:19:33 UTC+1, steep...@gmail.com a 
>>> écrit :
>>>
 Also make sure that WeeWX is actually running after you issued the 
 restart command.

 On Tuesday, March 1, 2022 at 9:53:40 PM UTC Steeple Ian wrote:

> Can you let me have your URL please, I need to check your realtime 
> data. The situation in your screen shot indicates that the template 
> is not 
> getting live data from WeeWX.
>
> On Tuesday, March 1, 2022 at 7:28:01 PM UTC 
> matthieu89...@gmail.com wrote:
>
>> Yes, I will watch for the file service.txt.
>>
>> For weewx.conf I add [Services]] section in the [Engine] 
>> stanza. : ,*user.w34_db_backup.W34_DB_Backup*
>> And at the end :
>> [W34_DB_Backup] * # database path(s) seperated by , rename 
>> this/these database(s) to match your own databases = 
>> /home/weewx/archive/weewx.sdb,/home/weewx/archive/another.sdb # 
>> backup 
>> path(s) comma seperated backups = 
>> [your_backup_path]/weewx_backup.sdb,[your_backup_path]/home/pi/another_backup.sdb
>>  
>> # set the daily time to backup comma seperated for multiple 
>> databases # the 
>> time must be set an to archive time so it runs immediately after the 
>> archive interval processes are complete backup_times = 00:00,00:00*
>>
>>
>> Yes, sorry but the data for the pression, temperature, and windy 
>> for weather34 are not correct.
>> Is not the real values
>>
>> What is the problem ?
>> Le lundi 28 février 2022 à 23:02:26 UTC+1, steep...@gmail.com a 
>> écrit :
>>
>>> I am glad the template is now running for you.
>>>
>>> Regarding the two errors: -
>>>
>>> 1. Metar, it looks as though you did not add your X-API-Key or 
>>> Metar airport code when you generated your services.txt. Did you 
>>> follow the 
>>> instructions to obtain a key and find your nearest airport?
>>> The three relevant lines in the web services section of 
>>> weewx.conf should look something like this (ABCD represents the 
>>> airport 
>>> code and 123456789 represents the API Key: -
>>>   me_url = https://api.checkwx.com/metar/ABCD/decoded
>>>   me_header = X-API-Key:123456789
>>>   me_interval = 3600
>>>
>>> 2. The file should already be in place, all you need to do is 
>>> edit weewx.conf and restart as in the instructions. I have updated 
>>> the 
>>> install instructions to make this clearer>
>>>
>>> Ian
>>>
>>>
>>>
>>> On Monday, February 28, 2022 at 5:25:50 PM UTC 
>>> matthieu89...@gmail.com wrote:
>>>
 Thanks !

[weewx-user] Re: How to get both lux and radiation values in the report?

[f4n...@gmail.com]

Thanks a lot Gary, this was somehow better to understand for me than in the 
Customization Guide.

And it works, now the zeros behind the dot are gone. My SDR setup is 
displaying both lx and w/m2 fine now. This was rather easy to do with just 
adding it a second time to the sensor map and adding the right conversions, 
but now I wonder how I could achieve this on the Interceptor driver 
instance too?  

Could I just add radiation = radiation, as well as luminosity = 
radiation*126,7 to the corrections section or is there more needed to 
generate a second plot for it? Kind of like when someone would want to 
output the temperature both in celsius and farenheit, how is this done?

gjr80 schrieb am Samstag, 5. März 2022 um 00:50:21 UTC+1:

> Before I answer a quick WeeWX units 101. The WeeWX unit system is the core 
> that allows WeeWX to convert between units (eg C to F), format observation 
> data in reports and add unit labels. The system is predicated on each 
> observation being allocated to a unit group (eg outTemp, inTemp, dewpoint 
> etc are allocated to group_temperature). In essence this tells WeeWX that 
> each of these observations are a temperature, so WeeWX knows how to convert 
> to other temperature units, format the numeric data and what unit labels to 
> use.
>
> There is a bit of history to light related observations in WeeWX. Without 
> going into the details the WeeWX extended schema includes a field named 
> illuminance that belongs to group_illuminance which uses the unit lux. 
> There is no field named luminosity in the WeeWX extended schema. 
> Consequently, when you use a field named luminosity in reports and plots 
> etc WeeWX will still happily display the data but you don't get any unit 
> labels, formatting of numeric values, unit conversion etc. So how to fix? 
> Simple, you need to tell WeeWX about the data in field luminosity. This 
> is covered to a certain extent in the Customization Guide under the section 
> Customizing 
> units and unit groups 
> . In your case 
> though the preferred approach would be to add a couple of lines to 
> extensions.py 
> (located in /home/weewx/bin/user or /usr/share/weewx/user depending on 
> your WeeWX install), something like the following should work (untested): 
>
> import weewx.units
> weewx.units.obs_group_dict['luminosity'] = 'group_illuminance'
>
> Save extensions.py and restart WeeWX. Your plots and reports should now 
> contain properly formatted/labelled luminosity data.
>
> Gary
> On Thursday, 3 March 2022 at 21:36:16 UTC+10 f4n...@gmail.com wrote:
>
>> It was the skin.conf, now they appear, thanks!
>>
>> Is there a way to add "lux" to the lux reading in the graph and current 
>> conditions list? Could i just add it in weewx.conf?
>>
>> In the current conditions list, the lux number reads like this 
>> "70070.00". 
>> Can i add something like lux = %.1f to weewx.conf?
>>
>>
>>
>>
>> gjr80 schrieb am Mittwoch, 2. März 2022 um 00:27:57 UTC+1:
>>
>>> The only real definitive way of determining what schema you are using is 
>>> to access the database and check what fields are there. If you have only 
>>> ever installed v 4.0.0 or later and did not explicitly change the schema 
>>> you are almost certainly using the extended schema. If you have upgraded a 
>>> v3.x or earlier install you are most likely using the legacy wview schema 
>>> unless you explicitly changed schemas. You can check the schema config 
>>> option for the binding concerned under [DataBindings] in weewx.conf, eg:
>>>
>>> [DataBindings] 
>>>
>>>  [[wx_binding]] 
>>>  
>>>  # The schema defines the structure of the database. 
>>>  # It is *only* used when the database is created. schema = 
>>> schemas.wview_extended.schema
>>>  schema = schemas.wview_extended.schema
>>>
>>> However, the schema config option is only used when the database is 
>>> created so it is possible that it may be different to the actual schema of 
>>> the database you are using. 
>>>
>>> The fact you don't get luminosity plots could be due to any one of a 
>>> myriad of issues, schema is just but one of the possible causes. The most 
>>> likely cause is that your skin is not set to generate and display such 
>>> plots.
>>>
>>> If you are using the 4.6.x Seasons skin you can specify in the skin 
>>> config file what observations you wish to see reported and plotted. As I 
>>> said in my previous post I suggest you have a look through the 
>>> [DisplayOptions] stanza, the comments should guide you. One thing I did 
>>> omit was that you will need to add suitable entries to the 
>>> [ImageGenerator] stanza of the skin config file to create your 
>>> luminosity plot files, something like (untested):
>>>
>>>
>>> [ImageGenerator]
>>> 
>>> [[day_images]]
>>> 
>>> [[[dayluminosity]]]
>>> luminosity
>>>
>>> likewise for week, month and year plots in 

Re: [weewx-user] Re: Storing Text as a record, wee_import and mysql UPDATE

[Glenn McKechnie]

Gary, That one works a treat.

On 05/03/2022, gjr80 wrote:
> Apologies Glenn, try this version. I'm in between moving from linux to Mac
> on my desktop and my test environment is not quite complete so that last
> version had some cursory testing only.

Not a problem.
And thanks for your time getting it sorted.


-- 

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/CAAraAzjThU64OTbyUMb9E1iA80ZCddXm8H0WGqcymfaYe87H4g%40mail.gmail.com.