[weewx-user] Re: Steel Series Gauges and RealTime update - 2.5 second interval - how?

[gjr80]

Steve,

Comments below.

Gary

On Thursday, 22 June 2017 11:37:20 UTC+10, Steve2Q wrote:
>
> Gary,  I have been plodding along but no joy. What is happening is after I 
> make the changes to weewx.conf, post_gauge-data.php, etc., Weewx wont even 
> start, so I don't have a syslog file for you to look at.
>

Looking at the weewx.conf you posted you have two [RealtimeGaugeData] 
stanzas:

# This is the stanza for Real Time Guage Data

[RealtimeGaugeData]
[RealtimeGaugeData]

This will certainly cause weeWX to hiccup very early in the startup, though 
it should give some output to log. I put the same config on a test system 
and received the following in the log:

Jun 22 15:24:17 jessie114 weewx[2288]: engine: Initializing weewx version 
3.7.1
Jun 22 15:24:17 jessie114 weewx[2288]: engine: Using Python 2.7.9 (default, 
Jun 29 2016, 13:08:31) #012[GCC 4.9.2]
Jun 22 15:24:17 jessie114 weewx[2288]: engine: Platform Linux-3.16.0-4-amd64
-x86_64-with-debian-8.8
Jun 22 15:24:17 jessie114 weewx[2288]: engine: Locale is 'en_AU.UTF-8'
Jun 22 15:24:17 jessie114 weewx[2288]: engine: pid file is /var/run/weewx.
pid
Jun 22 15:24:17 jessie114 weewx[2279]: Starting weewx weather system: weewx.
Jun 22 15:24:17 jessie114 weewx[2292]: engine: Error while parsing 
configuration file /home/weewx/weewx.conf
Jun 22 15:24:17 jessie114 weewx[2292]: Reason: 'Duplicate section 
name at line 407.'

You need to remove the second [RealtimeGaugeData] heading. I had a look 
through your posted weewx.conf and nothing else jumps out at me, though the 
proof will be in the pudding so to speak. Once you have made that change 
stop then start weeWX and see how it goes. If weeWX still appears not to 
start, and nothing seems to be in the log, then run weeWX directly; 
 that should give 
you some output direct to screen and hopefully it will indicate what the 
problem is.

Before we worry about the HTTP POST side of things we need to make sure 
gauge-data.txt is being generated by weeWX, if it isn't we will likely end 
up chasing our tails trying to sort out HTTP POST.
 

> If you have the time, maybe you could look over some files and see if you 
> can find what I am doing wrong.
>
> This is my web server structure:
> root directory
>  |
>   -photokinetics.org
>|
>  -Weather
>   |
> - all my weather data in which I created a folder called gauges (which is 
> empty)
>
> On my Weewx machine (RaspberryPi) I used setup.py to do the initial 
> install of weewx.
>
>  First attachment is my post_gauge-data.php file.
>
> Next is my weewx.conf file renamed weewx.conf.modded.txt
>
> rtg.py is in /home/weewx/bin/user
>
> My web server has a folder called .php which contains folders labeled 7.0, 
> 5.6, 5.5, 5.4 and 5.3  Does this mean that my server has php installed and 
> configured?
>

Would seem to be a good sign, if I go to 
http://photokinetics.org/Weather/post_gauge-data.php in my browser I get 
the following error message displayed: 

Parse error: syntax error, unexpected '/' in /home/n2qlq/photokinetics.org/
Weather/post_gauge-data.php on line 28

That tells me 2 things. Firstly, PHP is installed because line 28 is trying 
to be executed (rather than 'displayed' which is what would happen if PHP 
was not enabled). Secondly, there is an error at line 28 in the file. 
Looking at the post_gauge-data.php you posted line 28 is:

$json_file = /photokinetics.org/Weather/gauges/gauge-data.txt

whereas the original was:

$json_file = "data/gauge-data.txt";

