Re: [weewx-development] Weatherlink Live driver developpment

2020-06-30 Thread Maarten van der Hoeven
Thx, cant wait :)

Meanwhile, I am importing all history data from my weatherstation into the 
new Weatherlink-account (created when I started to use WLL). Data range 
starting from August 2012. A lot of data to use for testing :)

Op dinsdag 30 juni 2020 om 11:39:53 UTC+2 schreef flor...@pre-vost.fr:

> Thank's a lot ! 
>
> Seem to be the same structure that the Wll module, just ajust somethings 
> like data_structure_type and code will be adapted to extra sensor and 
> deported sensor
>
> Keep an eyes to this thread, I will update code soon :) 
>
> Le mardi 30 juin 2020 à 11:28:15 UTC+2, hoev...@gmail.com a écrit :
>
>> [WLLDriver]
>> driver = user.WLLDriver
>> max_tries = 5
>> retry_wait = 10
>> poll_interval = 5
>> url = http://192.168.2.33:80/v1/current_conditions
>> wl_apikey = nivwsekqwfbkhqtqwo8nximhl7zgxpcs
>> wl_apisecret = [thats a secret]
>> wl_stationid = 92818 (this one is the correct one!)
>> wl_archive_interval = 5
>>
>>
>> Op dinsdag 30 juni 2020 om 11:25:10 UTC+2 schreef flor...@pre-vost.fr:
>>
>>> Can you provid me your config of my driver in weewx.conf please ?
>>>
>>> Thank you,
>>>
>>> Le mardi 30 juin 2020 à 10:54:23 UTC+2, hoev...@gmail.com a écrit :
>>>
 Latest data in the database:

 mysql> select from_unixtime(datetime),datetime from archive;
 +-++
 | from_unixtime(datetime) | datetime   |
 +-++
 | 2020-06-30 10:25:00 | 1593505500 |
 | 2020-06-30 10:26:00 | 1593505560 |
 | 2020-06-30 10:27:00 | 1593505620 |
 +-++
 3 rows in set (0.00 sec)

 Started weewx again at 10:54. samen response: {}

 URL:

 https://api.weatherlink.com/v2/historic/22514?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593507220=1593505500=1593507000=52e056cf58079e984d2e1535939aa929cf3bac42ec7a25eed9a764d9dcdaab58

 Op dinsdag 30 juni 2020 om 10:47:59 UTC+2 schreef Maarten van der 
 Hoeven:

> I've stopped WeeWX for 30 minutes, and restarted. Same response: {}
>
> I checked the Weatherlink website: data is archived every 5 minutes. 
> Running a Pro-subscription
>
>
>
> Op dinsdag 30 juni 2020 om 10:07:39 UTC+2 schreef flor...@pre-vost.fr:
>
>> No data available. Please stop weewx and wait more thant 10min before 
>> restart
>
>

-- 
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/8f16f33a-703c-4dc8-9c04-6cce39776e61n%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-30 Thread flor...@pre-vost.fr
Thank's a lot ! 

Seem to be the same structure that the Wll module, just ajust somethings 
like data_structure_type and code will be adapted to extra sensor and 
deported sensor

Keep an eyes to this thread, I will update code soon :) 

Le mardi 30 juin 2020 à 11:28:15 UTC+2, hoev...@gmail.com a écrit :

> [WLLDriver]
> driver = user.WLLDriver
> max_tries = 5
> retry_wait = 10
> poll_interval = 5
> url = http://192.168.2.33:80/v1/current_conditions
> wl_apikey = nivwsekqwfbkhqtqwo8nximhl7zgxpcs
> wl_apisecret = [thats a secret]
> wl_stationid = 92818 (this one is the correct one!)
> wl_archive_interval = 5
>
>
> Op dinsdag 30 juni 2020 om 11:25:10 UTC+2 schreef flor...@pre-vost.fr:
>
>> Can you provid me your config of my driver in weewx.conf please ?
>>
>> Thank you,
>>
>> Le mardi 30 juin 2020 à 10:54:23 UTC+2, hoev...@gmail.com a écrit :
>>
>>> Latest data in the database:
>>>
>>> mysql> select from_unixtime(datetime),datetime from archive;
>>> +-++
>>> | from_unixtime(datetime) | datetime   |
>>> +-++
>>> | 2020-06-30 10:25:00 | 1593505500 |
>>> | 2020-06-30 10:26:00 | 1593505560 |
>>> | 2020-06-30 10:27:00 | 1593505620 |
>>> +-++
>>> 3 rows in set (0.00 sec)
>>>
>>> Started weewx again at 10:54. samen response: {}
>>>
>>> URL:
>>>
>>> https://api.weatherlink.com/v2/historic/22514?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593507220=1593505500=1593507000=52e056cf58079e984d2e1535939aa929cf3bac42ec7a25eed9a764d9dcdaab58
>>>
>>> Op dinsdag 30 juni 2020 om 10:47:59 UTC+2 schreef Maarten van der Hoeven:
>>>
 I've stopped WeeWX for 30 minutes, and restarted. Same response: {}

 I checked the Weatherlink website: data is archived every 5 minutes. 
 Running a Pro-subscription



 Op dinsdag 30 juni 2020 om 10:07:39 UTC+2 schreef flor...@pre-vost.fr:

> No data available. Please stop weewx and wait more thant 10min before 
> restart



-- 
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/0f8c495b-7a60-4e9a-8d5c-f906465a715cn%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-30 Thread Maarten van der Hoeven
[WLLDriver]
driver = user.WLLDriver
max_tries = 5
retry_wait = 10
poll_interval = 5
url = http://192.168.2.33:80/v1/current_conditions
wl_apikey = nivwsekqwfbkhqtqwo8nximhl7zgxpcs
wl_apisecret = [thats a secret]
wl_stationid = 92818 (this one is the correct one!)
wl_archive_interval = 5


Op dinsdag 30 juni 2020 om 11:25:10 UTC+2 schreef flor...@pre-vost.fr:

> Can you provid me your config of my driver in weewx.conf please ?
>
> Thank you,
>
> Le mardi 30 juin 2020 à 10:54:23 UTC+2, hoev...@gmail.com a écrit :
>
>> Latest data in the database:
>>
>> mysql> select from_unixtime(datetime),datetime from archive;
>> +-++
>> | from_unixtime(datetime) | datetime   |
>> +-++
>> | 2020-06-30 10:25:00 | 1593505500 |
>> | 2020-06-30 10:26:00 | 1593505560 |
>> | 2020-06-30 10:27:00 | 1593505620 |
>> +-++
>> 3 rows in set (0.00 sec)
>>
>> Started weewx again at 10:54. samen response: {}
>>
>> URL:
>>
>> https://api.weatherlink.com/v2/historic/22514?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593507220=1593505500=1593507000=52e056cf58079e984d2e1535939aa929cf3bac42ec7a25eed9a764d9dcdaab58
>>
>> Op dinsdag 30 juni 2020 om 10:47:59 UTC+2 schreef Maarten van der Hoeven:
>>
>>> I've stopped WeeWX for 30 minutes, and restarted. Same response: {}
>>>
>>> I checked the Weatherlink website: data is archived every 5 minutes. 
>>> Running a Pro-subscription
>>>
>>>
>>>
>>> Op dinsdag 30 juni 2020 om 10:07:39 UTC+2 schreef flor...@pre-vost.fr:
>>>
 No data available. Please stop weewx and wait more thant 10min before 
 restart
>>>
>>>

-- 
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/3268e4fd-4d15-4067-8175-826055cfbef5n%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-30 Thread flor...@pre-vost.fr
Can you provid me your config of my driver in weewx.conf please ?

Thank you,

Le mardi 30 juin 2020 à 10:54:23 UTC+2, hoev...@gmail.com a écrit :

> Latest data in the database:
>
> mysql> select from_unixtime(datetime),datetime from archive;
> +-++
> | from_unixtime(datetime) | datetime   |
> +-++
> | 2020-06-30 10:25:00 | 1593505500 |
> | 2020-06-30 10:26:00 | 1593505560 |
> | 2020-06-30 10:27:00 | 1593505620 |
> +-++
> 3 rows in set (0.00 sec)
>
> Started weewx again at 10:54. samen response: {}
>
> URL:
>
> https://api.weatherlink.com/v2/historic/22514?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593507220=1593505500=1593507000=52e056cf58079e984d2e1535939aa929cf3bac42ec7a25eed9a764d9dcdaab58
>
> Op dinsdag 30 juni 2020 om 10:47:59 UTC+2 schreef Maarten van der Hoeven:
>
>> I've stopped WeeWX for 30 minutes, and restarted. Same response: {}
>>
>> I checked the Weatherlink website: data is archived every 5 minutes. 
>> Running a Pro-subscription
>>
>>
>>
>> Op dinsdag 30 juni 2020 om 10:07:39 UTC+2 schreef flor...@pre-vost.fr:
>>
>>> No data available. Please stop weewx and wait more thant 10min before 
>>> restart
>>
>>

-- 
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/bbb7f1bb-b1d6-4b82-8913-22bc10d4cd8fn%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-30 Thread Maarten van der Hoeven
Found the problem. Turned out my device ID was not correct. 

URL:https://api.weatherlink.com/v2/historic/92818?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593508965=1593505500=1593508800=8b0021b0956d2c00ff93057028e2e82e03ccf02c1e9c0b9fae3849d8e46ee158

JSON output of historic, see attachment





Op dinsdag 30 juni 2020 om 10:54:23 UTC+2 schreef Maarten van der Hoeven:

> Latest data in the database:
>
> mysql> select from_unixtime(datetime),datetime from archive;
> +-++
> | from_unixtime(datetime) | datetime   |
> +-++
> | 2020-06-30 10:25:00 | 1593505500 |
> | 2020-06-30 10:26:00 | 1593505560 |
> | 2020-06-30 10:27:00 | 1593505620 |
> +-++
> 3 rows in set (0.00 sec)
>
> Started weewx again at 10:54. samen response: {}
>
> URL:
>
> https://api.weatherlink.com/v2/historic/22514?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593507220=1593505500=1593507000=52e056cf58079e984d2e1535939aa929cf3bac42ec7a25eed9a764d9dcdaab58
>
> Op dinsdag 30 juni 2020 om 10:47:59 UTC+2 schreef Maarten van der Hoeven:
>
>> I've stopped WeeWX for 30 minutes, and restarted. Same response: {}
>>
>> I checked the Weatherlink website: data is archived every 5 minutes. 
>> Running a Pro-subscription
>>
>>
>>
>> Op dinsdag 30 juni 2020 om 10:07:39 UTC+2 schreef flor...@pre-vost.fr:
>>
>>> No data available. Please stop weewx and wait more thant 10min before 
>>> restart
>>
>>

-- 
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/366fd4cc-9393-40c7-96c3-a24df801bfc2n%40googlegroups.com.

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-30 Thread Maarten van der Hoeven
Latest data in the database:

mysql> select from_unixtime(datetime),datetime from archive;
+-++
| from_unixtime(datetime) | datetime   |
+-++
| 2020-06-30 10:25:00 | 1593505500 |
| 2020-06-30 10:26:00 | 1593505560 |
| 2020-06-30 10:27:00 | 1593505620 |
+-++
3 rows in set (0.00 sec)

Started weewx again at 10:54. samen response: {}

URL:
https://api.weatherlink.com/v2/historic/22514?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593507220=1593505500=1593507000=52e056cf58079e984d2e1535939aa929cf3bac42ec7a25eed9a764d9dcdaab58

Op dinsdag 30 juni 2020 om 10:47:59 UTC+2 schreef Maarten van der Hoeven:

> I've stopped WeeWX for 30 minutes, and restarted. Same response: {}
>
> I checked the Weatherlink website: data is archived every 5 minutes. 
> Running a Pro-subscription
>
>
>
> Op dinsdag 30 juni 2020 om 10:07:39 UTC+2 schreef flor...@pre-vost.fr:
>
>> No data available. Please stop weewx and wait more thant 10min before 
>> restart
>
>

-- 
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/38379281-4a92-4aa6-b115-76e70919bcb4n%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-30 Thread Maarten van der Hoeven
I've stopped WeeWX for 30 minutes, and restarted. Same response: {}

I checked the Weatherlink website: data is archived every 5 minutes. 
Running a Pro-subscription



Op dinsdag 30 juni 2020 om 10:07:39 UTC+2 schreef flor...@pre-vost.fr:

> No data available. Please stop weewx and wait more thant 10min before 
> restart

-- 
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/6ad61303-ad51-42b4-b0dc-1887fae7df25n%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-30 Thread Florentin Prevost
No data available. Please stop weewx and wait more thant 10min before restart

-- 
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/2a5e9272-e530-464e-9610-5734ed0f3bf4o%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-30 Thread Maarten van der Hoeven
Done. This is the URL I grabbed from syslog:
https://api.weatherlink.com/v2/historic/22514?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593503708=1593502800=1593503400=100545991c40d123e4d4a29724a24176fa33407e585be3b211f91b1fa2589c38

JSON-result is:
{} 


Error in the syslog (sensors):
Jun 30 09:55:08 ubuntu weewx[6232] DEBUG user.WLLDriver: Request archive 
from 1593502980 to 1593503400
Jun 30 09:55:08 ubuntu weewx[6232] DEBUG user.WLLDriver: URL API 
Weatherlink is 
https://api.weatherlink.com/v2/historic/22514?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593503708=1593502800=1593503400=100545991c40d123e4d4a29724a24176fa33407e585be3b211f91b1fa2589c38
 

Jun 30 09:55:08 ubuntu weewx[6232] DEBUG urllib3.connectionpool: Starting 
new HTTPS connection (1): api.weatherlink.com:443
Jun 30 09:55:08 ubuntu weewx[6232] DEBUG urllib3.connectionpool: 
https://api.weatherlink.com:443 "GET 
/v2/historic/22514?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593503708=1593502800=1593503400=100545991c40d123e4d4a29724a24176fa33407e585be3b211f91b1fa2589c38
 
HTTP/1.1" 200 2
Jun 30 09:55:08 ubuntu weewx[6232] DEBUG user.WLLDriver: OK Wl 1
Jun 30 09:55:08 ubuntu weewx[6232] DEBUG user.WLLDriver: OK Wl 2
Jun 30 09:55:08 ubuntu weewx[6232] DEBUG user.WLLDriver: StartTimeStamp is 
: 1593503100
Jun 30 09:55:08 ubuntu weewx[6232] INFO user.WLLDriver: Failure to get data 
https://api.weatherlink.com/v2/historic/22514?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593503708=1593502800=1593503400=100545991c40d123e4d4a29724a24176fa33407e585be3b211f91b1fa2589c38
 
- try 3 - ('sensors')


Op dinsdag 30 juni 2020 om 09:40:09 UTC+2 schreef flor...@pre-vost.fr:

> Thank you !
> Can you do it with archive on weatherlink.
>
> Start my driver on Github and take the url on syslog of API v2 when the 
> driver search lost data and put it on your favorite Web browser and share 
> me the result. 
>

-- 
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/df865e66-4ea3-4821-811d-b14a9ed27398n%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-30 Thread Florentin Prevost
Thank you !
Can you do it with archive on weatherlink.

Start my driver on Github and take the url on syslog of API v2 when the driver 
search lost data and put it on your favorite Web browser and share me the 
result. 

-- 
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/3fcf1931-3fb9-4ba8-a1d4-eb7f3b0ea8c4o%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-30 Thread Maarten van der Hoeven
Current:

{"data":{"did":"001D0A71154A","ts":1593501864,"conditions":[{"lsid":325304,"data_structure_type":1,"txid":2,"temp":
 
58.1,"hum":82.8,"dew_point": 52.9,"wet_bulb": 54.8,"heat_index": 
58.1,"wind_chill": 54.8,"thw_index": 54.8,"thsw_index": 
55.2,"wind_speed_last":6.00,"wind_dir_last":215,"wind_speed_avg_last_1_min":6.37,"wind_dir_scalar_avg_last_1_min":218,"wind_speed_avg_last_2_min":7.50,"wind_dir_scalar_avg_last_2_min":219,"wind_speed_hi_last_2_min":14.00,"wind_dir_at_hi_speed_last_2_min":167,"wind_speed_avg_last_10_min":9.87,"wind_dir_scalar_avg_last_10_min":220,"wind_speed_hi_last_10_min":20.00,"wind_dir_at_hi_speed_last_10_min":234,"rain_size":2,"rain_rate_last":0,"rain_rate_hi":0,"rainfall_last_15_min":0,"rain_rate_hi_last_15_min":0,"rainfall_last_60_min":0,"rainfall_last_24_hr":0,"rain_storm":null,"rain_storm_start_at":null,"solar_rad":95,"uv_index":0.0,"rx_state":1,"trans_battery_flag":0,"rainfall_daily":0,"rainfall_monthly":0,"rainfall_year":0,"rain_storm_last":null,"rain_storm_last_start_at":null,"rain_storm_last_end_at":null},{"lsid":325305,"data_structure_type":1,"txid":3,"temp":
 
58.7,"hum":null,"dew_point":null,"wet_bulb":null,"heat_index":null,"wind_chill":null,"thw_index":null,"thsw_index":null,"wind_speed_last":null,"wind_dir_last":null,"wind_speed_avg_last_1_min":null,"wind_dir_scalar_avg_last_1_min":null,"wind_speed_avg_last_2_min":null,"wind_dir_scalar_avg_last_2_min":null,"wind_speed_hi_last_2_min":null,"wind_dir_at_hi_speed_last_2_min":null,"wind_speed_avg_last_10_min":null,"wind_dir_scalar_avg_last_10_min":null,"wind_speed_hi_last_10_min":null,"wind_dir_at_hi_speed_last_10_min":null,"rain_size":1,"rain_rate_last":0,"rain_rate_hi":0,"rainfall_last_15_min":0,"rain_rate_hi_last_15_min":0,"rainfall_last_60_min":0,"rainfall_last_24_hr":0,"rain_storm":null,"rain_storm_start_at":null,"solar_rad":null,"uv_index":null,"rx_state":0,"trans_battery_flag":0,"rainfall_daily":0,"rainfall_monthly":0,"rainfall_year":0,"rain_storm_last":null,"rain_storm_last_start_at":null,"rain_storm_last_end_at":null},{"lsid":325296,"data_structure_type":4,"temp_in":
 
68.3,"hum_in":54.3,"dew_point_in": 51.2,"heat_index_in": 
67.6},{"lsid":325295,"data_structure_type":3,"bar_sea_level":29.769,"bar_trend":
 
0.018,"bar_absolute":29.757}]},"error":null}



Op dinsdag 30 juni 2020 om 09:20:16 UTC+2 schreef Maarten van der Hoeven:

