Re: [weewx-development] getting /home/weewx/bin into $PATH

a few more things: - sorry the last posting was so blunt - i've been close to the (currently uncooperative) machine the past few days, so i'm more used to talking to a computer than to people. i mean no disrespect, and i *really* appreciate all of the ideas and testing that vince, cameron,

Re: [weewx-development] getting /home/weewx/bin into $PATH

a few thoughts: 1) a setup.py install should not touch any part of the system other than the directory in which you install weewx. if you want udev rules, logrotate, rsyslog, init.d/systemd, PATH, or anything else you do it yourself. the weewx setup.py is not a typical python installation -

[weewx-development] Re: wee_debug and new user support

it might be worthwhile to add a mechanism to wee_debug that makes it trivial to post the wee_debug output to weewx user group, or to email the output to the user so that the user can then forward that to weewx user group. of course it should do the standard thing of sending output to stdout.

[weewx-development] Re: wee_debug and new user support

On Wednesday, April 14, 2021 at 2:32:35 PM UTC-4 vince wrote: > I'm noticing a growing pattern of new users posting to weewx-user along > the lines of "*I know nothing of Linux but I tried to install weewx and > it doesn't work. Will somebody please help me". * > > Think we need a "how to

[weewx-development] Re: Version 4.1.0 is ready

On Tuesday, May 26, 2020 at 10:31:55 AM UTC-4, Michael Sanphillipo wrote: > > I'm coming from 4.0 do we need to update CRT after updating WeeWX? Also > what do I select when it asks whether or not to use the original conf file? >> >> if the extension was working in 4.0, it should continue to

Re: [weewx-development] weewx v4 need for syslog daemon

On Wednesday, May 20, 2020 at 12:15:20 PM UTC-4, Vince Skahan wrote: > > > The question I guess I have is why does weewx 'install' require a working > syslog answering ? That seems wrong to me. > > This happens on installing via setup.py and installing packages. Guessing > there's a call

Re: [weewx-development] weewx v4 need for syslog daemon

here are typical use cases for weewx log output: 1) emit to system log (nominally syslog, but varies by platform) 2) emit to separate log file, one file per weewx instance. optionally do log rotation (in case it is not handled by the os). location varies by platform, but nominally /var/log

Re: [weewx-development] weewx v4 need for syslog daemon

On Tuesday, May 19, 2020 at 9:00:18 PM UTC-4, Tom Mitchell wrote: > > FWIW, I have been using phusion/baseimage > as a base for my Docker > builds and it pipes syslog to stdout by default - that works fine for me. > > That said, I think it would be

[weewx-development] Re: Meteobridge Driver

On Wednesday, May 13, 2020 at 11:13:49 PM UTC-4, Ryan Stasel wrote: > > And thinking I should just look at making a driver that will query my > Meteobridge Nano for data. I know this is possible via it's cgi-bin > directory (I already have a Hubitat app doing this). > > Something like:

Re: [weewx-development] Re: Package weewx like other python projects

On Sunday, May 10, 2020 at 2:55:10 PM UTC-4, Vince Skahan wrote: > > On Sunday, May 10, 2020 at 8:37:17 AM UTC-7, Till Maas wrote: >> >> ...which I guess could be removed and users should >> be asked to install it from their distribution or via pip >> > > A good example is trying to do a

Re: [weewx-development] Re: Package weewx like other python projects

On Sunday, May 10, 2020 at 11:37:17 AM UTC-4, Till Maas wrote: > > > >4. weewx.conf gets automatically patched by an upgrade. This is a big > >feature of weewx over the standard package upgrades, which merely ask > a > >user if they want to "merge" their old config file with an

[weewx-development] Re: weewx with multiple stations supported by a driver

ah, the "where should we do the aggregation?" problem you should consider where you want the aggregation to happen. there are at least three options: - when the data are collected - when the data are stored - when the data are reported baseline for weewx databases is one-per-driver, but as

Re: [weewx-development] Re: Package weewx like other python projects

On Tuesday, May 5, 2020 at 2:24:47 PM UTC-4, Till Maas wrote: > > > By using the standard method, it would be also very easy to package for > different distributions, since they are optimised for the default > approach. For example Fedora supports automatically generating the > python

