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&t=1593206474&start-timestamp=1593120000&end-timestamp=1593206400&api-signature=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 [email protected]:
>>
>>> Do you've set the api secret ? 
>>>
>>> Le vendredi 26 juin 2020 à 23:09:59 UTC+2, [email protected] a écrit :
>>>
>>>> Hmmm, not sure. Looks like time&date 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 [email protected]:
>>>>
>>>>> 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, [email protected] a écrit :
>>>>>
>>>>>> Okay, URL and responses
>>>>>>
>>>>>>
>>>>>> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs&t=1593205164&start-timestamp=1593118500&end-timestamp=1593204900&api-signature=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c
>>>>>>
>>>>>> code
>>>>>> "401"
>>>>>> message
>>>>>> "Invalid API Signature."
>>>>>>
>>>>>>
>>>>>>
>>>>>> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs&t=1593205164&start-timestamp=1593118500&end-timestamp=1593204900&api-signature=2459c09bc4e1f00ab25912b82ab1df0db96860afff1b0194df98fc752cdf8f2c
>>>>>>
>>>>>> code
>>>>>> "401"
>>>>>> message
>>>>>> "Invalid API Signature."
>>>>>>
>>>>>>
>>>>>>
>>>>>> https://api.weatherlink.com/v2/historic/91978?api-key=nivwsekqwfbkhqtqwo8nximhl7zgxpcs&t=1593205153&start-timestamp=1593118500&end-timestamp=1593204900&api-signature=ae52423cb4b1756a678979aeffe0817d424a26cb5b1b416d0bb40b0838c179da
>>>>>>
>>>>>> code
>>>>>> "401"
>>>>>> message
>>>>>> "Invalid API Signature."
>>>>>>
>>>>>> Op vrijdag 26 juni 2020 om 22:58:12 UTC+2 schreef [email protected]
>>>>>> :
>>>>>>
>>>>>>> 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, [email protected] 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 
>>>>>>>>> [email protected]:
>>>>>>>>>
>>>>>>>>>> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/94ea37cd-5a1c-4f45-b744-12192f0ac06bn%40googlegroups.com.

Reply via email to