> I'd love to do that, need littile help.
>
> How do I retrieve my station_id? I can use the V2 api tho retrieve it, but 
> I need a api-signature to get that information. And to calculate the 
> api-signuature, I need my station-id. 
>
> Chicken and egg
>
> This is the string (example) to calculate the api-signature (SHA256). You 
> see there's the station-id in it, which I do not know.
>
> api-key987654321station-id1052t1558729481 
>
> Op dinsdag 30 juni 2020 om 08:11:10 UTC+2 schreef flor...@pre-vost.fr:
>
>> Thank you ! 
>>
>> I fix the issue for extra sensor when you request directly on your wll 
>> module.
>>
>> Can you share right now the answer of API v2 of Weatherlink.com like this 
>> :  
>> https://weatherlink.github.io/v2-api/authentication#walkthrough-examples 
>>
>> It help me full because I think that the structure is not the same that 
>> the wll module :)  
>>
>> -fp
>> Le dimanche 28 juin 2020 à 12:15:37 UTC+2, hoev...@gmail.com a écrit :
>>
>>> Sure!
>>>
>>> {"data":{"did":"001D0A71154A","ts":1593339301,"conditions":[{"lsid":321275,"data_structure_type":1,"txid":2,"temp":
>>>  
>>> 67.6,"hum":59.0,"dew_point": 52.8,"wet_bulb": 57.3,"heat_index": 
>>> 67.3,"wind_chill": 64.1,"thw_index": 63.8,"thsw_index": 
>>> 71.5,"wind_speed_last":11.00,"wind_dir_last":203,"wind_speed_avg_last_1_min":11.56,"wind_dir_scalar_avg_last_1_min":215,"wind_speed_avg_last_2_min":11.81,"wind_dir_scalar_avg_last_2_min":217,"wind_speed_hi_last_2_min":18.00,"wind_dir_at_hi_speed_last_2_min":225,"wind_speed_avg_last_10_min":12.75,"wind_dir_scalar_avg_last_10_min":219,"wind_speed_hi_last_10_min":20.00,"wind_dir_at_hi_speed_last_10_min":225,"rain_size":2,"rain_rate_last":0,"rain_rate_hi":0,"rainfall_last_15_min":0,"rain_rate_hi_last_15_min":0,"rainfall_last_60_min":0,"rainfall_last_24_hr":20,"rain_storm":24,"rain_storm_start_at":1593210300,"solar_rad":207,"uv_index":2.1,"rx_state":0,"trans_battery_flag":0,"rainfall_daily":0,"rainfall_monthly":175,"rainfall_year":175,"rain_storm_last":6,"rain_storm_last_start_at":1592760421,"rain_storm_last_end_at":1592866861},{"lsid":321279,"data_structure_type":1,"txid":3,"temp":
>>>  
>>> 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-30 Thread Maarten van der Hoeven
I'd love to do that, need littile help.

How do I retrieve my station_id? I can use the V2 api tho retrieve it, but 
I need a api-signature to get that information. And to calculate the 
api-signuature, I need my station-id. 

Chicken and egg

This is the string (example) to calculate the api-signature (SHA256). You 
see there's the station-id in it, which I do not know.

api-key987654321station-id1052t1558729481 

Op dinsdag 30 juni 2020 om 08:11:10 UTC+2 schreef flor...@pre-vost.fr:

> Thank you ! 
>
> I fix the issue for extra sensor when you request directly on your wll 
> module.
>
> Can you share right now the answer of API v2 of Weatherlink.com like this 
> :  
> https://weatherlink.github.io/v2-api/authentication#walkthrough-examples 
>
> It help me full because I think that the structure is not the same that 
> the wll module :)  
>
> -fp
> Le dimanche 28 juin 2020 à 12:15:37 UTC+2, hoev...@gmail.com a écrit :
>
>> Sure!
>>
>> {"data":{"did":"001D0A71154A","ts":1593339301,"conditions":[{"lsid":321275,"data_structure_type":1,"txid":2,"temp":
>>  
>> 67.6,"hum":59.0,"dew_point": 52.8,"wet_bulb": 57.3,"heat_index": 
>> 67.3,"wind_chill": 64.1,"thw_index": 63.8,"thsw_index": 
>> 71.5,"wind_speed_last":11.00,"wind_dir_last":203,"wind_speed_avg_last_1_min":11.56,"wind_dir_scalar_avg_last_1_min":215,"wind_speed_avg_last_2_min":11.81,"wind_dir_scalar_avg_last_2_min":217,"wind_speed_hi_last_2_min":18.00,"wind_dir_at_hi_speed_last_2_min":225,"wind_speed_avg_last_10_min":12.75,"wind_dir_scalar_avg_last_10_min":219,"wind_speed_hi_last_10_min":20.00,"wind_dir_at_hi_speed_last_10_min":225,"rain_size":2,"rain_rate_last":0,"rain_rate_hi":0,"rainfall_last_15_min":0,"rain_rate_hi_last_15_min":0,"rainfall_last_60_min":0,"rainfall_last_24_hr":20,"rain_storm":24,"rain_storm_start_at":1593210300,"solar_rad":207,"uv_index":2.1,"rx_state":0,"trans_battery_flag":0,"rainfall_daily":0,"rainfall_monthly":175,"rainfall_year":175,"rain_storm_last":6,"rain_storm_last_start_at":1592760421,"rain_storm_last_end_at":1592866861},{"lsid":321279,"data_structure_type":1,"txid":3,"temp":
>>  
>> 72.0,"hum":null,"dew_point":null,"wet_bulb":null,"heat_index":null,"wind_chill":null,"thw_index":null,"thsw_index":null,"wind_speed_last":null,"wind_dir_last":null,"wind_speed_avg_last_1_min":null,"wind_dir_scalar_avg_last_1_min":null,"wind_speed_avg_last_2_min":null,"wind_dir_scalar_avg_last_2_min":null,"wind_speed_hi_last_2_min":null,"wind_dir_at_hi_speed_last_2_min":null,"wind_speed_avg_last_10_min":null,"wind_dir_scalar_avg_last_10_min":null,"wind_speed_hi_last_10_min":null,"wind_dir_at_hi_speed_last_10_min":null,"rain_size":1,"rain_rate_last":0,"rain_rate_hi":0,"rainfall_last_15_min":0,"rain_rate_hi_last_15_min":0,"rainfall_last_60_min":0,"rainfall_last_24_hr":0,"rain_storm":null,"rain_storm_start_at":null,"solar_rad":null,"uv_index":null,"rx_state":0,"trans_battery_flag":0,"rainfall_daily":0,"rainfall_monthly":0,"rainfall_year":0,"rain_storm_last":null,"rain_storm_last_start_at":null,"rain_storm_last_end_at":null},{"lsid":321271,"data_structure_type":4,"temp_in":
>>  
>> 76.4,"hum_in":47.0,"dew_point_in": 54.7,"heat_index_in": 
>> 76.1},{"lsid":321270,"data_structure_type":3,"bar_sea_level":29.889,"bar_trend":
>>  
>> 0.031,"bar_absolute":29.876}]},"error":null}
>>
>> ISS on ID=2, extra temp sensor on ID=3
>>
>>
>>
>> Op zondag 28 juni 2020 12:13:08 UTC+2 schreef flor...@pre-vost.fr:
>>
>>> Hi Maarten,
>>>
>>> To help Bastiaan and me to WLL Driver, can you share the answer of your 
>>> request of http://1.2.3.4/v1/current_conditions (change 1.2.3.4 by your 
>>> internal IP) ?
>>> You've another sensor with other ID and it will be helpfull to have this 
>>> data to implement it on driver,
>>>
>>> Thank you ! 
>>>
>>> Le samedi 27 juin 2020 à 10:53:21 UTC+2, flor...@pre-vost.fr a écrit :
>>>
 Hi,

 Baastian, yes of course, I think it a good idea to make a request using 
 weewx object to read the daily rain to the database and make a comparison 
 with the rainfall daily by the WLL but I need the help of @Tom Keffer for 
 this.

 For UnitUS, I know that if it possible but for readability, I decided 
 to make a conversion before yield the packet to the genlooppackets(). 
 Also, 
 when i need to add record manual by using the method addRecords, I need to 
 put on the packet the right unit set in weewx.conf. If you've another 
 suggest, let me know :) 

 Maarten, I will fix this issue in few days, I know how can I do this by 
 search any key in each sensor :) 

 -fp

 Le samedi 27 juin 2020 à 10:40:09 UTC+2, hoev...@gmail.com a écrit :

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

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-30 Thread flor...@pre-vost.fr
Thank you ! 

I fix the issue for extra sensor when you request directly on your wll 
module.

Can you share right now the answer of API v2 of Weatherlink.com like this 
:  https://weatherlink.github.io/v2-api/authentication#walkthrough-examples 

It help me full because I think that the structure is not the same that the 
wll module :)  

-fp
Le dimanche 28 juin 2020 à 12:15:37 UTC+2, hoev...@gmail.com a écrit :

> Sure!
>
> {"data":{"did":"001D0A71154A","ts":1593339301,"conditions":[{"lsid":321275,"data_structure_type":1,"txid":2,"temp":
>  
> 67.6,"hum":59.0,"dew_point": 52.8,"wet_bulb": 57.3,"heat_index": 
> 67.3,"wind_chill": 64.1,"thw_index": 63.8,"thsw_index": 
> 71.5,"wind_speed_last":11.00,"wind_dir_last":203,"wind_speed_avg_last_1_min":11.56,"wind_dir_scalar_avg_last_1_min":215,"wind_speed_avg_last_2_min":11.81,"wind_dir_scalar_avg_last_2_min":217,"wind_speed_hi_last_2_min":18.00,"wind_dir_at_hi_speed_last_2_min":225,"wind_speed_avg_last_10_min":12.75,"wind_dir_scalar_avg_last_10_min":219,"wind_speed_hi_last_10_min":20.00,"wind_dir_at_hi_speed_last_10_min":225,"rain_size":2,"rain_rate_last":0,"rain_rate_hi":0,"rainfall_last_15_min":0,"rain_rate_hi_last_15_min":0,"rainfall_last_60_min":0,"rainfall_last_24_hr":20,"rain_storm":24,"rain_storm_start_at":1593210300,"solar_rad":207,"uv_index":2.1,"rx_state":0,"trans_battery_flag":0,"rainfall_daily":0,"rainfall_monthly":175,"rainfall_year":175,"rain_storm_last":6,"rain_storm_last_start_at":1592760421,"rain_storm_last_end_at":1592866861},{"lsid":321279,"data_structure_type":1,"txid":3,"temp":
>  
> 72.0,"hum":null,"dew_point":null,"wet_bulb":null,"heat_index":null,"wind_chill":null,"thw_index":null,"thsw_index":null,"wind_speed_last":null,"wind_dir_last":null,"wind_speed_avg_last_1_min":null,"wind_dir_scalar_avg_last_1_min":null,"wind_speed_avg_last_2_min":null,"wind_dir_scalar_avg_last_2_min":null,"wind_speed_hi_last_2_min":null,"wind_dir_at_hi_speed_last_2_min":null,"wind_speed_avg_last_10_min":null,"wind_dir_scalar_avg_last_10_min":null,"wind_speed_hi_last_10_min":null,"wind_dir_at_hi_speed_last_10_min":null,"rain_size":1,"rain_rate_last":0,"rain_rate_hi":0,"rainfall_last_15_min":0,"rain_rate_hi_last_15_min":0,"rainfall_last_60_min":0,"rainfall_last_24_hr":0,"rain_storm":null,"rain_storm_start_at":null,"solar_rad":null,"uv_index":null,"rx_state":0,"trans_battery_flag":0,"rainfall_daily":0,"rainfall_monthly":0,"rainfall_year":0,"rain_storm_last":null,"rain_storm_last_start_at":null,"rain_storm_last_end_at":null},{"lsid":321271,"data_structure_type":4,"temp_in":
>  
> 76.4,"hum_in":47.0,"dew_point_in": 54.7,"heat_index_in": 
> 76.1},{"lsid":321270,"data_structure_type":3,"bar_sea_level":29.889,"bar_trend":
>  
> 0.031,"bar_absolute":29.876}]},"error":null}
>
> ISS on ID=2, extra temp sensor on ID=3
>
>
>
> Op zondag 28 juni 2020 12:13:08 UTC+2 schreef flor...@pre-vost.fr:
>
>> Hi Maarten,
>>
>> To help Bastiaan and me to WLL Driver, can you share the answer of your 
>> request of http://1.2.3.4/v1/current_conditions (change 1.2.3.4 by your 
>> internal IP) ?
>> You've another sensor with other ID and it will be helpfull to have this 
>> data to implement it on driver,
>>
>> Thank you ! 
>>
>> Le samedi 27 juin 2020 à 10:53:21 UTC+2, flor...@pre-vost.fr a écrit :
>>
>>> Hi,
>>>
>>> Baastian, yes of course, I think it a good idea to make a request using 
>>> weewx object to read the daily rain to the database and make a comparison 
>>> with the rainfall daily by the WLL but I need the help of @Tom Keffer for 
>>> this.
>>>
>>> For UnitUS, I know that if it possible but for readability, I decided to 
>>> make a conversion before yield the packet to the genlooppackets(). Also, 
>>> when i need to add record manual by using the method addRecords, I need to 
>>> put on the packet the right unit set in weewx.conf. If you've another 
>>> suggest, let me know :) 
>>>
>>> Maarten, I will fix this issue in few days, I know how can I do this by 
>>> search any key in each sensor :) 
>>>
>>> -fp
>>>
>>> Le samedi 27 juin 2020 à 10:40:09 UTC+2, hoev...@gmail.com a écrit :
>>>
 Hello Bastiaan,

 The WLL is a wonderful piece of equipment. Now I can run production 
 with WeeWX, and start a test-enviroment in a virtual machine, while 
 talking 
 to the same WLL.

 I've installed your driver. I have running my ISS on ID 2 (and have an 
 external temp sensor running on sensor 3).

 When ISS set to ID=2, I only seems to see internal sensor data, like:

 LOOP:   2020-06-27 10:37:51 CEST (1593247071) altimeter: 
 1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247071, 
 inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
 27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
 rainRate: 0.0, usUnits: 17
 {'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
 LOOP:   2020-06-27 10:37:51 CEST (1593247071) dateTime: 1593247071, 
 maxSolarRad: None, 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-28 Thread Maarten van der Hoeven
Sure!

{"data":{"did":"001D0A71154A","ts":1593339301,"conditions":[{"lsid":321275,"data_structure_type":1,"txid":2,"temp":
 
67.6,"hum":59.0,"dew_point": 52.8,"wet_bulb": 57.3,"heat_index": 
67.3,"wind_chill": 64.1,"thw_index": 63.8,"thsw_index": 
71.5,"wind_speed_last":11.00,"wind_dir_last":203,"wind_speed_avg_last_1_min":11.56,"wind_dir_scalar_avg_last_1_min":215,"wind_speed_avg_last_2_min":11.81,"wind_dir_scalar_avg_last_2_min":217,"wind_speed_hi_last_2_min":18.00,"wind_dir_at_hi_speed_last_2_min":225,"wind_speed_avg_last_10_min":12.75,"wind_dir_scalar_avg_last_10_min":219,"wind_speed_hi_last_10_min":20.00,"wind_dir_at_hi_speed_last_10_min":225,"rain_size":2,"rain_rate_last":0,"rain_rate_hi":0,"rainfall_last_15_min":0,"rain_rate_hi_last_15_min":0,"rainfall_last_60_min":0,"rainfall_last_24_hr":20,"rain_storm":24,"rain_storm_start_at":1593210300,"solar_rad":207,"uv_index":2.1,"rx_state":0,"trans_battery_flag":0,"rainfall_daily":0,"rainfall_monthly":175,"rainfall_year":175,"rain_storm_last":6,"rain_storm_last_start_at":1592760421,"rain_storm_last_end_at":1592866861},{"lsid":321279,"data_structure_type":1,"txid":3,"temp":
 
72.0,"hum":null,"dew_point":null,"wet_bulb":null,"heat_index":null,"wind_chill":null,"thw_index":null,"thsw_index":null,"wind_speed_last":null,"wind_dir_last":null,"wind_speed_avg_last_1_min":null,"wind_dir_scalar_avg_last_1_min":null,"wind_speed_avg_last_2_min":null,"wind_dir_scalar_avg_last_2_min":null,"wind_speed_hi_last_2_min":null,"wind_dir_at_hi_speed_last_2_min":null,"wind_speed_avg_last_10_min":null,"wind_dir_scalar_avg_last_10_min":null,"wind_speed_hi_last_10_min":null,"wind_dir_at_hi_speed_last_10_min":null,"rain_size":1,"rain_rate_last":0,"rain_rate_hi":0,"rainfall_last_15_min":0,"rain_rate_hi_last_15_min":0,"rainfall_last_60_min":0,"rainfall_last_24_hr":0,"rain_storm":null,"rain_storm_start_at":null,"solar_rad":null,"uv_index":null,"rx_state":0,"trans_battery_flag":0,"rainfall_daily":0,"rainfall_monthly":0,"rainfall_year":0,"rain_storm_last":null,"rain_storm_last_start_at":null,"rain_storm_last_end_at":null},{"lsid":321271,"data_structure_type":4,"temp_in":
 
76.4,"hum_in":47.0,"dew_point_in": 54.7,"heat_index_in": 
76.1},{"lsid":321270,"data_structure_type":3,"bar_sea_level":29.889,"bar_trend":
 
0.031,"bar_absolute":29.876}]},"error":null}

ISS on ID=2, extra temp sensor on ID=3



Op zondag 28 juni 2020 12:13:08 UTC+2 schreef flor...@pre-vost.fr:
>
> Hi Maarten,
>
> To help Bastiaan and me to WLL Driver, can you share the answer of your 
> request of http://1.2.3.4/v1/current_conditions (change 1.2.3.4 by your 
> internal IP) ?
> You've another sensor with other ID and it will be helpfull to have this 
> data to implement it on driver,
>
> Thank you ! 
>
> Le samedi 27 juin 2020 à 10:53:21 UTC+2, flor...@pre-vost.fr a écrit :
>
>> Hi,
>>
>> Baastian, yes of course, I think it a good idea to make a request using 
>> weewx object to read the daily rain to the database and make a comparison 
>> with the rainfall daily by the WLL but I need the help of @Tom Keffer for 
>> this.
>>
>> For UnitUS, I know that if it possible but for readability, I decided to 
>> make a conversion before yield the packet to the genlooppackets(). Also, 
>> when i need to add record manual by using the method addRecords, I need to 
>> put on the packet the right unit set in weewx.conf. If you've another 
>> suggest, let me know :) 
>>
>> Maarten, I will fix this issue in few days, I know how can I do this by 
>> search any key in each sensor :) 
>>
>> -fp
>>
>> Le samedi 27 juin 2020 à 10:40:09 UTC+2, hoev...@gmail.com a écrit :
>>
>>> Hello Bastiaan,
>>>
>>> The WLL is a wonderful piece of equipment. Now I can run production with 
>>> WeeWX, and start a test-enviroment in a virtual machine, while talking to 
>>> the same WLL.
>>>
>>> I've installed your driver. I have running my ISS on ID 2 (and have an 
>>> external temp sensor running on sensor 3).
>>>
>>> When ISS set to ID=2, I only seems to see internal sensor data, like:
>>>
>>> LOOP:   2020-06-27 10:37:51 CEST (1593247071) altimeter: 
>>> 1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247071, 
>>> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
>>> 27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
>>> rainRate: 0.0, usUnits: 17
>>> {'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
>>> LOOP:   2020-06-27 10:37:51 CEST (1593247071) dateTime: 1593247071, 
>>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>>> LOOP:   2020-06-27 10:37:53 CEST (1593247073) dateTime: 1593247073, 
>>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>>> LOOP:   2020-06-27 10:37:56 CEST (1593247076) dateTime: 1593247076, 
>>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>>> LOOP:   2020-06-27 10:37:58 CEST (1593247078) dateTime: 1593247078, 
>>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>>> LOOP:   2020-06-27 10:38:01 CEST (1593247081) dateTime: 1593247081, 
>>> maxSolarRad: None, rainRate: 0.0, 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-28 Thread flor...@pre-vost.fr
Hi Maarten,

To help Bastiaan and me to WLL Driver, can you share the answer of your 
request of http://1.2.3.4/v1/current_conditions (change 1.2.3.4 by your 
internal IP) ?
You've another sensor with other ID and it will be helpfull to have this 
data to implement it on driver,

Thank you ! 

Le samedi 27 juin 2020 à 10:53:21 UTC+2, flor...@pre-vost.fr a écrit :

