[weewx-user] Re: WMR300 driver update

A lot of thank's Cameron. I will test it in some minutes. I have some log of 3.8.2 standard driver version when stops receiving data: Sep 25 06:25:07 MeteoElche weewx[1512]: wmr300: read: e.errno=None e.strerror=None e.message=could not detach kernel driver from interface 0: No hay datos dispon

[weewx-user] Divide by Zero error generating graphs

Hi all, New weewx user here using a home brew weather station based on Arduino's and nRF24L01+ radios. I wrote my own driver to accept packets on the nRF24L01 attached to the RPi and weewx is happily accepting my LOOP packets and producing reports every archiving period. I've also managed to imp

[weewx-user] Re: WMR300 driver update

Thank you very much Cameron, I will try to test it as soon as possible. El lunes, 24 de septiembre de 2018, 3:04:37 (UTC+2), Cameron D escribió: > > This time with attachment > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from

Re: [weewx-user] Date error on some historic data graphs using Belchertown skin

I can concur with the error, timezone here is NZ Standard Time (+12) Have a look at my Monthly graph - sorry can't get a screen grab with the cursor in place to show that the graphs are ahead of time. Maybe it's forecasting :) http://41south.net.nz/graphs/ Colin On Tue, Sep 25, 2018 at 3:34 PM

Re: [weewx-user] Date error on some historic data graphs using Belchertown skin

I suspect the issue will be related to how highcharts is interpreting timestamps in the plot data rather then the wrong data being in the plot data files. I have seen something like this before but it was related to the timezone of the client computer viewing the plots, would seem that is not th

Re: [weewx-user] Date error on some historic data graphs using Belchertown skin

OK. More info. I checked Pat O'Brien's website and also Juan Antonio Mosquera's website. Neither shows the date offset that my website shows. So, It looks like I've got a problem with my implementation or my database. But, since the NOAA reports for monthly min and max seem to be correct, that

Re: [weewx-user] Date error on some historic data graphs using Belchertown skin

Ah, yes. Gary is correct. It appears that only rainfall is aggregated (two hour aggregates for the Monthly plot). The others seem to be Min or Max at a discrete time. Phil On Monday, September 24, 2018 at 10:19:34 PM UTC-4, Philip Kutzenco wrote: > > Thomas, > > I think you are correct about ag

[weewx-user] Re: Fine Offset WH25: barometer values are received, but not shown in graphic

Hi, Could be any one of a number of things. Have you worked through the steps in the sdr driver readme ? Might help to see some of the output from those steps along with a sanitised copy of weewx.conf. You can use wee_debug

Re: [weewx-user] Date error on some historic data graphs using Belchertown skin

Not saying what is right or wrong but the rain data provided by the highcharts extension is an aggregate sum over an hour or a day, depending on the time period of the plot. That may be why rain is behaving differently to other obs. Gary On Tuesday, 25 September 2018 11:19:10 UTC+10, Thomas Ke

[weewx-user] CloudMQTT & Belchertown Skin

Is anyone using CloudMQTT broker with the Belchertown skin? I have data published to the broker, but will not connect via SSL/TLS Websockets. I can connect via TLS websockets using a different client. -- You received this message because you are subscribed to the Google Groups "weewx-user" gro

Re: [weewx-user] Date error on some historic data graphs using Belchertown skin

You're probably right. Plus, I gather that you are working with aggregated plots, not the raw data? It was just a thought... -tk On Mon, Sep 24, 2018 at 6:11 PM Philip Kutzenco wrote: > If that's so, wouldn't rainfall also exhibit the offset? > > Even if Thomas is correct (and something about

Re: [weewx-user] Date error on some historic data graphs using Belchertown skin

If that's so, wouldn't rainfall also exhibit the offset? Even if Thomas is correct (and something about rainfall calculation keeps it from being offset), the call out numbers (showing data values and date) you see when you move the cursor across the graph are wrong because of the date offset. S

Re: [weewx-user] Re: No lines on plot_type = line

Hmmm, I did the calculation by hand for the period you were using software record generation, and got values of about 0.0007 inches per archive interval, or about 0.008 in/hr --- Similar to what the VP2 was returning. Would you be willing to try software ET calculations again, this time using inst

Re: [weewx-user] Date error on some historic data graphs using Belchertown skin

In WeeWX, records are timestamped with the *end* of the record. Perhaps Highcharts uses the beginning? -tk On Mon, Sep 24, 2018 at 10:28 AM Philip Kutzenco wrote: > I notice that, for me, some of the historic data graphs supplied with the > Belchertown skin are off by one day. In particular, if

[weewx-user] Re: uninstall csv

I don't find a file in /home/weewx/bin/user and /home/weewx/bin/user/installer. just I find a file in /home/csv-0.10 I delete these file and change [csv] in weewx.conf but not process_service because there is nothink. but is good i have not generate file csv after reload weewx. thank you -- Y

[weewx-user] Fine Offset WH25: barometer values are received, but not shown in graphic

