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

[Dan Verbus]

I've got a service written that works, if you want a copy. Each sensor 
publishes to it's own MQTT topic and the service reads off the queue 
whenever it receives a loop packet and appends whatever data it finds. Let 
me know and I'll post it.

Dan


On Wednesday, June 21, 2017 at 7:37:28 PM UTC-4, Craig Thom wrote:
>
> 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.
>
> 

[weewx-user] Re: weewx time is wrong

[vince]

Hard to help much without knowing which os and version you're runnning, but 
in general you should be running ntp on your pi and not running 
fake-hwclock.   Try "ntpq -pn" to see your offset from the NTP reference 
time servers.

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

[weewx-user] Re: weewx and aercus weatherRanger problem with updating

[Damjan Hajsek]

Dne ponedeljek, 11. september 2017 16.00.53 UTC+2 je oseba mwall napisala:
>
>
>
> On Monday, September 11, 2017 at 9:24:48 AM UTC-4, Damjan Hajsek wrote:
>>
>> Thank you for helping, now I have more infos.
>> I have already setup my weather station to send data, but I am soure I 
>> miss something with weewx.
>> Below are settings from my weather station
>>
>> [Menu]
>> default=www.wunderground.com
>> web=1
>> web1=www.wunderground.com
>> web2=vreme.povej.net 
>>
>> [www.wunderground.com]
>> Server=www.wunderground.com 
>> ServerType=php
>> ServerPort=80
>> UploadType=Customize
>> ReadOnly=true
>>
>> [vreme.povej.net ]
>> Server=vreme.povej.net 
>> ServerType=php
>> ServerPort=80
>> UploadType=Customize
>> ReadOnly=true
>>>
>>>
>>>
> is weewx running on vreme.povej.net?
>
> you must set Server=x.x.x.x where x.x.x.x is the ip address (or host name) 
> of the computer on which weewx is running with the weewx-interceptor driver.
>
> then configure the interceptor driver to be in listen mode on port 80
>
> if weewx is running on a computer that is already running a web server on 
> port 80, then configure weewx to use some other port, say 8000, and set 
> ServerPort on the weather station to that port
>
> set debug=1 then watch the log to see when weewx starts to receive data
>
> m
>

ok what I did, is first to reconfigure to interceptor driver (device_type = 
observer), and set port 8880 in weewx.conf and than restart weewex, which 
is now running on povej.net I have also opened port 8880 on firewall
than set port 8880 on my weather station ServerPort=8880 and restart 
weather station. I also set Server=X.X.X.X my server IP.

debug is still enabled 1 in weewx.conf

I checked www.wunderground.com and now it updates from my weather station, 
but my http://vreme.povej.net is still not updated.
Don't know what should I set on weather station for ServerType=php
should it be ServerType=php or ServerType=jsp


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

[weewx-user] Re: weewx time is wrong

[zkab]

I did following:
sudo wee_device --set-time 
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.0.10 (weewx.drivers.vantage)
Setting time on console...
Current console time is 2017-09-11 19:05:13 CEST (1505149513)
which is correct time.

And then I issued following command:
sudo wee_device --info
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.0.10 (weewx.drivers.vantage)
Querying...
Davis Vantage EEPROM settings:

CONSOLE TYPE:   VantageVue

CONSOLE FIRMWARE:
  Date: Feb  3 2015
  Version:  4.18

CONSOLE SETTINGS:
  Archive interval: 300 (seconds)
  Altitude: 31 (meter)
  Wind cup type:large
  Rain bucket type: 0.2 MM
  Rain year start:  1
  Onboard time: 2017-09-11 19:06:47

which also seems to be correct time. But weewx/standard displays wrong time 
'11-Sep-2017 09:30'
Can't figure out what is wrong ... but something is very wrong

Den måndag 11 september 2017 kl. 16:51:38 UTC+2 skrev zkab:
>
> I run Standard weewx on a RPi and the weewx-time is wrong.
> The RPi gets the time from a ntp-server and the 'date' gives my a correct 
> time.
> How can I get weewx to fetch the right system time?
> I have fake-hwclock installed on RPi ...
> Have read several solutions but don't know how to proceed ... one solution 
> suggest to remove fake clock (sudo apt-get purge fake-hwclock)
>
>

-- 
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 time is wrong

[zkab]

I run Standard weewx on a RPi and the weewx-time is wrong.
The RPi gets the time from a ntp-server and the 'date' gives my a correct 
time.
How can I get weewx to fetch the right system time?
I have fake-hwclock installed on RPi ...
Have read several solutions but don't know how to proceed ... one solution 
suggest to remove fake clock (sudo apt-get purge fake-hwclock)

-- 
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: One shot 'Daily Summaries' using php.

[Glenn McKechnie]

Okay, done!

It's now a skin in its own right, AND it should now work for everyone
(famous last words?). The reason I say that is; I belatedly realized that
not everyone has appTemp, nor do they necessarily want deltaT - both of
which add some complexity to the installation.

