Right/best way to hide zwave.* entities from the Overview UI?

@rct wrote:

I’m still fairly new to Home Assistant. Things are working well without a ton of effort. One of the things that is detracting to the whole new user experience is all of the zwave.* entities that automatically get added to the Overview UI which usually just show “ready” and make it difficult to find the elements a user should be interested in like the actually control. (Currently, I’ve got about 25 dimmers/switches, a couple of locks, and more to be added.)

This seems like a fairly frequently asked question, but I’m having a hard time trying to figure out what is the right thing to do for the current state of Hass in December 2019. (I’m running 0.103.4 It seems the GUI, automations, etc. all have been significantly improved since much of the documentation and forum threads were written. In particular, a lot of docs/advice related to Z-wave seems out of date Thank you to everyone who has been contributing so much.)

So my question is: In late 2019 with 0.103, what’s the best way to hide the zwave.* status entities so they don’t clutter up the main GUI without removing them completely?

• I don’t want to completely disable/remove the zwave entities from Hass by disabling them, they seem to contain useful diagnostic information that one might need when something isn’t working.
• Ideally, I’d like something that would catch all of the zwave.* entities so I don’t have to maintain a list of every entity name. I still have more devices to add. It would be cumbersome to go into customize and try to hide each of the ``zwave.* entities.
• I’m somewhat assuming that anything in the zwave. domain is primarily related to the zwave network itself for debugging and status information and isn’t a user control like light, switch, lock, sensor, etc.

On a more general note, I wondering does it still make sense for zwave.* entities to be automatically added by default to the main overview UI? It might make more sense if they were grouped, or conditional so that they’d only show up if they weren’t in state ready. It would also make sense if that info was only visible from the Zwave control panel. If every Zwave device is in state ‘Ready’, do a user really need to see that info?

I have to say, currently the UX has gotten pretty good – a device like a dimmer can be easily added from the GUI, the entity names can be customized, and they can be added to an area, so they get grouped in that area’s card. For the most part, no config files need to be edited. Unfortunately, The light or switch entity as well as the zwave.* entity gets grouped into the area as well which detracts from the overall UX.

Thank you.

Posts: 2

Participants: 2

Read full topic