TFA Klimalogg PRO on RaspberryPi

[Steffen Schroeder]

Hi,

I'm wondering if weewx is supporting TFA Klimalogg PRO (see http://tfa-dostmann.de/ -> search for "klimalogg" - sorry there's not permalink)

Attaching it a Raspberry Pi I do not receive any data. In fact it seems that even the config can't be read.

I try to read the data by an USB transceiver.

Config:

....

debug = 1 

...

    # Set to type of station hardware.  Supported stations include:

    #  Vantage   FineOffsetUSB  Ultimeter

    #  WMR100    WS28xx         WS1

    #  WMR200    WS23xx         CC3000

    #  WMR9x8    TE923          Simulator

    station_type = WS28xx

[WS28xx]

    # This section is for the La Crosse WS-2800 series of weather stations.

    

    # Radio frequency to use between USB transceiver and console: US or EU

    # US uses 915 MHz, EU uses 868.3 MHz.  Default is US.

    transceiver_frequency = EU 

    

    # The station model, e.g., 'LaCrosse C86234' or 'TFA Primus'

    model = LaCrosse WS28xx

    

    # The pressure calibration offset, in hPa (millibars)

    pressure_offset = 0

    

    # The driver to use:

    driver = weewx.drivers.ws28xx

Call:

root@bruezpi:/home/weewx/bin# ./wee_config_ws28xx --debug

Using configuration file /home/weewx/weewx.conf

Driver version 0.32

Querying the station for the configuration...

No data after 30 seconds (press SET to sync)

No data after 60 seconds (press SET to sync)

Log

Oct 25 18:59:41 bruezpi wee_config_ws28xx[2707]: ws28xx: MainThread: driver version is 0.32

Oct 25 18:59:41 bruezpi wee_config_ws28xx[2707]: ws28xx: MainThread: frequency is EU

Oct 25 18:59:41 bruezpi wee_config_ws28xx[2707]: ws28xx: MainThread: altitude is 213.36 meters

Oct 25 18:59:41 bruezpi wee_config_ws28xx[2707]: ws28xx: MainThread: pressure offset is 0.0

Oct 25 18:59:41 bruezpi wee_config_ws28xx[2707]: ws28xx: MainThread: found transceiver at bus=001 device=004

Oct 25 18:59:41 bruezpi wee_config_ws28xx[2707]: ws28xx: MainThread: manufacturer: LA CROSSE TECHNOLOGY

Oct 25 18:59:41 bruezpi wee_config_ws28xx[2707]: ws28xx: MainThread: product: Weather Direct Light Wireless 

Oct 25 18:59:41 bruezpi wee_config_ws28xx[2707]: ws28xx: MainThread: interface: 0

Oct 25 18:59:41 bruezpi wee_config_ws28xx[2707]: ws28xx: MainThread: base frequency: 868300000

Oct 25 18:59:41 bruezpi wee_config_ws28xx[2707]: ws28xx: MainThread: frequency correction: 101656 (0x18d18)

Oct 25 18:59:41 bruezpi wee_config_ws28xx[2707]: ws28xx: MainThread: adjusted frequency: 910580197 (0x364659e5)

Oct 25 18:59:41 bruezpi wee_config_ws28xx[2707]: ws28xx: MainThread: transceiver identifier: 263 (0x0107)

Oct 25 18:59:41 bruezpi wee_config_ws28xx[2707]: ws28xx: MainThread: transceiver serial: 01021801130107

Is that station supported at all? Am I missing something?

Thanks.

Steffen

[mwall]

From log output it looks like a lacrosse transceiver. Are there any lacrosse model markings on the console?

Follow the steps listed in this thread:

https://groups.google.com/forum/m/#!topic/weewx-user/Jrf58FlrbbI

Be sure weewx is not running, then check transceiver, then pair, and so on.

m

[Steffen Schroeder]

Hi,

the console looks like this:

root@bruezpi:/home/weewx/bin# ./wee_config_ws28xx --check-transceiver

Using configuration file /home/weewx/weewx.conf
Driver version 0.32

Checking for transceiver...
Transceiver is present
serial: 01021801130107
id: 263 (0x0107)
root@bruezpi:/home/weewx/bin# ./wee_config_ws28xx --pair

Using configuration file /home/weewx/weewx.conf
Driver version 0.32

Pairing transceiver with console...
Press and hold the [v] key until "PC" appears (attempt 1 of 3)
Press and hold the [v] key until "PC" appears (attempt 2 of 3)
Transceiver is paired to console
root@bruezpi:/home/weewx/bin# ./wee_config_ws28xx --info

Using configuration file /home/weewx/weewx.conf
Driver version 0.32
Querying the station for the configuration...
No data after 30 seconds (press SET to sync)
No data after 60 seconds (press SET to sync)

root@bruezpi:/home/weewx/bin#

The connected devices are:

pi@bruezpi ~ $ dmesg | tail -n 60
[    2.123178] sdhci: Copyright(c) Pierre Ossman
[    2.131765] sdhci: Enable low-latency mode
[    2.186097] mmc0: SDHCI controller on BCM2708_Arasan [platform] using platform's DMA
[    2.198372] mmc0: BCM2708 SDHC host at 0x20300000 DMA 2 IRQ 77
[    2.208878] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.221032] ledtrig-cpu: registered to indicate activity on CPUs
[    2.238926] hidraw: raw HID events driver (C) Jiri Kosina
[    2.249083] usbcore: registered new interface driver usbhid
[    2.261362] Indeed it is in host mode hprt0 = 00021501
[    2.273022] usbhid: USB HID core driver
[    2.286345] TCP: cubic registered
[    2.309226] Initializing XFRM netlink socket
[    2.326106] NET: Registered protocol family 17
[    2.334808] Key type dns_resolver registered
[    2.368221] mmc0: read SD Status register (SSR) after 2 attempts
[    2.379289] registered taskstats version 1
[    2.403146] mmc0: new high speed SDHC card at address aaaa
[    2.413858] Waiting for root device /dev/mmcblk0p2...
[    2.434456] mmcblk0: mmc0:aaaa SL16G 14.8 GiB
[    2.445524]  mmcblk0: p1 p2
[    2.556301] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    2.572699] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.585747] Indeed it is in host mode hprt0 = 00001101
[    2.595364] VFS: Mounted root (ext4 filesystem) on device 179:2.
[    2.617116] devtmpfs: mounted
[    2.625059] Freeing unused kernel memory: 140K (c05bd000 - c05e0000)
[    2.826484] usb 1-1: New USB device found, idVendor=0424, idProduct=9512
[    2.838724] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.851556] hub 1-1:1.0: USB hub found
[    2.860132] hub 1-1:1.0: 3 ports detected
[    3.146373] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    3.256651] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    3.274848] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.292582] smsc95xx v1.0.4
[    3.361349] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:95:dc:4f
[    3.486306] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
[    3.612769] usb 1-1.2: New USB device found, idVendor=6666, idProduct=5555
[    3.626169] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.638247] usb 1-1.2: Product: Weather Direct Light Wireless Device
[    3.649392] usb 1-1.2: Manufacturer: LA CROSSE TECHNOLOGY
[    3.659589] usb 1-1.2: SerialNumber: 0123456
[    3.739141] hid-generic 0003:6666:5555.0001: hiddev0,hidraw0: USB HID v1.11 Device [LA CROSSE TECHNOLOGY Weather Direct Light Wireless Device] on usb-bcm2708_usb-1.2/input0
[    3.876377] usb 1-1.3: new full-speed USB device number 5 using dwc_otg
[    4.004538] usb 1-1.3: New USB device found, idVendor=046d, idProduct=c52b
[    4.026304] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    4.054435] usb 1-1.3: Product: USB Receiver
[    4.073802] usb 1-1.3: Manufacturer: Logitech
[    4.100850] input: Logitech USB Receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/input/input0
[    4.136888] hid-generic 0003:046D:C52B.0002: input,hidraw1: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-bcm2708_usb-1.3/input0
[    4.197421] input: Logitech USB Receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.1/input/input1
[    4.234827] hid-generic 0003:046D:C52B.0003: input,hiddev0,hidraw2: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-bcm2708_usb-1.3/input1
[    4.288164] hid-generic 0003:046D:C52B.0004: hiddev0,hidraw3: USB HID v1.11 Device [Logitech USB Receiver] on usb-bcm2708_usb-1.3/input2
[    4.521443] udevd[156]: starting version 175
[    6.483689] bcm2708-i2s bcm2708-i2s.0: Failed to create debugfs directory
[   11.188561] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   11.760310] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   20.769015] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   22.309029] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[   27.293216] Adding 102396k swap on /var/swap.  Priority:-1 extents:1 across:102396k SSFS
pi@bruezpi ~ $ lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 6666:5555 Prototype product Vendor ID

