I guess the TFA R100 is the predecessor model of the TFA KLIMALOGG PRO
30.3039.
TFA Dostmann don't have it in the catalogue anymore.
Did you check https://github.com/matthewwall/weewx-klimalogg ?
Maybe this works for you.
On 17.12.2020 12:43, 'G.-U. M' via weewx-user wrote:
Hello,
please ex
I have several sensors which in my observation do not have a counterpart
in the extended weewx database schema.
But I still want them stored in the weewx database and have them and
their history displayed in the web interface under http://IP-address/weewx
E.g. there seems to be only one (1) f
Hi,
I'm about to close gaps in my data history (due to system downtime and
also historical data from my pre-weewx times).
Adding missing records is nicely described and looks rather simple and
straightforward.
However, I don't know how to handle the update of already existing records.
E.g. du
I had the same issue like Vince the other day - and loop_on_init
hadn't been set by the install script...
I assume it's to set in the [GW1000] stanza - that's where I added it now.
Forwarded Message
Subject:[weewx-user] Re: gw1000 driver fail on wifi loss
Date:
Ever since integrating the new WH45 sensor, weewx went nuts:
(see below): no more reports written, no more archive records stored.
Had to take off the sensor and reset the GW1000 - then weewx went back
to normal.
I think it's an "API mismatch" - btw - Meteobridge also produces weird
sensor o
He's already been working on it - will check/test the suggestions
tomorrow respectively today later in the day - now too early (or late) here.
On 01.01.2021 00:52, galfert wrote:
Hopefully Gary will pick this up and add the WH45 compatibility to the
GW100 API driver.
On Thursday, December 31
@ (not only) weatherlist
If you had copied the list completely, 😉
See below - bold by me.
(but possibly a SSD comes cheaper than the higher capacity SLC micro SD
cards - still may need an enclosure with USB (best 3) interface; not too
expensive either)
.
Meteobridge enforces the u
As for me, the code of the new driver (0.2.1b1) works fine as far as I
can tell.
All data arrives and can be addressed, and the application doesn't crash
anymore.
It can be archived (some assignment needed as not all fields are part of
the extended database schema),
and it can be used in the
It works with all Ambient Weather sensors which are clones of Fine
Offset sensors.
(Ambient also sells non-Fine Offset clone sensors and weather stations)
What sensors these are, you can see at
https://www.wxforum.net/index.php?topic=40730.0
On 02.01.2021 21:34, George Morgan wrote:
Does th
the GW1000 so I may be looking at integrating FOSHK
plug-in into weewx directly...unless I'm missing something...
I also need to look at the license for FOSHK plug-in as
that may make this impossible (legally, that is)
On Sat, Jan 2, 20
I'm running weewx on Raspberry Pi with my Klimalogg Pro (KLP) and the KL
extension/skin.
At the first start it reads all the existing data records from the
Klimalogg Pro (52,000+) and stores them in the database.
Great!
Now I observed that when the connection for some reason gets lost - or
t
not very long (except for the initial check - here are 51,330 records to
be covered)
- the story is (I meanwhile checked the data base content and the
syslog) that weewx continues writing (empty) records when it isn't
connected to the console.
I think that's the reason for not reading the miss
On 04.01.2021 22:50, vince wrote:
So you're saying:
* periodically loses connection to the station
*/rather rarely - but at times (1-5 times in a year, usually due
to maintenance - see below)/**/
/**/it also technically happens during a reboot or a short time
shut down of the
Hi Vince,
as far as I can tell there is no gap between WSView app (FW 1.6.3) and
the data provided by the new driver.
I already had a pre-release version installed as my weewx installation
crashed with my new WH45 sensors.
(That's the last line in the wiki update by Gary - the program shouldn'
will take much more planning and time. My home has
primarily a hip roof which presents very little unobstructed
opportunities for mounting. I do know which channels they show up
on from the WS-2000 console...
On Mon, Jan 11, 2021, 3:14 PM 'Rainer Lang' via weewx-user
I don't think you properly understood what galfert was saying resp. what
he wanted to say:
what he meant was that an _additional_ Ecowitt GW1000 displayless
console (+/- 36 USD) would do the best job. If you don't know the piece,
I recommend to look it up at ecowitt.com. It's a matchbox size US
As a workaround I would remove / replace your suspects - change
"Umlaute", if any, from Ä -> AE, Ö -->OE, Ü --> UE, accents just omit
them and leave the vowels without them.
They will anyway only appear in temporary graphs. Then figure out your
UTF-8 issue and fix it, while your weewx could alre
I suggest that you first get weewx running with the interceptor driver
in a simple "normal" test environment.
e.g. weewx host and console in the same subnet, no other fancy network
and virtualization constructions.
Once that works, start changing step by step the test environment
towards your
1. can you send us the system log from the time on that weewx started
otherwise difficult to say what's going on in your system
2. also add your weewx.conf
3. Have you created a temporary file system for the pictures and html
files ?
If not (yet - that's to protect your SD card but not necessa
That's definitely not a feature.
However, did you have below 0°C/32°F temperatures ?
And do you have the inbuilt heater connected and powered ?
What works with others who had the phenomenon - and no heater activated
- was, taking it down, drying it inside/indoors and it worked again.
Mine has it
Hi
the GW1000 doesn't receive (or at least doesn't process) any pm10 data
from the WH41, even though that one may send out such data.
If you want clarity, send an email to Lucy (supp...@ecowitt.com) and ask
your below question.
Would be interesting to know what they have to say.
The WH0290 i
Would you please share your file /etc/weewx/skins/simple/index.html.tmpl ?
The error log seems to point at an error contained in this file.
Something missing or too much or at the wrong place.
Without seeing it, no further conclusion possible.
Thanks and regards
On 24.01.2021 21:52, sc.lep...
So it appears - just tested and saw that under Python 2.7.16 the skin
runs without problems. Weewx is 4.3.0
On 24.01.2021 22:08, John Kline wrote:
It seems weewx-simple does not (yet) support Python 3.
On Jan 24, 2021, at 12:46 PM, sc.lep...@gmail.com
wrote:
Hello
I used the simple templ
Hi William
In my understanding the WH65 is the FineOffset/Ecowitt 7-in-1 sensor array.
What console are you using ? WH2320E ? GW1000 ? HP2551 ?
I don't think you need a special field map for the WH65 sensor array.
But somehow your sensor data have to make their way into weewx - that's
usually v
.
On 24.01.2021 22:29, Rainer Lang wrote:
So it appears - just tested and saw that under Python 2.7.16 the skin
runs without problems. Weewx is 4.3.0
On 24.01.2021 22:08, John Kline wrote:
It seems weewx-simple does not (yet) support Python 3.
On Jan 24, 2021, at 12:46 PM, sc.lep
I had the some question some time ago - where is the directory util
- until I realized that this path seems to refer to a location on GitHUB.
You can find there the whole script text, mark it, copy it into the
clipboard and then create a new file with the name weewx-multi and copy
the clipb
Hi
when you want to get the data from the HP2551 console (that's the
console of the HP2553 package), you can only do this by the help of the
interceptor driver.
Get it and install it - then verify what I wrote below
You have to choose there / put in weewx.conf
[station]
station_type = Inter
On 08.02.2021 09:08, Renato Brigger wrote:
Hallo Renato,
Zunächst müssen wir mal klären, was genau diese WH2600SE ist ?
Ist das die Froggit WH2600SE Pro WiFi (Fine Offset WH2650 WiFi) oder
die uralte "ObserverIP" WH2600.
Sehen beide auf den ersten Blick gleich aus, unterscheiden sich aber bei
sudo weewxd /etc/weewx/weewx.conf
On 08.02.2021 12:48, PAK wrote:
Thanks for the advice. I have googled but still not sure I'm doing it
correctly as getting same error. How do i run bin/weewxd as root?
On Friday, February 5, 2021 at 9:07:02 PM UTC+10 graha...@gmail.com wrote:
did you run
I think, the crucial information we are looking for is hidden here: "You
can find more details here. "
I suppose there was a link which wasn't copied over with the text.
Would you mind providing this link ?
Thanks
On 18.02.2021 11:41, bchap...@gmail.com wrote:
You can find more details here.
That would imho be rather stupid. Why would they "sell" a link which
leads to applying for a PWS/aeris account as detailed information to an
existing user ?
What added value would an existing user get by applying again ???
Maybe there's still something more to it.
@Bruce: can you provide the li
Hi Gary,
I have a WH40 and WS90 connected to my GW2000.
The 0x57 command returns
FF-FF-57-00-54-0E-00-00-10-00-00-00-00-11-00-00-00-00-12-00-00-02-F2-13-00-00-0B-93-0D-00-00-0F-00-64-80-00-00-83-00-00-00-00-84-00-00-00-00-85-00-00-01-DE-86-00-00-0B-F2-81-00-00-87-00-64-00-64-00-64-00-64-00-64-00-6
Hallo Werner
Die API Doku enthält z.Zt. noch Fehler. In Kürze sollte eine korrigierte
Version erscheinen.
nachstehend die gültige und korrekte Fassung des CMD_READ_RAIN Befehls
und der "WiFi" (besser API) Rückmeldung
CMD_READ_RAIN 0x57 und die dazugehörige WiFi response (es gibt darin
keinen
You can only buy it from Ecowitt (ecowitt.com) so far.
If you want the console/gateway only, you will have to send a mail to
supp...@ecowitt.com.
However, there are delays right now as they have run out of stock with
their kickstarter campaign
for the GW2001 station (GW2000 + WS90 outdoor array
d
response 'FF FF 30 0B 01 01 62 6F 2C 45 27 01 A7'
May 2 00:56:38 raspberrypi weewx[3016] DEBUG __main__: Sending
packet 'FF FF 57 03 5A' to '192.168.1.46:45000
<http://192.168.1.46:45000>'
May 2 00:56:38 raspberrypi weewx[3016] DEBUG _
on of TimespanBinder later, allowing
it to be modified in a more straightforward way:
$getVar('%s.%s(data_binding='rpi24-binding')' % ($timespan,
$x)).max.format(add_label=False)
-tk
On Tue, Jul 5, 2022 at 2:57 PM 'Rainer Lang' via weew
As far as I know weewx doesn't provide uploads to ecowitt.net - the WiKi
shows uploads to many weather services but not to ecowitt.net - at least
I couldn't find it.
In order for data to be sent to ecowitt.net, your console (its MAC
address) needs to be registered with ecowitt.net. Once this is
This looks like a clone of the old Fine Offset WH1080 weather station
which is no longer sold by Ecowitt due to old technology.
Console connectivity is USB only, no WiFi, no connection to the weather
networks. No solar sensor either. (a solar panel for running the outdoor
array, yes).
The outdoo
e-or-less raw data. Recommendations for alternative, more modern,
setups that permit this would be welcome.
Peter
On Wed, 13 Jul 2022, 07:37 Rainer Lang, wrote:
This looks like a clone of the old Fine Offset WH1080 weather
station which is no longer sold by Ecowitt due to old technology.
You can use the weewx interceptor driver - station_type = ecowitt-client
and have your HP2551 console post via custom server to the server where
your weewx runs. path must contain a "/" (without ""), server/IP is IP
address only (no http:// in front) - port has to be the same where the
intercep
The HP25x0 consoles do not have an API and cannot be queried via the
GW1000 API/Ecowitt Gateway driver.
You either use a GW1x00/GW2000 instead (receive the same sensors in
parallel) with the Ecowtt Gateway (GW1000) driver,
or you will have to use the weewx Interceptor driver with the HP25x0
cons
the Ecowitt Gateway driver works on a pull procedure, i.e. requests the
data from the GWyx00 console, whereas the interceptor driver works with
data pushed by the console via the custom server functionality.
In both cases the consoles communicate via WiFi/WLAN into the local
network, and weewx r
1. the GW1000, GW1100, WH2650, GW2000, WN19x0 consoles all share the
same APi - the Ecowitt Gateway API aka GW1000 API
the Wittboy = GW2001 station = GW2000 console/gateway + WS90 7-in-1
sensor array
The WS90 outdoor array can be connected to any of the above mentioned
consoles with Ecowitt Gate
The Rpi4B has nothing to do with it (ca n'en a rien à voir - rien du tout !)
Just do the following things:
1. save your old .../skins/Seasons directory and its content
2. save your old weewx.conf
3. save your old weewx.sdb
e.g. on a USB stick
4. now do a complete new install on the new RPi (doesn
I would use the following approach:
1. take a (new) SD card and put a bootable OS image for a RPi3 on it
2. try to start up /boot your RPi3
3. if it doesn't boot, look up via Google the topic: creating an OS
image for RPi3 and get your RPi3 up and running
4. Once your RPi3 boots and runs, do a n
yes, this is normal in the sense that the interceptor driver only
handles the classic observations and the ones shown in your log are out
of the normal (for the standard interceptor).
Most of these messages (ignored parameter) only appear in the syslog
when you have debug = 1 activated in weew
Hi guys,
the weewx standard depiction of rain in the Seasons skin is accumulated
rain per hour as a box plot in the skin.conf [[[dayrain]]] stanza
how can I make the imagegenerator create a plot where the rain is shown
as accumulated rain by
1) a line
2) a line as top delimiter and the are
with plot_type = bar and aggregate_interval = 300 and
width = 2 the area under the curve is also fully filled 😎
even with the default weewx image generator
what remains open is the question about how to reset the cumulative
graph to 0 at midnight
On 21.10.2022 18:54, Chuck Rhode wrote:
On Fri, 21 Oct 2
When you want to use weewx under WSL (which works perfectly by the way -
at least with the Interceptor and the Ecowitt Gateway driver),
you need to make sure that the connectivity between the virtual machine
in which WSL is running and the local network the WSL host computer is
running in
has b
orts to var/www/html/ weewx,
i guess it something to do with permissions? or am i just dumb
thank you for your time,
Op vr 4 nov. 2022 om 22:24 schreef Rainer Lang :
When you want to use weewx under WSL (which works perfectly by the
way - at least with the Interceptor and the Ec
l2-systemd-script.sh
# Enter your password and wait until the script has finished
systemctl|
||
|You also have to look if the rsyslog service is installed/running (see
above command service --status-all)
if not, you can try|
|sudo apt-get install rsyslog||
|
||
On 05.11.2022 07:33, Rainer Lang wrote:
ndows, struggling
with that
still need to install system.d struggling with that too
Op za 5 nov. 2022 om 09:23 schreef Rainer Lang :
one more thing:
first of all you have to check if systemd is installed in your
ubuntu installation - if not you need to install it (or some
What I would do first is assigning one of your WH31 sensors (also) to
the outdoor T/H sensor
in weewx.conf
[StdCalibrate]
[[Corrections]] add the lines
outTemp = extraTemp1
outHumidity = extraHumid1
(as an example - you can take whichever of your WH31 you prefer,
extraTemp1, 2, 3, 4 ...))
As a r
ensor) universe.
On 18.11.2022 10:11, Rainer Lang wrote:
What I would do first is assigning one of your WH31 sensors (also) to
the outdoor T/H sensor
in weewx.conf
[StdCalibrate]
[[Corrections]] add the lines
outTemp = extraTemp1
outHumidity = extraHumid1
(as an example - you can take whichever of
Jede Skin braucht ihren eigenen Eintrag in der [StdReport]
Stanza von weewx.conf, eine eigene [[skin]] Stanza
Das funktionierende Beispiel ist unten angeführt.
On 14.11.2022 22:45, Rainer Lang wrote:
I don't know why you couldn't change or add
I suggest a systematic step-by-step error detecting approach here
including a few question beforehand:
- what do the GW2000 WebUI/WS View Plus app and ecowitt.net show for
wind observations ?
- what do you see if you run the Ecowitt Gateway driver (GW1000 API)
alone without the USB weewx.driver
I suggest you read through the Ecowitt Gateway (GW1000) driver WiKi 😁
https://github.com/gjr80/weewx-gw1000/wiki
and take a look at (not only) the Field Map
If after reading there some questions are left, come back here
On 20.12.2022 08:45, Francesco Galella wrote:
Hello everyone, I use an Ecowitt
the Klimalogg Pro database consists of two databases (default names:
weewx.sdb and weewx-kl.sdb) - they will have of course be located in a
different directory from your standard weewx installation if you keep
the database names.
The installation will not run with the weewx-kl.sdb only - even th
Hi Ted
weewx can't catch the sensor array data via the interceptor driver as
the WH2902C is an Ambient modified piece.
It cannot send to a customized server using the Ecowitt protocol. Maybe
it works with the WU protocol, but
haven't heard of it. If it were a non-Anbient Fine Offset clone, it
w
Hi Gary, thanks for he hint
I was digging a bit more - and found an earlier post of yours, which I
had already used before as I wanted dewpoint and heatindex to be
displayed beyond only sensor 1-4:
https://groups.google.com/g/weewx-user/c/svov51heFp8?pli=1
I did a complete reinstall again wi
You can go through the instructions/suggestions posted at
https://www.wxforum.net/index.php?topic=41575.0
this works in 99.5% of all cases so far. 😁
From what I read, your main issue might be
that you probably use the wrong app (probably wrongly stated in the
reseller manual) - you have to use th
Congratulations !
It is how it is - and, unless you do a factory reset, you won't
have to do this again.
For "general" FineOffset clone issues etc., WXforum is afaik the main
(in the sense most substantial) forum - for weewx there are some helpful
posts, too - but here is the main weewx
The WH2320E data can be processed by weewx with the interceptor driver,
device_type = ecowitt-client,
using the customized server function in the WH2320E (set up via WSView app).
On 25.03.2021 21:36, Fraoch wrote:
This looks a lot like a Fine Offset WH2900, at least the sensor
assembly does. Al
The driver on GitHub is up to date.
Works with a WH2900.
Just recently (a few days ago) helped someone to get it up and running
on their RPi.
The following recipe will work:
in WSView app:
Customized server
protocol Ecowitt
Port 8000 (or your choice - has to match the entry in weewx.conf)
some
we recommend NOT to use the intereptor driver for a GW1000/WH2650
console but to use the meanwhile existing
GW1000 API driver instead - otherwise you tend to run into multiple
issues (and unnecessarily use the
console's "Customized"server option which exists only once) due to the
many extra sens
While the GW1000 API driver provides you all the fields you can see in
the field map (--> wiki, https://github.com/gjr80/weewx-gw1000/wiki),
weewx archives/stores/writes to the database only the fields which are
contained in its database schema.
If you started with weewx 4.x.x that's most like
In combination with a Weather station, or just with a console (GW1000)
you can check e.g. the sensors and sensor-combos offered by FineOffset
via Ecowitt and resellers.
You will find a lot of info regarding this in the WXforum (not limited
to FineOffset (clones)). All supported by weewx.
As for
I had the same/a similar issue.
What finally worked was:
1. uploading the whole /var/www/html/weex directory manually (1st time)
with e.g. FileZilla
then also only the tables would show
2. activate FTP in [StdReport] - restart weewx
with the next archiving circle also the pictures were shown ..
I don't think that that's a phenomenon to be generalized.
My GW1000s (s !) are running with weewx (API) and Meteobridge (API)
being polled every 10 seconds without getting stuck.
There must be another reason for this behavior, maybe an instability in
the power grid (if it's not buffered by a p
Searching helps 😎
As per that link (review) the 01536 can save records for two weeks
(don't say based on what interval)
https://weatherstationexpert.com/acurite-01536/
On 25.05.2021 05:45, Jeff Carpenter wrote:
Hello
I just discovered that my weewx installation has not been collecting
data
Can't reach the weewx.com site
Anyone else has the same observation ??
--
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
Forwarded Message
Subject:Re: [weewx-user] Re: weewx.com down ??
Date: Thu, 27 May 2021 11:22:41 +0200
From: Rainer Lang
To: Karen K
That was not the question ...
@Karen:
can you connect with your browser ? A positive or negative reply would
be helpful.
I
@OP: don't give up too early, too fast 😉
As per his OP, it looks as if he is using Apache2, however, if the web
server is configured properly and configured to display the html files
created under /home/weewx/public_html (and if it's running at all) is a
different question.
Weewx seems to ru
One side remark regarding the dialogue below:
A Ventus830 (a FineOffset/Ecowitt WH2910 clone) cannot be updated with
the WSTool app, even though this is sometimes written like that in the
manual - you need the WSView app (latest version 😁) - when a firmware
newer than what you have is available
I use three different cameras, one Chinese brand PTZ PoE camera (H.View)
and two German products (Lupus).
They all save a pic every 60 seconds (as part of their security camera
feature) to my NAS - the PTZ via NFS, the others via FTP.
On the NAS the (files of the) latest pictures (showing an in
Did you compare to the readings the GW1000 posts to ecowitt.net (in case
you have it do so - if not, do it and check the next events) ?
In my case weewx reports the same readings as what is posted by the
consoles (several GW1000) to Ecowitt.net and to a template using the
customized server optio
It can be used by weewx with the Interceptor driver.
https://github.com/matthewwall/weewx-interceptor
The custom server option of the station (it's a Ecowitt WS2320E/WS2350
clone) will be used to send in Ecowitt protocoll to the server (e.g. a RPi).
helpful link: https://www.wxforum.net/index.ph
On a RPi you have to add the following line to your weewx.conf
device_type = ecowitt-client
port = 8000
iface = eth0 #if you are using the Ethernet port
#or
iface = wlan0 #if you are using the WiFi of the RPi
# only one of them 😉
you also have to make sure that no other app
age
Subject: [weewx-user] Re: Pulling my hair - one weird issue after the
other [3]
Date: Mon, 2 Aug 2021 16:05:30 +0200
From: Rainer Lang
To: Konrad Skeri Ekblad
Did you enter a path in the WSView app ?
There must be at least a "/" - even though weewx doesn't
Forwarded Message
Subject: [weewx-user] Re: Pulling my hair - one weird issue after the
other [4]
Date: Tue, 3 Aug 2021 14:28:28 +0200
From: Rainer Lang
To: Konrad Skeri Ekblad
I think this side effect is due to a recent change of Interceptor.py to
show also
On 03.08.2021 22:57, Clifford Snow wrote:
Hi Clifford, see below inline
I have weewx working. I can see reports for all my devices except for
the EcoWitt WH0290 air quality monitor. Plus I'm getting empty reports
on devices I don't have such as wind speed, direction and rain
measurements.
Fi
The WS-2000 with its outdoor array only is supported by the weewx
Interceptor driver (and the console custom server feature for WU protocol).
However, when it comes to more and extra sensors like WH31-type,
lightning, PM2.5, Soil Moisture etc.,
the interceptor driver will not process this info ne
weewx puts the index.html and related include files (*.inc) and pictures
into the directory which is defined in weewx.conf by HTML_ROOT=
in the [StdReport] section
If weewx is installed on the same server as apache2, the default
directory would be /var/www/html/weewx where the apache web serve
You have probably not disabled the belchertown skin completely for the
Cheetah Generator.
What you have to make sure with two (or more) instances on the same
server is:
with two weewx instances on one and the same server you need two
different weewx.conf
e.g. tempest.conf and 2ndstation.con
When both your instances have/use identical skin.conf, index.html.tmpl
etc. settings for the Belchertown skin, they don't need to be separated.
But if you want to "individualize" the skins for each instance, then
each one would need their own one.
On 05.10.2021 05:15, Chotechai Piyavongsiri wr
Could you please provide the following information
1. which Froggit model are you using
2. which weewx driver are you using
3. set debug = 3 in weewx.conf and restart weewx,
then provide the complete (!) syslog from the weewx start until at least
the first archiving interval (usually 300 seconds
Did you create a symbolic link redirecting the Apache default web folder
to yours ?
And did you allow Apache to access your report folder ?
1. Create symbolic link to point webserver to the reports
1. *sudo ln -s /var/weewx/reports /var/www/html/weewx*
2. Give the web server the ability to r
Hi Ralf
the Ventus W830 is a clone of the Ecowitt WH2910C console/station and
weewx supports it via the interceptor driver.
Have a look at
https://www.wxforum.net/index.php?topic=40730.msg417956#msg417956
and
https://www.wetterstationsforum.info/wiki/doku.php?id=wiki:wetterstationen:ecowitt-sta
Forgot to add:
in WS View you have to choose "Ecowitt protocol" 😎
On 01.12.2021 10:23, Rainer Lang wrote:
Hi Ralf
the Ventus W830 is a clone of the Ecowitt WH2910C console/station and
weewx supports it via the interceptor driver.
Have a look at
https://www.wxforum.net/index.php?t
The "error" is not an error but a warning - and it just means what it says
that apt-key will no longer be used in linux installations but will/can
be replaced
by trusted.gpd.d.
This will become effective 2022-April.
It has nothing to do with the weewx version you are installing (except
for the
If the installation is correctly done, just copying your weewx.sdb to
the new folder (/var/lib/weewx) will do.
The corresponding entries have to be in weewx.conf in the
[DatabaseTypes] section:
[DatabaseTypes]
# Defaults for SQLite databases
[[SQLite]]
driver = weedb.sqlite
Matthew's Interceptor driver doesn't handle that (yet ?).
As you seem to be living in Germany resp. speaking German, have a look at
https://www.pc-wetterstation.de/forum/viewtopic.php?f=26&t=10333&sid=bf68867d7a6c245e55636c156d07330b
where a modified Interceptor driver is described (and downloadab
Werner's interceptor driver is mainly meant for FOSHK clone consoles
like the HP350x or HP2551 which do not have an API which can be actively
queried by weewx. It interpretes the http posts of these consoles using
the custom server functionality
As for the GW1x00, WH2650, WN19x0 and the GW2000
Hi Nick
If you want to go with the FOSHK/Ecowitt ecosystem, have a look at their
offers
(www.ecowitt.com) and what can be combined/extended with what
(https://www.wxforum.net/index.php?topic=40730.0) and what a different
brands of the same stations
- you need to register in order to see pictur
1. choosing port 80 for the custom server to send/post to is not a smart
choice as this port is already used by the local (RPi) web server
(nginx, apache2, ...). You must choose a unique port e.g. 8000, 8080, ...
2. in weewx.conf you must not assign the port along with the ip address.
the entry
I'm also using the interceptor driver on Python 3.9.2 on Raspbian 11 -
no issue
BUT
the interceptor driver is most of the time used in listen mode and not
in sniffing mode.
In listen mode you instruct your console to post directly to your server
(single IP address and port) where the intercepto
it all depends on what you mean by a WS2900.
Have a look at the following thread and then tell us the Ecowitt name of
the station you are talking about (provided that station is a Fine
Offset clone):
https://www.wxforum.net/index.php?PHPSESSID=d3v98lhd7t2jolfnpft99hbqrs&topic=40730.0
(you need
I doubt that "it" or "everything" works.
Clicking on your link only provides a general page of your web hoster.
Something is still "fishy" - locally, on your web host or with both.
On 10.03.2022 16:19, Kalli Gøtze wrote:
Hi all,
Today i install weewx new and it works. www.kalligotze.org
Thanks f
There are only two ways to be really safe:
1. boot your RPi3+ from a (n external) HDD/SSD - instructions how to
make this work can be found in the internet
2. use an industrial standard SLC microSD card - it will hold for at
least 10 years.
(and make regular (!) backups of your important weewx
The Sainlogic SC008 is definitely NOT a Fine Offset /ecowitt clone model !
Still the interceptor might work - will depend on the SC008 console
functionality.
On 12.04.2022 09:44, ian...@kinnon.org wrote:
The image on Amazon looks like one of the generic Ecowitt clones, so
the interceptor client
1 - 100 of 287 matches
Mail list logo
