-
-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Support for input_number domain #188
base: main
Are you sure you want to change the base?
Conversation
Outstanding bug: Rounding error when input_number step is set to certain values (observed easily with step set to 2 or 3)
was just about to suggest this! |
the step and the max of an input_number entity. Appears that at this time applyStep() is unnecessary, and was in fact causing the problem I have tested stepped sliders of both input_number entities as well as light and climate entities, and stepping still works as expected when applyStep() is not called at all. This does not resolve the issue where step count results in "illegal" values on certain input_number entities.
I wish this will be available soon. I'm real waiting for this. This add-on is wonderfull. |
If I understand well, the fonction is ready with a minor bug. Can you merge it in a beta we can try it ? |
May this pull be merged? Looks like a very nice feature. Thank you very much Liz! |
PR submitted to maintained version of slider-button-card custom-cards#7 |
How should be used? I am trying to add an input_number but I get error, like does not exists... |
This was requested in issues #161 and #7
This adds support for the input_number domain and makes the entities far far easier to manage on a mobile touch display vs. the builtin entities card.
One note: There is a current oustanding bug where if the input_number.entity.min value is not cleanly divisible by the input_number.entity.step value, then the slider card is off by an amount. If your input_number has min = 5, max = 25, step = 5 then it will work just fine. But if the step is 2, then it will be off. This also has the side effect of changing the input_number to an "illegal" value when modified via slider-button-card. Step = 1 always works.
If anyone has any insight I would appreciate the help. Otherwise, I am submitting as is, because it is largely functional right now.