> Hi,
>
> Baastian, yes of course, I think it a good idea to make a request using 
> weewx object to read the daily rain to the database and make a comparison 
> with the rainfall daily by the WLL but I need the help of @Tom Keffer for 
> this.
>
> For UnitUS, I know that if it possible but for readability, I decided to 
> make a conversion before yield the packet to the genlooppackets(). Also, 
> when i need to add record manual by using the method addRecords, I need to 
> put on the packet the right unit set in weewx.conf. If you've another 
> suggest, let me know :) 
>
> Maarten, I will fix this issue in few days, I know how can I do this by 
> search any key in each sensor :) 
>
> -fp
>
> Le samedi 27 juin 2020 à 10:40:09 UTC+2, hoev...@gmail.com a écrit :
>
>> Hello Bastiaan,
>>
>> The WLL is a wonderful piece of equipment. Now I can run production with 
>> WeeWX, and start a test-enviroment in a virtual machine, while talking to 
>> the same WLL.
>>
>> I've installed your driver. I have running my ISS on ID 2 (and have an 
>> external temp sensor running on sensor 3).
>>
>> When ISS set to ID=2, I only seems to see internal sensor data, like:
>>
>> LOOP:   2020-06-27 10:37:51 CEST (1593247071) altimeter: 
>> 1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247071, 
>> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
>> 27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
>> rainRate: 0.0, usUnits: 17
>> {'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
>> LOOP:   2020-06-27 10:37:51 CEST (1593247071) dateTime: 1593247071, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:37:53 CEST (1593247073) dateTime: 1593247073, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:37:56 CEST (1593247076) dateTime: 1593247076, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:37:58 CEST (1593247078) dateTime: 1593247078, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:01 CEST (1593247081) dateTime: 1593247081, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:03 CEST (1593247083) dateTime: 1593247083, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:06 CEST (1593247086) dateTime: 1593247086, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:06 CEST (1593247086) altimeter: 
>> 1008.6925672055719, barometer: 1009.04207968256, dateTime: 1593247086, 
>> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
>> 27.057, maxSolarRad: None, pressure: 1008.6018492219138, 
>> rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:08 CEST (1593247088) dateTime: 1593247088, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>>
>>
>>
>> When set ISS to ID=1, I see the same
>>
>> LOOP:   2020-06-27 10:38:56 CEST (1593247136) altimeter: 
>> 1008.7264350305117, barometer: 1009.075943564148, dateTime: 1593247136, 
>> inDewpoint: 17.22, inHumidity: 54.9, inTemp: 
>> 27.057, maxSolarRad: None, pressure: 1008.635713103502, 
>> rainRate: 0.0, usUnits: 17
>> {'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
>> LOOP:   2020-06-27 10:38:56 CEST (1593247136) dateTime: 1593247136, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:58 CEST (1593247138) dateTime: 1593247138, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:01 CEST (1593247141) dateTime: 1593247141, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:03 CEST (1593247143) dateTime: 1593247143, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:06 CEST (1593247146) dateTime: 1593247146, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:08 CEST (1593247148) dateTime: 1593247148, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:11 CEST (1593247151) dateTime: 1593247151, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:11 CEST (1593247151) altimeter: 
>> 1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247151, 
>> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
>> 27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
>> rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:13 CEST (1593247153) dateTime: 1593247153, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>>
>> Op zaterdag 27 juni 2020 om 10:17:55 UTC+2 schreef Bastiaan Meelberg:
>>
>>> Python is pretty new to me, I was unaware 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread flor...@pre-vost.fr
Hi,
Please keep one repo... how user can choose the right repo ?

I think it will be good to split code to one git.

Le samedi 27 juin 2020 à 10:53:21 UTC+2, flor...@pre-vost.fr a écrit :

> Hi,
>
> Baastian, yes of course, I think it a good idea to make a request using 
> weewx object to read the daily rain to the database and make a comparison 
> with the rainfall daily by the WLL but I need the help of @Tom Keffer for 
> this.
>
> For UnitUS, I know that if it possible but for readability, I decided to 
> make a conversion before yield the packet to the genlooppackets(). Also, 
> when i need to add record manual by using the method addRecords, I need to 
> put on the packet the right unit set in weewx.conf. If you've another 
> suggest, let me know :) 
>
> Maarten, I will fix this issue in few days, I know how can I do this by 
> search any key in each sensor :) 
>
> -fp
>
> Le samedi 27 juin 2020 à 10:40:09 UTC+2, hoev...@gmail.com a écrit :
>
>> Hello Bastiaan,
>>
>> The WLL is a wonderful piece of equipment. Now I can run production with 
>> WeeWX, and start a test-enviroment in a virtual machine, while talking to 
>> the same WLL.
>>
>> I've installed your driver. I have running my ISS on ID 2 (and have an 
>> external temp sensor running on sensor 3).
>>
>> When ISS set to ID=2, I only seems to see internal sensor data, like:
>>
>> LOOP:   2020-06-27 10:37:51 CEST (1593247071) altimeter: 
>> 1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247071, 
>> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
>> 27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
>> rainRate: 0.0, usUnits: 17
>> {'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
>> LOOP:   2020-06-27 10:37:51 CEST (1593247071) dateTime: 1593247071, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:37:53 CEST (1593247073) dateTime: 1593247073, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:37:56 CEST (1593247076) dateTime: 1593247076, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:37:58 CEST (1593247078) dateTime: 1593247078, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:01 CEST (1593247081) dateTime: 1593247081, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:03 CEST (1593247083) dateTime: 1593247083, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:06 CEST (1593247086) dateTime: 1593247086, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:06 CEST (1593247086) altimeter: 
>> 1008.6925672055719, barometer: 1009.04207968256, dateTime: 1593247086, 
>> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
>> 27.057, maxSolarRad: None, pressure: 1008.6018492219138, 
>> rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:08 CEST (1593247088) dateTime: 1593247088, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>>
>>
>>
>> When set ISS to ID=1, I see the same
>>
>> LOOP:   2020-06-27 10:38:56 CEST (1593247136) altimeter: 
>> 1008.7264350305117, barometer: 1009.075943564148, dateTime: 1593247136, 
>> inDewpoint: 17.22, inHumidity: 54.9, inTemp: 
>> 27.057, maxSolarRad: None, pressure: 1008.635713103502, 
>> rainRate: 0.0, usUnits: 17
>> {'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
>> LOOP:   2020-06-27 10:38:56 CEST (1593247136) dateTime: 1593247136, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:58 CEST (1593247138) dateTime: 1593247138, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:01 CEST (1593247141) dateTime: 1593247141, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:03 CEST (1593247143) dateTime: 1593247143, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:06 CEST (1593247146) dateTime: 1593247146, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:08 CEST (1593247148) dateTime: 1593247148, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:11 CEST (1593247151) dateTime: 1593247151, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:11 CEST (1593247151) altimeter: 
>> 1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247151, 
>> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
>> 27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
>> rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:13 CEST (1593247153) dateTime: 1593247153, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>>
>> Op zaterdag 27 juni 2020 om 10:17:55 UTC+2 schreef Bastiaan Meelberg:
>>
>>> Python is pretty new to me, I was unaware of the use of the _packet 
>>> underscore method. I will update my code. Thanks for the tip.
>>>
>>> Have a look at the rain calculations, I found out yesterday, during a 
>>> 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread flor...@pre-vost.fr
Please keep a one repo on github. If we are some repo, how the user can 
choose the right driver ?

It will be good to split

Le samedi 27 juin 2020 à 10:53:21 UTC+2, flor...@pre-vost.fr a écrit :

> Hi,
>
> Baastian, yes of course, I think it a good idea to make a request using 
> weewx object to read the daily rain to the database and make a comparison 
> with the rainfall daily by the WLL but I need the help of @Tom Keffer for 
> this.
>
> For UnitUS, I know that if it possible but for readability, I decided to 
> make a conversion before yield the packet to the genlooppackets(). Also, 
> when i need to add record manual by using the method addRecords, I need to 
> put on the packet the right unit set in weewx.conf. If you've another 
> suggest, let me know :) 
>
> Maarten, I will fix this issue in few days, I know how can I do this by 
> search any key in each sensor :) 
>
> -fp
>
> Le samedi 27 juin 2020 à 10:40:09 UTC+2, hoev...@gmail.com a écrit :
>
>> Hello Bastiaan,
>>
>> The WLL is a wonderful piece of equipment. Now I can run production with 
>> WeeWX, and start a test-enviroment in a virtual machine, while talking to 
>> the same WLL.
>>
>> I've installed your driver. I have running my ISS on ID 2 (and have an 
>> external temp sensor running on sensor 3).
>>
>> When ISS set to ID=2, I only seems to see internal sensor data, like:
>>
>> LOOP:   2020-06-27 10:37:51 CEST (1593247071) altimeter: 
>> 1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247071, 
>> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
>> 27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
>> rainRate: 0.0, usUnits: 17
>> {'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
>> LOOP:   2020-06-27 10:37:51 CEST (1593247071) dateTime: 1593247071, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:37:53 CEST (1593247073) dateTime: 1593247073, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:37:56 CEST (1593247076) dateTime: 1593247076, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:37:58 CEST (1593247078) dateTime: 1593247078, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:01 CEST (1593247081) dateTime: 1593247081, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:03 CEST (1593247083) dateTime: 1593247083, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:06 CEST (1593247086) dateTime: 1593247086, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:06 CEST (1593247086) altimeter: 
>> 1008.6925672055719, barometer: 1009.04207968256, dateTime: 1593247086, 
>> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
>> 27.057, maxSolarRad: None, pressure: 1008.6018492219138, 
>> rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:08 CEST (1593247088) dateTime: 1593247088, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>>
>>
>>
>> When set ISS to ID=1, I see the same
>>
>> LOOP:   2020-06-27 10:38:56 CEST (1593247136) altimeter: 
>> 1008.7264350305117, barometer: 1009.075943564148, dateTime: 1593247136, 
>> inDewpoint: 17.22, inHumidity: 54.9, inTemp: 
>> 27.057, maxSolarRad: None, pressure: 1008.635713103502, 
>> rainRate: 0.0, usUnits: 17
>> {'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
>> LOOP:   2020-06-27 10:38:56 CEST (1593247136) dateTime: 1593247136, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:38:58 CEST (1593247138) dateTime: 1593247138, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:01 CEST (1593247141) dateTime: 1593247141, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:03 CEST (1593247143) dateTime: 1593247143, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:06 CEST (1593247146) dateTime: 1593247146, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:08 CEST (1593247148) dateTime: 1593247148, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:11 CEST (1593247151) dateTime: 1593247151, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:11 CEST (1593247151) altimeter: 
>> 1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247151, 
>> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
>> 27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
>> rainRate: 0.0, usUnits: 17
>> LOOP:   2020-06-27 10:39:13 CEST (1593247153) dateTime: 1593247153, 
>> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>>
>> Op zaterdag 27 juni 2020 om 10:17:55 UTC+2 schreef Bastiaan Meelberg:
>>
>>> Python is pretty new to me, I was unaware of the use of the _packet 
>>> underscore method. I will update my code. Thanks for the tip.
>>>
>>> Have a look at the rain calculations, I found out yesterday, 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread flor...@pre-vost.fr
Hi,

Baastian, yes of course, I think it a good idea to make a request using 
weewx object to read the daily rain to the database and make a comparison 
with the rainfall daily by the WLL but I need the help of @Tom Keffer for 
this.

For UnitUS, I know that if it possible but for readability, I decided to 
make a conversion before yield the packet to the genlooppackets(). Also, 
when i need to add record manual by using the method addRecords, I need to 
put on the packet the right unit set in weewx.conf. If you've another 
suggest, let me know :) 

Maarten, I will fix this issue in few days, I know how can I do this by 
search any key in each sensor :) 

-fp

Le samedi 27 juin 2020 à 10:40:09 UTC+2, hoev...@gmail.com a écrit :