appTemp and deltaT are still in there, they are available with some editing
of skin.conf plus some low level head scratching; but if you install the
skin and run it as is, you'll get windchill in place of appTemp, and deltaT
will be ignored completely, all without touching skin.conf.

All the required configuration values, for the default setup are picked up
by the SLE.  Database units don't matter (sort of, but you'll want to fix
them if you're metric ) and the php file (wxobs.inc) doesn't need to be
opened as all configuration is now done via the accepted skin.conf

I've added the imperial conversion to the deltaT, but as its all done
outside weewx  and direct from the database then the group_units do need to
be configured correctly - thus the head scratching.

I can't say it's a truly barebones skin.conf, but if the defaults are
accepted then nothing more needs to be changed. Everything that is needed
is picked up by the SLE. After that well, with options comes complexity.

Actually, I lie. The group_units will need enabling in skin.conf as it
picks those up from weewx, and weewx defaults to imperial. So, if your
station outputs metric units, you'll need to adjust those, as required.

If it's a keeper and you want to integrate it with your skin, I'd leave it
in its existing subdirectory. Make an empty template for your skin of
choice and add *#include wxobs.inc *between the body tags, then edit the
head area to point to the correct .js and .css file, and whatever else is
required. That should be the easiest and quickest way.

Enough...
Where is it? Still at -

https://github.com/glennmckechnie/weewx-wxobs




Cheers
 Glenn

rorpi - read only raspberry pi + weewx: now with scripts


On 6 September 2017 at 21:54, mwall  wrote:

> lets say that you want to distribute a feature that is not a 'complete'
> skin, but just some functionality that someone might add to another skin.
> examples include the forecast extension (a service, search list extension,
> and skin components), or your own data comparison (just a skin component).
>
> when you package that extension, include a 'skin' directory with a skin
> that shows the functionality.  that skin should be simple - probably
> nothing more than a bare-bones skin.conf and a single index.html.tmpl, plus
> whatever bits the feature needs.  the index.html.tmpl should be bare-bones
> too - just an illustration of how to put the functionality into a tmpl.
>
> when someone installs your extension, they get the skin(s).  the installer
> should *not* touch any other skins.
>
> in order to add the functionality to an existing skin, one must follow the
> pattern of the included skin.conf and index.html.tmpl and manually insert
> those bits into the skin that is receiving the feature.  for example, there
> will probably be some edit of the tmpl (hopefully just adding an #include
> and possibly a .css inclusion), and there might be some edit of the
> skin.conf (for example, adding to the CopyGenerator or adding a search list
> extension package to the CheetahGenerator).
>
> doing automatic insertion into an existing skin cannot happen with the
> current skin framework - there are too many ways it could break things, and
> removal would be even more problematic.
>
>
> --
> 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: weewx and aercus weatherRanger problem with updating

[Damjan Hajsek]

Thank you for helping, now I have more infos.
I have already setup my weather station to send data, but I am soure I miss 
something with weewx.
Below are settings from my weather station

[Menu]
default=www.wunderground.com
web=1
web1=www.wunderground.com
web2=vreme.povej.net 

[www.wunderground.com]
Server=www.wunderground.com 
ServerType=php
ServerPort=80
UploadType=Customize
ReadOnly=true

[vreme.povej.net ]
Server=vreme.povej.net 
ServerType=php
ServerPort=80
UploadType=Customize
ReadOnly=true

Dne ponedeljek, 11. september 2017 15.00.56 UTC+2 je oseba mwall napisala:
>
> On Monday, September 11, 2017 at 7:48:18 AM UTC-4, Damjan Hajsek wrote:
>>
>> Is it not possible to send data from weather station to weewx? Like 
>> weather station sends data to www.wunderground.com?
>>
>
> yes, this is exactly what the weewx-interceptor driver does.
>
> there are two modes of operation:  listen or sniff.  
>
> to use the driver in listen mode, you must configure the weather station 
> to send data to weewx, or you must use a proxy, such as a web server that 
> then redirects or forwards the data to weewx, or you must hijack dns so 
> that the weather station *thinks* it is sending to wunderground but 
> actually sends to weewx.  details are in the readme for the 
> weewx-interceptor driver.
>
> to use the driver in sniff mode, weewx must be on the same network as the 
> station.  weewx then 'sniffs' whatever data the station is sending to 
> wunderground.  details are in the readme for the weewx-interceptor driver.
>
> the hp1000 driver communicates directly with the weather station.
>
> m
>
>
>
>

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

Re: [weewx-user] Re: weewx and aercus weatherRanger problem with updating

[Damjan Hajsek]

Ins't eaysweatherIP also for sending data?
http://www.aercusinstruments.com/content/downloads/EasyWeatherIP%20Setup%281022%29.zip


