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 [email protected]: > 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 [email protected]: > >> 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 >>> [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/6e4b04f7-1938-4157-8fc3-83c9e4e0191bn%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/6e4b04f7-1938-4157-8fc3-83c9e4e0191bn%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> >>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> >>> Virus-free. >>> www.avast.com >>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> >>> >>> <#m_1925971519823076046_m_3145951131719336509_m_-1528038675054062087_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/57e47791-dc4b-4ea1-ae85-98fdd1e75836n%40googlegroups.com.