Re: [weewx-development] Reportgenerator 'hangs' with vector plot

On Saturday, April 4, 2020 at 9:24:41 AM UTC-4, Greg Troxel wrote: > > > I wonder if people have tried postgresql. (I'm still on sqlite.) > here is a summary of how identifiers are treated in various databases: https://github.com/ontop/ontop/wiki/Case-sensitivity-for-SQL-identifiers the

Re: [weewx-development] Reportgenerator 'hangs' with vector plot

On Saturday, April 4, 2020 at 9:24:41 AM UTC-4, Greg Troxel wrote: > > Glenn McKechnie > writes: > > > It's not weewx increasing in CPU usage, it's the CPU usage for > > mariadb. Check on your Synology NAS. > > I wonder if people have tried postgresql. (I'm still on sqlite.) > greg, we

Re: [weewx-development] Re: weewx--4.0.0b16: SyntaxError: invalid syntax

the weewx-mqtt extension has been updated to version 0.21: https://github.com/matthewwall/weewx-mqtt comments in the code illustrate how to use most of the options: https://github.com/matthewwall/weewx-mqtt/blob/master/bin/user/mqtt.py this includes fixes for: * python3 compatibility * weewx4

Re: [weewx-development] How to handle mixed US and metric units in a driver?

bill, for hardware that can be configured to send data in different unit types, you have to either: a) in the driver initialization, set the hardware to the units that you want, then hope that no one changes it while the station is running or: b) in every loop packet check the unit type for

Re: [weewx-development] CRITICAL __main__: Database OperationalError exception: (1054, "Unknown column 'rain' in 'field list'")

On Saturday, March 7, 2020 at 1:32:46 PM UTC-5, Tom Keffer wrote: > > This is probably being caused by the "rainRate" calculator. The default is > to calculate 'rainRate', despite you not having it listed in > [[Calculations]]. > > What to do? > >1. We could remove rainRate from the

[weewx-development] Re: is there a driver (not extension) for http get of json data ?

On Tuesday, February 25, 2020 at 3:23:58 PM UTC-5, Vince Skahan wrote: > > Before going too far down that path, I was wondering if there a generic > '*query > a URL that returns JSON*' driver to start with ? > someone should implement that :) in fact, it would be nice if that were a base

Re: [weewx-development] My experience upgrading from Weewx 3.92 to Weewx 4.0.0b12 on a system with both Python-2.7.17 and Python-3.8.1

On Monday, February 17, 2020 at 11:53:29 PM UTC-5, John Kline wrote: > > Did you send a PR to Matthew to catch up the master copy ? > > I got the feeling Matthew wasn’t interested. I’ll try again. > not at all the case. i've been swamped with real life and real work, and trying to get

Re: [weewx-development] Supporting Columbia Weather Systems MicroServer hardware?

