For some reason the input number seems to be restricted to a maximum accuracy of 0.01. This means I can’t for instance put in my gas and electricity prices up to the significance I’d like to, I have to make templates out of them. But it appears that breaks my history and won’t keep accurate costs made in the past. Also, it says in the documentation step size is restricted to 0.01, but it won’t accept a number smaller than 1 in the interface for me.
Hmm, I think I put my energy tariffs in a template sensor because I couldn’t get all decimals in an input_number.
Must have been the GUI then
BTW, step is used by the increment/decrement service calls and the slider. As tom_l had shown, the input_number’s state value can be much smaller than its step value.
Ok, that is weird, it simply won’t accept anything smaller than 1 for me (I’m on 2022.10). I’ve been able to force it to accept it by editing it afterwards, but the input seems to be rounded up to the hundreth.
So I can’t put in my tarifs like Tom…
I think I understand the limitation you are experiencing.
An input_number entity appearing in a Dashboard view allows you to enter a value smaller than the entity’s step. In the following example, input_number.sample has a step of 0.001 but accepts 0.0005.
Its value is confirmed to be 0.0005 in Developer Tools > States:
In contrast, if you click the input_number entity and try to set its value using the pop-up box, it limits the value to its step value. In the following example, the state value of input_number.sample is 0.0005 yet its pop-up box refuses to display that value and defaults to using its step value (0.001).
Nice, I can confirm that this does work, so it appears to be a bug. Although I think having the helper GUI be able to select anything for the step and accuracy would be the better solution, for now I just used the dashboard to change it.