Done. I'll watch the logs.
Thanks for the suggestion. Odd it would complain after a few years.
My friend is still here on the latest beta.
Maybe prime numbers? 
From scanning the events, it looks like the “base” data (which is supposed to be gathered very infrequently) is getting in with the other polls.
Maybe causing the 408?
I can increase the poll times and make some off the hour axis.
Just weird since .154 all was happy.
I went all prime. 23, 67, 151, 13 (hours)
If you watch the lastpoll current state while you do a refresh, you will see:
basedata
poll1
poll2
poll3
basedata
poll4
Looks like basedata is sneaking in where it doesn’t belong.
I get
basedata
Poll1
basedata
Poll2
Poll3
Poll4
and it threw this log
dev:12282025-11-14 16:07:46.762warnStatus 408 on H2 request
It depends on what queue he has them all set to. Might have stuff bucketed badly.
On a Refresh, either at startup or when manually initiated, basedata will run twice to make sure the firmware version is captured correctly (there was a version that delayed updating the firmware number after a firmware update).
2 Likes
So is this non-issue then?
It just started the last few betas but I can just ignore it if it's "Mostly Harmless".
Douglas Adams forever. 
It’s curious that you have these problems that nobody else has
2 Likes
Pretty much. Data in that group is a little behind for one cycle, but recovers in the next. H2 data is primarily the Alerts Bubble from the UI .
I’m trying to duplicate, but for the moment turn on the Suppress Warn Level Logging switch in the preferences.
FYI, the above is from a C8 with JS.
Very lightweight with one Zwave device, lock, and 2 Zigbee devices.
As a male I love to suppress any communication. 
Thanks, switch on.
1 Like
My tin-foil hat is probably on too tight again, but it's interesting that the only two known instances of this Warn message so far are JS users 
And starting on .154.
Watson, there is something afoot.
I may have fixed the 408 issue on the H2 data read. v3.1.21 is up
2 Likes
That's great.
I haven't had that error since my last post. 
Possibly something in a beta build fixed it?
Well we have an ounce of prevention then.
Will update.
1 Like
No update shows in HPM, 3.1.19 shows as current.
