Needed to see that log on the big screen, too much info for the iPad.
When I look through that log things seem to be working as they should. I am
not familiar with the interceptor driver but as I understand it when used
in observer mode the dateTime field for each packet is derived from the UTC
timestamp in the data posted to WU, if the UTC timestamp is not there the
system time is used instead. If we look at 19:17:33 the following data was
sniffed:
Oct 25 19:17:33 debian6-ANN weewx[6499]: interceptor: ServerThread: SNIFF:
ID=xxxxxxx&PASSWORD=XXXX&indoortempf=79.7&tempf=75.6&dewptf=65.1&windchillf=
75.6&indoorhumidity=81&humidity=70&windspeedmph=2.2&windgustmph=4.9&winddir=
77&absbaromin=29.98&baromin=29.99&rainin=0.00&dailyrainin=0.00&weeklyrainin=
0.00&monthlyrainin=0.11&yearlyrainin=-9999&solarradiation=0.00&UV=0&dateutc=
2018-10-25%2011:17:38&softwaretype=WeatherSmart%V1.7.0&action=updateraw&
realtime=1&rtfreq=5 HTTP/1.0#015#012Accept:*/*#015#012Host:
rtupdate.wunderground.com#015#012Connection: Close#015#012#015
dateutc is '2018-10-25 11:17:38' which is close enough to your local time
(+8 hours), this sniffed data was converted to the following raw packet:
Oct 25 19:17:33 debian6-ANN weewx[6499]: interceptor: MainThread: raw packet
: {'wind_speed': 3.1000000000000001, 'humidity_in': 80.0, 'temperature_in':
79.700000000000003, 'barometer': 29.989999999999998, 'windchill':
75.599999999999994, 'dewpoint': 65.099999999999994, 'humidity_out': 70.0,
'uv': 0.0, 'radiation': 0.0, 'rain': None, 'dateTime': 1540466108,
'pressure': 29.98, 'temperature_out': 75.599999999999994, 'wind_dir': 11.0,
'rain_total': 0.0, 'usUnits': 1, 'wind_gust': 4.9000000000000004}
which is interesting as timestamp 1540466108 is actually 19:15:08 in your
local time. Close but not the same as the sniffed data. This timestamp then
propagates through to the mapped packet:
Oct 25 19:17:33 debian6-ANN weewx[6499]: interceptor: MainThread: mapped
packet: {'barometer': 29.989999999999998, 'windchill': 75.599999999999994,
'dewpoint': 65.099999999999994, 'pressure': 29.98, 'outHumidity': 70.0, 'UV'
: 0.0, 'radiation': 0.0, 'rain': None, 'dateTime': 1540466108, 'windDir':
11.0, 'outTemp': 75.599999999999994, 'windSpeed': 3.1000000000000001,
'inHumidity': 80.0, 'inTemp': 79.700000000000003, 'windGust':
4.9000000000000004, 'usUnits': 1}
The above mapped packet is the loop data that weeWX accumulates to
ultimately produce an archive record, the archive record that this packet
contributed to is logged in these lines:
Oct 25 19:28:30 debian6-ANN weewx[6499]: manager: Added record 2018-10-25 19
:20:00 CST (1540466400) to database 'weewx.sdb'
Oct 25 19:30:16 debian6-ANN weewx[6499]: manager: Added record 2018-10-25 19
:20:00 CST (1540466400) to daily summary in 'weewx.sdb'
Notice in this case the log time and archive record time are near the same.
Looking further through the log this seems to be the same for the other
loop packets/archive records. Whilst there is the discrepancy of UTC to
timestamp and there seems to be a bit more delay in storing the archive
record things appear to be working reasonably well with nothing like the 2
hour delay of your first post. You might want to try setting debug back to
0, restarting weeWX and then monitoring your log to see if the 2 hour lag
returns. It could be the restart fixed it, raising the debug level only
alters what is logged and otherwise has no effect on weeWX operation so
that should not be what caused the change.
If the 2 hour lag returns then I think you might need Mattew's help, he is
the interceptor expert. He might also be able to comment on the UTC to
dateTime discrepancy.
Gary
On Thursday, 25 October 2018 23:24:03 UTC+10, [email protected] wrote:
>
> Hi Gary You are too polite
>
>
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
