On 12 December 2017 at 11:05, Howard Walter wrote:
>
>
> Miguel,
> Hopefully a solution to my issue will also solve your problem.
>
> Glenn and Vince,
> Thanks for your suggestions. Several libmtp files were installed (by
> default I assume); first removed libmtp-runtime and then libmtp-co
First thing, either run weewx or use PYTHONPATH=/usr/share/weewx
python /usr/share/weewx/user/owfs.py
You can't run them both (ie: stop weewx if you use PYTHONPA)TH
weewx.conf
station_type = OWFS
is correct.
[OWFS]
interface = u
That's telling weewx that the driver is on the usb (u) interf
Glen, thank you for writing back. Yes, I had it as service, not driver. So
I have installed everything from scratch...
raspbian stretch minimal image file copied to SD card
sudo raspi-config (to enable 1-Wire)
wget -qO - http://weewx.com/keys.html | sudo apt-key add -
wget -qO - http://weewx.com/a
john,
acurite might be in your budget.
a bridge plus 3 t/h sensors goes for about 100$US, a 5-in-1 sensor cluster
goes for about $80. those are retail prices - you can often get package
deals that bring those prices lower. acurite also has standalone rain
gauges, refrigerator/freezer sensors
Apologies, I already have a computer. I would prefer to setup weeWX on a
Proxmox container of my home server. That's why the systems needs to connect
via WiFi or an Ethernet connection. The controller box I mentioned was whatever
box the sensors connect to *if* the senors need that sort of thing
just installed weewx 3.8.0 and weewx-wd 1.0.3 and getting keyerror: meter
from Testtags, wdClientraw, wdSteelGauges
wdPWS and wdStackedWindRose are working
here is the log and weewx.conf files
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To
On Monday, December 11, 2017 at 3:50:33 PM UTC-8, John Russell wrote:
>
> Cost is a good question. I wouldn't want to spend more than ~$150 on 4
> temp sensors and the controller. If that includes a rain sensor then good,
> if not I'd spend extra money on it. Ideally I'd like a more modular
>
Miguel,
Hopefully a solution to my issue will also solve your problem.
Glenn and Vince,
Thanks for your suggestions. Several libmtp files were installed (by
default I assume); first removed libmtp-runtime and then libmtp-common.
Rebooted. As Glenn suspected, the mtp-probe messages disa
Cost is a good question. I wouldn't want to spend more than ~$150 on 4 temp
sensors and the controller. If that includes a rain sensor then good, if not
I'd spend extra money on it. Ideally I'd like a more modular approach, buy a
couple temp sensors and the controller, then expand as time goes
On Monday, December 11, 2017 at 7:19:15 AM UTC-8, Howard Walter wrote:
>
> I recently decided to upgrade my RPi running weewx 3.5 on the Debian 8
> Wheezy based Raspbian to weewx 3.8 running on the new Debian 9 Stretch
> Raspbian.
>
>
>
Changing two things at once can be challenging. Is it possi
add a few more:
- how much do you want to spend ?
- what price point is your max ?
- how hard do you want to work to make it happen ?
example:
- a Davis Vantage Vue is rock solid-reliable and sensors are solar
powered
- however, it doesn't have multiple external sensor capabil
My old WH1080 is getting more more and more USB hang-ups. I have to reset the
unit (remove the USB cable) to reboot the it. I obviously lose the data in the
circular buffer, so, depending on when I notice the hang-up, it leads to data
loss of several hours or even days.
I power the WH1080 thro
Hi All,
I'm a newbie looking for hardware suggestions and I don't seem to be
finding exactly what I want. But that's probably because I'm a newbie!
I've done some searching and found some questions that are frequently asked
newbies such as myself:
- do you want an integrated sensor clust
No expert here but this may be something to do with the mtp-probe.
If I plug my usb dongle into a systemd Pi I get...
Dec 12 09:12:21 weewx-public kernel: [2549795.987157] usb 1-1.4: new
full-speed USB device number 4 using dwc_otg
Dec 12 09:12:21 weewx-public kernel: [2549796.120625] usb 1-1.4:
Hi,
Short answer - don't know. A single log message provides only limited
information and no context for the error. This message does not appear to
be from weeWX per se but rather from a user developed extension/add-on. Can
you please provide a log extract showing (at least) one full archive pe
That fixed it. Thank you for your help. I appreciate you and the forum.
--
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.
Fo
Hi,
I've remarked I have this repeating error in my logs: " GaugeGenerator:
Cannot decode reading of 'None' for gauge 'windRose'"
Any idea how to resolve this?
Yves,
YMartin.com/meteo
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscr
Hi Miguel,
On 5 December 2017 at 02:27, Miguel Andres wrote:
> Hello,
>
>
> I have been suggested to post this question to this group as a weewx-user
> group instead of the issues in github.
>
>
> I have read issue 77 and has helped but --readings do not seem to show...
>From what you have show
On Monday, December 11, 2017 at 3:00:04 PM UTC-5, Gene Matthews wrote:
>
>
> [StdWXCalculate]
> [[Calculations]]
> pressure = software
> barometer = prefer_hardware
> altimeter = software
>
gene,
you specified that pressure should be calculated in software, so weewx
i
here is the weewx.conf file from /etc/weewx/
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2015 Tom Keffer
# See the file LICENSE.txt for your rights.
##
# This section is for general configuration information.
# S
Here is the out put from wee_dev9ce --info
gene@ayresboys:~ $ sudo wee_device --info
Using configuration file /etc/weewx/weewx.conf
Using WS28xx driver version 0.35 (weewx.drivers.ws28xx)
Querying the station for the configuration...
alarm_flags_other: 0
alarm_flags_wind_dir: 0
checksum_in: 1723
Here is the log from startup:
Dec 11 11:41:51 ayresboys weewx[2608]: Stopping weewx weather system:
weewx..
Dec 11 11:41:51 ayresboys systemd[1]: Stopped LSB: weewx weather system.
Dec 11 11:43:19 ayresboys systemd[1]: Starting LSB: weewx weather system...
Dec 11 11:43:20 ayresboys weewx[2721]: e
gene,
please post your weewx configuration, and please post the log from the time
that weewx starts up until after one or two archive periods.
the log snippet you posted is only the last 50 lines of syslog, so we
missed all of the startup information.
m
--
You received this message because y
Thanks for the response, I appreciate it. Here is the data from the
directly run weewxd.
REC:2017-12-11 09:50:00 PST (1513014600) altimeter: None, appTemp:
28.4346697916, barometer: None, cloudbase: 1334.85395765, dateTime:
1513014600, dewpoint: 29.4874425863, ET: None, heatindex: 32.36,
Dear Howard,
Thank your your post. May I rise your attention to my post dated Dec 4
titled
[weewx-user] --reading failure in weewx_3.8.0-1 and weewx-owfs-0.21
Raspberry Pi & DS18B20
It may not provide a solution but it certainly shows that there is an issue
here as I ran my tests with the same se
I recently decided to upgrade my RPi running weewx 3.5 on the Debian 8
Wheezy based Raspbian to weewx 3.8 running on the new Debian 9 Stretch
Raspbian.
When the 1-wire adapter is plugged into the usb socket, syslog shows
Dec 7 17:33:27 wx kernel: [436943.136563] usb 1-1.5: new full-speed USB
d
Thank's for your answer.
I am having some "extrange" problem with wlink driver.
It is only downloading data from archive, not real time data.
This is my debug: What do you think?
It downloads only data around 60 minutes past.
Using verbosity=1, displaying most info
wee_debug output will be se
Ok, just saw the subject so scrub step 1.
Gary
On Monday, 11 December 2017 18:58:29 UTC+10, gjr80 wrote:
>
> Hi,
>
> I am guessing you are using rapid fire with WU? Rapid fire is based upon
> loop packets whereas the aprs extension takes its timing and data from
> archive records. For some reas
Hi,
I am guessing you are using rapid fire with WU? Rapid fire is based upon
loop packets whereas the aprs extension takes its timing and data from
archive records. For some reason there will be wind speed data in your loop
packets (and hence WU is happy) but there is no wind speed data in your
Run this command:
sudo /usr/bin/wee_device --info
and post the results.
--
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.
30 matches
Mail list logo