so you need to put the quotes back in and end the line with a semi-colon. 
If I am reading your server directory structure correctly (some of those 
lines don't line up to well on a web page) you probably want $json_file to 
be set as follows:

$json_file = "gauges/gauge-data.txt";


> Anyway, Gary, I really appreciate your time in trying to help me out.
>
> Steve
>

-- 
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: Steel Series Gauges and RealTime update - 2.5 second interval - how?

[Steve2Q]

Gary,  I have been plodding along but no joy. What is happening is after I 
make the changes to weewx.conf, post_gauge-data.php, etc., Weewx wont even 
start, so I don't have a syslog file for you to look at.

If you have the time, maybe you could look over some files and see if you 
can find what I am doing wrong.

This is my web server structure:
root directory
 |
  -photokinetics.org
   |
 -Weather
  |
- all my weather data in which I created a folder called gauges (which is 
empty)

On my Weewx machine (RaspberryPi) I used setup.py to do the initial install 
of weewx.

 First attachment is my post_gauge-data.php file.

Next is my weewx.conf file renamed weewx.conf.modded.txt

rtg.py is in /home/weewx/bin/user

My web server has a folder called .php which contains folders labeled 7.0, 
5.6, 5.5, 5.4 and 5.3  Does this mean that my server has php installed and 
configured?

Anyway, Gary, I really appreciate your time in trying to help me out.

Steve





-- 
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 CONFIGURATION FILE
#
# Copyright (c) 2009-2015 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

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

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /home/weewx

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

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

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Valencia Pointe - Boynton Beach, FL"

# Latitude and longitude in decimal degrees
latitude = 26.514
longitude = -80.155

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 30, foot# Choose 'foot' or 'meter' for unit

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be used.
station_type = Ultimeter

# If you have a website, you may specify an URL
#station_url = http://www.example.com

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 6
station_url = http://www.photokinetics.org/Weather
[CC3000]
# This section is for RainWise MarkIII weather stations and CC3000 logger.

# Serial port such as /dev/ttyS0, /dev/ttyUSB0, or /dev/cuaU0
port = /dev/ttyUSB0

# The station model, e.g., CC3000 or CC3000R
model = CC3000

# The driver to use:
driver = weewx.drivers.cc3000
[FineOffsetUSB]
# This section is for the Fine Offset series of weather stations.

# The station model, e.g., WH1080, WS1090, WS2080, WH3081
model = WS2080

# The polling mode can be PERIODIC or ADAPTIVE
polling_mode = PERIODIC

# How often to poll the station for data, in seconds
polling_interval = 60

# The pressure calibration offset, in hPa (millibars)
pressure_offset = 0

# The driver to use:
driver = weewx.drivers.fousb
[Simulator]
# This section for the weewx weather station simulator

# The time (in seconds) between LOOP packets.
loop_interval = 2.5

# The simulator mode can be either 'simulator' or 'generator'.
# Real-time simulator. Sleep between each LOOP packet.
mode = simulator
# Generator.  Emit LOOP packets as fast as possible (useful for testing).
#mode = generator

# The start time. If not specified, the default is to use the present time.
#start = 2011-01-01 00:00

# The driver to use:
driver = weewx.drivers.simulator
[TE923]
# This section is for the Hideki TE923 series of weather stations.

# The station model, e.g., 'Meade TE923W' or 'TFA Nexus'
model = TE923

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

# The default configuration associates the channel 1 sensor with outTemp
# and outHumidity.  To change this, or to associate other channels with
# specific columns in the database schema, use the following maps.
[[sensor_map]]
# Map the remote sensors to columns in the database schema.
outTemp = t_1
outHumidity = h_1

[weewx-user] Re: Adding data from homemade wireless sensors to weewx

[Craig Thom]

Thanks.  I'm using the sdr driver, so I'm leaning toward a service, and 
I've already got a little experience writing one.

On Tuesday, June 20, 2017 at 6:05:12 PM UTC-4, Neville Davis wrote:
>
> In getting the data into weewx.I have a number of different sensors 
> i2C one wire and data from a web sever (json) from my Airconditioner...all 
> being input to weewx.
>
> My basic method is to get data as a csv file by running scripts from boot 
> ( i have 3 of these files being generated in a ramdisk) and then I use 2 
> methods...a driver the get all the weather data and a weewx service to get 
> the data from the aircon. The following is a screen shot of the current 
> conditions.
>
>
>
> On Monday, June 19, 2017 at 10:43:33 PM UTC+10, Craig Thom wrote:
>>
>> Thanks.  My question is really about getting the data into weewx, but 
>> I'll worry about that later.
>>
>> After another message about the sensors themselves, I've decided to go 
>> with low power 915MHz radio using the mysensors org protocol.  I should be 
>> able to get many months from 3xAA batteries.  The parts are coming from 
>> China, so I've got a month or two to think about getting them into weewx. 
>>  It will probably be after the eclipse, since I'll be spending increasing 
>> time testing the hardware and software to photograph it.
>>
>> So sensors through mysensors hub to MQTT broker, and then somehow into 
>> weewx.  In August.
>>
>> On Wednesday, June 14, 2017 at 11:28:27 AM UTC-4, Paul Bartholdi wrote:
>>>
>>> Hello,
>>>
>>> It could be good to have a look at "http://www.yoctopuce.com;. The 
>>> company is based in Geneva, Switzerland, but send products worldwide, with 
>>> typical Swiss high quality. They have extremely low power hubs usb --> 
>>> Ethernet, gsm or WiFi, which can put all the boards asleep and wake up only 
>>> on command from central PC. Boards include barometer, temperature(s), 
>>> humidity, light and many other possibilities not so much related to weather 
>>> station. Software exists for most high level languages (C, C++, Java, 
>>> Python, shell (bash) etc.).
>>> MQTT looks very interesting, but I had no time yet to play with it.  To 
>>> interface other programs with weewx data, I simply interrogate the database 
>>> (mysql).
>>> Hope this helps. Paul
>>>
>>> On Tuesday, June 13, 2017 at 3:53:48 PM UTC+2, Craig Thom wrote:

 tl;dr What's the best way of getting home brew wireless sensor data 
 into weewx?

 I plan to build a soil moisture (and temperature) sensor for my garden 
 bed.  I'll likely build another for leaf wetness and UV index, because the 
 sensors are cheap and it will be fun.

 The question is how best to get this data to weewx.  I am already using 
 the SDR driver for my Acurite 5-in-1 and additional sensors.

 I could use a 433MHz transmitter.  I think, though, I'd have to decide 
 on how to make a packet, then modify rtl_433 to recognize that packet, 
 then 
 modify SDR.py to use that new rtl_433 packet.  This seems pretty 
 complicated.

 Or, since these sensors will be within range of wifi, I could use an 
 ESP2866.  This is attractive because the microcontroller for reading the 
 sensor and processing the data is in the same package.  I really like this 
 idea.

 But how do I get the data to weewx?

 Because the sensor will be running on batteries (and maybe solar cells 
 for the UV/leaf wetness one), I do not want to turn on the wifi radio 
 except when absolutely necessary, so weewx will not be able to initiate 
 contact.

 My first thought was to use ftp, so the sensor connects to an FTP 
 server on my network, probably on the RPi running weewx, and dumps a file. 
  Then I could write a service within weewx to check for that file, read 
 it, 
 and add the data to the LOOP packet.

 But I was reading through old discussions here, and I found one using 
 MQTT as a source for weewx.  There was no resolution reached, other than 
 some references to weeRT that I didn't really understand (and weeRT is a 
 lot harder to Google than weewx).  

 MQTT is attractive because it's a standard, and other things could 
 subscribe to the sensor data (like a home automation program, or something 
 that will turn on the water to the garden bed).

 I'd rather not start from scratch with the regular sensors; I'd like to 
 keep using the sdr driver.

 Is there some really obvious solution that I'm missing?  Is there code 
 someone for producing Acurite-like radio packets so my sensors could just 
 pretend to be a tower sensor or something?

 (I was concerned about getting accurate numbers from a soil moisture 
 sensor, because all my reading says it depends on soil type, and it needs 
 to be calibrated, etc., but Davis doesn't do any of that calibration, and 
 if just using relative 

[weewx-user] Re: Can't Get Custom Driver To Load

[gjr80]

Bob,

When weeWX v3 was released there were a lot of changes (the big one was the 
database structure - but that thas no effect on your driver). A lot of the 
other changes were more subtle; some functions were renamed, others moved 
and others reworked. One significant change was the move of the calculation 
of so called derived observations (eg heatindex) out of the drivers and 
into the service StdWXCalculate. 

So what, well knowing this and given that your driver is fairly basic, it 
is not too hard to rework your driver to be v3 compatible. I sat down this 
morning and worked through it, did not take long. Have a look at the 
attached Raspberry_Pi.txt (can't attach .py). The changes were:

   1. use weewx.drivers rather than weewx.abstractstation
   2. base class for your driver is now weewx.drivers.AbstractDevice
   3. remove the heatindex, altimeter etc calcs from the driver, StdWXCalculate 
   will take care of this
   4. due to 2. we can remove the altitude stuff from the loader() method

Left the heating and cooling degree stuff there, that is not covered by the 
StdWXCalculate 
service. This revised driver loads OK under 3.7.1, I didn't go as far as 
setting up the data file to test it fully, that bit is up to you!


Gary

On Wednesday, 21 June 2017 22:45:21 UTC+10, Bob Snyder wrote:
>
> Awesome, Gary.  That did it. Thank you!  Now time to chase down driver 
> bugs.  Seems this one is from 2.x and has issues.  Thanks again!
>
> On Tuesday, June 20, 2017 at 10:23:31 PM UTC-5, gjr80 wrote:
>>
>> Jun 20 21:17:30 wx-rpi weewx[24467]: engine: Using configuration file /
>>> etc/weewx/weewx.conf
>>>
>>
>> Ahah, my mistake, I assumed this was a setup.py instal 
>> l but it appears it is not.
>>
>> No matter, do you have a directory /usr/share/weewx/user ? If so, try 
>> putting Raspberry_Pi.py there, stop then start weeWX and see how that 
>> goes. If it fails or if such a directory doesn't exist, it might be time to 
>> post weewx.conf in its entirety (remove any passwords/sensitive info) as 
>> well as a log extract from weewx start until it exits; often there are 
>> clues in the leadup to, or the error trace after, the error occurs.
>>
>> Gary
>>
>> On Wednesday, 21 June 2017 13:03:24 UTC+10, Bob Snyder wrote:
>>>
>>> Thanks for the quick reply, Gary.  Yes, /usr seemed odd to me.  My mind 
>>> went there instead of user when I read where to create the driver script.  
>>>
>>> I implemented the changes you suggested but get the same error.
>>>
>>> pi@wx-rpi:/home/weewx/bin/user $ ls -l
>>> total 4
>>> -rw-r--r-- 1 pi pi 2664 Jun 20 21:17 Raspberry_Pi.py
>>>
>>> [Raspberry_Pi]
>>> loop_interval = 5
>>> driver = user.Raspberry_Pi
>>>
>>> Jun 20 21:53:16 wx-rpi weewx[24736]: engine: Loading station type 
>>> Raspberry_Pi (user.Raspberry_Pi)
>>> Jun 20 21:53:16 wx-rpi weewx[24736]: engine: Caught unrecoverable 
>>> exception in engine:
>>> Jun 20 21:53:16 wx-rpi weewx[24736]:   No module named 
>>> Raspberry_Pi
>>>
>>>
>>>
>>> On Tuesday, June 20, 2017 at 9:36:41 PM UTC-5, gjr80 wrote:

 Hi,

 I think you should be putting your Raspberry_Pi.py file in the 
 /home/weewx/bin/user 
 directory not /usr.

 Also, under [Raspberry_Pi] you should use

 driver = user.Raspberry_Pi

 not 

 driver = usr.Raspberry_Pi

 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.
#
#$Revision: 1 $
#$Author: Nickolas McColl $
#$Date: 2014-08-16 $
#
"""Raspberry Pi driver for the weewx weather system"""


from __future__ import with_statement
# import math
import time
#import weedb
#import weeutil.weeutil
import weewx.drivers
import weewx.wxformulas




def loader(config_dict, engine):

return Raspberry_Pi(**config_dict['Raspberry_Pi'])


class Raspberry_Pi(weewx.drivers.AbstractDevice):
"""Station using Raspberry Pi"""


def __init__(self, **stn_dict):
self.loop_interval = float(stn_dict.get('loop_interval'))


def genLoopPackets(self):


while True:
start_time = time.time()


# Create Loop packet
f = open('/var/tmp/weewx/bin/wxdata.csv')
input = f.readline()
f.close()
data = input.split(',')
if len(data) == 13: # data line is complete, process
for i in range(1, (len(data))):
try:
data[i] = float(data[i])
except ValueError:
data[i] = None


raw_time =time.strptime(data[0], "%Y-%m-%d %H:%M:%S")


_packet = {'dateTime': int(time.mktime(raw_time)),
   'usUnits' : weewx.METRIC,

Re: [weewx-user] Re: Failure in my network with weewx and raspbian

[Thomas Keffer]

Incidentally, these errors are slightly easier to find with the current
version of Weewx. Starting with V3.3.0 it will tell you which template the
problem is in.

You have V3.1.0.

Consider upgrading.

-tk

On Wed, Jun 21, 2017 at 1:52 PM, Thomas Keffer  wrote:

> The problem is that you have a bad UTF-8 character in one of the templates
> used in StdReport. This caused an exception, preventing the HTML file from
> being generated. It has nothing to do with the network.
>
> These UTF-8 errors can be tough to find. Check the file index.html.tmpl
> carefully for a bad character. If you don't know how to do this, I will try
> to help.
>
> -tk
>
>
> On Wed, Jun 21, 2017 at 8:47 AM, Antonio R  wrote:
>
>>
>> The failures begin.
>> The page does not update this at 9:12 a.m.
>> Internet does not fail, for now.
>>
>>
>>
>> El martes, 20 de junio de 2017, 18:35:48 (UTC+2), Antonio R escribió:
>>>
>>> I've been using a weewx image for years, and lately what happens to me
>>> is, that without failing in the program, what happens is that my network
>>> drops down, the connection fails, the router reboots, I do not have any
>>> speed And when I disconnect the raspberry Pi all perfect, I spent a few
>>> days using another wview program and everything perfect.
>>> The log does not give me any fault, right now I do not have it so, but
>>> previously, I get to configure all the devices in my network with fixed IP,
>>> so that there were conflicts with the IP and nothing, I despair and
>>> dismantle the raspberry Pi, Now I have come again the desire to try and
>>> I am in it, when this happens to me, it is nothing more to assemble the
>>> image, it is to the four days aprox, during this time everything well.
>>> Let's see if anyone has ever seen this ???.
>>> If it were of interest you could attach the weewx.conf or the log file.
>>> To say that I am a novice in Raspbian, all the montages I have done have
>>> been with images already configured and not really installed from scratch,
>>> with raspbian and the image of weewx, I have only done it a few times.
>>> Thank you
>>>
>>> http://62.175.41.238/weewx/
>>> Station Watson W-8681  FineOffsetUSB
>>> Raspbian Jessie-Lite 10/04/2017
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

Re: [weewx-user] Re: Failure in my network with weewx and raspbian

[Thomas Keffer]

The problem is that you have a bad UTF-8 character in one of the templates
used in StdReport. This caused an exception, preventing the HTML file from
being generated. It has nothing to do with the network.

These UTF-8 errors can be tough to find. Check the file index.html.tmpl
carefully for a bad character. If you don't know how to do this, I will try
to help.

-tk


On Wed, Jun 21, 2017 at 8:47 AM, Antonio R  wrote:

>
> The failures begin.
> The page does not update this at 9:12 a.m.
> Internet does not fail, for now.
>
>
>
> El martes, 20 de junio de 2017, 18:35:48 (UTC+2), Antonio R escribió:
>>
>> I've been using a weewx image for years, and lately what happens to me
>> is, that without failing in the program, what happens is that my network
>> drops down, the connection fails, the router reboots, I do not have any
>> speed And when I disconnect the raspberry Pi all perfect, I spent a few
>> days using another wview program and everything perfect.
>> The log does not give me any fault, right now I do not have it so, but
>> previously, I get to configure all the devices in my network with fixed IP,
>> so that there were conflicts with the IP and nothing, I despair and
>> dismantle the raspberry Pi, Now I have come again the desire to try and
>> I am in it, when this happens to me, it is nothing more to assemble the
>> image, it is to the four days aprox, during this time everything well.
>> Let's see if anyone has ever seen this ???.
>> If it were of interest you could attach the weewx.conf or the log file.
>> To say that I am a novice in Raspbian, all the montages I have done have
>> been with images already configured and not really installed from scratch,
>> with raspbian and the image of weewx, I have only done it a few times.
>> Thank you
>>
>> http://62.175.41.238/weewx/
>> Station Watson W-8681  FineOffsetUSB
>> Raspbian Jessie-Lite 10/04/2017
>>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[weewx-user] Re: Davis Vantage Pro 2 - CentOS - data collection

[mwall]

rui,

this sounds like a fun project!

weewx can do a few things for you:

1) collect data from hardware.  it sounds like you might have a 
non-standard data logger system.  if so, you might have to create your own 
driver, or adapt one of the many custom drivers now available.  if it is 
standard davis equipment then weewx should work out-of-the-box for you.

2) local data storage (data logging).  by default weewx saves to a sqlite 
database, but it could save to a local mysql database instead.

3) local dashboards (reports).  generate HTML, text, XML, json, csv, as 
well as PNG plots.  these can optionally be uploaded to a remote server 
using rsync or ftp.

