Hi Ashley,
I think you presented your station already in 2006 in the weewx group
The relevant portion of your station for the weewx context here are two
pieces:
the legacy WH25 indoor T&HP sensor (nowadays WN32P) and the Fine Offset
WH2600 LAN gateway also known as observer IP.
The pressure read
you probably need to define the units/unit group for pm4_0 in
extensions.py 😎
On 01.08.2024 08:08, j.fri...@gmail.com wrote:
Hi Gary,
the v0.6.3b1 works wery well. There is only one possible issue with
PMI 4. index.html page shows it in other way then others values .
Thank you very much for
not sure if Gary has already considered the new WH46 situation into the
0.6.1 driver version
the API response is different depending on whether a WH45 or a WH46 are
connected to a console/gateway with the local Ecowitt API
- there can only be one WH45/46 connected - either a WH45 or a WH46
*in
mething like the count per
interval and a kind of weighted average for the distance. It exists
for the Tempest, which transmits lightning data using UDP as it
detects a lightning. Apart from the other data which is transmitted in
a constant interval.
Rainer Lang schrieb am Montag, 3. Juni 20
or reports every 79s "Hello, I'm
there" and every detected lightning on top of that, immediately.
If you don't live at Catatumbo River mouth, this shouldn't drain
the battery too much. Let's see if Rainer Lang knows more Details.
Greg Troxel schrieb am Freita
-prompt --driver=weewx.drivers.vantage \
--altitude="400,foot" --latitude=45.1 --longitude=-105.9 \
--location="My Special Station"|
the result should be a properly configured weewx.conf
On 20.03.2024 01:20, Rainer Lang wrote:
try reading (and applying) https://weewx.c
try reading (and applying) https://weewx.com/docs/5.0/hardware/vantage/
On 20.03.2024 01:07, Sidney wrote:
Type: Davis Vantage Pro2/Vue
Station model: WeatherDuino 4Pro DB
Connection: TCP/IP
IP: http://192.168.0.39
Thank you Rainer.
On Wednesday, March 20, 2024 at 12:42:51 AM UTC+1 Rainer Lang
server to get the page load on the local network.
Let's see whats next then. Thanks again.
On Tuesday, March 19, 2024 at 11:54:09 PM UTC+1 Rainer Lang wrote:
@Sidney - I think you are confusing a few things and are
comparing apples with pears.
You may not be aware
...
It is a Sainlogic WS3500 👍.
Thank you for your help.
On Tue, Mar 19, 2024, 21:23 'Rainer Lang' via weewx-user
wrote:
can you post your weewx.conf entries of the [Interceptor] stanza ?
Also a screecopy of your WS View Plus customized server entries
would be helpful.
getting This site can’t be reached. Sorry for probably a
silly question. Appreciate your support. THank you.
On Tuesday, March 19, 2024 at 9:12:41 PM UTC+1 Rainer Lang wrote:
correct, but weewx (its Seasons skin) doesn't have a
realtime dashboard (ex
can you post your weewx.conf entries of the [Interceptor] stanza ?
Also a screecopy of your WS View Plus customized server entries would be
helpful.
I have just run out of my crystal balls ...
And a WS3500 is what ? A Sainlogic WS3500, an Ecowitt WH2910 clone ?
The more precise you are in your
correct, but weewx (its Seasons skin) doesn't have a realtime dashboard
(except you install the mqtt based Belchertown skin).
The update interval is defined in weewx.conf and could go down to one
minute instead of five minutes (in theory - in practice to be found out
if the reports can complete
if you have a webserver installed, entering
http://ip-address-of-the-weewx-server/weewx will show you the last
created Seasons skin
On 19.03.2024 21:06, Sidney wrote:
Hi, I believe I've successfully installed weewx. The manual says:
After about 5 minutes (the exact length of time depends on y
've learnt a great deal so far on this massive learning curve,
but obviously I am not up to this ...yet.
Bear with me whilst I uninstall it all again, and start a fresh again.
Many thanks for the Links, I'm off to do some more reading.
On Mon, Mar 18, 2024 at 7:55 PM
The Ventus W830 is a Ecowitt WH2910 clone. In your mail it is not clear
what "it" means. Your RaspberryPi, weewx, the console ?
Maybe you should first make yourself familiar with your environment,
your setup, the architecture and then see where weewx comes into play.
I suggest you read http
a lighter, the flash of a camera in front of the sensor
On 14.03.2024 18:50, Joachim Puttkammer wrote:
How can I simulate lightning for the WH57 sensor?
--
You received this message because you are subscribed to the Google
Groups "weewx-user" group.
To unsubscribe from this group and stop
I don't think it has changed ... why would it ?
It's a reasonable approach for how and when to copy an active database.
That's independent of the weewx version.
Safest way is always to shutdown weewx (best immediately after the last
archive records were written), then copy, then restart weewx
interesting, but as you didn't give us more context, you're likely not
to receive a satisfactory reply
1. it is good practice to post a _*complete*_ syslog protocol from a
weewx start to at least one archiving and reporting cycle (unless it
doesn't reach it)
2. you should tell us about your co
w and will provide more detailed
log later with debug set to 1.
I may have forgotten to add the Klimalogg installation at GitHub -
matthewwall/weewx-klimalogg: klimalogg pro driver for weewx
<https://github.com/matthewwall/weewx-klimalogg>
/Boris
måndag 11 december 2023 kl. 17:03:56 UTC+1 s
only from the context (and when you know) one can guess that you are
talking about KlimaLogg and the the KlimaLogg extension.
And the messages refer to the tranceiver USB stick through which the
KlimaLogg console communicates with weewx
Are you aware of how the two devices cooperate ?
Did you p
you may have to have your console post its data also via the customized
server functionality to your RPi, using Wunderground protocol, and e.g.
port 8000
and then have your interceptor driver at the weewx end listen at port
8000. Mode would then be listening and not sniffing ! wu-client to be
c
hanks for that, very useful.
I guess what I meant by 'compatible' was the "Supported Hardware"
list on https://weewx.com/hardware.html, almost all of which
appear unobtainable.
On 07/12/2023 11:22, 'Rainer Lang' via weewx-user wrote:
Not sure wha
Not sure what you mean by "compatible" here - but beyond Davis there is
a whole station/sensor/IoT universe
Have a look at https://www.ecowitt.com
and for a better understanding
https://www.wxforum.net/index.php?topic=40730
all these stations can be used with weewx with either the Ecowitt local
ake the console sound guilty, but with that
said, that number is most correct. Confusing.
But I'll then post the findings here, and possibly some code so that
this thread can have the usefulness to others in the future.
Thank you
Marlon
On Monday, 06 November 2023 at 09:04:02 UTC
summary data shown on the ecowitt.net dashboard are the values from the
console and can be changed by the user in the console. At ecowitt.net no
summarizing is done for the displayed tiles, just display of what the
console sends. What is shown there is user responsibility. If the user
makes adj
nfig set to cumulative (since ecowitt does not export yearly).
Sharing the new config, csv and logs as you requested. You should be
able to compare now, Rainer.
Hope I can find a way to thank you and Gary for the help.
On Sunday, 05 November 2023 at 02:23:37 UTC+2 Rainer Lang wrote:
can you remov
can you remove all lines with ";;" from the import CSV file
and start the import again (I assume you still have an untouched copy of
your database),
re-create the NOAA reports and check again ...
The NOAA reports from your web site is the only place where I could
compare the import
lid.
WeeWX is storing rain somewhere and forgetting about it when it
creates graphs and reports? :D
Sorry, I am as desperate to solve this as I am confused. Two full
days on this now, feeling the pain.
On Wednesday, 01 November 2023 at 10:34:11 UTC+2 Rainer Lang wrote:
An
=40730.0 in English -
not as extensive but the best on the web in English language
by the same author
On 01.11.2023 09:27, Rainer Lang wrote:
I think you have to understand better how weewx works:
even if you set a archive interval of 300 seconds (5 minutes), each
data packet sent by your
should be divisible by my console's abilities.
As for the driver, thanks. Didn't know Interceptor was so outdated.
Unfortunately, I am not sure what else my froggit/fineOffset WH3000
can use. I couldn't get the standard ones to work.
Appreciated.
Marlon
On Wednesday, 01 Nov
a) you should use an interceptor driver version which cleanly handles
all your sensors - and also those you don't have
the original version on GitHub was never extended and is a crippled
version from a today's point of view as it covers the basic sensors only
and its exclusion field-map is incom
the download from the Ecowitt cloud is not fully based on their public
http-API - it rather offers a "canon ball" solution as the author says
for details about the API see https://doc.ecowitt.net/
if you want to develop your own thing or create a more specific solution
using the accounts APP an
you can install (unless already installed) the ncdu tool:
sudo apt-get install ncdu
and you'll have to run it in the root directory in a console window on
your RPi
it will give you a nice and complete overview which directories use
which storage capacity down to the files
On 18.10.2023 13:57,
25:24 fedora-workstation python3[53515]: weewx[53515]
CRITICAL weewx.engine: ^
Oct 17 15:25:24 fedora-workstation python3[53515]: weewx[53515]
CRITICAL weewx.engine: File
"/usr/share/weewx/user/gw1000.py", line 2311, in __init__
Oct
I meant of course
set *debug = 3*
Forwarded Message
Subject:Re: [weewx-user] Re: Cannot get weewx + gw1000 working
Date: Tue, 17 Oct 2023 15:32:48 +0200
From: Rainer Lang
To: weewx-user@googlegroups.com
it's difficult to follow what you are/were doing
it's difficult to follow what you are/were doing - it would be helpful
if you
a) provided us with a copy of your weewx.conf (you can your
passwords if there are any)
b) set your station to GW1000
c) set debug = 0
d) provided the complete syslog from weewx startup until either the 1st
repor
ut it into
software calculation
On Saturday, 14 October 2023 at 13:27:22 UTC+1 Rainer Lang wrote:
nothing is "amiss" in the "WS90 software", whatever you mean
by this.
I think you have a wrong understanding of the hardware you are
nothing is "amiss" in the "WS90 software", whatever you mean by this.
I think you have a wrong understanding of the hardware you are using and
its (assumed) capabilities.
1. Tom's hint will solve your issue in weewx, as the observations you
are asking for are not primary observations but deriv
sent my reply only privately by mistake - here for the group to benefit
to the group too
Forwarded Message
Subject:Re: [weewx-user] Correct data in weewx.sdb
Date: Tue, 19 Sep 2023 13:58:30 +0200
From: Rainer Lang
To: bgra...@umw.edu
the easiest way imo is
if you are going for a Ecowitt (clone) station, - look up
https://www.wxforum.net/index.php?topic=40730.0 to see what's available
from them these days and what they are able to do - then weewx will be
able to read their data which they all send via WLAN ("WiFi") to the
local network and/or the
to calibrate your WS-1001 (Ambient version of the FineOffset/EcowittWH24
outdoor array and the WH1080 console) you could just follow the
instructions in https://www.wxforum.net/index.php?topic=40730.0 chapter 6
determine the offset and enter it accordingly (either an offest of
change the value,
yes - why not calibrate your console first
when you see that the offset between absolute and relative pressure for
your location used is wrong, just adjust it 😎
the the first basic step I'd say
even though, when your absolute (=local) pressure reading is correct,
and your have the weewx option
lping
Rgds
Gert
On Tuesday, August 15, 2023 at 11:18:22 AM UTC+2 Rainer Lang wrote:
I think a simple solution could be to extract the file gw1000.py
from the gw1000-0.5.0b5.tar.gz archive and copy it to
/usr/share/weewx/user
On 15.08.2023 10:42, gert.a...@gmail.com wrote:
H
I think a simple solution could be to extract the file gw1000.py from
the gw1000-0.5.0b5.tar.gz archive and copy it to /usr/share/weewx/user
On 15.08.2023 10:42, gert.a...@gmail.com wrote:
Hi Ian
Thanks for looking.
I used this command to install WeeWx:
sudo apt install ./python3-weewx_5.0.0a2
FULL
the others have a 5 or 6 tier status information
those with voltage can be simply display "as is": x.x V
On 14.08.2023 12:38, Greg Troxel wrote:
"'Rainer Lang' via weewx-user" writes:
the driver only collects the data provided by the gateway API - and if
the driver only collects the data provided by the gateway API - and if
you have created corresponding fields and assignments, weewx stores this
data in the data base. That's it.
There is no further code as far as I am aware of.
Can you tell what exactly you want to do ?
Display the codes as hum
ly a type mismatch as you say.
Just wonder, if I map wh51_ch1_batt to /BatteryStatus2/, I need to
mention /BatteryStatus2/ in extension.py. righ?
Rainer Lang schrieb am Donnerstag, 10. August 2023 um 12:51:54 UTC+2:
in principle all seems to be correct in weewx.conf
now, how to check
in principle all seems to be correct in weewx.conf
now, how to check the database: get yourself the sqlitebrowser and look
it up yourself
sudo apt-get install sqlitebrowser
you will have to load your database and you can see everything, all
records etc.
but you may have a unit problem as
3 19:20:24 +0200
From: Rainer Lang
To: weewx-user@googlegroups.com
this is normal as the standard interceptor.py code doesn't have a
complete label map to handle these labels 😁
Matthew hasn't found the time to extend it - others had to do this
try the attached one (intercept
ed parameter gain50_piezo=1.00
Aug 6 13:05:12 raspberrypi weewx[18619] INFO user.interceptor:
unrecognized parameter wh90batt=3.16
Aug 6 13:05:12 raspberrypi weewx[18619] INFO user.interceptor:
unrecognized parameter interval=16'
--
Jason Marshall Thomas
On Sun, Aug 6, 2023 at 11:15 AM &
in since last interval, which is my understanding of what the
database fieldname 'rain' is meant to represent.
Having looked at the wview-extended.py schema I can see that I had
the wrong database field names for the battery values. I have
since changed the mappi
your location data you can get out of weewx 😉
On 29.07.2023 22:11, Stefan Gliessmann wrote:
That would work. But I would miss out on the location and elevation
data … I would like to include location in a database …
p q schrieb am Sa. 29. Juli 2023 um 20:25:
Why not use the same one and
You can get a GW1100 which comes already with an inbuilt indoor T/H
sensor, a WH32 outdoor for the outdoor T/H and maybe, if you need more,
another WH31 extra T/H sensor.
An external 3-in-1 sensor doesn't exist in the Ecowitt universe. Indoor,
yes, but a GW1100 cannot receive it.
And then run we
You probably gave your new plot a new different name - and have
forgotten to display it also in index.html.tmpl 😎
On 27.07.2023 20:13, DR wrote:
I have had 4.5.1 running on a Rasp Pi 4 for over a half a year. Not a
glitch.
I wanted to add to the Seasons Skin an additional plot. The stock
pa
you are free to do whatever you want...
You can even disable the rsyslog service completely and have no logging
at all.
However, turning off logging is not a very smart approach, and thinking
you can turn logging on again "when it's needed" is imho rather naive
thinking. When an application (an
maybe weewx is not the culprit
did you set the piezo rain priority in your GW1100 ? (-->Rain totals -->
Rainfall data priority --> Piezoelectric Rain Gauge)
On 24.07.2023 16:38, didier belin wrote:
Despite modifying weewx.conf , as quoted in another post
weewx.conf
poll_interval
the fields are oblivious of how the data stored was achieved (min, max,
avg, sum ...).
This is defined in the accumulators for the weewx field map - and if
your new variable is not contained or you want a different way from the
default accumulator behaviour, you have to add this to the [Accumula
you have to do some proper network analysis - this whole story is
neither a GW1000 nor a weewx issue.
And I doubt that "just out of the air" it all stopped and went wrong.
Something must have (been) changed in the network configuration.
"Upgraded the GW1000 firmware"
that means you must have use
eewx.confg
i can log in with chrome on that address
and my router has a fixed ip for this mac address
what i dont understand is why my raspi image from 3 weeks ago will not
work thats strange
my syslog attached
thanks for your help
On Saturday, 22 July 2023 at 09:53:09 UTC+1 Rainer Lang wr
can you see the live data in the WS View Plus app or in the
WebUI/embedded webpage (IP address of your GW1100 in the browser URL
field) ?
maybe the IP of your GW1100 changed, which won't keep it from posting to
ecowitt.net, but if it is now different from what is written in
weewx.conf, weewx
Assuming you assign your WH51 sensors to the SoilMoist1 thru SoilMoist4
database fields, be via a fieldmap extension or a
StdCalibrate/Corrections entry in weewx.conf,
you will also have to add some changes to extensions.py (in
/usr/share/weewx/user or /home/weewx depending on your installa
Another option I could suggest for this antiquarian piece of a weather
station (it's imho a shame that such old hardware is still being sold -
but probably the sellers want to empty their stock - when technology has
made already big leaps ahead for 5+ years) would be to get yourself a
modern Ec
can you please post your syslog after restarting weewx with debug = 3 in
weewx.conf from the weewx restart until at least the first archiving
cycle and report generation (so it ever completes) is finished
thanks
On 17.07.2023 17:53, Stefan Gliessmann wrote:
I have read the link above and made
Maybe you send us a complete excerpt from your syslog covering the weewx
startup and at least one archiving period
That would be more helpful than just a few snippets.
Thanks
On 17.07.2023 11:02, 'neu...@bnjpro.dk' via weewx-user wrote:
I have been the happy user of weeWX for a very long time n
ine 329, in
readDataFromWF
raise DriverException("Could not fetch records from
WeatherFlow webservice: {}".format(response))
user.weatherflowudp.DriverException: Could not fetch records
from WeatherFlow webservice:
On Monday, July 1
try
sudo |pip3 install --upgrade requests|
|if pip3 is not installed, do it before
|
|sudo apt-get -y install python3-pip|
|
|
|
|
||
On 10.07.2023 18:50, mukbar wrote:
Hello,
Have lurked here for years. Many folks have been invaluable in helping
me set up https://sanpedrowx.com/.
I am
What you are probably not so happy with is the new (since 4.7) Seasons
skin produced by its standard files.
What you can do is e.g.
- create a new directory under /etc/weewx/skins (or /home/weewx/skins
when you used setup.py)
with the name Seasons-Old (sudo mkdir /home/weewx/skins/Seasons-Old )
un 28 21:52:40 weewx weewx[3132] INFO user.wetter: service version is 0.7
Jun 28 21:52:40 weewx weewx[3132] INFO user.wetter: wetter API version
is 5.0.2 - 2015/06/01
Jun 28 21:52:40 weewx weewx[3132] INFO weewx.restx: Wetter: No config
info. Skipped.
Jun 28 21:52:40 weewx weewx[3132] INFO we
It can be omitted (under normal circumstances)
I was/am using it because I combine/d different observations from
different weewx databases
with different rain gauges into one graph/picture.
I think the image generator needs to be told from where to take the data
if more than one
observation is
"Where is this data actually stored if not in the database? Is there any
way to test this out, besides actually using the said driver?"
The data is not stored on a medium (e.g. disk) but just kept in memory
during the runtime of the program - and even there
only as long as the program logic al
Hi David,
the sentence *"**/It is not necessary to do so if only displaying
current values (ie values from the current archive record)"/* is maybe
a bit trickily phrased - at the time the report is generated weewx
includes values from the database and the current values of all
observations in
Forwarded Message
Subject:Re: [weewx-user] Rain cumulative total wrong total in graph
Date: Sat, 24 Jun 2023 14:42:09 +0200
From: Rainer Lang
To: weewx-user@googlegroups.com
the below works for me ...
[[[yearrain1]]]
# Make sure the y
the below works for me ...
[[[yearrain1]]]
# Make sure the y-axis increment is at least 0.02 for the
rain plot
yscale = None, None, 0.02
plot_type = bar
width = 1
rain1
fill_color = "#ff4500" #red
from US to METRICWX. weewx never starts. i ll
trying one more time.
Στις Παρασκευή 23 Ιουνίου 2023 στις 9:22:44 π.μ. UTC+3, ο χρήστης
Rainer Lang έγραψε:
what exactly did you do ?
migrated the (data from the) old database into a new database with
METRICWX as described in Tom
wser easily! thank you!
is there way my data base appears values to mm and C for temp,
instead to inches and F ?
Στις Τετάρτη 21 Ιουνίου 2023 στις 4:17:58 μ.μ. UTC+3, ο
χρήστης Rainer Lang έγραψε:
At the end of the day it doesn't matter where the
cess to my LAN, where the console would be.
*The other way round is possible, from my LAN network I have full
access to all machines and services in the DMZ. **
*
Rainer Lang schrieb am Donnerstag, 22. Juni 2023 um 20:37:44 UTC+2:
just technically speaking:
if your server stands in a DMZ
as it can be
(in a certain price range of course).
Right now, there is no choice, but the comparison with the cars was
very helpful.
Rainer Lang schrieb am Donnerstag, 22. Juni 2023 um 19:36:35 UTC+2:
sorry to say that but you are just trading subjective
non-representative opinions
sorry to say that but you are just trading subjective non-representative
opinions regarding Ecowitt (and clone) stations and hardware
modern Ecowitt stations have proven to be quite reliable and to compare
an ancient WH1080 with the modern Fine Offset / Ecowitt hardware is like
comparing a yea
it seems you posted the same question in the German Weather Forum
https://wetterstationsforum.info
There you already got the suggestion to read their WiKi section about
Ecowitt (clone) weather stations:
https://www.wetterstationsforum.info/wiki/doku.php?id=wiki:wetterstationen:ecowitt-stationen
something like this should work:
(you need to put your own labels 😉)
[[[dayrain4]]]
# Make sure the y-axis increment is at least 0.02 for the
rain plot
yscale = None, None, 0.02
plot_type = bar #line
width = 2
rain1
Hi Gary,
I think you know that by saying that your driver were "dump" I didn't
want to discredit your work. 😉 - Just that the work is done by the
console (or earlier in the chain).
The WH57 provides only the number of strikes since the last reporting
including the distance of that last strik
aking people - gmx.at looks like Austria - also in
https://www.wetterstationsforum.info/index.php and their related WiKi
for Ecowitt stations) 😉
On 21.06.2023 21:48, Rainer Lang wrote:
That's rather a question for the wxforum
https://www.wxforum.net/index.php?board=111.0
it's not
it with sqlitebrowser easily! thank you!
*is there way my data base appears values to mm and C for temp,
instead to inches and F ? *
Στις Τετάρτη 21 Ιουνίου 2023 στις 4:17:58 μ.μ. UTC+3, ο χρήστης Rainer
Lang έγραψε:
At the end of the day it doesn't matter where the weewx.sdb is
lo
can occur. When the Sensors emits a new value, is the distance
weighted? If not, any further calculations are pointless anyway.
(Maybe Rainer Lang knows the answer or knows someone who knows the answer)
- weewx has an archive_interval, does the driver weight the
distance/count or is the value for t
what the driver reads from the console and what is stored in the
database are two completely different things.
You can display in the Seasons skin all these values as current values
as long as they are used by index.html.tmpl and its inclusion files
(*.inc).'
But stored in the database is only f
Could you please send (attach as txt file) your whole skin.conf ?
The excerpt you show only means that certain sensor labels get a
different name - it doesn't mean that these sensors are shown somewhere.
You have to understand how weewx works and what needs to be done for
certain observations
At the end of the day it doesn't matter where the weewx.sdb is located -
as long as weewx and wee_database via weewx.conf and sqlite3 via the
path in the command know/are told
where it is located.
You can still check with sqlitebrowser what your entry in your database
for the respective EPOCH
at first glance looks ok to me -
but what I would do is:
download and install sqlitebrowser (suso apt-get install sqlitebrowser)
start it in update mode
sudo sqlitebrowser /var/weewx/weewx.sdb
and then go to your time stamp and add the values manually in the database
(don't forget to move the curs
in your field map, try to put
rainRate = rainRate, mm_per_hour
# instead of rainRate = rainRate, mm
and make sure in your weewx.conf under
[StdReport]
[[Defaults]]
[[[units]]]
groups
# you have defined
group_rainrate = mm_per_hour
On 20.06.2023 05:41, Joao Pedro wrote:
Hii guys :)
you should read and apply the proper synthax:
try wee_database --help
and apply
when you mention weewx.conf then as --config=/etc/weewx/weewx.conf
if you have only one database and one respective weewx.conf, you don't
need to mention it (but you can, however, then correctly)
(sudo) wee_da
, you will either have to repurpose existing but unused database
fields
or extend your database schema with the respective columns
On 13.06.2023 19:40, Rainer Lang wrote:
Hi Jason
1. the local API (local Ecowitt Gateway API aka GW1000 API) was never
implemented in the HP25x0, HP350x, WH2910
Hi Jason
1. the local API (local Ecowitt Gateway API aka GW1000 API) was never
implemented in the HP25x0, HP350x, WH2910 consoles => so no such thing
like depreciation
you want to know which console supports which API, look up
https://www.wxforum.net/index.php?topic=40730.0 😎
2. the reason w
1. what do you mean by "I am loosing rain--information." ?
can you please explain more in detail !? What do you lose ?
2. has weewx ever written to the database ?
you say you get an engine shutdown every ten minutes ... - if you use
the standard archiving interval (5 minutes - 300 seconds), ther
another option would be to use a modified version of Matthew Wall's
Interceptor driver - extend its field map to cover for all data sent by
the customized server function of the Ecowitt consoles.
All Ecowitt console have this function for the sensors they support.
Apart from adaptations to Pytho
on to access this resource.
On Friday, 19 May 2023 at 13:50:17 UTC+1 Rainer Lang wrote:
did you change the permissions for weewx web folder
/var/www/html/weewx
or
/home/weewx/public_html
whichever you are using ?
The example for the first path would be
sudo chmod -
As far as I know is the capacitor voltage of the WS90 not communicated
via the local API (Ecowitt Gateway API), only the battery voltage.
The capacitor voltage you can see in the Ecowitt cloud dashboard of your
station/console - that's a different communication protocol between your
console and
did you change the permissions for weewx web folder
/var/www/html/weewx
or
/home/weewx/public_html
whichever you are using ?
The example for the first path would be
sudo chmod -R 755 /var/www/html/weewx
only then the Apache webserver has the permission to read (and display)
the /var/www/ht
what console or device does weewx read from ?
which driver/extension are you using for catching the lightning data of
your Ecowitt WH57/Ambient WH31L ?
On 27.03.2023 12:27, Mark Fraser wrote:
Revisiting my lightning sensor configuration as I've got no graphs on
the Seasons skin and wondering i
"but weewx is not reporting any wind data." - what exactly you want to
say by that sentence ?
What driver are you using ?
WHich version of weewx are you using ?
What are your weewx.conf settings for that ?
What does your skin.conf look like ?
I guess by "the white page with graphs and text" you
can you provide your .conf file and the first three lines of the csv
file (header + 2 data lines) ?
On 11.03.2023 15:33, Willi Dennerlohr wrote:
unfortunately no success
Am Sa., 11. März 2023 um 14:55 Uhr schrieb Rainer Lang
:
convert " , " into "," (without "
1 - 100 of 257 matches
Mail list logo
