[weewx-user] Re: Importing old station data via CSV: how to map time?

[gjr80]

If you were using 3.6.x it looks like issue #176 
 may have been causing the 
latest issue. This was fixed in 3.7.0.

Gary

On Thursday, 16 March 2017 11:15:19 UTC+10, Max G wrote:
>
> Hi Gary,
>
> Thank you kindly for checking this out for me...
> I think the thread and your response is important, as many have these 3081 
> weather stations...
>
> Well, I copied your field map straight into the config file:
>
> source = CSV
> file = /home/maxg/wwimport/test4import.txt
> interval = 10
> qc = True
> calc_missing = True
> tranche = 250
> UV_sensor = True
> solar_sensor = True
> raw_datetime_format = %d-%m-%Y %H:%M
> rain = discrete
> wind_direction = -360,360
>
> # test4import.txt:
> #No,Time,Interval(mi),Indoor Humidity(%),Indoor 
> Temperature(°C),Outdoor Humidity(%),Outdoor Temperature(°C),Absolute 
> Pressure(hPa),Wind(km/h),Gust(km/h),Direction,Relative 
> Pressure(hPa),Dewpoint(°C),Windchill(°C),Hour Rainfall(mm),24 hour 
> Rainfall(mm),Week Rainfall(mm),Month Rainfall(mm),Total Rainfall(mm),Wind 
> Level(bft),Gust Level(bft),lightmeter(lux),UV
> #1,16-02-2017 
> 09:00,10,57,28.8,64,26.2,993.1,2.5,5.0,NW,1012.0,18.9,26.2,0.0,0.0,0.0,0.9,654.0,1,1,86352.0,0
> #2,16-02-2017 
> 13:46,10,57,28.4,64,26.5,993.0,5.0,8.6,N,1010.6,19.2,26.5,0.0,0.0,0.0,0.9,654.0,1,2,148704.0,0
> #3,16-02-2017 
> 13:56,10,57,28.4,57,28.7,992.9,1.1,3.6,N,1010.5,19.4,28.7,0.0,0.0,0.0,0.9,654.0,1,1,96896.0,0
>
> [[FieldMap]]
> dateTime= Time
> usUnits =
> interval= Interval(mi), minute
> barometer   = Relative Pressure(hPa), hPa
> pressure= Absolute Pressure(hPa), hPa
> altimeter   =
> inTemp  = Indoor Temperature(°C), degree_C
> outTemp = Outdoor Temperature(°C), degree_C
> inHumidity  = Indoor Humidity(%), percent
> outHumidity = Outdoor Humidity(%), percent
> windSpeed   = Wind(km/h), km_per_hour
> windDir =
> windGust= Gust(km/h), km_per_hour
> windGustDir =
> rainRate=
> rain= Total Rainfall(mm), mm
> dewpoint= Dewpoint(°C), degree_C
> windchill   = Windchill(°C), degree_C
> heatindex   =
> ET  =
> radiation   =
> UV  = UV, uv_index
>
>
>
> and got the following result (failure):
>
> wee_import --import-config=/home/maxg/wwimport/csv.conf --dry-run
> Starting wee_import...
> A CSV import from source file '/home/maxg/wwimport/test4import.txt' has 
> been requested.
> Using database binding 'wx_binding', which is bound to database 
> 'weewx.sdb'
> Destination table 'archive' unit system is '0x01' (US).
> Missing derived observations will be calculated.
> This is a dry run, imported data will not be saved to archive.
>  Unable to parse source-to-weewx field map.
>  No mapping specified in '/home/maxg/wwimport/csv.conf' for field 
> 'dateTime'.
>  Nothing done, exiting.
>
>
> then I thought, you might be using the latest versions... so I upgraded to 
> 3.7, and get this (success):
>
> # [2017-03-16 11:02] maxg@rpi1b ~ $
> wee_import --import-config=/home/maxg/wwimport/csv.conf --dry-run
> Starting wee_import...
> A CSV import from source file '/home/maxg/wwimport/test4import.txt' has 
> been requested.
> Using database binding 'wx_binding', which is bound to database 
> 'weewx.sdb'
> Destination table 'archive' unit system is '0x01' (US).
> Missing derived observations will be calculated.
> This is a dry run, imported data will not be saved to archive.
> Starting dry run import ...
> 3 records identified for import.
> Records processed: 3; Unique records: 3; Last timestamp: 2017-02-16 13:56:
> 00 AEST (1487217360)
> Finished dry run import. 3 records were processed and 3 unique records 
> would have been imported.
>
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] use weewx db in wview

[Thomas Keffer]

The sqlite people claim that the database format is cross-platform, even
between 32 and 64 bit. Linky .

-tk

On Wed, Mar 15, 2017 at 3:44 PM,  wrote:

> The db move from weewx to wview worked fine, no problems. I used sqlite3
> .dump rather than just copy as I was going from 64-bit to 32. Done just in
> time as my weewx server crashed an hour later...  thanks again
>
> Bob
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] use weewx db in wview

[bgrattan]

The db move from weewx to wview worked fine, no problems. I used sqlite3 .dump 
rather than just copy as I was going from 64-bit to 32. Done just in time as my 
weewx server crashed an hour later...  thanks again

Bob

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: SteelSeries gauges .....No gauges are displayed

[Sam]

Gary Thank you so much.  I learned a little bit as well. Thanks for that 
too.

On Wednesday, March 15, 2017 at 5:23:49 PM UTC-4, gjr80 wrote:
>
> And there it is, missing comma at the end of line 38.
>
> Gary
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: SteelSeries gauges .....No gauges are displayed

[gjr80]

And there it is, missing comma at the end of line 38.

Gary

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx can't open USB port on Raspberry Pi

[Michael Wall]

I found my error and now weewx is working.
Michael