Dne ponedeljek, 11. september 2017 14.44.05 UTC+2 je oseba Damjan Hajsek 
napisala:
>
> OK, now I see.
> Weather stations sends data, like on www.wunderground.com
> So it is possible to send data also to my web server and than setup weewx 
> to read that data?
>
>
> Dne ponedeljek, 11. september 2017 13.57.32 UTC+2 je oseba Andrew Milner 
> napisala:
>>
>> No
>>
>> weewx does not receive data - it reads data.  It is not 'listening' - it 
>> is controlling.
>>
>> If you can get a data file onto the weewx machine then weewx can be made 
>> to read the file instead of a weather station - but the simple answer to 
>> your question is no - unless you write a lot of code in which case anything 
>> is possible!!.
>>
>> Most people in your situation would use an old pc or raspberry pi to run 
>> weewx and get the data from the weather station, and then use weewx's ftp 
>> and rsync capabilities to a) generate web pages  b) ftp web pages to a 
>> webserver  c) use rsync to take backups of weewx database to offsite server 
>> and would have a webserver running elsewhere to serve the weewx generated 
>> web pages.
>>
>>
>>
>> On 11 September 2017 at 14:48, Damjan Hajsek  wrote:
>>
>>> Is it not possible to send data from weather station to weewx? Like 
>>> weather station sends data to www.wunderground.com?
>>>
>>> Dne ponedeljek, 11. september 2017 12.28.50 UTC+2 je oseba Andrew Milner 
>>> napisala:

 You need to have weewx installed on a server or pc on the same local 
 network as the weather station for the driver to work.  Yes, the driver 
 talks directly to the station over wifi and from what I can read it 
 identifies the ip address of the station by broadcasting on the local 
 network.

 Weewx can then upload/transfer vie ftp or rsync the generated pages to 
 the offsite server which you have got in another location.  Weewx only 
 creates the pages and stores the database - it does not do the webserver 
 aspects of a web site.



 On Monday, 11 September 2017 11:57:54 UTC+3, Damjan Hajsek wrote:

> As far as I read about this HP1000 driver it connect to weather 
> station.
> But my weather station is at home and server is on other location. I 
> thought weather station sends data to my server where weewx is installed 
> and this shows up on my weewx web pages.
>
> Dne ponedeljek, 11. september 2017 09.01.18 UTC+2 je oseba Damjan 
> Hajsek napisala:
>>
>> I checked log and it is full of this
>>
>> weewx[26283]: HP1000: Timed out too many times
>>
>>
>> Sep 11 08:28:10 webserver weewx[26279]: engine: Initializing weewx 
>> version 3.7.1
>> Sep 11 08:28:10 webserver weewx[26279]: engine: Using Python 2.7.5 
>> (default, Nov  6 2016, 00:28:07) #012[GCC 4.8.5 20150623 (Red Hat 
>> 4.8.5-11)]
>> Sep 11 08:28:11 webserver weewx[26279]: engine: Platform 
>> Linux-3.10.0-514.26.1.el7.x86_64-x86_64-with-centos-7.3.1611-Core
>> Sep 11 08:28:11 webserver weewx[26279]: engine: Locale is 'sl_SI.UTF-8'
>> Sep 11 08:28:11 webserver weewx[26279]: engine: pid file is 
>> /var/run/weewx.pid
>> Sep 11 08:28:11 webserver weewx[26283]: engine: Using configuration file 
>> /etc/weewx/weewx.conf
>> Sep 11 08:28:11 webserver weewx: Starting weewx: [  V redu  ]
>> Sep 11 08:28:11 webserver weewx[26283]: engine: Loading station type 
>> HP1000 (user.HP1000)
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: HP1000 Starting
>> Sep 11 08:28:11 webserver systemd: Started SYSV: start and stop the 
>> weewx weather system.
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Using "netifaces" to 
>> determine broadcast mask
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Address Mask = 
>> XXX.XXX.255.255
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Retry count = 5.00
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Socket timeout = 5.00
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Loop delay = 15.00
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Retry Wait = 5.00
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Max Retry = 3.00
>> Sep 11 08:28:11 webserver weewx[26283]: engine: StdConvert target unit 
>> is 0x1
>> Sep 11 08:28:11 webserver weewx[26283]: wxcalculate: The following 
>> values will be calculated: barometer=prefer_hardware, 
>> windchill=prefer_hardware, dewpoint=prefer_hardware, 
>> appTemp=prefer_hardware, rainRate=prefer_hardware, 
>> windrun=prefer_hardware, heatindex=prefer_hardware, 
>> maxSolarRad=prefer_hardware, humidex=prefer_hardware, 
>> pressure=prefer_hardware, inDewpoint=prefer_hardware, 
>> ET=prefer_hardware, altimeter=prefer_hardware, 

Re: [weewx-user] Re: weewx and aercus weatherRanger problem with updating

[Damjan Hajsek]

OK, now I see.
Weather stations sends data, like on www.wunderground.com
So it is possible to send data also to my web server and than setup weewx 
to read that data?