> Hello Bastiaan,
>
> The WLL is a wonderful piece of equipment. Now I can run production with 
> WeeWX, and start a test-enviroment in a virtual machine, while talking to 
> the same WLL.
>
> I've installed your driver. I have running my ISS on ID 2 (and have an 
> external temp sensor running on sensor 3).
>
> When ISS set to ID=2, I only seems to see internal sensor data, like:
>
> LOOP:   2020-06-27 10:37:51 CEST (1593247071) altimeter: 
> 1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247071, 
> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
> 27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
> rainRate: 0.0, usUnits: 17
> {'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
> LOOP:   2020-06-27 10:37:51 CEST (1593247071) dateTime: 1593247071, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:37:53 CEST (1593247073) dateTime: 1593247073, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:37:56 CEST (1593247076) dateTime: 1593247076, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:37:58 CEST (1593247078) dateTime: 1593247078, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:38:01 CEST (1593247081) dateTime: 1593247081, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:38:03 CEST (1593247083) dateTime: 1593247083, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:38:06 CEST (1593247086) dateTime: 1593247086, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:38:06 CEST (1593247086) altimeter: 
> 1008.6925672055719, barometer: 1009.04207968256, dateTime: 1593247086, 
> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
> 27.057, maxSolarRad: None, pressure: 1008.6018492219138, 
> rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:38:08 CEST (1593247088) dateTime: 1593247088, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>
>
>
> When set ISS to ID=1, I see the same
>
> LOOP:   2020-06-27 10:38:56 CEST (1593247136) altimeter: 
> 1008.7264350305117, barometer: 1009.075943564148, dateTime: 1593247136, 
> inDewpoint: 17.22, inHumidity: 54.9, inTemp: 
> 27.057, maxSolarRad: None, pressure: 1008.635713103502, 
> rainRate: 0.0, usUnits: 17
> {'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
> LOOP:   2020-06-27 10:38:56 CEST (1593247136) dateTime: 1593247136, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:38:58 CEST (1593247138) dateTime: 1593247138, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:39:01 CEST (1593247141) dateTime: 1593247141, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:39:03 CEST (1593247143) dateTime: 1593247143, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:39:06 CEST (1593247146) dateTime: 1593247146, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:39:08 CEST (1593247148) dateTime: 1593247148, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:39:11 CEST (1593247151) dateTime: 1593247151, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:39:11 CEST (1593247151) altimeter: 
> 1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247151, 
> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
> 27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
> rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:39:13 CEST (1593247153) dateTime: 1593247153, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>
> Op zaterdag 27 juni 2020 om 10:17:55 UTC+2 schreef Bastiaan Meelberg:
>
>> Python is pretty new to me, I was unaware of the use of the _packet 
>> underscore method. I will update my code. Thanks for the tip.
>>
>> Have a look at the rain calculations, I found out yesterday, during a 
>> rain shower, setting  the self.rain_previous_period to zero is not a 
>> good idea. If weewx is reloading the diver (and it does) it will add the 
>> daily rain as a whole new rainfall. I will update my repo during the day.
>>
>> Also at midnight WLL will reset the rain_daily, so at that moment the 
>> 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread Bastiaan Meelberg
Yes! That will do the trick for now.

Keep in mind that the rain count in the current repo is Wrong! I will post 
an updated one soon.



On Saturday, June 27, 2020 at 10:46:45 AM UTC+2, Maarten van der Hoeven 
wrote:
>
> @Bastiaan, when I change this piece of code (txid=2), it is retrieving 
> live data from ISS:
>
> def DecodeDataWLL(self, data): 
> timestamp = data['ts'] 
> packet = {'dateTime': timestamp, 'usUnits': weewx.US} 
>
> for condition in data['conditions']: 
>   if condition["data_structure_type"] == 1 and 
> *condition['txid'] 
> == 2:* 
>
>>
>

-- 
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/698d4e2f-e3c5-43dd-aa70-76e9a2938ec3o%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread Bastiaan Meelberg
Hello Maarten,

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


   - 

{
  "data": {
"did": "001D0A7104C8",
"ts": 1593247405,
"conditions": [
  {
"lsid": 242741,
"data_structure_type": 1,
"txid": 1,
"temp": 73.6,
"hum": 81.3,
"dew_point": 67.5,
"wet_bulb": 69.1,
"heat_index": 75.6,
"wind_chill": 73.6,
"thw_index": 75.6,
"thsw_index": 85,
"wind_speed_last": 2,
"wind_dir_last": 198,
"wind_speed_avg_last_1_min": 2.37,
"wind_dir_scalar_avg_last_1_min": 174,
"wind_speed_avg_last_2_min": 2.37,
"wind_dir_scalar_avg_last_2_min": 170,
"wind_speed_hi_last_2_min": 4,
"wind_dir_at_hi_speed_last_2_min": 110,
"wind_speed_avg_last_10_min": 1.68,
"wind_dir_scalar_avg_last_10_min": 187,
"wind_speed_hi_last_10_min": 5,
"wind_dir_at_hi_speed_last_10_min": 190,
"rain_size": 2,
"rain_rate_last": 0,
"rain_rate_hi": 0,
"rainfall_last_15_min": 0,
"rain_rate_hi_last_15_min": 0,
"rainfall_last_60_min": 0,
"rainfall_last_24_hr": 25,
"rain_storm": 25,
"rain_storm_start_at": 1593206161,
"solar_rad": 496,
"uv_index": 3.4,
"rx_state": 0,
"trans_battery_flag": 0,
"rainfall_daily": 20,
"rainfall_monthly": 325,
"rainfall_year": 1694,
"rain_storm_last": 46,
"rain_storm_last_start_at": 1592308741,
"rain_storm_last_end_at": 1592553661
  },
  {
"lsid": 242760,
"data_structure_type": 1,
"txid": 4,
"temp": null,
"hum": null,
"dew_point": null,
"wet_bulb": null,
"heat_index": null,
"wind_chill": null,
"thw_index": null,
"thsw_index": null,
"wind_speed_last": 2,
"wind_dir_last": 198,
"wind_speed_avg_last_1_min": 2.37,
"wind_dir_scalar_avg_last_1_min": 174,
"wind_speed_avg_last_2_min": 2.37,
"wind_dir_scalar_avg_last_2_min": 170,
"wind_speed_hi_last_2_min": 4,
"wind_dir_at_hi_speed_last_2_min": 110,
"wind_speed_avg_last_10_min": 1.68,
"wind_dir_scalar_avg_last_10_min": 187,
"wind_speed_hi_last_10_min": 5,
"wind_dir_at_hi_speed_last_10_min": 190,
"rain_size": 1,
"rain_rate_last": 0,
"rain_rate_hi": 0,
"rainfall_last_15_min": 0,
"rain_rate_hi_last_15_min": 0,
"rainfall_last_60_min": 0,
"rainfall_last_24_hr": 0,
"rain_storm": null,
"rain_storm_start_at": null,
"solar_rad": null,
"uv_index": null,
"rx_state": 0,
"trans_battery_flag": 0,
"rainfall_daily": 0,
"rainfall_monthly": 0,
"rainfall_year": 0,
"rain_storm_last": null,
"rain_storm_last_start_at": null,
"rain_storm_last_end_at": null
  },
  {
"lsid": 242740,
"data_structure_type": 4,
"temp_in": 76.7,
"hum_in": 55.3,
"dew_point_in": 59.5,
"heat_index_in": 77.2
  },
  {
"lsid": 242739,
"data_structure_type": 3,
"bar_sea_level": 29.809,
"bar_trend": -0.007,
"bar_absolute": 29.707
  }
]
  },
  "error": null
}



A fully customisable tx_id configurator is on my to_do list. Can you post 
you're current_condtition JSON, so I can have a look.  



On Saturday, June 27, 2020 at 10:40:09 AM UTC+2, Maarten van der Hoeven 
wrote:
>
> Hello Bastiaan,
>
> The WLL is a wonderful piece of equipment. Now I can run production with 
> WeeWX, and start a test-enviroment in a virtual machine, while talking to 
> the same WLL.
>
> I've installed your driver. I have running my ISS on ID 2 (and have an 
> external temp sensor running on sensor 3).
>
> When ISS set to ID=2, I only seems to see internal sensor data, like:
>
> LOOP:   2020-06-27 10:37:51 CEST (1593247071) altimeter: 
> 1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247071, 
> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
> 27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
> rainRate: 0.0, usUnits: 17
> {'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
> LOOP:   2020-06-27 10:37:51 CEST (1593247071) dateTime: 1593247071, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:37:53 CEST (1593247073) dateTime: 1593247073, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:37:56 CEST (1593247076) dateTime: 1593247076, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:37:58 CEST (1593247078) dateTime: 1593247078, 
> 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread Maarten van der Hoeven
@Bastiaan, when I change this piece of code (txid=2), it is retrieving live 
data from ISS:

def DecodeDataWLL(self, data): 
timestamp = data['ts'] 
packet = {'dateTime': timestamp, 'usUnits': weewx.US} 

for condition in data['conditions']: 
  if condition["data_structure_type"] == 1 and 
*condition['txid'] 
== 2:* 

Op zaterdag 27 juni 2020 om 10:40:09 UTC+2 schreef Maarten van der Hoeven:

> Hello Bastiaan,
>
> The WLL is a wonderful piece of equipment. Now I can run production with 
> WeeWX, and start a test-enviroment in a virtual machine, while talking to 
> the same WLL.
>
> I've installed your driver. I have running my ISS on ID 2 (and have an 
> external temp sensor running on sensor 3).
>
> When ISS set to ID=2, I only seems to see internal sensor data, like:
>
> LOOP:   2020-06-27 10:37:51 CEST (1593247071) altimeter: 
> 1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247071, 
> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
> 27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
> rainRate: 0.0, usUnits: 17
> {'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
> LOOP:   2020-06-27 10:37:51 CEST (1593247071) dateTime: 1593247071, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:37:53 CEST (1593247073) dateTime: 1593247073, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:37:56 CEST (1593247076) dateTime: 1593247076, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:37:58 CEST (1593247078) dateTime: 1593247078, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:38:01 CEST (1593247081) dateTime: 1593247081, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:38:03 CEST (1593247083) dateTime: 1593247083, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:38:06 CEST (1593247086) dateTime: 1593247086, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:38:06 CEST (1593247086) altimeter: 
> 1008.6925672055719, barometer: 1009.04207968256, dateTime: 1593247086, 
> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
> 27.057, maxSolarRad: None, pressure: 1008.6018492219138, 
> rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:38:08 CEST (1593247088) dateTime: 1593247088, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>
>
>
> When set ISS to ID=1, I see the same
>
> LOOP:   2020-06-27 10:38:56 CEST (1593247136) altimeter: 
> 1008.7264350305117, barometer: 1009.075943564148, dateTime: 1593247136, 
> inDewpoint: 17.22, inHumidity: 54.9, inTemp: 
> 27.057, maxSolarRad: None, pressure: 1008.635713103502, 
> rainRate: 0.0, usUnits: 17
> {'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
> LOOP:   2020-06-27 10:38:56 CEST (1593247136) dateTime: 1593247136, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:38:58 CEST (1593247138) dateTime: 1593247138, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:39:01 CEST (1593247141) dateTime: 1593247141, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:39:03 CEST (1593247143) dateTime: 1593247143, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:39:06 CEST (1593247146) dateTime: 1593247146, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:39:08 CEST (1593247148) dateTime: 1593247148, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:39:11 CEST (1593247151) dateTime: 1593247151, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:39:11 CEST (1593247151) altimeter: 
> 1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247151, 
> inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
> 27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
> rainRate: 0.0, usUnits: 17
> LOOP:   2020-06-27 10:39:13 CEST (1593247153) dateTime: 1593247153, 
> maxSolarRad: None, rainRate: 0.0, usUnits: 17
>
> Op zaterdag 27 juni 2020 om 10:17:55 UTC+2 schreef Bastiaan Meelberg:
>
>> Python is pretty new to me, I was unaware of the use of the _packet 
>> underscore method. I will update my code. Thanks for the tip.
>>
>> Have a look at the rain calculations, I found out yesterday, during a 
>> rain shower, setting  the self.rain_previous_period to zero is not a 
>> good idea. If weewx is reloading the diver (and it does) it will add the 
>> daily rain as a whole new rainfall. I will update my repo during the day.
>>
>> Also at midnight WLL will reset the rain_daily, so at that moment the 
>> rain_previous must be reset.
>>
>> I also don't think you need to do all the METRIC and METRICWX 
>> conversions. Weewx will do that for you, if you set the 'usUnits': 
>> weewx.US  in the _packet. The LOOP will be generated and weewx is adding 
>> the record using the set database 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread Maarten van der Hoeven
Hello Bastiaan,

The WLL is a wonderful piece of equipment. Now I can run production with 
WeeWX, and start a test-enviroment in a virtual machine, while talking to 
the same WLL.

I've installed your driver. I have running my ISS on ID 2 (and have an 
external temp sensor running on sensor 3).

When ISS set to ID=2, I only seems to see internal sensor data, like:

LOOP:   2020-06-27 10:37:51 CEST (1593247071) altimeter: 
1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247071, 
inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
rainRate: 0.0, usUnits: 17
{'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
LOOP:   2020-06-27 10:37:51 CEST (1593247071) dateTime: 1593247071, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:37:53 CEST (1593247073) dateTime: 1593247073, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:37:56 CEST (1593247076) dateTime: 1593247076, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:37:58 CEST (1593247078) dateTime: 1593247078, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:38:01 CEST (1593247081) dateTime: 1593247081, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:38:03 CEST (1593247083) dateTime: 1593247083, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:38:06 CEST (1593247086) dateTime: 1593247086, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:38:06 CEST (1593247086) altimeter: 
1008.6925672055719, barometer: 1009.04207968256, dateTime: 1593247086, 
inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
27.057, maxSolarRad: None, pressure: 1008.6018492219138, 
rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:38:08 CEST (1593247088) dateTime: 1593247088, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17



When set ISS to ID=1, I see the same

LOOP:   2020-06-27 10:38:56 CEST (1593247136) altimeter: 
1008.7264350305117, barometer: 1009.075943564148, dateTime: 1593247136, 
inDewpoint: 17.22, inHumidity: 54.9, inTemp: 
27.057, maxSolarRad: None, pressure: 1008.635713103502, 
rainRate: 0.0, usUnits: 17
{'data': {'broadcast_port': 2, 'duration': 3600}, 'error': None}
LOOP:   2020-06-27 10:38:56 CEST (1593247136) dateTime: 1593247136, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:38:58 CEST (1593247138) dateTime: 1593247138, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:39:01 CEST (1593247141) dateTime: 1593247141, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:39:03 CEST (1593247143) dateTime: 1593247143, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:39:06 CEST (1593247146) dateTime: 1593247146, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:39:08 CEST (1593247148) dateTime: 1593247148, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:39:11 CEST (1593247151) dateTime: 1593247151, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:39:11 CEST (1593247151) altimeter: 
1008.6586993806619, barometer: 1009.0082158009718, dateTime: 1593247151, 
inDewpoint: 17.28, inHumidity: 55.1, inTemp: 
27.057, maxSolarRad: None, pressure: 1008.5679853403257, 
rainRate: 0.0, usUnits: 17
LOOP:   2020-06-27 10:39:13 CEST (1593247153) dateTime: 1593247153, 
maxSolarRad: None, rainRate: 0.0, usUnits: 17

Op zaterdag 27 juni 2020 om 10:17:55 UTC+2 schreef Bastiaan Meelberg:

> Python is pretty new to me, I was unaware of the use of the _packet 
> underscore method. I will update my code. Thanks for the tip.
>
> Have a look at the rain calculations, I found out yesterday, during a rain 
> shower, setting  the self.rain_previous_period to zero is not a good 
> idea. If weewx is reloading the diver (and it does) it will add the daily 
> rain as a whole new rainfall. I will update my repo during the day.
>
> Also at midnight WLL will reset the rain_daily, so at that moment the 
> rain_previous must be reset.
>
> I also don't think you need to do all the METRIC and METRICWX conversions. 
> Weewx will do that for you, if you set the 'usUnits': weewx.US  in the 
> _packet. The LOOP will be generated and weewx is adding the record using 
> the set database metrics.
>
>
>
> On Friday, June 26, 2020 at 6:56:18 PM UTC+2, flor...@pre-vost.fr wrote:
>>
>> Hi everyone and thank you for your support ! I'm very glade to know that 
>> people want to make this driver because there are not a lot.
>>
>> This is my repo :  https://github.com/Drealine/WLLDriver 
>>
>> @Bastiaan it's very nice ! Just, why you use update packet or not simply 
>> do a for _packet in blabla(): It's a udp protocol ?
>>
>> With my driver, you can retrive lost data by using API v2 of Weatherlink. 
>> Depend to your subscription.
>>
>> Glad to work with you, and if you want, it will be 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-27 Thread Bastiaan Meelberg
Python is pretty new to me, I was unaware of the use of the _packet 
underscore method. I will update my code. Thanks for the tip.

Have a look at the rain calculations, I found out yesterday, during a rain 
shower, setting  the self.rain_previous_period to zero is not a good idea. 
If weewx is reloading the diver (and it does) it will add the daily rain as 
a whole new rainfall. I will update my repo during the day.

Also at midnight WLL will reset the rain_daily, so at that moment the 
rain_previous must be reset.

I also don't think you need to do all the METRIC and METRICWX conversions. 
Weewx will do that for you, if you set the 'usUnits': weewx.US  in the 
_packet. The LOOP will be generated and weewx is adding the record using 
the set database metrics.



On Friday, June 26, 2020 at 6:56:18 PM UTC+2, flor...@pre-vost.fr wrote:
>
> Hi everyone and thank you for your support ! I'm very glade to know that 
> people want to make this driver because there are not a lot.
>
> This is my repo :  https://github.com/Drealine/WLLDriver 
>
> @Bastiaan it's very nice ! Just, why you use update packet or not simply 
> do a for _packet in blabla(): It's a udp protocol ?
>
> With my driver, you can retrive lost data by using API v2 of Weatherlink. 
> Depend to your subscription.
>
> Glad to work with you, and if you want, it will be more often that split 
> some git to one. 
>
> Regards, -fp 
>
> Le vendredi 26 juin 2020 à 18:35:45 UTC+2, Bastiaan Meelberg a écrit :
>
>> Hi, 
>>
>> I’m also working on a wll driver, including The 2,5 UDP packages. It is 
>> running now for a few days with good results (no rain check yet). 
>> The integration with the online fetch sounds interesting! 
>> This is my git fork: 
>> https://github.com/grebleem/WeatherLinkliveUDP 
>>
>> It is feeding my site: https://meteo-otterlo.nl 
>>
>> Cheers, 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/073ec2e6-6d1e-4947-82e2-51d9f1dd4ff2o%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Maarten van der Hoeven
On sensor 1, sensor_type 242 I have:

bar_absolute 29.799
bar_hi_at1593193506
bar_sea_level29.812
arch_int300
bar_lo29.812
bar_hi29.818
bar_lo_at1593193598
ts1593193800

On sensor 2, sensor_type 242 I have:

temp_in_lo_at1593193748
arch_int300
temp_in_hi95.4
temp_in_hi_at1593193508
hum_in_hi38.2
temp_in_last95
temp_in_lo94.9
hum_in_lo37.6
hum_in_last38.2
dew_point_in65.6
hum_in_lo_at1593193508
heat_index_in98.2
hum_in_hi_at1593193748
ts1593193800

On sensor 2, sensor_type 242 I have:

wind_speed_avgnull
dew_point_hi_atnull
supercap_volt_lastnull
uv_dosenull
wind_chill_lastnull
solar_rad_hinull
solar_volt_lastnull
dew_point_lo_atnull
thsw_index_hi_atnull
dew_point_lastnull
rain_size1
thsw_index_lonull
uv_index_hinull
thsw_index_hinull
thsw_index_lo_atnull
solar_rad_hi_at1593193800
heat_index_hinull
arch_int300
good_packets_streak33
wind_runnull
rain_rate_hi_at1593193508
tx_id3
temp_hi83.2
temp_lo82.8
wind_dir_of_prevailnull
thw_index_lastnull
rain_rate_hi_clicks0
etnull
rainfall_in0
wind_chill_lo_atnull
rainfall_mm0
wet_bulb_lastnull
trans_batterynull
rain_rate_hi_in0
hum_lonull
heat_index_lastnull
hum_hinull
heat_index_hi_atnull
rain_rate_hi_mm0
rainfall_clicks0
wet_bulb_hi_at1593180160
solar_rad_volt_last12
wind_speed_hinull
temp_last82.8
temp_avg82.9
trans_battery_flag0
hum_lastnull
wind_chill_lonull
wet_bulb_hinull
wind_speed_hi_atnull
reception98
wet_bulb_lo_atnull
solar_rad_avgnull
error_packets0
afc-2
cooling_degree_days0.061805565
rssi-80
wet_bulb_lonull
wind_speed_hi_dirnull
temp_lo_at1593193685
dew_point_hinull
thw_index_lonull
uv_index_hi_atnull
dew_point_lonull
solar_energynull
resynchs0
temp_hi_at1593193513
thw_index_hinull
hum_lo_atnull
thw_index_lo_atnull
thw_index_hi_atnull
thsw_index_lastnull
hum_hi_atnull
uv_index_avgnull
uv_volt_last3
heating_degree_days0
ts1593193800


Op vrijdag 26 juni 2020 om 23:26:59 UTC+2 schreef Maarten van der Hoeven:

> Doh!!! That makes a difference. Sigh...
>
> Progress now, but an new failure
>
> Jun 26 23:21:16 ubuntu weewx[5603] INFO user.WLLDriver: Failure to get 
> data 
> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593206474=159312=1593206400=ae70c3c915ea7c2a0d01250a291f962f0f75bcddf925f27ba39389e1a3ffa875
>  
> - try 3 - ('bar_sea_level')
>
> URL response. JSON response is very long. What part do you want to see? 
> Small part:
>
>
> 1
>
> bar_absolute
> 30.002
> bar_hi_at
> 1593120400
> bar_sea_level
> 30.015
> arch_int
> 300
> bar_lo
> 30.011
> bar_hi
> 30.016
> bar_lo_at
> 1593120430
> ts
> 1593120600
>
> Op vrijdag 26 juni 2020 om 23:15:11 UTC+2 schreef Maarten van der Hoeven:
>
>> Here is my driver-config. api-secret is set (although I've changed it a 
>> bit in this copy below):
>>
>> [WLLDriver]
>> driver = user.WLLDriver
>> max_tries = 5
>> retry_wait = 10
>> poll_interval = 5
>> url = http://192.168.2.33:80/v1/current_conditions
>> wl_apikey = nivwsekqwfbkhqtqwo8nximhl7zgxpcs
>> wl _apisecret = x6omxelabcdefgbn1ef1msbqfdmiwgys
>> wl_stationid = 91978
>> wl_archive_interval = 5
>>
>> Op vrijdag 26 juni 2020 om 23:12:17 UTC+2 schreef flor...@pre-vost.fr:
>>
>>> Do you've set the api secret ? 
>>>
>>> Le vendredi 26 juin 2020 à 23:09:59 UTC+2, hoev...@gmail.com a écrit :
>>>
 Hmmm, not sure. Looks like time is right to me

 root@ubuntu:/etc/weewx# date
 Fri 26 Jun 2020 11:08:42 PM CEST
 root@ubuntu:/etc/weewx# 



 Op vrijdag 26 juni 2020 om 23:07:24 UTC+2 schreef flor...@pre-vost.fr:

> Check your time server. It appear that is not correctly set and the 
> API return a wrong time when you request API
>
> Le vendredi 26 juin 2020 à 23:04:35 UTC+2, hoev...@gmail.com a écrit :
>
>> Okay, URL and responses
>>
>>
>> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c
>>
>> code
>> "401"
>> message
>> "Invalid API Signature."
>>
>>
>>
>> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c
>>
>> code
>> "401"
>> message
>> "Invalid API Signature."
>>
>>
>>
>> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205153=1593118500=1593204900=ae52423cb4b1756a678979aeffe0817d424a26cb5b1b416d0bb40b0838c179da
>>
>> code
>> "401"
>> message
>> "Invalid API Signature."
>>
>> Op vrijdag 26 juni 2020 om 22:58:12 UTC+2 schreef flor...@pre-vost.fr
>> :
>>
>>> No, I would like just to restart weewx and when debug mode show URL 
>>> API, request this link on your favorite browser and put on comment the 
>>> result
>>>
>>> Le vendredi 26 juin 2020 à 22:54:19 UTC+2, hoev...@gmail.com a 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Maarten van der Hoeven
Doh!!! That makes a difference. Sigh...

Progress now, but an new failure

Jun 26 23:21:16 ubuntu weewx[5603] INFO user.WLLDriver: Failure to get data 
https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593206474=159312=1593206400=ae70c3c915ea7c2a0d01250a291f962f0f75bcddf925f27ba39389e1a3ffa875
 
- try 3 - ('bar_sea_level')

URL response. JSON response is very long. What part do you want to see? 
Small part:


1

bar_absolute
30.002
bar_hi_at
1593120400
bar_sea_level
30.015
arch_int
300
bar_lo
30.011
bar_hi
30.016
bar_lo_at
1593120430
ts
1593120600

Op vrijdag 26 juni 2020 om 23:15:11 UTC+2 schreef Maarten van der Hoeven:

> Here is my driver-config. api-secret is set (although I've changed it a 
> bit in this copy below):
>
> [WLLDriver]
> driver = user.WLLDriver
> max_tries = 5
> retry_wait = 10
> poll_interval = 5
> url = http://192.168.2.33:80/v1/current_conditions
> wl_apikey = nivwsekqwfbkhqtqwo8nximhl7zgxpcs
> wl _apisecret = x6omxelabcdefgbn1ef1msbqfdmiwgys
> wl_stationid = 91978
> wl_archive_interval = 5
>
> Op vrijdag 26 juni 2020 om 23:12:17 UTC+2 schreef flor...@pre-vost.fr:
>
>> Do you've set the api secret ? 
>>
>> Le vendredi 26 juin 2020 à 23:09:59 UTC+2, hoev...@gmail.com a écrit :
>>
>>> Hmmm, not sure. Looks like time is right to me
>>>
>>> root@ubuntu:/etc/weewx# date
>>> Fri 26 Jun 2020 11:08:42 PM CEST
>>> root@ubuntu:/etc/weewx# 
>>>
>>>
>>>
>>> Op vrijdag 26 juni 2020 om 23:07:24 UTC+2 schreef flor...@pre-vost.fr:
>>>
 Check your time server. It appear that is not correctly set and the API 
 return a wrong time when you request API

 Le vendredi 26 juin 2020 à 23:04:35 UTC+2, hoev...@gmail.com a écrit :

> Okay, URL and responses
>
>
> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c
>
> code
> "401"
> message
> "Invalid API Signature."
>
>
>
> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c
>
> code
> "401"
> message
> "Invalid API Signature."
>
>
>
> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205153=1593118500=1593204900=ae52423cb4b1756a678979aeffe0817d424a26cb5b1b416d0bb40b0838c179da
>
> code
> "401"
> message
> "Invalid API Signature."
>
> Op vrijdag 26 juni 2020 om 22:58:12 UTC+2 schreef flor...@pre-vost.fr:
>
>> No, I would like just to restart weewx and when debug mode show URL 
>> API, request this link on your favorite browser and put on comment the 
>> result
>>
>> Le vendredi 26 juin 2020 à 22:54:19 UTC+2, hoev...@gmail.com a 
>> écrit :
>>
>>> Or do you mean running weewx standalone?
>>>
>>> Parameter name: "api-key" has value 
>>> "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
>>> Parameter name: "api-secret" has value "ABC123"
>>> Parameter name: "end-timestamp" has value "1593204600"
>>> Parameter name: "start-timestamp" has value "1593118200"
>>> Parameter name: "station-id" has value "91978"
>>> Parameter name: "t" has value "1593204804"
>>> Parameter name: "api-key" has value 
>>> "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
>>> Parameter name: "api-secret" has value "ABC123"
>>> Parameter name: "end-timestamp" has value "1593204600"
>>> Parameter name: "start-timestamp" has value "1593118200"
>>> Parameter name: "station-id" has value "91978"
>>> Parameter name: "t" has value "1593204816"
>>>
>>> Op vrijdag 26 juni 2020 om 22:45:24 UTC+2 schreef Maarten van der 
>>> Hoeven:
>>>
 I've got weewx already on debug. Or do you mean something else?

 # WEEWX CONFIGURATION FILE


 ##

 # This section is for general configuration information.

 # Set to 1 for extra debug info, otherwise comment it out or set to 
 zero
 debug = 1

 # Root directory of the weewx data file hierarchy for this station
 WEEWX_ROOT = /

 # Whether to log successful operations
 log_success = True

 # Whether to log unsuccessful operations
 log_failure = True

 # How long to wait before timing out a socket (FTP, HTTP) connection
 socket_timeout = 20

 # Do not modify this. It is used when installing and updating weewx.
 version = 4.1.1

 Op vrijdag 26 juni 2020 om 22:35:10 UTC+2 schreef 
 flor...@pre-vost.fr:

> Relaunch weewx and use the url on debug. Here, 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread flor...@pre-vost.fr
you've a space :*wl _apisecret* = x6omxelabcdefgbn1ef1msbqfdmiwgys 

correct :   *wl_apisecret* = x6omxelabcdefgbn1ef1msbqfdmiwgys 

Le vendredi 26 juin 2020 à 23:15:11 UTC+2, hoev...@gmail.com a écrit :

> Here is my driver-config. api-secret is set (although I've changed it a 
> bit in this copy below):
>
> [WLLDriver]
> driver = user.WLLDriver
> max_tries = 5
> retry_wait = 10
> poll_interval = 5
> url = http://192.168.2.33:80/v1/current_conditions
> wl_apikey = nivwsekqwfbkhqtqwo8nximhl7zgxpcs
> wl _apisecret = x6omxelabcdefgbn1ef1msbqfdmiwgys
> wl_stationid = 91978
> wl_archive_interval = 5
>
> Op vrijdag 26 juni 2020 om 23:12:17 UTC+2 schreef flor...@pre-vost.fr:
>
>> Do you've set the api secret ? 
>>
>> Le vendredi 26 juin 2020 à 23:09:59 UTC+2, hoev...@gmail.com a écrit :
>>
>>> Hmmm, not sure. Looks like time is right to me
>>>
>>> root@ubuntu:/etc/weewx# date
>>> Fri 26 Jun 2020 11:08:42 PM CEST
>>> root@ubuntu:/etc/weewx# 
>>>
>>>
>>>
>>> Op vrijdag 26 juni 2020 om 23:07:24 UTC+2 schreef flor...@pre-vost.fr:
>>>
 Check your time server. It appear that is not correctly set and the API 
 return a wrong time when you request API

 Le vendredi 26 juin 2020 à 23:04:35 UTC+2, hoev...@gmail.com a écrit :

> Okay, URL and responses
>
>
> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c
>
> code
> "401"
> message
> "Invalid API Signature."
>
>
>
> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c
>
> code
> "401"
> message
> "Invalid API Signature."
>
>
>
> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205153=1593118500=1593204900=ae52423cb4b1756a678979aeffe0817d424a26cb5b1b416d0bb40b0838c179da
>
> code
> "401"
> message
> "Invalid API Signature."
>
> Op vrijdag 26 juni 2020 om 22:58:12 UTC+2 schreef flor...@pre-vost.fr:
>
>> No, I would like just to restart weewx and when debug mode show URL 
>> API, request this link on your favorite browser and put on comment the 
>> result
>>
>> Le vendredi 26 juin 2020 à 22:54:19 UTC+2, hoev...@gmail.com a 
>> écrit :
>>
>>> Or do you mean running weewx standalone?
>>>
>>> Parameter name: "api-key" has value 
>>> "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
>>> Parameter name: "api-secret" has value "ABC123"
>>> Parameter name: "end-timestamp" has value "1593204600"
>>> Parameter name: "start-timestamp" has value "1593118200"
>>> Parameter name: "station-id" has value "91978"
>>> Parameter name: "t" has value "1593204804"
>>> Parameter name: "api-key" has value 
>>> "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
>>> Parameter name: "api-secret" has value "ABC123"
>>> Parameter name: "end-timestamp" has value "1593204600"
>>> Parameter name: "start-timestamp" has value "1593118200"
>>> Parameter name: "station-id" has value "91978"
>>> Parameter name: "t" has value "1593204816"
>>>
>>> Op vrijdag 26 juni 2020 om 22:45:24 UTC+2 schreef Maarten van der 
>>> Hoeven:
>>>
 I've got weewx already on debug. Or do you mean something else?

 # WEEWX CONFIGURATION FILE


 ##

 # This section is for general configuration information.

 # Set to 1 for extra debug info, otherwise comment it out or set to 
 zero
 debug = 1

 # Root directory of the weewx data file hierarchy for this station
 WEEWX_ROOT = /

 # Whether to log successful operations
 log_success = True

 # Whether to log unsuccessful operations
 log_failure = True

 # How long to wait before timing out a socket (FTP, HTTP) connection
 socket_timeout = 20

 # Do not modify this. It is used when installing and updating weewx.
 version = 4.1.1

 Op vrijdag 26 juni 2020 om 22:35:10 UTC+2 schreef 
 flor...@pre-vost.fr:

> Relaunch weewx and use the url on debug. Here, the url is not in 
> the current timestamp. It for this thay you've this error.



-- 
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 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Maarten van der Hoeven
Here is my driver-config. api-secret is set (although I've changed it a bit 
in this copy below):

[WLLDriver]
driver = user.WLLDriver
max_tries = 5
retry_wait = 10
poll_interval = 5
url = http://192.168.2.33:80/v1/current_conditions
wl_apikey = nivwsekqwfbkhqtqwo8nximhl7zgxpcs
wl _apisecret = x6omxelabcdefgbn1ef1msbqfdmiwgys
wl_stationid = 91978
wl_archive_interval = 5

Op vrijdag 26 juni 2020 om 23:12:17 UTC+2 schreef flor...@pre-vost.fr:

> Do you've set the api secret ? 
>
> Le vendredi 26 juin 2020 à 23:09:59 UTC+2, hoev...@gmail.com a écrit :
>
>> Hmmm, not sure. Looks like time is right to me
>>
>> root@ubuntu:/etc/weewx# date
>> Fri 26 Jun 2020 11:08:42 PM CEST
>> root@ubuntu:/etc/weewx# 
>>
>>
>>
>> Op vrijdag 26 juni 2020 om 23:07:24 UTC+2 schreef flor...@pre-vost.fr:
>>
>>> Check your time server. It appear that is not correctly set and the API 
>>> return a wrong time when you request API
>>>
>>> Le vendredi 26 juin 2020 à 23:04:35 UTC+2, hoev...@gmail.com a écrit :
>>>
 Okay, URL and responses


 https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c

 code
 "401"
 message
 "Invalid API Signature."



 https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c

 code
 "401"
 message
 "Invalid API Signature."



 https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205153=1593118500=1593204900=ae52423cb4b1756a678979aeffe0817d424a26cb5b1b416d0bb40b0838c179da

 code
 "401"
 message
 "Invalid API Signature."

 Op vrijdag 26 juni 2020 om 22:58:12 UTC+2 schreef flor...@pre-vost.fr:

> No, I would like just to restart weewx and when debug mode show URL 
> API, request this link on your favorite browser and put on comment the 
> result
>
> Le vendredi 26 juin 2020 à 22:54:19 UTC+2, hoev...@gmail.com a écrit :
>
>> Or do you mean running weewx standalone?
>>
>> Parameter name: "api-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
>> Parameter name: "api-secret" has value "ABC123"
>> Parameter name: "end-timestamp" has value "1593204600"
>> Parameter name: "start-timestamp" has value "1593118200"
>> Parameter name: "station-id" has value "91978"
>> Parameter name: "t" has value "1593204804"
>> Parameter name: "api-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
>> Parameter name: "api-secret" has value "ABC123"
>> Parameter name: "end-timestamp" has value "1593204600"
>> Parameter name: "start-timestamp" has value "1593118200"
>> Parameter name: "station-id" has value "91978"
>> Parameter name: "t" has value "1593204816"
>>
>> Op vrijdag 26 juni 2020 om 22:45:24 UTC+2 schreef Maarten van der 
>> Hoeven:
>>
>>> I've got weewx already on debug. Or do you mean something else?
>>>
>>> # WEEWX CONFIGURATION FILE
>>>
>>>
>>> ##
>>>
>>> # This section is for general configuration information.
>>>
>>> # Set to 1 for extra debug info, otherwise comment it out or set to 
>>> zero
>>> debug = 1
>>>
>>> # Root directory of the weewx data file hierarchy for this station
>>> WEEWX_ROOT = /
>>>
>>> # Whether to log successful operations
>>> log_success = True
>>>
>>> # Whether to log unsuccessful operations
>>> log_failure = True
>>>
>>> # How long to wait before timing out a socket (FTP, HTTP) connection
>>> socket_timeout = 20
>>>
>>> # Do not modify this. It is used when installing and updating weewx.
>>> version = 4.1.1
>>>
>>> Op vrijdag 26 juni 2020 om 22:35:10 UTC+2 schreef 
>>> flor...@pre-vost.fr:
>>>
 Relaunch weewx and use the url on debug. Here, the url is not in 
 the current timestamp. It for this thay you've this error.
>>>
>>>

-- 
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/ae406b56-fa43-439a-b6b0-e7064d819a49n%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread flor...@pre-vost.fr
Do you've set the api secret ? 

Le vendredi 26 juin 2020 à 23:09:59 UTC+2, hoev...@gmail.com a écrit :

> Hmmm, not sure. Looks like time is right to me
>
> root@ubuntu:/etc/weewx# date
> Fri 26 Jun 2020 11:08:42 PM CEST
> root@ubuntu:/etc/weewx# 
>
>
>
> Op vrijdag 26 juni 2020 om 23:07:24 UTC+2 schreef flor...@pre-vost.fr:
>
>> Check your time server. It appear that is not correctly set and the API 
>> return a wrong time when you request API
>>
>> Le vendredi 26 juin 2020 à 23:04:35 UTC+2, hoev...@gmail.com a écrit :
>>
>>> Okay, URL and responses
>>>
>>>
>>> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c
>>>
>>> code
>>> "401"
>>> message
>>> "Invalid API Signature."
>>>
>>>
>>>
>>> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c
>>>
>>> code
>>> "401"
>>> message
>>> "Invalid API Signature."
>>>
>>>
>>>
>>> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205153=1593118500=1593204900=ae52423cb4b1756a678979aeffe0817d424a26cb5b1b416d0bb40b0838c179da
>>>
>>> code
>>> "401"
>>> message
>>> "Invalid API Signature."
>>>
>>> Op vrijdag 26 juni 2020 om 22:58:12 UTC+2 schreef flor...@pre-vost.fr:
>>>
 No, I would like just to restart weewx and when debug mode show URL 
 API, request this link on your favorite browser and put on comment the 
 result

 Le vendredi 26 juin 2020 à 22:54:19 UTC+2, hoev...@gmail.com a écrit :

> Or do you mean running weewx standalone?
>
> Parameter name: "api-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
> Parameter name: "api-secret" has value "ABC123"
> Parameter name: "end-timestamp" has value "1593204600"
> Parameter name: "start-timestamp" has value "1593118200"
> Parameter name: "station-id" has value "91978"
> Parameter name: "t" has value "1593204804"
> Parameter name: "api-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
> Parameter name: "api-secret" has value "ABC123"
> Parameter name: "end-timestamp" has value "1593204600"
> Parameter name: "start-timestamp" has value "1593118200"
> Parameter name: "station-id" has value "91978"
> Parameter name: "t" has value "1593204816"
>
> Op vrijdag 26 juni 2020 om 22:45:24 UTC+2 schreef Maarten van der 
> Hoeven:
>
>> I've got weewx already on debug. Or do you mean something else?
>>
>> # WEEWX CONFIGURATION FILE
>>
>>
>> ##
>>
>> # This section is for general configuration information.
>>
>> # Set to 1 for extra debug info, otherwise comment it out or set to 
>> zero
>> debug = 1
>>
>> # Root directory of the weewx data file hierarchy for this station
>> WEEWX_ROOT = /
>>
>> # Whether to log successful operations
>> log_success = True
>>
>> # Whether to log unsuccessful operations
>> log_failure = True
>>
>> # How long to wait before timing out a socket (FTP, HTTP) connection
>> socket_timeout = 20
>>
>> # Do not modify this. It is used when installing and updating weewx.
>> version = 4.1.1
>>
>> Op vrijdag 26 juni 2020 om 22:35:10 UTC+2 schreef flor...@pre-vost.fr
>> :
>>
>>> Relaunch weewx and use the url on debug. Here, the url is not in the 
>>> current timestamp. It for this thay you've this error.
>>
>>

-- 
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/69e0cb02-16a6-4f93-9465-77da408e7639n%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Maarten van der Hoeven
Hmmm, not sure. Looks like time is right to me

root@ubuntu:/etc/weewx# date
Fri 26 Jun 2020 11:08:42 PM CEST
root@ubuntu:/etc/weewx# 



Op vrijdag 26 juni 2020 om 23:07:24 UTC+2 schreef flor...@pre-vost.fr:

> Check your time server. It appear that is not correctly set and the API 
> return a wrong time when you request API
>
> Le vendredi 26 juin 2020 à 23:04:35 UTC+2, hoev...@gmail.com a écrit :
>
>> Okay, URL and responses
>>
>>
>> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c
>>
>> code
>> "401"
>> message
>> "Invalid API Signature."
>>
>>
>>
>> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c
>>
>> code
>> "401"
>> message
>> "Invalid API Signature."
>>
>>
>>
>> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205153=1593118500=1593204900=ae52423cb4b1756a678979aeffe0817d424a26cb5b1b416d0bb40b0838c179da
>>
>> code
>> "401"
>> message
>> "Invalid API Signature."
>>
>> Op vrijdag 26 juni 2020 om 22:58:12 UTC+2 schreef flor...@pre-vost.fr:
>>
>>> No, I would like just to restart weewx and when debug mode show URL API, 
>>> request this link on your favorite browser and put on comment the result
>>>
>>> Le vendredi 26 juin 2020 à 22:54:19 UTC+2, hoev...@gmail.com a écrit :
>>>
 Or do you mean running weewx standalone?

 Parameter name: "api-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
 Parameter name: "api-secret" has value "ABC123"
 Parameter name: "end-timestamp" has value "1593204600"
 Parameter name: "start-timestamp" has value "1593118200"
 Parameter name: "station-id" has value "91978"
 Parameter name: "t" has value "1593204804"
 Parameter name: "api-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
 Parameter name: "api-secret" has value "ABC123"
 Parameter name: "end-timestamp" has value "1593204600"
 Parameter name: "start-timestamp" has value "1593118200"
 Parameter name: "station-id" has value "91978"
 Parameter name: "t" has value "1593204816"

 Op vrijdag 26 juni 2020 om 22:45:24 UTC+2 schreef Maarten van der 
 Hoeven:

> I've got weewx already on debug. Or do you mean something else?
>
> # WEEWX CONFIGURATION FILE
>
>
> ##
>
> # This section is for general configuration information.
>
> # Set to 1 for extra debug info, otherwise comment it out or set to 
> zero
> debug = 1
>
> # Root directory of the weewx data file hierarchy for this station
> WEEWX_ROOT = /
>
> # Whether to log successful operations
> log_success = True
>
> # Whether to log unsuccessful operations
> log_failure = True
>
> # How long to wait before timing out a socket (FTP, HTTP) connection
> socket_timeout = 20
>
> # Do not modify this. It is used when installing and updating weewx.
> version = 4.1.1
>
> Op vrijdag 26 juni 2020 om 22:35:10 UTC+2 schreef flor...@pre-vost.fr:
>
>> Relaunch weewx and use the url on debug. Here, the url is not in the 
>> current timestamp. It for this thay you've this error.
>
>

-- 
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/36fad4bd-aa6a-41cd-909c-9416510532d5n%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread flor...@pre-vost.fr
Check your time server. It appear that is not correctly set and the API 
return a wrong time when you request API

Le vendredi 26 juin 2020 à 23:04:35 UTC+2, hoev...@gmail.com a écrit :

> Okay, URL and responses
>
>
> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c
>
> code
> "401"
> message
> "Invalid API Signature."
>
>
>
> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c
>
> code
> "401"
> message
> "Invalid API Signature."
>
>
>
> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205153=1593118500=1593204900=ae52423cb4b1756a678979aeffe0817d424a26cb5b1b416d0bb40b0838c179da
>
> code
> "401"
> message
> "Invalid API Signature."
>
> Op vrijdag 26 juni 2020 om 22:58:12 UTC+2 schreef flor...@pre-vost.fr:
>
>> No, I would like just to restart weewx and when debug mode show URL API, 
>> request this link on your favorite browser and put on comment the result
>>
>> Le vendredi 26 juin 2020 à 22:54:19 UTC+2, hoev...@gmail.com a écrit :
>>
>>> Or do you mean running weewx standalone?
>>>
>>> Parameter name: "api-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
>>> Parameter name: "api-secret" has value "ABC123"
>>> Parameter name: "end-timestamp" has value "1593204600"
>>> Parameter name: "start-timestamp" has value "1593118200"
>>> Parameter name: "station-id" has value "91978"
>>> Parameter name: "t" has value "1593204804"
>>> Parameter name: "api-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
>>> Parameter name: "api-secret" has value "ABC123"
>>> Parameter name: "end-timestamp" has value "1593204600"
>>> Parameter name: "start-timestamp" has value "1593118200"
>>> Parameter name: "station-id" has value "91978"
>>> Parameter name: "t" has value "1593204816"
>>>
>>> Op vrijdag 26 juni 2020 om 22:45:24 UTC+2 schreef Maarten van der Hoeven:
>>>
 I've got weewx already on debug. Or do you mean something else?

 # WEEWX CONFIGURATION FILE


 ##

 # This section is for general configuration information.

 # Set to 1 for extra debug info, otherwise comment it out or set to zero
 debug = 1

 # Root directory of the weewx data file hierarchy for this station
 WEEWX_ROOT = /

 # Whether to log successful operations
 log_success = True

 # Whether to log unsuccessful operations
 log_failure = True

 # How long to wait before timing out a socket (FTP, HTTP) connection
 socket_timeout = 20

 # Do not modify this. It is used when installing and updating weewx.
 version = 4.1.1

 Op vrijdag 26 juni 2020 om 22:35:10 UTC+2 schreef flor...@pre-vost.fr:

> Relaunch weewx and use the url on debug. Here, the url is not in the 
> current timestamp. It for this thay you've this error.



-- 
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/111be23b-bd95-4398-b86c-28f2c4124491n%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Maarten van der Hoeven
Okay, URL and responses

https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c

code
"401"
message
"Invalid API Signature."


https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205164=1593118500=1593204900=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c

code
"401"
message
"Invalid API Signature."


https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593205153=1593118500=1593204900=ae52423cb4b1756a678979aeffe0817d424a26cb5b1b416d0bb40b0838c179da

code
"401"
message
"Invalid API Signature."

Op vrijdag 26 juni 2020 om 22:58:12 UTC+2 schreef flor...@pre-vost.fr:

> No, I would like just to restart weewx and when debug mode show URL API, 
> request this link on your favorite browser and put on comment the result
>
> Le vendredi 26 juin 2020 à 22:54:19 UTC+2, hoev...@gmail.com a écrit :
>
>> Or do you mean running weewx standalone?
>>
>> Parameter name: "api-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
>> Parameter name: "api-secret" has value "ABC123"
>> Parameter name: "end-timestamp" has value "1593204600"
>> Parameter name: "start-timestamp" has value "1593118200"
>> Parameter name: "station-id" has value "91978"
>> Parameter name: "t" has value "1593204804"
>> Parameter name: "api-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
>> Parameter name: "api-secret" has value "ABC123"
>> Parameter name: "end-timestamp" has value "1593204600"
>> Parameter name: "start-timestamp" has value "1593118200"
>> Parameter name: "station-id" has value "91978"
>> Parameter name: "t" has value "1593204816"
>>
>> Op vrijdag 26 juni 2020 om 22:45:24 UTC+2 schreef Maarten van der Hoeven:
>>
>>> I've got weewx already on debug. Or do you mean something else?
>>>
>>> # WEEWX CONFIGURATION FILE
>>>
>>>
>>> ##
>>>
>>> # This section is for general configuration information.
>>>
>>> # Set to 1 for extra debug info, otherwise comment it out or set to zero
>>> debug = 1
>>>
>>> # Root directory of the weewx data file hierarchy for this station
>>> WEEWX_ROOT = /
>>>
>>> # Whether to log successful operations
>>> log_success = True
>>>
>>> # Whether to log unsuccessful operations
>>> log_failure = True
>>>
>>> # How long to wait before timing out a socket (FTP, HTTP) connection
>>> socket_timeout = 20
>>>
>>> # Do not modify this. It is used when installing and updating weewx.
>>> version = 4.1.1
>>>
>>> Op vrijdag 26 juni 2020 om 22:35:10 UTC+2 schreef flor...@pre-vost.fr:
>>>
 Relaunch weewx and use the url on debug. Here, the url is not in the 
 current timestamp. It for this thay you've this error.
>>>
>>>

-- 
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/d7bab34f-30f6-4517-bb0d-386ddf23caafn%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread flor...@pre-vost.fr
No, I would like just to restart weewx and when debug mode show URL API, 
request this link on your favorite browser and put on comment the result

Le vendredi 26 juin 2020 à 22:54:19 UTC+2, hoev...@gmail.com a écrit :

> Or do you mean running weewx standalone?
>
> Parameter name: "api-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
> Parameter name: "api-secret" has value "ABC123"
> Parameter name: "end-timestamp" has value "1593204600"
> Parameter name: "start-timestamp" has value "1593118200"
> Parameter name: "station-id" has value "91978"
> Parameter name: "t" has value "1593204804"
> Parameter name: "api-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
> Parameter name: "api-secret" has value "ABC123"
> Parameter name: "end-timestamp" has value "1593204600"
> Parameter name: "start-timestamp" has value "1593118200"
> Parameter name: "station-id" has value "91978"
> Parameter name: "t" has value "1593204816"
>
> Op vrijdag 26 juni 2020 om 22:45:24 UTC+2 schreef Maarten van der Hoeven:
>
>> I've got weewx already on debug. Or do you mean something else?
>>
>> # WEEWX CONFIGURATION FILE
>>
>>
>> ##
>>
>> # This section is for general configuration information.
>>
>> # Set to 1 for extra debug info, otherwise comment it out or set to zero
>> debug = 1
>>
>> # Root directory of the weewx data file hierarchy for this station
>> WEEWX_ROOT = /
>>
>> # Whether to log successful operations
>> log_success = True
>>
>> # Whether to log unsuccessful operations
>> log_failure = True
>>
>> # How long to wait before timing out a socket (FTP, HTTP) connection
>> socket_timeout = 20
>>
>> # Do not modify this. It is used when installing and updating weewx.
>> version = 4.1.1
>>
>> Op vrijdag 26 juni 2020 om 22:35:10 UTC+2 schreef flor...@pre-vost.fr:
>>
>>> Relaunch weewx and use the url on debug. Here, the url is not in the 
>>> current timestamp. It for this thay you've this error.
>>
>>

-- 
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/5dba4bcc-a9cd-4861-aef3-5de628ff4621n%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Maarten van der Hoeven
Or do you mean running weewx standalone?

Parameter name: "api-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
Parameter name: "api-secret" has value "ABC123"
Parameter name: "end-timestamp" has value "1593204600"
Parameter name: "start-timestamp" has value "1593118200"
Parameter name: "station-id" has value "91978"
Parameter name: "t" has value "1593204804"
Parameter name: "api-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
Parameter name: "api-secret" has value "ABC123"
Parameter name: "end-timestamp" has value "1593204600"
Parameter name: "start-timestamp" has value "1593118200"
Parameter name: "station-id" has value "91978"
Parameter name: "t" has value "1593204816"

Op vrijdag 26 juni 2020 om 22:45:24 UTC+2 schreef Maarten van der Hoeven:

> I've got weewx already on debug. Or do you mean something else?
>
> # WEEWX CONFIGURATION FILE
>
>
> ##
>
> # This section is for general configuration information.
>
> # Set to 1 for extra debug info, otherwise comment it out or set to zero
> debug = 1
>
> # Root directory of the weewx data file hierarchy for this station
> WEEWX_ROOT = /
>
> # Whether to log successful operations
> log_success = True
>
> # Whether to log unsuccessful operations
> log_failure = True
>
> # How long to wait before timing out a socket (FTP, HTTP) connection
> socket_timeout = 20
>
> # Do not modify this. It is used when installing and updating weewx.
> version = 4.1.1
>
> Op vrijdag 26 juni 2020 om 22:35:10 UTC+2 schreef flor...@pre-vost.fr:
>
>> Relaunch weewx and use the url on debug. Here, the url is not in the 
>> current timestamp. It for this thay you've this error.
>
>

-- 
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/2f4b042d-9ecb-46df-958b-94055b8024c4n%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Maarten van der Hoeven
I've got weewx already on debug. Or do you mean something else?

# WEEWX CONFIGURATION FILE

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 4.1.1

Op vrijdag 26 juni 2020 om 22:35:10 UTC+2 schreef flor...@pre-vost.fr:

> Relaunch weewx and use the url on debug. Here, the url is not in the 
> current timestamp. It for this thay you've this error.

-- 
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/f4800848-fc8f-4178-a8de-4857dfd20004n%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Florentin Prevost
Relaunch weewx and use the url on debug. Here, the url is not in the current 
timestamp. It for this thay you've this error.

-- 
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/5681a995-88a6-496f-9cb3-e79f00e3090ao%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Maarten van der Hoeven




code
"401"
message
"API call timestamp parameter \"t\" is stale."


Op vrijdag 26 juni 2020 om 22:30:19 UTC+2 schreef flor...@pre-vost.fr:

> Sorry, I would like the result in json of this url for example : 
> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593201429=1593114900=1593201300=4ec4be2e568748b906bb2467731310c508f3532eacc55a0f8a23d997add0a2d0

-- 
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/9ace1877-cbe9-4a77-baac-f7b81fbe2a33n%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Florentin Prevost
Sorry, I would like the result in json of this url for example : 
https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593201429=1593114900=1593201300=4ec4be2e568748b906bb2467731310c508f3532eacc55a0f8a23d997add0a2d0

-- 
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/737a81dc-4660-4f9f-9052-0aeb2ccab22ao%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Maarten van der Hoeven
Dont know what usine means. You're looking for this?

Jun 26 21:57:09 ubuntu weewx[3036] DEBUG weewx.engine: Finished loading 
service user.mqtt.MQTT
Jun 26 21:57:09 ubuntu weewx[3036] DEBUG weewx.engine: Loading service 
weewx.engine.StdPrint
Jun 26 21:57:09 ubuntu weewx[3036] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdPrint
Jun 26 21:57:09 ubuntu weewx[3036] DEBUG weewx.engine: Loading service 
weewx.engine.StdReport
Jun 26 21:57:09 ubuntu weewx[3036] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdReport
Jun 26 21:57:09 ubuntu weewx[3036] INFO __main__: Starting up weewx version 
4.1.1
Jun 26 21:57:09 ubuntu weewx[3036] DEBUG weewx.engine: Station does not 
support reading the time
Jun 26 21:57:09 ubuntu weewx[3036] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewxtest'
Jun 26 21:57:09 ubuntu weewx[3036] INFO weewx.manager: Starting backfill of 
daily summaries
Jun 26 21:57:09 ubuntu weewx[3036] INFO weewx.engine: Starting main packet 
loop.
Jun 26 21:57:09 ubuntu weewx[3036] DEBUG user.WLLDriver: Request archive 
from 1592677980 to 1593201300
Jun 26 21:57:09 ubuntu weewx[3036] DEBUG user.WLLDriver: Impossible to 
request data > 24H. Request new data to Weatherlink from 1593114900 to 
1593201300 ...
Jun 26 21:57:09 ubuntu weewx[3036] DEBUG user.WLLDriver: URL API 
Weatherlink is 
https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593201429=1593114900=1593201300=4ec4be2e568748b906bb2467731310c508f3532eacc55a0f8a23d997add0a2d0
 

Jun 26 21:57:09 ubuntu weewx[3036] DEBUG urllib3.connectionpool: Starting 
new HTTPS connection (1): api.weatherlink.com:443
Jun 26 21:57:09 ubuntu weewx[3036] DEBUG weewx.manager: Daily summary 
version is 2.0
Jun 26 21:57:09 ubuntu weewx[3036] DEBUG urllib3.connectionpool: 
https://api.weatherlink.com:443 "GET 
/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593201429=1593114900=1593201300=4ec4be2e568748b906bb2467731310c508f3532eacc55a0f8a23d997add0a2d0
 
HTTP/1.1" 401 49
Jun 26 21:57:09 ubuntu weewx[3036] DEBUG user.WLLDriver: OK Wl 1
Jun 26 21:57:09 ubuntu weewx[3036] DEBUG user.WLLDriver: OK Wl 2


Op vrijdag 26 juni 2020 om 22:22:59 UTC+2 schreef flor...@pre-vost.fr:

> Can you give me the result of the request usine to weatherlink ?

-- 
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/42e53d7e-7846-4849-a2e0-bb4b744d886cn%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Florentin Prevost
Can you give me the result of the request usine to weatherlink ?

-- 
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/e350bca1-a396-4207-92f4-9f1158455dbeo%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Maarten van der Hoeven
Hello Florentin,

I am getting retries on my sensors. 

I have ISS running on ID2, and an external temp sensor at ID 3. Could this 
be the reason of not getting the sensors?

Can you test it against my WL-archive? I will send you the api-key and 
secret in that case

Jun 26 21:57:20 ubuntu weewx[3036] DEBUG user.WLLDriver: OK Wl 1
Jun 26 21:57:20 ubuntu weewx[3036] DEBUG user.WLLDriver: OK Wl 2
Jun 26 21:57:20 ubuntu weewx[3036] DEBUG user.WLLDriver: StartTimeStamp is 
: 1593115200
Jun 26 21:57:20 ubuntu weewx[3036] INFO user.WLLDriver: Failure to get data 
https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593201439=1593114900=1593201300=d475287eac8fec7264de64abc1ffb2212bf57902c90e8d623f375209eb5dbe38
 
- try 1 - ('sensors')
Jun 26 21:57:30 ubuntu weewx[3036] DEBUG user.WLLDriver: Request archive 
from 1592677980 to 1593201300
Jun 26 21:57:30 ubuntu weewx[3036] DEBUG user.WLLDriver: Impossible to 
request data > 24H. Request new data to Weatherlink from 1593114900 to 
1593201300 ...
Jun 26 21:57:30 ubuntu weewx[3036] DEBUG user.WLLDriver: URL API 
Weatherlink is 
https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593201450=1593114900=1593201300=55695588ffc568087c334e124788607a1a24ac091992170cdbea2eec0e4f72e3
 

Jun 26 21:57:30 ubuntu weewx[3036] DEBUG urllib3.connectionpool: Starting 
new HTTPS connection (1): api.weatherlink.com:443
Jun 26 21:57:31 ubuntu weewx[3036] DEBUG urllib3.connectionpool: 
https://api.weatherlink.com:443 "GET 
/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593201450=1593114900=1593201300=55695588ffc568087c334e124788607a1a24ac091992170cdbea2eec0e4f72e3
 
HTTP/1.1" 401 49
Jun 26 21:57:31 ubuntu weewx[3036] DEBUG user.WLLDriver: OK Wl 1
Jun 26 21:57:31 ubuntu weewx[3036] DEBUG user.WLLDriver: OK Wl 2
Jun 26 21:57:31 ubuntu weewx[3036] DEBUG user.WLLDriver: StartTimeStamp is 
: 1593115200
Jun 26 21:57:31 ubuntu weewx[3036] INFO user.WLLDriver: Failure to get data 
https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593201450=1593114900=1593201300=55695588ffc568087c334e124788607a1a24ac091992170cdbea2eec0e4f72e3
 
- try 2 - ('sensors')
Jun 26 21:57:41 ubuntu weewx[3036] DEBUG user.WLLDriver: Request archive 
from 1592677980 to 1593201300
Jun 26 21:57:41 ubuntu weewx[3036] DEBUG user.WLLDriver: Impossible to 
request data > 24H. Request new data to Weatherlink from 1593114900 to 
1593201300 ...
Jun 26 21:57:41 ubuntu weewx[3036] DEBUG user.WLLDriver: URL API 
Weatherlink is 
https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593201461=1593114900=1593201300=cea8b312bb2a06c5409affbd3e8e3c782834065078ea9e0e47e1a78047e1f422
 

Jun 26 21:57:41 ubuntu weewx[3036] DEBUG urllib3.connectionpool: Starting 
new HTTPS connection (1): api.weatherlink.com:443
Jun 26 21:57:41 ubuntu weewx[3036] DEBUG urllib3.connectionpool: 
https://api.weatherlink.com:443 "GET 
/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593201461=1593114900=1593201300=cea8b312bb2a06c5409affbd3e8e3c782834065078ea9e0e47e1a78047e1f422
 
HTTP/1.1" 401 49
Jun 26 21:57:41 ubuntu weewx[3036] DEBUG user.WLLDriver: OK Wl 1
Jun 26 21:57:41 ubuntu weewx[3036] DEBUG user.WLLDriver: OK Wl 2
Jun 26 21:57:41 ubuntu weewx[3036] DEBUG user.WLLDriver: StartTimeStamp is 
: 1593115200
Jun 26 21:57:41 ubuntu weewx[3036] INFO user.WLLDriver: Failure to get data 
https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs=1593201461=1593114900=1593201300=cea8b312bb2a06c5409affbd3e8e3c782834065078ea9e0e47e1a78047e1f422
 
- try 3 - ('sensors')
Jun 26 21:57:51 ubuntu weewx[3036] DEBUG user.WLLDriver: Request archive 
from 1592677980 to 1593201300


Op vrijdag 26 juni 2020 om 18:56:18 UTC+2 schreef flor...@pre-vost.fr:

> Hi everyone and thank you for your support ! I'm very glade to know that 
> people want to make this driver because there are not a lot.
>
> This is my repo :  https://github.com/Drealine/WLLDriver 
>
> @Bastiaan it's very nice ! Just, why you use update packet or not simply 
> do a for _packet in blabla(): It's a udp protocol ?
>
> With my driver, you can retrive lost data by using API v2 of Weatherlink. 
> Depend to your subscription.
>
> Glad to work with you, and if you want, it will be more often that split 
> some git to one. 
>
> Regards, -fp 
>
> Le vendredi 26 juin 2020 à 18:35:45 UTC+2, Bastiaan Meelberg a écrit :
>
>> Hi, 
>>
>> I’m also working on a wll driver, including The 2,5 UDP packages. It is 
>> running now for a few days with good results (no rain check yet). 
>> The integration with the online fetch sounds interesting! 
>> This is my git fork: 
>> https://github.com/grebleem/WeatherLinkliveUDP 
>>
>> It is feeding my site: https://meteo-otterlo.nl 
>>
>> Cheers, Bastiaan 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread flor...@pre-vost.fr
Hi everyone and thank you for your support ! I'm very glade to know that 
people want to make this driver because there are not a lot.

This is my repo :  https://github.com/Drealine/WLLDriver 

@Bastiaan it's very nice ! Just, why you use update packet or not simply do 
a for _packet in blabla(): It's a udp protocol ?

With my driver, you can retrive lost data by using API v2 of Weatherlink. 
Depend to your subscription.

Glad to work with you, and if you want, it will be more often that split 
some git to one. 

Regards, -fp 

Le vendredi 26 juin 2020 à 18:35:45 UTC+2, Bastiaan Meelberg a écrit :

> Hi,
>
> I’m also working on a wll driver, including The 2,5 UDP packages. It is 
> running now for a few days with good results (no rain check yet). 
> The integration with the online fetch sounds interesting!
> This is my git fork:
> https://github.com/grebleem/WeatherLinkliveUDP
>
> It is feeding my site: https://meteo-otterlo.nl
>
> Cheers, 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/f3d47134-557a-4594-ad93-40a54420533en%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Bastiaan Meelberg
Hi,

I’m also working on a wll driver, including The 2,5 UDP packages. It is running 
now for a few days with good results (no rain check yet). 
The integration with the online fetch sounds interesting!
This is my git fork:
https://github.com/grebleem/WeatherLinkliveUDP

It is feeding my site: https://meteo-otterlo.nl

Cheers, 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/3b397228-95e6-4075-9dc6-1088d8932b83o%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-26 Thread Maarten van der Hoeven
Hello Florentin,

Do you want me to help you with this? A have programming skills, though not 
Python yet, but am able to test with my WLL. And poke around in the code, 
if you want me to...

Op donderdag 25 juni 2020 om 17:34:37 UTC+2 schreef flor...@pre-vost.fr:

> This is :  https://github.com/Drealine/WLLDriver  
>
> Le jeudi 25 juin 2020 à 16:41:45 UTC+2, Tom Keffer a écrit :
>
>> Is there an online repository that holds the code? GitHub? Elsewhere?
>>
>> On Thu, Jun 25, 2020 at 6:59 AM Tom Keffer  wrote:
>>
>>> Let me give it a try. It's a simple uploader.
>>>
>>> -tk
>>>
>>> On Thu, Jun 25, 2020 at 6:21 AM flor...@pre-vost.fr  
>>> wrote:
>>>
 Hi Tom,

 Sorry, at the moment, I fix this issue.
 When you want to make a request by using : requests.get("url") in 
 genLoopPacket(), Weewx is mistaken with this proper get function, I don't 
 know why but I fix this by declare Request = requests.session()

 Also, I want to know if it possible to have the daily rain max by using 
 a function in manager.py ? I see _read_metadata() or _get_day_summary() 
 but 
 I don't know how to implement it.

 F. Prevost

 I see 


 Le mardi 23 juin 2020 à 15:43:26 UTC+2, Tom Keffer a écrit :

> Florentin, you are being very vague about the error. You're showing no 
> code, and you're not showing the error. "weewx confuse to internal get". 
> I 
> don't know what that means. 
>
>
>
>
>
> On Mon, Jun 22, 2020 at 11:35 AM flor...@pre-vost.fr <
> flor...@pre-vost.fr> wrote:
>
>> Ok I found the problem, I use request to get json from URL but weewx 
>> confuse to internal get. 
>>
>> How can I pass this error ?
>>
>> Le lundi 22 juin 2020 à 19:26:46 UTC+2, flor...@pre-vost.fr a écrit :
>>
>>> Hi,
>>>
>>> Yeahh :) It work ahah ^^ Thank you for your answer.
>>>
>>> I try to implement genArchiveRecords(self,since_ts): but I've this 
>>> error : 
>>>
>>>
>>>1. INFO weewx.engine: Main loop exiting. Shutting engine down.
>>>2. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: Caught 
>>>unrecoverable exception:
>>>3. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>>   'generator' object has no attribute 'get'
>>>4. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>>   Traceback (most recent call last):
>>>5. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>> File "/usr/share/weewx/weewxd", line 154, in main
>>>6. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>>   engine.run()
>>>7. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>> File "/usr/share/weewx/weewx/engine.py", line 158, in run
>>>8. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>>   self.dispatchEvent(weewx.Event(weewx.STARTUP))
>>>9. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>> File "/usr/share/weewx/weewx/engine.py", line 224, in 
>>> dispatchEvent
>>>10. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>>   callback(event)
>>>11. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>> File "/usr/share/weewx/weewx/engine.py", line 530, in 
>>> startup
>>>12. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>>   self._catchup(self.engine.console.genStartupRecords)
>>>13. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>> File "/usr/share/weewx/weewx/engine.py", line 639, in 
>>> _catchup
>>>14. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>>   ts = record.get('dateTime')
>>>15. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>>   AttributeError: 'generator' object has no attribute 'get'
>>>16. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>>   Exiting.
>>>17. Jun 22 19:20:30 debian systemd[1]: session-14.scope: 
>>>Succeeded.
>>>
>>>
>>> I don't know why ? I import weewx.engine into my blabla.py
>>>
>>> Maybe I losted to implement other value or function ?
>>> Le lundi 22 juin 2020 à 14:08:03 UTC+2, Tom Keffer a écrit :
>>>
 A driver is different from a service. The documentation you quoted 
 is for a *service*. You want the section *Porting to new hardware 
 *.

 Take a look at Vince's driver that you linked to in the first post 
 of this thread. On line 106 
 ,
  
 the configuration dictionary (argument 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-25 Thread flor...@pre-vost.fr
This is :  https://github.com/Drealine/WLLDriver  

Le jeudi 25 juin 2020 à 16:41:45 UTC+2, Tom Keffer a écrit :

> Is there an online repository that holds the code? GitHub? Elsewhere?
>
> On Thu, Jun 25, 2020 at 6:59 AM Tom Keffer  wrote:
>
>> Let me give it a try. It's a simple uploader.
>>
>> -tk
>>
>> On Thu, Jun 25, 2020 at 6:21 AM flor...@pre-vost.fr  
>> wrote:
>>
>>> Hi Tom,
>>>
>>> Sorry, at the moment, I fix this issue.
>>> When you want to make a request by using : requests.get("url") in 
>>> genLoopPacket(), Weewx is mistaken with this proper get function, I don't 
>>> know why but I fix this by declare Request = requests.session()
>>>
>>> Also, I want to know if it possible to have the daily rain max by using 
>>> a function in manager.py ? I see _read_metadata() or _get_day_summary() but 
>>> I don't know how to implement it.
>>>
>>> F. Prevost
>>>
>>> I see 
>>>
>>>
>>> Le mardi 23 juin 2020 à 15:43:26 UTC+2, Tom Keffer a écrit :
>>>
 Florentin, you are being very vague about the error. You're showing no 
 code, and you're not showing the error. "weewx confuse to internal get". I 
 don't know what that means. 





 On Mon, Jun 22, 2020 at 11:35 AM flor...@pre-vost.fr <
 flor...@pre-vost.fr> wrote:

> Ok I found the problem, I use request to get json from URL but weewx 
> confuse to internal get. 
>
> How can I pass this error ?
>
> Le lundi 22 juin 2020 à 19:26:46 UTC+2, flor...@pre-vost.fr a écrit :
>
>> Hi,
>>
>> Yeahh :) It work ahah ^^ Thank you for your answer.
>>
>> I try to implement genArchiveRecords(self,since_ts): but I've this 
>> error : 
>>
>>
>>1. INFO weewx.engine: Main loop exiting. Shutting engine down.
>>2. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: Caught 
>>unrecoverable exception:
>>3. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>   'generator' object has no attribute 'get'
>>4. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>   Traceback (most recent call last):
>>5. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>> File "/usr/share/weewx/weewxd", line 154, in main
>>6. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>   engine.run()
>>7. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>> File "/usr/share/weewx/weewx/engine.py", line 158, in run
>>8. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>   self.dispatchEvent(weewx.Event(weewx.STARTUP))
>>9. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>> File "/usr/share/weewx/weewx/engine.py", line 224, in 
>> dispatchEvent
>>10. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>   callback(event)
>>11. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>> File "/usr/share/weewx/weewx/engine.py", line 530, in startup
>>12. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>   self._catchup(self.engine.console.genStartupRecords)
>>13. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>> File "/usr/share/weewx/weewx/engine.py", line 639, in 
>> _catchup
>>14. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>   ts = record.get('dateTime')
>>15. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>   AttributeError: 'generator' object has no attribute 'get'
>>16. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>>   Exiting.
>>17. Jun 22 19:20:30 debian systemd[1]: session-14.scope: 
>>Succeeded.
>>
>>
>> I don't know why ? I import weewx.engine into my blabla.py
>>
>> Maybe I losted to implement other value or function ?
>> Le lundi 22 juin 2020 à 14:08:03 UTC+2, Tom Keffer a écrit :
>>
>>> A driver is different from a service. The documentation you quoted 
>>> is for a *service*. You want the section *Porting to new hardware 
>>> *.
>>>
>>> Take a look at Vince's driver that you linked to in the first post 
>>> of this thread. On line 106 
>>> ,
>>>  
>>> the configuration dictionary (argument config_dict) is passed into 
>>> the function loader(). It contains everything in weewx.conf. On the 
>>> next line, 107, just the substructure 
>>> config_dict['WeatherLinkLiveJSON'], which corresponds to the 
>>> section [WeatherLinkLiveJSON]in weewx.conf, is passed on to the 
>>> class WeatherLinkLiveJSONDriver. Nothing else. That's a typical 
>>> pattern.
>>>
>>> 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-25 Thread Tom Keffer
Is there an online repository that holds the code? GitHub? Elsewhere?

On Thu, Jun 25, 2020 at 6:59 AM Tom Keffer  wrote:

> Let me give it a try. It's a simple uploader.
>
> -tk
>
> On Thu, Jun 25, 2020 at 6:21 AM flor...@pre-vost.fr 
> wrote:
>
>> Hi Tom,
>>
>> Sorry, at the moment, I fix this issue.
>> When you want to make a request by using : requests.get("url") in
>> genLoopPacket(), Weewx is mistaken with this proper get function, I don't
>> know why but I fix this by declare Request = requests.session()
>>
>> Also, I want to know if it possible to have the daily rain max by using a
>> function in manager.py ? I see _read_metadata() or _get_day_summary() but I
>> don't know how to implement it.
>>
>> F. Prevost
>>
>> I see
>>
>>
>> Le mardi 23 juin 2020 à 15:43:26 UTC+2, Tom Keffer a écrit :
>>
>>> Florentin, you are being very vague about the error. You're showing no
>>> code, and you're not showing the error. "weewx confuse to internal get". I
>>> don't know what that means.
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Jun 22, 2020 at 11:35 AM flor...@pre-vost.fr <
>>> flor...@pre-vost.fr> wrote:
>>>
 Ok I found the problem, I use request to get json from URL but weewx
 confuse to internal get.

 How can I pass this error ?

 Le lundi 22 juin 2020 à 19:26:46 UTC+2, flor...@pre-vost.fr a écrit :

> Hi,
>
> Yeahh :) It work ahah ^^ Thank you for your answer.
>
> I try to implement genArchiveRecords(self,since_ts): but I've this
> error :
>
>
>1. INFO weewx.engine: Main loop exiting. Shutting engine down.
>2. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: Caught
>unrecoverable exception:
>3. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>'generator' object has no attribute 'get'
>4. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>Traceback (most recent call last):
>5. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>  File "/usr/share/weewx/weewxd", line 154, in main
>6. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>engine.run()
>7. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>  File "/usr/share/weewx/weewx/engine.py", line 158, in run
>8. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>self.dispatchEvent(weewx.Event(weewx.STARTUP))
>9. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>  File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
>10. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>   callback(event)
>11. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
> File "/usr/share/weewx/weewx/engine.py", line 530, in startup
>12. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>   self._catchup(self.engine.console.genStartupRecords)
>13. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
> File "/usr/share/weewx/weewx/engine.py", line 639, in _catchup
>14. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>   ts = record.get('dateTime')
>15. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>   AttributeError: 'generator' object has no attribute 'get'
>16. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:
>   Exiting.
>17. Jun 22 19:20:30 debian systemd[1]: session-14.scope: Succeeded.
>
>
> I don't know why ? I import weewx.engine into my blabla.py
>
> Maybe I losted to implement other value or function ?
> Le lundi 22 juin 2020 à 14:08:03 UTC+2, Tom Keffer a écrit :
>
>> A driver is different from a service. The documentation you quoted is
>> for a *service*. You want the section *Porting to new hardware
>> *.
>>
>> Take a look at Vince's driver that you linked to in the first post of
>> this thread. On line 106
>> ,
>> the configuration dictionary (argument config_dict) is passed into
>> the function loader(). It contains everything in weewx.conf. On the
>> next line, 107, just the substructure
>> config_dict['WeatherLinkLiveJSON'], which corresponds to the section
>> [WeatherLinkLiveJSON]in weewx.conf, is passed on to the class
>> WeatherLinkLiveJSONDriver. Nothing else. That's a typical pattern.
>>
>> -tk
>>
>> On Sun, Jun 21, 2020 at 11:25 PM Florentin Prevost <
>> flor...@pre-vost.fr> wrote:
>>
>>> Hi,
>>>
>>> Thank you. I stuck just into passed config_dict.
>>>
>>> How can I pass this value into my driver ?
>>>
>>> In documentation, he say that create class like this :
>>>
>>> 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-25 Thread Tom Keffer
Let me give it a try. It's a simple uploader.

-tk

On Thu, Jun 25, 2020 at 6:21 AM flor...@pre-vost.fr 
wrote:

> Hi Tom,
>
> Sorry, at the moment, I fix this issue.
> When you want to make a request by using : requests.get("url") in
> genLoopPacket(), Weewx is mistaken with this proper get function, I don't
> know why but I fix this by declare Request = requests.session()
>
> Also, I want to know if it possible to have the daily rain max by using a
> function in manager.py ? I see _read_metadata() or _get_day_summary() but I
> don't know how to implement it.
>
> F. Prevost
>
> I see
>
>
> Le mardi 23 juin 2020 à 15:43:26 UTC+2, Tom Keffer a écrit :
>
>> Florentin, you are being very vague about the error. You're showing no
>> code, and you're not showing the error. "weewx confuse to internal get". I
>> don't know what that means.
>>
>>
>>
>>
>>
>> On Mon, Jun 22, 2020 at 11:35 AM flor...@pre-vost.fr 
>> wrote:
>>
>>> Ok I found the problem, I use request to get json from URL but weewx
>>> confuse to internal get.
>>>
>>> How can I pass this error ?
>>>
>>> Le lundi 22 juin 2020 à 19:26:46 UTC+2, flor...@pre-vost.fr a écrit :
>>>
 Hi,

 Yeahh :) It work ahah ^^ Thank you for your answer.

 I try to implement genArchiveRecords(self,since_ts): but I've this
 error :