On Wednesday, March 15, 2017 at 11:39:06 AM UTC-7, Michael Wall wrote:
>
> I have tried over the past few days to get weewx running on a Raspberry Pi 
> 3 to read from my Davis Vantage Vue weather station. My Vantage console has 
> a serial output port set to 9600 baud. It then goes through a serial to USB 
> converter using a Prolific chip set. This configuration works well going 
> into a USB port on my PC running Win10 and using the Davis WeatherLink 
> software. I noticed in the attached Pi console view that the Pi wants to 
> put the USB connection to ttyUSB1 so I edited the weewx.conf file to use 
> the ttyUSB1 port. I think you can see all this on the attached screen view. 
> As you see weewx fails to see the Vantage port, I think.
>
> What should I do to correct this problem or should I wait a few hours and 
> see what happens?
>
> Thanks for your help.
>
> Michael
>
> Mar 15 11:13:51 raspberrypi kernel: [ 5124.813251] usb 1-1.2.3: new 
> full-speed USB device number 18 using dwc_otg
> Mar 15 11:13:51 raspberrypi kernel: [ 5124.915414] usb 1-1.2.3: New USB 
> device found, idVendor=067b, idProduct=2303
> Mar 15 11:13:51 raspberrypi kernel: [ 5124.915439] usb 1-1.2.3: New USB 
> device strings: Mfr=1, Product=2, SerialNumber=0
> Mar 15 11:13:51 raspberrypi kernel: [ 5124.915453] usb 1-1.2.3: Product: 
> USB-Serial Controller D
> Mar 15 11:13:51 raspberrypi kernel: [ 5124.915465] usb 1-1.2.3: 
> Manufacturer: Prolific Technology Inc. 
> Mar 15 11:13:51 raspberrypi kernel: [ 5124.916658] pl2303 1-1.2.3:1.0: 
> pl2303 converter detected
> Mar 15 11:13:51 raspberrypi kernel: [ 5124.920741] usb 1-1.2.3: pl2303 
> converter now attached to ttyUSB1
> Mar 15 11:13:51 raspberrypi systemd-udevd[3478]: failed to execute 
> '/lib/udev/mtp-probe' 'mtp-probe 
> /sys/devices/platform/soc/3f98.usb/usb1/1-1/1-1.2/1-1.2.3 1 18': No 
> such file or directory
> Mar 15 11:14:06 raspberrypi systemd[1]: Starting LSB: weewx weather 
> system...
> Mar 15 11:14:06 raspberrypi weewx[3515]: engine: Initializing weewx 
> version 3.7.0
> Mar 15 11:14:06 raspberrypi weewx[3515]: engine: Using Python 2.7.9 
> (default, Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
> Mar 15 11:14:06 raspberrypi weewx[3515]: engine: Platform 
> Linux-4.4.50-v7+-armv7l-with-debian-8.0
> Mar 15 11:14:06 raspberrypi weewx[3515]: engine: Locale is 'en_US.UTF-8'
> Mar 15 11:14:06 raspberrypi weewx[3515]: engine: pid file is 
> /var/run/weewx.pid
> Mar 15 11:14:06 raspberrypi weewx[3519]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> Mar 15 11:14:06 raspberrypi weewx[3519]: engine: debug is 1
> Mar 15 11:14:06 raspberrypi weewx[3519]: engine: Initializing engine
> Mar 15 11:14:06 raspberrypi weewx[3519]: engine: Loading station type 
> Vantage (weewx.drivers.vantage)
> Mar 15 11:14:06 raspberrypi weewx[3519]: vantage: driver version is 3.0.10
> Mar 15 11:14:06 raspberrypi weewx[3504]: Starting weewx weather system: 
> weewx.
> Mar 15 11:14:06 raspberrypi systemd[1]: Started LSB: weewx weather system.
> Mar 15 11:14:06 raspberrypi weewx[3519]: vantage: Opened up serial port 
> /dev/ttyUSB1; baud 9600; timeout 4.00
> Mar 15 11:14:10 raspberrypi weewx[3519]: vantage: retry  #0 failed
> Mar 15 11:14:14 raspberrypi weewx[3519]: vantage: retry  #1 failed
> Mar 15 11:14:18 raspberrypi weewx[3519]: vantage: retry  #2 failed
> Mar 15 11:14:22 raspberrypi weewx[3519]: vantage: retry  #3 failed
> Mar 15 11:14:22 raspberrypi weewx[3519]: vantage: Unable to wake up console
> Mar 15 11:14:22 raspberrypi weewx[3519]: import of driver failed: Unable 
> to wake up Vantage console ()
> Mar 15 11:14:23 raspberrypi weewx[3519]: engine: Unable to load driver: 
> Unable to wake up Vantage console
> Mar 15 11:14:23 raspberrypi weewx[3519]:   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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WindRose data file format

[gjr80]

If you are using a driver that had a genLoopPackets() method then weeWX will be 
producing/processing loop packets. As far as I know that is how the fileparse 
driver works.

Gary

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: SteelSeries gauges .....No gauges are displayed

[gjr80]

How about line 38? What does it contain, please copy it and post exactly as it 
is.

Gary

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: SteelSeries gauges .....No gauges are displayed

[Sam]

Gary,
gauges.js is in /var/www/html/weewx/ss/scripts.

The console throws out Uncaught SyntaxError: Unexpected identifier 
  gauges.js:39link address is   
http://192.168.1.125/weewx/ss/scripts/gauges.js
I am assuming that means there is a problem at line 39 in  gauges.js
Line 39 reads  oldGauges  : 'gauges.htm', //*** Change this 
to the relative path for your 'old' gauges page.



On Wednesday, March 15, 2017 at 3:22:29 AM UTC-4, gjr80 wrote:
>
> Ok, interesting. I just did a clean install of 3.7.0 via deb and followed 
> the instructions you listed and everything works fine. Now that I think 
> back not being able to find gauges.js can lead to no gauges being rendered 
> on screen. Can you confirm that gauges.js is in 
> /var/www/html/weewx/ss/scripts ?
>
> If it is we need to see if any javascript errors are being thrown. Can you 
> open the Browser Console in your browser, what this will be called varies I 
> think from browser to browser. I use firefox and it is under Developer, 
> Browser Console. Edge it is under F12 Developer Tools. You will need to 
> find it for your browser. Have a look at the Javascript console, are there 
> any errors there that apprear to relate to gauges.js etc.  Clear the log 
> and refresh your weewx/ss/index.html page in your broswer to see if any 
> errors come up.  If so what do they say?.
>
> Gary
>
>
> On Wednesday, 15 March 2017 14:17:34 UTC+10, Sam wrote:
>>
>>   Line 73 says   realTimeUrlWeewx   : 'gauge-data.txt', 
>>
>> On Tuesday, March 14, 2017 at 10:50:46 PM UTC-4, gjr80 wrote:
>>>
>>> Hi,
>>>
>>> I see nothing obviously wrong there. It's possible that the SteelSeries 
>>> Weather Gauges can't find you data file (gauge-data.txt), what do you 
>>> have against realTimeURL_weewx in gauges.js (it about line 68). This 
>>> tells the Steel Series Weatehr Gauges where to find you gauge-data.txt 
>>> file.
>>>
>>> Gary 
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: My reports do not run

[mwall]

On Wednesday, March 15, 2017 at 2:11:06 PM UTC-4, Theophanis Kontogiannis 
wrote:
>
> Hi all,
>
> Any idea why my reports do not run?
>
> My config file is here:  http://pastebin.com/PzJKvDxw
>
> No errors in the log file.
>

based on the log you posted, there are no problems.  you just need to wait.

your fine offset station has an archive interval of 1800 seconds (30 
minutes) - the factory default.  so you must wait that long to see any data.

you might consider changing your settings to a 5 minute archive interval 
and software record generation.

see the [FineOffsetUSB] section of the user guide:

http://weewx.com/docs/usersguide.htm#[Station]

or the fine offset section of the hardware guide for more details.

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: My reports do not run

[Theophanis Kontogiannis]

Log file with DEBUG=1:  http://pastebin.com/BzW6huaX

Thank you

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: My reports do not run

[vince]

On Wednesday, March 15, 2017 at 11:11:06 AM UTC-7, Theophanis Kontogiannis 
wrote:

> Any idea why my reports do not run?
>

not without seeing some logs, preferably with debug=1 in weewx.conf 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: My reports do not run

[Eelco F]

Are you sure there is no error in the logs? I usually have clues in the 
logs if there were errors.
What system are ou running on?

If you installed via .deb or apt-get take a look here: 

https://groups.google.com/forum/#!topic/weewx-user/ydhQftFQ2Ys

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] My reports do not run

[Theophanis Kontogiannis]

Hi all,

Any idea why my reports do not run?

My config file is here:  http://pastebin.com/PzJKvDxw

No errors in the log file.

Thank you

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Releasing V3.7.0

[mwall]

On Wednesday, March 15, 2017 at 12:19:23 PM UTC-4, Geoff Cusick wrote:
>
> I think the problem may persist.  Just updated to 3.7.0.
>

geoff,

the fix for post_interval was added after 3.7.0 was released.  it will be 
included in 3.7.1.

if you want to test it on a 3.7.0 installation, replace your restx.py with 
this one:

https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/restx.py

m 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: cannot find "alltime"

[Eelco F]

Ah, very well. We're all human aren't we? ;)

Keep up the good work Tom, I really apreciate weewx and all your effort 
very much.

Op woensdag 15 maart 2017 16:05:45 UTC+1 schreef Tom Keffer:
>
> Why isn't the stats file included in the deb package? It's not an 
>> extension is it?
>>
>
> ​An oversight. It will be included in v3.7.1.
>
> -tk​
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: cannot find "alltime"

[Thomas Keffer]

>
> Why isn't the stats file included in the deb package? It's not an
> extension is it?
>

​An oversight. It will be included in v3.7.1.

-tk​

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: cannot find "alltime"

[Thomas Keffer]

Simple typo. Should be MyStats, not Mystats.

-tk

On Wed, Mar 15, 2017 at 7:17 AM, Eelco F  wrote:

