On Tuesday, September 22, 2020 at 8:08:02 AM UTC-7, Tom Keffer wrote:
>
> Just tried it, and it worked for me. It would a truly dumb design that
> depended on an internet connection to respond to a local query.
>
>
>
One thing I did find experimentally is that if you use hostnames, don't use
On Wednesday, September 30, 2020 at 11:50:45 AM UTC-7, Tom Quinn wrote:
>
> that seems to work just fine... I think. this looks like I think it should.
>
>
> /home/weewx/bin/user # python timetest.py
>
>
>
Have you confirmed your python isn't messed up ?
Perhaps try a simple test something like:
import time
print(time.localtime())
print(time.asctime(time.localtime()))
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group
API looks so close to a PurpleAir that you almost wonder if they bought the
company. The webpage is a little interesting though, as they mention
things like the device needing an Internet conenction (for time) in order
to function it seems. But it looks to me like any extension that speaks
I tend to see my PA 'a' and 'b' sensors very close to each other, but I
average them when I feed the data to weewx.
My PA's JSON contains:
"hardwarediscovered": "2.0+BME280+PMSX003-B+PMSX003-A",
"hardwareversion": "2.0",
Run "curl http://purpleair-/json | jq . | sort" for a more
On Saturday, October 3, 2020 at 3:42:22 PM UTC-7, James Fritz wrote:
>
> this is the error I can find, not sure how to fix:
>
> Oct 3 17:36:05 raspberryWeather kernel: [ 5472.665286] wlan0:
> authentication with 30:23:03:6b:2a:df timed out
>
>
We're not going to be able to help with one-liners
On Saturday, October 3, 2020 at 8:51:22 AM UTC-7, James Fritz wrote:
>
> I installed weewx then the UDP driver for weatherflow. I had it working
> for the local webpage for data coming in. I then tried to install the
> Belchertwon skin and was having problems there, so I uninstalled
>
On Thursday, September 24, 2020 at 8:29:38 AM UTC-7, Dan'l B wrote:
>
> I ran Vince’s UDP listener, with the following results, which don’t look
> anything like the older Air/Sky unit outputs.
>
>
>
Right - a Tempest is a different sensor than the Air/Sky sensors, but
notionally is the union of
Over in the WeatherFlow forums a guy had an interesting problem where
occasionally he has timestamps in his weewx.sdb of 300 or so (ie, 12:05AM
1/1/1970 GMT). My 'guess' is his host took a reboot and weewx fired up
before the host had accurate date+time.
Is there an easy way to block writes
On Monday, September 14, 2020 at 5:03:23 PM UTC-7, YB322 wrote:
>
> It is clearly something with the station itself, but not sure why it is
> randomly throwing a time in the future, think it is some kind of bug in the
> latest firmware as I have now seen a couple of other posts with the same
>
If you switch to the extended schema, you don't need to add the lightning
elements a second time in weewx.conf, as they're already in the v4 extended
schema, but you'd need to line up the names you picked so that they match
the database schema. The element names are "lightning_strike_count"
> ftpgenerator: (0): caught exception '': [Errno
111] Connection refused
Connection refused means you are trying to connect to a computer that isn't
running the service you're trying to connect to. Is it possible you have
a typo in weewx.conf for the system name (or address) you hope to
On Thursday, May 28, 2020 at 3:16:04 PM UTC-7, Benjamin Trey Blue wrote:
>
> ...but I'm too Linux-dumb to have figured it out yet and I'm not really
> sure how to go about even troubleshooting it further.
>
> Should I maybe consider setting-up weewx to run as a non-root user and
> then
On Thursday, May 28, 2020 at 4:47:51 PM UTC-7, David wrote:
>
> Hi Vince,
> I could force the rpm installation, but was hoping to get the WeeWX rpm
> file fixed since this will be an ongoing issue.
>
>
Given people are all volunteers, you might be waiting a while for a
On Thursday, May 28, 2020 at 4:16:47 PM UTC-7, David wrote:
>
> Hi Robert,
> Thanks for the reply.
> I have tried this but unfortunately it doesn't solve the problem.
> While it provides a '/usr/bin/python' file, it doesn't solve the problem
> of providing a package which has the required
Here is a quick rpm that should fake out things for you. Try installing
this first and then the weewx rpm for centos8.
These aren't digitally signed, so if rpm barks at you, 'use the force Luke'
:-)
I've attached the spec file just so you can see what it has inside. If you
need to tweak it,
On Friday, May 29, 2020 at 6:33:22 AM UTC-7, mwall wrote:
>
> however, there *are* bld_deps that are python2:
> %define bld_deps python, python-configobj
> are these somehow getting propagated into the rpm itself?
>
>
If you run "rpm -qp --requires filename.rpm" you will see the dependencies
I'll open an issue on this one this afternoon and provide some updates
there, if that's ok with Tom+Matthew...
--
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
On Friday, May 29, 2020 at 10:40:47 AM UTC-7, mwall wrote:
>
> On Friday, May 29, 2020 at 12:24:14 PM UTC-4, vince wrote:
>>
>> I'll open an issue on this one this afternoon and provide some updates
>> there, if that's ok with Tom+Matthew...
>>
>
> yes, please
On Friday, May 29, 2020 at 1:40:28 AM UTC-7, David wrote:
>
> On Friday, May 29, 2020 at 11:32:47 AM UTC+9:30, vince wrote:
> Thanks for that Vince, i'll give it a go and get back to you.
> I understand people volunteer to do this stuff and certainly wasn't
> expecting an immediate
> Thank you for your answers.The "Meteo-pi hat" is the product sell by
>> prodata system (https://www.weatherstations.co.uk/meteo-pi.htm) ?
>>
>>
Does anybody currently running weewx have one of these integrated
successfully ?
That looks like a nice product for $89 US if you go through the
On Friday, May 29, 2020 at 2:14:52 PM UTC-7, Brent Geery wrote:
>
> Mine is working without a hitch the last week. I'm new to the Davis VP2+,
> the PI Zero, and the Meteo-pi hat. It's only just reporting to WU right
> now, and I haven't customized weewx reports yet, but everything worked the
>
On Friday, May 29, 2020 at 10:40:47 AM UTC-7, mwall wrote:
>
> On Friday, May 29, 2020 at 12:24:14 PM UTC-4, vince wrote:
>>
>> I'll open an issue on this one this afternoon and provide some updates
>> there, if that's ok with Tom+Matthew...
>>
>
> yes, please
On Sunday, May 31, 2020 at 1:47:51 PM UTC-7, Luc Heijst wrote:
>
> The boot process from a USB-stick as described above is simplified.
> See:
> https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/README.md
>
>
>
I might add - add a correct wpa_supplicant.conf file as well, if
On Sunday, May 31, 2020 at 3:44:09 PM UTC-7, Luc Heijst wrote:
>
> Another approach for setting up the wifi is connect the RPi (the first
> time) with an ethernet cable to the network,
> Remote log in with a putty session and configure wifi with raspi-config.
> I also configure a static
On Monday, June 1, 2020 at 6:44:48 AM UTC-7, Sébastien Bouillon wrote:
>
>
> Do you know the battery life of the Davis station in the event of a power
> failure?
>
>
>
If you use their data logger, literally months.
On Tuesday, May 26, 2020 at 3:47:30 PM UTC-7, Harry P wrote:
>
>
> Is there a way of porting Weewx over to windows? I cannot seem to get it
> installed on my dedicated Ubuntu laptop and or Ubuntu in Windows 10. I
> would love to get weewx working thru my sdr as my Lacrosse does not report
>
On Tuesday, June 2, 2020 at 3:59:58 AM UTC-7, Mike Thompson wrote:
> My plan would be to move home/weewx across to the new platform and then to
> upgrade to Weewx 4.x, does that sound viable?
>
>
Absolutely - should be straightforward.
I've done a very basic test with a spare RPI 1B standalone
I think you're overthinking things.but your basic steps look good.
To import the old data into the new db, you would need to convert your old
db to the new/bigger schema (if your new db uses the big schema), do the
dump, and restore just the INSERT lines (like you did) and rebuild_daily
On Friday, October 23, 2020 at 2:31:44 PM UTC-7, howe...@gmail.com wrote:
>
> So you're suggesting dump/insert the converted old records into the
> smaller new file, rather than the new records into the converted old file?
> I can try that. Thanks!
>
>>
>>
It doesn't matter if 1+4 = 5 or 4+1 =
On Tuesday, October 27, 2020 at 2:20:33 PM UTC-7, Alessandro Del Prete
wrote:
>
> I have the same issue, it's a brand new installation of weewx 4.1.1,
> working since a month with a belchertown skin and a weatherflow tempest.
>
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:
On Wednesday, October 28, 2020 at 8:29:28 AM UTC-7, Ian Smith wrote:
>
> when moving from initial simulator to actual hardware, what's the best way
> of clearing out all of the simulated readings from the database?
>
>
stop weewx, delete the old db, restart weewx and a clean db will be created
oops - yes I do see miles for one number there.
Sorry for the confusion.
--
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-user+unsubscr...@googlegroups.com.
On Saturday, October 24, 2020 at 10:26:59 AM UTC-7, Boston Tom wrote:
>
> I am running 3.7.1 on an rpi with the interceptor driver to collect data
> from my Lacrosse system and publish it to the web, CWOP, APRS, etc.
>
> Everything has been running fine for several years, but I am considering
>
On Saturday, October 24, 2020 at 10:47:03 AM UTC-7, blee...@xs4all.nl wrote:
>
> I'm facing just a minor issue: in the skin.conf is defined
> 'earthquake_maxradiuskm = 2000'. Therefore I'm expecting a distance in
> km's, but the actual distance as well as the units are still in miles (mijl
> in
On Sunday, August 2, 2020 at 8:25:24 PM UTC-7, brisguy foo wrote:
> In the log, the switching between direct a daemon execution starts around
> 10:15 which is when I finally successfully installed version 4.1.1. It
> looks like I killed the daemon around 10:15 and fixed an error in the .conf
>
On Saturday, August 1, 2020 at 9:17:07 AM UTC-7, Chotechai Piyavongsiri
wrote:
>
> Thanks Vince. I took that line out, it did not help.
>
>
>
Well in the absence of any error logs after you made that change, there is
little we can do to help.
Belchertown runs fine with just its d
On Saturday, August 1, 2020 at 1:24:35 AM UTC-7, gjr80 wrote:
>
> The error in your original post relates to an error parsing a config file.
> There are only two config files involved; weewx.conf and the Belchertown
> skin.conf. As per my previous post I suggest you look in the Belchertown
>
On Monday, August 3, 2020 at 11:58:11 AM UTC-7, brisguy foo wrote:
>
> My original complaint was that I could not get the daemon to START without
> rebooting the system. I never mentioned problems with shutting it down. If
> you look at the log starting around 10:47, you'll see messages
On Saturday, August 8, 2020 at 9:06:22 AM UTC-7, Kev D wrote:
>
> Are there any up to date dockers that work out there? I have found a few
> online but they are quite dated and have issues.
>
>
Multiple ones, but part of the point of docker is you can use them as a
baseline to build your own to
On Sunday, August 2, 2020 at 11:51:54 AM UTC-7, brisguy foo wrote:
>
> configobj.DuplicateError: Duplicate keyword name at line 119.
>
> Any ideas on how to fix this?
>
I'd suggest you look at line 119 in weewx.conf and you'll notice you have a
duplicate keyword line there.
--
You received
On Thursday, August 6, 2020 at 1:27:31 AM UTC-7, Andy Sloane wrote:
>
> The production instance is running on a VM but I think the host is being
> hammered already, so spinning another one up isn't an option. Besides,
> would VMWare let me share a USB controller and peripheral between two VMs?
On Thursday, August 6, 2020 at 6:18:51 AM UTC-7, George Alexander wrote:
> I have been trying, thus far without success, to display the measurements
> from two separate databases of weewx on the one report.
>
>
>
In your cheetah template simply add info telling it which db to pull from
On Wednesday, August 5, 2020 at 3:04:56 PM UTC-7, Greg from Oz wrote:
>
> Forgot to mention the old version jumps to the latest post of a long list
> where the new version you have to scroll down to it. That is annoying when
> there are lots of replies.
>
>
>
Definitely not a fan of the new
On Wednesday, August 5, 2020 at 9:59:28 AM UTC-7, Andy Sloane wrote:
>
> I am using the standard skin on Weewx, and would like to create a "staging
> area" where I can experiment with different skins. This area would be
> completely hidden from public view, unless you had the URL. Is this
>
On Friday, July 3, 2020 at 9:59:52 AM UTC-7, Phil Green wrote:wx.
>
> Weewx is running on a Pi3 and up to date and working well.
> I have noticed that periodically at midnight my system shows a drop in
> received signal by the console.
>
>
I wouldn't worry too much about it. You'll see that
On Saturday, July 4, 2020 at 6:58:53 PM UTC-7, Kevin Davis wrote:
>
> Out of curiosity, what are you running for backup power? Surely you’re
> power has flickered enough to almost two years to trigger a reboot.
>
>
Not necessarily. My Seagate Dockstar running weewx has been up 1289 days
On Sunday, July 12, 2020 at 3:34:54 PM UTC-7, David Trebacz wrote:
>
> I'm new to WeeWx, but have been lurking for years. I've got WeeWx
> 4.11/Python3 configured on a machine and plan to cutover my Davis Vantage
> Pro station soon. Very much looking forward to using WeeWx's modern and
>
On Saturday, July 11, 2020 at 12:49:15 PM UTC-7, Michael Grossie wrote:
>
> Raspbian Stretch
> Python v2.7, v3.5, v3.8.3
> Default (for root) v3.8.3
> Raspberry Pi 2 Model B
> WeeWX v4.1.1
>
>
>
Weewx doesn't currently care which python you use, as long as you have that
python's prerequisites
Your windSpeed line mapping is obviously wrong.
--
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-user+unsubscr...@googlegroups.com.
To view this discussion
On Thursday, June 25, 2020 at 8:16:32 AM UTC-7, Geni 0815 wrote:
>
> in graphs.inc is [[[windchill]]]
>
>
>
One item is wind chill (sometimes called 'feels like'), the other is
outside temperature.
They are usually different if you have any wind.
--
You received this message because you are
On Tuesday, June 23, 2020 at 7:29:03 PM UTC-7, gjr80 wrote:
>
> Apologies to Forrest Gump's mother but the first thing that came into my
> head was ' Weather Underground is like a box of chocolatesyou never
> know what your gonna get'
>
>
>>
I lean more toward "WU is as WU does..." or "WU
On Sunday, June 21, 2020 at 3:54:56 PM UTC-7, michael form wrote:
>
> ...saw no need since I assumed that the system would get the correct time
> from a time server.
>
[...]
I would have thought that it would...
>
Not usually a good move to assume anything. You have to understand how
I'd start by ensuring the pi has quality time. Generally running NTP works
better than the built-in systemd time software. An inexpensive realtime
clock module also tends to help. There are 'dozens' of posts here about
the importance of having accurate date+time especially on devices like a
On Thursday, June 18, 2020 at 11:26:36 AM UTC-7, Russell van vlack wrote:
>
> With the Davis Weatherlink IP being discontinued, what are folks using to
> connect their cabled stations to the internet? I see a couple of
> recommendations a while ago for something like this:
>
On Friday, June 19, 2020 at 5:42:09 AM UTC-7, Iain Simpson wrote:
>
> I am wondering whether this is the wisest route or whether to
> a. use the '.deb' file and rebuild my customisation.
>
>
What customization are you referring to ?
Skins ?
Code ?
Or just your weewx.conf edits ?
--
You received
On Tuesday, June 23, 2020 at 1:16:09 PM UTC-7, Manfred Maier wrote:
>
> Pushing once.
> Is there a way to perform the calculations of 3rd party extensions for
> historic timestamps in the database?
>
>
Probably not without writing something equally custom.
The algorithms are (hopefully) well
On Tuesday, June 9, 2020 at 2:26:06 PM UTC-7, Florentin Prevost wrote:
>
> I'm use this driver and sometimes, it happen that the driver crash and
> they are no logs in /var/log/syslog.
>
> I use this :
> https://github.com/Drealine/weewx-weatherlinklive-json/tree/patch-1
>
> The driver send a
On Tuesday, June 9, 2020 at 2:16:26 PM UTC-7, Xant wrote:
>
> Properly posted at WeeWX User's Group, not Development
>
My opinion - long discussions not relevant to weewx at all aren't properly
posted.
Others of course might differ in opinion, which is fine too.
Have a nice day.
--
You
On Wednesday, June 3, 2020 at 8:32:46 PM UTC-7, Xant wrote:
>
> 2) WeatherFlow
> For price x performance, I'm sided to WeatherFlow, which not just ping at
> 2.5secs timeframe, but also has NO moving parts, ambient light, UV index,
> solar radiation. Sonic anemometer!
>
> The previous model
On Friday, June 5, 2020 at 12:40:53 PM UTC-7, WindnFog wrote:
>
> except KeyError, e:
>^
> SyntaxError: invalid syntax
>
>
>
This is becoming our most frequently asked question.
Anytime you see this, it says you are running old python2 code vs. the
python3 interpreter.
On Friday, June 5, 2020 at 2:13:18 PM UTC-7, WindnFog wrote:
>
> Progress! One issue left:
>
> python3[8081]: weewx[8081] INFO user.sftp: sftpgenerator: upload not
> possible: No module named 'pysftp'
>
> Any thoughts on how to fix this?
>
>>
>>>
Try googling the error you got - like everything
On Saturday, June 6, 2020 at 6:18:28 AM UTC-7, Peter Fletcher wrote:
>
> My current weewx report site includes general weather information, but it
> also includes information (temperature and humidity in different locations
> in my house) which is of interest to me but not (presumably) to anyone
On Friday, June 5, 2020 at 5:24:27 PM UTC-7, Greg Gowins wrote:
>
> At the end of last year, I became a backer of the new Tempest weather
> station from WeatherFlow. After patiently waiting, it arrived today! I
> got the initial set up done with no problem, and it is sending data to the
>
On Monday, June 8, 2020 at 10:35:16 PM UTC-7, Xant wrote:
> Wondering feedback from any path above.
>
>
>
Actually I'm wondering what your post(s) have to do with weewx. Seems
like you want to write a Medium blog or something, which is fine - good
stuff, just perhaps the wrong place to post
On Wednesday, June 3, 2020 at 7:21:30 AM UTC-7, WindnFog wrote:
> Seems to be a bit risky and not for the faint of heart. What say, gurus? I
> can leave it at python 2.7.16 for now, although at some point that's going
> away . . .
>
>
>
Not risky in the least, but also no 'technical' reason
On Thursday, June 11, 2020 at 4:43:09 AM UTC-7, Florentin Prevost wrote:
>
> At Jun 8 19:15:07, the weewx fail and no error appear. It is possible to
> reload a driver ?
Nothing in the log you provided shows weewx crashing at all.
--
You received this message because you are subscribed to
On Thursday, June 11, 2020 at 4:00:24 PM UTC-7, Henri Emurian wrote:
>
> Thanks for the help mwall. Journalctl does show me log data, but the
> amount of data is voluminous, and I can't find any logs on weewx. Is there
> a way to filter the results so that I can see the weewx logs? As for
>
On Thursday, June 11, 2020 at 10:35:48 AM UTC-7, Florentin Prevost wrote:
>
> You've seen in detail the log ?
> Because i say already 2 times that Weewx stop without log. Look at this
> line on below comment :
Jun 8 19:15:07 DRSRV1 weewx[24193] DEBUG urllib3.connectionpool:
>
On Friday, June 12, 2020 at 12:41:43 AM UTC-7, Florentin Prevost wrote:
>
> At the moment, WLL driver make a request to my WLL each 3 secondes, maybe
> short ?
>
>
Yes, I would say it is far too short. I would not query it more
frequently than (max_retries * sleep time) so that you don't
On Thursday, June 11, 2020 at 5:19:24 PM UTC-7, gjr80 wrote:
>
> The thing to remember is that WeeWX tends to go quiet when a driver stops
> feeding WeeWX, WeeWX will keep running but largely does nothing. Agree
> there's not much to go on so far but o am not familiar with Weatherlink
> Live
On Tuesday, July 28, 2020 at 3:38:39 PM UTC-7, Jamie Stephens wrote:
>
> another crash, any ideas?
>
>
First guess is a python2/python3 thing. Are you on the latest version of
the driver ?
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To
On Tuesday, July 28, 2020 at 4:49:50 PM UTC-7, vince wrote:
>
> FWIW, I'm using driver 1.1, weewx 4.1.1, python 3.5.3 on a somewhat dated
> pi3plus (Debian 9), with weewx installed using python3 and setup.py method.
>
doh - Belchertown 1.1, mqtt 0.23, and weather
FWIW, I'm using driver 1.1, weewx 4.1.1, python 3.5.3 on a somewhat dated
pi3plus (Debian 9), with weewx installed using python3 and setup.py method.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop
On Tuesday, July 28, 2020 at 1:07:05 PM UTC-7, Scott Grayban wrote:
>
> I opened a issue ticket at
> https://github.com/poblabs/weewx-belchertown/issues/344
>
>
I did a clean install on weewx v4 and belchertown latest, both with python3.
Live stats works just fine for me, without MQTT encryption
On Thursday, July 30, 2020 at 5:00:39 PM UTC-7, Dale Huber wrote:
>
> On Thursday, July 30, 2020 at 7:52:04 PM UTC-4, Dale Huber wrote:
>>
>> I use the wget command and I get an error from the download site when
>> using Linux. Not sure what to do, if i use a browser to download it will
>> save
On Thursday, July 30, 2020 at 8:24:07 AM UTC-7, Tom Keffer wrote:
>
> Should have spotted this earlier: your sensor map is messed up. You're
> using the serial number that was given as an example in the driver's
> documentation, instead of your own serial number.
>
Wow we see this a lot.
I
On Monday, January 11, 2021 at 5:03:14 AM UTC-8 graha...@gmail.com wrote:
> conclusion: only seriously under-powered boxes would be unable to complete
> within typical 300 sec archive interval.
> would be good if someone with such a box gave it a try
>
>
If you can point us at the exact script
For for 1,357,184 records in the db records in my 340 MB database's archive
table
Using Tom's variant from a local file to a backup file in the same working
directory
Dockstar = 46.8 secs via python, 35.1 secs to cp (usb2 laptop drive)
pi3 = 44.3 secs via python,
Way back in 2014 (wow) when we had that long thread about this, many of us
checked our hundreds of backups with 'pragma integrity_check' and never
found any that were not restorable, so I'm pretty ok with taking that risk
still.
On Monday, January 11, 2021 at 5:26:08 PM UTC-8 Tom Keffer wrote:
2020 at 1:06:21 PM UTC-6 vince wrote:
>
>> Yup - your os is far too ancient for the libraries the weewx dpkg is
>> built against. That version went end-of-life in May-2018.
>>
>> I'd suggest you reimage with the current RaspiOS from
>> https://www.raspberrypi
Also, your log had things in it like "/usr/lib/python2.7/socket.py" which
tells me it is trying to use python2 when a modern raspi os uses python3 as
the default. Did you use the wrong instructions when you installed weewx
? You should have used the python3 instructions.
Please provide the
, 2020 at 11:53:08 AM UTC-8 gjr80 wrote:
> Vince,
>
> Thank you. From memory the driver should retry continuously when the
> network returns if loop_on_init = True in weewx.conf (though I am not sure
> I tested this by turning of my network). Can you confirm the loop_on_
Gary - I wanted to pass along some logs from a gw1000 driver abort
yesterday.
I had my home network down for a bit yesterday to do some firmware updates
on my Ubiquiti USG, Switch and AcLite access point and weewx aborted rather
quickly.
The external, wired, and wifi networks were indeed down
This comes up frequently.
A webserver is not installed in the Rasperry Pi os by default.
You have to install the one of your choosing.
Simply run:
sudo apt-get install nginx
Then the URL you are trying to access will work.
On Sunday, December 27, 2020 at 8:03:05 AM UTC-8
uide.
> Placing it in [GW1000] will have no effect.
>
> Gary
> On Monday, 28 December 2020 at 09:36:33 UTC+10 lang....@googlemail.com
> wrote:
>
>> I had the same issue like Vince the other day - and loop_on_init
>> hadn't been set by the install scrip
Agree.
Also thanks for the reminder re: wee_config --reconfigure. I had not seen
magic buried in a driver that asked questions when you reconfigure. That
kinda blows up scripted installs to some extent for folks like me who use
--no-prompt a lot.
These might be nits but I thought I'd mention
ter about 9 hours after restart. Have removed cmon by
>> commenting out any mention of cmon in weewx.conf and restarted.
>>
>> Regards,
>>
>> Garry Lockyer
>> Former DEC Product Support Engineer :^)
>> Kepner-Tregoe Trained :^))
>> C: +1.250.689.0686
I'm not aware of an end-to-end tutorial for what you're asking.
Given your stated caveats about no experience of building a webserver, nor
connecting to MQTT, this one might be too much of a lift for your expertise
level. There are also lots of security things to think about. Don't open
On Thursday, January 7, 2021 at 3:17:26 PM UTC-8 Russell Cutcliffe wrote:
> Now to fix the startup issue that's appeared...
>
We can't help without seeing logs to see what 'issue' you are referring to.
I know you're on ubuntu, but I wanted to pass along one edge case I noticed
yesterday. If
> I was hoping to avoid USB<=>RS232 converters, as I understood they were
> problematic (in the past) and would add another thing-to-go-wrong. I have
> one other old device to monitor and it too has only an RS232 interface.
> Thought I'd be clever and get a low power box with two RS232
> [[Belchertown]]
>> skin = Belchertown
>> HTML_ROOT = /home/weewx/public_html/Belchertown
>> enable = true
>>
>>
>
Your HTML_ROOT is putting the Belchertown output into a subdirectory of
your web document root.
Try opening http://your.host.name/Belchertown and
On Friday, November 20, 2020 at 5:52:15 PM UTC-8 daleea...@gmail.com wrote:
> Despite having downloaded the github's most recent version, and following
> the instructions in the readme file, I run into a file not found error when
> I get to the part of doing"
> sudo wee_extension --install
On Wednesday, November 25, 2020 at 7:50:02 AM UTC-8 fvirg...@gmail.com
wrote:
> I would like to upgrade my weewx version 3.9.2 to 4.2.
> I downloaded version 4.2 in the / home folder and here I stopped. Could
> you help me with the next steps?
>
>
http://www.weewx.com/docs/upgrading.htm
--
There is a massive AWS outage on the east coast, so it's very possible
that's the cause...
--
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
What does your weewx.conf stanza sensor_map for the driver look like, and
do you actually have rapid_wind enabled for your station via the Tempest
app setup ?
I guess I'm wondering if you're using the obs_st mapping of wind (which is
once/minute) and not the rapid_wind mapping of wind (which
On Saturday, December 5, 2020 at 7:26:00 PM UTC-8 gjr80 wrote:
> When you are receiving wind speed values (only) every three seconds what
> does windGust mean? The highest wind speed value seen in that three
> second period?
>
Let me explain the WF gear and UDP API that the weewx driver uses
Well typically you want to do one thing at a time...
- spin up a raspi or VM with weewx using the simulator driver
- if you're using something other than sqlite3, get the db working too
- then get all your skins working
- then try to get the driver working assuming others have gone there
We can't help much without an exact transcript of what you're seeing...your
descriptions aren't quite enough for us.
It is likely you have quotes in there, or you're missing quotes, based on a
google search for ":schema missing wget" and poking around the first few
links.
Try putting quotes
On Wednesday, December 9, 2020 at 8:11:23 AM UTC-8 Sunray wrote:
> A question to you experts: is this feasible at all ? What are the minimum
> setup steps that must be done locally at the cabin? I guess the key steps
> are 1) to find out the local IP addresses of the weather station and the
801 - 900 of 2275 matches
Mail list logo
