Thanks, Tom!
Here is the output using your vantage.py. This first is from my Vantage Vue.
Keep scrolling because at the and there is the output from the Vantage Pro,
from the other Raspberry, using the same modified vantage.py.
Also, looking at Vantage Pro weewx's database, as expected, there
Tom, thanks for your continuing investigations! I’m afraid I am out of town
for the next few days so I won’t be able to get back to you till early/mid
next week with any new info.--
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe
Hi, guys. First, sorry about any mistakes. My english isn't the best...
I have 2 Raspberrys and I did a fresh 4.6.2 installation on both, via
apt-get install weewx.
RPi #1 has a Vantage Pro 2. Everything worked well out of the box.
RPi #2 has a Vantage Vue. Evetything seems to work, except in
Rob, it occurs to me that the origins of the REC archive record wasn't
clear in the weewxd output that you posted. Could you run the instrumented
version of vantage.py again, but this time capture the output through the
generation of an archive record? I believe your archive interval is 60
Thanks, I thought I'd fixed that!
On Thursday, February 17, 2022 at 8:34:24 PM UTC-8 gjr80 wrote:
> Rob,
>
> Not that I think it has anything to do with the issue at hand but I
> suspect you have the incorrect sign on your station longitude, unless of
> course your station is actually in
That's the setting in weewx.conf, not the console. The console setting
appears correct.
Gary
On Friday, 18 February 2022 at 14:34:24 UTC+10 gjr80 wrote:
> Rob,
>
> Not that I think it has anything to do with the issue at hand but I
> suspect you have the incorrect sign on your station
Rob,
Not that I think it has anything to do with the issue at hand but I suspect
you have the incorrect sign on your station longitude, unless of course
your station is actually in Zalantun, Mongolia. :)
Gary
On Friday, 18 February 2022 at 13:28:55 UTC+10 robcr...@gmail.com wrote:
> No,
Everything looks normal there. I'll have to give this a think.
On Thu, Feb 17, 2022 at 7:28 PM Rob Cranfill wrote:
> No, thank *you*! :-)
>
>
> On Thursday, February 17, 2022 at 6:44:34 PM UTC-8 tke...@gmail.com wrote:
>
>> Hmm, the RAW and LOOP packets are as to be expected, yet the archive
>>
No, thank *you*! :-)
On Thursday, February 17, 2022 at 6:44:34 PM UTC-8 tke...@gmail.com wrote:
> Hmm, the RAW and LOOP packets are as to be expected, yet the archive
> records contain the unwanted data. Something is injecting the bogus data
> into the data stream. Another request: run
>
>
Hmm, the RAW and LOOP packets are as to be expected, yet the archive
records contain the unwanted data. Something is injecting the bogus data
into the data stream. Another request: run
*wee_debug --info --output=/var/tmp/sanitized.txt*
Look through /var/tmp/sanitized.txt to make sure that it
Your wish is my command! :-)
On Thursday, February 17, 2022 at 5:52:21 PM UTC-8 tke...@gmail.com wrote:
> That's great, but now you have my curiosity piqued! All of the channels
> have been shut off, yet the driver is still emitting values? How can this
> possibly be?
>
> Would you mind
I do still see various "soil" and "leaf" values in the REC & LOOP data, but
I'm happy now that I've simply removed the unwanted graphs from the
"plot_groups" entry in Seasons' skin.conf file. (as seen
at http://robcranfill.net/weather/ :-) )
REC:2022-02-17 11:32:00 PST (1645126320)
Rob, I'll be curious to hear whether you continue to get bogus database
entries after doing this.
On Wed, Feb 16, 2022 at 11:50 AM Rob Cranfill wrote:
> Aha, I see that now in the 'info' output.
>
> After repeated applications of the proper wee_device command,
>
> wee_device
Aha, I see that now in the 'info' output.
After repeated applications of the proper wee_device command,
wee_device --set-transmitter-type=*N*,10
I now have:
TRANSMITTERS:
Channel Receive Repeater Type
1 active noneiss
2 inactivenone
hello,
I just upgraded to 4.6.2-1.deb, so far so good.
to be continued.
Patrick
Le 15/02/2022 à 20:35, Tom Keffer a écrit :
For some reason, every channel in your console is active. You can try
shutting them all off except the ISS. Either do it through the console
( see your owners manual),
For some reason, every channel in your console is active. You can try
shutting them all off except the ISS. Either do it through the console (
see your owners manual), or wee_device can do this.
Generally the ISS is on channel 1.
On Mon, Feb 14, 2022 at 5:37 PM Rob Cranfill wrote:
> Well that
So where are the extra leaf1+2 and soil1+2+3+4 (apologies for my earlier
typos) sensors coming from ?
Are there references to any of them in your skin.conf or weewx.conf files ?
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe
Well that 'splains it! :-) I'll set about removing those (and cleaning up
the DB, right? As detailed elsewhere in this thread?)
As requested,
pi@pi3b:/etc/weewx $ wee_device --info
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.2.3 (weewx.drivers.vantage)
Unable
Rob,
Before this version, weewx only reported on explicit tags. For example, if
you didn't put $current.soilTemp1 in the template, you were not going to
see it in the report.
Now it basically reports on everything that's in the database.
To stop it, look in the skin.conf file for the Seasons
First, I guess I'm just confused as to why I'm getting all this good stuff
when my previous (<4.6) installation was happy for so long.
I just did a quick 'grep' looking around, and I do see that the standard
Seasons skin *defines* a bunch of these unwanted values. Is that enough to
cause
(oops - degree_F there)
On Monday, February 14, 2022 at 11:27:03 AM UTC-8 vince wrote:
> You have to have something mapped to a lot of leaf and soil sensors.
> We'd need to see all your skin.conf files and your weewx.conf file to know
> for sure where they're coming from. If you can't
You have to have something mapped to a lot of leaf and soil sensors. We'd
need to see all your skin.conf files and your weewx.conf file to know for
sure where they're coming from. If you can't find it, I'd suggest you use
StdQC to just filter out the extraneous things (link to User's Guide)
Here is my user dir:
pi@pi3b:~ $ ls -l /usr/share/weewx/user/
total 232K
-rw-rw-r-- 1 root root 140K Jul 1 2021 belchertown.py
-rw-r--r-- 1 root root 31K May 9 2020 cmon.orig
-rw-r--r-- 1 root root 32K May 9 2020 cmon.py
-rw-r--r-- 1 root root 541 Jul 14 2019 extensions.py
-rw-r--r-- 1
On Sunday, February 13, 2022 at 1:09:29 AM UTC-5 roger...@gmail.com wrote:
> 1) This was the first time have run it directly :)
> pi@weather-pi:/etc/weewx/scripts $ sudo ./weewxd
> REC:2022-02-12 21:50:00 PST (1644731400) 'altimeter': '30.2184565672
> <(218)%20456-5672>', 'appTemp':
On Saturday, February 12, 2022 at 3:47:09 PM UTC-5 robcr...@gmail.com wrote:
> Matthew,
>
> pi@pi3b:/etc/weewx $ wee_extension --list
>
> Extension NameVersion Description
> Belchertown 1.2 A clean modern skin with real time streaming
> updates and interactive charts. Modeled
1) This was the first time have run it directly :)
pi@weather-pi:/etc/weewx/scripts $ sudo ./weewxd
REC:2022-02-12 21:50:00 PST (1644731400) 'altimeter': '30.2184565672',
'appTemp': '48.4549536262', 'barometer': '30.219', 'cloudbase':
'1622.11179175', 'consBatteryVoltage': 'None',
I would be very surprised if Belchertown is adding data to the database as
it is an extension that generates output only, as far as I can see it does
not contain any code to add data to loop packets/archive records nor
add/alter any archive records to/in the database.
wee_extension --list
Matthew,
pi@pi3b:/etc/weewx $ wee_extension --list
Extension NameVersion Description
Belchertown 1.2 A clean modern skin with real time streaming
updates and interactive charts. Modeled after BelchertownWeather.com
cmon 0.20 Collect and display computer health
Matthew - I run the same purpleair extension and version. It just grabs
some simple AQ stuff. And sends it to a secondary db.
CREATE TABLE archive (`dateTime` INTEGER NOT NULL PRIMARY KEY, `usUnits`
INTEGER NOT NULL, `interval` INTEGER NOT NULL, `purple_temperature` REAL,
`purple_humidity`
On Saturday, February 12, 2022 at 11:23:24 AM UTC-5 roger...@gmail.com
wrote:
> purpleair 0.1 Collect Purple Air air quality data.
>
this *might* be the culprit. you can verify by:
1) run weewx directly, then post here a few LOOP packets and REC records
from that. that will
Hi Matthew,
pi@weather-pi:/usr/share/weewx $ wee_extension --list
Extension NameVersion Description
Belchertown 1.2 A clean modern skin with real time streaming
updates and interactive charts. Modeled after BelchertownWeather.com
purpleair 0.1 Collect Purple Air
On Saturday, February 12, 2022 at 1:26:42 AM UTC-5 roger...@gmail.com wrote:
> Any pointers on where to look?
>
roger and rob,
what extensions do you have on your weewx system?
some extensions use existing database fields to store data instead of
adding to the schema. is this the case on
Hi Matthew,
It does look like there is something putting data in for those sensors.
There are still inserts taking place, some in the last few minutes.
select dateTime,leafTemp1 from archive;
1644646200|-88.0
1644646500|-88.0 <---Friday, February 11, 2022 10:15:00 PM GMT-08:00
I too am seeing reports from sensors I don't have - leaf and soil temp and
moisture, from my 4.6.2 (upgraded via apt) and a VantageVue.
I look forward to hearing more on this, and I'll let y'all know if I figure
anything out.
On Thursday, February 10, 2022 at 6:14:09 PM UTC-8
On Friday, February 11, 2022 at 12:57:24 PM UTC-5 ales.b...@gmail.com wrote:
> Or is simulator now enabled? :-( I'm confused what's going on after the
> upgrade, I'm new to weewx, so perhaps sorry for silly questions
>
ales,
which driver do you usually use? did your installation change to
On Friday, February 11, 2022 at 10:41:12 AM UTC-5 jonatha...@gmail.com
wrote:
> On Fri, 2022-02-11 at 00:52 -0800, Jonathan Ryshpan wrote:
>
> On Thu, 2022-02-10 at 20:48 -0800, Roger L wrote:
>
> Removing those lines did indeed fix the title bar. That fix worked!
>
> I am still seeing this
On Friday, February 11, 2022 at 3:39:54 PM UTC-5 ales.b...@gmail.com wrote:
> Hi Matthew,
> lang/en.conf did help, I just forgot to /etc/init.d/weewx restart, I feel
> ashamed. Same for the simulator instead of observer, everything back to
> life after restart and 5 minutes...
>
a change to
Hi Matthew,
lang/en.conf did help, I just forgot to /etc/init.d/weewx restart, I feel
ashamed. Same for the simulator instead of observer, everything back to
life after restart and 5 minutes...
Thanks for help.
Dne pátek 11. února 2022 v 18:57:24 UTC+1 uživatel Aleš Berka napsal:
> Still the
Still the same, even with unit_system = metric in lang/en.conf...
By the way, do you think my data are broken since upgrade or is just this
issue with display units?
See attachment.
[image: Screenshot_119.png]
Or is simulator now enabled? :-( I'm confused what's going on after the
upgrade, I'm
On Fri, 2022-02-11 at 00:52 -0800, Jonathan Ryshpan wrote:
> On Thu, 2022-02-10 at 20:48 -0800, Roger L wrote:
> > Removing those lines did indeed fix the title bar. That fix
> > worked!
> >
> > I am still seeing this lines below. I have not seen from 'leafTemp1
> > ' onward before.
> I think
On Thursday, February 10, 2022 at 11:38:23 PM UTC-5 roger...@gmail.com
wrote:
> Here are the last few lines of the select statement. I did not see any
> null values.
>
> 1644552300|-89.0
> 1644552600|-89.0
> 1644552900|-89.0
> 1644553200|-89.0
> 1644553500|-89.0
> 1644553800|-89.0
>
On Friday, February 11, 2022 at 6:56:46 AM UTC-5 ales.b...@gmail.com wrote:
> However I don't understand what's changed, my reports are in US / Imperial
> units, although I have changed
>
could you try setting `unit_system = metricwx` in the `lang/en.conf` file
instead of in defaults?
--
On Thursday, February 10, 2022 at 11:48:28 PM UTC-5 roger...@gmail.com
wrote:
> Removing those lines did indeed fix the title bar. That fix worked!
>
> I am still seeing this lines below. I have not seen from 'leafTemp1 '
> onward before.
>
thank you, roger. if you remove the data for the
Hi,
I have upgraded 4.5.1 using debian package to 4.6.1 and also had the
trouble with titlebar.inc - I have fixed it thanks to posts above.
However I don't understand what's changed, my reports are in US / Imperial
units, although I have changed
[[Defaults]]
# Which language to
I installed it from the Docker image: mitct02/weewx:4.6.1 and see the
problem as well.
On Friday, February 11, 2022 at 3:53:11 AM UTC-5 jonatha...@gmail.com wrote:
> On Thu, 2022-02-10 at 20:48 -0800, Roger L wrote:
>
> Removing those lines did indeed fix the title bar. That fix worked!
>
> I
Here is part of the output during the install:
Configuration file '/etc/weewx/skins/Standard/index.html.tmpl'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I :
Removing those lines did indeed fix the title bar. That fix worked!
I am still seeing this lines below. I have not seen from 'leafTemp1 '
onward before.
Today
Outside Temperature
77.7
38.8
°F
Heat Index
76.3
37.8
°F
Wind Chill
77.7
37.7
°F
Dew Point
44.3
35.0
°F
Humidity
88
I believe that I did an upgrade, but not sure. I ran this command 'sudo
apt-get install weewx' and was asked about replacing files, I selected the
default values for each question.
Here are the last few lines of the select statement. I did not see any null
values.
1644552300|-89.0
On Thursday, February 10, 2022 at 10:25:24 PM UTC-5 rcst...@gmail.com wrote:
> Awesome, thanks! Should I wait for 4.6.2 and live with this a few days, or
> should I go ahead and fix the titlebar.inc? Thanks again!
to fix titlebar.inc, just remove these lines:
$show_rss $show_reports
Awesome, thanks! Should I wait for 4.6.2 and live with this a few days, or
should I go ahead and fix the titlebar.inc? Thanks again!
On Thursday, February 10, 2022 at 7:24:04 PM UTC-8 matthew wall wrote:
> On Thursday, February 10, 2022 at 10:04:36 PM UTC-5 rcst...@gmail.com
> wrote:
>
>> in
On Thursday, February 10, 2022 at 10:04:36 PM UTC-5 rcst...@gmail.com wrote:
> in my case I did an upgrade. I too have a Vantage Vue, but am not seeing
> those other values.
thank you, ryan. the junk in the titlebar was my mistake - i inadvertently
copied some diagnostic code in
in my case I did an upgrade. I too have a Vantage Vue, but am not seeing
those other values.
You can see what I'm seeing here: https://www.staze.org/weewx/
On Thursday, February 10, 2022 at 6:29:54 PM UTC-8 matthew wall wrote:
> On Thursday, February 10, 2022 at 9:14:09 PM UTC-5
On Thursday, February 10, 2022 at 9:14:09 PM UTC-5 roger...@gmail.com wrote:
> I am seeing the same after the upgrade. Also, I am also seeing output of
> sensors I do not have on my Vantage Vue.
> All worked with v4.6.0
>
when you installed 4.6.0, was that an upgrade or a new install? how
Hmmm, I'll check with Matthew and see what's going on.
On Thu, Feb 10, 2022 at 6:14 PM Roger L wrote:
> I am seeing the same after the upgrade. Also, I am also seeing output of
> sensors I do not have on my Vantage Vue.
> All worked with v4.6.0
>
> Additional output not seen with v4.6.0
>
I am seeing the same after the upgrade. Also, I am also seeing output of
sensors I do not have on my Vantage Vue.
All worked with v4.6.0
Additional output not seen with v4.6.0
leafTemp1
-89.0
-90.0
°F
leafTemp2
-82.0
-82.0
°F
leafWet1
1
0
leafWet2
8
8
soilTemp1
-89.0
-90.0
°F
I'm now seeing what seems like debug info at the top of Seasons after
upgrade.
"True True
['outTemp', 'heatindex', 'windchill', 'dewpoint', 'outHumidity',
'barometer', 'windSpeed', 'rain', 'rainRate', 'UV', 'radiation',
'lightning_strike_count', 'inTemp', 'inHumidity', 'extraTemp1',
56 matches
Mail list logo
