Replies: 2 comments
|
Hi, can you please provide some screenshots of how the ui will be changed? So that i better understand how you are using it? Thank you! |
0 replies
|
Can you try https://github.com/dominikamann/oekofen-pellematic-compact/releases/tag/v3.6.5 (now 0.1 steps are possible by default) You can now easily build it by your own by using HA Helpers. 1.) Create a new entity for Temperature
2.) Create a automation to set the value to the current temperature
3.) Create a automation on value change to set the new temperature to the heater
Now you can use your own helper entitiy and you will see input fields instead of a slider. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment



Uh oh!
There was an error while loading. Please reload this page.
Hi !
First of all, thanks for this great integration I'm using for months.
Nevertheless, i have a minor trouble related to input_number's
modeandstepconfiguration values.In fact, according to me, the default slider behavior is not well adapted to change some of them (eg.
number.pellematic_heating_circuit_1_heat_tempornumber.pellematic_heating_circuit_1_set_down_temp)Most of the time, the screen is too small to have a correct precision using a slider, and moreover, you can easily move a slider by error while scrolling your phone.
I know that i can define the desired Ui behavior in a dedicated card, but for my case, the "box" mode and "0.1" steps will just be the perfect default (the one that will always appear in the default history card).
Thus, I tried to change some input numbers' mode and step in the "Developer Tools > States" interface from:
To:
It works and the behavior is exactly what I expected, until the State is overridden by the integration's next refresh 😞
Is there a way to proceed ? Or, maybe, my question is out of scope ?
Thanks for your time and help.
T.
All reactions