Dne ponedeljek, 11. september 2017 13.57.32 UTC+2 je oseba Andrew Milner 
napisala:
>
> No
>
> weewx does not receive data - it reads data.  It is not 'listening' - it 
> is controlling.
>
> If you can get a data file onto the weewx machine then weewx can be made 
> to read the file instead of a weather station - but the simple answer to 
> your question is no - unless you write a lot of code in which case anything 
> is possible!!.
>
> Most people in your situation would use an old pc or raspberry pi to run 
> weewx and get the data from the weather station, and then use weewx's ftp 
> and rsync capabilities to a) generate web pages  b) ftp web pages to a 
> webserver  c) use rsync to take backups of weewx database to offsite server 
> and would have a webserver running elsewhere to serve the weewx generated 
> web pages.
>
>
>
> On 11 September 2017 at 14:48, Damjan Hajsek  > wrote:
>
>> Is it not possible to send data from weather station to weewx? Like 
>> weather station sends data to www.wunderground.com?
>>
>> Dne ponedeljek, 11. september 2017 12.28.50 UTC+2 je oseba Andrew Milner 
>> napisala:
>>>
>>> You need to have weewx installed on a server or pc on the same local 
>>> network as the weather station for the driver to work.  Yes, the driver 
>>> talks directly to the station over wifi and from what I can read it 
>>> identifies the ip address of the station by broadcasting on the local 
>>> network.
>>>
>>> Weewx can then upload/transfer vie ftp or rsync the generated pages to 
>>> the offsite server which you have got in another location.  Weewx only 
>>> creates the pages and stores the database - it does not do the webserver 
>>> aspects of a web site.
>>>
>>>
>>>
>>> On Monday, 11 September 2017 11:57:54 UTC+3, Damjan Hajsek wrote:
>>>
 As far as I read about this HP1000 driver it connect to weather station.
 But my weather station is at home and server is on other location. I 
 thought weather station sends data to my server where weewx is installed 
 and this shows up on my weewx web pages.

 Dne ponedeljek, 11. september 2017 09.01.18 UTC+2 je oseba Damjan 
 Hajsek napisala:
>
> I checked log and it is full of this
>
> weewx[26283]: HP1000: Timed out too many times
>
>
> Sep 11 08:28:10 webserver weewx[26279]: engine: Initializing weewx 
> version 3.7.1
> Sep 11 08:28:10 webserver weewx[26279]: engine: Using Python 2.7.5 
> (default, Nov  6 2016, 00:28:07) #012[GCC 4.8.5 20150623 (Red Hat 
> 4.8.5-11)]
> Sep 11 08:28:11 webserver weewx[26279]: engine: Platform 
> Linux-3.10.0-514.26.1.el7.x86_64-x86_64-with-centos-7.3.1611-Core
> Sep 11 08:28:11 webserver weewx[26279]: engine: Locale is 'sl_SI.UTF-8'
> Sep 11 08:28:11 webserver weewx[26279]: engine: pid file is 
> /var/run/weewx.pid
> Sep 11 08:28:11 webserver weewx[26283]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> Sep 11 08:28:11 webserver weewx: Starting weewx: [  V redu  ]
> Sep 11 08:28:11 webserver weewx[26283]: engine: Loading station type 
> HP1000 (user.HP1000)
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: HP1000 Starting
> Sep 11 08:28:11 webserver systemd: Started SYSV: start and stop the weewx 
> weather system.
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Using "netifaces" to 
> determine broadcast mask
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Address Mask = 
> XXX.XXX.255.255
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Retry count = 5.00
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Socket timeout = 5.00
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Loop delay = 15.00
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Retry Wait = 5.00
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Max Retry = 3.00
> Sep 11 08:28:11 webserver weewx[26283]: engine: StdConvert target unit is 
> 0x1
> Sep 11 08:28:11 webserver weewx[26283]: wxcalculate: The following values 
> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
> rainRate=prefer_hardware, windrun=prefer_hardware, 
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
> humidex=prefer_hardware, pressure=prefer_hardware, 
> inDewpoint=prefer_hardware, ET=prefer_hardware, 
> altimeter=prefer_hardware, cloudbase=prefer_hardware
> Sep 11 08:28:11 webserver weewx[26283]: wxcalculate: The following 
> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Sep 11 08:28:11 webserver weewx[26283]: engine: Archive will use data 
> binding wx_binding
> Sep 11 08:28:11 webserver weewx[26283]: engine: Record 

Re: [weewx-user] Re: weewx and aercus weatherRanger problem with updating

[Andrew Milner]

No

weewx does not receive data - it reads data.  It is not 'listening' - it is
controlling.

If you can get a data file onto the weewx machine then weewx can be made to
read the file instead of a weather station - but the simple answer to your
question is no - unless you write a lot of code in which case anything is
possible!!.

Most people in your situation would use an old pc or raspberry pi to run
weewx and get the data from the weather station, and then use weewx's ftp
and rsync capabilities to a) generate web pages  b) ftp web pages to a
webserver  c) use rsync to take backups of weewx database to offsite server
and would have a webserver running elsewhere to serve the weewx generated
web pages.