4) forward data to an aggregator (upload/relay).  this can be done using 
many different protocols, from HTTP to MQTT.  the weewx wiki has a list of 
many of these uploader services.

these functions are somewhat independent.  for example, you can configure 
weewx to only collect data and save to local data store (1 and 2 only).  or 
you could configure it to collect data and send to an aggregator (1 and 4 
only).  or you could configure it to receive and display data (1, 2, and 3).

the local storage is quite useful.  we run many weewx sites where the data 
are uploaded for use by a wider audience.  but often the connection between 
weewx and the aggregation sites is not reliable.  since weewx stores a 
local copy of the data, it can 'fill in the gaps' when connectivity is 
reestablished.  in that respect it is acting as a data logger, but with 
more intelligence than the dumb logger that comes with many weather 
stations.

as for the dashboards and publishing data, please see 'strategies for 
publishing dashboards' on the weewx wiki:

https://github.com/weewx/weewx/wiki/dashboards

it sounds like you might want both use case 4 and use case 5.

finally, imho you should avoid ftp.  use rsync for bulk updates of 
reports/dashboards.  or, if possible, upload data directly using HTTP PUT 
or MQTT and have the aggregator do the report generation and dashboards.

m

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

[weewx-user] Davis Vantage Pro 2 - CentOS - data collection

