Nice work - I like the change. It is a step in the right direction and will allow bigger changes down the road. Better to change the UI in incrementally like this instead of a huge change IMHO...
@bravenel @gopher.ny
Guys, while this is a major update with many interesting features, perhaps not the wisest thing to do this update right before a long holiday weekend. The old firmware was great without the update.
Enjoy the holidays. Get some well-deserved rest, have some fun.
And thanks for all the hard work to improve the platform.
If the update is giving you serious issues, like it was for me, it's painless to roll back to 2.3.9.210. It was nice to play with the new UI during the long break and I look forward to everything getting fixed and updating back to 2.4.0.
Thankfully, I havenât noticed the issues that others are seeing, but, then again, Iâve got a simple setup. The occasional errors that I was seeing with the built-in Hue app seem to have been fixed by opening the app and clicking Done, as some others have noted.
My issues has to do with Owntracks and location reporting. I'm not heavily reliant on presence but do have backup rules in place in case we forget to lock the door or set the alarm. The issue was severe enough to cause problems when we were home.
These issues are not unexpected with changes of this scale and adding community apps to the mix. I was actually surprised 2.4.0 worked as well as it did. I did perceive a noticable slowdown of the UI when compared to 2.3.9 on my C5 though.
I actually think it's a good thing to do... Those who want to play with it while on vacation from work can do so and have fun with it, those who don't want any muss or fuss over the holidays can just ignore it, don't update.
The fact that Hubitat allows you to control when you update, and allows you to easily roll back, makes this very easy to manage. 
This
Nice direction guys.
This brings forward a lot of the kind of things that help folk get a quick lay of the land and status of things critical to the overall health of the environment. Thanks !
Side Note:
Donno if it was just my transition in or what but folks may need to be alerted in the upgrade notes to the fact that they may need to go in and mess with the Modes and make a decision about using the Legacy vs the New. Couldn't figure out why my system was not in the right Mode when I upgraded.
I found a bug. If there is a an ' in the device name, then the device page (http://abc/device/edit/xxx) comes up blank... As in no UI elements are displayed on web or mobile. However it works when the device edit page is a slide out from the device list which is how I am able to fix it and prove it out. When I remove the ' the device edit page works. There is no difference in the html source code other than the device name, so it appears to be on the Hubitat side for the script call.
Maybe unrelated, but I have also noticed that the SmartStart component of the (Android) app is also picky about names. I just did away with apostrophes, dashes, etc, when naming a new z-wave lr device, lol.
Youâre not the first one to notice this:
Can you clarify on which device/browser youâre running into the issue? It doesnât seem to be affecting all users.
I don't quite understand what this means? What is the difference?
Noted.
May not affect all OSes/browsers, FYI.
I can reproduce with safari on iOS 18.
Unfortunately, not a fan here. I get why it appeals to most, but this is not for me. I prefer lean and powerful over pretty. This is just too much white space/wasted screen space for me. But, I appreciate the hard work nonetheless - clearly a lot of work went into this.
A couple comments/questions - anyone else experiencing these issues?
-
Scrolling is not smooth on my iPhone. When I go to a new page, and start to scroll, the first swipe seems to scroll just a few lines. It takes a second swipe to scroll smoothly.
-
Perhaps related to the above, when I navigate to a new page on my iPhone, it takes two presses to actually complete the first command. Eg. Going to a device page then pressing the off command.
-
When I am in the zwave details page, if I search for a device using safariâs search bar, I lose the navigation bar at the top of the screen, so no way to go back to the previous menu through the UI.
-
Anyone else notice zwave flakiness after this update?
Haven't seen that at all. Z-wave wasn't worked on at all during this round... What issues exactly are you having? (Remember, correlation is not causation)
Understood - thatâs why I asked if anyone else has experienced anything. Both yesterday morning and this morning, automated outbound zwave commands werenât firing. This morning I tried to repair a couple of devices and the device process hung⌠which I havenât seen it do in quite some time. Then it failed repairing a device that is about 10 feet away from the hub.
If zwave wasnât touched in this round of changes, then Iâll chalk it up to a random issue.
I powered off for 10 minutes and will see how it behaves over the next couple days. Otherwise, my zwave network has always been rock solid. No ghosts, good topography.
FWIW, about 30s is all it takes to allow the radios to reset, longer won't do any better.
I've had a couple instances of Z-Wave flakiness on 2.4.0.x, but nothing consistent or repeatable. 
I ran into this too. Modes didn't work until I picked a modes app.
This is happening in Chrome on Android too. I wasn't sure what I did but have run into it several times.
I think there is a difference between approaching the system from a newbie in a browser on a PC vs daily operational access via the phone. I tend to agree with you as I switched over to the phone ....but back in the browser I'm readily going "yes, this is much easier, comforting, and approachable for new eyes".