It looks like this has been addressed in:
1 Like
Yes so I see. Well at least you can see how NOT to submit them!
1 Like
Thanks for the heads-up; I was unaware that this was the reason for my troubles.
Thank you for the update and bug reporting!
Brilliant logic… anybody with too many badges on an autogenerated page should be the ones encouraged to take control of their dashboard… not newer users that are still trying to get up to speed / still afraid to commit too much time into a build only to have the Devs come through 2 months later to make a ‘small tweak’ that completely wrecks what the user worked for hours or days on…
…swear to god… almost like they’re trying to make the entry hurdles new-user-prohibitive.
This is what you want @labob246 https://github.com/zwave-js/node-zwave-js/search?q=barrier&type=issues
1 Like
There’s an FCC issue standing in the way of operating the barrier currently. Just FYI. It will be fixed soon, but I’m still waiting for the migration tool
2 Likes
Surely creating your own dashboard is far easier than dealing with potentially hundreds of little badges that get auto-placed in a big mess…
1 Like
Sure. And until it gets to the point of ‘potentially hundreds’? Currently- I have 35, with room for 7 more at current screen before it rolls to a third line.
For a new user- a) testing packages or b) gradually adding devices and integrations… for a ‘default, out-of-the-box’ initial showing- wouldn’t you want it to show more of what it can do? Not less? …even being able to see a badge, even as a placeholder, can help imagine what a layout should /maybe/ look like.
In my particular instance- I’m still running on dev hardware (pi3, mSD, wifi) while I try to research previous pitfalls before commiting to my pi4/SSD build… trying to avoid hiccups involving things like setting the secure zwave key after initial setup… or if there’s a newer, more better way of installing various hardwares- my nortek zwave/zigbee, RMmini3, bluetooth plant monitors and zwave door lock all had particular setup steps…
But yeah… creating your own dashboard is a better solution… when somebody gets to that point… honestly- I’m more interested in integration automations than interface layout, as of recent… and truth be told, likely look towards something floorplan based more than strictly Lovelace… haven’t looked into it enough to know whats really possible… but now… guess I’ll just hang out back here with the 2020.12.1/5.10 that my last snapshot was at.
Old Way - default badges until user is ready for custom build
New Way - default badges for nobody
Badges on the default page aren’t the problem. Users with large enough installs that haven’t tended to their UI before blaming ‘too many default badges’ as the problem are the problem.
The entities are still added to the default view, just not as badges.
Still… the purpose of the sensor badge is to collate ‘quick glance’ type info at the top of the page where it makes sense, not buried down with all the other cards…
With badges I can view my google traffic time to work, temperature, bonsai soil moisture and checking account balance without scrolling. not to mention- at some point CUPS network printers started getting auto-detected… can’t say that it would have occurred to me to even /want/ a printer status badge… having placeholder badges reminds me that my 3d printer card can have badges for power stats… that I could make a card of battery sensors…
to make things ‘better’ for a situation that should already be remedied before its a hurdle.
I accept that badges can be useful, there should be an option to turn on the old functionality. Perhaps that will be done, but I won’t be (can’t) code it.
Have you seen the official demos? I found it useful originally.
I honestly think this discussion is highly subjective. I’ve been around here long enough to see drastically different needs and designs. To code a possibly comprehensive default dashboard given whatever each new user’s initial set of hardware, etc. could be and what you can do with it seems like a fairly tricky problem (to code) to me — and most users (if not all, eventually) will swiftly move on from the defaults. To use your examples: I have no need for bonsai moisture control or network printers.
There are also roughly two kinds of users starting with HA: Those new to home automation, and those migrating from another platform. They will have different initial needs.
What’s possible seems almost infinite and perhaps there’s enjoyment in the process of discovery but this is just my view.
But, back to your very first remark: I had a case of starting up a new HA and seeing like a 100 hundred badges. It overwhelmed me so much I just immediately removed it all. So, to me (just one of many users), I welcome the change.
So I was planning to link the feature request or with post that lead to this change but I can’t find one so I’m a bit confused where the feedback leading to this change was collected.
Regardless it sounds like there should be a setting either specifically for the default dashboard or for any dashboard to show all entities as badges at the top. Would suggest you open a feature request for that.
Personally I hate the badges. I think they look ugly, don’t show enough info to be a useful overview and just end up eating valuable real estate at the top of my dashboard. If I just want to look up an entity I go to developer tools by default since I want to see and search on the full state of things, attributes included, in addition to being able to interact with it. But I also am probably more picky then most as I won’t even use autogenerated layouts, I use the layout card in panel mode in basically every dashboard I make.
But truth be told it doesnt really matter what any of us think about your ui. You should be able to make the UI you find most useful for you, your opinion is really all that matters when it comes to your ui. I assume there is a good reason somewhere for why the default was changed but since it has degraded your experience you should request an enhancement for a setting that allows you to bring it back.
Thanks! Figured there was one, just didn’t know where to link.
Same for me using Qubino Flush Shutter module… 
I’m now getting the same issue. I’m running old versions of the FW on 21 TP-Link devices, restored back to a previous version of HA worked again tried the latest a second time…broken.
It does not work for me even on previous version. How far back did you go? Which version makes it work?
It’s only the latest version that affected me. I just figured out that if I remove the outlet and only leave bulb and switches it works again. It appears the TP-LINK integration stopped working with switches and maybe is causing the issue. I’ll try to troubleshoot later tonight
Actually no, but since I’m also not ready to turn my attention I haven’t really looked so would have been easy to slip by…
But that’s the thing… the default doesn’t need to be anywhere near per-user comprehensive. It should essentially be a functionality-dump where it just sees things, tacks them onto a page…
Further proving the ‘by the time it gets complicated enough, that’s who should be moving on from default anyway’ point.
And? My examples wouldn’t be part of your install… you wouldn’t have the hardware so the default dashboard wouldn’t show those things.
New users need to see what HA is capable of, migrating users will be moving past defaults soon enough anyway.
okay, so you had like a hundred badges, removed them… then what did you do? Are you still using the default dashboard? I think it’s important for new users to see ALL varieties of how information can be presented in a ‘food for thought’ sense…
Further- it’s the idea that even sensors that I’ve manually defined in the config don’t display now either… stuff like this gets changed while the main z-wave wiki page still doesn’t link or mention the network key… random bullshit changes that break installs for no good reason. ‘clutter’ on installs that are beyond the point that complaining can be done in good faith.