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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Re: [weewx-development] Weatherlink Live driver developpment

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

Re: [weewx-development] Weatherlink Live driver developpment

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

Re: [weewx-development] Weatherlink Live driver developpment

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

Re: [weewx-development] Weatherlink Live driver developpment

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

Re: [weewx-development] Weatherlink Live driver developpment

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

Re: [weewx-development] Weatherlink Live driver developpment

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

Re: [weewx-development] Weatherlink Live driver developpment

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

Re: [weewx-development] Weatherlink Live driver developpment

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

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

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

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

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 =

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

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

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

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

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

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:

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

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,

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

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

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:

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

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

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():

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:

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 :

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

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

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

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

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

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

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:

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

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,

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

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

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.