> Allright, I did check  /usr/share/weewx/user but that isn't bin/user
> right? So I wasn't sure to where he was referring to. I know things are
> different for setup.py en deb install.
>
> Originally there was no stats.py in /usr/share/weewx/user, after the
> upgrade to 3.7.0. So i copied it manually now from github to this directory
> as instructed.
> my skin.conf now has this line:  search_list_extensions =
> user.stats.Mystats
>
>
>
> I'm still having issues:
> Mar 15 15:10:15 kwsweerstation weewx[13955]: reportengine: Caught
> unrecoverable exception in generator weewx.cheetahgenerator.
> CheetahGenerator
> Mar 15 15:10:15 kwsweerstation weewx[13955]:   Module
> 'user.stats' has no attribute 'Mystats' when searching for
> 'user.stats.Mystats'
> Mar 15 15:10:15 kwsweerstation weewx[13955]:   Traceback (most
> recent call last):
> Mar 15 15:10:15 kwsweerstation weewx[13955]: File
> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
> Mar 15 15:10:15 kwsweerstation weewx[13955]:   obj.start()
> Mar 15 15:10:15 kwsweerstation weewx[13955]: File
> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
> Mar 15 15:10:15 kwsweerstation weewx[13955]:   self.run()
> Mar 15 15:10:15 kwsweerstation weewx[13955]: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 154, in run
> Mar 15 15:10:15 kwsweerstation weewx[13955]: 
>  self.initExtensions(gen_dict[section_name])
> Mar 15 15:10:15 kwsweerstation weewx[13955]: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 196, in initExtensions
> Mar 15 15:10:15 kwsweerstation weewx[13955]:   class_ =
> weeutil.weeutil._get_object(x)
> Mar 15 15:10:15 kwsweerstation weewx[13955]: File
> "/usr/share/weewx/weeutil/weeutil.py", line 1140, in _get_object
> Mar 15 15:10:15 kwsweerstation weewx[13955]:   raise
> AttributeError("Module '%s' has no attribute '%s' when searching for '%s'"
> % (mod.__name__, part, module_class))
> Mar 15 15:10:15 kwsweerstation weewx[13955]:   AttributeError:
> Module 'user.stats' has no attribute 'Mystats' when searching for
> 'user.stats.Mystats'
> Mar 15 15:10:15 kwsweerstation weewx[13955]:   Generator
> terminated
>
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WindRose data file format

[Robert Mantel]

Oh, maybe I can't because I'm using the fileparse extension to gather the 
sensor data from a text file that gets updated every two minutes with a 
python script running a json query to my raw sensor data server (phant 
server), or is the fileparse service also considered a loop packet 
generating service?

On Wednesday, 15 March 2017 09:00:56 UTC-4, gjr80 wrote:
>
>
> On Wednesday, 15 March 2017 22:33:52 UTC+10, Robert Mantel wrote:
>>
>> Sound like I should just install your extension, as it would provide what 
>> I need.  Even though my update rate is only every 2 minutes, I guess that 
>> would be realtime enough for me.
>>
>
> I guess that is up to you, if you want the programming challenge then roll 
> your own...
>
> The service is bound to loop packets so the file can be produced at most 
> once every loop period.
>
> One limitation is of my service is that since it is not tied to the 
> StdReport service you don't have the standard RSYNC and FTP 'reports' 
> available to transfer the resulting file should you need to transfer it to 
> another server. If your web server and weeWX machine are one and the same 
> you shouldn't have a problem.
>
> Gary
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: cannot find "alltime"

[Eelco F]

Oops, it should read: search_list_extensions = user.stats.MyStats, Iĺl try 
again

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: cannot find "alltime"

[Eelco F]

Allright, I did check  /usr/share/weewx/user but that isn't bin/user right? 
So I wasn't sure to where he was referring to. I know things are different 
for setup.py en deb install.

Originally there was no stats.py in /usr/share/weewx/user, after the 
upgrade to 3.7.0. So i copied it manually now from github to this directory 
as instructed.
my skin.conf now has this line:  search_list_extensions = user.stats.Mystats



I'm still having issues:
Mar 15 15:10:15 kwsweerstation weewx[13955]: reportengine: Caught 
unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
Mar 15 15:10:15 kwsweerstation weewx[13955]:   Module 
'user.stats' has no attribute 'Mystats' when searching for 
'user.stats.Mystats'
Mar 15 15:10:15 kwsweerstation weewx[13955]:   Traceback (most 
recent call last):
Mar 15 15:10:15 kwsweerstation weewx[13955]: File 
"/usr/share/weewx/weewx/reportengine.py", line 239, in run
Mar 15 15:10:15 kwsweerstation weewx[13955]:   obj.start()
Mar 15 15:10:15 kwsweerstation weewx[13955]: File 
"/usr/share/weewx/weewx/reportengine.py", line 273, in start
Mar 15 15:10:15 kwsweerstation weewx[13955]:   self.run()
Mar 15 15:10:15 kwsweerstation weewx[13955]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 154, in run
Mar 15 15:10:15 kwsweerstation weewx[13955]:  
 self.initExtensions(gen_dict[section_name])
Mar 15 15:10:15 kwsweerstation weewx[13955]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 196, in initExtensions
Mar 15 15:10:15 kwsweerstation weewx[13955]:   class_ = 
weeutil.weeutil._get_object(x)
Mar 15 15:10:15 kwsweerstation weewx[13955]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1140, in _get_object
Mar 15 15:10:15 kwsweerstation weewx[13955]:   raise 
AttributeError("Module '%s' has no attribute '%s' when searching for '%s'" 
% (mod.__name__, part, module_class))
Mar 15 15:10:15 kwsweerstation weewx[13955]:   AttributeError: 
Module 'user.stats' has no attribute 'Mystats' when searching for 
'user.stats.Mystats'
Mar 15 15:10:15 kwsweerstation weewx[13955]:   Generator 
terminated


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: cannot find "alltime"

[vince]

On Wednesday, March 15, 2017 at 6:51:14 AM UTC-7, Eelco F wrote:

> However I'm afraid I don quite follow your references to the directories. 
> There is no such directory as /bin/user on my systems. So where exactly 
> should the stats.py reside on a ubuntu/debian system?
>
>
Read carefully, he said bin/user (ie, the user directory under the weewx 
$BINDIR) and not /bin/user (a hyptothetical user subdirectory under the os 
/bin tree)