And the system log is telling me:

Oct 26 12:58:20 bruezpi wee_config_ws28xx[2277]: ws28xx: RFComm: console is paired to device with ID 0107
Oct 26 12:58:44 bruezpi wee_config_ws28xx[2279]: ws28xx: MainThread: driver version is 0.32
Oct 26 12:58:44 bruezpi wee_config_ws28xx[2279]: ws28xx: MainThread: frequency is EU
Oct 26 12:58:44 bruezpi wee_config_ws28xx[2279]: ws28xx: MainThread: altitude is 213.36 meters
Oct 26 12:58:44 bruezpi wee_config_ws28xx[2279]: ws28xx: MainThread: pressure offset is 0.0
Oct 26 12:58:44 bruezpi wee_config_ws28xx[2279]: ws28xx: MainThread: found transceiver at bus=001 device=004
Oct 26 12:58:44 bruezpi wee_config_ws28xx[2279]: ws28xx: MainThread: manufacturer: LA CROSSE TECHNOLOGY
Oct 26 12:58:44 bruezpi wee_config_ws28xx[2279]: ws28xx: MainThread: product: Weather Direct Light Wireless
Oct 26 12:58:44 bruezpi wee_config_ws28xx[2279]: ws28xx: MainThread: interface: 0
Oct 26 12:58:44 bruezpi wee_config_ws28xx[2279]: ws28xx: MainThread: base frequency: 868300000
Oct 26 12:58:44 bruezpi wee_config_ws28xx[2279]: ws28xx: MainThread: frequency correction: 101656 (0x18d18)
Oct 26 12:58:44 bruezpi wee_config_ws28xx[2279]: ws28xx: MainThread: adjusted frequency: 910580197 (0x364659e5)
Oct 26 12:58:44 bruezpi wee_config_ws28xx[2279]: ws28xx: MainThread: transceiver identifier: 263 (0x0107)
Oct 26 12:58:44 bruezpi wee_config_ws28xx[2279]: ws28xx: MainThread: transceiver serial: 01021801130107

So to me, it looks like pairing was successful - however reading the configuration fails.

Can/Should i add some debug statements to the driver?

Thanks and regards,

Steffen

[mwall]

On Sunday, October 26, 2014 8:06:46 AM UTC-4, Steffen Schroeder wrote:

So to me, it looks like pairing was successful - however reading the configuration fails.

Can/Should i add some debug statements to the driver?

steffen,

from the output you posted it looks like everything is working properly.  after you do:

wee_config_ws28xx --info

you must press the [SET] button otherwise the transceiver will timeout as it waits for a sync with the station.

m

[Steffen Schroeder]

Pressing the "SET" key was not successful. (already tried that before)

The KlimaLogg Pro has a dedicated key for syncing called "USB". Pressing it long creates a link between at tranceiver and the statation. Pressing it shortly established a connection between known transceiver / station.

This works well on windows with the proprietary software from TFA. 

Any other ideas?

[mwall]

On Sunday, October 26, 2014 4:01:49 PM UTC-4, Steffen wrote:

Pressing the "SET" key was not successful. (already tried that before)

The KlimaLogg Pro has a dedicated key for syncing called "USB". Pressing it long creates a link between at tranceiver and the statation. Pressing it shortly established a connection between known transceiver / station.

This works well on windows with the proprietary software from TFA. 

Any other ideas?

so does a short press of the USB button do a sync when 'wee_config_ws28xx --info' is running?

if you run weewx, do you see the station sync at the top of the hour?  shortly before the hour, with debug=1 in weewx.conf, run weewx directly

sudo weewxd /etc/weewx/weewx.conf

then watch the log.  you should see messages that indicate whether the station is paired to the transceiver, as well as whether the transceiver detects and maintains sync at the top of the hour.

m

[mwall]

On Sunday, October 26, 2014 8:06:46 AM UTC-4, Steffen wrote:

So to me, it looks like pairing was successful - however reading the configuration fails.

Can/Should i add some debug statements to the driver?

steffen,

based on this manual, it sounds like a long press on the USB button is pairing (the [v] key on lacrosse stations) and a short press on the USB button is sync (short press of the [SET] key on lacrosse stations):

http://www.produktinfo.conrad.com/datenblaetter/375000-399999/396442-an-01-ml-TFA_30_3039IT_KLIMALOGG_P_de_en_fr_nl_pt.pdf

you can get more information from the driver by enabling various debug flags.  see the postings by luc in this thread:

https://groups.google.com/forum/#!topic/weewx-user/Jrf58FlrbbI

luc's posting also includes examples of the log from his weather station so you will understand what to expect.

since the klimalogg pro supports up to 8 sensors, i would guess that the data format will be different than the lacrosse stations.  if that is the case then we can figure out the format by sniffing the usb data transfers (luc has good experience with this).

m

[Steffen]

M,

pairing seams to be successful.

However reading data might fail.

