Re: [weewx-user] catching the 'why' of engine.py exiting

Tue, 04 Aug 2026 17:09:01 -0700

pm2_5 all null is the pathological case.

Would you run this against your database and post the time?

sqlite3 weewx.sdb
.timer on
SELECT dateTime, pm2_5 FROM archive WHERE pm2_5 IS NOT NULL ORDER BY dateTime DESC LIMIT 1;

On Aug 4, 2026, at 5:01 PM, [email protected] <[email protected]> wrote:

OP here. No skin.conf and no aqi_source configured:

aqi_enabled = 1
aqi_location_enabled = 1

There is a pm2_5 column in my database but all values are null

On Tuesday, August 4, 2026 at 4:39:49 PM UTC-7 John Kline wrote:
Vince,

That’s worth noting — if he has no aqi_source set, he’s on the “auto” default, which is one of the values that still triggers the archive scan in beta4. So whatever got his cycle time down, it wasn’t that gate, and I don’t know what did.  We also don’t know if the OP has pm2_5_aqi as a column in the database; nor do we know if his archive records have values for pm2_5.  As such, we haven’t reached any conclusions on what is causing the slowdown.

My advice to the skin author still stands. The effort to find a non-null pm2_5_aqi or pm2_5 should be bounded by the last day or two; and not go back 13 years (in this case).

John
On Aug 4, 2026, at 4:27 PM, Vince Skahan <[email protected]> wrote:

John -  I see no aqi_source in the weectl debug the o.p. sent me.  He must be running whatever the default is unless he edited skin.conf to set it there.

There is no mention of aqi_source nor its options anywhere in the wiki or instructions that I can find.  It 'is' buried and set to 'auto' in skin.conf with no commentary at all.

On Tuesday, August 4, 2026 at 3:15:37 PM UTC-7 John Kline wrote:

On beta4. I diffed it against beta3. The scan is unchanged — same _archive_latest_numeric, same unbounded query. What changed is the gating: a new aqi_source option (auto / local / forecast), with the archive path running only when


local_aqi_enabled = aqi_enabled and aqi_source in (“auto”, “local”)


aqi_source defaults to “auto” — which is in that tuple. On defaults, beta4 still runs the scans. So: which did you set? If you set aqi_source = forecast, that explains your speedup, and the bug remains live for anyone on defaults with a big database. If you’re on auto and it’s still fast, my diagnosis is incomplete and something else in beta4 deserves credit.


 

--
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].

--
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].
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/d91d8619-53dd-49b0-b3f0-76292f8737c8n%40googlegroups.com.

--
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].
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/374AE33F-67F6-47F8-865D-A42A054BD09D%40johnkline.com.

Reply via email to