[Resolved?] Hub load is severe caused by Google Home Integration

Woke up to see the "severe load" message on my C-8, but only after I used chrome rather than firefox. On my android app, trying to connect to the hub showed "unsupported browser." After logging into the hub in chrome, I saw (see) a lot of activity by the Google Home integration. Revisiting the app and simply clicking "done" quenched the "load" issue, but it seems to me that the Google Home integration is still taking up a lot of CPU. Here's a log entry for the app - haven't seen this before:

app:7072026-05-16 10:46:44.659 AM

debug

postReportState payload:[devices:[states:[650:[online:true, isLocked:true, isJammed:false], 651:[online:true, isLocked:true, isJammed:false], 781:[online:true, brightness:50, on:false], 785:[online:true, on:false], 787:[online:true, brightness:34, on:false], 794:[online:true, on:true], 667:[online:true, on:false], 796:[online:true, openPercent:0], 668:[online:true, brightness:100, on:false], 797:[online:true, openPercent:0], 673:[online:true, brightness:83, on:false, color:[name:Soft White, temperature:3182]], 676:[online:true, brightness:85, on:false], 677:[online:true, brightness:5, on:false, color:[name:Orange, spectrumRGB:788480]], 294:[online:true, on:false], 679:[online:true, brightness:100, on:false], 680:[online:true, brightness:100, on:true], 808:[online:true, on:true], 681:[online:true, on:true], 683:[online:true, on:true], 684:[online:true, brightness:5, on:false, color:[name:Soft White, temperature:2827]], 685:[online:true, on:false], 692:[online:true, temperatureAmbientCelsius:21.7], 693:[online:true, on:false], 71:[online:true, temperatureAmbientCelsius:18.1], 583:[online:true, temperatureAmbientCelsius:17.8], 330:[online:true, openPercent:0], 589:[online:true, isLocked:true, isJammed:false], 595:[online:true, isLocked:true, isJammed:false], 732:[online:true, on:false], 733:[online:true, on:false], 225:[online:true, brightness:3, on:false, color:[name:Red, spectrumRGB:458752]], 609:[online:true, openPercent:0], 739:[online:true, on:false], 611:[online:true, openPercent:0], 230:[online:true, temperatureAmbientCelsius:23.1], 359:[online:true, on:false], 232:[online:true, temperatureAmbientCelsius:21.1], 744:[online:true, on:false], 616:[online:true, on:false], 360:[online:true, on:false], 617:[online:true, on:false], 233:[online:true, temperatureAmbientCelsius:22.0], 618:[online:true, on:true], 234:[online:true, on:false], 619:[online:true, on:true], 235:[online:true, temperatureAmbientCelsius:20.7], 747:[online:true, on:false], 749:[online:true, temperatureAmbientCelsius:20.4], 625:[online:true, on:false], 255:[online:true, brightness:5, on:false, color:[name:Red, spectrumRGB:786432]]]]]

Any clues as to what's going on?

TIA, Jim

Here's a little more info - I'm getting lots of warnings about my google smart clocks and displays, interspersed w/ errors regarding my Honeywell thermostats:
dev:1542026-05-16 11:19:51.076 AM
warn
method initialize of child device JLC MBR Clock ran for 128,601ms
dev:3962026-05-16 11:19:50.667 AM
warn
method initialize of child device google-nest-hub on 192.168.1.95 ran for 133,177ms
dev:1552026-05-16 11:19:50.611 AM
warn
method initialize of child device JWC MBR clock ran for 133,615ms
dev:1532026-05-16 11:19:50.575 AM
warn
method initialize of child device Kitchen display ran for 133,562ms
dev:2652026-05-16 11:19:48.403 AM
info
Get Operating State: idle - Fan to idle
dev:2652026-05-16 11:19:41.388 AM
debug
2nd Unauthorized failure ... giving up!
dev:2652026-05-16 11:19:41.378 AM
warn
Something went wrong during login: java.net.SocketTimeoutException: Read timed out
dev:2652026-05-16 11:19:30.596 AM
debug
Calling refresh after Unauthorize failure!
dev:3962026-05-16 11:17:35.501 AM
warn
method initialize of child device google-nest-hub on 192.168.1.95 ran for 131,991ms
dev:1532026-05-16 11:17:35.010 AM
warn
method initialize of child device Kitchen display ran for 131,017ms
dev:1552026-05-16 11:17:35.002 AM
warn
method initialize of child device JWC MBR clock ran for 131,024ms
dev:1542026-05-16 11:17:34.995 AM
warn
method initialize of child device JLC MBR Clock ran for 131,506ms
dev:1552026-05-16 11:15:22.001 AM
warn
method initialize of child device JWC MBR clock ran for 133,787ms
dev:3962026-05-16 11:15:21.536 AM
warn
method initialize of child device google-nest-hub on 192.168.1.95 ran for 133,375ms
dev:1542026-05-16 11:15:21.504 AM
warn
method initialize of child device JLC MBR Clock ran for 132,897ms
dev:1532026-05-16 11:15:17.782 AM
warn
method initialize of child device Kitchen display ran for 129,668ms
dev:2652026-05-16 11:14:30.556 AM
debug
Scheduling a retry in 5 minutes due to Unauthorized!
dev:2652026-05-16 11:14:30.555 AM
warn
Something went wrong during login: java.net.SocketTimeoutException: Read timed out

Legend:
154 = Lenovo smart clock
396 = google nest hub
153 = Kitchen android tablet displaying dashboard 2
155 = another Lenovo smart clock
265 = Honeywell wifi thermostat
264 = 2nd Honeywell wifi thermostat
707 = google home app

Hub is connected via ethernet w/ a static IP.

Well, it looks like a simple reboot of the Google Hub cleared up most of these entries. Hoping for the best...