[Rui Fernandes]

Dear All,
  First of all, I apologize to ask a question that might be a little bit 
off-topic since it is quite generic.

  I'm installing a Davis Vantage Pro 2 weather station collocated with a 
GNSS equipment. It was not acquired by my group and we are trying to figure 
out if and how we can collect and transmit the data via internet with this 
type of equipment. The weather station is linked to the data-logger via 
wireless (working perfectly) and we also have a CentOS computer that we are 
planning to use (if possible) to download the data from the data-logger via 
ethernet cable (the data-logger has an ethernet adapter).

  The connection is quite terrible (it is in south of Madagascar) and we 
will have no real ip. Therefore, we are not planning to use the PC as web 
server to show the data. We would like to send the data to our server (in 
Reunion) via ftp or other protocol where after could be disseminated to 
others.

  So, the Windows software that is coming with the weather station is 
hopeless. After some research, we found the weeWX, which looks the best 
option to download the data from the data-logger.

  Some questions:
 a) anyone with this kind of experience can advise us if indeed the 
installation of the weeWX is the best option or are there another easier 
alternatives to retrieve the data (sorry for this question)?
 
 b) is there any particular option on weewx.conf and/or standard.skin 
that we should use in order to simplify the system?

  Thanks in advance for any support.

  Cheers,
  Rui Fernandes

