TFA NEXUS save sqlite and internal memory data

281 views
Skip to first unread message

Thomas Max

unread,
Jun 4, 2014, 3:04:41 PM6/4/14
to weewx...@googlegroups.com
Hello
The internal memory of the TFA NEXUS (3000 data points in 5 minutes) is not described in Using 'of weewx.
Is it possible that everything runs in parallel.


regards




Hallo
Der interne Speicher der TFA NEXUS (3000 Datenpunkte bei 5 min) wird bei Benutztung von weewx nicht mehr beschrieben.
Ist es möglich das alles parallel läuft.


Grüße

Luc

unread,
Jun 4, 2014, 6:53:19 PM6/4/14
to weewx...@googlegroups.com
Hello Thomas,

The English translation of 'beschieben' is 'written', so it might be the English readers didn't understand your question.
To my believe you can't switch of the internal data writin. With the Windows program supplied with the weather station you can choose the aquisition interval. It can be changed from 5 minutes to 24 h.
Can you check what value this interval has?

Cheers, Luc

(Google translate: English->German)

Hallo Thomas, 

Die englische Übersetzung von 'beschieben ist"written", so könnte es sein, die englischen Leser Ihre Frage nicht zu verstehen. 
Zu meinem glauben, Sie können nicht einschalten oder die interne Daten writin. Mit dem Windows-Programm mit der Wetterstation überversorgt können Sie die Erfassung Intervall zu wählen. Es kann von 5 Minuten bis 24 Stunden geändert werden. 
Können Sie überprüfen, welchen Wert dieses Intervall hat? 

Prost, Luc

mwall

unread,
Jun 4, 2014, 10:52:12 PM6/4/14
to weewx...@googlegroups.com
On Wednesday, June 4, 2014 3:04:41 PM UTC-4, Thomas Max wrote:
Hello
The internal memory of the TFA NEXUS (3000 data points in 5 minutes) is not described in Using 'of weewx.
Is it possible that everything runs in parallel.

thomas,

the te923 driver does not yet read archive records from the station.  this means that the weewx archive records are created by weewx from the 'live' readings.  it also means that the archive interval is defined in weewx.conf, not read from the station.

however, you can manually read records from the station like this (assuming a setup.py install to /home/weewx):

cd /home/weewx
PYTHONPATH=bin python bin/weewx/drivers/te923.py --records

use the --help option to see all options.

m

Thomas Max

unread,
Jun 15, 2014, 4:16:54 PM6/15/14
to weewx...@googlegroups.com
Thank you for the answers 
The te923.py driver reads only live from Station. 
The interval is now set to 1 minute. 

regards

Vielen dank für die Antworten
Der te923.py Treiber liest nur live von Station .
Der Intervall ist jetzt auf 1 Minute eingestellt.

grüße

Nico Gulden

unread,
Dec 22, 2015, 10:35:49 AM12/22/15
to weewx-user
Hi, 

I have a TFA Nexus too and I already read the records via the driver and the --records option. I now have a file with a bunch of lines looking like this:

1447452420:21.20:68:5.90:87:o:o:o:o:o:o:o:o:1012.2:i:4:0:11:2.5:5.2:4.9:44

I'd like to import those records from the file to the weewx sqlite database. Is there some utility I can use? Any help is appreciated. Thanks in advanced.

Best regards.

mwall

unread,
Dec 22, 2015, 1:13:40 PM12/22/15
to weewx-user


On Tuesday, December 22, 2015 at 10:35:49 AM UTC-5, Nico Gulden wrote:
Hi, 

I have a TFA Nexus too and I already read the records via the driver and the --records option. I now have a file with a bunch of lines looking like this:

1447452420:21.20:68:5.90:87:o:o:o:o:o:o:o:o:1012.2:i:4:0:11:2.5:5.2:4.9:44

I'd like to import those records from the file to the weewx sqlite database. Is there some utility I can use? Any help is appreciated. Thanks in advanced.


nico,

thanks to significant contributions from andrew miles, we recently updated the te923 driver to read station memory automatically when weewx starts up. it is not yet fully tested, but you're welcome to have a go at it.

https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/te923.py

be sure to backup your weewx database before you use the driver.

m

ma...@erwinheger.de

