[weewx-user] Davis vantage pro2 - Upgrading wind sensor - upgrading weewx?

2016-12-03 Thread Jacek Skowroński
Hi guys,
Today I had upgrade my ecosystem. I had added external sensor for wind. To 
be exact I dissatached wind sensor from ISS and attached it for external 
module. Set it up with ID=3.
When I put wee_device I see
 TRANSMITTERS:
  Channel 1:iss
  Channel 2:soil
  Channel 3:wind
  Channel 4:(N/A)
  Channel 5:(N/A)
  Channel 6:(N/A)
  Channel 7:(N/A)
  Channel 8:(N/A)


Console shows wind ok, weewx site shows wind, but it seems like there is no 
gusts. I mean average wind is same as gusts.
Do I have to configure something in weewx to tell the sw that I have 
external module for wind?

Regards
Jacek

-- 
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 on Linux set top box

2016-11-26 Thread Jacek Skowroński
Have anybody of You tried runing weewx on Linux set top box like vu+?
There is quad core cpu 1.3ghz 256ram memory sata disk
Maybe It would be more stable than Pi?

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


Re: [weewx-user] Re: davis - system stoped to collect and send data

2016-11-26 Thread Jacek Skowroński
pi@raspberrypi:~ $ sudo wee_device --clear-memory
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.0.9 (weewx.drivers.vantage)
Proceeding will erase old archive records.
Are you sure you wish to proceed (y/n)? y
Clearing the archive memory ...
Archive records cleared.





On Saturday, November 26, 2016 at 2:11:25 PM UTC+1, Tom Keffer wrote:
>
> I can't tell for sure, but this is probably a simple case of logger memory 
> corruption. As Gary suggests, the cure is to clear the memory
>
> wee_device --clear-memory
>
> Running weewx with debug=1 will give a more definitive diagnosis.
>
> -tk
>
> On Sat, Nov 26, 2016 at 5:03 AM, Jacek Skowroński <yac...@gmail.com 
> > wrote:
>
>> I did restart yesterday,
>> First Pi, then davis.
>> After whole night and half of the day I get such logs.
>> pi@raspberrypi:~ $ tail -f /var/log/syslog
>> Nov 26 13:45:17 raspberrypi weewx[634]: reportengine: copied 0 files to /
>> var/www/html/weewx
>> Nov 26 13:45:26 raspberrypi weewx[634]: reportengine: ftp'd 26 files in 
>> 8.37 seconds
>> Nov 26 13:50:17 raspberrypi weewx[634]: cheetahgenerator: Generated 14 
>> files for report StandardReport in 1.64 seconds
>> Nov 26 13:50:17 raspberrypi weewx[634]: genimages: Generated 12 images 
>> for StandardReport in 0.60 seconds
>> Nov 26 13:50:17 raspberrypi weewx[634]: reportengine: copied 0 files to 
>> /var/www/html/weewx
>> Nov 26 13:50:25 raspberrypi weewx[634]: reportengine: ftp'd 26 files in 
>> 8.28 seconds
>> Nov 26 13:55:17 raspberrypi weewx[634]: cheetahgenerator: Generated 14 
>> files for report StandardReport in 1.66 seconds
>> Nov 26 13:55:17 raspberrypi weewx[634]: genimages: Generated 12 images 
>> for StandardReport in 0.61 seconds
>> Nov 26 13:55:17 raspberrypi weewx[634]: reportengine: copied 0 files to /
>> var/www/html/weewx
>> Nov 26 13:55:26 raspberrypi weewx[634]: reportengine: ftp'd 26 files in 
>> 8.37 seconds
>>
>> On my webpage: http://boleslawice.info/
>> Data are 17hours old.
>> On WU 
>> http://wunderground.com/personal-weather-station/dashboard?ID=IWOJEWDZ56 
>> data seems to be ok, but WU is set up in the RapidFire
>> What should I do to get data?
>> How can I check the database? file weewx.sdb is updated 3 minutes ago. 
>>
>> On Friday, November 25, 2016 at 10:54:49 PM UTC+1, Jacek Skowroński wrote:
>>>
>>> Hi, I had lost my old config, had to go for old sd card.
>>> System started to collect old data - from last 4 days.Send it to the 
>>> webpage - boleslawice.info, WU and other weather system and then 
>>> stopped to collect data.
>>>
>>> Now I have something like:
>>> pi@raspberrypi:~ $ tail -f /var/log/syslog
>>> Nov 25 22:41:42 raspberrypi weewx[631]: restx: Wunderground-PWS: Data 
>>> for station IWOJEWDZ56 will be posted
>>> Nov 25 22:41:42 raspberrypi weewx[631]: restx: PWSWeather: Data for 
>>> station YACENTY2 will be posted
>>> Nov 25 22:41:42 raspberrypi weewx[631]: restx: CWOP: Posting not enabled.
>>> Nov 25 22:41:42 raspberrypi weewx[631]: restx: WOW: Data for station 
>>> 976406001 will be posted
>>> Nov 25 22:41:42 raspberrypi weewx[631]: restx: AWEKAS: Data will be 
>>> uploaded for user yacenty
>>> Nov 25 22:41:42 raspberrypi weewx[631]: engine: Starting up weewx 
>>> version 3.6.2
>>> Nov 25 22:41:42 raspberrypi weewx[631]: engine: Clock error is -6.36 
>>> seconds (positive is fast)
>>> Nov 25 22:41:42 raspberrypi weewx[631]: vantage: Clock set to 2016-11-25 
>>> 22:41:43 CET (1480110103)
>>> Nov 25 22:41:43 raspberrypi weewx[631]: engine: Starting main packet 
>>> loop.
>>> Nov 25 22:41:48 raspberrypi weewx[631]: vantage: LOOP try #1; error: 
>>> Expected to read 99 chars; got 0 instead
>>> Nov 25 22:45:18 raspberrypi weewx[631]: cheetahgenerator: Generated 14 
>>> files for report StandardReport in 1.63 seconds
>>> Nov 25 22:45:18 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
>>> next retry is Fri Nov 25 22:45:48 2016 [try 
>>> http://www.rsyslog.com/e/2007 ]
>>> Nov 25 22:45:18 raspberrypi weewx[631]: genimages: Generated 12 images 
>>> for StandardReport in 0.60 seconds
>>> Nov 25 22:45:18 raspberrypi weewx[631]: reportengine: copied 9 files to 
>>> /var/www/html/weewx
>>> Nov 25 22:45:31 raspberrypi weewx[631]: reportengine: ftp'd 35 files in 
>>> 13.07 seconds
>>> Nov 25 22:50:18 raspberrypi weewx[631]: cheetahgenerator: Generated 14 
>>> files for report StandardReport in 1.64 second

[weewx-user] Re: davis - system stoped to collect and send data

2016-11-26 Thread Jacek Skowroński
I did restart yesterday,
First Pi, then davis.
After whole night and half of the day I get such logs.
pi@raspberrypi:~ $ tail -f /var/log/syslog
Nov 26 13:45:17 raspberrypi weewx[634]: reportengine: copied 0 files to /var
/www/html/weewx
Nov 26 13:45:26 raspberrypi weewx[634]: reportengine: ftp'd 26 files in 
8.37 seconds
Nov 26 13:50:17 raspberrypi weewx[634]: cheetahgenerator: Generated 14 
files for report StandardReport in 1.64 seconds
Nov 26 13:50:17 raspberrypi weewx[634]: genimages: Generated 12 images for 
StandardReport in 0.60 seconds
Nov 26 13:50:17 raspberrypi weewx[634]: reportengine: copied 0 files to 
/var/www/html/weewx
Nov 26 13:50:25 raspberrypi weewx[634]: reportengine: ftp'd 26 files in 8.28 
seconds
Nov 26 13:55:17 raspberrypi weewx[634]: cheetahgenerator: Generated 14 
files for report StandardReport in 1.66 seconds
Nov 26 13:55:17 raspberrypi weewx[634]: genimages: Generated 12 images for 
StandardReport in 0.61 seconds
Nov 26 13:55:17 raspberrypi weewx[634]: reportengine: copied 0 files to /var
/www/html/weewx
Nov 26 13:55:26 raspberrypi weewx[634]: reportengine: ftp'd 26 files in 
8.37 seconds

On my webpage: http://boleslawice.info/
Data are 17hours old.
On WU 
http://wunderground.com/personal-weather-station/dashboard?ID=IWOJEWDZ56 
data seems to be ok, but WU is set up in the RapidFire
What should I do to get data?
How can I check the database? file weewx.sdb is updated 3 minutes ago. 

On Friday, November 25, 2016 at 10:54:49 PM UTC+1, Jacek Skowroński wrote:
>
> Hi, I had lost my old config, had to go for old sd card.
> System started to collect old data - from last 4 days.Send it to the 
> webpage - boleslawice.info, WU and other weather system and then stopped 
> to collect data.
>
> Now I have something like:
> pi@raspberrypi:~ $ tail -f /var/log/syslog
> Nov 25 22:41:42 raspberrypi weewx[631]: restx: Wunderground-PWS: Data for 
> station IWOJEWDZ56 will be posted
> Nov 25 22:41:42 raspberrypi weewx[631]: restx: PWSWeather: Data for 
> station YACENTY2 will be posted
> Nov 25 22:41:42 raspberrypi weewx[631]: restx: CWOP: Posting not enabled.
> Nov 25 22:41:42 raspberrypi weewx[631]: restx: WOW: Data for station 
> 976406001 will be posted
> Nov 25 22:41:42 raspberrypi weewx[631]: restx: AWEKAS: Data will be 
> uploaded for user yacenty
> Nov 25 22:41:42 raspberrypi weewx[631]: engine: Starting up weewx version 
> 3.6.2
> Nov 25 22:41:42 raspberrypi weewx[631]: engine: Clock error is -6.36 
> seconds (positive is fast)
> Nov 25 22:41:42 raspberrypi weewx[631]: vantage: Clock set to 2016-11-25 
> 22:41:43 CET (1480110103)
> Nov 25 22:41:43 raspberrypi weewx[631]: engine: Starting main packet loop.
> Nov 25 22:41:48 raspberrypi weewx[631]: vantage: LOOP try #1; error: 
> Expected to read 99 chars; got 0 instead
> Nov 25 22:45:18 raspberrypi weewx[631]: cheetahgenerator: Generated 14 
> files for report StandardReport in 1.63 seconds
> Nov 25 22:45:18 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Fri Nov 25 22:45:48 2016 [try http://www.rsyslog.com/e/2007 
> ]
> Nov 25 22:45:18 raspberrypi weewx[631]: genimages: Generated 12 images for 
> StandardReport in 0.60 seconds
> Nov 25 22:45:18 raspberrypi weewx[631]: reportengine: copied 9 files to 
> /var/www/html/weewx
> Nov 25 22:45:31 raspberrypi weewx[631]: reportengine: ftp'd 35 files in 
> 13.07 seconds
> Nov 25 22:50:18 raspberrypi weewx[631]: cheetahgenerator: Generated 14 
> files for report StandardReport in 1.64 seconds
> Nov 25 22:50:18 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Fri Nov 25 22:50:48 2016 [try http://www.rsyslog.com/e/2007 
> ]
> Nov 25 22:50:18 raspberrypi weewx[631]: genimages: Generated 12 images for 
> StandardReport in 0.61 seconds
> Nov 25 22:50:18 raspberrypi weewx[631]: reportengine: copied 0 files to 
> /var/www/html/weewx
> Nov 25 22:50:27 raspberrypi weewx[631]: reportengine: ftp'd 26 files in 
> 9.03 seconds
> Nov 25 22:52:26 raspberrypi systemd[1]: Starting Cleanup of Temporary 
> Directories...
> Nov 25 22:52:26 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Fri Nov 25 22:52:56 2016 [try http://www.rsyslog.com/e/2007 
> ]
> Nov 25 22:52:26 raspberrypi systemd[1]: Started Cleanup of Temporary 
> Directories.
>
> but the last data are from 19:55.
> How can I force weewx to communictae with davis?
> pi was restarted few times.
>
> pi in general sees the davis
>
> pi@raspberrypi:~ $ wee_device --info
> Using configuration file /etc/weewx/weewx.conf
> Using Vantage driver version 3.0.9 (weewx.drivers.vantage)
> Querying...
> Davis Vantage EEPROM settings:
>
> CONSOLE TYPE:   VantagePro2
>
> CONSOLE FIRMWARE:
>   Date: Jun  3 2013
>   Version

Re: [weewx-user] Re: Weewxwd installation when weewx installed from deb

2016-11-12 Thread Jacek Skowroński
Thanks for warn I do not blame You, I like the risk sometimes.
I did what You pointed.
Still there is some problem. But I do not care at this moment - data are on 
my webpage - weewx and saratoga also they are sent to the WU

Here is an error log - maybe it would help You in development of very nice 
plugin.

Nov 12 14:30:20 raspberrypi weewx[18627]: cheetahgenerator: Generate failed 
with exception ''
Nov 12 14:30:20 raspberrypi weewx[18627]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Clientraw/clientrawextra.txt.tmpl
Nov 12 14:30:20 raspberrypi weewx[18627]: cheetahgenerator:  Reason: 
cannot find 'split' while searching for 'split'
Nov 12 14:30:20 raspberrypi weewx[18627]:   Traceback (most recent call 
last):
Nov 12 14:30:20 raspberrypi weewx[18627]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 315, in generate
Nov 12 14:30:20 raspberrypi weewx[18627]:   print >> _file, text
Nov 12 14:30:20 raspberrypi weewx[18627]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Nov 12 14:30:20 raspberrypi weewx[18627]:   rc = getattr(self, 
mainMethName)()
Nov 12 14:30:20 raspberrypi weewx[18627]: File 
"_etc_weewx_skins_Clientraw_clientrawextra_txt_tmpl.py", line 164, in 
respond
Nov 12 14:30:20 raspberrypi weewx[18627]:   NotFound: cannot find 
'split' while searching for 'split'
Nov 12 14:30:20 raspberrypi weewx[18627]: cheetahgenerator: Generated 3 
files for report wdClientraw in 1.09 seconds
Nov 12 14:30:20 raspberrypi weewx[18627]: imageStackedWindRose: Generated 1 
images for wdStackedWindRose in 0.10 seconds
Nov 12 14:30:20 raspberrypi weewx[18627]: cheetahgenerator: Generated 1 
files for report wdSteelGauges in 0.09 seconds
Nov 12 14:30:30 raspberrypi weewx[18627]: reportengine: ftp'd 33 files in 
10.30 seconds

Once more, thanks for help and good plugin
Regards
Jacek


On Saturday, November 12, 2016 at 1:57:10 PM UTC+1, gjr80 wrote:
>
> On Saturday, 12 November 2016 20:12:55 UTC+10, Jacek Skowroński wrote:
>>
>> Any hint how to fix the mentioned errors?
>>
>
> I did warn you.
>
>> Weewx-WD v1.0.0 has a few bugs in it that may or may not affect you. I am 
>> just putting the finishing touches to a v1.0.1 package that adresses these 
>> issues. If you could hang off installing for a week that might be 
>> advantageous. 
>>
>
> The wind rose font issue is easily worked around. As per the Weewx-WD docs 
> installing the GNU FreeFont truetype fonts will fix the problem:
>  
> sudo apt-get install fonts-freefont-ttf
>
> The next version gracefully handles the lack of the GNU FreeFont truetype 
> fonts.
>
> The other issue is more complex but I suspect it can be avoided by installing 
> pyephem <http://weewx.com/docs/setup.htm> (I say avoided becasue the 
> issue is still there, it is just that Weewx-WD 1.0.0 handles sunrise and 
> sunset times a little differently if pyephem is installed):
>
> sudo apt-get install python-dev
> sudo apt-get install python-pip
> sudo pip install pyephem
>
> Even with these workarounds I am not certain you will have no more issues. 
> As I said this morning, I recommend you give me a few days to get the next 
> version finalised.
>
> 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: Weewxwd installation when weewx installed from deb

