Home Assistant Devs, PLEASE STOP forcing changes to the Developer Tools pages. I don't have any issue with the ongoing upgrades so that non-technical uses have a better experience. I get it. But forced changes to the areas where most tech savvy users generally live and work is just not cool. I'm talking specifically about the addition of Device and Area columns in the States tab of the Developer Tools. I can see the utility of being able to toggle them on and off, but simply forcing us to accept something that is unnecessary most of the time doesn't sit well for me. Yes, its a minor change, and yes I'll get used to it; but for pete's sake make these 'extras' optional!!!!! A simple toggle to turn on/off would be great. Set it to on by default. I'll turn it off if I don't need it.
As each new release is rolled out, I look forward to seeing where HA is going. Catering to the non technical user is a great way to bring a really good product to the masses. For the most part the devs continue to bring the more technical aspects of HA to the lay user by way of an easy to use UI. Thats all good by me. However lets not forget that there are still LOTS of experienced users that tend to work best using muscle memory. Things that move or change in the page layout slows down our workflow. Things that are 'unnecessary' impede progress until the new muscle memory is learned. Its not a big ask to request that backend changes are presented in a way so that power users can elect to enable/disable the new change. This should be a core value in my opinion.
Just my humble opinion. Haters can hate it. Thats OK.
I didn't even notice it until you mentioned it.
The developers have repeatedly said they are not interested in supporting a huge amount of frontend configuration options, but you can suggest it here: home-assistant · Discussions · GitHub
+1
It fills the screen, has (for me ) 0 value too and is also inconsistent as attributes can be switched on/off
If/when you open a request, let me know so I can try to add interest 
That's a good point.
There was quite a bit of discussion about this during the beta... I wouldn't bet on the new columns going anywhere.
Aren't "Device Name" already a default part of the entity-names ? ( Redundant column in my opinion ) And you can't even use it to sort
They're part of the composed entity ID, but not the entity name... here's an example of one of the event entities that Alexa Devices just added...
The entity ID is composed like:
domain.[area]_[device name]_[entity name]
I'm not opposed to the new columns, per se, but I find all the variations in how names and IDs are composed/displayed to be a bit chaotic. It doesn't seem like it will really decrease the amount of renaming that users will end up doing... but it may change where they are doing it.
So ,Maybe that was what i mend, as ALL my "Entities" in the left 1st Column has it's DeviceName included
