does this indicate the same MQTT service is being loaded twice? that might
confuse the driver
⊣GE⊢
> On 22 Jun 2023, at 8:42 am, jose riaño wrote:
>
> Jun 21 17:33:19 raspberrypi weewx[6765]: engine: Loading service
> user.mqtt.MQTT
> Jun 21 17:33:19 raspberrypi weewx[6765]: restx: MQTT: servi
So for the WH57, any further calculations are pointless.
The referenced PR is for a Tempest, as far as I know, the Tempest reports
every singly lightning detection as an event immediately, as an addition to
the packet containing all the values every minute.
gjr80 schrieb am Mittwoch, 21. Juni 20
The reason I map things to existing fields is that it's upgrade proof. If
you extend the db then you need to remember to do that if you rebuild your
system from scratch. Same reason I do the edits in weewx.conf rather than
skin.conf for the skin. It keeps the skin upgrade proof.
On Wednesday
pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
Jun 21 17:33:11 raspberrypi weewx[6711]: manager: Daily summary version is
2.0
Jun 21 17:33:11 raspberrypi weewx[6711]: manager: Daily summary version is
2.0
Jun 21 17:33:11 raspberrypi weewx[6711]: engine: Clock error is -0.30
seconds (positive is fa
Or you can modify your database with wee_database and add fields
wh31_ch1_batt, wh31_ch2_batt etc to the database schema. Utilising the
existing batteryStatus1, batteryStatus2 fields is arguably simpler and
quicker to implement, adding fields to the database arguably provide self
evident names
The issue is not whether the driver is 'dumb' or what the console does nor
over what period. The fact of the matter is that WH57 only provides the
distance of the last detected strike, not the average, not the sum nor any
other aggregate. That distance has no relationship whatsoever with any
ea
On Wednesday, June 21, 2023 at 11:54:17 AM UTC-7 weewx-user wrote:
I have used the Ecowit Gateway Driver from here -
https://github.com/gjr80/weewx-gw1000 and read the Wiki from here
https://github.com/gjr80/weewx-gw1000/wiki and followed the steps as best I
can (see my comments about my skin s
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
I really don't see the point of trying to weight lightning strike distance
from a WH57. In essence the WH57 reports three things; the number of
lightning strike detected today, the time of the last detected lightning
strike and the distance of the last lightning strike. This is clearly
stated i
Google is your friend (most of the time 😎)
read https://www.wxforum.net/index.php?topic=40093.msg460073#msg460073
It's generally good to look for answers regarding Fine Offset/Ecowitt
(clone) hardware in the wxforum
https://www.wxforum.net/index.php?board=111.0
(and for German speaking people
afaik only if from the very beginning you choose this unit system - once
started you cannot change this anymore
(or at least not easily - in principle you could make a migration, but
in my estimate this would require quite some effort)
On 21.06.2023 21:45, Δημήτρης Βήχος wrote:
finaly i did it
That's rather a question for the wxforum
https://www.wxforum.net/index.php?board=111.0
it's not really a weewx question
In a way the Ecowitt gateway driver is dumb - it just asks the console
(GW1x00, GW2000, WH2650, WN19x0) for information, receives it and puts
it into the weewx loop.
Dependin
finaly i did 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 l
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
How are lightning strikes and lightning distance calculated?
- How does the WH57 do it?
- How does the Ecowitt Gateway Driver do it?
Lightning distance and lightning strike count aren't independent values
when you don't look at the events individually, but over a observation
period:
- WH57 has
I have used the Ecowit Gateway Driver from here -
https://github.com/gjr80/weewx-gw1000 and read the Wiki from
here https://github.com/gjr80/weewx-gw1000/wiki and followed the steps as
best I can (see my comments about my skin set before)
If I use PYTHONPATH=/usr/share/weewx python -m user.gw10
I think I'd start by veryifying that the WS90 data you are looking for is
in the weewx database to begin with. What weewx.sdb elements did you use to
store the WS90 battery and signal strength in ? How did you define that
to happen ?
--
You received this message because you are subscribed to
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
Sorry *SKILL SET *is low
On Wednesday, June 21, 2023 at 4:09:31 PM UTC+1 weewx-user wrote:
> I am using a Ecowitt GW2000 with an WS90 outdoor sensor.
>
> https://multinet.org.uk/weewx/
>
> It is mostly setup as I would like it but for the life of me I can't get
> the WS90 signal strength or
I am using a Ecowitt GW2000 with an WS90 outdoor sensor.
https://multinet.org.uk/weewx/
It is mostly setup as I would like it but for the life of me I can't get
the WS90 signal strength or battery status to show up under sensors. This
is what I have in the skin.conf
[Labels]
# Override so
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
my database is on /var/lib/weewx/weewx.sdb
metfm@metfm:~$ ls -ail /var/lib/weewx
σύνολο 18692
264962 drwxr-xr-x 1 root root 18 Ιουν 21 14:20 .
269 drwxr-xr-x 1 root root 592 Φεβ 26 18:30 ..
270727 -rwxrwxrwx 1 root root 19140608 Ιουν 21 14:20 weewx.sdb
metfm@metfm:~$
Στις Τετάρτη
No. The default Debian based distro database is /var/lib/weewx/weewx.sdb.
The archive directory is only used (by default) for setup.py installs.
OP. Have you confirmed the location (and name) of your WeeWX database? What
does the following command show:
$ ls -ail /var/lib/weewx
Gary
On Wednes
It should be /var/lib/weewx/archive/weewx.sdb
Can you give us a screenshot where the weewx.sdb is??
Στις Τετ, 21 Ιουν 2023, 11:03 ο χρήστης Δημήτρης Βήχος <
hobbyline...@gmail.com> έγραψε:
> debian installed. also triyng with sudo sqlite3 /var/lib/weewx/weewx.sdb
> same thing.
>
> Στις Τετάρτη 2
debian installed. also triyng with sudo sqlite3 /var/lib/weewx/weewx.sdb
same thing.
Στις Τετάρτη 21 Ιουνίου 2023 στις 9:55:34 π.μ. UTC+3, ο χρήστης gjr80
έγραψε:
> Have you customised your WeeWX install? You appear to be using a package
> install so unless you have changed it your WeeWX data
25 matches
Mail list logo