2016-11-12 Thread Jacek Skowroński
     self.plotFont = 
ImageFont.truetype(self.windrose_font_path, self.windrose_plot_font_size)
Nov 12 11:05:32 raspberrypi weewx[18627]: File 
"/usr/lib/python2.7/dist-packages/PIL/ImageFont.py", line 240, in truetype
Nov 12 11:05:32 raspberrypi weewx[18627]:   return 
FreeTypeFont(font, size, index, encoding)
Nov 12 11:05:32 raspberrypi weewx[18627]: File 
"/usr/lib/python2.7/dist-packages/PIL/ImageFont.py", line 137, in __init__
Nov 12 11:05:32 raspberrypi weewx[18627]:   self.font = 
core.getfont(font, size, index, encoding)
Nov 12 11:05:32 raspberrypi weewx[18627]:   IOError: cannot 
open resource
Nov 12 11:05:32 raspberrypi weewx[18627]:   Generator terminated
Nov 12 11:05:33 raspberrypi weewx[18627]: cheetahgenerator: Generated 1 
files for report wdSteelGauges in 0.40 seconds
Nov 12 11:05:45 raspberrypi weewx[18627]: reportengine: ftp'd 41 files in 
12.53 seconds

Now I have few questions.
If FTP service is on and all files from pi are sent to www serwer, does it 
mean that all files located in weewx/WD folder should go to the ftp server? 
Or do I have to prepare other service called FTPWD to send WD files?
Any hint how to fix the mentioned errors?

On Saturday, November 12, 2016 at 8:35:49 AM UTC+1, gjr80 wrote:
>
> Did you try explicitly setting the --config option as per my last? I also 
> note you ran wee_extension from the / directory. You might want to try 
> changing into the /usr/share/weewx folder and then running it again, it 
> could be a path issue.
>
> Gary
>
> On Saturday, 12 November 2016 17:17:30 UTC+10, Jacek Skowroński wrote:
>>
>> Yes file is in the standard location. Weewx is working without any warn 
>> on start so It's crazy to have problems with config.
>> Could i send You a file to chceck? Maybe there is something with program 
>> wee_extension
>> Regards
>> Jacek
>>
>> W dniu pt., 11.11.2016 o 23:00 gjr80 <gjrod...@gmail.com> napisał(a):
>>
>>> That error indicates that wee_extension found an error in your 
>>> weewx.conf and could not parse it. I trust that your weewx.conf is 
>>> located in /etc/weewx (you said you did a deb install) and that it in 
>>> fact is not malformed? If everything is fine you might want to tell 
>>> wee_extension exactly where weewx.conf is rather than have it guessing. 
>>> You could try:
>>>
>>> wee_extension --config=/etc/weewx/weewx.conf --install=/home/pi/weewxwd-
>>> 1.0.0.tar.gz
>>>
>>> Gary
>>>
>>>
>>> On Saturday, 12 November 2016 07:43:27 UTC+10, Jacek Skowroński wrote:
>>>>
>>>> by the way, the solution you gave me producess errors
>>>>
>>>> pi@raspberrypi:/ $ sudo wee_extension --install= 
>>>> /home/pi/weewxwd-1.0.0.tar.gz
>>>> Traceback (most recent call last):
>>>>   File "/usr/bin/wee_extension", line 83, in 
>>>> main()
>>>>   File "/usr/bin/wee_extension", line 62, in main
>>>> config_path, config_dict = weecfg.read_config(options.config, _args)
>>>>   File "/usr/share/weewx/weecfg/__init__.py", line 223, in read_config
>>>> config_dict = configobj.ConfigObj(config_path, file_error=True)
>>>>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
>>>> __init__
>>>> self._load(infile, configspec)
>>>>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in 
>>>> _load
>>>> raise error
>>>> configobj.ConfigObjError: Parsing failed with several errors.
>>>> First error at line 1.
>>>>
>>>>
>>>> On Friday, November 11, 2016 at 10:15:18 PM UTC+1, gjr80 wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> The Weewx-WD install instructions have not yet been updated to reflect 
>>>>> the removal of the weewx extension management capabilities from 
>>>>> setup.py and the creation of the wee_extension utilitiy at weewx 
>>>>> v3.2.0. You can safely install Weewx-WD with wee_extension using 
>>>>> something 
>>>>> like:
>>>>>
>>>>> ./wee_extension --install=/path/to/weewxwd-1.0.0.tar.gz
>>>>>
>>>>> Weewx-WD v1.0.0 has a few bugs in it that may or may not affect you. I 
>>>>> am just putting the finishing touches to a v1.0.1 package that adresses 
>>>>> these issues. If you could hang off installing for a week that might be 
>>>>> adva

Re: [weewx-user] Re: Weewxwd installation when weewx installed from deb

2016-11-12 Thread Jacek Skowroński
thx
finally this works

pi@raspberrypi:/usr/share/weewx $ sudo wee_extension 
--config=/etc/weewx/weewx.conf --install=/home/pi/weewxwd-1.0.0.tar.gz
Request to install '/home/pi/weewxwd-1.0.0.tar.gz'
Extracting from tar archive /home/pi/weewxwd-1.0.0.tar.gz
Saving installer file to /usr/share/weewx/user/installer/Weewx-WD
Saved configuration dictionary. Backup copy at 
/etc/weewx/weewx.conf.20161112110131
Finished installing extension '/home/pi/weewxwd-1.0.0.tar.gz'


On Saturday, November 12, 2016 at 8:35:49 AM UTC+1, gjr80 wrote:
>
> Did you try explicitly setting the --config option as per my last? I also 
> note you ran wee_extension from the / directory. You might want to try 
> changing into the /usr/share/weewx folder and then running it again, it 
> could be a path issue.
>
> Gary
>
> On Saturday, 12 November 2016 17:17:30 UTC+10, Jacek Skowroński wrote:
>>
>> Yes file is in the standard location. Weewx is working without any warn 
>> on start so It's crazy to have problems with config.
>> Could i send You a file to chceck? Maybe there is something with program 
>> wee_extension
>> Regards
>> Jacek
>>
>> W dniu pt., 11.11.2016 o 23:00 gjr80 <gjrod...@gmail.com> napisał(a):
>>
>>> That error indicates that wee_extension found an error in your 
>>> weewx.conf and could not parse it. I trust that your weewx.conf is 
>>> located in /etc/weewx (you said you did a deb install) and that it in 
>>> fact is not malformed? If everything is fine you might want to tell 
>>> wee_extension exactly where weewx.conf is rather than have it guessing. 
>>> You could try:
>>>
>>> wee_extension --config=/etc/weewx/weewx.conf --install=/home/pi/weewxwd-
>>> 1.0.0.tar.gz
>>>
>>> Gary
>>>
>>>
>>> On Saturday, 12 November 2016 07:43:27 UTC+10, Jacek Skowroński wrote:
>>>>
>>>> by the way, the solution you gave me producess errors
>>>>
>>>> pi@raspberrypi:/ $ sudo wee_extension --install= 
>>>> /home/pi/weewxwd-1.0.0.tar.gz
>>>> Traceback (most recent call last):
>>>>   File "/usr/bin/wee_extension", line 83, in 
>>>> main()
>>>>   File "/usr/bin/wee_extension", line 62, in main
>>>> config_path, config_dict = weecfg.read_config(options.config, _args)
>>>>   File "/usr/share/weewx/weecfg/__init__.py", line 223, in read_config
>>>> config_dict = configobj.ConfigObj(config_path, file_error=True)
>>>>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
>>>> __init__
>>>> self._load(infile, configspec)
>>>>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in 
>>>> _load
>>>> raise error
>>>> configobj.ConfigObjError: Parsing failed with several errors.
>>>> First error at line 1.
>>>>
>>>>
>>>> On Friday, November 11, 2016 at 10:15:18 PM UTC+1, gjr80 wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> The Weewx-WD install instructions have not yet been updated to reflect 
>>>>> the removal of the weewx extension management capabilities from 
>>>>> setup.py and the creation of the wee_extension utilitiy at weewx 
>>>>> v3.2.0. You can safely install Weewx-WD with wee_extension using 
>>>>> something 
>>>>> like:
>>>>>
>>>>> ./wee_extension --install=/path/to/weewxwd-1.0.0.tar.gz
>>>>>
>>>>> Weewx-WD v1.0.0 has a few bugs in it that may or may not affect you. I 
>>>>> am just putting the finishing touches to a v1.0.1 package that adresses 
>>>>> these issues. If you could hang off installing for a week that might be 
>>>>> advantageous.
>>>>>
>>>>> Gary
>>>>>
>>>>> On Saturday, 12 November 2016 06:39:22 UTC+10, Jacek Skowroński wrote:
>>>>>>
>>>>>> Hi,
>>>>>> I have some confusion.
>>>>>> I'd like to install weewxwd. Previously I had installed weewx from 
>>>>>> deb.
>>>>>> Where should I find setup.py file in general? This is the first step 
>>>>>> in installation of the weewxwd
>>>>>>
>>>>>> sudo find / -name 'setup.py'
>>>>>>
>>>>>> gives nothing
>>>>>>
>>>>>> Thanks for help
>>>>>>
>>>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/weewx-user/EJxwFGpcu60/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> weewx-user+...@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] Re: Weewxwd installation when weewx installed from deb

