How i can achive data only when i received "all" Packet?

S1m0n3

unread,

Dec 5, 2019, 10:26:58 AM12/5/19

to weewx-user

Hello, i've tried to search but don't found nothing about it. I'm using an WH3080 with Solar and UV Panel and intercept the data via SDR. The problem is that sometimes (and I don't understand when) are shown only the data relating to the UV and Solar package or only the classical data (temperature, humidity, etc ...). For those who do not know the station transmits 3 different packages, one containing the time, one the temperature, rain and humidity information and one containing data on solar radiation. Is it possible in some way to archive the data only after both data have been received in order to overcome this problem?

Simone, Thanks!

Thomas Keffer

unread,

Dec 5, 2019, 10:59:37 AM12/5/19

to weewx-user

What you have is a "partial packet" station. As you describe, different packets contain different kinds of data. No one packet contains all types of data.

WeeWX accumulates the irregular partial packets, then at regular intervals, it extracts full records out of them. These are then put in the database. This is its normal mode. You don't have to do anything.

See the section Loop packets vs archive records in the Customizing Guide for more details.

-tk

On Thu, Dec 5, 2019 at 8:27 AM S1m0n3 <simone....@gmail.com> wrote:

Hello, i've tried to search but don't found nothing about it. I'm using an WH3080 with Solar and UV Panel and intercept the data via SDR. The problem is that sometimes (and I don't understand when) are shown only the data relating to the UV and Solar package or only the classical data (temperature, humidity, etc ...). For those who do not know the station transmits 3 different packages, one containing the time, one the temperature, rain and humidity information and one containing data on solar radiation. Is it possible in some way to archive the data only after both data have been received in order to overcome this problem?

Simone, Thanks!

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/2ca0c782-84e6-49cf-a073-435e82b469b5%40googlegroups.com.

S1m0n3

unread,

Dec 5, 2019, 11:51:35 AM12/5/19

to weewx-user

Yep, this is true in the databse all data are achived! But the problem (I think) is with Current conditions. Because some times in is shown in the website (and also in the realtime.txt that i generated with weewx-crt) only packet of temp, hum and rain and some times only the packet with solar data. Why this?

Il giorno giovedì 5 dicembre 2019 16:59:37 UTC+1, Thomas Keffer ha scritto:

What you have is a "partial packet" station. As you describe, different packets contain different kinds of data. No one packet contains all types of data.

WeeWX accumulates the irregular partial packets, then at regular intervals, it extracts full records out of them. These are then put in the database. This is its normal mode. You don't have to do anything.

See the section Loop packets vs archive records in the Customizing Guide for more details.

-tk

On Thu, Dec 5, 2019 at 8:27 AM S1m0n3 <simone....@gmail.com> wrote:

Hello, i've tried to search but don't found nothing about it. I'm using an WH3080 with Solar and UV Panel and intercept the data via SDR. The problem is that sometimes (and I don't understand when) are shown only the data relating to the UV and Solar package or only the classical data (temperature, humidity, etc ...). For those who do not know the station transmits 3 different packages, one containing the time, one the temperature, rain and humidity information and one containing data on solar radiation. Is it possible in some way to archive the data only after both data have been received in order to overcome this problem?

Simone, Thanks!

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.

To unsubscribe from this group and stop receiving emails from it, send an email to weewx...@googlegroups.com.

Thomas Keffer

unread,

Dec 5, 2019, 11:59:59 AM12/5/19

to weewx-user

The $current tag used in the WeeWX templates uses the full record, so it has all the data.

The extension weewx-crt and the file realtime.txt are not part of WeeWX, so you would have to ask the author.

-tk

To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/6cdfea07-a8a9-481a-b65d-f02ac3e67927%40googlegroups.com.

S1m0n3

unread,

Dec 5, 2019, 12:07:22 PM12/5/19

to weewx-user

Ok, for weewx-crt but the same problem is with $current and data sent to Wunderground, happens only a few times that the report is incomplete, I've archive_interval set to 60 secs, maybe I can increase it? Also $current is populated only when there is an archive record?

Thanks!

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/6cdfea07-a8a9-481a-b65d-f02ac3e67927%40googlegroups.com.

mwall

unread,

Dec 5, 2019, 12:26:29 PM12/5/19

to weewx-user

On Thursday, December 5, 2019 at 11:51:35 AM UTC-5, S1m0n3 wrote:

Yep, this is true in the databse all data are achived! But the problem (I think) is with Current conditions. Because some times in is shown in the website (and also in the realtime.txt that i generated with weewx-crt) only packet of temp, hum and rain and some times only the packet with solar data. Why this?

the weewx-crt extension will use either archive data or loop data, depending on how you configured it. use the 'binding' option to control it:

[CumulusRealTime]

binding = loop # loop or archive, default is loop

for loop data, it will emit a string that (may) have only some observations

for archive data, the string should contain all observations

S1m0n3

unread,

Dec 5, 2019, 1:12:18 PM12/5/19

to weewx-user

thanks for the suggestion, already do it, but without results. However also current report have a problem...

I attach a couple of screens and my weewx.conf for more clarity...

CurrentConditions.jpg

weewx.conf

S1m0n3

unread,

Dec 5, 2019, 1:36:30 PM12/5/19

to weewx-user

Starting weewx directly I can see that some times is recorded only certain data.

pi@raspberrypi:/etc/weewx $ sudo weewxd weewx.conf

LOOP: 2019-12-05 19:29:23 CET (1575570563) altimeter: 1024.07359709, appTemp: 4.2191466395, barometer: 1026.31573074, cloudbase: 1528.67207528, dateTime: 1575570563, dewpoint: 0.125855991736, heatindex: 6.9, humidex: 6.9, inDewpoint: 5.28062060313, inHumidity: 36.6881925288, inTemp: 20.6116649542, maxSolarRad: None, outBatteryStatus: 0, outHumidity: 62.0, outTemp: 6.9, pressure: 944.132230441, rain: None, rain_total: 0.0, rainRate: 0.0, usUnits: 16, windchill: 6.9, windDir: 135.0, windGust: 4.89601216896, windSpeed: 3.67200912672

LOOP: 2019-12-05 19:29:23 CET (1575570563) altimeter: 1024.04466293, appTemp: 4.2191466395, barometer: 1026.28628886, cloudbase: 1528.67207528, dateTime: 1575570563, dewpoint: 0.125855991736, heatindex: 6.9, humidex: 6.9, inDewpoint: 5.28062060313, inHumidity: 36.6881925288, inTemp: 20.6116649542, maxSolarRad: None, outBatteryStatus: 0, outHumidity: 62.0, outTemp: 6.9, pressure: 944.105146158, rain: 0.0, rain_total: 0.0, rainRate: 0.0, usUnits: 16, windchill: 6.9, windDir: 135.0, windGust: 4.89601216896, windSpeed: 3.67200912672

LOOP: 2019-12-05 19:30:07 CET (1575570607) dateTime: 1575570607, inDewpoint: 5.26733505035, inHumidity: 36.6654703931, inTemp: 20.6067191307, maxSolarRad: None, radiation: 1.249, rainRate: 0.0, usUnits: 16, UV: 0.0

LOOP: 2019-12-05 19:30:07 CET (1575570607) dateTime: 1575570607, inDewpoint: 5.27606165308, inHumidity: 36.6654064294, inTemp: 20.616610778, maxSolarRad: None, radiation: 1.249, rainRate: 0.0, usUnits: 16, UV: 0.0

LOOP: 2019-12-05 19:30:07 CET (1575570607) dateTime: 1575570607, inDewpoint: 5.27169835894, inHumidity: 36.6654384162, inTemp: 20.6116649542, maxSolarRad: None, radiation: 1.249, rainRate: 0.0, usUnits: 16, UV: 0.0

LOOP: 2019-12-05 19:30:11 CET (1575570611) altimeter: 1024.11531263, appTemp: 3.5051466395, barometer: 1026.35817831, cloudbase: 1528.67207528, dateTime: 1575570611, dewpoint: 0.125855991736, heatindex: 6.9, humidex: 6.9, inDewpoint: 5.2629717273, inHumidity: 36.6655023602, inTemp: 20.6017733075, maxSolarRad: None, outBatteryStatus: 0, outHumidity: 62.0, outTemp: 6.9, pressure: 944.17127897, rain: 0.0, rain_total: 0.0, rainRate: 0.0, usUnits: 16, windchill: 5.54370388825, windDir: 135.0, windGust: 8.56802129569, windSpeed: 7.34401825345

