SIGW1100 and Ecowitt WS90 weewx3.9.2 going to upgrade to version 4.XXX
zasp...@gmail.com
Going to make the big jump form a series 3 weewx to the latest version are there any pitfalls I should be aware of .
been running the GW1000 driver a couple of weeks works without issues so far
The WS90 has and onboard capacitor and its logged on the Ecowitt app
does the GW1000 driver log this voltage? or is it just the battery voltage
Thanks for any advice
Rainer Lang
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 the Ecowitt cloud.
have a look at Ecowitt Gateway driver WiKi
aka GW1000 API driver:
https://github.com/gjr80/weewx-gw1000/wiki/Sensor-battery-states
And, just for clarity, the Ecowitt app doesn't log anything. It reads the data from the Ecowitt cloud where console has posted them. 😉
--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/0ea4581d-20fd-4300-8e9b-92445a2f3a9dn%40googlegroups.com.
gjr80
Mark Fraser
Rainer Lang
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 Python3 Matthew doesn't seem to have
worked on the iInterceptor driver for quite a long time - and
the Ecowitt sensor universe has significantly expanded ever
since.
Other developers have created already an extended version where the WS90 capacitor voltage is included.
There is a (working !) extention of the
Interceptor driver (interceptor.py) made/adapted by the German
developer Werner Krenn (also a member of the community here) to
cover for ALL recent Ecowitt sensors existing today.
See attachment.
You can experiment with it.
I suggest you do the installation with the basic version first
- https://github.com/matthewwall/weewx-interceptor/
Understand how it works and make it working
for you - it's pretty easy and straightforward
(you can install the interceptor driver in parallel to your
GW1000 driver - the entry in the station stanza in weewx.conf
decides which driver (section) you use).
Once it works with the basic sensors (it will create non-fatal
error messages in the syslog for every non-covered sensor), save
the original interceptor.py and replace it by the one in the zip
file.
Also add to weewx.conf in your [Accumulator]
stanza
[Accumulator]
[[lightning_strike_count]]
extractor = last
That's if you want to use a WH57 lightning sensor together with
the Interceptor driver
If you don't create the non-existing database fields in the
wview_extended database schema (or repurpose existing but unused
fields to accomodate your new sensor data) and use the respective
field map and/or respective entries in the weewx.conf
[StdCalibrate] [[Corrections]] stanza, this data won't be
saved/archived and will only be available as $current between
archiving periods.
But that's not a driver issue, it's a user issue. 😎
You want to save the "extra" data which are not part of the
wview_extended database schema, you have to extend it (or
repurpose)
good luck
--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPSrEd%3DVUFHv7FH6b6_X8DjFURDzHDG2Yc4Fy2gtM5ghU3okOg%40mail.gmail.com.