2016-11-11 Thread Jacek Skowroński
Yes file is in the standard location. Weewx is working without any warn on
start so It's crazy to have problems with config.
Could i send You a file to chceck? Maybe there is something with program
wee_extension
Regards
Jacek

W dniu pt., 11.11.2016 o 23:00 gjr80 <gjroder...@gmail.com> napisał(a):

> That error indicates that wee_extension found an error in your weewx.conf
> and could not parse it. I trust that your weewx.conf is located in
> /etc/weewx (you said you did a deb install) and that it in fact is not
> malformed? If everything is fine you might want to tell wee_extension
> exactly where weewx.conf is rather than have it guessing. You could try:
>
> wee_extension --config=/etc/weewx/weewx.conf --install=/home/pi/weewxwd-
> 1.0.0.tar.gz
>
> Gary
>
>
> On Saturday, 12 November 2016 07:43:27 UTC+10, Jacek Skowroński wrote:
>
> by the way, the solution you gave me producess errors
>
> pi@raspberrypi:/ $ sudo wee_extension --install=
> /home/pi/weewxwd-1.0.0.tar.gz
> Traceback (most recent call last):
>   File "/usr/bin/wee_extension", line 83, in 
> main()
>   File "/usr/bin/wee_extension", line 62, in main
> config_path, config_dict = weecfg.read_config(options.config, _args)
>   File "/usr/share/weewx/weecfg/__init__.py", line 223, in read_config
> config_dict = configobj.ConfigObj(config_path, file_error=True)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in
> __init__
> self._load(infile, configspec)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
> raise error
> configobj.ConfigObjError: Parsing failed with several errors.
> First error at line 1.
>
>
> On Friday, November 11, 2016 at 10:15:18 PM UTC+1, gjr80 wrote:
>
> Hi,
>
> The Weewx-WD install instructions have not yet been updated to reflect the
> removal of the weewx extension management capabilities from setup.py and
> the creation of the wee_extension utilitiy at weewx v3.2.0. You can
> safely install Weewx-WD with wee_extension using something like:
>
> ./wee_extension --install=/path/to/weewxwd-1.0.0.tar.gz
>
> Weewx-WD v1.0.0 has a few bugs in it that may or may not affect you. I am
> just putting the finishing touches to a v1.0.1 package that adresses these
> issues. If you could hang off installing for a week that might be
> advantageous.
>
> Gary
>
> On Saturday, 12 November 2016 06:39:22 UTC+10, Jacek Skowroński wrote:
>
> Hi,
> I have some confusion.
> I'd like to install weewxwd. Previously I had installed weewx from deb.
> Where should I find setup.py file in general? This is the first step in
> installation of the weewxwd
>
> sudo find / -name 'setup.py'
>
> gives nothing
>
> Thanks for help
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/EJxwFGpcu60/unsubscribe.
> To unsubscribe from this group and all its topics, 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: Weewxwd installation when weewx installed from deb

2016-11-11 Thread Jacek Skowroński
by the way, the solution you gave me producess errors

pi@raspberrypi:/ $ sudo wee_extension --install= 
/home/pi/weewxwd-1.0.0.tar.gz
Traceback (most recent call last):
  File "/usr/bin/wee_extension", line 83, in 
main()
  File "/usr/bin/wee_extension", line 62, in main
config_path, config_dict = weecfg.read_config(options.config, _args)
  File "/usr/share/weewx/weecfg/__init__.py", line 223, in read_config
config_dict = configobj.ConfigObj(config_path, file_error=True)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
__init__
self._load(infile, configspec)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
raise error
configobj.ConfigObjError: Parsing failed with several errors.
First error at line 1.


On Friday, November 11, 2016 at 10:15:18 PM UTC+1, gjr80 wrote:
>
> Hi,
>
> The Weewx-WD install instructions have not yet been updated to reflect the 
> removal of the weewx extension management capabilities from setup.py and 
> the creation of the wee_extension utilitiy at weewx v3.2.0. You can 
> safely install Weewx-WD with wee_extension using something like:
>
> ./wee_extension --install=/path/to/weewxwd-1.0.0.tar.gz
>
> Weewx-WD v1.0.0 has a few bugs in it that may or may not affect you. I am 
> just putting the finishing touches to a v1.0.1 package that adresses these 
> issues. If you could hang off installing for a week that might be 
> advantageous.
>
> Gary
>
> On Saturday, 12 November 2016 06:39:22 UTC+10, Jacek Skowroński wrote:
>>
>> Hi,
>> I have some confusion.
>> I'd like to install weewxwd. Previously I had installed weewx from deb.
>> Where should I find setup.py file in general? This is the first step in 
>> installation of the weewxwd
>>
>> sudo find / -name 'setup.py'
>>
>> gives nothing
>>
>> Thanks for help
>>
>

-- 
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: Weewxwd installation when weewx installed from deb

2016-11-11 Thread Jacek Skowroński
thanks for info about the way of installation and about troubles
I will wait

On Friday, November 11, 2016 at 9:39:22 PM UTC+1, Jacek Skowroński wrote:
>
> Hi,
> I have some confusion.
> I'd like to install weewxwd. Previously I had installed weewx from deb.
> Where should I find setup.py file in general? This is the first step in 
> installation of the weewxwd
>
> sudo find / -name 'setup.py'
>
> gives nothing
>
> Thanks for help
>

-- 
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] Weewxwd installation when weewx installed from deb

2016-11-11 Thread Jacek Skowroński
Hi,
I have some confusion.
I'd like to install weewxwd. Previously I had installed weewx from deb.
Where should I find setup.py file in general? This is the first step in 
installation of the weewxwd

sudo find / -name 'setup.py'

gives nothing

Thanks for help

-- 
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] weewx, raspberry pi and sd cards - the lifetime for card

2016-11-04 Thread Jacek Skowroński
Rpi 3 is fully working with usb hdd so i got rid of sd card

W dniu piątek, 4 listopada 2016 Jacek Skowroński <yace...@gmail.com>
napisał(a):

> I am in the middle of chcanging sd to hdd. Of success i will keep rpi if
> fail i will go exactly same solution old PC like hp or dell
>
> W dniu piątek, 4 listopada 2016 Eelco F <valkenier...@gmail.com
> <javascript:_e(%7B%7D,'cvml','valkenier...@gmail.com');>> napisał(a):
>
>> Well, I experienced the same issues running the system on a raspberry pi
>> B. Every 3 Months or so, the sd cards just gave up. Corrupted files and
>> file system, causing freezes. I had the whole system including swap,
>> raspbian and weewx and Apache running on the sd card. No extra disks or
>> sticks.
>> I ended up doing some calculation: weewx rewrites its database every 5
>> min, that is 12 times/h, 248 times/day, let's say 7500/month.
>> Apart from that it rewrites html files, images etc. at the same
>> frequency. Also the operating system performs writes, in the log for
>> example, and swap.
>> Adding this all up together, I think an sd card just wears out, after a
>> few months.
>> I replaced the raspberry by a secondhand HP thin client, for a few bucks
>> at eBay. With a regular hdd.
>> It takes more power of course, but it's a lot faster too. It's running
>> Ubuntu server, and is stable until now.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/weewx-user/atRpRzKrlyk/unsubscribe.
>> To unsubscribe from this group and all its topics, 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] weewx, raspberry pi and sd cards - the lifetime for card

2016-11-04 Thread Jacek Skowroński
I am in the middle of chcanging sd to hdd. Of success i will keep rpi if
fail i will go exactly same solution old PC like hp or dell

W dniu piątek, 4 listopada 2016 Eelco F  napisał(a):

> Well, I experienced the same issues running the system on a raspberry pi
> B. Every 3 Months or so, the sd cards just gave up. Corrupted files and
> file system, causing freezes. I had the whole system including swap,
> raspbian and weewx and Apache running on the sd card. No extra disks or
> sticks.
> I ended up doing some calculation: weewx rewrites its database every 5
> min, that is 12 times/h, 248 times/day, let's say 7500/month.
> Apart from that it rewrites html files, images etc. at the same frequency.
> Also the operating system performs writes, in the log for example, and swap.
> Adding this all up together, I think an sd card just wears out, after a
> few months.
> I replaced the raspberry by a secondhand HP thin client, for a few bucks
> at eBay. With a regular hdd.
> It takes more power of course, but it's a lot faster too. It's running
> Ubuntu server, and is stable until now.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/atRpRzKrlyk/unsubscribe.
> To unsubscribe from this group and all its topics, 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] weewx, raspberry pi and sd cards - the lifetime for card

2016-11-01 Thread Jacek Skowroński
answering inline

W dniu 2016-11-01 o 16:10, Andrew Milner pisze:

Out of curiosity - do you
a)run software other than debian, weewx, SQLite and maybe a webserver on
your pi?

no, the pi is dedicated for weewx, so this is a core. Of course I have
additional small programs like htop, bwm-ng and other just to monitor the
pi.

b)do you regularly - eg once a month - keep your rpi sw up-to-date with
update/upgrade?

yes, I do

c)do you regularly keep other software you use up-to-date?

no, because there no software that is outside system update.

d)do you make sure that you do not run experimental sw on your 'production'
pi, but only on a backup pi - in case issues are raised during the
experiment .

hard to say what is experimental, I did not provide any bigger chages to
the rasbian so I think there is nothing special

e)do you run fsck routinely?

no, I do it only in case of error

f)have you tried repairing the sd card by booting into single user - or
touching to force fsck on boot?

2 times, I booted lapton with knoppix, put the card in reader and tried to
repair, after few hours of fight - theoretically card was repaired but when
I inserted it and booted system from it, the weewex was corrupted

g)do you always - 100% of the time - do orderly powerdowns and in the event
of any unexpected power failures routinely do full fsck and repairs?

having pi UPS, it's nearly impossible to have unexpected power failure.
This setup is also connected to the APC UPS - to make power better for
electric devices.


Some of these questions are relevant in that, for example, the effects of a
disorderly loss of power may not be seen until some time after the event -
when the disk sector(s) in question are next accessed.  Software which
crashes can corrupt a disk before crashing - and if that SW is not used
(because it crashed) the effect can go unnoticed for some considerable time
 and so on and so forth .

First crash of card was done thanks to power failrure, so I invested in APC
UPS and then Pi UPS

There's no need to respond to this post - it is more intended to just make
sure that you are thinking of these things - since I seem to recall that
you're not, for example, on the latest weewx - and seemed to have
difficulties working out a simple template change to add soilTemp1 to a
webpage, so I am not sure of your level of expertise in
computers/Linux/RPi/weewx/etc .

In this case what I can say - I'm little bit lazy but from the other side.
I would not open open

Just trying to be helpful and give you some 'food for thought' .  as I
said, no need to respond!!

Andrew


On 1 November 2016 at 16:25, Jacek Skowroński <yace...@gmail.com
<javascript:_e(%7B%7D,'cvml','yace...@gmail.com');>> wrote:

