it used to show the hub name in the bottom left of the UI. I know in the past there have been some requests for the hub name in the header/etc. But it looks like with this latest release the hub name is gone? Or is it just me/my browser? Either way...that was helpful for those of us with multiple hubs.
Ok, zoomed out on the browser and see it is actually still there...I just can't see it because now the left menu is longer and takes up the space.
It shows up on my PC but not on my mobile device. I'm using chrome on both.
Is this what you are seeing?
It can get covered by the menu on smaller screens. Let's see about a way to fix it.
yeah I found out it's just the fact the left menu is longer now with the added subscriptions...so on a normal browser on my laptop 1920x1080. It isn't viewable.
For now, a fix is to zoom out to less than 100% magnification to see it or Quit Chrome so the previously downloaded files are no longer shown at the bottom of the browser window. Then you will again be able to see the hub name at 100% magnification.
[Edit] You can also click the X at the bottom right of Chrome to hide the previous downloads and then it will also show again.
Hub name will show at the bottom of the menu on small screens starting with 2.2.6.137.
Make the screen less tall, and it will appear. Or is it a larger screen device that's big enough so that name disappears from the bottom bar and does not yet appear in the menu section?
That was just my normal (Pixel 5) screen. So, yes, I didn't see it in the bottom bar.
But, you're right--when I twisted it sideways, it appeared. 
You have a genuine talent for finding use cases that we missed 
Why am I tempted to photoshop a screen shot right now ???
I'm not sure how to take that. 
I guess 36 years as a System Administrator, etc. has given me some special powers. 
I was pretty concerned about the Rule Editing slowness and the rules not firing.
I'm NOT concerned about this one much, actually.
I was curious more than anything.
I mean it in the best possible way. Knowing about rules not firing early enough gave us time to dig in and figure it out before 2.2.6.134 gained a wide installation base - much appreciated!
I gotta say, like most of the zillion other times (here sometimes, but certainly with other issues), it was pure dumb luck.
I was not expecting that at all--because I wasn't thinking there were any changes that might have done that. So, when my "disarm" routine didn't work, I went through a bunch of things to see if I screwed stuff up (re-ran it, checked logs, soft-reset, etc.). I'm just glad you found & fixed it!
Download the Hubitat app
