Number modes

[ivanfmartinez]

I just started with integration and found that some numbers are with sliders and others not.

Checking HA documentation for NumberEnyity I found that without mode attribute it will let HA to decide which UI to be used.

https://developers.home-assistant.io/docs/core/entity/number/
"Defines how the number should be displayed in the UI. It's recommended to use the default auto. Can be box or slider to force a display mode."

For most of cases I prefer the numeric value instead of slider, what you think about an option to select which mode should be passed to HA.

The slider is good for some small values, but not for bigger ranges. Also the slider does not show the direct value, and HA docs does not explain how exctly it will select the ui item.

For example this AC Charging power is show in W on the luxpower app/web interface and here came as percent, looking only the slider we cannot see the value without clicking and viewing (or creating a simple-entity view)

Seeing the numbers in "box" mode can made easier for users.

But I want to hear from others.

[dmode9000]

Totally agree. All the numbers should be in "box" mode. Sliders are too dangerous because you can easily mess up an important setting just by accidentally hitting the slider on your phone. I'm 100% behind using boxes - it's much safer.

[ant0nkr]

I'm not sure about all numbers. I think, % types better to leave sliders. But, others - yeah, it seems Box type would be better.

[ivanfmartinez]

I'm not sure about all numbers. I think, % types better to leave sliders. But, others - yeah, it seems Box type would be better.

@ant0nkr depending of % value it also can be dangerous.

I'm currently using a temporary connection to test inverter. I have limited in 500W on the web interface, this field is converted to percent on modbus register (0.5%) a single wrong click can make this percent became 1% which will double the current and that will trip the breaker because it was on a circuit that have other devices.

I know that as @dmode9000 said we can use customize, but if user can select on UI like as a parameter like 'use all numbers as box' can be very easy, if not selected it can still with the "auto" selection.

If we decide what can be a good way to go, I can try to make a PR.

[dmode9000]

I don't know how others deal with sliders, but sliders drive me crazy when I need to select a specific entity value, and the thing jumps way below or way above the target when I click it. So in all integrations where there are critical entities with sliders, I force them into box mode through customize.yaml. Here's what it looks like now on guybw's integration:

customize:
  number.lux_ac_battery_charge_level:
    mode: box
  number.lux_ac_charge_battery_current:
    mode: box
  number.lux_charge_current_limit:
    mode: box
  number.lux_ac_charge_start_battery_soc:
    mode: box
  number.lux_ac_charge_end_battery_soc:
    mode: box
  number.lux_forced_discharge_battery_level:
    mode: box

[ant0nkr]

I don't know how others deal with sliders, but sliders drive me crazy when I need to select a specific entity value, and the thing jumps way below or way above the target when I click it. So in all integrations where there are critical entities with sliders, I force them into box mode through customize.yaml. Here's what it looks like now on guybw's integration:

customize:
  number.lux_ac_battery_charge_level:
    mode: box
  number.lux_ac_charge_battery_current:
    mode: box
  number.lux_charge_current_limit:
    mode: box
  number.lux_ac_charge_start_battery_soc:
    mode: box
  number.lux_ac_charge_end_battery_soc:
    mode: box
  number.lux_forced_discharge_battery_level:
    mode: box

Hi.
Yes in v 0.2 there is a boxes, not sliders.