unread,
Dec 22, 2015, 2:03:06 PM12/22/15
to weewx...@googlegroups.com
Sounds pretty good. I'll give it a try after christmas, i own a TFA Sinus. Thx, and: merry christmas to all of you guys, you do a great job with weewx!

Erwin Heger
--
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.
For more options, visit https://groups.google.com/d/optout.

J.L. Blom

unread,
Dec 26, 2015, 8:23:57 AM12/26/15
to weewx...@googlegroups.com
On 22/12/15 20:02, ma...@erwinheger.de wrote:
> Sounds pretty good. I'll give it a try after christmas, i own a TFA
> Sinus. Thx, and: merry christmas to all of you guys, you do a great
> job with weewx!
>
> Erwin Heger
>
> Am 22.12.2015 um 19:13 schrieb mwall <mw...@users.sourceforge.net
> <mailto:mw...@users.sourceforge.net>>:
>
>>
>>
>> On Tuesday, December 22, 2015 at 10:35:49 AM UTC-5, Nico Gulden wrote:
>>
>> Hi,
>>
>> I have a TFA Nexus too and I already read the records via the
>> driver and the --records option. I now have a file with a bunch
>> of lines looking like this:
>>
>> 1447452420:21.20:68:5.90:87:o:o:o:o:o:o:o:o:1012.2:i:4:0:11:2.5:5.2:4.9:44
>>
>> I'd like to import those records from the file to the weewx
>> sqlite database. Is there some utility I can use? Any help is
>> appreciated. Thanks in advanced.
>>
>>
>>
>> nico,
>>
>> thanks to significant contributions from andrew miles, we recently
>> updated the te923 driver to read station memory automatically when
>> weewx starts up. it is not yet fully tested, but you're welcome to
>> have a go at it.
>>
>> https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/te923.py
>>
>> be sure to backup your weewx database before you use the driver.
>>
>> m
>>
>> --
>> 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
>> <mailto:weewx-user+...@googlegroups.com>.
>> For more options, visit https://groups.google.com/d/optout.

Marc,
I own a TFA Nexus and I have been waiting for this update to the TE923
driver since I started with weewx. I have a small question about use
however.
Is it sufficient to replace the driver in the location
/usr/share/weewx/weewx/drivers/ or do I have to use:
wee_config --reconfigure --driver= te923.py
or do I first have to rename the original driver to te923.py.old. I am
still in the begiiners stage of working with python and a lot is still
unclear.
Thanks in advance,
Joep
(www.neuroweave.nl)

mwall

unread,
Dec 26, 2015, 9:54:16 AM12/26/15
to weewx-user
On Saturday, December 26, 2015 at 8:23:57 AM UTC-5, Joep L. Blom wrote:
Is it sufficient to replace the driver in the location
/usr/share/weewx/weewx/drivers/ or do I have to use:
wee_config --reconfigure --driver= te923.py
or do I first have to rename the original driver to te923.py.old.

you can simply replace, but i suggest keeping the old driver in case you need to revert.  you can try wee_config - it is not required, but it will (should) replace your old TE923 stanza with an example of the new observation/schema mapping.

1) shut down weewx

sudo /etc/init.d/weewx stop

2) move aside the old driver

mv drivers/te923.py drivers/te923-orig.py

3) 'install' the new driver

cp ~/Downloads/te923-0.16.py drivers/te923.py

3a) optionally run wee_config to get the new mappings (this is not tested, and if mappings are not specified in weewx.conf the driver will still function using the defaults).

4) start weewx

sudo /etc/init.d/weewx start

a few caveats:

- the new driver uses a completely different mechanism for mapping sensor names to database fields. see DEFAULT_OBSERVATION_MAP in the code for the new sensor names and how they map to wview (and wview extended) schema names.  if you made any changes to sensor_map or battery_map then this will affect you.  sensor_map and battery_map no longer exist.

- see the comments in the code about 'schema additions' about suggested extensions to the wview schema if you have more than one remote sensor.

- although i have been running this for a couple of weeks now on a small memory model te923, it has not been extensively tested.

- andrew figured out how to modify just about every station parameter, and these are exposed via the wee_device utility.  'wee_device --help' to see the options.  these are not fully tested, so any feedback about them would be appreciated.

- record_generation=hardware is intentionally not yet enabled.  however, catchup during startup *is* implemented.

m

J.L. Blom

