Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[Luc Heijst]

Herman,
For tfrec working in Buster, see my 
post https://groups.google.com/g/weewx-user/c/b-GiJ1qkdF8
Luc

Op dinsdag 17 november 2020 om 09:51:02 UTC-3 schreef cool...@gmail.com:

> Working again...:)) A lot of changes to the config file...  Good lesson to 
> backup a working weewx.conf..
> But still interested in tfrec working in Buster..
> regards
> Herman
>
> Op dinsdag 17 november 2020 om 12:50:59 UTC+1 schreef cool...@gmail.com:
>
>> a dump from the tail of syslog:
>>
>> Nov 17 12:45:14 central weewx[20281] INFO __main__: Starting up weewx 
>> version 4.2.0
>>
>> Nov 17 12:45:14 central weewx[20281] INFO weewx.engine: Main loop 
>> exiting. Shutting engine down.
>>
>> Nov 17 12:46:14 central weewx[20281] ERROR user.kl: unable to terminate 
>> RF thread after 60 seconds
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: Caught 
>> unrecoverable exception:
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   Unknown 
>> data binding 'u'kl_binding''
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> Traceback (most recent call last):
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewxd", line 154, in main
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> engine.run()
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 173, in run
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> self.dispatchEvent(weewx.Event(weewx.STARTUP))
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 241, in dispatchEvent
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> callback(event)
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 562, in startup
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> dbmanager = self.engine.db_binder.get_manager(self.data_binding, 
>> initialize=True)
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/manager.py", line 529, in get_manager
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> default_binding_dict=defaults)
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/manager.py", line 634, in 
>> get_manager_dict_from_config
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> raise weewx.UnknownBinding("Unknown data binding '%s'" % e)
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> UnknownBinding: Unknown data binding 'u'kl_binding''
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   Exiting.
>>
>>
>> Op dinsdag 17 november 2020 om 12:40:26 UTC+1 schreef cool...@gmail.com:
>>
>>> Hello Luc,
>>>
>>> Since the last update of weewx (I stupidly accepted the change in the 
>>> config file) my klimmalogg setup is broken. I tried to copy back some info 
>>> I had from previous whew.conf backups but it seems that some things are 
>>> changed within weewx itself. I can't get it to work anymore. e.g. kl.py is 
>>> not in the drivers directory. 
>>> other example is the change from  weewx.manager.WXDaySummaryManager into 
>>> weewx.manager.DaySummaryManager in the conf file. 
>>> I tried reinstalling the plugin from scratch but that didn't help 
>>> either. Any idea about this update and the impact on KL?
>>>
>>> And for sure I would like to do the same as Walter Speth and just push 
>>> the data on an MQTT topic to flow into an influxdb. So yes, a bit curious 
>>> how you got tired working. I didn't manage to go that way.
>>>
>>> Regards
>>> Herman
>>>
>>> Op maandag 24 augustus 2020 om 13:23:57 UTC+2 schreef Luc Heijst:
>>>
 Hi Walter,

 I don't know if your approach is working. The software in the KlimaLogg 
 PRO station is very time critical.
 Perhaps you try the driver first within weewx and when it is working 
 you can go from there.

 The KlimaLogg PRO base station needs to be synchronized once with the 
 driver.
 To do this:
 Press and hold the USB button for three seconds until a beep is heard, 
 then start weewx with the kl-driver (within 5 seconds). A second beep is 
 heard when the synchronization was succesfull.

 From now on a short press on the USB button is needed whenever the 
 driver lost communication with the base station. The driver is telling you 
 to do so.

 There is another (much easier) way to read the values of the KlimaLogg 
 sensors with a SDR-dongle (the base station is not needed anymore), see: 
 https://github.com/baycom/tfrec 
 The instructions on this site to compile the tfrc program don't work 
 anymore for Raspbian Buster. 

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[gjr80]

Hi,

How did you upgrade WeeWX? If you upgraded using setup.py or one of the 
packages the installer should have saved a copy of your original weewx.conf 
(or the new version weewx.conf if you upgraded using the deb package and 
chose to keep your modified weewx.conf). This allows you to compare old and 
new weewx.conf post upgrade. Have a read through the setup.py 
, deb package 
 or rpm 
package  
upgrade instructions; they explain where the copy of the old weewx.conf is 
saved for each upgrade type.

Gary
On Tuesday, 17 November 2020 at 22:51:02 UTC+10 cool...@gmail.com wrote:

> Working again...:)) A lot of changes to the config file...  Good lesson to 
> backup a working weewx.conf..
> But still interested in tfrec working in Buster..
> regards
> Herman
>
> Op dinsdag 17 november 2020 om 12:50:59 UTC+1 schreef cool...@gmail.com:
>
>> a dump from the tail of syslog:
>>
>> Nov 17 12:45:14 central weewx[20281] INFO __main__: Starting up weewx 
>> version 4.2.0
>>
>> Nov 17 12:45:14 central weewx[20281] INFO weewx.engine: Main loop 
>> exiting. Shutting engine down.
>>
>> Nov 17 12:46:14 central weewx[20281] ERROR user.kl: unable to terminate 
>> RF thread after 60 seconds
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: Caught 
>> unrecoverable exception:
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   Unknown 
>> data binding 'u'kl_binding''
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> Traceback (most recent call last):
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewxd", line 154, in main
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> engine.run()
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 173, in run
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> self.dispatchEvent(weewx.Event(weewx.STARTUP))
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 241, in dispatchEvent
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> callback(event)
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 562, in startup
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> dbmanager = self.engine.db_binder.get_manager(self.data_binding, 
>> initialize=True)
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/manager.py", line 529, in get_manager
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> default_binding_dict=defaults)
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/manager.py", line 634, in 
>> get_manager_dict_from_config
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> raise weewx.UnknownBinding("Unknown data binding '%s'" % e)
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> UnknownBinding: Unknown data binding 'u'kl_binding''
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   Exiting.
>>
>>
>> Op dinsdag 17 november 2020 om 12:40:26 UTC+1 schreef cool...@gmail.com:
>>
>>> Hello Luc,
>>>
>>> Since the last update of weewx (I stupidly accepted the change in the 
>>> config file) my klimmalogg setup is broken. I tried to copy back some info 
>>> I had from previous whew.conf backups but it seems that some things are 
>>> changed within weewx itself. I can't get it to work anymore. e.g. kl.py is 
>>> not in the drivers directory. 
>>> other example is the change from  weewx.manager.WXDaySummaryManager into 
>>> weewx.manager.DaySummaryManager in the conf file. 
>>> I tried reinstalling the plugin from scratch but that didn't help 
>>> either. Any idea about this update and the impact on KL?
>>>
>>> And for sure I would like to do the same as Walter Speth and just push 
>>> the data on an MQTT topic to flow into an influxdb. So yes, a bit curious 
>>> how you got tired working. I didn't manage to go that way.
>>>
>>> Regards
>>> Herman
>>>
>>> Op maandag 24 augustus 2020 om 13:23:57 UTC+2 schreef Luc Heijst:
>>>
 Hi Walter,

 I don't know if your approach is working. The software in the KlimaLogg 
 PRO station is very time critical.
 Perhaps you try the driver first within weewx and when it is working 
 you can go from there.

 The KlimaLogg PRO base station needs to be synchronized once with the 
 driver.
 To do this:
 Press and hold the USB button for three seconds until a beep is heard, 
 then start

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[cool...@gmail.com]