On 11 September 2017 at 14:48, Damjan Hajsek 
wrote:

> Is it not possible to send data from weather station to weewx? Like
> weather station sends data to www.wunderground.com?
>
> Dne ponedeljek, 11. september 2017 12.28.50 UTC+2 je oseba Andrew Milner
> napisala:
>>
>> You need to have weewx installed on a server or pc on the same local
>> network as the weather station for the driver to work.  Yes, the driver
>> talks directly to the station over wifi and from what I can read it
>> identifies the ip address of the station by broadcasting on the local
>> network.
>>
>> Weewx can then upload/transfer vie ftp or rsync the generated pages to
>> the offsite server which you have got in another location.  Weewx only
>> creates the pages and stores the database - it does not do the webserver
>> aspects of a web site.
>>
>>
>>
>> On Monday, 11 September 2017 11:57:54 UTC+3, Damjan Hajsek wrote:
>>
>>> As far as I read about this HP1000 driver it connect to weather station.
>>> But my weather station is at home and server is on other location. I
>>> thought weather station sends data to my server where weewx is installed
>>> and this shows up on my weewx web pages.
>>>
>>> Dne ponedeljek, 11. september 2017 09.01.18 UTC+2 je oseba Damjan Hajsek
>>> napisala:

 I checked log and it is full of this

 weewx[26283]: HP1000: Timed out too many times


 Sep 11 08:28:10 webserver weewx[26279]: engine: Initializing weewx version 
 3.7.1
 Sep 11 08:28:10 webserver weewx[26279]: engine: Using Python 2.7.5 
 (default, Nov  6 2016, 00:28:07) #012[GCC 4.8.5 20150623 (Red Hat 
 4.8.5-11)]
 Sep 11 08:28:11 webserver weewx[26279]: engine: Platform 
 Linux-3.10.0-514.26.1.el7.x86_64-x86_64-with-centos-7.3.1611-Core
 Sep 11 08:28:11 webserver weewx[26279]: engine: Locale is 'sl_SI.UTF-8'
 Sep 11 08:28:11 webserver weewx[26279]: engine: pid file is 
 /var/run/weewx.pid
 Sep 11 08:28:11 webserver weewx[26283]: engine: Using configuration file 
 /etc/weewx/weewx.conf
 Sep 11 08:28:11 webserver weewx: Starting weewx: [  V redu  ]
 Sep 11 08:28:11 webserver weewx[26283]: engine: Loading station type 
 HP1000 (user.HP1000)
 Sep 11 08:28:11 webserver weewx[26283]: HP1000: HP1000 Starting
 Sep 11 08:28:11 webserver systemd: Started SYSV: start and stop the weewx 
 weather system.
 Sep 11 08:28:11 webserver weewx[26283]: HP1000: Using "netifaces" to 
 determine broadcast mask
 Sep 11 08:28:11 webserver weewx[26283]: HP1000: Address Mask = 
 XXX.XXX.255.255
 Sep 11 08:28:11 webserver weewx[26283]: HP1000: Retry count = 5.00
 Sep 11 08:28:11 webserver weewx[26283]: HP1000: Socket timeout = 5.00
 Sep 11 08:28:11 webserver weewx[26283]: HP1000: Loop delay = 15.00
 Sep 11 08:28:11 webserver weewx[26283]: HP1000: Retry Wait = 5.00
 Sep 11 08:28:11 webserver weewx[26283]: HP1000: Max Retry = 3.00
 Sep 11 08:28:11 webserver weewx[26283]: engine: StdConvert target unit is 
 0x1
 Sep 11 08:28:11 webserver weewx[26283]: wxcalculate: The following values 
 will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
 dewpoint=prefer_hardware, appTemp=prefer_hardware, 
 rainRate=prefer_hardware, windrun=prefer_hardware, 
 heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
 humidex=prefer_hardware, pressure=prefer_hardware, 
 inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
 cloudbase=prefer_hardware
 Sep 11 08:28:11 webserver weewx[26283]: wxcalculate: The following 
 algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
 Sep 11 08:28:11 webserver weewx[26283]: engine: Archive will use data 
 binding wx_binding
 Sep 11 08:28:11 webserver weewx[26283]: engine: Record generation will be 
 attempted in 'software'
 Sep 11 08:28:11 webserver weewx[26283]: engine: Using archive interval of 
 300 seconds (specified in weewx configuration)
 Sep 11 08:28:11 webserver weewx[26283]: engine: Using binding 'wx_binding' 
 to database 'weewx.sdb'
 Sep 11 08:28:11 webserver weewx[26283]: manager: Starting backfill of 
 daily summaries

[weewx-user] Re: weewx and aercus weatherRanger problem with updating

[Damjan Hajsek]

Is it not possible to send data from weather station to weewx? Like weather 
station sends data to www.wunderground.com?