-- 
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: Can't Get Custom Driver To Load

[Bob Snyder]

Awesome, Gary.  That did it. Thank you!  Now time to chase down driver 
bugs.  Seems this one is from 2.x and has issues.  Thanks again!

On Tuesday, June 20, 2017 at 10:23:31 PM UTC-5, gjr80 wrote:
>
> Jun 20 21:17:30 wx-rpi weewx[24467]: engine: Using configuration file /etc
>> /weewx/weewx.conf
>>
>
> Ahah, my mistake, I assumed this was a setup.py instal 
> l but it appears it is not.
>
> No matter, do you have a directory /usr/share/weewx/user ? If so, try 
> putting Raspberry_Pi.py there, stop then start weeWX and see how that 
> goes. If it fails or if such a directory doesn't exist, it might be time to 
> post weewx.conf in its entirety (remove any passwords/sensitive info) as 
> well as a log extract from weewx start until it exits; often there are 
> clues in the leadup to, or the error trace after, the error occurs.
>
> Gary
>
> On Wednesday, 21 June 2017 13:03:24 UTC+10, Bob Snyder wrote:
>>
>> Thanks for the quick reply, Gary.  Yes, /usr seemed odd to me.  My mind 
>> went there instead of user when I read where to create the driver script.  
>>
>> I implemented the changes you suggested but get the same error.
>>
>> pi@wx-rpi:/home/weewx/bin/user $ ls -l
>> total 4
>> -rw-r--r-- 1 pi pi 2664 Jun 20 21:17 Raspberry_Pi.py
>>
>> [Raspberry_Pi]
>> loop_interval = 5
>> driver = user.Raspberry_Pi
>>
>> Jun 20 21:53:16 wx-rpi weewx[24736]: engine: Loading station type 
>> Raspberry_Pi (user.Raspberry_Pi)
>> Jun 20 21:53:16 wx-rpi weewx[24736]: engine: Caught unrecoverable 
>> exception in engine:
>> Jun 20 21:53:16 wx-rpi weewx[24736]:   No module named 
>> Raspberry_Pi
>>
>>
>>
>> On Tuesday, June 20, 2017 at 9:36:41 PM UTC-5, gjr80 wrote:
>>>
>>> Hi,
>>>
>>> I think you should be putting your Raspberry_Pi.py file in the 
>>> /home/weewx/bin/user 
>>> directory not /usr.
>>>
>>> Also, under [Raspberry_Pi] you should use
>>>
>>> driver = user.Raspberry_Pi
>>>
>>> not 
>>>
>>> driver = usr.Raspberry_Pi
>>>
>>> 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] Failure in my network with weewx and raspbian