Working again...:)) A lot of changes to the config file...  Good lesson to 
backup a working weewx.conf..
But still interested in tfrec working in Buster..
regards
Herman

Op dinsdag 17 november 2020 om 12:50:59 UTC+1 schreef cool...@gmail.com:

> a dump from the tail of syslog:
>
> Nov 17 12:45:14 central weewx[20281] INFO __main__: Starting up weewx 
> version 4.2.0
>
> Nov 17 12:45:14 central weewx[20281] INFO weewx.engine: Main loop exiting. 
> Shutting engine down.
>
> Nov 17 12:46:14 central weewx[20281] ERROR user.kl: unable to terminate RF 
> thread after 60 seconds
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: Caught 
> unrecoverable exception:
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   Unknown 
> data binding 'u'kl_binding''
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
> Traceback (most recent call last):
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
> "/usr/share/weewx/weewxd", line 154, in main
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
> engine.run()
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 173, in run
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
> self.dispatchEvent(weewx.Event(weewx.STARTUP))
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 241, in dispatchEvent
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
> callback(event)
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 562, in startup
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
> dbmanager = self.engine.db_binder.get_manager(self.data_binding, 
> initialize=True)
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/manager.py", line 529, in get_manager
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
> default_binding_dict=defaults)
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/manager.py", line 634, in 
> get_manager_dict_from_config
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
> raise weewx.UnknownBinding("Unknown data binding '%s'" % e)
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
> UnknownBinding: Unknown data binding 'u'kl_binding''
>
> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   Exiting.
>
>
> Op dinsdag 17 november 2020 om 12:40:26 UTC+1 schreef cool...@gmail.com:
>
>> Hello Luc,
>>
>> Since the last update of weewx (I stupidly accepted the change in the 
>> config file) my klimmalogg setup is broken. I tried to copy back some info 
>> I had from previous whew.conf backups but it seems that some things are 
>> changed within weewx itself. I can't get it to work anymore. e.g. kl.py is 
>> not in the drivers directory. 
>> other example is the change from  weewx.manager.WXDaySummaryManager into 
>> weewx.manager.DaySummaryManager in the conf file. 
>> I tried reinstalling the plugin from scratch but that didn't help either. 
>> Any idea about this update and the impact on KL?
>>
>> And for sure I would like to do the same as Walter Speth and just push 
>> the data on an MQTT topic to flow into an influxdb. So yes, a bit curious 
>> how you got tired working. I didn't manage to go that way.
>>
>> Regards
>> Herman
>>
>> Op maandag 24 augustus 2020 om 13:23:57 UTC+2 schreef Luc Heijst:
>>
>>> Hi Walter,
>>>
>>> I don't know if your approach is working. The software in the KlimaLogg 
>>> PRO station is very time critical.
>>> Perhaps you try the driver first within weewx and when it is working you 
>>> can go from there.
>>>
>>> The KlimaLogg PRO base station needs to be synchronized once with the 
>>> driver.
>>> To do this:
>>> Press and hold the USB button for three seconds until a beep is heard, 
>>> then start weewx with the kl-driver (within 5 seconds). A second beep is 
>>> heard when the synchronization was succesfull.
>>>
>>> From now on a short press on the USB button is needed whenever the 
>>> driver lost communication with the base station. The driver is telling you 
>>> to do so.
>>>
>>> There is another (much easier) way to read the values of the KlimaLogg 
>>> sensors with a SDR-dongle (the base station is not needed anymore), see: 
>>> https://github.com/baycom/tfrec 
>>> The instructions on this site to compile the tfrc program don't work 
>>> anymore for Raspbian Buster. When you are interested I can send you my 
>>> notes how I managed to get it work under Buster.
>>>
>>> Success,
>>> Luc
>>>
>>>
>>> Luc,
>>> I appreciate so much the profound work you have been doing over the last 
>>> 5 years.
>>> Could you please advise for my project? I am not using weewx, did not 
>>

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[cool...@gmail.com]

a dump from the tail of syslog:

Nov 17 12:45:14 central weewx[20281] INFO __main__: Starting up weewx 
version 4.2.0

Nov 17 12:45:14 central weewx[20281] INFO weewx.engine: Main loop exiting. 
Shutting engine down.

Nov 17 12:46:14 central weewx[20281] ERROR user.kl: unable to terminate RF 
thread after 60 seconds

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: Caught 
unrecoverable exception:

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   Unknown 
data binding 'u'kl_binding''

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   Traceback 
(most recent call last):

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
"/usr/share/weewx/weewxd", line 154, in main

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
engine.run()

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 173, in run

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
self.dispatchEvent(weewx.Event(weewx.STARTUP))

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 241, in dispatchEvent

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
callback(event)

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 562, in startup

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
dbmanager = self.engine.db_binder.get_manager(self.data_binding, 
initialize=True)

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 529, in get_manager

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
default_binding_dict=defaults)

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 634, in 
get_manager_dict_from_config

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   raise 
weewx.UnknownBinding("Unknown data binding '%s'" % e)

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
UnknownBinding: Unknown data binding 'u'kl_binding''

Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   Exiting.


Op dinsdag 17 november 2020 om 12:40:26 UTC+1 schreef cool...@gmail.com:

> Hello Luc,
>
> Since the last update of weewx (I stupidly accepted the change in the 
> config file) my klimmalogg setup is broken. I tried to copy back some info 
> I had from previous whew.conf backups but it seems that some things are 
> changed within weewx itself. I can't get it to work anymore. e.g. kl.py is 
> not in the drivers directory. 
> other example is the change from  weewx.manager.WXDaySummaryManager into 
> weewx.manager.DaySummaryManager in the conf file. 
> I tried reinstalling the plugin from scratch but that didn't help either. 
> Any idea about this update and the impact on KL?
>
> And for sure I would like to do the same as Walter Speth and just push the 
> data on an MQTT topic to flow into an influxdb. So yes, a bit curious how 
> you got tired working. I didn't manage to go that way.
>
> Regards
> Herman
>
> Op maandag 24 augustus 2020 om 13:23:57 UTC+2 schreef Luc Heijst:
>
>> Hi Walter,
>>
>> I don't know if your approach is working. The software in the KlimaLogg 
>> PRO station is very time critical.
>> Perhaps you try the driver first within weewx and when it is working you 
>> can go from there.
>>
>> The KlimaLogg PRO base station needs to be synchronized once with the 
>> driver.
>> To do this:
>> Press and hold the USB button for three seconds until a beep is heard, 
>> then start weewx with the kl-driver (within 5 seconds). A second beep is 
>> heard when the synchronization was succesfull.
>>
>> From now on a short press on the USB button is needed whenever the driver 
>> lost communication with the base station. The driver is telling you to do 
>> so.
>>
>> There is another (much easier) way to read the values of the KlimaLogg 
>> sensors with a SDR-dongle (the base station is not needed anymore), see: 
>> https://github.com/baycom/tfrec 
>> The instructions on this site to compile the tfrc program don't work 
>> anymore for Raspbian Buster. When you are interested I can send you my 
>> notes how I managed to get it work under Buster.
>>
>> Success,
>> Luc
>>
>>
>> Luc,
>> I appreciate so much the profound work you have been doing over the last 
>> 5 years.
>> Could you please advise for my project? I am not using weewx, did not 
>> even install it. Yet I want to retrieve data from KlimaLogg-pro.
>>
>> starting from: https://github.com/matthewwall/weewx-klimalogg
>>
>> My approach: call routines in your kl.py from another python program like
>> from kl import *
>> maxtries = 3
>> klimalogg = KlimaLoggConfigurator()
>> klimalogg.station = KlimaLoggDriver()
>> klimalogg.check_transceiver(maxtries)
>> klimalogg.p

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[cool...@gmail.com]

