No, it is not a problem for me. I just noted that there is difference, if
anyone felt like looking into it..
--
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
The WMR200 is a bit special as it is using channel 1 for the original
outdoor sensor. The good thing about this is that if the original outdoor
sensor is broken then a "standard" extra sensor set on channel 1 can be
used, but this is also why the change was not correctly made.
On e.g. WMR928 th
Doesn't the WMR928 use a different driver - wmr9x8? There are different
four different drivers for different WMR models according to the hardware
guide.
On Saturday, 7 January 2017 14:50:00 UTC+2, Per Edström wrote:
> The WMR200 is a bit special as it is using channel 1 for the original
> o
Because I have the following Oregon-stations running:
1x WMR100
2x WMR200
1x WMR928
I need to have some consistency between them i.e. that the numbering of the
extraSensors are related to the channel used or else fault finding,
changing of the web templates etc will be more difficult. The extraS
Yes, different drivers for the WMR200 and WMR9x8 as there is a
HW-difference but they need to handle the extraSensors in the same way i.e.
having the channel number as numbering of the extraTemp.
As I described it earlier: it should be read as "extraTemp[channel]" and
not as the sequence of ext
Did you see Matthew's comment earlier in the thread regarding the sensor
mapping changes he has implemented?? The sensor mapping allows you to map
the station's fields to whatever database fields you desire - so you can
therefore have consistency within your databases and templates whilst
havi
On Saturday, January 7, 2017 at 1:57:33 AM UTC-5, Jamie Borget wrote:
>
> I noticed today that my acurite bridge is picking up my neighbors acurite
> tower sensor. I'm using the weewx interceptor plugin using sniff mode with
> the pcap filter. I can't figure out how to disable their sensor. I'm
Hi Thomas, Thanks for the reply. My interest in ET is solely for irrigation
purposes. My Rachio system uses ET to determine how much water the
sun/wind siphoned off. Rachio calculates this on it's own in in/day but I
like to have a sanity check. Looks like the unit of measurement now is
mm? If
The unit of measurement for ET depends on your database. If you use the
default (US), and it looks like you are, then it will be in inches.
-tk
On Sat, Jan 7, 2017 at 5:56 AM, John Hill wrote:
> Hi Thomas, Thanks for the reply. My interest in ET is solely for
> irrigation purposes. My Rachio s
I still don't see the reason for changing the code in wmr200.py
Note that "outTemp" on WMR200 is actually "extraTemp1" as it is on channel
1. The standard mapping should be that the first extra sensor is extraTemp2
as it is on channel 2.
--
You received this message because you are subscribed
The code in wmr200.py should be changed so the original outdoor sensor
could be swapped out for another sensor, as stated in my code-example
earlier.
Although I don't think many WMR200-users have a need to swap the outdoor
sensor or use 10 extra sensors, there might be someone that need that
f
The weewx coluimn 'extraTemp1' signifies by its name that it is an output
from a 'extra' temperature sensor - it may be on channel 1, channel 99, or
channel A B or C depending on the specific hardware which has created the
record. Weewx only builds in 5 'extra' columns which people may use as
Per - this is being written 'tongue-in-cheek' - but you could always change
the database schema and call the columns extraTempA, extraTempB, extraTempC
. change your templates to match . and map the driver output fields
accordingly into the now renamed database columns . Not a c
First time my rain gauge has had rain and on the Current page the rain rate
displays a correct number but in %: in/hr 85%. I've looked through the
skin.conf and index.htm.tmpl but cannot spot an error that might cause
this. Any pointers about where else I should look, or do I misunderstand
this
On Saturday, January 7, 2017 at 7:50:00 AM UTC-5, Per Edström wrote:
>
> With the implementation now in place a new sensor on channel 1 on WMR200
> will be "extraTemp0" or channel 1 is left unsuable. Was that the intention?
>
the change was made based on this report:
https://github.com/weewx/wee
On Saturday, January 7, 2017 at 9:37:07 AM UTC-5, Dan'l B wrote:
>
> First time my rain gauge has had rain and on the Current page the rain
> rate displays a correct number but in %: in/hr 85%. I've looked through the
> skin.conf and index.htm.tmpl but cannot spot an error that might cause
> t
My bad, I didn't look carefully enough at the columns and see that the 6age
is of chance of precipitation. Apologies!
On Saturday, January 7, 2017 at 9:37:07 AM UTC-5, Dan'l B wrote:
>
> First time my rain gauge has had rain and on the Current page the rain
> rate displays a correct number but i
I missed that little detail, the wiki shows separate lines, I just was so
happy I managed to get the sensor data into a file
I now have a two line txt file and both readings are picked up by the
fileparse driver.
Thanks.
On Friday, January 6, 2017 at 9:51:13 PM UTC-8, Andrew Milner
Thanks for your reply mwall, I've tried setting it up as you've specified
and I couldn't ever get it to work. Below is what I have in my config:
[Interceptor]
driver = user.interceptor
device_type = acurite-bridge
mode = sniff
iface = eth1
pcap_filter = src 192.168.0.41 and d
On Saturday, January 7, 2017 at 12:11:58 PM UTC-5, Jamie Borget wrote:
>
> I can even see a raw packet that starts with temperature.0002651.*
>
> raw packet: {'temperature.2651.24C86E077FD8': 13.5,
> 'usUnits.2651.24C86E077FD8': 1, 'dateTime.2651.24C86E077FD8':
> 1483808097, 'baromete
Thanks so much, what noob mistake. I appreciate your quick reply!
On Saturday, January 7, 2017 at 10:23:39 AM UTC-7, mwall wrote:
>
> On Saturday, January 7, 2017 at 12:11:58 PM UTC-5, Jamie Borget wrote:
>>
>> I can even see a raw packet that starts with temperature.0002651.*
>>
>> raw packet: {
per,
here are the (proposed) default maps for the wmr100, wmr200, and wmr9x8
drivers:
wmr100:
'inTemp': 'temperature_0',
'outTemp': 'temperature_1',
'extraTemp1': 'temperature_2',
'extraTemp2': 'temperature_3',
'extraTemp3': 'temperature_4',
'extr
1. I don't see how extraTemp4-7 can be used in WMR88 or WMR928 as they only
support 3 extra sensors. The WMR200 need extraTemp8-9 as it supports 9
extra sensors. However, as the original outdoor sensor is on channel 1 and
can be replaced by an external sensor (maybe the user only wants to use
T
Why don't WMR200 have:
'extraBatteryStatus1': 'battery_status_2', #Channel 2
'extraBatteryStatus2': 'battery_status_3',
'extraBatteryStatus3': 'battery_status_4',
'extraBatteryStatus4': 'battery_status_5',
'extraBatteryStatus5': 'battery_status_6',
'
I have looked through the code and I can't find the collection of battery
status from extra sensors anywhere. Looking on the WMR200-protocol I guess
there is no clear place where the information is available:
http://www.bashewa.com/wmr200-protocol.php
Now, enabling the debug reveals that my WMR2
I agree but but i have one weather station only, unfortunately i don't have
one for dev only and my crashy config connected to the weather station is
still in prod because this config replace a dead WRM200 running on cumulus
since 2014 and data must still flow :)
But if the new config is good no
I did change one thing at a time with 24h test on the new config starting
with basic config with the simulator to the full config. that's a long and
tedious process that took me almost a week. That's partially why i can't
stop my actual config to report in the database and on internet.
Next time
Hi,
I have a similar problem with weewx 3.6.2 and forecast 3.2.9 but on
sofaskin
the single table is one size bigger than normal on my other config with
weewx 3.2.6 and forecast 3.08 and sofaskin.
maybe something has changed in the forecast_table.css ???
On Saturday, January 7, 2017 at 6:23:
Per - one thing I think you are missing is that the weewx database schema
and available column names is device independent and, for most consoles,
provides far more available columns than the console provides. The schema
does not change with the station type - but the way the columns are used
I believe there is also forecast-compact.css according to this thread:
https://groups.google.com/forum/?fromgroups=#!searchin/weewx-user/forecast$20css$20files%7Csort:relevance/weewx-user/u2w_oLIVy3s/8uE0n42EFAAJ
may be a total red herring though!!
On Sunday, 8 January 2017 03:01:44 UTC+2, Marc
On Friday, January 6, 2017 at 6:23:27 PM UTC-5, Matt Frost wrote:
>
> I have a newly installed VP2 running weewx 3.6.2. I installed
> weewx-forecast 3.2.9 and have it mostly working. The issue I'm having is
> with the formatting of the single table. The single table sample page looks
> fine but
On Friday, January 6, 2017 at 5:23:27 PM UTC-6, Matt Frost wrote:
>
> I have a newly installed VP2 running weewx 3.6.2. I installed
> weewx-forecast 3.2.9 and have it mostly working. The issue I'm having is
> with the formatting of the single table. The single table sample page looks
> fine bu
Thanks. I finally figured that out. I was putting the forecast into a
container that was center aligned and that was messing things up. I ended
up creating a new container for the forecast and that solved most of my
problems. The only issue I have left is the sunrise/sunset information is
showi
Hi all,
I've been having issues with some spikes in the rate data which I think was
caused by the unit playing up. I want to delete these instances of it but I
cannot work out how/what I need to do and most of the details I have seen
relate to say temperatures.
I can access the db etc but whe
Substitute rain, rainRate for outTemp in the userguide for spike removal:
http://weewx.com/docs/usersguide.htm#Hardware_problems
eg
Verify the bad data exist where you think they exist
sqlite3 weewx.sdb
sqlite> select dateTime,outTemp from archive where outTemp > 1000;
becomes
sqlite3 weewx.sd
Hello All,
Weewx with Interceptor and OS lw30x hardware. Ever since a recent
Interceptor update that was supposed to correct the UV/Radiation readings,
weewx is reporting UV to the reports and Wunderground, but it's always 0.
Here are my most recent packets:
~~~
mac=0004a369e0d6&id=8e&rid=6
if you do select * from archive you should get the column headings - what
are you having a problem interpreting?
You may find it more user friendly to install and use phpliteadmin to
access and look at the database and its tables.
.
On Sunday, 8 January 2017 06:04:40 UTC+2, Nick La Gall
On Saturday, January 7, 2017 at 11:48:27 PM UTC-5, Sam Roza wrote:
>
> Hello All,
>
> Weewx with Interceptor and OS lw30x hardware. Ever since a recent
> Interceptor update that was supposed to correct the UV/Radiation readings,
> weewx is reporting UV to the reports and Wunderground, but it's al
sorry, i just realized that there is no console on a lw30x.
we need to figure out exactly what uvh and uv are. to do that, you need to
let the lw30x send data to the oregon scientific servers and see what
numbers they show for anything related to solar.
m
--
You received this message because
It looked okay for my first couple of months importing. The weewx.sdb
database went from 2 MB to 11 MB. So somethings there.
But it didn't generate the NOAA reports. Is it supposed to do that
automatically from older data in the database ?
Oct 2010 look like this :
MONT
The best way of forcing the NOAA reports to be generated is to a) stop
weewxb) delete all NOAA reportsc) start weewx
Not sure if it automatically generates reports earlier than ones already
present in the directory - hence deleting ALL NOAA reports and have weewx
regenerate them all aga
WeeWx-WD is not displaying rainfall in the saratoga templates and the only
rain-related error I can see in syslog is this:
>
> Jan 8 01:50:48 raspberrypi weewx[31749]: weewxWd: wdMoonApsis SLE
>> executed in 0.021 seconds
>
> Jan 8 01:50:48 raspberrypi weewx[31749]: weewxWd: wdEclipse SLE execu
I think it will be tough to correlate given the current weather in California.
I have Data in the osweather site going back as far as September and my logs
should also go back relatively far. I'll see if I can't get you an idea of the
scale they are using.
Looks like the scale is relatively sm
43 matches
Mail list logo