weewx 3.8.2 rtl_433 18.05 I can see that barometer readings from the WH25 are received via rtl_433 directly and via weewx syslog messages, but the values do not get plotted in the barometer graphs. After 24h of weewx collecting data, all I get is an empty barometer graph: [image: http://rpi3/_m

Re: [weewx-user] Re: No lines on plot_type = line

I had it set "ET = software" from around 10am to 11am. (ignore 8:36am, I had the console unplugged) 1537740900|2018-09-23 18:15:00|36.9||0.0||0.0 1537741200|2018-09-23 18:20:00|36.8|88.0|0.0|7.0|0.0 1537741500|2018-09-23 18:25:00|36.7|88.0|0.0|9.0|0.0 1537741800|2018-09-23 18:30:00|36.7|88.0|0.0|1

[weewx-user] Date error on some historic data graphs using Belchertown skin

I notice that, for me, some of the historic data graphs supplied with the Belchertown skin are off by one day. In particular, if you go to the "Graphs" page and select either "Month" or "Year", the temperature graph data are labeled as being one day beyond what they should be. For instance at t

[weewx-user] Re: Bootstrap gauge scales - how to change?

Ok, I've found the guage section of skin.conf (Bootstrap) and am playing with values. Thanks to the post by Buzz Z. Bob -- 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 ema

[weewx-user] Re: Problems updating my Driver

Hi Mike Have you working drivers that work GrovePi board to Weewx? I have hardware from switchdoc and want to try Weewx. -- 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 em

Re: [weewx-user] Re: No lines on plot_type = line

What we need to see is the archive database. Using sqlite3, something like *sqlite3 /home/weewx/archive/weewx.sdb* # Adjust as necessary sqlite> *select dateTime, datetime(dateTime,'unixepoch','localtime'), outTemp, outHumidity, windSpeed, radiation, ET from archive where dateTime>1537675200 limi

Re: [weewx-user] Re: No lines on plot_type = line

Here's some lines from archive_day_et with hardware and then after software was enabled: ET = prefer_hardware 1537675200|0.0|1537740900|0.0|1537740900|0.0|9|0.0|9 1537761600|0.0|1537788900|0.006|1537794000|0.006|25|0.006|25 ET = software 1537675200|0.0|1537740900|0.0|1537740900|0.0|9|0.0|9 153

[weewx-user] Re: Belchertown Skin MQTT Updates Pressure Reading

Hi I changed this in the index.html template file. should this be included in the next release? Should fix the metric code also. if ( data.hasOwnProperty("altimeter_inHg") ) { jQuery(".wx-barometer-value").text( parseFloat( data["barometer_inHg"] ).toFixed(2) + " $unit.label.pressure" ); // Ba

Re: [weewx-user] Rain Rate record 15358.8 mm/hr on 14 May 05:48

Hello, Glenn See the Wiki entry Clean up old "bad" data and see if that doesn't answer your question. If not, come back and we'll dig in deeper. -tk On Mon, Sep 24, 2018 at 12:38 AM Glenn F wrote: > It has probably been asked, an

[weewx-user] Belchertown Skin MQTT Updates Pressure Reading

Hi All, I have installed the Belchertown skin and have the real time updates working but I have notices the pressure reading on the static page is the barometer_inHg and the MQTT uses the altimeter_inHg. When the pages loads I see the altitude adjusted pressure then it drops to the altimeter

[weewx-user] Alarm example working, but how do I extend it?

Hi good people of weewx. I have had a problem but after good peoples help in here, it is working like a charm. And so many good tips and tricks to take advantage of. But. I have the alarm example up and running (except I tried doing an expression with a single equation sign, but I think python

Re: [weewx-user] Re: Belchertown extension + WMR300 stop data received.

Hello Leo, You might have similar symptoms, but I suspect a different cause. The modified driver I posted earlier today should fix some problems with random stopping of data collection. The issue in this thread relates specifically to a problem when running belchertown skin, but not otherwise.

[weewx-user] Rain Rate record 15358.8 mm/hr on 14 May 05:48

It has probably been asked, and if so point me in the direction please. I'd love to delete this record, I never built an ark nor got flooded out, so would love this to show the actual , real, value.. Running a FineOffsetUSB system . Glenn.. -- You received this message because you are

Re: [weewx-user] Re: Belchertown extension + WMR300 stop data received.

I have the same problem on my wmr300 and need to reload my weewx every hour to have a working setup. Den 2018-09-22 kl. 17:15, skrev Cameron D: Hi, I can interpret the log, but I do not understand what it has to do with the extension being active or not. Every 20 seconds you write an "a6" pac

Re: [weewx-user] Re: Belchertown extension + WMR300 stop data received.

That sequence *was* what I initially was thinking, however I suspect this might be a problem that my changes do not fix, so it might not matter what order it is done in, especially if there might be hours waiting for the problem to recur. If my changes do fix the problem, then all well and good.