Hello Luc,

Since the last update of weewx (I stupidly accepted the change in the 
config file) my klimmalogg setup is broken. I tried to copy back some info 
I had from previous whew.conf backups but it seems that some things are 
changed within weewx itself. I can't get it to work anymore. e.g. kl.py is 
not in the drivers directory. 
other example is the change from  weewx.manager.WXDaySummaryManager into 
weewx.manager.DaySummaryManager in the conf file. 
I tried reinstalling the plugin from scratch but that didn't help either. 
Any idea about this update and the impact on KL?

And for sure I would like to do the same as Walter Speth and just push the 
data on an MQTT topic to flow into an influxdb. So yes, a bit curious how 
you got tired working. I didn't manage to go that way.

Regards
Herman

Op maandag 24 augustus 2020 om 13:23:57 UTC+2 schreef Luc Heijst:

> Hi Walter,
>
> I don't know if your approach is working. The software in the KlimaLogg 
> PRO station is very time critical.
> Perhaps you try the driver first within weewx and when it is working you 
> can go from there.
>
> The KlimaLogg PRO base station needs to be synchronized once with the 
> driver.
> To do this:
> Press and hold the USB button for three seconds until a beep is heard, 
> then start weewx with the kl-driver (within 5 seconds). A second beep is 
> heard when the synchronization was succesfull.
>
> From now on a short press on the USB button is needed whenever the driver 
> lost communication with the base station. The driver is telling you to do 
> so.
>
> There is another (much easier) way to read the values of the KlimaLogg 
> sensors with a SDR-dongle (the base station is not needed anymore), see: 
> https://github.com/baycom/tfrec 
> The instructions on this site to compile the tfrc program don't work 
> anymore for Raspbian Buster. When you are interested I can send you my 
> notes how I managed to get it work under Buster.
>
> Success,
> Luc
>
>
> Luc,
> I appreciate so much the profound work you have been doing over the last 5 
> years.
> Could you please advise for my project? I am not using weewx, did not even 
> install it. Yet I want to retrieve data from KlimaLogg-pro.
>
> starting from: https://github.com/matthewwall/weewx-klimalogg
>
> My approach: call routines in your kl.py from another python program like
> from kl import *
> maxtries = 3
> klimalogg = KlimaLoggConfigurator()
> klimalogg.station = KlimaLoggDriver()
> klimalogg.check_transceiver(maxtries)
> klimalogg.pair(maxtries)
> in your code KlimaLoggConfigurator and KlimaLoggDriver are subclassed from 
> weewx classes. I removed the superclass from their definitions.
> first "results":
> Checking for transceiver...
> Transceiver is present
> serial: 01012110140255
> id: 567 (0x0237)
> Pairing transceiver with console...
> Press and hold the USB button until "USB" appears (attempt 1 of 3)
> Press and hold the USB button until "USB" appears (attempt 2 of 3)
> Press and hold the USB button until "USB" appears (attempt 3 of 3)
> Transceiver not paired to console.
>
> Would you agree, this makes sense? Anything to change up to here?
> USB pairing did not work so far (pressing the button --> "USB" blinking in 
> display, nothing else happening.
>
>
> best regards
> Walter
>
>
> Luc Heijst schrieb am Montag, 25. Mai 2020 um 17:21:24 UTC+2:
>
> Hi Pete,
>
> Attached the Klimalogg Pro driver compatible with python2, python3 and the 
> weewx v.4.0 logging.
>
> Luc
>
> On Monday, 25 May 2020 03:23:25 UTC-3, pete_panic wrote:
>
> Hi everyone!
>
> This thread has been extremely helpful. Thank you so much for all the 
> input. Nevertheless unfortunatly I wasn't able yet to successfully get the 
> rf communication between the raspi and the Klimalogg Pro started.
>
> I was able to connect to the transceiver and everything went well until 
> the log showed the error message "exception in doRF: %s" after "starting rf 
> communication". Since I am not firm (yet) with python (I'm more one of the 
> old php guys), I wonder if there was the possibility to have a python3 
> compatible version of the Klimalogg Pro driver? I did get the message to 
> press the USB button on the console but that did not help, it kept on 
> showing up...
>
> Did anyone else have this problem?
>
> Thank you again and cheers
>
> Pete
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/6e4b04f7-1938-4157-8fc3-83c9e4e0191bn%40googlegroups.com
>  
> 

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[Walter Speth]

Luc,

you were right in many respects.
I had some success, yet not with tfrec. It always renders "BAD" instead of
temperature or humidity. I changed trigger value and gain a lot but found
no set of parameters that worked. I ordered another but different SDR stick
and we'll see whether hardware was the root cause.

Following your other advice I indeed installed weewx with your klimalogg
driver and it worked as designed. Then I added to your routine
genLoopPackets   the code to put the data into mosquitto:

def pub(packet):

tags = {"temp":"temperature", "humidity":"humidity",
"batteryStatus":"battery"}
for tag in tags:
for i in range(10):
key = "%s%d" % (tag, i)
if key in packet and not (packet[key] is None):
topic = "klimalogg/%d/%s" % (i, tags[tag])
payload = packet[key]
publish.single(topic, payload, hostname="localhost")
null = None


this was easily catched by openhabian (standard mqtt binding). Yet only
works for the current value. I am struggling a bit with storage and
presentation (grafana). All was new to me: openhab, weewx, grafana, SDR.

I also need to put your kl.py into debug mode one day to understand the
sequence in which weewx invokes the routines.

For the time being I just wanted to let you know.

regards,

Walter




Am Mo., 24. Aug. 2020 um 13:23 Uhr schrieb L.J.M. Heijst <
ljm.hei...@gmail.com>:

> Hi Walter,
>
> I don't know if your approach is working. The software in the KlimaLogg
> PRO station is very time critical.
> Perhaps you try the driver first within weewx and when it is working you
> can go from there.
>
> The KlimaLogg PRO base station needs to be synchronized once with the
> driver.
> To do this:
> Press and hold the USB button for three seconds until a beep is heard,
> then start weewx with the kl-driver (within 5 seconds). A second beep is
> heard when the synchronization was succesfull.
>
> From now on a short press on the USB button is needed whenever the driver
> lost communication with the base station. The driver is telling you to do
> so.
>
> There is another (much easier) way to read the values of the KlimaLogg
> sensors with a SDR-dongle (the base station is not needed anymore), see:
> https://github.com/baycom/tfrec
> The instructions on this site to compile the tfrc program don't work
> anymore for Raspbian Buster. When you are interested I can send you my
> notes how I managed to get it work under Buster.
>
> Success,
> Luc
>
>
> Luc,
> I appreciate so much the profound work you have been doing over the last 5
> years.
> Could you please advise for my project? I am not using weewx, did not even
> install it. Yet I want to retrieve data from KlimaLogg-pro.
>
> starting from: https://github.com/matthewwall/weewx-klimalogg
>
> My approach: call routines in your kl.py from another python program like
> from kl import *
> maxtries = 3
> klimalogg = KlimaLoggConfigurator()
> klimalogg.station = KlimaLoggDriver()
> klimalogg.check_transceiver(maxtries)
> klimalogg.pair(maxtries)
> in your code KlimaLoggConfigurator and KlimaLoggDriver are subclassed from
> weewx classes. I removed the superclass from their definitions.
> first "results":
> Checking for transceiver...
> Transceiver is present
> serial: 01012110140255
> id: 567 (0x0237)
> Pairing transceiver with console...
> Press and hold the USB button until "USB" appears (attempt 1 of 3)
> Press and hold the USB button until "USB" appears (attempt 2 of 3)
> Press and hold the USB button until "USB" appears (attempt 3 of 3)
> Transceiver not paired to console.
>
> Would you agree, this makes sense? Anything to change up to here?
> USB pairing did not work so far (pressing the button --> "USB" blinking in
> display, nothing else happening.
>
>
> best regards
> Walter
>
>
> Luc Heijst schrieb am Montag, 25. Mai 2020 um 17:21:24 UTC+2:
>
> Hi Pete,
>
> Attached the Klimalogg Pro driver compatible with python2, python3 and the
> weewx v.4.0 logging.
>
> Luc
>
> On Monday, 25 May 2020 03:23:25 UTC-3, pete_panic wrote:
>
> Hi everyone!
>
> This thread has been extremely helpful. Thank you so much for all the
> input. Nevertheless unfortunatly I wasn't able yet to successfully get the
> rf communication between the raspi and the Klimalogg Pro started.
>
> I was able to connect to the transceiver and everything went well until
> the log showed the error message "exception in doRF: %s" after "starting rf
> communication". Since I am not firm (yet) with python (I'm more one of the
> old php guys), I wonder if there was the possibility to have a python3
> compatible version of the Klimalogg Pro driver? I did get the message to
> press the USB button on the console but that did not help, it kept on
> showing up...
>
> Did anyone else have this problem?
>
> Thank you again and cheers
>
> Pete
> --
> You received this message because you are subscribed to a topic in the
> Google Group

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[L.J.M. Heijst]

Title: Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi


Hi Walter,

I don't know if your approach is working. The software in the KlimaLogg PRO station is very time critical.
Perhaps you try the driver first within weewx and when it is working you can go from there.

The KlimaLogg PRO base station needs to be synchronized once with the driver.
To do this:
Press and hold the USB button for three seconds until a beep is heard, then start weewx with the kl-driver (within 5 seconds). A second beep is heard when the synchronization was succesfull.

>From now on a short press on the USB button is needed whenever the driver lost communication with the base station. The driver is telling you to do so.

There is another (much easier) way to read the values of the KlimaLogg sensors with a SDR-dongle (the base station is not needed anymore), see: https://github.com/baycom/tfrec 
The instructions on this site to compile the tfrc program don't work anymore for Raspbian Buster. When you are interested I can send you my notes how I managed to get it work under Buster.

Success,
Luc





Luc,
I appreciate so much the profound work you have been doing over the last 5 years.
Could you please advise for my project? I am not using weewx, did not even install it. Yet I want to retrieve data from KlimaLogg-pro.

starting from: https://github.com/matthewwall/weewx-klimalogg

My approach: call routines in your kl.py from another python program like
    from kl import *
    maxtries = 3
    klimalogg = KlimaLoggConfigurator()
    klimalogg.station = KlimaLoggDriver()
    klimalogg.check_transceiver(maxtries)
    klimalogg.pair(maxtries)
in your code KlimaLoggConfigurator and KlimaLoggDriver are subclassed from weewx classes. I removed the superclass from their definitions.
first "results":
    Checking for transceiver...
    Transceiver is present
    serial: 01012110140255
    id: 567 (0x0237)
    Pairing transceiver with console...
    Press and hold the USB button until "USB" appears (attempt 1 of 3)
    Press and hold the USB button until "USB" appears (attempt 2 of 3)
    Press and hold the USB button until "USB" appears (attempt 3 of 3)
    Transceiver not paired to console.

