Thanks
On Wednesday, November 1, 2023 at 1:49:00 PM UTC-7 Ben Cotton wrote:
> On Wed, Nov 1, 2023 at 4:17 PM Ralph Underwood wrote:
> >
> > I was using the NOAA Aviation Radar image (
> https://www.aviationweather.gov/data/obs/radar/rad_rala_lws.gif)
> > in my Seasons s
I was using the NOAA Aviation Radar image
(https://www.aviationweather.gov/data/obs/radar/rad_rala_lws.gif)
in my Seasons skin. They improved/fixed it so it no longer works.
Anyone find a replacement that works from NOAA?
I find some images but they are all national US, I live on the left
Probably not too elegant, I have been setting soilTemp4 to 32 and setting
the label to "Freezing" and adding it to any charts that I want to show
freezing.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop
I recently installed a PurpleAir outdoor sensor. It’s connected on wifi and
appears to be sending data. I can display all of the data points listed in
the purple air driver docs on a WeeWx Seasons page.
When I attempt to a create a graph - I get the errors in the log below
(this is with
Thanks. I now have the aviation weather radar displaying.
On Tuesday, January 12, 2021 at 5:30:23 AM UTC-8 mjenk...@gmail.com wrote:
> If you go up a level, the ones not in the folders are the current ones.
>
> https://www.aviationweather.gov/data/obs/radar/rad_rala_lws.gif
>
>
> On Monday,
Anybody able to make the new and improved NWS radar work? Has anyone
written code to build a dynamic link for the aviation weather radar? It
appears to me that we need to enter date and time into the url for the
radar. I copied the aviation radar link into my skin.conf and it appeared
to
What's wrong with using VNC? I use it to get to two remote Weewx running
RPi. With the RPi, VNC has a deal to access up to five computers for free.
On Wednesday, December 9, 2020 at 6:33:55 PM UTC-8 wa4...@gmail.com wrote:
> Many good ideas here.
>
> My suggestion:
> Set up an identical package
Also the humidity sensor did not come included with the Ultimeter 2100
package, it is an option.
On Monday, April 20, 2020 at 6:49:26 AM UTC-7, Ralph Underwood wrote:
>
> Did you enter a local barometer reading to the 2100? I don't have my
> manual handy, but seem to remember that
Did you enter a local barometer reading to the 2100? I don't have my manual
handy, but seem to remember that in order for the 2100 to output the
barometer reading you first have to calibrate it by entering a local value
once. I don't upload to weather sites with my systems but both of my
I like to see the freezing level on many of my charts so I set soilTemp4 to
32 degrees in the StdCalibrate section of weewx.conf
[StdCalibrate]
[[Corrections]]
# For each type, an arbitrary calibration expression can be given.
# It should be in the units defined in the
Bravo! Look forward to testing next month when I should have some free
time.
On Tuesday, April 9, 2019 at 1:45:51 PM UTC-7, bell...@gmail.com wrote:
>
> To further my WeeWX/MQTT/Python knowledge, I have written a WeeWX
> multi-threaded service. One thread receives the MQTT messages and puts
Hi George,
Try just writing the file with python -
m1 = "test"
file = open('/var/tmp/file-test.txt' , 'w')
file.write(str(m1)+'\n')
file.close()
My first time with my python script I had a typo that I could not see for a
couple of hours - I did learn a lot as I scoured the reference books for
Probably a permissions issue. I run my python script as sudo. Hope that
helps.
Ralph
--
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
I have a small python program that subscribes to mqtt and writes a text
file. I then use the filepile as a service to get the data into WeeWx. The
"main" data comes from a Ultimeter station via the driver.
I came up with this approach while I was modifing/testing using the
WeeWxMQTT driver a
You may find that you need to look to the seasons.css file to see how
things are formatted in titlebar.inc.
On Saturday, March 30, 2019 at 6:27:40 PM UTC-7, tomn...@frontier.com wrote:
>
> Thanks, that's sort-of what I was thinking, but couldn't find any clues
> about about where they'd be
I haven't been using TOP to monitor memory usage - I have cmon running and
note the total memory use is creeping up. I restarted this station a
couple of times yesterday. I had a request to show the freezing level on
some charts - ended up setting soilTemp4 to 32 degrees and including it on
I will test v0.22. Thanks!!
On Thursday, February 21, 2019 at 9:04:04 AM UTC-8, Ralph Underwood wrote:
>
> The URL for the development station is http://www.mapleleaf.ruresearch.com.
> This station is in my basement lab area - the wind and rain stuff is
> sitting on a counter s
The URL for the development station is http://www.mapleleaf.ruresearch.com.
This station is in my basement lab area - the wind and rain stuff is
sitting on a counter so that's why there are no readings for them. The
"Temperature 1" reading is from a DS18B20 sensor connected to an Adafruit
I have a couple of stations with Ultimeter 2100 and usb-serial connections
to RPi 3 B+. Both appear to have increasing memory usage.
I just copied the "new" ultimeter.py driver to the driver directory and
restarted - this was my result. I went back to "old" version of driver and
restarted
What's involved in changing the driver to a service? My coding skills are
just above minimal, however I would be happy to be involved in testing. I
frequently fall asleep reading my 1,540 page "Learning Python" - using it
as a pillow has only raised by knowledge level slightly.
I have one
*IT WORKS!*
I added: TIME = dateTime to wxMesh stanza of weewx.conf the stopped and
restarted WeeWx - waited a few minutes and I now have values showing up in
/var/www/html/weewx/index.html
Thanks a lot for all of the help!
Now that I have something working I can start experimenting with
Do I need to have TIME = date-time in my weewx..conf wxMesh stanza?
I thought that the TIME sent from mosquitto would be ignored.
I attempted Vince's suggestion and still same.
I'll look it all over again later.
Thanks
On Wednesday, April 11, 2018 at 11:24:38 AM UTC-7, vince wrote:
>
> On
I didn't start a discussion on that but I will look for it. I have been
searching for a post where (I thought it was mwall) mentions setting the
dateTime to something to force weewx to use the correct one. Or maybe it
was a dream :)
Thanks for your help.
--
You received this message because
pi@mapleleaf:~ $ date +%s
1523465424
pi@mapleleaf:~ $ date
Wed Apr 11 09:50:28 PDT 2018
appears to match my iMac time. The Rpi does not have a realtime clock;
however I have a couple in my parts drawer. I will find a battery and try
one of them.
I programmed the Huzzah with another Rpi -
Hi Bill
I rebuilt my development system, installed Jessie, configured rpi,
installed Mosquitto and weewx with the simulator. Attempted to do the
extension install of wxMesh, that failed so I manually installed the wxMesh
file in /usr/share/weewx/user. Changed the driver to wxMesh and made
UTC-3, Ralph Underwood wrote:
>>>
>>> I understand that you are using the HTU21 and think that it might be
>>> best if I concentrate on that setup. Can you post the actual sketch you
>>> are using?
>>>
>>
> Attached. I use an Adafruit
I restarted mosquitto and when I use mosquitto_sub -d -t weather I get:
Client mosqsub|16684-ru-pi sending CONNECT
Client mosqsub|16684-ru-pi received CONNACK
Client mosqsub|16684-ru-pi sending SUBSCRIBE (Mid: 1, Topic: weather, QoS:
0)
Client mosqsub|16684-ru-pi received SUBACK
Subscribed (mid:
Thanks Bill for the reply.
I am now sending
INTE:68.11
via mqtt
I do note that I do not have TIME in my mqtt message.
WeeWx still not happy with this as the log after starting:
Apr 10 08:24:14 ru-pi systemd[1]: Starting LSB: weewx weather system...
Apr 10 08:24:14 ru-pi weewx[6379]:
I found some goof info on the development group and got closer to a working
setup. I purchased an Adafruit HTU21 sensor board and using Bill Morrows
code example I now get MQTT output like this:
TIME:0,INTE:19.36,INHU:59.75
TIME:0,INTE:19.35,INHU:59.74
TIME:0,INTE:19.35,INHU:59.88
My goals is to add some sensors via MQTT to my stations which are all RPi 3
and use WeeWx 3.8.0. I am running the Mosquitto broker on the same RPi as
WeeWx
One station uses a Ultimeter 2100 driver -* can I use WeeWxMQTT as a
service*?
Other stations are a combination of OWFS and FileParse
I am interested in your progress. I have a esp8266 on my work bench -
haven't got started with it yet. I was looking for options use wifi with my
OWFS based system. I use the file parse driver to add data connected to
RPi.
On Sunday, January 21, 2018 at 10:42:47 AM UTC-8, Andreas Otten
My Ultimeter 2100 has been very reliable. One time after a lightning storm
it did find its way into the wrong mode. After finding the manual, I hit
the right key combination and it has been rock solid.
I am also currently using FSWEBCAM in test mode - haven't noticed any
problems.
On
Good suggestion. I can't wait for the ice and snow to be gone for a day or
two and get the sensor down where I can really troubleshoot what is wrong.
Everything is working great with that sensor disconnected. It could also
be a problem with AD converter on the Hobby Board's anemometer board.
Those ESP8266 look interesting. I ordered a couple so I can do some
experimenting.
--
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
wrote:
>
> shouldn't each reading be on a separate line - so it should be
> soilTemp1=60.64
> pressure=29.54
>
> rather than
>
> soilTemp1=60.64 pressure=29.54
>
>
> On Saturday, 7 January 2017 07:23:27 UTC+2, Ralph Underwood wrote:
>
>> I made a chang
I made a change so that only the pressure value shows up in my txt file and
it works! Maybe tomorrow I can figure out what is wrong with the
temperature.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop
I used wee_extension to install fileparse.py and now I am stumped with this
error: fileparse: cannot read value for '61.34,29.534': invalid literal for
float(): 61.34,29.534
Appears that I might have to do some more studying about floats and such.
--
You received this message because you are
I decided to try the barometer sensor on the RPi i2c bus.
I have managed to get data from the sensor and write out a text file in
/var/tmp/wxdata. I have a cron job overwrite the file every minute (for
now) with fresh readings.
Attempting to follow the directions in FileParse.py gets me
I have a OWFS station on Rpi going with temps, rain gauge, wind and
direction. I started work on this station several years ago and and the got
too busy with my day job.
In the mean time I implemented at Pete Bros. Ultimeter 2100 station which
was working fine until a recent power outage,
I installed the station last week and it appears to be working. I managed
to break the anemometer while I was installing the mast so I have no wind
info until my next visit to the site in a week or two. Pete Bros. had the
parts available and I already have them in hand. I ended up commenting
; wee_extension try
>
> ./wee_extension --install weewx-owfs-0.18.tgz
>
> Note the ./
>
> Gary
>
> On Sunday, 6 November 2016 11:54:16 UTC+10, Ralph Underwood wrote:
>>
>> I am running weewx 3.6.1 on a Rpi using an Utilmeter 2100. I am trying
>> t
I am running weewx 3.6.1 on a Rpi using an Utilmeter 2100. I am trying to
install owfs-0.18 and I can't seem to get past the step "*wee_extension
--install weewx-owfs-0.18.tgz*".
I get "command not found". I can see the wee_extension file in
/home/weewx/bin
I have never used wee_extension
I'll second that, great support from users and developers!
This is the third weewx station I have cobbled together - one with a
wireless Oregon Scientific, one with one-wire, and now this one with Pete
Bros. - Plus two more carefully monitoring my basement as I test and
experiment. The Rpi
:15:45 PM UTC-4, Ralph Underwood wrote:
>>
>> Oct 27 17:24:15 raspberrypi weewx[6672]: engine: Unable to load driver:
>> could not open port /dev/ttyUSB0: [Errno 2] No such file or directory:
>> '/dev/ttyUSB0'
>>
>
> hi ralph,
>
> it looks like yo
I could use some hints on what I need to modify to get the Ultimter to talk
to WeeWx.
I have a serial to usb converter as the Rpi does not have a serial port and
I somehow missed that the Ultimeter was not USB when I ordered it.
I tried to use this in my weewx.conf :
45 matches
Mail list logo