You probably want to check out 
http://www.weewx.com/docs/usersguide.htm#Where_to_find_things in the User's 
Guide to find the location.  Best guess is /usr/share/weewx/bin/user for a 
Debian system.  You might have to create the directory (sorry - I run 
setup.py so I can't check easily from here).

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: cannot find "alltime"

[Eelco F]

Dear Gary,

I think this is the issue, thank you for pointing that out. Shouldn't the 
installer just take care of this?

However I'm afraid I don quite follow your references to the directories. 
There is no such directory as /bin/user on my systems. So where exactly 
should the stats.py reside on a ubuntu/debian system?

Eelco



Op woensdag 15 maart 2017 11:10:28 UTC+1 schreef gjr80:
>
> Ok, as far as I can tell the examples directory is not in the deb package 
> so anyone using apt-get or dpkg will not have an examples directory. You 
> can download the stats.py file directly from GitHub by typing the 
> following from the command line on your weeWX machine:
>
> $ wget https://
> raw.githubusercontent.com/weewx/weewx/master/examples/stats.py
>
> That will download stats.py to the current directory, you can then copy 
> it to the bin/user directory.
>
> Gary
>
> On Wednesday, 15 March 2017 19:54:00 UTC+10, gjr80 wrote:
>>
>> Hi Eelco and VM-83,
>>
>> I thought this had been answered but apparently not. WeeWX 3.7.0 saw the 
>> examples moved out of the bin directory and the xsearch.py SLE example 
>> was renamed stats.py. Similarly, the MyXSearch SLE was renamed MyStats 
>> (the MyXSearch SLE, now MyStats,provides the $alltime and $seven_day 
>> tags). Admittedly it was the 28th item in the change log included in the 
>> release 
>> post 
>> :
>>
>> Moved examples out of bin directory.  Eliminated experimental directory.
>> Reinforce the use of user directory, eliminate use of examples directory.
>> Renamed xsearch.py to stats.py.
>>
>> To get things working again you will need to copy the file stats.py from 
>> the examples directory to your bin/user directory (the examples 
>> directory is now in /home/weewx for a setup.py install, not so sure 
>> about rpm or deb packages though). Also, in skin.conf the line:
>>
>> search_list_extensions = examples.xsearch.MyXSearch
>>
>> will need to be changed to:
>>
>> search_list_extensions = user.stats.MyStats
>>
>> This should restore the $alltime and $seven_day tags.
>>
>> Gary
>>
>> On Wednesday, 15 March 2017 19:17:52 UTC+10, Eelco F wrote:
>>>
>>> I'm having the same issue, as I posted in a separate post. Sorry, I 
>>> overlooked this thread.
>>>
>>> I have weewx running on ubuntu 16.04.2. I upgraded from 3.6.2 to 3.7.0. 
>>> I must say I always performed a manual update until 3.6.2. Now I added the 
>>> repository and upgraded by apt-get.
>>>
>>> after that, I got this:
>>>
>>> Mar 15 09:50:17 weerstation weewx[1446]: reportengine: Caught 
>>> unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
>>> Mar 15 09:50:17 weerstation weewx[1446]:   No module named 
>>> examples.xsearch
>>> Mar 15 09:50:17 weerstation weewx[1446]:   Traceback (most 
>>> recent call last):
>>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>>> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
>>> Mar 15 09:50:17 weerstation weewx[1446]:   obj.start()
>>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>>> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
>>> Mar 15 09:50:17 weerstation weewx[1446]:   self.run()
>>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 154, in run
>>> Mar 15 09:50:17 weerstation weewx[1446]:  
>>>  self.initExtensions(gen_dict[section_name])
>>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 196, in initExtensions
>>> Mar 15 09:50:17 weerstation weewx[1446]:   class_ = 
>>> weeutil.weeutil._get_object(x)
>>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>>> "/usr/share/weewx/weeutil/weeutil.py", line 1132, in _get_object
>>> Mar 15 09:50:17 weerstation weewx[1446]:   mod = 
>>> __import__(module)
>>> Mar 15 09:50:17 weerstation weewx[1446]:   ImportError: No 
>>> module named examples.xsearch
>>> Mar 15 09:50:17 weerstation weewx[1446]:   Generator 
>>> terminated
>>> Mar 15 09:50:17 weerstation weewx[1446]: imagegenerator: Generated 11 
>>> images for StandardReport in 0.13 seconds
>>>
>>>
>>> In my skin .conf there is this reference:
>>> search_list_extensions = examples.xsearch.MyXSearch
>>> I also tried to comment this out, it breaks things even further, as was 
>>> said by TS.
>>>
>>>
>>>
>>>
>>> Op zondag 12 maart 2017 11:50:47 UTC+1 schreef Erwin Heger:

 It won't solve itself by posting  several times ... 

 First answer the questions of matthew, afterwards we know a bit more 
 and can give better advise. 

 Erwin 

 > Am 12.03.2017 um 11:40 schrieb VM_83 : 
 > 
 > First i made an update from V.3.6.2 to v.3.7.0 
 > 
 the skin cannot find the 

[weewx-user] Re: WindRose data file format

[gjr80]

On Wednesday, 15 March 2017 22:33:52 UTC+10, Robert Mantel wrote:
>
> Sound like I should just install your extension, as it would provide what 
> I need.  Even though my update rate is only every 2 minutes, I guess that 
> would be realtime enough for me.
>

I guess that is up to you, if you want the programming challenge then roll 
your own...

The service is bound to loop packets so the file can be produced at most 
once every loop period.

One limitation is of my service is that since it is not tied to the 
StdReport service you don't have the standard RSYNC and FTP 'reports' 
available to transfer the resulting file should you need to transfer it to 
another server. If your web server and weeWX machine are one and the same 
you shouldn't have a problem.

Gary

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Using MariaDB/MySQL with non-standard directories

[Thomas Keffer]

Thanks, Theo, for your digging and, thanks to you, I learned something.

In general, we don't mention these things in the weewx documentation, as
they are part of the MySQL / Maria admin world. Indeed, there are many
other such database admin comments we could add, such as the use of
triggers, timeouts, character sets, etc. If the user is going to be using
MySQL, we expect him/her to be conversant in its administration.

-tk



On Wed, Mar 15, 2017 at 5:34 AM, Theophanis Kontogiannis 
wrote:

> Hi Tom,
>
> I read through this: http://mysql-python.sourceforge.net/MySQLdb.html#id6
> 
>
> And I think that the magic words are:
>
> *Okay, so you want to use _mysql anyway. Here are some examples.*
>
> *The simplest possible database connection is:*
>
> *import _mysql*
>
> *db=_mysql.connect()*
>
>
>
> *This creates a connection to the MySQL server running on the local
> machine* *using the standard UNIX socket (or named pipe on Windows),**
> your login name (from the USER environment variable), no password, and does
> not USE a database. Chances are you need to supply more information.:*
>
> *db=_mysql.connect("localhost","joebob","moonpie","thangs")*
>
>
>
> *This creates a connection to the MySQL server running on the local
> machine via a UNIX socket (or named pipe), the user name "joebob", the
> password "moonpie", and selects the initial database "thangs".*
>
> *We haven't even begun to touch upon all the parameters connect() can
> take. For this reason, I prefer to use keyword parameters:*
>
> *db=_mysql.connect(host="localhost",user="joebob",*
> * passwd="moonpie",db="thangs")*
>
>
>
> *This does exactly what the last example did, but is arguably easier to
> read. But since the default host is "localhost", and if your login name
> really was "joebob", you could shorten it to this:*
>
> *db=_mysql.connect(passwd="moonpie",db="thangs")*
>
>
>
> *UNIX sockets and named pipes don't work over a network, so if you specify
> a host other than localhost, TCP will be used, and you can specify an odd
> port if you need to (the default port is 3306):*
>
> *db=_mysql.connect(host="outhouse",port=3307,passwd="moonpie",db="thangs")*
>
>
>
> *If you really had to, you could connect to the local host with TCP by
> specifying the full host name, or 127.0.0.1.*
>
>
>
> This is the standard behavior. To connect to the standard unix socket
> which is /var/lib/mysql/mysql.sock
>
> As my socket is in /mnt/services/DBs/mysql/mysql.sock  there is no config
> in MySQLdb to point it to that path.
>
> It is black white according to the document above.
>
> Use 'locahost' and point MySQLdb to the standard socket (I do not use
> standard socket) or use 127.0.0.1 and go for TCP/IP (on port 3306).
>
> Hence my thought on explicitly mentioning that in weewx docs cause people
> do use non-standard sockets.
>
> My python knowledge is minimal so I am digging info based on my SysAdm
> experience.
>
> Hope it helps and shorts things out.
>
> BR
> Theo
>
>
>
> On Tuesday, March 14, 2017 at 10:50:59 PM UTC+2, Tom Keffer wrote:
>>
>> I think you're right.
>>
>> >>> from MySQLdb import connect
>> >>> #   No port number specified:
>> >>> conn = connect(host='localhost', user='weewx',passwd='weewx')
>> >>> conn.get_host_info()
>> 'Localhost via UNIX socket'
>> >>> conn.close()
>> >>> #   Add a port number:
>> >>> conn = connect(host='localhost', port=3306, user='weewx',
>> passwd='weewx')
>> >>> conn.get_host_info()
>> 'Localhost via UNIX socket'
>> >>> conn.close()
>> >>> conn = connect(host='127.0.0.1', user='weewx',passwd='weewx')
>> >>> conn.get_host_info()
>> '127.0.0.1 via TCP/IP'
>>
>> Sorry for questioning you. Somewhere along the line when I was developing
>> weedb, I came under the impression that it was the presence or absence of
>> the port that controlled whether a TCP/IP or socket connection was used.
>>
>> Unfortunately, I still can't help you on why you're unable to connect
>> with the socket. There does not seem to be any MySQLdb function that
>> returns what socket it expects to be communicating with. Or, at least, I
>> can't find it.
>>
>> You can try the exercise above to see what communication protocol your
>> installation is using. I'd be interested to see if it's different from mine.
>>
>> -tk
>>
>> On Tue, Mar 14, 2017 at 1:16 PM, Theophanis Kontogiannis <
>> tko...@gmail.com> wrote:
>>
>>> This is not what I got after testing it.
>>>
>>> Please read in line the per use case test result (with the new mysql.py
>>> code)
>>>
>>> On Tuesday, March 14, 2017 at 10:02:12 PM UTC+2, Tom Keffer wrote:

 Let me try again:

- If hostname is localhost *or 127.0.0.1*, but no port is supplied:
use sockets.

 No.
>>> If it is localhost it uses socket.
>>> If it is 127.0.0.1 it uses TCP/IP.
>>>

- If hostname is localhost* or 127.0.0.1*, but a port is supplied:
use TCP/IP.

 No.
>>> If it is 127.0.0.1+port 

Re: [weewx-user] Re: error after update to 3.7.0

[Thomas Keffer]

​See the post
https://groups.google.com/d/msg/weewx-user/ydhQftFQ2Ys/i8422WUgBAAJ and
beyond.

-tk​

On Wed, Mar 15, 2017 at 2:01 AM, Eelco F  wrote:

> There is this reference in my skin.conf:
>
> search_list_extensions = examples.xsearch.MyXSearch
>
> if I comment this out, I even get some more errors:
>
>
> cheetahgenerator: Generate failed with exception ' 'NameMapper.NotFound'>'
> Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator:  Ignoring
> template /etc/weewx/skins/Aangepast/trend.html.tmpl
> Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator:  Reason:
> cannot find 'alltime'
> Mar 15 10:00:17 weerstation weewx[1446]:   Traceback (most recent call
> last):
> Mar 15 10:00:17 weerstation weewx[1446]: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 329, in generate
> Mar 15 10:00:17 weerstation weewx[1446]:   print >> _file,
> compiled_template
> Mar 15 10:00:17 weerstation weewx[1446]: File
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in
> __str__
> Mar 15 10:00:17 weerstation weewx[1446]:   rc = getattr(self,
> mainMethName)()
> Mar 15 10:00:17 weerstation weewx[1446]: File
> "_etc_weewx_skins_Aangepast_trend_html_tmpl.py", line 530, in respond
> Mar 15 10:00:17 weerstation weewx[1446]:   NotFound: cannot find
> 'alltime'
> Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator: Generate failed
> with exception ''
> Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator:  Ignoring
> template /etc/weewx/skins/Aangepast/smartphone/temp_outside.html.tmpl
> Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator:  Reason:
> cannot find 'seven_day'
> Mar 15 10:00:17 weerstation weewx[1446]:   Traceback (most recent call
> last):
> Mar 15 10:00:17 weerstation weewx[1446]: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 329, in generate
> Mar 15 10:00:17 weerstation weewx[1446]:   print >> _file,
> compiled_template
> Mar 15 10:00:17 weerstation weewx[1446]: File
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in
> __str__
> Mar 15 10:00:17 weerstation weewx[1446]:   rc = getattr(self,
> mainMethName)()
> Mar 15 10:00:17 weerstation weewx[1446]: File
> "_etc_weewx_skins_Aangepast_smartphone_temp_outside_html_tmpl.py", line
> 125, in respond
> Mar 15 10:00:17 weerstation weewx[1446]:   NotFound: cannot find
> 'seven_day'
> Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator: Generate failed
> with exception ''
> Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator:  Ignoring
> template /etc/weewx/skins/Aangepast/week.html.tmpl
> Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator:  Reason:
> cannot find 'seven_day'
> Mar 15 10:00:18 weerstation weewx[1446]:   Traceback (most recent call
> last):
> Mar 15 10:00:18 weerstation weewx[1446]: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 329, in generate
> Mar 15 10:00:18 weerstation weewx[1446]:   print >> _file,
> compiled_template
> Mar 15 10:00:18 weerstation weewx[1446]: File
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in
> __str__
> Mar 15 10:00:18 weerstation weewx[1446]:   rc = getattr(self,
> mainMethName)()
> Mar 15 10:00:18 weerstation weewx[1446]: File
> "_etc_weewx_skins_Aangepast_week_html_tmpl.py", line 125, in respond
> Mar 15 10:00:18 weerstation weewx[1446]:   NotFound: cannot find
> 'seven_day'
> Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator: Generate failed
> with exception ''
> Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator:  Ignoring
> template /etc/weewx/skins/Aangepast/smartphone/wind.html.tmpl
> Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator:  Reason:
> cannot find 'seven_day'
> Mar 15 10:00:18 weerstation weewx[1446]:   Traceback (most recent call
> last):
> Mar 15 10:00:18 weerstation weewx[1446]: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 329, in generate
> Mar 15 10:00:18 weerstation weewx[1446]:   print >> _file,
> compiled_template
> Mar 15 10:00:18 weerstation weewx[1446]: File
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in
> __str__
> Mar 15 10:00:18 weerstation weewx[1446]:   rc = getattr(self,
> mainMethName)()
> Mar 15 10:00:18 weerstation weewx[1446]: File
> "_etc_weewx_skins_Aangepast_smartphone_wind_html_tmpl.py", line 127, in
> respond
> Mar 15 10:00:18 weerstation weewx[1446]:   NotFound: cannot find
> 'seven_day'
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to 

Re: [weewx-user] Using MariaDB/MySQL with non-standard directories

[Theophanis Kontogiannis]

Hi Tom,

I read through this: http://mysql-python.sourceforge.net/MySQLdb.html#id6 


And I think that the magic words are:

*Okay, so you want to use _mysql anyway. Here are some examples.*

*The simplest possible database connection is:*

*import _mysql*

*db=_mysql.connect()*

 

*This creates a connection to the MySQL server running on the local machine* 
*using 
the standard UNIX socket (or named pipe on Windows),** your login name 
(from the USER environment variable), no password, and does not USE a 
database. Chances are you need to supply more information.:*

*db=_mysql.connect("localhost","joebob","moonpie","thangs")*

 

*This creates a connection to the MySQL server running on the local machine 
via a UNIX socket (or named pipe), the user name "joebob", the password 
"moonpie", and selects the initial database "thangs".*

*We haven't even begun to touch upon all the parameters connect() can take. 
For this reason, I prefer to use keyword parameters:*

*db=_mysql.connect(host="localhost",user="joebob",*
* passwd="moonpie",db="thangs")*

 

*This does exactly what the last example did, but is arguably easier to 
read. But since the default host is "localhost", and if your login name 
really was "joebob", you could shorten it to this:*

*db=_mysql.connect(passwd="moonpie",db="thangs")*

 

*UNIX sockets and named pipes don't work over a network, so if you specify 
a host other than localhost, TCP will be used, and you can specify an odd 
port if you need to (the default port is 3306):*

*db=_mysql.connect(host="outhouse",port=3307,passwd="moonpie",db="thangs")*

 

*If you really had to, you could connect to the local host with TCP by 
specifying the full host name, or 127.0.0.1.*



This is the standard behavior. To connect to the standard unix socket which 
is /var/lib/mysql/mysql.sock

As my socket is in /mnt/services/DBs/mysql/mysql.sock  there is no config 
in MySQLdb to point it to that path.

It is black white according to the document above.

Use 'locahost' and point MySQLdb to the standard socket (I do not use 
standard socket) or use 127.0.0.1 and go for TCP/IP (on port 3306).

Hence my thought on explicitly mentioning that in weewx docs cause people 
do use non-standard sockets. 

My python knowledge is minimal so I am digging info based on my SysAdm 
experience.

Hope it helps and shorts things out.

BR
Theo



On Tuesday, March 14, 2017 at 10:50:59 PM UTC+2, Tom Keffer wrote:
>
> I think you're right. 
>
> >>> from MySQLdb import connect
> >>> #   No port number specified:
> >>> conn = connect(host='localhost', user='weewx',passwd='weewx')
> >>> conn.get_host_info()
> 'Localhost via UNIX socket'
> >>> conn.close()
> >>> #   Add a port number:
> >>> conn = connect(host='localhost', port=3306, user='weewx', 
> passwd='weewx')
> >>> conn.get_host_info()
> 'Localhost via UNIX socket'
> >>> conn.close()
> >>> conn = connect(host='127.0.0.1', user='weewx',passwd='weewx')
> >>> conn.get_host_info()
> '127.0.0.1 via TCP/IP'
>
> Sorry for questioning you. Somewhere along the line when I was developing 
> weedb, I came under the impression that it was the presence or absence of 
> the port that controlled whether a TCP/IP or socket connection was used.
>
> Unfortunately, I still can't help you on why you're unable to connect with 
> the socket. There does not seem to be any MySQLdb function that returns 
> what socket it expects to be communicating with. Or, at least, I can't find 
> it.
>
> You can try the exercise above to see what communication protocol your 
> installation is using. I'd be interested to see if it's different from mine.
>
> -tk
>
> On Tue, Mar 14, 2017 at 1:16 PM, Theophanis Kontogiannis  > wrote:
>
>> This is not what I got after testing it.
>>
>> Please read in line the per use case test result (with the new mysql.py 
>> code)
>>
>> On Tuesday, March 14, 2017 at 10:02:12 PM UTC+2, Tom Keffer wrote:
>>>
>>> Let me try again:
>>>
>>>- If hostname is localhost *or 127.0.0.1*, but no port is supplied: 
>>>use sockets.
>>>
>>> No. 
>> If it is localhost it uses socket. 
>> If it is 127.0.0.1 it uses TCP/IP.
>>
>>>
>>>- If hostname is localhost* or 127.0.0.1*, but a port is supplied: 
>>>use TCP/IP.
>>>
>>> No. 
>> If it is 127.0.0.1+port it uses TCP/IP
>> If it is localhost+port it uses socket. 
>>
>>>
>>>- If hostname is anything else, use TCP/IP.
>>>
>>> Correct
>>  
>>
>>> If you want to use sockets, you should *not* specify a port number. It 
>>> only makes sense: you are not using TCP/IP, so why would it need a port 
>>> number?
>>>
>>
>> For testing the various use cases.
>>
>> In my case however I am using non standard location for the socket, but 
>> weedb does not honour the MySQL configuration for that.
>>  
>>
>>>
>>> As far as why your server cannot connect to the mysql.sock socket, I 
>>> can't say. That's a MariaDB / MySQLDB question.
>>>
>>
>> Correct. 
>>  
>>
>>> 

[weewx-user] Re: WindRose data file format

[Robert Mantel]

Sound like I should just install your extension, as it would provide what I 
need.  Even though my update rate is only every 2 minutes, I guess that 
would be realtime enough for me.

On Tuesday, 14 March 2017 19:49:33 UTC-4, gjr80 wrote:
>
> Hi,
>
> Short of going to Mark Crossley the SteelSeries Weather Gauges author and 
> asking him directly (which I am sure he would answer, I have found him very 
> approachable), there is no definitive definition of what the WindRoseData 
> field is to contain. We can deduce a few things about it from various 
> sources.
>
> 1. the field should contain a comma separated list of 8 or 16 numbers 
> (corresponding to the 8 ordinal points of a compass or the 16 points of a 
> wind compass). Whether you can use a different number ofvalues I don't know 
> (eg 4 if you only want the cardinal points or 5 if you live in a pentary 
> world)
> 2. the first number is the 'North' value, the others progressively move 
> around the compass in a clockwise direction
> 3. the WindRoseData numbers appear to be normalised before plotting (ie 
> the absolute value of the numbers is not important rather it is the 
> relative proprtions that are important)
> 4. Cumulus has a #WindRoseData# webtag that is descibed in the Cumulus 
> wiki  as "A 
> comma-separated list of the wind 'totals' used to draw the wind rose (8 or 
> 16 values)". (The developer of the SteelSeries Weather Gauges is a Cumulus 
> user and that is where you will find a lot of SteelSeries Weather Gauges 
> info). I have not found anything that defines what "wind 'totals'" are, is 
> it the number of windDir samples that fall in the respective arc, are 
> these weighted with windSpeed etc. I have taken it to be the windSpeed 
> weighted 
> count of windDir falling in the sector concerned. It is fairly easy to 
> generate a query on the weeWX archive that will give the raw data and a 
> little bit of python can then be used to fashion the raw data into a 
> WindRoseData list. You can see what I have done if you look at 
> calc_windrose() function in rtgd.py here 
> 
> .
>
> Gary
>
> On Wednesday, 15 March 2017 08:26:27 UTC+10, Robert Mantel wrote:
>>
>> I'm looking to create a python script to generate my own wind rose data 
>> using json queries from my phant server which stores the raw sensor data 
>> from my station.  My question is, what format is the WindRoseData=[] line 
>> looking for?  Is it just populating a list, is it in pairs of wind 
>> direction and speed?  I'm having a hard time figuring this out from the 
>> gauges.js script.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Weewx doesn't start after upgrade to 3.7