Dne ponedeljek, 11. september 2017 12.28.50 UTC+2 je oseba Andrew Milner 
napisala:
>
> You need to have weewx installed on a server or pc on the same local 
> network as the weather station for the driver to work.  Yes, the driver 
> talks directly to the station over wifi and from what I can read it 
> identifies the ip address of the station by broadcasting on the local 
> network.
>
> Weewx can then upload/transfer vie ftp or rsync the generated pages to the 
> offsite server which you have got in another location.  Weewx only creates 
> the pages and stores the database - it does not do the webserver aspects of 
> a web site.
>
>
>
> On Monday, 11 September 2017 11:57:54 UTC+3, Damjan Hajsek wrote:
>
>> As far as I read about this HP1000 driver it connect to weather station.
>> But my weather station is at home and server is on other location. I 
>> thought weather station sends data to my server where weewx is installed 
>> and this shows up on my weewx web pages.
>>
>> Dne ponedeljek, 11. september 2017 09.01.18 UTC+2 je oseba Damjan Hajsek 
>> napisala:
>>>
>>> I checked log and it is full of this
>>>
>>> weewx[26283]: HP1000: Timed out too many times
>>>
>>>
>>> Sep 11 08:28:10 webserver weewx[26279]: engine: Initializing weewx version 
>>> 3.7.1
>>> Sep 11 08:28:10 webserver weewx[26279]: engine: Using Python 2.7.5 
>>> (default, Nov  6 2016, 00:28:07) #012[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)]
>>> Sep 11 08:28:11 webserver weewx[26279]: engine: Platform 
>>> Linux-3.10.0-514.26.1.el7.x86_64-x86_64-with-centos-7.3.1611-Core
>>> Sep 11 08:28:11 webserver weewx[26279]: engine: Locale is 'sl_SI.UTF-8'
>>> Sep 11 08:28:11 webserver weewx[26279]: engine: pid file is 
>>> /var/run/weewx.pid
>>> Sep 11 08:28:11 webserver weewx[26283]: engine: Using configuration file 
>>> /etc/weewx/weewx.conf
>>> Sep 11 08:28:11 webserver weewx: Starting weewx: [  V redu  ]
>>> Sep 11 08:28:11 webserver weewx[26283]: engine: Loading station type HP1000 
>>> (user.HP1000)
>>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: HP1000 Starting
>>> Sep 11 08:28:11 webserver systemd: Started SYSV: start and stop the weewx 
>>> weather system.
>>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Using "netifaces" to 
>>> determine broadcast mask
>>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Address Mask = 
>>> XXX.XXX.255.255
>>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Retry count = 5.00
>>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Socket timeout = 5.00
>>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Loop delay = 15.00
>>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Retry Wait = 5.00
>>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Max Retry = 3.00
>>> Sep 11 08:28:11 webserver weewx[26283]: engine: StdConvert target unit is 
>>> 0x1
>>> Sep 11 08:28:11 webserver weewx[26283]: wxcalculate: The following values 
>>> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
>>> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
>>> rainRate=prefer_hardware, windrun=prefer_hardware, 
>>> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
>>> humidex=prefer_hardware, pressure=prefer_hardware, 
>>> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
>>> cloudbase=prefer_hardware
>>> Sep 11 08:28:11 webserver weewx[26283]: wxcalculate: The following 
>>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>>> Sep 11 08:28:11 webserver weewx[26283]: engine: Archive will use data 
>>> binding wx_binding
>>> Sep 11 08:28:11 webserver weewx[26283]: engine: Record generation will be 
>>> attempted in 'software'
>>> Sep 11 08:28:11 webserver weewx[26283]: engine: Using archive interval of 
>>> 300 seconds (specified in weewx configuration)
>>> Sep 11 08:28:11 webserver weewx[26283]: engine: Using binding 'wx_binding' 
>>> to database 'weewx.sdb'
>>> Sep 11 08:28:11 webserver weewx[26283]: manager: Starting backfill of daily 
>>> summaries
>>> Sep 11 08:28:11 webserver weewx[26283]: restx: StationRegistry: 
>>> Registration not requested.
>>> Sep 11 08:28:11 webserver weewx[26283]: restx: Wunderground: Posting not 
>>> enabled.
>>> Sep 11 08:28:11 webserver weewx[26283]: restx: PWSweather: Posting not 
>>> enabled.
>>> Sep 11 08:28:11 webserver weewx[26283]: restx: CWOP: Posting not enabled.
>>> Sep 11 08:28:11 webserver weewx[26283]: restx: WOW: Posting not enabled.
>>> Sep 11 08:28:11 webserver weewx[26283]: restx: AWEKAS: Posting not enabled.
>>> Sep 11 08:28:11 webserver weewx[26283]: engine: Starting up weewx version 
>>> 3.7.1
>>> Sep 11 08:28:36 webserver weewx[26283]: HP1000: Timed out too many times
>>> Sep 11 08:29:01 webserver weewx[26283]: HP1000: Timed out too many times
>>> Sep 11 08:29:26 webserver weewx[26283]: HP1000: Timed out too many times
>>> Sep 11 08:29:51 webserver 

