Scott, please...send me an email to runahue at gmail and we make some tests.


El martes, 20 de agosto de 2019, 17:18:21 (UTC+2), Ruben Navarro Huedo 
escribió:
>
> Scott: If it is running i can test it.
> Is it getting LOOP data from weatherlink.com ?
>
>
> El viernes, 16 de agosto de 2019, 1:51:59 (UTC+2), Scott Shambarger 
> escribió:
>>
>>
>>
>> On Wednesday, August 7, 2019 at 6:11:01 AM UTC-7, mwall wrote:
>>  
>>
>>> ...- summertime activities keep getting in the way :)
>>>
>>> Too true... happily I finally had a day or so to work on the driver...
>>
>> I ended up adding more than just the LOOP packet parsing though, 
>> including:
>>  - pulling station settings from the StationStatus api (archive interval, 
>> rain bucket size, and station timezone), so they are optional in the config 
>> now...
>>  - timezone handling for archive packets...added code for both named 
>> timezones and fixed-offset ones, but I'm not sure how the fixed-offset are 
>> exposed via the API, so that may not work (codes there, and setting them 
>> directly in weewx.conf works).
>>   NOTE: named timezones require pytz, but if it's not installed, then the 
>> driver falls-back to the original localtime handling...
>>  - added support for wee_config
>>  - added support for wee_driver --info so that the config can be easily 
>> tested
>>  - added test for downloading/parsing archive packets
>>  - lots of options when running the wlink.py directly for testing...
>>
>> I've tested it with python 2.6 and 2.7, and tried as many error cases as 
>> I could, but i only have the one weather station to test with :)
>>
>> Let me know if you find any glaring errors...
>>
>> Thanks,
>> Scott
>>
>>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/46003eec-7017-445f-9215-7f81d0315ab8%40googlegroups.com.

Reply via email to