[a . kienleitner]

Hi!

I updated weewx to v3.7. 
Now it doesn't start anymore and I get the following error message:

Mar 15 12:23:08 *** systemd[1]: Starting Weewx weather station interface 
and internet weather updater...
Mar 15 12:23:09 *** weewx[5030]: engine: Initializing weewx version 3.7.0
Mar 15 12:23:09 *** weewx[5030]: engine: Using Python 2.7.13 (default, Dec 
26 2016, 20:43:13)
 [GCC 6.2.1 20160830]
Mar 15 12:23:10 *** weewx[5030]: engine: Platform 
Linux-4.9.13-3-ARCH-armv6l-with-glibc2.4
Mar 15 12:23:10 *** weewx[5030]: engine: Locale is 'C'
Mar 15 12:23:10 *** weewx[5030]: engine: pid file is /var/run/weewx.pid
Mar 15 12:23:10 *** systemd[1]: weewx.service: Supervising process 5034 
which is not our child. We'll most likely not notice when it exits.
Mar 15 12:23:10 *** systemd[1]: Started Weewx weather station interface and 
internet weather updater.
Mar 15 12:23:10 *** weewx[5034]: engine: Using configuration file 
/home/weewx/weewx.conf
Mar 15 12:23:10 *** weewx[5034]: engine: Loading station type WMR100 
(weewx.drivers.wmr100)
Mar 15 12:23:10 *** weewx[5034]: import of driver failed: global name 
'loginf' is not defined ()
Mar 15 12:23:10 *** weewx[5034]: engine: Unable to load driver: global name 
'loginf' is not defined
Mar 15 12:23:10 *** weewx[5034]:   Exiting...
Mar 15 12:23:10 *** systemd[1]: weewx.service: Main process exited, 
code=exited, status=4/NOPERMISSION
Mar 15 12:23:10 *** kill[5036]: kill: not enough arguments
Mar 15 12:23:10 *** systemd[1]: weewx.service: Control process exited, 
code=exited status=1
Mar 15 12:23:10 *** systemd[1]: weewx.service: Unit entered failed state.
Mar 15 12:23:10 *** systemd[1]: weewx.service: Failed with result 
'exit-code'.


