I've had a headless Pi 3 running WeeWX with rtl_sdr for two and a half
years without a problem. I had to add a pressure sensor to the Pi, but
that was fun.
I just ran updates and rebooted it. The last time I did that was in
February, and it had run continuously since then.
On Saturday,
I am also using an Acurite 5-in-1 (and eight additional sensors (including
the lightning sensor)) connected to a Raspberry Pi.
rtl_sdr is the tuner, and rtl_433 uses rtl_sdr to receive and decode
packets from known devices, including the Acurite ones. Then the WeeWX SDR
driver uses rtl_433 to
The free API key is good for a maximum of 10 calls per minute and 500 per
day. That's not enough for commercial use, or at least commercial use that
could justify paying for a higher tier.
On Friday, May 18, 2018 at 4:01:56 AM UTC-4, Andrew Milner wrote:
>
> I shall wait and see. I would
A few days later I'll also endorse the Raspberry Pi 3. I've been running
WeeWX on it for a year and haven't had any outages that weren't my own
fault.
I should probably back up the micro SD card, since it's been in use for a
year.
This thing has not stopped working. No outages. Uptime runs
sudo service weewx restart
works fine. The one little problem I've seen is that, if you are using the
SDR driver, it can come back up before rtl_433 has quit and is ready to go
again, so weewx delays and tries again.
On Sunday, January 7, 2018 at 3:02:29 PM UTC-5, Dave Walker wrote:
>
> I
Have you used this FTDI adapter in other situations or a different one?
I ask because there are apparently lots of counterfeit FTDI chips out
there.
On Tuesday, January 2, 2018 at 10:33:25 PM UTC-5, Terry Hock wrote:
>
> Hi,
>I am trying to get the Peet Brothers Ultimeter 2100 working
I know enough just to screw things up, so I'm probably wrong, and I have
not updated sdr_433, but
I just looked through sdr.py, and, for the 5n1 sensor, the parse_text
method has both "wind_speed" and "wind_speed_mph", but the parse_json
method, which is decoding msg_type 49, does not.
I am
That station registry is just a collection of people running weewx. That
is independent of Weather Underground or any other site.
The section you want for Weather Underground is this one. The station ID
and station key (which you enter here as password) you from Weather
Underground after you
I built a pressure and temperature sensor using a BMP280 connected directly
to the Raspberry Pi and wrote a driver. It's too close to the Pi and my
other computers to give useful temperature readings. I bought an indoor
Acurite temperature/humidity sensor and use that for indoor temp and
Is weewx running on the Raspberry Pi?
Weewx on my Raspberry Pi uses MySQL for logging data. I use master/slave
replication to duplicate they database on my Windows computer, but it would
certainly work on a Linux computer. When either is down it catches up when
they are both back up.
Well, never mind. It was showing data for yesterday, but now there's a
gap. So I guess it doesn't automatically update, and I should run
wunderfixer.
On Sunday, August 27, 2017 at 12:35:42 PM UTC-4, Craig Thom wrote:
>
> It works. I didn't even know this was a feature. The only refer
It works. I didn't even know this was a feature. The only reference I can
find to it in the documentation is the "stale" setting for CWOP to prevent
catching up, since CWOP apparently only handles real time data.
My internet service at home was down for a few hours yesterday, and today I
I wish I'd thought of that earlier. I don't think I've got time to put
together any mobile weather monitoring between now and then.
My home is at 96%, so I'll be recording that (at normal 5 minute
intervals). My eclipse watching spot is less than a mile off the center
line, between the sweet
data and a weewx service to get
> the data from the aircon. The following is a screen shot of the current
> conditions.
>
>
>
> On Monday, June 19, 2017 at 10:43:33 PM UTC+10, Craig Thom wrote:
>>
>> Thanks. My question is really about getting the data into weewx, bu
ps. Paul
>
> On Tuesday, June 13, 2017 at 3:53:48 PM UTC+2, Craig Thom wrote:
>>
>> tl;dr What's the best way of getting home brew wireless sensor data into
>> weewx?
>>
>> I plan to build a soil moisture (and temperature) sensor for my garden
>> b
tl;dr What's the best way of getting home brew wireless sensor data into
weewx?
I plan to build a soil moisture (and temperature) sensor for my garden bed.
I'll likely build another for leaf wetness and UV index, because the
sensors are cheap and it will be fun.
The question is how best to
This is not an answer to your question, but, if you have root access to the
database on the remote server, you can create one local to weewx and set up
replication, with the weewx machine db the master and the remote one the
slave.
Then you would just update the local one. The remote db will
Thanks. I must have done that during setup, because it's using all of my
64GB card.
I've only been running a few months and my MySQL database is 27MB. I have
added a lot of columns, so that probably doesn't help.
On Saturday, May 27, 2017 at 10:08:44 AM UTC-4, Dennis slagers wrote:
>
>
I am a relative newcomer, too, and am not involved in development or
support of weewx, so I'm probably wrong, but, since no one has said
anything, here goes.
The IDENTIFIER string for FOWH1080Packet is "Fine Offset WH1080 weather
station", and it appears that string is what is used to tell
weewx/commit/64dd68465278e22cdd91b957706e547d79950724>.
>
> To appear in v3.7.2.
>
> -tk
>
> On Mon, May 22, 2017 at 7:30 AM, Thomas Keffer <tke...@gmail.com
> > wrote:
>
>> There is no 'low' extractor, but one could certainly be added.
>>
>> -tk
>>
>>
ay, May 20, 2017 at 6:34:27 AM UTC-4, Craig Thom wrote:
>
> It appears that the "distance" value archived is the average of the values
> from each loop packet. Since that value appears to be whatever the last
> distance was, even if that was a month ago, I don't think thi
It appears that the "distance" value archived is the average of the values
from each loop packet. Since that value appears to be whatever the last
distance was, even if that was a month ago, I don't think this is a useful
number. Here's an example:
The value reported at the start of the
And, since the antennas for these are monopoles, they will work much better
when stuck on a piece of metal at least a foot in diameter.
On Friday, May 19, 2017 at 12:33:16 AM UTC-4, Andy wrote:
>
> https://m.aliexpress.com/s/item/32611544795.html this one works ok, as
> said before antenna is
I think any DVB-T radio using those two chips will work. As far as I can
tell, the connector the antenna uses is the only real difference, and, if
you plan to use the stock antenna, that's no big deal.
There's not a lot of Linux involved. You need to install rtl_sdr and
rtl_433, and then
, 2, 124.346153846154, 7.17307692307692
1493443800, 3, 123.36, 7
1493443500, 4, 119.809090909091, 7
On Saturday, April 29, 2017 at 1:39:53 AM UTC-4, Craig Thom wrote:
>
> The total strikes I'm showing in my database don't match what's coming
> from the sensor.
>
> This is the rele
The total strikes I'm showing in my database don't match what's coming from
the sensor.
This is the relevant entry in [sdr] [[sensor_map]]
lightningStrikesTotal = strikes_total.6FAF.AcuriteLightningPacket
Here's what I've got in the database, and I have no idea why the total
isn't
JADP, but I installed Raspbian jessie lite (8) on a Raspberry Pi 3 and
installed weewx using the .deb package, and it worked without having to
make any changes.
On Sunday, April 23, 2017 at 3:26:34 AM UTC-4, Andrew Milner wrote:
>
> weewx works just fine on rpi with Jessie. I have never
The weewx driver is here: https://github.com/matthewwall/weewx-sdr
I don't think it's complete, and there were some things I had to work out,
but you can search for the answers here.
One thing to keep in mind is that the pressure sensor for my Acurite
system, and probably all the others, is in
N/A for the gust direction was the fix. To undo the fix apply the config
change.
On Sunday, April 16, 2017 at 2:23:20 PM UTC-4, Nicolas Cazan wrote:
>
> Okay, but today's driver update contains the fixes, or should we do them
> manually?
>
--
You received this message because you are
Assuming it's an Acurite display (you didn't say), you'll need to change
the USB mode from 2 to 4. It defaults to 2 when it loses power.
On Sunday, April 16, 2017 at 3:06:58 PM UTC-4, gary s wrote:
>
> I had the battery on my main display unit go bad. I replaced the
> batteries and now cant
That fixed the problem.
The strikes count seems to be reset every archive period. Is this the
expected behavior? Is there an easy way to product a daily total or a
rate/hr?
dateTime, lightningStrikes, lightningDistance
1492366200, 5,4.45360824742268
1492365900, 6,
I haven't done that, so that's the answer, I assume.
and I had just modified sdr.py to try to see what was happening:
def _calculate_delta(label, newtotal, oldtotal):
delta = None
if newtotal is not None and oldtotal is not None:
if newtotal >= oldtotal:
ime': 1492338563,
'outTemp': 62.4, 'lightningStrikesTotal': 39.0, 'usUnits': 1}
On Sunday, April 16, 2017 at 6:29:00 AM UTC-4, Craig Thom wrote:
>
> I got a strike recorded (but not heard) while I was editing weewx.conf.
>
> That last byte keeps changing. Now it's "74".
>
>
Strikes 39 Distance 4 L_status 0x00 - c0 6f af cf 50 4e 27 84 f6
2017-04-16 06:27:07 Acurite lightning 0x6FAF Ch A Msg Type 0x02: 62.6 F 79 %
RH Strikes 39 Distance 4 L_status 0x00 - c0 6f af cf 50 4e 27 84 f6
On Sunday, April 16, 2017 at 6:26:07 AM UTC-4, Craig Thom wrote:
>
&
This is what I've got in weewx,conf for the device:
[SDR]
[[sensor_map]]
lightningDistance = distance.6FAF.AcuriteLightningPacket
lightningStrikesTotal = strikes_total.6FAF.AcuriteLightningPacket
[[deltas]]
lightningStrikes = lightningStrikesTotal
These are my
Software Defined Radio. The way I am using with weewx is with a USB tuner
built for DVB-T TV broadcasts in other countries (but not the U.S.) that
use the RTL2832U chipset. People discovered that these tuners could cover
a much larger range than DVB-T and have been using them for receiving
Maybe my fan isn't running, since I've got the dual solar panel version.
I'll figure it out Sunday.
The sensor on my front porch must be getting some light around 6 pm,
because it gets too high then. Maybe I should figure out a way to get
weewx to use the lower of the two temperature sensors
Not that I know of, although some people have added solar cells to make the
fan in the 5-in-1 spin faster.
Since I'm using SDR, I've decided to remap temperature and humidity to be
read from a different sensor (the lightning one, in this case). I thought
I had picked a good spot, but the
ms obvious in retrospect that this was needed.
On Tuesday, April 11, 2017 at 1:16:00 PM UTC-4, mwall wrote:
>
> On Tuesday, April 11, 2017 at 12:40:16 PM UTC-4, Craig Thom wrote:
>>
>> My display shows 0.38" of rain today.
>>
>> rtl_433 show an increase of raincounter_raw f
12:35:54", "model" : "Acurite 5n1 sensor", "sensor_id"
: 1730, "channel" : "A", "sequence_num" : 2, "battery" : "OK",
"message_type" : 49, "wind_speed" : 0.000, "wind_dir_deg"
And it's always possible a bird has built a nest in my rain gauge, I guess.
I'll check that later, too.
On Tuesday, April 11, 2017 at 8:23:07 AM UTC-4, Craig Thom wrote:
>
> It's raining lightly now, so I can't be sure, but other nearby stations
> and the airport not far away ar
It's raining lightly now, so I can't be sure, but other nearby stations and
the airport not far away are showing accumulation, but I'm not.
I've got to go to work now. When I get home, I'll pour some rain in the
sensor and see what happens.
I think the problem is with rtl_433. Here's the
On Sunday, April 9, 2017 at 8:08:19 AM UTC-4, mwall wrote:
>
> [StdCalibrate]
> [[Corrections]]
> windDir = windDir + 180 if windDir < 180 else windDir - 180
>
> I think you could also use
windDir = (windDir + 180) % 360
--
You received this message because you are subscribed to
About twenty-six hours ago I got my BMP280 pressure sensor up and running.
Now the barometric pressure calculated by weewx is within 0.02 inHg of
what the airport less than two miles away reports as sea level pressure.
That's closer than what my Acurite display shows.
Go team!
--
You
. That should be fun.
On Thursday, March 30, 2017 at 5:52:25 PM UTC-4, Craig Thom wrote:
>
> Forgive me for being stupid, but this is all new to me.
>
> It's the last step, getting the data to weewx, that I'm fuzzy on. Do you
> import the csv file with wee_import?
>
&g
Forgive me for being stupid, but this is all new to me.
It's the last step, getting the data to weewx, that I'm fuzzy on. Do you
import the csv file with wee_import?
I am going to play with reading my Acurite (and other) wireless sensors
using SDR, which means I can eliminate their display
The data in the MySQL archive (now that it's working) show good values for
Pressure, but Weather Underground shows gaps of up to an hour with
"pressure" of "--" in both graph and table. I noticed it when I got up
this morning and saw that as the current data.
This is not a deal breaker, since
I am using a RPi 3 and an RTC. As noted, it's not for accuracy; it's for
what happens when you reboot it, in the brief period between the time weewx
starts and ntp sets the clock.
The clock was cheap and only took a few minutes to set up.
On Sunday, March 12, 2017 at 4:38:54 PM UTC-4,
ly have NO idea what that does – that’s tomorrow’s research
> project.
>
>
>
> Clay Jackson
>
>
>
>
>
> *From:* weewx...@googlegroups.com [mailto:
> weewx...@googlegroups.com ] *On Behalf Of *Craig Thom
> *Sent:* Sunday, March 12, 2017 7:48 PM
> *To:* weewx-user <we
Yes, I was using MySQL, and I changed nothing in MySQL. The only thing I
changed was upgrading weewx. The MySQL server is on the same machine as
weewx.
I got it working, but it did require a change to my MySQL configuration,
the configuration that was working fine before the weewx upgrade.
12, 2017 at 11:09:14 PM UTC-4, Craig Thom wrote:
>
> 3.6.2
>
> I started with the new weewx.conf and made changes one at a time, testing
> each one.
>
> Everything is fine until I change
>
> [DataBindings]
>
> [[wx_binding]]
>
> from database = arc
3.6.2
I started with the new weewx.conf and made changes one at a time, testing
each one.
Everything is fine until I change
[DataBindings]
[[wx_binding]]
from database = archive_sqlite to archive_mysql
I used the default values when I set it up, so all the schema,table, user
name,
12, 2017 at 10:18:45 PM UTC-4, Craig Thom wrote:
>
> I am running on Raspbian on a Raspberry Pi.
>
> I kept my old weewx.conf file.
>
> The only edit I made was to set Wunderground Rapidfire to 'TRUE', but
> after I set it back to false I got the same error.
>
> Th
I am running on Raspbian on a Raspberry Pi.
I kept my old weewx.conf file.
The only edit I made was to set Wunderground Rapidfire to 'TRUE', but after
I set it back to false I got the same error.
This log was captured after I rebooted the Pi.
Mar 12 22:03:56 weatherpi weewx[608]: engine:
Yes, I read something about Rapidfire not working with Acurite sensors
until 3.7 is released. I decided to stay with the stable release, although
third beta looks promising.
I am showing a strong signal from the station to the display whenever I
look, so, if it drops out on occasion, I'm not
) then
nulls get recorded.
On Sunday, March 5, 2017 at 3:45:41 PM UTC-5, mwall wrote:
>
> On Sunday, March 5, 2017 at 3:36:37 PM UTC-5, Craig Thom wrote:
>>
>> I'm getting an error in syslog that says weewx isn't getting good data
>> from my Acurite sensor, but
It's a desktop PC running Windows 10. It's on most of the time, but I was
playing.
I don't remember the steps I did to get the MASTER/SLAVE replication going,
other than step by step having to learn what everything meant.
Here are a few tips:
If you are running mysql on a Raspberry Pi or any
I'm getting the same issue, and, since the display is not showing the
phantom rain spike, I assume it's in the USB communication. I've ordered a
shorter USB cable with ferrite cores, but, in the mean time, since I'm
using US measurements, I added
[stdQC]
...
rain = 0, 0.4, inch
Is
Did you check syslog to see if weewx is giving you any errors?
$tail -f /var/log/syslog
You can stop and restart weewx in another SSH terminal window so you don't
miss anything in the tail window.
A couple of times, after I've rebooted, weewx has been unable to
communicate with my 1035
I ran into the same issue last week when I was installing weewx for the
first time (on my first RPi). It went smoothly after that. I have MySQL
Workbench installed on my main Windows PC, so I'm able to connect it and
confirm it is racking up the rows (after creating a user for myself with
I wish I'd found that a week ago. I installed lynx on my RPi3 and got it
that way. I had installed Raspbian without a GUI.
On Thursday, February 23, 2017 at 5:41:02 PM UTC-5, Glenn McKechnie wrote:
>
> You probably need to go down a more 'auto' path.
>
> Open a terminal then visit
61 matches
Mail list logo