1. INFO weewx.engine: Main loop exiting. Shutting engine down.
2. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: Caught
unrecoverable exception:
3. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
'generator' object has no attribute 'get'
4. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
Traceback (most recent call last):
5. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
  File "/usr/share/weewx/weewxd", line 154, in main
6. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
engine.run()
7. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
  File "/usr/share/weewx/weewx/engine.py", line 158, in run
8. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
self.dispatchEvent(weewx.Event(weewx.STARTUP))
9. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
  File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
10. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
callback(event)
11. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
  File "/usr/share/weewx/weewx/engine.py", line 530, in startup
12. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
self._catchup(self.engine.console.genStartupRecords)
13. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
  File "/usr/share/weewx/weewx/engine.py", line 639, in _catchup
14. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
ts = record.get('dateTime')
15. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
AttributeError: 'generator' object has no attribute 'get'
16. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
Exiting.
17. Jun 22 19:20:30 debian systemd[1]: session-14.scope: Succeeded.


 I don't know why ? I import weewx.engine into my blabla.py

 Maybe I losted to implement other value or function ?
 Le lundi 22 juin 2020 à 14:08:03 UTC+2, Tom Keffer a écrit :

> A driver is different from a service. The documentation you quoted is
> for a *service*. You want the section *Porting to new hardware
> *.
>
> Take a look at Vince's driver that you linked to in the first post of
> this thread. On line 106
> ,
> the configuration dictionary (argument config_dict) is passed into
> the function loader(). It contains everything in weewx.conf. On the
> next line, 107, just the substructure
> config_dict['WeatherLinkLiveJSON'], which corresponds to the section
> [WeatherLinkLiveJSON]in weewx.conf, is passed on to the class
> WeatherLinkLiveJSONDriver. Nothing else. That's a typical pattern.
>
> -tk
>
> On Sun, Jun 21, 2020 at 11:25 PM Florentin Prevost <
> flor...@pre-vost.fr> wrote:
>
>> Hi,
>>
>> Thank you. I stuck just into passed config_dict.
>>
>> How can I pass this value into my driver ?
>>
>> In documentation, he say that create class like this :
>>
>> class MyAlarm(StdService):
>> """Service that sends email if an arbitrary expression evaluates 
>> true"""
>>
>> def __init__(self, engine, config_dict):
>>
>>
>>
>> Thank's
>> Le lundi 22 juin 2020 00:16:03 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-25 Thread flor...@pre-vost.fr
Hi Tom,

