I noticed the same thing on my devices. I thought it might have been my imagination until I rolled back to 2.3.9 (due to different issues) and found it to be considerably faster rendering the UI than 2.4.0.
I tend to keep devices for several years so none are cutting edge.
Looking again at my image, perhaps I missed a horizontal slider? Too much effort.
I searched, but couldn't see it anywhere obvious. I've rolled back, cba with unnecessary issues. I do try to stay current but I won't be upgrading moving forward.
local
Looks like I'm sticking with 2.3.9. I'm not upgrading hardware.
I’m running 2.4 on a C8 Pro and a C7, I can’t see a huge difference between them in UI speed.
Perhaps you should take a look at your apps and devices in logs to see if there is something consuming a lot of CPU time?
I don't necessarily think it's all the HE hardware. I'm running a C5. I can see stark differences, even on 2.3.9, using the different devices (phones, tablets and laptops) that I have here. It seems there is a lot going on when rendering the UI.
For me, the sluggishness isn't enough to stop me from updating again when they get things fixed but it is a concern and hopefully won't continue to degrade.
Yeah, I think the end user device is the biggest contributor. My old iPad is definitely slower than my M2 Max MacBook Pro. But the difference between my C8 Pro and C7 is not significant.
Yes the C7 is slower, but not by very much, and the gap between 2.3.9 and 2.4.0 doesn’t seem to be any bigger IME.
Hi. Sorry, I can see how I may have been unclear.
I'm not upgrading hardware I. E. I'm not upgrading my phone.
I don't intend to investigate apps etc. Everything is fine under the old UI. The new UI is for whatever reason imposing increased demands. Maybe I'm running more, who knows. Facts are facts. Old software is fine for me. New is not.
Sorry if this sounds unhelpful. I've been around tech in various guises for long enough to recognise a situation in which newer, snazzier software places strain on older tech. I this case, maybe mostly down the viewing device
With Hubitat (and my c7), I'm lucky enough to have a perfectly functional system without the need for latest/greatest support.
Ta.
Bingo. I think users are possibly seeing varying degrees of performance changes depending on what they have installed.
I'd bet my left nut the UI is a higher resource hog. But maybe this only manifests in certain fringe cases. And there'll be no chance of a turnaround and/or fix.
Could be worse.
Fair enough, it wasn’t till others commented that I realised the difference was the end user hardware, not the hubs.
TBH, Android hardware has been notoriously poor performing until the last 2 ish years. I’ve tested the UI on a 4 year old base spec 7th gen iPad (A10 Fusion SoC from 2016) and on my 1 year old iPhone 15 Pro (A17 Pro) and while the iPad is a little slower, it’s not enough to be really noticeable, or an issue.
This is despite my iPhone getting a browser bench score of 25.7 and my iPad getting a score of 5.74.
https://browserbench.org/Speedometer3.0/
Out of curiosity, what does your phone get?
Yeah that’s what I suspected, that is a pretty low score, even compared to the 8 year old SoC design in my iPad.
Edit, for sh!ts and giggles, I ran it on my 2 year old M2 Max MackBook Pro (Work supplied). 
Haha. Yeah, my mobile isn't winning any races.
Issue is that it works fine with the old UI, plus everything else I use my phone for on a daily basis. I have no issues streaming Bluetooth audio in the car, hands-free, viewing cctv (local or remote), running semi-complex sharptools dash's.... Etc.
Plus your standard edition daily browsing and comms.
All work a-OK. Never made me think "jesus, this is horrible, maybe it's time I upgraded".
However, I install the new hub firmware, and within seconds I'm thinking my phones a POS.
That's a UI issue. Plain and simple. Something under the hood is resulting in some serious additional overheads. Perhaps this isn't an issue with anyone with more modern equipment, I accept that. No arguments there.
But I'm sure anyone can appreciate that when a device is subject to daily use, using a variety of software and apps, when an app 'upgrade' cripples the device, it's clear where the fault lies.
And that's it, unfortunately.
I doubt anyone will care because whatever changes have been made to the engine only affects people like me, assuming it's some kind of hardware fault, configure issue or whatever.
So I'd be fighting a losing battle.
I get where you are coming from, but the new site uses "Material Design Lite" (at least that's what "inspecting" it shows me), and that is known to be slow on older versions of Android (according to my googling).
It's not the site, it's likely a combo of HW and Android version.
Not familiar with this. New = twice as slow?
Exactly the same experience. I ran that speedometer test on the 3 devices I use most (Android 11 & 2 laptops with Linux Lite) and all 3 registered in the 2s. Even less than your device.
I use these devices daily on the web, navigation, and office type applications without issue. I even use GIMP (Photoshop equivalent) without a perceivable slowdown. The only time I run into a slowdown is with the hub UI. Something in the rendering of the hub's UI is very resource intensive.
I'm sure it's not noticed by the developers because they are using high end hardware but it is a genuine issue that they may want to explore. If someone buys the hub and their first experience is a very slow UI because they don't buy the latest and greatest devices every 2 years isn't going to be good one. A slick UI isn't going to fix that.
We'll be looking into the UI's performance for sure.
Sounds great. Thanks! I'm still going to update to 2.4.0.145 and if I can pinpoint severe slowdowns I'll post where they are on the older hardware
I'm 99% certain it's due to the complicated/unoptimized web page rendering logic, and nothing to do with the hub itself.
I'm using .145 as we speak. Rendering devices, apps and logs takes considerable time.
This also happens on 2.3.9 but when you clear the search bar and enter new search criteria it will take awhile for the old search to clear and the new search to appear.
Anyway, the features in the new UI, like device notes, are worth the delay coming from a 4+ year user. If the code can be optimized that would be great.
Thanks!
App log , device log and past logs seem to take a while to come up and i dont see a lot of differences in the interface.
New UI won't enable Oauth on an app. Reverted to old UI and it worked.
Download the Hubitat app
