Release 2.2.8 issues

This is the smaller one. The largest is 4306528

This error is typically indicative of the browser itself having issues keeping up. I’ve sometimes seen a browser hang like this when it is struggling to render a lot of data. You might simply have a lot of data on your logs page and the browser is hanging while trying to render it all.

If you sit there and wait, does the browser ever resolve the hang on its own?

If the browser window hangs you can either

  1. Refresh the window (doesn’t impact the hub’s processing just issues a reconnect and refresh)
  2. Open another tab/window and access the hub
  1. Refresh the window (doesn’t impact the hub’s processing just issues a reconnect and refresh) - No Impact
  2. Open another tab/window and access the hub - Yes, I can open another tab and access the hub and all the function work while waiting on the log files.

C7 for example


Apps

I'm clicking around
image

and this
image

Why is thisi growing??

Note the C5 doesn't have this issue.

I thought I heard that they should be set at 11 as the lowest, otherwise it causes the database to compact itself frequently. Just a thought.

1 Like

LOL I'm lower. Why 1-20000 value?
I'll set to 11 and see.

And that can cause issues. Just the way it is. I can only surmise that 1 was logical as a low point, but issues surfaced later.

That was fixed in 2.2.8

2 Likes

How long will it clear up.? C7 was 5 and C5 was 10

As @aaiyar said, it's fixed. Maybe/Maybe not - don't know. But, unless I'm missing somethings, your C7 would be deleting more records, more frequently (5 vs 10).

I'd suggest you fill out a trouble ticket. Unless Hubitat chimes in with a known issue, you're just going to get (more) frustrated.

1 Like

OK thank you for all of your help.

2 Likes

FYI, AFAIK, those values only take effect after a reboot. But @gopher.ny is the best person to ask.

I have noticed the same issue viewing the logs. I only mention it because it is different that on 2.2.7 and is much slower to display,

This is mainly just an annoyance since everything else is working. I can do other things on the hub in a different tab and the hub is still catching events and running automations while the past logs load.

Opening current logs is fine. Opening past logs takes a very long time but does eventually display. I get the Wait prompt two or 3 times before it displays. Past logs were always a little slower to display but in 2.2.8 the delay is much longer.

1 Like

2.2.8 doesn't do it any more - caused more trouble than it's worth. It's the same behavior for all values now.

About an hour or you can run http://your.hubs.ip.here/hub/cleanupDatabase endpoint to force it immediately. It will take a while to come back, most likely.

2 Likes

@gopher.ny Is the Hue Group bug a known issue?

It's noted, yes.

2 Likes

Thanks. I use a lot of groups, so none work. I was trying to avoid having all of the bulbs shown as devices. Oh well.

1 Like

C7 came back right away as Done and C5 took a two of seconds longer. Thank you for the information