Would you agree, this makes sense? Anything to change up to here?
USB pairing did not work so far (pressing the button --> "USB" blinking in display, nothing else happening.


best regards
Walter


Luc Heijst schrieb am Montag, 25. Mai 2020 um 17:21:24 UTC+2:




Hi Pete,

Attached the Klimalogg Pro driver compatible with python2, python3 and the weewx v.4.0 logging.

Luc

On Monday, 25 May 2020 03:23:25 UTC-3, pete_panic wrote:




Hi everyone!

This thread has been extremely helpful. Thank you so much for all the input. Nevertheless unfortunatly I wasn't able yet to successfully get the rf communication between the raspi and the Klimalogg Pro started.

I was able to connect to the transceiver and everything went well until the log showed the error message "exception in doRF: %s" after "starting rf communication". Since I am not firm (yet) with python (I'm more one of the old php guys), I wonder if there was the possibility to have a python3 compatible version of the Klimalogg Pro driver? I did get the message to press the USB button on the console but that did not help, it kept on showing up...

Did anyone else have this problem?

Thank you again and cheers

Pete






--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/6e4b04f7-1938-4157-8fc3-83c9e4e0191bn%40googlegroups.com.




	

		Virus-free. www.avast.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/812515819.20200824082349%40gmail.com.

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[Walter Speth]

Luc,
I appreciate so much the profound work you have been doing over the last 5 
years.
Could you please advise for my project? I am not using weewx, did not even 
install it. Yet I want to retrieve data from KlimaLogg-pro.

starting from: https://github.com/matthewwall/weewx-klimalogg

My approach: call routines in your kl.py from another python program like
from kl import *
maxtries = 3
klimalogg = KlimaLoggConfigurator()
klimalogg.station = KlimaLoggDriver()
klimalogg.check_transceiver(maxtries)
klimalogg.pair(maxtries)

in your code KlimaLoggConfigurator and KlimaLoggDriver are subclassed from 
weewx classes. I removed the superclass from their definitions.
first "results":
Checking for transceiver...
Transceiver is present
serial: 01012110140255
id: 567 (0x0237)
Pairing transceiver with console...
Press and hold the USB button until "USB" appears (attempt 1 of 3)
Press and hold the USB button until "USB" appears (attempt 2 of 3)
Press and hold the USB button until "USB" appears (attempt 3 of 3)
Transceiver not paired to console.

Would you agree, this makes sense? Anything to change up to here?
USB pairing did not work so far (pressing the button --> "USB" blinking in 
display, nothing else happening.


best regards
Walter


Luc Heijst schrieb am Montag, 25. Mai 2020 um 17:21:24 UTC+2:

> Hi Pete,
>
> Attached the Klimalogg Pro driver compatible with python2, python3 and the 
> weewx v.4.0 logging.
>
> Luc
>
> On Monday, 25 May 2020 03:23:25 UTC-3, pete_panic wrote:
>>
>> Hi everyone!
>>
>> This thread has been extremely helpful. Thank you so much for all the 
>> input. Nevertheless unfortunatly I wasn't able yet to successfully get the 
>> rf communication between the raspi and the Klimalogg Pro started. 
>>
>> I was able to connect to the transceiver and everything went well until 
>> the log showed the error message "exception in doRF: %s" after "starting rf 
>> communication". Since I am not firm (yet) with python (I'm more one of the 
>> old php guys), I wonder if there was the possibility to have a python3 
>> compatible version of the Klimalogg Pro driver? I did get the message to 
>> press the USB button on the console but that did not help, it kept on 
>> showing up...
>>
>> Did anyone else have this problem?
>>
>> Thank you again and cheers
>>
>> Pete
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6e4b04f7-1938-4157-8fc3-83c9e4e0191bn%40googlegroups.com.

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[pete_panic]

Hey Luc,

this is fantastic! Thank you so much. Copied it to the weewx installation, 
fine tuned a bit et voilá. Working smoothly!

The original problem was that I installed ubuntu 20.4 on a raspi 2 and that 
package only includes python 3. Installing pyhton 2 and switching between 
versions I ran into some more trouble regarding dependencies.

Thank you really very much, Luc, you made my day. Very much so!

Greatest help!

Cheers Peter


Am Montag, 25. Mai 2020 17:21:24 UTC+2 schrieb Luc Heijst:
>
> Hi Pete,
>
> Attached the Klimalogg Pro driver compatible with python2, python3 and the 
> weewx v.4.0 logging.
>
> Luc
>
> On Monday, 25 May 2020 03:23:25 UTC-3, pete_panic wrote:
>>
>> Hi everyone!
>>
>> This thread has been extremely helpful. Thank you so much for all the 
>> input. Nevertheless unfortunatly I wasn't able yet to successfully get the 
>> rf communication between the raspi and the Klimalogg Pro started. 
>>
>> I was able to connect to the transceiver and everything went well until 
>> the log showed the error message "exception in doRF: %s" after "starting rf 
>> communication". Since I am not firm (yet) with python (I'm more one of the 
>> old php guys), I wonder if there was the possibility to have a python3 
>> compatible version of the Klimalogg Pro driver? I did get the message to 
>> press the USB button on the console but that did not help, it kept on 
>> showing up...
>>
>> Did anyone else have this problem?
>>
>> Thank you again and cheers
>>
>> Pete
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/98da1c4b-0f4a-4616-bee0-668f139f6695%40googlegroups.com.

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[pete_panic]

Hi everyone!

This thread has been extremely helpful. Thank you so much for all the 
input. Nevertheless unfortunatly I wasn't able yet to successfully get the 
rf communication between the raspi and the Klimalogg Pro started. 

I was able to connect to the transceiver and everything went well until the 
log showed the error message "exception in doRF: %s" after "starting rf 
communication". Since I am not firm (yet) with python (I'm more one of the 
old php guys), I wonder if there was the possibility to have a python3 
compatible version of the Klimalogg Pro driver? I did get the message to 
press the USB button on the console but that did not help, it kept on 
showing up...

Did anyone else have this problem?

Thank you again and cheers

Pete

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/41a0b461-d3ca-4861-aac5-36a9b5e41fec%40googlegroups.com.

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[Jindřich Štěpán]

Oh. sorry, now I see I forgot install Cheetah ! :)

2018-01-17 17:00 GMT+01:00 Jindřich Štěpán :

