[weewx-development] Re: Get dailyrain value in custom driver

2020-06-27 Thread Bastiaan Meelberg
Hi, Just use the rainfall_daily from the WLL and set that as the start value. On Saturday, June 27, 2020 at 11:45:12 PM UTC+2, flor...@pre-vost.fr wrote: > > Hi, > > How it is possible to have the daily rain in custom driver ? > > I would like to check this value to compare with the

[weewx-development] Get dailyrain value in custom driver

2020-06-27 Thread flor...@pre-vost.fr
Hi, How it is possible to have the daily rain in custom driver ? I would like to check this value to compare with the Weatherlink live module. It for attempt to fail result when you restart weewx -- You received this message because you are subscribed to the Google Groups

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread flor...@pre-vost.fr
Hi, Please keep one repo... how user can choose the right repo ? I think it will be good to split code to one git. Le samedi 27 juin 2020 à 10:53:21 UTC+2, flor...@pre-vost.fr a écrit : > Hi, > > Baastian, yes of course, I think it a good idea to make a request using > weewx object to read the

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread flor...@pre-vost.fr
Please keep a one repo on github. If we are some repo, how the user can choose the right driver ? It will be good to split Le samedi 27 juin 2020 à 10:53:21 UTC+2, flor...@pre-vost.fr a écrit : > Hi, > > Baastian, yes of course, I think it a good idea to make a request using > weewx

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread flor...@pre-vost.fr
Hi, Baastian, yes of course, I think it a good idea to make a request using weewx object to read the daily rain to the database and make a comparison with the rainfall daily by the WLL but I need the help of @Tom Keffer for this. For UnitUS, I know that if it possible but for readability, I

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread Bastiaan Meelberg
Yes! That will do the trick for now. Keep in mind that the rain count in the current repo is Wrong! I will post an updated one soon. On Saturday, June 27, 2020 at 10:46:45 AM UTC+2, Maarten van der Hoeven wrote: > > @Bastiaan, when I change this piece of code (txid=2), it is retrieving >

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread Bastiaan Meelberg
Hello Maarten, Glad you like my driver. I had similar problems, my ISS is on 1 and a wind unit on 4. WLL will produce more ‘conditions’ in the JSON with the same data_structure_type. So simply looking for a structure_type is not sufficient. for example here is my current_condition: - {

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread Maarten van der Hoeven
@Bastiaan, when I change this piece of code (txid=2), it is retrieving live data from ISS: def DecodeDataWLL(self, data): timestamp = data['ts'] packet = {'dateTime': timestamp, 'usUnits': weewx.US} for condition in data['conditions']:

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread Maarten van der Hoeven
Hello Bastiaan, The WLL is a wonderful piece of equipment. Now I can run production with WeeWX, and start a test-enviroment in a virtual machine, while talking to the same WLL. I've installed your driver. I have running my ISS on ID 2 (and have an external temp sensor running on sensor 3).

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread Bastiaan Meelberg
Python is pretty new to me, I was unaware of the use of the _packet underscore method. I will update my code. Thanks for the tip. Have a look at the rain calculations, I found out yesterday, during a rain shower, setting the self.rain_previous_period to zero is not a good idea. If weewx is

[weewx-development] Re: Syslog use in thread possibly cause thread exit?

2020-06-27 Thread James
On Friday, June 12, 2020 at 4:01:38 PM UTC+10, gjr80 wrote: > > Hi, > > Can’t see why syslog is not thread safe, before v4 the WeeWX report engine > ran in a separate thread and all logging was done through syslog and I > don’t recall there ever being a syslog/thread issue. Likewise a number of