Question?

[paulober]

What do you mean with: "Not support historical data support". I thought the data will be saved in weewx db from when it get's connected to weatherstation via WeatherLink Live Access point's local api?

[paulober]

And you say: The local api allows up to 2.5 secs for polling but in the configuration min value is set to 10 secs?

[michael-slx]

Regarding the historical data: Yes, it is obviously stored in WeeWX's database. However, the WeatherLink Live also has it's own internal data logger, e.g. for when the power goes out (it can run on batteries). There is currently no easy way to read that internal storage.

2.5 second polling: Only wind and rain sensors are supported for that 2.5 seconds-API. It works by automatically sending out that data every 2.5 seconds, whereas the rest of the sensors (temperature, humidity, etc.) have to be polled by the driver. That's where the interval can be configured. I've personally had issues with intervals below 10 seconds, e.g. the WeatherLink got stuck or acted weird. Additionally, there is little to gain with faster polling anyway since all sensors except wind and rain update only every 15 - 30 seconds.

[paulober]

Ok, thank you for the quick response.

[paulober]

I have one last (hopefully) question: How does this work if I want to record the fastest wind speed, for example? Because if I only query data every 3 minutes, I probably won't measure exactly when the speed was fastest? And are there any options that in my web interface I update the data every 15 seconds, but only store it in the DB every 3 minutes unless it is for example the fastest wind speed or the largest amount of water I have so far?

Kind regards
@paulober

[PavLL]

?

[PavLL]

what tf do you want from me

[michael-slx]

? idk

I'm helping out @paulober. Did you get a notification?

[paulober]

what tf do you want from me

Sry, I changed my username from pavll to paulober. So now you were mentioned in every commit I've done because you claimed my old username

[michael-slx]

The driver itself only has the polling_interval option and it's usually best to leave that at the default 10 seconds.

To control how often the data is stored in the database, use WeeWX's archive_interval option. The high/low/sum values are then automatically calculated and stored in the database. Take a look at WeeWX documentation for more info.

Note that WeeWX by itself doesn't do anything with the 2.5 second push updates except calculate the summary every archive interval. You might want to look into third-party plugins and skins that do make use of that data.

[paulober]

Ok, thanks. That's what I was searching for. Ok and if between the 10 secs of the Weatherlink Live polling one strong wind speed of 60 km/h, for example, take place but a few secs later when I poll the wind speed is back on 40 km/h. The WeeWX will not recognize 60 km/h peak as max and store it along?

Also, I put polling_interval = 10 and archive_interval = 300 but the website only refreshes once every 5 minutes how can i refresh the page more often than I want the software to data into DB?

[michael-slx]

[...] if between the 10 secs of the Weatherlink Live polling one strong wind speed of 60 km/h, for example, take place but a few secs later when I poll the wind speed is back on 40 km/h. The WeeWX will not recognize 60 km/h peak as max and store it along?

Yes, the maximum wind speed will be recognized. The sensor itself sends a new value every 2.5 seconds and that value is immediately sent to WeeWX, so no wind (or rain) values are lost.

[...] how can i refresh the page more often than I want the software to data into DB?

That's not possible with WeeWX.

[paulober]

Ok, thank you for all the information. So for making my website live refresh like on https://belchertownweather.com/ I would need to make a plugin that makes use of the 2.5-second push values and then refresh the report without triggering an archive action.

[michael-slx]

Yes, kind of.

Regenerating the report every 2.5 seconds and uploading it would be too much. Instead, this site uses the WeeWX MQTT plugin and a separate MQTT/Websockets server to forward the data.

The weewx-belchertown GitHub repository describes this very well: https://github.com/poblabs/weewx-belchertown#mqtt-and-mqtt-websockets-optional

[paulober]

How can i get the telemetry from the driver containing battery and signal strength etc... ?

[michael-slx]

Examples for battery are shown in the README (battery mapper), look at the mapping examples.

Signal strength is not supported by the WeatherLink Live.

[paulober]

I allready did this but there isn't any battery data in my loop packages.

[michael-slx]

Can you post your mapping config line?

[paulober]

mapping = th:1, th_indoor, baro, rain:1, wind:1, uv:1, solar:1, thw:1, thsw:1:appTemp, windchill:1, battery:1:outTemp:rain:wind:uv

[michael-slx]

OK, that looks good.

So there's no battery info in any LOOP packet? I'm asking because the battery data only gets polled every 10 seconds or whatever your polling interval is set at, that's normal.
But it should be at least included in the ARCHIVE packets.

[paulober]

This is one of the bigger loop packages where battery is included but it's 0.0.
{"outTemp_C": "1.1666666666666674", "outHumidity": "82.5", "dewpoint_C": "-1.4999999999999996", "heatindex_C": "1.1666666666666674", "wetbulb_C": "0.0", "inTemp_C": "16.27777777777778", "inHumidity": "30.1", "inDewpoint_C": "-1.2777777777777781", "inHeatindex_C": "14.61111111111111", "pressure_mbar": "960.3119540771902", "altimeter_hPa": "1029.360408635459", "UV": "0.0", "radiation_Wpm2": "0.0", "thw_C": "1.1666666666666674", "thsw_C": "0.055555555555556344", "appTemp_C": "0.055555555555556344", "windchill_C": "1.1666666666666674", "batteryStatus1": "0.0", "outTempBatteryStatus": "0.0", "rainBatteryStatus": "0.0", "windBatteryStatus": "0.0", "uvBatteryStatus": "0.0", "dateTime": "1642365001.0", "barometer_mbar": "1033.809967930292", "cloudbase_meter": "921.7087944769806", "humidex_C": "1.1666666666666674", "maxSolarRad_Wpm2": "0.0", "rainRate_cm_per_hour": "0.0", "hourRain_cm": "0.0", "rain24_cm": "0.0", "dayRain_cm": "0.0", "usUnits": "16.0"}

[michael-slx]

Your packet looks good too.

The behavior you're describing is normal:

• Battery status is only polled every 10 seconds
• In WeeWX, battery status 0 means OK, 1 would be Battery Low.

[paulober]

Ah ok, thanks for the info.

[jav4]

I've writing an extension to the driver that can use the protocol the WeatherLink Live uses to communicate with Weatherlink.com and capture the historical data it accumulates while it's disconnected from the network. Right now it requires a brief connection to weatherlink.com when starting (so it isn't 100% offline) but doesn't upload weather information there, it's just kept in WeeWX. It also provides some additional health information not available through the local API.

Is this work of interest to anyone? Code needs some cleaning and filling with details I don't have, but curently works.

[gdt]

@jav4 yes ii's of interest! I suggest you open a PR marked 'draft' with what you have, as soon as you are comfortable doing so, for comment, for others to read and try, to and share the concept. I'm just a user, but if I were the developer that's what I'd want you to do.