> It's my secind pi first was pi 1b the secind is pi 3
>
> W dniu wtorek, 1 listopada 2016 Daniel Rich <wwwdr...@gmail.com
> <javascript:_e(%7B%7D,'cvml','wwwdr...@gmail.com');>> napisał(a):
>
>> To be honest, that sounds like a bad Pi, not a bad SD card. The Pi is
>> fairly tolerant of power issues, I have run them off of USB cables
>> connected to other systems, USB wall power adaptors, and even POE adaptors
>> with never a problem like the one you are seeing.
>>
>> The only thing that comes immediately to mind is to make sure you don't
>> have swap enabled in your system. In general, you never want to run
>> anything on a Pi that uses enough memory to cause swapping -- both for
>> performance and SD write issues. The kind of writes that weewx does for the
>> sqlite database and logging shouldn't cause enough write traffic to hit the
>> SD write limits for several years (there is a really good article from a
>> couple of years ago on the myth of SD write limitations, I'll see if I can
>> dig it up and post it to the list).
>>
>> In all my years of using SD cards in various devices (PoGoPlug, Pi, an
>> old firewall I have since retired, assorted tablets, etc.), I have only
>> ever had a single card failure -- and that was from a bad card, not any
>> sort of write limit being reached.
>>
>> On Monday, October 31, 2016 at 8:25:43 AM UTC-7, Jacek Skowroński wrote:
>>>
>>> I mean crash of the rasbperry Pi
>>>
>>> and many errors like kernel panic connected with the filesystem
>>>
>>> Few times I had tried to get card to the PC with knoppix and do fsck to
>>> repair filesystem but all trials make the data corrupted -> I gave up and
>>> bougth new card and system was working for some time.
>>>
>>> At the begining I thought it's a case of power / stability of power.
>>>
>>> For about 6months I have PiUPS and APC UPS, APC is mainly for making the
>>> power more electric user friendly and to keep power for 5minutes. PiUPS is
>>> for keepi

Re: [weewx-user] soilTemp on the webpage

2016-11-01 Thread Jacek Skowroński
thanks

On Tuesday, November 1, 2016 at 1:04:29 PM UTC+1, Tom Keffer wrote:
>
> It's very simple. In index.html.tmpl, change this
>
>   
> Inside Temperature
> $current.inTemp
>   
>
> to this
>
>   
> Inside Temperature
> $current.inTemp
>   
>   
> Soil temperature
> $current.soilTemp1
>   
>
> -tk
>
>
> On Tue, Nov 1, 2016 at 1:41 AM, Jacek Skowroński <yac...@gmail.com 
> > wrote:
>
>> Hi guys, could You help me with showing soil temperature on my weewx 
>> webpage - boleslawice.info
>> I went through the customization documentation but it seems very 
>> complicated for me.
>> Maybe somebody already have skin with the soil temp showing on?
>>
>> Thanks in advance
>> BR
>> Jacek
>>
>> -- 
>> 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 .
>> 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] weewx, raspberry pi and sd cards - the lifetime for card

2016-11-01 Thread Jacek Skowroński
It's my secind pi first was pi 1b the secind is pi 3

W dniu wtorek, 1 listopada 2016 Daniel Rich <wwwdr...@gmail.com> napisał(a):

> To be honest, that sounds like a bad Pi, not a bad SD card. The Pi is
> fairly tolerant of power issues, I have run them off of USB cables
> connected to other systems, USB wall power adaptors, and even POE adaptors
> with never a problem like the one you are seeing.
>
> The only thing that comes immediately to mind is to make sure you don't
> have swap enabled in your system. In general, you never want to run
> anything on a Pi that uses enough memory to cause swapping -- both for
> performance and SD write issues. The kind of writes that weewx does for the
> sqlite database and logging shouldn't cause enough write traffic to hit the
> SD write limits for several years (there is a really good article from a
> couple of years ago on the myth of SD write limitations, I'll see if I can
> dig it up and post it to the list).
>
> In all my years of using SD cards in various devices (PoGoPlug, Pi, an old
> firewall I have since retired, assorted tablets, etc.), I have only ever
> had a single card failure -- and that was from a bad card, not any sort of
> write limit being reached.
>
> On Monday, October 31, 2016 at 8:25:43 AM UTC-7, Jacek Skowroński wrote:
>>
>> I mean crash of the rasbperry Pi
>>
>> and many errors like kernel panic connected with the filesystem
>>
>> Few times I had tried to get card to the PC with knoppix and do fsck to
>> repair filesystem but all trials make the data corrupted -> I gave up and
>> bougth new card and system was working for some time.
>>
>> At the begining I thought it's a case of power / stability of power.
>>
>> For about 6months I have PiUPS and APC UPS, APC is mainly for making the
>> power more electric user friendly and to keep power for 5minutes. PiUPS is
>> for keeping power for 30minutes and then to clearly poweroff. From this
>> time - I have 100% power on, but on Saturday second card failed. I get mail
>> from WU about no data from station, I attached tv to the Pi and I had seen
>> kernel panic because of filesystem.
>>
>> This is my problem.
>>
>> W dniu 2016-10-31 o 16:19, Daniel Rich pisze:
>>
>> Jacek,
>>
>> When you say you are seeing "corruption", what do you mean? In my
>> experience SD card failures typically show as write or read failures, but
>> not data corruption.
>>
>> Like Thomas, I have PI systems that have been running for over two years
>> with no SD card failures. As long as you don't do something like enable a
>> swap partition and run so much on the PI that you cause swapping, there
>> shouldn't be enough data activity to hit any of the SD write limits for
>> several years.
>>
>> ---
>> Dan Rich <dr...@employees.org> |   http://www.employees.org/~drich/
>>|  "Step up to red alert!"  "Are you sure, 
>> sir?
>>|   It means changing the bulb in the sign..."
>>|  - Red Dwarf (BBC)
>>
>> On 2016-10-31 05:36, Jacek Skowroński wrote:
>>
>> I had 5 already
>>
>> toshiba claas 10
>> samsung evo pro
>> sandisk extreme
>> sandisk ultra
>> Intenso claas 10
>>
>> in general all get corrupted after 3-4 month
>>
>> all cards had been 16-32gb
>>
>> W dniu 2016-10-31 o 13:34, Thomas Keffer pisze:
>>
>> I've been running an experiment
>> <http://www.threefools.org/weewx/status/index.html> on how long an SD
>> card can survive in the weewx environment.
>>
>> So far, using a Sandisk Extreme Plus, it's been running nearly 2 years
>> without a problem.
>>
>> If you buy a good one, it can last quite a long time.
>>
>> What kind of card are you using?
>>
>> -tk
>>
>>
>>
>> On Mon, Oct 31, 2016 at 4:11 AM, Jacek Skowroński <yac...@gmail.com>
>> wrote:
>>
>>> great, I will update my environment with hdd.
>>>
>>> Regards
>>> Jacek
>>>
>>> W dniu 2016-10-31 o 12:09, Andrew Milner pisze:
>>>
>>> Yes, they work.  I use a powered usb hub because the rpi usb is somewhat
>>> flakey - and my fineoffset weather station is also going to the rpi via a
>>> powered usb hub.
>>>
>>>
>>> On Monday, 31 October 2016 11:56:48 UTC+2, Jacek Skowroński wrote:
>>>
>>>> Have You tried and it work? Could You recommend any certain HDD model
>>>> and usb

[weewx-user] soilTemp on the webpage

2016-11-01 Thread Jacek Skowroński
Hi guys, could You help me with showing soil temperature on my weewx 
webpage - boleslawice.info
I went through the customization documentation but it seems very 
complicated for me.
Maybe somebody already have skin with the soil temp showing on?

Thanks in advance
BR
Jacek

-- 
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] weewx, raspberry pi and sd cards - the lifetime for card

2016-11-01 Thread Jacek Skowroński
Could You provide some structure how to divide data between ram and flash?
On flash i'd like to have
DB
Config
Skins

Rest could be in ram
Www files
Logs
Any other tempoprary weewx files

W dniu wtorek, 1 listopada 2016 Glenn McKechnie <glenn.mckech...@gmail.com>
napisał(a):

