RE: [weewx-user] Re: Module Error

[steepleian]

Tom and Gary, The only way in which I have been able to get the custom installer to fail is making a false step by making the wrong selection when prompted on how WeeWX was originally installed. Mauro has previously successfully installed this current version of Weather34 onto my test server with a clean install of WeeWX 4.1.1 / Python3, so the issue is ‘what is happening on his own setup’. I have asked Mauro to go back and start afresh on his own RaspberryPi with a clean install of WeeWX 4.1.1 and Python3, making sure all is working well with Simulator, install Weather34 and then follow the extensive troubleshooting guide that JD has devised and post the results here. The question regarding whether wee_reports_34 is running in the correct place. Yes it is rather unusual, but if you have a look at my website https://claydonsweather.org.uk and click on one of the pop-up chart links at the foot of the individual sensor modules you will see why. Choose a weekly chart for say barometer, hover and click on a chart data point and see what happens. Click again and a different scenario. It is this click which runs wee_reports_34. So back to the task in hand, hopefully we can get to the bottom of Mauro’s problems 😊 Thanks for your continued support, Ian Sent from Mail for Windows 10 From: Tom KefferSent: 12 August 2020 02:27To: weewx-userSubject: Re: [weewx-user] Re: Module Error You're probably right. I suspect the custom weather34 installer went a little ... off track.  On Tue, Aug 11, 2020 at 6:02 PM J D  wrote:This is not a weewx issue or a python path issue. The file is in the correct location, but the troubleshooting guide must be done to find out why there is an error.On Tuesday, August 11, 2020 at 3:27:16 PM UTC-7, Mauro De Lauretis wrote:Hi all!I'm running the last version of weewx with python3 on my Raspberry Pi.As skin I use the weather34 weewx version (https://github.com/steepleian/weewx-Weather34) There are also incorporated highcharts that are created live from the database when selecting on the website.However, a part of them won't work with my setup and this Is the message I get:  root@raspberrypi:~# sudo python3 /var/www/html/weewx/weather34/w34highcharts/wee_reports_w34Traceback (most recent call last):  File "/var/www/html/weewx/weather34/w34highcharts/wee_reports_w34", line 8, in     import weewxModuleNotFoundError: No module named 'weewx'   Do you have any ideas what the issue could be? Thanks Mauro-- 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/ca782342-2160-4630-aee3-438d53a85c50o%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/CAPq0zECtu0d8VYDWbm%3DUAEvU86JTU_Kf1rRKreuUNwO1xLf7pw%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/7A6EA92F-E1F7-4882-8023-11B2142314E2%40hxcore.ol.

Re: [weewx-user] Re: Module Error

[Mauro De Lauretis]

The location of the executable is there because it is installed liked that 
to run on the local server.

If I try to do sudo PYTHONPATH=/home/weewx/bin python3 
/var/www/html/weewx/weather34/w34highcharts/wee_reports_w34 I get this:

*pi@raspberrypi*:*~ $* sudo su

root@raspberrypi:/home/pi# sudo PYTHONPATH=/home/weewx/bin python3 
/var/www/html/weewx/weather34/w34highcharts/wee_reports_w34

Using configuration file /home/weewx/weewx.conf

Generating for all time

Traceback (most recent call last):

  File "/var/www/html/weewx/weather34/w34highcharts/wee_reports_w34", line 
99, in 

main()

  File "/var/www/html/weewx/weather34/w34highcharts/wee_reports_w34", line 
68, in main

config_dict['StdReport']['w34Highcharts']['CheetahGenerator'] =  
{'search_list_extensions': 'user.w34highchartsSearchX.w34highcharts_' + 
args[1].split('/')[-1].split('.')[0], 'encoding': 'strict_ascii', 'ToDate': 
{'DayJSON': {'template': args[1],'HTML_ROOT': args[2]}}}

IndexError: list index out of range


Il giorno mercoledì 12 agosto 2020 alle 03:27:38 UTC+2 tke...@gmail.com ha 
scritto:

> You're probably right. I suspect the custom weather34 installer went a 
> little ... off track. 
>
> On Tue, Aug 11, 2020 at 6:02 PM J D  wrote:
>
>> This is not a weewx issue or a python path issue. The file is in the 
>> correct location, but the troubleshooting guide must be done to find out 
>> why there is an error.
>>
>
>>
>> On Tuesday, August 11, 2020 at 3:27:16 PM UTC-7, Mauro De Lauretis wrote:
>>>
>>> Hi all!
>>> I'm running the last version of weewx with python3 on my Raspberry Pi.
>>> As skin I use the weather34 weewx version (
>>> https://github.com/steepleian/weewx-Weather34)
>>>
>>> There are also incorporated highcharts that are created live from the 
>>> database when selecting on the website.
>>> However, a part of them won't work with my setup and this Is the message 
>>> I get:
>>>
>>>
>>> root@raspberrypi:~# sudo python3 
>>> /var/www/html/weewx/weather34/w34highcharts/wee_reports_w34
>>>
>>> Traceback (most recent call last):
>>>
>>>   File "/var/www/html/weewx/weather34/w34highcharts/wee_reports_w34", 
>>> line 8, in 
>>>
>>> import weewx
>>>
>>> ModuleNotFoundError: No module named 'weewx'
>>>
>>>
>>>
>>>
>>> Do you have any ideas what the issue could be?
>>>
>>>
>>> Thanks
>>>
>>>
>>> Mauro
>>>
>> -- 
>>
> 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/ca782342-2160-4630-aee3-438d53a85c50o%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/b5d05819-d3ff-4d3c-9057-c449e9939bfan%40googlegroups.com.

Re: [weewx-user] Re: Questions about weewx-loopdata 2.x

[John Kline]

> Where can I find a description of what a “Rain Year” is?

By default, rainyear is the same as year.  It’s the 12-month period for which 
the cumulative rain amount is measured.
See: https://en.wikipedia.org/wiki/Water_year
To set the rain year, see:  http://weewx.com/docs/usersguide.htm#rain_year_start

> Where and how can I set that $wind.rms.formatted and $windGust.max.formatted 
> have a decimal place at km / h?

I’m assuming you mean .rms.formatted and 
.windGust.max.formatted (where  is 10m, day, week, month, year 
or rainyear).

Also assuming you want to see one decimal position in these values.

In the LoopDataReport section of weewx.conf, there is already 1 decimal place 
specified for km_per_hour (“%.1f”), unless you have changed it:
   [[[Units]]]
StringFormats
mile_per_hour = %.1f
degree_C = %.1f
km_per_hour = %.1f
degree_F = %.1f 

I suspect you have a different target report specified:
Let’s imagine your [LoopData] section looks like this where the target_report 
is WeatherBoardReport:

[LoopData]
[[FileSpec]]
loop_data_dir = /home/weewx/gauge-data
filename = loop-data.txt
[[Formatting]]
target_report = WeatherBoardReport

In this case, you would to specify the decimal for km_per_hour under 
WeatherBoardReport, since that is the report you have specified for conversion 
and formattting.  You would want that report to specify the decimal place for 
km_per_hour.

[[WeatherBoardReport]]
   [[[Units]]]
StringFormats
km_per_hour = %.1f


> On Aug 11, 2020, at 11:01 PM, Geni 0815  wrote:
> 
> 
> Hi John, Thanks for the new version.
> I still have the following questions:
> Where can I find a description of what a "Rain Year" is?
> Where and how can I set that $wind.rms.formatted and $windGust.max.formatted 
> also have a decimal place at km / h?
> Current Livelink
> 
> Am Mittwoch, 12. August 2020 03:20:18 UTC+2 schrieb John Kline:
>> 
>> OK, I found the issue.  My tests simulate running weewx and processing 
>> packets.  The issue was at startup where I use daily summaries to create 
>> accumulators for day, week, year and rainyear.  That code was missing the 
>> first daily summary of each of these periods.
>> 
>> I’ve fixed this issue in v2.7.  Please give it a try.
>> 
 On Aug 11, 2020, at 9:41 AM, John Kline  wrote:
 
>>> 
>>> It does not look like you have installed from head on github.
>>> 
>>> Go to this page:
>>> 
>>> https://github.com/chaunceygardiner/weewx-loopdata
>>> 
>>> Click “Code” and then click download zip.  Install that zip file.
>>> 
>>> When you do that, after time_delta in the log, you should see week_start 
>>> and rainyear_start.
>>> 
> On Aug 11, 2020, at 9:37 AM, Geni 0815  wrote:
> 
 
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: tmpname   
  : /tmp/LoopDataz7h4ntn0
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: enable
  : 0
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: remote_server 
  : www.foobar.com
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: remote_port   
  : None
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: remote_user   
  : root
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: remote_dir
  Af: /home/weewx/loop-data
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: compress  
  : 0
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: log_success   
  : 0
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: ssh_options   
  : -o ConnectTimeout=1
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: timeout   
  : 1
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
 skip_if_older_than : 3
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: time_delta
  : 10800
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
 trend_obstypes : ['barometer', 'outTemp']
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
 rainyear_obstypes  : ['outTemp', 'wind', 'windSpeed', 'windDir', 
 'windGust', 'windGustDir', 'rain']
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: year_obstypes 
  : ['outTemp', 'wind', 'windSpeed', 'windDir', 'windGust', 
 'windGustDir', 'rain']
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
 month_obstypes : ['wind', 'windSpeed', 'windDir', 'windGust', 
 'windGustDir', 'rain', 'outTemp']
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: week_obstypes 
  : ['wind', 'windSpeed', 'windDir', 'windGust', 'windGustDir', 'rain', 
 'outTemp']
 Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: day_obstypes  
  : 

Re: [weewx-user] Trouble with Vaisala driver - syslog not defined

[Tom Keffer]

It looks like the driver was not properly ported to WeeWX V4. There is
still some old V3 cod in there. Try filing an issue request with the author.

-tk

On Tue, Aug 11, 2020 at 6:59 PM Chris Howard  wrote:

>
> I am attempting to install on a BeagleBone Black Wireless.
> My device is a Vaisala wxt520.  I have installed a driver from github.
>
> BeagleBone ubuntu is based on Debian 9 so I am running python2.
>
> I'm not afraid to edit files, but not sure if this driver should run on my
> system
> and maybe I just missing something dumb in the install.
>
> I did try a small sample python program to see if I could successfully
> import syslog
> and send a message to syslog.  That seemed to work fine.
>
> Here is my error message:
> Aug 12 01:34:33 beaglebone weewx[2348]: Stopping weewx weather system:
> weewx not running
> Aug 12 01:34:40 beaglebone weewx[2400] INFO __main__: Initializing weewx
> version 4.1.1
> Aug 12 01:34:40 beaglebone weewx[2400] INFO __main__: Using Python 2.7.13
> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
> Aug 12 01:34:40 beaglebone weewx[2400] INFO __main__: Platform
> Linux-4.14.71-ti-r80-armv7l-with-debian-9.5
> Aug 12 01:34:40 beaglebone weewx[2400] INFO __main__: Locale is
> 'en_US.UTF-8'
> Aug 12 01:34:40 beaglebone weewx[2400] INFO __main__: PID file is
> /var/run/weewx.pid
> Aug 12 01:34:40 beaglebone weewx[2389]: Starting weewx weather system:
> weewx.
> Aug 12 01:34:40 beaglebone weewx[2404] INFO __main__: Using configuration
> file /etc/weewx/weewx.conf
> Aug 12 01:34:40 beaglebone weewx[2404] INFO __main__: Debug is 0
> Aug 12 01:34:41 beaglebone weewx[2404] INFO weewx.engine: Loading station
> type WXT5x0 (user.wxt5x0)
> Aug 12 01:34:41 beaglebone weewx[2404] ERROR weewx.engine: Import of
> driver failed: global name 'syslog' is not defined ( 'exceptions.NameError'>)
> Aug 12 01:34:41 beaglebone weewx[2404] CRITICAL weewx.engine: 
> Traceback (most recent call last):
> Aug 12 01:34:41 beaglebone weewx[2404] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/engine.py", line 103, in setupStation
> Aug 12 01:34:41 beaglebone weewx[2404] CRITICAL weewx.engine: 
>   self.console = loader_function(config_dict, self)
> Aug 12 01:34:41 beaglebone weewx[2404] CRITICAL weewx.engine: 
> File "/usr/share/weewx/user/wxt5x0.py", line 109, in loader
> Aug 12 01:34:41 beaglebone weewx[2404] CRITICAL weewx.engine: 
>   return WXT5x0Driver(**config_dict[DRIVER_NAME])
> Aug 12 01:34:41 beaglebone weewx[2404] CRITICAL weewx.engine: 
> File "/usr/share/weewx/user/wxt5x0.py", line 470, in __init__
> Aug 12 01:34:41 beaglebone weewx[2404] CRITICAL weewx.engine: 
>   loginf('driver version is %s' % DRIVER_VERSION)
> Aug 12 01:34:41 beaglebone weewx[2404] CRITICAL weewx.engine: 
> File "/usr/share/weewx/user/wxt5x0.py", line 122, in loginf
> Aug 12 01:34:41 beaglebone weewx[2404] CRITICAL weewx.engine: 
>   logmsg(syslog.LOG_INFO, msg)
> Aug 12 01:34:41 beaglebone weewx[2404] CRITICAL weewx.engine: 
> NameError: global name 'syslog' is not defined
> Aug 12 01:34:41 beaglebone weewx[2404] CRITICAL __main__: Unable to load
> driver: global name 'syslog' is not defined
> Aug 12 01:34:41 beaglebone weewx[2404] CRITICAL __main__: 
> Exiting...
>
>
> --
> 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/48c3ed56-d160-4952-a0ac-265d98a7be20o%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/CAPq0zEDOf%2BZAj_gFRx0YFVXAdzLd1cUKN16x4H0Ha1a7mx02Sg%40mail.gmail.com.

Re: [weewx-user] Re: New Vantage Pro ISS installation has clobbered weewx.

['Peter Fletcher' via weewx-user]

Everything is still working normally. For the record, however, I have 
attached the complete log listing for one of the crashes when it wasn't. At 
least to me, it gives no more information than the text printed to stderror.

On Monday, August 10, 2020 at 8:57:51 PM UTC-4 tke...@gmail.com wrote:

> It may be past the "catch up" phase. 
>
> This would be a lot easier to diagnose with the log...
>
> On Mon, Aug 10, 2020 at 5:48 PM 'Peter Fletcher' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> Now I know I'm insane!
>>
>> I copied my old conf file, modified the original to disable the user 
>> code, and confirmed that it worked with weewxd. However, weewx with the 
>> vanilla conf still crashed as a service. I then stopped the service and 
>> started it again and it worked! Stopped the service, copied back the 
>> original conf file, restarted it and it worked without problems!! Go figure!
>>
>> On Monday, August 10, 2020 at 7:33:10 PM UTC-4, Peter Fletcher wrote:
>>>
>>> I know that this sounds insane, but my modified (to add some extra data 
>>> derived from external sensors) weewx installation which has been running 
>>> for a couple of months now crashes on startup. I stopped weewx to replace a 
>>> (very) old Vantage Pro 2 ISS, removed the old unit, put the new unit in its 
>>> place, reconfigured the console to communicate with the new unit, observed 
>>> that the console was showing valid data, and restarted weewx, which is 
>>> running on a Pi connected to the console via a MeteoPi. weewx immediately 
>>> crashes, with the following exception tree, arising from my user code.
>>>  
>>>
>> -- 
>>
> 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/49991444-d821-4ca0-b987-7c76be31f7d2o%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/b3be6da5-3971-49fc-963e-804ab76f9b18n%40googlegroups.com.
Aug 10 18:50:00 localhost weewx[1595] INFO __main__: Initializing weewx version 
4.1.1
Aug 10 18:50:00 localhost weewx[1595] INFO __main__: Using Python 3.7.3 
(default, Jul 25 2020, 13:03:44) #012[GCC 8.3.0]
Aug 10 18:50:00 localhost weewx[1595] INFO __main__: Platform 
Linux-5.4.51-v7+-armv7l-with-debian-10.4
Aug 10 18:50:00 localhost weewx[1595] INFO __main__: Locale is 'en_US.UTF-8'
Aug 10 18:50:00 localhost weewx[1595] INFO __main__: Using configuration file 
/etc/weewx/weewx.conf
Aug 10 18:50:00 localhost weewx[1595] INFO __main__: Debug is 0
Aug 10 18:50:00 localhost weewx[1595] INFO weewx.engine: Loading station type 
Vantage (weewx.drivers.vantage)
Aug 10 18:50:00 localhost /weewxd: ArchTH: using /var/tmp/THNow.txt
Aug 10 18:50:00 localhost /weewxd: LoopTH: using /var/tmp/THNow.txt
Aug 10 18:50:00 localhost weewx[1595] INFO weewx.engine: StdConvert target unit 
is 0x1
Aug 10 18:50:00 localhost weewx[1595] INFO weewx.wxservices: The following 
values will be calculated: pressure=prefer_hardware, barometer=prefer_hardware, 
altimeter=prefer_hardware, windchill=prefer_hardware, 
heatindex=prefer_hardware, dewpoint=prefer_hardware, 
inDewpoint=prefer_hardware, rainRate=prefer_hardware, 
maxSolarRad=prefer_hardware, cloudbase=prefer_hardware, 
humidex=prefer_hardware, appTemp=prefer_hardware, ET=prefer_hardware, 
windrun=prefer_hardware
Aug 10 18:50:00 localhost weewx[1595] INFO weewx.wxservices: The following 
algorithms will be used for calculations: altimeter=aaASOS, maxSolarRad=RS
Aug 10 18:50:00 localhost weewx[1595] INFO weewx.engine: Archive will use data 
binding wx_binding
Aug 10 18:50:00 localhost weewx[1595] INFO weewx.engine: Record generation will 
be attempted in 'hardware'
Aug 10 18:50:00 localhost weewx[1595] INFO weewx.engine: Using archive interval 
of 300 seconds (specified by hardware)
Aug 10 18:50:00 localhost weewx[1595] INFO weewx.restx: StationRegistry: 
Registration not requested.
Aug 10 18:50:00 localhost weewx[1595] INFO weewx.restx: Wunderground: Posting 
not enabled.
Aug 10 18:50:00 localhost weewx[1595] INFO weewx.restx: PWSweather: Posting not 
enabled.
Aug 10 18:50:00 localhost weewx[1595] INFO weewx.restx: CWOP: Posting not 
enabled.
Aug 10 18:50:00 localhost weewx[1595] INFO weewx.restx: WOW: Posting not 
enabled.
Aug 10 18:50:00 localhost weewx[1595] INFO weewx.restx: AWEKAS: Posting not 
enabled.
Aug 10 18:50:00 localhost weewx[1595] INFO __main__: Starting up weewx versi

Re: [weewx-user] Re: Questions about weewx-loopdata 2.x

[Geni 0815]

Thanks for the explanation.

I had target_report = SeasonsReport, and there are 2 unit definitions for 
some.
 km_per_hour =% .0f
 km_per_hour2 =% .1f
 knot =% .0f
 knot2 =% .1f
meter_per_second = %.1f
meter_per_second2 = %.1f
mile_per_hour = %.0f
mile_per_hour2 = %.1f

  I have now redefined target_report = LoopDataReport, now it works as 
desired

Am Mittwoch, 12. August 2020 14:56:16 UTC+2 schrieb John Kline:
>
> > Where can I find a description of what a “Rain Year” is?
>
> By default, rainyear is the same as year.  It’s the 12-month period for 
> which the cumulative rain amount is measured.
> See: https://en.wikipedia.org/wiki/Water_year
> To set the rain year, see:  
> http://weewx.com/docs/usersguide.htm#rain_year_start
>
> > Where and how can I set that $wind.rms.formatted and 
> $windGust.max.formatted have a decimal place at km / h?
>
> I’m assuming you mean .rms.formatted and 
> .windGust.max.formatted (where  is 10m, day, week, month, 
> year or rainyear).
>
> Also assuming you want to see one decimal position in these values.
>
> In the LoopDataReport section of weewx.conf, there is already 1 decimal 
> place specified for km_per_hour (“%.1f”), unless you have changed it:
>[[[Units]]]
> StringFormats
> mile_per_hour = %.1f
> degree_C = %.1f
> km_per_hour = %.1f
> degree_F = %.1f 
>
> I suspect you have a different target report specified:
> Let’s imagine your [LoopData] section looks like this where the 
> target_report is WeatherBoardReport:
>
> [LoopData]
> [[FileSpec]]
> loop_data_dir = /home/weewx/gauge-data
> filename = loop-data.txt
> [[Formatting]]
> target_report = WeatherBoardReport
>
> In this case, you would to specify the decimal for km_per_hour under 
> WeatherBoardReport, since that is the report you have specified for 
> conversion and formattting.  You would want that report to specify the 
> decimal place for km_per_hour.
>
> [[WeatherBoardReport]]
>[[[Units]]]
> StringFormats
> km_per_hour = %.1f
>
>
> On Aug 11, 2020, at 11:01 PM, Geni 0815 > 
> wrote:
>
> 
> Hi John, Thanks for the new version.
> I still have the following questions:
> Where can I find a description of what a "Rain Year" is?
> Where and how can I set that $wind.rms.formatted and 
> $windGust.max.formatted also have a decimal place at km / h?
> Current Livelink 
>
> Am Mittwoch, 12. August 2020 03:20:18 UTC+2 schrieb John Kline:
>>
>> OK, I found the issue.  My tests simulate running weewx and processing 
>> packets.  The issue was at startup where I use daily summaries to create 
>> accumulators for day, week, year and rainyear.  That code was missing the 
>> first daily summary of each of these periods.
>>
>> I’ve fixed this issue in v2.7.  Please give it a try.
>>
>> On Aug 11, 2020, at 9:41 AM, John Kline  wrote:
>>
>> 
>> It does not look like you have installed from head on github.
>>
>> Go to this page:
>>
>> https://github.com/chaunceygardiner/weewx-loopdata
>>
>> Click “Code” and then click download zip.  Install that zip file.
>>
>> When you do that, after time_delta in the log, you should see week_start 
>> and rainyear_start.
>>
>> On Aug 11, 2020, at 9:37 AM, Geni 0815  wrote:
>>
>> 
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> tmpname: /tmp/LoopDataz7h4ntn0
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> enable : 0
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> remote_server  : www.foobar.com
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> remote_port: None
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> remote_user: root
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: remote_dir   
>>   Af: /home/weewx/loop-data
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> compress   : 0
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> log_success: 0
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> ssh_options: -o ConnectTimeout=1
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> timeout: 1
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> skip_if_older_than : 3
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> time_delta : 10800
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> trend_obstypes : ['barometer', 'outTemp']
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> rainyear_obstypes  : ['outTemp', 'wind', 'windSpeed', 'windDir', 
>> 'windGust', 'windGustDir', 'rain']
>> Aug 11 18:05:41 Wetter-Raspi weewx[

Re: [weewx-user] Re: Module Error

[Mauro De Lauretis]

root@raspberrypi:/var/www/html/weewx/weather34/w34highcharts/scripts# cat 
plots_config.js

var pathjsonfiles =  "json/";//Location weewx report output 
json files from home location of weewx. DO NOT CHANGE UNLESS YOU CHANGE 
SKIN DIRECTORY.

var pathjsondayfiles = "json_day/";  //Location day report output json 
files from home location of where wee_report_34 run. DO NOT CHANGE UNLESS 
YOU CHANGE SKIN DIRECTORY.

var weereportcmd = "./wee_reports_w34";  //Command to run wee_report_34. DO 
NOT CHANGE.

var realtimefilename = "w34realtime.txt"; //File name must match what is in 
the weewx config for realtime


var autoupdateinterval = 60; //This is seconds

var realtimeinterval = 10;  //This is seconds

var hide_zero_wind_barb = false;  //Hide/display Zero Barb

var disable_day_plots = false; //Disable day plots


//[0] array offset(s) to wanted real-time data(s)(can be empty),[1] array 
offset(s) to data's real-time units(can be empty),[2] array of unit convert 
function(s)(can be empty), [3] plot type, [4] plot X resolution, [5] delta 
value

// The (can be empty) entries then must have a plot_type that is another 
plot type entry with fill in values this is how to display a different 
plot_type when using real-time data.

var realtimeplot = {


temperatureplot:[[2,4],[14,14],['convert_temp','convert_temp'],['temperatureplot'],[150]],


tempallplot:[[2,4,3],[14,14,-1],['convert_temp','convert_temp',null],['tempallplot'],
 
[150]],

winddirplot:[[7],[13],['convert_wind'],['winddirplot'], [150]],

windplot:[[6],[13],['convert_wind'],['windplot'],[150]],


windallplot:[[5,40,46],[13,13,-1],['convert_wind','convert_wind',null],['windallplot'],[150]],

barometerplot:[[10],[15],['convert_pressure'],['barometerplot'],[150]],


rainplot:[[47,8],[16,16],['convert_rain','convert_rain'],['rainplot'],[50],[]],

windroseplot:[[6,11],[13,-1],['convert_wind', 
null],['windroseplot'],[150]],

windrosegustplot:[[63,46],[13,-1],['convert_wind', 
null],['windrosegustplot'],[150]]

};

Il giorno mercoledì 12 agosto 2020 alle 10:13:47 UTC+2 Mauro De Lauretis ha 
scritto:

> The location of the executable is there because it is installed liked that 
> to run on the local server.
>
> If I try to do sudo PYTHONPATH=/home/weewx/bin python3 
> /var/www/html/weewx/weather34/w34highcharts/wee_reports_w34 I get this:
>
> *pi@raspberrypi*:*~ $* sudo su
>
> root@raspberrypi:/home/pi# sudo PYTHONPATH=/home/weewx/bin python3 
> /var/www/html/weewx/weather34/w34highcharts/wee_reports_w34
>
> Using configuration file /home/weewx/weewx.conf
>
> Generating for all time
>
> Traceback (most recent call last):
>
>   File "/var/www/html/weewx/weather34/w34highcharts/wee_reports_w34", line 
> 99, in 
>
> main()
>
>   File "/var/www/html/weewx/weather34/w34highcharts/wee_reports_w34", line 
> 68, in main
>
> config_dict['StdReport']['w34Highcharts']['CheetahGenerator'] =  
> {'search_list_extensions': 'user.w34highchartsSearchX.w34highcharts_' + 
> args[1].split('/')[-1].split('.')[0], 'encoding': 'strict_ascii', 'ToDate': 
> {'DayJSON': {'template': args[1],'HTML_ROOT': args[2]}}}
>
> IndexError: list index out of range
>
>
> Il giorno mercoledì 12 agosto 2020 alle 03:27:38 UTC+2 tke...@gmail.com 
> ha scritto:
>
>> You're probably right. I suspect the custom weather34 installer went a 
>> little ... off track. 
>>
>> On Tue, Aug 11, 2020 at 6:02 PM J D  wrote:
>>
>>> This is not a weewx issue or a python path issue. The file is in the 
>>> correct location, but the troubleshooting guide must be done to find out 
>>> why there is an error.
>>>
>>
>>>
>>> On Tuesday, August 11, 2020 at 3:27:16 PM UTC-7, Mauro De Lauretis wrote:

 Hi all!
 I'm running the last version of weewx with python3 on my Raspberry Pi.
 As skin I use the weather34 weewx version (
 https://github.com/steepleian/weewx-Weather34)

 There are also incorporated highcharts that are created live from the 
 database when selecting on the website.
 However, a part of them won't work with my setup and this Is the 
 message I get:


 root@raspberrypi:~# sudo python3 
 /var/www/html/weewx/weather34/w34highcharts/wee_reports_w34

 Traceback (most recent call last):

   File "/var/www/html/weewx/weather34/w34highcharts/wee_reports_w34", 
 line 8, in 

 import weewx

 ModuleNotFoundError: No module named 'weewx'




 Do you have any ideas what the issue could be?


 Thanks


 Mauro

>>> -- 
>>>
>> 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/ca782342-2160-4630-aee3-438d53a85c50o%40googlegroups.com
>>>  
>>

Re: [weewx-user] Re: Module Error

[Mauro De Lauretis]

This the syslog:

Aug 12 16:19:33 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...

Aug 12 16:19:36 raspberrypi weewx[14231] INFO __main__: Initializing weewx 
version 4.1.1

Aug 12 16:19:36 raspberrypi weewx[14231] INFO __main__: Using Python 3.7.3 
(default, Dec 20 2019, 18:57:59) #012[GCC 8.3.0]

Aug 12 16:19:36 raspberrypi weewx[14231] INFO __main__: Platform 
Linux-5.4.51+-armv6l-with-debian-10.4

Aug 12 16:19:36 raspberrypi weewx[14231] INFO __main__: Locale is 
'it_IT.UTF-8'

Aug 12 16:19:36 raspberrypi weewx[14231] INFO __main__: PID file is 
/var/run/weewx.pid

Aug 12 16:19:36 raspberrypi weewx[14220]: Starting weewx weather system: 
weewx.

Aug 12 16:19:36 raspberrypi systemd[1]: Started LSB: weewx weather system.

Aug 12 16:19:37 raspberrypi weewx[14240] INFO __main__: Using configuration 
file /home/weewx/weewx.conf

Aug 12 16:19:37 raspberrypi weewx[14240] INFO __main__: Debug is 1

Aug 12 16:19:37 raspberrypi weewx[14240] DEBUG __main__: Initializing engine

Aug 12 16:19:37 raspberrypi weewx[14240] INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)

Aug 12 16:19:37 raspberrypi weewx[14240] DEBUG weewx.drivers.vantage: 
Driver version is 3.2.1

Aug 12 16:19:37 raspberrypi weewx[14240] DEBUG weewx.drivers.vantage: 
Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00

Aug 12 16:19:37 raspberrypi weewx[14240] DEBUG weewx.drivers.vantage: 
Gentle wake up of console successful

Aug 12 16:19:37 raspberrypi weewx[14240] DEBUG weewx.drivers.vantage: 
Hardware type is 16

Aug 12 16:19:38 raspberrypi weewx[14240] DEBUG weewx.drivers.vantage: ISS 
ID is 1

Aug 12 16:19:38 raspberrypi weewx[14240] DEBUG weewx.drivers.vantage: 
Hardware name: Vantage Pro2

Aug 12 16:19:38 raspberrypi weewx[14240] DEBUG weewx.engine: Loading 
service weewx.engine.StdTimeSynch

Aug 12 16:19:38 raspberrypi weewx[14240] DEBUG weewx.engine: Finished 
loading service weewx.engine.StdTimeSynch

Aug 12 16:19:38 raspberrypi weewx[14240] DEBUG weewx.engine: Loading 
service weewx.engine.StdConvert

Aug 12 16:19:38 raspberrypi weewx[14240] INFO weewx.engine: StdConvert 
target unit is 0x10

Aug 12 16:19:38 raspberrypi weewx[14240] DEBUG weewx.engine: Finished 
loading service weewx.engine.StdConvert

Aug 12 16:19:38 raspberrypi weewx[14240] DEBUG weewx.engine: Loading 
service weewx.engine.StdCalibrate

Aug 12 16:19:38 raspberrypi weewx[14240] DEBUG weewx.engine: Finished 
loading service weewx.engine.StdCalibrate

Aug 12 16:19:38 raspberrypi weewx[14240] DEBUG weewx.engine: Loading 
service weewx.engine.StdQC

Aug 12 16:19:38 raspberrypi weewx[14240] DEBUG weewx.engine: Finished 
loading service weewx.engine.StdQC

Aug 12 16:19:38 raspberrypi weewx[14240] DEBUG weewx.engine: Loading 
service weewx.wxservices.StdWXCalculate

Aug 12 16:19:38 raspberrypi weewx[14240] DEBUG weewx.manager: Daily summary 
version is 2.0

Aug 12 16:19:38 raspberrypi weewx[14240] INFO weewx.wxservices: The 
following values will be calculated: pressure=prefer_hardware, 
altimeter=prefer_hardware, appTemp=prefer_hardware, 
barometer=prefer_hardware, beaufort=prefer_hardware, 
cloudbase=prefer_hardware, dewpoint=prefer_hardware, ET=prefer_hardware, 
heatindex=prefer_hardware, humidex=prefer_hardware, 
inDewpoint=prefer_hardware, maxSolarRad=prefer_hardware, 
rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware

Aug 12 16:19:38 raspberrypi weewx[14240] INFO weewx.wxservices: The 
following algorithms will be used for calculations: altimeter=aaASOS, 
maxSolarRad=RS

Aug 12 16:19:38 raspberrypi weewx[14240] DEBUG weewx.engine: Finished 
loading service weewx.wxservices.StdWXCalculate

Aug 12 16:19:38 raspberrypi weewx[14240] DEBUG weewx.engine: Loading 
service user.weather34.Weather34RealTime

Aug 12 16:19:39 raspberrypi weewx[14240] INFO user.weather34: service 
version is 0.0.5

Aug 12 16:19:39 raspberrypi weewx[14240] INFO user.weather34: output goes 
to /var/www/html/weewx/weather34/w34realtime.txt

Aug 12 16:19:39 raspberrypi weewx[14240] INFO user.weather34: 'None' values 
will be displayed as NULL

Aug 12 16:19:39 raspberrypi weewx[14240] INFO user.weather34: units will be 
displayed as METRICWX

Aug 12 16:19:39 raspberrypi weewx[14240] INFO user.weather34: zambretti 
forecast: False

Aug 12 16:19:39 raspberrypi weewx[14240] INFO user.weather34: Web Service: 
ds is installed

Aug 12 16:19:39 raspberrypi weewx[14240] INFO user.weather34: Web Service: 
me is installed

Aug 12 16:19:39 raspberrypi weewx[14240] INFO user.weather34: Web Service: 
eq is installed

Aug 12 16:19:39 raspberrypi weewx[14240] INFO user.weather34: Web Service: 
ki is installed

Aug 12 16:19:39 raspberrypi weewx[14240] INFO user.weather34: Web Service: 
wu is installed

Aug 12 16:19:39 raspberrypi weewx[14240] INFO user.weather34: Web Service: 
aq is installed

Aug 12 16:19:39 raspberrypi weewx[14240] INFO user.weather34: Web Service: 
al is installed

Aug 12 16:19:39 raspberrypi weewx[14240] DEBUG user.weather34: C

Re: [weewx-user] Re: Module Error

[Mauro De Lauretis]

Using verbosity=1, displaying most info


wee_debug output will be sent to stdout(console)


Using configuration file /home/weewx/weewx.conf

Using database binding 'wx_binding', which is bound to database 
'archive_sqlite'


System info

  Platform:   Linux-5.4.51+-armv6l-with-debian-10.4

  Python Version: 3.7.3


Load Information

  1 minute load average:  0.46

  5 minute load average:  0.46

  15 minute load average: 0.45


General Weewx info

  Weewx version 4.1.1 detected.


Station info

  Station type: Vantage

  Driver:   weewx.drivers.vantage


Driver info

[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 = serial



# 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 = 1.2.3.4



##

# 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 = 1



# 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


Currently installed extensions

No extensions installed


Archive info

  Database name:weewx.sdb

  Table name:   archive

  Version   2.0

  Unit system:  16 (METRIC)

  First good timestamp: 2020-08-03 14:10:00 CEST (1596456600)

  Last good timestamp:  2020-08-12 16:25:00 CEST (1597242300)

  Number of records:2613

  weewx (weewx.conf) is set to use an archive interval of 300 seconds.

  The station hardware was not interrogated in determining archive interval.


Databases configured in weewx.conf

  Database name:weewx.sdb

  Database driver:  weedb.sqlite


  Database name:weewx

  Database driver:  weedb.mysql

  Database host:localhost



Parsed and obfuscated weewx.conf

# WEEWX CONFIGURATION FILE

#

# Copyright (c) 2009-2019 Tom Keffer 

# See the file LICENSE.txt for your rights.


##


# This section is for general configuration information.


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

debug = 1


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

WEEWX_ROOT = /home/weewx


# Whether to log successful operations

log_success = True


# Whether to log unsuccessful operations

log_failure = True


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

socket_timeout = 20


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

version = 4.1.1


##


#   This section is for information about the station.


[Station]



# Description of the station location

location = "Pineto, Teramo"



# Latitude in decimal degrees. Negative for southern hemisphere

latitude = 42.634585

# Longitude in decimal degrees. Negative for western hemisphere.

longitude = 14.040554



# Altitude of the station, with unit it is in. This is downloaded from

# from the station if the hardware supports it.

altitude = 40, meter# Choose 'foot' or 'meter' for unit



# Set to type of station hardware. There must be a corresponding stanza

# in this file with a 'driver' parameter indicating the driver to be 
used.

station_type = Vantage



# If you have a website, you may specify an URL

station_url = XXX obfuscated by wee_debug XXX



# The start of the rain year (1=January; 10=October, etc.). This is

# downloaded from the station if the hardwa

Re: [weewx-user] Re: upgrade from weewx 3.9.2 to 4.1.1 doesn't work ...

[Tom Keffer]

As noted in the install page for Debian
, for stretch (Debian 9), you need to
use Python 2. So, you want


*wget -qO - http://weewx.com/apt/weewx-
python2.list | sudo tee
/etc/apt/sources.list.d/weewx.list*
*sudo apt-get update*
*sudo apt-get install weewx*

The reason is that not all packages are available for Python 3 on stretch.

-tk



On Tue, Aug 11, 2020 at 10:07 PM Geni 0815  wrote:

> pi@raspberrypi:~ $ PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
>
> pi@raspberrypi:~ $ NAME="Raspbian GNU/Linux"
>
> pi@raspberrypi:~ $ VERSION_ID="9"
>
> pi@raspberrypi:~ $ VERSION="9 (stretch)"
>
> pi@raspberrypi:~ $ VERSION_CODENAME=stretch
>
> pi@raspberrypi:~ $ ID=raspbian
>
> pi@raspberrypi:~ $ ID_LIKE=debian
>
> pi@raspberrypi:~ $ HOME_URL="http://www.raspbian.org/";
>
> pi@raspberrypi:~ $ SUPPORT_URL="http://www.raspbian.org/RaspbianForums";
>
> pi@raspberrypi:~ $ BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs";
>
>
> Am Dienstag, 11. August 2020 16:45:24 UTC+2 schrieb Tom Keffer:
>>
>> What version of Rasbian are you running?
>>
>> *cat /etc/os-release*
>>
>> -tk
>>
>> On Tue, Aug 11, 2020 at 7:25 AM geni08...@gmail.com 
>> wrote:
>>
>>> pi@raspberrypi:~ $ sudo apt install weewx
>>> Paketlisten werden gelesen... Fertig
>>> Abhängigkeitsbaum wird aufgebaut.
>>> Statusinformationen werden eingelesen Fertig
>>> Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
>>> Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
>>> Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
>>> nicht erstellt wurden oder Incoming noch nicht verlassen haben.
>>> Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu
>>> lösen:
>>>
>>> Die folgenden Pakete haben unerfüllte Abhängigkeiten:
>>>  weewx : Hängt ab von: python3-cheetah ist aber nicht installierbar
>>> E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene
>>> defekte Pakete.
>>> pi@raspberrypi:~ $
>>>
>>> tke...@gmail.com schrieb am Dienstag, 11. August 2020 um 14:30:02 UTC+2:
>>>
 I'm sorry: I just realized that your post is unrelated to the original
 post. We need some context to understand what you are trying to do. The
 screenshot you sent does not match your description of what you did. Are
 you truly upgrading? If so, from what version?

 What happens when you do a simple install:


 *wget -qO - http://weewx.com/apt/weewx-python3.list
  | sudo tee
 /etc/apt/sources.list.d/weewx.list*
 *sudo apt update*
 *sudo apt install weewx*

 -tk

 On Mon, Aug 10, 2020 at 10:44 PM geni08...@gmail.com <
 geni08...@gmail.com> wrote:

> I did this:
> wget -qO - http://weewx.com/apt/weewx-python3.list | sudo tee
> /etc/apt/sources.list.d/weewx.list
> sudo apt-get update
> sudo apt-get upgrade
> sudo apt install python3-mysqldb
> sudo apt install python3-ephem
> sudo apt-get update
> sudo apt-get upgrade
>
>
> tke...@gmail.com schrieb am Dienstag, 11. August 2020 um 02:56:50
> UTC+2:
>
>> (Please do not send a screen shot. They are hard to read, include
>> only a few lines, and cannot be translated. Cut and paste instead.)
>>
>> Did you do
>>
>> *sudo apt-get update*
>>
>> first?
>>
>> On Mon, Aug 10, 2020 at 10:02 AM geni08...@gmail.com <
>> geni08...@gmail.com> wrote:
>>
>>> Update gets stuck with errors from missing packages
>>> [image: weewx1.jpg]
>>>
>>> Jlou 43 schrieb am Dienstag, 4. August 2020 um 23:13:53 UTC+2:
>>>
  Thanks for your reply, but I solved my problem by reinstalling
 this way:


 3. Install WeeWX

 After installing the prerequisites, you can install WeeWX itself.

1.

Expand the source archive:

tar xvfz weewx-X.Y.Z.tar.gz

2.

Change directory into the expanded archive:

cd weewx-X.Y.Z

3.

To specify an install location different from the default
/home/weewx, modify the parameter home in the setup.cfg file.
Mac users will want to change it to /Users/Shared/weewx.
4.

Then build and install. Python 2 users: substitute python2 for
python3.

python3 ./setup.py build
sudo python3 ./setup.py install


 I replace python3 by python2 and now everything works perfectly, but
 if i have to switch to python3 your advice will be helpful.
 Thank you.


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

Re: [weewx-user] Re: Module Error

[Tom Keffer]

I see. So, it's being used as a CGI script?

Incidentally, I'm not seeing anything that could not be handled using the
regular weewx installer. I could be missing something subtle, but I don't
believe you need a custom installer. All of the items that need to go in
/var/www/html/weewx can be copied there by the CopyGenerator. Everything
else is in standard locations.

-tk

On Wed, Aug 12, 2020 at 1:06 AM  wrote:

> Tom and Gary,
>
>
>
> The only way in which I have been able to get the custom installer to fail
> is making a false step by making the wrong selection when prompted on how
> WeeWX was originally installed.
>
>
>
> Mauro has previously successfully installed this current version of
> Weather34 onto my test server with a clean install of WeeWX 4.1.1 /
> Python3, so the issue is ‘what is happening on his own setup’. I have asked
> Mauro to go back and start afresh on his own RaspberryPi with a clean
> install of WeeWX 4.1.1 and Python3, making sure all is working well with
> Simulator, install Weather34 and then follow the extensive troubleshooting
> guide that JD has devised and post the results here.
>
>
>
> The question regarding whether wee_reports_34 is running in the correct
> place. Yes it is rather unusual, but if you have a look at my website
> https://claydonsweather.org.uk and click on one of the pop-up chart links
> at the foot of the individual sensor modules you will see why. Choose a
> weekly chart for say barometer, hover and click on a chart data point and
> see what happens. Click again and a different scenario. It is this click
> which runs wee_reports_34.
>
>
>
> So back to the task in hand, hopefully we can get to the bottom of Mauro’s
> problems 😊
>
>
>
> Thanks for your continued support,
>
>
>
> Ian
>
>
>
> Sent from Mail  for
> Windows 10
>
>
>
> *From: *Tom Keffer 
> *Sent: *12 August 2020 02:27
> *To: *weewx-user 
> *Subject: *Re: [weewx-user] Re: Module Error
>
>
>
> You're probably right. I suspect the custom weather34 installer went a
> little ... off track.
>
>
>
> On Tue, Aug 11, 2020 at 6:02 PM J D  wrote:
>
> This is not a weewx issue or a python path issue. The file is in the
> correct location, but the troubleshooting guide must be done to find out
> why there is an error.
>
> On Tuesday, August 11, 2020 at 3:27:16 PM UTC-7, Mauro De Lauretis wrote:
>
> Hi all!
>
> I'm running the last version of weewx with python3 on my Raspberry Pi.
>
> As skin I use the weather34 weewx version (
> https://github.com/steepleian/weewx-Weather34)
>
>
>
> There are also incorporated highcharts that are created live from the
> database when selecting on the website.
>
> However, a part of them won't work with my setup and this Is the message I
> get:
>
>
>
>
>
> root@raspberrypi:~# sudo python3
> /var/www/html/weewx/weather34/w34highcharts/wee_reports_w34
>
> Traceback (most recent call last):
>
>   File "/var/www/html/weewx/weather34/w34highcharts/wee_reports_w34", line
> 8, in 
>
> import weewx
>
> ModuleNotFoundError: No module named 'weewx'
>
>
>
>
>
>
>
> Do you have any ideas what the issue could be?
>
>
>
> Thanks
>
>
>
> Mauro
>
> --
> 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/ca782342-2160-4630-aee3-438d53a85c50o%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/CAPq0zECtu0d8VYDWbm%3DUAEvU86JTU_Kf1rRKreuUNwO1xLf7pw%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/7A6EA92F-E1F7-4882-8023-11B2142314E2%40hxcore.ol
> 
> .
>

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

RE: [weewx-user] Re: Module Error

[steepleian]

Ok carry on with the other troubleshooting stages. Sent from Mail for Windows 10 From: Mauro De LauretisSent: 12 August 2020 16:03To: weewx-userSubject: Re: [weewx-user] Re: Module Error Changed into this: [StdReport]     # Where the skins reside, relative to WEEWX_ROOT    SKIN_ROOT = skins     # Where the generated reports should go, relative to WEEWX_ROOT    HTML_ROOT = /var/www/html/weewx     # The database binding indicates which data should be used in reports.    data_binding = wx_binding  No changes, still the same problem:root@raspberrypi:/var/www/html/weewx/weather34/w34highcharts# sudo python3 wee_reports_w34Traceback (most recent call last):  File "wee_reports_w34", line 8, in     import weewxModuleNotFoundError: No module named 'weewx'   Il giorno mercoledì 12 agosto 2020 alle 16:46:18 UTC+2 steep...@gmail.com ha scritto:Hi Mauro, You need to change HTML_ROOT in StdReport stanza to HTML_ROOT = /var/www/html/weewx  and restart WeeWX Wait for the next report cycle and I think things will improve. Ian On Wed, 12 Aug 2020 at 15:32, Mauro De Lauretis  wrote:Using verbosity=1, displaying most info wee_debug output will be sent to stdout(console) Using configuration file /home/weewx/weewx.confUsing database binding 'wx_binding', which is bound to database 'archive_sqlite' System info  Platform:       Linux-5.4.51+-armv6l-with-debian-10.4  Python Version: 3.7.3 Load Information  1 minute load average:  0.46  5 minute load average:  0.46  15 minute load average: 0.45 General Weewx info  Weewx version 4.1.1 detected. Station info  Station type: Vantage  Driver:       weewx.drivers.vantage Driver info[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 = serial        # 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 = 1.2.3.4        ##    # 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 = 1        # 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 Currently installed extensionsNo extensions installed Archive info  Database name:        weewx.sdb  Table name:           archive  Version               2.0  Unit system:          16 (METRIC)  First good timestamp: 2020-08-03 14:10:00 CEST (1596456600)  Last good timestamp:  2020-08-12 16:25:00 CEST (1597242300)  Number of records:    2613  weewx (weewx.conf) is set to use an archive interval of 300 seconds.  The station hardware was not interrogated in determining archive interval. Databases configured in weewx.conf  Database name:        weewx.sdb  Database driver:      weedb.sqlite   Database name:        weewx  Database driver:      weedb.mysql  Database host:        localhost  Parsed and obfuscated weewx.conf# WEEWX CONFIGURATION FILE## Copyright (c) 2009-2019 Tom Keffer # See the file LICENSE.txt for your rights. ## # This section is for general configuration information. # Set to 1 for extra debug info, otherwise comment it out or set to zerodebug = 1 # Root directory of the weewx data file hierarchy for this stationWEEWX_ROOT = /home/weewx # Whether to log successful operationslog_success = True # Whether to log unsuccessful operationslog_failure = True # How long to wait before timing out a socket (FTP, HTTP) connectionsocket_timeout = 20 # Do not modify this. It is used when installing and updating weewx.version = 4.1.1 ## #   This section is for information about the station. [Station]        # Description of the station location    location

Re: [weewx-user] Re: Questions about weewx-loopdata 2.x

[John Kline]

I’m happy to hear that it is working.  Thank you for trying it out!

> ...and there are 2 unit definitions for some.
I think you are asking about km_per_hour2 (as opposed to km_per_hour).  Here’s 
what http://weewx.com/docs/customizing.htm has to say about that:
group_speed2
This group is similar to group_speed, but is used for calculated wind speeds 
which typically have a slightly higher resolution. Possible options are one 
mile_per_hour2, km_per_hour2, knot2, or meter_per_second2.


> On Aug 12, 2020, at 7:07 AM, Geni 0815  wrote:
> 
> 
> Thanks for the explanation.
> 
> I had target_report = SeasonsReport, and there are 2 unit definitions for 
> some.
>  km_per_hour =% .0f
>  km_per_hour2 =% .1f
>  knot =% .0f
>  knot2 =% .1f
> meter_per_second = %.1f
> meter_per_second2 = %.1f
> mile_per_hour = %.0f
> mile_per_hour2 = %.1f
> 
>   I have now redefined target_report = LoopDataReport, now it works as desired
> 
> Am Mittwoch, 12. August 2020 14:56:16 UTC+2 schrieb John Kline:
>> 
>> > Where can I find a description of what a “Rain Year” is?
>> 
>> By default, rainyear is the same as year.  It’s the 12-month period for 
>> which the cumulative rain amount is measured.
>> See: https://en.wikipedia.org/wiki/Water_year
>> To set the rain year, see:  
>> http://weewx.com/docs/usersguide.htm#rain_year_start
>> 
>> > Where and how can I set that $wind.rms.formatted and 
>> > $windGust.max.formatted have a decimal place at km / h?
>> 
>> I’m assuming you mean .rms.formatted and 
>> .windGust.max.formatted (where  is 10m, day, week, month, 
>> year or rainyear).
>> 
>> Also assuming you want to see one decimal position in these values.
>> 
>> In the LoopDataReport section of weewx.conf, there is already 1 decimal 
>> place specified for km_per_hour (“%.1f”), unless you have changed it:
>>[[[Units]]]
>> StringFormats
>> mile_per_hour = %.1f
>> degree_C = %.1f
>> km_per_hour = %.1f
>> degree_F = %.1f 
>> 
>> I suspect you have a different target report specified:
>> Let’s imagine your [LoopData] section looks like this where the 
>> target_report is WeatherBoardReport:
>> 
>> [LoopData]
>> [[FileSpec]]
>> loop_data_dir = /home/weewx/gauge-data
>> filename = loop-data.txt
>> [[Formatting]]
>> target_report = WeatherBoardReport
>> 
>> In this case, you would to specify the decimal for km_per_hour under 
>> WeatherBoardReport, since that is the report you have specified for 
>> conversion and formattting.  You would want that report to specify the 
>> decimal place for km_per_hour.
>> 
>> [[WeatherBoardReport]]
>>[[[Units]]]
>> StringFormats
>> km_per_hour = %.1f
>> 
>> 
>>> On Aug 11, 2020, at 11:01 PM, Geni 0815  wrote:
>>> 
>>> 
>>> Hi John, Thanks for the new version.
>>> I still have the following questions:
>>> Where can I find a description of what a "Rain Year" is?
>>> Where and how can I set that $wind.rms.formatted and 
>>> $windGust.max.formatted also have a decimal place at km / h?
>>> Current Livelink
>>> 
>>> Am Mittwoch, 12. August 2020 03:20:18 UTC+2 schrieb John Kline:
 
 OK, I found the issue.  My tests simulate running weewx and processing 
 packets.  The issue was at startup where I use daily summaries to create 
 accumulators for day, week, year and rainyear.  That code was missing the 
 first daily summary of each of these periods.
 
 I’ve fixed this issue in v2.7.  Please give it a try.
 
> On Aug 11, 2020, at 9:41 AM, John Kline  wrote:
> 
> 
> It does not look like you have installed from head on github.
> 
> Go to this page:
> 
> https://github.com/chaunceygardiner/weewx-loopdata
> 
> Click “Code” and then click download zip.  Install that zip file.
> 
> When you do that, after time_delta in the log, you should see week_start 
> and rainyear_start.
> 
>> On Aug 11, 2020, at 9:37 AM, Geni 0815  wrote:
>> 
>> 
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: tmpname 
>>: /tmp/LoopDataz7h4ntn0
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: enable  
>>: 0
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> remote_server  : www.foobar.com
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: remote_port 
>>: None
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: remote_user 
>>: root
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: remote_dir  
>>Af: /home/weewx/loop-data
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: compress
>>: 0
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO

[weewx-user] Re: weather forecast inside the weewx standard skin seasons

[Vetti52]

Same question to me!

Although, I think, that the forecast extension from 
https://github.com/chaunceygardiner/weewx-forecast 

 
currently is the most promising approach. It should not be that complex, to 
integrate just one of the graphs into weewx season skin. However, without 
WU support!!! 

I am ready to cooperate!

To me, the main concern is using a reliable forecast for my region, which 
is not in the US, but in Germany! I would prefer to integrate forecast from 
"Deutscher Wetterdienst DWD". There is no API available, but they provide 
data from DWD-GeoWebService https://maps.dwd.de.  As I 
am not familiar with this kind of data handling, I ask for support. More 
information seems to be available at the Geoserver Manual 
, which is to my opinion a very universal 
source of data, so worth to have a look at it for Weewx developers.

Anyway. First of all, I will try to to integrate an openweathermap 
forecast, which seems to be currently supported by weewx-forecast, and is 
also available for my region. 

-- 
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/3c485927-4004-433c-a6f8-ad9f50e7ddb1o%40googlegroups.com.

[weewx-user] Re: Belchertown Skin, Websockets, Firefox Fail to Connect

[G Hammer]

Puzzling thing is, I just installed the latest version of the skin and it 
still fails in Firefox. At the same time, Pat's site loads and works fine.

-- 
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/634cf414-2e3d-4534-87f9-d3ebaf3ccff3o%40googlegroups.com.

Re: [weewx-user] Re: weather forecast inside the weewx standard skin seasons

[Graham Eddy]

the forecast extension produces html tables not jpgs - i found it easiest to 
integrate using iframes (i use ‘compact’ and ‘strip’ tables)

> On 13 Aug 2020, at 5:21 am, Vetti52  wrote:
> 
> Although, I think, that the forecast extension from 
> https://github.com/chaunceygardiner/weewx-forecast 
> currently
>  is the most promising approach. It should not be that complex, to integrate 
> just one of the graphs into weewx season skin. However, without WU support!!! 
> 

-- 
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/4E500D28-9337-46A9-88C1-80FCB51E488C%40gmail.com.

[weewx-user] Re: How to Show Battery Status with the New GW1000 Driver?

[gjr80]

Hi,

You are correct in that sensors.inc needs to be modified and you probably 
want to add a few entries to the Seasons skin.conf or weewx.conf as well. I 
have included a modified sensors.inc 
 
in the GW100 driver repo on GitHub. To modify Seasons to display GW100 
sensor battery states:

1. move aside your existing skins/Seasons/sensor.inc by renaming it to 
sensors_orig.inc. For setup.py installs:

$ sudo mv /home/weewx/skins/Seasons/sensors.inc /home/weewx/skins/Seasons/
sensors_orig.inc

or for package installs:

$ sudo mv /etc/weewx/skins/Seasons/sensors.inc /home/weewx/skins/Seasons/
sensors_orig.inc

2. download sensors.inc from the GW1000 driver GitHub repo, for setup.py 
installs:

$ wget -P /home/weewx/skins/Seasons https:
//raw.githubusercontent.com/gjr80/weewx-gw1000/master/supplementary/skins/Seasons/sensors.inc

or for package installs:

$ wget -P /etc/weewx/skins/Seasons https:
//raw.githubusercontent.com/gjr80/weewx-gw1000/master/supplementary/skins/Seasons/sensors.inc

3. edit sensors.inc and make the necessary changes to $sensor_batt_data to 
reflect the sensors connected to your GW1000. There are comments towards 
the top of the file that describe how to make the changes.

4. edit Seasons/skin.conf and if required add suitable descriptive names 
for each sensor state field under the [Labels] [[Generic]] stanza. These 
labels are the text that will appear for each sensor battery state entry in 
the Sensor Status panel. For example:

[Labels]

# Override some labels. No need to identify these as a "Battery"
# or "Voltage", because that is included in the template.
[[Generic]]

wh31_ch1_batt = Garage (WH31)
wh31_ch2_batt = Kitche (WH31)
wh41_ch1_batt = Dining (WH41)
wh51_ch1_batt = Front Garden (WH51)
wh51_ch3_batt = Flower Bed (WH51)
wh57_batt = Lightning (WH57)

You could also place these entries in weewx.conf under [StdReport] 
[[SeasonsReport]] [[Labels]]] Generic. The choice is yours, arguably 
weewx.conf is upgrade safe but it is highly unlikely that a WeeWX upgrade will 
make destructive changes to Seasons skin.conf.

5. On the next report cycle provided you have sensor battery state data in your 
archive record it should be included in the Seasons main page Sensor Status 
panel. Note you may have to refresh the page.

Gary




On Wednesday, 12 August 2020 00:15:33 UTC+10, Blaze wrote:
>
> Hi,
>
> How do I show the battery status for my Ecowitt weather sensors? This is a 
> default install running on "Ubuntu 20.04.1 LTS". I installed WeeWx using 
> the setup.py,  with Apache2, WeeWx v4.1.1 and the new GW1000 driver 
> (gw1000-0.1.0b10.tar.gz).  As you can see below I am getting the data, but 
> I don't understand how to get battery status to show on my page. I assume I 
> need to modify the "/home/weewx/skins/Seasons/sensors.inc" file, but I'm 
> not sure what I would need to add or change. Can someone give me pointers?
>
> Aug 10 03:05:25 myweewx weewx[14186] DEBUG gw1000: user.gw1000: Filtered 
> parsed data: {'intemp': 21.5, 'inhumid': 54, 'absbarometer': 985.8, 
> 'relbarometer': 985.8, 'outtemp': 24.0, 'outhumid': 80, 'soilmoist1': 53, 
> 'soilmoist2': 37, 'soilmoist3': 47, 'soilmoist4': 59, 'temp1': 19.3, 
> 'humid1': 59, 'wh26_batt': 0, 'wh31_ch1_batt': 0, 'wh51_ch1_batt': 0, 
> 'wh51_ch2_batt': 0, 'wh51_ch3_batt': 0, 'wh51_ch4_batt': 0, 
> 'wh51_ch5_batt': 0, 'datetime': 1597028725}
> Aug 10 03:05:25 myweewx weewx[14186] DEBUG gw1000: user.gw1000: Next 
> update in 60 seconds
> Aug 10 03:05:25 myweewx weewx[14186] DEBUG gw1000: user.gw1000: Augmented 
> packet: {'dateTime': 1597028725, 'usUnits': 17, 'inTemp': 21.5, 'outTemp': 
> 24.0, 'inHumidity': 54, 'outHumidity': 80, 'pressure': 985.8, 
> 'relbarometer': 985.8, 'extraTemp1': 19.3, 'extraHumid1': 59, 'soilMoist1': 
> 53, 'soilMoist2': 37, 'soilMoist3': 47, 'soilMoist4': 59, 'wh26_batt': 0, 
> 'wh31_ch1_batt': 0, 'wh51_ch1_batt': 0, 'wh51_ch2_batt': 0, 
> 'wh51_ch3_batt': 0, 'wh51_ch4_batt': 0, 'wh51_ch5_batt': 0}
>
> Thanks!
> Rob
>

-- 
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/103277e3-c643-4a6a-b540-9435f7bceda7o%40googlegroups.com.

[weewx-user] WS2300

['Dirk Soßna' via weewx-user]

Hello,

I have a Problem with the neasure of rain. the Station tells me, that it 
had rained but there was no rain. in the Display there are no rain 
mesurements.

what can I do to Change the readings.

regards

Dirk

-- 
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/7fd5dd2a-c3c9-40b8-a657-fbd2df2743c0o%40googlegroups.com.