> Hi guys, thanks to your advice, especially this link
> https://github.com/weewx/weewx/wiki/weewx-on-openwrt I was able ( on
> third attempt after lack of space and then lack of memory on my router, so
> i installed extroot and swap on usb flash stick ) to install weewx and it
> reads data from TFA logger! :)
>
> Now I would like to make some simple XML page with updated data so I can
> read it from my home PLC machine. But after installation (I installed
> following the http://www.weewx.com/docs/setup.htm page using setup.py,
> the whole weewx data seems to be in folder /home/weewx/, driver for
> Klimalogg is then in /home/weewx/bin/user/ ), there is no folder
> /home/weewx/public_html/ .
> Also, I found this in syslog...
>
> Wed Jan 17 15:55:21 2018 user.notice weewx[1432]: manager: Added record
> 2018-01-17 15:55:00 ??? (1516204500) to database 'weewx-kl.sdb'
> Wed Jan 17 15:55:21 2018 user.notice weewx[1432]: manager: Added record
> 2018-01-17 15:55:00 ??? (1516204500) to daily summary in 'weewx-kl.sdb'
> Wed Jan 17 15:55:24 2018 user.crit weewx[1432]: reportengine: Unable to
> instantiate generator weewx.cheetahgenerator.CheetahGenerator
> Wed Jan 17 15:55:24 2018 user.crit weewx[1432]:   No module
> named Cheetah.Template
> Wed Jan 17 15:55:24 2018 user.info weewx[1432]:   Traceback
> (most recent call last):
> Wed Jan 17 15:55:24 2018 user.info weewx[1432]: File
> "/home/weewx/bin/weewx/reportengine.py", line 220, in run
> Wed Jan 17 15:55:24 2018 user.info weewx[1432]:   obj =
> weeutil.weeutil._get_object(generator)(
> Wed Jan 17 15:55:24 2018 user.info weewx[1432]: File
> "/home/weewx/bin/weeutil/weeutil.py", line 1132, in _get_object
> Wed Jan 17 15:55:24 2018 user.info weewx[1432]:   mod =
> __import__(module)
> Wed Jan 17 15:55:24 2018 user.info weewx[1432]: File
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 65, in 
> Wed Jan 17 15:55:24 2018 user.info weewx[1432]:   import
> Cheetah.Template
> Wed Jan 17 15:55:24 2018 user.info weewx[1432]: 
> ImportError: No module named Cheetah.Template
> Wed Jan 17 15:55:24 2018 user.crit weewx[1432]:   Generator
> ignored
> Wed Jan 17 15:55:25 2018 user.crit weewx[1432]: reportengine: Unable to
> instantiate generator weewx.imagegenerator.ImageGenerator
> Wed Jan 17 15:55:25 2018 user.crit weewx[1432]:   No module
> named Image
> Wed Jan 17 15:55:25 2018 user.info weewx[1432]:   Traceback
> (most recent call last):
> Wed Jan 17 15:55:25 2018 user.info weewx[1432]: File
> "/home/weewx/bin/weewx/reportengine.py", line 220, in run
> Wed Jan 17 15:55:25 2018 user.info weewx[1432]:   obj =
> weeutil.weeutil._get_object(generator)(
> Wed Jan 17 15:55:25 2018 user.info weewx[1432]: File
> "/home/weewx/bin/weeutil/weeutil.py", line 1132, in _get_object
> Wed Jan 17 15:55:25 2018 user.info weewx[1432]:   mod =
> __import__(module)
> Wed Jan 17 15:55:25 2018 user.info weewx[1432]: File
> "/home/weewx/bin/weewx/imagegenerator.py", line 15, in 
> Wed Jan 17 15:55:25 2018 user.info weewx[1432]:   import
> weeplot.genplot
> Wed Jan 17 15:55:25 2018 user.info weewx[1432]: File
> "/home/weewx/bin/weeplot/genplot.py", line 14, in 
> Wed Jan 17 15:55:25 2018 user.info weewx[1432]:   import
> Image, ImageDraw
> Wed Jan 17 15:55:25 2018 user.info weewx[1432]: 
> ImportError: No module named Image
> Wed Jan 17 15:55:25 2018 user.crit weewx[1432]:   Generator
> ignored
>
>
> Please help. :)
>
> 2018-01-11 19:14 GMT+01:00 Atanas Manoilov :
>
>> root@storage:~# pip freeze
>> Cheetah==2.4.4
>> CherryPy==3.1.2
>> M2Crypto==0.21.1
>> Mako==0.4.1
>> Markdown==2.3.1
>> PIL==1.1.7
>> Pygments==1.6
>> Twisted==10.1.0
>> configobj==5.0.6
>> cups==1.0
>> jsonrpclib==0.1.3
>> lxml==2.3.3
>> netsnmp-python==1.0a1
>> ply==3.1
>> pyOpenSSL==0.13
>> pybonjour==1.1.1
>> pycurl==7.19.0
>> pyusb==1.0.2
>> simplejson==2.1.2
>> six==1.11.0
>> wsgiref==0.1.2
>> zope.interface==3.3.0
>> root@storage:~#
>>
>>
>> On Wednesday, 10 January 2018 16:18:40 UTC+1, mwall wrote:
>>>
>>> On Sunday, December 3, 2017 at 6:50:17 PM UTC-5, Atanas Manoilov wrote:

 Hi,

 Thank you all for this driver development! I managed to have it running
 on Ubuntu 16.04 but unfortunately I need it on Solaris 11.2
 Can this driver run on Solaris 11.2 ?
 I face difficulties loading the driver. This is the log which is
 generated immediately after weewx process is started up:

>>>
>>> atanas,
>>>
>>> which pyusb and libusb are installed on the solaris 11.2 system?
>>>
>>> m
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Gro

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[Jindřich Štěpán]

Hi guys, thanks to your advice, especially this link
https://github.com/weewx/weewx/wiki/weewx-on-openwrt I was able ( on third
attempt after lack of space and then lack of memory on my router, so i
installed extroot and swap on usb flash stick ) to install weewx and it
reads data from TFA logger! :)

Now I would like to make some simple XML page with updated data so I can
read it from my home PLC machine. But after installation (I installed
following the http://www.weewx.com/docs/setup.htm page using setup.py, the
whole weewx data seems to be in folder /home/weewx/, driver for Klimalogg
is then in /home/weewx/bin/user/ ), there is no folder
/home/weewx/public_html/ .
Also, I found this in syslog...

Wed Jan 17 15:55:21 2018 user.notice weewx[1432]: manager: Added record
2018-01-17 15:55:00 ??? (1516204500) to database 'weewx-kl.sdb'
Wed Jan 17 15:55:21 2018 user.notice weewx[1432]: manager: Added record
2018-01-17 15:55:00 ??? (1516204500) to daily summary in 'weewx-kl.sdb'
Wed Jan 17 15:55:24 2018 user.crit weewx[1432]: reportengine: Unable to
instantiate generator weewx.cheetahgenerator.CheetahGenerator
Wed Jan 17 15:55:24 2018 user.crit weewx[1432]:   No module
named Cheetah.Template
Wed Jan 17 15:55:24 2018 user.info weewx[1432]:   Traceback
(most recent call last):
Wed Jan 17 15:55:24 2018 user.info weewx[1432]: File
"/home/weewx/bin/weewx/reportengine.py", line 220, in run
Wed Jan 17 15:55:24 2018 user.info weewx[1432]:   obj =
weeutil.weeutil._get_object(generator)(
Wed Jan 17 15:55:24 2018 user.info weewx[1432]: File
"/home/weewx/bin/weeutil/weeutil.py", line 1132, in _get_object
Wed Jan 17 15:55:24 2018 user.info weewx[1432]:   mod =
__import__(module)
Wed Jan 17 15:55:24 2018 user.info weewx[1432]: File
"/home/weewx/bin/weewx/cheetahgenerator.py", line 65, in 
Wed Jan 17 15:55:24 2018 user.info weewx[1432]:   import
Cheetah.Template
Wed Jan 17 15:55:24 2018 user.info weewx[1432]:   ImportError:
No module named Cheetah.Template
Wed Jan 17 15:55:24 2018 user.crit weewx[1432]:   Generator
ignored
Wed Jan 17 15:55:25 2018 user.crit weewx[1432]: reportengine: Unable to
instantiate generator weewx.imagegenerator.ImageGenerator
Wed Jan 17 15:55:25 2018 user.crit weewx[1432]:   No module
named Image
Wed Jan 17 15:55:25 2018 user.info weewx[1432]:   Traceback
(most recent call last):
Wed Jan 17 15:55:25 2018 user.info weewx[1432]: File
"/home/weewx/bin/weewx/reportengine.py", line 220, in run
Wed Jan 17 15:55:25 2018 user.info weewx[1432]:   obj =
weeutil.weeutil._get_object(generator)(
Wed Jan 17 15:55:25 2018 user.info weewx[1432]: File
"/home/weewx/bin/weeutil/weeutil.py", line 1132, in _get_object
Wed Jan 17 15:55:25 2018 user.info weewx[1432]:   mod =
__import__(module)
Wed Jan 17 15:55:25 2018 user.info weewx[1432]: File
"/home/weewx/bin/weewx/imagegenerator.py", line 15, in 
Wed Jan 17 15:55:25 2018 user.info weewx[1432]:   import
weeplot.genplot
Wed Jan 17 15:55:25 2018 user.info weewx[1432]: File
"/home/weewx/bin/weeplot/genplot.py", line 14, in 
Wed Jan 17 15:55:25 2018 user.info weewx[1432]:   import
Image, ImageDraw
Wed Jan 17 15:55:25 2018 user.info weewx[1432]:   ImportError:
No module named Image
Wed Jan 17 15:55:25 2018 user.crit weewx[1432]:   Generator
ignored


Please help. :)

2018-01-11 19:14 GMT+01:00 Atanas Manoilov :

> root@storage:~# pip freeze
> Cheetah==2.4.4
> CherryPy==3.1.2
> M2Crypto==0.21.1
> Mako==0.4.1
> Markdown==2.3.1
> PIL==1.1.7
> Pygments==1.6
> Twisted==10.1.0
> configobj==5.0.6
> cups==1.0
> jsonrpclib==0.1.3
> lxml==2.3.3
> netsnmp-python==1.0a1
> ply==3.1
> pyOpenSSL==0.13
> pybonjour==1.1.1
> pycurl==7.19.0
> pyusb==1.0.2
> simplejson==2.1.2
> six==1.11.0
> wsgiref==0.1.2
> zope.interface==3.3.0
> root@storage:~#
>
>
> On Wednesday, 10 January 2018 16:18:40 UTC+1, mwall wrote:
>>
>> On Sunday, December 3, 2017 at 6:50:17 PM UTC-5, Atanas Manoilov wrote:
>>>
>>> Hi,
>>>
>>> Thank you all for this driver development! I managed to have it running
>>> on Ubuntu 16.04 but unfortunately I need it on Solaris 11.2
>>> Can this driver run on Solaris 11.2 ?
>>> I face difficulties loading the driver. This is the log which is
>>> generated immediately after weewx process is started up:
>>>
>>
>> atanas,
>>
>> which pyusb and libusb are installed on the solaris 11.2 system?
>>
>> m
>>
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[Atanas Manoilov]

root@storage:~# pip freeze
Cheetah==2.4.4
CherryPy==3.1.2
M2Crypto==0.21.1
Mako==0.4.1
Markdown==2.3.1
PIL==1.1.7
Pygments==1.6
Twisted==10.1.0
configobj==5.0.6
cups==1.0
jsonrpclib==0.1.3
lxml==2.3.3
netsnmp-python==1.0a1
ply==3.1
pyOpenSSL==0.13
pybonjour==1.1.1
pycurl==7.19.0
pyusb==1.0.2
simplejson==2.1.2
six==1.11.0
wsgiref==0.1.2
zope.interface==3.3.0
root@storage:~#

On Wednesday, 10 January 2018 16:18:40 UTC+1, mwall wrote:
>
> On Sunday, December 3, 2017 at 6:50:17 PM UTC-5, Atanas Manoilov wrote:
>>
>> Hi,
>>
>> Thank you all for this driver development! I managed to have it running 
>> on Ubuntu 16.04 but unfortunately I need it on Solaris 11.2
>> Can this driver run on Solaris 11.2 ?
>> I face difficulties loading the driver. This is the log which is 
>> generated immediately after weewx process is started up:
>>
>
> atanas,
>
> which pyusb and libusb are installed on the solaris 11.2 system?
>
> 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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[Jindřich Štěpán]

mwall, thanks for the scenario draft. The only question remains, if the Asus
WL500GP V2 with OpenWRT will work with TFA USB receiver. Hopely yes. :)
Will try it hopely soon.