> Hi Jacek,
>
> <https://github.com/glennmckechnie/rorpi-raspberrypi>
>
> On 1 November 2016 at 20:58, Jacek Skowroński <yace...@gmail.com
> <javascript:_e(%7B%7D,'cvml','yace...@gmail.com');>> wrote:
>
>> after one hour I get
>> 14302 be/4 root  0.00 B 11.70 M  0.00 %  0.01 % python
>> /usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf
>>
>> does it mean that weewx pid write down 11.7? or which file produced so
>> huge amount of data?
>>
>
>
> Interesting that you have no DISK READ value, I'd have thought there would
> be something in that field?
>
> Yes, that's what it has written to disk, although 11.7M doesn't sound
> excessive for weewx. As I noted previously, that value is for everything
> that weewx is handling; sqlite database writes, webserver pages and images.
> It also includes writes to tmp, although thats probably a tmpfs so it's
> removed from the disk already. Anyway, that means that it's not one file in
> particular that's attracting all that traffic.
>
> Maybe I should put it in the ram or on the flash
>>
>>
> That's your call, if you're asking me then yes :-) One size doesn't fit
> all, but you can choose a method that you're happy with and can handle.
> Me?  I'd be attempting to preserve the SDCard for its main purpose,
> running the OS and keeping the pi alive. The data that weewx generates is
> moved elsewhere, preferably somewhere or something with a proven track
> record. In particular something that matches its value ie: the database
> gets priority storage, the webserver not so much.
>
>
>
> Cheers
>  Glenn
>
> rorpi - read only raspberry pi + weewx: now with scripts
> <https://github.com/glennmckechnie/rorpi-raspberrypi>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/atRpRzKrlyk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com
> <javascript:_e(%7B%7D,'cvml','weewx-user%2bunsubscr...@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] weewx, raspberry pi and sd cards - the lifetime for card

2016-11-01 Thread Jacek Skowroński
after one hour I get
14302 be/4 root  0.00 B 11.70 M  0.00 %  0.01 % python 
/usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf

does it mean that weewx pid write down 11.7? or which file produced so huge 
amount of data?
Maybe I should put it in the ram or on the flash

On Tuesday, November 1, 2016 at 10:01:15 AM UTC+1, Glenn McKechnie wrote:
>
>
> I didn't recognize vmstat, a quick search turns up the following...
>
> *"vmstat 60 1440* > /path/to/vmstat.`date +%d` This will write to a file 
> every minute for 24 hours then create a new file and start over."
>
> That might be a good candidate to move over to the flash, along with the 
> logs as Andrew suggested.  In fact, it's writing more than the logging 
> daemon so you've just doubled the logging load there.
>
> [jbd2/mmcblk0p2-] is the ext4 journal - I always find it interesting to 
> see just how large that value gets over time. Make the SDcard read-only and 
> that drops to zero.
>
> Keep it running and see what else shows up, anything that pops up there is 
> a possible candidate to move to the USBstick or hdd.
>
> The webserver (the image / html files generated by weewx are included in 
> weewx's iotop total) can also be moved over to the flash /USB stick, hdd, 
> whatever.
> The rorpi HowTo moves the webserver into memory (except for NOAA files - 
> It's been pointed out that if there are a lot of them, they are worth 
> keeping on the drive rather than regenerating.) I haven't thought of a 
> valid reason to keep the www files on disk, they are regenerated 
> constantly. Although there will be an empty page after a weewx  restart, 
> but a placeholder could be kept to inform any one unlucky enough to be 
> viewing in that small time window.
>
>
> Cheers
>  Glenn
>
> rorpi - read only raspberry pi + weewx: now with scripts 
> <https://github.com/glennmckechnie/rorpi-raspberrypi>
>
> On 1 November 2016 at 19:39, Jacek Skowroński <yac...@gmail.com 
> > wrote:
>
>> Total DISK READ :   0.00 B/s | Total DISK WRITE :   0.00 B/s
>> Actual DISK READ:   0.00 B/s | Actual DISK WRITE:   0.00 B/s
>>   PID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
>>87 be/3 root  0.00 B136.00 K  0.00 %  0.03 % 
>> [jbd2/mmcblk0p2-]
>> 14302 be/4 root  0.00 B704.00 K  0.00 %  0.00 % python 
>> /usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf
>> 12435 be/4 pi0.00 B 24.00 K  0.00 %  0.00 % vmstat 60 1440
>>   495 be/4 root  0.00 B 16.00 K  0.00 %  0.00 % rsyslogd -n
>>
>>
>> On Tuesday, November 1, 2016 at 9:28:58 AM UTC+1, Glenn McKechnie wrote:
>>>
>>> run iotop as * iotop -oaP * This will show running process's only and 
>>> accumulated totals - run it for a while and you'll get a better feel of 
>>> what's happening as regards total writes.
>>>
>>> sqlite write total will be included under the python /usr/bin/weewx 
>>> total - sqlite is a friendlier option for the SDCard
>>>
>>> /dev/ttyUSB0 should be dealt with in memory, no disk access involved
>>>
>>> logging will be visible under iotop as rsyslogd -n (or whatever daemon 
>>> you use).  Turns out, it's not as big a burden as it's made out to be; at 
>>> least on the systems here.
>>>
>>> I wouldn't have thought ftp would add any burden - the files have been 
>>> generated already and it's just reading them.
>>>
>>> As you say, it is a bit odd.
>>>
>>>  
> [...]
>

-- 
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] weewx, raspberry pi and sd cards - the lifetime for card

2016-11-01 Thread Jacek Skowroński

vmstat is from 2 days to see when and what is going on.

I need to talk to my friend who moved files from sd to flash. Because he 
did it for me.


Regards

Jacek


W dniu 2016-11-01 o 10:01, Glenn McKechnie pisze:

/
/I didn't recognize vmstat, a quick search turns up the following.../

"vmstat 60 1440/ > /path/to/vmstat.`date +%d` This will write to a 
file every minute for 24 hours then create a new file and start over."


That might be a good candidate to move over to the flash, along with 
the logs as Andrew suggested.  In fact,it's writing more than the 
logging daemon so you've just doubled the logging load there.


[jbd2/mmcblk0p2-] is the ext4 journal - I always find it interesting 
to see just how large that value gets over time. Make the SDcard 
read-only and that drops to zero.


Keep it running and see what else shows up, anything that pops up 
there is a possible candidate to move to the USBstick or hdd.


The webserver (the image / html files generated by weewx are included 
in weewx's iotop total) can also be moved over to the flash /USB 
stick, hdd, whatever.
The rorpi HowTo moves the webserver into memory (except for NOAA files 
- It's been pointed out that if there are a lot of them, they are 
worth keeping on the drive rather than regenerating.) I haven't 
thought of a valid reason to keep the www files on disk, they are 
regenerated constantly. Although there will be an empty page after a 
weewx  restart, but a placeholder could be kept to inform any one 
unlucky enough to be viewing in that small time window.



Cheers
 Glenn

rorpi - read only raspberry pi + weewx: now with scripts 
<https://github.com/glennmckechnie/rorpi-raspberrypi>


On 1 November 2016 at 19:39, Jacek Skowroński <yace...@gmail.com 
<mailto:yace...@gmail.com>> wrote:


Total DISK READ :   0.00 B/s | Total DISK WRITE :   0.00 B/s
Actual DISK READ:   0.00 B/s | Actual DISK WRITE:   0.00 B/s
  PID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
   87 be/3 root  0.00 B136.00 K  0.00 %  0.03 %
[jbd2/mmcblk0p2-]
14302 be/4 root  0.00 B704.00 K  0.00 %  0.00 % python
/usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid
/etc/weewx/weewx.conf
12435 be/4 pi0.00 B 24.00 K  0.00 %  0.00 % vmstat
60 1440
  495 be/4 root  0.00 B 16.00 K  0.00 %  0.00 %
rsyslogd -n


On Tuesday, November 1, 2016 at 9:28:58 AM UTC+1, Glenn McKechnie
wrote:

run iotop as *iotop -oaP * This will show running process's
only and accumulated totals - run it for a while and you'll
get a better feel of what's happening as regards total writes.

sqlite write total will be included under the python
/usr/bin/weewx total - sqlite is a friendlier option for the
SDCard

/dev/ttyUSB0 should be dealt with in memory, no disk access
involved

logging will be visible under iotop as rsyslogd -n (or
whatever daemon you use). Turns out, it's not as big a burden
as it's made out to be; at least on the systems here.

I wouldn't have thought ftp would add any burden - the files
have been generated already and it's just reading them.

As you say, it is a bit odd.

[...]
--
You received this message because you are subscribed to a topic in the 
Google Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/atRpRzKrlyk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com 
<mailto: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] weewx, raspberry pi and sd cards - the lifetime for card

2016-11-01 Thread Jacek Skowroński
Total DISK READ :   0.00 B/s | Total DISK WRITE :   0.00 B/s
Actual DISK READ:   0.00 B/s | Actual DISK WRITE:   0.00 B/s
  PID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
   87 be/3 root  0.00 B136.00 K  0.00 %  0.03 % 
[jbd2/mmcblk0p2-]
14302 be/4 root  0.00 B704.00 K  0.00 %  0.00 % python 
/usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf
12435 be/4 pi0.00 B 24.00 K  0.00 %  0.00 % vmstat 60 1440
  495 be/4 root  0.00 B 16.00 K  0.00 %  0.00 % rsyslogd -n


On Tuesday, November 1, 2016 at 9:28:58 AM UTC+1, Glenn McKechnie wrote:
>
> run iotop as * iotop -oaP * This will show running process's only and 
> accumulated totals - run it for a while and you'll get a better feel of 
> what's happening as regards total writes.
>
> sqlite write total will be included under the python /usr/bin/weewx total 
> - sqlite is a friendlier option for the SDCard
>
> /dev/ttyUSB0 should be dealt with in memory, no disk access involved
>
> logging will be visible under iotop as rsyslogd -n (or whatever daemon you 
> use).  Turns out, it's not as big a burden as it's made out to be; at least 
> on the systems here.
>
> I wouldn't have thought ftp would add any burden - the files have been 
> generated already and it's just reading them.
>
> As you say, it is a bit odd.
>
>
> Cheers
>  Glenn
>
> rorpi - read only raspberry pi + weewx: now with scripts 
> <https://github.com/glennmckechnie/rorpi-raspberrypi>
>
> On 1 November 2016 at 18:52, Jacek Skowroński <yac...@gmail.com 
> > wrote:
>
>> iotop shows nothing special from time to time 50KB/S write but total is 
>> always 0.
>>
>> I use sqlite version - and the file weewx.sdb was located on external USB 
>> Flash
>>
>> I have default skin, I send data to 4 weathers services and ftping those 
>> to my web server - located in external DC.
>>
>> So in my point of view it's crazy!!!
>>
>> One of my friend told me that the problem could be reading data from 
>> /dev/ttyUSB0 and putting logs on sd card
>>
>> W dniu 2016-11-01 o 00:53, Glenn McKechnie pisze:
>>
>> One way to lock up your SDCard is outlined at rorpi - read only 
>> raspberry pi + weewx: now with scripts
>> <https://github.com/glennmckechnie/rorpi-raspberrypi> 
>> Making the / filesystem 100% read-only should go some way to ensuring the 
>> SDCard will stay around longer. While it mentions using USB sticks and hdd 
>> drives as writable alternatives, the responses in this thread regarding 
>> those will be more useful to you. (FWIW, I find the RAID 1 USB stick setup 
>> intriguing!)
>>
>> Interesting that you've lost so many cards, and have eliminated your 
>> power supply as a problem.
>> How busy is your system? If you run iotop (apt-get install iotop) what 
>> does it show? 
>> <https://github.com/glennmckechnie/rorpi-raspberrypi/wiki/rorpi-raspberrypi-preinstall#Disk_access_viewing_with_iotop_oaP>
>>
>> Are you using mysql? It's a lot busier when it comes to disk access.
>> Also, are you only generating the one skin on the pi? If you have 
>> multiple skins (testing them out or whatever) the image files tend to add 
>> up ( I bricked an 8gb Sandisk Cruzer doing this ), especially at archive 
>> intervals less than 5 minutes. 
>>
>> Cheers
>>  Glenn
>>
>> rorpi - read only raspberry pi + weewx: now with scripts 
>> <https://github.com/glennmckechnie/rorpi-raspberrypi>
>>
>> On 31 October 2016 at 19:34, Jacek Skowroński <yac...@gmail.com 
>> > wrote:
>>
>>> Hi, 
>>> How does Your sd card "live" in raspberry pi?
>>> On my example I lost 5 cards already - all of them by 3-4months long.
>>> Is it normal?
>>>
>>> Yust now I'm looking to get rid of sd cards and write down data 
>>> somewhere else.
>>> Any topics? Any hints?
>>>
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/atRpRzKrlyk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@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+...@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] weewx, raspberry pi and sd cards - the lifetime for card

2016-11-01 Thread Jacek Skowroński
iotop shows nothing special from time to time 50KB/S write but total is 
always 0.


I use sqlite version - and the file weewx.sdb was located on external 
USB Flash


I have default skin, I send data to 4 weathers services and ftping those 
to my web server - located in external DC.


So in my point of view it's crazy!!!

One of my friend told me that the problem could be reading data from 
/dev/ttyUSB0 and putting logs on sd card



W dniu 2016-11-01 o 00:53, Glenn McKechnie pisze:
One way to lock up your SDCard is outlined at rorpi - read only 
raspberry pi + weewx: now with scripts

<https://github.com/glennmckechnie/rorpi-raspberrypi>
Making the / filesystem 100% read-only should go some way to ensuring 
the SDCard will stay around longer. While it mentions using USB sticks 
and hdd drives as writable alternatives, the responses in this thread 
regarding those will be more useful to you. (FWIW, I find the RAID 1 
USB stick setup intriguing!)


Interesting that you've lost so many cards, and have eliminated your 
power supply as a problem.
How busy is your system? If you run iotop (apt-get install iotop) what 
does it show? 
<https://github.com/glennmckechnie/rorpi-raspberrypi/wiki/rorpi-raspberrypi-preinstall#Disk_access_viewing_with_iotop_oaP>


Are you using mysql? It's a lot busier when it comes to disk access.
Also, are you only generating the one skin on the pi? If you have 
multiple skins (testing them out or whatever) the image files tend to 
add up ( I bricked an 8gb Sandisk Cruzer doing this ), especially at 
archive intervals less than 5 minutes.


Cheers
 Glenn

rorpi - read only raspberry pi + weewx: now with scripts 
<https://github.com/glennmckechnie/rorpi-raspberrypi>


On 31 October 2016 at 19:34, Jacek Skowroński <yace...@gmail.com 
<mailto:yace...@gmail.com>> wrote:


Hi,
How does Your sd card "live" in raspberry pi?
On my example I lost 5 cards already - all of them by 3-4months long.
Is it normal?

Yust now I'm looking to get rid of sd cards and write down data
somewhere else.
Any topics? Any hints?


--
You received this message because you are subscribed to a topic in the 
Google Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/atRpRzKrlyk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com 
<mailto: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] Re: import from WU to weewx

2016-10-31 Thread Jacek Skowroński

what does mean such an error?

how to fix it?

Oct 31 22:27:00 raspberrypi wee_import[14634]: manager: unable to add 
record 2016-10-23 23:50:00 CEST (1477259400) to database 'weewx.sdb': 
UNIQUE constraint failed: archive.dateTime
Oct 31 22:27:00 raspberrypi wee_import[14634]: manager: unable to add 
record 2016-10-23 23:55:00 CEST (1477259700) to database 'weewx.sdb': 
UNIQUE constraint failed: archive.dateTime
Oct 31 22:27:01 raspberrypi wee_import[14634]: manager: unable to add 
record 2016-10-24 00:00:00 CEST (147726) to database 'weewx.sdb': 
NOT NULL constraint failed: archive.interval