[weewx-user] Re: weewx and aercus weatherRanger problem with updating

[Andrew Milner]

You need to have weewx installed on a server or pc on the same local 
network as the weather station for the driver to work.  Yes, the driver 
talks directly to the station over wifi and from what I can read it 
identifies the ip address of the station by broadcasting on the local 
network.

Weewx can then upload/transfer vie ftp or rsync the generated pages to the 
offsite server which you have got in another location.  Weewx only creates 
the pages and stores the database - it does not do the webserver aspects of 
a web site.



On Monday, 11 September 2017 11:57:54 UTC+3, Damjan Hajsek wrote:

> As far as I read about this HP1000 driver it connect to weather station.
> But my weather station is at home and server is on other location. I 
> thought weather station sends data to my server where weewx is installed 
> and this shows up on my weewx web pages.
>
> Dne ponedeljek, 11. september 2017 09.01.18 UTC+2 je oseba Damjan Hajsek 
> napisala:
>>
>> I checked log and it is full of this
>>
>> weewx[26283]: HP1000: Timed out too many times
>>
>>
>> Sep 11 08:28:10 webserver weewx[26279]: engine: Initializing weewx version 
>> 3.7.1
>> Sep 11 08:28:10 webserver weewx[26279]: engine: Using Python 2.7.5 (default, 
>> Nov  6 2016, 00:28:07) #012[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)]
>> Sep 11 08:28:11 webserver weewx[26279]: engine: Platform 
>> Linux-3.10.0-514.26.1.el7.x86_64-x86_64-with-centos-7.3.1611-Core
>> Sep 11 08:28:11 webserver weewx[26279]: engine: Locale is 'sl_SI.UTF-8'
>> Sep 11 08:28:11 webserver weewx[26279]: engine: pid file is 
>> /var/run/weewx.pid
>> Sep 11 08:28:11 webserver weewx[26283]: engine: Using configuration file 
>> /etc/weewx/weewx.conf
>> Sep 11 08:28:11 webserver weewx: Starting weewx: [  V redu  ]
>> Sep 11 08:28:11 webserver weewx[26283]: engine: Loading station type HP1000 
>> (user.HP1000)
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: HP1000 Starting
>> Sep 11 08:28:11 webserver systemd: Started SYSV: start and stop the weewx 
>> weather system.
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Using "netifaces" to 
>> determine broadcast mask
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Address Mask = 
>> XXX.XXX.255.255
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Retry count = 5.00
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Socket timeout = 5.00
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Loop delay = 15.00
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Retry Wait = 5.00
>> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Max Retry = 3.00
>> Sep 11 08:28:11 webserver weewx[26283]: engine: StdConvert target unit is 0x1
>> Sep 11 08:28:11 webserver weewx[26283]: wxcalculate: The following values 
>> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
>> dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, 
>> windrun=prefer_hardware, heatindex=prefer_hardware, 
>> maxSolarRad=prefer_hardware, humidex=prefer_hardware, 
>> pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, 
>> altimeter=prefer_hardware, cloudbase=prefer_hardware
>> Sep 11 08:28:11 webserver weewx[26283]: wxcalculate: The following 
>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>> Sep 11 08:28:11 webserver weewx[26283]: engine: Archive will use data 
>> binding wx_binding
>> Sep 11 08:28:11 webserver weewx[26283]: engine: Record generation will be 
>> attempted in 'software'
>> Sep 11 08:28:11 webserver weewx[26283]: engine: Using archive interval of 
>> 300 seconds (specified in weewx configuration)
>> Sep 11 08:28:11 webserver weewx[26283]: engine: Using binding 'wx_binding' 
>> to database 'weewx.sdb'
>> Sep 11 08:28:11 webserver weewx[26283]: manager: Starting backfill of daily 
>> summaries
>> Sep 11 08:28:11 webserver weewx[26283]: restx: StationRegistry: Registration 
>> not requested.
>> Sep 11 08:28:11 webserver weewx[26283]: restx: Wunderground: Posting not 
>> enabled.
>> Sep 11 08:28:11 webserver weewx[26283]: restx: PWSweather: Posting not 
>> enabled.
>> Sep 11 08:28:11 webserver weewx[26283]: restx: CWOP: Posting not enabled.
>> Sep 11 08:28:11 webserver weewx[26283]: restx: WOW: Posting not enabled.
>> Sep 11 08:28:11 webserver weewx[26283]: restx: AWEKAS: Posting not enabled.
>> Sep 11 08:28:11 webserver weewx[26283]: engine: Starting up weewx version 
>> 3.7.1
>> Sep 11 08:28:36 webserver weewx[26283]: HP1000: Timed out too many times
>> Sep 11 08:29:01 webserver weewx[26283]: HP1000: Timed out too many times
>> Sep 11 08:29:26 webserver weewx[26283]: HP1000: Timed out too many times
>> Sep 11 08:29:51 webserver weewx[26283]: HP1000: Timed out too many times
>> Sep 11 08:32:21 webserver weewx[26283]: HP1000: Timed out too many times
>> Sep 11 08:32:46 webserver weewx[26283]: HP1000: Timed out too many times
>>
>>
>>
>> Dne nedelja, 10. september 2017 23.44.27 UTC+2 je oseba mwall napisala:
>>>
>>> 

