[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

It is unable to open socket 2, it looks like an other weewx is running. 

On Sunday, July 12, 2020 at 6:09:14 PM UTC+2, Maarten van der Hoeven wrote:
>
> Strange. I want to use the driver in my 'production'-environment, and got 
> this error. Any clue? As on my 'test'-environment it is running okay.
>
> Jul 12 18:03:16 weewx weewx[907239] INFO __main__: Using configuration 
> file /etc/weewx/weewx.conf
> Jul 12 18:03:16 weewx weewx[907239] INFO __main__: Debug is 1
> Jul 12 18:03:16 weewx weewx[907239] DEBUG __main__: Initializing engine
> Jul 12 18:03:16 weewx weewx[907239] INFO weewx.engine: Loading station 
> type WeatherLinkLiveUDP (user.weatherlinkliveudp)
> Jul 12 18:03:16 weewx weewx[907239] CRITICAL __main__: Caught OSError: 
> [Errno 98] Address already in use
> Jul 12 18:03:16 weewx weewx[907239] CRITICAL __main__:   Traceback 
> (most recent call last):
> Jul 12 18:03:16 weewx weewx[907239] CRITICAL __main__: File 
> "/usr/share/weewx/weewxd", line 148, in main
> Jul 12 18:03:16 weewx weewx[907239] CRITICAL __main__:   
> engine = weewx.engine.StdEngine(config_dict)
> Jul 12 18:03:16 weewx weewx[907239] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 69, in __init__
> Jul 12 18:03:16 weewx weewx[907239] CRITICAL __main__:   
> self.setupStation(config_dict)
> Jul 12 18:03:16 weewx weewx[907239] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 92, in setupStation
> Jul 12 18:03:16 weewx weewx[907239] CRITICAL __main__:   
> __import__(driver)
> Jul 12 18:03:16 weewx weewx[907239] CRITICAL __main__: File 
> "/usr/share/weewx/user/weatherlinkliveudp.py", line 50, in 
> Jul 12 18:03:16 weewx weewx[907239] CRITICAL __main__:   
> comsocket.bind(('', 2))
> Jul 12 18:03:16 weewx weewx[907239] CRITICAL __main__:   OSError: 
> [Errno 98] Address already in use
> Jul 12 18:03:16 weewx weewx[907239] CRITICAL __main__:   Waiting 
> 10 seconds then retrying...
>
> Driver:
> maarten@weewx:/usr/share/weewx/user$ ls -las
> total 184
>   4 drwxr-xr-x  4 root root   4096 Jul 12 18:07 .
>   4 drwxr-xr-x 11 root root   4096 Jun  2 11:15 ..
> 112 -rw-rw-r--  1 root root 112300 May 27 19:54 belchertown.py
>   4 -rw-rw-r--  1 root root   1795 Jul 10 11:36 calcdrought.py
>   4 -rw-r--r--  1 root root541 May 25 21:10 extensions.py
>   4 -rw-r--r--  1 root root306 Jun  2 00:16 __init__.py
>   4 drwxr-xr-x  7 root root   4096 Jul 12 18:00 installer
>   4 -rw-r--r--  1 root root   3857 Jun  3 12:17 lastrain.py
>  20 -rw-r--r--  1 root root  19742 May 27 15:25 mqtt.py
>   4 drwxr-xr-x  2 root root   4096 Jul 12 18:00 __pycache__
>  20 -rw-r--r--  1 root root  16841 Jul 12 18:00 weatherlinkliveudp.py
>
>
> Conf:
> 
> # station_type = Vantage
> station_type = WeatherLinkLiveUDP
> 
>
> ##
>
> [WeatherLinkLiveUDP]
> wll_ip = 192.168.2.33
> poll_interval = 10
> driver = user.weatherlinkliveudp
> extra_id = 3
>
>
>
>
> Op woensdag 8 juli 2020 om 19:37:41 UTC+2 schreef Maarten van der Hoeven:
>
>> Hi,
>>
>> I've been testing with the driver for a couple of days now, and all data 
>> is looking fine. I didnt see any strange deviation from the data that comes 
>> from your driver, and the data that comes from my WeatherLink IP (set up in 
>> another environment).
>>
>> So, it look good!
>>
>>
>> Op dinsdag 7 juli 2020 om 23:07:46 UTC+2 schreef Maarten van der Hoeven:
>>
>>> Yes, now the csv (although still empty) is created in the 'root'-dir. No 
>>> need for tmp anymore
>>>
>>> maarten@ubuntu:~/weatherlink$ ls -las
>>> total 36
>>>  4 drwxrwxr-x  2 maarten maarten  4096 Jul  7 23:06 .
>>>  4 drwxr-xr-x 24 maarten maarten  4096 Jul  7 21:41 ..
>>>  0 -rw-rw-r--  1 maarten maarten 0 Jul  7 23:06 davis1594155999.csv
>>>  8 -rw-r--r--  1 maarten maarten  7282 Jul  7 21:43 davis-csv.conf
>>>  4 -rw-r--r--  1 maarten maarten  2242 Jul  7 21:31 README.md
>>> 16 -rw-r--r--  1 maarten maarten 13259 Jul  7 22:53 weewx_weatherlink
>>>
>>>
>>> Op dinsdag 7 juli 2020 om 22:54:33 UTC+2 schreef Bastiaan Meelberg:
>>>
 Somehow the tmp/ dir is not created. I dropped the tmp for now. Can you 
 try again?



 On Tuesday, July 7, 2020 at 9:57:43 PM UTC+2, Maarten van der Hoeven 
 wrote:
>
> Okay, have played with it.
>
> First I needed to create a tmp-directory. Without it, the csv-file 
> cannot be created.
> Started the importer to import one single day: 2020-01-01. It creates 
> an empty csv-file 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

[weewx-development] Re: Davis Weather Link Live driver with UDP

[flor...@pre-vost.fr]

HI Bastiaan,

If you want to check all values on JSON data for all sensor, you can make a 
while function with the lenght of sensors like this : length_json = 
len(data_wl['sensors'])

Le mercredi 8 juillet 2020 à 22:26:40 UTC+2, hoev...@gmail.com a écrit :

> fetched the latest from github, and changed the datasets to 2,4,3. Valid 
> data downloaded. Output on screen:
> Fetching 1594116000 - 1594117800
> The following sensors are found:
> Product name: WeatherLink LIVE Health
> category:Health
> sensor type: 504
> Product name: Sensor Suite
> category:Other
> sensor type: 55
> Product name: Barometer
> category:Barometer
> sensor type: 242
> Product name: Inside Temp/Hum
> category:Inside Temp/Hum
> sensor type: 243
> Product name: Vantage Pro2 Plus with 24-hr-Fan-Aspirated Radiation shield, 
> includes UV & Solar Radiation Sensors
> category:ISS
> sensor type: 46
>
>
> Op woensdag 8 juli 2020 om 22:09:30 UTC+2 schreef Bastiaan Meelberg:
>
>> Interesting. I made a small change so the program will show the sensors 
>> found. 
>> It looks like the extra temp is dataset 0 (lets skip that for now), 
>> barometer is set 2, inside is set 3 and the remaining data is set 4. So 
>> like you figured out, this should give the correct data:
>>
>> baro_data = weather_data['sensors'][2]['data'
>>>
>>> ]
>>> iss_data = weather_data['sensors'][4]['data']
>>> indoor_data = weather_data['sensors'][3]['data']
>>>
>>>
>> On Wednesday, July 8, 2020 at 9:53:38 PM UTC+2, Maarten van der Hoeven 
>> wrote:
>>>
>>> maarten@ubuntu:~/weatherlink$ python3 weewx_weatherlink -s 
>>> 2020-07-07T12:00 -e 2020-07-07T12:30
>>> Use dates: 2020-07-07 12:00:00 - 2020-07-07 12:30:00
>>> 1 [1594116000] - [1594117800]: 2020-07-07 12:00:00 - 2020-07-07 12:30:00
>>> Finding stations:
>>>
>>>
>>>
>>> Op woensdag 8 juli 2020 om 21:22:33 UTC+2 schreef Bastiaan Meelberg:
>>>
 Thanks for testing.

 The 'problem' with api v2 is that it delivers a HUGE amount of data. 
 With my setup it works perfect, I can import months at the time.

 I think indeed of you different setup it is not working. Maybe a 
 question/answer that the program is showing bit of the data and asks if it 
 is the data the user wants to import.

 I added a 'print url' to the latest build, if you can try an import of 
 a short period, lets say 30 min and use the link to download the JSON data 
 in a web-browser. (The link is valid for a few minutes, due to the 
 timestamp in the signature) and post it.




 On Wednesday, July 8, 2020 at 9:10:36 PM UTC+2, Maarten van der Hoeven 
 wrote:
>
> If I change the code to (#2, #0 and #3 are the values in your code), 
> the data is imported okay (except extratemp1). I guess it has something 
> to 
> do with my ISS not having ID=1, but ID=2. An my external temp sensor 
> running on ID=3
>
> Find attached the resulting csv file
>
> baro_data = weather_data['sensors'][2]['data'] #2
> iss_data = weather_data['sensors'][1]['data'] #0
> indoor_data = weather_data['sensors'][3]['data'] #3
>
>
> Op dinsdag 7 juli 2020 om 21:33:57 UTC+2 schreef Bastiaan Meelberg:
>
>> Hi Maarten,
>>
>> If you want you can give the importer a try:
>>
>> https://github.com/grebleem/weewx_wl_import
>>
>> Thanks.
>>
>>
>> On Tuesday, July 7, 2020 at 1:09:34 PM UTC+2, Maarten van der Hoeven 
>> wrote:
>>>
>>> Hi Bastiaan,
>>>
>>> something I can test?
>>>
>>> Op zondag 5 juli 2020 14:02:38 UTC+2 schreef flor...@pre-vost.fr:

 Sorry for that. 

 There was a  misunderstandings . Let's forget this conversation;)  

 -fp 

 Le samedi 4 juillet 2020 à 13:36:23 UTC+2, hoev...@gmail.com a 
 écrit :

> Yes, agree. I like the weather, I like programming, I like to 
> cooperate. It's my current lack of python-knowledge that I want to 
> contribute the best I can do right now, and that is testing both of 
> your 
> drivers. I dont see it as competition, and may the best win. Far from 
> that. 
> In the end, it's my small contribution to the community in testing 
> two 
> drivers, and make them both better working. In hoping that the user 
> pick 
> the driver it feels most comfortably with, or not. 
>
> Op zaterdag 4 juli 2020 12:52:09 UTC+2 schreef Bastiaan Meelberg:
>
>> I just program what I need, because I like programming.
>>  
>> Use my program (you all-ready did I see in you're driver ;-), or 
>> don't use it. That is the good think of open source. 
>>
>> Your importer is doing the calculation e.g. Fahrenheit to 

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

fetched the latest from github, and changed the datasets to 2,4,3. Valid 
data downloaded. Output on screen:
Fetching 1594116000 - 1594117800
The following sensors are found:
Product name: WeatherLink LIVE Health
category:Health
sensor type: 504
Product name: Sensor Suite
category:Other
sensor type: 55
Product name: Barometer
category:Barometer
sensor type: 242
Product name: Inside Temp/Hum
category:Inside Temp/Hum
sensor type: 243
Product name: Vantage Pro2 Plus with 24-hr-Fan-Aspirated Radiation shield, 
includes UV & Solar Radiation Sensors
category:ISS
sensor type: 46


Op woensdag 8 juli 2020 om 22:09:30 UTC+2 schreef Bastiaan Meelberg:

> Interesting. I made a small change so the program will show the sensors 
> found. 
> It looks like the extra temp is dataset 0 (lets skip that for now), 
> barometer is set 2, inside is set 3 and the remaining data is set 4. So 
> like you figured out, this should give the correct data:
>
> baro_data = weather_data['sensors'][2]['data'
>>
>> ]
>> iss_data = weather_data['sensors'][4]['data']
>> indoor_data = weather_data['sensors'][3]['data']
>>
>>
> On Wednesday, July 8, 2020 at 9:53:38 PM UTC+2, Maarten van der Hoeven 
> wrote:
>>
>> maarten@ubuntu:~/weatherlink$ python3 weewx_weatherlink -s 
>> 2020-07-07T12:00 -e 2020-07-07T12:30
>> Use dates: 2020-07-07 12:00:00 - 2020-07-07 12:30:00
>> 1 [1594116000] - [1594117800]: 2020-07-07 12:00:00 - 2020-07-07 12:30:00
>> Finding stations:
>>
>>
>>
>> Op woensdag 8 juli 2020 om 21:22:33 UTC+2 schreef Bastiaan Meelberg:
>>
>>> Thanks for testing.
>>>
>>> The 'problem' with api v2 is that it delivers a HUGE amount of data. 
>>> With my setup it works perfect, I can import months at the time.
>>>
>>> I think indeed of you different setup it is not working. Maybe a 
>>> question/answer that the program is showing bit of the data and asks if it 
>>> is the data the user wants to import.
>>>
>>> I added a 'print url' to the latest build, if you can try an import of a 
>>> short period, lets say 30 min and use the link to download the JSON data in 
>>> a web-browser. (The link is valid for a few minutes, due to the timestamp 
>>> in the signature) and post it.
>>>
>>>
>>>
>>>
>>> On Wednesday, July 8, 2020 at 9:10:36 PM UTC+2, Maarten van der Hoeven 
>>> wrote:

 If I change the code to (#2, #0 and #3 are the values in your code), 
 the data is imported okay (except extratemp1). I guess it has something to 
 do with my ISS not having ID=1, but ID=2. An my external temp sensor 
 running on ID=3

 Find attached the resulting csv file

 baro_data = weather_data['sensors'][2]['data'] #2
 iss_data = weather_data['sensors'][1]['data'] #0
 indoor_data = weather_data['sensors'][3]['data'] #3


 Op dinsdag 7 juli 2020 om 21:33:57 UTC+2 schreef Bastiaan Meelberg:

> Hi Maarten,
>
> If you want you can give the importer a try:
>
> https://github.com/grebleem/weewx_wl_import
>
> Thanks.
>
>
> On Tuesday, July 7, 2020 at 1:09:34 PM UTC+2, Maarten van der Hoeven 
> wrote:
>>
>> Hi Bastiaan,
>>
>> something I can test?
>>
>> Op zondag 5 juli 2020 14:02:38 UTC+2 schreef flor...@pre-vost.fr:
>>>
>>> Sorry for that. 
>>>
>>> There was a  misunderstandings . Let's forget this conversation;)  
>>>
>>> -fp 
>>>
>>> Le samedi 4 juillet 2020 à 13:36:23 UTC+2, hoev...@gmail.com a 
>>> écrit :
>>>
 Yes, agree. I like the weather, I like programming, I like to 
 cooperate. It's my current lack of python-knowledge that I want to 
 contribute the best I can do right now, and that is testing both of 
 your 
 drivers. I dont see it as competition, and may the best win. Far from 
 that. 
 In the end, it's my small contribution to the community in testing two 
 drivers, and make them both better working. In hoping that the user 
 pick 
 the driver it feels most comfortably with, or not. 

 Op zaterdag 4 juli 2020 12:52:09 UTC+2 schreef Bastiaan Meelberg:

> I just program what I need, because I like programming.
>  
> Use my program (you all-ready did I see in you're driver ;-), or 
> don't use it. That is the good think of open source. 
>
> Your importer is doing the calculation e.g. Fahrenheit to Celsius 
> I don't like that, weewx is way better in making the conversions. 
> Also I just want to import a date range and not have to figure out 
> my station_id. So I decided to make my own.
>
> But feel free to make a better driver/importer. 
>
>
> On Saturday, July 4, 2020 at 12:38:54 PM UTC+2, Florentin Prevost 
> wrote:
>>
>> Like we 

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

Interesting. I made a small change so the program will show the sensors 
found. 
It looks like the extra temp is dataset 0 (lets skip that for now), 
barometer is set 2, inside is set 3 and the remaining data is set 4. So 
like you figured out, this should give the correct data:

baro_data = weather_data['sensors'][2]['data']
> iss_data = weather_data['sensors'][4]['data']
> indoor_data = weather_data['sensors'][3]['data']
>
>
On Wednesday, July 8, 2020 at 9:53:38 PM UTC+2, Maarten van der Hoeven 
wrote:
>
> maarten@ubuntu:~/weatherlink$ python3 weewx_weatherlink -s 
> 2020-07-07T12:00 -e 2020-07-07T12:30
> Use dates: 2020-07-07 12:00:00 - 2020-07-07 12:30:00
> 1 [1594116000] - [1594117800]: 2020-07-07 12:00:00 - 2020-07-07 12:30:00
> Finding stations:
>
>
>
> Op woensdag 8 juli 2020 om 21:22:33 UTC+2 schreef Bastiaan Meelberg:
>
>> Thanks for testing.
>>
>> The 'problem' with api v2 is that it delivers a HUGE amount of data. With 
>> my setup it works perfect, I can import months at the time.
>>
>> I think indeed of you different setup it is not working. Maybe a 
>> question/answer that the program is showing bit of the data and asks if it 
>> is the data the user wants to import.
>>
>> I added a 'print url' to the latest build, if you can try an import of a 
>> short period, lets say 30 min and use the link to download the JSON data in 
>> a web-browser. (The link is valid for a few minutes, due to the timestamp 
>> in the signature) and post it.
>>
>>
>>
>>
>> On Wednesday, July 8, 2020 at 9:10:36 PM UTC+2, Maarten van der Hoeven 
>> wrote:
>>>
>>> If I change the code to (#2, #0 and #3 are the values in your code), the 
>>> data is imported okay (except extratemp1). I guess it has something to do 
>>> with my ISS not having ID=1, but ID=2. An my external temp sensor running 
>>> on ID=3
>>>
>>> Find attached the resulting csv file
>>>
>>> baro_data = weather_data['sensors'][2]['data'] #2
>>> iss_data = weather_data['sensors'][1]['data'] #0
>>> indoor_data = weather_data['sensors'][3]['data'] #3
>>>
>>>
>>> Op dinsdag 7 juli 2020 om 21:33:57 UTC+2 schreef Bastiaan Meelberg:
>>>
 Hi Maarten,

 If you want you can give the importer a try:

 https://github.com/grebleem/weewx_wl_import

 Thanks.


 On Tuesday, July 7, 2020 at 1:09:34 PM UTC+2, Maarten van der Hoeven 
 wrote:
>
> Hi Bastiaan,
>
> something I can test?
>
> Op zondag 5 juli 2020 14:02:38 UTC+2 schreef flor...@pre-vost.fr:
>>
>> Sorry for that. 
>>
>> There was a  misunderstandings . Let's forget this conversation;)  
>>
>> -fp 
>>
>> Le samedi 4 juillet 2020 à 13:36:23 UTC+2, hoev...@gmail.com a 
>> écrit :
>>
>>> Yes, agree. I like the weather, I like programming, I like to 
>>> cooperate. It's my current lack of python-knowledge that I want to 
>>> contribute the best I can do right now, and that is testing both of 
>>> your 
>>> drivers. I dont see it as competition, and may the best win. Far from 
>>> that. 
>>> In the end, it's my small contribution to the community in testing two 
>>> drivers, and make them both better working. In hoping that the user 
>>> pick 
>>> the driver it feels most comfortably with, or not. 
>>>
>>> Op zaterdag 4 juli 2020 12:52:09 UTC+2 schreef Bastiaan Meelberg:
>>>
 I just program what I need, because I like programming.
  
 Use my program (you all-ready did I see in you're driver ;-), or 
 don't use it. That is the good think of open source. 

 Your importer is doing the calculation e.g. Fahrenheit to Celsius I 
 don't like that, weewx is way better in making the conversions. 
 Also I just want to import a date range and not have to figure out 
 my station_id. So I decided to make my own.

 But feel free to make a better driver/importer. 


 On Saturday, July 4, 2020 at 12:38:54 PM UTC+2, Florentin Prevost 
 wrote:
>
> Like we work on the same functions for Wll driver. Why not to work 
> together to developp the driver ? Each one developp the same code and 
> it 
> would a shame to work 2 times for the same code ...



-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/030685d7-1ad5-4fc6-af67-9812bf28a617o%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

maarten@ubuntu:~/weatherlink$ python3 weewx_weatherlink -s 2020-07-07T12:00 
-e 2020-07-07T12:30
Use dates: 2020-07-07 12:00:00 - 2020-07-07 12:30:00
1 [1594116000] - [1594117800]: 2020-07-07 12:00:00 - 2020-07-07 12:30:00
Finding stations:



Op woensdag 8 juli 2020 om 21:22:33 UTC+2 schreef Bastiaan Meelberg:

> Thanks for testing.
>
> The 'problem' with api v2 is that it delivers a HUGE amount of data. With 
> my setup it works perfect, I can import months at the time.
>
> I think indeed of you different setup it is not working. Maybe a 
> question/answer that the program is showing bit of the data and asks if it 
> is the data the user wants to import.
>
> I added a 'print url' to the latest build, if you can try an import of a 
> short period, lets say 30 min and use the link to download the JSON data in 
> a web-browser. (The link is valid for a few minutes, due to the timestamp 
> in the signature) and post it.
>
>
>
>
> On Wednesday, July 8, 2020 at 9:10:36 PM UTC+2, Maarten van der Hoeven 
> wrote:
>>
>> If I change the code to (#2, #0 and #3 are the values in your code), the 
>> data is imported okay (except extratemp1). I guess it has something to do 
>> with my ISS not having ID=1, but ID=2. An my external temp sensor running 
>> on ID=3
>>
>> Find attached the resulting csv file
>>
>> baro_data = weather_data['sensors'][2]['data'] #2
>> iss_data = weather_data['sensors'][1]['data'] #0
>> indoor_data = weather_data['sensors'][3]['data'] #3
>>
>>
>> Op dinsdag 7 juli 2020 om 21:33:57 UTC+2 schreef Bastiaan Meelberg:
>>
>>> Hi Maarten,
>>>
>>> If you want you can give the importer a try:
>>>
>>> https://github.com/grebleem/weewx_wl_import
>>>
>>> Thanks.
>>>
>>>
>>> On Tuesday, July 7, 2020 at 1:09:34 PM UTC+2, Maarten van der Hoeven 
>>> wrote:

 Hi Bastiaan,

 something I can test?

 Op zondag 5 juli 2020 14:02:38 UTC+2 schreef flor...@pre-vost.fr:
>
> Sorry for that. 
>
> There was a  misunderstandings . Let's forget this conversation;)  
>
> -fp 
>
> Le samedi 4 juillet 2020 à 13:36:23 UTC+2, hoev...@gmail.com a écrit :
>
>> Yes, agree. I like the weather, I like programming, I like to 
>> cooperate. It's my current lack of python-knowledge that I want to 
>> contribute the best I can do right now, and that is testing both of your 
>> drivers. I dont see it as competition, and may the best win. Far from 
>> that. 
>> In the end, it's my small contribution to the community in testing two 
>> drivers, and make them both better working. In hoping that the user pick 
>> the driver it feels most comfortably with, or not. 
>>
>> Op zaterdag 4 juli 2020 12:52:09 UTC+2 schreef Bastiaan Meelberg:
>>
>>> I just program what I need, because I like programming.
>>>  
>>> Use my program (you all-ready did I see in you're driver ;-), or 
>>> don't use it. That is the good think of open source. 
>>>
>>> Your importer is doing the calculation e.g. Fahrenheit to Celsius I 
>>> don't like that, weewx is way better in making the conversions. 
>>> Also I just want to import a date range and not have to figure out 
>>> my station_id. So I decided to make my own.
>>>
>>> But feel free to make a better driver/importer. 
>>>
>>>
>>> On Saturday, July 4, 2020 at 12:38:54 PM UTC+2, Florentin Prevost 
>>> wrote:

 Like we work on the same functions for Wll driver. Why not to work 
 together to developp the driver ? Each one developp the same code and 
 it 
 would a shame to work 2 times for the same code ...
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/fdbe50d7-54f1-4f19-888b-669425c1a6b1n%40googlegroups.com.


92884.json
Description: application/json

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

Thanks for testing.

The 'problem' with api v2 is that it delivers a HUGE amount of data. With 
my setup it works perfect, I can import months at the time.

I think indeed of you different setup it is not working. Maybe a 
question/answer that the program is showing bit of the data and asks if it 
is the data the user wants to import.

I added a 'print url' to the latest build, if you can try an import of a 
short period, lets say 30 min and use the link to download the JSON data in 
a web-browser. (The link is valid for a few minutes, due to the timestamp 
in the signature) and post it.




On Wednesday, July 8, 2020 at 9:10:36 PM UTC+2, Maarten van der Hoeven 
wrote:
>
> If I change the code to (#2, #0 and #3 are the values in your code), the 
> data is imported okay (except extratemp1). I guess it has something to do 
> with my ISS not having ID=1, but ID=2. An my external temp sensor running 
> on ID=3
>
> Find attached the resulting csv file
>
> baro_data = weather_data['sensors'][2]['data'] #2
> iss_data = weather_data['sensors'][1]['data'] #0
> indoor_data = weather_data['sensors'][3]['data'] #3
>
>
> Op dinsdag 7 juli 2020 om 21:33:57 UTC+2 schreef Bastiaan Meelberg:
>
>> Hi Maarten,
>>
>> If you want you can give the importer a try:
>>
>> https://github.com/grebleem/weewx_wl_import
>>
>> Thanks.
>>
>>
>> On Tuesday, July 7, 2020 at 1:09:34 PM UTC+2, Maarten van der Hoeven 
>> wrote:
>>>
>>> Hi Bastiaan,
>>>
>>> something I can test?
>>>
>>> Op zondag 5 juli 2020 14:02:38 UTC+2 schreef flor...@pre-vost.fr:

 Sorry for that. 

 There was a  misunderstandings . Let's forget this conversation;)  

 -fp 

 Le samedi 4 juillet 2020 à 13:36:23 UTC+2, hoev...@gmail.com a écrit :

> Yes, agree. I like the weather, I like programming, I like to 
> cooperate. It's my current lack of python-knowledge that I want to 
> contribute the best I can do right now, and that is testing both of your 
> drivers. I dont see it as competition, and may the best win. Far from 
> that. 
> In the end, it's my small contribution to the community in testing two 
> drivers, and make them both better working. In hoping that the user pick 
> the driver it feels most comfortably with, or not. 
>
> Op zaterdag 4 juli 2020 12:52:09 UTC+2 schreef Bastiaan Meelberg:
>
>> I just program what I need, because I like programming.
>>  
>> Use my program (you all-ready did I see in you're driver ;-), or 
>> don't use it. That is the good think of open source. 
>>
>> Your importer is doing the calculation e.g. Fahrenheit to Celsius I 
>> don't like that, weewx is way better in making the conversions. 
>> Also I just want to import a date range and not have to figure out my 
>> station_id. So I decided to make my own.
>>
>> But feel free to make a better driver/importer. 
>>
>>
>> On Saturday, July 4, 2020 at 12:38:54 PM UTC+2, Florentin Prevost 
>> wrote:
>>>
>>> Like we work on the same functions for Wll driver. Why not to work 
>>> together to developp the driver ? Each one developp the same code and 
>>> it 
>>> would a shame to work 2 times for the same code ...
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/6fc1db15-6034-4571-817d-307e46ee377ao%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

I'm sorry, too quick. Previous code-change was lacking external values. 
With this adjustment, all internal and external data is collected by the 
import (except extratemp1).

baro_data = weather_data['sensors'][2]['data'] #2
iss_data = weather_data['sensors'][4]['data'] #0
indoor_data = weather_data['sensors'][3]['data'] #3

Find attached the produced cvs, now filled with correct data

Op woensdag 8 juli 2020 om 21:10:36 UTC+2 schreef Maarten van der Hoeven:

> If I change the code to (#2, #0 and #3 are the values in your code), the 
> data is imported okay (except extratemp1). I guess it has something to do 
> with my ISS not having ID=1, but ID=2. An my external temp sensor running 
> on ID=3
>
> Find attached the resulting csv file
>
> baro_data = weather_data['sensors'][2]['data'] #2
> iss_data = weather_data['sensors'][1]['data'] #0
> indoor_data = weather_data['sensors'][3]['data'] #3
>
>
> Op dinsdag 7 juli 2020 om 21:33:57 UTC+2 schreef Bastiaan Meelberg:
>
>> Hi Maarten,
>>
>
>> If you want you can give the importer a try:
>>
>> https://github.com/grebleem/weewx_wl_import
>>
>> Thanks.
>>
>
>>
>> On Tuesday, July 7, 2020 at 1:09:34 PM UTC+2, Maarten van der Hoeven 
>> wrote:
>>>
>>> Hi Bastiaan,
>>>
>>> something I can test?
>>>
>>> Op zondag 5 juli 2020 14:02:38 UTC+2 schreef flor...@pre-vost.fr:

 Sorry for that. 

 There was a  misunderstandings . Let's forget this conversation;)  

 -fp 

 Le samedi 4 juillet 2020 à 13:36:23 UTC+2, hoev...@gmail.com a écrit :

> Yes, agree. I like the weather, I like programming, I like to 
> cooperate. It's my current lack of python-knowledge that I want to 
> contribute the best I can do right now, and that is testing both of your 
> drivers. I dont see it as competition, and may the best win. Far from 
> that. 
> In the end, it's my small contribution to the community in testing two 
> drivers, and make them both better working. In hoping that the user pick 
> the driver it feels most comfortably with, or not. 
>
> Op zaterdag 4 juli 2020 12:52:09 UTC+2 schreef Bastiaan Meelberg:
>
>> I just program what I need, because I like programming.
>>  
>> Use my program (you all-ready did I see in you're driver ;-), or 
>> don't use it. That is the good think of open source. 
>>
>> Your importer is doing the calculation e.g. Fahrenheit to Celsius I 
>> don't like that, weewx is way better in making the conversions. 
>> Also I just want to import a date range and not have to figure out my 
>> station_id. So I decided to make my own.
>>
>> But feel free to make a better driver/importer. 
>>
>>
>> On Saturday, July 4, 2020 at 12:38:54 PM UTC+2, Florentin Prevost 
>> wrote:
>>>
>>> Like we work on the same functions for Wll driver. Why not to work 
>>> together to developp the driver ? Each one developp the same code and 
>>> it 
>>> would a shame to work 2 times for the same code ...
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/07f829ba-f956-41cd-94cd-17a694fabdddn%40googlegroups.com.
ts,usUnits,arch_int,wind_dir_of_prevail,temp_avg,dew_point_last,heat_index_last,wind_chill_last,bar_sea_level,bar_absolute,temp_in_last,dew_point_in,hum_in_last,wind_speed_avg,wind_speed_hi,wind_speed_hi_dir,wind_run,hum_last,rainfall_in,rain_rate_hi_in,solar_rad_avg,uv_index_avg
1594073100,1,5,247,52.4,49.7,52.5,52.4,30.146,30.134,66.3,53.8,64.1,2.68,5,248,0.2234,90.5,0,0,0,0
1594073400,1,5,270,52.4,49.7,52.5,52.3,30.147,30.135,66.1,53.6,64,3.43,7,254,0.2858,90.6,0,0,0,0
1594073700,1,5,270,52.3,49.6,52.4,51.9,30.148,30.136,66.1,53.7,64.3,3.62,7,259,0.3015,90.5,0,0,0,0
1594074000,1,5,270,52.2,49.6,52.4,52.1,30.149,30.137,65.9,53.5,64.2,2.81,7,284,0.23416667,90.6,0,0,0,0
1594074300,1,5,270,52.2,49.5,52.3,52.2,30.149,30.137,65.7,53.5,64.7,2.06,4,272,0.1717,90.6,0,0,0,0
1594074600,1,5,270,52.1,49.4,52.2,52.1,30.147,30.135,65.8,53.6,64.7,2.43,4,269,0.2025,90.6,0,0,0,0
1594074900,1,5,270,52,49.4,52.1,52,30.149,30.137,65.5,53.3,64.7,2.81,4,274,0.23416667,90.8,0,0,0,0
1594075200,1,5,270,51.9,49.4,52,51.9,30.146,30.134,65.5,53.4,64.9,2.75,6,281,0.22916667,91,0,0,0,0
1594075500,1,5,270,51.9,49.4,52,51.9,30.152,30.14,65.5,53.4,64.9,2.87,6,258,0.2391,91,0,0,0,0
1594075800,1,5,247,51.9,49.4,52,51.9,30.154,30.142,65.6,53.5,64.9,2.68,5,252,0.2234,91.2,0,0,0,0
1594076100,1,5,247,51.9,49.4,52,51.9,30.153,30.141,65.4,53.5,65.4,2.43,4,247,0.2025,91.2,0,0,0,0
1594076400,1,5,247,51.9,49.4,52,51.9,30.153,30.141,65.4,53.5,65.4,2.75,5,243,0.22916667,91.3,0,0,0,0

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

If I change the code to (#2, #0 and #3 are the values in your code), the 
data is imported okay (except extratemp1). I guess it has something to do 
with my ISS not having ID=1, but ID=2. An my external temp sensor running 
on ID=3

Find attached the resulting csv file

baro_data = weather_data['sensors'][2]['data'] #2
iss_data = weather_data['sensors'][1]['data'] #0
indoor_data = weather_data['sensors'][3]['data'] #3


Op dinsdag 7 juli 2020 om 21:33:57 UTC+2 schreef Bastiaan Meelberg:

> Hi Maarten,
>
> If you want you can give the importer a try:
>
> https://github.com/grebleem/weewx_wl_import
>
> Thanks.
>
>
> On Tuesday, July 7, 2020 at 1:09:34 PM UTC+2, Maarten van der Hoeven wrote:
>>
>> Hi Bastiaan,
>>
>> something I can test?
>>
>> Op zondag 5 juli 2020 14:02:38 UTC+2 schreef flor...@pre-vost.fr:
>>>
>>> Sorry for that. 
>>>
>>> There was a  misunderstandings . Let's forget this conversation;)  
>>>
>>> -fp 
>>>
>>> Le samedi 4 juillet 2020 à 13:36:23 UTC+2, hoev...@gmail.com a écrit :
>>>
 Yes, agree. I like the weather, I like programming, I like to 
 cooperate. It's my current lack of python-knowledge that I want to 
 contribute the best I can do right now, and that is testing both of your 
 drivers. I dont see it as competition, and may the best win. Far from 
 that. 
 In the end, it's my small contribution to the community in testing two 
 drivers, and make them both better working. In hoping that the user pick 
 the driver it feels most comfortably with, or not. 

 Op zaterdag 4 juli 2020 12:52:09 UTC+2 schreef Bastiaan Meelberg:

> I just program what I need, because I like programming.
>  
> Use my program (you all-ready did I see in you're driver ;-), or don't 
> use it. That is the good think of open source. 
>
> Your importer is doing the calculation e.g. Fahrenheit to Celsius I 
> don't like that, weewx is way better in making the conversions. 
> Also I just want to import a date range and not have to figure out my 
> station_id. So I decided to make my own.
>
> But feel free to make a better driver/importer. 
>
>
> On Saturday, July 4, 2020 at 12:38:54 PM UTC+2, Florentin Prevost 
> wrote:
>>
>> Like we work on the same functions for Wll driver. Why not to work 
>> together to developp the driver ? Each one developp the same code and it 
>> would a shame to work 2 times for the same code ...
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/3bbc3def-4867-4f56-9c88-c36bc75a4404n%40googlegroups.com.
ts,usUnits,arch_int,wind_dir_of_prevail,temp_avg,dew_point_last,heat_index_last,wind_chill_last,bar_sea_level,bar_absolute,temp_in_last,dew_point_in,hum_in_last,wind_speed_avg,wind_speed_hi,wind_speed_hi_dir,wind_run,hum_last,rainfall_in,rain_rate_hi_in,solar_rad_avg,uv_index_avg
1594073100,1,5,0,49.9,0,0,0,30.146,30.134,66.3,53.8,64.1,0,0,0,0,0,0,0,0,0
1594073400,1,5,0,49.9,0,0,0,30.147,30.135,66.1,53.6,64,0,0,0,0,0,0,0,0,0
1594073700,1,5,0,49.9,0,0,0,30.148,30.136,66.1,53.7,64.3,0,0,0,0,0,0,0,0,0
1594074000,1,5,0,49.9,0,0,0,30.149,30.137,65.9,53.5,64.2,0,0,0,0,0,0,0,0,0
1594074300,1,5,0,49.8,0,0,0,30.149,30.137,65.7,53.5,64.7,0,0,0,0,0,0,0,0,0
1594074600,1,5,0,49.5,0,0,0,30.147,30.135,65.8,53.6,64.7,0,0,0,0,0,0,0,0,0
1594074900,1,5,0,49.4,0,0,0,30.149,30.137,65.5,53.3,64.7,0,0,0,0,0,0,0,0,0
1594075200,1,5,0,49.4,0,0,0,30.146,30.134,65.5,53.4,64.9,0,0,0,0,0,0,0,0,0
1594075500,1,5,0,49.4,0,0,0,30.152,30.14,65.5,53.4,64.9,0,0,0,0,0,0,0,0,0
1594075800,1,5,0,49.4,0,0,0,30.154,30.142,65.6,53.5,64.9,0,0,0,0,0,0,0,0,0
1594076100,1,5,0,49.4,0,0,0,30.153,30.141,65.4,53.5,65.4,0,0,0,0,0,0,0,0,0
1594076400,1,5,0,49.3,0,0,0,30.153,30.141,65.4,53.5,65.4,0,0,0,0,0,0,0,0,0
1594076700,1,5,0,49.2,0,0,0,30.155,30.143,65.2,53.3,65.3,0,0,0,0,0,0,0,0,0
1594077000,1,5,0,49,0,0,0,30.157,30.145,65.3,53.5,65.6,0,0,0,0,0,0,0,0,0
1594077300,1,5,0,48.8,0,0,0,30.152,30.14,65.2,53.4,65.6,0,0,0,0,0,0,0,0,0
1594077600,1,5,0,48.6,0,0,0,30.155,30.143,65.1,53.3,65.6,0,0,0,0,0,0,0,0,0
1594077900,1,5,0,48.3,0,0,0,30.155,30.143,65.1,53.3,65.6,0,0,0,0,0,0,0,0,0
1594078200,1,5,0,48.3,0,0,0,30.158,30.146,65.3,53.6,65.8,0,0,0,0,0,0,0,0,0
1594078500,1,5,0,48.4,0,0,0,30.156,30.144,65.1,53.4,65.8,0,0,0,0,0,0,0,0,0
1594078800,1,5,0,48.2,0,0,0,30.158,30.146,64.8,53.1,65.8,0,0,0,0,0,0,0,0,0
1594079100,1,5,0,48,0,0,0,30.157,30.145,64.8,53.1,65.8,0,0,0,0,0,0,0,0,0
1594079400,1,5,0,47.8,0,0,0,30.155,30.143,64.7,53,65.8,0,0,0,0,0,0,0,0,0
1594079700,1,5,0,47.5,0,0,0,30.151,30.139,64.8,53.3,66.3,0,0,0,0,0,0,0,0,0
159408,1,5,0,47.2,0,0,0,30.151,30.139,64.6,53.1,66.2,0,0,0,0,0,0,0,0,0

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

Hi,

I've been testing with the driver for a couple of days now, and all data is 
looking fine. I didnt see any strange deviation from the data that comes 
from your driver, and the data that comes from my WeatherLink IP (set up in 
another environment).

So, it look good!


Op dinsdag 7 juli 2020 om 23:07:46 UTC+2 schreef Maarten van der Hoeven:

> Yes, now the csv (although still empty) is created in the 'root'-dir. No 
> need for tmp anymore
>
> maarten@ubuntu:~/weatherlink$ ls -las
> total 36
>  4 drwxrwxr-x  2 maarten maarten  4096 Jul  7 23:06 .
>  4 drwxr-xr-x 24 maarten maarten  4096 Jul  7 21:41 ..
>  0 -rw-rw-r--  1 maarten maarten 0 Jul  7 23:06 davis1594155999.csv
>  8 -rw-r--r--  1 maarten maarten  7282 Jul  7 21:43 davis-csv.conf
>  4 -rw-r--r--  1 maarten maarten  2242 Jul  7 21:31 README.md
> 16 -rw-r--r--  1 maarten maarten 13259 Jul  7 22:53 weewx_weatherlink
>
>
> Op dinsdag 7 juli 2020 om 22:54:33 UTC+2 schreef Bastiaan Meelberg:
>
>> Somehow the tmp/ dir is not created. I dropped the tmp for now. Can you 
>> try again?
>>
>>
>>
>> On Tuesday, July 7, 2020 at 9:57:43 PM UTC+2, Maarten van der Hoeven 
>> wrote:
>>>
>>> Okay, have played with it.
>>>
>>> First I needed to create a tmp-directory. Without it, the csv-file 
>>> cannot be created.
>>> Started the importer to import one single day: 2020-01-01. It creates an 
>>> empty csv-file 
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/b7e9e9e0-7102-4e53-bdae-0204b47def25n%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

Yes, now the csv (although still empty) is created in the 'root'-dir. No 
need for tmp anymore

maarten@ubuntu:~/weatherlink$ ls -las
total 36
 4 drwxrwxr-x  2 maarten maarten  4096 Jul  7 23:06 .
 4 drwxr-xr-x 24 maarten maarten  4096 Jul  7 21:41 ..
 0 -rw-rw-r--  1 maarten maarten 0 Jul  7 23:06 davis1594155999.csv
 8 -rw-r--r--  1 maarten maarten  7282 Jul  7 21:43 davis-csv.conf
 4 -rw-r--r--  1 maarten maarten  2242 Jul  7 21:31 README.md
16 -rw-r--r--  1 maarten maarten 13259 Jul  7 22:53 weewx_weatherlink


Op dinsdag 7 juli 2020 om 22:54:33 UTC+2 schreef Bastiaan Meelberg:

> Somehow the tmp/ dir is not created. I dropped the tmp for now. Can you 
> try again?
>
>
>
> On Tuesday, July 7, 2020 at 9:57:43 PM UTC+2, Maarten van der Hoeven wrote:
>>
>> Okay, have played with it.
>>
>> First I needed to create a tmp-directory. Without it, the csv-file cannot 
>> be created.
>> Started the importer to import one single day: 2020-01-01. It creates an 
>> empty csv-file 
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/182cd6b8-4e6e-4252-a636-49450338889dn%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

Somehow the tmp/ dir is not created. I dropped the tmp for now. Can you try 
again?



On Tuesday, July 7, 2020 at 9:57:43 PM UTC+2, Maarten van der Hoeven wrote:
>
> Okay, have played with it.
>
> First I needed to create a tmp-directory. Without it, the csv-file cannot 
> be created.
> Started the importer to import one single day: 2020-01-01. It creates an 
> empty csv-file 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/bac54855-1b2a-4e68-a75b-eccd96b63c3co%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

Okay, have played with it.

First I needed to create a tmp-directory. Without it, the csv-file cannot 
be created.
Started the importer to import one single day: 2020-01-01. It creates an 
empty csv-file 

maarten@ubuntu:~/weatherlink/tmp$ ls -las
total 8
4 drwxrwxr-x 2 maarten maarten 4096 Jul  7 21:49 .
4 drwxrwxr-x 3 maarten maarten 4096 Jul  7 21:47 ..
0 -rw-rw-r-- 1 maarten maarten0 Jul  7 21:47 davis1594151264.csv
0 -rw-rw-r-- 1 maarten maarten0 Jul  7 21:49 davis1594151341.csv
maarten@ubuntu:~/weatherlink/tmp$ 

with errors

maarten@ubuntu:~/weatherlink$ python3 weewx_weatherlink --date=2020-01-01
Use date: 2020-01-01 00:00:00
1 [1577833200] - [1577919600]: 2020-01-01 00:00:00 - 2020-01-02 00:00:00
Finding stations:

station id: 92884
Name:   Welsumerveld
Country:Netherlands
latitude:   52.310936
longitude:  6.0856133


  -- WARNING! --
 Running WeeWX during a wee_import session can lead to abnormal termination 
of the import. 
 If WeeWX must remain running (e.g., so that live data is not lost) run the 
wee_import session on another machine
 or to a second database and merge the in-use and second database once the 
import is complete.

Is this correct? [y/n] y
Fetching 1577833200 - 1577919600
Fetching 1577833200 - 1577919600
Traceback (most recent call last):
  File "weewx_weatherlink", line 361, in 
main()
  File "weewx_weatherlink", line 340, in main
writer.writerow(wu_data[0].keys())
IndexError: list index out of range

Running a range:
maarten@ubuntu:~/weatherlink$ python3 weewx_weatherlink 
--startdate=2020-01-01 --enddate=2020-01-15
Use dates: 2020-01-01 00:00:00 - 2020-01-15 00:00:00
1 [1577833200.0] - [1577919600.0]: 2020-01-01 00:00:00 - 2020-01-02 00:00:00
2 [1577919600.0] - [1578006000.0]: 2020-01-02 00:00:00 - 2020-01-03 00:00:00
3 [1578006000.0] - [1578092400.0]: 2020-01-03 00:00:00 - 2020-01-04 00:00:00
4 [1578092400.0] - [1578178800.0]: 2020-01-04 00:00:00 - 2020-01-05 00:00:00
5 [1578178800.0] - [1578265200.0]: 2020-01-05 00:00:00 - 2020-01-06 00:00:00
6 [1578265200.0] - [1578351600.0]: 2020-01-06 00:00:00 - 2020-01-07 00:00:00
7 [1578351600.0] - [1578438000.0]: 2020-01-07 00:00:00 - 2020-01-08 00:00:00
8 [1578438000.0] - [1578524400.0]: 2020-01-08 00:00:00 - 2020-01-09 00:00:00
9 [1578524400.0] - [1578610800.0]: 2020-01-09 00:00:00 - 2020-01-10 00:00:00
10 [1578610800.0] - [1578697200.0]: 2020-01-10 00:00:00 - 2020-01-11 
00:00:00
11 [1578697200.0] - [1578783600.0]: 2020-01-11 00:00:00 - 2020-01-12 
00:00:00
12 [1578783600.0] - [157887.0]: 2020-01-12 00:00:00 - 2020-01-13 
00:00:00
13 [157887.0] - [1578956400.0]: 2020-01-13 00:00:00 - 2020-01-14 
00:00:00
14 [1578956400.0] - [1579042800.0]: 2020-01-14 00:00:00 - 2020-01-15 
00:00:00
15 [1579042800.0] - [1579042800]: 2020-01-15 00:00:00 - 2020-01-15 00:00:00
Finding stations:

station id: 92884
Name:   Welsumerveld
Country:Netherlands
latitude:   52.310936
longitude:  6.0856133


  -- WARNING! --
 Running WeeWX during a wee_import session can lead to abnormal termination 
of the import. 
 If WeeWX must remain running (e.g., so that live data is not lost) run the 
wee_import session on another machine
 or to a second database and merge the in-use and second database once the 
import is complete.

Is this correct? [y/n] y
Fetching 1577833200 - 1577919600
Fetching 1577833200 - 1577919600
Fetching 1577919600 - 1578006000
Fetching 1577919600 - 1578006000
Fetching 1578006000 - 1578092400
Fetching 1578006000 - 1578092400
Fetching 1578092400 - 1578178800
Fetching 1578092400 - 1578178800
Fetching 1578178800 - 1578265200
Fetching 1578178800 - 1578265200
Fetching 1578265200 - 1578351600
Fetching 1578265200 - 1578351600
Fetching 1578351600 - 1578438000
Fetching 1578351600 - 1578438000
Fetching 1578438000 - 1578524400
Fetching 1578438000 - 1578524400
Fetching 1578524400 - 1578610800
Fetching 1578524400 - 1578610800
Fetching 1578610800 - 1578697200
Fetching 1578610800 - 1578697200
Fetching 1578697200 - 1578783600
Fetching 1578697200 - 1578783600
Fetching 1578783600 - 157887
Fetching 1578783600 - 157887
Fetching 157887 - 1578956400
Fetching 157887 - 1578956400
Fetching 1578956400 - 1579042800
Fetching 1578956400 - 1579042800
Fetching 1579042800 - 1579042800
Fetching 1579042800 - 1579042800
Traceback (most recent call last):
  File "weewx_weatherlink", line 361, in 
main()
  File "weewx_weatherlink", line 340, in main
writer.writerow(wu_data[0].keys())
IndexError: list index out of range
maarten@ubuntu:~/weatherlink$ 

Creating another empty csv-file

maarten@ubuntu:~/weatherlink/tmp$ ls -las
total 8
4 drwxrwxr-x 2 maarten maarten 4096 Jul  7 21:56 .
4 drwxrwxr-x 3 maarten maarten 4096 Jul  7 21:47 ..
0 -rw-rw-r-- 1 maarten maarten0 Jul  7 21:47 davis1594151264.csv
0 -rw-rw-r-- 1 maarten maarten0 Jul  7 21:49 davis1594151341.csv
0 -rw-rw-r-- 1 maarten maarten0 Jul  7 21:56 davis1594151771.csv
maarten@ubuntu:~/weatherlink/tmp$ 


Op dinsdag 7 juli 2020 om 21:33:57 UTC+2 

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

Hi Maarten,

If you want you can give the importer a try:

https://github.com/grebleem/weewx_wl_import

Thanks.

On Tuesday, July 7, 2020 at 1:09:34 PM UTC+2, Maarten van der Hoeven wrote:
>
> Hi Bastiaan,
>
> something I can test?
>
> Op zondag 5 juli 2020 14:02:38 UTC+2 schreef flor...@pre-vost.fr:
>>
>> Sorry for that. 
>>
>> There was a  misunderstandings . Let's forget this conversation;)  
>>
>> -fp 
>>
>> Le samedi 4 juillet 2020 à 13:36:23 UTC+2, hoev...@gmail.com a écrit :
>>
>>> Yes, agree. I like the weather, I like programming, I like to cooperate. 
>>> It's my current lack of python-knowledge that I want to contribute the best 
>>> I can do right now, and that is testing both of your drivers. I dont see it 
>>> as competition, and may the best win. Far from that. In the end, it's my 
>>> small contribution to the community in testing two drivers, and make them 
>>> both better working. In hoping that the user pick the driver it feels most 
>>> comfortably with, or not. 
>>>
>>> Op zaterdag 4 juli 2020 12:52:09 UTC+2 schreef Bastiaan Meelberg:
>>>
 I just program what I need, because I like programming.
  
 Use my program (you all-ready did I see in you're driver ;-), or don't 
 use it. That is the good think of open source. 

 Your importer is doing the calculation e.g. Fahrenheit to Celsius I 
 don't like that, weewx is way better in making the conversions. 
 Also I just want to import a date range and not have to figure out my 
 station_id. So I decided to make my own.

 But feel free to make a better driver/importer. 


 On Saturday, July 4, 2020 at 12:38:54 PM UTC+2, Florentin Prevost wrote:
>
> Like we work on the same functions for Wll driver. Why not to work 
> together to developp the driver ? Each one developp the same code and it 
> would a shame to work 2 times for the same code ...



-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/aff52eb0-bb75-438d-b421-c9db552fb65ao%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

Hi Bastiaan,

something I can test?

Op zondag 5 juli 2020 14:02:38 UTC+2 schreef flor...@pre-vost.fr:
>
> Sorry for that. 
>
> There was a  misunderstandings . Let's forget this conversation;)  
>
> -fp 
>
> Le samedi 4 juillet 2020 à 13:36:23 UTC+2, hoev...@gmail.com a écrit :
>
>> Yes, agree. I like the weather, I like programming, I like to cooperate. 
>> It's my current lack of python-knowledge that I want to contribute the best 
>> I can do right now, and that is testing both of your drivers. I dont see it 
>> as competition, and may the best win. Far from that. In the end, it's my 
>> small contribution to the community in testing two drivers, and make them 
>> both better working. In hoping that the user pick the driver it feels most 
>> comfortably with, or not. 
>>
>> Op zaterdag 4 juli 2020 12:52:09 UTC+2 schreef Bastiaan Meelberg:
>>
>>> I just program what I need, because I like programming.
>>>  
>>> Use my program (you all-ready did I see in you're driver ;-), or don't 
>>> use it. That is the good think of open source. 
>>>
>>> Your importer is doing the calculation e.g. Fahrenheit to Celsius I 
>>> don't like that, weewx is way better in making the conversions. 
>>> Also I just want to import a date range and not have to figure out my 
>>> station_id. So I decided to make my own.
>>>
>>> But feel free to make a better driver/importer. 
>>>
>>>
>>> On Saturday, July 4, 2020 at 12:38:54 PM UTC+2, Florentin Prevost wrote:

 Like we work on the same functions for Wll driver. Why not to work 
 together to developp the driver ? Each one developp the same code and it 
 would a shame to work 2 times for the same code ...
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/1732442d-eefa-48ee-9ced-6e833a9fe92co%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[flor...@pre-vost.fr]

Sorry for that. 

There was a  misunderstandings . Let's forget this conversation;)  

-fp 

Le samedi 4 juillet 2020 à 13:36:23 UTC+2, hoev...@gmail.com a écrit :

> Yes, agree. I like the weather, I like programming, I like to cooperate. 
> It's my current lack of python-knowledge that I want to contribute the best 
> I can do right now, and that is testing both of your drivers. I dont see it 
> as competition, and may the best win. Far from that. In the end, it's my 
> small contribution to the community in testing two drivers, and make them 
> both better working. In hoping that the user pick the driver it feels most 
> comfortably with, or not. 
>
> Op zaterdag 4 juli 2020 12:52:09 UTC+2 schreef Bastiaan Meelberg:
>
>> I just program what I need, because I like programming.
>>  
>> Use my program (you all-ready did I see in you're driver ;-), or don't 
>> use it. That is the good think of open source. 
>>
>> Your importer is doing the calculation e.g. Fahrenheit to Celsius I don't 
>> like that, weewx is way better in making the conversions. 
>> Also I just want to import a date range and not have to figure out my 
>> station_id. So I decided to make my own.
>>
>> But feel free to make a better driver/importer. 
>>
>>
>> On Saturday, July 4, 2020 at 12:38:54 PM UTC+2, Florentin Prevost wrote:
>>>
>>> Like we work on the same functions for Wll driver. Why not to work 
>>> together to developp the driver ? Each one developp the same code and it 
>>> would a shame to work 2 times for the same code ...
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/f9c8bf4d-76da-4a3d-9903-6a88b51c629en%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

Yes, agree. I like the weather, I like programming, I like to cooperate. 
It's my current lack of python-knowledge that I want to contribute the best 
I can do right now, and that is testing both of your drivers. I dont see it 
as competition, and may the best win. Far from that. In the end, it's my 
small contribution to the community in testing two drivers, and make them 
both better working. In hoping that the user pick the driver it feels most 
comfortably with, or not. 

Op zaterdag 4 juli 2020 12:52:09 UTC+2 schreef Bastiaan Meelberg:
>
> I just program what I need, because I like programming.
>  
> Use my program (you all-ready did I see in you're driver ;-), or don't use 
> it. That is the good think of open source. 
>
> Your importer is doing the calculation e.g. Fahrenheit to Celsius I don't 
> like that, weewx is way better in making the conversions. 
> Also I just want to import a date range and not have to figure out my 
> station_id. So I decided to make my own.
>
> But feel free to make a better driver/importer. 
>
>
> On Saturday, July 4, 2020 at 12:38:54 PM UTC+2, Florentin Prevost wrote:
>>
>> Like we work on the same functions for Wll driver. Why not to work 
>> together to developp the driver ? Each one developp the same code and it 
>> would a shame to work 2 times for the same code ...
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/6646604a-c00b-4af7-bd21-86e79f85f1eao%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Florentin Prevost]

It just a proposition.

Also, I mentionned you in credits.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/090a6b38-eb4e-4bcf-9068-f3b49244923co%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

I just program what I need, because I like programming.
 
Use my program (you all-ready did I see in you're driver ;-), or don't use 
it. That is the good think of open source. 

Your importer is doing the calculation e.g. Fahrenheit to Celsius I don't 
like that, weewx is way better in making the conversions. 
Also I just want to import a date range and not have to figure out my 
station_id. So I decided to make my own.

But feel free to make a better driver/importer. 


On Saturday, July 4, 2020 at 12:38:54 PM UTC+2, Florentin Prevost wrote:
>
> Like we work on the same functions for Wll driver. Why not to work 
> together to developp the driver ? Each one developp the same code and it 
> would a shame to work 2 times for the same code ...

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/d961df85-5d4d-421f-85cf-8634364b9e51o%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Florentin Prevost]

Like we work on the same functions for Wll driver. Why not to work together to 
developp the driver ? Each one developp the same code and it would a shame to 
work 2 times for the same code ...

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/02392c02-a913-49c8-a075-c67fd217236fo%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

What do you mean?


On Saturday, July 4, 2020 at 12:30:23 PM UTC+2, Florentin Prevost wrote:
>
> Why do you copy idea ?
> I'm glad to work together for the wll driver but it seems that you work to 
> same fonctions...

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/dd1aaf50-e4c1-4d9e-a62c-a15e3a2e8f32o%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Florentin Prevost]

Why do you copy idea ?
I'm glad to work together for the wll driver but it seems that you work to same 
fonctions...

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/df2b72b0-b73c-4168-908f-519d3b712ae1o%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

Good to hear about the import! Just finished the import of old archived 
data into my weatherlink-account this week, going back to August 2012. So 
have a nice set of testdata :)

Op zaterdag 4 juli 2020 om 12:27:28 UTC+2 schreef Bastiaan Meelberg:

> Good to hear! I all-ready had some rain and it looks good. Thank you for 
> testing.
>
> The WeatherLink v2 API  weewx-import 
> will 
> go live tonight or tomorrow, so you can import large periods from 
> WeatherLink to weewx.
>
>
> On Saturday, July 4, 2020 at 11:56:25 AM UTC+2, Maarten van der Hoeven 
> wrote:
>>
>> I did run the driver for a couple of days now, all data seems okay to me. 
>> Today it is said it's going to rain, so going to test that data as well 
>> today.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/095a0ca8-a25a-4a69-b6e2-5e57c01ae288n%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

I did run the driver for a couple of days now, all data seems okay to me. 
Today it is said it's going to rain, so going to test that data as well 
today.

Op donderdag 2 juli 2020 om 19:38:42 UTC+2 schreef Maarten van der Hoeven:

> Yes, okay now (two top records). It gave me also the opportunity to iron 
> out a bug in my own weewx-service. Hadnt caught the situation that rain 
> might be NULL :)
>
> mysql> select datetime,from_unixtime(datetime),outtemp,extratemp1,rain,ET 
> from archive order by datetime desc limit 10;
>
> ++-+++--+---+
> | datetime   | from_unixtime(datetime) | outtemp| 
> extratemp1 | rain | ET|
>
> ++-+++--+---+
> | 1593711420 | 2020-07-02 19:37:00 | 18.914 |  
> 19.47 |0 |  0.003361470627628734 |
> | 1593711360 | 2020-07-02 19:36:00 |  18.89 | 
> 19.393 |0 | 0.0034129711072366695 |
> | 1593711060 | 2020-07-02 19:31:00 |  18.78 | 
> 19.057 | NULL |  0.003440203244074394 |
> | 1593711000 | 2020-07-02 19:30:00 |  18.78 | 
> 18.9305554 | NULL | 0.0034680891688093356 |
> | 1593710940 | 2020-07-02 19:29:00 |  18.72 |  
> 18.89 | NULL |  NULL |
> | 1593695820 | 2020-07-02 15:17:00 |  19.61 | 
> 20.370370370370367 | NULL | 0.0031779497530594037 |
> | 1593695760 | 2020-07-02 15:16:00 |  19.61 | 
> 20.443 | NULL |  0.003190712625375343 |
> | 1593695700 | 2020-07-02 15:15:00 | 19.557 | 
> 20.443 | NULL |  0.003232360174501971 |
> | 1593695640 | 2020-07-02 15:14:00 | 19.557 | 
> 20.443 | NULL | 0.0032646454867943896 |
> | 1593695580 | 2020-07-02 15:13:00 | 19.557 | 
> 20.443 | NULL |  0.003283176153447136 |
>
> ++-+++--+---+
>
> 10 rows in set (0.00 sec)
>
>
> Op donderdag 2 juli 2020 15:06:20 UTC+2 schreef Bastiaan Meelberg:
>
>> Sorry about that. I was surprised as well. I accidentally comment out the 
>> rain to get in the Loop, during debugging.
>>
>> It should be good in the current master build:
>>
>> https://github.com/grebleem/weewx-weatherlinkliveudp/archive/master.zip
>>
>>
>> I'm also working on a weatherlink import, at this moment the program will 
>> produce a .cvs and wee_import can import this file. Keep you posted!
>>
>>
>> On Thursday, July 2, 2020 at 2:50:13 PM UTC+2, Maarten van der Hoeven 
>> wrote:
>>>
>>> A question. Is 'rain' still work in progress? I notice a repeating 
>>> NULL-value (no worries, testing against a test-database within a virtual 
>>> machine. fully seperated from my 'production'-site)
>>>
>>> mysql> select 
>>> datetime,from_unixtime(datetime),outtemp,extratemp1,rain,ET from archive 
>>> order by datetime desc limit 10;
>>>
>>> ++-+++--+---+
>>> | datetime   | from_unixtime(datetime) | outtemp| 
>>> extratemp1 | rain | ET|
>>>
>>> ++-+++--+---+
>>> | 1593693840 | 2020-07-02 14:44:00 | 20 |  
>>> 21.64814814814815 | NULL |  0.004293896657547285 |
>>> | 1593693780 | 2020-07-02 14:43:00 | 20 | 
>>> 21.832 | NULL |  0.004304368552713827 |
>>> | 1593693720 | 2020-07-02 14:42:00 | 20 | 
>>> 21.832 | NULL |  0.004311294113859122 |
>>> | 1593693660 | 2020-07-02 14:41:00 | 20 | 
>>> 21.832 | NULL |  0.004316451537816886 |
>>> | 1593693600 | 2020-07-02 14:40:00 | 20.0416664 | 
>>> 21.9305554 | NULL |  0.004321999760490444 |
>>> | 1593693540 | 2020-07-02 14:39:00 | 20.054 | 
>>> 22.074074074074073 | NULL |  0.004325689825000265 |
>>> | 1593693480 | 2020-07-02 14:38:00 | 20.082 | 
>>> 22.164 | NULL |  0.004326424995698886 |
>>> | 1593693300 | 2020-07-02 14:35:00 |  20.09259259259259 | 
>>> 22.275 | NULL | 0.0042999357683097044 |
>>> | 1593693240 | 2020-07-02 14:34:00 |  20.11 |   
>>> 22.2037037037037 | NULL |   0.00429406704665147 |
>>> | 1593693180 | 2020-07-02 14:33:00 |  20.12962962962963 |  
>>> 22.11 | NULL |  0.004320916570420523 |
>>>
>>> ++-+++--+---+
>>> 10 rows in set (0.01 sec)
>>>
>>>
>>> Op donderdag 2 juli 2020 om 13:44:43 UTC+2 schreef Maarten van der 
>>> Hoeven:
>>>
 

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

Yes, okay now (two top records). It gave me also the opportunity to iron 
out a bug in my own weewx-service. Hadnt caught the situation that rain 
might be NULL :)

mysql> select datetime,from_unixtime(datetime),outtemp,extratemp1,rain,ET 
from archive order by datetime desc limit 10;
++-+++--+---+
| datetime   | from_unixtime(datetime) | outtemp| 
extratemp1 | rain | ET|
++-+++--+---+
| 1593711420 | 2020-07-02 19:37:00 | 18.914 |  
19.47 |0 |  0.003361470627628734 |
| 1593711360 | 2020-07-02 19:36:00 |  18.89 | 
19.393 |0 | 0.0034129711072366695 |
| 1593711060 | 2020-07-02 19:31:00 |  18.78 | 
19.057 | NULL |  0.003440203244074394 |
| 1593711000 | 2020-07-02 19:30:00 |  18.78 | 
18.9305554 | NULL | 0.0034680891688093356 |
| 1593710940 | 2020-07-02 19:29:00 |  18.72 |  
18.89 | NULL |  NULL |
| 1593695820 | 2020-07-02 15:17:00 |  19.61 | 
20.370370370370367 | NULL | 0.0031779497530594037 |
| 1593695760 | 2020-07-02 15:16:00 |  19.61 | 
20.443 | NULL |  0.003190712625375343 |
| 1593695700 | 2020-07-02 15:15:00 | 19.557 | 
20.443 | NULL |  0.003232360174501971 |
| 1593695640 | 2020-07-02 15:14:00 | 19.557 | 
20.443 | NULL | 0.0032646454867943896 |
| 1593695580 | 2020-07-02 15:13:00 | 19.557 | 
20.443 | NULL |  0.003283176153447136 |
++-+++--+---+
10 rows in set (0.00 sec)


Op donderdag 2 juli 2020 15:06:20 UTC+2 schreef Bastiaan Meelberg:
>
> Sorry about that. I was surprised as well. I accidentally comment out the 
> rain to get in the Loop, during debugging.
>
> It should be good in the current master build:
>
> https://github.com/grebleem/weewx-weatherlinkliveudp/archive/master.zip
>
>
> I'm also working on a weatherlink import, at this moment the program will 
> produce a .cvs and wee_import can import this file. Keep you posted!
>
>
> On Thursday, July 2, 2020 at 2:50:13 PM UTC+2, Maarten van der Hoeven 
> wrote:
>>
>> A question. Is 'rain' still work in progress? I notice a repeating 
>> NULL-value (no worries, testing against a test-database within a virtual 
>> machine. fully seperated from my 'production'-site)
>>
>> mysql> select datetime,from_unixtime(datetime),outtemp,extratemp1,rain,ET 
>> from archive order by datetime desc limit 10;
>>
>> ++-+++--+---+
>> | datetime   | from_unixtime(datetime) | outtemp| 
>> extratemp1 | rain | ET|
>>
>> ++-+++--+---+
>> | 1593693840 | 2020-07-02 14:44:00 | 20 |  
>> 21.64814814814815 | NULL |  0.004293896657547285 |
>> | 1593693780 | 2020-07-02 14:43:00 | 20 | 
>> 21.832 | NULL |  0.004304368552713827 |
>> | 1593693720 | 2020-07-02 14:42:00 | 20 | 
>> 21.832 | NULL |  0.004311294113859122 |
>> | 1593693660 | 2020-07-02 14:41:00 | 20 | 
>> 21.832 | NULL |  0.004316451537816886 |
>> | 1593693600 | 2020-07-02 14:40:00 | 20.0416664 | 
>> 21.9305554 | NULL |  0.004321999760490444 |
>> | 1593693540 | 2020-07-02 14:39:00 | 20.054 | 
>> 22.074074074074073 | NULL |  0.004325689825000265 |
>> | 1593693480 | 2020-07-02 14:38:00 | 20.082 | 
>> 22.164 | NULL |  0.004326424995698886 |
>> | 1593693300 | 2020-07-02 14:35:00 |  20.09259259259259 | 
>> 22.275 | NULL | 0.0042999357683097044 |
>> | 1593693240 | 2020-07-02 14:34:00 |  20.11 |   
>> 22.2037037037037 | NULL |   0.00429406704665147 |
>> | 1593693180 | 2020-07-02 14:33:00 |  20.12962962962963 |  
>> 22.11 | NULL |  0.004320916570420523 |
>>
>> ++-+++--+---+
>> 10 rows in set (0.01 sec)
>>
>>
>> Op donderdag 2 juli 2020 om 13:44:43 UTC+2 schreef Maarten van der Hoeven:
>>
>>> Yes, that makes a difference! Also showing okay on the website!
>>>
>>> mysql> select 
>>> datetime,from_unixtime(datetime),outtemp,extratemp1,extratemp2,extratemp3 
>>> from archive order by datetime desc limit 10;
>>>
>>> ++-+++++
>>>
>>> | datetime   | 

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

Sorry about that. I was surprised as well. I accidentally comment out the 
rain to get in the Loop, during debugging.

It should be good in the current master build:

https://github.com/grebleem/weewx-weatherlinkliveudp/archive/master.zip


I'm also working on a weatherlink import, at this moment the program will 
produce a .cvs and wee_import can import this file. Keep you posted!


On Thursday, July 2, 2020 at 2:50:13 PM UTC+2, Maarten van der Hoeven wrote:
>
> A question. Is 'rain' still work in progress? I notice a repeating 
> NULL-value (no worries, testing against a test-database within a virtual 
> machine. fully seperated from my 'production'-site)
>
> mysql> select datetime,from_unixtime(datetime),outtemp,extratemp1,rain,ET 
> from archive order by datetime desc limit 10;
>
> ++-+++--+---+
> | datetime   | from_unixtime(datetime) | outtemp| 
> extratemp1 | rain | ET|
>
> ++-+++--+---+
> | 1593693840 | 2020-07-02 14:44:00 | 20 |  
> 21.64814814814815 | NULL |  0.004293896657547285 |
> | 1593693780 | 2020-07-02 14:43:00 | 20 | 
> 21.832 | NULL |  0.004304368552713827 |
> | 1593693720 | 2020-07-02 14:42:00 | 20 | 
> 21.832 | NULL |  0.004311294113859122 |
> | 1593693660 | 2020-07-02 14:41:00 | 20 | 
> 21.832 | NULL |  0.004316451537816886 |
> | 1593693600 | 2020-07-02 14:40:00 | 20.0416664 | 
> 21.9305554 | NULL |  0.004321999760490444 |
> | 1593693540 | 2020-07-02 14:39:00 | 20.054 | 
> 22.074074074074073 | NULL |  0.004325689825000265 |
> | 1593693480 | 2020-07-02 14:38:00 | 20.082 | 
> 22.164 | NULL |  0.004326424995698886 |
> | 1593693300 | 2020-07-02 14:35:00 |  20.09259259259259 | 
> 22.275 | NULL | 0.0042999357683097044 |
> | 1593693240 | 2020-07-02 14:34:00 |  20.11 |   
> 22.2037037037037 | NULL |   0.00429406704665147 |
> | 1593693180 | 2020-07-02 14:33:00 |  20.12962962962963 |  
> 22.11 | NULL |  0.004320916570420523 |
>
> ++-+++--+---+
> 10 rows in set (0.01 sec)
>
>
> Op donderdag 2 juli 2020 om 13:44:43 UTC+2 schreef Maarten van der Hoeven:
>
>> Yes, that makes a difference! Also showing okay on the website!
>>
>> mysql> select 
>> datetime,from_unixtime(datetime),outtemp,extratemp1,extratemp2,extratemp3 
>> from archive order by datetime desc limit 10;
>>
>> ++-+++++
>>
>> | datetime   | from_unixtime(datetime) | outtemp| 
>> extratemp1 | extratemp2 | extratemp3 |
>>
>> ++-+++++
>> | 1593690180 | 2020-07-02 13:43:00 | 19.443 |  
>> 20.24074074074074 |   NULL |   NULL |
>> | 1593690120 | 2020-07-02 13:42:00 | 19.393 |  
>> 20.12962962962963 |   NULL |   NULL |
>> | 1593690060 | 2020-07-02 13:41:00 |  19.347222 | 
>> 19.918 |   NULL |   NULL |
>> | 159369 | 2020-07-02 13:40:00 | 19.332 | 
>> 19.832 |   NULL |   NULL |
>> | 1593689940 | 2020-07-02 13:39:00 | 19.332 | 
>> 19.740740740740737 |   NULL |   NULL |
>> | 1593689820 | 2020-07-02 13:37:00 | 19.332 
>> |   NULL |   NULL |   NULL |
>> | 1593689760 | 2020-07-02 13:36:00 | 19.332 
>> |   NULL |   NULL |   NULL |
>> | 1593689700 | 2020-07-02 13:35:00 | 19.332 
>> |   NULL |   NULL |   NULL |
>> | 1593676680 | 2020-07-02 09:58:00 |  16.72 
>> |   NULL |   NULL |   NULL |
>> | 1593676620 | 2020-07-02 09:57:00 |  16.72 
>> |   NULL |   NULL |   NULL |
>>
>> ++-+++++
>>
>> 10 rows in set (0.00 sec)
>>
>>
>>
>> Op donderdag 2 juli 2020 om 12:10:15 UTC+2 schreef Bastiaan Meelberg:
>>
>>> Very helpful! 
>>> Just found out that the extra_id from the .conf file is a str type. 
>>> Comparing this to an int will never match. 
>>> Try this build please:
>>> https://github.com/grebleem/weewx-weatherlinkliveudp/archive/Debug1.zip
>>>
>>>
>>> On Thursday, July 2, 2020 at 9:57:25 AM UTC+2, Maarten van der Hoeven 
>>> wrote:

 No data in whatever extratemp. I got the external sensor on channel id 
 = 3 (hence extra_id=3), but I suspect the data 

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

A question. Is 'rain' still work in progress? I notice a repeating 
NULL-value (no worries, testing against a test-database within a virtual 
machine. fully seperated from my 'production'-site)

mysql> select datetime,from_unixtime(datetime),outtemp,extratemp1,rain,ET 
from archive order by datetime desc limit 10;
++-+++--+---+
| datetime   | from_unixtime(datetime) | outtemp| 
extratemp1 | rain | ET|
++-+++--+---+
| 1593693840 | 2020-07-02 14:44:00 | 20 |  
21.64814814814815 | NULL |  0.004293896657547285 |
| 1593693780 | 2020-07-02 14:43:00 | 20 | 
21.832 | NULL |  0.004304368552713827 |
| 1593693720 | 2020-07-02 14:42:00 | 20 | 
21.832 | NULL |  0.004311294113859122 |
| 1593693660 | 2020-07-02 14:41:00 | 20 | 
21.832 | NULL |  0.004316451537816886 |
| 1593693600 | 2020-07-02 14:40:00 | 20.0416664 | 
21.9305554 | NULL |  0.004321999760490444 |
| 1593693540 | 2020-07-02 14:39:00 | 20.054 | 
22.074074074074073 | NULL |  0.004325689825000265 |
| 1593693480 | 2020-07-02 14:38:00 | 20.082 | 
22.164 | NULL |  0.004326424995698886 |
| 1593693300 | 2020-07-02 14:35:00 |  20.09259259259259 | 
22.275 | NULL | 0.0042999357683097044 |
| 1593693240 | 2020-07-02 14:34:00 |  20.11 |   
22.2037037037037 | NULL |   0.00429406704665147 |
| 1593693180 | 2020-07-02 14:33:00 |  20.12962962962963 |  
22.11 | NULL |  0.004320916570420523 |
++-+++--+---+
10 rows in set (0.01 sec)


Op donderdag 2 juli 2020 om 13:44:43 UTC+2 schreef Maarten van der Hoeven:

> Yes, that makes a difference! Also showing okay on the website!
>
> mysql> select 
> datetime,from_unixtime(datetime),outtemp,extratemp1,extratemp2,extratemp3 
> from archive order by datetime desc limit 10;
>
> ++-+++++
>
> | datetime   | from_unixtime(datetime) | outtemp| 
> extratemp1 | extratemp2 | extratemp3 |
>
> ++-+++++
> | 1593690180 | 2020-07-02 13:43:00 | 19.443 |  
> 20.24074074074074 |   NULL |   NULL |
> | 1593690120 | 2020-07-02 13:42:00 | 19.393 |  
> 20.12962962962963 |   NULL |   NULL |
> | 1593690060 | 2020-07-02 13:41:00 |  19.347222 | 
> 19.918 |   NULL |   NULL |
> | 159369 | 2020-07-02 13:40:00 | 19.332 | 
> 19.832 |   NULL |   NULL |
> | 1593689940 | 2020-07-02 13:39:00 | 19.332 | 
> 19.740740740740737 |   NULL |   NULL |
> | 1593689820 | 2020-07-02 13:37:00 | 19.332 
> |   NULL |   NULL |   NULL |
> | 1593689760 | 2020-07-02 13:36:00 | 19.332 
> |   NULL |   NULL |   NULL |
> | 1593689700 | 2020-07-02 13:35:00 | 19.332 
> |   NULL |   NULL |   NULL |
> | 1593676680 | 2020-07-02 09:58:00 |  16.72 
> |   NULL |   NULL |   NULL |
> | 1593676620 | 2020-07-02 09:57:00 |  16.72 
> |   NULL |   NULL |   NULL |
>
> ++-+++++
>
> 10 rows in set (0.00 sec)
>
>
>
> Op donderdag 2 juli 2020 om 12:10:15 UTC+2 schreef Bastiaan Meelberg:
>
>> Very helpful! 
>> Just found out that the extra_id from the .conf file is a str type. 
>> Comparing this to an int will never match. 
>> Try this build please:
>> https://github.com/grebleem/weewx-weatherlinkliveudp/archive/Debug1.zip
>>
>>
>> On Thursday, July 2, 2020 at 9:57:25 AM UTC+2, Maarten van der Hoeven 
>> wrote:
>>>
>>> No data in whatever extratemp. I got the external sensor on channel id = 
>>> 3 (hence extra_id=3), but I suspect the data comes into extratemp1. I d not 
>>> have any preference on that. Mysql-output, and three json files of current 
>>> conditions
>>>
>>>


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/3e644104-c496-4caf-b777-9dc060b162ebn%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

Yes, that makes a difference! Also showing okay on the website!

mysql> select 
datetime,from_unixtime(datetime),outtemp,extratemp1,extratemp2,extratemp3 
from archive order by datetime desc limit 10;
++-+++++
| datetime   | from_unixtime(datetime) | outtemp| 
extratemp1 | extratemp2 | extratemp3 |
++-+++++
| 1593690180 | 2020-07-02 13:43:00 | 19.443 |  
20.24074074074074 |   NULL |   NULL |
| 1593690120 | 2020-07-02 13:42:00 | 19.393 |  
20.12962962962963 |   NULL |   NULL |
| 1593690060 | 2020-07-02 13:41:00 |  19.347222 | 
19.918 |   NULL |   NULL |
| 159369 | 2020-07-02 13:40:00 | 19.332 | 
19.832 |   NULL |   NULL |
| 1593689940 | 2020-07-02 13:39:00 | 19.332 | 
19.740740740740737 |   NULL |   NULL |
| 1593689820 | 2020-07-02 13:37:00 | 19.332 |   
NULL |   NULL |   NULL |
| 1593689760 | 2020-07-02 13:36:00 | 19.332 |   
NULL |   NULL |   NULL |
| 1593689700 | 2020-07-02 13:35:00 | 19.332 |   
NULL |   NULL |   NULL |
| 1593676680 | 2020-07-02 09:58:00 |  16.72 |   
NULL |   NULL |   NULL |
| 1593676620 | 2020-07-02 09:57:00 |  16.72 |   
NULL |   NULL |   NULL |
++-+++++
10 rows in set (0.00 sec)


Op donderdag 2 juli 2020 om 12:10:15 UTC+2 schreef Bastiaan Meelberg:

> Very helpful! 
> Just found out that the extra_id from the .conf file is a str type. 
> Comparing this to an int will never match. 
> Try this build please:
> https://github.com/grebleem/weewx-weatherlinkliveudp/archive/Debug1.zip
>
>
> On Thursday, July 2, 2020 at 9:57:25 AM UTC+2, Maarten van der Hoeven 
> wrote:
>>
>> No data in whatever extratemp. I got the external sensor on channel id = 
>> 3 (hence extra_id=3), but I suspect the data comes into extratemp1. I d not 
>> have any preference on that. Mysql-output, and three json files of current 
>> conditions
>>
>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/9af83a21-7338-4bbe-8b1a-a0ed3c7a4e9bn%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

Very helpful! 
Just found out that the extra_id from the .conf file is a str type. 
Comparing this to an int will never match. 
Try this build please:
https://github.com/grebleem/weewx-weatherlinkliveudp/archive/Debug1.zip


On Thursday, July 2, 2020 at 9:57:25 AM UTC+2, Maarten van der Hoeven wrote:
>
> No data in whatever extratemp. I got the external sensor on channel id = 3 
> (hence extra_id=3), but I suspect the data comes into extratemp1. I d not 
> have any preference on that. Mysql-output, and three json files of current 
> conditions
>
>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/a63ab09e-38c8-40c7-ad2a-30412503325ao%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

That is strange, it is setup now to LOOP as extraTemp1. If you want it as 
nr 3 that can be made modular as well. Can you save a few 
'current_conditions' JSON files (not copy paste). I can load them up in the 
debugger, see what goes wrong.


On Wednesday, July 1, 2020 at 9:40:31 PM UTC+2, Maarten van der Hoeven 
wrote:
>
> Copied the development-driver on the right place, and added extra_id =3 to 
> the driver-config in weewx.conf
>
> I ran weewxd from the prompt; I do not see any extratemp3 passing by. 
>
> root@ubuntu:/home/maarten/Downloads# /usr/bin/weewxd 
> LOOP:   2020-07-01 21:35:49 CEST (1593632149) altimeter: 
> 1006.8298368803157, appTemp: 17.28481418176042, barometer: 
> 1007.1457023136227, beaufort: 1, cloudbase: 621.1850988795652, dateTime: 
> 1593632149, dewpoint: 12.612, heatindex: 17.72, 
> humidex: 20.314658361183554, inDewpoint: 14.445, inHumidity: 
> 45.2, inTemp: 27.332, maxSolarRad: None, outHumidity: 72.1, 
> outTemp: 17.72, pressure: 1006.7393357345647, radiation: 16, 
> rainRate: 0.0, signal1: 0, txBatteryStatus: 0, usUnits: 17, UV: 0.0, 
> windchill: 17.72, windDir: 258, windGust: 3.57632, windGustDir: 
> 260, windSpeed: 1.78816
> LOOP:   2020-07-01 21:35:49 CEST (1593632149) beaufort: 1, dateTime: 
> 1593632149, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 258, 
> windGust: 3.57632, windGustDir: 260, windSpeed: 1.78816
> LOOP:   2020-07-01 21:35:52 CEST (1593632152) beaufort: 2, dateTime: 
> 1593632152, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 254, 
> windGust: 3.57632, windGustDir: 260, windSpeed: 2.2352
> LOOP:   2020-07-01 21:35:54 CEST (1593632154) beaufort: 1, dateTime: 
> 1593632154, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 250, 
> windGust: 3.57632, windGustDir: 260, windSpeed: 1.78816
> LOOP:   2020-07-01 21:35:57 CEST (1593632157) beaufort: 1, dateTime: 
> 1593632157, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 250, 
> windGust: 3.57632, windGustDir: 260, windSpeed: 1.34112
> LOOP:   2020-07-01 21:35:59 CEST (1593632159) beaufort: 1, dateTime: 
> 1593632159, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 250, 
> windGust: 3.57632, windGustDir: 260, windSpeed: 1.34112
> LOOP:   2020-07-01 21:36:02 CEST (1593632162) beaufort: 1, dateTime: 
> 1593632162, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 255, 
> windGust: 3.57632, windGustDir: 252, windSpeed: 1.34112
> LOOP:   2020-07-01 21:36:04 CEST (1593632164) beaufort: 1, dateTime: 
> 1593632164, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 259, 
> windGust: 3.57632, windGustDir: 252, windSpeed: 1.78816
> LOOP:   2020-07-01 21:36:07 CEST (1593632167) beaufort: 2, dateTime: 
> 1593632167, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 267, 
> windGust: 3.57632, windGustDir: 252, windSpeed: 2.68224
> LOOP:   2020-07-01 21:36:09 CEST (1593632169) beaufort: 1, dateTime: 
> 1593632169, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 256, 
> windGust: 3.57632, windGustDir: 252, windSpeed: 1.78816
> LOOP:   2020-07-01 21:36:09 CEST (1593632169) altimeter: 
> 1006.7959690570649, appTemp: 17.28481418176042, barometer: 
> 1007.1118384320345, beaufort: 1, cloudbase: 621.1850988795652, dateTime: 
> 1593632169, dewpoint: 12.612, heatindex: 17.72, 
> humidex: 20.314658361183554, inDewpoint: 14.445, inHumidity: 
> 45.2, inTemp: 27.332, maxSolarRad: None, outHumidity: 72.1, 
> outTemp: 17.72, pressure: 1006.7054718529766, radiation: 16, 
> rainRate: 0.0, signal1: 0, txBatteryStatus: 0, usUnits: 17, UV: 0.0, 
> windchill: 17.72, windDir: 256, windGust: 3.57632, windGustDir: 
> 260, windSpeed: 1.78816
> LOOP:   2020-07-01 21:36:12 CEST (1593632172) beaufort: 1, dateTime: 
> 1593632172, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 258, 
> windGust: 3.57632, windGustDir: 252, windSpeed: 1.78816
> LOOP:   2020-07-01 21:36:14 CEST (1593632174) beaufort: 2, dateTime: 
> 1593632174, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 265, 
> windGust: 3.57632, windGustDir: 252, windSpeed: 3.12928
> LOOP:   2020-07-01 21:36:17 CEST (1593632177) beaufort: 2, dateTime: 
> 1593632177, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 265, 
> windGust: 3.57632, windGustDir: 252, windSpeed: 3.12928
> REC:2020-07-01 21:36:00 CEST (1593632160) altimeter: 
> 1006.8298368803157, appTemp: 17.28481418176042, barometer: 
> 1007.1457023136227, beaufort: 1.1667, cloudbase: 
> 621.1850988795652, dateTime: 1593632160, dewpoint: 12.612, ET: 
> 0.0011517070455688023, heatindex: 17.72, humidex: 
> 20.314658361183554, inDewpoint: 14.445, inHumidity: 45.2, 
> inTemp: 27.332, interval: 1.0, maxSolarRad: None, outHumidity: 
> 72.1, outTemp: 17.72, pressure: 1006.7393357345647, radiation: 
> 16.0, rainRate: 0.0, signal1: 0.0, 

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

Copied the development-driver on the right place, and added extra_id =3 to 
the driver-config in weewx.conf

I ran weewxd from the prompt; I do not see any extratemp3 passing by. 

root@ubuntu:/home/maarten/Downloads# /usr/bin/weewxd 
LOOP:   2020-07-01 21:35:49 CEST (1593632149) altimeter: 
1006.8298368803157, appTemp: 17.28481418176042, barometer: 
1007.1457023136227, beaufort: 1, cloudbase: 621.1850988795652, dateTime: 
1593632149, dewpoint: 12.612, heatindex: 17.72, 
humidex: 20.314658361183554, inDewpoint: 14.445, inHumidity: 
45.2, inTemp: 27.332, maxSolarRad: None, outHumidity: 72.1, 
outTemp: 17.72, pressure: 1006.7393357345647, radiation: 16, 
rainRate: 0.0, signal1: 0, txBatteryStatus: 0, usUnits: 17, UV: 0.0, 
windchill: 17.72, windDir: 258, windGust: 3.57632, windGustDir: 
260, windSpeed: 1.78816
LOOP:   2020-07-01 21:35:49 CEST (1593632149) beaufort: 1, dateTime: 
1593632149, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 258, 
windGust: 3.57632, windGustDir: 260, windSpeed: 1.78816
LOOP:   2020-07-01 21:35:52 CEST (1593632152) beaufort: 2, dateTime: 
1593632152, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 254, 
windGust: 3.57632, windGustDir: 260, windSpeed: 2.2352
LOOP:   2020-07-01 21:35:54 CEST (1593632154) beaufort: 1, dateTime: 
1593632154, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 250, 
windGust: 3.57632, windGustDir: 260, windSpeed: 1.78816
LOOP:   2020-07-01 21:35:57 CEST (1593632157) beaufort: 1, dateTime: 
1593632157, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 250, 
windGust: 3.57632, windGustDir: 260, windSpeed: 1.34112
LOOP:   2020-07-01 21:35:59 CEST (1593632159) beaufort: 1, dateTime: 
1593632159, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 250, 
windGust: 3.57632, windGustDir: 260, windSpeed: 1.34112
LOOP:   2020-07-01 21:36:02 CEST (1593632162) beaufort: 1, dateTime: 
1593632162, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 255, 
windGust: 3.57632, windGustDir: 252, windSpeed: 1.34112
LOOP:   2020-07-01 21:36:04 CEST (1593632164) beaufort: 1, dateTime: 
1593632164, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 259, 
windGust: 3.57632, windGustDir: 252, windSpeed: 1.78816
LOOP:   2020-07-01 21:36:07 CEST (1593632167) beaufort: 2, dateTime: 
1593632167, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 267, 
windGust: 3.57632, windGustDir: 252, windSpeed: 2.68224
LOOP:   2020-07-01 21:36:09 CEST (1593632169) beaufort: 1, dateTime: 
1593632169, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 256, 
windGust: 3.57632, windGustDir: 252, windSpeed: 1.78816
LOOP:   2020-07-01 21:36:09 CEST (1593632169) altimeter: 
1006.7959690570649, appTemp: 17.28481418176042, barometer: 
1007.1118384320345, beaufort: 1, cloudbase: 621.1850988795652, dateTime: 
1593632169, dewpoint: 12.612, heatindex: 17.72, 
humidex: 20.314658361183554, inDewpoint: 14.445, inHumidity: 
45.2, inTemp: 27.332, maxSolarRad: None, outHumidity: 72.1, 
outTemp: 17.72, pressure: 1006.7054718529766, radiation: 16, 
rainRate: 0.0, signal1: 0, txBatteryStatus: 0, usUnits: 17, UV: 0.0, 
windchill: 17.72, windDir: 256, windGust: 3.57632, windGustDir: 
260, windSpeed: 1.78816
LOOP:   2020-07-01 21:36:12 CEST (1593632172) beaufort: 1, dateTime: 
1593632172, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 258, 
windGust: 3.57632, windGustDir: 252, windSpeed: 1.78816
LOOP:   2020-07-01 21:36:14 CEST (1593632174) beaufort: 2, dateTime: 
1593632174, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 265, 
windGust: 3.57632, windGustDir: 252, windSpeed: 3.12928
LOOP:   2020-07-01 21:36:17 CEST (1593632177) beaufort: 2, dateTime: 
1593632177, maxSolarRad: None, rainRate: 0.0, usUnits: 17, windDir: 265, 
windGust: 3.57632, windGustDir: 252, windSpeed: 3.12928
REC:2020-07-01 21:36:00 CEST (1593632160) altimeter: 
1006.8298368803157, appTemp: 17.28481418176042, barometer: 
1007.1457023136227, beaufort: 1.1667, cloudbase: 
621.1850988795652, dateTime: 1593632160, dewpoint: 12.612, ET: 
0.0011517070455688023, heatindex: 17.72, humidex: 
20.314658361183554, inDewpoint: 14.445, inHumidity: 45.2, 
inTemp: 27.332, interval: 1.0, maxSolarRad: None, outHumidity: 
72.1, outTemp: 17.72, pressure: 1006.7393357345647, radiation: 
16.0, rainRate: 0.0, signal1: 0.0, txBatteryStatus: 0.0, usUnits: 17, UV: 
0.0, windchill: 17.72, windDir: 253.651796853672, windGust: 
3.57632, windGustDir: 260, windrun: 0.1028192, windSpeed: 1.71365333
LOOP:   2020-07-01 21:36:17 CEST (1593632177) altimeter: 
1006.7959690570649, appTemp: 16.346030181760423, barometer: 
1007.1118384320345, beaufort: 2, cloudbase: 621.1850988795652, dateTime: 
1593632177, dewpoint: 12.612, heatindex: 17.72, 
humidex: 

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

Good to hear!

If you have time, can you check the latest development build: 
https://github.com/grebleem/weewx-weatherlinkliveudp/archive/development.zip
 
If you add this to the stanza
extra_id =3

You should have the extra sensor data in weewx.


On Tuesday, June 30, 2020 at 10:08:26 PM UTC+2, Maarten van der Hoeven 
wrote:
>
> Yes, running nice! 
>
> I have an external temp sensor; willing to test also!
>
> Op dinsdag 30 juni 2020 19:11:01 UTC+2 schreef Bastiaan Meelberg:
>>
>> Made a lot of changes the last few days to make this driver more solid. 
>> For those who is interested please check out the latest development 
>> branch:
>>
>> https://github.com/grebleem/weewx-weatherlinkliveudp/tree/development
>>
>> Make shure the stanza in weewx.conf look something like this:
>> [WeatherLinkLiveUDP]
>> wll_ip = 192.168.1.47
>> poll_interval = 20# number of seconds (min. is 10 seconds)
>> driver = user.weatherlinkliveudp
>>
>> The next implementation will be extra temp sensor.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/ebf88323-e47a-4a42-a3a1-987b960a0727o%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

Made a lot of changes the last few days to make this driver more solid. 
For those who is interested please check out the latest development branch:

https://github.com/grebleem/weewx-weatherlinkliveudp/tree/development

Make shure the stanza in weewx.conf look something like this:
[WeatherLinkLiveUDP]
wll_ip = 192.168.1.47
poll_interval = 20# number of seconds (min. is 10 seconds)
driver = user.weatherlinkliveudp

The next implementation will be extra temp sensor.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/42e6c053-33fa-4ceb-81eb-1d23c28efbe8o%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

You are right. It needs a better solution, but it works for now.

The problem with multiple sensors is that there is a second conditions in 
data with the data_structure_type. But some values are 'null' and some are 
'0' (e.g. rain_rate_last).
I will change it in the future that the user can set a tx_id for ISS, wind 
and so on.


On Sunday, June 28, 2020 at 12:00:39 PM UTC+2, flor...@pre-vost.fr wrote:
>
> Bastiaan,
>
> How can I find lsid without make a request to know in json format ?
>
> I don't know if the best practice is to check via lsid or 
> data_structure_type ?
>
> Thank's,
>
> Le dimanche 28 juin 2020 à 11:51:02 UTC+2, hoev...@gmail.com a écrit :
>
>> Driver updated, data is okay now!
>>
>> Also running MQTT and bechertown: I see windspeed reported as km/h, 
>> although I've set the unit to m/s in weewx.conf
>>
>> Yes, tx_id 3 is an extra temp sensor. I've got the ISS on ID=2, and the 
>> temp sensor on ID=3
>>
>> Op zondag 28 juni 2020 om 11:48:59 UTC+2 schreef Bastiaan Meelberg:
>>
>>> Very helpful Maarten! Thank you.
>>>
>>> The temp with tx_id 3 that is an 'extra' temp sensor?
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/26a2faee-5022-40d3-b739-6bcef553ff74o%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

My apologies for my misinformation... I thought I had set the windspeed om 
meter_per_seconds, but it was still on the default km_per_hour.

I've changed the units in weewx.conf, now displaying as meter_per_second


Op zondag 28 juni 2020 12:00:44 UTC+2 schreef Bastiaan Meelberg:
>
> The MQTT is sending the wind in kph:
>
> {"dateTime": "1593338025.0", "windSpeed_kph": "4.828032", "winDir": 
> "319.0", "windGust_kph": "25.749504", "windGustDir": "169.0", "rain_cm": 
> "0.0", "rainRate_mm_per_hour": "0.0", "beaufort_count": "1.0", 
> "maxSolarRad_Wpm2": "822.1835611108015", "hourRain_cm": "0.0", "rain24_cm"
> : "0.06", "dayRain_mm": "0.0", "usUnits": "16.0"}
>
>
> The Belchertown skin is not altering the MQTT message, so I made this 
> change to the weewx.conf file to display the correct unit:
>
> # Various options for customizing your reports.
>
> [[Defaults]]
> [[[Units]]]
> Groups
> group_speed = km_per_hour# Options are 
> 'mile_per_hour', 'km_per_hour', 'knot', or 'meter_per_second'
>
> If you need another MQTT need to send it.
>
>
>
> On Sunday, June 28, 2020 at 11:51:02 AM UTC+2, Maarten van der Hoeven 
> wrote:
>>
>> Driver updated, data is okay now!
>>
>> Also running MQTT and bechertown: I see windspeed reported as km/h, 
>> although I've set the unit to m/s in weewx.conf
>>
>> Yes, tx_id 3 is an extra temp sensor. I've got the ISS on ID=2, and the 
>> temp sensor on ID=3
>>
>> Op zondag 28 juni 2020 om 11:48:59 UTC+2 schreef Bastiaan Meelberg:
>>
>>> Very helpful Maarten! Thank you.
>>>
>>> The temp with tx_id 3 that is an 'extra' temp sensor?
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/a0c096fe-c8f2-4614-bde9-7df362ecb999o%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

The MQTT is sending the wind in kph:

{"dateTime": "1593338025.0", "windSpeed_kph": "4.828032", "winDir": "319.0", 
"windGust_kph": "25.749504", "windGustDir": "169.0", "rain_cm": "0.0", 
"rainRate_mm_per_hour": "0.0", "beaufort_count": "1.0", "maxSolarRad_Wpm2": 
"822.1835611108015", "hourRain_cm": "0.0", "rain24_cm": "0.06", "dayRain_mm"
: "0.0", "usUnits": "16.0"}


The Belchertown skin is not altering the MQTT message, so I made this 
change to the weewx.conf file to display the correct unit:

# Various options for customizing your reports.

[[Defaults]]
[[[Units]]]
Groups
group_speed = km_per_hour# Options are 'mile_per_hour', 
'km_per_hour', 'knot', or 'meter_per_second'

If you need another MQTT need to send it.



On Sunday, June 28, 2020 at 11:51:02 AM UTC+2, Maarten van der Hoeven wrote:
>
> Driver updated, data is okay now!
>
> Also running MQTT and bechertown: I see windspeed reported as km/h, 
> although I've set the unit to m/s in weewx.conf
>
> Yes, tx_id 3 is an extra temp sensor. I've got the ISS on ID=2, and the 
> temp sensor on ID=3
>
> Op zondag 28 juni 2020 om 11:48:59 UTC+2 schreef Bastiaan Meelberg:
>
>> Very helpful Maarten! Thank you.
>>
>> The temp with tx_id 3 that is an 'extra' temp sensor?
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/8347a821-0921-44ca-8596-75d4e970b2e5o%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[flor...@pre-vost.fr]

Bastiaan,

How can I find lsid without make a request to know in json format ?

I don't know if the best practice is to check via lsid or 
data_structure_type ?

Thank's,

Le dimanche 28 juin 2020 à 11:51:02 UTC+2, hoev...@gmail.com a écrit :

> Driver updated, data is okay now!
>
> Also running MQTT and bechertown: I see windspeed reported as km/h, 
> although I've set the unit to m/s in weewx.conf
>
> Yes, tx_id 3 is an extra temp sensor. I've got the ISS on ID=2, and the 
> temp sensor on ID=3
>
> Op zondag 28 juni 2020 om 11:48:59 UTC+2 schreef Bastiaan Meelberg:
>
>> Very helpful Maarten! Thank you.
>>
>> The temp with tx_id 3 that is an 'extra' temp sensor?
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/66245f56-9cf4-4a70-a93d-df01eefbcf2dn%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Maarten van der Hoeven]

Driver updated, data is okay now!

Also running MQTT and bechertown: I see windspeed reported as km/h, 
although I've set the unit to m/s in weewx.conf

Yes, tx_id 3 is an extra temp sensor. I've got the ISS on ID=2, and the 
temp sensor on ID=3

Op zondag 28 juni 2020 om 11:48:59 UTC+2 schreef Bastiaan Meelberg:

> Very helpful Maarten! Thank you.
>
> The temp with tx_id 3 that is an 'extra' temp sensor?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/c0fd6467-3c48-4db5-905f-c0f70604438bn%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

Very helpful Maarten! Thank you.

The temp with tx_id 3 that is an 'extra' temp sensor?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/9329d3e9-fdaf-4c4e-83bb-43cd27f96012o%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

Yes! That would be great to get one solid WLL driver.

Cheers,
Bastiaan

On Sunday, June 28, 2020 at 11:41:35 AM UTC+2, flor...@pre-vost.fr wrote:
>
> Hi !
> Nice to have a driver for udp request !
>
> I'm very glad to work with you to develop the driver to have in futur a 
> single driver :) 
>
> Le dimanche 28 juin 2020 à 11:28:58 UTC+2, Bastiaan Meelberg a écrit :
>
>> The last few weeks I have been working on a weewx driver for Davis 
>> Weather Link Live. This device can give regular intervals of full ISS data 
>> and a 2.5 seconds interval of UDP data containing wind and rain. See this 
>> site for more information 
>> https://weatherlink.github.io/weatherlink-live-local-api/
>>
>> At this moment there is a working beta version: 
>> https://github.com/grebleem/WeatherLinkliveUDP for who is interested. 
>> The driver can be seen in action here https://meteo-otterlo.nl 
>>
>> However, the JSON data can be a bit odd when using multiple stations. 
>> That is if a second ISS for an anemometer or a separate temperature sensor 
>> is installed. 
>>
>> So if you have a Davis Weather Link Live (WLL), it would helpful if you 
>> post the JSON response from a http://1.2.3.4:80/v1/current_conditions 
>> request in a web browser (where 1.2.3.4 is the ip address of the WLL). So I 
>> can implement multiple sensors in this driver. 
>>
>> Also at the davis-udp.py program will write the UDP JSON to a file, these 
>> also would be very helpful!
>>
>> Thanks,
>> Bastiaan
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/37950807-7193-4938-897c-beea7cf7e825o%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

Maarten,

The driver is updated. Try again please.

On Sunday, June 28, 2020 at 11:37:58 AM UTC+2, Maarten van der Hoeven wrote:
>
> Running the beta, it throws an error instantly:
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/d27c7641-b4cb-4097-a48e-72101587d09ao%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[flor...@pre-vost.fr]

Hi !
Nice to have a driver for udp request !

I'm very glad to work with you to develop the driver to have in futur a 
single driver :) 

Le dimanche 28 juin 2020 à 11:28:58 UTC+2, Bastiaan Meelberg a écrit :

> The last few weeks I have been working on a weewx driver for Davis Weather 
> Link Live. This device can give regular intervals of full ISS data and a 
> 2.5 seconds interval of UDP data containing wind and rain. See this site 
> for more information 
> https://weatherlink.github.io/weatherlink-live-local-api/
>
> At this moment there is a working beta version: 
> https://github.com/grebleem/WeatherLinkliveUDP for who is interested. The 
> driver can be seen in action here https://meteo-otterlo.nl 
>
> However, the JSON data can be a bit odd when using multiple stations. That 
> is if a second ISS for an anemometer or a separate temperature sensor is 
> installed. 
>
> So if you have a Davis Weather Link Live (WLL), it would helpful if you 
> post the JSON response from a http://1.2.3.4:80/v1/current_conditions 
> request in a web browser (where 1.2.3.4 is the ip address of the WLL). So I 
> can implement multiple sensors in this driver. 
>
> Also at the davis-udp.py program will write the UDP JSON to a file, these 
> also would be very helpful!
>
> Thanks,
> Bastiaan
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/88e11f03-702c-4964-8734-b32c074dc412n%40googlegroups.com.

[weewx-development] Re: Davis Weather Link Live driver with UDP

[Bastiaan Meelberg]

I see I still use the lsid of mine station in some part of the driver, will 
update is in a few minutes.


On Sunday, June 28, 2020 at 11:37:58 AM UTC+2, Maarten van der Hoeven wrote:
>
> Running the beta, it throws an error instantly:
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/207ef048-24a8-404a-89e1-ea654b98a812o%40googlegroups.com.