W dniu 2016-10-31 o 21:35, gjr80 pisze:

I'll answer a couple of these here since they are not explicitly covered in the 
Utilities Guide.

wee_import requires weewx 3.6.0. If you are using 3.5.1 (or earlier) just 
upgrade, upgrading from 3.5.1 is trivial

There is no limit to how many records you can import from WU. That being said, 
records are fetched 1 day at a time (WU limitation) so I don't know I would 
like to import 10 years worth. Also, given WUs quirks who knows what it (WU) 
would do.

Read the wee_import section of the Utilieis Guide carefully as well as the 
comments in the WU import config file, there are limitations to importing from 
WU that you need to be aware of when setting up the import paramaters.

I must take the code down from my GitHub site, that was very early code I 
worked on before it was clear the wee_import was going to be included in weewx. 
Do not use it, it will not end well.

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: import from WU to weewx

2016-10-31 Thread Jacek Skowroński
sorry Mate, I've read it few times, but not is super visible so I'd like to 
use community to help. If it's a huge problem I can do this differently.
Thanks for Your help
Regards
Jacek

On Monday, October 31, 2016 at 8:04:22 PM UTC+1, vince wrote:
>
> On Monday, October 31, 2016 at 11:41:41 AM UTC-7, Jacek Skowroński wrote:
>>
>> does it work on weewx 351?
>>
>> On Monday, October 31, 2016 at 7:07:32 PM UTC+1, Andrew Milner wrote:
>>>
>>> wee_import - see the utilities guide - will retrieve from WU
>>>
>>>
>>>
>>> On Monday, 31 October 2016 19:53:07 UTC+2, Jacek Skowroński wrote:
>>>
>>>> Hi, I wrote in previous topic that I had an issue with my card. It 
>>>> seems I'm 15 days without backup
>>>> Are there any option to get my data from WU or other internet protocol 
>>>> I already used awaeaks or sth?
>>>>
>>>
>
> Jacek - you might want to actually 'read' the utilities guide section.   
> You're asking a lot of questions that seem to indicate you're not trying 
> too hard to look up these things yourself.
>
> Re: version compatibility, if you do a google search for wee_import you'll 
> find Gary's github page (it was the 'first' link for me) with some details 
> if you are < 3.6.0 in your weewx version.
>
>
>  
>

-- 
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: import from WU to weewx

2016-10-31 Thread Jacek Skowroński
does it work on weewx 351?

On Monday, October 31, 2016 at 7:07:32 PM UTC+1, Andrew Milner wrote:
>
> wee_import - see the utilities guide - will retrieve from WU
>
>
>
> On Monday, 31 October 2016 19:53:07 UTC+2, Jacek Skowroński wrote:
>
>> Hi, I wrote in previous topic that I had an issue with my card. It seems 
>> I'm 15 days without backup
>> Are there any option to get my data from WU or other internet protocol I 
>> already used awaeaks or sth?
>>
>

-- 
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: import from WU to weewx

2016-10-31 Thread Jacek Skowroński
thanks great
How many days can I import in general and in row?

On Monday, October 31, 2016 at 7:07:32 PM UTC+1, Andrew Milner wrote:
>
> wee_import - see the utilities guide - will retrieve from WU
>
>
>
> On Monday, 31 October 2016 19:53:07 UTC+2, Jacek Skowroński wrote:
>
>> Hi, I wrote in previous topic that I had an issue with my card. It seems 
>> I'm 15 days without backup
>> Are there any option to get my data from WU or other internet protocol I 
>> already used awaeaks or sth?
>>
>

-- 
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] import from WU to weewx

2016-10-31 Thread Jacek Skowroński
Hi, I wrote in previous topic that I had an issue with my card. It seems 
I'm 15 days without backup
Are there any option to get my data from WU or other internet protocol I 
already used awaeaks or sth?

-- 
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: Davis Vantage Pro2 and WU - best settings

2016-10-31 Thread Jacek Skowroński

Hahaha,

sorry this is only thing I can say.
After Your email I went to the wu.

I use C scale and there is nothing, I had swtched to F scale and there 
are data shown :P


What changed? I had put command to change module type from 8 to 7, so I 
changed leaf_soil to soil only



W dniu 2016-10-31 o 13:48, Thomas Keffer pisze:

Jacek,

Well, that's interesting. The record you posted originally 
<https://groups.google.com/d/msg/weewx-user/WCi0gdv007g/bK6xzM0sAwAJ> 
had values for soilTemp1 and leafTemp1.


REC:2016-10-30 17:30:00 CET (1477845000) altimeter:
30.2914897657, appTemp: 42.5550178172, barometer: 30.332,
cloudbase: 2354.14897393, consBatteryVoltage: 1.68, dateTime:
1477845000, dewpoint: 38.9625445147, ET: 0.0, extraHumid1: None,
extraHumid2: None, extraTemp1: None, extraTemp2: None, extraTemp3:
None, forecastRule: 1, heatindex: 46.1, highOutTemp: 46.1,
highRadiation: None, highUV: None, humidex: 46.1, inDewpoint:
54.6182787763, inHumidity: 49.0, inTemp: 75.1, interval: 5,
leafTemp1: 45.0, leafTemp2: None, leafWet1: None, leafWet2: None,
lowOutTemp: 46.0, maxSolarRad: None, outHumidity: 76.0, outTemp:
46.1, pressure: 29.5091101841, radiation: None, rain: 0.0,
rainRate: 0.0, rxCheckPercent: 97.375, soilMoist1: None,
soilMoist2: None, soilMoist3: None, soilMoist4: None, soilTemp1:
45.0, soilTemp2: None, soilTemp3: None, soilTemp4: None,
txBatteryStatus: 0, usUnits: 1, UV: None, windchill: 46.1,
windDir: 22.5, windGust: 4.0, windGustDir: 22.5, windrun:
54.58, windSpeed: 2.0


The record you posted later 
<https://groups.google.com/d/msg/weewx-user/WCi0gdv007g/A6nJVZRkAwAJ> 
does not:


REC:2016-10-31 10:10:00 CET (1477905000) altimeter:
30.706461, appTemp: 43.3933532069, barometer: 30.374,
cloudbase: 2206.82767798, consBatteryVoltage: 1.68, dateTime:
1477905000, dewpoint: 40.2107582169, ET: 0.0, extraHumid1: None,
extraHumid2: None, extraTemp1: None, extraTemp2: None, extraTemp3:
None, forecastRule: 9, heatindex: 46.7, highOutTemp: 46.8,
highRadiation: None, highUV: None, humidex: 46.7, inDewpoint:
52.0544643875, inHumidity: 50.0, inTemp: 71.7, interval: 5,
leafTemp1: None, leafTemp2: None, leafWet1: None, leafWet2: None,
lowOutTemp: 46.6, maxSolarRad: None, outHumidity: 78.0, outTemp:
46.7, pressure: 29.5501031564, radiation: None, rain: 0.0,
rainRate: 0.0, rxCheckPercent: 99.9375, soilMoist1: None,
soilMoist2: None, soilMoist3: None, soilMoist4: None, soilTemp1:
47.0, soilTemp2: None, soilTemp3: None, soilTemp4: None,
txBatteryStatus: 0, usUnits: 1, UV: None, windchill: 46.7,
windDir: 45.0, windGust: 7.0, windGustDir: 22.5, windrun:
2.917, windSpeed: 2.0


What changed?

Second, the WU servers are very unreliable. They ignore records, 
substitute null values for valid values, substitute invalid values for 
null values, or ignore values altogether. I'm not going to attempt to 
debug them remotely.


In any case, I see a value for soil temperature (51°F) on your WU site 
<https://www.wunderground.com/personal-weather-station/dashboard?ID=IWOJEWDZ56> 
right now. So, clearly, the WU is getting values. It's just choosing 
not to display them consistently.


-tk



On Mon, Oct 31, 2016 at 5:25 AM, Jacek Skowroński <yace...@gmail.com 
<mailto:yace...@gmail.com>> wrote:


ok


W dniu 2016-10-31 o 13:24, Andrew Milner pisze:

Ignore the UV value on WU - I see my station is also showing a UV
value and I also have no UV sensor  Makes you wonder just
where WU get their data from!!!  I do not know when it
started showing UV because I do not actually look at the WU site
very often!!

Andrew


On Monday, 31 October 2016 14:13:03 UTC+2, Andrew Milner wrote:

You actually had a UV value the very first time I looked at
your WU site - then it disappeared.

Just go at this slowly - so far we know that the data is
correctly in the database - so you should also be able to put
the soil temperature onto any web pages that you generate
with weewx reports - then you just need to work with Tom and
make sure restx is outputting the correct format for WU.



On Monday, 31 October 2016 14:06:11 UTC+2, Jacek Skowroński
wrote:

what is crazy now - the wu started to show UV parameter
with value 2, eventhought I do not have UV sensor yet.


W dniu 2016-10-31 o 12:35, Andrew Milner pisze:

did you stop weewx, set debug = 1 and restart weewx for
that log - or what exacly was the log supposed to show?



On Monday, 31 October 2016 13:32:21 UTC+2, Jacek
Skowroński wrote:

some part of log

Oct 31 12:25:15 raspberrypi weewx[11294]: vantage:
Requesting 200 LOOP packets.
Oct 31 12

Re: [weewx-user] Re: Davis Vantage Pro2 and WU - best settings

2016-10-31 Thread Jacek Skowroński

ok


W dniu 2016-10-31 o 13:24, Andrew Milner pisze:
Ignore the UV value on WU - I see my station is also showing a UV 
value and I also have no UV sensor  Makes you wonder just where WU 
get their data from!!!  I do not know when it started showing UV 
because I do not actually look at the WU site very often!!


Andrew


On Monday, 31 October 2016 14:13:03 UTC+2, Andrew Milner wrote:

You actually had a UV value the very first time I looked at your
WU site - then it disappeared.

Just go at this slowly - so far we know that the data is correctly
in the database - so you should also be able to put the soil
temperature onto any web pages that you generate with weewx
reports - then you just need to work with Tom and make sure restx
is outputting the correct format for WU.



On Monday, 31 October 2016 14:06:11 UTC+2, Jacek Skowroński wrote:

what is crazy now - the wu started to show UV parameter with
value 2, eventhought I do not have UV sensor yet.


W dniu 2016-10-31 o 12:35, Andrew Milner pisze:

did you stop weewx, set debug = 1 and restart weewx for that
log - or what exacly was the log supposed to show?



On Monday, 31 October 2016 13:32:21 UTC+2, Jacek Skowroński
wrote:

some part of log

