wow, you have a pretty low bar for what you feel is “incendiary”.
the title of the thread literally just gives the facts as seen from the viewpoint of the OP…
the cards are useless to the OP because they are disabled and they take up too much space, especially since are useless because they are disabled.
Just the facts…nothing “incendiary” at all.
Tell me what you think would be a less “incendiary” title that conveys the intent of the thread and I’ll be happy to change it.
I tried the dev-tools service and for some reason it only worked half the time and I kept getting an unauthorized access from an IP that eventually caused my IP Ban to kick in that banned 127.0.0.1.
And the fact that you have to then go to the HA log to see the results is extremely inconvenient at best.
As far as the accuracy of the config checker goes, I remember a long time ago there were a few issues with it but I use it exclusively to check my configuration changes before I restart (from the button in the ui) and I don’t remember the last time I’ve had any issues with it not finding an error. And it’s almost instantaneous. So there’s that.
I don’t think the OP wants those two panels disabled. I think they want the new ones that have been added above those panels to be blocked. The ones you pointed out aren’t the useless ones.
Just chipping in here too, i like the whole new aspect of GUI for new users. Makes it easier for them to start quickly and move along.
That said i also do use the config checker a lot. All solutions provided are nice but having the button on the first page is just a no brainer. Or better yet, just give it another tab on the page before that. Cosmetics aside i run that thing like a bazillion times when i’am working on it. Doing a config check from hassio takes 8 to 9 seconds! That is just too long for a quick check, restarting takes me 10 minutes (i have too many zwave) so it is important to have a quick check (although maybe not 100%)
Perhaps the author of visual studio code plugin can make it such that once you save your edits it does a call of some sort and verifies it.
Either way, i’am used to it already now but still it saves me 0.3 seconds for scrolling down.
And for all the basher/hate whatever here, sometimes its better to just write text ‘politically’ correct. Since what someone means doesn’t always come over the same way. Thats why i always tell friends ‘if you text someone more then 5 times, just call them’ because a lot of crap can get in between the lines with no bad intent.
It was not my intent to set of a firestorm of criticism for anyone. It was my intention to ask if it was possible to easily hide or minimize the forms that were taking up a lot of space and causing extra scrolling.
Just exactly what I asked – now edited to be more tactful without changing the meaning one iota.
I had tried to hide the forms with uBlock Origin already but I didn’t know about “cosmetic filtering” and consequently the webcomponent elment names were not hiding when I tried it. Now that I know how to hide them with uBlock, I am happy.
And as I said midway through this thread, I do sincerely apologize if anyone was offended.
I took a peek at the source code today and as far as I can tell the config panel, service call, and SSH are all ultimately calling the same script to perform the checking,
Yeah, I don’t know why there would have been any difference. I was just reporting that there was. and it seems others have seen differences too in the amount of time it takes to run.
I don’t think the OP wants those two panels disabled. I think they want the new ones that have been added above those panels to be blocked. The ones you pointed out aren’t the useless ones.
My screenshot was showing what it looks like with the 2 panels blocked using the filters I posted
I had tried to hide the forms with uBlock Origin already but I didn’t know about “cosmetic filtering” and consequently the webcomponent elment names were not hiding when I tried it. Now that I know how to hide them with uBlock, I am happy.
@a3a Yep the Shadow DOM thing with HA can be a bit of a pain here, but if you use ‘inspect element’ on your browser you can still hide elements.
I think @rpress said it best. It is surprising how much room a disabled feature takes up. Sure it is a small scroll, but when you do it dozens of times in a day it certainly adds up to an annoyance… Please consider hiding the map when disabled, only showing the map when needing to select a location, or moving the check config/restart buttons.
I’ve released version 0.1.0 of a Config Check AppDaemon app, that will allow you to initiate a configuration check from Lovelace and see the results in the frontend (and restart automatically if the configuration is valid). Full details here: Apop's Home Assistant Setup and Other Resources