unread,
Dec 26, 2015, 10:22:16 AM12/26/15
to weewx...@googlegroups.com
> --
> 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
> <mailto:weewx-user+...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.
Marc,
Thanks for your quick reply. I´ll do it asap and let you know the
results. I have used from 09-2010 to 2013-04 weatherdisplay and wview
till 2015-05 and since then weewx, so I have a rather large database but
till now I haven't combined them (I'm also not very accustomed to sql3
coming from a period where we first constructed our own databases and
later used the mother of all databases dbaseII! and then I had a
department and I only had to use the results, all back in the eighties !).)
I know I have to tweak a littlebit the weatherdisplay data and they are
stored in a mysql database but I assume that can be done.
Thanks again for your fast reply.
Joep

J.L. Blom

unread,
Dec 27, 2015, 8:28:27 AM12/27/15
to weewx...@googlegroups.com
On 26/12/15 15:54, mwall wrote:
Marc,
I installed the driver as you said and started weewx. However it gives
many errors also one of unrecognised memory size.
I have attached the part of the log starting with the restart of weewx
(te923-16.txt) to see if you can find how toi solve the problem.
Moreover, I have used wee-device --get-date and that says as date:
27-02-2015 although the 27 is OK the 02 is'nt.
It also gives an interval of 10 (which I think is minutes0 what also is
not the correct number. Maybe you can shed some light on it. (if you
have the time in your holiday).
Joep

te923-16.txt

mwall

unread,
Dec 27, 2015, 11:50:32 AM12/27/15
to weewx-user
On Sunday, December 27, 2015 at 8:28:27 AM UTC-5, Joep L. Blom wrote:
I installed the driver as you said and started weewx. However it gives
many errors also one of unrecognised memory size.

only one process can talk to the station at a time.  it looks like you have weewxd running (process 30773/30777) then you run wee_device (process 30825).  you must stop weewxd before you run wee_device.

m

J.L. Blom

unread,
Dec 27, 2015, 6:18:00 PM12/27/15
to weewx...@googlegroups.com
> --
> 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
> <mailto:weewx-user+...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.
MArc,
Thanks for your reply. Yes, that was indeed an oversight on my side,
however, the errors on line 478 and 479 look more serious. Apparently it
corrected itself but on line 519 there is an error in memory size
, however, after that it started working rather well. When I look in the
standard graphs it seems to work rather well. However, I thought that
missing data would be taken from the history (large memory model) and
filled in. However, if you look at the graphs, for example of insid
temperature you see a gap of about 20 minutes that should be read from
the Nexus memory. Do you have an explanation?
Joep

J.L. Blom

unread,
Dec 29, 2015, 8:22:33 AM12/29/15
to weewx...@googlegroups.com
On 27/12/15 17:50, mwall wrote:
I did some more testing with the new TE923 driver and discovered several
problems which today made it a necessity to return the old driver.
I have added a - part of - the log of today where you can see that the
new driver worked but - after using wee_device suddenly many errors
developed. I had set the date to today as wee_device --get-date gave as
date 1-3-2015 and that apparently worked. I tested wee_device with all
other commands and it seemed to work OK. However, after that weewx did
not start again but gave no errors (as you can see in the log). It
started (as I could see with ps -ef) but generated nothing and the date
of the reports didn't change. I restarted the raspberry PI2 but that had
no effect.
I therefore have - temporarily - reverted to the old driver but
hopefully you can shed some light on this problem as I would like to get
rid of the gaps in recording when for some reason or other weewx is not
running.
Thanks in advance,
Joep

weewx-log-errors-new-TE923-driver.txt

Nico Gulden

unread,
Jan 6, 2016, 2:35:18 AM1/6/16
to weewx...@googlegroups.com
Hello Marc,
Hello fellow weather enthusiasts in this thread,
Thanks for the insight on this. I didn't have the time yet to have a
closer look at this driver and check, if it works with my device. Thanks
Joep for your testing. I have almost the same setup with RPi2, Raspbian
8 and the Nexus connected to it.

My scenario from my initial posting is rather different. The records I
have are an export from another, broken device that I have changed by
now. Therefore, the new device does not have the records in it's memory.

I now look for a way to import the records saved in a text file in the
format I already mentioned, to the weewxdb. Maybe some sql statements
work here, but I don't know which field holds which value for the
database. Maybe somebody could help me there. Thank you.

Best regards.

signature.asc
Reply all
Reply to author
Forward
0 new messages