udo mkdir /var/www/html/weewx
> sudo chown ${WEEWXUSER}:${WEEWXUSER} /var/www/html/weewx
> ln -s /var/www/html/weewx /home/${WEEWXUSER}/weewx-data/public_html
>
>
> On Friday, April 26, 2024 at 7:53:03 AM UTC-7 Remy Lavabre wrote:
>
>> 1/ if I try xxx.xxx.xxx.xxx/index.html -&g
l *and* xxx.xxx.xxx.xxx/weewx/index.html does not
work...
Any idear ??
Le vendredi 26 avril 2024 à 15:46:48 UTC+2, p q a écrit :
> Looks like a rights issue with Apache. Find the apache.conf file and you
> probably need to enable access to the right directories.
>
> On Fri, Ap
Hello,
Good morning,
I didn't find the answer to my problem in the various discussions on the
WeeWX forum...
I installed Weewx 5 in a virtual environment.
So I have my weewx-data and weewx-venv directories in /home/---/
weewxd seems to "finally" work normally with the ~/weewx-data/public_html
ps://www.weewx.com/docs/5.0/utilities/weectl-debug/> to post a copy
> of your configuration file. Be sure to also set debug=1, restart, then post
> a copy of the log. It will have important startup clues.
>
>
> On Thu, Apr 25, 2024 at 8:30 AM Remy Lavabre
> wrote:
>
>> Good
Good morning,
My configuration under weewx 4.10.2 works perfectly with a custom driver.
I'm "desperately" trying to upgrade to weewx 5 under virtual environment.
-> Configuration with the basic driver simulating the data works ok.
-> When I try with my driver, I get the following response:
Good morning,
Small question(s) for a PIP installation:
1/ Is there a difference between:
- the use of the weewx daemon
- the weewxd command placed in the contrab at the RPi starting
- the manually typed command "nohup weewxd &"?
2/What is the interest/advantage of one method compared to
Tom Keffer a écrit :
> Thank you, Matthew. I had totally forgotten that older weewx.conf files
> set WEEWX_ROOT=/
>
> Remy: as Matthew asked, do you know how your weewx.conf came to be in its
> state? Did you copy it from a previous debian install?
>
> On Fri, Mar 1, 2024 at 6:3
nstalling extension awekaswx from awekaswx.zip
:ooo
Le vendredi 1 mars 2024 à 15:34:55 UTC+1, Remy Lavabre a écrit :
> Hi Matthew,
> Thank you for your help !
>
> *--->>> /etc/weewx does not exist*
> remy@remy-virtual-machine:/etc$ cd weewx
> bash: cd: weewx:
Hi Matthew,
Thank you for your help !
*--->>> /etc/weewx does not exist*
remy@remy-virtual-machine:/etc$ cd weewx
bash: cd: weewx: Aucun fichier ou dossier de ce type
>>>
*# Root directory of the weewx data file hierarchy for this
stationWEEWX_ROOT = /*
*The weewx.conf file
fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory:
'/etc/weewx/bin/user/ws6in1.py'
Le vendredi 1 mars 2024 à 14:21:47 UTC+1, Remy Lavabre a écrit :
> (weewx-venv) remy@remy-virtual-machine:~/weewx-data$* weectl extension
> install AWEKAS.zip --verbo
, I do want it. I am unable to reproduce the problem. It's possible
>> the problem is with how the extension has been packaged.
>>
>> On Thu, Feb 29, 2024 at 1:43 PM Remy LAVABRE wrote:
>>
>>> I do not think that the problem come from awekaswx.py.
>>> The
, Tom Keffer a écrit :
> You sent it for the "Unrecognized type" error, not the "No such file"
> error.
>
> Could you send me the entire file AWEKAS.zip and I will try it on my end?
>
> -tk
>
> On Thu, Feb 29, 2024 at 1:19 PM Remy LAVABRE
> wrote:
>
(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory:
'/etc/weewx/bin/user/awekaswx.py'
(weewx-venv) remy@remy-virtual-machine:~/weewx-data$
Le jeudi 29 février 2024 à 22:19:57 UTC+1, Remy LAVABRE a écrit :
> Sorry Tom but I’ve already send you
rminal? It
> should tell you which configuration file it is using. That will tell us
> what it expects WEEWX_ROOT to be.
>
> On Thu, Feb 29, 2024 at 10:13 AM Remy LAVABRE
> wrote:
>
>> Sorry Tom, I don’t understand what you want exactly...
>>
>> Le jeu. 29 févr. 2
Sorry Tom, I don’t understand what you want exactly...
Le jeu. 29 févr. 2024, 17:45, Tom Keffer a écrit :
> How about the transcript? What did you see when you ran weectl?
>
> On Thu, Feb 29, 2024 at 8:05 AM Remy Lavabre
> wrote:
>
>> Feb 29 17:03:12 remy-virtual-machi
> more of the log. It will tell you what WEEWX_ROOT is.
>
> Also, it would be useful to see the full transcript when you ran weectl
> extension install, not just the error.
>
> -tk
>
> On Thu, Feb 29, 2024 at 7:53 AM Remy Lavabre wrote:
>
>> Ok thank
y'(weewx-venv)
remy@remy-virtual-machine:~/weewx-data$ *
*Thank you once again! :-(*
Le jeudi 29 février 2024 à 16:40:17 UTC+1, Tom Keffer a écrit :
> On Thu, Feb 29, 2024 at 12:01 AM Remy Lavabre wrote:
>
>> Hello Tom,
>> in your doc (
>> https://github.com/weewx/weewx/wiki/
Yesss ! Thank's Gary!!! We progress... :-)))
BUT... :-(((
Now with *from weecfg.extension import ExtensionInstaller or from setup
import ExtensionInstaller the error* in install.py, the error is :
(weewx-venv) remy@remy-virtual-machine:~/weewx-data$ weectl extension
install awekas.zip
Using
Hello Tom,
in your doc
(https://github.com/weewx/weewx/wiki/Weewx-Driver-Development-Tips), you
say :
*A basic skeleton for your file might look like the one below.from setup
import ExtensionInstaller...*
Le jeudi 29 février 2024 à 08:50:33 UTC+1, Remy LAVABRE a écrit :
> *with* : un
til.copy(source_path, destination_path)
>> File "/usr/lib/python3.8/shutil.py", line 418, in copy
>> copyfile(src, dst, follow_symlinks=follow_symlinks)
>> File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
>> with open(src, 'rb') as fsrc, op
='awekaswx',
description='Get Bresser 7in1 data on Awekas',
author="Remy LAVABRE",
author_email="remy.lava...@gmail.com",
files=[('bin/user', ['bin/user/awekaswx.py'])]
)
*We have :*
(weewx-venv) remy@remy-virtual-machine:~/weewx-
3.8/shutil.py", line 264, in copyfile
with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory:
'/tmp/tmprpxo6tw5/AWEKAS/bin/user/awekaswx.py'
*and the install.py :*
# installer for Awekas Bresser awekaswx driver
# Copyright 2024 Rem
Sorry, small error on my part, it's not "usr" that should be read but "user"
Le dimanche 25 février 2024 à 19:55:27 UTC+1, Remy Lavabre a écrit :
> Hello,
>
> weewx is installed in virtual PIP mode -> ~/weewx-data/... and
> ~/weewx-venv/...
> I manually
Hello,
weewx is installed in virtual PIP mode -> ~/weewx-data/... and
~/weewx-venv/...
I manually added the xxx.py driver for my weather station in the
~/weewx-data/bin/user directory.
It is declared in weewx.conf as "driver = usr.xxx", as was done in version
4.x
When launching weewxd, I get
paramétrer
> le driver interceptor
> Sur le repo github ce n'est pas très clair...
>
> Mon site est ici : https://meteo-pontscorff.fr/ (il y a mes coordonnées
> mail)
> Merci !
> Stéphane
>
> Le samedi 24 février 2024 à 05:49:39 UTC+1, Remy LAVABRE a écrit :
&
stephane hello,
I said something stupid to you previously. interceptor intercepts at the
wifi level and not as I thought at the 400 or 800 Mhz radio level... sorry!
so normal that you have inTemp and barometer! :-)
I too have a Bresser station and retrieve data automatically from Awekas in
the
What is the Bresser station you use Stéphane ?
Normaly no inTemp with bresser and interceptor -> inTemp is given with by
the base and so not radio send as the barometer value...
Le ven. 23 févr. 2024, 23:19, sc.lep...@gmail.com
a écrit :
> Hello
> I use weewx with interceptor :
>
> Feb 23
Good morning,
I've been seeing various problems (mainly access rights?) for some time
with the 5.x update.
For a configuration in 4.10.2 on Pi with Bulleyes 64B, does the transition
to 5.x present risks of malfunction with the use of a modified base skin
(Seasons) but above all:
- A
Good morning,
I have the same outdoor sensor but not the same base.
The exterior sensor works perfectly but does not seem to me to be very
realistic in terms of wind speed. I think we can easily apply a factor x1.5
to get closer to reality...
The minimum amount of rain needed to trigger is
Good morning,
The SteelSeries skin leaves the possibility of displaying weather forecasts.
The gauge-data.txt.tmpl file contains the following lines:
*## if forecasting is installed, report the Zambretti forecast#if
$varExists('forecast.zambretti')#set $fc = $forecast.label('Zambretti',
long time on
the problem...
Thanks again Gary
Le jeudi 25 janvier 2024 à 15:25:38 UTC+1, Remy LAVABRE a écrit :
> hello gary,
> Many thanks for your help and my apologies for the late response as my
> internet connection is currently cut...
> I would never have thought of looking
mit
> 9455fa1
> <https://github.com/weewx/weewx/commit/9455fa17169463c3174f3517bdc652c4f2dd5036>
> .
>
> On Sun, Jan 28, 2024 at 7:30 AM Remy Lavabre wrote:
>
>> thanks Tom,
>>
>> I had thought about putting rain = prefer_software but as this type of
>> rain conf
t;
> ...
> [[Delta]]
> [[[rain]]]
> input = dayRain
>
> On Sat, Jan 27, 2024 at 9:17 AM Remy Lavabre wrote:
>
>> Hello Tom,
>>
>> I followed your instructions:
>>
>> 1/“rain” field present in the database
>> 2/
two
> approaches.
>
> It is not necessary to save "dayRain". WeeWX mostly uses "rain". Besides,
> as you note, it can always be calculated.
>
>
>
> On Fri, Jan 26, 2024 at 7:06 AM Remy Lavabre wrote:
>
>> And one more question
>>
janvier 2024 à 15:46:04 UTC+1, Remy Lavabre a écrit :
> Hello Tom and thank you for your response.
>
> [StdWXCalculate]
> [[Calculations]]
> ...
> [[Delta]]
> [[[rain]]]
> input = dayRain
>
> This will ca
ps://github.com/weewx/weewx/blob/master/src/weewx/wxxtypes.py#L586>.
> To use it, add this to weewx.conf:
>
> [StdWXCalculate]
> [[Calculations]]
> ...
> [[Delta]]
> [[[rain]]]
> input = dayRain
>
>
>
>
> On
2023 (a timestamp >= 1690581600).
>> And around this date, I didn't notice anything particular in my
>> database... :-(
>>
>> Le lundi 22 janvier 2024 à 15:23:25 UTC+1, Remy Lavabre a écrit :
>>
>>> Hello Gary,
>>>
>>> I've put what you asked fo
o it
appears to be from July 29, 2023 (a timestamp >= 1690581600).
And around this date, I didn't notice anything particular in my database...
:-(
Le lundi 22 janvier 2024 à 15:23:25 UTC+1, Remy Lavabre a écrit :
> Hello Gary,
>
> I've put what you asked for below.
>
Hello Gary,
I've put what you asked for below.
The problem is systematic (this is an advantage in some way...)
I think you are right about the problem of a field in the database... But
which one?
SteelSeries was working perfectly BEFORE I added/deleted the data base. I
didn't notice the
Hello Gary and thank you for your response.
I have put all the fields in my database below :
[image: WX1.png]
[image: WX2.png]
[image: WX3.png]
[image: WX4.png]
Indeed the error perhaps comes from this side because I deleted fields
which were useless to me and added others...*However I do
Thank-you...
Sorry but in the syslog, there is only that...
And systematically same error at each packetsloop !
if the option is disabled in weewx.conf obviously no problem. :-(
Jan 16 13:56:19 localhost wee_reports[62658] INFO user.alarm_multi: Alarm
set for expression 18: "extraTemp3 is not
-> https://github.com/gjr80/weewx-steelseries
Good morning,
I don't understand the reason and why of the error that occurs with my
version 4.10.2 of weewx and the 'SteelSeries' Skin.
Can anyone help me and tell me what's going on?
THANKS
Jan 20 10:31:21 localhost weewx[16495] ERROR
Good morning,
I created a [driver] for weewx to retrieve data from the Awekas API (my
Bresser weather station does not have a USB port).
This works but regarding the rain, it is not the instantaneous rain (from a
packetloop) that we recover but the rain over 24 hours since midnight.
Is there a
anuary 2024 at 10:27:48 UTC-5 Remy Lavabre wrote:
>
>> Good morning,
>>
>> Wishing to write a driver for WeeWX in order to automatically retrieve
>> and integrate AWEKAS data into the weewx.sbd database, I have a question
>> regarding the manageme
Good morning,
Wishing to write a driver for WeeWX in order to automatically retrieve and
integrate AWEKAS data into the weewx.sbd database, I have a question
regarding the management of "PacketsLoop" data:
The Weewx documentation states that for temperatures, it is an average of
the
t.
>
> On Mon, Nov 20, 2023 at 12:31 AM Remy Lavabre
> wrote:
>
>> Good morning,
>> I previously used weeWX connected to the USB output of my weather
>> station. No problem, the station was well referenced on the world map of
>> WeeWX weather stations.
>>
&
Good morning,
I previously used weeWX connected to the USB output of my weather station.
No problem, the station was well referenced on the world map of WeeWX
weather stations.
Unfortunately my station broke down and an exchange was carried out under
warranty with a new station without a USB
heater_value = 69 if heater else 68
>
> This is assuming US Units. Then you could plot inTemp and heater_value
> together.
>
> On Sun, Nov 5, 2023 at 5:12 AM Remy LAVABRE wrote:
>
>> OK thanks. but would you have an idea about visualizing the on/off state
>> on
ing library in WeeWX is capable of using only one
> y-axis scale. A limitation, to be sure.
>
> On Sun, Nov 5, 2023 at 1:44 AM Remy Lavabre wrote:
>
>> Good morning,
>> A "simple" question (apparently): I have a boolean type variable in my
>> WeeWX databas
ing library in WeeWX is capable of using only one
> y-axis scale. A limitation, to be sure.
>
> On Sun, Nov 5, 2023 at 1:44 AM Remy Lavabre
> wrote:
>
>> Good morning,
>> A "simple" question (apparently): I have a boolean type variable in my
>> WeeWX data
Good morning,
A "simple" question (apparently): I have a boolean type variable in my
WeeWX database (ON/Off state).
Is it possible to show this state in a diagram? For example, draw the curve
of an indoor temperature and at the same time on the graph the "ON" or
"OFF" state of the Boolean
Hello,
Weewx documentation, customisation guide
The Image generator
Le mer. 1 nov. 2023, 00:08, jmltech a écrit :
> Hi,
> I’m using the Season skin 4.9.1, under Weewx 4.10.2
>
> In reading through the group messgaes, and looking at the skin.conf, I see
> a lot of configuration and override
skins that try to calculate something from "a
> month ago", when a month has 31 days and the previous month had 30. What is
> "a month ago" from 31 October? Not 31 September --- it doesn't exist.
>
> See Issue #436 <https://github.com/weewx/weewx/issues/436>.
>
Hello, Weewx 4.5.2 worked perfectly until 2023-10-30 23:55:00
Since this date, the Seasons2 skin no longer updates the index.html file.
The Raspberry is not crashed, the database continues to fill normally and
all graphs are generated normally.
The log trace gives the error below.
Does anyone
Thank you all for all this information which really helped me!
Sincerely
Le mardi 24 octobre 2023 à 11:01:49 UTC+2, Karen K a écrit :
> Remy Lavabre schrieb am Montag, 23. Oktober 2023 um 18:07:30 UTC+2:
>
> Would it be possible to know the WeeWX calculation formula used to obtain
>
Good morning,
Would it be possible to know the WeeWX calculation formula used to obtain
the height of the cloud base in weewx from the outside temperature and the
dew point?
Thank you - Kind regards
--
You received this message because you are subscribed to the Google Groups
"weewx-user"
Hello Gary,
No sorry, it doesn't work anymore.
See below :
#Histogrammes horaires électricité LINKY
[[[daylinky1]]]
yscale = None, None, 1
plot_type = bar
unit = watt_hour
electricityLinky
color = Red
Hello Gary and thank you again for your response.
1/If I put the option chart_fill_colors = Red in [[[daylinky1]]] as you
suggest, it curiously blocks everything. My histogram is not generated but
also the following ones from skin.conf.
If I replace chart_fill_colors = Red in the
Hi.
Skin.conf :
#Histogrammes horaires électricité LINKY
[[[daylinky1]]]
yscale = None, None, 1
plot_type = bar
unit = watt_hour
electricityLinky
chart_fill_colors = Red
color = Red
Good morning,
the option *chart_fill_colors = *is supposed to change the fill color of
the bar charts *(chart_fill_colors: A list of the color to be used as the
fill of the bar charts. Optional. The default is to use the same color as
the outline color ( option chart_line_colors).*
But when
Thank you Gary for all these detailed explanations! Thank you also for your
patience...
Thanks to you I was finally able to finish integrating the data into the
weewx database as I wanted!
Without your precious help, I would* NEVER* have gotten there!
Just one last quick question, if weewx is
Hello and thank you for your answer.
By adding the line weewx.units.obs_group_dict['wetbulbTemp'] =
'group_temperature' to the /usr/share/weewx/user/extensions.py file, the
wetbulbTemp field is now imported correctly.
Thank you for your help !
However, I have a new question as I haven't been able
Thanks Gary,
My fields, including for rain, incremented automatically yesterday for the
first time!
Your solution was the right one and I still don't understand why the
previous time the rain was not taken into account in my weewx database
However, thank you for your explanations which
Thank you very much for your patience Gary,
Indeed I did not provide you with all the data from the CSV file in order
to simplify.
However, the fields were in the correct order with the correct wording.
Regarding the --dry-run command, I actually remove it for integration. This
is why all my
Hi Gary,
I followed your advice:
1/ I now have in the rain field of my csv file the amount of rain that fell
over the previous 5 minutes.
2/ I changed the config file so that rain=discrete is now the config value
Unfortunately, the integration of the csv file in the weewx database with
this new
Thank you Gary for your very quick and detailed response. Nice of you!
I had read the documentation on the Weewx utilities guide but had not
understood it in the sense you indicate...
So I modified my Python program to calculate in the csv file the amount of
water that fell over the 5 minute
*Good morning,I am using the wee_import.py utility to integrate AWEKAS data
into my weewx database.command executed: *sudo wee_import
--config=/etc/weewx/weewx.conf
--import-config=/home/pi/Documents/Bresser7in1/csv-Bresser.conf --dry-run
--verbose
*My CSVFile :*
Thanks Gary for your response.
I added :
import weewx.units
weewx.units.obs_group_dict['wetbulbTemp'] = 'group_temperature'
in file /usr/share/weewx/weecfg/extension.py
It didn't change anything about the problem when using wee_import.py, I
still get the same error.
I specify that I did not
*Good morning,*
*My WeeWX.sdb database works perfectly. I removed all unnecessary fields
with sudo wee_database --drop-columns=XXX,YYY,ZZZ which worked perfectly.I
renamed the field "heatindex1", from the base to "wetbulbTemp" with the
command: sudo wee_database
ive on the
> webserver. WeeWX FTP only moves files from the weewx host to the webserver,
> not the other way around.
>
> On Wed, May 17, 2023 at 5:07 AM Remy Lavabre
> wrote:
>
>> Good morning,
>> Is there a way with the FTP skin not to synchronize a particular file
>> betw
Good morning,
Is there a way with the FTP skin not to synchronize a particular file
between the appache weewx server and a copy at a host, such as a page view
counter file?
THANKS
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe
>$time_since_last_frost.long_form and $time_since_last_rain.long_form work
fine for me with weewx 4.10
[image: Capture d’écran du 2023-02-04 09-31-41.png]
Le samedi 4 février 2023 à 07:23:41 UTC+1, blaise@gmail.com a écrit :
> 02/04/23 07:15:00
> No rain today and
> Since 01/31/23 15:05:00
Hello everyone...
Like you, I use the superb WeeWX software (thanks again for its designers!)
and perhaps the alarm.py extension (or even better, alarm_multi.py).
By slightly modifying alarm.py or alarm_multi.py, it is very easily
possible to receive notifications on your GSM mobile phone (The
, for example. The Pi suddenly shut down with a fresh install, PiOS
lite 64B and no software other than WeeWX and the Python libraries!
The purpose of my message was to know if others had tried WeeWX 24/24 7/7
in 64B on a Pi Zero 2W...
Thank-you...
Le dimanche 2 octobre 2022 à 10:35:27 UTC+2, Remy
Thank you for all the answers.
For information, the Pi Zero 2W is 64N with 512K of memory.
I used it in 64B version in lite version without screen.
I installed a cooler and its temperature is around 42°C on average. So
there is no overheating.
Diagrams over several days show no overhead and no
Good morning all.
I have been using weewx for 3 years with pi os 32B without any problem with
a pi zero w then 2w.
Since I switched to version 64B, I have had lots of incomprehensible
crashes with the pi not responding and having to reset. weewx is not in
question.
I tried to increase the swap,
the value
>> "MinProtocol = TLSv1.2"?
>
>
> Are you saying that we should implement ssl.set_alpn_protocols() as well?
> Do you have a case where that was necessary?
>
> -tk
>
> On Mon, Jun 27, 2022 at 5:48 AM Remy Lavabre wrote:
>
>> Hello again Tom,
another step. In addition to replacing weeutil/ftpupload.py,
> replace weewx/reportengine.py with this copy.
>
> -tk
>
> On Mon, Jun 27, 2022 at 12:56 AM Remy Lavabre wrote:
>
>> Hello Tom and thank you.
>>
>> Unfortunately it does not work (see attached syslog)
>>
max_trie = 3
ftp_encoding = UTF-8
#bug in the Python libraries that happens when use a Pure-FTP server
reuse_ssl = True
Le lundi 27 juin 2022 à 09:56:07 UTC+2, Remy Lavabre a écrit :
> Hello Tom and thank you.
>
> Unfortunately it does not work (see attached syslog)
[SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1123)
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine:
ftpgenerator: Upload failed
Le dimanche 26 juin 2022 à 21:44:40 UTC+2, tke...@gmail.com a écrit :
> Try this version of weeutil/ftpupload.py. It will allow you to set a
er levels, but, before doing that, is
> there any way you can talk your service provider into updating their
> libraries? It's the better approach.
>
> On Sun, Jun 26, 2022 at 12:45 AM Remy Lavabre wrote:
>
>> Hello,
>> I would like to use WeeWX's FTP option.
>> In Python, t
Hello,
I would like to use WeeWX's FTP option.
In Python, this works perfectly (WITH THE OPTION IN BOLD) :
from ftplib import FTP_TLS
import ssl
import requests
HOST='A'
ID = 'B'
MDP = 'C'
def connect():
ftp = FTP_TLS()
ftp.debugging = 2
*
gt;>>>>>>> -if 'windGust' not in data or 'windGustDir' not in data:
>>>>>>>> +"""If windGustDir is missing, substitute windDir.
>>>>>>>> +Set windGustDir to None if windGust is zero."""
>>>>
in data:
>>>>>> raise weewx.CannotCalculate
>>>>>> if self.force_null and data['windGust'] == 0:
>>>>>> +# windGust is zero. Force windGustDir to None
>>>>>> val = None
>>>
gt;>>> +# windGustDir is missing. If available, substitute windDir.
>>>> +if 'windDir' not in data:
>>>> +raise weewx.CannotCalculate
>>>> +val = data['windDir']
>>>> else:
>>
')
>
> Commit 9dc4da8
> <https://github.com/weewx/weewx/commit/9dc4da86a260f01d8792ac93d12871a05bff572d>
> .
>
> If you want this right away, you can replace weewx/wxxtypes.py with this
> version
> <https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/wxxt
[image: Capture d’écran de 2022-02-13 10-14-16.png]
Same problem for me !
Since weewx 4.6.x windGustDir is always N/A but the value is correct.
I never had this problem before with 4.5.x or before... Only since 4.6.x
WindGustDir is always None in loop package values :
LOOP: 2022-02-13
[image: Capture d’écran de 2022-02-13 10-14-16.png]
Same problem for me !
Since weewx 4.6.x windGustDir is always N/A but the value is correct.
I never had this problem before with 4.5.x or before... Only since 4.6.x
Would it be possible to tell me how to get the loop packages so that I can
Same problem for me !
Since weewx 4.6.x windGustDir is always N/A.
Nevers add this problem before with 4.5.x or later...
Le samedi 12 février 2022 à 19:23:27 UTC+1, asla...@gmail.com a écrit :
> The result with a couple of LOOP records.
> Both windGust and windGustDir occur in both REC and Loop
à 20:30:39 UTC+1, Remy Lavabre a écrit :
> Thank you for your answer Vincent.
> Could you indicate me which python file exactly to add the New value
> context='long_delta ? And where I must add this New value in the py file ?
> I have seen the article you indicate me but i did not und
Thank you for your answer Vincent.
Could you indicate me which python file exactly to add the New value
context='long_delta ? And where I must add this New value in the py file ?
I have seen the article you indicate me but i did not understand what to
do...
Than you . Cordialy vincent
Le lundi 7
With the previous version 4.51, no problem since 1 year.
Since 4.6.0 the records are good on the database, but I have errors in the
log file and the value in the "current conditions" of the skin Seasons
don't move.
They remain frozen at the last known value with Weewx 4.5.1. In fact, the
Season
Multi_alarm.py is a super python program for different test alarm on each
loop pack et {ex outTemp<0, rainRate>0, inTemp<17 etc. etc}.
If you want only battery power test, perhaps this is more for you... :
https://github.com/weewx/weewx/blob/master/examples/lowBattery.py
If you want I can send
Hello Rob.
Multi_alarm.py is perfect for the job !
And the battery will be checked at each loop packet record !
After, you can sens à mail or SMS or... all what you want !
;-)
Le lun. 7 juin 2021 à 18:27, Rob Cranfill a écrit :
> Apologies if this has been asked - I searched without luck - let
;>>> Thanks for the quick response! And it actually works :-)))
>>>>>
>>>>> Two slight corrections are however to be made to work fine :
>>>>>
>>>>> -1 / You forgot the "$" at timestamp. We must read
>>>
$month.windSpeed.maxtime*.raw* instead of #set t =
>>> $month.windSpeed.maxtime
>>>
>>> Aside from that it was a perfect solution !! Thanks again Tom
>>>
>>> Le jeudi 3 juin 2021 à 22:41:54 UTC+2, tke...@gmail.com a écrit :
>>>
>>
):
>
> #set t = $month.windSpeed.maxtime
> The max wind speed this month is $month.windSpeed.max from direction
> $current(timestamp=$t).windDir at time $t.
>
>
>
> On Thu, Jun 3, 2021 at 8:38 AM Remy Lavabre wrote:
>
>> Good morning all,
>>
>> To have the maximum wind
Good morning all,
To have the maximum wind gust over a period this works very well and also
gives the time and date of this wind gust:
Win Gust Max
#for $archive in $archive_data
$archive[1].wind.gustdir.ordinal_compass
Hello,
I have a problem with using the barometerRate variable.
In skin :
$obs.label.barometerRate
$current.barometerRate
And the result in HTML is :
Barometer Change Rate ?'barometerRate'?
I don't understand why the "$current.barometerRate" variable is not
reconize
Where is the problem ?
Hi,
I have a problem to with the FTP option :
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine:
ftpgenerator: (0): caught exception '': [SSL:
DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1056)
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine:
Traceback (most
1 - 100 of 118 matches
Mail list logo