[FEATURE] Improve precision and usability of the Grid Power Target control

[BHNDNL]

Area of the proposal

Sensors, entities, or statistics

What problem would this solve?

The Grid Power Target slider is extremely sensitive, making it difficult to set an exact target value.

Precise adjustment is difficult on both desktop PCs and smartphones. Small movements of the slider can cause significant changes to the target value.

Proposed solution

Improve the precision and usability of the Grid Power Target control.

Suggested changes:

• Allow direct numerical input of the target value (in watts).
• Provide finer adjustment increments.
• Improve slider sensitivity and touch handling.
• Ensure reliable and precise operation on both desktop and mobile devices.

Example use case

When configuring the battery system for zero-export operation, I want to set a Grid Power Target of +20 W to maintain a small, consistent grid import and avoid accidental grid export.

However, the current slider is too sensitive to reliably select an exact value. Small movements can change the target by several watts or more, making precise configuration difficult on both desktop PCs and smartphones.

Expected result: I should be able to enter or select exactly +20 W and have this value applied reliably, ideally using direct numerical input or fine adjustment steps.

Who would benefit from this?

Most Omnibattery users

Alternatives or workarounds

No response

Additional context

No response

Confirmations

• I searched existing discussions and did not find the same proposal.
• This is a general feature idea, not a request to support a new battery brand or model.
• I understand that community interest and technical feasibility influence prioritization, and that no delivery date is guaranteed.
• I removed passwords, tokens, API keys, complete serial numbers, IP addresses, and other sensitive information.

[github-actions[bot]]

Thanks for the suggestion! 🙌

Here's how this works:

• Vote by clicking 👍 on the original post — not in the comments
• The more votes an idea gets, the higher it moves in the priority queue
• I review feature ideas periodically and implement the ones that benefit the most users

If your idea is very specific to your setup, it may not make it into the core integration — I'll try to suggest a workaround in that case.

Feel free to discuss details or alternatives below.

[ffunes]

Thanks for the idea! Implemented in a0eb6ec: in the panel you can now tap the value next to any slider and type an exact number (Enter or tap away to apply, Escape to cancel). It's clamped to the entity's range, so +20 W is one tap away.

It ships in the next beta and in the next release.

[anorakophobia]

(AI-written on behalf of @anorakophobia)

Thanks for the slider input, @ffunes. One side effect: since a0eb6ec the pytest check on release/v1.6.0 (and on every PR based on it) fails on test_frontend_slider_interaction.py::test_dashboard_sliders_hold_the_submitted_value_until_ha_confirms_it. It counts _markRangePending calls and expects two; the new typed-value path adds a correct third one. To help get CI green I opened #791 (test only). I hope that's OK, and sorry if you were already on it; feel free to close it if it doubles your work.

[ffunes]

In the Omnibattery panel you can now tap the value next to any slider and type an exact number (Enter or tap away to apply, Escape to cancel), so a +20 W grid target is set exactly. This ships in v1.6.0. Thanks @BHNDNL.