Sorry, at the moment, I fix this issue.
When you want to make a request by using : requests.get("url") in 
genLoopPacket(), Weewx is mistaken with this proper get function, I don't 
know why but I fix this by declare Request = requests.session()

Also, I want to know if it possible to have the daily rain max by using a 
function in manager.py ? I see _read_metadata() or _get_day_summary() but I 
don't know how to implement it.

F. Prevost

I see 


Le mardi 23 juin 2020 à 15:43:26 UTC+2, Tom Keffer a écrit :

> Florentin, you are being very vague about the error. You're showing no 
> code, and you're not showing the error. "weewx confuse to internal get". I 
> don't know what that means. 
>
>
>
>
>
> On Mon, Jun 22, 2020 at 11:35 AM flor...@pre-vost.fr  
> wrote:
>
>> Ok I found the problem, I use request to get json from URL but weewx 
>> confuse to internal get. 
>>
>> How can I pass this error ?
>>
>> Le lundi 22 juin 2020 à 19:26:46 UTC+2, flor...@pre-vost.fr a écrit :
>>
>>> Hi,
>>>
>>> Yeahh :) It work ahah ^^ Thank you for your answer.
>>>
>>> I try to implement genArchiveRecords(self,since_ts): but I've this error 
>>> : 
>>>
>>>
>>>1. INFO weewx.engine: Main loop exiting. Shutting engine down.
>>>2. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: Caught 
>>>unrecoverable exception:
>>>3. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>>>'generator' object has no attribute 'get'
>>>4. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>>>Traceback (most recent call last):
>>>5. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>>File "/usr/share/weewx/weewxd", line 154, in main
>>>6. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>>  engine.run()
>>>7. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>>File "/usr/share/weewx/weewx/engine.py", line 158, in run
>>>8. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>>  self.dispatchEvent(weewx.Event(weewx.STARTUP))
>>>9. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>>File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
>>>10. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>>>callback(event)
>>>11. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>>>  File "/usr/share/weewx/weewx/engine.py", line 530, in startup
>>>12. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>>>self._catchup(self.engine.console.genStartupRecords)
>>>13. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>>>  File "/usr/share/weewx/weewx/engine.py", line 639, in _catchup
>>>14. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>>>ts = record.get('dateTime')
>>>15. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>>>AttributeError: 'generator' object has no attribute 'get'
>>>16. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>>>Exiting.
>>>17. Jun 22 19:20:30 debian systemd[1]: session-14.scope: Succeeded.
>>>
>>>
>>> I don't know why ? I import weewx.engine into my blabla.py
>>>
>>> Maybe I losted to implement other value or function ?
>>> Le lundi 22 juin 2020 à 14:08:03 UTC+2, Tom Keffer a écrit :
>>>
 A driver is different from a service. The documentation you quoted is 
 for a *service*. You want the section *Porting to new hardware 
 *.

 Take a look at Vince's driver that you linked to in the first post of 
 this thread. On line 106 
 ,
  
 the configuration dictionary (argument config_dict) is passed into the 
 function loader(). It contains everything in weewx.conf. On the next 
 line, 107, just the substructure config_dict['WeatherLinkLiveJSON'], 
 which corresponds to the section [WeatherLinkLiveJSON]in weewx.conf, is 
 passed on to the class WeatherLinkLiveJSONDriver. Nothing else. That's 
 a typical pattern.

 -tk

 On Sun, Jun 21, 2020 at 11:25 PM Florentin Prevost  
 wrote:

> Hi,
>
> Thank you. I stuck just into passed config_dict.
>
> How can I pass this value into my driver ? 
>
> In documentation, he say that create class like this : 
>
> class MyAlarm(StdService):
> """Service that sends email if an arbitrary expression evaluates 
> true"""
>
> def __init__(self, engine, config_dict):
>
>
>
> Thank's
> Le lundi 22 juin 2020 00:16:03 UTC+2, Tom Keffer a écrit :
>>
>> Yes, it's possible to access anything in the dictionary. For example, 
>> the name of the database used by the binding wx_binding would be given by
>>
>> 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-23 Thread Tom Keffer
Florentin, you are being very vague about the error. You're showing no
code, and you're not showing the error. "weewx confuse to internal get". I
don't know what that means.





On Mon, Jun 22, 2020 at 11:35 AM flor...@pre-vost.fr 
wrote:

> Ok I found the problem, I use request to get json from URL but weewx
> confuse to internal get.
>
> How can I pass this error ?
>
> Le lundi 22 juin 2020 à 19:26:46 UTC+2, flor...@pre-vost.fr a écrit :
>
>> Hi,
>>
>> Yeahh :) It work ahah ^^ Thank you for your answer.
>>
>> I try to implement genArchiveRecords(self,since_ts): but I've this error
>> :
>>
>>
>>1. INFO weewx.engine: Main loop exiting. Shutting engine down.
>>2. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: Caught
>>unrecoverable exception:
>>3. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>'generator' object has no attribute 'get'
>>4. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>Traceback (most recent call last):
>>5. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>File "/usr/share/weewx/weewxd", line 154, in main
>>6. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>  engine.run()
>>7. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>File "/usr/share/weewx/weewx/engine.py", line 158, in run
>>8. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>  self.dispatchEvent(weewx.Event(weewx.STARTUP))
>>9. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
>>10. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>  callback(event)
>>11. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>File "/usr/share/weewx/weewx/engine.py", line 530, in startup
>>12. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>  self._catchup(self.engine.console.genStartupRecords)
>>13. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>File "/usr/share/weewx/weewx/engine.py", line 639, in _catchup
>>14. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>  ts = record.get('dateTime')
>>15. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>AttributeError: 'generator' object has no attribute 'get'
>>16. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>>Exiting.
>>17. Jun 22 19:20:30 debian systemd[1]: session-14.scope: Succeeded.
>>
>>
>> I don't know why ? I import weewx.engine into my blabla.py
>>
>> Maybe I losted to implement other value or function ?
>> Le lundi 22 juin 2020 à 14:08:03 UTC+2, Tom Keffer a écrit :
>>
>>> A driver is different from a service. The documentation you quoted is
>>> for a *service*. You want the section *Porting to new hardware
>>> *.
>>>
>>> Take a look at Vince's driver that you linked to in the first post of
>>> this thread. On line 106
>>> ,
>>> the configuration dictionary (argument config_dict) is passed into the
>>> function loader(). It contains everything in weewx.conf. On the next
>>> line, 107, just the substructure config_dict['WeatherLinkLiveJSON'],
>>> which corresponds to the section [WeatherLinkLiveJSON]in weewx.conf, is
>>> passed on to the class WeatherLinkLiveJSONDriver. Nothing else. That's
>>> a typical pattern.
>>>
>>> -tk
>>>
>>> On Sun, Jun 21, 2020 at 11:25 PM Florentin Prevost 
>>> wrote:
>>>
 Hi,

 Thank you. I stuck just into passed config_dict.

 How can I pass this value into my driver ?

 In documentation, he say that create class like this :

 class MyAlarm(StdService):
 """Service that sends email if an arbitrary expression evaluates 
 true"""

 def __init__(self, engine, config_dict):



 Thank's
 Le lundi 22 juin 2020 00:16:03 UTC+2, Tom Keffer a écrit :
>
> Yes, it's possible to access anything in the dictionary. For example,
> the name of the database used by the binding wx_binding would be given by
>
> config_dict['Databases']['wx_binding']['database']
>
>
> However, it is rarely necessary to do this. Better to use the
> functions in manager.py to simply open up the database you need. For
> example,
>
> db = manager.open_manager_with_config(config_dict, 'wx_binding')
>
>
> would return a database Manager object for the wx_binding.
>
> See the section *Programming interface
> * in
> the Customizing Guide.
>
> -tk
>
> On Sun, Jun 21, 2020 at 2:21 PM Florentin Prevost 
> wrote:
>
>> Thank you very well for your answer :)
>>
>> For the first question, 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-22 Thread flor...@pre-vost.fr
Ok I found the problem, I use request to get json from URL but weewx 
confuse to internal get. 

How can I pass this error ?

Le lundi 22 juin 2020 à 19:26:46 UTC+2, flor...@pre-vost.fr a écrit :