I,m running 2 RPIs with arch linux and with one wmrs200 and wmr180.


BR
Andreas

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: cannot find "alltime"

[gjr80]

Ok, as far as I can tell the examples directory is not in the deb package 
so anyone using apt-get or dpkg will not have an examples directory. You 
can download the stats.py file directly from GitHub by typing the following 
from the command line on your weeWX machine:

$ wget https:
//raw.githubusercontent.com/weewx/weewx/master/examples/stats.py

That will download stats.py to the current directory, you can then copy it 
to the bin/user directory.

Gary

On Wednesday, 15 March 2017 19:54:00 UTC+10, gjr80 wrote:
>
> Hi Eelco and VM-83,
>
> I thought this had been answered but apparently not. WeeWX 3.7.0 saw the 
> examples moved out of the bin directory and the xsearch.py SLE example 
> was renamed stats.py. Similarly, the MyXSearch SLE was renamed MyStats 
> (the MyXSearch SLE, now MyStats,provides the $alltime and $seven_day 
> tags). Admittedly it was the 28th item in the change log included in the 
> release 
> post 
> :
>
> Moved examples out of bin directory.  Eliminated experimental directory.
> Reinforce the use of user directory, eliminate use of examples directory.
> Renamed xsearch.py to stats.py.
>
> To get things working again you will need to copy the file stats.py from 
> the examples directory to your bin/user directory (the examples directory 
> is now in /home/weewx for a setup.py install, not so sure about rpm or 
> deb packages though). Also, in skin.conf the line:
>
> search_list_extensions = examples.xsearch.MyXSearch
>
> will need to be changed to:
>
> search_list_extensions = user.stats.MyStats
>
> This should restore the $alltime and $seven_day tags.
>
> Gary
>
> On Wednesday, 15 March 2017 19:17:52 UTC+10, Eelco F wrote:
>>
>> I'm having the same issue, as I posted in a separate post. Sorry, I 
>> overlooked this thread.
>>
>> I have weewx running on ubuntu 16.04.2. I upgraded from 3.6.2 to 3.7.0. I 
>> must say I always performed a manual update until 3.6.2. Now I added the 
>> repository and upgraded by apt-get.
>>
>> after that, I got this:
>>
>> Mar 15 09:50:17 weerstation weewx[1446]: reportengine: Caught 
>> unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
>> Mar 15 09:50:17 weerstation weewx[1446]:   No module named 
>> examples.xsearch
>> Mar 15 09:50:17 weerstation weewx[1446]:   Traceback (most 
>> recent call last):
>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
>> Mar 15 09:50:17 weerstation weewx[1446]:   obj.start()
>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
>> Mar 15 09:50:17 weerstation weewx[1446]:   self.run()
>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 154, in run
>> Mar 15 09:50:17 weerstation weewx[1446]:  
>>  self.initExtensions(gen_dict[section_name])
>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 196, in initExtensions
>> Mar 15 09:50:17 weerstation weewx[1446]:   class_ = 
>> weeutil.weeutil._get_object(x)
>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>> "/usr/share/weewx/weeutil/weeutil.py", line 1132, in _get_object
>> Mar 15 09:50:17 weerstation weewx[1446]:   mod = 
>> __import__(module)
>> Mar 15 09:50:17 weerstation weewx[1446]:   ImportError: No 
>> module named examples.xsearch
>> Mar 15 09:50:17 weerstation weewx[1446]:   Generator 
>> terminated
>> Mar 15 09:50:17 weerstation weewx[1446]: imagegenerator: Generated 11 
>> images for StandardReport in 0.13 seconds
>>
>>
>> In my skin .conf there is this reference:
>> search_list_extensions = examples.xsearch.MyXSearch
>> I also tried to comment this out, it breaks things even further, as was 
>> said by TS.
>>
>>
>>
>>
>> Op zondag 12 maart 2017 11:50:47 UTC+1 schreef Erwin Heger:
>>>
>>> It won't solve itself by posting  several times ... 
>>>
>>> First answer the questions of matthew, afterwards we know a bit more and 
>>> can give better advise. 
>>>
>>> Erwin 
>>>
>>> > Am 12.03.2017 um 11:40 schrieb VM_83 : 
>>> > 
>>> > First i made an update from V.3.6.2 to v.3.7.0 
>>> > 
>>> the skin cannot find the 'alltime' search list extension.  cannot say 
>>> how to fix it without knowing more about your configuration. 
>>>
>>> how did you do the upgrade?  what version of weewx were you running 
>>> before? 
>>>
>>> what's in the skin.conf for sofaskin? 
>>>
>>> what's in your weewx configuration file? 
>>>
>>

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