[Antonio R]

Okay Thomas, I'll be attentive and when I start failing I'll let you know.
Indeed a friend of my area told me the same as you, but I see that my
connection falls for no reason.
Thank you very much when my connection fails, I will attach all the data
you have.
Thank you very much.

Antonio Rocamora










2017-06-20 19:55 GMT+02:00 Thomas Keffer :

> I don't see how weewx could *cause* your internet connection to fail.
>
> The other way around is possible: a bad internet connection could cause
> weewx to fail, but that would be a bug.
>
> If and when you have the problem again, be sure to submit the log. It is
> impossible to diagnose the problem without knowing precisely what we are
> trying to solve!
>
> -tk
>
>
>
> On Tue, Jun 20, 2017 at 10:36 AM, Antonio R  wrote:
>
>> Ok thanks a lot, but what worries me is in a few days, the fall of my
>> internet connection, because of weewx.
>> Thanks friend.
>>
>> Antonio Rocamora
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 2017-06-20 19:18 GMT+02:00 Thomas Keffer :
>>
>>> On Tue, Jun 20, 2017 at 10:14 AM, Andrew Milner <
>>> andrew.s.r.mil...@gmail.com> wrote:
>>>
 unstable read, blocks differ - it is 'normal' to have 5-10 of these
 error messages per day with fousb and wh1080/2080 stations - so do not
 worry about those.

>>>
>>>
>>> ​... which is what he noted.
>>>
>>> --
>>> 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/No901m846_8/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.
>>
>
> --
> 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/No901m846_8/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.