2018-01-11 14:18 GMT+01:00 mwall :

>
>
> On Thursday, January 11, 2018 at 8:03:32 AM UTC-5, Jindřich Štěpán wrote:
>>
>> Thank you guys for the answers. From PLC perspective, I can read data in
>> several ways. Considering use of openwrt with USB, the simplest for me
>> would be to use only minimal part of weewx as I understand it is whole
>> system. Would it be possible somehow to use only driver for TFA USB
>> receiver and build around some code to store data on router, or maybe send
>> over TCP/IP? Looking for minimum configuration. :) But maybe just
>> installing the whole weewx would be easier ? :) Is weewx capable to
>> send data over TCP/IP or better serve as TCP/IP server I can query this way
>> for data? Thank you.
>>
>
> you must also consider how the hardware behaves.  although it is possible
> to start weewx, read some data, stop weewx, then repeat, this is not an
> efficient or reliable way to use weewx with the klimalogg hardware.  it is
> better to keep weewx running continuously, communicating with the
> klimalogg.  then periodically have weewx either emit one or more files with
> the data or upload directly using MQTT or HTTP(S).
>
> regarding the last part of your question, you can use either a push or
> pull configuration.  imho, having weewx push will be the easier and more
> reliable approach.
>
> push: weewx is http client and does a PUT/POST/GET to push data to a server
>
> pull: weewx runs a web server and responds with data to GET requests
>
> push implementation is easy:
> 1) install weewx on the openwrt system
> 2) install the klimalogg extension
> 3) disable all of the weewx reports
> 4) disable local data retention if you do not have space on the openwrt
> 5) install an http uploader
> job done!
>
> for (4), it is best if you let weewx keep a local database (especially
> given how it interacts with the klimalogg logger).  so put a usb stick in
> the openwrt system to keep the local database.  its not that big.  and it
> sounds like you want that anyway.
>
> for (5), use an existing extension if the protocol you need has already
> been implemented.
>
> if no one has written a weewx extension with the protocol for your system,
> then write one!  it will be about 50-100 lines of python, there are plenty
> of examples, you can derive from an existing class so you don't have to
> write a bunch of new code, and if you post in the weewx-developer list
> you'll get plenty of help!
>
> m
>
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[mwall]

On Thursday, January 11, 2018 at 8:03:32 AM UTC-5, Jindřich Štěpán wrote:
>
> Thank you guys for the answers. From PLC perspective, I can read data in 
> several ways. Considering use of openwrt with USB, the simplest for me 
> would be to use only minimal part of weewx as I understand it is whole 
> system. Would it be possible somehow to use only driver for TFA USB 
> receiver and build around some code to store data on router, or maybe send 
> over TCP/IP? Looking for minimum configuration. :) But maybe just 
> installing the whole weewx would be easier ? :) Is weewx capable to 
> send data over TCP/IP or better serve as TCP/IP server I can query this way 
> for data? Thank you.
>

you must also consider how the hardware behaves.  although it is possible 
to start weewx, read some data, stop weewx, then repeat, this is not an 
efficient or reliable way to use weewx with the klimalogg hardware.  it is 
better to keep weewx running continuously, communicating with the 
klimalogg.  then periodically have weewx either emit one or more files with 
the data or upload directly using MQTT or HTTP(S).

regarding the last part of your question, you can use either a push or pull 
configuration.  imho, having weewx push will be the easier and more 
reliable approach.

push: weewx is http client and does a PUT/POST/GET to push data to a server

pull: weewx runs a web server and responds with data to GET requests

push implementation is easy:
1) install weewx on the openwrt system
2) install the klimalogg extension
3) disable all of the weewx reports
4) disable local data retention if you do not have space on the openwrt
5) install an http uploader
job done!

for (4), it is best if you let weewx keep a local database (especially 
given how it interacts with the klimalogg logger).  so put a usb stick in 
the openwrt system to keep the local database.  its not that big.  and it 
sounds like you want that anyway.

for (5), use an existing extension if the protocol you need has already 
been implemented.