Re: [weewx-user] Re: cannot find "alltime"

[gjr80]

Hi Eelco and VM-83,

I thought this had been answered but apparently not. WeeWX 3.7.0 saw the 
examples moved out of the bin directory and the xsearch.py SLE example was 
renamed stats.py. Similarly, the MyXSearch SLE was renamed MyStats (the 
MyXSearch SLE, now MyStats,provides the $alltime and $seven_day tags). 
Admittedly it was the 28th item in the change log included in the release 
post :

Moved examples out of bin directory.  Eliminated experimental directory.
Reinforce the use of user directory, eliminate use of examples directory.
Renamed xsearch.py to stats.py.

To get things working again you will need to copy the file stats.py from 
the examples directory to your bin/user directory (the examples directory 
is now in /home/weewx for a setup.py install, not so sure about rpm or deb 
packages though). Also, in skin.conf the line:

search_list_extensions = examples.xsearch.MyXSearch

will need to be changed to:

search_list_extensions = user.stats.MyStats

This should restore the $alltime and $seven_day tags.

Gary

On Wednesday, 15 March 2017 19:17:52 UTC+10, Eelco F wrote:
>
> I'm having the same issue, as I posted in a separate post. Sorry, I 
> overlooked this thread.
>
> I have weewx running on ubuntu 16.04.2. I upgraded from 3.6.2 to 3.7.0. I 
> must say I always performed a manual update until 3.6.2. Now I added the 
> repository and upgraded by apt-get.
>
> after that, I got this:
>
> Mar 15 09:50:17 weerstation weewx[1446]: reportengine: Caught 
> unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
> Mar 15 09:50:17 weerstation weewx[1446]:   No module named 
> examples.xsearch
> Mar 15 09:50:17 weerstation weewx[1446]:   Traceback (most 
> recent call last):
> Mar 15 09:50:17 weerstation weewx[1446]: File 
> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
> Mar 15 09:50:17 weerstation weewx[1446]:   obj.start()
> Mar 15 09:50:17 weerstation weewx[1446]: File 
> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
> Mar 15 09:50:17 weerstation weewx[1446]:   self.run()
> Mar 15 09:50:17 weerstation weewx[1446]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 154, in run
> Mar 15 09:50:17 weerstation weewx[1446]:  
>  self.initExtensions(gen_dict[section_name])
> Mar 15 09:50:17 weerstation weewx[1446]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 196, in initExtensions
> Mar 15 09:50:17 weerstation weewx[1446]:   class_ = 
> weeutil.weeutil._get_object(x)
> Mar 15 09:50:17 weerstation weewx[1446]: File 
> "/usr/share/weewx/weeutil/weeutil.py", line 1132, in _get_object
> Mar 15 09:50:17 weerstation weewx[1446]:   mod = 
> __import__(module)
> Mar 15 09:50:17 weerstation weewx[1446]:   ImportError: No 
> module named examples.xsearch
> Mar 15 09:50:17 weerstation weewx[1446]:   Generator terminated
> Mar 15 09:50:17 weerstation weewx[1446]: imagegenerator: Generated 11 
> images for StandardReport in 0.13 seconds
>
>
> In my skin .conf there is this reference:
> search_list_extensions = examples.xsearch.MyXSearch
> I also tried to comment this out, it breaks things even further, as was 
> said by TS.
>
>
>
>
> Op zondag 12 maart 2017 11:50:47 UTC+1 schreef Erwin Heger:
>>
>> It won't solve itself by posting  several times ... 
>>
>> First answer the questions of matthew, afterwards we know a bit more and 
>> can give better advise. 
>>
>> Erwin 
>>
>> > Am 12.03.2017 um 11:40 schrieb VM_83 : 
>> > 
>> > First i made an update from V.3.6.2 to v.3.7.0 
>> > 
>> the skin cannot find the 'alltime' search list extension.  cannot say how 
>> to fix it without knowing more about your configuration. 
>>
>> how did you do the upgrade?  what version of weewx were you running 
>> before? 
>>
>> what's in the skin.conf for sofaskin? 
>>
>> what's in your weewx configuration file? 
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: cannot find "alltime"