> Hi,
>
> Yeahh :) It work ahah ^^ Thank you for your answer.
>
> I try to implement genArchiveRecords(self,since_ts): but I've this error : 
>
>
>1. INFO weewx.engine: Main loop exiting. Shutting engine down.
>2. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: Caught 
>unrecoverable exception:
>3. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>'generator' object has no attribute 'get'
>4. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>Traceback (most recent call last):
>5. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>File "/usr/share/weewx/weewxd", line 154, in main
>6. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>engine.run()
>7. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>File "/usr/share/weewx/weewx/engine.py", line 158, in run
>8. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>self.dispatchEvent(weewx.Event(weewx.STARTUP))
>9. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
>10. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>  callback(event)
>11. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>File "/usr/share/weewx/weewx/engine.py", line 530, in startup
>12. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>  self._catchup(self.engine.console.genStartupRecords)
>13. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>File "/usr/share/weewx/weewx/engine.py", line 639, in _catchup
>14. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
>  ts = record.get('dateTime')
>15. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>AttributeError: 'generator' object has no attribute 'get'
>16. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
>Exiting.
>17. Jun 22 19:20:30 debian systemd[1]: session-14.scope: Succeeded.
>
>
> I don't know why ? I import weewx.engine into my blabla.py
>
> Maybe I losted to implement other value or function ?
> Le lundi 22 juin 2020 à 14:08:03 UTC+2, Tom Keffer a écrit :
>
>> A driver is different from a service. The documentation you quoted is for 
>> a *service*. You want the section *Porting to new hardware 
>> *.
>>
>> Take a look at Vince's driver that you linked to in the first post of 
>> this thread. On line 106 
>> ,
>>  
>> the configuration dictionary (argument config_dict) is passed into the 
>> function loader(). It contains everything in weewx.conf. On the next 
>> line, 107, just the substructure config_dict['WeatherLinkLiveJSON'], 
>> which corresponds to the section [WeatherLinkLiveJSON]in weewx.conf, is 
>> passed on to the class WeatherLinkLiveJSONDriver. Nothing else. That's a 
>> typical pattern.
>>
>> -tk
>>
>> On Sun, Jun 21, 2020 at 11:25 PM Florentin Prevost  
>> wrote:
>>
>>> Hi,
>>>
>>> Thank you. I stuck just into passed config_dict.
>>>
>>> How can I pass this value into my driver ? 
>>>
>>> In documentation, he say that create class like this : 
>>>
>>> class MyAlarm(StdService):
>>> """Service that sends email if an arbitrary expression evaluates true"""
>>>
>>> def __init__(self, engine, config_dict):
>>>
>>>
>>>
>>> Thank's
>>> Le lundi 22 juin 2020 00:16:03 UTC+2, Tom Keffer a écrit :

 Yes, it's possible to access anything in the dictionary. For example, 
 the name of the database used by the binding wx_binding would be given by

 config_dict['Databases']['wx_binding']['database']


 However, it is rarely necessary to do this. Better to use the functions 
 in manager.py to simply open up the database you need. For example,

 db = manager.open_manager_with_config(config_dict, 'wx_binding')


 would return a database Manager object for the wx_binding.

 See the section *Programming interface 
 * in 
 the Customizing Guide.

 -tk

 On Sun, Jun 21, 2020 at 2:21 PM Florentin Prevost  
 wrote:

> Thank you very well for your answer :) 
>
> For the first question, sorry, I wanted to say that if it possible to 
> pass argument that is not in stanza [myWlink] for example. Because I've 
> set 
> the same parameter for sql database if you know what i mean. 
>
>
> Le dimanche 21 juin 2020 20:58:58 UTC+2, Tom Keffer a écrit :
>>
>> 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-22 Thread flor...@pre-vost.fr
Hi,

Yeahh :) It work ahah ^^ Thank you for your answer.

I try to implement genArchiveRecords(self,since_ts): but I've this error : 


   1. INFO weewx.engine: Main loop exiting. Shutting engine down.
   2. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: Caught 
   unrecoverable exception:
   3. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
   'generator' object has no attribute 'get'
   4. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
   Traceback (most recent call last):
   5. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
   File "/usr/share/weewx/weewxd", line 154, in main
   6. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
   engine.run()
   7. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
   File "/usr/share/weewx/weewx/engine.py", line 158, in run
   8. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
   self.dispatchEvent(weewx.Event(weewx.STARTUP))
   9. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
   File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
   10. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
   callback(event)
   11. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
   File "/usr/share/weewx/weewx/engine.py", line 530, in startup
   12. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
   self._catchup(self.engine.console.genStartupRecords)
   13. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__: 
   File "/usr/share/weewx/weewx/engine.py", line 639, in _catchup
   14. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
   ts = record.get('dateTime')
   15. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
   AttributeError: 'generator' object has no attribute 'get'
   16. Jun 22 19:19:32 debian weewx[1344] CRITICAL __main__:   
   Exiting.
   17. Jun 22 19:20:30 debian systemd[1]: session-14.scope: Succeeded.


I don't know why ? I import weewx.engine into my blabla.py

Maybe I losted to implement other value or function ?
Le lundi 22 juin 2020 à 14:08:03 UTC+2, Tom Keffer a écrit :

> A driver is different from a service. The documentation you quoted is for 
> a *service*. You want the section *Porting to new hardware 
> *.
>
> Take a look at Vince's driver that you linked to in the first post of this 
> thread. On line 106 
> ,
>  
> the configuration dictionary (argument config_dict) is passed into the 
> function loader(). It contains everything in weewx.conf. On the next 
> line, 107, just the substructure config_dict['WeatherLinkLiveJSON'], 
> which corresponds to the section [WeatherLinkLiveJSON]in weewx.conf, is 
> passed on to the class WeatherLinkLiveJSONDriver. Nothing else. That's a 
> typical pattern.
>
> -tk
>
> On Sun, Jun 21, 2020 at 11:25 PM Florentin Prevost  
> wrote:
>
>> Hi,
>>
>> Thank you. I stuck just into passed config_dict.
>>
>> How can I pass this value into my driver ? 
>>
>> In documentation, he say that create class like this : 
>>
>> class MyAlarm(StdService):
>> """Service that sends email if an arbitrary expression evaluates true"""
>>
>> def __init__(self, engine, config_dict):
>>
>>
>>
>> Thank's
>> Le lundi 22 juin 2020 00:16:03 UTC+2, Tom Keffer a écrit :
>>>
>>> Yes, it's possible to access anything in the dictionary. For example, 
>>> the name of the database used by the binding wx_binding would be given by
>>>
>>> config_dict['Databases']['wx_binding']['database']
>>>
>>>
>>> However, it is rarely necessary to do this. Better to use the functions 
>>> in manager.py to simply open up the database you need. For example,
>>>
>>> db = manager.open_manager_with_config(config_dict, 'wx_binding')
>>>
>>>
>>> would return a database Manager object for the wx_binding.
>>>
>>> See the section *Programming interface 
>>> * in 
>>> the Customizing Guide.
>>>
>>> -tk
>>>
>>> On Sun, Jun 21, 2020 at 2:21 PM Florentin Prevost  
>>> wrote:
>>>
 Thank you very well for your answer :) 

 For the first question, sorry, I wanted to say that if it possible to 
 pass argument that is not in stanza [myWlink] for example. Because I've 
 set 
 the same parameter for sql database if you know what i mean. 


 Le dimanche 21 juin 2020 20:58:58 UTC+2, Tom Keffer a écrit :
>
> Make sure you read the section *Porting to new hardware 
> * in the 
> Customizing Guide. It answers some of your questions.
>
> 1. The full configuration information is available as the first 
> argument to your driver loader() function as a dictionary. However, 
> in general, 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-22 Thread Tom Keffer
A driver is different from a service. The documentation you quoted is for a
*service*. You want the section *Porting to new hardware
*.

Take a look at Vince's driver that you linked to in the first post of this
thread. On line 106
,
the configuration dictionary (argument config_dict) is passed into the
function loader(). It contains everything in weewx.conf. On the next line,
107, just the substructure config_dict['WeatherLinkLiveJSON'], which
corresponds to the section [WeatherLinkLiveJSON]in weewx.conf, is passed on
to the class WeatherLinkLiveJSONDriver. Nothing else. That's a typical
pattern.

-tk

On Sun, Jun 21, 2020 at 11:25 PM Florentin Prevost 
wrote:

> Hi,
>
> Thank you. I stuck just into passed config_dict.
>
> How can I pass this value into my driver ?
>
> In documentation, he say that create class like this :
>
> class MyAlarm(StdService):
> """Service that sends email if an arbitrary expression evaluates true"""
>
> def __init__(self, engine, config_dict):
>
>
>
> Thank's
> Le lundi 22 juin 2020 00:16:03 UTC+2, Tom Keffer a écrit :
>>
>> Yes, it's possible to access anything in the dictionary. For example, the
>> name of the database used by the binding wx_binding would be given by
>>
>> config_dict['Databases']['wx_binding']['database']
>>
>>
>> However, it is rarely necessary to do this. Better to use the functions
>> in manager.py to simply open up the database you need. For example,
>>
>> db = manager.open_manager_with_config(config_dict, 'wx_binding')
>>
>>
>> would return a database Manager object for the wx_binding.
>>
>> See the section *Programming interface
>> * in
>> the Customizing Guide.
>>
>> -tk
>>
>> On Sun, Jun 21, 2020 at 2:21 PM Florentin Prevost 
>> wrote:
>>
>>> Thank you very well for your answer :)
>>>
>>> For the first question, sorry, I wanted to say that if it possible to
>>> pass argument that is not in stanza [myWlink] for example. Because I've set
>>> the same parameter for sql database if you know what i mean.
>>>
>>>
>>> Le dimanche 21 juin 2020 20:58:58 UTC+2, Tom Keffer a écrit :

 Make sure you read the section *Porting to new hardware
 * in the
 Customizing Guide. It answers some of your questions.

 1. The full configuration information is available as the first
 argument to your driver loader() function as a dictionary. However, in
 general, you should try to keep your driver as modular as possible, and not
 pick and choose information from all over the dictionary. Best practice is
 to have your driver depend on information in its private stanza. For
 example, if your driver is named mywlnk.py, it should have a stanza

 [MyWlink]

 and look there for all its information. But, there are many exceptions
 to this best practice.

 2. The function genArchiveRecords() is a *generator function*. If you
 don't know what that is, see the section *Generators
 * in the Python
 documentation. It takes one argument: a timestamp with the last time in the
 database. Your function should return all archive records since that time,
 using a yield statement. It will be called at startup and at the end of
 each archive interval. However, exactly when should not be your concern ---
 that's the engine's job.

 -tk

 On Sun, Jun 21, 2020 at 10:18 AM Florentin Prevost 
 wrote:

> Hi,
>
> I worked with the fork of
> https://github.com/vinceskahan/weewx-weatherlinklive-json and I would
> like to ask some questions about driver developpment.
>
> - How can I passed argument of weewx.conf to my driver ? I work to
> request lost data from Weewx on Weatherlink.com because WeatherLink Live
> don't have API to take archive directly and I would like to passed some
> arguments like archive_interval, sql password & etc
> - How work genArchiveRecords when it call? It run as each report ? Or
> it is a loop that waiting to have return values ?
>
>
> Thank you for your answer and support.
>
> --
> 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-de...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-development/d04b1fde-25c3-476d-b885-8d45b682976ao%40googlegroups.com
> 
> .
>
 --
>>> You received this message 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-22 Thread Florentin Prevost
Hi,

Thank you. I stuck just into passed config_dict.

How can I pass this value into my driver ? 

In documentation, he say that create class like this : 

class MyAlarm(StdService):
"""Service that sends email if an arbitrary expression evaluates true"""

def __init__(self, engine, config_dict):



Thank's
Le lundi 22 juin 2020 00:16:03 UTC+2, Tom Keffer a écrit :
>
> Yes, it's possible to access anything in the dictionary. For example, the 
> name of the database used by the binding wx_binding would be given by
>
> config_dict['Databases']['wx_binding']['database']
>
>
> However, it is rarely necessary to do this. Better to use the functions in 
> manager.py to simply open up the database you need. For example,
>
> db = manager.open_manager_with_config(config_dict, 'wx_binding')
>
>
> would return a database Manager object for the wx_binding.
>
> See the section *Programming interface 
> * in the 
> Customizing Guide.
>
> -tk
>
> On Sun, Jun 21, 2020 at 2:21 PM Florentin Prevost  > wrote:
>
>> Thank you very well for your answer :) 
>>
>> For the first question, sorry, I wanted to say that if it possible to 
>> pass argument that is not in stanza [myWlink] for example. Because I've set 
>> the same parameter for sql database if you know what i mean. 
>>
>>
>> Le dimanche 21 juin 2020 20:58:58 UTC+2, Tom Keffer a écrit :
>>>
>>> Make sure you read the section *Porting to new hardware 
>>> * in the Customizing 
>>> Guide. It answers some of your questions.
>>>
>>> 1. The full configuration information is available as the first argument 
>>> to your driver loader() function as a dictionary. However, in general, 
>>> you should try to keep your driver as modular as possible, and not pick and 
>>> choose information from all over the dictionary. Best practice is to have 
>>> your driver depend on information in its private stanza. For example, if 
>>> your driver is named mywlnk.py, it should have a stanza
>>>
>>> [MyWlink]
>>>
>>> and look there for all its information. But, there are many exceptions 
>>> to this best practice.
>>>
>>> 2. The function genArchiveRecords() is a *generator function*. If you 
>>> don't know what that is, see the section *Generators 
>>> * in the Python documentation. 
>>> It takes one argument: a timestamp with the last time in the database. Your 
>>> function should return all archive records since that time, using a yield 
>>> statement. It will be called at startup and at the end of each archive 
>>> interval. However, exactly when should not be your concern --- that's the 
>>> engine's job.
>>>
>>> -tk
>>>
>>> On Sun, Jun 21, 2020 at 10:18 AM Florentin Prevost  
>>> wrote:
>>>
 Hi,

 I worked with the fork of 
 https://github.com/vinceskahan/weewx-weatherlinklive-json and I would 
 like to ask some questions about driver developpment. 

 - How can I passed argument of weewx.conf to my driver ? I work to 
 request lost data from Weewx on Weatherlink.com because WeatherLink Live 
 don't have API to take archive directly and I would like to passed some 
 arguments like archive_interval, sql password & etc 
 - How work genArchiveRecords when it call? It run as each report ? Or 
 it is a loop that waiting to have return values ?


 Thank you for your answer and support. 

 -- 
 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-de...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-development/d04b1fde-25c3-476d-b885-8d45b682976ao%40googlegroups.com
  
 
 .

>>> -- 
>> 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-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-development/d524dd2b-0369-42ee-b5e5-73194a97fce1o%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 

Re: [weewx-development] Weatherlink Live driver developpment

2020-06-21 Thread Tom Keffer
Yes, it's possible to access anything in the dictionary. For example, the
name of the database used by the binding wx_binding would be given by

config_dict['Databases']['wx_binding']['database']


However, it is rarely necessary to do this. Better to use the functions in
manager.py to simply open up the database you need. For example,

db = manager.open_manager_with_config(config_dict, 'wx_binding')


would return a database Manager object for the wx_binding.

See the section *Programming interface
* in the
Customizing Guide.

-tk

On Sun, Jun 21, 2020 at 2:21 PM Florentin Prevost 
wrote:

> Thank you very well for your answer :)
>
> For the first question, sorry, I wanted to say that if it possible to pass
> argument that is not in stanza [myWlink] for example. Because I've set the
> same parameter for sql database if you know what i mean.
>
>
> Le dimanche 21 juin 2020 20:58:58 UTC+2, Tom Keffer a écrit :
>>
>> Make sure you read the section *Porting to new hardware
>> * in the Customizing
>> Guide. It answers some of your questions.
>>
>> 1. The full configuration information is available as the first argument
>> to your driver loader() function as a dictionary. However, in general,
>> you should try to keep your driver as modular as possible, and not pick and
>> choose information from all over the dictionary. Best practice is to have
>> your driver depend on information in its private stanza. For example, if
>> your driver is named mywlnk.py, it should have a stanza
>>
>> [MyWlink]
>>
>> and look there for all its information. But, there are many exceptions to
>> this best practice.
>>
>> 2. The function genArchiveRecords() is a *generator function*. If you
>> don't know what that is, see the section *Generators
>> * in the Python documentation.
>> It takes one argument: a timestamp with the last time in the database. Your
>> function should return all archive records since that time, using a yield
>> statement. It will be called at startup and at the end of each archive
>> interval. However, exactly when should not be your concern --- that's the
>> engine's job.
>>
>> -tk
>>
>> On Sun, Jun 21, 2020 at 10:18 AM Florentin Prevost 
>> wrote:
>>
>>> Hi,
>>>
>>> I worked with the fork of
>>> https://github.com/vinceskahan/weewx-weatherlinklive-json and I would
>>> like to ask some questions about driver developpment.
>>>
>>> - How can I passed argument of weewx.conf to my driver ? I work to
>>> request lost data from Weewx on Weatherlink.com because WeatherLink Live
>>> don't have API to take archive directly and I would like to passed some
>>> arguments like archive_interval, sql password & etc
>>> - How work genArchiveRecords when it call? It run as each report ? Or it
>>> is a loop that waiting to have return values ?
>>>
>>>
>>> Thank you for your answer and support.
>>>
>>> --
>>> 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-de...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-development/d04b1fde-25c3-476d-b885-8d45b682976ao%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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/d524dd2b-0369-42ee-b5e5-73194a97fce1o%40googlegroups.com
> 
> .
>

-- 
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/CAPq0zEBCujg_VZhiyDBbjgQfMj%3DH%3Dawx5KF_E3rnUCSf7%3Df%3Dvw%40mail.gmail.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-21 Thread Florentin Prevost
Thank you very well for your answer :) 

For the first question, sorry, I wanted to say that if it possible to pass 
argument that is not in stanza [myWlink] for example. Because I've set the 
same parameter for sql database if you know what i mean. 


Le dimanche 21 juin 2020 20:58:58 UTC+2, Tom Keffer a écrit :
>
> Make sure you read the section *Porting to new hardware 
> * in the Customizing 
> Guide. It answers some of your questions.
>
> 1. The full configuration information is available as the first argument 
> to your driver loader() function as a dictionary. However, in general, 
> you should try to keep your driver as modular as possible, and not pick and 
> choose information from all over the dictionary. Best practice is to have 
> your driver depend on information in its private stanza. For example, if 
> your driver is named mywlnk.py, it should have a stanza
>
> [MyWlink]
>
> and look there for all its information. But, there are many exceptions to 
> this best practice.
>
> 2. The function genArchiveRecords() is a *generator function*. If you 
> don't know what that is, see the section *Generators 
> * in the Python documentation. 
> It takes one argument: a timestamp with the last time in the database. Your 
> function should return all archive records since that time, using a yield 
> statement. It will be called at startup and at the end of each archive 
> interval. However, exactly when should not be your concern --- that's the 
> engine's job.
>
> -tk
>
> On Sun, Jun 21, 2020 at 10:18 AM Florentin Prevost  > wrote:
>
>> Hi,
>>
>> I worked with the fork of 
>> https://github.com/vinceskahan/weewx-weatherlinklive-json and I would 
>> like to ask some questions about driver developpment. 
>>
>> - How can I passed argument of weewx.conf to my driver ? I work to 
>> request lost data from Weewx on Weatherlink.com because WeatherLink Live 
>> don't have API to take archive directly and I would like to passed some 
>> arguments like archive_interval, sql password & etc 
>> - How work genArchiveRecords when it call? It run as each report ? Or it 
>> is a loop that waiting to have return values ?
>>
>>
>> Thank you for your answer and support. 
>>
>> -- 
>> 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-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-development/d04b1fde-25c3-476d-b885-8d45b682976ao%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/d524dd2b-0369-42ee-b5e5-73194a97fce1o%40googlegroups.com.


Re: [weewx-development] Weatherlink Live driver developpment

2020-06-21 Thread Tom Keffer
Make sure you read the section *Porting to new hardware
* in the Customizing
Guide. It answers some of your questions.

1. The full configuration information is available as the first argument to
your driver loader() function as a dictionary. However, in general, you
should try to keep your driver as modular as possible, and not pick and
choose information from all over the dictionary. Best practice is to have
your driver depend on information in its private stanza. For example, if
your driver is named mywlnk.py, it should have a stanza

[MyWlink]

and look there for all its information. But, there are many exceptions to
this best practice.

2. The function genArchiveRecords() is a *generator function*. If you don't
know what that is, see the section *Generators
* in the Python documentation. It
takes one argument: a timestamp with the last time in the database. Your
function should return all archive records since that time, using a yield
statement. It will be called at startup and at the end of each archive
interval. However, exactly when should not be your concern --- that's the
engine's job.

-tk

On Sun, Jun 21, 2020 at 10:18 AM Florentin Prevost 
wrote:

> Hi,
>
> I worked with the fork of
> https://github.com/vinceskahan/weewx-weatherlinklive-json and I would
> like to ask some questions about driver developpment.
>
> - How can I passed argument of weewx.conf to my driver ? I work to request
> lost data from Weewx on Weatherlink.com because WeatherLink Live don't have
> API to take archive directly and I would like to passed some arguments like
> archive_interval, sql password & etc
> - How work genArchiveRecords when it call? It run as each report ? Or it
> is a loop that waiting to have return values ?
>
>
> Thank you for your answer and support.
>
> --
> 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/d04b1fde-25c3-476d-b885-8d45b682976ao%40googlegroups.com
> 
> .
>

-- 
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/CAPq0zEDHNGfqZF%3DWGyBSDs6fKPsJ6gibh2eZGMx3%3DJnkk9-F7g%40mail.gmail.com.