if no one has written a weewx extension with the protocol for your system, 
then write one!  it will be about 50-100 lines of python, there are plenty 
of examples, you can derive from an existing class so you don't have to 
write a bunch of new code, and if you post in the weewx-developer list 
you'll get plenty of help!

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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[Jindřich Štěpán]

Thank you guys for the answers. From PLC perspective, I can read data in
several ways. Considering use of openwrt with USB, the simplest for me
would be to use only minimal part of weewx as I understand it is whole
system. Would it be possible somehow to use only driver for TFA USB
receiver and build around some code to store data on router, or maybe send
over TCP/IP? Looking for minimum configuration. :) But maybe just
installing the whole weewx would be easier ? :) Is weewx capable to
send data over TCP/IP or better serve as TCP/IP server I can query this way
for data? Thank you.

2018-01-10 16:16 GMT+01:00 mwall :

>
>
> On Wednesday, January 10, 2018 at 9:40:52 AM UTC-5, Jindřich Štěpán wrote:
>>
>> Hi,
>>
>> I own one Klimalogg station and also Foxtrot ( www.tecomat.com )home
>> automation system. I'm wondering about using the driver you developed on
>> some linux machine at my house and send data to my home PLC. I have Asus
>> WL500GP V2 with OpenWRT or Synology NAS both with USB connector.
>>
>> Do you think it would be possible somehow use Asus or Synology to read
>> and send data from TFA to my PLC?
>>
>
> yes.
>
> you can run weewx on openwrt.  here is an example from one weewx user:
>
> https://github.com/weewx/weewx/wiki/weewx-on-openwrt
>
> you can also run weewx on synology.
>
> as for sending data to the PLC, you need to be more specific.  what are
> the options for receiving data into the PLC?  or, i would assume you feed
> it into a larger control system that manages the PLC and other components?
>
> weewx can easily do MQTT, and it is not difficult to make it work with
> other protocols, whether they are direct (HTTP/HTTPS) or indirect
> (involving some sort of file transfer)
>
> m
>
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[mwall]

On Sunday, December 3, 2017 at 6:50:17 PM UTC-5, Atanas Manoilov wrote:
>
> Hi,
>
> Thank you all for this driver development! I managed to have it running on 
> Ubuntu 16.04 but unfortunately I need it on Solaris 11.2
> Can this driver run on Solaris 11.2 ?
> I face difficulties loading the driver. This is the log which is generated 
> immediately after weewx process is started up:
>

atanas,

which pyusb and libusb are installed on the solaris 11.2 system?

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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[Lucas “Hans” Heijst]

Hi Jindrich,

Many Synology NASses have linux as operating system. In principle weewx would 
run on such NAS. Years ago I had my TFA Primus weatherstation running on a 
DS209 and a DS209+.
The installation gave several problems in particular the serial port driver 
needed for the USB, so after a year with many problems I gave up and bought a 
Raspberry PI for reading my weather stations and the klimalogg pro. Last year I 
stopped with the TFA stations because they both were broken.
I don't know about your Foxtrot automation system. weewx has many interfaces 
with intelligent devices so there is a good chance it has an interface for the 
Foxtrot.
Best you can drop a question on the weewx user forum.
Success.

Cheers,
Luc

Verstuurd vanaf mijn iPad

> Op 10 jan. 2018 om 11:40 heeft Jindřich Štěpán  
> het volgende geschreven:
> 
> Hi,
> 
> I own one Klimalogg station and also Foxtrot ( www.tecomat.com )home 
> automation system. I'm wondering about using the driver you developed on some 
> linux machine at my house and send data to my home PLC. I have Asus WL500GP 
> V2 with OpenWRT or Synology NAS both with USB connector. 
> 
> Do you think it would be possible somehow use Asus or Synology to read and 
> send data from TFA to my PLC?
> 
> Thank you,
> Jindrich
> 
> 
> 
> 
> 
> Dne sobota 25. října 2014 19:05:41 UTC+2 Steffen napsal(a):
>> 
>> 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
>> #  WMR100WS28xx WS1
>> #  WMR200WS23xx CC3000
>> #  WMR9x8TE923  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: 86830
>> 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
> 
> -- 
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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.
For more options, v

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[Atanas Manoilov]

Hi,

Thank you all for this driver development! I managed to have it running on 
Ubuntu 16.04 but unfortunately I need it on Solaris 11.2
Can this driver run on Solaris 11.2 ?
I face difficulties loading the driver. This is the log which is generated 
immediately after weewx process is started up:


Dec  3 23:33:26 XXX weewx[11205]: [ID 702911 user.error] import of driver 
> failed: ld.so.1: isapython2.7: fatal: usb_detach_kernel_driver_np: can't 
> find symbol ()
> Dec  3 23:33:26 XXX weewx[11205]: [ID 702911 user.crit] engine: Unable to 
> load driver: ld.so.1: isapython2.7: fatal: usb_detach_kernel_driver_np: 
> can't find symbol
> Dec  3 23:33:26 XXX weewx[11205]: [ID 702911 user.crit]   
> Exiting...
>



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

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[w8opinfo]

Made a ui to correct history.dat files, i.e. faulty dates based on TFA 
1.3.2. windows version in c#. Since Klimalogg now runs on a linux server 
I've to write a interfaces in Python to organise the database raw as in TFA 
windows. Guess I could convert sqlite to history.dat format, but that 
doesn't seems right.

Anyway, very pleased to have Klimalogg running on a server.

R.
Edward



Op zondag 3 december 2017 21:21:56 UTC+1 schreef mwall:
>
>
> On Sunday, December 3, 2017 at 8:33:03 AM UTC-5, w8opinfo wrote:
>>
>> Heb jij nog een python code liggen die 0_history.dat format bestanden 
>> maakt die je wil delen?
>>
>
> the weewx-klimalogg driver does not read history.dat files - it 
> communicates directly with the klimalogg hardware
>
> a driver that reads history.dat file could be useful.  or perhaps it would 
> be more appropriate to write an extension to wee_import so that wee_import 
> could read history.dat files?
>
> 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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[mwall]

On Sunday, December 3, 2017 at 8:33:03 AM UTC-5, w8opinfo wrote:
>
> Heb jij nog een python code liggen die 0_history.dat format bestanden 
> maakt die je wil delen?
>

the weewx-klimalogg driver does not read history.dat files - it 
communicates directly with the klimalogg hardware

a driver that reads history.dat file could be useful.  or perhaps it would 
be more appropriate to write an extension to wee_import so that wee_import 
could read history.dat files?

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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[w8opinfo]

Waardeer je bijdragen, om m.n. de Klimalogg driver voor Linux te 
ontwikkelen, bijzonder.
Ben vorig jaar begonnen de bestaande TFA driver met een port manager te 
beschrijven. Ontdekte op dit forum dat je tijden vooruit was. Had inmiddels 
een ui geprogrammeerd op basis van 0_history.dat. Heb jij nog een python 
code liggen die 0_history.dat format bestanden maakt die je wil delen?

Edward





Op donderdag 18 december 2014 12:30:55 UTC+1 schreef 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 
>

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