Z-Wave Device Configuration, input boxes messed up

Configuration Z-Wave
1

I have some issue with Z-Wave device configuration, the template seems to be messed up. The input boxes are outside of the frame and editing the values is nearly impossible.

I have tried the usual: HA app, Chrome, Safari, empty browser cache. Does anyone see the same? Is there anything I can do to fix this?

image
image716Ă—635 35.2 KB

1 Like
2
3

Have you tried re-interviewing the device? It seems like there was some error and it couldn’t load all of the configuration settings, the empty ones should be filled in.

4

I have the same issue on several devices, I think this has nothing to do with them, it’s a frontend design bug.
The empty ones are not empty, just the numbers are out of sight.

5

If you’re viewing this on a PC browser, try resizing the browser window so it is very skinny. At some point, the input fields will be moved to a separate line, making them wider. Have you tried on a smaller mobile device like a phone? It renders as the “skinny” view.

Wide:

image
image786Ă—663 26 KB

Skinny:

image
image791Ă—698 25.9 KB

6

I don’t know, how to do that in a browser. I expect this to work normal with default settings. :wink:

7

Thanks, what is described in these issues is exactly what I am seeing. I can set the .mdc_text_field css variable in the developer console and the fields become usable… I will update the issues.

8

You don’t know how to resize your browser window? Just suggesting a possible workaround so it’s usable. I guess this was a joke, not really sure…

9

I just misunderstood your message. I was assuming Skinny is some function, I can select somewhere :wink:

Well, exiting full screen mode and making the window “skinny” indeed works to display the hidden values. So yes, suitable as a workaround until the bug gets resolved.

Thanks :wink:

10

:joy: I edited my post, hopefully that’s a bit clearer.

1 Like
11

Same issue here. Thanks for the effective and simple skinnymode-tip Freshcoast.

It might help to add HA version on the github-issue #12874, although it seems to have been present for quite some time so might not be relevant. Mine is 2022.12.3 running on PI-4.

12

I actually deal with this for almost a year, but had not time to actively try to solve it. I did know, that entering values is still possible doing it “blindly”.
So it got on the bottom of my list, as every new release needs my attention for much bigger issues due the massive changes introduced this year…