There are many NAKs in the log (assuming a response of 15h = NAK [ASCII-wise it is, but not sure if it's ASCII ;-)]).

Please find attached the debug log.

At least while polling and pressing USB button I get an answer from the station.

How can i Interprete them now?

Please find log attached (double lines omitted)

Thanks,

Steffen

[Luc Heijst]

On Monday, 27 October 2014 15:32:55 UTC-3, Steffen wrote:

M,

pairing seams to be successful.

However reading data might fail.

There are many NAKs in the log (assuming a response of 15h = NAK [ASCII-wise it is, but not sure if it's ASCII ;-)]).

Please find attached the debug log.

At least while polling and pressing USB button I get an answer from the station.

How can i Interprete them now?

Please find log attached (double lines omitted)

Thanks,

Steffen

Hi Steffen,

Excuse me that I break in your thread. 

I assisted M(atthew Wall) with analyzing the data between a TFA Primus/Opus and the ws28xx driver. I used an USB sniffer program on the laptop where TFA's program HeavyWeatherPro was installed.

I started the capture of the USB trafic and started HeavyWeatherPro and synhronised the program with the USB dongle of the weather station.

The next step was to perform one by one the functions of HeavyWeatherPro, like setting/changing parameters, reading history data and so on.

The next step was analyzing the captured data. It helps if you know which data was set or read, so I kept notes at what time I changed things or started an action.

Now for your weather station. I looks like some of the protocol for the TFA Primus/Opus can be used for your station.

Other functions and data work different. What I see in your log file is probably the weather message, The problem is that I don't know yet the meaning of that data.

What we could do is analyse your data traffic between KlimaLogg Pro and the USB-dongle with an USB-sniffer and compare that data with all data that is available via program KlimaLogg Pro.

Also we could look at the three KlimaLogg data files in map: C:\Users\your_name\AppData\Roaming\KlimaLoggPro. Furthermore your weatherdata can be exported to a csv-file.

If you are willing to help, we can try figure out the protocol your station is using and add a new driver for it to weewx as soon as the protocol is working correctly. I must warn you: this process can take much of your time!

Luc

BTW. The 15h messages are no NAKS. The weather station (or the USB dongle) continuous sends state 15h (sometimes 14h). The messages are preceded by a 16h state.

[Steffen Schroeder]

Hi Luc,
Yes I'm willing to help. So what can I do?

Best,
Steffen

--
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/O1ogABfGETA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Luc Heijst]

On Monday, 27 October 2014 17:08:49 UTC-3, Steffen wrote:

Hi Luc,
Yes I'm willing to help. So what can I do?

Best,
Steffen

Thanks for your help Steffen. We will have contact via mail.

Luc 

[Luc Heijst]

Status update

By means of captured data between the USB transceiver and windows program KlimaLoggPro (thanks Steffen for your assistance) we could analyze the current weather messages and the historical data messages. See attachments.

The writing of a KlimaLog driver for weewx is put on hold for the moment because the communication won't start without user intervention (pushing the USB key on the weather station).

I have contacted the technical staff of TFA Dostmann about this. May be there is a manner to bypass the manual start trigger.

Luc 

[Bernhard Kohn]

Hi, 

I am also trying to get the data of the KlimaLoggPro. But I think, it is maybe worth not to read out the KlimaLoggPro directly, but instead try to receive with an 868 receiver the signals of the sensor elements? In the fhem forum there is a message (in german), which say's is possible by using a Jeelink receiver. Just as an idea.

best regards

  Bernhard

[Luc Heijst]

Hi all,

Attached the description of the message types of the TFA KlimaLogg Pro weather station.

The meaning of the bytes of the read/wrte config message is not known yet.

The protocol has similarities with the TFA Primus/Opus / LaCrosse WS2800 weather stations.

Note: The protocol contains Request Send Time / Send Time messages. Not sure what the weather station will do with the sent date/time when the station is configured for the DCF-77 synchronised clock.

Luc

[Luc Heijst]

KlimaLogg Pro Message Types Version 0.2

Luc

[Luc Heijst]

On Saturday, 1 November 2014 18:15:40 UTC-3, Luc Heijst wrote:

I have contacted the technical staff of TFA Dostmann about this. May be there is a manner to bypass the manual start trigger.

 

I've got the following answers from TFA Dostmann:

"we must inform you that the connecting from the data recorder “KlimaLogg Pro” to the software is only possible wit user intervention, so it is necessary to push the “USB” button to get connected." 

and

"Our supplier, which has programed the KlimaLogg Pro does no more change this application. We are sorry to not give you better informations."

Luc

[Jérôme]

All,

I have also contacted TFA a few months back, and got the same answer ;-)

In the mean time, I have been investigating a little bit on my side and have seen that once you have paired your device with the USB button, there a KlimaloggService that is getting the data very few seconds. It puts that in a file that you can monitor to get "real time" data.

There is NO need to press the USB button anymore after, even if you restart the computer (as long as it's very fast), the service will start and directly gather the data.

Therefore, I would say that if we can get the "current" data from the USB dongle, even if no history, that is very fine by me, because the history can be done automatically by the Raspberry Pi, little by little.

Was anybody able to read the current data from the USB dongle on Linux ? Even if it's just displaying on the command line or something ?

Thanks,
Jérôme

[Luc Heijst]

Hi Jerome,
The ws28xx driver was able to read the current weather messages of the KlimaLogg Pro. Because the data differs from the Ws28xx devices the driver didn't recognize these messages and the proper replies were not sent. As a test I will modify the ws28xx driver in such a way that it will read the current weather messages of the KlimaLogg Pro.
I don't own a KlimaLogg Pro weather station myself, so I need your help to test the driver. If you agree we will have further contact via mail.
Luc

[Luc Heijst]

To all,

Status update KlimaLogg (Pro) driver for weewx.

I started with writing a kl.py (KlimaLogg) driver based upon the logic of the ws28xx driver. The first goal is to receive the current weather messages and store the data in the weewx database. 

Eventually we can provide a catchup function for the historic data in case of missed messages (during a power cut).

Reading and writing the configuration parameters is not planned because it's a lot of work to decipher the message format. An exception may be the reading/writing of the history interval parameter (to set it to 5 min).

Kl driver version 0.3 reads the current weather messages. Because the weather station can have 0-8 extra temp/hygro sensors we have to find a way to skip the data of the non-existing sensors.

The good news is that -once the usb-transceiver is paired with the software- the USB button is not needed anymore to start synchronisation. Jérôme, who is testing the driver for us, wrote: "once the sync has been done with the transceiver, even on another machine (it was on my windows, with the real software), you never have to do it again. Pressing "USB" will just trigger a new message to be sent (history I believe), but if you do nothing, nearly every 10 seconds, you get an updated value (of current weather).".

Luc

[Steffen Schroeder]

Hi,

Although I found another (wired) solution for my project, this sounds promising. Will try the kl driver 0.3

Best,

Steffen

[Jérôme Patey]

It doesn't add data to weewx yet, but if you check the syslog, you'll see the temperatures.

The wired version you're using involves direct wiring to the base station ?

--

jer...@patey.net

[Steffen Schroeder]

Hi,

I'm not using the wired version of TFA KlimaLogg. 

I started together with Luc Reengeneering KlimaLogg PRO. Since we came to the intermediate result that for reconnection pressing of USB is needed - I stepped way from KlimaLogg and started with a self made (wired DHT22) version.

For my use case getting the data is sufficient. No need to store the date in a DB.

Kind regards,

Steffen

[Kai]

Hi Luc,

could you post your kl.py-Python code and a short explanation if it's done?

Thanks
Kai

[Luc Heijst]

On Thursday, 18 December 2014 06:22:34 UTC-3, Kai wrote:

could you post your kl.py-Python code and a short explanation if it's done?

Hi Kai,

I will send you the driver by email.

Luc 

[BORIS]

Hello Luc and Kai,
I am running a WMR88 with weewx on a Ubuntu Netbook. I also have a TFA Klimalogg PRO for temperature and humidity logging.
I would be interested in adding these temperature and humidity measurements to my weewx server, or as an alternative to run a second weewx program on the same Netbook if possible.
Since you have a working driver kl.py I would like to test it on my system. I have only basic knowlege of Python and Linux, but willing to learn more.

Regards
Boris

[walterli]

Hi Luc, Kai and Boris,

I'm as well owner of a KlimaLogg Pro and currently looking for a way to connect it to my NAS (Synology) which runs on unix. I would like to read the data from the KlimaLoggPro and store it to any database (txt-file, mySQL, ...) on my NAS.

This thread looks promising. I therefore installed "weewx" on my NAS. Starting weewx as a process with station_type = WS28xx, it is immediately stopped. When plugging in the USB receiver of the KlimaLogg Pro, and then starting weewx it continues to run, but no data is transferred. However, when unplugging in this state the USB receiver I get an error message. For me this means, the receiver is somehow recognized.

Like Boris, I'm wondering if it is possible to contribute somhow to the developpement of a driver for the KlimaLogg. I'm also not skilled in Python and Linux, but in other related fields like Modbus. I could imagine to help figuring out the used protocol for the data exchange with KlimaLogg Pro...

Regards walterli

[Luc Heijst]

Hello Boris and walterli,

The kl-driver is not finished yet. It currently reads the current weather messages and doesn't store anything yet in the weewx database.

There might be an issue with loosing communication round 02:00-03:00 AM, we are investigating how to solve this.

I will send you the current driver by mail.

Cheers, Luc

[Luc Heijst]

To all KlimaLoggPro weather station users,

My -not-finished-yet- kl-driver was written for weewx v2.7.0.

Now it is converted to weewx v3! :-)

So, if you want to join in to test this driver, be sure you are running weewx v3!

Cheers, 

Luc

[MP]

Luc,

can you send me a link to the driver/ the driver, too?

Thanks.

[Luc Heijst]

Hello MP,

Welcome to the club of KlimaLogg driver testers!

The first release of the driver that wrote data to the weewx database got an error. As soon as this error is fixed I will send you the driver with installation instructions by mail.

Luc

[Luc Heijst]

Status update KlimaLogg Pro driver.

Version 0.15 reads each 7 second period the current weather data from the weather station. Each 10 second period a loop packet is send to weewx.
Sensor data which is 'None' (of non-existing extra sensors) is not written to the loop packet.
The results of the loop packets are stored in the weewx database each 5 minutes.

The latest history data is read each history interval (from 1 min to 6 hours) and printed to the log file. Eventually this data can be used for catchup (not implemented).

Luc

[Michael Schulze]

I'm also very interested in testing the new driver. I just got a Klimalogg PRO and installed weewx on my Raspi, for now simulation mode.

Thanks for your work,
Michael

[Luc Heijst]

Michael,

Welcome and a Happy New Year! 

I will send you the driver and instructions by mail.

Luc

[Christian]

Hi Luc and all other in this Group,

Happy New Year!

Can you please send me the driver. Im very interested. Thanks for your work.

Thanks

Christian

[Florian]

Dear Luc,

Happy New Year!

Hopefully I'll get my Klimalogg Pro tomorrow.

So I'm interested in testing your driver.

Did I understand that:

-I pair the transmitters with the Klimalogg Pro Station.
-I press USB to send data to my PC with installed TFA Software

-PC imports the complete History stored in the Klimalogg Pro Station (max. 50.000 records)

-After that, the Klimalogg Pro Station sends current records (realtime) of all paired sensors?

-I can turn of my PC/close TFA Software?

-I can then receive these values with weewx on the raspberry pi?

-The Klimalogg Pro Station continuously stores records. Will it then reach its' storage limit or won't the data be stored?

Thanks in advance

Florian

  

Am Mittwoch, 31. Dezember 2014 16:34:52 UTC+1 schrieb Luc Heijst:

[Luc Heijst]

Hello Christian and Florian,

I will mail you the KlimLogg driver with installation instructions.

See my answers below.

Cheers, Luc

On Friday, 2 January 2015 09:18:34 UTC-3, Florian wrote:

Dear Luc,

Happy New Year!

Hopefully I'll get my Klimalogg Pro tomorrow.

So I'm interested in testing your driver.

Did I understand that:

-I pair the transmitters with the Klimalogg Pro Station.

lh: I think so, check the KlimaLogg documentation

 

-I press USB to send data to my PC with installed TFA Software

lh. There is a difference in the duration of the press.

a. long press until KlimaLogg beeps for pairing the USB-transceiver with the KlimaLoggPro windows program and/or the weewx program. 

b. short pres when communication is lost after startup to synchronise communication again (for both KlimaLogPro and weewx priograms)

-PC imports the complete History stored in the Klimalogg Pro Station (max. 50.000 records)

lh: Yes Note. This functionality will also be build in the weewx KlimaLogg driver (hopefully implemented by the end of January)

-After that, the Klimalogg Pro Station sends current records (realtime) of all paired sensors?

lh: Yes, and also history records each history interval (from 1 min to 6 hours, typical 15 min)

 

-I can turn of my PC/close TFA Software?

lh: Yes 

-I can then receive these values with weewx on the raspberry pi?

lh: Yes, move your USB transceiver to your RPI., Remember to do the pairing as described in the installation instructions

 

-The Klimalogg Pro Station continuously stores records. Will it then reach its' storage limit or won't the data be stored?

lh: The KlimaLogg Pro station has a circular history buffer. When it reaches it's limit of 50,000 records it will start over at record 1 (the eldest record) and continues. So you allways have the most recent 50,000 history records 

[Lars]

Hi Luc,

Happy New Year to you and all others in this group. I have a Raspberry and a Klimaloog PRO and I am seeking for a way to evalualte the data of the sensors automatically. In the first step I want to use it with WeeWX. It would be nice, if yu could sent me the driver for testing.

Lars

[Luc Heijst]

Hi Lars,

Version 0.23 of the KlimaLogg driver is ready to use. It will store the data of the KlimaLogg Pro and extra sensors tot the weewx datatabase.

I must warn you: once you have seen all you can do with weewx you might never do a second step! See the weewx showcase at: http://www.weewx.com/showcase.html

I will send you the driver and installation instructions by email.

Success!

Luc

[Stefan Schoone]

Hi Luc,

I'm interesting in testing my Klimalogg Pro on my RPi. Could you please send me your driver per Mail?

I'v got 7 sensors connected with my basestation and i'd like you test this with weewx.

Thanks and greetings from Germany,

 Stefan

[Luc Heijst]

Hi Stefan,

Seven sensors, wow! You're the record holder in this group!

Luc

[Raimund Walter]

Hi,

very interesstin. can you send me the driver too ?. i want to test it on my nas, can you send me the source too ?

regards

raimund walter

Am Dienstag, 6. Januar 2015 17:05:36 UTC+1 schrieb Luc Heijst:

[Luc Heijst]

Hi Raimund,

The driver is written in Python, so the driver and the source are the same! 

I will send you driver and installation instructions by mail.

Luc

[Jens Remus]

This thread looks promissing! Once in a while I search Google whether someone has finally figured out how to use the TFA Klimalogg Pro with Linux, preferably on a Rasbperry Pi. I had actually given up any hope.

I own a Klimalogg Pro with three (soon five) sensors and would be glad to participate! Can you please put me on your distribution list?

I just need to get up to speed with WeeWX. But that should not be too difficult.

Are there any plans to move the driver development to e.g. GitHub, so that others might contribute?

Thanks in advance and greetings from Stuttgart, Germany,
Jens

[Luc Heijst]

Hi Jens,

When finished the KlimaLogg driver will be a part of the weewx distribution. The development of weewx will probably switch to GitHub soon.

I will send you the latest driver (v0.26_6) with installation instructions by mail.

Luc

[Luc Heijst]

Status update KlimaLogg drivers v0.26_8 and v0.27_14

Version v0.26_8  is sent to all new KlimaLogg testers.

- reads the current weather messages and stores them in the weewx database

- logs the actual history messages

Version v027_14 is the extended driver with extra funtions sent to all who want to participate (and have to test and report regularly!)

- time setting of the klimalogg station

- reading config parameters

- catchup of history recordss in case the weewx database misses data (limited to a fixed number of records)

TODO:

- study the alchoritm when the history buffer reaches its maximum and apply this to the klimalogg driver

- checking the format of the various config parameters

- checking the working of catchup history data

- writing the configuration parameters back to the klimalogg station when needed (Alarms might disturb the communication. If so the alarms will be switched off. The history interval might be controlled via weewx.conf)

- the DCF time reading did disturb the communication with the klimalogg driver in a number of ways. Maybe we switch this functiion off in the klimalogg driver

Cheers, Luc

[Rainer Böhme]

Hi Luc,

seems to be a hot topic. :-)

Im currently using a Klimologg PRO with 6 sensor. I would be happy to participate in the test, too.

So it would be great if you send me the driver.

Greetings from Leipzig, Germany,
Rainer

[Luc Heijst]

Hi Rainer,

Welcome to the group of KlimaLogg driver testers!

Today I made progress with the extended driver v0.27_18.

For now I will send you the standard driver v0.26_8.

Cheers, Luc

[Luc Heijst]

Status update KlimaLogg Pro driver for weewx versions v0.26_10 (normal driver) and v0.27_23 (extended driver).

Finally the extended driver runs without errors!

Beside all functions the normal driver has, this driver reads and logs the config parameters and does at startup a catchup of missed data with the data of the historical records of the KlimaLogg station.

Things TODO:

- get time setting working when asked by the station

- get time setting working when initiated by the kl driver

- check recordnumber behaviour when the history record reaches its maximum of 50,000 records and when known, adjust the driver logic.

- translate the sensor descriptions to readable format

- check the history catchup mechanism when the driver has been stopped for a period

- check writing back the config parameters when a parameter is changed (by the driver)

- if the communication stalls: find a way to get it started again without user intervention

Luc

[Philipp Berger]

Hi Luc,

can you please send me your excellent driver?

Greetings from vienna

[Lars]

Hi Luc,

Tank you and all the testers for the very good work. I can see the data of my 4 sensors ( 4 temperatures and 4 humidities) in the systlog file. 

I followed the weewx customisation guide and came to the conclusion that for displaying  additional sensors via html I had to follow the chapter "defining new tags". For the fist 2 sensors I use inTemp, inHumidity and outTemp, out Humidity. Is this correct or is there a more "simple" way?

Lars

Am Dienstag, 6. Januar 2015 17:05:36 UTC+1 schrieb Luc Heijst:

[Luc Heijst]

Hi Lars,

The method you mention is for tags which don't exist yet. But all your KlimaLogg tags are right in the weewx database!

What you could do is the following:

Graphs

======

To show the data of all sensors, change file skin.conf in the weewx/skins/Standard directory

Look for the sections with day, week, month and year plots and replace the rain, wind 

and other graphs you don't need with temp and humidity graphs like in the sample below.

Note: This example uses the standard sensor_mapping of the KlimaLogg driver.

[[day_images]]

image_width = 500

image_height = 200

x_label_format = %H:%M

bottom_label_format = %d.%m.%Y %H:%M

time_length = 86400 # == 24 hours

show_daynight = true

line_gap_fraction = 0.1

[[[daytemp1]]]

[[[[inTemp]]]]

label = Inside temp

[[[[outTemp]]]]

label = fill in the  name of your sensor 1 temp

[[[[extraTemp1]]]]

label = fill in the  name of your sensor 2 temp

[[[[extraTemp2]]]]

label = fill in the  name of your sensor 3 temp

[[[[extraTemp3]]]]

label = fill in the  name of your sensor 4 temp

[[[daytemp2]]]

[[[[soiltemp1]]]]

label = fill in the  name of your sensor 5 temp

[[[[soiltemp2]]]]

label = fill in the  name of your sensor 6 temp

[[[[soiltemp3]]]]

label = fill in the  name of your sensor 7 temp

[[[[soiltemp4]]]]

label = fill in the  name of your sensor 8 temp

[[[dayhumidity1]]]

[[[[inHumidity]]]]

label = Inside humidity

[[[[outHumidity]]]]

label = fill in the  name of your sensor 1 humidity

[[[[extraHumid1]]]]

label = fill in the  name of your sensor 2 humidity

[[[[extraHumid2]]]]

label = fill in the  name of your sensor 3 humidity

[[[[leafWet1]]]]

label = fill in the  name of your sensor 4 humidity

[[[dayhumidity2]]]

[[[[soilMoist1]]]]

label = fill in the  name of your sensor 5 humidity

[[[[soilMoist2]]]]

label = fill in the  name of your sensor 6 humidity

[[[[soilMoist3]]]]

label = fill in the  name of your sensor 7 humidity

[[[[soilMoist4]]]]

label = fill in the  name of your sensor 8 humidity

[[week_images]]

image_width = 500

image_height = 200

x_label_format = %d

bottom_label_format = %d.%m.%Y %H:%M

time_length = 604800 # == 7 days

aggregate_type = avg

aggregate_interval = 3600 # == 1 hour

show_daynight = true

[[[weektemp1]]]

[[[[inTemp]]]]

label = Inside temp

[[[[outTemp]]]]

label = fill in the  name of your sensor 1 temp

[[[[extraTemp1]]]]

label = fill in the  name of your sensor 2 temp

[[[[extraTemp2]]]]

label = fill in the  name of your sensor 3 temp

[[[[extraTemp3]]]]

label = fill in the  name of your sensor 4 temp

[[[weektemp2]]]

[[[[soiltemp1]]]]

label = fill in the  name of your sensor 5 temp

[[[[soiltemp2]]]]

label = fill in the  name of your sensor 6 temp

[[[[soiltemp3]]]]

label = fill in the  name of your sensor 7 temp

[[[[soiltemp4]]]]

label = fill in the  name of your sensor 8 temp

[[[weekhumidity1]]]

[[[[inHumidity]]]]

label = Inside humidity

[[[[outHumidity]]]]

label = fill in the  name of your sensor 1 humidity

[[[[extraHumid1]]]]

label = fill in the  name of your sensor 2 humidity

[[[[extraHumid2]]]]

label = fill in the  name of your sensor 3 humidity

[[[[leafWet1]]]]

label = fill in the  name of your sensor 4 humidity

[[[weekhumidity2]]]

[[[[soilMoist1]]]]

label = fill in the  name of your sensor 5 humidity

[[[[soilMoist2]]]]

label = fill in the  name of your sensor 6 humidity

[[[[soilMoist3]]]]

label = fill in the  name of your sensor 7 humidity

[[[[soilMoist4]]]]

label = fill in the  name of your sensor 8 humidity

[[month_images]]

image_width = 500

image_height = 200

x_label_format = %d

bottom_label_format = %d.%m.%Y %H:%M

time_length = 2592000 # == 30 days

aggregate_type = avg

# aggregate_interval = 86400 # == 24 hours

aggregate_interval = 10800 # == 3 hours

[[[monthtemp1]]]

[[[[inTemp]]]]

label = Inside temp

[[[[outTemp]]]]

label = fill in the  name of your sensor 1 temp

[[[[extraTemp1]]]]

label = fill in the  name of your sensor 2 temp

[[[[extraTemp2]]]]

label = fill in the  name of your sensor 3 temp

[[[[extraTemp3]]]]

label = fill in the  name of your sensor 4 temp

[[[monthtemp2]]]

[[[[soiltemp1]]]]

label = fill in the  name of your sensor 5 temp

[[[[soiltemp2]]]]

label = fill in the  name of your sensor 6 temp

[[[[soiltemp3]]]]

label = fill in the  name of your sensor 7 temp

[[[[soiltemp4]]]]

label = fill in the  name of your sensor 8 temp

[[[monthhumidity1]]]

[[[[inHumidity]]]]

label = Inside humidity

[[[[outHumidity]]]]

label = fill in the  name of your sensor 1 humidity

[[[[extraHumid1]]]]

label = fill in the  name of your sensor 2 humidity

[[[[extraHumid2]]]]

label = fill in the  name of your sensor 3 humidity

[[[[leafWet1]]]]

label = fill in the  name of your sensor 4 humidity

[[[monthhumidity2]]]

[[[[soilMoist1]]]]

label = fill in the  name of your sensor 5 humidity

[[[[soilMoist2]]]]

label = fill in the  name of your sensor 6 humidity

[[[[soilMoist3]]]]

label = fill in the  name of your sensor 7 humidity

[[[[soilMoist4]]]]

label = fill in the  name of your sensor 8 humidity

[[year_images]]

image_width = 500

image_height = 200

x_label_format = %b

bottom_label_format = %d.%m.%Y %H:%M

time_length = 31622400 # == 366 days

aggregate_type = avg

aggregate_interval = 259200 # == 3 days

[[[yeartemp1]]]

[[[[inTemp]]]]

label = Inside temp

[[[[outTemp]]]]

label = fill in the  name of your sensor 1 temp

[[[[extraTemp1]]]]

label = fill in the  name of your sensor 2 temp

[[[[extraTemp2]]]]

label = fill in the  name of your sensor 3 temp

[[[[extraTemp3]]]]

label = fill in the  name of your sensor 4 temp

[[[yeartemp2]]]

[[[[soiltemp1]]]]

label = fill in the  name of your sensor 5 temp

[[[[soiltemp2]]]]

label = fill in the  name of your sensor 6 temp

[[[[soiltemp3]]]]

label = fill in the  name of your sensor 7 temp

[[[[soiltemp4]]]]

label = fill in the  name of your sensor 8 temp

[[[yearhumidity1]]]

[[[[inHumidity]]]]

label = Inside humidity

[[[[outHumidity]]]]

label = fill in the  name of your sensor 1 humidity

[[[[extraHumid1]]]]

label = fill in the  name of your sensor 2 humidity

[[[[extraHumid2]]]]

label = fill in the  name of your sensor 3 humidity

[[[[leafWet1]]]]

label = fill in the  name of your sensor 4 humidity

[[[yearhumidity2]]]

[[[[soilMoist1]]]]

label = fill in the  name of your sensor 5 humidity

[[[[soilMoist2]]]]

label = fill in the  name of your sensor 6 humidity

[[[[soilMoist3]]]]

label = fill in the  name of your sensor 7 humidity

[[[[soilMoist4]]]]

label = fill in the  name of your sensor 8 humidity

Success!

Luc

[Luc Heijst]

Hi Philipp,

I will send you the latest extended driver.

Luc

[Luc Heijst]

Status update KlimaLogg Pro driver for weewx version 0.28_3

We are almost there!

Changelog:

- added detailed config parameter logging

- translated the sensor descriptions to readable format

- increased maximum number of history messages to use for catchup from 20 to 1500

- checked OK: the history catchup mechanism when the driver has been stopped for a period

- checked OK: writing back the config parameters when a parameter is changed (by the driver)

Things TODO:

- check if the time setting has effect when sent to the station

- check if the communication still stalls

- check recordnumber behaviour when the history record reaches its maximum of 50,000 records (and when known, adjust the driver logic).

Luc

[Sven]

Hi Luc,

it's sounds great and I'll test your excellent driver!

If it's possible please sent me the driver an the instruction?!

Thanks and greetings from Germany,

Sven

[Patrick Metz]

Hi Luc,

thank you for your work. Could you please send me the driver and the instructions?
Just ordered the Klimalogg Pro and missed to check if there is Linux support for this. :-(

Cheers,
Patrick

[Luc Heijst]

Hello Sven and Patrick,

I will send you the driver with instructions.

Have Fun!

Luc

[hhbcon...@googlemail.com]

Hi Luc,

could you send me the driver, too? Thank you for this very useful piece of software.

Cheers,
Peter

[Luc Heijst]

Status update KlimaLogg Pro driver for weewx version 0.28_10c

We booked successes but also had disappointments.

The unexpected succes was that reading the history records is a lot faster than with the ws28xx stations.

Maybe not a surprise when one knows that the klimalogg station holds six history records per message as the ws28xx driver has one.

The fastest record reception until now is an average of 70 ms for retrieval of one history record.

The disappointment was that the used timing was too fast for a Raspberry Pi model B+.

We had to increase the first sleep wait counter from 300 ms to 360 ms. Not tested yet. On the long run this change can make the driver faster!

The history buffer on the station stores the received history data in order, but the timestamps may be not correct.

Once we noticed that at 03:00 AM the DCF reception software changed the stations clock to a wrong timestamp 4 months ahead! The following day at 02:00 AM this was corrected, but the error lasted 23 hours...

So far we were not able to set the clock of the station with the driver software under normal conditions, buit we are still working at it.

Another disappointment was that the timestamps on the station can have wrong values due to several actions by the user (due to intensive testing of the driver)

For most users this won't happen, so we accept these abnormalities and won't correct them.

Soon we will start polishing the code, which still contains a lot of machine-translated decompiled c++ code, which can be made a lot more efficient for Python.

The result will be a release candidate version available to anyone. When the driver is working good, it will be part of the weewx distribution.

Cheers, Luc

Cheers.

[Luc Heijst]

Hi Peter,

I have sent you the driver code together with the installation instructions.

Maybe you are the last tester before the first release candidate version becomes available to everyone!

Have fun!

Cheers, Luc

PS. Guess what? Urged by all the enthousiastic Klimalogg Pro users I ordered a station myself!

I have to get my Raspberry PI working again to test this station. The next step is to move this station to my Synology DS209+II and combine the data of my ws28xx weather station with the klimalogg pro.I'll keep you informed.

[mika]

Hi Luc,

thats sounds good! You did a great job!!

Could you sent me the driver with the instruction?

Thanks!

[Luc Heijst]

Hi mika (or is it Sven?),

Welcome again to our group of klimalogg driver testers!

You didn't respond on my earlier mail that the alternative email adress you gave me was not good.

I sent you the latest driver with instructions.

[Tim Bellinghausen]

Hi Luc,

could you send me the driver for the Klimalogg pro, please. I received the Klimalogg today and want to use it with WeeWX on my Banana Pi.

Thanks, Tim

[Luc Heijst]

Hi Tim,

I will send you the driver with installation instructions.

I'm curious how the klimalogg driver will perform on a Banana PI. Please send me your syslog/debug log when you have weewx and the driver properly working.

Thanks in advance.

Luc

[Mike Klauser]

Hi Luc,

I'm also very interested in the Klimalogg Pro driver. I own one for many years and want to use it now with WeeWX on a Raspberry Pi 2.

It would be great if you could send me the driver with installation instructions.

Thanks in advance and best regards from Switzerland,

Mike

[Luc Heijst]

Hi Mike,

As far as I know you are the first using this driver on a Rapberry PI 2 model.

Please report how the driver is performing on your system.

I wil mail you the driver with instructions.

Luc

[Gerhard Hempl]

I also ordered a Pi2 and would like to use it to read data from my KlimaLogg Pro.
Therefore I would really appreciate to get the driver, too.

Gerhard

[Luc Heijst]

Status update klimalogg driver for weewx version 0.29p4

The driver code is made more 'Pythonic'. The work is not finished yet, Matthew is working at it.
I came to the conclusion that the KlimaLogg Pro station better can have its own database view due to the many differences with the standard database fields. Yet to be done.
The time set mechanism by the driver only works when the station is initialized. TFA reports that time setting by the driver was not intended. Too bad!

Most KlimaLogg Pro users probably don't have other equipment that uses the same type USB transceiver, like the ws28xx type weather stations have. When you do you might encounter timing problems with both drivers. It appears that an USB transceiver not only receives the messages send by the other transceivers station but also receives the messages that the other transceiver sends to the other station. Both types of messages are recognized and not used in the own driver, but it influences the timing of its own messages in a bad way. Especially messages which are time-critical like the reading/writing of the configuration parameters and the reading of successive messages with historic data. We are still looking for a solution.

Luc

[Gerhard Hempl]

Thank you for the great driver. It worked immediately.
Only my html pages still look a bit weird, but the graphs are generated properly.


Is there some way to get the dew points from all sensors added to the database?
My plan is to use the Klimalogg to monitor the temperature and humidity of different rooms.
The outside sensor is more or less optional.
Therefore I would like to log also multiple dew points.

Would this be possible with that driver? Or would this fit into weewx at all?

Gerhard

[Luc Heijst]

Hi Gerhard,

One of the next releases of the driver will have its own database view. The field names will be (besides three mandatory field names like dateTime): Temp0 .. Temp8, Humidity0 .. Humidity8, Dewpoint0 .. Dewpoint8, Heatindex0 .. Heatindex8 and BatteryStatus0 .. BatteryStatus8.

The last ones still to be detected when someone has a sensor with worn out batteries.

The driver will calculate the dewpoints and heatindexes if the necessary data is present and valid.

Cheers, Luc

[Gerhard Hempl]

Hi Luc,

Thanks, that's great news.
Then I'd better wait for the driver and not mess around with the customization of the database.
I was not aware that the dewpoints are not transmitted by the driver but calculated in the software.

Best Regards
Gerhard

[Pascal Jerney]

Hi Luc!

I also have a KlimaLogg Pro Station and I would like to test your driver with my RaspberryPi.
Could you please send me the driver with instructions by e-mail?

Thank you very much!
Pascal

[Claudius Coenen]

I would like to request the beta driver, too. I'm planning on using it on an intel atom based NAS.

[Luc Heijst]

Hello Pascal and Claudius,

Welcome to our still growing group of klimalogg driver testers!

I will send you the latest driver with installation instructions

Luc

[Günther Huck]

Hello

Your project looks realy great. Have same situation (Raspberry and Klimalogg). Please can you send me the driver and instruction for testing, too?

Thanks in advance

Guenther 

[Luc Heijst]

Status update klimalogg driver for weewx version 0.29p10

The driver is now optimized for Python. Thanks again Matthew for your work!

We are close to test a package distribution of the kl driver (as part of a weewx release). Expected the coming weeks.

We encourage the klimalogg users to use the klimalogg database schema (klschema) instead of the standard wview schema.

A package of a driver with its own database schema is not done before, so we need more testing...

I plan to stop in the near future the support for the wview schema for the KlimaLogg station because the klschema is better in many ways for this station.

As an owner of a TFA Opus weather station I tried to let two instances of weewx work together with the TFA Opus and TFA KlimaLogg Pro.

This resulted in many unexpected received data (from the other station) in each of the two drivers which influenced the timing in a bad way and caused on the long run a stall of the communication of both drivers.

As a workaround I will test the following:

• via acron jobs the ws28xx driver is operational from 00:58 till 23:54
• via cron jobs the kl driver is operational from 23:58 till 00:54
• both drivers need about three minutes before the communication on the station stops (that is: the indication PC [ws28xx] or USB [klimalogg} disappears from the console.) 
• the klimalogg communication should start automatically once a day at 00:00
• the ws28xx communication should start automatically each hour (in our case at 01:00 each day)

The result will be the TFA Opus weather station is operational from 01:00 till 23:54 and the TFA KlimaLogg Pro station is operational from 00:00 till 00:54.

Both drivers will at startup do a catchup of missed data, so the graphs of both stations (generated by the ws28xx driver) will show all data of both stations. 

For the klimalogg the data of the current day won't be available until the next day. As a workaround for this situation I could generate two-day plots for the klimalogg instead of one-day plots.

Todo:

• It would be nice if we could preset the sensors description in weewx.conf. In that case we don't need the KlimaLoggPro windows program anymore to change the sensors description.
• Maybe we could switch the acoustic alarm off from 22:00 till 08:00 in case the driver sets an alarm as a result of a faulty DCF date/time reading at 02:00 or at 03:00 AM.
  I advice not using the DCF time setting option at all because it is not reliable and gives more problems than advantages. So an alarm silence period is not such a hot item anymore when DCF reception is switched off.
• Sort out what happens when the batteries of the station of one of the sensors have low voltages. Which alarmdata we will receive and where? What indications we will see on the station and on the sensor involved? Will the behaviour of the communication change?
  
• Test the driver as a package to be released with a new version of weewx.

Luc

[Luc Heijst]

Status update klimalogg driver for weewx version 0.29p13

The work on the driver itself is finished. We have included the battery low stati and the signal quality to the database.

Also the descriptions of the extra sensors can be preset by the klimalogg driver.

What else can be done?

First of all the (official) release of the driver. We are working on it. More to come the next weeks. A nice klimalogg skin would be welcome too!

Secondly (inapplicable for most users) the cooperation of two stations both using the same Weather Direct Light Wireless transceiver from LaCrosse / TFA.

In fact both stations suffer from the fact the other stations transceiver is catching their mesages, throwing them away and leaving them without the messages they need...

It becomes worse when resent messages again are catched by the other transceiver, which at the end will result in a lost communication.

I have been working at two solutions.

First let both stations work on its own without the other: ws28xx from 00:58-23:55 and klimalogg from 23:58-00:55. Both are talking to the same Weather Direct Light Wireless transceiver! Works fine but has the disadvantage that the klimalogg data will be available once a day.

Secondly let both stations use their own Weather Direct Light Wireless transceiver and let them work together and find a way they don't bother each other too much. Easier said than done! But we don't give hope up yet!

Cheers, Luc

[Marten Schlüter]

Hey Luc,

seems like you're doing really great work here!

Could you please send me the driver and the instructions how to install/use it?

Cheers, 

Marten

[Luc Heijst]

Hey Marten,

Welcome to our group of klimalogg driver testers! I wil mail you the driver with the new revised instructions

Success!

Cheers, 

Luc

[kad....@gmail.com]

Hey Luc,

I have a klimalogg with 7 sensors, it"s possible to test your version with the insturction?

thank you for you reply.

[Luc Heijst]

Status update klimalogg driver for linux version 0.29p15

The installation instructions are reformatted to the 'house' style of weewx and all nessecary files are now combined in one package file.

Also we found a way to let the ws28xx weather station an the KlimaLog Pro station work simultanious. Both stations use the same make USB transceiver and receive (intercept) each others messages. When a message of the other transceiver is received, a random wait is invoked to give the other tranceiver a chance to receive a 'resent' message. With the last modifications both drivers are working together now for more than two days without disturbance.

Luc

[wuerf...@gmail.com]

You have made hefty effort and spent really much time in it - many thanks for that!!!!

I just got my KlimaLog Pro with two sensors and found this thread and I would like to try your driver an my QNAP TS-469. 

Could you please send it to my by mail? Thanks a lot!

WürfelMac

[Luc Heijst]

Status update klimalogg driver for linux version 0.29p18

I forgot to mention that the kl-package also contain two skins:

• a kl skin for klimalogg used with the kl-schema
  
• a klw skin for klimalogg used with the default wview-schema

Starting with version p17 the klimalogg driver recognizes alarm records which also are received in a history message (the alarm record uses the space of a history record). 

When an alarm record is detected a debug message is printed.

Fixed: alarm records are now excluded from the catchup history protocol

We got a breakthrough in ws28xx and klimalogg stations working together. Both drivers read (intercepted) each others messages. 

Just ONE character made the difference: we should send a setRX() instead of setTX() message!

Luc

[Luc Heijst]

Hi yaka and WürfelMac,

You both brought the number of klimalogg users who wanted to test the klimalogg driver with weewx to 30!

(I forgot to count myself and two others who went their own way.)

Welcome you both to our group of klimalogg driver testers!

Cheers, Luc

[Bram Wieringa]

Hi Luc,

I'm also an owner of the Klimalogg Pro station and would like to help in testing the driver. Can you send me instructions? Thanks.

Best regards,

Bram

Op zondag 8 maart 2015 00:12:41 UTC+1 schreef Luc Heijst:

[Mikkel Lund Mortensen]

Hi Luc. It seems like a really interesting project that have been started. 

Are the drivers available in Weewx already, or are they still in betatesting. If so then I would very much like to join your little test program.

Regards.

Mikkel 

[Luc Heijst]

Hi Mikkel,

The kl driver is not yet available in weewx. The recent version 1.0 was released three weeks ago. I will send you the the driver package by mail.

Luc

[mar...@will-online.me]

Hi Luc,

I too would like to connect my Klimalogg Pro to weewx. I am using Klimalogg with 4 external sensors. Would be happy if I could test your driver.

Regards,

Marcel

[Oleg]

Hi Luc,

seems like you're doing really great work here!

Could you please send me the driver and the instructions how to install/use it?

Oleg

[Daniel Reimann]

Hi Luc,

I've a Klimalogg Pro with 4 external sensors and would like to connect them on a BeagleBone Black board. It's for a project on my current embedded linux CAS course and it seems like you did already the main work for that!
Could you please send me the driver package with installation instructions in order I could test it on my BeagleBone?

Regards,
Daniel

[Luc Heijst]

Hi Oleg and Daniel,

I will send you driver and instructions by mail.

Luc

[Wolfgang Klanner]

Hi Luc,

great work - i would like to connect my Klimalogg Pro to weewx. I am using Klimalogg with 5 external sensors. Would be happy if I could test your driver.

Regards,

Wolfgang from austria

[Peter Illés]

Hello together,
I'm also interested in connecting my KlimaLog pro (4 sensors) with linux through weewx.
Pairing seems working, but I cannot receive any data (even with presing USB key to start transmitting)


[root@*********]# wee_config_device --check-transceiver
Using configuration file /etc/weewx/weewx.conf
Using WS28xx driver version 0.33 (weewx.drivers.ws28xx)
Checking for transceiver...
Transceiver is present
serial: 01011006140164
id: 320 (0x0140)


Dňa štvrtok, 14. mája 2015 7:03:02 UTC+2 Wolfgang Klanner napísal(-a):

[Luc Heijst]

Hello Peter,
The ws28xx driver doesn't work with the KlimaLogg Pro. I will send you the klimalogg driver by mail.
Luc

[Martin]

Hello Luc,

I have bought a CUL868 to connect my TFA sensors with the raspberry pi. But now I found out that the CUL868 doesn't support all 868MHz sensors.
So I locked for another solution to get the TFA sensor messages on my raspberry pi.
Now I'm reading here that you can read out the KLIMALOGG pro data on the raspberry pi.
I have connected 5 sensors on my Klimalogg Pro.
Can you please send me your driver to read out data from Klimalogg Pro, thank you.

Best regards,
Martin

[baltas...@aiesec.net]

Hi Luc, could you also share the driver with me - I also have the KlimaLogg Pro in my weekend hut and would love to give it a try! Cheers, Baltasar

[st...@gmx.de]

Hi, 

could someone share me the code with the installation instructions as well? 

Have a station with 4 sensors. 

Best regards

Thomas 

[Luc Heijst]

Hi Baltasar and Thomas,

I sent you the driver with instructions by mail. Succes!

Luc

[st...@gmx.de]

Thank, getting data out ouf the station worked now. 

Only my PC loses sometimes the connection to the USB-Dongle and the report does not look too good, is there any improvement planned? 

Thomas