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
input_number does not work as expected #22
Comments
Yes. That's what the template-entity-row does. |
@thomasloven you're the owner of this component and can do waht you think is right but don't you think things like that should be reflected in the documentation? |
The thing is that would require special cases for every type of entity row, and that's an effort I'm not ready to put into this. Maybe try this instead? |
I agree.
I understand it but wanted to use that feature is it's there
well, I didn't want to create a complex layout out of multiple horizontal/vertical stacks. |
That link wasn't for the conditional card, but for the conditional entity-row, which was added in 0.105 or 0.106, I think. It's not templateable, though, but I may create another entity row for that at some point... unless someone else does first. |
HA: 0.106.6
This component: 1.1.0
Browser: Safari, Chrome
OS X 10.11.6
When I use this entity row for
input_number
, I get a read-only representation of it regardless of itsmode
.Here is my config:
The text was updated successfully, but these errors were encountered: