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

You get a "duplicate key" error from the database, which is logged, but ignored. On Thu, Mar 28, 2019 at 7:32 PM Henry Denston wrote: > Tom, can you tell me what WeeWX will do in case it gets a package with the > same unix timestamp a package already had before? > As dateTime is a unique key

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

Tom, can you tell me what WeeWX will do in case it gets a package with the same unix timestamp a package already had before? As dateTime is a unique key I'm curious if WeeWX automatically 'filters' the data/packages or if some kind of exception is thrown (that may have an impact on system

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

That's right. On Thu, Mar 21, 2019 at 8:55 PM Henry Denston wrote: > Thank you for the clarification tom. > So I assume there are not going to be more tables added (e.g. for week, > month etc) but only the daily hi/lows, right? > > Regards, henry. > > On Friday, March 22, 2019 at 12:45:41 AM

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

Thank you for the clarification tom. So I assume there are not going to be more tables added (e.g. for week, month etc) but only the daily hi/lows, right? Regards, henry. On Friday, March 22, 2019 at 12:45:41 AM UTC+1, Tom Keffer wrote: > > The daily summaries hold one row per day. > > Each

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

On Sunday, February 24, 2019 at 11:42:22 AM UTC-8, Henry Denston wrote: > > Ok, thanks Tim, good advice! :) > > So basically there is no need to use the file from > util/init.d/weewx.debian like the DOCs advice. > So there is no downside by not using the instruction from the documentary > and

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

Yep, either way works. Using screen is like a poor mans service, so to speak. I use it in that way for other things too. I was using WeewWX with an SDR (software defined radio) with an acurite for a while and it would only work that way. On Sunday, February 24, 2019 at 1:42:22 PM UTC-6,

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

Ok, thanks Tim, good advice! :) So basically there is no need to use the file from util/init.d/weewx.debian like the DOCs advice. So there is no downside by not using the instruction from the documentary and just execute the ./bin/weewxd weewx.conf file with the weewx.conf as first parameter

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

One pro to doing it this way is you can watch the LOOP data as it is coming in. A good way to debug if nothing else. On Sunday, February 24, 2019 at 1:28:33 PM UTC-6, Tim Urberg wrote: > > One you could use screen, which allows a totally separate screen to be > running in the background. > >

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

Thank you. Another question that I would like to ask: Is there any downside just adding (executing) the sudo ./bin/weewxd weewx.conf script to the /etc/rc.locatl file? So my WeeWx installation gets started everytime on startup of my system. In the Docs this instruction is given: cd

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

Hi, Perhaps a small insight into the operation of the image generator might help. Yes it is true that at the end of each archive period (during the report generation cycle) the plots are copied to public_html (or wherever you have set them to be copied). However, it is not quite as simple as

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] Developing a WeeWX-Driver for custom weather station hardware (adding custom sensors)

Ok, after hours of trial and error I guess the lable 'aggregate_interval' is responsible for my issue. I set it to 60 (so Images/Plots will get copied when older than a minute everytime a record runs). Sorry for the spam. But can you answer me the question if there are limitations regarding

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

Thank you very much Tom. One thing I can not figure out is: In the docs it says that everytime an archive period is over (every time a new record is done) all the newly generated images (plots) get copied into the public_html folder. What I noticed for me is that this is not the case.

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

Tom, in case I would like to create my own database schema, is it enough to just remove the cloumns from the dictionary in this file: .\weewx\bin\schemas\wview.py'' ? Seems like weewx still tries to write to removed database columns when trying to save a record. Would really appreciate it in

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

WeeWX uses a blocking call when it processes LOOP packets. So, nothing happens until the hardware returns a packet. As the packet is processed, the engine looks at the timestamp. If/when the timestamp exceeds the end of an archive period (plus a slight delay, usually about 15 seconds, called the

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

Got it, thank you. I'm testing my driver right now and I noticed some strange behavior. *My driver works like this:* It queries an external MySQL database and selects all datasets (rows, and one row contains a timestamp, the value of sensor1, sensor2 etc.) that have not been processed by WeeWx

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

If you're going to all the trouble of creating a custom database schema, you can certainly make additional changes to suit your needs. Just be careful not to drop something you'll need for your reports. However, you'll find removing unused observation types does not save as much space as you

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

Yes, your strategy would work, and your names (radiation1, radiation2, and radiation3) are sensible names to give the extra sensors. You would have to change the database schema to accommodate the extra sensors. Do you have an existing database, to which you want to add the new observation

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

Hi Tom, thank you very much for your great reply! :) I do not have an existing database yet. I already read the *Adding a new type to the database *section in the Customizing Guide, however was confused as I thought this only applies in

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

Hello everyone! I'm currently developing a custom weather station (a microcontroller collecting data from custom sensors and forwarding it to a RaspberryPi). I already read the customization guide multiple times and started to develop a custom weewx-driver for my custom weather station. The