[Eelco F]

On a second system, I'm getting the same error after the update. After that 
i manually re-installed 3.7.0 by dpkg -i. The issue still persists.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: cannot find "alltime"

[Eelco F]

I'm having the same issue, as I posted in a separate post. Sorry, I 
overlooked this thread.

I have weewx running on ubuntu 16.04.2. I upgraded from 3.6.2 to 3.7.0. I 
must say I always performed a manual update until 3.6.2. Now I added the 
repository and upgraded by apt-get.

after that, I got this:

Mar 15 09:50:17 weerstation weewx[1446]: reportengine: Caught unrecoverable 
exception in generator weewx.cheetahgenerator.CheetahGenerator
Mar 15 09:50:17 weerstation weewx[1446]:   No module named 
examples.xsearch
Mar 15 09:50:17 weerstation weewx[1446]:   Traceback (most 
recent call last):
Mar 15 09:50:17 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/reportengine.py", line 239, in run
Mar 15 09:50:17 weerstation weewx[1446]:   obj.start()
Mar 15 09:50:17 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/reportengine.py", line 273, in start
Mar 15 09:50:17 weerstation weewx[1446]:   self.run()
Mar 15 09:50:17 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 154, in run
Mar 15 09:50:17 weerstation weewx[1446]:  
 self.initExtensions(gen_dict[section_name])
Mar 15 09:50:17 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 196, in initExtensions
Mar 15 09:50:17 weerstation weewx[1446]:   class_ = 
weeutil.weeutil._get_object(x)
Mar 15 09:50:17 weerstation weewx[1446]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1132, in _get_object
Mar 15 09:50:17 weerstation weewx[1446]:   mod = 
__import__(module)
Mar 15 09:50:17 weerstation weewx[1446]:   ImportError: No 
module named examples.xsearch
Mar 15 09:50:17 weerstation weewx[1446]:   Generator terminated
Mar 15 09:50:17 weerstation weewx[1446]: imagegenerator: Generated 11 
images for StandardReport in 0.13 seconds


In my skin .conf there is this reference:
search_list_extensions = examples.xsearch.MyXSearch
I also tried to comment this out, it breaks things even further, as was 
said by TS.




Op zondag 12 maart 2017 11:50:47 UTC+1 schreef Erwin Heger:
>
> It won't solve itself by posting  several times ... 
>
> First answer the questions of matthew, afterwards we know a bit more and 
> can give better advise. 
>
> Erwin 
>
> > Am 12.03.2017 um 11:40 schrieb VM_83  >: 
> > 
> > First i made an update from V.3.6.2 to v.3.7.0 
> > 
> the skin cannot find the 'alltime' search list extension.  cannot say how 
> to fix it without knowing more about your configuration. 
>
> how did you do the upgrade?  what version of weewx were you running 
> before? 
>
> what's in the skin.conf for sofaskin? 
>
> what's in your weewx configuration file? 
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: error after update to 3.7.0

[Eelco F]

There is this reference in my skin.conf:

search_list_extensions = examples.xsearch.MyXSearch

if I comment this out, I even get some more errors:


cheetahgenerator: Generate failed with exception ''
Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Aangepast/trend.html.tmpl
Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator:  Reason: 
cannot find 'alltime'
Mar 15 10:00:17 weerstation weewx[1446]:   Traceback (most recent call 
last):
Mar 15 10:00:17 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 329, in generate
Mar 15 10:00:17 weerstation weewx[1446]:   print >> _file, 
compiled_template
Mar 15 10:00:17 weerstation weewx[1446]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Mar 15 10:00:17 weerstation weewx[1446]:   rc = getattr(self, 
mainMethName)()
Mar 15 10:00:17 weerstation weewx[1446]: File 
"_etc_weewx_skins_Aangepast_trend_html_tmpl.py", line 530, in respond
Mar 15 10:00:17 weerstation weewx[1446]:   NotFound: cannot find 
'alltime'
Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator: Generate failed 
with exception ''
Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Aangepast/smartphone/temp_outside.html.tmpl
Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator:  Reason: 
cannot find 'seven_day'
Mar 15 10:00:17 weerstation weewx[1446]:   Traceback (most recent call 
last):
Mar 15 10:00:17 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 329, in generate
Mar 15 10:00:17 weerstation weewx[1446]:   print >> _file, 
compiled_template
Mar 15 10:00:17 weerstation weewx[1446]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Mar 15 10:00:17 weerstation weewx[1446]:   rc = getattr(self, 
mainMethName)()
Mar 15 10:00:17 weerstation weewx[1446]: File 
"_etc_weewx_skins_Aangepast_smartphone_temp_outside_html_tmpl.py", line 
125, in respond
Mar 15 10:00:17 weerstation weewx[1446]:   NotFound: cannot find 
'seven_day'
Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator: Generate failed 
with exception ''
Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Aangepast/week.html.tmpl
Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator:  Reason: 
cannot find 'seven_day'
Mar 15 10:00:18 weerstation weewx[1446]:   Traceback (most recent call 
last):
Mar 15 10:00:18 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 329, in generate
Mar 15 10:00:18 weerstation weewx[1446]:   print >> _file, 
compiled_template
Mar 15 10:00:18 weerstation weewx[1446]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Mar 15 10:00:18 weerstation weewx[1446]:   rc = getattr(self, 
mainMethName)()
Mar 15 10:00:18 weerstation weewx[1446]: File 
"_etc_weewx_skins_Aangepast_week_html_tmpl.py", line 125, in respond
Mar 15 10:00:18 weerstation weewx[1446]:   NotFound: cannot find 
'seven_day'
Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator: Generate failed 
with exception ''
Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Aangepast/smartphone/wind.html.tmpl
Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator:  Reason: 
cannot find 'seven_day'
Mar 15 10:00:18 weerstation weewx[1446]:   Traceback (most recent call 
last):
Mar 15 10:00:18 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 329, in generate
Mar 15 10:00:18 weerstation weewx[1446]:   print >> _file, 
compiled_template
Mar 15 10:00:18 weerstation weewx[1446]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Mar 15 10:00:18 weerstation weewx[1446]:   rc = getattr(self, 
mainMethName)()
Mar 15 10:00:18 weerstation weewx[1446]: File 
"_etc_weewx_skins_Aangepast_smartphone_wind_html_tmpl.py", line 127, in 
respond
Mar 15 10:00:18 weerstation weewx[1446]:   NotFound: cannot find 
'seven_day'

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Best weather analyzing and presentation software?

[Ruben Navarro Huedo]

A lot of thanks 
Email sent 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: SteelSeries gauges .....No gauges are displayed

[gjr80]

Ok, interesting. I just did a clean install of 3.7.0 via deb and followed 
the instructions you listed and everything works fine. Now that I think 
back not being able to find gauges.js can lead to no gauges being rendered 
on screen. Can you confirm that gauges.js is in 
/var/www/html/weewx/ss/scripts ?

If it is we need to see if any javascript errors are being thrown. Can you 
open the Browser Console in your browser, what this will be called varies I 
think from browser to browser. I use firefox and it is under Developer, 
Browser Console. Edge it is under F12 Developer Tools. You will need to 
find it for your browser. Have a look at the Javascript console, are there 
any errors there that apprear to relate to gauges.js etc.  Clear the log 
and refresh your weewx/ss/index.html page in your broswer to see if any 
errors come up.  If so what do they say?.

Gary


On Wednesday, 15 March 2017 14:17:34 UTC+10, Sam wrote:
>
>   Line 73 says   realTimeUrlWeewx   : 'gauge-data.txt', 
>
> On Tuesday, March 14, 2017 at 10:50:46 PM UTC-4, gjr80 wrote:
>>
>> Hi,
>>
>> I see nothing obviously wrong there. It's possible that the SteelSeries 
>> Weather Gauges can't find you data file (gauge-data.txt), what do you 
>> have against realTimeURL_weewx in gauges.js (it about line 68). This 
>> tells the Steel Series Weatehr Gauges where to find you gauge-data.txt 
>> file.
>>
>> Gary 
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.