bill, i would suggest that you start with weewx3 and python2, and use the ip100 driver as a guide. it is trivial to update the ip100 to python3/weewx4 compatibility and by the time you are ready for that, weewx4 should be out of beta, so your upgrade path will be painless (i would do the

[weewx-development] Re: WeeWX Version 4, beta 6

it has always been best practice to not modify the system's python. however, to do that strictly would mean that you must do one of these: * use python's virtualenv * install your own version of python, completely separately from the system python * install extensions to the system python

[weewx-development] Re: WeeWX Version 4, beta 6

On Thursday, January 2, 2020 at 1:16:06 PM UTC-5, Johannes Ebner wrote: > > > Then I tried to install weewx but getting the following error: > > pi@Weewx:~/weewx-4.0.0b6 $ ./setup.py build > Traceback (most recent call last): > File "./setup.py", line 21, in > import configobj >

[weewx-development] Re: WeeWX Version 4, beta 6

On Tuesday, December 31, 2019 at 1:42:37 PM UTC-5, Vince Skahan wrote: > > On Monday, December 30, 2019 at 1:28:50 PM UTC-8, Tom Keffer wrote: >> >> ... is up. In the usual spot. >> http://weewx.com/downloads/development_versions/ >> >> > Does b6 have a minimum python version ? > as i

Re: [weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

On Saturday, December 14, 2019 at 6:57:13 PM UTC-5, Tom Keffer wrote: > > > For stations with an internal clock, it's possible the time will drift a > few seconds, maybe even archive_delay seconds ahead. We don't want to > reject records just because of that. > done at commit f0bb3259 --

Re: [weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

leon, i put the change in engine.py instead of wmr300.py - that way it will fix this problem for every driver, not just wmr300. changed at weewx-development commit e9962fe8 can you test it with the appropriate DST settings and historical data on your station? m -- You received this

Re: [weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

tom, i did a patch on the wmr300 driver, but perhaps this would be better done in the engine? rejecting packets/records that have a dateTime in the future is pretty generic doing it in the engine would prevent problems from any driver... m -- You received this message because you are

Re: [weewx-development] 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

On Saturday, December 14, 2019 at 5:20:04 PM UTC-5, Leon Shaner wrote: > > That coupled with the refusal to insert the future-data records would have > avoided loss of data. > leon, i put in a fix at commit 10d00a23. this is on the development branch. this will reject any historical record

Re: [weewx-development] weewx 4 on mac

On Monday, September 2, 2019 at 10:36:26 AM UTC-4, Tom Keffer wrote: > > But they are just strings, and mwall's comment about aligning the >> default setup.py path to /home/weewx to match other platforms is >> compelling. >> > > Except, unfortunately, on the Mac, /home is a mounted drive, so we

Re: [weewx-development] weewx 4 on mac

On Thursday, August 29, 2019 at 8:40:54 AM UTC-4, Tom Keffer wrote: > > I have no objection to something like this, but the path you've chosen > (/opt/weewx/var/run.stderr) seems pretty specific to your system. I'm not a > Mac expert. Is there a more generic location it could write to? > why

[weewx-development] Re: New alpha version

On Saturday, August 24, 2019 at 8:15:19 PM UTC-4, Vince Skahan wrote: > > > The log format surprised me a bit: > > Aug 24 16:00:18 pi4 weewx[17512]/INFO weewx.imagegenerator: Generated 28 > images for SeasonsReport in 1.46 seconds > Aug 24 16:00:18 pi4 weewx[17512]/INFO weewx.reportengine:

Re: [weewx-development] Logging by Python

we already have the log-label option. it must be specified when weewxd is invoked. for example: weewxd --log-label weewx-cmon weewxd --log-label weewx-vantage then use 'weewx-cmon' and 'weewx-vantage' in your rsyslog configuration. see the weewx-multi init.d script for an example. btw,

[weewx-development] Re: Packaging the weather34 Template (WX-HWS)

> > >> On 04 Jul 2019, at 08:56, steeple ian wrote: >> >> Matthew, >> >> Yes I did, >> >> This is from the syslog: - >> >> reportengine: Caught unrecoverable exception in generator >> 'weewx.reportengine.CopyGenerator' >> Jul 4 13:40:44 DietPi weewx[7627]: [Errno 21] Is a >>

[weewx-development] Re: Packaging the weather34 Template (WX-HWS)

On Wednesday, July 3, 2019 at 7:21:53 PM UTC-4, steeple ian wrote: > > If I want to copy_once an entire folder containing mixed type files and > sub folders, is there a syntax for that or do I have to list each wild-card > file type and sub-folder? > did you try it? no magic syntax, just what

[weewx-development] Re: Weather Link Live - Driver

On Monday, June 24, 2019 at 12:34:31 AM UTC-4, Tom wrote: > > Hello All, > I'm trying to write my own driver to locally pull data from a weather link > live box (because I couldn't find one elsewhere), and I'm struggling - this > is my first deeper exploration into python. > > I'm wondering

[weewx-development] Re: WU Forecast

On Sunday, June 23, 2019 at 10:19:23 AM UTC-4, St. B. wrote: > > I can email the update forecast.py file if you want, until Matthew shows > up with the appropriate code. > do you mind posting it in this thread? then i can merge it into the forecast codebase and get a new release out. many of

[weewx-development] Re: Packaging the weather34 Template (WX-HWS)

another thing to consider is when to write something yourself in your extension versus use what has already been written in another extension. for example, forecasting. you could easily make queries to wu or other forecast service in the weewx-wx34 extension. or you could make the weewx-wx34

[weewx-development] Re: Looking for advice on driver to target for replacement ObserverIP

On Saturday, May 18, 2019 at 1:26:23 AM UTC-4, Sean Begley wrote: > > My plan is to have my device (what I'm currently calling ObserverPi) > receive asynchronous messages from 915MHz sensors (could be extended to > other frequencies and sensors), populate a data structure and then have >

[weewx-development] Re: Looking for advice on driver to target for replacement ObserverIP

On Thursday, May 16, 2019 at 11:05:17 PM UTC-4, Sean Begley wrote: > > > I'd like to have a small, stand alone device (basically just like the > ObserverIP only not locked down to ambientweather.net and wunderground.com) > that can catch the 915MHz from a physically ideal location and send the

[weewx-development] Re: Looking for advice on driver to target for replacement ObserverIP

On Thursday, May 16, 2019 at 11:46:51 AM UTC-4, Sean Begley wrote: > > > My setup includes a RaspberryPi (or any linux machine) with an RTL-SDR > based receiver attached. Using rtl_433 I can receive all data from the > sensor units. I'm in the process of writing a python script to transform

Re: [weewx-development] Windy website API under definition ?

On Thursday, April 18, 2019 at 12:23:32 PM UTC-4, Wysiwyg wrote: > > api_key is filled by the key I get from > https://stations.windy.com/stations > it's a very long key ( ~124 characters) > yes, the api_key is ridiculously long. they must be expecting data from every atom in the universe.

Re: [weewx-development] Windy website API under definition ?

weewx-windy 0.2 only supports http GET, and station identifier is not necessary for that. set station=0 and everything should work. apparently the station identifier is only necessary for the POST protocol. the spec indicates that a station identifier is an integer.

Re: [weewx-development] Windy website API under definition ?

please try the latest (at least commit 71d72da i had to revert to using http GET instead of POST because the windy.com server won't accept what looks like a properly encoded JSON request (and they

Re: [weewx-development] Windy website API under definition ?

the weewx-windy uploader should work with python3 now please try it and let me know how it works for you sorry i cannot test it fully - windy.com is refusing my attempts to create test stations

Re: [weewx-development] Windy website API under definition ?

here is an uploader for windy: https://github.com/matthewwall/weewx-windy unfortunately it is not yet working - when i hit node.windy.com i get: Cannot GET /pws/update i'm guessing its an https thing... m

Re: [weewx-development] Re: [patch] station.py support OS uptime for FreeBSD 11

On Thursday, April 11, 2019 at 5:23:58 PM UTC-4, Jon Marnock wrote: > > Would it be better to just use something more generic like uptime(1) and > parse the output? > > pure python would be preferable to calling out to a system utility. remember that weewx runs on windows too.

Re: [weewx-development] Database access from driver

On Monday, March 25, 2019 at 11:41:13 AM UTC-4, Louis De Lange wrote: > > I am thinking about some workarounds for the genArchiveRecords() methods. > Since the historical data request does not contain the cost data it would > be useful to be able to pull the cost from the last record in the

Re: [weewx-development] Developing a WeeWX-Driver for custom weather station hardware (adding custom sensors)

On Thursday, February 21, 2019 at 1:59:25 PM UTC-5, Henry Denston wrote: > > But can you answer me the question if there are limitations regarding the > color formatting in the skin.conf? > E.g. I can not set the color '0xD17729' in the ImageGenerator Section for > the label

Re: [weewx-development] Re: Vantage LOOP2 packets (for THSW index)

On Monday, February 11, 2019 at 6:03:22 PM UTC-5, Deborah Pickett wrote: > > While I have your attention, a bikeshed-style question about schema > naming. Is there a preferred naming style for new database columns? > THSWIndex? thswIndex? thswindex? Or something else more verbose? > i like

[weewx-development] Re: Help analyzing data from LaCrosse V21WTH to build interceptor driver

hi dan, could you post a few json packets so we can see how they differ? also, if you could make a table with two columns - first column is the data string, second column is the list of ALL conditions at/near the time you saw the data string. it would be most helpful to see a range of

[weewx-development] Re: Meteostick not handling negative temperature?

changes applied at commit 043fa5a for weewx-meteostick v0.50 m

[weewx-development] Re: stuck with new driver

On Wednesday, January 23, 2019 at 2:05:58 PM UTC-5, Alan W. wrote: > > > My config file points to the driver in my home dir, and the group has been > changed to weewx from my group - I am a member of the weewx group. This > looks to my that the appropriate bit of weewx doesn't see the driver,

[weewx-development] Re: Meteostick not handling negative temperature?

pat, it is not clear what the problem is. are you saying that weewx crashes whenever there is a negative temperature from the sensors? if so, we need to see the stack trace, and the code if you have made modifications. m

[weewx-development] Re: Misol weather station

On Wednesday, December 12, 2018 at 11:10:20 PM UTC-5, Leon Lessing wrote: > > Hi guys, > > I got this working via rflink, I am using the .deb installation file. > (ubuntu 16.04) > Couple of things I found. > 1. Editing /etc/weewx/weewx.conf directly does not affect the > configuration, you

[weewx-development] Re: running weewx on a pi but unable to get data fron lw30x

this question was addressed here: https://github.com/matthewwall/weewx-interceptor/issues/39 if you still need help, please post to weewx-user and explain your configuration. when sniffing/listening to network traffic, the logical and physical configurations of your network really matter. m

[weewx-development] Re: adding hardware type to the hardware guide

On Sunday, October 7, 2018 at 8:10:19 PM UTC-4, Vince Skahan wrote: > > > do we keep track of those kind of stations someplace in weewx-land ? > there are a few places: 1) the 'drivers' section of the wiki lists all of the known drivers for various types of hardware. as of 07oct2018, there

[weewx-development] Re: adding hardware type to the hardware guide

On Sunday, October 7, 2018 at 5:09:52 PM UTC-4, Vince Skahan wrote: > > I wanted to take a crack at adding the WeatherFlow Smart Weather Station ( > http://weatherflow.com/smart-home-weather-stations/) to the hardware > guide. What's the best way to cook up a new section for that and get into

[weewx-development] notes about grafana, mqtt, influx, and weewx

vince and i have been having a discussion about how to get data from weewx into grafana. i figured there are others who could benefit from this discussion, and i'm sure there are some grafana/influx/mqtt users who could contribute. vince's application is to compare data from three different

[weewx-development] Re: White listing files with install.py?

On Monday, September 3, 2018 at 4:46:55 PM UTC-4, Pat O'Brien wrote: > > In case I've overlooked something - which is highly possible - is it > possible to install files with install.py - but also "white list" certain > files? Such that "if file exists, do not re-install (overwrite)"? > nope.

[weewx-development] Re: prerequisites for running the weewx test suite

On Thursday, April 5, 2018 at 10:40:37 PM UTC-4, Vince Skahan wrote: > > I'm fiddling with trying 'make test' to run the test suite, and all the > mysql tests fail ala: > > "BadPasswordError: (1045, "Access denied for user 'weewx1'@'localhost' > (using password: YES)") > > > I added

Re: [weewx-development] MacOS (10.11.6) wview user converting to weewx, python errors

On Saturday, March 3, 2018 at 6:43:19 PM UTC-5, Tom Keffer wrote: > > Nice to have a Mac expert around! Perhaps in a quiet moment you can tell > me how to get the system logger to work on High Sierra. > yes, please, i would like some of that magic too!

Re: [weewx-development] MacOS (10.11.6) wview user converting to weewx, python errors

this looks like a problem with the python installation, not with the current directory. you do not have to be in the /Users/Shared/weewx directory to run weewxd. On Sunday, March 4, 2018 at 12:04:24 PM UTC-5, Tom Keffer wrote: > > The problem is that you are in the wrong subdirectory and, as a

Re: [weewx-development] MacOS (10.11.6) wview user converting to weewx, python errors

> > > > On Mon, Mar 5, 2018 at 5:13 AM, kdbarto > wrote: > >> >> Pip wasn’t installed and failed to self-install. So i reverted to >> easy_install. >> > this is why the macos installation guide says to use easy_install, not pip. python installation and dependencies are

[weewx-development] Re: [RFC] Support for the Oregon Scientific WMR89

oops! andr3id not ray!

[weewx-development] Re: [RFC] Support for the Oregon Scientific WMR89

On Friday, January 26, 2018 at 4:34:07 PM UTC-5, andr3id wrote: > > It worked with a newer version of Python and a newer pyserial. I've build > python 3.6.4 on the RPi and then installed pyserial through the built-in > pip tool. To test the weewx driver I have to fix a newer Python 2 on RPi >

[weewx-development] Re: [RFC] Support for the Oregon Scientific WMR89

On Wednesday, January 17, 2018 at 5:32:07 PM UTC-5, andr3id wrote: > > Anyway, with the information found on wxforum > , I've managed to modify > a linux kernel driver to make the WMR89 show up as a USB serial interface > in Linux. > welcome!

Re: [weewx-development] NMEA Support - Raspberry PI

On Tuesday, January 16, 2018 at 9:25:44 AM UTC-5, Thomas Boström wrote: > > Are there any documentation how to change the station/driver to the Airmar > driver, I am running the Simulator for the moment. > (I think I have solved my problem with the weewx.drivers) > this has all the gory details:

[weewx-development] Re: [RFC] Support for the Oregon Scientific WMR89

ray, 'marunio' over at wxforum figured out that the baud rate on the wmr89 is non-standard. that is why no one has been able to make any sense of the comms. now that we know the baud rate (128000) it should be pretty easy to make a weewx driver for the wmr89. it looks like the

[weewx-development] Re: [RFC] Support for the Oregon Scientific WMR89

ray, nice work! you might want to do this as a standalone driver instead of try to merge the functionality into the wmr9x8 driver. it probably means quite a bit of code duplication, at least for the first implementation. but there is already a lot of duplication between the wmr drivers

[weewx-development] Re: Query against archive_day_outTemp

On Tuesday, November 14, 2017 at 10:20:16 AM UTC-5, Clay Jackson wrote: > > My “day job” is supporting Quest Foglight (a database monitoring tool) – > just for fun, I pointed it at the weewx database. > clay, is there any chance you could point that profiling tool at a weewx instance that is

[weewx-development] Re: Weewx auto start

On Wednesday, September 13, 2017 at 9:31:57 AM UTC-4, mjsw...@gmail.com wrote: > > OK, assuming I am not as skilled as a programmer as you and that I am > reasonably skilled enough to set up weewx, Allstar, or Xastir and manage > cron jobs, how would I go about getting info from the log?

[weewx-development] Re: Weewx auto start

On Tuesday, September 12, 2017 at 5:08:43 PM UTC-4, Mike Swiatkowski wrote: > > Has anyone had issues with weewx not starting on bootup? I tried > update-rc.d /etc/init.d/weewx defaults 98. It does not seem to autostart > on reboot. I am running debian 8 x64. What is the proper procedure to

Re: [weewx-development] Re: Radiation and ET - Sunshine Duration

On Monday, July 24, 2017 at 5:52:14 PM UTC-4, Clay Jackson wrote: > > Thanks, Matt – I was more interested in how to get the “sunshine > duration”, which would be the number of seconds during the day where the > radiation was greater than 120W/m^2. I suppose I could do that as a > service

[weewx-development] Re: Remote sensor collection - files or RPC or.....

clay, if you've got a tcp/ip network between the data collection stations, then there are quite a few options: a) run an instance of emoncms, use the weewx-emoncms extension to send data from weewx to emoncms. create dashboards in emoncms. b) run a MQTT broker, use the weewx-mqtt extension

[weewx-development] Re: Rainwise WS-2000 Support

On Monday, June 26, 2017 at 10:32:02 PM UTC-4, Harry Bruce wrote: > > Has anyone worked on supporting the older Rainwise WS-2000 Computer > Interface? > is that a serial interface? > Is there a guide for developing new Device Drivers? I'm planning on > trying to start with the CC-3000

[weewx-development] Re: La Crosse WS3650

shunra, it looks like there is some code available that talks to the ws3600 series of weather stations: https://sourceforge.net/projects/open3600/ so that could be a starting point for a ws3600 driver for weewx fwiw, the ws3600 was the followup to the ws2300 (more memory, touch screen, cup

[weewx-development] Re: retrieving total rain in a custom service

On Tuesday, April 25, 2017 at 4:13:56 PM UTC-4, Daniel Jönsson wrote: > It seems to me that 'rainTotal' is the same as rain in that table. > the fine offset hardware reports an integer counter, which is the number of bucket tips. the fousb driver converts that counter to 'rainTotal' the

[weewx-development] Re: Modifying the database schema using variables from weewx.config

On Friday, March 24, 2017 at 4:38:00 PM UTC-4, Thomas Carlin wrote: > > One thing that is worth mentioning, I don't intend to use this to replace > the weatherstation driver, in my case Vantage. I have been following the > code examples listed in Adding a second datasource, >

[weewx-development] Re: continuation of discussion on wxMesh MQTT

On Sunday, March 12, 2017 at 6:49:17 AM UTC-4, Wysiwyg wrote: > > This has no meaning and I guess it would be better to filter. > also it may happens that some mqtt topics may be not for weewx but for > other personnal use. > > I would like to check if a key is existing in weewx schema before put

[weewx-development] Re: A strange way to "read a station"

On Wednesday, March 15, 2017 at 5:24:23 PM UTC-4, Ian Boag wrote: > > I think I have it . > > In simulator.py . getLoopPackets > > for obs_type in self.observations: > _packet[obs_type]=self.observations ... blah .. blah > > Hijacking this looks like it should work . ? > just use

[weewx-development] Re: Debug verbosity in V3.7

On Saturday, March 11, 2017 at 10:08:44 PM UTC-5, Darryn Capes-Davis wrote: > > Yes, specifically it is Wunderground code. Introduce in Nov for caching > rapid fire values. I suppose this code would have well helped for > developing, but too verbose in my opinion for debug=1. > fixed at commit

[weewx-development] Re: Debug verbosity in V3.7

darryn, could you be more specific about which log messages? for restful services, doing debug=2 should show the url/data before actually uploading, so that you can debug network issues from the client point of view. there is also log_failure and log_success that should apply to each restful

[weewx-development] Re: weewx won't start with user.wh23xx driver

On Saturday, March 11, 2017 at 6:30:47 PM UTC-5, Thom Rogers wrote: > > Hi Matt, > > I found the usb repo, but not sure what I need to download from there (and > where to put it ) in order to use with my wh23xx driver. > thom, the usb branch includes the wh23xx driver. the lower-level code is

[weewx-development] Re: New Parser in SDR

On Thursday, March 9, 2017 at 8:01:26 PM UTC-5, Clay Jackson wrote: > > I just picked up an Acurite 275M outdoor temp/humidity sensor that has an > external probe – I want to set up at least one, and maybe 2 or 3 for Soil > Temp recorders. RTL_433 will read them and produce this – all I need

[weewx-development] Re: A strange way to "read a station"

On Tuesday, March 7, 2017 at 11:36:53 PM UTC-5, Ian Boag wrote: > > Not sure where to start - the obvious place is the fousb.py driver and > have it go to a file with the downloaded query in it (instead of talking to > the station). I can read the numbers etc. I assume that fousb.py just >

[weewx-development] Re: What prevents archives and generated files?

On Saturday, February 25, 2017 at 1:50:23 PM UTC-5, crich...@gmail.com wrote: > > Thanks. I'll get to cleaning up the code later, but on the time thing... > here's the code and values that are part of rec_time being sent in. > It sure looks to me that int(time.time()+0.5) gives local time. Of

[weewx-development] Re: What prevents archives and generated files?

On Saturday, February 25, 2017 at 11:07:01 AM UTC-5, crich...@gmail.com wrote: > > I tried this again with more messaging enabled, and I think the problem is > that the times in the records have to be local times, not something from > the past, and not actually UTC. Both those cases result in

[weewx-development] Re: continuation of discussion on wxMesh MQTT

On Thursday, February 23, 2017 at 7:59:13 AM UTC-5, Bill Morrow wrote: > > I discovered a possible problem with this approach working well with other > parts of weewx. Last night I was attempting to get the Realtime Gauge-Data ( > https://github.com/gjr80/weewx-realtime_gauge-data) extension

[weewx-development] Re: weewx won't start with user.wh23xx driver

On Tuesday, February 21, 2017 at 10:49:35 AM UTC-5, Thom Rogers wrote: > > I'm confused as to why you are talking about an acurite driver. I'm > interfacing to an Excelvan WH2310 which I believe is a Fine Offset station, > not Acurite. > i mistyped. i meant the fine offset wh23xx.

[weewx-development] Re: continuation of discussion on wxMesh MQTT

bill, you might want a separate thread in the wxMesh driver - one thread that receives mqtt data and puts it on a queue, then the main thread that runs genLoopPackets and picks data off the queue as soon as they arrive. see the ws3000 driver for a pretty simple example implementation. it has

[weewx-development] Re: Advice on a new driver and how to make it available

On Sunday, February 12, 2017 at 10:26:35 PM UTC-5, vk3...@gmail.com wrote: > > Just noticed that the beta of V3.7.0 is available. > In the release notes from Tom he noted that any missing 'windGustDir' is > to be determined by Weewx with this version. > Please note that the last version of my

[weewx-development] Re: Advice on a new driver and how to make it available

On Monday, February 20, 2017 at 9:45:55 PM UTC-5, vk3...@gmail.com wrote: > > I think I'm nearly ready to release this but I'd still like a comment on > hwo to best handle the new version (V3.7.0) > susan, you should not have to do anything special for weewx 3.7.0 - there are no changes in 3.7

[weewx-development] Re: What prevents archives and generated files?

On Monday, February 20, 2017 at 8:27:07 PM UTC-5, crich...@gmail.com wrote: > > Here's the comment from the top of the file: Derived (shamelessly stolen) > from Matthew Wall's Observer driver by Chris Richmond. > Meaning the basic structure is still there, just the additions to deal > with my

[weewx-development] Re: What prevents archives and generated files?

On Monday, February 20, 2017 at 2:27:55 PM UTC-5, crich...@gmail.com wrote: > > I'm making progress with my driver, and I'm making LOOPs in weewk now, but > the archive's and generated files aren't happening. > There aren't any errors anywhere, just no DB updates, pictures, or web > pages. The

[weewx-development] Re: weewx won't start with user.wh23xx driver

On Sunday, February 19, 2017 at 1:35:20 AM UTC-5, Thom Rogers wrote: > > > Any advice on how to overcome the "No backend available" error? > thom, you have to install a usb 'backend' that is supported by pyusb. three examples are libusb, libusb1, or openusb. libusb1 is probably your best

[weewx-development] Re: foobot air quality monitory

On Saturday, February 18, 2017 at 9:18:07 PM UTC-5, Inoukb wrote: > > Hello, Inouk from Foobot here. Available to help if necessary. > > Not sure why you guys don't use our API though: > http://api.foobot.io/apidoc/index.html > hello inouk! is it possible to configure the foobot to send to a

[weewx-development] Re: ./bin/weewxd weewx.conf fails with ImportError: No module named configobj

On Friday, February 17, 2017 at 2:22:44 PM UTC-5, Thom Rogers wrote: > > Not sure what this tells us, but here's the output of those commands: > trying to figure out whether you have multiple python installations did you set PYTHONPATH? what happens when you run with no PYTHONPATH set?

[weewx-development] Re: ./bin/weewxd weewx.conf fails with ImportError: No module named configobj

On Friday, February 17, 2017 at 8:24:19 AM UTC-5, Thom Rogers wrote: > > No. No luck on that either > > > >>> import configobj > > Traceback (most recent call last): > > File "", line 1, in > > ImportError: No module named configobj > >> >> which python do you get when you invoke the shell?

[weewx-development] Re: ./bin/weewxd weewx.conf fails with ImportError: No module named configobj

On Thursday, February 16, 2017 at 9:50:28 PM UTC-5, Thom Rogers wrote: > > Even though I've successfully installed configobj via the pip install > configobj command, when I try to start weewx it errors with "No module > named configobj" > can you import configobj at a python prompt?

[weewx-development] Re: format of what genLoopPackets yields with "yield packet"

On Thursday, February 16, 2017 at 10:36:10 PM UTC-5, crich...@gmail.com wrote: > > OK, I think I've got it. One more thing. Is there a point to including > pairs where the value is zero, or is that assumed when the data gets rolled > up for archive or plotting? > Thx, Chris >> >> >>> chris,

  1   2   >