[weewx-user] Re: weewx and aercus weatherRanger problem with updating

[Damjan Hajsek]

As far as I read about this HP1000 driver it connect to weather station.
But my weather station is at home and server is on other location. I 
thought weather station sends data to my server where weewx is installed 
and this shows up on my weewx web pages.

Dne ponedeljek, 11. september 2017 09.01.18 UTC+2 je oseba Damjan Hajsek 
napisala:
>
> I checked log and it is full of this
>
> weewx[26283]: HP1000: Timed out too many times
>
>
> Sep 11 08:28:10 webserver weewx[26279]: engine: Initializing weewx version 
> 3.7.1
> Sep 11 08:28:10 webserver weewx[26279]: engine: Using Python 2.7.5 (default, 
> Nov  6 2016, 00:28:07) #012[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)]
> Sep 11 08:28:11 webserver weewx[26279]: engine: Platform 
> Linux-3.10.0-514.26.1.el7.x86_64-x86_64-with-centos-7.3.1611-Core
> Sep 11 08:28:11 webserver weewx[26279]: engine: Locale is 'sl_SI.UTF-8'
> Sep 11 08:28:11 webserver weewx[26279]: engine: pid file is /var/run/weewx.pid
> Sep 11 08:28:11 webserver weewx[26283]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> Sep 11 08:28:11 webserver weewx: Starting weewx: [  V redu  ]
> Sep 11 08:28:11 webserver weewx[26283]: engine: Loading station type HP1000 
> (user.HP1000)
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: HP1000 Starting
> Sep 11 08:28:11 webserver systemd: Started SYSV: start and stop the weewx 
> weather system.
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Using "netifaces" to 
> determine broadcast mask
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Address Mask = XXX.XXX.255.255
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Retry count = 5.00
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Socket timeout = 5.00
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Loop delay = 15.00
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Retry Wait = 5.00
> Sep 11 08:28:11 webserver weewx[26283]: HP1000: Max Retry = 3.00
> Sep 11 08:28:11 webserver weewx[26283]: engine: StdConvert target unit is 0x1
> Sep 11 08:28:11 webserver weewx[26283]: wxcalculate: The following values 
> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
> dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, 
> windrun=prefer_hardware, heatindex=prefer_hardware, 
> maxSolarRad=prefer_hardware, humidex=prefer_hardware, 
> pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, 
> altimeter=prefer_hardware, cloudbase=prefer_hardware
> Sep 11 08:28:11 webserver weewx[26283]: wxcalculate: The following algorithms 
> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Sep 11 08:28:11 webserver weewx[26283]: engine: Archive will use data binding 
> wx_binding
> Sep 11 08:28:11 webserver weewx[26283]: engine: Record generation will be 
> attempted in 'software'
> Sep 11 08:28:11 webserver weewx[26283]: engine: Using archive interval of 300 
> seconds (specified in weewx configuration)
> Sep 11 08:28:11 webserver weewx[26283]: engine: Using binding 'wx_binding' to 
> database 'weewx.sdb'
> Sep 11 08:28:11 webserver weewx[26283]: manager: Starting backfill of daily 
> summaries
> Sep 11 08:28:11 webserver weewx[26283]: restx: StationRegistry: Registration 
> not requested.
> Sep 11 08:28:11 webserver weewx[26283]: restx: Wunderground: Posting not 
> enabled.
> Sep 11 08:28:11 webserver weewx[26283]: restx: PWSweather: Posting not 
> enabled.
> Sep 11 08:28:11 webserver weewx[26283]: restx: CWOP: Posting not enabled.
> Sep 11 08:28:11 webserver weewx[26283]: restx: WOW: Posting not enabled.
> Sep 11 08:28:11 webserver weewx[26283]: restx: AWEKAS: Posting not enabled.
> Sep 11 08:28:11 webserver weewx[26283]: engine: Starting up weewx version 
> 3.7.1
> Sep 11 08:28:36 webserver weewx[26283]: HP1000: Timed out too many times
> Sep 11 08:29:01 webserver weewx[26283]: HP1000: Timed out too many times
> Sep 11 08:29:26 webserver weewx[26283]: HP1000: Timed out too many times
> Sep 11 08:29:51 webserver weewx[26283]: HP1000: Timed out too many times
> Sep 11 08:32:21 webserver weewx[26283]: HP1000: Timed out too many times
> Sep 11 08:32:46 webserver weewx[26283]: HP1000: Timed out too many times
>
>
>
> Dne nedelja, 10. september 2017 23.44.27 UTC+2 je oseba mwall napisala:
>>
>> http://weewx.com/docs/usersguide.htm#monitoring
>>
>> 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.