Oct 31 12:25:15 raspberrypi weewx[11294]: vantage:
Requesting 200 LOOP packets.
Oct 31 12:25:15 raspberrypi weewx[11294]: reportengine:
Running report StandardReport
Oct 31 12:25:15 raspberrypi weewx[11294]: vantage: gentle
wake up of console successful
Oct 31 12:25:15 raspberrypi weewx[11294]: reportengine:
Found configuration file
/etc/weewx/skins/Standard/skin.conf for report StandardReport
Oct 31 12:25:16 raspberrypi weewx[11294]: restx:
Wunderground-PWS: Published record 2016-10-31 12:25:00
CET (1477913100)
Oct 31 12:25:16 raspberrypi weewx[11294]:
cheetahgenerator: Generated 14 files for report
StandardReport in 1.25 seconds
Oct 31 12:25:17 raspberrypi weewx[11294]: genimages:
Generated 12 images for StandardReport in 0.58 seconds
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine:
copied 0 files to /var/www/weewx
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine:
Running report FTP
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine:
Found configuration file /etc/weewx/skins/Ftp/skin.conf
for report FTP
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine:
FTP upload not requested. Skipped.
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine:
Running report RSYNC
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine:
Found configuration file /etc/weewx/skins/Rsync/skin.conf
for report RSYNC
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine:
rsync upload not requested. Skipped.
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage:
Getting archive packets since 2016-10-31 12:25:00 CET
(1477913100)
Oct 31 12:30:15 raspberrypi rsyslogd-2007: action 'action
17' suspended, next retry is Mon Oct 31 12:31:45 2016
[try http://www.rsyslog.com/e/2007 ]
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: gentle
wake up of console successful
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage:
Retrieving 1 page(s); starting index= 0
Oct 31 12:30:15 raspberrypi weewx[11294]: manager: added
record 2016-10-31 12:30:00 CET (1477913400) to database
'weewx.sdb'
Oct 31 12:30:15 raspberrypi weewx[11294]: manager: added
record 2016-10-31 12:30:00 CET (1477913400) to daily
summary in 'weewx.sdb'
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: DMPAFT
complete: page timestamp 2016-10-22 16:05:00 CEST
(1477145100) less than final timestamp 2016-10-31
12:30:00 CET (1477913400)
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: Catch
up complete.
Oct 31 12:30:15 raspberrypi weewx[11294]: reportengine:
Running reports for latest time in the database.
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage:
Requesting 200 LOOP packets.
Oct 31 12:30:15 raspberrypi weewx[11294]: reportengine:
Running report StandardReport
Oct 31 12:30:15 raspberrypi weewx[11294]: reportengine:
Found configuration file
/etc/weewx/skins/Standard/skin.conf for report StandardReport
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: gentle
wake up of console

Re: [weewx-user] Re: Davis Vantage Pro2 and WU - best settings

2016-10-31 Thread Jacek Skowroński
what is crazy now - the wu started to show UV parameter with value 2, 
eventhought I do not have UV sensor yet.



W dniu 2016-10-31 o 12:35, Andrew Milner pisze:
did you stop weewx, set debug = 1 and restart weewx for that log - or 
what exacly was the log supposed to show?




On Monday, 31 October 2016 13:32:21 UTC+2, Jacek Skowroński wrote:

some part of log

Oct 31 12:25:15 raspberrypi weewx[11294]: vantage: Requesting 200
LOOP packets.
Oct 31 12:25:15 raspberrypi weewx[11294]: reportengine: Running
report StandardReport
Oct 31 12:25:15 raspberrypi weewx[11294]: vantage: gentle wake up
of console successful
Oct 31 12:25:15 raspberrypi weewx[11294]: reportengine: Found
configuration file /etc/weewx/skins/Standard/skin.conf for report
StandardReport
Oct 31 12:25:16 raspberrypi weewx[11294]: restx: Wunderground-PWS:
Published record 2016-10-31 12:25:00 CET (1477913100)
Oct 31 12:25:16 raspberrypi weewx[11294]: cheetahgenerator:
Generated 14 files for report StandardReport in 1.25 seconds
Oct 31 12:25:17 raspberrypi weewx[11294]: genimages: Generated 12
images for StandardReport in 0.58 seconds
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine: copied 0
files to /var/www/weewx
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine: Running
report FTP
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine: Found
configuration file /etc/weewx/skins/Ftp/skin.conf for report FTP
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine: FTP upload
not requested. Skipped.
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine: Running
report RSYNC
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine: Found
configuration file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine: rsync
upload not requested. Skipped.
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: Getting archive
packets since 2016-10-31 12:25:00 CET (1477913100)
Oct 31 12:30:15 raspberrypi rsyslogd-2007: action 'action 17'
suspended, next retry is Mon Oct 31 12:31:45 2016 [try
http://www.rsyslog.com/e/2007 ]
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: gentle wake up
of console successful
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: Retrieving 1
page(s); starting index= 0
Oct 31 12:30:15 raspberrypi weewx[11294]: manager: added record
2016-10-31 12:30:00 CET (1477913400) to database 'weewx.sdb'
Oct 31 12:30:15 raspberrypi weewx[11294]: manager: added record
2016-10-31 12:30:00 CET (1477913400) to daily summary in 'weewx.sdb'
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: DMPAFT
complete: page timestamp 2016-10-22 16:05:00 CEST (1477145100)
less than final timestamp 2016-10-31 12:30:00 CET (1477913400)
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: Catch up complete.
Oct 31 12:30:15 raspberrypi weewx[11294]: reportengine: Running
reports for latest time in the database.
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: Requesting 200
LOOP packets.
Oct 31 12:30:15 raspberrypi weewx[11294]: reportengine: Running
report StandardReport
Oct 31 12:30:15 raspberrypi weewx[11294]: reportengine: Found
configuration file /etc/weewx/skins/Standard/skin.conf for report
StandardReport
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: gentle wake up
of console successful
Oct 31 12:30:16 raspberrypi weewx[11294]: restx: Wunderground-PWS:
Published record 2016-10-31 12:30:00 CET (1477913400)
Oct 31 12:30:16 raspberrypi weewx[11294]: cheetahgenerator:
Generated 14 files for report StandardReport in 1.19 seconds
Oct 31 12:30:17 raspberrypi weewx[11294]: genimages: Generated 12
images for StandardReport in 0.56 seconds
Oct 31 12:30:17 raspberrypi weewx[11294]: reportengine: copied 0
files to /var/www/weewx
Oct 31 12:30:17 raspberrypi weewx[11294]: reportengine: Running
report FTP
Oct 31 12:30:17 raspberrypi weewx[11294]: reportengine: Found
configuration file /etc/weewx/skins/Ftp/skin.conf for report FTP
Oct 31 12:30:17 raspberrypi weewx[11294]: reportengine: FTP upload
not requested. Skipped.
Oct 31 12:30:17 raspberrypi weewx[11294]: reportengine: Running
report RSYNC
Oct 31 12:30:17 raspberrypi weewx[11294]: reportengine: Found
configuration file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
Oct 31 12:30:17 raspberrypi weewx[11294]: reportengine: rsync
upload not requested. Skipped.
Oct 31 12:30:42 raspberrypi wpa_supplicant[416]: wlan0: WPA: Group
rekeying completed with 1c:87:2c:e5:db:38 [GTK=CCMP]


W dniu 2016-10-31 o 12:30, Andrew Milner pisze:

Right - now we are getting somewhere 

You appear tohave got soilTemp1 in the database with the sensible
looking values . so I guess it is now up to Tom to provide a
way of checking what

Re: [weewx-user] Re: Davis Vantage Pro2 and WU - best settings

2016-10-31 Thread Jacek Skowroński

some part of log

Oct 31 12:25:15 raspberrypi weewx[11294]: vantage: Requesting 200 LOOP 
packets.
Oct 31 12:25:15 raspberrypi weewx[11294]: reportengine: Running report 
StandardReport
Oct 31 12:25:15 raspberrypi weewx[11294]: vantage: gentle wake up of 
console successful
Oct 31 12:25:15 raspberrypi weewx[11294]: reportengine: Found 
configuration file /etc/weewx/skins/Standard/skin.conf for report 
StandardReport
Oct 31 12:25:16 raspberrypi weewx[11294]: restx: Wunderground-PWS: 
Published record 2016-10-31 12:25:00 CET (1477913100)
Oct 31 12:25:16 raspberrypi weewx[11294]: cheetahgenerator: Generated 14 
files for report StandardReport in 1.25 seconds
Oct 31 12:25:17 raspberrypi weewx[11294]: genimages: Generated 12 images 
for StandardReport in 0.58 seconds
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine: copied 0 files 
to /var/www/weewx

Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine: Running report FTP
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine: Found 
configuration file /etc/weewx/skins/Ftp/skin.conf for report FTP
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine: FTP upload not 
requested. Skipped.

Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine: Running report RSYNC
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine: Found 
configuration file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
Oct 31 12:25:17 raspberrypi weewx[11294]: reportengine: rsync upload not 
requested. Skipped.
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: Getting archive 
packets since 2016-10-31 12:25:00 CET (1477913100)
Oct 31 12:30:15 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
next retry is Mon Oct 31 12:31:45 2016 [try http://www.rsyslog.com/e/2007 ]
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: gentle wake up of 
console successful
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: Retrieving 1 page(s); 
starting index= 0
Oct 31 12:30:15 raspberrypi weewx[11294]: manager: added record 
2016-10-31 12:30:00 CET (1477913400) to database 'weewx.sdb'
Oct 31 12:30:15 raspberrypi weewx[11294]: manager: added record 
2016-10-31 12:30:00 CET (1477913400) to daily summary in 'weewx.sdb'
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: DMPAFT complete: page 
timestamp 2016-10-22 16:05:00 CEST (1477145100) less than final 
timestamp 2016-10-31 12:30:00 CET (1477913400)

Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: Catch up complete.
Oct 31 12:30:15 raspberrypi weewx[11294]: reportengine: Running reports 
for latest time in the database.
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: Requesting 200 LOOP 
packets.
Oct 31 12:30:15 raspberrypi weewx[11294]: reportengine: Running report 
StandardReport
Oct 31 12:30:15 raspberrypi weewx[11294]: reportengine: Found 
configuration file /etc/weewx/skins/Standard/skin.conf for report 
StandardReport
Oct 31 12:30:15 raspberrypi weewx[11294]: vantage: gentle wake up of 
console successful
Oct 31 12:30:16 raspberrypi weewx[11294]: restx: Wunderground-PWS: 
Published record 2016-10-31 12:30:00 CET (1477913400)
Oct 31 12:30:16 raspberrypi weewx[11294]: cheetahgenerator: Generated 14 
files for report StandardReport in 1.19 seconds
Oct 31 12:30:17 raspberrypi weewx[11294]: genimages: Generated 12 images 
for StandardReport in 0.56 seconds
Oct 31 12:30:17 raspberrypi weewx[11294]: reportengine: copied 0 files 
to /var/www/weewx

Oct 31 12:30:17 raspberrypi weewx[11294]: reportengine: Running report FTP
Oct 31 12:30:17 raspberrypi weewx[11294]: reportengine: Found 
configuration file /etc/weewx/skins/Ftp/skin.conf for report FTP
Oct 31 12:30:17 raspberrypi weewx[11294]: reportengine: FTP upload not 
requested. Skipped.

Oct 31 12:30:17 raspberrypi weewx[11294]: reportengine: Running report RSYNC
Oct 31 12:30:17 raspberrypi weewx[11294]: reportengine: Found 
configuration file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
Oct 31 12:30:17 raspberrypi weewx[11294]: reportengine: rsync upload not 
requested. Skipped.
Oct 31 12:30:42 raspberrypi wpa_supplicant[416]: wlan0: WPA: Group 
rekeying completed with 1c:87:2c:e5:db:38 [GTK=CCMP]



W dniu 2016-10-31 o 12:30, Andrew Milner pisze:

Right - now we are getting somewhere 

You appear tohave got soilTemp1 in the database with the sensible 
looking values . so I guess it is now up to Tom to provide a way 
of checking what is actually being uploaded to WU if debug does not 
give the output from restx, and then - once you know that WU are 
receiving the data I guess it is up to WU as to why they are not 
displaying it!


Sorry - but I cannot help any more - you need Tom or Gary for the next 
part of the puzzle!!


Good luck



On Monday, 31 October 2016 13:21:17 UTC+2, Jacek Skowroński wrote:

seems that I have a lot of data.


pi@raspberrypi:~ $ sqlite3 /var/lib/weewx/weewx.sdb
SQLite version 3.8.7.1 2014-10-29 13:59:56
Enter ".help" for usage hints.
sqlite> select dateTime, soilTemp1 from archive where soilTemp1 > 0

[weewx-user] Re: weewx, raspberry pi and sd cards - the lifetime for card

2016-10-31 Thread Jacek Skowroński
Have You tried and it work? Could You recommend any certain HDD model and 
usb-hdd adapter model? Does it need external power connector?

On Monday, October 31, 2016 at 10:39:57 AM UTC+1, gjr80 wrote:
>
> Hi again,
>
> As usual Google is your friend - search for 'boot raspberry Pi from USB 
> disk' and you will find a plethora of replies, many of which have tutorials 
> or links to tutorials.
>
> 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] Davis Vantage Pro2 and WU - best settings

2016-10-31 Thread Jacek Skowroński
I have soil_leaf module (ID=2), temp proble is the only one attached to 
the module and it is in slot 1.


The console is configured to get data from ID=2 and module is set to the 
leaf_soil.



That is all on the physical side.

When I press temp button on the console I see temp with no1.

Goig back to the issue, I'd like to have this value in the net so would 
be best to have it in the WU.

Thanks for help

regards
Jacek


W dniu 2016-10-31 o 07:43, Andrew Milner pisze:
have you checked the soil temperature probe is in the correct slot?  
It appears to be being read as a leaf temperature probe and not a soil 
temperature probe.


On Monday, 31 October 2016 08:31:06 UTC+2, Jacek Skowroński wrote:

Yes i have only sensor for temperature
I have No humidity sensor now
Can we somohow force wu to see this data?

Nowhere i told i have other sensors

W dniu poniedziałek, 31 października 2016 Thomas Keffer
<tke...@gmail.com > napisał(a):

Hello, Jacek,

You said you have soil temperature and humidity sensors, but
it appears that you actually have soil and /leaf temperature/
sensors. That is, you have values for soilTemp1and leafTemp1,
but nothing for soilMoist1.

Or, perhaps the sensors are plugged into the wrong probe slot?
You should check.

The WeatherUnderground PWS protocol
<http://wiki.wunderground.com/index.php/PWS_-_Upload_Protocol>
does not recognize leaf temperature, so that would explainwhy
you are not seeing anything.

-tk

On Sun, Oct 30, 2016 at 9:36 AM, Jacek Skowroński
<yace...@gmail.com> wrote:

some logs
REC:2016-10-30 17:30:00 CET (1477845000) altimeter:
30.2914897657, appTemp: 42.5550178172, barometer: 30.332,
cloudbase: 2354.14897393, consBatteryVoltage: 1.68,
dateTime: 1477845000, dewpoint: 38.9625445147, ET: 0.0,
extraHumid1: None, extraHumid2: None, extraTemp1: None,
extraTemp2: None, extraTemp3: None, forecastRule: 1,
heatindex: 46.1, highOutTemp: 46.1, highRadiation: None,
highUV: None, humidex: 46.1, inDewpoint: 54.6182787763,
inHumidity: 49.0, inTemp: 75.1, interval: 5, leafTemp1:
45.0, leafTemp2: None, leafWet1: None, leafWet2: None,
lowOutTemp: 46.0, maxSolarRad: None, outHumidity: 76.0,
outTemp: 46.1, pressure: 29.5091101841, radiation: None,
rain: 0.0, rainRate: 0.0, rxCheckPercent: 97.375,
soilMoist1: None, soilMoist2: None, soilMoist3: None,
soilMoist4: None, soilTemp1: 45.0, soilTemp2: None,
soilTemp3: None, soilTemp4: None, txBatteryStatus: 0,
usUnits: 1, UV: None, windchill: 46.1, windDir: 22.5,
windGust: 4.0, windGustDir: 22.5, windrun: 54.58,
windSpeed: 2.0
LOOP:   2016-10-30 17:30:16 CET (1477845016) altimeter:
30.2924734796, appTemp: 42.4369596271, barometer: 30.333,
cloudbase: 2353.42091128, consBatteryVoltage: 1.68,
dateTime: 1477845016, dayET: 0.0, dayRain: 0.0, dewpoint:
38.8657479904, extraAlarm1: 0, extraAlarm2: 0,
extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0,
extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0,
extraHumid1: None, extraHumid2: None, extraHumid3: None,
extraHumid4: None, extraHumid5: None, extraHumid6: None,
extraHumid7: None, extraTemp1: None, extraTemp2: None,
extraTemp3: None, extraTemp4: None, extraTemp5: None,
extraTemp6: None, extraTemp7: None, forecastIcon: 8,
forecastRule: 1, heatindex: 46.0, humidex: 46.0,
inDewpoint: 54.6182787763, inHumidity: 49.0, insideAlarm:
0, inTemp: 75.1, leafTemp1: 45.0, leafTemp2: None,
leafTemp3: None, leafTemp4: None, leafWet1: None,
leafWet2: None, leafWet3: None, leafWet4: 0.0,
maxSolarRad: None, monthET: 0.0, monthRain: 2.960629922,
outHumidity: 76.0, outsideAlarm1: 0, outsideAlarm2: 0,
outTemp: 46.0, pressure: 29.5100730398, radiation: None,
rain: 0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0,
soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0,
soilMoist1: None, soilMoist2: None, soilMoist3: None,
soilMoist4: None, soilTemp1: 45.0, soilTemp2: None,
soilTemp3: None, soilTemp4: None, stormRain: 0.0,
stormStart: None, sunrise: 1477802580, sunset: 1477837860,
txBatteryStatus: 0, usUnits: 1, UV: None, windchill: 46.0,
windDir: 32.0, windGust: 2.0, windGustDir: 32.0,
windSpeed: 2.0, windSpeed10: 2.0, yearET: 0.0, yearRain:
12.3

so both loop and rec have soilTemp1 value of 45.0.

and here other log
pi@raspberryp

[weewx-user] Re: Davis Vantage Pro2 and WU - best settings

2016-10-30 Thread Jacek Skowroński
/skin.conf for report StandardReport
Oct 30 17:35:16 raspberrypi weewx[10216]: vantage: gentle wake up of 
console successful
Oct 30 17:35:17 raspberrypi weewx[10216]: restx: Wunderground-PWS: 
Published record 2016-10-30 17:35:00 CET (1477845300)
Oct 30 17:35:19 raspberrypi weewx[10216]: cheetahgenerator: Generated 14 
files for report StandardReport in 3.61 seconds
Oct 30 17:35:20 raspberrypi weewx[10216]: genimages: Generated 12 images 
for StandardReport in 0.63 seconds
Oct 30 17:35:20 raspberrypi weewx[10216]: reportengine: copied 9 files to 
/var/www/weewx
Oct 30 17:35:20 raspberrypi weewx[10216]: reportengine: Running report FTP
Oct 30 17:35:20 raspberrypi weewx[10216]: reportengine: Found configuration 
file /etc/weewx/skins/Ftp/skin.conf for report FTP
Oct 30 17:35:20 raspberrypi weewx[10216]: reportengine: FTP upload not 
requested. Skipped.
Oct 30 17:35:20 raspberrypi weewx[10216]: reportengine: Running report RSYNC
Oct 30 17:35:20 raspberrypi weewx[10216]: reportengine: Found configuration 
file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
Oct 30 17:35:20 raspberrypi weewx[10216]: reportengine: rsync upload not 
requested. Skipped.

so any hint what is wrong that WU does not get soil temp?
https://www.wunderground.com/personal-weather-station/dashboard?ID=IWOJEWDZ56#history
 
there is only C sign

On Sunday, October 30, 2016 at 4:52:01 PM UTC+1, Jacek Skowroński wrote:
>
> I'm transferring both modes,
> I had stopped weewx and run weewd so from its output I know taht there is 
> soiltemp1 and has value 46. other has none.
> I did for fe minutes and output was similiar.
> Is it debug? Or it's something different?
>
> On Sunday, October 30, 2016 at 10:21:19 AM UTC+1, Andrew Milner wrote:
>>
>> Tom expressed doubts as to whether WU displayed soil temps on rapid fire 
>> - and you appear to be using rapid fire.  Have you tried uploading normal 
>> archive records instead of rapid firing??
>>
>> Did you run with debug set, as Tom suggested, and confirm that the REC 
>> and LOOP contain the soil temperature??
>>
>>
>> On Sunday, 30 October 2016 10:02:55 UTC+2, Jacek Skowroński wrote:
>>
>>> I had changed the probe slot for 1, and now I have
>>> soilTemp1: 46.0,
>>>
>>> but on the WU page something is strange. I get C close to the soil temp, 
>>> but there is no value.
>>>
>>> https://www.wunderground.com/personal-weather-station/dashboard?ID=IWOJEWDZ56#history
>>>
>>> On Saturday, October 29, 2016 at 9:49:27 PM UTC+2, Jacek Skowroński 
>>> wrote:
>>>>
>>>> Hi,
>>>> I have Davis Vatange pro2 with external leaf_soil module located on 
>>>> ID=2.
>>>> So according to help I did such an command
>>>>
>>>> wee_device --set-transmitter-type=2,8,1,1
>>>>
>>>>
>>>> So if I understood it correctly I would have temperature and humidity 
>>>> of soil on the external temp1 and external hum1.
>>>> How to get those data to WU?
>>>>
>>>> Just now on my station we do not see temp and humidity of the soil.
>>>>
>>>> https://www.wunderground.com/personal-weather-station/dashboard?ID=IWOJEWDZ56
>>>>
>>>> Next topic is best timings for sending data, is it possible to get data 
>>>> in RealTime?
>>>> In general Davis has archival for 5min (300sec) so it sends data every 
>>>> 5minute.
>>>> I had tried rapid fire, but it sends data every 2.5 sec but data 
>>>> changes every 5minute so it's a little bit crazy.
>>>>
>>>> Is there anybody using Davis Vantage pro2 and WU and could share your 
>>>> config?
>>>>
>>>> Thanks in advance
>>>> BR
>>>> Jacek 
>>>>
>>>

-- 
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: Davis Vantage Pro2 and WU - best settings

2016-10-29 Thread Jacek Skowroński
For some reason I get the following values:
soilTemp1: None, soilTemp2: 43.0, soilTemp3: None, soilTemp4: None,

so I have only soilTemp2.
Is it possible to chnge it by software to the soiilTemp1 or should I go to 
the garden and change slot for temperature probe?
Thanks Tom for clarification.

On Saturday, October 29, 2016 at 9:49:27 PM UTC+2, Jacek Skowroński wrote:
>
> Hi,
> I have Davis Vatange pro2 with external leaf_soil module located on ID=2.
> So according to help I did such an command
>
> wee_device --set-transmitter-type=2,8,1,1
>
>
> So if I understood it correctly I would have temperature and humidity of 
> soil on the external temp1 and external hum1.
> How to get those data to WU?
>
> Just now on my station we do not see temp and humidity of the soil.
>
> https://www.wunderground.com/personal-weather-station/dashboard?ID=IWOJEWDZ56
>
> Next topic is best timings for sending data, is it possible to get data in 
> RealTime?
> In general Davis has archival for 5min (300sec) so it sends data every 
> 5minute.
> I had tried rapid fire, but it sends data every 2.5 sec but data changes 
> every 5minute so it's a little bit crazy.
>
> Is there anybody using Davis Vantage pro2 and WU and could share your 
> config?
>
> Thanks in advance
> BR
> Jacek 
>

-- 
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 and Davis vantage pro2 development

2016-10-24 Thread Jacek Skowroński
Hi guys.
>From about 2 years I'm using weewx - thanks for good sw - good job.
>From 6months I'm using Davis Vantage pro2 (6153). Today I had bought 
external module - Davis 6435 for leaf wet and soil data (temperature and 
moisure).
I know that I had to add new ID to get it visible in the Davis console.
I've found that info in documentation: 

Action --set-transmitter-type

If you have additional sensors for your Vantage station, you can configure 
them using your console. However, if you have a Davis Weather Envoy receiver 
, 
it will not have a console! As an alternative, wee_device can do this using 
the command --set-transmitter-type.

For example, to add an extra temperature sensor to channel 3, do the 
following:

wee_device --set-transmitter-type=3,1,2

This says to turn on channel 3, set its type to 1 ("Temperature only"), and 
have it show up in the database as extraTemp2. Here's another example, this 
time for a combined temperature / humidity sensor:

wee_device --set-transmitter-type=5,3,2,4

This will add the combined sensor to channel 5, set its type to 3 
("Temperature and humidity"), and it will show up in the database as 
extraTemp2 and extraHumid4.

The --help option will give you the code for each sensor type.


so there are 2 main questions:

1. Where can I find full specification on external module types?

2. Is here anybody that had already configured weewx with Davis Vantage 
pro2 with 6345 module? How to add soli temperature on the ground? How to 
add soil temp/humidity on the -30cm level. How to add leaf wet data to 
weewx and also send it to the wu?


Thanks for help

Regards

Jacek

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