--+---+--+---+--+--+--+--++
>>>>>>
>>>>>> 5 rows in set (0.00 sec)
>>>>>>
>>>>>>
>>>>>> Console output (syslog):
>>>>>> Jul 8 15:49:31 ubuntu weewx[3696] DEBUG user.WLLDriver: Packet
>>>>>> received from WLL mod
| 0.20004 | 3.902
>>>>> | NULL | NULL | NULL | 15.612 |
>>>>> | 2020-07-14 18:21:00 | 0 | 4.5875
>>>>> | NULL | NULL | NULL | 15.6458334 |
>>>>>
18:16:00 | 0 | 0
>>> | NULL | NULL | NULL | 15.775 |
>>> | 2020-07-14 18:15:00 | 0 | 0
>>> | NULL | NULL | NULL | 15.775 |
>>> | 2020-07-14 18:1
| 0 | 0
>> | NULL | NULL | NULL | 15.83333333332 |
>> | 2020-07-14 18:13:00 | 0 | 0
>> | NULL | NULL | NULL | 15.916 |
>> | 2020-07-14 18:12:00 | 0 |
>>>>>
>>>>> e order by datetime desc limit 10;
>>>>> +-++-+
>>>>> | from_unixtime(datetime) | rain
645 |
+-++-+
4 rows in set (0.001 sec)
Op dinsdag 14 juli 2020 om 12:24:30 UTC+2 schreef Maarten van der Hoeven:
> New fresh code coming straight from the factory. It's still wet. Running
> it now. Deleted all archived records, and dropped the daily archives. Mor
river: Set
>>>> previous period rain to: 2
>>>> Jul 14 10:17:53 weewximport weewx[881] DEBUG user.WLLDriver: rainRate
>>>> rightnow is : 0.007874015748031498
>>>> Jul 14 10:17:53 weewximport weewx[881] DEBUG user.WLLDriver: Packet
>>>>
t;> Jul 14 10:17:55 weewximport weewx[881] DEBUG urllib3.connectionpool:
>> Starting new HTTP connection (1): 192.168.2.33:80
>> Jul 14 10:17:55 weewximport weewx[881] DEBUG urllib3.connectionpool:
>> http://192.168.2.33:80 "GET /v1/current_conditions HTTP/1.1" 200 Non
usUnits': 1,
>> 'windSpeed': 3.0, 'windDir': 213, 'windGust': 5.0, 'windGustDir': 227,
>> 'rain': 0.0, 'rainRate': 0.007874015748031498}:
>> Jul 14 10:17:55 weewximport weewx[881] DEBUG urllib3.connectionpool:
>> Starting new HTTP connection (1): 192.168.2.33:80
>> J
Screen shot of weatherlink, two rainticks
Op dinsdag 14 juli 2020 om 10:19:23 UTC+2 schreef Maarten van der Hoeven:
> Okay, got the first to rain ticks (of 0.2 mm each). First rain tick at
> about 09:50 and second rain tick at about 10:08 (verified with my other
> weewx-environment
0-07-14 10:17:53 CEST (1594714673)
Op dinsdag 14 juli 2020 om 08:22:39 UTC+2 schreef Maarten van der Hoeven:
> Yup, started your driver this morning. Will watch it.
>
> Op maandag 13 juli 2020 om 22:34:12 UTC+2 schreef flor...@pre-vost.fr:
>
>> Can you try my latest version ?
Yup, started your driver this morning. Will watch it.
Op maandag 13 juli 2020 om 22:34:12 UTC+2 schreef flor...@pre-vost.fr:
> Can you try my latest version ?
>
> It seems that tomorrow rain ^^
>
--
You received this message because you are subscribed to the Google Groups
"weewx-development"
gt;>>>> |0 | 4.5997194 |0 |
>>>>> | 1594224240 | 2020-07-08 18:04:00 | 0
>>>>> |0 | 1.999878 |0 |
>>>>> | 1594224180 | 2020-07-08 18:03:00 | 0
>>>&
t; indoor_data = weather_data['sensors'][3]['data']
>>
>>
> On Wednesday, July 8, 2020 at 9:53:38 PM UTC+2, Maarten van der Hoeven
> wrote:
>>
>> maarten@ubuntu:~/weatherlink$ python3 weewx_weatherlink -s
>> 2020-07-07T12:00 -e 2020-07-07T12:30
>> Use dates
a few minutes, due to the timestamp
> in the signature) and post it.
>
>
>
>
> On Wednesday, July 8, 2020 at 9:10:36 PM UTC+2, Maarten van der Hoeven
> wrote:
>>
>> If I change the code to (#2, #0 and #3 are the values in your code), the
>> data is import
| 0 |
>> 0 | 1.5999024 |0 |
>> | 1594222920 | 2020-07-08 17:42:00 | 0 |
>> 0 | 1.5999024 |0 |
>> | 1594222860 | 2020-07-08 17:41:00 | 0 |
>> 0 | 1.5999024 |0 |
>> |
indoor_data = weather_data['sensors'][3]['data'] #3
Find attached the produced cvs, now filled with correct data
Op woensdag 8 juli 2020 om 21:10:36 UTC+2 schreef Maarten van der Hoeven:
> If I change the code to (#2, #0 and #3 are the values in your code), the
> data is imported okay (
>
> https://github.com/grebleem/weewx_wl_import
>
> Thanks.
>
>
> On Tuesday, July 7, 2020 at 1:09:34 PM UTC+2, Maarten van der Hoeven wrote:
>>
>> Hi Bastiaan,
>>
>> something I can test?
>>
>> Op zondag 5 j
om 23:07:46 UTC+2 schreef Maarten van der Hoeven:
> Yes, now the csv (although still empty) is created in the 'root'-dir. No
> need for tmp anymore
>
> maarten@ubuntu:~/weatherlink$ ls -las
> total 36
> 4 drwxrwxr-x 2 maarten maarten 4096 Jul 7 23:06 .
> 4 drwxr-xr-x 24
0 |
++---+---+--++--+
100 rows in set (0.01 sec)
Op woensdag 8 juli 2020 om 15:57:34 UTC+2 schreef Maarten van der Hoeven:
> Okay, got v0.2 running now. My weewx.conf stanza shows (ISS on ID=2,
> extratemp
878 | 0.6 |
>> 16.3989996 | 16.4 |
>> | 2020-07-06 15:05:00 | 0 | 0.6 |
>> 3.39979264 | 30.8 |
>> | 2020-07-06 15:10:00 | 0 |0 |
>> 1.3999146 | 3.2 |
&
:
> Somehow the tmp/ dir is not created. I dropped the tmp for now. Can you
> try again?
>
>
>
> On Tuesday, July 7, 2020 at 9:57:43 PM UTC+2, Maarten van der Hoeven wrote:
>>
>> Okay, have played with it.
>>
>> First I needed to create a tmp-directory. With
u want you can give the importer a try:
>
> https://github.com/grebleem/weewx_wl_import
>
> Thanks.
>
>
> On Tuesday, July 7, 2020 at 1:09:34 PM UTC+2, Maarten van der Hoeven wrote:
>>
>> Hi Bastiaan,
>>
>> something I c
1.4 |
+---+---+--++--+
21 rows in set (0.86 sec)
Op dinsdag 7 juli 2020 om 12:12:57 UTC+2 schreef Maarten van der Hoeven:
> Same goes when records come from WLLDriver, same mismatch in
> rounding/conversion
>
> mysql> select
> from_unixtime(weewx.archive.date
Hi Bastiaan,
something I can test?
Op zondag 5 juli 2020 14:02:38 UTC+2 schreef flor...@pre-vost.fr:
>
> Sorry for that.
>
> There was a misunderstandings . Let's forget this conversation;)
>
> -fp
>
> Le samedi 4 juillet 2020 à 13:36:23 UTC+2, hoev...@gmail.com a écrit :
>
>> Yes, agree. I
--+
10 rows in set (1.92 sec)
Op dinsdag 7 juli 2020 12:10:45 UTC+2 schreef Maarten van der Hoeven:
>
> Did testing with WLLArchive.
>
> WLLArchive is picking up archived records, just from the point where
> records are missing.Thats good. I've stopped weewx for two days (we
Did testing with WLLArchive.
WLLArchive is picking up archived records, just from the point where
records are missing.Thats good. I've stopped weewx for two days (weewxtest
in my case, not production), and Weatherlink.com is queried to get the
missing records.
I see in mysql there's a
Updated the driver, thanks for that. Windspeed/-gust is much better now.
However, I see some differences in the windgust, when it is within a
UDP-packet and when it's within a current-condition-packet. Some piece of
syslog, where I highlighted the difference in values. For what I
understand,
Jul 4 17:39:37 ubuntu weewx[20924] DEBUG user.WLLDriver: Packet received
from WLL module {'dateTime': 1593877175, 'usUnits': 17, 'windSpeed': 5.36,
'windDir': 210, 'windGust': 8.05, 'windGustDir': 211, 'rain': 0.0,
'rainRate': 0.0}:
Jul 4 17:39:37 ubuntu weewx[20924] INFO weewx.restx: MQTT:
econd2'
group_temperature = degree_C# Options are 'degree_F' or
'degree_C'
Op zaterdag 4 juli 2020 13:44:15 UTC+2 schreef Maarten van der Hoeven:
>
> Some findings
>
> I cannot stop the weewx process by ' /etc/init.d/weewx stop', it keeps
> running for several minute
0 13:28:16 UTC+2 schreef Maarten van der Hoeven:
>
> Yes, apologies. Working now. I had the 'old' config of WLL still in
> place. Did only change WLLArchive according to the readme...
>
> It is getting archive records, will test it today!
>
>
> Op zaterdag 4 juli 2020 om
Yes, agree. I like the weather, I like programming, I like to cooperate.
It's my current lack of python-knowledge that I want to contribute the best
I can do right now, and that is testing both of your drivers. I dont see it
as competition, and may the best win. Far from that. In the end, it's
Yes, apologies. Working now. I had the 'old' config of WLL still in place.
Did only change WLLArchive according to the readme...
It is getting archive records, will test it today!
Op zaterdag 4 juli 2020 om 12:35:04 UTC+2 schreef flor...@pre-vost.fr:
> Hi,
>
> Like in Readme on Github,
ain and it looks good. Thank you for
> testing.
>
> The WeatherLink v2 API <https://weatherlink.github.io/v2-api/> weewx-import
> will
> go live tonight or tomorrow, so you can import large periods from
> WeatherLink to weewx.
>
>
> On Saturday, July 4, 2020 at 11:56
I did run the driver for a couple of days now, all data seems okay to me.
Today it is said it's going to rain, so going to test that data as well
today.
Op donderdag 2 juli 2020 om 19:38:42 UTC+2 schreef Maarten van der Hoeven:
> Yes, okay now (two top records). It gave me also the opportun
Hi, not sure it the driver is ready to go. But I saw a commit on github 12
hours ago, so I thought, lets give it a try :)
weewx.conf:
[WLLDriver]
driver = user.WLLDriver
max_tries = 5
retry_wait = 5
poll_interval = 5
udp_enable = 1
hostname = 192.168.2.33
wl_apikey =
an import this file. Keep you posted!
>
>
> On Thursday, July 2, 2020 at 2:50:13 PM UTC+2, Maarten van der Hoeven
> wrote:
>>
>> A question. Is 'rain' still work in progress? I notice a repeating
>> NULL-value (no worries, testing against a test-database within a virtual
ULL | 0.004320916570420523 |
++-+++--+---+
10 rows in set (0.01 sec)
Op donderdag 2 juli 2020 om 13:44:43 UTC+2 schreef Maarten van der Hoeven:
> Yes, that makes a difference! Also showing okay on the w
t;
> On Thursday, July 2, 2020 at 9:57:25 AM UTC+2, Maarten van der Hoeven
> wrote:
>>
>> No data in whatever extratemp. I got the external sensor on channel id =
>> 3 (hence extra_id=3), but I suspect the data comes into extratemp1. I d not
>> have any preference
an you check the latest development build:
> https://github.com/grebleem/weewx-weatherlinkliveudp/archive/development.zip
>
> If you add this to the stanza
> extra_id =3
>
> You should have the extra sensor data in weewx.
>
>
> On Tuesday, June 30, 2020 at 10:08:26 PM
Yes, I like the idea. A seperate program that pulls data from Weatherlink
and stores the data in sqlite or mysql (whatever is configured in
weewx.conf). And let weewx do the aggreate and daily summaries
Op dinsdag 30 juni 2020 19:05:43 UTC+2 schreef Bastiaan Meelberg:
>
> Ik like the idea of
t;>>> | 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: {}
>>>>
gt; 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
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(da
000=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 P
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
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
_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,&
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
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":
yRain_mm": "0.0", "usUnits": "16.0"}
>
>
> The Belchertown skin is not altering the MQTT message, so I made this
> change to the weewx.conf file to display the correct unit:
>
> # Various options for customizing your reports.
>
> [[Defaults]]
&
Driver updated, data is okay now!
Also running MQTT and bechertown: I see windspeed reported as km/h,
although I've set the unit to m/s in weewx.conf
Yes, tx_id 3 is an extra temp sensor. I've got the ISS on ID=2, and the
temp sensor on ID=3
Op zondag 28 juni 2020 om 11:48:59 UTC+2 schreef
']:
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-e
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).
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.weathe
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
> pol
i-key" has value "nivwsekqwfbkhqtqwo8nximhl7zgxpcs"
>>>>>> Parameter name: "api-secret" has value "ABC123"
>>>>>> Parameter name: "end-timestamp" has
gt;> Parameter name: "end-timestamp" has value "1593204600"
>>>> Parameter name: "start-timestamp" has value "1593118200"
>>>> Parameter name: "station-id" has value "91978"
>>>> Parameter name: "
uot; has value "ABC123"
>> Parameter name: "end-timestamp" has value "1593204600"
>> Parameter name: "start-timestamp" has value "1593118200"
>> Parameter name: "station-id" has value "91978"
>> Para
uot;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&q
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
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 :
>
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:
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
I am happy to test your driver in development. I have a Weather Link Live
running for test purposes, so I can play with it.
Op zondag 21 juni 2020 19:18:41 UTC+2 schreef Florentin Prevost:
>
> Hi,
>
> I worked with the fork of
> https://github.com/vinceskahan/weewx-weatherlinklive-json and I
uot;: "^4.17.2",
> "webpack-bundle-analyzer": "^2.13.1",
> "webpack-cli": "^3.1.2",
> "webpack-merge": "^4.1.4"
>
> 4. Install and build again
>
> *cd weert-js/client*
> *npm install*
>
s*
> lrwxrwxrwx 1 tkeffer tkeffer25 Sep 8 06:21 webpack ->
> ../webpack/bin/webpack.js*
> lrwxrwxrwx 1 tkeffer tkeffer46 Jul 1 10:04 webpack-bundle-analyzer
> -> ../webpack-bundle-analyzer/lib/bin/analyzer.js*
> lrwxrwxrwx 1 tkeffer tkeffer29 Jul 1 10:04
ps://github.com/tkeffer/weert-js#building-and-running-the-client> in
> the README.
>
> -tk
>
> On Tue, Nov 13, 2018 at 5:12 AM Maarten van der Hoeven > wrote:
>
>> Sorry, not completed my message. I am quite experienced at Linux, so I
>> understand the pointers to lo
e":11.666,"gauge_pressure":1019.3588138825883,"heatindex_temperature":11.666,"in_humidity_percent":58,"in_temperature":21.5,"out_humidity_percent":81,"out_temperature":11.666,"radiation_radiation":308,"
Hi,
I've taken notice of the remark about a steep learning curve. However, I've
installed all according to the manual, and I see data posted (trail of ndm
with posted data every second or so) and data populated into the influx
database.
However, when I access the webpage
70 matches
Mail list logo