LOOP: 2019-12-05 19:30:59 CET (1575570659) altimeter: 1024.07359709, appTemp: 3.7431466395, barometer: 1026.31573074, cloudbase: 1528.67207528, dateTime: 1575570659, dewpoint: 0.125855991736, heatindex: 6.9, humidex: 6.9, inDewpoint: 5.27616009846, inHumidity: 36.6768154914, inTemp: 20.6116649542, maxSolarRad: None, outBatteryStatus: 0, outHumidity: 62.0, outTemp: 6.9, pressure: 944.132230441, rain: 0.0, rain_total: 0.0, rainRate: 0.0, usUnits: 16, windchill: 5.88500495833, windDir: 135.0, windGust: 8.56802129569, windSpeed: 6.1200152112

REC: 2019-12-05 19:30:00 CET (1575570600) altimeter: 1024.05913001, appTemp: 4.2191466395, barometer: 1026.3010098, cloudbase: 1528.67207528, dateTime: 1575570600.0, dewpoint: 0.125855991736, ET: 8.47310725735e-06, heatindex: 6.9, humidex: 6.9, inDewpoint: 5.28062060313, inHumidity: 36.6881925288, inTemp: 20.6116649542, interval: 1, maxSolarRad: None, outBatteryStatus: 0.0, outHumidity: 62.0, outTemp: 6.9, pressure: 944.1186883, rain: 0.0, rain_total: 0.0, rainRate: 0.0, usUnits: 16, windchill: 6.9, windDir: 135.0, windGust: 4.89602433796, windGustDir: 135.0, windrun: 0.0612003042245, windSpeed: 3.67201825347

LOOP: 2019-12-05 19:31:07 CET (1575570667) dateTime: 1575570667, inDewpoint: 5.27169835894, inHumidity: 36.6654384162, inTemp: 20.6116649542, maxSolarRad: None, radiation: 1.249, rainRate: 0.0, usUnits: 16, UV: 0.0

LOOP: 2019-12-05 19:31:07 CET (1575570667) dateTime: 1575570667, inDewpoint: 5.26733505035, inHumidity: 36.6654703931, inTemp: 20.6067191307, maxSolarRad: None, radiation: 1.249, rainRate: 0.0, usUnits: 16, UV: 0.0

LOOP: 2019-12-05 19:31:07 CET (1575570667) dateTime: 1575570667, inDewpoint: 5.26723538386, inHumidity: 36.6540613031, inTemp: 20.6116649542, maxSolarRad: None, radiation: 1.249, rainRate: 0.0, usUnits: 16, UV: 0.0

LOOP: 2019-12-05 19:32:07 CET (1575570727) dateTime: 1575570727, inDewpoint: 5.2449019493, inHumidity: 36.5971751703, inTemp: 20.6116649542, maxSolarRad: None, radiation: 1.249, rainRate: 0.0, usUnits: 16, UV: 0.0

REC: 2019-12-05 19:32:00 CET (1575570720) dateTime: 1575570720.0, ET: 7.91892052817e-06, inDewpoint: 5.26875626438, inHumidity: 36.6616567041, inTemp: 20.6100163464, interval: 1, maxSolarRad: None, radiation: 1.249, rainRate: 0.0, usUnits: 16, UV: 0.0

gjr80

unread,

Dec 5, 2019, 3:30:13 PM12/5/19

to weewx-user

Hi,

First thing I would be doing to address the incomplete data on your page is to increase your archive interval from one minute to something like five minutes. The problem with partial packet stations is that when your archive interval is close to the length of the interval between sensor updates you run the risk of having no updates for that particular sensor(s) in an archive period. This will result in $current having no data to display for that sensor(s). Having a very short archive interval may be good in that it provides more frequent updates but for partial packet stations it can be problematic.

Gary

Simone R

unread,

Dec 5, 2019, 3:38:58 PM12/5/19

to weewx...@googlegroups.com

Clear, thanks for your suggestion, I try to increase interval to 180-300 secs! ;-)

--
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/7iAvruvSHyc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/52df0557-7b98-479b-a726-793ea4517edc%40googlegroups.com.

Thomas Keffer

unread,

Dec 5, 2019, 4:32:16 PM12/5/19

to weewx-user

The values in $current are the values accumulated over the archive interval. If your interval is as short as 60 seconds, it's possible that not all data have been seen in that time, so, of course, you're going to be missing data. A value of 300 seconds (5 minutes) tends to work better.

-tk

To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/6e39c6d9-86a3-46f4-b93f-46653688ff62%40googlegroups.com.

Reply all

Reply to author

Forward