[weewx-development] Re: InfluxDB Support?

2016-08-10 Thread mwall
On Tuesday, August 9, 2016 at 11:11:47 PM UTC-4, Vince Skahan wrote: > > On Tuesday, August 9, 2016 at 7:53:35 PM UTC-7, mwall wrote: >> >> try this: >> >> https://github.com/matthewwall/weewx-influx >> >> > > Matthew - you have a lot of cool

[weewx-development] Re: candidate for Standard skin replacement

2017-01-22 Thread mwall
On Sunday, January 22, 2017 at 6:53:25 PM UTC-5, Vince Skahan wrote: > > On Sunday, January 22, 2017 at 2:19:26 PM UTC-8, mwall wrote: >> >> another update to the newskin candidate: >> >> http://lancet.mit.edu/mwall/projects/weewx-newskin/ >> > > should

[weewx-development] Re: candidate for Standard skin replacement

2017-01-22 Thread mwall
another update to the newskin candidate: http://lancet.mit.edu/mwall/projects/weewx-newskin/ changes include: - lightened up the graphic design and layout - rudimentary color scheme elements - using a much-less-ugly font (currently uses google font server, but i'm evaluating fonts to include

[weewx-development] Re: WRM300 barometer problem

2017-01-23 Thread mwall
On Monday, January 23, 2017 at 3:24:46 AM UTC-5, Agusti Rifer wrote: > > I have an Oregon WMR300 I find a problem, if the file generation interval > is set to 900 (15mins) everything works correctly, but if it is set to 5 > minutes, the barometer is only recorded every 3 records and on the weewx

[weewx-development] Re: WRM300 barometer problem

2017-01-23 Thread mwall
On Monday, January 23, 2017 at 10:25:27 AM UTC-5, Agusti Rifer wrote: > > I have placed the added file wmr300-0.18rc1, i have downloaded the > generation time to 2 minutes, but the problem persists. > Every 15 minutes makes a correct barometer and the rest all N/A. > you must replace wmr300.py

[weewx-development] Re: WRM300 barometer problem

2017-01-23 Thread mwall
fixed in 0.18rc2.py m #!/usr/bin/env python # Copyright 2015 Matthew Wall # See the file LICENSE.txt for your rights. # # Credits: # Thanks to Benji for the identification and decoding of 7 packet types # # Thanks to Eric G for posting USB captures and providing hardware for testing #

[weewx-development] Re: For your consideration: new driver called socketlogger

2017-01-30 Thread mwall
pat, please take a look at this weewx wiki page: https://github.com/weewx/weewx/wiki/observer the interceptor approach is pretty much the only option for the fine offset bridges, but there is a direct-connect approach for the fine offset wifi consoles that requires zero configuration (no

[weewx-development] Re: For your consideration: new driver called socketlogger

2017-01-30 Thread mwall
On Monday, January 30, 2017 at 9:56:05 AM UTC-5, Pat O'Brien wrote: > > Hey Matthew, your GitHub link 404s. Do you have an updated link for it? > https://github.com/matthewwall/weewx-observer

Re: [weewx-development] Re: candidate for Standard skin replacement

2017-01-29 Thread mwall
On Sunday, January 29, 2017 at 12:31:28 PM UTC-5, Tom Keffer wrote: > > So, I would propose including #errorCatcher on the top of all the > included files. > done at commit 352c5dc on the newskin branch i also add a 'map' widget - if you specify a google map apikey in skin.conf Extras, then

[weewx-development] Re: candidate for Standard skin replacement

2017-01-29 Thread mwall
here is another update to the new Standard replacement candidate: http://lancet.mit.edu/mwall/projects/weewx-newskin/ changes include: - separate page for celestial details - consolidate and simplify css - a new 'sensor status' section - modified simulator to emit battery status, voltages

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

2017-02-21 Thread mwall
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: foobot air quality monitory

2017-02-18 Thread mwall
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: What prevents archives and generated files?

2017-02-20 Thread mwall
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?

2017-02-20 Thread mwall
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

2017-02-20 Thread mwall
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: Advice on a new driver and how to make it available

2017-02-20 Thread mwall
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: Advice on a new driver and how to make it available

2017-02-20 Thread mwall
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: ./bin/weewxd weewx.conf fails with ImportError: No module named configobj

2017-02-17 Thread mwall
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: format of what genLoopPackets yields with "yield packet"

2017-02-16 Thread mwall
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,

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

2017-02-16 Thread mwall
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: What prevents archives and generated files?

2017-02-25 Thread mwall
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: What prevents archives and generated files?

2017-02-25 Thread mwall
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: continuation of discussion on wxMesh MQTT

2017-02-23 Thread mwall
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

2017-02-21 Thread mwall
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: Advice on a new driver and how to make it available

2017-02-13 Thread mwall
On Monday, February 13, 2017 at 9:28:05 PM UTC-5, susan wrote: > > Thanks for the feedback. I'll plead 'guilty' to not bumping the version > number, but I've just downloaded and expanded the file I attached above and > the line in the 'install.py' file that I think drives all this is: > >

[weewx-development] Re: Loop vs Archive

2017-02-12 Thread mwall
On Thursday, February 9, 2017 at 1:00:08 AM UTC-5, Clay Jackson wrote: > > I've got an Acurite 5n1 that I'm reading using the SDR radio driver. > Since that doesn't provide a barometer, I'm reading an APRS formatted > stream from another station I have, and grabbing the barometer from there

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

2017-02-17 Thread mwall
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: New driver for Ambient ObserverIP

2017-01-16 Thread mwall
On Monday, January 16, 2017 at 12:24:42 PM UTC-5, blown46pwr wrote: > > Does this help? > https://www.dropbox.com/s/bawuan2dfdqs5az/Alma%2C%20MI%20Current%20Weather%20Conditions.htm?dl=0 > that is the page generated by weewx. we need the page that you get when you connect to the observer.

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

2017-01-19 Thread mwall
perhaps most important items as you make your work available to others: - add a copyright line to the top of readme, install.py, and the driver .py itself: Copyright 2017 Susan email address is optional. - if you want to distribute under a license, then include a file called

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

2017-01-19 Thread mwall
On Thursday, January 19, 2017 at 11:54:26 PM UTC-5, vk3...@gmail.com wrote: > > Thanks for all of the feedback - brilliant! > Mike - I was a bit wary of claiming too much 'copyright' as I must admit > I've "borrowed" quite a bit from your "pmon" extension. > I noticed that using the

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

2017-01-19 Thread mwall
finally, and most importantly,... very nicely done!

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

2017-01-19 Thread mwall
here is a bit more unsolicited advice: - split the code into two classes: HP1000Driver and HP1000Station. the station class should do all the work - that is where the network stuff happens, and that is where the decoding happens. then you can derive a TESTStation from HP1000Station to put

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

2017-01-19 Thread mwall
On Friday, January 20, 2017 at 12:40:51 AM UTC-5, dr__bob wrote: > > So a try, except bracketing the sendto would help. With a configurable > delay? With a configurable number of retries? But I've really got to > figure out why my cable modem apparently periodically restarts. > weewx is

[weewx-development] Re: Davis Vantage Pro 2 Plus <--> Raspi 2 (weewx) <---> vserver (weewx)

2016-09-11 Thread mwall
hello Björn, you have many options. basically you install a weewx uploader extension on the pi that feeds data to your server. here are a few: MQTT - very low bandwidth, easy to integrate with many other systems InfluxDB - easy integration with grafana and other plotting tools, but not so

[weewx-development] Re: acurite bridge firmware update change

2016-09-12 Thread mwall
radar, thanks for posting the sensor outputs. these have been incorporated into the interceptor driver as of v0.10rc2. it *should* automatically detect whether the acurite bridge has older firmware that emits chaney's format or the newer firmware that puts out the wu-ish format. m

[weewx-development] Re: creating new Driver/service

2016-09-14 Thread mwall
On Wednesday, September 14, 2016 at 10:56:56 AM UTC-4, jmltech wrote: > > What would be a good example to follow for creating a new driver and > service? joe, first of all, you should decide whether to do a driver or a service. a driver is the primary source of data when you run weewx. a

Re: [weewx-development] Re: New OpsGenie Heartbeat and Alerts integration

2016-09-18 Thread mwall
On Saturday, September 17, 2016 at 10:31:41 PM UTC-4, Darryn Capes-Davis wrote: > > Thanks all for the feedback. Now have > https://github.com/dcapslock/Weewx-OpsGenie with first release > https://github.com/dcapslock/Weewx-OpsGenie/releases/download/v0.1/Weewx-OpsGenie.tar.gz. > > Will write

[weewx-development] Re: Meteostick driver for weewx

2016-10-01 Thread mwall
this is regarding the commits for meteostick driver 0.45, which included removal of the use of weewx.units.Converter() for unit conversions and the change to weewx.METRICWX from weewx.US for the unit system of LOOP packets emitted by the meteostick driver. there have been many exchanges via

Re: [weewx-development] candidate for Standard skin replacement

2016-11-14 Thread mwall
On Monday, November 14, 2016 at 6:36:48 PM UTC-5, Vince Skahan wrote: > > On Monday, November 14, 2016 at 3:31:16 PM UTC-8, mwall wrote: >> >> thanks glenn. i have added a link to weewx.com. also added a satellite >> link, analogous to the radar link. >> > &

[weewx-development] Re: Inaccurate rain recordings

2016-11-24 Thread mwall
On Thursday, November 24, 2016 at 8:58:01 PM UTC-5, vk3...@gmail.com wrote: > > I'll check a few things out when I get home but I had not realised that I > needed to provide the 'delta' rain value for each loop packet. I was > passing back the 'daily rain so far' value so I'll look into changing

[weewx-development] Re: candidate for Standard skin replacement

2016-11-12 Thread mwall
thanks to chris for his work on 'Standard Skin Version 2', as well as the feedback from glenn, alan, vince, steve, and others in that thread. hopefully we can get the momentum to make it happen this time...

[weewx-development] candidate for Standard skin replacement

2016-11-12 Thread mwall
to install and try it yourself, you can see the refactored skins here: http://lancet.mit.edu/mwall/projects/weewx-newskin known issues: - day/week/month/year are not obviously click/touch-able - timestamp for each max/min is a hover; should be click/touch-able - grey is a boring color m

Re: [weewx-development] Re: candidate for Standard skin replacement

2016-11-12 Thread mwall
forgot the .inc files in setup.py manifest fixed at 2cdea68 you'll have to re-install, or copy the .inc files manually

Re: [weewx-development] candidate for Standard skin replacement

2016-11-14 Thread mwall
thank you for the feedback! what features/functionality do you consider must-have for the standard skin? what other attributes should the new standard skin have, e.g., "easy for new users to understand", "easy to extend", "show all sensor data", "illustrate core weewx capabilities" change up

Re: [weewx-development] candidate for Standard skin replacement

2016-11-14 Thread mwall
thanks glenn. i have added a link to weewx.com. also added a satellite link, analogous to the radar link. including a forecast.inc is exactly my intent. same for a javascripty-plots.inc or heatmap.inc or anticipated-spray-days.inc or tides.inc or a nullschool.inc you should be able to just

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

2017-01-11 Thread mwall
susan, just to be clear, your driver works with the wifi console, not the bridge, right? be sure to package your driver as a weewx extension. that will make it much easier for people to install. see the customization guide for details about how to package an extension, and see the fileparse

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

2017-01-11 Thread mwall
On Wednesday, January 11, 2017 at 10:01:58 PM UTC-5, vk3...@gmail.com wrote: > > At present the code includes 'testing code' that I've used to confirm that > the various unit transformations all work, and this is controlled by a > single class boolean variable. Is it better to leave this code in

[weewx-development] Re: New driver for Ambient ObserverIP

2017-01-09 Thread mwall
On Monday, January 9, 2017 at 10:13:31 PM UTC-5, blown46pwr wrote: > > The web page is still loading as simulator. > you need to remove the 'break' line too. better yet, do some captures of the web page and post them, then i can ensure that the driver works with them. the code could be

[weewx-development] Re: New driver for Ambient ObserverIP

2017-01-09 Thread mwall
On Monday, January 9, 2017 at 9:52:15 PM UTC-5, blown46pwr wrote: > > Thanks for helping. > > Which file am I supposed to edit? I do not see "logdbg" in the config file > and it only goes to line 506? >> >> >> modify the driver file user/observerip.py. and i mistyped. it should be this:

[weewx-development] Re: New driver for Ambient ObserverIP

2017-01-09 Thread mwall
On Monday, January 9, 2017 at 9:29:55 PM UTC-5, blown46pwr wrote: > > Now the only questionable message I get is this: observerip: packet > missing UV but it is running. However the index.html file is still loading > the simulator information. > apparently the web page on your station does not

[weewx-development] Re: New driver for Ambient ObserverIP

2017-01-12 Thread mwall
On Thursday, January 12, 2017 at 10:36:54 PM UTC-5, blown46pwr wrote: > > Only thing left to figure out is the wind direction. > please connect to your weather station with a web browser using this url: http://XXX/weather.htm where XXX is the ip address of the weather station. then save the

Re: [weewx-development] Bug in uwxutils.py

2017-01-11 Thread mwall
On Wednesday, January 11, 2017 at 7:45:38 PM UTC-5, Tom Keffer wrote: > > Gack! That's been in there since the original translation from Pascal, now > 4 years ago! > there is a fair amount of unused code in uwxutils - apparently none of the functions that use uwxutils.CToF are actually used:

[weewx-development] Re: idokep.hu

2016-12-28 Thread mwall
sandor, around line 70 of idokep.py, change this: site_dict.setdefault('station_type', 'WS23XX') site_dict.setdefault('database_dict', config_dict['Databases' ][config_dict['StdArchive']['archive_database']]) to this: site_dict.setdefault('station_type',

Re: [weewx-development] Dynamic History Plots using D3

2017-01-07 Thread mwall
chris, angular (1 or 2) has way too much overhead react is more heavyweight than i would like as well i lean toward riot: http://riotjs.com/ if you're going to do dashboards right, you either need a dashboard framework that can do everything, or you need a bunch of components that play well

[weewx-development] Re: Json data for Graphing

2017-01-08 Thread mwall
darryn, as you design this json interface, i hope that we can avoid the mess that is customraw.txt and realtime.txt those two files are output by weather-display and cumulus, respectively. those are the primary mechanism for getting data from those applications to their non-native displays,

Re: [weewx-development] Re: Json data for Graphing

2017-01-08 Thread mwall
On Sunday, January 8, 2017 at 8:42:48 AM UTC-5, Tom Keffer wrote: > > Alternatively, make a "loop report engine," analogous to the present > archive report engine. Or, adapt the existing report engine so it can work > on loop data. > > This would be the more general solution. > agreed. a loop

[weewx-development] Re: New driver for Ambient ObserverIP

2017-01-10 Thread mwall
On Monday, January 9, 2017 at 10:13:31 PM UTC-5, blown46pwr wrote: > > The web page is still loading as simulator. > > Appreciate the help. Have to go to bed. Will tackle more tomorrow. Thanks! > please try pulling the latest from github (driver version 0.6), then try again. m

[weewx-development] Re: idokep.hu

2016-12-27 Thread mwall
On Tuesday, December 27, 2016 at 6:41:52 PM UTC-5, Sándor Makány wrote: > > Kedves Lóránt! > > Próbálom beüzemelni a modulod, azonban az alábbi hibába futok bele: > File "/usr/share/weewx/user/idokep.py", line 63, in __init__ > Dec 27 23:37:45 raspberrypi weewx[4830]: site_dict = >

[weewx-development] Re: candidate for Standard skin replacement

2016-12-06 Thread mwall
thanks for the feedback thus far! try the latest iteration on the new Standard skin in the newskin branch, or look at a snapshot here: http://lancet.mit.edu/mwall/projects/weewx-newskin-161104/ a few things to note: - celestial now includes daylight hours. tested for extreme polar locations

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

2017-03-23 Thread mwall
On Thursday, March 23, 2017 at 10:56:44 PM UTC-4, Thomas Carlin wrote: > > First the simple question, is there a way to structure this configuration > so that with a single loop, without statically defining the sensor name in > the code, i can get all the sensors, and their respective settings?

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

2017-03-24 Thread mwall
On Friday, March 24, 2017 at 10:42:36 AM UTC-4, Thomas Carlin wrote: > > RE: the units, how does the rest of Weewx handle those? is it done by the > driver, or the engine, or the device? I would like to stay consistent with > the rest of the software. Since this is really only accessing a

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

2017-03-24 Thread mwall
On Friday, March 24, 2017 at 8:13:57 PM UTC-4, Robert Mantel wrote: > > Bill, I have a question about the format of the MQTT message. I have my > raspberry pi running weewx, I also have that unit using mathew's mqtt > publisher to push data to my mosquitto server. I set up another virtual >

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

2017-03-24 Thread mwall
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

2017-03-15 Thread mwall
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: UPDATE: wee_debug: add support for *BSD sysinfo and load information

2017-03-20 Thread mwall
bill, thanks for posting this. we probably should refactor the platform stuff in wee_debug. instead of checking for a specific *platform*, it should check for specific *features*. for example, it can easily spit out standard platform stuff: platform.python_version() platform.platform()

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

2017-03-20 Thread mwall
On Monday, March 20, 2017 at 11:12:55 AM UTC-4, Wysiwyg wrote: > > also during the weekend I noticed that at reboot, as weewx start before my > ethernet connexion is fully setup, it seems I get a crash (the driver is > not able to connect). > > Is it possible to use this weewx.WeeWxIOError

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

2017-03-15 Thread mwall
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

Re: [weewx-development] Pressure resolution and BMP280

2017-04-01 Thread mwall
On Saturday, April 1, 2017 at 5:29:16 PM UTC-4, Craig Thom wrote: > > My goal is to use the existing SDR driver and to use a service to read the > pressure from the BMP280 and add it to the data the SDR driver is > collecting. craig, handling the units in a service is slightly different that

[weewx-development] Re: New parser for Weewx SDR

2017-04-02 Thread mwall
thank you john! added to weewx-sdr at commit 1858f84 m

[weewx-development] Re: New Parser in SDR

2017-03-09 Thread mwall
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: weewx won't start with user.wh23xx driver

2017-03-11 Thread mwall
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: Debug verbosity in V3.7

2017-03-11 Thread mwall
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

2017-03-11 Thread mwall
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: A strange way to "read a station"

2017-03-08 Thread mwall
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: Receive station data via UDP broadcast packets?

2017-08-15 Thread mwall
On Sunday, August 6, 2017 at 1:35:40 PM UTC-4, Arthur Emerson wrote: > WeatherFlow is finally about to ship their crowd-funded PWS. Their basic architecture is a > wireless network hub device, with Bluetooth BLE links to one or more "Air" and "Sky" outdoor > devices that each contain groups of

[weewx-development] Re: Receive station data via UDP broadcast packets?

2017-08-15 Thread mwall
i'm leaning toward a generic weewx-wu driver that captures (sniff or listen) tcp/ip packets that are wu protocol (http GET). that driver would work with acurite bridge, fine offset observer, and any other hardware that sends directly to weather underground. there is already a working

[weewx-development] Re: weewxd dies when weather station goes offline

2017-07-10 Thread mwall
On Friday, May 19, 2017 at 4:33:29 PM UTC-4, Frits Schouten wrote: > > Sorry, about forgetting the syslog output. I was distracted with another > computer fault. > Please find attached a section of the syslog file involving the death of > weewx. > which version of interceptor are you running?

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

2017-07-24 Thread mwall
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

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

2017-07-24 Thread mwall
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: Rainwise WS-2000 Support

2017-06-30 Thread mwall
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: Tycon TP2700WC Support (Rebranded Fine Offset WH2310)

2017-06-30 Thread mwall
On Friday, June 30, 2017 at 10:05:47 PM UTC-4, White Rabbit wrote: > > Hi I don't suppose there is any chance of this device being supported in > the near future? > a few of us have had it running reliably for some time now: https://github.com/matthewwall/weewx-wh23xx i guess i forgot to add

[weewx-development] Re: How to Output Data in JSON or Text Format?

2017-06-30 Thread mwall
On Sunday, March 19, 2017 at 4:50:34 PM UTC-4, Greg Thornwall wrote: > > > Hi, I am trying to build a separate wx monitor using a Raspberry Pi to > display more real time data.I built a DIY wx station using a Pi with > FileParse. What's the best way to implement it? I would like to get to the

[weewx-development] Re: Bloomsky support

2017-06-30 Thread mwall
gary, i use the owfs service to augment data on a few installations, but generally speaking i find it better to use a separate weewx instance for each device. the weewx-multi rc script makes it *really* easy to manage multiple weewx instances (you could do it with a bunch of systemd unit

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

2017-04-25 Thread mwall
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: new plot types and features

2017-08-19 Thread mwall
On Monday, August 7, 2017 at 8:36:10 AM UTC-4, Neil Trimboy wrote: > > Bump, sorry same question. What happened to some of the new images, in > particular the flags ? > I cant find the plotting branch referred to. > the code for flags, polar plots, arbitrary functions, and a few other odds and

[weewx-development] Re: La Crosse WS3650

2017-06-17 Thread mwall
On Saturday, June 3, 2017 at 5:47:24 AM UTC-4, Shunra Cats wrote: > > Is there a weewx driver for this weather station? I ask as our current > weather station isn't well, and this is a possible replacement. > hi shunra, there is not yet a weewx driver for the ws3650. to develop a driver we

[weewx-development] Re: La Crosse WS3650

2017-06-17 Thread mwall
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: Weewx auto start

2017-09-13 Thread mwall
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

2017-09-12 Thread mwall
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

[weewx-development] Re: Query against archive_day_outTemp

2017-11-19 Thread mwall
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: Hi Guys and Gals

2017-10-27 Thread mwall
On Friday, October 27, 2017 at 5:01:02 AM UTC-4, Putte Gustafsson wrote: > > Anyone know where I can download weewx-csv-0.10.tgz > Seems like lancet.mit.edu is down for at the moment? > must have been a temporary network issue. this is the uptime: 8:50PM up 141 days, 4:14, 1 user, load

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

2018-01-10 Thread mwall
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

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

2018-01-16 Thread mwall
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

2018-01-17 Thread mwall
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!

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

2018-01-26 Thread mwall
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

2018-01-26 Thread mwall
oops! andr3id not ray!

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

2018-01-01 Thread mwall
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] notes about grafana, mqtt, influx, and weewx

2018-09-07 Thread mwall
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: Campbell Scientific Driver.

2018-03-07 Thread mwall
On Wednesday, March 7, 2018 at 8:19:17 AM UTC-5, Steve Shuff wrote: > > I have a Campbell Scientific station which currently uploads data to > Weather-Underground and am hoping to modify the program in the station > (CR1000) to send data to my Apache server on my Raspberry Pi . This would >

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

2018-04-05 Thread mwall
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

  1   2   >